Database Develop

[Q] hp touchpad battery life on standby

Just wondering what sort of battery life people are getting with the touchpad on standby?
I am using cm nightly 9-20120608-nightly-tenderloin, the CPU is set to min 384MHz and the governor is set to powersave, but I am still losing about 25% battery in 10 hours on standby.

yh i'm the same too

marcs100 said:
Just wondering what sort of battery life people are getting with the touchpad on standby?
I am using cm nightly 9-20120608-nightly-tenderloin, the CPU is set to min 384MHz and the governor is set to powersave, but I am still losing about 25% battery in 10 hours on standby.
Click to expand...
Click to collapse
The battery life for the touchpad, in android, is not good. It you know you're going to turn yours off for a while, either go into webOS, or shut down completely.

yeah I am tending to shutdown the touchpad to save battery
life. Can't remember the last time I booted into webos

marcs100 said:
Just wondering what sort of battery life people are getting with the touchpad on standby?
I am using cm nightly 9-20120608-nightly-tenderloin, the CPU is set to min 384MHz and the governor is set to powersave, but I am still losing about 25% battery in 10 hours on standby.
Click to expand...
Click to collapse
With a CPU governor and the proper profiles, you can get pretty decent battery life. I suggest CPU Master.
Sent from my Galaxy Nexus using Tapatalk 2

marcs100 said:
Just wondering what sort of battery life people are getting with the touchpad on standby?
I am using cm nightly 9-20120608-nightly-tenderloin, the CPU is set to min 384MHz and the governor is set to powersave, but I am still losing about 25% battery in 10 hours on standby.
Click to expand...
Click to collapse
What is the reason to set the min. frequency to 384 MHz?

flatlenin said:
What is the reason to set the min. frequency to 384 MHz?
Click to expand...
Click to collapse
It solves a lot of the sleep related issues.

how much does the governerr really effect the battary?

im just wondering how much does the governerr effect battary life? i changed from ondemand to smartass2 and im not sure i see any diffrent...
and im scheduales which one is best for multitasking and which is for when playing games?
and should i change the governerr setting?
i also read that sleep_ideal_frequency should be 200 and not 100 beacuse 100 wastes more or something like that, is that true?
using galaxy i9000 semaphore kernal jb

bump

I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.

Lavoslav said:
I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.
Click to expand...
Click to collapse
This is so wrong its a pain to read.:banghead: Why do we have the max and min frequency options in the semaphore app? Why do we have "Max Performance" and "Max Battery" power settings on laptops?
Sent from my GT-I9000

There was a thread some while ago that concluded in OnDemand and Performance being to two to give longest battery life and best performance.
I don't have specifics or even a link, but the thread was about schedulers and governors and which went together for best performance and battery life. I'm sure it's google'able
Sent from my GT-I9000 using xda premium

i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?

itzikd1 said:
i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?
Click to expand...
Click to collapse
maybe you can try and tell us

There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color

BlueFlame4 said:
There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color
Click to expand...
Click to collapse
I do use internet mostly so what will be the most effective governerr any idea?

itzikd1 said:
I do use internet mostly so what will be the most effective governerr any idea?
Click to expand...
Click to collapse
Try OnDemand or SmartAssV2.

[Q] sweep2wake + setcpu saves power?

Hello all. I am using sweep2wake function in my mobile. I know it uses wakelocks to implement, so it will prevent the mobile from going into deeper sleep state and so will consume battery when idle. I am using a setcpu screen off profile (200 max, 200 min). will it compromise?

rajag33 said:
Hello all. I am using sweep2wake function in my mobile. I know it uses wakelocks to implement, so it will prevent the mobile from going into deeper sleep state and so will consume battery when idle. I am using a setcpu screen off profile (200 max, 200 min). will it compromise?
Click to expand...
Click to collapse
Well you can test it. See how it will be with and without...

shut_down said:
Well you can test it. See how it will be with and without...
Click to expand...
Click to collapse
@shut_down Nice to see you responding everywhere and very active in this forum. your thanks meter shows it.
when I am not using the screen off profile, sweep2wake uses a bit more battery. with screen off profile set to all minimum, there is no obvious battery drain in using sweep2wake. so as usual setcpu saves my day. (but it takes 2 to 3 more seconds to wake the screen)
Edit: when I am using some other governor rathar than pegasusq, for my screen off profile(abyssplug, interactive), then there is no wake up delay). I read somewhere, that Pegasusq is not good for deep sleep states, and it helped. And when using conservative governor for screen off, phone is not waking, and I have to reboot it manually. Hope it helps someone.

rajag33 said:
@shut_down Nice to see you responding everywhere and very active in this forum. your thanks meter shows it.
when I am not using the screen off profile, sweep2wake uses a bit more battery. with screen off profile set to all minimum, there is no obvious battery drain in using sweep2wake. so as usual setcpu saves my day. (but it takes 2 to 3 more seconds to wake the screen)
Click to expand...
Click to collapse
Well yes, that lowering CPU freq gives you less responsive wake up. I am not sure what would be the solution. On the one side there is sweep2wake, on the other is battery life.

shut_down said:
Well yes, that lowering CPU freq gives you less responsive wake up. I am not sure what would be the solution. On the one side there is sweep2wake, on the other is battery life.
Click to expand...
Click to collapse
when I am using some other governor rather than pegasusq,
for my screen off profile(abyssplug, interactive), then
there is no wake up delay). I read somewhere, that
Pegasusq is not good for deep sleep states, and it
helped. And when using conservative governor for screen
off, phone is not waking, and I have to reboot it
manually. Hope it helps someone.

[Discussion] Nexus 6 Underclocking

I know that on all my phones I underclock them to be able to conserve as much battery life as I can. I was wanting to know how many other people underclock this device and what are the setups they are using? I, for example, am using LiquidSmooth v4 Nightly 12/23 and Sensei Kernel R26.1 underclocked at a max frequency of 1.1GHz. I have CPU hotplugging enabled and only use 2 cores.

What's your SOT with that set up? With the stock frequencies I can't get 6.5-7 hours SOT. I'm running LS 12/24 with Lean Kernel OCUC set at 300mhz-26496 I.e. (.3-2.7ghz) and the standard interactiveX Governor that is with it.

Why not just leave it in Battery Saver mode all the time?

Pilz said:
What's your SOT with that set up? With the stock frequencies I can't get 6.5-7 hours SOT. I'm running LS 12/24 with Lean Kernel OCUC set at 300mhz-26496 I.e. (.3-2.7ghz) and the standard interactiveX Governor that is with it.
Click to expand...
Click to collapse
I can't remember actually. I meant to check that. I'll see after use tomorrow.

knitler said:
Why not just leave it in Battery Saver mode all the time?
Click to expand...
Click to collapse
And I have a problem with battery saver mode on liquid smooth. It doesn't vibrate upon receiving a notification. And it seems like it only does that, and turns off animations and lowers brightness

jamcswain said:
And I have a problem with battery saver mode on liquid smooth. It doesn't vibrate upon receiving a notification. And it seems like it only does that, and turns off animations and lowers brightness
Click to expand...
Click to collapse
I believe it also locks the CPU clock down and turns off auto-sync on accounts. On my phone if I use it it tells me I have like 3-4 days of battery left

I am currently under locked at 1958 and my battery life improved drastically. I'm using Set CPU. Here is a screenshot. I'm currently on Chroma. I havent noticed any lag what so ever.

[Q] Nexus 6 problems: display, battery

I've received Nexus 6 from FlipKart, Its great but two major concerns:
1. Screen is very yellow (warm color) and on reducing brightness it becomes magenta. When compared to any other phone including Nexus 5, its extremely yellow. Tried couple of apps, none of them do a good job of fixing the yellows. Did anyone find a good app/setting to calibrate this screen right?
2. Battery life is pathetic: From 100% to 10% in half day. SOT is barely 3 - 3.5 hours (Greenified Facebook, Encryption off), no gaming, where as my friend gets 5hours. Sometimes phone hangs and switches off. When I switch on, it looses 15% battery. It has only been charged 2-3 times (only got it 2 days ago). Does it get better with time? or Am I having a faulty battery?
Update: forgot to mention my phone shuts down at 28% battery. And it didn't boot at all. I realized battery was zero. Is this calibration issue? Or bad battery

Flash elementalx, you'll be able to change color values and battery life is great

1. You can change your RGB using any kernel with support to it. Almost every single kernel have support to RGB LCD KCAL. Use a app such as Trickster to modify the RGB once you flashed a kernel of your choosing.
2. Battery life is subjective to how you use your device. Just because someone was able to achieve 5 hours+ SOT doesn't mean you will either because there are way too many factors that play into effect such as: cellular signal strength, wakelocks, apps installed, etc. If you want to maximize your battery life, look into underclocking the CPU/GPU frequency and flash a custom kernel (e.g. Franco) that removes mpdecision. Mpdecision is a huge battery drain and the frequencies that it selects is completely random and unnecessary in my opinion.
http://forum.xda-developers.com/showpost.php?p=57808725&postcount=7 my battery life with Franco pre-r1.

I agree that mpdecision really does drain battery a lot. I have mine OVERCLOCKED to 2.88 ghz with sensei kernel and intelliplug. And I am still getting way better battery life than stock. Just flash this kernel with intelliplug and there goes your battery issues. And you can also adjust your screen colors.

rmx36 said:
I agree that mpdecision really does drain battery a lot. I have mine OVERCLOCKED to 2.88 ghz with sensei kernel and intelliplug. And I am still getting way better battery life than stock. Just flash this kernel with intelliplug and there goes your battery issues. And you can also adjust your screen colors.
Click to expand...
Click to collapse
For more elaboration on mpdecision,
All Qualcomm based phones have Qualcomm prorprietary userspace binary called "mpdecision" aka m(ake)p(oor)decision. Instead of letting the kernel itself to decide what frequencies and how many cores to run, this "mpdecsion" binary polls the kernel run queue statistics and decides for the whole system the "optimal" frequency and the "optimal" number of cores to use. The concept is fine, except the decision making is done in userspace and it's 100% closed source so there's no way to tweak it and there's a latency (because all userspace binaries needs to "poll" the kernel for the latest information which is slightly delayed). - faux123
Click to expand...
Click to collapse
In other words, mpdecision makes your phone sit at 1.5GHz for doing the most simplest tasks, even composing a email it'll bring your frequency to be at 1.5GHz.
Download CPU Spy and use your phone, then look at CPU Spy and you'll see how much time is spent in that frequency. Then flash another kernel that does not use mpdecision then you'll see the difference, the phone sits at frequencies that makes sense for the load that is on the device.
The alternative solutions would be, Franco's Hotplugging Algorithm or intelliplug by Faux.

Battery life is very subjective.
I am still 100% stock, encrypted, auto brightness and get over 6 hours SOT every charge. Mainly WiFi, some LTE. No gaming.
I will root and switch to another kernel when I have time and see the difference. I would expect more battery.
However if you are only at 2.5 hours SOT on a full charge, I wouldn't expect it to double just by changing kernels.

JasonJoel said:
Battery life is very subjective.
I am still 100% stock, encrypted, auto brightness and get over 6 hours SOT every charge. Mainly WiFi, some LTE. No gaming.
I will root and switch to another kernel when I have time and see the difference. I would expect more battery.
However if you are only at 2.5 hours SOT on a full charge, I wouldn't expect it to double just by changing kernels.
Click to expand...
Click to collapse
Thats so impossible. I've switched to 2G only but i run on Wifi all time and yet 1 day standby and 3.5hrs SOT.

zephiK said:
1. You can change your RGB using any kernel with support to it. Almost every single kernel have support to RGB LCD KCAL. Use a app such as Trickster to modify the RGB once you flashed a kernel of your choosing.
2. Battery life is subjective to how you use your device. Just because someone was able to achieve 5 hours+ SOT doesn't mean you will either because there are way too many factors that play into effect such as: cellular signal strength, wakelocks, apps installed, etc. If you want to maximize your battery life, look into underclocking the CPU/GPU frequency and flash a custom kernel (e.g. Franco) that removes mpdecision. Mpdecision is a huge battery drain and the frequencies that it selects is completely random and unnecessary in my opinion.
http://forum.xda-developers.com/showpost.php?p=57808725&postcount=7 my battery life with Franco pre-r1.
Click to expand...
Click to collapse
Impressive! I'm trying ElementalX kernel right now. Is it safe to switch-off MP-decision on that using trickster or shall I go with franco blind folded.

taranfx said:
Thats so impossible. I've switched to 2G only but i run on Wifi all time and yet 1 day standby and 3.5hrs SOT.
Click to expand...
Click to collapse
Well, not impossible as it has been that way on my phone since day 1.
But i agree that it is really odd how some people are getting 3 hours and others getting 6.
I had the opposite on my Note 4 though. Everyone got 6 and I got 4. So who knows?

taranfx said:
Impressive! I'm trying ElementalX kernel right now. Is it safe to switch-off MP-decision on that using trickster or shall I go with franco blind folded.
Click to expand...
Click to collapse
You only want to disable MPDecision if theres a alternative. For Franco, mpdecision is 100% removed so you don't need to disable anything.
I don't know ElementalX so I can't say, ask in their thread. If you use Franco, everything is done for you and you don't need to do anything on your part.

My battery life with LK is pretty good as well! I was able to tether for 10 hours straight and still had 22% left after sleeping ~8 hours.