Database Develop

[Q] Maybe a clue to battery issues? 2 instances android.process.acore using 100% CPU

Let me start by saying Thank You VERY much DroidTheory (and everyone who has contributed to making this an excellent stable ROM).
I am on the 1.4 (wiped cache, dalvik, battery stats, formatted system) build and I've been having the battery issues that everyone is talking about since 1.2. I am in the forums constantly and I have read all of the posts and the fixes for them. I have wiped battery data from a full charge, I'm on 1.4 so OMA files are already gone, I'm in Portland Or and we have stong 4G no drops ever since I have had my phone. So it isn't the cycling 4G/3G issue.
So I know there are multiple "my battery is dying" threads but I had not seen this one mentioned in any and don't want to get buried.
So I am having a bit of an issue getting a screen shot of it everytime I try I just get a wierd distorted image. That is not the issue I came for but if anyone knows.
What I am noticing is when I use the "Android System Info" app in the processes if I sort by CPU% I see 2 instances of the same thing "android.process.acore" both reporting 100% CPU and 35.28MB RAM. My total CPU is reporting around 50% at most times. I have tried killing the processes to see what may happen and there are no negative effects but the processes just seem to come back eventually if I check an hour (not exact) later there they are again.
I assume it's impossible for 200% of CPU to be used right now but what I'm wondering is would 100% CPU on one process equal to 50% when considering that nothing uses both cores yet?
Any clues what these processes (android.process.acore) are and if there is anything I can do. If someone can suggest a good way to take screens I will be happy to post one as well.

Use Screenshot ER instead of AndroSS. Curious to your findings. Massive battery drain here. I dropped 10% in 45 minutes doing absolutely nothing. Nothing rogue in my battery stats...
Sent from my DROID BIONIC using xda premium

Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales. Im really hoping the 2 aren't in compatible as I've been using this since it came out in my D1 and I am damn used to it. Anyways here is my screen shot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DROID BIONIC using XDA App

Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App

Proff3ss0r Farnsw0rth said:
Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales.
Click to expand...
Click to collapse
Pretty sure Fed said LP/LP+ isn't tested to work on gingerbread yet
Maybe that'll be fixed once he's done w/ the rewrite?
Wish I could help ya tho...just another pointless reply here

Proff3ss0r Farnsw0rth said:
Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I see this, 100% CPU on 1 or more threads of a single process on multiprocessor linux boxes where that process has run away/spinning in code... on a 2 processor system the system would look always loaded 50% or more...

Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App

That was my guess on the cores was 100% of of what it has the ability to use right now is only 50% of available.
Sent from my DROID BIONIC using XDA App

I have launcher pro and those processes don't run at all on my phone.
Sent from my DROID BIONIC using XDA App

Proff3ss0r Farnsw0rth said:
Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I am using the stock Blur launcher. My battery is just taking a beating...
I really want to figure this out because I love this ROM.

I swapped out to launcher ex I was pretty much able to duplicate my lp+ setup I'll see what happens I'm good so far no return. We'll see if this cures my battery issues.
Sent from my DROID BIONIC using XDA App

And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App

I get great battery life with launcher pro. It may not be optimized for gingerbread(or so it's said) but it runs great for me. I was getting a day and a half on Eclipse for the x2.
Sent from my DROID BIONIC using xda premium

I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium

Proff3ss0r Farnsw0rth said:
And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I installed Android System Info and checked that my android.process.acore was not using any cpu cycles (0%). I use the Go Launcher. I would suggest trying the dreaded "Factory Hard Reset". I know it's a pain and time consuming, but it cures a lot of random ills.
Good luck.

Yeah I am doing a reinstall with a rewipe at the moment (I know this isn't hard reset). I am a very process oriented person so I doubt I missed any of the wipe/formats needed for Unleashed but I'm going to give it another try.
After doing a bit of google searching for "android.process.acore" I find ALOT of people with the exact same issues (on different phones) all with non-stock launchers. I have found a few suggested fixes. Like removing widgets from stock browser and all other launchers (I have a few right now as I've been testing and trying to work around.
This does seem to be a widespread problem though for more than just us.
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?

Proff3ss0r Farnsw0rth said:
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?
Click to expand...
Click to collapse
Will do. I just checked and it's still at 0. I'll check throughout the day and let you know tonight.
Good luck.

ROB281 said:
I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
+1
Zeam launcher is awesome.

I checked out zeam but I just can't deal with how minimal it is don't get me wrong I run very minimal home screens (nearly 0 widgets but battery and clock and only 2 home screens. I just can't deal with the lack of options in zeam. I don't really have any further leads on this I've been fighting with it as I've had chances at work but still no luck. Does anyone here know how to actually read a logcat or will that even get me what I need?
Sent from my DROID BIONIC using XDA App

FWIW, I'm getting ABYSMAL battery life (7h4m from full charge to shutdown as of my last cycle just now), with only 8 minutes of phone calls, light surfing, light texting, email sysncs at 1/hour.
I'm running GoLauncher with UNL3EASH3D v4. I have yet to see the process you describe (and I've been checking it pretty frequently trying to track down my drain- in fact, without exception every time I check, Android System Info is the process using the highest cycles at about 10-13%). I also used Go with stock for a day or so and didn't have this level of drain. HOWEVER, I didn't duplicate my stock setup when i flashed unleashed, so it may well be unrelated to the ROM.
I AM seeing waaaaaay too much awake time on the stock battery stats screen.
I'm about to do a wipe and reinstall and run minimal for a few days to see if I can pinpoint anything. Trying to hold out for the update if I can... (Love the ROM, so really don't wanna go stock)

[i9020A] 2450 mAh Slim-line Battery?

Hey has anyone had any luck with these 2450 mAh original form-factor Nexus S Batteries available on Ebay? I'm tempted but at this price it's like something is wrong, lol...
2450mAh i9020 on Ebay will bring it up - I guess I don't have posting privileges yet.

For the assist: http://www.ebay.com/sch/i.html?_trksid=m570.l3201&_nkw=2450mAh+i9020+&_sacat=0

dartmouthy said:
Hey has anyone had any luck with these 2450 mAh original form-factor Nexus S Batteries available on Ebay?.
Click to expand...
Click to collapse
I bought it anyway, what the hell. I'll report back when I receive it
PS Thanks Aman!

dartmouthy said:
Hey has anyone had any luck with these 2450 mAh original form-factor Nexus S Batteries available on Ebay? I'm tempted but at this price it's like something is wrong, lol...
2450mAh i9020 on Ebay will bring it up - I guess I don't have posting privileges yet.
Click to expand...
Click to collapse
It's likely half the rating if that. There's a reason these are so cheap. They're crap, and fake.
Best scenario: Everything works, albeit the battery doesn't last as it should.
Worst scenario: Ends up breaking your phone.

Yikes. Yeah if the voltage wasn't 3.7V I'd stay away from it - my initial thought was that they might not be Li-Ion. Do they have a factory in Hong Kong specializing in printing fake labels to put over old 1000 mAh batteries? lol. Well I'll let you know how it goes, either way I was told it "shipped"...
I'm running Codename Android 3.5 with the latest stable Air Kernel at the moment, and that gives me a good 3.5 hours of screen time and 30 hours running time in general typically between charges - with my old-ass original battery. Maybe I should just be happy with that and not take the chance of plugging this guy in :/
He's got a 99% feedback rating and 700 sales so we shall see.
polobunny said:
It's likely half the rating if that. There's a reason these are so cheap. They're crap, and fake.
Best scenario: Everything works, albeit the battery doesn't last as it should.
Worst scenario: Ends up breaking your phone.
Click to expand...
Click to collapse

dartmouthy said:
Yikes. Yeah if the voltage wasn't 3.7V I'd stay away from it - my initial thought was that they might not be Li-Ion. Do they have a factory in Hong Kong specializing in printing fake labels to put over old 1000 mAh batteries? lol. Well I'll let you know how it goes, either way I was told it "shipped"...
I'm running Codename Android 3.5 with the latest stable Air Kernel at the moment, and that gives me a good 3.5 hours of screen time and 30 hours running time in general typically between charges - with my old-ass original battery. Maybe I should just be happy with that and not take the chance of plugging this guy in :/
He's got a 99% feedback rating and 700 sales so we shall see.
Click to expand...
Click to collapse
It's a worst case scenario. Most likely it will simply not hold a good charge. I don't believe they have a factory specialized in printing fake labels. They just have a very optimistic way of calculating these things.
Then again, aren't you surprised they can cram supposedly 2450mAh in the same format of a quality Samsung 1500mAh battery? That's more than 50% added to the OEM battery in the same size battery. And for cheaper.
I got this rule in life, but even more so with chinese electronics. If it seems too good to be true, it's probably too good to be true.

polobunny said:
If it seems too good to be true, it's probably too good to be true.
Click to expand...
Click to collapse
That's a good philosophy - this is where glass half full doesn't pay dividends - Chinese electronics

I bought one of these batteries via ebay. As soon as I get the text and see. . . I will let you know
ebay.it /itm /190719824923?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2648#ht_2925wt_952

There's a similar one that's supposedly made in Japan on Amazon for $20
http://www.amazon.com/dp/B005O8S55U/

please report back.... it should be very obvious the increased battery life it it is what it stated.
I doubt it, but if its true ill be buying one haha.

So I'm sure you've all been anxious to hear what happened with the miracle battery. Lol. Got it in the mail today. Which is funny because the day after I ordered it I called him out on the fakes... he ended up giving me a refund and it was processed. Ha! Well I bought a Samsung SGH-989 I'm using as my main machine since all this and have given my Nexus S to my son... But I'll test out the battery over the weekend and report back with details
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-T989D using xda app-developers app

Any updates on the performance? What does the phone recognize for the capacity?
Sent from my Nexus S using xda app-developers app

O MAN! i got excited until i read the comments

I just received one of these (charging up now). I will report back with performance results after a day or two of use.

Does anyone know of a tool or utility to verify the stated capacity of the battery? I used battery spy but it didn't really have a stats page other than to see the graph of power related activity. My son's battery has been working fine for the past couple of weeks. He seems to get about 36 hours runtime with WiFi GPS and sync on. No 3g data plan just a my5 talk and text. Typically 3 hours screen time, 30 mins talk time, over that 36 hour charge. If there's an app for this let me know and I'll put up some screenshots.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

This is essentially idle standby performance which I thought was pretty good!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

dartmouthy said:
This is essentially idle standby performance which I thought was pretty good!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Yes because a paperweight should get the best battery life. Report back with some usage. I'd be interested in how it really stands up to my stock one.

mdean1981 said:
Yes because a paperweight should get the best battery life.
Click to expand...
Click to collapse
What do you mean? Are you being snarky or is that supposed to be funny or something? Lol.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

@dartmouthy
In order to properly test your battery vs stock one, some battery testing software is needed : obviously:
Look at these apps
https://play.google.com/store/apps/details?id=ru.NanoDinamics.NovaTester
https://play.google.com/store/apps/details?id=com.batterybench&feature
note: the first app's description is in russian but app language is in english and it does give exact capacity in mah and both app take long time for testing.
Choose app you like and if you or your son have enough spare time try to test it out. Also state what ROM and kernel you're using. Then we can see does battery really have stated capacity.

dartmouthy said:
What do you mean? Are you being snarky or is that supposed to be funny or something? Lol.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I was being a little of both. It just cracks me up to see people post their battery stats but yet the phone was never used. No harm sir just making a bit of a funny out of something commonly seen.

AOSP roms = possible problems

I have been following most of the AOSP threads fairly closely to see people's experiences and I have seen a disturbing amount of people report bricked phones. The odd thing about it is that these bricks didn't occur during the process of flashing a rom. They all happened (or most of them at least) while trying to power on the phone after it was turned off or in deep sleep. Here are links to posts by DIFFERENT AOSP rom users who all experienced similar issues (one of these posts contain links to 3 other posts):
http://forum.xda-developers.com/showpost.php?p=42682374&postcount=78
http://forum.xda-developers.com/showpost.php?p=42654173&postcount=434
http://forum.xda-developers.com/showpost.php?p=42681918&postcount=436
http://forum.xda-developers.com/showpost.php?p=42557657&postcount=417
I personally have run Slim's rom for a good 4-5 hours w/o problems. However, I went back to Sense shortly thereafter. I'm not trying to cause some kind of panic but on the same hand I don't want to see people sitting around with a $500 desk ornament. Bottom line is we are responsible for what we do with our phones and as a result we should do as much research as possible before flashing anything. Look before you leap!
Edit: Here is an additional means to record your brick experience:
smac7 said:
I made this to try to pinpoint the issue. This way we can collaborate with all one owners, not just sprint.
If you have this issue, please add your info.
Here is the form
https://docs.google.com/forms/d/17NmaM3zhWueTxI_y7f1U7N6Er6tprd22I8_f3aIYmCw/viewform
Here is the responses
https://docs.google.com/spreadsheet/ccc?key=0AkLYIbykddrAdF9TMXBXaXZjMFhEczlSYUhoVDNHU1E#gid=0
Let me know if i should add any other crucial questions. I encourage people to post this in other threads when relevant.
Edit: page is open for public sharing
Click to expand...
Click to collapse
Thanks goes out to the user who took the time to do this.

Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
That's some messed up stuff.... You shouldn't have had to pay since it was a "hardware" issue. It should've been covered under the manufacturers warranty.

Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I know but whenever i've had a problem like that it's always been a free fix through sprint......

yeah I am in the same boat, I believe I was the first to report this. At first I thought it was just me and I passed it off as nothing. Since I've got my replacement I've watched people starting to trickle in with the same exact problem on AOSP I would definitely avoid flashing AOSP until the cause is narrowed down and solved if possible. As I said before it would be a damn shame not to run AOSP on this mighty device, but I have to stick with sense for now and hope that this problem is squashed soon.

Wow really? How upsetting. I'll have to keep an ear open. If there is any news regarding this issue please share
Sent from my HTCONE using xda app-developers app

Has anyone on a NON AOSP rom run their battery down and had it die? Did it charge? I know on a few other phones it was actually the recovery that had this issue. I would try it myself but as I have my phone through work, replacing it is a bit more complicated.

I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app

That makes sense. Thanks
Sent from my HTCONE using xda app-developers app

socalnative1 said:
I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
you are not able to relock the bootloader. we're talking total shut down, no power, no charge, no recovery, no bootloader, no fastboot adb devices, not a thing period point blank. i have the dead device still, and for the life of me cannot get it to do anything. I have been on my replacement for 2 weeks now running sense. hopefully the cause and solution are near.

Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta

felacio said:
Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm with you on that

Until we get more kernel sources/reliable code out of HTC, playing with AOSP can be a dangerous game. And tbqh, it could well be OP's fault (not saying it is, but it can be). Flashing custom software of any kind is going to give your carrier/OEM an easy way out if anything goes wrong, which everyone really should keep in mind before making the jump.

What recovery are the "bricked" users running. TWRP or CWM?

Yeah I had my battery die completely on a sense Rom, but I was easily able to charge it and turn it back on 2 minutes later.
Sent from My Only "One"

Glad I'm doing a lot of reading before I make the jump back to HTC. Seems like the One is more of a pain in the ass to Develop (safely) for than the GS3. Looks like I'll be sticking to sense for a while.

For once in all of my android ownership, I'm not really pressed to switch to aosp so this isn't a huge deal for me. The phone is already blazing fast and I actually enjoy and use a lot of the features HTC has implemented into Sense 5. And HTC's browser is the smoothest I've ever used. I do hope someone figures out the problem though. Hate to see more people get bricked.
Sent from my HTCONE using xda premium

Kraizk said:
What recovery are the "bricked" users running. TWRP or CWM?
Click to expand...
Click to collapse
So far, only TWRP users have reported this issue.

I don't want to be Mr. Obvious but I'm assuming that you guys have already tried the trick of putting your phone under a bright light, etc etc

Terrible Battery Life on Stock

Hey guys,
I am having trouble getting through a single day lately. I don't recall exactly when it started, but the phone is only 6 months old so I can't imagine its a dying battery already.
Today I am seeing the following. Screen brightness is at about 60%. I'm completely stock, unrooted, running 5.0.1. Any thoughts would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910T using XDA Free mobile app

So you got 15.5 hours. That is kind of good

BACARDILIMON said:
So you got 15.5 hours. That is kind of good
Click to expand...
Click to collapse
15 hours with 2.5 hours SOT is even remotely good? Man my Note 3, and Note 4 before the last month or so, would easily get a day and a half with 4+ hours SOT. If this is the new normal, color me unimpressed.
Sent from my SM-N910T using XDA Free mobile app

UnexplainedBacon said:
15 hours with 2.5 hours SOT is even remotely good? Man my Note 3, and Note 4 before the last month or so, would easily get a day and a half with 4+ hours SOT. If this is the new normal, color me unimpressed.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
It is the new normal. Different os. Things changed. You still got through the day with how you use the phone. I know guys trying to fix phone that dont get 5 hours. U was lucky

UnexplainedBacon said:
15 hours with 2.5 hours SOT is even remotely good? Man my Note 3, and Note 4 before the last month or so, would easily get a day and a half with 4+ hours SOT. If this is the new normal, color me unimpressed.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did you do a factory reset after updating to 5.0.1?

Ditch TW got easily 6 hours SOT running CM 12 yesterday. Until Samsung fixes the bugs in lollipop its just not worth messing with it.
Sent from my SM-N910T using XDA Free mobile app

I'm getting similar results. I'm looking for a fix if anyone can help. Is there a way to test the battery to see if something is going wrong?
Sent from my SM-N910T using XDA Free mobile app

Gjohnson7771 said:
I'm getting similar results. I'm looking for a fix if anyone can help. Is there a way to test the battery to see if something is going wrong?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Lol your temp went crazy in less than a minute lol. Flash a good rom and if u have bad drains need to show what apps are running.
BAD ASS NOTE 4

I'm actually experiencing this on stock and custom ROMS. I'm about to ODIN the phone. Tried factory resetting and wiping every single storage partition on the phone (minus obvious stuff like /EFS). Nothing helps. My phone also gets hot underneath the camera randomly when doing menial tasks. I'll let you know if ODIN helps.
I also came from a Note 3 which got great battery life, even on Lollipop. Remember that we've had Lollipop a few month before you Note 4 guys got it. OP is right. Something is seriously wrong with Lollipop on the Note 4.

Product F(RED) said:
I'm actually experiencing this on stock and custom ROMS. I'm about to ODIN the phone. Tried factory resetting and wiping every single storage partition on the phone (minus obvious stuff like /EFS). Nothing helps. My phone also gets hot underneath the camera randomly when doing menial tasks. I'll let you know if ODIN helps.
I also came from a Note 3 which got great battery life, even on Lollipop. Remember that we've had Lollipop a few month before you Note 4 guys got it. OP is right. Something is seriously wrong with Lollipop on the Note 4.
Click to expand...
Click to collapse
Phone getting hot is normal once I rooted. Runs cooler on stock kernel tho

BACARDILIMON said:
Phone getting hot is normal once I rooted. Runs cooler on stock kernel tho
Click to expand...
Click to collapse
Yeah, I actually noticed that actually. Once I flashed the stock COD6 kernel, the phone generally ran cooler (it would get hot for short periods of time, but never as hot or as frequent as with custom kernels like Emotion or Bioshock).
I just got done ODINing the phone. It's on the first bootup, on the T-Mobile splash screen. Hopefully this takes care of it. The previous owner never rooted it. It came with the official Lollipop update. When you take OTA's, it patches the system, so hopefully the issue is caused by a bad update.
I noticed one wakelock on before I ODIN'd (and hopefully no longer) was msm_hsic_host, which is modem-related. The modem wakes up every now and then to check on the status of the phone's connection to the network. However in my case, after having the phone unplugged for 4-5 hours, there would be a 1 hr 45 minute wakelock with little usage.

Product F(RED) said:
Yeah, I actually noticed that actually. Once I flashed the stock COD6 kernel, the phone generally ran cooler (it would get hot for short periods of time, but never as hot or as frequent as with custom kernels like Emotion or Bioshock).
I just got done ODINing the phone. It's on the first bootup, on the T-Mobile splash screen. Hopefully this takes care of it. The previous owner never rooted it. It came with the official Lollipop update. When you take OTA's, it patches the system, so hopefully the issue is caused by a bad update.
I noticed one wakelock on before I ODIN'd (and hopefully no longer) was msm_hsic_host, which is modem-related. The modem wakes up every now and then to check on the status of the phone's connection to the network. However in my case, after having the phone unplugged for 4-5 hours, there would be a 1 hr 45 minute wakelock with little usage.
Click to expand...
Click to collapse
I get that to but have sync shut off. Apps who wake up all the time will give you that. Fb destroys it lol.

V10 (msm 8992) | CPU, GPU, IO, RAM, Interactive Gov. || TWEAKS

Original post, here, in TMO section
http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478
Cheers mates :highfive:

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was my result after 3 days...
Sent from my LG-H900 using Tapatalk

its kinda like u r sucking ur battery. never saw this kind of droppage, i shuld try a factory reset!

greekunit690 said:
This was my result after 3 days...
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
You are literally the only person to have these results..
Stop spamming. You screwed something up while installing it (hard to do because I gave you the lines to copy/paste over) or you are running some kernel or ROM causing this drain. I'd like to see something other than the battery graph, to see what your app usage was...
Go home troll.

warBeard_actual said:
You are literally the only person to have these results..
Stop spamming. You screwed something up while installing it (hard to do because I gave you the lines to copy/paste over) or you are running some kernel or ROM causing this drain. I'd like to see something other than the battery graph, to see what your app usage was...
Go home troll.
Click to expand...
Click to collapse
I actually wasn't trying to be a troll or spam. I'm on an AT&T V10 so I'm obviously running stock Rom rooted (as there's no unlocked bootloader yet). Only other thing I have from xposed is gravity box only for visual changes. I copied and pasted directly to the ETC folder as you stated was allowable later in the thread. I only asked to see because, like you said, it's hard to mess something up. Don't really appreciate being called a troll for asking a simple question....
Edit: only other thing I can think of is I changed batteries on a daily basis because I'm away from outlets for most of the day and have nowhere to recharge. I think I read something that the phone takes up battery on start up. But without this mod I would usually get 5-6 hours SOT and about 14 hours on a full charge
Sent from my LG-H900 using Tapatalk

greekunit690 said:
I actually wasn't trying to be a troll or spam. I'm on an AT&T V10 so I'm obviously running stock Rom rooted (as there's no unlocked bootloader yet). Only other thing I have from xposed is gravity box only for visual changes. I copied and pasted directly to the ETC folder as you stated was allowable later in the thread. I only asked to see because, like you said, it's hard to mess something up. Don't really appreciate being called a troll for asking a simple question....
Edit: only other thing I can think of is I changed batteries on a daily basis because I'm away from outlets for most of the day and have nowhere to recharge. I think I read something that the phone takes up battery on start up. But without this mod I would usually get 5-6 hours SOT and about 14 hours on a full charge
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Your screen shot included nothing but a battery graph. No app usage, no explanation of what you are running / doing. And your saying "I'm rooted running xposed and all stock" is not you running stock. It is you running xposed rooted and probably with other small modifications here and there.
Just would be useful to not just come up here and make it look like this script magically destroyed your battery life somehow when it is literally nothing but basic shell scripts to modify very high level parameters of device operation. Like I said, you are literally the only person to ever have an issue. Post something useful other than "hey this is terrible here's a one off screen shot and no other information about what makes me unique from everyone else."
I didn't respond to your original question in the other thread because it was uninformative as to what you might have done wrong while installing the file. You posted a graph, then asked what you did wrong.
Good question. I have no idea. But obviously something because I've been using this for weeks now, and many other people as well and nobody has experienced this mystery battery sucking you are seeing.
It is important to note that your device will boot with all CPU governors set to "performance" which taps your frequency to max. This file changes it post boot, so if you didn't copy the file, or more importantly didn't set it's permissions properly afterwards, your device will be stuck running performance, possibly reboot, and certainly will suck your battery dry very quick.
You need to give me more if you want my help, otherwise I will ignore you. I do this stuff for a living and it isn't my job to be a test engineer for your device as well as my own.

warBeard_actual said:
Your screen shot included nothing but a battery graph. No app usage, no explanation of what you are running / doing. And your saying "I'm rooted running xposed and all stock" is not you running stock. It is you running xposed rooted and probably with other small modifications here and there.
Just would be useful to not just come up here and make it look like this script magically destroyed your battery life somehow when it is literally nothing but basic shell scripts to modify very high level parameters of device operation. Like I said, you are literally the only person to ever have an issue. Post something useful other than "hey this is terrible here's a one off screen shot and no other information about what makes me unique from everyone else."
I didn't respond to your original question in the other thread because it was uninformative as to what you might have done wrong while installing the file. You posted a graph, then asked what you did wrong.
Good question. I have no idea. But obviously something because I've been using this for weeks now, and many other people as well and nobody has experienced this mystery battery sucking you are seeing.
It is important to note that your device will boot with all CPU governors set to "performance" which taps your frequency to max. This file changes it post boot, so if you didn't copy the file, or more importantly didn't set it's permissions properly afterwards, your device will be stuck running performance, possibly reboot, and certainly will suck your battery dry very quick.
You need to give me more if you want my help, otherwise I will ignore you. I do this stuff for a living and it isn't my job to be a test engineer for your device as well as my own.
Click to expand...
Click to collapse
Sorry for the confusion. Yes I meant stock Rom as in no custom Rom. And as stated all I have xposed wise is gravity box with visual only.
I'm going to try a factory reset as someone else stated and copy only your file and see what happens after a few days.
I'm no noob when it comes to flashing and changing parameters which is why I was confused about why this had such a detrimental effect.
Again I thank you for your hard work and all the positive things you've given xda on your own time. I'm sure it's just something to do with only upgrading from root and not starting fresh
Sent from my LG-H900 using Tapatalk

greekunit690 said:
Sorry for the confusion. Yes I meant stock Rom as in no custom Rom. And as stated all I have xposed wise is gravity box with visual only.
I'm going to try a factory reset as someone else stated and copy only your file and see what happens after a few days.
I'm no noob when it comes to flashing and changing parameters which is why I was confused about why this had such a detrimental effect.
Again I thank you for your hard work and all the positive things you've given xda on your own time. I'm sure it's just something to do with only upgrading from root and not starting fresh
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
I think it would be good if you post the command output of
Code:
ls -l /etc/init.qcom.post_boot.sh
and also a screenshot with the app usage stats.

WillyPillow said:
I think it would be good if you post the command output of
Code:
ls -l /etc/init.qcom.post_boot.sh
and also a screenshot with the app usage stats.
Click to expand...
Click to collapse
Seems to be doing a bit better today but again not much difference from without the change.
Here is the output in from terminal emulator
And here's screen time
And the app usage
Sent from my LG-H900 using Tapatalk

greekunit690 said:
Seems to be doing a bit better today but again not much difference from without the change.
Here is the output in from terminal emulator
And here's screen time
And the app usage
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
@greekunit690 it might just be coincidence, but under your display settings try unchecking & rechecking the Auto option under Brightness. I've found that for whatever reason the brightness setting will get stuck at the highest level even though I have Auto selected. This has led to rapid battery drain for me when it happens.

Dryvlyne said:
@greekunit690 it might just be coincidence, but under your display settings try unchecking & rechecking the Auto option under Brightness. I've found that for whatever reason the brightness setting will get stuck at the highest level even though I have Auto selected. This has led to rapid battery drain for me when it happens.
Click to expand...
Click to collapse
I change my brightness throughout the day so I'm sure that wouldn't be the case..thanks for the input though
Sent from my LG-H900 using Tapatalk

Just saying...im running your mod and its great I love it!
Sent from my VS990 using Tapatalk

in99flames said:
Just saying...im running your mod and its great I love it!
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
i cant use it
how did you install it ?

Its not hard. Just follow the instructions and use terminal emulator to input the commands. After you do it once from the commands you can simply copy and paste the file in the appropriate folder and correct the permissions when an update is posted.

rowihel2012 said:
i cant use it
how did you install it ?
Click to expand...
Click to collapse
If you're having issues you can try this
http://forum.xda-developers.com/showthread.php?t=3388850
Sent from my LG-H901 using XDA-Developers mobile app

another holy mother of earth issue with our v10 mine with zerolemon charged for 12 hours getting 6hours SOT , drains 20% overnight. WTH

warBeard_actual said:
Original post, here, in TMO section
http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478
Cheers mates :highfive:
Click to expand...
Click to collapse
Having a little trouble in that thread determining which one is the latest version to download, could you link me to the latest dangerously version and regular version please? Ty

Can i use it on H960A?

brenas25 said:
Can i use it on H960A?
Click to expand...
Click to collapse
yes