Database Users

2.15.00.07.28 radio & 3G connectivity issue

Just FYI, whenever I reboot my phone my 3G still does not come on. Toggling the Mobile widget still does not work. My only fix is to toggle Airplane mode. I was hoping the new radio would fix this problem.
Anyone else?

second that
hey, I second that. I have seen some other forums denying he issue but there is def an issue with the 3g. Turning my phone on and off or turning airplane mode on or off fixes the problem as well. Also, Idk if this is a Pandora issue of not but, Pandora radio will pause itself sometimes and not resume as well as skip songs before they are done randomly. Once again I am not sute what is to blame for the Pandora issue. I have 2.2 froyo leaked installed and the streaming audio fix b4 fix and v5 fix installed from the update thread from the froyo 2.2 leaked thread

Whenever I go from WiFi to 3G it never works. I have to reboot or do the airplane mode "trick".

I'm using hydra kernel v1 ocuv @ 1.13 ghz and the 8/1 leak with some fixes..
Just ran unrevoked-forever and updated to 2.15.00.07.28 radio. No issues with 3g connectivity.
Maybe you should reinstall your Rom and verify you have the most recent kernel.
I have heard there being issues with 2.1 and the new baseband. Not sure if this applies to you guys.
I don't have this issue.
Sent from my ADR6300 using XDA App

I had this issue with the 2.05 radio and the leaked OTA. Enough of an issue to revert back to stock.
Now I'm running 2.15 radio and aiccucs v4.2 ROM with zero issues. I thought I was having radio issue, but remembered where I work I have terrible reception anyway.

hometoast said:
Now I'm running 2.15 radio and aiccucs v4.2 ROM with zero issues. I thought I was having radio issue, but remembered where I work I have terrible reception anyway.
Click to expand...
Click to collapse
i also am running 2.15 radio on iuccucs v4.2rom and have no issues with 3g. i also had the 2.15 radio running on stock rooted 2.1 for a week or so with no issues.
its maybe something to do with the kernel/rom your running?

SLOflatlander said:
i also am running 2.15 radio on iuccucs v4.2rom and have no issues with 3g. i also had the 2.15 radio running on stock rooted 2.1 for a week or so with no issues.
its maybe something to do with the kernel/rom your running?
Click to expand...
Click to collapse
I'm assuming it is some application that's causing it...because only a few people seem to be having this problem, and it does not appear to be related to any particular ROM. Be nice if Android 2.2 had a safe mode or diagnostic startup.

I can't really say that I've had any issues. It seems spotty at times and I have issues downloading from market but nothing like you mention.
Sent from my ADR6300 using XDA App

I haven't lost 3g too often, but when it happens the airplane mode doesn't do anything, still shows signal bars without the 3g symbol. then if i reboot it boots up into airplane mode, and i can disable it and get 3g back.
cant wait for the official build, just glad we got s-off

do you have juice defender installed? i think it toggles mobile data on and off every so often to save battery if im not mistaken

SLOflatlander said:
do you have juice defender installed? i think it toggles mobile data on and off every so often to save battery if im not mistaken
Click to expand...
Click to collapse
Good idea, but not in my case...

3G connectivity issue resolved (in my case anyway) !!!
Problem: no 3g after re-booting. Only apparent fix was to toggle airplane mode.
Here's something that I just discovered... Whenever I re-boot, there is about a 90% chance that 3G will not start up. However, if I remove the lock screen right after it first appears (during boot-up) then 3G will always start. So in my case, it was the lock screen that was preventing my 3G from starting up.
I don't know if this is the same 3G connectivity issue that others are having, but in my case this (removing/sliding the lock screen) has worked 100% of the time, so far.

3g Issue Resolved, Fluke?
Whenever booting up dictionary word of the day widget would force close, assuming due to no connectivity. It may be a fluke, but once I removed the widget and restarted, no error, and 3g consistently... Will report back if anything changes...

I had the problem on a FRESH install of FrankenROM running the 2.15 radio. I reflashed and still had the problem.
I've run SkyRaider 2.2, 2.5 and 2.5.2 with no problems and am currently running CM6 RC3 and haven't ever had the issue either... All with the 2.15 radio.

Random Reboots

So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?

I called today the customer service of my carrier "oi" and I spent kinda 30 minutes talking, trying to solve a problem.
When I saw, my phone was in a bootloop with the cyanogenmod boot and I was continuing to talk, without any interrumption.
The only difference was thet the phone was hot!
Running at 1.4 with the last netarchy kernel my max was 38!!! (low)

Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue

slowz3r said:
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
Click to expand...
Click to collapse
I hope so!

Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.

Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App

No random reboots here, got it on the 3rd. Phone runs smooth as silk. I'm on stock 2.3.2. Out of all the phones I've owned this has been the most stable.
Could my phone possibly be from a different batch? I'm not experiencing any of the issues alot of other people are besides 100% init process, which I solved with keeping USB debugging on.
Sent from my Nexus S using XDA App

ruben8448 said:
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't think it's the kernel, even stock users have the reboot problems.

I don't have any such problem on Cyanogenmod 7 rc1...

iKitsunee said:
I don't think it's the kernel, even stock users have the reboot problems.
Click to expand...
Click to collapse
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App

ruben8448 said:
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ah, I'm actually using that kernel as well, hasn't happened to me but I suppose it might vary from phone to phone.

jerrycycle said:
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Click to expand...
Click to collapse
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.

Serious_Beans said:
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Click to expand...
Click to collapse
The kernel is set to default at stock setting so no need to have it set on boot. It isn't going to overclock unless you raise the cpu past 1g

google have already said that the problem its just s/w and they are going to fix it with an update and it's not the new 2.3.3! Hope it don't take much longer!!
Sent from my Nexus S using XDA App

There is a stock kernel for cm7 out that has all the voodoo engagement and ext 4 hack

I've had random reboots and it only happens to me when I'm using bluetooth.
Sent from my Nexus S using XDA App

its been over one month now and i never had such problem with mine..its running smoothly both with stock and cm7..

I experienced my first random reboot today. Installed clocksync and was fine. Today I loaded the app... screen was blank then saw the boot animation.
Sent from my Nexus S

I experienced 2 reboots in a row trying to retrieve a service from my mobile operator. I got so frustrated ´cause the mobile operator service takes too long,
the last time I looked, elapsed 7 minutes, few minutes later, reboot...
Became afraid to call again from the nexus, not trusting anymore
wifi on, sync on, bluetooth off, gps off, it was charging with the regular charger, factory rom and kernel, not rooted, launcher pro

I also have random reboots. it's strange though, it goes to the boot animation for some time, looks like the phone reboots, then all the apps and launcher is reloaded, but if you check the phone boot time under settings -> about, the uptime is not reset.
can you guys confirm that your boot times are also no reset during the randon reboots oft he known google android software issue for nexus s?
thanks,

[Q] Random Reboots

Ok guys, I know that there are posts about random reboots but it seems non have a solid solution. My Hd2 has started doing these annoying reboots for about a week. I was using Tyweens NexusHD2 2.9 and all of a sudden reboots started. So I switched to Typhoon CM7 3.5.7(currently on phone now). Reboots still occur. So I did Task 29, wiped sd card, plus clean install of Typhoon CM7 3.5.7. Phone still reboots. It actually rebooted during setup. I even changed from Magldr 150/5(suggested) to 200/45 thinking it was memory related. Still rebooting. I have noticed it does it more when WiFi is on. Is there something with the latest Android 2.3.5 and Wifi? Any help would be greatly appreciated.

beergenius said:
Ok guys, I know that there are posts about random reboots but it seems non have a solid solution. My Hd2 has started doing these annoying reboots for about a week. I was using Tyweens NexusHD2 2.9 and all of a sudden reboots started. So I switched to Typhoon CM7 3.5.7(currently on phone now). Reboots still occur. So I did Task 29, wiped sd card, plus clean install of Typhoon CM7 3.5.7. Phone still reboots. It actually rebooted during setup. I even changed from Magldr 150/5(suggested) to 200/45 thinking it was memory related. Still rebooting. I have noticed it does it more when WiFi is on. Is there something with the latest Android 2.3.5 and Wifi? Any help would be greatly appreciated.
Click to expand...
Click to collapse
did you overclock or undervolt ?
Sent from my HTC HD2 using XDA Premium App

tmotard said:
did you overclock or undervolt ?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No not at all.

I'm having the exact same problem... but strangely now even when I try older gingerbread builds, it does the same thing. Its only been recently, too... I've had the phone for a while and I don't remember it doing this.
I can have the, same build and same gps libs on my wifes hd2, and hers won't reboot. Mine will.
I even went as far as swapping out my mainboard with another one I had from a cracked screen issue... and that didn't solve the reboots.
I can't figure it out. It must be gingerbread and certain phones. Ive tried 2.3.5, 2.3.4 and 2.3.3 and they all are now rebooting. I don't know why its only been lately, too. The, only thing that solves it for me is running Tytungs NexusHD2 ROM v1.9 Froyo based. I can even add the latest agps fix and don't have any reboots. Only thing I really miss from gingerbread is the DSP bass boost which makes a huge difference for my bluetooth audio via my car.
Remains a frustrating mystery to me.

turn wi-fi sleep policy never

karizman76 said:
turn wi-fi sleep policy never
Click to expand...
Click to collapse
I always set this as my default wifi policy since I am always connected at home. So that's a no-go for that tip. At least for me, personally... still reboots.

So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.

beergenius said:
So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.
Click to expand...
Click to collapse
Rafdroid is a Froyo based ROM - same with the NexusHD2 v1.9g build that I'm using and so far no problems.
But when using any gingerbread (sense or non-sense) / CM7 build, I am getting those random reboots. Sometimes so much to the point where the phone is unusable. Then there are times when I could go hours without any. I thought it was something related to 2.3.5 since that's right around the time things started going strange, but like I noted - I've downgraded to 2.3.4 and 2.3.3 - and the same thing is happening. I used to use Hyperdroid GBX 7 for months without issue... now when I load it, it gives the same result. Same with Hyperdroid GBX v12, Hyperdroid CM7, Typhoon, stock bravo based CM7 Nightlies, AmericanAndroid, NexusHD2 Gingerbread version or anything Gingerbread based - period.
It also seems coincidental that the reboots started right around the time when Tmobile issued a bulletin asking for user input about recent unusual high battery draining with mobile data. I really haven't followed up and I don't know if it was determined what was causing it for some users but I am thinking maybe it could be possibly related. I can't explain why my wife's phone can run the exact same ROM and not experience the same thing yet mine does. It seems like an isolated issue - I don't see a lot of people complaining about the same issue lately. Maybe it has something to do with a specific mainboard revision/manufacturing date and some kind of over sensitivity to mobile data power output or something. As I noted in the prior post, I did switch out the mainboard with another one that I had laying around. I did take note of the revision manufacturing date stamped on the board, and they were identical. And both experience the identical problem. My wife's HD2 was bought 3rd party from a private owner at another time separate from when the 2 HD2's I have on hand were purchased. Perhaps she has a different revision/manufacturing date.
The two mainboards that I am having a problem with have a date of 2010/03/16 - they are both identical.
I would take apart my wife's to check her date and am willing to bet it's something different, but I've had really bad luck picking apart these HD2's the few times that I've done it. I've broken wifi coaxial cables and ripped flex cables. The date is stamped on the bottom of the mainboard.

beergenius said:
So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.
Click to expand...
Click to collapse
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried

zaq said:
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried
Click to expand...
Click to collapse
I am wondering if specific phones that run Gingerbread are experiencing this lately because of this:
http://support.t-mobile.com/thread/3544?start=0&tstart=0
Like I noted - perhaps it has something to do with an oversensitivity to 3G mobile data power output, etc.

zaq said:
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried
Click to expand...
Click to collapse
Same behavior here - had random reboots multiple times per day until I switched to 2G only (only adjustment I made)....have not had one in over 72 hours of uptime now.

Sounds like Bad Blocks to me. Happens to a lot of ppl, me included.
I have 4.
http://forum.xda-developers.com/showthread.php?t=1189544

casemandan said:
Sounds like Bad Blocks to me. Happens to a lot of ppl, me included.
I have 4.
http://forum.xda-developers.com/showthread.php?t=1189544
Click to expand...
Click to collapse
How would bad blocks be the problem if the solution is turning off 3G?

rocklobster702 said:
The two mainboards that I am having a problem with have a date of 2010/03/16 - they are both identical.
I would take apart my wife's to check her date and am willing to bet it's something different, but I've had really bad luck picking apart these HD2's the few times that I've done it. I've broken wifi coaxial cables and ripped flex cables. The date is stamped on the bottom of the mainboard.
Click to expand...
Click to collapse
OK, I can now pretty much confirm my original hypothesis about the mainboard. I have switched it out with one that was manufactured in late 2009 according to the timestamp on the board, and that's eliminated this problem for a while now with Gingerbread entirely.
The exact problem is beyond me, but unfortunately I stick to my guns that it's a hardware issue. Not sure why it would affect Gingerbread so much more than Froyo but my guess would be it has something to so with mobile data power management or something of the sort.
So for those saying that turning 3G off counteracts this rebooting effect, try a good Froyo build to keep your 3G connectivity. The reboots didn't happen nearly as much as they did wile running Gingerbread for me (although I would get 1 or 2 every few days).
Unless you can get your hands on another mainboard... or another phone.
Replacing my HD2 entirely for now wasn't an option for me... it's the only "Android" phone that I can run with the grandfathered 5.99 Tmobile web. Any native Android phone is identified by tmobile from its IEMI and forced to upgrade to a smartphone data plan to work with mobile data. They just happen to allow legacy (less than WP7) Windows Phones work with that old data plan, which is what the HD2 is.

sgalbincea said:
Same behavior here - had random reboots multiple times per day until I switched to 2G only (only adjustment I made)....have not had one in over 72 hours of uptime now.
Click to expand...
Click to collapse
+1 switching to 2g sucks but works,my wifes hd2 works fine though like others have mentioned. this is crazy lol
BTW all these reboots stated for me when to mobile messed up their signals and was causing android phones to have high batt drain.

Where can i switched off 3G beacause i've the same problem with reboots?

Settings networks and mobile network
Sent from my HTC HD2 using XDA App

I have notice mine does it when I am at home using WIFI and 3G is on. If I turn 3G off all is ok. When I am out and about I can turn WIFI off and 3G on and no problems. Wacky.

i had a similar problem on my hd2 tmobile with coredroid 1.6 on it..
Random reboots have become all too often, usually when i start applications and i did not want to waste any more time so I changed the rom...

I would get a random reboot every two our there hours until I took of all my widgets except for two and I haven't had a random reboot in about 2 days and I didn't mess with the 3g signals. but my phone still has battery drain issues
Sent from my HTC HD2 using xda premium

[Q] Phone calls cause device crash

When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?

*deleted post incorrect information

Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium

dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?

chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED

How did you solve the issue?

I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.

Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.

xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.

[Q] Phone locks up and restarts with navigation - overheat it seems?

I've been noticing this problem increase over the past few months. It started when I used navigation over longer trips like an hour. The phone would all of a sudden stop responding and then just restart. I noticed its really hot when this happens so I figure it's overheating. Recently it even happens on short trips.
I'm using triforce rom 3.1 which uses agat's kernel. I have not noticed any other restart or crashing issues aside from when I use navigation. I find it important to mention that this all occurs even if the phone is not plugged in or charging.
Has anyone else noticed something like this?
I thought about taking it to sprint since i have tep, but I figure they will either just tell me it's my fault since it's a custom rom or just offer to format the phone like they do with every other problem.
Any ideas are appreciated.

Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app

chris-allen said:
Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.

iivisionii said:
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.
Click to expand...
Click to collapse
I just wanted to follow up and see if anyone had more suggestions or a specific kernel to try. I tried 3 different ones with the following results:
KT-SGS4-JB4.2-TW-SPR-02.20.2014 - No navigation reboots, started rebooting randomly otherwise
AGAT_GS4_v0.5.1 - Still reboots/overheats during navigation
AGAT_GS4_v0.5.2 - Still reboots/overheats during navigation

Stock. I've never had good luck on custom kernels going back to the S2 (the same devs as currently).
Really, my devices have always ran worse and with significant issues, including the one you are describing.
If that's not an option, play with the governor settings, remove any overclock, and try other ROMs.