Develop Bugs

[Q] 3g Mobile Network Issues

A lot of times lately I'm losing my 3g Mobile Network, my signal strength will be a full 4 bars and I still get the issue. Usually if I reboot the phone it will come back. I'm starting to think it gets lost after it connects to WiFi and then when I disconnect WiFi. Anyone having this issue? If so, are there any tricks to getting this to stop?
My phone is completely stock 2.2, no root.
I'm not sure which of these events may have triggered my intermittent lack of 3G connectability but these are the only changes I've made since this started happening:
1) Upgraded to Froyo.
2) Performed the .dun trick to allow 3g Hotspot. (Although I never use it, I tested it a few times but this problem happens without the Hotspot turned on.)

Did you do a factory reset after the froyo update?
Sent from my Incredible using tapatalk.

Nope, I used the SD card method before I got the OTA. Have never done a factory reset.

I have this as well, be it im on a different carrier (Cricket) but it appears in all stock htc froyo builds.
My assumption is that is the radio being used. of how HTC's implementation of Froyo interacts with the radio.
I switched radio's and havent had it occur on me while in the OS yet, and it does occur sometimes on boot still, but if it loads on boot it seems to stay up and stable.
My trick is to turn airplane mode on for about 30 seconds (30 seconds after i see the airplane icon), then turn it off, i assume this reloads the radio, when the brings 3g back.
I can also read my nv settings with qpst and reflash them back to the phone with no changes, which causes the radio to reload as well, and 3g ALWAYS kicks back on.
Also updating the PRL (even if its the same PRL) seems to work as well (assuming this is due to the reboot, which reloaded the radio)
The radio i am using now is:
2.15.00.09.01 - Seems pretty stable, except the occasional one of at boot, which is fixed by airplane on/off.
From what i can gather this nothing to do with custom roms, as many offical Verizon customers on Official NON Rooted 100% completely stock phones have this as well.
Hopefully HTC/Verizon will fix this in a MR update.

token419 said:
My trick is to turn airplane mode on for about 30 seconds (30 seconds after i see the airplane icon), then turn it off, i assume this reloads the radio, when the brings 3g back.
Click to expand...
Click to collapse
I'm gonna try that next time it happens. Easier than rebooting, then it wont bother me too much.

I had that problem once, and never saw it again.
One problem that just happened for a second time today is I cannot send or recieve MMS. HTC had me reboot the phone and call VZW support, of course they yelled at me for not using a task killer -.-
The reset worked, but I'm going to get annoyed if this becomes a regular problem

I have same setup and same issue. As soon as I made the EPST changes for tethering and hotspot, I started having this issue where I'd lose my data connection completely after disconnecting from my wifi when I leave my house. A reboot of the phone fixes it but it's still kind of annoying. It happens I'd say about twice a week.

[Q] After official update, defy wont even charge or connect to 3g, any help?

Okay, heres my situation. Before I updated, I was running 2.1 stock, never rooted or made any mods. Then, I updated to the TmoUSA Defy 2.2 update (the one that was briefly released), and now I can no longer connect to 3g/ have EXTREMELY bad 3g reception.
Also, I can no longer boot into recovery mode (power button + volume down). When I see the Android figure with the "!", nothing happens when I touch the bottom left of the touch screen? To originally flash the 2.2 update, I simply went in to recovery, and flashed the update.zip. Im doing nothing differently now, and can no longer get into it.
My main issue I am having though, is with 3g reception. Im in the exact same spot of my house, and used to have 4 bars of 3g, and would get about 1.5mbps down, and now, Im forced onto Edge, which obviously is over 10 times slower -_-
Any help would be greatly appreciated!
___________________________________________________________________________________________________________________________
UPDATE:
Okay, this is AWFUL. I did a full reset through the recovery, and cleared the cache. But that did not help at all. On top of that, my issues are worse.
My phone cannot connect to 3g, I went to my school, and there are several cell towers on campus, and I always had full bars of 3G service. And guess what? I didnt get a single bar, just 2g service.
New problems occurred, now the phone gets hot, with no programs running. I tried restarting, but that didn't work. Second, my phone died in about 2-3 hours with little to no use, 1 txt thats all. And it DOESNT CHARGE AT ALL. At first, it took a few hours to charge from 20% to full, and now, I tried charging after school, and its stuck at 0%?
Is there any way to downgrade to 2.1, including the baseband? Should I contact Motorola? I've never rooted it, just installed the official 2.2 update for the US, the one that was briefly released (deeply regretting it now :'( )

Try pressing both volume up and down at the same time when you see the android guy. They changed it from touching lower screen in the upgrade to froyo
Then once in recovery do a restore reset and see if that helps.
Sent from my MB525 using XDA App

Okay, this is AWFUL. I did a full reset through the recovery, and cleared the cache. But that did not help at all. On top of that, my issues are worse.
My phone cannot connect to 3g, I went to my school, and there are several cell towers on campus, and I always had full bars of 3G service. And guess what? I didnt get a single bar, just 2g service.
New problems occurred, now the phone gets hot, with no programs running. I tried restarting, but that didn't work. Second, my phone died in about 2-3 hours with little to no use, 1 txt thats all. And it DOESNT CHARGE AT ALL. At first, it took a few hours to charge from 20% to full, and now, I tried charging after school, and its stuck at 0%?
Is there any way to downgrade to 2.1, including the baseband? Should I contact Motorola? I've never rooted it, just installed the official 2.2 update for the US, the one that was briefly released (deeply regretting it now :'( )

I presume you are indeed on T-Mo US? I'd start by calling their tech support, just get elevated to upper tier. Then give Moto a shot. Have you done an Operator selection search? If you go into the INFO menu -- dialer > *#*#4636#*#* > Phone information, scroll down to Preferred network type, it should say GSM auto (prl) to get 3G reception. If not, try changing it.

Bump? Any help would be great, I just sent an email to Motorola, but probably wont get a reply for a day or two. I can't even use my phone, it dies within 2 hours, doesn't charge, and wont even connect to 3g.....

scrannel said:
I presume you are indeed on T-Mo US? I'd start by calling their tech support, just get elevated to upper tier. Then give Moto a shot. Have you done an Operator selection search? If you go into the INFO menu -- dialer > *#*#4636#*#* > Phone information, scroll down to Preferred network type, it should say GSM auto (prl) to get 3G reception. If not, try changing it.
Click to expand...
Click to collapse
Thanks! I'll try that as soon as I can turn on my phone :'( Seriously though, thanks a lot. I am going to try that as soon as possible, but as of now, its been "charging" for 4 hours now, and it still just shows the picture of the battery @ 0%, and wont boot. I honestly have no idea, I tried a few different micro USB chargers, with no luck. When I used my Galaxy S charger, it showed a "?" instead of a %", as if it was not even recognizing the battery.

I assume you have tried the charger that came with the phone and have also tried it connected to USB on a computer?
Have you tried reformatting the SD card (or tried another) -- that may affect boot. And/or have you tried booting w/o SIM? I know you updated, but it could be a coincidental battery failure.

scrannel said:
I assume you have tried the charger that came with the phone and have also tried it connected to USB on a computer?
Have you tried reformatting the SD card (or tried another) -- that may affect boot. And/or have you tried booting w/o SIM? I know you updated, but it could be a coincidental battery failure.
Click to expand...
Click to collapse
Yes, that could be. But then again, it hasn't connected once to 3g after the update? I'm going to guess I have a battery failure, I kinda had a feeling that it might be that. It was so sudden though, I got great battery life, that lasted at least a full day to 2 days. And then after the update, it would hardly last 2 hours. The phone was also constantly warmer than usual, but I didn't have anything running. Im just going to hope that it was coincidental, and that right after I updated it, my battery died, and I didn't have it on GSM Auto (prl).

Welcome to my world...... I finally got to the point where I could only get Edge... Phone got replaced under warranty.

Loss of Service:Fix(kinda) test

Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.

i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better

Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.

plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App

I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium

I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!

I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.

Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)

Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.

I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.

Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App

Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk

about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?

I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium

leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.

I went to root+stock kernel and the problem is gone and LOS is gone to

txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium

Reboot Loop NEW FINDINGS

Hey guys, my gnex has just been stricken (for the second time) by the boot loop. Managed to fix it last time with a flash of the google image, but this time it isnt working.
Same as usual, mine features the greyed out wifi toggle as well, and reboots every time the screen goes off (which makes sense that I've been noticing it go off every 2 minutes).
I have found that the device will not reboot if it is plugged in and set in the dev options to "stay awake" while charging. This seems to keep it running, same if I set the time-out to longer. My theory has to do with the distribution of power...I think that something is telling the phone it doesn't have enough power to function.
Like everyone else I've done endless factory resets, flashed the goog image and such and such to no avail. Currently stock but I left my bootloader unlocked atm. I can still boot into recov and everything and even flash other roms.
Has anyone else noticed this, or could someone who is also having the problem confirm the screen thing?
I think last time I posted I was on winmo, missed this forum.

Bump? Anyone else having this issue?

Just send it in for warranty. I sent mine in and Samsung exchanged the phone

I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?

My Nexus has been stuck on "Turning WiFi on.." since I've had it. It would also constantly boot loop itself whenever the screen went off. I flashed the new AOKP build to avoid this issue, however, the WiFi still does not work If I'm ever on stock again, I'll give stay awake a shot.
I live in the U.S. with the GSM GNex, so warranty is out of the question unfortunately.

Fixed the loop by flashing aopk again with franco's kernel. Brilliant but my Wifi is still messed up. I flashed a new baseband XXKL1 and no improvements. I'm gonna just wait it out for a bit because I've seen some threads elsewhere where that has actually worked, but who knows. I'll probably cave and send it out soon.

RogerPodacter said:
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
Click to expand...
Click to collapse
Yes and no. It happened twice and the second time I fixed it by going FROM stock to AOPK with included kernel. Now it happened on THAT setup so I went back to stock and no dice. Its a very weird problem....

I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.

mastergrifis said:
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
Click to expand...
Click to collapse
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.

ShatteredAxe said:
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
Click to expand...
Click to collapse
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating

mastergrifis said:
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
Click to expand...
Click to collapse
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!

ShatteredAxe said:
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
Click to expand...
Click to collapse
I have a Desire Z by my side, but of course I want my Gnex back as new. The only thing that scares me is the warranty. I'm not sure if it's still valid. I mean, apparently there's no sign of root/bootloaderunlocked, but how can I explain that suddenly my phone has started rebooting itself without any reasons?

Yeah, only option is to just try and see what happens.

No call/text/data until reboot

Got a Note 3 last November, everything ran great, a few weeks ago the phone would show full signal with 4g LTE icon and everything but it cant make/receive call/text. No data whatsoever.
Airplane mode does not toggle it just grey out after activation. When trying to make a call it wouldn't go through and the call just get stuck, hitting the end button doesn't do anything. Everything is back to normal after a reboot, but the same thing would happen again every 2-3 days and would require another reboot.
CSR tried to resetting things on their end but that didn't fix it, got a new SIM, a replacement phone from Tmobile it does the same thing but less frequent.
Anyone else experience this? I'm about to get another replacement . Running latest T-mobile firmware/baseband no root/mods.

bobafuzz said:
Got a Note 3 last November, everything ran great, a few weeks ago the phone would show full signal with 4g LTE icon and everything but it cant make/receive call/text. No data whatsoever.
Airplane mode does not toggle it just grey out after activation. When trying to make a call it wouldn't go through and the call just get stuck, hitting the end button doesn't do anything. Everything is back to normal after a reboot, but the same thing would happen again every 2-3 days and would require another reboot.
CSR tried to resetting things on their end but that didn't fix it, got a new SIM, a replacement phone from Tmobile it does the same thing but less frequent.
Anyone else experience this? I'm about to get another replacement . Running latest T-mobile firmware/baseband no root/mods.
Click to expand...
Click to collapse
Are you running pure stock?

Pure stock, just got a replacement and the same thing happened again.

bobafuzz said:
Pure stock, just got a replacement and the same thing happened again.
Click to expand...
Click to collapse
I also got a Note 3 just 2 weeks ago. Same thing happened to my phone and I thought it was ROM that I had flashed. It has gone away but I am still wondering what was causing such symptoms.
I would see LTE but when I try to make calls there is no sound, not even rining and it would never go though. Someone would call me and my phone would not ring. Same with data, when all others get instant messages in a group chat, my note 3 would be the only one not receiving any messages.
It would stay this way until reboot. When the phone restarts then everything is back to normal. This was very very annoying because you would never know when your connection is lost.

Did you have to reboot to get it back?

bobafuzz said:
Did you have to reboot to get it back?
Click to expand...
Click to collapse
Yeah I had to reboot every time it did have those symptoms.