So, Here's a little back story on my TB.
I've been rooted for over 1.5 yrs and have had no issues until this past month or so.
Running Froyo 2.2 on stock HTC. No ROMs.
Haven't changed anything and haven't loaded any games since I got my Nexus 7.
At work I leave the phone in the cradle on charge, especially when I try to use Wifi.
So the issue at hand.
It does not matter what app I use, OpenGarden, Camera, Video maybe a game or 2. Seems to be the more high end apps that cause the problem.
When I start these apps, not together, it will work for a while (on full battery) then the phone will shut down.
I'll restart and the battery will show as 1/8 to 1/5 charge.
I have changed batteries and it will still do the same shut down.
I haven't tried a restore or a re-root. Haven't touched in a long time and don't want to mess it up. I originally rooted the long method then went through the Revolutionary Easy Root and have been there ever since.
Any general ideas as to why these apps are sucking my battery dry? It is just a weird scenario and haven't found similar issues with a rooted phone.
Or should I take the plunge and get the Samsung Galaxy S III (and root with ICS)?
I really love the TB, but it is getting slow, especially compared to running apps on the Nexus 7.
Try updating to the latest ruu.
Sent from my ThunderBolt using Tapatalk 2
Thanks.
Can you point to the latest RUU and instructions?
http://www.androidpolice.com/2012/0...t-no-its-not-ics-but-it-does-fix-some-things/
Try this site. I don't know if it works or not.
Sent from my ThunderBolt using Tapatalk 2
Also can try cleaning battery terms and making sure they're all out and straight. When battery amp draw goes higher, I could see that causing the phone to freeze or reboot from amps/volts being too low. Just something to try before unrooting with an ruu...
Already checked the terminals. Happened with several batteries.
OK. So I noticed the anomalous shutdown recently and actually found what the problem was. I had installed Ninja Royale and Blood Brothers, but never actually ran them since I've been running them on my Nexus7.
On the N7 I was noticing short jumps to the start splash screen of these games during game play. So I decided to UnInstall them from the TB and now no longer have any random shutdowns or battery crunch and reboots.
Might be a combination of Froyo on the TB and a newer game, but this seems to have worked.
The N7 seems to be able to handle the load and the jumpi-ness of the splash screen and the battery holds up as well.
So, my fix was to uninstall Ninja Royale and Blood Brothers from the TB to fix the reboot issue.
I was having similar problems. Ended up replacing the battery.
Related
Alright, so this phone is becoming extremely frustrating.
The very first day i got the rezound I had it for literally five hours right from the store and I figured i would restart it to freshen things up after messing around with setting up my home screens.
Upon my phone turning back on, it booted up to the lockscreen... froze... turned itself on and then restarted itself and it LOOPS... it does NOT get past this point it bootloops the process
So I pulled the battery a few times, then did a factory reset in hboot and the problem fixed itself, so I gave it the benefit of the doubt and thought maybe it was just a fluke so i reset everything back up... now three days later... I restarted the phone... upon turning it back on... SAME THING... BOOTLOOPING for no reason
I have never tried to temp root my phone or do anything whatsoever. This is a 100% legit phone but its becoming extremely annoying. Im returning this thing to VZW tonight and exchanging it for another one but im torn between exchanging it for a different rezound or just straight up returning it and waiting for the nexus december 8th to come out.
There have been ALOT of reported problems with this phone from my bootlooping... dead pixels... horrible battery life... etc
Dont reboot it anymore. There is an app in the market called fast reboot.when you need to freshen the phone just push the icon and it wiill get all the free memory in about 10-15 seconds.
Sent from my Galaxy Tab 10.1
im supose to be locked into a phone for the next 2 years that i cant reboot because it bootloops?
I have seen several people with boot-looping issues.
I'm not one of them and I don't think it is rampant with this phone. As for dead pixels and horrible battery life - those issues are even fewer and far between.
I wouldn't say there have been ALOT; probably a normal percentage of definite defective units mixed with people being unfamiliar with "how things work" on a phone like this.
..... my $.02
yeah im returning it at VZW tonight for a new unit... if the second one has any issues at all that have been described on this forum so sorry i gave them two chances... returning and waiting for nexus
You also gotta realize your hearing about a ton of issues with the phone, because only people with issues are posting about it. The other 90% that dont have issues arent posting.
Anytime a new phone comes out about 10% of them are duds with the same problems you are describing. When the nexus comes out their forum will be full of threads about problems with that phone. Read thru the android forums and no matter what the phone, you will see complaints about the phone. i have been reading them for years.
Sent from my Galaxy Tab 10.1
I had the phone for about 7 hours three have been fighting loops. My temporary solution is to disable LTE and put my standard size battery in the device ? I don't know why, but I have a hunch that my specific device may be verry sensitive to heat issues.
I called Verizon and they show the boot cycling a known issue and that it was submitted to HTC.
The phone does not seem overly hot to Me so my hunch could be wrong
Sent from my ADR6425LVW using Tapatalk
Well my first Rez was a dud. It got as hot as 130F at one point! Returned it, now this second one will boot to a certain point then bootlop!! My evo never did this ****!!
Sent from my SCH-I510 using XDA App
Ok here's what I did. I shut down, removed the 4G sim and rebooted. It fully booted with no cell service of course. I went into the LTE switch and set it to CDMA auto. I shut down, re-inserted sim, booted up and it's working. Not sure if all that was necessary, but that's what I did...
Sent from my ADR6425LVW using Tapatalk
Ok phone getting better but loops still persist.I am giving up and getting a replacement in the am. BTW. THE tmo vibrant with stock headsets and voodoo sound 10 blows the beats gimmicks away.
Sent from my ADR6425LVW using Tapatalk
Bootloops = Heat
In my experience, Bootloops are a result of heat. The phone heats up (or the radio heats up), the phone reboots on the thermal warning, but the bootup time is not nearly long enough to cool down a phone that hot, so once the OS (or kernel) loads to the point where it starts checking for thermals, it sees a heat issue, and reboots.
I have this on my DInc which I was hoping to replace with a Rezound because of these bootloops, but of course I am going to have sit and see if this subsides (or what the Nexus people say) because ...
... you are right, you do NOT want a phone for 2 years which bootloops when you use it for 15 minutes. It is hell.
What is causing all the heat on your phone ??
Sent from my HTC
LTE 4G Rezound
deleted
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Hmmm i think mine has something like that. BUT i dont do it so much.
Had the same issue with mine last night. Removed Sim disabled all network services and replaced Sim and it worked when I enabled networks again. Mine has been set to cdma only also. I think it might be an issue when authenticating with Verizon that somehow crashes the phone.
chkn said:
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Click to expand...
Click to collapse
Let's hope that is the problem since I haven't had it and would hate to see it be a hardware problem. That is something that can be fixed with an update. I think phones are getting to thin for their own good. Cases problem don't help either.
For what it is worth, my phone is charging, streaming music, and I'm on the internet with auto brightness on. The temp is reading 100F. When I first got it, I was trying to kill the battery so I streamed Netflix over 4g and it got warm but never rebooted. Hope they figure this out for y'all.
Sent from my ADR6425LVW using Tapatalk
I got stuck bootlooping related to the fb chat widget. As soon as it would load, sense would restart and after 10-20 the phone started rebooting.
Non stop. I got it to boot with battery cover off (no reception).
Cover on, it would restart as soon as the lock screen was up.
Battery pull, no help.
So I did a battery pull, guessed volume down +power and choose factory reset.
No fb chat widget and no issues so far
Sent from my ADR6425LVW using XDA App
struggling radio = heat = reboot = still hot = reboot ...
Same as I currently have on my incredible.
They may be able to do something in software, but it is really hardware. the radio struggling to get a signal is not a software issue.
Sent from my ADR6300 using XDA App
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
baaj said:
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
Click to expand...
Click to collapse
thats odd. is it stock? if not, you should list everything you did to the phone. If you had it overclocked, maybe it overheated and shut down so as not to fry the chips?
Yeah, all's still stock. I've not even rooted yet.
Same thing happened to me with a skyrocket that I had. Except I did have it rooted running sky ics rom. And I had it plugged into the charger. So...maybe not quite the same thing...sorry. lol
I just went to the store and swapped it out for a new one. No questions asked within 30 days.
Sent from my SAMSUNG-SGH-I717 using xda premium
baaj said:
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
Click to expand...
Click to collapse
my note did the exact same thing yesterday or day befor,, i keep it in my locker at work , any how looked at it had over 50% battery life and when i came back a few hours later , it was dead , i got it to come on but battery was way way down , no life ,, dont know what the deal was ,, but has been running fine now.
i
Just happend to me, after testing out the mhl adapter at my parents place i restarted the phone. Then once all was booted up i put it to sleep to make the drive home only 15 min away i did notice the the phone was hot in my pocket but screen wasnt on. Pulled out my phone and it didnt turn on. I pluged in the the usb and it powered up normal.
Well its a new toy, they will have bugs and they will fix them. So far so good. I did get the juice defender app, seams to be.working.out.great went all day and still had 75% power when I got home.
tapatalk ~ Samsung galaxy note
My phone does get warm from time to time (on the back right below the camera lens), though I didn't notice it before the crash. Is this heat normal?
Only thing i did have is a random reboot once...thats about it.
Galaxy Note
My only odd experience is after unplayable Asphalt 6HD for a little while, and phone does get warm. After I close the game I get nothing. Blank screen and take a few minutes to come back to life and when it does it as if it went through a soft reboot.
Sent from my SAMSUNG-SGH-I717 using XDA App
UPDATE - problem has not gone away. It seems to be (at least partially) related to a malformed battery contact. Exchanging for a new one tomorrow.
I'm a light user throughout the day. Charged my phone to 100% before I left for work today. On my way home, I used my phone a lot. I visited websites that had a lot of content. I was pinching and zooming and the phone crashed/restarted on me. Same thing happen 10 minutes later. I was using the phone for about 20 minutes non stop prior to this to happening. The phone was in the upper 50s (56%-59%). The phone was getting noticeably warm on the back cover, but not to point where it was burning hot.
This doesn't happen to me during my lunch when I use the phone non-stop for a full hour. My phone is stock, not rooted. Had for about 1 1/2 week now.
My phone is a week old tomorrow. It is bone stockTmobile and has been having force close/ freeze issues. Nothing specific that I can recall doing at the time. I have a moderate amount of apps and games I play on it. When calling or just using in general it freezes which I then have to restart or pull the battery if completely frozen. I have wiped the phone and went back to factory setting. It seems to make no difference. What have you guys done to fix this issue?? A guy I work with has the exact same phone and his works flawless. I normally close the apps when done and I regularly clear the memory in the ram tab to help keep things running good. My S2 also started getting force close and freezing issues after updating to ICS. While I was waiting for Tmobile to warranty the S2 I bought the S3. Now have similar issues. Plus this phone seems to be blessed with wifi dropout issues, complete signal loss (comes back after restart), cant disable the led, and takes a screen shot on its own without having to push home + power. Just wait long enough and viola Nice phone but a little bigger screen, and a little faster processor. Starting to wonder if I should just take back and enjoy the S2 till something better comes out. Is it possible I just received a LEMON??
I recently rooted using odin, and all seemed to go well, much to my relief as this was my first attempt. After rooting I downloaded a bunch of apps (all from google play) ad free, uninstallers, root checker, wifi password finder,titanium....... oh, and noMoarPowah by Chainfire, which I'll get to in a sec. I uninstalled Swype, did Nandroid backup......... Anyway, I noticed the other day that I couldn't run any videos on my phone, not just youtube, but onesthat I'd taken myself. I hear sound but have a black screen. If I tilt the phone left or right, I see a brief flash of the video, then back to black screen again.
I've uninstalled all the apps I downloaded since rooting, but it hasn't made any difference. Could uininstalling Swype have caused this?
The last couple of days too I've noticed a huge increase in battery useage. I had to change batteries at midday the other day, which previously was unheard of, and within minutes of rebooting, the newly charged battery was down to 60% ish. I noticed something called mobi.mgeek.tunnybrowser was the culprit, which was linked to dolphin browser, so I unistalled that along with jetpack too, but it hasn't made a huge difference to my battery useage, so that needs further investigation.
On to NomoahPowah. I installed that 'cos it seemed like a bit of fun, only to find that it didn't work properly on my phone, apparently, it hasn't been updated for ICS. So I uninstalled it.......or so I thought! Upon plugging the charger in, up it came again, large as life. Couldn't find any mention of it on my phone tho, so, I installed it again and tried another uninstaller this time..........same result! Seems I can't get rid of the damn thing.......any suggestions, guys?
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.