I was on 5.9.904 with Eclipse 2.2 and flashed back to 5.9.902 and upgraded to 5.9.905 then installed Eclipse 3 for 5.9.905 and now my 4G sucks.
Keep in mind I'm in a solid 4G area where it never switches to 3G.
Sometimes the icon is blue and it works but most of the time its white and doesn't work.
I have to set my phone to airplane mode and back for it to work again and sometimes that doesn't work.
If I go back to 5.9.902 and upgrade to 5.9.904 will that change the radio back to the old version or not? If nothing works I'm just going to get a replacement of hopefully a new phone from Verizon.
Thanks
If you had better connection with .902 then just FXZ back to that and don't install the official update when it ask you to. That is why there are different FXZ files so that you have the option to use what is best for you.
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
I haven't upgraded to 905 yet, but I've been having all sorts of problems with 4g for the past 2 days. I'm on 904 and eclipse
Sent from my DROID BIONIC using Tapatalk 2
scottocs said:
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
Click to expand...
Click to collapse
Radio updates are not always permanent. If you are on 5.9.905 you can FXZ back to 5.9.902 (which will put in the 5.9.902 radios) and then go find the 5.9.904 update.zip, and flash that in stock recovery to get back on the 5.9.904 radios.
Im starting to think it is something wrong with Eclipse 3 because the connection on stock 5.9.905 is working fine.
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
I think that I am not in a hurry to get the .905 OTA.
with all the issues with the last couple of radio updates im sure they will push out another one soon to fix those issues lol. it's best just to stick to a stable radio version until confirmed issues are solved.
Amendment to original post
Lemmy Caution said:
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
Click to expand...
Click to collapse
On further troubleshooting - assumed that root was not broken. It seemed that all of my apps were working as they should but when I attempted a SafeStrap restart and restore my UnSafe installation, The SafeStrap prompts would not appear. So, I checked root -found that it was in fact broken so, I ran Voodoo, restored root, ReInstalled Safestrap Recovery from the app and, restored my unsafe system to .905.
Since it was the weekend, I haven't had much of a chance to test 4G but while I was at the gym, I did listen to some podcasts. Email seems to be pushing. Today (weekday) should give me ample opportunity to test the update.
Hopefully, the restore fixed the problem.
This entire thread Sounds like bad hardware our user error
Sent from my Xclipsed Bionic
I am in the same boat here. I took the .905 update last weekend and my 4g has been terrible since. It stays 'white' most of the time and when it is blue and I open an application it instantly turns back to white and I get no connectivity...does anyone have a suggestion? Also, I was rooted and had safestrap. After the update...I guess I am not sure if I have root anymore? a root check app says I do not but I was still able to reinstall safestrap apk and then boot into eclipse.
Thanks in advance
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
My phone is 5.9.904. Does that mean I can't get the 905 update?
So is it the update or a network issue?
ronaldheld said:
So is it the update or a network issue?
Click to expand...
Click to collapse
On my personal use, I was trying to see if the MAX batt saver option had something to do with the data connecting. Since setting it on nighttime save, I havent had too much of an issue.
these are from the eclipse forum
I take no credit, but used them both (despite not having any data issues at all) and others claim these work:
A:
1. Power down
2. Remove the back cover, battery, SD card and SIM card.
3. Power back up, let the phone come all the way back up and tell you that you can only do "emergency calls only"
4. Power down
5. Reinstall SIM card, SD card, battery and back cover.
6. Power back on and let the phone boot normally.
B. in settings, Battery, Battery Mode, do not use "maximum battery saver". use nightime saver. (I use custom battery saver, which just slightly adjusts the nighttime hours).
no harm in trying these.
Link to 905
Anyone have a solid link to 905? The one DROIDMODDERX posted here (http://www.sendspace.com/file/xo8f4g) won't download to my phone. Not sure if it is my phone or the link. I can pull stuff off of Google Play all day long though.
Juroid said:
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
Click to expand...
Click to collapse
x2 on network issue. I've noticed 4g issues many times lately on my phone and also on stock .902
Not network issues....the leaked .905 is flawed.
My wife and I did a test. I did t his because for the 3 days I used the leak I noticed white data drops happening a helluva lot.
We were in the same room standing less than a foot apart in the same house.
We hit the same app/icons on our bionics at the same time even.
I had the .905 leak....it went white 5 times for roughly 15-120 seconds each time in a 15 minute window.....my wife's stock .902? NEVER.
Nuff said...or not. lol
Related
My first day with the Droid bionic... it's my first non-Samsung Android phone, so I'm not sure what to think.
In the midst of trying to figure it out and get it all setup (rooted, Titanium Backup restore, apps only), and my data drops out. Apparently for good.
I had solid 4G data when I first opened up the phone this afternoon. I ran some speed tests and switched to WiFi. I left the house a bit later and realized I couldn't open a webpage. I noticed the WiFi was still on, so I shut it off, but the cellular data never came back.
Tried putting it in airplane mode and back, rebooted (several times), tried the data toggle on the power control widget, I even forced the phone into CDMA only mode (and back).
I'm stumped. Has anyone else seen this? Is there any kind of possibility that restoring apps or rooting could have anything to do with it? I have not seen this problem over many a ROM on the Vibrant, and then the Droid Charge. I even loaded a GB ROM on the Charge and restored all my apps without issue.
Any help would be appreciated. I'd really not like to have to wipe the phone and start over.
I had something similar happen although I'm not rooted yet. For 3 days I was golden. Then I installed switchpro widget to see how the 3G/4G toggle worked with the Bionic and it made my mobile connectivity wonky. I uninstalled it. It still is wonky today.
LTE is there then goes away a reboot corrects it until it goes away. 3G is exactly the same. Turn on WIFI and the LTE disappears. It's supposed to stay up just turn white like it did for 3 days prior to installing then uninstalling switchpro. It could just be coincidence with the switchpro thing idk. I'm not all that knowledgeable with APN's, but after some research somehow I believe mine got mixed up via switchpro. Getting a new Bionic tomorrow.
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Flapjack said:
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
I'd get another one then. Or if you don't want to do that get a different brand
I think I'll just try a hard reset. I'm sure it was something I did with Titanium backup... I'll just have to figure out what.
Or you could try a factory reset to see if that solves it
EDIT: I see you thought of that 1st
Something similar happened to me. The only way I could fix it was by restarting the phone until the data crashed again. I solved this problem (or I think I did, still testing it) by removing all my widgets. I have a strong suspicion it was a widget doing this (specifically the AIX weather widget, but I am not sure yet).
So, I suggest that you remove all of your widgets and restart your phone and see what happens.
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
I'm thinking its got to be something related to wifi. every time I disconnect from wifi I can't connect to data unless I reset my phone.
Sent from my DROID BIONIC using XDA App
Flapjack said:
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
Click to expand...
Click to collapse
Glad to hear that. Factory reset did not fix it for me. Will have a new tomorrow
I am also having this problem. If Motorola still used vanilla android this wouldn't be an issue. I hate when manufacturers feel it necessary to fix something that isn't broke. I am sad to see how many people are experiencing this problem because if it was isolated to my phone and a few others then a warranty replacement would do the trick. I now feel like I wasted 380 on phone and accessories. I placed a call to Verizon tech support and their as clueless as usual. I hope an update is released soon that fixes this issue (or a custom rom). I remain hopeful that we start seeing good things on our Motorola devices now that google owns moto.
NOTE: I wish people would start reading through existing threads before starting new ones. I started a thread to this effect back on day 3. Several others have started threads to this effect as well. I think there are now 4 or 5 on this very same subject.
Sent from my DROID BIONIC using xda premium
soo this is my 2nd Droid 4 and i tried calling verizon and it seems they dont want to send me another one. i have ICS .213 (the same thing was on my last droid 4 but it did not have data/service problems just a bad battery and broken volume rocker)
every 20mins or so i will lose service and when i try to make a call it will say Sim invalid, well i went to the verizon store and got a new Sim card and it still does it, went back there again he gave me another one and still did the same thing so he told me to call tech support.
i called tech support and they pretty much do there normal stuff of rebooting and what not but now it seems they wont replace it as they just keep telling me to call back when it is happening (which of course by the time i get a tier 2 rep it will be working again) and i called back 4 times and they just say there is nothing they can do and i need to call when it is happening (which i do)
the last rep asked what my system version is so i hung up because i did not want them to flag my phone because i am on a leak ICS
has anyone else had the invalid sim? i tried a factory reset and wipe the cache and what not but it still happens
Do you have safestrap installed? You might want to try a 3rd party ROM, just to see whether that clears things up. Honestly, it sounds to me like a hardware issue, but it may have been better if you had waited to make sure your replacement phone was working properly before you flashed the leak
If a 3rd party ROM fixes the issue, I'd try reinstalling the leak.
If a 3rd party ROM doesn't fix the issue, I'd still try reinstalling the leak :silly:
Actually, before you do any of that, what mode is your wireless radio in? Settings-->More...-->Mobile Networks-->Network Mode
Assuming you are in the US on VZW (which it sounds like), it should be set to LTE/CDMA. When I first flashed the leak it was in 'Global' mode and I got all sorts of weird connectivity errors.
No i dont have safestrap. And Yea its in lte/cdma mode i finally got them to send me another one but wont be until thur
This new one im getting im just gonna leave it on GB and root it and wait for the official ics
Sent from my DROID4 using xda app-developers app
i might have fixed it... i reflashed the .213 ICS leak and right after that i did a system and cache format and so far no data drops as of yet and it seems i got more bars (was running on 2 bars now its 4) will post back in a few hours to tell if it really fixed it so in the future if this happens to someone else they can read this
came back to say after 2 hours of running fine it is back to dropping service like crazy, this is gonna be a rough two days with out a phone
does ICS leak .208 have a different radio then .213? if so can i just download the .208 file and then just flash it like normal?
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
I have a Bionic that i just put ICS on. 4G was killing my battery so i used *#*#4346#*#* to put it in CDMA auto. Now it won't let me revert back to LTE/cdma/evdo. I choose that setting and it automatically changes it back to CDMD auto. I haven't seen 4G since i did this. Please help! My wifes phone gets 4g service, so i know the service isn't down.
sweetchuck08 said:
I have a Bionic that i just put ICS on. 4G was killing my battery so i used *#*#4346#*#* to put it in CDMA auto. Now it won't let me revert back to LTE/cdma/evdo. I choose that setting and it automatically changes it back to CDMD auto. I haven't seen 4G since i did this. Please help! My wifes phone gets 4g service, so i know the service isn't down.
Click to expand...
Click to collapse
Mine did the same thing. I got mine back somehow. If I recall, I set it to the original setting again. After that I turned off data, and turned off the radio all together. Rebooted and it worked. I made a thread about this in the general section but 200 views later no response.
I had to do a factory reset to get mine back.
Been too scared to turn off 4g since.
I've heard of people having similar issues and were able to solve it by turning off the phone, removing the SIM card and powering it back on, then turning it off again re-inserting the SIM and then turning it back on. Not sure if it will help in your situation, but it's worth a try before a FDR.
Same here. Been too afraid to change it again.
Sent from my DROID BIONIC using xda app-developers app
Weird. I'm on leak 6.7.230 and it happily toggles between 3G and 3G+4G through that menu.
possible solution
I know I'm late to the party here, but i wanted to add my 2 cents, as i just got a Bionic and had this problem.
I used the LTE on/off app to turn the 4g off to save battery. When i wanted 4G back, it would not come back. I tried restarting, pulling the battery with the phone on, booting with no sim, etc. Nothing worked. Setting the phone to 4g would cause it to lose all data connections. The 3G would always stay on for about 20 secs, before dropping.
Finally, after a restart with, i went to the *#*#4346#*#* screen, set it to 4G, and pulled the battery before the data dropped (i already had the phone case open so a battery pull could be performed quickly. I then let the phone sit for a good 5+ minutes without a battery in it, and when i finally booted back up the 4G was there.
Now i don't know if this was a coincidence or not (i'm not going to try to replicate it, i'm leaving well-enough alone), but i wanted to share my experience b/c this thread was one of the top hits on Google for this specific problem. So hopefully this will help someone out.
I am stock, unrooted, and I installed the KitKat update a couple of weeks ago and my phone is absolutely terrible now.
1. Getting the "no-sim" (no sprint sim, no 4G for you!) error message, which I have never gotten before on this phone. I get the error intermittantly after installing the kitkat update
2. Battery drain is substantial, about twice the rate of what it was before
3. Phone runs much warmer than normal
4. Very bad reception, texts and calls not going through. I used to be able to get full bars 4G in my house, now I don't even get 3G after the update, and I had a 30 minute phone conversation from my house the other day and I dropped the call 4 times.
I thought maybe it was just a tower issue but it's been like this for the past few weeks. I've tried doing a PRL update, profile update, etc. but nothing helps.
Is the reception issue a problem with the most recent PRL update?
If I root the phone and install a custom ROM will this address my problems? I've rooted my tablets before but not a phone. Would going over to CM solve these issues?
I had the same problem way back on this phone and it was the SIM had gone bad. I would definitely expect that yours has just gone bad. That would cause your battery to drain due to constantly seeking network but SIM won't register. Which would also likely cause the excessive heat too.
I hope this is all the problem is for you. It was a simple fix at the Sprint store. Good luck!!!
Sent from my HTC One using Tapatalk
take the sim card out and clean it maybe? and do a factory reset after you backup?(of course, unless you root and use some software to backup, all other backup methods just won't help too much)
Reason been, I had the total stock phone when I did the KK update on Feb 1st I think, and I didn't see any problem other than somehow enabled my google voice. No signal problem(same s..t as the dec update last year, before that it was even worse) and no battery problem(turned on the stock battery saving)
I had problems (2) and (3), and a few others, since installing the update. In my case, the GPS receiving notification would flash incessantly, and Location Services seemed to be the battery drain culprit, I could dramatically reduce the drain by turning the GPS off (not a great solution).
The answer, at least in my case, was a hard reset. I did that, reinstalled my apps, and the GPS / battery issue has gone away. I was also having other intermittent weird issues that have gone away since reinstalling. I guess the upgrade must have corrupted some things...
Sent from my iPad using Tapatalk
Hard reset your phone and clean the SIM card. You should be all good then. Kit Kat should have the opposite effect on your battery life. I usually get 10+ hours on a charge. Matters what I'm doing with my phone.
Sent from my HTCONE using Tapatalk
Just wanted to add that my phone has suffered from none of the issues above. I'm using it on a GSM network in India and running InsertCoin Rom. Everything works well. Battery has been decent and I can easily pull 12 hrs plus
Sent from my HTCONE using Tapatalk
So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.
I dont think you can downgrade from KitKat to Jellybean not on stock atleast.
SeriesOfTubes said:
So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.
Click to expand...
Click to collapse
when you took the OverTheAir upgrade package, it will get into bootloader and change(upgrade) your phone's ROM(not really Read Only Memory any more, but still carry that name) and from then on, you will have to use the bootloader to reload the old jelly bean to get back to JB, otherwise, no matter how you reset, it'll be KK. (the reload process requires special files and procedures, with computer and USB cables) Although "factory reset" won't revert back to the "original factory settings" that came with the phone at the time you bought it, it will wipe out all the settings and apps and anything that's not set by the factory default. After the so called factory reset, your phone will get into a state that the "factory" testers have, which should be a stable state because the "factory" supposed to do a lot of tests based on that state and pass all those tests. This will give you a nice baseline about which could be wrong, the hardware, the network, or the software. Though, it won't be always true because human make mistakes, so the "factory" could release a software that's buggy. like the one we got on last dec, but still, once you get to the so called "factory" state, which all the other phones using the same hardware and software will get to the same point, you can be sure that no other unknown factors are causing your problems. It's like you have the exact same thing on your hand as somebody else on the other side of the planet, so other people can do the tests required to figure out your problems. Will that help you for some apps you want to run that crash your phone or cause big problem? No, that's the responsibility of the apps' developers, not the phone manufacturer. in that case, you'll have to give up that app.