You probably get these all the time so apologies.
I've done the google and the msm_hsic_host is referenced for when you connect the phone via usb.
But the problem I have is it's there all the time, regardless of using a computer USB cable or using a wall charger.
These appear far too often, reboots help but there seems to be something wrong and I cannot figure it out.
Any and all help / advice welcome becuase it's really fustrating.
Cheers
What OS are you running? Could it be an app you installed? Have you tried flashing to stock to see what happens?
On stock 4.2.2
Will have to see on the app front.. Might do a purge and see if it helps.
Sent from my Nexus 4 using xda app-developers app
Good luck. Please report back with your findings.
I was on stock 4.4.2 and got pretty good battery life.
Lol OP, I think what you're using is 4.4.2 not 4.2.2. It's time to get it right now, don't you think?
Btw, are you using stock kernel or custom? Either way try flashing stock kernel back and format dalvik and cache. If you're using custom kernel, same..flash stock kernel back then flash your kernel.
Sigh you are right. 4.4.2 of course.
Everything is stock on my nexus4, haven't even rooted it.
Which is why this behaviour is so annoying, might understand if I'd have played around with roms etc.
I've deleted loads of apps, may remove some more today if it doesn't let out. Will then think about going for a wipe down.
Cheers for the suggestions.
Sent from my Nexus 4 using xda app-developers app
Maybe this will help you: http://forum.xda-developers.com/showthread.php?t=1999368
From what i've read, this wakelock is not about the USB cable per se. The 3g modem is connected to the phone as an external USB device, which is controlled by the msm_hsic_host.
In few words, every time your phone needs something from the 3g modem, msm_hsic_host is triggered.
Im on 4.4.2 stock rooted and every time I'm in a place with low signal this wake lock drains a good amount of my battery.
Maybe you should try different kernels to see if that helps.
Sent from my Nexus 4 using xda app-developers app
Cheers
Using other on better battery stats shows the phone is never in deep sleep.
Now just to find out why.
Sent from my Nexus 4 using xda app-developers app
You need to show us the info from Partial Wakelocks, not Kernel.
Unleashed by my Nexus 4
Thanks yeah I know that would be more helpful so apologies that I haven't.
Wanted to if possible avoid rooting the phone but I think I'll do that this evening to see what's going on.
Sent from my Nexus 4 using xda app-developers app
Related
Hi, guys I don't know why but my battery is draining like hell every time I reboot my phone it just decreases 5% and while playing games in every 8 minutes my battery goes down about 12% is there any advice
My phone:
Omega v29 with siyah 1.7rc1
With nfc off,s beam off,s voice off.
Edit: while typing this my battery goes down about 3%
Sent from my GT-I9300 using xda app-developers app
Ouch ... bump charge it and wipe battery stats in recovery. Or maybe even do a fresh install. Sometimes that will fix it
Sent from my GT-I9300 using xda premium
Stop spreading that freaking lie. Wiping the battery stats doesn't do anything. Besides it is wiped every time the phone is charged to 100%. Don't believe me. Look it up, a Google engineer has posted this along time ago.
Sent from my SGH-I897 using xda premium
b-eock said:
Stop spreading that freaking lie. Wiping the battery stats doesn't do anything. Besides it is wiped every time the phone is charged to 100%. Don't believe me. Look it up, a Google engineer has posted this along time ago.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
So can u help in solving the problem????????
Sent from my GT-I9300 using xda app-developers app
b-eock said:
Stop spreading that freaking lie. Wiping the battery stats doesn't do anything. Besides it is wiped every time the phone is charged to 100%. Don't believe me. Look it up, a Google engineer has posted this along time ago.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Darn.. really? Then CWM should take this out in the features
Sent from my GT-S5830 using xda premium
WIping battery stats is useful when installing a new ROM, so it can measure battery capacity better (extreme tl;dr version). Install BetterBatteryStats and look for unusual wakelocks and processes. Report back with what causes the issue and we will see. If you could include screenshots of BBS, that would be the best
You don't get it do you? It is wiped when you install a ROM. It is WIPED when you charge to 100%. The batterystats.bin has no effect what so ever on your wake locks, battery problems, or anything else you think it is related to. All it does is report to the settings what has been using the battery.
Sent from my SGH-I897 using xda premium
b-eock said:
Stop spreading that freaking lie. Wiping the battery stats doesn't do anything. Besides it is wiped every time the phone is charged to 100%. Don't believe me. Look it up, a Google engineer has posted this along time ago.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
You know there are nicer ways to tell someone that wiping battery stats doesn't do anything . If it doesn't do anything than it shouldn't be in the options...period. I was trying to be helpful and offer a suggestion..and it couldn't hurt to try.
.. so whats your suggestion so no more "lies" get spread??
CWM is largely generic, so the Battery Wipe option is there whatever device. It is a waste of Dev. time to remove/customise for every device.
It doesn't do anything... in this case. It may on other devices.
But this is largely OT now... so back in the room.
It doesnt do anything for any device. A long time ago it was thought to do something. But a Google Engineer said otherwise pubically.
Sent from my GT-I9300 using xda premium
Guys just experienced something that this battery drain only happens to me only on Sammy jb roms and not on cm10 so is there any fix for it?????????
Sent from my GT-I9300 using xda app-developers app
Check that android.process.media is not running and consuming 20% of CPU cycles. This process always runs when you restart the phone as it scans the phone's internal and external SD card for media files.
Sleepycat3 said:
Check that android.process.media is not running and consuming 20% of CPU cycles. This process always runs when you restart the phone as it scans the phone's internal and external SD card for media files.
Click to expand...
Click to collapse
So how could I stop it
Sent from my GT-I9300 using xda app-developers app
Seems like all the threads i read that mention this problem the user is running Omega rom 2.x.. Maybe its something the dev as added into the rom that is causing it to kill your battery..
Got. The solution just changed the kernel. To stock and everything is as good as it was
Sent from my GT-I9300 using xda app-developers app
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
flash stock, you wont have to deal with it.
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
SoD seems to show up randomly... I've heard that JWR ROMs have less SoDs than JSS so you could try one, or if your not into switching ROMs here is an app (free) that could help you. It's called Safe Charge, and the comments say that it works great.
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Oops I guess I missed that part... I'm pretty sure that you can find a near similar ROM/kernel setup for JWR... If all else fails, try stock...
(Oh and if you can still RMA it, do it. People have speculated that its a hardware issue...)
No worries. I'm trying out SlimBean because I hear that doesn't have the issues, but not being able to use Franco with it is a bit of a bummer. In fact I haven't yet found a third party kernel that does work with it.
Sent from my Nexus 4 using xda app-developers app
I had this happen to me with a particular rom. Everything was great until id lock the phone, then try to unlock and see nothing but a black screen. I switched roms and it never happened again.
Sent from my SGH-I317M using xda premium
My nexus 10 is dying with displayed charge at or around 70%. I had lost the tablet and it was dead for months. Idk if that is relevant or not. It did take a full charge a few times after finding the tablet before the above stated issue occurred. The charger I'm using should be in good shape as it charges my Galaxy S4 w/o issue. Running CM 10.1.3 (Stable).
Thoughts? Thanks in advance.
Update: now the device is dying while showing charge level in the high 90% mark. Device now dies mid-boot even plugged in. Before it would stay on so long as I kept it plugged in. It will stay on if I go into cwm. That's the curious part.
Sent from my SGH-I337 using XDA Premium HD app
After doing some research I'm going to guess calibration to be the issue. What to do if calibration is so out of wack it thinks its charged when it's dead?
Update: I ran calibration after I managed to get it to 100%. A few minutes later it died. Curiously I put my tablet in recovery mode and it has stayed on for at least an hour now. However when I try to boot into CM it dies. Every retry it dies a little sooner in boot.
Maybe you could go back to stock via fastboot. If that doesnt work I think tour battery is dead.
Sent from my Galaxy Nexus using XDA Premium HD app
Actually I've been letting it sit idle in recovery mode. Its had at least 4 hours to drain now. Haven't been able to kill it yet so I am extra confused. I read the charge with an app and it was at 4400. The tablet is perfectly happy in recovery. I wiped my system partition and reflashed CM. This seemed to have an affect to a degree. Once the dalvik cache was rebuilt the tablet died again and went back to the odd behavior I mentioned. I would prefer to not return to stock unless it is absolutely necessary. I will if I have to but I would like to see if anyone else has seen this issue or has an idea on how to TS it as is.
For the Android junkie this would be a fun issue to trace down. I simply don't have the education. I just created my developer console account and am going through the documentation to create my first app. Clearly outside of Google Fu I'm relatively useless.
Sent from my SGH-I337 using XDA Premium HD app
Try wiping the battery stats from recovery, if yours lets you.
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
SmokinCharger said:
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
Click to expand...
Click to collapse
I think in going to have to. I've proved the battery is charged and CWM knows it. I'd like to do a titanium backup to preserve my game data but I don't see how if the darn thing dies mid-boot. May have to bite the bullet on this one
Sent from my SGH-I337 using XDA Premium HD app
dibblebill said:
Try wiping the battery stats from recovery, if yours lets you.
Click to expand...
Click to collapse
It didn't so I just wiped the whole /system partition (I believe that's where the battery bin exists) and flashed CM back. No good.
Sent from my SGH-I337 using XDA Premium HD app
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
hunforfee1 said:
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why thank you. I'll have a look.
Sent from my SGH-I337 using XDA Premium HD app
Flashed full factory image
I used the image found here to completely wipe and reset all partitions and make the thing like it just came out of the box with no trace of mods left (that I'm aware of). It happily booted in and I got about halfway through initial setup and it died and returned to the same behavior.
What do I do now?
Hey guys I'm on an AT&T D800... since Monday afternoon my phone had been unusable... it got extremely hot both front and back near the mid to top of the phone... and was just chewing through battery 31% in 15 minutes... so I powered down and left it numerous times on different stock based rooms and still no luck it would just overheat till it shutdown or battery died if I didn't turn it off... I managed to get it charged enough to restore my stock backup, unroot, and put the stock recovery back on and then did 2 factory resets with still no change... so I called at&t and they sent out a warranty replacement which will be here tomorrow.. so my question is do any of these return to stock methods actually clear rootchecker? That's my only worry that they'll see that and nail me the retail price of the phone... I didn't use a custom kernel just the roms...
I see conflicting stories from people saying yes it does it clear rootchecker and others saying no.. I would just try but I don't have WiFi so I don't burn up my months data just to find out it didn't work.
The phone seems to be working fine since I powered it up 2 hours ago but I'm worried about any residual/repeat issues or decreased lifespan of phone from the overheating issues
Thanks in advance!
Sent from my LG-D800 using XDA Premium 4 mobile app
Flashing a Stock .kdz works completely. Perhaps you should read this sticky: http://forum.xda-developers.com/showthread.php?t=2432476
Thanks I've read that one before but I've also read other threads that say it still shows rooted when booted into download mode even after doing this reflashing
Sent from my LG-D800 using XDA Premium 4 mobile app
I'll give it a go though and see how it turns out
Sent from my LG-D800 using XDA Premium 4 mobile app
Not a problem here...
Cool then I'll follow that method.. thanks again
Sent from my LG-D800 using XDA Premium 4 mobile app
Did you check to see why the battery was being depleted so fast? I am willing to bet the phone itself was fine, but some app was utilizing the entire CPU, which would heat the phone up and kill the battery quickly.
Which means it's entirely possible you'll have that issue with the new one as well.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Yeah but after 2 factory reset there were only unused factory installed apps
Sent from my LG-D800 using XDA Premium 4 mobile app
The rom restores I can see that holding true but after 2 complete resets and not adding any apps... not even setting up any Google services I don't know what it would be
Sent from my LG-D800 using XDA Premium 4 mobile app
An about a month ago switched to 7.1.2 from 6.0.1.
Stock rooted version. The phone is one and a half years old.
Since then I'm having random freezes that only pressing the power button and reboot will help.
I can't figure out what causes these freezes.
Anybody else having this ?
Sent from my Nexus 6P using xda premium
How did you update to 7.1.2 was it stock image ?
Yes. Stock image
Sent from my Nexus 6P using xda premium
Try a factory reset see if that helps really hard to say. Are you using substratum try removing overlays. If using custom kernel resore to stock. If it was me I would completely wipe my phone including internal. Then flash a fresh factory image to rule out any software related issues. Just make sure you back up all your pics etc.
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm using stock kernel. The freezes are random. Can't figure out what triggers them.
The freeze can be while the phone connected to charger, lying on a table or when I on Facebook or something else...
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
There apps that you can get that will show you logs of what's going on in the background. Catlog or syslog are ones that I know of. They can be hard to understand but might give you some clues to what's going on. After the phone does it thing quickly check the log and see if any errors from apps and such that stand out.