Database Users

FIX for Wifi-Roaming-bug

This thread is about the 3 types of known wifi-roaming bugs, how to differentiate these and fix at least one of them with a little hack.
Documentation of the bug avioded by this workaround on Google: Click Here
BIG NEWS!! As mentioned by a spanish user above there are newer firmwares, that are correcting the wifi-roaming bug, that was fixed by this fix.
Confirmed by an german OTA-Update. So try upgrading your firmware to fix the bug.
But : Keep in mind that an OTA-Update, official from Samsung wont install on a modified system. This includes also our modified wpa-supplicant. So if you want to use a newer firmware you have to restore the old wpa-supplicant: View attachment wpa_supplicant.zip(From The newest Firmware in Germany[OTA-Eplus, JZO54K.I9300XXELL4)
General facts to know about buggy Wifi-Roaming on Android Devices:​
Bugs types that are existing
1.The phone never tries to roam by, unless it completely loses signal. Then it connects to the strongest AP. This is the typical Galaxy S2 bug.
2.The phone never tries to roam, and on top of that tries to reconnect to the specific AP that it knows, even if it is right next to a better one while connecting. This has been observed on some Nexus devices, but is apparently fixed on the Galaxy Nexus running CM10.
3.The phone tries to roam as it can see a better AP, but drops the connection and reconnects to the stronger AP shortly after. That's the typical Galaxy S3 and Galaxy Nexus bug, which is fixed by the hack described in this thread.
Only Bug 3 in this list is fixed by this hack. It will not help for the other two bugs!
To determine which bug you are observing, try this:​
- Pick two access points that are within range of each other, we will call them AP1 and AP2.
- Locate the phone close to AP1, turn on wifi, and connect to the network. You should get full signal strength.
- Start listening to a web radio stream using e.g. TuneIn Radio (available on Play Store), configure the buffer size to the minimum possible.
- Slowly walk towards AP2, watching the signal strength indicator.
- If you reach AP2 and the phone still shows a low signal strength (at most one bar) after 10-20 seconds:
You are observing a different bug which is not avoided by this workaround.
- Turn off wifi and turn it back on again.
- If the phone now connects to AP2 and shows a high signal strength, you are observing the Galaxy S2 bug --> Bug 1 in the list
- If the phone still connects to AP1 and shows a low signal strength, you are observing the Nexus bug --> Bug 2 in the list
- If the connection drops before getting close enough to AP2, the access points are too far away from each other. -->Retry with a different set of access points.
- If the signal strength seems to increase while getting closer to AP2, but then the wifi icon disappears briefly and comes back after a few seconds, and the web radio stream drops, you are observing the Galaxy S3 bug, and this workaround will help you. --> Bug 3 in the list
- If the signal strength increases while getting closer to AP2, the wifi icon doesn't disappear, and the web radio stream doesn't drop, everything is working normally --> no bug:
-You might have a device that just doesn't have a wifi bug. Apparently such devices indeed exist.
-You might have a Galaxy S3 or Galaxy Nexus, but you were lucky. Try walking back to AP1 and check if it drops the connection this time.
-You might have already applied the workaround above, or a different fix for the same bug. (However there doesn't seem to be one yet.)
______________________________________________________________________________________________________________________
Now as you know which bug your device has you maybe have noticed that your device has bug type 3, here is the hack to fix it:​
IMPORTANT: IM NOT RESPONSIBLE FOR NOT WORKING DEVICES AFTER THIS PROCEDURE. INSTALL AT YOUR OWN RISK!! THIS MOD IS EXPERIMENTAL!!
THIS MOD ONLY IS CONFIRMED WORKING FOR THE SAMSUNG GALAXY i9300 AND THE SAMSUNG GALAXY NEXUS i9250
For the installation procedure i give here root rights are needed. It also is recommended to make a CWM-Backup before. If you are unsure about root rights or dont know how to use a Custom Recovery feel free to ask before you do anything.​
Installation Instructions for the Standalone-file(no Custom-Recovery needed):
1. Download View attachment Standalone-file.zip and unzip
2. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
3. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
4. Delete the original "wpa_supplicant"-file from the folder
5. Paste the modified "wpa_supplicant"-file downloaded from here in \system\bin. Make sure the file still is named "wpa_supplicant"
6. Reboot your device
Installation Instructions for CWM Flashable-file(CWM-Recovery needed):
1. Download View attachment 1549825
2. Copy the downloaded file to your sdcard.
3. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
4. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
5. Reboot to recovery and flash the downloaded file.
6. Reboot your device.
Your device should now roam correctly from one AP to another.
Please leave your feedback here in the thread and hit the thanks-button if it fixed your problem. ENJOY
FOR ADDITIONAL INFO: Click Here
______________________________________________________________________________________________________________________
Special Thanks to:
- TheSeven, who created this hack
- querty12, who created the flashable CWM-file
- Gabeloooooo, who was the first to give me feedback about this​

I hope this leads to a fix. GS3 is garbage when there is more than 1 AP, makes VOIP useless.

Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon

felixchris said:
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
Click to expand...
Click to collapse
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?

Gabeloooooo said:
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Click to expand...
Click to collapse
Actually this fix was tested on Stock Rom and Cyanogenmod It works on official Stock Roms as well Just have to be rooted

Tried it, breaks wifi. Can't enable wifi anymore. (i9300 stock 4.1.1)
And oddly enough, restoring the old file back to system\bin doesnt fix it. Will do a couple of tests than will restore from nandroid.
Ok, the reason it didn't work is permissions. Copying using ES explorer did not give the execute permission. Now both files allow me to enable wifi. Will report back on AP roaming after using for a while.

Thanks for your feedback Gabeloooooo
Can you please, after finishing your tests, tell me which permissions you did to set ? as i can mentione it in the instructions
i only tested with root browser...

Used this: rwx r-x r-x

thx will add it to the instructions

Things seem MUCH better with this fix. It is no longer constantly disconnecting. MAJOR IMPROVEMENT!!
I haven't tested groove ip yet, too many bad experiences in the past, but will try it this week to see how it fares.

So maybe if you like the world you could drag it out to the SGS3 - World as i am normally focused on the SGSL- Forums But thanks gor the feedback
Sent from my GT-I9003 using xda app-developers app

Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.

Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Click to expand...
Click to collapse
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back

Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?

Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Click to expand...
Click to collapse
It was tested on this Version and till now they never changed it

I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/showpost.php?p=35143039&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2? :fingers-crossed:

felixchris said:
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Click to expand...
Click to collapse
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!

Jard16 said:
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Click to expand...
Click to collapse
did this fix work on your Nexus 4?

drewski_1 said:
did this fix work on your Nexus 4?
Click to expand...
Click to collapse
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.

SGS2 and Nexus4
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/show...9&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2?
Click to expand...
Click to collapse
The SGS2 also had problems with WifiRoaming, but they were different as far as i know. This fix shouldnt work for the Galaxy S2.
Quote:
Originally Posted by drewski_1 View Post
did this fix work on your Nexus 4?
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
Click to expand...
Click to collapse
I dont know of what kind the bug of the Nexus 4 is. So i dont know if it will fix anything. As posted above you can just install it and see if it changes anything Be sure to follow the instructions and BACKUP!!

[Q] Package File is Invalid - No mentioned fixes working for me

I got my Nexus 4 today, and I've been pretty excited since.. So far, it's worked flawlessly everywhere except for when I need to download something from the play store.
Almost every download results in "Package File is Invalid"
I googled for hours, literally. I wiped data/cache of Google Play Store, Services Framework, wiped Cache from the stock recovery, and even factory resetted the phone to no avail.
I'm guessing it's a problem with my home's router setting. Everything works fine on my nexus except for the play store. Haven't gotten a chance to mess with other wifis yet, but can anyone tell me a way of fixing it?
If it doesn't work by tomorrow, I might run a custom ROM and try, though I really wanna stick with stock till 4.3/5.0 comes out :\
Any help?

Login to the Playstore from a PC and make sure your N4 is listed on your account. Also, try and install an app on your phone from there.

What happens if you try to install an app with Wi-Fi off (Mobile Data)? This could rule out an issue with your router or ISP.

SpookyTunes said:
What happens if you try to install an app with Wi-Fi off (Mobile Data)? This could rule out an issue with your router or ISP.
Click to expand...
Click to collapse
It works fine on 3G for me. It's not a ROM issue since I tried it on stock, PA, and now CM10.1.
However, very small apps download without issues. I think the cap is around 5 mb above which the error shows up.
I'm 100% sure it's my router's settings that seem to be working against the nexus. Any idea what I could do?
I absolutely LOVE the fluidity of this phone (coming from a single core phone running a buggy JB rom) but this is killing me!!
The worst thing is, all the workarounds that I've read about since yesterday work for few, but not all people. And there are lots of workarounds. I've tried all that I've read but nothing's working :\
fernandezhjr said:
Login to the Playstore from a PC and make sure your N4 is listed on your account. Also, try and install an app on your phone from there.
Click to expand...
Click to collapse
It is, just checked again, it's listed just fine.. I tried installing whatsapp through the play store on my pc but after it downloads the 10mb file on the phone, it gives this error again.

sixaxis94 said:
It works fine on 3G for me. It's not a ROM issue since I tried it on stock, PA, and now CM10.1.
However, very small apps download without issues. I think the cap is around 5 mb above which the error shows up.
I'm 100% sure it's my router's settings that seem to be working against the nexus. Any idea what I could do?
Click to expand...
Click to collapse
What router (Make / Model) is it?
Check for a router firmware update. If there are no updates or support, check if it is supported by DD-WRT.
Try doing a factory reset on the router, then set the security settings to (WPA2 only / AES only) and use the Android app WiFi Analyzer to find the best channel.

sixaxis94 said:
I got my Nexus 4 today, and I've been pretty excited since.. So far, it's worked flawlessly everywhere except for when I need to download something from the play store.
Almost every download results in "Package File is Invalid"
I googled for hours, literally. I wiped data/cache of Google Play Store, Services Framework, wiped Cache from the stock recovery, and even factory resetted the phone to no avail.
I'm guessing it's a problem with my home's router setting. Everything works fine on my nexus except for the play store. Haven't gotten a chance to mess with other wifis yet, but can anyone tell me a way of fixing it?
If it doesn't work by tomorrow, I might run a custom ROM and try, though I really wanna stick with stock till 4.3/5.0 comes out :\
Any help?
Click to expand...
Click to collapse
This is also whats happening to my phone..i have no problem downloading apps that are below 5mb but anything more is invalid..i think its the wifi here but i cant check through 3g cause there's no signal
Sent from my Nexus 4 using xda app-developers app

SpookyTunes said:
What router (Make / Model) is it?
Check for a router firmware update. If there are no updates or support, check if it is supported by DD-WRT.
Try doing a factory reset on the router, then set the security settings to (WPA2 only / AES only) and use the Android app WiFi Analyzer to find the best channel.
Click to expand...
Click to collapse
It's a DLink router.. No updates available
I reset it yesterday and put WPA2 but it hasn't solved the problem still :\
Wifi analyzer told me channel 6 onwards were good, so I tried 6 and 7 but didn't help either
I've had to download apk's for all the free apps to make it work as of now
I'll check with my mom and dad's phone to see if this problem exists for them too, but they're running gingerbread so idk if it'll mean much even if it works

sixaxis94 said:
It's a DLink router.. No updates available
I reset it yesterday and put WPA2 but it hasn't solved the problem still :\
Wifi analyzer told me channel 6 onwards were good, so I tried 6 and 7 but didn't help either
I've had to download apk's for all the free apps to make it work as of now
I'll check with my mom and dad's phone to see if this problem exists for them too, but they're running gingerbread so idk if it'll mean much even if it works
Click to expand...
Click to collapse
First I would return to stock ROM. A custom ROM could have it's own WiFi issues.
As for the router, the only other suggestions I can make are;
test it in unsecured mode (open Wi-Fi access)
force 802.11G (disable B and N access)
lower the MTU from 1500 to 1480
disable uPnP
disable (or enable) WMM support.
disable any content filtering (like blocking java, proxies, etc).
Changing these options one at a time and see if any one fixes your issue.

Use VPN
Has been occurring a lot lately. Well, not a fancy fix but a simple one ..... use hotspot shield to connect and then all files install normally over wifi. Don't know why it does, but it works!

I have had "package file is invalid" issues with my Nexus 4 and my home WiFi connection from day 1 of owning a Nexus 4. I have tested it on 4 different WiFi Routers with different firmwares including stock and DD-WRT.
- Linksys WRT320N Dual Band (With Stock and DD-WRT Firmware).
- Linksys WRT160N V3. (Stock and DD-WRT)
- Tenda N60. (Stock "2012-12-12 V1.0.0.16_EN" and newer variants).
- ASUS RT-N66U "Dark Knight".
Tested 2.4ghz and 5ghz, varrious combinations of WEP,WPA-PSK, WPA2-PSK, WPA2-AES. It makes no difference the ONLY router from the above 4 that works correctly when downloading over WiFi from the Play Store is the Tenda N60 using the early release stock firmware "2012-12-12 V1.0.0.16_EN" that the router is shipped with. Even with the Tenda N60 if yuo upgrade the firmware to newer releases of stock firmware it will cause the issue to return.
Now this is an issue specific to the Nexus 4, I also have a Nexus 7, Samsung Galaxy S3, HTC Desire, Huawei Ascend G300. None of these devices have this issue using any of the router or firmware revisions. i.e: I can download from Google Play over the same WiFi connection with no problems.
I have had my Nexus 4 swapped for a replacment and the issue remains. So I've come to the conclusion that it's defintiely device specific the Nexus 4 has something inherently wrong with it..whether it's WiFi Drivers, Android Kernel, WiFi Chipset I dont know.
It doesnt affect all WiFi conenctions I can use my WiFi connectiona t work and the issue doesnt occur. It's strange that the cheapest router of the 4 I ahve tested i.e: The Tenda N60 is the only one that works consitently, I have never seen the "package file is invalid" issue using this router and Tenda firmware "2012-12-12 V1.0.0.16_EN".
This basically rules out any ISP, or WiFi security settingas as I used the same SSID, Security types and Network Key on the Tenda as the other 3 routers..
Poor show by Google, they obviously dont care about fixing this issue.

So your router having an issue is a Google problem? Well done coming to that conclusion...
For what it's worth, I have no such issues with my home router (Thomson) or my work WiFi network (no idea what router we have here but it's probably a Linksys/Cisco jobby)

EddyOS said:
So your router having an issue is a Google problem? Well done coming to that conclusion...
For what it's worth, I have no such issues with my home router (Thomson) or my work WiFi network (no idea what router we have here but it's probably a Linksys/Cisco jobby)
Click to expand...
Click to collapse
Ermm...you might want to read that last post again, 4 different routers from different manufactuirers with different WiFi Chipsets (Linksys x 2, Tenda, ASUS) tested with stock and 3rd party firmwares all exhibit the same issue with the Nexus 4. Where as NO other android device or any other WiFi device on my network including a Nexus 7 with the same version android version as my Nexus 4 (4.2.2 ), connected via the same routers have any issues, even side by side downloading the same app from the Play store at the same time the others will suceed the Nexus 4 will fail the download "package file is invlalid" which sounds like a data corrption issue.
Co-incdecne thats it's only the Nexus 4 that has these issues ? I highly doubt 4 different routers are all faulty...especially since it's only the Nexus 4 that has this issue.
If you check the google code pages you'll find several other people complaining of the same issue.

gsmtechuk said:
Ermm...you might want to read that last post again, 4 different routers from different manufactuirers with different WiFi Chipsets (Linksys x 2, Tenda, ASUS) tested with stock and 3rd party firmwares all exhibit the same issue with the Nexus 4. Where as NO other android device or any other WiFi device on my network including a Nexus 7 with the same version android version as my Nexus 4 (4.2.2 ), connected via the same routers have any issues, even side by side downloading the same app from the Play store at the same time the others will suceed the Nexus 4 will fail the download "package file is invlalid" which sounds like a data corrption issue.
Co-incdecne thats it's only the Nexus 4 that has these issues ? I highly doubt 4 different routers are all faulty...especially since it's only the Nexus 4 that has this issue.
If you check the google code pages you'll find several other people complaining of the same issue.
Click to expand...
Click to collapse
All I'm saying is the 2 routers I use most have no issues and neither does the one my parents, my local pub or any of my friends. Might be a UK thing, I don't know, but I've never had a problem on WiFi at all...

EddyOS said:
All I'm saying is the 2 routers I use most have no issues and neither does the one my parents, my local pub or any of my friends. Might be a UK thing, I don't know, but I've never had a problem on WiFi at all...
Click to expand...
Click to collapse
I agree with that, maybe it's even a particular hardware batch of N4's, not sure. I can use my N4 fine on my work WiFi and other locations. Like I said it does work on my home WiFi if I use The Tenda N60 router with it's early release stock firmware, any firmware upgrades cause the problem to return though. But it cant be right that you should have to use a specific router and specific firmware which you cant upgrade without breaking the N4.
I've got another support case open with Google Play which they've apparently passed to their techs, lets see what they come back with... I have heard of someone with this issue using a custom ROM with a different Kernel to the Google stock build which includes newer Qualcomm Prima WiFi drivers (Paranoid Android) , they claim this fixes the issue for them.
Im relectant to flash a custom ROM and void warranty though for a basic feature that should work out of the box though.

I tried a lot of different things but nothing seems to have worked sadly.. I'm gonna update my ROM tomorrow to CM10RC4 and see if that helps, though I doubt it's the ROM's fault. Btw, I had the same issue with the stock ROM too

I've been having this problem whenever my portable wifi device connects to a slow mobile network. All my friends connect to my hotspot, but only my Nexus 4 gets the "Package file is invalid." error. For months, I've had to contend with switching to mobile data just to finish my downloads.
My only conclusion is that the Nexus 4 has a problem with slow connections over wifi by corrupting the data transmitted. It's fine when using mobile data.

Check this out:
http://forum.xda-developers.com/showthread.php?t=2300873
It requires the phone to be rooted. I'm already testing it out now.

I cant verify 100% yet but my Nexus 4 took the Android 4.3 OTA update yesterday. I have since tried several WiFi downloads over WiFI from the Google Play store and not a single one has failed !
So my intitial thoughts are that the Android 4.3 update has recolved this issue..and it was indeed a bug/fault in the previous versions maybe it's the new kernel, Qualcomm Prima WiFi drivers, New Google Play app... But whatever it is. It seems to have fixed the issue. Well done Google about time too !
The only down point is the denial of any issue their end from Google Play staff and blatant lies they tell customers about not knowing about such bugs.

gsmtechuk said:
I cant verify 100% yet but my Nexus 4 took the Android 4.3 OTA update yesterday. I have since tried several WiFi downloads over WiFI from the Google Play store and not a single one has failed !
So my intitial thoughts are that the Android 4.3 update has recolved this issue..and it was indeed a bug/fault in the previous versions maybe it's the new kernel, Qualcomm Prima WiFi drivers, New Google Play app... But whatever it is. It seems to have fixed the issue. Well done Google about time too !
The only down point is the denial of any issue their end from Google Play staff and blatant lies they tell customers about not knowing about such bugs.
Click to expand...
Click to collapse
Ironically, the 4.3 update on my Nexus 4 yesterday actually seemed to trigger the Package File is Invalid error, as it wasn't a problem before. MX Player and Jetpack Joyride are triggering this for me atm. Anyone else still have this on Android 4.3?

Several devices.....
Lutrinae said:
Ironically, the 4.3 update on my Nexus 4 yesterday actually seemed to trigger the Package File is Invalid error, as it wasn't a problem before. MX Player and Jetpack Joyride are triggering this for me atm. Anyone else still have this on Android 4.3?
Click to expand...
Click to collapse
Having the same issues on all of my devices, but only while trying to download on my home wi-fi. Like the OP said, anything over 5mb won't download. Droid Razr M, Droid Razr HD, Note 10.1, Tab 2 10.1, and Nexus 7 (running 4.3), I cannot figure out what changed on my Belkin router (AC900) to cause this to happen suddenly. It was just noticed last night, and I have spent hours today trying to find a fix, and creating more problems to fix. If anyone has any step by step instructions of how to fix this, please explain to me like you would a 6 year old. BTW, rooting is not an option of all of these devices, so please make it a root free option. And I have cleared all caches/datas and done all the force stops recommended, as well as removed the google accounts and readded them.

[FIX][Cm12/12.1] Wifi Connectivity Issues/Drops

Usually i switch on WiFi and disable mobile data manually while at home. It turns out that i don't receive any Push Notifications like WhatsApp, Threema, Facebook and GMail/Inbox (those who are using gcm) when the device is connected to WiFi solely and the screen is locked. If i unlock the device after a certain amount of time, a bunch of notifications are popping up. This is reproducable and won't occur on mobile data. Just do the following, while i.e. at home:
Connect to WiFi
Deactivate your Mobile Data
Lock your screen and let your Device rest for a couple of seconds
Tell someone to send you a Mail to your Gmail Account (or on any other GCM-Push related way)
You probably may notice that your device won't wake up to notify you about this incoming message until you pick it up and unlock it. I have tested this since weeks with multiple official nightlies of CM12, custom builds and even unofficial CM12.1 builds, they all show the same behaviour. Even with official CM11s this issue persists, but can be worked around by unchecking "WiFi Optimizations" in advanced WiFi-Settings. Unfortunately Lollipop doesn't have this WiFi Optimization trigger anymore. Ofc "Keep WiFi on during sleep" is set to "always". After all tests i came to the conclusion that the device simply gets no wakelock trigger from notifications if connected to WiFi solely. I've fixed this for me by fiddeling with the configuration files (root needed).
Open /system/etc/wifi/WCNSS_qcom_cfg.ini and change
Code:
hostNSOffload=0
to
Code:
hostNSOffload=1
After this change and a reboot, your device should be able to wake up from incoming notifications instantly while on WiFi. Some custom ROM, like SlimSaber have set this out of the box, while official cm nightlies and other custom ROM, like exodus, haven't.

Have you tested IPv6 over WiFi with 12.1? As that is also broken on 12.

JaY_III said:
Have you tested IPv6 over WiFi with 12.1? As that is also broken on 12.
Click to expand...
Click to collapse
Usually i've disabled ivp6, because of the known problems with it. I've tested it with ipv6 enabled and it worked.
Meanwhile i was able to test a lil bit more on other networks. It seems like this all is router dependant. While having the chance to exessively using another WiFi network yesterday, i was able to check that there are no such problems as described before. After went home, problems reappeared. I have to conclude that there must be some culprit with my router at least (Telekom Speedport W724V).

I noticed such notification flood several times.
I can't say under which circumstances because I didn't care about it yet but your post made me remember this.
I gonna investigate that asap.
As far as I can say this happened only at home yet. My router is an AVM FritzBox 7390.
On my OPO I have usually always one of the newest official CM12 nightlies installed.

I've tested stock settings while connected to a completely different router a few days ago and wasn't able to reproduce the issue. It really turns out that it has something to do with certain routers, in my case a Speedport W724V Type A (by Huawei). It seems like this issues has something to do with ARP Offloading and filtering of Broadcast/Multicast. As far as i understand, Androids MAC Adress isn't hard coded and the router loses the connection to the device if it goes into sleep state. Therefore the router has to broadcast via arp to look for the device, but the device simply doesn't respond to the arp request, coz the wifi driver is configured to ignore that broadcasts and continue sleeping. This issue is, as i read, present since KitKat where it could at least be worked around by disabling the WiFi Optimizations, which seems to be only a checkbox for above mentioned manual method Lollipop.
Currently i've no idea how to fix this in a better way, since my described method works flawlessly, but it's definately a lil battery drainer. Another way to work around this is by setting "Keep Wi-Fi on during sleep" to "never" and let the device handover the data connection to mobile data while sleeping. This, at least, ensures the battery savings which were intended by the developers.
Steve Kondik merged an interesting commit today, which i am not aware of if this will change anything related to this issue. As this commit was merged into cm12.1 branch i doubt that we will see anything related in cm12 based roms, nor the upcoming cm12s. Maybe some nifty dev like @ak or @Lord Boeffla can take a look into this and implement it into their kernel.

I put the interesting commit into my cm12.1 kernel, which comes out tomorrow.
If all goes well I can look to back port it to cm12 and maybe even cm11(s).
Let's see. First we need opinions on the test kernel tomorrow.
Andi

Genericxx said:
I've tested stock settings while connected to a completely different router a few days ago and wasn't able to reproduce the issue. It really turns out that it has something to do with certain routers, in my case a Speedport W724V Type A (by Huawei). It seems like this issues has something to do with ARP Offloading and filtering of Broadcast/Multicast. As far as i understand, Androids MAC Adress isn't hard coded and the router loses the connection to the device if it goes into sleep state. Therefore the router has to broadcast via arp to look for the device, but the device simply doesn't respond to the arp request, coz the wifi driver is configured to ignore that broadcasts and continue sleeping. This issue is, as i read, present since KitKat where it could at least be worked around by disabling the WiFi Optimizations, which seems to be only a checkbox for above mentioned manual method Lollipop.
Currently i've no idea how to fix this in a better way, since my described method works flawlessly, but it's definately a lil battery drainer. Another way to work around this is by setting "Keep Wi-Fi on during sleep" to "never" and let the device handover the data connection to mobile data while sleeping. This, at least, ensures the battery savings which were intended by the developers.
Steve Kondik merged an interesting commit today, which i am not aware of if this will change anything related to this issue. As this commit was merged into cm12.1 branch i doubt that we will see anything related in cm12 based roms, nor the upcoming cm12s. Maybe some nifty dev like @ak or @Lord Boeffla can take a look into this and implement it into their kernel.
Click to expand...
Click to collapse
It fixed my wifi bug so far on euphoria 5.1

Okay guys, i've tried AK's latest experimental kernel (v203). Beside of some small problems which are still under developement, WiFi seems to be fixed completely with the implementation of the new prima drivers for me. This could mean, that they will be automatically fixed with the release of the official cm12.1 nightlies. As for now i will thank everyone, especially @ak and @Lord Boeffla for participating and help to hunt down and solve this annoying issue. You're great guys :good:

Genericxx said:
Okay guys, i've tried AK's latest experimental kernel (v203). Beside of some small problems which are still under developement, WiFi seems to be fixed completely with the implementation of the new prima drivers for me. This could mean, that they will be automatically fixed with the release of the official cm12.1 nightlies. As for now i will thank everyone, especially @ak and @Lord Boeffla for participating and help to hunt down and solve this annoying issue. You're great guys :good:
Click to expand...
Click to collapse
Thanks. With the latest beta kernel for cm12.1 which I released this morning, these drivers are also included.
If they turn out to work better - my other kernel variants (cm11s, cm11, cm12) are also already ready with these new drivers backported. Just have not released them as I want to give it some more testing.
Andi

Anyone else notice the same issue on Oxygen Os? I'm not sure if it's just the router I connect to at work, since this doesn't happen at home. Can't tell yet, will give this a shot.

xxBrun0xx said:
Anyone else notice the same issue on Oxygen Os? I'm not sure if it's just the router I connect to at work, since this doesn't happen at home. Can't tell yet, will give this a shot.
Click to expand...
Click to collapse
Would be an interesting test.
We cannot look into the driver used for Oxygen OS as the kernel code is not yet released as far as I know (if it is, I would be happily be corrected )
Andi

I'll bet that oxygen suffers of the same problems as every cm12 build does (even if it's more aosp) and CyanogenOS 12 (CM12s) will also.

Genericxx said:
I'll bet that oxygen suffers of the same problems as every cm12 build does (even if it's more aosp) and CyanogenOS 12 (CM12s) will also.
Click to expand...
Click to collapse
Let's see.
I backported the new drivers to CM12, CM11s and CM11 already.
Just need to decide whether I ship that or not
Andi

Lord Boeffla said:
Let's see.
I backported the new drivers to CM12, CM11s and CM11 already.
Just need to decide whether I ship that or not
Andi
Click to expand...
Click to collapse
is it already out ?

reyscott1968 said:
is it already out ?
Click to expand...
Click to collapse
Indeed it is.
Andi

Just to report back, this did seem to fix my wifi issues, although I've since switched to Exodus, so I didn't have a ton of time to play with it.

Thanks for taking the time to investigate this issue. I should have done the same I will ago when it started bothering me.
I will try one of the kernels and see if it fixes it. If not I'll try your method once I am back home.
Thanks!

Jur1nator said:
Thanks for taking the time to investigate this issue. I should have done the same I will ago when it started bothering me.
I will try one of the kernels and see if it fixes it. If not I'll try your method once I am back home.
Thanks!
Click to expand...
Click to collapse
You're welcome. I have to admit that the problem reappeared. So the new Wi-Fi drivers have no permanent solution for me. As told in the other thread I found my temporary solution by simply let Wi-Fi auto turn off when device for to sleep. My data plan allows me this easily, but if you're on a 200mb data plan this could be ****ty for you. Let's see if future commits of cm will change anything.

I fortunately have a 3gb lte contract, so this shouldn't be the issue. I just don't want to accept that there might not be a solution without tradeoffs.
I'll let you know if I find anything

Jur1nator said:
I fortunately have a 3gb lte contract, so this shouldn't be the issue. I just don't want to accept that there might not be a solution without tradeoffs.
I'll let you know if I find anything
Click to expand...
Click to collapse
Would be nice. I'm hunting this issue down since January, so far, as said, without any real solution other than using another router. it works anywhere except at home, so i know exactly how annoying this is. It's not that big problem to use mobile data when screen is off, but is pisses me off, if i just forget this sometimes and miss urgend messages from WhatsApp or Threema, coz they're arriving hours later. As desribed above, there is a way to prevent the OnePlus to not filter the WiFi Broadcasts. You just have to edit this one line in the configuration manually, but it comes at the cost of battery.

nexus player cant recognize 5ghz channel

my 1 day old nexus player cant recognize my 5 ghz channel ,no problem with the 2.4 ghz.

Gilico79 said:
my 1 day old nexus player cant recognize my 5 ghz channel ,no problem with the 2.4 ghz.
Click to expand...
Click to collapse
I couldn't connect to my 5ghz router (tplink archer c7 v2) even though other devices could. However none of my other devices are ac, the others are N 5ghz. On a hunch, I went to my router's config and disable ac on the 5ghz then the nexus player connected immediately to the 5ghz band. I don't know if it's an issue with the archer c7 or with nexus player but at least I have better speeds now.
But if there's something else to change I'd like to know because I'd prefer to use ac.

sark666 said:
I couldn't connect to my 5ghz router (tplink archer c7 v2) even though other devices could. However none of my other devices are ac, the others are N 5ghz. On a hunch, I went to my router's config and disable ac on the 5ghz then the nexus player connected immediately to the 5ghz band. I don't know if it's an issue with the archer c7 or with nexus player but at least I have better speeds now.
But if there's something else to change I'd like to know because I'd prefer to use ac.
Click to expand...
Click to collapse
I have the same exact router and I am connected to 5gz with my Nexus player with AC enabled. I am not able to confirm if Nexus is actually connected as AC just yet. I will confirm and post back, but I just wanted to let you know it is working for me with AC on. I am using the stock firmware, no DD-WRT for what it's worth. I also did not see any stock firmware updates for this version of the router.

Interesting, please let me know. I had openwrt on it for a bit but had issues and went back to stock. But I am on tplinks latest firmware. Released in April of this year. Maybe let me know what firmware version you currently have. I may revert firmwares.

sark666 said:
Interesting, please let me know. I had openwrt on it for a bit but had issues and went back to stock. But I am on tplinks latest firmware. Released in April of this year. Maybe let me know what firmware version you currently have. I may revert firmwares.
Click to expand...
Click to collapse
I have not been able to find a way to determine if the Nexus is connecting with AC or not, but AC is on and it is connected to my 5gz signal. If you know of an app or some other method to find this out, let me know. So far the few apps I installed didn't tell me much. I am rooted with Stock at the moment, so most apps I need to test in the Play store require to find the apk to sideload. I hope the Play store blocking what I can and can not install goes away when I install a custom rom like Lollirock or AOSP 6.0 onto the Nexus. It says it isn't compatible, but it loads up just fine when I sideload it.
Then the last time I checked tplinks site for firmware, there was none listed. Then after I saw you mention the April update, I checked their site again and now see they just released another one on Oct 14, 2015. I have not updated it and my release listed in the router is Firmware Version: 3.14.1 Build 141030 Rel.56452n Hardware Version: Archer C7 v2/v3 00000000 The bottom of the router is listed as v2 though. It may be worth testing unless you know of a way to downgrade to my version easily.

r4wb0Ss said:
I have not been able to find a way to determine if the Nexus is connecting with AC or not, but AC is on and it is connected to my 5gz signal. If you know of an app or some other method to find this out, let me know. So far the few apps I installed didn't tell me much. I am rooted with Stock at the moment, so most apps I need to test in the Play store require to find the apk to sideload. I hope the Play store blocking what I can and can not install goes away when I install a custom rom like Lollirock or AOSP 6.0 onto the Nexus. It says it isn't compatible, but it loads up just fine when I sideload it.
Then the last time I checked tplinks site for firmware, there was none listed. Then after I saw you mention the April update, I checked their site again and now see they just released another one on Oct 14, 2015. I have not updated it and my release listed in the router is Firmware Version: 3.14.1 Build 141030 Rel.56452n Hardware Version: Archer C7 v2/v3 00000000 The bottom of the router is listed as v2 though. It may be worth testing unless you know of a way to downgrade to my version easily.
Click to expand...
Click to collapse
Hmm, where are you seeing a new firmware dated Oct 14, 2015?
When I look here:
http://www.tp-link.com/en/download/Archer-C7_V2.html#Firmware
The latest firmware I see is dated April 27, 2015 which I am currently running. It's listed in the tplink admin login as:
3.14.3 Build 150427 Rel.36706n
Hmm, I don't see your firmware build even in the prior ones.
There are only 3 firmware versions in total. Mine & Archer C7_V2_V3_141110 (dated Nov 10, 2014) & Archer C7_V2_150304 (dated March 4, 2015)
The only thing I can think is you have never upgraded the firmware on your tplink and they don't post the stock firmware? Although I thought there were more than 3. Maybe they remove older ones. I'd be curious if you can connect with ac on the latest firmware but I don't think you can roll back to what you are currently running. Unless you're looking at a tplink page that I am not.
Yes when you go to a custom rom you won't have the market limitation anymore. I'm still on stock but probably going to go to a custom rom. The only negative is I don't think the remote is currently working. I may wait and see.
Regarding confirming if a device is connected as AC or N on 5ghz, I have no clue. I've seen a couple of friends routers (different models) and they don't show it either. Kind of annoying. However, I believe yours is probably connected at ac, as when I leave ac enabled the nexus continually fails connecting. Only when I disable ac does it successfully connect at 5ghz. Even though you may lose ac, you might want to consider updating as I believe they fixed a couple of serious security bugs in the older firmwares. That might even be why some are removed. I'm living with N right now, but I would like ac as I may move the nexus player to a room that's further away and ac supposedly handles distances much better than n.
Just as some tips for side loading. You probably know of apkmirror.com, which is good but doesn't have everything. There's also a chrome plugin for the market that gives you the option to download apks directly, and also install directly to another device. The second option doesn't always work though. the Nexus player may be greyed out when you try this but a lot work. So from my browser I'm just searching for apps and selecting install to the NP. For the others I download them and I was going to use ftp but I found it's easier just using airdroid which I already installed on the NP.

sark666 said:
Hmm, where are you seeing a new firmware dated Oct 14, 2015?
When I look here:
http://www.tp-link.com/en/download/Archer-C7_V2.html#Firmware
The latest firmware I see is dated April 27, 2015 which I am currently running. It's listed in the tplink admin login as:
3.14.3 Build 150427 Rel.36706n
Hmm, I don't see your firmware build even in the prior ones.
There are only 3 firmware versions in total. Mine & Archer C7_V2_V3_141110 (dated Nov 10, 2014) & Archer C7_V2_150304 (dated March 4, 2015)
The only thing I can think is you have never upgraded the firmware on your tplink and they don't post the stock firmware? Although I thought there were more than 3. Maybe they remove older ones. I'd be curious if you can connect with ac on the latest firmware but I don't think you can roll back to what you are currently running. Unless you're looking at a tplink page that I am not.
Click to expand...
Click to collapse
I was using this site: http://www.tp-link.us/download/Archer-C7_V2.html#Firmware The only difference I can see is this site is the .us version vs the .com version you linked me, which was the first time I seen this. I am located in the US, but it seems odd they would have different firmware downloads available between the 2 nearly identical sites. Then I either updated the firmware when I first installed the router, which was approximately a year ago, or I installed whatever was out then. I do not recall 100%, as everything was working I didn't bother with it. But now I am curious if it will help with security issues and/or break my AC connections.
sark666 said:
Yes when you go to a custom rom you won't have the market limitation anymore. I'm still on stock but probably going to go to a custom rom. The only negative is I don't think the remote is currently working. I may wait and see.
Click to expand...
Click to collapse
I think the remote works, but it only has so many buttons, so it will dramatically limit your functionality. I plan on using a TV Launcher to replace the default launcher, no matter what rom, stock or not, I am using. It is designed for basic functionality so the remote should be just fine for it. Then I found a badass remote app called Droidmote on XDA and it works very well with the Nexus player on the stock launcher. I am sure it will work just as well with a custom rom too. I have it installed on my phone and tablet and was able to maneuver around every app I tested that I was not able to before I installed it and was only using the stock remote.
sark666 said:
Even though you may lose ac, you might want to consider updating as I believe they fixed a couple of serious security bugs in the older firmwares. That might even be why some are removed. I'm living with N right now, but I would like ac as I may move the nexus player to a room that's further away and ac supposedly handles distances much better than n.
Click to expand...
Click to collapse
Yeah, I am not sure if I should upgrade to the latest firmware or not... but if there are a couple serious security bugs, I suppose I probably should update. Hopefully the October firmware allows AC to still work enabled. I sure hope so as I was planning on moving the Nexus to the opposite end of the house and having AC wifi is one of the main reasons why I chose the Nexus player.
sark666 said:
You probably know of apkmirror.com, which is good but doesn't have everything. There's also a chrome plugin for the market that gives you the option to download apks directly, and also install directly to another device. The second option doesn't always work though. the Nexus player may be greyed out when you try this but a lot work. So from my browser I'm just searching for apps and selecting install to the NP. For the others I download them and I was going to use ftp but I found it's easier just using airdroid which I already installed on the NP.
Click to expand...
Click to collapse
I am familiar with apkmirror.com and similar sites, but I never dug into chrome with the market plugin. That is good info to know and may test it out, but I dont mind sideloading. I send the files to Google drive and load ES explorer and installs fast. However, I do prefer having the ability to do this directly from the Play store, which will be possible when I go to a custom rom. Anyway, if you update to the October firmware, let us know if it helped or made any difference. I will check it out myself by the weekend and post back if anything changes on my side.

That is strange but I've seen tplink do that before. I wish they wouldn't do that.
And your US site doesn't seem to have historical firmware available, unless there's a link I'm not seeing. I may flash this one and see if it fixes ac as I bought this as well with the intention of it being somewhat far from the router and would rather not rely on N.
Coll, I'll check out that TV launcher. If it works with the remote then that's a plus. One thing I'm not sure of, if one changes to a custom rom how does install the TV version of an app? Some of them are easier to use. Just wondering if the TV versions of an app will show up in the market when on a basically stock rom.

This problem has to do with the channel of 5Ghz, you need to select a low number channel otherwise the nexus play simply won't pick it up.
I have set 5ghz to channel 48 and works great.

cchaves77 said:
This problem has to do with the channel of 5Ghz, you need to select a low number channel otherwise the nexus play simply won't pick it up.
I have set 5ghz to channel 48 and works great.
Click to expand...
Click to collapse
I can confirm that I am running on a low channel (36) for 5ghz as well.

I have the same router. I ended up setting 2.4ghz to channel 1, and 5ghz to channel 169. Kept having issues with streaming Hulu, it would stop and buffer a lot. Seems better after I made these adjustments. I used a WiFi analyzer app on my phone to make sure I am not using channels that other people in the building are using.

That is odd. I have a Netgear true dual band AC router. My Nexus Player pulls and runs excellent on my 5G. Both my Nexus 6 and Nexus Player pull 800mbps link speeds on my 5G. Sounds like a router related problem.

I've had the same problem! It comes from the Location setting. At the very beginning, in the setup wizard you've set the location as US probably, and not all 5Ghz Channels are (legally) available there.
Change the location to the same location as your Router. For me that was the problem.

ungureanub said:
I've had the same problem! It comes from the Location setting. At the very beginning, in the setup wizard you've set the location as US probably, and not all 5Ghz Channels are (legally) available there.
Change the location to the same location as your Router. For me that was the problem.
Click to expand...
Click to collapse
There is no where to set your location in NP.
Real life got in the way but I just tried this on every ac channel available starting from the lowest and the NP could never connect; disable ac and it connects instantly.
I'll see about flashing that firmware for the archer c7 v2 and see if that fixes it.

Gilico79 said:
my 1 day old nexus player cant recognize my 5 ghz channel ,no problem with the 2.4 ghz.
Click to expand...
Click to collapse
I had this problem with my Zyxel 802.11ac access point. Once I told my access point to stop trying to use 80Mhz channels (selection read "20/40/80MHz"; switched it to "20/40MHz") and went from forcing a specific channel to "auto" (i.e. let the access point choose the channel) the problem went away, and my Nexus Player has a nice strong, steady connection on 5GHz.

It is because Google fails to the DFS channels. I modded my Nexus 10 to get them but can't figure out how to enable them on the player. http://forum.xda-developers.com/nexus-10/general/adding-support-5ghz-wifi-channels-nexus-t2961722
Check this out to see the supported channels. (note 80mhz uses 4 channels.)
http://clients.mikealbano.com/

When I received and turned on my nexus player, it was not able to see 5GHz SSID. I immediately went and updated to the latest MarshMallow and now all 5GHz channels work without any problem. Those who had trouble with 5 GHz channels, are you all updated to the latest Android?

sark666 said:
There is no where to set your location in NP.
Real life got in the way but I just tried this on every ac channel available starting from the lowest and the NP could never connect; disable ac and it connects instantly.
I'll see about flashing that firmware for the archer c7 v2 and see if that fixes it.
Click to expand...
Click to collapse
When you choose your language in the setup wizard. As long as I had there "US English" it did not worked. After choosing UK English or German ... well its working. I knew the trick from my Nexus 5. As I received it from Google Play I could not connect to the same 5GHz Network. I've called the Support and they knew from the beginning what my problem was and "advised" me to do this trick.
But I do not know, why you have to do this!

WiFi Hotspot Creator and WiFi doesn't work at P8 Lite + Huawei Backup app???

I have a Huawei P8 Lite since 3 months and one day when I wanted to share my 4G mobile data internet via Hotspot(which I do very frequently) it was not detectable in any other device I have. Also when I turn on WiFi it doesn't show any available connection (while in other devices it does show many).
Another question, considering to make a factory reset, the Huawei Backup system app does it backups apps and app data, like savedata and saved games???
Thank you to everyone in advance!!!

I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.

wolfensg said:
I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.
Click to expand...
Click to collapse
Thank you so very much! I would give more than 1 like if I could!
I'm disturbing you too much I think, but I will ask you for some details:
-The Marshmallow 6.0 BETA Rom it scares me just because of the word "BETA". Is it stable enough? Any big problem? Is it easy after to update to the Final Marshmallow build when it comes out?
-Did you had any problem with WiFi or just with the Hotspot?
-Did you root your phone? I didn't root just because of the possible problems when flashing a Rom or the difficulty of re-locking bootloader.
-About the Huawei Backup app, do you know if it backups the app data/savedata also? And about compatibilities when jumping from Lollipop to Marshmallow?
Thank you and sorry again for disturbing too much! You can answer only to the questions you know.

amarildo.rajta said:
Thank you so very much! I would give more than 1 like if I could!
I'm disturbing you too much I think, but I will ask you for some details:
-The Marshmallow 6.0 BETA Rom it scares me just because of the word "BETA". Is it stable enough? Any big problem? Is it easy after to update to the Final Marshmallow build when it comes out?
-Did you had any problem with WiFi or just with the Hotspot?
-Did you root your phone? I didn't root just because of the possible problems when flashing a Rom or the difficulty of re-locking bootloader.
-About the Huawei Backup app, do you know if it backups the app data/savedata also? And about compatibilities when jumping from Lollipop to Marshmallow?
Thank you and sorry again for disturbing too much! You can answer only to the questions you know.
Click to expand...
Click to collapse
I'm using european 6.0 BETA (ALE-L21C432B524) and have not rooted the phone (I simply don't see any point in rooting at the moment). Xposed framework if working properly maybe could encourage me to root the phone but since EMUI is not 100% AOSP compatible - I don't see a benefit of using Xposed framework as I cannot predict which module will be working properly.
Going back to the 6.0 beta: System is very stable. I did have some problems in the beginning (I did standard upgrade via local update file). The problems were: callendar entries disappearing at random (and then reappearing), some other glitches with UI, etc - but nothing really bothering. All problems were gone since I made factory reset - so I DO RECOMMEND making factory reset after the upgrade.
Also - to be honest - as for the wi-fi hotspot - I needed this as from time to time I'm working from home and I need to set up VPN to my company each time (my internet provider however does not allow me to set up VPN tunnel). That is why I've tested few days ago if wi-fi hotspot option is working now (as I was unable to make it work on previous firmware) and... voila - it works just fine now And I'm able to work from home without issues.
As for the Huawei Backup - I haven't use this one so I cannot tell if the backup will work, etc (I have made the manual backup of all the data files (Music, Pictures,etc) before the wipe and my mobile is connected all the time with the google account so I didn't bother about making any backups of apps/contacts.
Good things I see in this beta:
- much more battery friendly (dual-sim enabled handset with quite a lot of calls is able to be operational for the whole day on a single charge (on Lollipop it was not possible at all)
- contacts and messaging apps are separated (yeah - I did not like that idea of having one app for everything as in Lollipop based EMUI
- contacts and messaging are not a battery hog now (on LP EMUI 3.1 they consumed 30% of battery each day and it was a pain to replace them with something useful as many apps on the google market just does not support properly dual-sim)
- in general the phone is smoother and feels faster
Bad things:
- lockscreen wallpaper seems to be stretched somehow and if you are making a theme of your own (as I am) - you would need to rebuild lockscreen image (fixed in B574!)
- double-tap problem seems to still exist (the problem when typing quite fast on ANY keyboard - you still get double letters, regardles of "gloves modes on/off" or screen protectors, etc, etc - Huawei support which I contacted - also confirm the problem STILL exists... but don't know WHEN it will be adressed... (fixed in B574!)
Neutral things (may be considered bad but seems to be unrelated of this beta and occur also on older firmwares):
- some software seems to be incompatible (but this also applies to LP based EMUI for this phone) - I had problems with starting up ExaGear Strategies (crashes), Winulator (crashes when starting StarCraft (but it seems to be bug with Winulator and ANY android newer than KitKat), fHeroes2 (colorful artifacts when on the "battle" screen, does not occur on map and on title screen - requires running OLDER version of fHeroes2 (downloadable from authors website and not from Google Play) and selecting 24 bpp color and smooth stretching) (problem with fHeroes2 fixed in the latest fHeroes2 update!)

wolfensg said:
I'm using european 6.0 BETA (ALE-L21C432B524) and have not rooted the phone (I simply don't see any point in rooting at the moment). Xposed framework if working properly maybe could encourage me to root the phone but since EMUI is not 100% AOSP compatible - I don't see a benefit of using Xposed framework as I cannot predict which module will be working properly.
Going back to the 6.0 beta: System is very stable. I did have some problems in the beginning (I did standard upgrade via local update file). The problems were: callendar entries disappearing at random (and then reappearing), some other glitches with UI, etc - but nothing really bothering. All problems were gone since I made factory reset - so I DO RECOMMEND making factory reset after the upgrade.
Also - to be honest - as for the wi-fi hotspot - I needed this as from time to time I'm working from home and I need to set up VPN to my company each time (my internet provider however does not allow me to set up VPN tunnel). That is why I've tested few days ago if wi-fi hotspot option is working now (as I was unable to make it work on previous firmware) and... voila - it works just fine now And I'm able to work from home without issues.
As for the Huawei Backup - I haven't use this one so I cannot tell if the backup will work, etc (I have made the manual backup of all the data files (Music, Pictures,etc) before the wipe and my mobile is connected all the time with the google account so I didn't bother about making any backups of apps/contacts.
Good things I see in this beta:
- much more battery friendly (dual-sim enabled handset with quite a lot of calls is able to be operational for the whole day on a single charge (on Lollipop it was not possible at all)
- contacts and messaging apps are separated (yeah - I did not like that idea of having one app for everything as in Lollipop based EMUI
- contacts and messaging are not a battery hog now (on LP EMUI 3.1 they consumed 30% of battery each day and it was a pain to replace them with something useful as many apps on the google market just does not support properly dual-sim)
- in general the phone is smoother and feels faster
Bad things:
- lockscreen wallpaper seems to be stretched somehow and if you are making a theme of your own (as I am) - you would need to rebuild lockscreen image
- double-tap problem seems to still exist (the problem when typing quite fast on ANY keyboard - you still get double letters, regardles of "gloves modes on/off" or screen protectors, etc, etc - Huawei support which I contacted - also confirm the problem STILL exists... but don't know WHEN it will be adressed...
Neutral things (may be considered bad but seems to be unrelated of this beta and occur also on older firmwares):
- some software seems to be incompatible (but this also applies to LP based EMUI for this phone) - I had problems with starting up ExaGear Strategies (crashes), Winulator (crashes when starting StarCraft (but it seems to be bug with Winulator and ANY android newer than KitKat), fHeroes2 (colorful artifacts when on the "battle" screen, does not occur on map and on title screen - requires running OLDER version of fHeroes2 (downloadable from authors website and not from Google Play) and selecting 24 bpp color and smooth stretching).
Click to expand...
Click to collapse
Thank you very much once again! I really appreciate it! I would buy you a beer or a coffee.
The review of the Marshmallow Rom from you is clear and complete, and right too as you use it in work and me I'm just a student. Now I'm considering seriously to jump to the 6.0 BETA, as it looks more STABLE than BETA.
-Talking about the future and a possibly soon Final build of the Rom, do you think the update to that will be problematic or difficult?
-And you didn't had any problem with WiFi or you don't remember?

amarildo.rajta said:
Thank you very much once again! I really appreciate it! I would buy you a beer or a coffee.
The review of the Marshmallow Rom from you is clear and complete, and right too as you use it in work and me I'm just a student. Now I'm considering seriously to jump to the 6.0 BETA, as it looks more STABLE than BETA.
-Talking about the future and a possibly soon Final build of the Rom, do you think the update to that will be problematic or difficult?
-And you didn't had any problem with WiFi or you don't remember?
Click to expand...
Click to collapse
Always happy to help anyone (if only I have some free time)
Ad 1. Since I have no information about the official release it is hard to say.
However I see two options - either it would be possible to simply do the local update to the non-beta version or to do the downgrade to Lollipop (as per the official tool which is already available (you can search the XDA issues) and then do the upgrade again.
Ad 2. I'm constantly using wi-fi at home (due to the poor GSM signal) and I did not see any issues so far (I'm using 6.0 for at least month now).

Ok, small correction
I've tried today for at least an hour to create the Wi-Fi hotspot and it failed on 6.0. I've also tried on my fiances ALE-L21 with the same result - it was working for around 30 seconds :/
Previously I've also tried to work with VPN via Wi-Fi hotspot on this 6.0 but I (unfortunately for me) did not test long enough (just tried to connect and to run few company websites ;/

wolfensg said:
Ok, small correction
I've tried today for at least an hour to create the Wi-Fi hotspot and it failed on 6.0. I've also tried on my fiances ALE-L21 with the same result - it was working for around 30 seconds :/
Previously I've also tried to work with VPN via Wi-Fi hotspot on this 6.0 but I (unfortunately for me) did not test long enough (just tried to connect and to run few company websites ;/
Click to expand...
Click to collapse
Ok then! Anyway I still hope a little bit to succeed fixining that because I haven't been trying to make the Hotspot work with VPN.
Thanks for letting me know!

amarildo.rajta said:
Ok then! Anyway I still hope a little bit to succeed fixining that because I haven't been trying to make the Hotspot work with VPN.
Thanks for letting me know!
Click to expand...
Click to collapse
On the other hand - I am able to set up VPN on the phone and to use VPN environment from it (browsing, etc) but it's not the solution

Im also having this prob please tell the procedure to solve
wolfensg said:
I had the same problem (with wi-fi hotspot) on any Lollipop based firmware (tested Play branded B144, B052, B170) - when moved to Android 6.0 beta - problem stopped occuring.
Click to expand...
Click to collapse
Please tell procedure how to solve

parthis said:
Please tell procedure how to solve
Click to expand...
Click to collapse
Actually... You've quoted my "solution" ... I just upgraded to Android 6.0 (beta build) but also works fine for standard (non-beta) builds. Currently I'm using B574 and works flawlessly.

wolfensg said:
Actually... You've quoted my "solution" ... I just upgraded to Android 6.0 (beta build) but also works fine for standard (non-beta) builds. Currently I'm using B574 and works flawlessly.
Click to expand...
Click to collapse
I tried B574 but it doesnt works its failed now what i do

parthis said:
I tried B574 but it doesnt works its failed now what i do
Click to expand...
Click to collapse
What you may do is to try the following:
- check the compatibility of the device which tries to access the hotspot (you can test by attempting to access the hotspot from another device and vice versa - check this "non working" device by trying to connect to wi-fi via router, another phone's hotspot, etc)
- if the above not working and if you are sure that you are on B574 and you did not make any factory reset after the upgrade - you may try to make factory reset and try afterwards
- you can also try to take the phone to on warranty repair (maybe something is not entirely ok)
As I've mentioned - it is perfectly working for me (I have B574, unmodified stock, without any custom addons and without root), but since it is not working for you - I'd suggest to try the above in the exact order - or maybe someone will come up with another solution.