news from the mtk agent who was in your office? Any progress related to the problems already reported and being addressed?
Anyone flashed snapshot 4.6.0 yet ? anything running better, is it worth flashing or sitting it out for it to go beta / final ?
Because users need to test it and they don’t like to install something in blind.
If I’m having problem with something, I’ll install a beta/snapshot version only when the changelog says something about it.
Just a couple of developers are not enough to test all situations, settings, environment that can be found in a large sampling.
More people testing before a new release means more stable version.
2 Likes
Highly disagree.
This is only true if people are trained in how to test software, report errors correctly and generally know how to help themselves.
1 Like
We miss the part that snapshots are part of a automated process. 
So developers may even not tested it.
2 Likes
Snapshot 4.6.0 is riddled with problems mostly with faulty DNS resolution and broken internet if you don’t specify DNS for your VPN client. Port forwarding also didn’t work for me. Uninstalled and binned.
People reporting problems, even only saying “this is not working now, but it was working before” is still a good thing to release a more stable version.
Developers in an small company have a very limited environment to test their products, so they will not find problems from the real world.
6 Likes
@admon So only people which are trained IT professionals and certified software testers should be allowed to post bug reports? Then public alpha and beta tests are not needed anymore since the majority of the users are not “capable” of posting bug reports.
I believe that most of the bug reports are lacking the structure.
4 easy questions could help a lot:
Steps to reproduce the bug?
Resulting and expected behaviour?
Technical data (Log files, screenshots)?
System information (own hardware, WiFi adapter, firmware version)?
Unfortunately you cannot enforce this structure in a forum but only with bug reporting software like Jira, jam.dev, bugzilla etc.
2 Likes
I spotted something similar with the 4.6 alpha version on the Beryl AX, I won’t test 4.6 until it releases as a beta
1 Like
Not much. Now only the 2.4G blue screen is fixed.Other issue has no good news, We just get some tools to capturing the network packet yesterday .
1 Like
Same old same old, no “new” bugs 
Will check it on monday. Today is saturday in china.
We fixed the main issue below:
1, 2.4G WiFi driver causes windows blue screen
2,When you access the web UI of the device through GoodCloud, will jump to the local IP address
3,The software warehouse cannot be used
other fixed bug on bug system I can’t check today. I will push our PM to get the changelog next week
You mean MT3000 4.6.0?
No I mean the MT6000 4.6.0 snapshot
But it’s not a big deal. Just showing a warning - which is totally normal in snapshots.
I don’t know why this is happening, but for me, this doesn’t create any trouble.
Just using this as a glaring example of a bug for the claim that it has “no new bugs”. So many others to list here including DNS resolution and port forwarding issues as reported above. Buggy snapshot as hell.
just flashed
from what already got reported, the only new issue i found was one device not wanting to connect.
it seems that it didn’t want to clear the older session flag from the client, however probably something rare since all my other devices connected properly from 20 wifi devices I have.
I upgraded with the keep settings checkbox so im not sure if that affects something in the mediatek config file.
I managed to fix it to disable wifi and enable it again, in case of a log tar, I did made one so if a developer is interested please let me know and i sent a pm 
That’s what I said too 
1 Like