Database Develop

[Q] dynamic overclocking

.
..

I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk

Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?

..

MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk

..

MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk

Let's list some battery tips

Hey! I've just bought S5 yesterday and I know it's still premature to evaluate my phone's performance. I've made my first 100% to 16% with the phone and my stats were.
Phone on: 18h
Screen: 3h
Bright auto -5, wifi on, 3g on all time.
I find it is not as much as I expected but I must admit there was an update in between of the OS, and many updates in the play store which probably drained my battery higher than normally. Then I've checked tips for reducing consumption and that what I made:
- install battery guru
- disable syncs in google account
- disable updates in play store (notifications and so)
- disable some samsung apps
- disable gestures and movements
- location on power saving mode
However, my intention in this post is to gather more tips you are using with samsung rom (no root). Disable accounts or whatever you do...
Anyway, I guess I should expect an improvement in the battery life in coming charges...right?
Thanks!

Battery guru even sucks more battery than its saves, because it needs google service -.-'
I use:
Faux kernel - with my own tweaks, for hopefull best performance and battery life. OC 2.7
Greenify - to Slumber apps / System apps (Paid)
Unbounce - to lower the wake ups etc. (Paid)
BootManager - For faster start up / Battery saving
Stop Log - Turning off trash for speed up and battery life
Everything is turned off except:
Wifi - When home and somewere were its not locked.
Mobile data - Always on
Removed:
Idunno what its called but it has a blue icon and beammode?
Turned off:
Svoice
Samsung Link and that other samsung like app
Samsung push
Software update
Phone Screen:
Depends on were im at:
Home: 50%
School: 30 - 50
Work: 50%
Gaming: 50 - 100%
Movie: 50 - 100%
Background:
Black saves more battery and mine looks cool ^_^
Faux Settings for me, higest what ive got so far using it is 17 hours phone use, with 4:35 screen time on and it was still on 24% had to charge it because of my date
CPU Clocks:
Max: 2726400
Min: 300000
Gov: Intelliactive
Cpu hotplug:
intelliplug
Touchboost turned on
Screen off Frequency: 729600
intelliplug = Balanced (4)
Thermal Manager:
Chosen everything that was recommended
GPU Manager:
msm-andreno-tz
CPU clock control: 578
rest is stock
I/O Scheduler: both row - 1024
Same Page Merge:
Iltelli-KSM Enabled - left the rest stock of it
Miscellaneous:
Power suspend modes: Userspace
Power suspend turned on
tcp congestion: westwood
Rest is stock
I would love to change the black/gray to Pure black, to save more battery life, Gravity box could do this trick, but the app froze my phone somehow, now that its gone it works fine like before. so if you can change it do it.

Thanks! I've removed battery guru. I know that without rooting phone I may not be able to disable many things but I guess I can avoid some wakelocks coming from the pre installed software. Right? Which of them could be? Should I disable Samsung account? Any app that replaces S health in using the heart rate sensor? I think this is the only functionality I would have to keep which needs a Samsung account
Summing up , things that could make android os and system android reduce

paco_ramirez said:
Thanks! I've removed battery guru. I know that without rooting phone I may not be able to disable many things but I guess I can avoid some wakelocks coming from the pre installed software. Right? Which of them could be? Should I disable Samsung account? Any app that replaces S health in using the heart rate sensor? I think this is the only functionality I would have to keep which needs a Samsung account
Summing up , things that could make android os and system android reduce
Click to expand...
Click to collapse
Well the apps that push notification these use too much battery, like samsung push, just disable the apps you dont use at all
Verstuurd vanaf mijn SM-G900F met Tapatalk

Thanks!, I've just disabled it. More things?

paco_ramirez said:
Thanks!, I've just disabled it. More things?
Click to expand...
Click to collapse
Do you have root and recovery?
Verstuurd vanaf mijn SM-G900F met Tapatalk

My #1 tip would be before you look at how bad ur battery is. realise these are smartphones. and we buy them because of connectivity. why buy a smartphone if you keep turning of its ability to be smart
these phones run HD displays constant internet connectivity and all sorts of sync options

Sock12345 - I don't have it rooted yet. I'm thinking about it because I don't want to have the warranty avoided. I don't know how is the law concerning this in Spain. However, I would like to root it so that I can find out thexactly drainers and get rid of them. I will check this possibility
-PiLoT- you're totally right. Maybe I am asking too much to the phone which works incredibly well. But I have the feeling that some pre installed apps maybe battery drainers. Maybe they do not drain as much as I think...

[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.

[Q] CPU running at high clock most of the time

Updated section:
After clearing cache through recovery and doing a hard reset, the uAh has gone back to 3142000. Standby time seems good with the battery losing 7% overnight. It does charge quite quickly from 0-100 in about 2h. The previous heating issue remains with cpu monitors showing that the cpu jumps to high clock when I touch the screen. I don't see any change in which apps use the most battery with the screen taking up the most as before the problem started.
The heat appears to be what is draining the battery but I can't find any single app that causes it to ramp to max.
Pictures:
No-frills is set to stock settings to see how the phone handles the actions
2nd picture is when phone is idle
3rd picture is immediately after swiping through a few tabs and scrolling through some pages in the app which causes cpu clock and load to increase
Old sectionFor when battery uAh was low)
I've had this Z1 for about 11 months. I can only get around 2.5h on screen time with regular usage. The battery uAh was only 1848000 Recently it fell to the 1700s. Calibration appears to reduce the value further. The phone seems to heat up in about a minute or two no matter what app is running.
The phone is rooted on stock 4.4.2
I have tried updating to Lollipop before but received an error due to rooting, so I don't think anything changed.

bump

alantay11 said:
bump
Click to expand...
Click to collapse
sounds like it's time for you to replace your battery.

You may try to disable the "input boost frequency"
By default when you toch the screen, cpu frequency of two cores instantly jumps to around 1400 to preventing any lag but it seems to use more power and causing heat
I have disables this and since then I'm no longer have any heat issue and also the battery life is so much better now but you may exprience a little lag while scrolling on heavy web pages but thats all
Btw i'm on .157 and using Kernel Adiutor for cpu tweaks
You may disable this by the app mentioned above or by editing sys.somc.touch_perf_kick=1 from 1 to 0 in buid.prop or adding this line

MI9 Fingerprint CPU Frequency bug

Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.

MysteriousStranger said:
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
Click to expand...
Click to collapse
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)

MysteriousStranger said:
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
Click to expand...
Click to collapse
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.

Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.

kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
This summer when I started to get the pocket photos, before the .27 was released (yes I was among the ones that got it before it was redrawn) I deleted the fingerprints to get rid of the pocket activity due to the non-existing pocket mode. As .27/.28 came with pocket mode I started to use fingerprint again but discovered that face unlock that I had been using was far more convenient and suited me better despite the somewhat lower security rating. I don’t use Gpay, and do not keep top secret stuff on my phone so I’m happy being rid of the fingerprint sensor. The sensitive economic things are protected by pin-code anyway.
So it was not battery time that drove me to ditch the fingerprint sensor, that extra battery time just came as added value for me!

kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
If you notice, the CPU frequency increase occurs randomly after a period of time, not as soon as you turn on the phone, which seems like a bug to me. In addition, the frequency does not settle down again, leading to less standby time available. So I don't really understand how an active fingerprint sensor affects the CPU frequency after a while, and not since the boot.

gerhard_wa said:
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Click to expand...
Click to collapse
If that was the way to be, the frequency should be that high even right after booting.

MysteriousStranger said:
If that was the way to be, the frequency should be that high even right after booting.
Click to expand...
Click to collapse
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!

I noticed this as well right from the first firmware update I used (EEA). It's been fixed after upgrading to Android Q's beta modified by Xiaomi.eu, but I don't see much, if any, improvements in battery life, while also witnessing a giant storage performance regression. Hella disappointed.

gerhard_wa said:
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
Click to expand...
Click to collapse
I get your point but the fact is that in never goes into these lower frequencies again, even after unlocking the phone and idling with screen on, which is strange. I don't get it, really. Plus, you are not able to see in real tilme what process is hooking up CPU resources, as you could normally do in older android versions by using an app.

Ok, if the frequency never locks in the high range again and the scanner starts just as snappy I guess you are right that it must be a bug.
Skickat från min MI 9 via Tapatalk

I disabled fingerprint auth, but I don't seen any improvements in battery life.

I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.

kingbasescu said:
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
Click to expand...
Click to collapse
Try rebooting your device and you will see what the actual idle frequencies should be, then monitor it for a day or two! Can't find what triggers it but It's bugged for sure.

apoklyps3 said:
I disabled fingerprint auth, but I don't seen any improvements in battery life.
Click to expand...
Click to collapse
Reboot your phone after disabling it, otherwise the frequencies stay the same