Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
To avoid hijacking anyone else's JB battery issues thread, i'll make my own.
First, a bit of back story. I installed the factory JB image (9020A) via fastboot to try and track down why I've been getting abysmal battery life and decided to do a little experiment. I turned on airplane mode, and let my phone sit, undisturbed for a couple hours. When I checked it, it had lost something to the effect of 10% battery life per hour while doing nothing in airplane mode! I forgot to get a Better Battery Stats dump, so I'm going to repeat the experiment, this time in safe mode then get share my dump.
After that long winded explanation, let's to the actual (obvious) question: Why is my battery dying so fast? And, could a hardware malfunction cause something in the OS to keep a wakelock (i.e. would a warranty replacement help)?
Thanks in advance to anyone who decides to try and help tackle this nonsense.
beovvulf said:
To avoid hijacking anyone else's JB battery issues thread, i'll make my own.
First, a bit of back story. I installed the factory JB image (9020A) via fastboot to try and track down why I've been getting abysmal battery life and decided to do a little experiment. I turned on airplane mode, and let my phone sit, undisturbed for a couple hours. When I checked it, it had lost something to the effect of 10% battery life per hour while doing nothing in airplane mode! I forgot to get a Better Battery Stats dump, so I'm going to repeat the experiment, this time in safe mode then get share my dump.
After that long winded diatribe, let's to the actual (obvious) question: Why is my battery dying so fast? And, could a hardware malfunction cause something in the OS to keep a wakelock (i.e. would a warranty replacement help)?
Thanks in advance to anyone who decides to try and help tackle this nonsense.
Click to expand...
Click to collapse
On a brand new rom install the media scanner is scanning your whole SD card to check for media files (pictures, videos, audio).
Normally once that is done, it will only scan for new files at boot or when you unmount your SD card from your computer.
Something to keep in mind if you play with a lot of media files daily.
polobunny said:
On a brand new rom install the media scanner is scanning your whole SD card to check for media files (pictures, videos, audio).
Normally once that is done, it will only scan for new files at boot or when you unmount your SD card from your computer.
Something to keep in mind if you play with a lot of media files daily.
Click to expand...
Click to collapse
Thanks for the suggestion. When I do my next test, I will format my sd card before starting, see if a blank slate helps.
beovvulf said:
To avoid hijacking anyone else's JB battery issues thread, i'll make my own.
First, a bit of back story. I installed the factory JB image (9020A) via fastboot to try and track down why I've been getting abysmal battery life and decided to do a little experiment. I turned on airplane mode, and let my phone sit, undisturbed for a couple hours. When I checked it, it had lost something to the effect of 10% battery life per hour while doing nothing in airplane mode! I forgot to get a Better Battery Stats dump, so I'm going to repeat the experiment, this time in safe mode then get share my dump.
After that long winded explanation, let's to the actual (obvious) question: Why is my battery dying so fast? And, could a hardware malfunction cause something in the OS to keep a wakelock (i.e. would a warranty replacement help)?
Thanks in advance to anyone who decides to try and help tackle this nonsense.
Click to expand...
Click to collapse
It's probably the ROM itself. Apps still turn on looking for something to do even without data or wifi.....
Try a ROM that it know to have less battery drain. Some ROMs have certain kernels that have sleep modes that will help your issue.
good luck
Sorry to dig this back up, but I have further developments.
I finally broke down and bought a second stock battery (with handy charger/stand), and I am still getting massive drain on the brand new battery regardless of what radios are on. I have completely stock JB images flashed so I am not even going to consider ROM/kernel/radio issues at this point. I just want to know if this has happened to anyone else before?
Also, I am getting weird striations on the screen, they are really noticeable on a predominantly red background.
My phone is hard brick
I did change in vold.fstab:
#dev_mount sdcard /storage/sdcard0 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /storage/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
# external sdcard
#dev_mount external_sd /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
dev_mount external_sd /storage/sdcard0 auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
Click to expand...
Click to collapse
Here is DOS command history:
C:\Users\xxx>adb push C:\Users\xxx\Downloads\vold.fstab1 /system/etc/vold.fstab1
476 KB/s (975 bytes in 0.002s)
C:\Users\xxx>adb shell
~ # ←[6ncd system/etc
cd system/etc
/system/etc # ←[6nls -l v*
ls -l v*
-rw-r--r-- 1 root root 977 Sep 28 18:34 vold.fstab
-rw-r--r-- 1 root root 794 Sep 28 15:58 vold.fstab.bkp
-rw-rw-rw- 1 root root 975 Sep 28 18:39 vold.fstab1
/system/etc # ←[6nmv vold.fstab1 vold.fstab
mv vold.fstab1 vold.fstab
/system/etc # ←[6nchmod 644 vold.fstab
chmod 644 vold.fstab
/system/etc # ←[6nreboot
reboot
C:\Users\xxx>adb reboot recovery
C:\Users\xxx>
Click to expand...
Click to collapse
My ROM: [Rom]Sky-JellyBean T-1,000 4.2 ((T4--(10/01)) GS3-Touchwiz--Vs--CM 10
My Recovery [RECOVERY]TWRP 2.2.2.0 touch recovery [2012-08-24]
1. So as you can see, when I try to reboot from shell prompt (USB connected to the PC), in order to check effect with changed vold.fstab, everyting was fine.
2. Next step was to reboot in recovery and try something diffident with vold.fstab. I executed "adb reboot recovery", but after rebooting process, there is no response from device, no power on, no download mode, no recovery.
Don't know it is about device (because didn't flash any block device, or maybe some bug in kernel, or recovery system), or still is it possible for memory flush because of many reboots (in this case it is easy with JTAG, I'll find someone on internet).
Any idea where to look for the problem ???
Thank you in advance
It's soft bricked not hard bricked. Pull battery, wait and then hold volume down while plugging in usb for power without inserting battery.
Should goto download.
Sent from my SGH-I727 using Tapatalk 2
kr3w1337 said:
It's soft bricked not hard bricked. Pull battery, wait and then hold volume down while plugging in usb for power without inserting battery.
Should goto download.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thank you, I did try but it doesn't work ( I already tried JIG method too), but phone is dead, no sign of any working mod (recovery or download).
Worry for wet in my phone, from humidity, when I'm opening battery cover so many times, or memory failure resulted with so many restarts. I did same things so many times with my old Galaxy S and Blackberry, and no problem ????. Please any advice ...
milniko said:
Thank you, I did try but it doesn't work ( I already tried JIG method too), but phone is dead, no sign of any working mod (recovery or download).
Worry for wet in my phone, from humidity, when I'm opening battery cover so many times, or memory failure resulted with so many restarts. I did same things so many times with my old Galaxy S and Blackberry, and no problem ????. Please any advice ...
Click to expand...
Click to collapse
I am guessing from your "accent," that your not from the states. Having the back cover off is NOT going to differentiate the humidity in any negligible amount. You could / should try removing both your sim card AND sd card, pop out the battery, plug it into the USB connected to your computer, THEN put the battery back in, THEN Power / UP/DOWN to get into recovery.
This method "theoretically" could get the phone to recover into the stock recovery system, once there, re flash the phone using ODIN with a stock rom. Granted you will lose all that you had on the phone, BUT it is better then having to shell out more $ for a new one. If you are in the states, then contact your provider (if it is still under warranty), tell them that you were plugged into the USB and trying to install via KIES the ICS update, then the phone went bad on you.
Thanks MasterDecker, and sorry for my "accent', by the way I'm not native American ,
I had a hundred of soft bricks with different devices (my 3 Android phone, 2 tablets, phones from my friends), and I had one "hard brick", it was at time when I did regular ATT's update for Gingerbread, in the middle of OTA update (buttery was full but aroud 46%, turn off by itself and device was dead ), in order to return Galaxy S for exchange (screen was less sensitive, don't know way)
ATT technician explained that processor was "wet" and it failed ???? I'm very careful with any flashing procedure, and in my last case, I just trying to understand what was wrong with my device, or my procedure.
But thank you for advice how I could handle device returning with ATT support, perhaps this is the way to end this story, or pay 50$ for JTAG servce, and hoping that it is only about memory fail ...
milniko said:
Thanks MasterDecker, and sorry for my "accent', by the way I'm not native American ,
I had a hundred of soft bricks with different devices (my 3 Android phone, 2 tablets, phones from my friends), and I had one "hard brick", it was at time when I did regular ATT's update for Gingerbread, in the middle of OTA update (buttery was full but aroud 46%, turn off by itself and device was dead ), in order to return Galaxy S for exchange (screen was less sensitive, don't know way)
ATT technician explained that processor was "wet" and it failed ???? I'm very careful with any flashing procedure, and in my last case, I just trying to understand what was wrong with my device, or my procedure.
But thank you for advice how I could handle device returning with ATT support, perhaps this is the way to end this story, or pay 50$ for JTAG servce, and hoping that it is only about memory fail ...
Click to expand...
Click to collapse
I still highly doubt that the processor was wet. My particular SII has ventured to Cebu Philippines in both the hottest and most humid of the summer AND the wettest of the monsoon season, and has no signs of any "humidity / water," damages. JTAG might be about your best option, but I still think that when you made your changes that it affected the boot loader.
Method #2 to try (if you have not already,) Remove battery, remove sim card, remove sd card, unplug from usb cable, & with a jewelrs loop, look carefully at the connectors for battery, sim card and sd card, Not really for scoring, but scorching, signs of excessive heat. If none are present, then that would most likely rule out excessive heat.
Hold down the power button, and re insert the USB cable, keep holding the power button for an additional 60 seconds AFTER inserting the cable plug. IF it does not boot up, THEN while still holding the power button insert the sim card, wait an additional 60 seconds, IF it still does not power on, or show signs of powering on, THEN while still holding down the power button re install the battery, and give it another 60 seconds. If this fails to flash any lights or power the phone on, then try again, only this time hold all 3 buttons down continuously while re doing the above steps.
This SHOULD confuse the phone enough to do a self test & restore to installed ROM.
Please advise if these steps have helped you. If not then I will think of another way.
Did try three times all ways in method #2, and they didn't work ... , with jewelrs loop, I did look carefully at the connectors for battery, sim card and sd card, but not really any signs of excessive heat ...
milniko said:
Did try three times all ways in method #2, and they didn't work ... , with jewelrs loop, I did look carefully at the connectors for battery, sim card and sd card, but not really any signs of excessive heat ...
Click to expand...
Click to collapse
And battery is not draining ... (wrong opposite I realized when I left buttery in during the night)
milniko said:
Did try three times all ways in method #2, and they didn't work ... , with jewelrs loop, I did look carefully at the connectors for battery, sim card and sd card, but not really any signs of excessive heat ...
Click to expand...
Click to collapse
milniko said:
And battery is not draining ...
Click to expand...
Click to collapse
I would then have to concede that it is in need of a JTAG.
My next questions are simply, why did you change the vold.fstab to begin with? When you did the adb reboot, was there ANY, and I mean ANY amount of static discharge to the device? Was there a "electric fluctuation" to your computer from your electrical outlet? (i/e brown out, black out, surge)
MasterDecker said:
My next questions are simply, why did you change the vold.fstab to begin with? When you did the adb reboot, was there ANY, and I mean ANY amount of static discharge to the device? Was there a "electric fluctuation" to your computer from your electrical outlet? (i/e brown out, black out, surge)
Click to expand...
Click to collapse
And battery is draining ... (I was wrong, it's opposite, I did realized when I leaved buttery in, during the night).
So again I was almost one week on jellybean (Sky-JellyBean T-1,000 4.2) moving from ICS (6/27/12***uclf5***galaxy s3 r4 update).
This ICS custom ROM is good and fast, but 3-4 mounts without any update, so I decided to go forward. But few days later I found that apps moving to SD card goes only to internal memory (to me, kind of very important limitation). So I started with experimenting with several options in vold.fstab with commands related with external and internal SD card trying somehow to change problem with apps moving (mounting on opposite way or mounting to the link folder). I did more then 20 times changes and reboot in one hour (implement change in recovery, reboot and check, and back to recovery; so I was working only with touchscreen). But with last scenario, my phone died ..., to me for no reason
With jewelrs loop, I did look carefully at the connectors for battery, sim card, sd card and USB connector, but not really any signs of excessive heat, nor my computer show any unusual activity (sign).
I guess it is hardware problem, in this case JTAG is useless, and maybe I should wait for AT&T i727 to be update with JellyBean;
I think this is the best moment to call for AT&T support ...???
If you want to go the warranty route, you can restore to GB stock without the screen working, then do the Kies update to ICS and brick it there.
T.J. Bender said:
If you want to go the warranty route, you can restore to GB stock without the screen working, then do the Kies update to ICS and brick it there.
Click to expand...
Click to collapse
??? Can not understand, answer, if I can ... ??? Maybe I didn't mention, phone is dead, it's mean no screen on (even touch screen is OK, I guess), no any sound, no buttons on, no recovery, no download, no USB recognize, so no ODIN flashing (or Kies) ???
I can only detect that battery is draining, and nothing else ... unfortunately !!!
If ODIN doesn't recognize your phone, you're done. Mail it in.
If ODIN does recognize your phone correctly in DL mode, even if the screen doesn't work, you can use the restore package in the sticky to take your phone back to GB stock. Then do the Kies update to 4.0.4 (you can do it as long as Kies recognizes your phone, even if the screen's off) and unplug the USB and/or remove the battery during the install. Bam, insta-brick on a stock phone. Send it in for replacement.
But, yeah, if ODIN doesn't recognize your phone at all, you're fudged. Send it to Sammy for replacement.
milniko said:
And battery is draining ... (I was wrong, it's opposite, I did realized when I leaved buttery in, during the night).
So again I was almost one week on jellybean (Sky-JellyBean T-1,000 4.2) moving from ICS (6/27/12***uclf5***galaxy s3 r4 update).
This ICS custom ROM is good and fast, but 3-4 mounts without any update, so I decided to go forward. But few days later I found that apps moving to SD card goes only to internal memory (to me, kind of very important limitation). So I started with experimenting with several options in vold.fstab with commands related with external and internal SD card trying somehow to change problem with apps moving (mounting on opposite way or mounting to the link folder). I did more then 20 times changes and reboot in one hour (implement change in recovery, reboot and check, and back to recovery; so I was working only with touchscreen). But with last scenario, my phone died ..., to me for no reason
With jewelrs loop, I did look carefully at the connectors for battery, sim card, sd card and USB connector, but not really any signs of excessive heat, nor my computer show any unusual activity (sign).
I guess it is hardware problem, in this case JTAG is useless, and maybe I should wait for AT&T i727 to be update with JellyBean;
I think this is the best moment to call for AT&T support ...???
Click to expand...
Click to collapse
I would have to agree. Call up AT&T, tell them that you plugged it into the computer for the KIES update, the phone rebooted and never recovered. Follow through their asinine scripts, if the first rep does not offer the replacement, then escalate to a supervisor, if the supervisor does not offer the replacement, escalate it to another supervisor above that one. Keep on going until you get offered either a replacement or a flat refund for your ORIGINAL PURCHASE PRICE, plus have them prorate your account for the few weeks it has been out of commission.
nothing