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!!
Related
I've had my totally stock Epic for a week now, coming from a highly customized Heroc, and I believe I've found my 1st problem. Until yesterday everything worked well. But now, for two different Wi-Fi access points in my home (one set to G/N and the other to B/G) the handset sees them, remembers them, but claims they're not in range. I can toggle Airplane mode to get a minute or so of Wi-Fi connectivity but then I lose it again and both AP's are reported to be out of range again. 4G and Blue Tooth are turned off. It's a new Epic and is on hw version 5.
Anyone else see the same problem?
NVM - WiFi now magically working w/o anything being done ... strange, but ok!
I posted this on a different thread but figure this thread is more aptly named for my issue and solution.
Ever since I rooted my phone I've had issues with wifi for use with anything such as the market, web browser, sms, you name it.
Found that there is a file that is easily corruptible and can easily be fixed thankfully with a free app from the market called Android Mate.
You'll have to have your phone rooted and then navigate to the phones base directory then go here: /data/wifi/ and delete this file: bcm_supp.conf
Android Mate seems to have issues with navigating the base folder (root directory) so for me I went to the data folder and had to manually type in /wifi and it pulled up the bcm_Supp.comf file and I deleted it and rebooted my phone and presto no more issues.
Hope this helps a few people
After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29
Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit
Work
Thanks u very much.worked on my milestone
Thanks. Actually worked.
Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".
I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App
pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please
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.
chhaggerty has compiled a T900 version from source, why this thread is no longer needed and will no longer be maintained.
This is a port of CyanogenMod 12 | P900 made by bonuzzz and Valera1978 and adapted to T900 | Galaxy Tab Pro 12.2 (SM-T900).
Download T900 - cm12 v. 3, T900 - cm12 v. 5, T900 - cm12 v. 6 and an updated Gapps 5.0.x minimal (You choose what to install from Play Store, after flashing).
Flash in TWRP 2.8.0.0 or later. Here is the latest unofficial TWRP-2.8.3.0.img
attn. updated 12/21/2014 For latest versions of the ROM, check TweakerLs' MediaFire folder
His ROM-port is additionally patched with;
- Functioning Cursor
- 5GhZ Wifi channels enabled
- Bluetooth shows as SM-T900
Be patient both at flashing as during first boot it will take a few minutes and the screen will turn Black, just hang on and your device will eventually reboot, and you can enjoy cm12 Lollipop.
It's really nice and smooth. However, it's a pity that Xposed is not yet compatible with Lollipop (ART), why I will most likely stay with a 4.4.4 ROM.
Enjoy,
Thanks! What a great surprise.
Any issues at all? Screen rotation and other things that were an issue in CM11 working in CM12?
omniomi said:
Any issues at all? Screen rotation and other things that were an issue in CM11 working in CM12?
Click to expand...
Click to collapse
This a P-900 port why there will be some incompatibility issues, notably the screen rotation. The alternative is to wait for someone to write it from cm sources and it might take some time.
A guess
I imagine it has the same screen rotation problem that was prevalent on the CM11 version for a while. Might want to check on how it was fixed.
Edit: using it now. Working very well
arcadia2uk said:
This is a port of CyanogenMod 12 | P900 made by bonuzzz and Valera1978 and adapted to T900 | Galaxy Tab Pro 12.2 (SM-T900).
Download T900 version and the updated Gapps
Flash in TWRP 2.8.0.0 or later
Be patient both at flashing as during first boot it will take a few minutes and the screen will turn Black, just hang on and your device will eventually reboot, and you can enjoy cm12 Lollipop.
It's really nice and smooth. However, it's a pity that Xposed is not yet compatible with Lollipop (ART), why I will most likely stay with a 4.4.4 ROM.
Enjoy,
Click to expand...
Click to collapse
Can somebody test this and list all of the working and non-working function of the ROM? That would be awesome.
vi6s said:
Can somebody test this and list all of the working and non-working function of the ROM? That would be awesome.
Click to expand...
Click to collapse
To my knowledge there's only an issue with automatic screen-rotation. However, as I earlier mentioned I don't use Lollipop as I am very fond of Xposed. The fact that that Xposed isn't working, is not a problem with this ROM, but the fact that Android 5.0 is using ART, while Xposed only works with Dalvik.
Running for two days now. I can confirm the following:
- WiFi - Joined multiple networks, no issues
- GPS - locked almost immediately after starting Google Maps
- Cameras - front and back
- Screen Cast (mirroring) - works with my Amazon Fire TV. Interestingly it would fail with the stock Samsung build.
- Hard to quantify, but it feels smoother than Samsung stock. Perhaps the lack of bloatware?
Issues of note:
- As stated by others, auto-rotate doesn't work. Is there a way to force rotation on demand?
- I miss the stock keyboard. I extracted the keyboard APK before flashing, but it fails to install. Lollipop keyboard seems plain in comparison.
- Since this is a port, apps detect this tablet as a P900. However, since specs are so similar to a T900 I doubt this will be an issue.
If anyone wants to test something specific, just ask.
Sent from my SM-T900 using XDA Premium HD app
Nomedias said:
Running for two days now. I can confirm the following:
Issues of note:
- As stated by others, auto-rotate doesn't work. Is there a way to force rotation on demand?
- I miss the stock keyboard. I extracted the keyboard APK before flashing, but it fails to install. Lollipop keyboard seems plain in comparison.
- Since this is a port, apps detect this tablet as a P900. However, since specs are so similar to a T900 I doubt this will be an issue.
Sent from my SM-T900 using XDA Premium HD app
Click to expand...
Click to collapse
- There are a few apps that can force rotation on demand; I like Ultimate Rotation Control, but there is also Set Orientation just to mention a couple.
- Hacker's Keyboard has a lot of the same functionality, and so has A.I type tablet keyboard and a few others.
- The detection as a P900 is just visual and has no impact, other than the stated screen rotation issue. It was just laziness on my part that I didn't change the build.prop to show T900 and v2wifixx, rather than P900 and v1awifi. However, I just uploaded a version 5, with a modded build.prop.
TweakerL said:
I imagine it has the same screen rotation problem that was prevalent on the CM11 version for a while. Might want to check on how it was fixed.
Edit: using it now. Working very well
Click to expand...
Click to collapse
Absolutely correct, it's the same issue and you can consult chhaggerty's github repos to port necessary changes.
I thought having the same name in build.prop lets you auto restore your apps from google play after you wipe and flash a new rom but I could be wrong; anyone know
I use thumb keyboard for my tablet and phone; love it.
A couple of issues.
First let me say that overall I'm impressed with this build. It works quite well for the most part.
I'll just quickly confirm the rotation problem.
Now, a couple of odd problems:
#1 I can't see one of my 5ghz Wi-Fi connections. It's weird because I can see two other 5ghz connections. The one I can't see I can see on my phone, and I've changed several settings on the router to see if that would affect it. I have also killed wpa_supplicant to see if that would get it to show, but no luck.
#2 Bluetooth audio seems to be skipping a lot. I'm not sure exactly what can be done in this aspect, however, because I'm streaming music I suspect that whatever the issue is with the wifi might be the cause for the problem.
Again, overall very solid build.
EDIT: I remember that with the CM11 version, changing the country band configuration for WIFI would solve this problem, however, I don't see that option in CM12. Will look into build.prop.
EDIT2: I changed “ro.WiFi.channels=“ to “ro.WiFi.channels=14“ in build.prop, then rebooted and the missing network popped up. I'm not sure if it was just coincidence but if anyone comes across this problem I'd suggest they try it and report back results. As for my bluetooth streaming problem, as I expected once I was in the better network the problem went away. Now everything seems perfect except for rotation, which doesn't bother me because I already use ultimate rotation control on a regular basis. I haven't tested the IR blaster, but that's hardly something I use.
TweakerL said:
#1 I can't see one of my 5ghz Wi-Fi connections. It's weird because I can see two other 5ghz connections. The one I can't see I can see on my phone, and I've changed several settings on the router to see if that would affect it. I have also killed wpa_supplicant to see if that would get it to show, but no luck.
#2 Bluetooth audio seems to be skipping a lot. I'm not sure exactly what can be done in this aspect, however, because I'm streaming music I suspect that whatever the issue is with the wifi might be the cause for the problem.
Click to expand...
Click to collapse
Higher channels than 11 is normally only used for outside usage (U-NII-3), and is rarely used on standard routers, at least in the US, which is most likely the reason for the setting. I also believe as you suspected that the blue-tooth issues you have experienced is due to this fact. I have no issues at all with the channels, but I believe my routers set-up is channel 6.
Updated to v.6, 2014-12-17 in OP
arcadia2uk said:
Higher channels than 11 is normally only used for outside usage (U-NII-3), and is rarely used on standard routers, at least in the US, which is most likely the reason for the setting. I also believe as you suspected that the blue-tooth issues you have experienced is due to this fact. I have no issues at all with the channels, but I believe my routers set-up is channel 6.
Updated to v.6, 2014-12-17 in OP
Click to expand...
Click to collapse
Is there a change-log for v.6?
Ludespeed said:
Is there a change-log for v.6?
Click to expand...
Click to collapse
No. All info about changes would be in the original post in the P900 version thread.
arcadia2uk said:
No. All info about changes would be in the original post in the P900 version thread.
Click to expand...
Click to collapse
Ok cool; thanks! Still trying decide flashing this or waiting till a sources build
Ludespeed said:
I thought having the same name in build.prop lets you auto restore your apps from google play after you wipe and flash a new rom but I could be wrong; anyone know
I use thumb keyboard for my tablet and phone; love it.
Click to expand...
Click to collapse
I recommend you use Titanium Backup. It restored both apps and the settings. Google Play only restores app, not the settings.
In the us 5 GHz wifi channels are in the 100's range. I had the same issues with my note 10.1 using gnabo rom. It is based on a european build. I had to set my router to channel 48 for the 5 ghz band and it now picks it up loud and clear.
Sent from my SM-T320
I'm in the US and entering the 14 in the line ro.WiFi.channels=14. Didn't allow my 5g channels to show up. Still looking for an answer.?
You have to change the channel on the router. Try 48
Sent from my SM-T320
@superdragonpt Due to the fact that I'm not allowed to post to the original
ROM thread, I'm providing my feedback via this channel.
I've successfully updated my phone to the latest AOSP 7.1.1 stable8 ROM with Gapps nano. Although most of the phone functions are working very well and maybe a little bit faster, there some smaller issues which I want to report or maybe ask for a solution:
1. From time to time the phone seems to freeze and then reboots with the
requirement to enter the SIM pin again. I've not yet identified a fixed schema
which my help to identify the root cause of the problem. Any tips how I can
solve this problem are appreciated.
2. The WIFI connection to 2.4/5 GHz access points seems to be worse than
with the old Android 5 image. I've read that other users have experienced
the same problem but a solution hasn't been provided yet.
3. The camera problems have already been discussed in another thread. So
I hope you will be able to fix it with the next stable release.
4. What I'm still missing is the option to choose between several audio profiles,
e.g. "silent", "normal", "loud" etc. It might be possible that I've not yet found
the option in the settings. If so, a tip how I can activate the feature would be
highly appreciated.
To 1: Today the phone freezed exactly as I selected a WIFI network and pressed the connect button. After a while it has rebooted automatically and I had to enter my SIM pin again.
[STABLE 10] Bugs I encountered
- NFC (Android Beam) file transfer error
- Bluetooth won't send/receive any .apk files
- High resolution video playback bug
- VPN connection does not tunnel to Built in browser, 3rd party app works.
- Hotspot breaks when turned on and off several times
- Wifi keeps disconnecting
- Idk if package installer in this build installs slower than previous ones
New members are not allowed to post reply on the original thread so I decided to report it here.
@jayjay1413 Might it be possible that you've mixed-up the phone types?
As far as I know a *stable10* doesn't exist for the Jiayu S3 Adv(ance) but
for the Jiayu S3 Plus.
Google Chromecast
Hi, using stable 8 I haven't been able to connect to my chromecast, I returned to the previous rom I was using (TFAndroid 2.54) that works perfectly for my S3 Advnace. I tried Nougat because I wanted the split screen featrure but for me chromecast connection is more important.