Related
Ever since upgrading to AT&T 2.2, I have a had an issue that on every other reboot, the phone radio does not turn on. I am not getting a SIM error, or any other error indication, nor does the phone go to airplane mode (bluetooth and wifi work). If I check phone settings, I get phone # unknown and no phone signal. Once I shut the phone down and turn it back on again, phone service is back.
I'd suspect a SIM issue, but this did not happen on 2.1. Could this be a bad flash (I could not get Kies Mini to push the firmware, I had to install via Odin)? Has anyone else seen this kind of flakiness?
Bump
Is anyone else seeing intermittent issues of the phone thinking it doesn't have a SIM installed? The good news is that I have not had two reboots in a row with this problem, the bad news is that I do see this on nearly 50% of boots.
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
ryanmahan said:
I dont have the problem, if it does happens it only happens like once a week for me, it usually fixes it by going into airplane and back to regular
Click to expand...
Click to collapse
I tried that. On my phone, that does not remedy the situation. The SIM itself has not moved since the update (I can't remember if I pulled it when I ran the upgrade), so I don't think it's a loose contact.
att can fix
Bring the SIM and phone into ATT, they will fix it for you there, hopefully for free, that could work, just unroot before and unflash if you did, then say you have SIM problems and then tell them that you had it in during the update, sometimes that causes problems
I have this same issue. Yesterday after about 5 reboots the phone would not pick up any signal... at times and after several minutes, some signal would show up and then disappear again... After about the fifth time, I turned off WiFi, because it had been on the whole time and that fixed the problem. Signal came back after a while and was stable. Turning WiFi back on did not bring back the problem. I guess Froyo just does not like the WiFi being on when booting the phone. Hopefully this can help others fix this same issue when encountered.
Sent from my SAMSUNG-SGH-I897 using XDA App
So over the last few days my phone seems to have settled into some sort of weird pattern with reboots. Although there are outliers, in general it always seems to reboot between 19-24h of uptime and nearly always at like 45 or 50 mins past the hour. It's the most bizarre thing in the world and why I think there's some funky software doing it. I don't have true random reboots, but I can't figure out what it is that is doing this. Very odd.
In all cases my phone is sitting with the screen off (I've NEVER had a reboot while using the phone/screen on) but it doesn't matter what radios are on, WiFi, BT, GPS (can be off or on).
Last time I ran "CatLog" a logging app from Market and had it write to SD logs and a reboot happened but it only by default writes every 200 lines so the last line in the file was probably not the last line in the log. I'm going to try again later and set it to write every line or few lines so I can see the last entry in the log before a reboot. Might shine some light on it.
Just find it very strange since it's a very stable and capable phone for about 18hrs and then it just craps on itself. Very strange.
finally. I too just think it is some weird software or driver bug because I was running EB 1.0.4 FINE for like 3-4 days and loving it... then it started resetting almost hourly. I didn't install any other apps past my initial normal set of apps.
Even CM7, seems like it is fine for a few days, then gets crazy. As long as I put a new nightly rom on it every day, it's good.
I didn't have any issues with stock though and didn't seem to have issues with CM7 for a while until lately.
The leaked GB rom causes lockups immediately out of the gate seemed hourly.
I use CM7 as my main daily driver now but I think you are on to something. We are talking about the Screen of Death right? I don't think mine ever reboots, but gets stuck at the lockscreen where the the display comes up, swiping to unlock vibrates then the phone but doesn't change screens to desktop. The buttons and click/drag widgets work even though you are looking the lockscreen.
I've never had my phone powered off in my pocket or noticed it "rebooting". Mine just has the SoD that seems to follow your pattern idea. They may be related. Stock roms may reset once it locks up, where CM7 just keeps running in its locked state.
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
I just hope that update gets here sooner than later.
Sent from my LG-P999 using XDA App
I dunno. The tmobile jingle is pretty loud and I never hear it. CM7 has a silent one so possibly there but I dunno.
I use my phone pretty often and never had the suspicious that it reboots. My phone stays very cool during my usage compared to my nexus and other phones
My uptime was 4 hours since I reset it last. I'll monitor it with results. It'll be hard not to flash but I'll keep track and see how far I can keep it online.
i have not had any reboots or waking up to a dead phone ....with the only fix is a battery pull.... ever since I started.
1) my over night charging / long term charging to 100%... only on the LG charger that it came with. Only short term...maybe. less than an hour and not to a 100% charge on a non LG charger (car charger etc...)
2) I restart my G2x every morning when I take it off the LG charger..(after I take it off..I did it once while on the charger and had an issue... (there is definitely an issue related to when it charges to/ around 100% charge)
Just my 2 cents.
Pattern to my reboots - do yours have a pattern?
Hold Power and volume up simultaneously for about 10 seconds.
I've had my phone since Friday, but the only time I had the rebooting problem was this past Saturday when it rebooted four times within 15 minutes or so. Before the rebooting began, the phone had slowed down to a crawl, so I went ahead and rebooted it. After that, I sat it down and watched it reboot a few times on its own. Luckily my iPhone 4 owning co-worker was completely unaware of this issue since we tease and bicker with each other every day over Android and iOS .
mobilehavoc said:
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
Click to expand...
Click to collapse
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
smashpunks said:
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
Click to expand...
Click to collapse
What bloat did you remove? I've removed most but not all of it. Can you list it?
mobilehavoc said:
What bloat did you remove? I've removed most but not all of it. Can you list it?
Click to expand...
Click to collapse
Everything other than smart share, tegra zone and qik. Of course have nova and need for speed also.
Oh also have car home froze..
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
player911 said:
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
Click to expand...
Click to collapse
Yes I know the battery driver is part of the problem as can be seen on CM7 builds but what's odd is my time varies so for a long time it would reboot every 17-20 hours, now all of a sudden it goes to 36 hours before it usually reboots. Looking at logs it doesn't appear to throw any major errors before a reboot which implies that it's a a kernel panic or low-level fault. At this point I've given up on trying to find the issue since it's been repeated over and over that T-Mo and LG are releasing an update. Might as well enjoy the phone and wait for that to come out
Amen. Just keep flashing CM nightlies and you'll never worry about it.
Guys I'm having an extremely frustrating issue. Anytime I flash a ROM, it'll work great for a little while, but then sometimes when i reboot, it'll say no signal, and then my phone thinks it's in airplane mode. I try to get out of it, but it won't. Then randomly it'll get signal, but the phone will be so slow and laggy, and then it goes back to no signal and no more lag. I've been using Infused ROM and usually that one is okay, but sometimes I've had to reflash to get it fully working. Lately I switched to SensatioN ROM using Hellraiser, and this one has given me trouble every single time. I've reflashed about 5 or 6 times, and even went back to stock. Any idea what is going on?!?
bgree15 said:
Guys I'm having an extremely frustrating issue. Anytime I flash a ROM, it'll work great for a little while, but then sometimes when i reboot, it'll say no signal, and then my phone thinks it's in airplane mode. I try to get out of it, but it won't. Then randomly it'll get signal, but the phone will be so slow and laggy, and then it goes back to no signal and no more lag. I've been using Infused ROM and usually that one is okay, but sometimes I've had to reflash to get it fully working. Lately I switched to SensatioN ROM using Hellraiser, and this one has given me trouble every single time. I've reflashed about 5 or 6 times, and even went back to stock. Any idea what is going on?!?
Click to expand...
Click to collapse
My first guess would be a hardware defect. Try a complete return to stock (and STAY stock), including a wipe/factory reset from the Settings screen and see how it performs. If the signal is still wacky - time for warranty service.
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
I
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
I don't know why your having such an issue with cm. Which is odd because I'm running a rom that's CM based and works fine. I'd say maybe try another rom if for nothing other than to see if CM is truly the issue.
I praise you for having the unlimited data still, I wish I would be been smarter and kept mine because there are months where I'm a little too close to that sad but lack of data with 2gb
And my hometown is Syracuse NY as I see your city is there. I miss the cuse but not the loudness of the city
From my Wicked S3 on SOKP
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
BSOD2600 said:
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
Click to expand...
Click to collapse
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
From my Wicked S3 on SOKP
ShapesBlue said:
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
Click to expand...
Click to collapse
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
BSOD2600 said:
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
Click to expand...
Click to collapse
Yes freeze stock camera. I'm using focal and it works fine but the stock camera won't work at all
From my Wicked S3 on SOKP
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
BattsNotIncld said:
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
Click to expand...
Click to collapse
I think you might be right. Even when it is up and running, I have been noticing lately that I get the power menu popping up sometimes when I wasn't even touching the power button. So last night when it was in one of its constant boot loop fits I took it apart a bit (took the back off, took out the battery sim and sd, and unscrewed the shell) and blew some compressed air all around the power button. It had been rebooting for about an hour at that point and then as soon as I put it back together it came up on the first try. So far so good.
So 1 year ago my J7 2016 (Exynos7870, J710MN variant) started having problems, the random reboot. So I installed a new ROM (HavocOS) and the problem seemed to go away but it didn't, after some time the intervals between the random reboots were gradually getting shorter so I flashed another ROM (BlackBird OS) and the interval between reboots was once again around 3 hours, but it still kept getting shorter. Now I installed the Klaxosaur ROM and after 19 days it was rebooting very frequently, like a reboot every 10 minutes, so I reinstalled Klaxosaur and the delay is longer again (still around 3 hours). Now, one important thing is that the reboots don't happen on recovery mode or when I'm playing games, I installed a Wake Lock app but it didn't seem to work (maybe it's because the APP didn't work but that might be the fix?) Please help! I'll soon get a new smartphone but I really love my J7.
Could be a sign of your battery dying.
ShaDisNX255 said:
Could be a sign of your battery dying.
Click to expand...
Click to collapse
I don't think it is because it works just fine on games (when CPU is being used) and I already got a new battery and this didn't change. Also if I let my phone stay on the recovery mode for 10 hours with the screen on it doesn't reboot...