Database Develop

major battery issue [darchdroid]

hi guys. ive been thru every post in darch latest and previous threads, and no real confirmation as to what my problem is. i promise you tho, if someone has suggested it in those threads, i have tried it. from rebooting at the end of a full charge to recalibrating my battery. nothing is helping, and while it wasnt an isse before, tomaro i am going to soaring eagle (casino) and desperatly need the fix[xxx]
in darch previous build, he posted a vattery fix that blew mymind. i didnt think it was physically possible to get that many hours out of such heavy usage, but whatever he did, it worked. i was hoping someone can really help me out on this one...do you think someone could take a look at what his fixxxxxxxxxxxxx consisted of, and encorporate it into this current build? i would appreciate it so much, if i hit the big numbers tomaro, i will gladly paypal you any number of money in return!

Like you've been told in the main thread, all of those battery fix/x/x/xes have been incorporated into the current build already. Because you are the only person experiencing these issues (As far as I can tell) then it comes down to something that you're doing.
Go to Settings -> Spare Parts -> Battery History and then change the top drop down menu to "Partial wake usage" and post if any of the bars are full.
Also, did you flash after a total wipe, or did you flash over 2.6.5?
Do you overclock or use Autokiller?
What apps and widgets do you use? (List them ALL)
I have plenty of apps and several widgets on my phone and I'm still pulling at least ~25 hours of heavy use. I sent ~300 texts, did some web surfing, and made three phone calls (well, five... but three of length) and I'm sitting easy at 57% after a good 16 hours.

like it took me 100 times to get an answer to, theres no way that battery fix is in this current build. i went through 2 whole days with those fixxes, and mt battery life does not compare. and if darch tried to encorporate it, he broke it whille fixing gps or mms. its not working for me, im not a noob, i know how to flash and follow proper troubleshooting procedures.
i dont mess with overclock, i leave it set at 710. i wont report my location to an app that doesnt require it to function, so no autokiller
the only apps im using are launcherpro and fancy widget

hostileenviroment said:
i dont mess with overclock, i leave it set at 710. i wont report my location to an app that doesnt require it to function, so no autokiller
Click to expand...
Click to collapse
Do you use an overclock widget or do you just let the kernel do the frequency scaling? What shows up under Settings > Spare Parts > Battery history > Partial Wake Usage?

Autokiller no longer requires location..just saying.
-------------------------------------
Sent via the XDA Tapatalk App

comintern said:
Do you use an overclock widget or do you just let the kernel do the frequency scaling? What shows up under Settings > Spare Parts > Battery history > Partial Wake Usage?
Click to expand...
Click to collapse
i just let the kernal do its dirty work. are there some oc settings that might help preserve battery?
it says android, media, music, facebook, dialr and google in sp. i can only see some blue in android, and media, the rest are all grey..
just left for soaring eagle. any input wold be grrrreat

radxcoresteven said:
Autokiller no longer requires location..just saying.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
oh really? thanks man, i didnt know. guess the devdloper flt the pressure lol

I wasn't calling you a noob... :/
What is your signal strength on darchdroid? THAT is a problem that a lot of people are having. Bad signal strength = bad battery life. (Also, I want dBm, not bars)
I still think blaming darch for this when you are [now] one of two people with this problem is a little... absurd. There are tons of people running this ROM.

I'm having pretty crappy battery life too. My phone seems to sleep fine and doesn't drain when not in use. Nothing bizarre in spare parts. It's when I'm using it that it the the battery seems to abnormally plunge.
I wiped before flashing.
Not using any OC apps.
No autokiller or similar apps.
I restored all my apps with titanium backup.
I dunno.

My signal strength fluctuates anywhere from -89 dBM to -94 dBm at the location I spend most of my day at.

DevinXtreme said:
I wasn't calling you a noob... :/
What is your signal strength on darchdroid? THAT is a problem that a lot of people are having. Bad signal strength = bad battery life. (Also, I want dBm, not bars)
I still think blaming darch for this when you are [now] one of two people with this problem is a little... absurd. There are tons of people running this ROM.
Click to expand...
Click to collapse
apologies. your first post seemed a little condesending.
i actually get better signal w dd. 74dbms. a little ironic huh lol
i updated my recovery, wiped everything twice, and reflashed. installed NOTHING and its till draining. im going in for a redownload.
i think their are plenty of ppl with the battery issue...ppl who dont care tho, or dont know, or just havent posted
thanls for your help devin, i appreciate it. so whats the next step?

My battery issue is documented, I barely get 8 or 9 hours

Unplugged at 10AM this morning, it's 2:10PM now and I'm at 46%. Heavy usage, on the internet for probably an hour and a half atleast. I thought this was normal battery usage because it's all I've ever gotten. Doesn't bother me because I carry around an extra battery for a total of 16 hours battery life, and I have a third battery if I intend to go for a while without a charger
EDIT: Signal is -88 and is usually always around that point.

i was using the latest radio from flipz (2.42.blahblah) and my signal was hovering around -95 dbm, just flashed the old stock radio and it's up to -75ish dbm

So what's better -95 or lower (example -75)

DirtyShroomz said:
So what's better -95 or lower (example -75)
Click to expand...
Click to collapse
Higher (closer to 0) is better, so -75dBM is better than -95dBM. -70dBM or better should be full bars. -100dBM should be the worst signal that displays 1 bar (if it displayed right). One thing you might try is pulling the radio interface library from DamageControl and push it out to /system/lib/libhtc_ril.so. I think Darch uses an older version.

my phone is draining like water between my fingers. if i post a logcat, will that help?

DevinXtreme said:
Like you've been told in the main thread, all of those battery fix/x/x/xes have been incorporated into the current build already.
Click to expand...
Click to collapse
By this do you mean that the always on mobile setting is disabled by default. That setting alone has doubled my battery life on other phones. Also, for those with lower signal, consider disabling the "Use wireless networks" setting under location. With low signal it can cause more battery usage than GPS. Devs that think they are helping by trying to use wireless signals for location are actually hurting. A big one that comes to mind is Locale. I have written the dev once and about to write again. They turn on wireless all the time to try and use it for location and they don't turn it off after. Even when my current conditions in locale specifically say to turn wifi off.

hostileenviroment said:
apologies. your first post seemed a little condesending.
i actually get better signal w dd. 74dbms. a little ironic huh lol
i updated my recovery, wiped everything twice, and reflashed. installed NOTHING and its till draining. im going in for a redownload.
i think their are plenty of ppl with the battery issue...ppl who dont care tho, or dont know, or just havent posted
thanls for your help devin, i appreciate it. so whats the next step?
Click to expand...
Click to collapse
Do you have GPS always turned on? I only turn it on when I'm using it.
Have you removed apps that you don't use? I've created a .bat that automatically removes all the stuff I don't use (Livewallpapers.apk, for example), pushes my current ringtones to system storage (it's faster, more battery efficient) and then reboots the phone.
Do you have autobrightness on? I have my brightness stay at a low-ish setting (still visible mostly everywhere, though) because I noticed the light sensor was being a little wacky.
What baseband and PRL do you have?
hostileenviroment said:
my phone is draining like water between my fingers. if i post a logcat, will that help?
Click to expand...
Click to collapse
A logcat may be useful to people who know more about the jargon that those spit out. I've solved a couple of my own problems by looking through them, but I knew what I was looking for. I wouldn't know what to look for in this circumstance.
lineman78 said:
By this do you mean that the always on mobile setting is disabled by default. That setting alone has doubled my battery life on other phones. Also, for those with lower signal, consider disabling the "Use wireless networks" setting under location. With low signal it can cause more battery usage than GPS. Devs that think they are helping by trying to use wireless signals for location are actually hurting. A big one that comes to mind is Locale. I have written the dev once and about to write again. They turn on wireless all the time to try and use it for location and they don't turn it off after. Even when my current conditions in locale specifically say to turn wifi off.
Click to expand...
Click to collapse
Mobile Network Always On is just default on this ROM. I've yet to find a setting for it. However, I found an app (Well, gomorrah pointed it out to me) that allows the data network to be turned off. It's called SwitchPro and it costs $.99 and it's well worth it.
I leave the network location on, but that really depends on your location. I've never had a problem with it.
The batteryfix/x/x/xes that I mentioned fixed a wakelock issue that happened in 2.6.2(?). Ever since then, the fixes were incorporated into the ROM. That doesn't mean that new problems could have arisen, but that those problems are patched. It doesn't seem to be a wakelock issue like it was in the past.
What I recommend to everyone is to follow the standard bug-reporting procedures detailed in the first post for the ROM. If there really is a bug, darch should be able to nail it.
And one last thing; can everyone with battery problems do this for me and post their results:
Code:
adb shell
top -m 5 -n 1
(If you could run it a few times over, say, 15 minutes, using the phone as you normally would, this could cause something to show up)

I know what my cause is... I have very poor signal at work and it spends all day just trying to squeeze out enough signal to get emails and sms. Disabling always on mobile has doubled the battery life of my phone and every other person that has said they tried it and has no side-effects that I have found. I am new to Darchdroid. Does Darch have a bug management system or a process to manage bugs/feature requests?

[Q] Why won't my N1 battery last more then half a day?

Hi I'm with Fido using an AT&T N1. My battery doesn't last me a full day. I thought maybe it was a defective battery, so I ordered a new one. This didn't solve my issue. I still have to charge it early in the afternoon and It's not like I'm watching video's it's just sitting there on my desk.
Anybody having the same problems or has a solution?
Thanks

Check what's using your battery, and act accordingly.

Are you on the wifis when it is at your desk? If not, how many bars of reception are you getting?

Root, undervolted kernel, more efficient roms, sync settings, apn control, brightness settings, battery calibration.
Welcome to android
Were all searching for ways to make our phones last longer/dynamic/faster.
Sent from my Google Phone

It says 67% of use is display, I set it to shut off after 30 seconds.
The wifi and BT are off.
Another thing I find weird. I have the dock. Every time i remove it from the dock and have to draw the password pattern, it's like the screen calibration is messed up. I have to close the screen and open it to get it working properly. This also makes it impossible to answer the phone when it rings while it's docked. I remove the phone and the slide to answer doesn't work as if it's not calibrated.

Check that your CPU isn't running at 100% frequency because of some rogue app.
Check that your phone has at least a couple of bars reception.

My N1 on AT&T runs 4.5%/hr usage when I'm not actively using it, around 6% if I'm doing typical stuff with it (reading email, web, etc).
It's on 3G, rarely use wifi (it's off), GPS is on, Bluetooth is on, K9 Mail is doing Push IMAP, Beautiful Weather is updating, misc other stuff is likely updating. Tasker is running doing lots of stuff, one of them is grabbing my GPS location and uploading it to my website every 10 minutes.
No IM, Facebook, or Twitter automatically running/updating.
I don't obsess over the screen brightness, generally leave it at Auto except when doing navigation in the car (It's never bright enough during the day) and I tend to pick dark themes but that's mainly because I don't like dark-on-white themes period on my phone.

adri_ment said:
It says 67% of use is display, I set it to shut off after 30 seconds.
Click to expand...
Click to collapse
Where does it say display use is 67%? In settings> about phone > battery use?

Does your phone feel hot? I notice sometimes that I'll be walking around and my phone is like burning a hole in my pocket, not literally but very hot. I noticed that when I installed wildmonks kernel and SetCPU that my battery increased TONS.

Some general things to check:
Auto email push
Cell stand by (look at reception)
Widgets auto refreshing
CPU frequency
I make sure all of the above is working properly, and my battery lasts for 2 days with light-medium usage

Sort of related question.... occasionally, I'll have "android system" just chew through my battery....if I let it just run for a few days, or if I clear the dalvik cache, it seems to fix itself, but I'm really clueless as to what is causing this....any ideas?

Don't know, but when it happens - it means the same thing I've mentioned multiple times in multiple different threads, some apps can cause the kernel to run in loop of some sorts - running at 100% CPU speed and eating the battery very quickly. Reboot sorts it out until it happens next time. Finding and uninstalling the rogue app sorts the issue, but it's a bit pain. Task killers don't help even a tiny bit, since they can't restart system service, and it's not the app that's running the loop.

Actually, for me, only clearing dalvik cache sorted it out. I had my battery die, swapped in a spare, and that one died within an hour or two....soooo yeah, reboot def did not fix the problem! xD

MaximReapage said:
Actually, for me, only clearing dalvik cache sorted it out. I had my battery die, swapped in a spare, and that one died within an hour or two....soooo yeah, reboot def did not fix the problem! xD
Click to expand...
Click to collapse
what is your set up
Sent from my Nexus One using XDA App

Use WiFi whenever you can. WiFi will more than double your cc very life over using 3g. Even just sitting there idle, its a huge difference.

ChongoDroid said:
what is your set up
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=714184
FRG83 blackbar version

Try super power beta.very impressive! !!what a genius! Will contribute soon!
Sent from my Nexus One using XDA App

[Q] Blitz - Battery and Freezes

Hey Guys, I've posted in other conversations about bad battery life with blitzkrieg and it seems pretty split down the middle between those who experience good battery life and those who don't. I did follow the advice and wait several days after I re-flashed blitz and my battery has yet to level out. I keep background data off at night when I go to bed, I went to bed with 93% battery left and woke up 7 hours later with a 23% battery life - while the phone was at rest.
I also have a problem about once every two days my phone will freeze up and restart. When it happens it just gets froze on screen and the whole phone vibrates for 20-30 seconds and then restarts.
Has anyone experiences these problems and found a solution to them? Should I change my settings at all?
I really don't want to get an extended battery but with the life my phone is currently getting I don't see much more of an option.
Thanks guys,

The phone freeze/reboot is a known issue with no known resolution. Before I dropped my last phone it had that problem consistently from stock v4 through every variant of the ota updates, revolt roms, gingervolt roms, kennels, scripts, no scripts, blah blah etc.
Now, however, I picked up a second Revo and have run it through gb and flashed gv 1.3, blitz 2.1 and various scripts and tweaks virtually mirroring my old device. I did that Monday morning and haven't had a single instance yet! These guys here do awesome work..
As for the battery draining, I haven't put my extended battery back on this phone yet because I was curious how the stock would perform with these mods. For the first couple days I was discharging at an even 10% an hour. Yesterday and today its dropped to 7.5%. Why? No damn idea. But I can live with that.
So, nothing terribly helpful here but just a disclaimer that your mileage may vary and a nod to the devs here doing kickass work. Good enough that I actively went looking for another Revo instead of fussing with a second line upgrade. That speaks volumes.

Oh yeah I'm not dissing the devs at all they're great!
The revo is a strange device all the reboots due to GPS and airplane mode I'm sure is a hardware fault because every revo I've had has done it and I'm on my third. I love blitz and can't live without my overclock lol I'm just wondering if there's special settings or CPU governors I'm not using that would help.
Sent from my VS910 4G using XDA App

I've used CPU Master and am on ROM toolbox now. Can't say I've seen a significant difference between the two as far as battery goes. I've used both ondemand and smoothass, same deal.
I did have some luck limiting reboots on my first by bumping up the min to 768 but haven't needed to bother on this phone so its 2 something. No extra settings or anything. : )

Guess it's just the screwy differences in hardware that make some a better build quality than others. Well I said I wouldn't do it, but I lied...
I'm restoring to my GV 1.3 pre-blitz image as I type this. Guess I like battery over performance, we'll see...I may be back to blitz.

Can somebody explain the difference between ondemand and smoothass. I still don't understand them that well. Thanks!

I didn't read the whole thread but seeing profiles for the kernel helps a lot like when my screen is off my phone is set to minimum on the min and max which sometimes causes lag turning on but once the screen comes on it's up and running fine. At that level if I keep the screen off it takes nearly an hour to drop a percent.
Sent from my VS910 4G using xda premium

Perhaps this is not the best reference but here is one about charging your Lion battery:
This link won't paste:
[URL="http://dottech.org/tipsntricks/17705/tip-condition-your-new-cell-phones-battery-to-make-it-last-longer-but-be-sure-to-condition-it-properly/[/URL]
It points out two possible issue:
1) over discharge (perhaps our meters account for this,
2) getting the battery hot, my phone does warm up setting on the charger, sounds like the usb port charging might be better for the battery?

An exercise in battery longevity.

Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min( 652800) Max( 652800) Max.screen off(300mhz)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
Installed gsam for more meaningful data logging.
Unchecked Auto Sync Data in the Data Usage settings
Changed CPU clock min/max 652800
Installed Deep sleep battery saver Xposed module. (on slumber profile) buts phone into deep sleep when screen is off.
If i remember anything else i did on here, i'll post it.
(sorry its taking so long for replies/updates, "new user status" prevents my posts 5 minutes in between.) (hard to believe, been a member since 2011, just lurked alot.)
*May have found lower limit on the CPU, no instability as of yet, however phone is acting a bit erratic, looking into this currently. (booting takes FOREVER. this is a problem.)
*Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
*Changed CPU freq. to min max 652800 based on advice of the community.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?

gh0stpirate said:
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min(960000) Max(stock) Max.screen off(157440)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
If i remember anything else i did on here, i'll post it.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
Click to expand...
Click to collapse
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.

It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.

bblzd said:
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
Click to expand...
Click to collapse
Thanks for the tips! heres what i changed:
installed gsam for more meaningful data logging.
unchecked Auto Sync Data in the Data Usage settings
changed CPU clock min/max 300mhz

Zainiak said:
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
Click to expand...
Click to collapse
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.

gh0stpirate said:
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
Click to expand...
Click to collapse
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.

bblzd said:
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
Click to expand...
Click to collapse
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!

gh0stpirate said:
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
Click to expand...
Click to collapse
Unfortunately I do not, just speculation based off what I've seen when monitoring current draw (using Current Widget) and the battery percentage before and after a reboot.
I do have shots demonstrating low idle drain with Auto Syncs and Locations disabled. On average I'd say my drop is about 1% over 5 hours of deep sleep, but it's always hard to tell because there's no way for me to know exactly when it drops without active logging which would interfere with the phone's deep sleep.

Generally speaking a reboot uses ~1% of your battery. If you're locking your CPU to run at only 300mhz I would just leave it on the entire time. Especially if mobile data is off and so is WiFi. Make sure you go into Settings > WiFi > *Touch the 3-dot menu* > Advanced > Disable "Scanning Always Available". I lose about 1-2% in airplane mode overnight over clocked with high quality sound driver from Viper4Android. Plus the Google now hotword activated everywhere but lock screen.
A while back I did a test with my N5 to purposely nerf its power to see how long of a SoT I could get with it. I did pretty much everything you mentioned in the OP. Locked max CPU frequency to match min. Lowest screen brightness, airplane mode, etc. I was able to get over 12 hours SoT. So if the N5 can get 12 hours with the screen on using the same setup you plan in using with the phone getting nice and warm... I don't think a week standby time is too farfetched as long as it's idle most of the time except for pictures. Depends on how much music you listen to I guess. Only problem is even with music saved on the device itself, running at 300mhz you're going to run into skips and pops. Especially when the screen is off. Music playback will be kinda iffy.
Good luck though and let us know how it goes.
Edit: Actually I was mistaken. I just disabled everything like location, sync, etc. Default kernel parameters except switching to ondemandplus governor. This was on an older release of Uber kernel. 12+ hours SoT with ~30% battery remaining!
Here's my post;
http://forum.xda-developers.com/showthread.php?p=52133394

You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.

KJ said:
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
Click to expand...
Click to collapse
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.

RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
Currently Using Apollo music player, can confirm Zero issues using music playback, confirmed CPU freq. using cpu frequency app. most of these things are using hardware decoders

RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
But if the phone is sleeping soundly as it should.... The max CPU is irrelevant if not being used. The lag and strain to run processes may hurt a lot though.

You let the music play while the screen was off for a few minutes or did you just play it for a few seconds? I have music stutter on screen off with frequencies higher than 300mhz. I get it with 729mhz. If it doesn't happen to you, awesome. Not sure why though. Do you have time to purchase an OTG charger? Might be worth looking into and they aren't that expensive.
http://www.amazon.com/Best-Sellers-...-Phone-Battery-Packs/zgbs/wireless/7073960011

Currently listening with screen off/on full songs. No issues. no time to purchase an OTG charger however :/

Updated main post to reflect newest enhancements.
Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?

It can be done
Sent from my Nexus 5 using XDA Free mobile app

I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,

Flukzr said:
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Click to expand...
Click to collapse
I remembered a discussion along those lines, ill bump the freq. to 652800 min max, and update the main post. An external pack would be great, but i unfortunately just don't have the cash at the moment. between the trip and i just ordered a triple monitor stand and a new wifi usb to play with nethunter

gh0stpirate said:
Screen Brightness set to low as possibe.
Airplane Mode
Click to expand...
Click to collapse
This is basically all you need, the phone will idle for a week or so in airplane mode.

Can't disable BCL, phone throttled below 40%

I tired the init script or the kernel switches - they both do the same thing really, write 'disabled' into qcom,bcl.39/mode file.
Which does nothing. I still get throttled down to 1958mhz with only two cores running. thermal-engine-shamu.conf has been fixed ages ago (and really that file by default has very mild throttling)
As you can imagine this lags the hell out of the phone and it's very annoying.
Running latest 6.0.1 stock image with all kinds of different kernels, including stock, making no difference. Even kernels that claim to disable or allow disable of BCL (like benzoCore) I get nothing. I am sometimes able to restore the clock speed cap, but not turn the cores on. Plugging into the charger sometimes restores cores and clock speeds instantly, sometimes doesn't. Charging to above 40% AND rebooting always restores them. Using zen hotplug to simplify things.
I'm pretty much ready to chuck this and get a 6P unless someone knows how to solve this?

I don't know if it is useful or even what you are looking for. There's a zip here on nexus forum called disable throttle. I flashed that and it resolved some issues.
Sent from my Nexus 6 using XDA-Developers mobile app
Edit. Here is what I use. Again not sure if this is what you are looking for. But thought I'd share in case it's something useful for you.
http://forum.xda-developers.com/nexus-6/development/mod-disable-throttling-battery-low-t3440814

Thank you. That first line from the OP is not really accurate unless older versions of Android throttled below 40% with the default thermal-engine.conf file. On 6.0.1, the thermal engine throttling kicks in at 25% and only for the GPU. The CPU isn't throttled at all until either at 15% or 10% (don't remember which). And I already have that zip flashed.
I'm pretty certain the 40% throttle, which is the problem I'm struggling with, is the BCL driver that cannot be turned off by just writing "disabled" into the mode file.
Frankly not sure why everyone isn't up in arms about this, because it makes the phone pretty damn unusable. I suspect there are a number of inputs which make a difference, so the majority people are not experiencing this. Maybe I have too high of a constant CPU load, so the throttle affects me more than others? Maybe BCL is being triggered by inputs from my failing battery (mine has about 85% of its original capacity left)? Some ROM versions don't do this? Who knows.. It seems a waste to upgrade when a non-throttled 6 would cover 95% of my use cases except for the lousy camera. I'll be replacing the battery soon so maybe that'll fix it.. fingers crossed.

*double post*

I'd it were me I'd buy a new battery. Also for camera. I know it's a hardware limitation your talking about but. But I use camera nx1. Modified Google camera I snagged from the apps and themes section here
Anyways. Not sure what I can mention to help. Other then that sucks. N6 is a great phone and it seems like some users just phonws with issues that others are not experiencing. Wish there was a solution for you. Sorry man.
Sent from my Nexus 6 using XDA-Developers mobile app