I've done this several times without any sort of problems, but I'm wondering what is the general consensus.
While I'm at it, would the inspire mod/possible inspire fix work with gb miui? Theres one that is .5mb and another one that is 5mb...
Sent from a dream.
Phone's do not charge while being flashed. You should always charge your phone before flashing. There should be no reason to charge while flashing.
Agoattamer said:
Phone's do not charge while being flashed. You should always charge your phone before flashing. There should be no reason to charge while flashing.
Click to expand...
Click to collapse
True, but also I don't think being plugged in while flashing is going to hurt anything.
Actually, I use 4EXT recovery, and mine absolutely does charge while flashing...I always make sure there is at least 50 percent charge in it when I do flash a new ROM, but it DOES charge anyway. I know it's a feature of 4EXT and not all recoveries are the same....just wanted to add my .02
I have had mine plugged in basically every time I have flashed a new ROM for the last three months or so (and given my addiction that's been a lot!!) and no harm or oddness has come of it whatsoever.
Mikatana said:
Actually, I use 4EXT recovery, and mine absolutely does charge while flashing...I always make sure there is at least 50 percent charge in it when I do flash a new ROM, but it DOES charge anyway. I know it's a feature of 4EXT and not all recoveries are the same....just wanted to add my .02
I have had mine plugged in basically every time I have flashed a new ROM for the last three months or so (and given my addiction that's been a lot!!) and no harm or oddness has come of it whatsoever.
Click to expand...
Click to collapse
I hate to say this but it will not charge while during the flashing process as the USB connection is disabled due to the drivers being deleted and reinstalled. While this may work It could cause issues. Most likely very rare but the chance is there like all flashing.
"The [led] lights are on, but no one is home" type thing
Sent from my Inspire 4G using xda premium
zelendel said:
I hate to say this but it will not charge while during the flashing process as the USB connection is disabled due to the drivers being deleted and reinstalled. While this may work It could cause issues. Most likely very rare but the chance is there like all flashing.
Click to expand...
Click to collapse
I just tried and while it was flashing icecoldsandwich, it was at exactly 50% when I hit "install" and halfway through the flash it went up one percent...so it does infect charge...but like you said since the drivers are being removed and such...it could over heat or something and since all the safety features are disabled that us a possibility
Sent from my Inspire 4G using XDA
I don't know if it works but I always am charging while flashing... maybe it just makes me feel safer. But yeah the inspire mod did help me with the sound on MIUI when I tried it.
trh1341 said:
I just tried and while it was flashing icecoldsandwich, it was at exactly 50% when I hit "install" and halfway through the flash it went up one percent...so it does infect charge...but like you said since the drivers are being removed and such...it could over heat or something and since all the safety features are disabled that us a possibility
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
This is exactly my experience with having it plugged in while I flash a new ROM. I have also watched the battery charge keep going up while in recovery.
4EXT does allow off-mode charging and USB connections while in recovery, so I am guessing that the drivers in question are actually part of the recovery, not the ROM, so it still does it's thing....?
seriously arguing over whether or not the phone is charging during a 10second flashing process? It likely severs the connection at some point but not for long as it was stated with loading new drivers. if your phone is low enough that you are concerned about this, charge it first. Mine is never connected during a flash, too much chance to wiggle the cable and bounce the connection thus causing problems.
I would say no I would charge the phone up before flashing your phone just to be on the safe side last thing you want is your phone dieing in the middle of a flash
Sent from my Desire HD using xda premium
What about flashing a rom via CWM while charging??? is it safe?, I Assume "The flashing" discussed here is using the flashtool or someting..,and not the one that use CWM..,
Related
Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.
dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App
i too am sticking it through, im too in love with this to revert back.
yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.
I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F
I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.
i reverted back last night but i will def be back once things are more stable.. i already miss it
So I've had the phone for about 3 weeks now and never had the restarting problem but now it's done it twice in the past 24 hours. Anyone know why it's doing it and how to fix it?
no one???? it's done it more again
hockeybpr25 said:
no one???? it's done it more again
Click to expand...
Click to collapse
need details what rom/kernel are you using? or is it completely stock? whats running when it restarts if anything? check new apps maybe one is being screwy
blazing through on my VZ Droid Charge
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
hmm if its completely stock I couldn't say why, but maybe someone with more experience than me could chime in... as for a fix, perhaps if you backed everything up first, then a factory reset might do the trick
blazing through on my VZ Droid Charge
hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
I'd look at any apps you recently installed. My Fascinate would reboot quite a bit at times for no reason, it could be a Samsung glitch.
What I tell my customers to do is;
-check that there isn't any software updates
-pull the battery and wait 30 sec. I know it is the generic answer but it fixes most problems, it just like a computer if it not working right, restart. (Laptops mainly in pulling the battery.)
-or factory/data reset. It often will fix the issue but there are the few cases where it will not solve the problem. (and you will lose all of your stuff on your phone, contacts are backed up by Google or backup asst.)
-lastly, root it!!! no problems on my GummyCharged, v1.5, 2.3.4 (I don't tell my customer this choice)
Yeah I'm going to root soon. I just keep on reading these forums everyday so I can hopefully prepare for rooting with no issues.
Sent from my SCH-I510 using XDA Premium App
Hi guys. I am s off and on a custom-made rom. My phone charges fine with power off or on. But read about the problem when power is off cause off 100 % dead battery. Is it confirmed that any and if so which one charges phone with dead battery ? Thanks in advance.
What.......
bs android said:
Hi guys. I am s off and on a custom-made rom. My phone charges fine with power off or on. But read about the problem when power is off cause off 100 % dead battery. Is it confirmed that any and if so which one charges phone with dead battery ? Thanks in advance.
Click to expand...
Click to collapse
I keep reading you want 4.0.1.4 with blue text... I have to say I'm a bit surprised not to see more discussions about this.. a stable/working recovery seems like a pretty important thing and its not clear to me that we are 100% there yet...
I'm also surprised there aren't more discussions on this. My battery died and it was a real ***** to get working again.
This is pretty important.
Sent from my HTC Sensation Z710e using XDA App
The version you want is the second 4.0.1.4. Confusing I know but 4.0.1.5 has the charging bug and instead of releasing 4.0.1.6 with a fix someone had the bright idea of going back to a modified 4.0.1.4.
Jutt69 said:
The version you want is the second 4.0.1.4. Confusing I know but 4.0.1.5 has the charging bug and instead of releasing 4.0.1.6 with a fix someone had the bright idea of going back to a modified 4.0.1.4.
Click to expand...
Click to collapse
And the problem is if you use ROM manager which thinks 4.0.1.5 is the latest when it's actually 4.0.1.4 second edition (blue text) you need.
chrisw99 said:
And the problem is if you use ROM manager which thinks 4.0.1.5 is the latest when it's actually 4.0.1.4 second edition (blue text) you need.
Click to expand...
Click to collapse
Agreed. ROM Manager is best ignored at the moment.
i Had 4.015 charge light came on when charge power off but it was false charge, confirmed with adb, updated with 4.014 with blue text. Charging with power off.
Sent from my HTC Sensation 4G using XDA App
I have 4.0.1.5 and mine charges without problems when power is either on or off. Bit i dont know if it charges with dead battery. As i understand the new modified 4.0.1.4 charges dead batteries also ??
Again thanks in advance.... Hope for some answers
I can confirm the new 4.0.1.4 does not charge with the battery dead. However, I've found that some can, some can't. I'm currently on 4.0.1.5 and until I get an alternate charging source I'm not letting the battery die.
I'm on revised 4.0.1.4 and can charge while off, I couldn't while on 4.0.1.5. Haven't let my battery die so can't comment on that, but I guess it's best not to risk it which ever your using!
Sent from my HTC Sensation Z710e using XDA App
Hi!
Strange behavior on my Sensation.
I have installed ARH 1.1.8 (I was back to stock rom due to issues with 1.1.7). I have also installed the CWM 4.0.1.4 Recovery (blue text with Revolutionary logo).
In the Power settings, I unchecked FastBoot.
If I turn off the sensation and plug the wall charger, the battery doesn't charge (led is off) and I can't start the Sensation without first removing the battery...
Then I have flashed the stock recovery, turn off the sensation, plug the wall charger, the led is on during 3 seconds then shut down and again I can't start the Sensation without first removing the battery.
Now I have re-flashed CWM 4.0.1.4 Recovery and re-checked FastBoot in the Power settings and it charges normally...
Do I use the bad version of the CWM recovery? Why doesn't it work with the stock recovery (it did with the stock rom)?
Could it be related to the rom?
Thanks in advance for your help!
NB: Sorry for crossposting but I haven't received any answer in the other posts for the moment...
I had similar problem. I followed guide to debrand and stay s-off. Then I followed the guide for root and super cid to flash 4.0.1.4 updated and then leedroid
zim2dive said:
I keep reading you want 4.0.1.4 with blue text... I have to say I'm a bit surprised not to see more discussions about this.. a stable/working recovery seems like a pretty important thing and its not clear to me that we are 100% there yet...
Click to expand...
Click to collapse
I agree that the charging issue and different version numbers are problems. But they are serious inconveniences at most. The safety of our devices is not at risk.
Sent from my HTC Sensation Z710e using XDA Premium App
moto211 said:
I agree that the charging issue and different version numbers are problems. But they are serious inconveniences at most. The safety of our devices is not at risk.
Click to expand...
Click to collapse
??? I was reading some reports of guys having to "jump start" from a battery wired in to USB after having the battery run all the way down??
I dunno, this seems like a rather fundamental issue...
granted it seems like most ppl seem to be getting along just fine.. I'm just not sure I'm ready to be one of the ones who don't
zim2dive said:
??? I was reading some reports of guys having to "jump start" from a battery wired in to USB after having the battery run all the way down??
I dunno, this seems like a rather fundamental issue...
granted it seems like most ppl seem to be getting along just fine.. I'm just not sure I'm ready to be one of the ones who don't
Click to expand...
Click to collapse
I was one of the people who jump started their battery. A serious inconvenience for sure. But at no time was there a risk of ending up with a bricked device.
Sent from my HTC Sensation Z710e using XDA Premium App
After booting with the *fixed* charging issue, I opened up ROM Manager and was prompted to update to the latest version. 5.0.0.10 I believe.
**********DO NOT DO THIS UPDATE AS IT WILL KILL CHARGING**************
I only escaped because I had a spare battery from my previous Sensation that luckily had enough charge left to turn on the device.
************DO NOT UPDATE UNLESS THE DEVS SAY SO***********
You may lose the ability to charge your phone! Meaning - if it dies, the phone is dead. End of the line. The only reason I could bring my own phone back was because I had another Sensation battery that fortunately had enough juice to boot up and for me to flash the image here: http://forum.xda-developers.com/showthread.php?t=1192300
Do not make the same mistake I did or you risk a **************************************BRICK*********************************
Please do not do any updates !!!!! Koush or not, the charging issue is a very REAL threat! I tried everything and if I did not have a spare battery, I would be completely screwed right now!
i did that, and i have NO PROBLENS ...
strange
and even if you were right.. it woulndt be a brick.. there is always this option:
solution
I've had the newest version from Rom Manager for awhile now, and it works fine. Charges while off and everything. We've already got discussions on the new CWR in http://forum.xda-developers.com/showthread.php?t=1242522 and http://forum.xda-developers.com/showthread.php?t=1242942
No problems here either
I updated to v5.0.1.0 and got no problems with it. I got 3 battieries so no worries! You wont brick your phone either if you run out of juice, theres a micky mouse way to "jump starting" your dead battery posted above. You guys should really invest $15 for an external charger and anker battery from ebay. The investment is so little for piece of mind.
EtherealRemnant said:
After booting with the *fixed* charging issue, I opened up ROM Manager and was prompted to update to the latest version. 5.0.0.10 I believe.
**********DO NOT DO THIS UPDATE AS IT WILL KILL CHARGING**************
I only escaped because I had a spare battery from my previous Sensation that luckily had enough charge left to turn on the device.
************DO NOT UPDATE UNLESS THE DEVS SAY SO***********
You may lose the ability to charge your phone! Meaning - if it dies, the phone is dead. End of the line. The only reason I could bring my own phone back was because I had another Sensation battery that fortunately had enough juice to boot up and for me to flash the image here: http://forum.xda-developers.com/showthread.php?t=1192300
Do not make the same mistake I did or you risk a **************************************BRICK*********************************
Please do not do any updates !!!!! Koush or not, the charging issue is a very REAL threat! I tried everything and if I did not have a spare battery, I would be completely screwed right now!
Click to expand...
Click to collapse
No issues here either.
I think you, sir, need to get yourself a new charger
External charger? Since when would a dead battery = a brick? It's not an iPhone with internal battery that can't be removed.
You aren't even on the latest version of CWM. 5.0.1.0 is the latest and 100% stable.
Please change the thread name to something not as scary, specially when you are the only person that has that kind of issues.
Updated yesterday, charged last night with no problems.
Sent from my HTC Sensation Z710e using xda premium
Dude this is old news. I learnt the hard way. The newest version of cwm works great
Sent from my HTC Sensation 4G using XDA App
Mod needs to delete this thread.
BlackElvis79 said:
Updated yesterday, charged last night with no problems.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Some for me, yesterday update today charching...
Works great, it's ok also battery calibration...
lollo1927 said:
Some for me, yesterday update today charching...
Works great, it's ok also battery calibration...
Click to expand...
Click to collapse
I did today morning and no any trouble!
If you have some new in your phone pls charge your phone to 100% and keep on charger after you must make battery wipe across cwm your phone will work perfectly! My advise if something went wrong search the mistake inside yourself!
Sent from my HTC Sensation Z710e using XDA Premium App
I have always been afraid of upgrading after the last fiasco. I remember the problem occurred when you uncheck fastboot. But when fastboot was unchecked the phone would not charge. Knowing that fastboot is default on many ROMs, are you guys sure the issue has been resolved in the update? Did you try checking to see charging was happening when you actually uncheck the fastboot?
BlackVision said:
Well it works when when fastboot is checked. Meaning the phone actually is not off. But does the update allow charging when you uncheck fastboot?
Click to expand...
Click to collapse
Yes. To prove to yourself, pull battery put back hook up to computer and...
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
result is "charging"
bml5631 said:
Yes. To prove to yourself, pull battery put back hook up to computer and...
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
result is "charging"
Click to expand...
Click to collapse
You right the devs make for us the best!
Sent from my HTC Sensation Z710e using XDA Premium App
good here
I updated and charging is fine.
Same here no problem at all!
YOU NEED TO CHANGE THE TREAD TITLE
Hi my name is DloBrown and Im A nightly addict i've been sober for 1 month now ='(
vladnosferatu said:
i did that, and i have NO PROBLENS ...
strange
Click to expand...
Click to collapse
+1 I updated to 5.0.1 as well and have no charging issue.
A very good day to everyone.
I have been using my HTC Sensation for a year and a half already and recently it's starting to crank up.
It started last week when I was using my phone when suddenly it just switched off by itself and no matter how I attempted to switch it back on again it would boot up to the lock screen page and baam, it shuts off again. It doesn't restarts by itself or anything, it just simply switches off and no, I am unable to switch it on again. The only time I am able to do so again is when I plug it into a power source, that is when it would finally be able to start up.
At first I thought that it wasn't something big until recently it started occuring more frequently and I noticed that it only occurs whenever I have my 3G switched on. If I'm plugged in, my phone would still be working without switching off even though I have my 3G switched on. But when I unplug it from its power source, I'll be able to use it with 3G on for a good 20-30mins or even lesser at times and there it goes shutting off by itself again. What actually got me dumbfounded is how I can be having 80% of battery power when this happens.
I have tried the using a card/paper as a wedge for the battery so that it connects better but to no avail even though I have noticed that indeed, my battery seems to have some extra allowance for it to fidget about within the confinements of the spot which is allocated for the battery. I have tried the switching the phone's data usage to GSM only as well as switching it to WCDMA only but both still didn't work. I have also done a factory wipe which didn't work, super wiped it before flashing ARHD once again which didn't work as well.
To make things worse, my phone is not covered under warranty anymore and my only last hope is that the problem lies with my phone's battery rather than the PCB board which is why I'm putting all my hope on the Anker battery which stocks would only come in next Monday which I don't wanna spend on only to find out that it's not gonna be able to save my phone from its miserable plight...
This is my phone's setup:
Android Version 4.0.3
Sense Version 3.6
Software Number - Android Revolution HD 6.8.0 XE by mik1986
Kernel Version - 3.0.16-g31a4fc7 [email protected] #1 SMP PREEMPT
Baseband Version - 11.76A.3504.00P_11.24A.3504.31_M
I'm really desperate to find a solution to this so if there's anyone of you who has faced this issue/solved this issue please enlighten me as to what I can do, any/all help would be greatly appreciated.
Try other Roms..yrs might be unstable...
Sent from my HTC Sensation XE with Beats using xda-titanium app
I've tried other ROMS already but it still force shuts itself whenever my phone's 3G is switched on. Any solutions?
seems like a radio problem ..reflash the firmware you are having or ..flash 3.33/3.32 universal firmware from kohr-ah firmware thread in sensation development section
once done ..get getril app ..open it and flash proper ril for the firmware if you not having matching ril
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Sorrowed said:
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Click to expand...
Click to collapse
Reflash it and see ...
Sent from my Nexus 7 using xda premium
ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack. Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried reflashing the 3.33 firmware but it keeps telling me that the installation has been aborted.
Skipjacks said:
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
Click to expand...
Click to collapse
I've tried this method of yours as well but apparently it tells me the same thing when I try to flash the firmware. "Installation aborted" and I don't know why is this happening...
stanix.de said:
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
Click to expand...
Click to collapse
I've found a seller over here in my country who I'm going to be meeting tomorrow and finally test it out as to whether has it been my battery's problem or is it just my hardware being faulty. Will test it out and let you know of the end results, thanks mate!
android1234567 said:
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: LumberJack(Had to change due to my account lacking the minimum requirement of 10 posts before I can post a link) Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
Click to expand...
Click to collapse
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Sorrowed said:
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Click to expand...
Click to collapse
No, it would not.
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Sorrowed said:
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Click to expand...
Click to collapse
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
Definitely! Thank goodness it was just the battery otherwise there goes a great phone. Not to mention that with the anker battery it has a greater and better lifespan!
TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
My situation is identical to yours. 1,5 years old, constantly rebooting, after reboot the battery power drops to 4%. If it's connected to the power cord it works normally. Already ordered Anker battery and I'll see what happens.
If I look closely, I can see that my battery is a little bloated and not completely flat. Did anybody else noticed that?
So I guess all of this should be written on HTC Sensation FAQ page since it's not a bug, but a feature...