Related
some people say drop data problem on Galaxy Nexus, it is related to radio/baseband issue, a lot of people recommend the following components
Radio/Baseband：
cwm-radio-i9250-xxla2 (latest radio from Google)
Kernel：
franco.Kernel-r158 (best kernel on market)
ROM：
aokp_maguro_build-35 (latest aokp rom)
Just go back to 4.0.2
Sent from my Galaxy Nexus using XDA
I have the above combination and it's worse. The radios in my device are going nuts.
How can it be so bad?
I'm like going crazy!!!
Its the worst phone ever !!!!!!!!!!
Sent from my Galaxy Nexus using XDA
Was at the Verizon store today and there floor model had no drop issues. Tried mine right next to it and it started to randomly drop. They are sending me a new one and are saying it will be here tomorrow hopefully I don't have the issue after the new one. The tech has a nexus and said he has no issues with his.
Sent from my Galaxy Nexus using Tapatalk 2
i had the same problem, it would drop data even though it showed i had strong signal until i set the min cpu to 700mhz. after i did that i never had any data drop problems
hope that helps
Came here to ask about this. Was wondering why it keeps happening. Was working fine when I was on stock 4.0.4 but since flashing aokp it happens all the time.
Sent from my Galaxy Nexus using XDA
I had these issues with aokp and Franco kernel m3. Switched to revolution hd and James Bond kernel. Haven't had a single drop since.
Skickat från min Galaxy Nexus via Tapatalk 2
I'm completely stock IMM76I, rooted and I sometimes get data drops.. this happens more frequently when I haven't rebooted my phone for several days. Sometimes the signal letter (H) disappears completely until I turn airplane mode on/off. Other times I see H but there is no data, only a reboot fixes it.
I'm using Tasker to auto-reboot the phone every day at 5AM, but this is gettig really annoying. I wasn't having any issues prior to that IMM76I OTA.
edwin124 said:
i had the same problem, it would drop data even though it showed i had strong signal until i set the min cpu to 700mhz. after i did that i never had any data drop problems
hope that helps
Click to expand...
Click to collapse
Noticed this was happening only when I was commuting on the highway, my phone loses data connectivity (albeit still showing 'H') and never gets it back until I reboot.
I'll try the set 700MHZ method and report back. But will increasing the min CPU from 350 to 700 hurt battery life a lot?
gabster21 said:
I'm completely stock IMM76I, rooted and I sometimes get data drops.. this happens more frequently when I haven't rebooted my phone for several days. Sometimes the signal letter (H) disappears completely until I turn airplane mode on/off. Other times I see H but there is no data, only a reboot fixes it.
I'm using Tasker to auto-reboot the phone every day at 5AM, but this is gettig really annoying. I wasn't having any issues prior to that IMM76I OTA.
Click to expand...
Click to collapse
I get this a lot, it's really annoying.
I'm really hopping they fix this in the next update, it totally ruins the experience of using the phone. You don't know what you'll get half the time.
gabster21 said:
Noticed this was happening only when I was commuting on the highway, my phone loses data connectivity (albeit still showing 'H') and never gets it back until I reboot.
I'll try the set 700MHZ method and report back. But will increasing the min CPU from 350 to 700 hurt battery life a lot?
Click to expand...
Click to collapse
Based on my exp, you don't lose much battery life. I accidentally left the CPU at minimum 691 MHz and got similar battery life with 307 MHz as my minimum.
Sent from my Galaxy Nexus using Tapatalk 2
If you don't have PRIMELA03* bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
blowtorch said:
If you don't have PRIMEKL03 bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
Click to expand...
Click to collapse
I just noticed I'm on the 4.0.1 bootloader. I'll flash the 4.0.4 one when I get home to see if I can finally get rid of this issue.
I tried flashing radios and RILs and it really hasn't helped...
I had similar issues though mine were mostly when leaving a wifi area my phone would not grab my cell data until I toggled airplane mode on then back off. Later I found out about GetRIL and discovered that most ROMs (due to being based on 4.0.4) have the XXLA02 RIL (Radio Interface Layer) while I was running the UGLC1 radio. GetRIL checks for you and allows you to flash the proper RIL (if rooted with busybox). I flashed the matching UGLC1 RIL and havent had a drop since
blowtorch said:
If you don't have PRIMEKL03 bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
Click to expand...
Click to collapse
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
andQlimax said:
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
Click to expand...
Click to collapse
As per my previous post I didnt change my Radio but rather matched my Radio to my RIL (Radio Interface Layer). My phone hasnt dropped data in the longest time since I've owned it and shows no signs of ever dropping it (unless of course I lose signal ).
WoodroweBones said:
As per my previous post I didnt change my Radio but rather matched my Radio to my RIL (Radio Interface Layer). My phone hasnt dropped data in the longest time since I've owned it and shows no signs of ever dropping it (unless of course I lose signal ).
Click to expand...
Click to collapse
Ya..wait for it
Inviato dal mio Galaxy Nexus con Tapatalk 2
andQlimax said:
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
Click to expand...
Click to collapse
This question has been asked way too many times. I say the same response because it helps people solve this problem. The bootloader and radio configuration needs to be correct at least as a starting point and first step in trouble shooting. you assume everyone has the correct bootloader and radio, now that is just presumptuous. I'm so happy that you know "everything" about radios bootloaders and apns that is righteous! your post was very helpful, a great help thanks so much.
andQlimax said:
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
Click to expand...
Click to collapse
This is actually not true. I was on 4.0.4 but had the 4.0.1 bootloader somehow.
I haven't had a single data drop since flashing the new bootloader with XXLA02. The real test will be tomorrow, when I take my phone into work (big metal building). If I get no data drops at all tomorrow, problem fixed.
A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse
Basic question. Still, have you backed up and tried Factory restore?
recently my phone doesn't read the SIM after a few hours of use. Says there's no SIM.
Sent from my HTC One X using Tapatalk 2
agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi
wilku said:
agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi
Click to expand...
Click to collapse
I do not agree. I'm also using 2.17 and everything with GPS and wifi is OK.
Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2
omaboy said:
Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I used only files from the instalation guide. No other modifications
CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)
krivas said:
A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse
Click to expand...
Click to collapse
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2
Hunt3r.j2 said:
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2
Click to expand...
Click to collapse
I did not drop the phone, or did something strange with it. The only thing i want from a device that costs € 500,00 is that everything is does work.
I've have experienced a drop in mobile network signal after the 2.17 update. Haven't tested GPS but WiFi seems alright. I have not dropped the phone nor done anything unusual to it, just updated. Before, I had 5 bars/full signal all the time, and when I checked battery stats the network signal indicator throughout the day was green. Now, after the update the indicator is yellow and I have around 1-3 bars if signal.
Also, I'm in Denmark so I got the 1.29.xxx.12 update which was supposed to optimize signal strength. So right now I hope they are working on a similar fix.
Sent from my HTC One X using xda app-developers app
smidgeox said:
CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)
Click to expand...
Click to collapse
The Custom ROMMERS part worked for me.
I had the same Problem. Just checked after a half hour and it still works.
Just try this method
Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.
I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app
dzdimov said:
I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app
Click to expand...
Click to collapse
To me, your issues sound like radio related issued, although I could be wrong. You both on custom roms? With custom recoveries? I suggest if 1.29 worked better signal wise that you flash that radio in your custom recovery. That might improve your signal. Its basically different for everyone which radios work the best so basically it's trial and error.
Lemme know how you get on :thumbup:
Nightscope said:
Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.
Click to expand...
Click to collapse
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now
duckysempai said:
I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now
Click to expand...
Click to collapse
Hi, have you flashed any different radios? What's your current software version and does your Wifi drop as well? Or is it just mobile data?
After the 2.17 OTA update, the signal is always medium...but now there r no call drops or loss in signal
sandipbarik said:
I got my 2.17 OTA update last night, immedietly after the update my wifi signal was dropping, which was pretty stable 3 bars before that.
Today morning im getting dropped gsm signal...sometimes its showing no signal...eve a manual signal search gets me no network, omly airplane mode on/off gets the signal back.
I m not unlocked and not rooted...just plain factory stock.
should i unlock it and flash the radio from the 1.29 rom ??
Click to expand...
Click to collapse
That's up to you, but many users have experienced that some radios work better for different people. 2.17 works ok for me, maybe you should try.
Sent from my HTC One X
I think i have the same problem, when data On, GPS On he sometimes turn of after i turn in and when put the pin and he try to connect to the carrier turn of again. This only happens now when i flash faux kernel and before with alex-v kernel..
I have been having random data "stoppage" on my GSM G-Nex since it first came out.
Data will suddenly stop. I can tell when all the bars turn grey and the "+" sign goes away or when I am listening to Pandora or XM/Sirius and it suddenly stops. This is in areas with solid 100% full signal coverage. It happens usually once a day at minimum and at random times.
I have tried numerous ICS roms & radios with the same results. Problem is, I usually don't notice it until long periods go between getting emails or someone asks me "did you get my email?". I check the phone and data is gone.
I have to reboot to get it back.
I know this issue has been around since the beginning of the G-Nex but I am wondering if there has been any actual fix for it either by a hack or from Samsung. It's really annoying. Has JB fixed it 100% or is it a hardware issue?
Search for an app called restart connections. That might be a simpler, if not very elegant, solution. You could schedule it to run every 30min.
Sent from my Galaxy Nexus using xda app-developers app
I used to get data drops with 4.0.4.
After updating to JB I've yet to have one.
Sent from my Nexus 7 using xda premium
El Daddy said:
I used to get data drops with 4.0.4.
After updating to JB I've yet to have one.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That's good news. I've had a couple JB ROMs (including stock) but there are 2 apps that don't work properly for me that I need. Hopefully that will be fixed soon and I will give JB a shot again. Frankly, I really didn't see too much in JB that made me want it "now" so I am in no rush to upgrade again until my apps are fixed.
Hmm, never had data drops, from 4.0.2 all the way to 4.1.1.
I actually have this problem every now and then. Hate it because sometimes it's when I need the Internet. Gonna give 4.1 a shot since aokp just came out with m1. Hopefully this helps.
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
So i was wondering if anyone else is having this issue.
for reference, I am on VZW, with the 4.1.1 radios (as the updated 4.2 radios had me locked into 3G no matter what, at work)
and i ALWAYS do a complete wipe (data/cache/dalvik/system) between ROM flashes.
4.3 bootloader as well.
anyway, this has been an issue since 4.3 hit my device...anything from pure AOSP to CM builds.
when I am on 3G, the bars will go gray and i cannot pull down data at all. (and yes i know the difference between blue and gray bars, I'm saying ANYTHING will say "network not available" not just google apps)
toggling data on/off fixes the problem. I ususally run into this problem 2-3 times a day and it is ALWAYS on 3G.
its not a huge deal, just more annoying than anything else. just wondering if I am alone here. going to be giving the 4.2.2 radios another chance and see if that fixes things.
Having this exact issue...it's driving me nuts as well. At this point I believe I've tried every radio with no luck. Going to try jumping back to 4.2 soon to see if it solves the issue.
Me too
+1
I love how much fast my GNex is on 4.3, but I don't think I can deal with this data bull**** much longer. Frankly, I'm really getting tired of getting a new version of Android, being happy at first, then finding the HUGE bug that makes my phone a horror to use. WHY HAVE YOU FORSAKEN THINE VZW GNEX, GOOGLE!?!?
Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.
ericbarch said:
Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.
Click to expand...
Click to collapse
That's right, 4.3 sucks.
Sent from my Galaxy Nexus using Tapatalk 4
Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app
So happy I found this thread!
I'm having the SAME issue: GSM i9250 on Straight talk ATT sim (apn setting are updated and correct). Stock not rooted; been happening since 4.3 Update. From what I've read even folks on the N4 are having similar issues.
I've factory reset 3-4 times for testing purposes (back to "normal" for about an hour then those pesky gray bars and NO data on 3G/4G).
I have to do the airplane mode toggle every 1/2 hour if I'm really using the internet. Big pain in the ass!
I always rooted my devices in the past and haven't done the GNEX because I always felt stock was smooth enough for my purposes (quasi-work-phone and I need stability). If I have to deal with this bull-sh&% I'm probably gonna have to root and install a 4.2 ROM.
Any-whoo...thanks for letting me rant :^)
Hopefully "kit-kat" will help?
same issue its very annoying... did anyone find the fix ??
ffejy462 said:
Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Is this a fix?
My issue seems to be on 4g as well. If the phone switches from wifi to 4g or if it goes from 4g to 3g and back to 4g it shows a connection with bars but never connects to data again.