Related
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
nemo.mareed said:
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
Click to expand...
Click to collapse
Is it rooted?
Sent from my VS910 4G using xda premium
Yes it is rooted. Is that a problem?
nemo.mareed said:
Yes it is rooted. Is that a problem?
Click to expand...
Click to collapse
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Haro912 said:
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
I just figured out the problem has to do with wifi. When I turn it off and use 3G instead the mobile becomes stable (so far). Is anyone facing the same problem or it's just me? Is there a fix?
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Haro912 said:
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Click to expand...
Click to collapse
No. But the frequency of the reboots increased after I re-installed the original MT stock ROM.
When I first bough the device it restarted once or twice a day. Now it reboots non stop unless I take out the battery. I re-installed the stock ROM from another source but the problem persisted. The problem goes away when I turn off wifi abut comes back when I turn it on.
Sounds like something to do with the kernel, not the ROM... maybe. I had horrible luck with any and all custom kernels for a long while. Although that's just my luck, might not be yours...
Looks like you had a problem from the beginning... Try everything stock, and if it's still there, return it... Wow my first post in years...
I know someone who had the same problem..
switched to the iPhone 4s...
Same here...
Me too...
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Problem solved!
kdevine said:
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Click to expand...
Click to collapse
Wohooooooooooooo The problem DOES go away with CM7 beta 8 !!!! It's like magic!
Phone no longer reboots randomly
Wifi is stable and does not disconnect or cause the phone to reboot or the battery to heat up
And battery life improved 300%!!! I now charge it every other day with moderate 3g/wifi usage!
I had CM7 for three weeks so far and my frustration turned into happiness! It's just amazing how changing the software makes a HUGE difference!! Before CM7 I always felt like smashing my MT because of the hard time it gave me!
I followed the instructions on: http://www.motorolatriumphhacks.com/
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
alcapone1130 said:
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
Click to expand...
Click to collapse
as far as ive seen with both cm7 and cm9, random reboots houldnt be an issue anymore, but for other still having the issue it usually comes from about 4 things over the rest
1. faulty hardware, which normally isnt the case, if faulty hardware was the issue you'd probly be seeing more then random reboots, but its still possible
2. Rom didn't take correctly during flash, either by chance, or because the phone wasent properly cleared and now settings are "head butting"
3. Running a custom rom in which you can adjust the cpu and the settings are either to low or to high, both can cause reboots
4. Most common one ive seen by far outta them all, Apps, certain apps especially after some updates will "play tricks" on the device and for some reason cause reboots sometimes, usually the next update of said app will resolve the issue but not always, so if you find an app thats the culprit you can notify that apps developer
you can always try and go back to 100% stock and see if the issue is still there but if your like me you probly hate the stock froyo by now lol
It may seem painful or whatnot but unless you find exactly what may be causing the reboots the best bet overall would be
Do a complete Fresh install of whatever rom you use, dont flash anything besides the rom and gapps if needed, also dont restore any backups yet, just to be sure
Once the fresh new rom is booted i turn the phone off then back on for safe measures lol
Now if you can lol try running the phone with No aftermarket apps besides any/if any that came on the rom, if the problem is gone you know for sure here that it was one of your apps
then 1 by 1 install your apps and give it some time in between app installs to see if the problem comes back and hopefully this way if it does youll know which app is causing troubles
FAQ
To quote directly from my FAQ,
"Reboots on Android are a pain, and can be attributed to multiple sources. I’ve been able to successfully reduce the amount of reboots that I get, but never eliminate them… Anyhow, here’s some troubleshooting information:
1. Format SD card in Windows (back up your SD card data first!) Make sure you format to FAT32. Don’t try formatting it in Linux. I have done this before and the phone wouldn’t boot up!
2. Slightly overclocking prevents some freezes.
Under Settings > Cyanogenmod Settings > Performance overclock the max speed to around 1300-1400ish. This should speed the phone up, but not to the point of the thing overheating
3. Fix SD Card permissions. Do this by booting into Recovery (You can do that if you have this ROM installed) and go to advanced > Fix SD card permissions. Now reboot.
4. Do not use Firefox, except the Nightly builds. Firefox has went through drastic speed and performance improvements recently, but the older builds, despite being called stable, are so slow, they will make the phone freeze and reboot. Yes, this includes Aurora. UPDATE: All Firefox versions except stable (ironic, eh?) have been used by me personally and have not made my phone reboot. Make sure you’re on at least version 14. (This one doesn't apply as much anymore, I need to update my FAQ!)
5. Give the phone a break from time to time. After intensive gaming for hours on end, the phone will often reboot while exiting a game.
That’s all the tips I have. I managed to drastically reduce my reboots by doing these, but not eliminate them completely. I hope g60madman or mantera find some hidden timeout value in the kernel (if one exists, like the auto reboot on BSOD in Windows) and either lengthens the timeout value or disables automatic rebooting so if this is a kernel panic, we may see the debugging details and upload them to fix some crashes.
6. Make sure that you have the VM heap size set to be adequate enough. I recommend at least 24 MB, preferably anywhere from 32 MB and up if you want the phone to last a while without rebooting.
7. Sometimes a cache wipe and dalvik cache wipe are needed to stop bootloops. Unfortunately, every once in a while, you may start getting bootloops. This usually due to some sort of corruption in the cache or dalvik cache. You can safely clear them through Clockworkmod Recovery without loosing any data, and this usually fixes the problem. If not, do a factory reset through Clockworkmod Recovery and reinstall this ROM."
I bought this phone from my local AT&T store on the day that it was released.
Since then I've had several issues with this model.
The one that I bought at the physical store would not go longer than 40 hours without locking up entirely, forcing me to reboot. I fought it for a long time thinking that it was an app I was using. By the time I determined that it was a hardware problem, I was past the warranty period and processed the phone as a warranty exchange.
The exchanged phone worked better but after a week the screen started to display as if it had no red (so everything had a green tinge to it). I actually had to fight support to get it replaced on time because the phone that I had already sent in wasn't done being processed. Also during this time my replacement did lock up once or twice but I didn't know whether that was just something random or whether it was a hardware problem.
The second exchanged phone does show better uptime but still I have had trouble going a few days without having to reboot due to lockups/sluggishness. AT&T has replaced my SIM card and I have since also figured out that my SD card wasn't working correctly.
I think that covers the background of my experience, but I wanted to share the following and get thoughts/comparison. I ordered a 32GB class 4 card and left the 8GB card out. While waiting for the new card to come in I noticed a huge difference in responsiveness and stability. This includes smoothness of transitions and uptime (having no SD card I went more than 100 hours of uptime for the first time since I purchased the phone).
After I installed the 32GB card, I have noticed that some of that smoothness and stability has gone away. It's not QUITE as bad as I remember from the 8GB card, but it's definitely not like it was. I also briefly experienced the "green screen" issue like on the prior replacement (thankfully, a reboot fixed it).
I'd like to put together some benchmark results. Could anyone here recommend good comprehensive benchmark software (beyond just CPU & memory tests)? Is anyone willing to perform similar benchmarks (one set with SD, another without SD)?
[[add]] I forgot to mention that the performance problems seem to get worse the longer that it's been since it was last booted. Which is part of the reason that it's taken me so long to troubleshoot, since I was convinced that it was some kind of memory leak. Also this phone has only run either stock, infusedv1, or infusedv2, behavior seems to the same regardless of whether it's stock or infused.
Wow, I've had none of those type of issues. Not at all! I've had a 32gb card from the day I bought it, transferred from my Captivate. Never seen any drop in performance.
Merlin8000 said:
I bought this phone from my local AT&T store on the day that it was released.
Since then I've had several issues with this model.
The one that I bought at the physical store would not go longer than 40 hours without locking up entirely, forcing me to reboot. I fought it for a long time thinking that it was an app I was using. By the time I determined that it was a hardware problem, I was past the warranty period and processed the phone as a warranty exchange.
The exchanged phone worked better but after a week the screen started to display as if it had no red (so everything had a green tinge to it). I actually had to fight support to get it replaced on time because the phone that I had already sent in wasn't done being processed. Also during this time my replacement did lock up once or twice but I didn't know whether that was just something random or whether it was a hardware problem.
The second exchanged phone does show better uptime but still I have had trouble going a few days without having to reboot due to lockups/sluggishness. AT&T has replaced my SIM card and I have since also figured out that my SD card wasn't working correctly.
I think that covers the background of my experience, but I wanted to share the following and get thoughts/comparison. I ordered a 32GB class 4 card and left the 8GB card out. While waiting for the new card to come in I noticed a huge difference in responsiveness and stability. This includes smoothness of transitions and uptime (having no SD card I went more than 100 hours of uptime for the first time since I purchased the phone).
After I installed the 32GB card, I have noticed that some of that smoothness and stability has gone away. It's not QUITE as bad as I remember from the 8GB card, but it's definitely not like it was. I also briefly experienced the "green screen" issue like on the prior replacement (thankfully, a reboot fixed it).
I'd like to put together some benchmark results. Could anyone here recommend good comprehensive benchmark software (beyond just CPU & memory tests)? Is anyone willing to perform similar benchmarks (one set with SD, another without SD)?
[[add]] I forgot to mention that the performance problems seem to get worse the longer that it's been since it was last booted. Which is part of the reason that it's taken me so long to troubleshoot, since I was convinced that it was some kind of memory leak. Also this phone has only run either stock, infusedv1, or infusedv2, behavior seems to the same regardless of whether it's stock or infused.
Click to expand...
Click to collapse
And you're running on stock rom? I experience the green screen you talked about, but also a red, blue, yellow, pinkish, beige type, and I'm sure other colors. Not joking, other people have experienced it too, there's a thread on it.
Sent from my SGH-I997
Jep56 said:
Wow, I've had none of those type of issues. Not at all! I've had a 32gb card from the day I bought it, transferred from my Captivate. Never seen any drop in performance.
Click to expand...
Click to collapse
Yeah I'd be willing to think that it was an app except that I've also had the same issue running vanilla stock with no apps installed or accounts linked (on the device that I bought from the store).
Would you be willing to do an experiment and see if you notice any performance benefit when your card is not installed?
http://forum.xda-developers.com/showthread.php?t=1417699
Thread about screen. But nobody knows why it happens.
Sent from my SGH-I997
jayson94538 said:
http://forum.xda-developers.com/showthread.php?t=1417699
Thread about screen. But nobody knows why it happens.
Sent from my SGH-I997
Click to expand...
Click to collapse
I experienced both the green screen and the performance problems on stock with my first replacement and was unable to fix it. It was warranty replaced as I had mentioned. From my experience in PC repair, it was exactly what I saw when I had a bent pin in my VGA monitor connector, so I presumed it to be hardware after returning to stock didn't fix it.
I've only seen the yellowish tint on my phone, happened 1 time and never again after that.
Sent from my SAMSUNG-SGH-I997 using xda premium
Merlin8000 said:
I experienced both the green screen and the performance problems on stock with my first replacement and was unable to fix it. It was warranty replaced as I had mentioned. From my experience in PC repair, it was exactly what I saw when I had a bent pin in my VGA monitor connector, so I presumed it to be hardware after returning to stock didn't fix it.
Click to expand...
Click to collapse
Performance became very good after flashing to a custom rom. You can really tell the difference from stock to custom.
Sent from my SGH-I997
jayson94538 said:
Performance became very good after flashing to a custom rom. You can really tell the difference from stock to custom.
Sent from my SGH-I997
Click to expand...
Click to collapse
I've been running infused v2 for quite some time. I've really only run stock when I aboslutely had to. I keep eyeing the CM & other ROMs but have been waiting for bluetooth to get fixed since I do use that regularly in the car.
Merlin8000 said:
I've been running infused v2 for quite some time. I've really only run stock when I aboslutely had to. I keep eyeing the CM & other ROMs but have been waiting for bluetooth to get fixed since I do use that regularly in the car.
Click to expand...
Click to collapse
Try Zeus.
--Mike
I was running miui but switched back to stock for the Bluetooth issue... I ran quadrant standard benchmark test before and after... I only hit 932 with stock rom and with miui I managed 3194 as my best number... I don't know how good quadrant is for benchmarking but even outside of the numbers it was way smoother and faster with miui... never experienced any of the negative things you have though
Sent from my SAMSUNG-SGH-I997R using Tapatalk
I'm running the stock ROM but rooted with CWM along with a PNY 32GB Class 10 microSDHC:
http://www3.pny.com/category_buymul...essionID=x23hT0xmzIlb6WhG1Iyu&Category_ID=460
I have not experienced any problems. Unless you're installing applications to it I don't see why the external SD card would cause slowdowns. I know the OS does use the internal "SD" storage space but not the external SD. Have you tried formatting it with the phone? Odd indeed...
secretasianman said:
I'm running the stock ROM but rooted with CWM along with a PNY 32GB Class 10 microSDHC:
-url-
I have not experienced any problems. Unless you're installing applications to it I don't see why the external SD card would cause slowdowns. I know the OS does use the internal "SD" storage space but not the external SD. Have you tried formatting it with the phone? Odd indeed...
Click to expand...
Click to collapse
I can't say that I've tried that, I do have all my apps installed on my internal card, in fact since I got the internal card, I've been able to move all my media file locations to the external SD, making sure that I have room for my apps on the phone.
I had considered a class 10 but from what I read, there's no advantage between a class 10 and a class 4 due to the apparent bus speed limitations.
I'm still hoping to see if anyone saw a performance benefit from not having their SD card installed.
I'm willing to give formatting it a try if my problems continue, but that will probably be in the same effort as moving to a new ROM. Bluetooth is rather important to me as I've stated but if Zeus has it working I'm willing to have a look one weekend soon.
Thanks for the input.
I have had nothing but problems with this phone. It was my first Android device and it will be my last. I had an iPhone ever since the first one came out about 4 years I guess. I never had a single problem with it. Never not once.
When I first bought this phone I loved it. And it stayed that way for about a month. After the first month things started going downhill quick. The phone started freezing up and I thought I had to many apps running so I started killing the ones I weren't using. Well it stopped freezing as much then it started resetting itself at least 3 times a day. I was on the phone to get an exchange and I dropped the phone and cracked the screen. I didn't get insurance and had a case ordered. It came in the mail the next day.
wyattjo said:
I was running miui but switched back to stock for the Bluetooth issue... I ran quadrant standard benchmark test before and after... I only hit 932 with stock rom and with miui I managed 3194 as my best number... I don't know how good quadrant is for benchmarking but even outside of the numbers it was way smoother and faster with miui... never experienced any of the negative things you have though
Sent from my SAMSUNG-SGH-I997R using Tapatalk
Click to expand...
Click to collapse
Same thing here: Tried Zeus and MIUI, both are excellent roms (MIUI in particular surprised me), and both benchmark way faster than my stock Rogers Gingerbread rom...but outside of that they don't really offer much more in terms of everyday use, stock rom isn't any more bloated, and it runs just as smooth. Battery life is about the same too in my experience, so I just went back to stock Rogers ROM.
So I've switched to Zeus, and while I've got to say it's a noticeably better experience than Infused, I'm still having stability problems. I'm unable to keep this thing going for more than 2-3 days without a complete lockup.
I'm just not sure what's going on here. To reference my original post, I feel that it's disk-related (just from the way that the device behaves in general).
One thing that I've noticed is that under LogViewer, I see frequent occurrences of this:
listenToSocket -> Communications error
java.io.IOException: No such file or directory
at android.net.LocalSocketImpl.connectLocal(Native Method)
at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
at android.net.LocalSocket.connect(LocalSocket.java:98)
at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:102)
at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:85)
at java.lang.Thread.run(Thread.java:1019)
Error in NativeDaemonConnector
java.io.IOException: No such file or directory
at android.net.LocalSocketImpl.connectLocal(Native Method)
at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
at android.net.LocalSocket.connect(LocalSocket.java:98)
at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:102)
at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:85)
at java.lang.Thread.run(Thread.java:1019)
Can anyone tell me if that's normal?
MobileData said:
Try Zeus.
--Mike
Click to expand...
Click to collapse
Merlin8000 said:
So I've switched to Zeus, and while I've got to say it's a noticeably better experience than Infused, I'm still having stability problems. I'm unable to keep this thing going for more than 2-3 days without a complete lockup.
I'm just not sure what's going on here. To reference my original post, I feel that it's disk-related (just from the way that the device behaves in general).
One thing that I've noticed is that under LogViewer, I see frequent occurrences of this:
listenToSocket -> Communications error
java.io.IOException: No such file or directory
at android.net.LocalSocketImpl.connectLocal(Native Method)
at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
at android.net.LocalSocket.connect(LocalSocket.java:98)
at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:102)
at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:85)
at java.lang.Thread.run(Thread.java:1019)
Error in NativeDaemonConnector
java.io.IOException: No such file or directory
at android.net.LocalSocketImpl.connectLocal(Native Method)
at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
at android.net.LocalSocket.connect(LocalSocket.java:98)
at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:102)
at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:85)
at java.lang.Thread.run(Thread.java:1019)
Can anyone tell me if that's normal?
Click to expand...
Click to collapse
not normal.
Merlin, back up your contacts to google. Save your pics.
Take out your microsd.
factory reset from in the phone /setting/privacy.
use this:
http://forum.xda-developers.com/showthread.php?t=1331381
read carefully
then flash zeus.
your prev flash is prob bad
I honestly don't have the patience or time for that today, but perhaps this weekend.
Note: This will be the second time in a row that I've done this. I went through heimdall back to stock weekend before last:
http://forum.xda-developers.com/showthread.php?p=22173536#post22173536
qkster said:
not normal.
Merlin, back up your contacts to google. Save your pics.
Take out your microsd.
factory reset from in the phone /setting/privacy.
use this:
http://forum.xda-developers.com/showthread.php?t=1331381
read carefully
then flash zeus.
your prev flash is prob bad
Click to expand...
Click to collapse
You mentioned backing up to Google. I actually use my personal zimbra server for contacts so that's not a concern, but you bring up an interesting thought.
Is titanium backup known to be harmful? I've been using it to backup/restore app data ONLY (in other words i install the app from market/amzn then restore data to the app and manually set the system settings) after flashing anything that's been rooted.
qkster said:
not normal.
Merlin, back up your contacts to google. Save your pics.
Take out your microsd.
factory reset from in the phone /setting/privacy.
use this:
http://forum.xda-developers.com/showthread.php?t=1331381
read carefully
then flash zeus.
your prev flash is prob bad
Click to expand...
Click to collapse
Merlin8000 said:
You mentioned backing up to Google. I actually use my personal zimbra server for contacts so that's not a concern, but you bring up an interesting thought.
Is titanium backup known to be harmful? I've been using it to backup/restore app data ONLY (in other words i install the app from market/amzn then restore data to the app and manually set the system settings) after flashing anything that's been rooted.
Click to expand...
Click to collapse
That's a bad thing.
Occasionally, after flashing a rom, while restoring apps with tibu, strange things like app fc's or apps disappearing -greyed out or soft boot.
I assumed that it is due to corrupt tibu or back up.
I would reflash the rom after thorough wipes and download new apps and new tibu.
I NEVER restore data with the app. That's just asking for trouble. The stored data is on a different system.
Just the fact that you've restored data in itself, is prolly your problem.
I've assumed that restoring data is such an obvious NO-NO, that everyone who flashes a custom rom would be aware.
idk..i could be wrong, and it can be done, but I don't restore data...only google contacts
I've seen similar recm...restore apps..NO data
As of a few days ago, my inspire has learned a new trick.
but before I explain what is going on, heres the situation im in.
Ive Been running Icecoldsandwich for about a month now with some random UI/hot reboots here and there which is to be expected, no big deal.
however as of about 3 days ago, my inspire started to fully reboot from the white HTC screen, Werid, but **** happens so i ignored it.
Now it is doing this about every half hour,no matter what, i dont even have to touch the damn thing and it does this. Im Beginning to think its a hardware issue.
Heres what Ive tried so far
-battery pull (nothing)
-was using BLN which uses more power in standby so i upped voltages a bit (nothing)
-disabled BLN (nothing)
-disabled/enabled start up tweaks (getting desperate)
- restored an old backup of black ice which never had this issue ( STILL REBOOTED WTFF)
-some other stuff that i cant remember
Now i have an PD98IMG.zip on my sd card which was made when i originally rooted my phone and am about to restore that, but I have a feeling that wont help.
The only thing i can think of is that its a hardware issue, because after restoring that backup this issue shouldve disappeared and Im really at my wits end. SO before i throw the damn thing across the room and smash it, can anyone PLEASE help me out.
Im not new to the whole rooting game so dont treat me like a noob, ive been messing with this phone for a while now and this is the first time ive had an issue like this, which seriously appeared out of nowhere for no reason. Ive been on Ice cold sandwich for over a month now and this just started.
Thanks for any help/advice, If anyone has encountered this issue please contact me
PS: sorry to make a thread about this but ive searched both inspire &desire hd forums and came up empty handed.
You didn't mention anything about your micro sd card. Will it boot without the card inserted or using a different card freshly formatted? Corrupt cards or cards that are almost full can cause hair pulling issues.
Hmmmmm. That's a very good point you bring up there. My cards got over a gig left on it but hasn't been formatted since I rooted the phone.
I suppose I'll try that though since im out of options.
since I had to make it a "goldcard" will there be anything I need to do after I format it to make it work correctly?
Sent from my Desire HD using Tapatalk
Also, it does boot without an SD card, I'll see if it turns off with it out
Sent from my Desire HD using Tapatalk
Does not matter if it is a gold card. Will not affect anything. If your phone does not reboot with the card out then most likely it is going bad, has corrupt files, has apps or widgets moved to it that really should have been left on the phone. Or you used a backup app to restore system files that may be causing issues.
If having the card out allows your phone to run without reboots I would format that card, wipe that phone, reinstall a ROM and start clean and fresh.
This behavior could also be caused by a bad battery. Are you still using the original? A lot of them were pretty crappy.
well It still reboots with no sd card in it so I suppose it isn't that.
As for the battery, it is the original and that would make a lot of sense cause I leave it on the charger a lot.
my sister has the same phone so ill have to swap batteries and see if that makes a difference
thanks for the advice guys, I'm months from an upgrade so I really need to get to the bottom of this.
Sent from my Desire HD using Tapatalk
If it does turn out to be the battery, I would recommend an Anker brand replacement. They are pretty good and cheaper than the Seidio ones.
well I can rule out the battery cause I switched them and it continues to reboot.
I'm beginning to think it's the radio because it doesn't seem to reboot in airplane mode and it seems to reboot more when I'm driving, perhaps when switching towers.
I'll experiment with a few different ones and see what I get
Sent from my Desire HD using Tapatalk
okay everyone well its been some time now & I am still dealing with the same BS.
It has recently come to my attention that im not the only one dealing with this problem so I want to refresh this thread & perhaps get some new advice & options.
heres where I stand:
ive tried everything from roms-radios-batteries - everything in between. adjusted voltages, & every single setting available.
What ive found so far is that this issue is almost definitely signal related, when in airplane mode my phone Does not reboot.
ive also been advised that removing the sim card stops the reboots as well.
ALSO, I turned off 3g/4G for a few hours with only 1 reboot.
however I feel that was due to a different reason cause normally my phone reboots at least once every hour if not more.
im losing my mind & am about to smash this POS if I cant figure something out.
Is it possible its ATT related?
Should I return to stock? (unroot) -(really wanna avoid that)
WTFF. please, someone help! im going nuts!
Again any advice would Def be appreciated, & if anyone else has this problem please chime in & state your position.
sorry for the long post, (trying to be thorough)
& Thanks in advance
Sent from my Desire HD using Tapatalk
I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
djfourmoney said:
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
Click to expand...
Click to collapse
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
qkster said:
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
Click to expand...
Click to collapse
I mentioned that in the post, I did it while in Mexico City. It worked fine until this week, late last week. The battery only gives me about 5 hours now with just 32% audio playback and about 10% web access.
I guess I'll order a Anker battery from Amazon.
I rooted the phone again last night but before I did that, the phone became unresponsive three times in an hour. Which microSD card are you talking about? I just bought a 32GB Class 6 card and that works fine, I play all my audio from it, no problems.
If you mean the internal microSD card, that could be possible. I assume I can crack open the phone and replace this easily?
I should mention it never does that while plugged into a power source, so maybe this is all battery related.
Possible Fix...
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
djfourmoney said:
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
Click to expand...
Click to collapse
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
qkster said:
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
Click to expand...
Click to collapse
Thus far, that issue has not returned. Yes the battery holds a charge, but last only about 5-6 hours now, not 7-8 hours.
It seems it was a minor software issue. I did a factory reset, you keep missing that.
I did it in Mexico City (7 days ago).... Since that point and returning to the US, I have put my apps back on the phone. I had already updated to Gingerbread and it just reset to that.
I won't know more until I am out and about with my phone. I will be watching various auto racing events and don't plan on leaving the house this weekend.
Aussie V8's at COTA
NASCAR All Star Race @ Charlotte
World Challenge @ COTA
ELMS @ Imola
DTM @ Brands Hatch
WTCC @ Sazburg
Nurburgring 24 Sunday-Monday
elbscorp said:
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
Click to expand...
Click to collapse
No problem, I've never had a problem with TB. I updated the rom to a rooted version of the AT&T Gingerbread release so I could even use it... lol
The phone was rooted for Froyo, I downloaded the AT&T Gingerbread from Samsung via Kies when it was released and it remained rooted.
But resetting it back to stock, TB didn't work until I put the rooted rom on the phone.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
elbscorp said:
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
elbscorp said:
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Well like this, I will not go into the details but somebody else put Swipe Lock on the phone and of course I didn't know what he put into the phone. I was trying to resolve data issue on TelCel.
I had to do a hard reset outside of the operating system. Since the ROM was already upgraded to Gingerbread but unrooted, it went back to its unrooted state meaning I couldn't use TB.
So I re-downloaded apps from my memory. All of them are free so it wasn't an issue, just time consuming.
qkster said:
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
Click to expand...
Click to collapse
See above.
I used download mode to get out of Swipe Lock. I never used Swipe Lock, a-hole wanted to charge me 120 pesos ($7) to wipe it and put it back to stock, I wasn't going to do it, I know enough about Android phones to do it myself.
Oh well, lesson learned, I believe wiping the cashe from TwLauncher has solved the problem.
I did re-install all the apps from the store. I wasn't able to use TB until Thurs night (5/16). I noticed the errors Friday afternoon, wipe the cashe and no issues since.