Mushiiipeas

If you had bothered to read my first post, you’d know I already posted the issues. The issues I had weren’t addressed or fixed as others were having the same problems. They are still ongoing cloud issues. I initially installed the beta, because i had issues with the public build & thought the beta build might be better, only to do a full circle & go back to the public build which somehow fixed itself. Stop telling people to get over themselves when you have no idea what I had to do or what others are going through. also, don’t bother replying if you’re not here to help or help others or give feedback that might be useful.

Hello again

You are probably reading this too late. For those that are reading this first - STOP - this beta version does NOT work. Fraser, you’ve wasted a lot of people’s time by STILL not giving people a precaution. If you have been unfortunate to install this beta version, go to Page 18/19 & read what I did/had to do. Short version is I reinstalled the old firmware & over a month later it’s been working flawlessly. Not had a single issue, QOS has been working perfectly fine too.

Fraser, it’s been a year & a half & it’s still in beta. I had similar issues to another person with the ‘usrbin dpiclass died’. Not every single person who attempts to install it, will mention it. The reason I posted that, was so people understand the reality of it before jumping the gun & falling in the deep end (something you both failed to mention & would’ve steered me away from had you given a caution). The reason I did that is to help people like the person who commented above. Because, let’s face something you clearly can’t; it’s not a smooth install for everyone either. I think it’s fair to give people a heads up, as opposed to acting like it’s a simple & easy clean install. Also, side note as I’ve mentioned to someone - I’ve reverted back to the original latest firmware as it turned out to be really bad. Also, while you’re aware of the dpiclass issue, you have no fix & still standby the firmware despite having issues which boggles my mind.

No, it’s really bad. I had similar issues to another person. I went back to the latest firmware & installed that. It’s not worth all the hassle. While gaming, it was jittery & unplayable.

Right, so this is for anybody still considering this upgrade. Here are some things you NEED to know. ***PLEASE READ IT ALL FROM START TO END FIRST BEFORE STARTING THE PROCESS!*** it will take approx 2-3 hours so don’t do this thinking everything will go smoothly. it doesn’t work out like that. The longest part is doing a full reset (hitting the pin) & waiting for it to load/boot up. You will need to be patient because you will have issues. First of all, if you have ad block on your browser, DISABLE that first & see if you still have QOS issues. (That’s the main reason I upgraded as it wasn’t detecting or allowing me to add devices). Delete all cookies/history, close browser & restart the router. Hit the reset pin on your router if necessary, this is the quickest & easiest option as opposed to upgrading firmware (it will delete all settings you have so ensure you have a back up or saved settings if you want to change it back) if that doesn’t work then here’s what I did. Just remember there’s no going back & you can’t stay on this firmware as it has issues. You will need to follow through & this is the longest part. install the intermediary firmware. router will reboot. Log back into the router (192.168.1.1), try to install RC10. It wont allow you to as it will have issues with recognising RC10. Hit the reset pin on your router, (ensuring the power light flashes) & the router will do a full reset. (Note: that it does not return to previous firmware or uninstall intermediary firmware) when back on, you will have detecting internet issues, connection drops etc. eventually it will work & you’ll be able to get back into the router. (If you have - ‘you are no longer connected to your router’ simply refresh the page or type in the address again (192.168.1.1). I had to do this 3 times (hit the reset pin, wait for router to boot up, detect internet & go through the whole password set up process) then it eventually detected RC10, installed that firmware. Then installed RC14 after. Edit - I had issues 10mins into gaming which was causing jitter/stutter. I have now reverted back to the latest firmware. The issue was the same as a post above with the ‘DumaOS] process '//usr/bin/dpiclass' died restart:true’