Been using the Flint 2 for a week or so and I'm impressed with it. Signal seems better than my previous AX86S.
I've run into a few issues though, which are slightly annoying. (Firmware Version 4.7.0)
I have two tablet devices that have been connected to the 2.4Ghz and are pretty much full in terms of signal. These will function fine, achieving 45-70mbps download and roughly the same up. Then, for no reason, they'll struggle and it'll go to roughly 1-5mbps.
Whilst this is happening, i connect my phone to the same 2.4ghz SSID and run a speed test. The phone seems fine and roughly get around the 150-175mbps.
The phone: Samsung Galaxy S23 (Wi-Fi 802.11 a/b/g/n/ac/6e, tri-band)
The second issue is if i am to leave the house and return. The Galaxy S23 carries on fine, speeds and throughput are good. But another device we have (Nokia G60 5G - Wi-Fi 802.11 a/b/g/n/ac/6, dual-band) Connects but the speeds are schockingly bad - 15mbps.
Disconnecting the device from WiFi and reconnecting solves this issue, but surely, we shouldn't have to be doing this?
I'm pretty much running out of ideas and close to returning the Flint 2 and going back to the ASUS setup.
Has anyone had these issues, or know what causes them?
Firmware v4.6.4 introduced a new Mediatek WiFi driver and some bugs with it, affecting mainly old AC devices.
In V4.7.0 the problems are not fixed yet.
To check if that is your case you have downgrade to v4.6.2 an check if WiFi it's OK.
There is a development test firmware provided by a moderator that runs fine too.
Looks like Mediatek is aware of the problem and many of Flint 2 owners, me included, are waiting for a fix in the next firmware. Meanwhile we are using v4.6.2 or de development version.
I did test V4.6.2 yesterday for an hour so and I noticed that the signal was worse than that of 4.7.0
Throughput speed was also worse too. So I reverted back to 4.7.0 - As soon as i went back to that signal went back to normal.
Does it need time to 'settle' or should it just be fine from the off?
Does it need to be a fresh install without settings being kept, or can we keep settings?
I've also dropped support an email to see what they come back with too. I did see a test firmware on a WeTransfer link that supposedly fixed the issues, but that link has since expired.
Does 4.6.2 and the test firmware also fix the issue of a device having lower speeds once it's left the network and then connected again (For example, leaving the house with wifi left on, and then it auto connecting once you're back in range)
I have not tested the 4.7.4 BETA yet because there is no reference in the release note about any bug-fix related to WiFi or any change in the Mediatek SDK used for the build (the WiFi driver is part of the SDK).
I have decided to wait for the final release and see what happens.
Meanwhile the development version (openwrt-mt6000-20241221154531) does the job!
I am curious about how (openwrt-mt6000-20241221154531) fixes the problem.
Could it be that it is a 4.7.0 version compiled with the previous SDK? I am just guessing ...
I only tested it because Support told me that the 4.7.4 BETA had fixed the issues
The current plan is we will officially release the v4.7.4 within the next 15 days.
This beta firmware primarily addresses the issue of reduced speed on the 5G Wi-Fi.
The main reason I suggest you test the Beta firmware is to verify whether the 5G Wi-Fi speed issue has been resolved.
I've emailed them back and told them that the issue I have isn't solved on 4.7.4 (Phone speed being lower on 5GHZ when leaving the house/network and returning)
Bruce, in one of the other threads (linked in this one near the top), has said a new BETA build will appear soon with the fixes included. I would guess that one would be the one that fixes the issues. Hopefully.
If the problem is in the WiFi Driver included in the Mediatek SDK, the GL·iNet developers can do nothing to fix the problem. They have to wait for the Mediatek people to fix the last version of the SDK and then release a new version.
If the people of Mediatek takes too much time to release a fixed SDK I would ask GL·iNet for a firmware version compiled with the previous, bug free, SDK.
As the MTK driver is provided for sdk packages, it is not sure what conclusion MTK will give. They are checking. The codes has been updated, please wait for the beta version firmware to be released.
You are right @Jbennett360, the current 4.7.4 beta version does not fix the slow down issue! I'm using for about 2 months the developer version without problems and no issues.
MT6000 v4.7.4 firmware does not have a code to fix this issue, and the updated beta firmware will be released in these weeks, which will be integrated updates to improve this issue.
No need to try that temporary test firmware, please wait for the newer version to be released.