My TV Box connects to my router via WiFi and will run fine for a while (say for an hour or so, but it varies). Then at some point it will loose connection to router and the device's WiFi turns off. No amount of turning the WiFi on brings the WiFi back to life. Inspecting the advanced settings menu of the WiFi, reveals that the WiFi has a valid MAC ID, but if you reboot the device the MAC ID is changed to 02:00:00:00:00:00. Unplug the power from the TV box for a while and then start it up once more, the WiFi will work again, but only for some time, before failing again.
I always used the Ethernet port of the device, up until recently, where I wanted to use the WiFi, so I have no idea if this is a software issue, caused by the latest update, or if the hardware has always been faulty, but I never knew it.
I've read on forums for other devices, that had the same WiFi MAC ID 02:00:00:00:00:00, that a specific file (WCNSS_qcom_wlan_factory_nv.bin) should be placed in the root/persist folder. Using a root browser reveals that my device has no persist folder in the root. If make the persist folder manually and place this file there, then sometimes the MAC ID is restored, and the WiFi may or may not work for a little while again, before failing once more. Also after rebooting the device, the persist folder is gone again
I've also read that the wifi and bluetooth of this device run from the same chip - my device's bluetooth works without any problems.
I opened the device and had a look with the naked eye - I couldn't see any obvious problem, but who knows, there could be a loose solder joint on the WiFi chip.
I have also restored Update_MXIII GII rv109.zip stock ROM to the device via SD card method, in the hope that this might fix whatever firmware issues there might be, but still no difference.
Can anyone confirm that this device should have a persist folder in the root, with certain files pertaining to the WiFi?
If so I find it strange that my device's WiFi works at all.
Any other views or advice? Do you reckon it might be faulty hardware, or firmware?
Comment