Sorry for not posting this sooner everyone. But if you want to check out the first DX/D2 Overclocker to hit the market here are a few screens:
{
"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"
}
One of the key features this one carries is you can have as many presets as you want and as an integrated stress test feature to see if your settings are happy or not. There are also some new safety features coming today and something big I can't speak about tomorrow or Wednesday.
If you have any comments or ideas, let me know. I always want to improve things!
Thanks.
I can vouch for this product. Very nice layout and the settings work as advertised. I can't wait to see what you have up your sleeve!
Nice app! I like the presets. Gives you a good place to start from.
Nice app OP!
working for me so far, nice work. i was hoping i wouldnt have to go through the files like in the tutorials...
quadrant was like 1375 or so, now i hit 1485. not bad i think!
How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week
Venc said:
How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week
Click to expand...
Click to collapse
That bar graph you are most often seeing is people running the benchmark "Qaudrant". Go download it from the Market, it is free.
Real time CPU scaling and current speed are in 1.3.2 that just hit the Market. Enjoy.
I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?
The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it
gweedo767 said:
The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it
Click to expand...
Click to collapse
Alright thanks, how long should I let it run?
AsaSpades said:
Alright thanks, how long should I let it run?
Click to expand...
Click to collapse
How long you let it run is up to you.
I typically start it then set it on my desk while I cook dinner/take a shower/do chores etc..
When I am done I check it out and see if it crapped out or not.
Also, I have tried all 3 methods currently available for OC'ing our X's and (in my opinion) this is the best out of them.
Nice user interface, some good starting points for OC'ing and with the latest build you get current/max/min clocks and battery temp.
Now, he just needs to add current voltage so I know what speed and voltage my X is pulling at that time.
OH, and some kind of log would be tits as well.
(Just thinking out loud)
D.
I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message
adammsu said:
I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message
Click to expand...
Click to collapse
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.
debaucher said:
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.
Click to expand...
Click to collapse
i agree, only minor, IF IN FACT that it really has been overclocked the whole time., and isn't dropping up and down all day.
I also have been having the same issues but I thought it was just me.
Sent from my DROIDX using XDA App
AsaSpades said:
I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?
Click to expand...
Click to collapse
I think the problem here is the 1.45 ghz. To increase the Frequency that drastically, you also need to increase voltage. With a voltage setting too low you will lock your phone. The closer you get to a stable VSEL value the more you will be able to do before it locks up. That is why the stress test is so powerful a test to determine if the voltage is appropriate. When at 1.40 ghz your voltage must be close to stable if you can use under lite usage, but if you can only use it lightly, why OC so drastically?
Another App in the market, Droid x/2 Overclock, gives an advised list of frequencies and the VSEL value, and for 1.45 ghz, it advises 82 VSEL as the starting point. which is about 33% more power than it uses at stock frequency (62 VSEL). This is why you said you are tearing through your battery much quicker.
To alleviate the added draw, what I do, is run 2 settings, I leave it undervolted and clocked down to 750 mhz for every day use (barely notice a difference from stock performance) which increases my battery life to 35 hrs + and have a second setting for things like Emulators clocked up to 1.45 ghz running 78 VSEL very stable, never locks up. The added step is worthwhile to me since it both saves the added strain on the processor, Less Heat, and drastically Increases Battery Life.
If you insist on leaving it full blazing 1.45 ghz, get SetCPU (also in the market) and set profiles that can down control power, ie when my screen is off, the CPU is capped at 300 mhz. For the most part the Android OS already controls this pretty decent, but I like to be able to manually control it myself.
I would really like to see the application stop the service after it does it sets the clock after 90seconds.
As it stands now, I force stop it every boot.
Related
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Have you gone into Spare Parts and checked Partial Wake?
stayclean said:
Have you gone into Spare Parts and checked Partial Wake?
Click to expand...
Click to collapse
I did, but it said the only appreciable lock was 3m 25s for Android System (all time.) Dialer was 4s all time. There are no stats for 'time since last boot' or 'time since last unplugged'; I recently rebooted and have the phone currently plugged in.
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
gaan kak said:
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Click to expand...
Click to collapse
You do have the End button Behaviour to sleep right?
its in sparepatrss?
stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Right now I have wi-fi off, with generally average phone service on 3G. Sometimes it dips down to 1 bar or reaches 4, but is usually 2-3.
I have the governor set to 'ondemand', with a min of ~176 and a max of ~714. The brightness is set to auto. I don't know if I have much stuff auto-syncing, is there a way to check if I do? I don't have very many apps installed - I just rooted this afternoon, and this is my first android phone so I'm trying to take it slow.
davidevan said:
You do have the End button Behaviour to sleep right?
its in sparepatrss?
Click to expand...
Click to collapse
Pretty sure in Android, the end button defaults to sleep anyway, so I don't think that really accomplishes much. Maybe try turning off 3G when not using the phone actively? That will drain the battery a bit.
stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Yeah, you're right...uptime has nothing to do with sleeping.
To the OP...reboot the phone then let the phone run for about 1.5 - 2 hours or so without using it. Then go to Menu - Settings - About phone - Battery use. Then tap the graph at the top where it shows your time and compare your Awake time bar to your screen on time bar. They should be similar, with a bit more in the awake time depending on wat is set to sync.
To be honest, there is no fix to be honest. I've had this problem on many occasions and it fixes itself automatically whenever it wants to.
Sent from my HERO200 using Tapatalk
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
laie1472 said:
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
{
"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"
}
make it sleep=
just give it some nice warm hot cocoa with a dab of whisky, works like a charm
ranger61878 said:
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
Click to expand...
Click to collapse
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
I too am noticing lots of awake time on my battery graph with CM7 RC4. I rebooted about an hour ago, and haven't touched my phone until taking these screenshots. (Sorry for hosting them offsite, the network here blocks the xda uploader.)
http://img828.imageshack.us/slideshow/webplayer.php?id=sparepartspartialwakesil.png
One thing I found very interesting is that even though my phone shows nearly 50 minutes of 'awake' time, my battery still reads 100% even though it's been unplugged the entire time.
sleepy
laie1472 said:
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I haven't a clue...maybe JM can shed some light for us
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
I have always used 176/729 ondemand and had no issues with music and get great battery life (and my phone sleeps ).
il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
laie1472 said:
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
il Duce said:
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
Click to expand...
Click to collapse
Here's what I'm getting at. If the frequency constantly changes due to the users demand or cpu load and maxes out at the selected frequency but doesn't go below the selected frequency either. Then lets say its in the middle of scaling up or down and the user hits the end button, then what frequency would the cpu be at??? Being that it's no way of telling if it hit the min or the max user defined choice. So if the user has a min of 352 and a max of 768 and this were to happen. Couldn't the kernel then be put to sleep at a frequency of 768 ??? After all its still in line with the user defined settings. With apps like over clock widget and set/cpu you could select the off screen clock settings but being as those apps conflict with the native app how can the user be sure of what the off screen frequency is set to if this were the case???
Yea it's Me Again With the
Modified Hero
[KERNEL] mOCk kernel v1.6.12 for MIUI
Credit:
llorn / mantera
originally made for the Triumph. Works on both CacingKalung's MIUI 2.2.3 and elol's Galnet MIUI mod for the Mi410 and supports 2 way call recording!
{
"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 is a first on MIUI for me
Undervolts great too and has no performance issues till now. Been using it for the last week
how to use undervolt settings ? i hope that will improve the battery life
Edit .: cant get the file ..says its not accessble or removed ??
ok i got it installed !!
used this link
could you tell me how to set the undervolt settings.. getting no frills now
Edit:got incredicontrol set up voltages
Got no frills set up governors n I/o scheduler
Lets see how it goes
apart from 2 way call recording, what extra advantages of this KERNEL. specially in terms of gaming......
how about incoming call valume?
undervolting now working ...its not getting saved !! gives the same default values once rebooted
Zailer. I reckon you haven't used Incredicontrol before
Everything is working fine for me.
So far I haven't encountered the call volume bug but it is indeed lower in volume than that on rc3.
Gaming performance is inferior to rc3 but better than MIUI 1.1.x but the phone is very responsive at even lower clocks.
No other advantage though.
You get 2 way call recording in rc3 too (infact better in the latter since amr recording and in call controls are not working in MIUI).
I haven't been successful with 2wcr in MIUI prior to this. Ymmv.
Sent from my Spice MI-410 on MIUI 2.2.3
thanks for the response.
but whats the big deal in using incredicontrol ? just set the undervolting as the developer told in his thread rite(675,700..). i did it . but when i reboot and check them its shows the default value (900 ,900.. )
should i believe from what you have just told ...that these incredicontrol will show the normal values even when the actual undervolt is working ??
i have tried voltage controll also .. its says undervolting is not allowed in this kernel
may be you can help me by sharing the right way to do things
First check in Settings -> about phone whether the kernel update has been applied or not.
Incredicontrol should remember the voltage values if the set on reboot option is checked.
I am using even more aggressive undervolt settings than the ones suggested by the kernel dev.
Shall post some screenshots later.
Hope this helps
Sent from my Spice MI-410 on MIUI 2.2.3
Testing this kernel now, using CacingKalung's Rom build.
I'm more interested in battery life so I'll be playing around with that, previously on the pure CacingKalung build, I managed to reach 13 hours with undervolting involved, but on the smartassv2 governor. I have Sync all running, Trillian running, I use Navigation, Whatsapp, Wifi and 3g nearly 24/7.
Will be trying to break that even further this time around with InteractiveX. For those interested, my device seems to be able to take much lower voltages, here's what they are.
61440: 600
122880: 600
245760: 600
368640: 600
460800: 600
576000: 850
652800: 850
768000: 850
806400: 900
921600: 925
1024000: 975
1113000: 1000
1209600: 1075
1305600: 1125
1401600: 1150
Will try to reach lower volts with this ROM and report back in.
Btw, IncrediControl works for me fine, saves my voltages FYI.
Remember to reset your battery stats after you flash the kernel. I noticed some significant battery drain before that.
Nice uv :thumbup:
Btw, I have been doing 1.4 ghz @ 1100mv, 1.5 @ 1150 and 1.6 @ 1200
Sent from my Spice MI-410 on MIUI 2.2.3
Guys this is killing me ...
@freerad
Thanks, I appreciate u helping me in detail.. but I have surely tried using "set on boot" and its showed in the about rom page as mock
Ok now am back to ck's rom and mock kernel. I hope the link I downloaded from is the same kenel
Sent from my CSL-MI410
I tried lower before on SpeedDemon Kernel, I haven't tried to see if it's possible on this one, will do soon.
The one thing i find though is that at the speed that I type, the powersaving governors don't work for me, they don't seem to be very able to keep up with my typing speed, so for now I'm back to SmartassV2.
Will try to try for lower volts, for now the results of this kernel will take a while, I usually do daily use testing.
hamsteyr said:
Testing this kernel now, using CacingKalung's Rom build.
I'm more interested in battery life so I'll be playing around with that, previously on the pure CacingKalung build, I managed to reach 13 hours with undervolting involved, but on the smartassv2 governor. I have Sync all running, Trillian running, I use Navigation, Whatsapp, Wifi and 3g nearly 24/7.
Will be trying to break that even further this time around with InteractiveX. For those interested, my device seems to be able to take much lower voltages, here's what they are.
61440: 600
122880: 600
245760: 600
368640: 600
460800: 600
576000: 850
652800: 850
768000: 850
806400: 900
921600: 925
1024000: 975
1113000: 1000
1209600: 1075
1305600: 1125
1401600: 1150
Will try to reach lower volts with this ROM and report back in.
Btw, IncrediControl works for me fine, saves my voltages FYI.
Click to expand...
Click to collapse
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
mi410 said:
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
Click to expand...
Click to collapse
no, when I opened Incredicontrl after sometimes, I found some default values, not that lower values that I set. though my phone did not reboot.
need to check with checking 'set on boot'
edit: no matter what I do, voltage settings get back to some default setting,
mi410 said:
no, when I opened Incredicontrl after sometimes, I found some default values, not that lower values that I set. though my phone did not reboot.
need to check with checking 'set on boot'
edit: no matter what I do, voltage settings get back to some default setting,
Click to expand...
Click to collapse
Yep + incredicontrol does not save the custom settings
That's odd then, my IncrediControl works just fine.
You should note that you should allow your IncrediControl to completely load before launching it. By this, I mean WAIT for the sign that says "Incredicontrol has been granted superuser permissions"
For me it seems that it takes a while but it happens, just not instantly. If you load IncrediControl too early, you'll see the default stock voltages.
Anyway, managed to pull 14 hours.
Reverted back to SmartAss v2, running on 1300 Mhz. My system doesn't seem to like lower volts, so these are the same volts as before. I seem to be able to work fine with even just 1200 so I may just clock it back down and try that instead.
hamsteyr said:
That's odd then, my IncrediControl works just fine.
You should note that you should allow your IncrediControl to completely load before launching it. By this, I mean WAIT for the sign that says "Incredicontrol has been granted superuser permissions"
For me it seems that it takes a while but it happens, just not instantly. If you load IncrediControl too early, you'll see the default stock voltages.
Click to expand...
Click to collapse
Exactly
I too believe this is what you guys were doing wrong.
I am using my phone successfully with slightly different clocks but in some ways more aggressive and am getting 30-40% better battery life!
i.e. I still have around 30% charge left when I return home from work.
Include 2 hours of very heavy usage during my commute
Prior to this, I could barely get home with 10% charge and often my battery would discharge completely.
I have set up Tasker to overclock and undervolt along with some handy shortcuts.
I abstained from using apps like SetCPU since I have Tasker running all the time and didn't want to add another background service.
I use the context to undervolt as soon as the display is off and to overclock as soon as the display is turned on. Seems to do the trick
My undervolt / Sleep settings : 61440-1024000 Hz on Interactive governor
My overclock / Wake / Boot settings: 1024000-1612800 Hz on smartass2 governor
My voltage chart:
61440: 600
122880: 700
245760: 750
368640: 800
460800: 850
576000: 850
652800: 850
768000: 850
806400: 900
921600: 950
1024000: 975
1113000: 1000
1209600: 1050
1305600: 1075
1401600: 1100
1516800: 1150
1612800: 1200
Most of the time with these settings, my phone is on 64MHz, 1024MHz and 1.6 Ghz and is quite responsive.
Shall do an overnight cpu-spy test
For games like Blood and Glory, I jack up to 1.6 GHz at performance mode using a Tasker shortcut.
Hope this helps
mi410 said:
OMG ! it is so aggressive settings. installed the kernel and applied these voltage settings. working fine, no considerable lag or whatsoever. but I am still afraid of checking 'set on boot'
Click to expand...
Click to collapse
If your phone doesn't not boot or messes up, just press down the menu button repeatedly while booting and you'll get into safe mode. Then you may clear data in application settings for IncrediControl
ok this time incredicontrol worked. but exactly how , I don't know. I just restarted the phone, charged to 100 % and then then applied these voltage settings but this time I didn't change all at a time. rather I did change one or three at the most at a time and press 'apply' each time until all settings were done. applied 'set on boot' also. need to check the battery backup now.
Trying to use that on mine, clocking 1.2 Ghz max on SmartAssV2, and 64 -> 768 Mhz Interactive X on screen off.
I'm getting some aftermarket 1600 Batteries as well, I'll see what I can get with them after this test.
Edit: It seems that the max that I'm able to reach is just 14 hours on a 1400 mAH battery, not too bad I suppose. Will post more when I get my 1600.
Welcome to Myrt Torture Tester.
As always, this app is BETA, expect bugs. Tested on Stock GB/HP Extreme & guestekrnL, CM7/Etana, CM9/HP ICS & Harsh.
Will only work on OC/UV-kernels.
It's primarily intended as a tester to find your stable frequencies and voltages, but can also be used as a battery-life tester and a rough benchmark.
This app comes with no more support than the 2nd post. If you don't know how to use it after reading that you don't need it.
Using this app, you will be capable of causing actual damage to your device. I take no responsibility for any consequences.
This app shall under NO CIRCUMSTANCES be included in any ROM, or uploaded any other place than this post.
Changelog
0.5.6 - Fixes crash when system is unresponsive for long periods.
0.5.5 - Keeps reading the current cpu-frequency throughout the test. (Some beta kernels unexpectedly change frequencies during the test, this allows you to see it.)
0.5.4 - CM7-compatability-fix.
0.5.3 - Fixes frequency not being set on guestekrnL.
0.5.2 - Fixed links on about page.
0.5.1 - Plays nice on non-oc kernels.
0.5.0 - First BETA-release
HOW TO USE:
In its simplest form, the app is a benchmark. You start a CPU-test at a specific frequency for a specific time-period and get the average Mflops-result. If you are going to compare different kernels, it will give you a normalized to 1Ghz result as well. Different kernels usually have different frequency-tables, so test them at the closest steps you can find, then compare the normalized result.
The more useful aspect of it is to test if a specific frequency is stable at a specific voltage. The app only allows to test the frequencies in the voltage table - because if it is stable at those frequencies it will be stable at all other frequencies which fall within those voltage-steps. If you have undervolted too much, the phone will usually reboot pretty quickly. If you have undervolted "on-the-edge", the phone will likely freeze. If you have undervolted so that it is basically stable, but sometimes fails, you'll either get a crash to the desktop or MTT will inform you of a calculation error. If you are testing for stability you need to test for at least 60 minutes to have any confidence in the result, I've had several tests fail after 45-50 minutes.
It can also be used to see what impact, if any, undervolting has on the processors' power-consumption. After you have made sure a frequency/voltage-pair is stable, you can run a battery-test and compare it to an identical test at stock voltage. This will simply run from a full(ish) battery to a certain battery percentage, and give you how long it was able to run. Since the battery-percentage is pretty loosely coupled to the actual battery-charge, it will also give figures for consumption per minute or second. This kind of test should also be run over a long a period as possible to get accurate results. Measuring from 100% to 90% will only give you an indication, prone to error. You can not compare a test between, say 100->50 and 100->20, because the discharge rate varies with the charge-level.
For most accurate testing and benchmarking: enable flightmode, unplug the device, freeze any apps which may run in the background, uninstall everything you don't need, wait 3 minutes after booting before testing, do not touch the screen or move the device while a test is running. Even then there are Android quirks which will cause some variation in the results. Therefore the same test should be repeated as many times as you can afford.
The major enemy of stability, assuming you have enough voltage, is heat. Make sure to test the device under the same conditions as it will be used. If you're going to overclock on a hot summer's day, test it on a hot summer's day. MTT dims the screen to minimize the impact it has on the battery and heat-generation, be aware that your device will be hotter when the screen is at normal brightness.
Stability tests should also be performed at different battery-levels. If your device is stable when the battery is fully charged, it does not automatically mean it will be stable when it is almost discharged.
MTT logs all succesfull tests (max 200 lines.) If you enable "Store log on sdcard" in preferences the log will be saved to /sdcard/MTT_Log.txt.
Known issues:
o Sometimes the device will give you half the score you should get. I do not know if this is a kernel or android-bug, but it seems that both test threads get scheduled to run on the same core, and the second core goes unused, even when it is active. Exiting the app and starting it again does not help usually, but killing it sometimes does. Rebooting is always an option.
o Not a "known issue", but this app lets you under- and overvolt in 5mV steps. Different kernels may handle this differently, either not undervolting at all, or adjusting it to the nearest 25mV step. It has worked on the kernels I have tried, but there are too many kernels out there to be sure.
TrymHansen said:
HOW TO USE:
In its simplest form, the app is a benchmark. You start a CPU-test at a specific frequency for a specific time-period and get the average Mflops-result. If you are going to compare different kernels, it will give you a normalized to 1Ghz result as well. Different kernels usually have different frequency-tables, so test them at the closest steps you can find, then compare the normalized result.
The more useful aspect of it is to test if a specific frequency is stable at a specific voltage. The app only allows to test the frequencies in the voltage table - because if it is stable at those frequencies it will be stable at all other frequencies which fall within those voltage-steps. If you have undervolted too much, the phone will usually reboot pretty quickly. If you have undervolted "on-the-edge", the phone will likely freeze. If you have undervolted so that it is basically stable, but sometimes fails, you'll either get a crash to the desktop or MTT will inform you of a calculation error. If you are testing for stability you need to test for at least 60 minutes to have any confidence in the result, I've had several tests fail after 45-50 minutes.
It can also be used to see what impact, if any, undervolting has on the processors' power-consumption. After you have made sure a frequency/voltage-pair is stable, you can run a battery-test. This will simply run from a full(ish) battery to a certain battery percentage, and give you how long it was able to run. Since the battery-percentage is pretty loosely coupled to the actual battery-charge, it will also give figures for consumption per minute or second. This kind of test should also be run over a long a period as possible to get accurate results. Measuring from 100% to 90% will only give you an indication, prone to error. You can not compare a test between, say 100->50 and 100->20, because the discharge rate varies with the charge-level.
For most accurate testing and benchmarking: enable flightmode, freeze any apps which may run in the background, uninstall everything you don't need. Even then there are Android quirks which will cause some variation in the results. Therefore the same test should be repeated as many times as you can afford.
The major enemy of stability, assuming you have enough voltage, is heat. Make sure to test the device under the same conditions as it will be used. If you're going to overclock on a hot summer's day, test it on a hot summer's day. MTT dims the screen to minimize the impact it has on the battery and heat-generation, be aware that your device will be hotter when the screen is at normal brightness.
Stability tests should also be performed at different battery-levels. If your device is stable when the battery is fully charged, it does not automatically mean it will be stable when it is almost discharged.
MTT logs all succesfull tests. If you enable "Store log on sdcard" in preferences the log will be saved to /sdcard/MTT_Log.txt.
Click to expand...
Click to collapse
Really interesting! Big thanks
Sent by LG Optimus 2x
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc results in that new max freq being used all the time in the program.
kfallz said:
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc also results in that new max freq being used all the time in the program.
Click to expand...
Click to collapse
Ok, thanks for the feedback. Which version of guestekrnL? I'm mainly using that myself, works here on 1.7.
EDIT: Ok, I've found the reason. I had disabled the 00cpufreqenabler script (to simulate other kernels), but it didn't work after I enabled it. Will release a fix as soon as I can override the permission properly.
kfallz said:
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc results in that new max freq being used all the time in the program.
Click to expand...
Click to collapse
App updated to 0.5.3 - fixes the issue where frequency is not set on guestekrnL.
TrymHansen said:
App updated to 0.5.3 - fixes the issue where frequency is not set on guestekrnL.
Click to expand...
Click to collapse
Giving the new version a try, and not that it matters now but I'm using 1.7.0t2
Yea working fine now
Updated to 0.5.4 - Now the sliders behave properly on CM7.
Myrt, do you think that we have more than one different hardware inside our phones? Because the results are way to different from one ppl to another, for example, Temasek can't OC even to 1.1GHz, and Vadonka puts at 1.4GHz without the burn, with the tests, I get to 70ºC in 2min with 1.1GHz, but the strange thing, is that the phone doesn't lags or anything to show that it haves an high-temp. Did you have some screen of the test in your own phone? I have exchanged my first phone because it always get too hot for me, my second gets hot always when I try to play any game.
chaozbr said:
Myrt, do you think that we have more than one different hardware inside our phones? Because the results are way to different from one ppl to another, for example, Temasek can't OC even to 1.1GHz, and Vadonka puts at 1.4GHz without the burn
Click to expand...
Click to collapse
No, we have pretty much the same hardware, specification-wise. It is very common to have different tolerances for speeds and voltages. I'm pretty sure that the moment Vadonka tries my app at 1.4Ghz, he too will get a hot CPU.
, with the tests, I get to 70ºC in 2min with 1.1GHz, but the strange thing, is that the phone doesn't lags or anything to show that it haves an high-temp.
Did you have some screen of the test in your own phone? I have exchanged my first phone because it always get too hot for me, my second gets hot always when I try to play any game.
Click to expand...
Click to collapse
I didn't take a screenshot, if that is what you ask, I have the app abort the test at 72C, and the temp falls quickly back to normal. I don't even have vadonkas kernel installed anymore, I'm a stock man, installed CM7 just to make the app compatible.
However, I guess we can encourage people to post their temps and frequencies here, in this thread. If anyone manages to run 1.4Ghz for more than 5 minutes and not reach 70C I'll be impressed. (I do all my temp-testing when plugged in though, probably easier when unplugged.)
TrymHansen said:
No, we have pretty much the same hardware, specification-wise. It is very common to have different tolerances for speeds and voltages. I'm pretty sure that the moment Vadonka tries my app at 1.4Ghz, he too will get a hot CPU.
I didn't take a screenshot, if that is what you ask, I have the app abort the test at 72C, and the temp falls quickly back to normal. I don't even have vadonkas kernel installed anymore, I'm a stock man, installed CM7 just to make the app compatible.
I had these temps in Spica HP kernel, so stock rom, CM7 with Vadonka, I saw an 84ºC (leave my brother playing in the phone, and he said to me that the phone was hot haha)
Click to expand...
Click to collapse
TrymHansen said:
However, I guess we can encourage people to post their temps and frequencies here, in this thread. If anyone manages to run 1.4Ghz for more than 5 minutes and not reach 70C I'll be impressed. (I do all my temp-testing when plugged in though, probably easier when unplugged.)
Click to expand...
Click to collapse
If we can't run 1.4GHz for me than 5min without reaching 70ºC, and 70ºC is the maximum temp, we can't play or let the phone in the frequency for daily use?
chaozbr said:
If we can't run 1.4GHz for me than 5min without reaching 70ºC, and 70ºC is the maximum temp, we can't play or let the phone in the frequency for daily use?
Click to expand...
Click to collapse
Well, no, I'm not saying that, there are too many unknowns.
1) We don't know if the reported temp is correct.
2) We dont' really know the max temp for tegra2. (The 70C figure is not from an official source.)
3) This app is meant to test stability, so temps will get as hot as possible. A game will most likely not stress the CPUs quite as much.
But, all that taken into consideration, 1.4Ghz is probably too high for sustained operation. It will probably be fine for normal use, where the CPUs get to rest once in a while, but not for prolonged CPU-heavy tasks (which this app demonstrates.) That being said, this app is designed to produce as much heat as possible to test stability.
It took me 41sec till the CPU reached 70°C from 40°C on 1408MHz using latest beta 3.0.y etana.
Tapatalk 2-vel küldve az én Optimus 2X-ről
Thanks for this, this app looks great!
I usually don't UV as it introduces some instability to my device even at low -UV values which isn't worth the rather small gain in battery life - but it's still good to know that this app existis if I'll change my mind someday
tonyp said:
Thanks for this, this app looks great!
I usually don't UV as it introduces some instability to my device even at low -UV values which isn't worth the rather small gain in battery life - but it's still good to know that this app existis if I'll change my mind someday
Click to expand...
Click to collapse
Yeah, I don't usually undervolt either, I carry spare batteries, and the fear of unstability was always lurking when I did. (I did make an undervolt app afterall, had to test it.)
So with this app my hope is that many myths will be dispelled - using this people should be able to find out what they need.
(A few weeks ago I had forgotten the batteries in a bag in a hotellroom, far away. I really, really, really needed 20 extra minutes of battery-life then. So now I will probably undervolt to voltages I know are safe, just in case something similar should happen. Sometimes 5 minutes make all the difference in the world.)
I cannot set any other V (no UV or OV) using Temasek 99 with latest Vadonka Beta 11.05. Kernel. The program always crash after the 2sec warmup.
Gesendet von meinem Optimus 2X mit Tapatalk 2
kennbo82 said:
I cannot set any other V (no UV or OV) using Temasek 99 with latest Vadonka Beta 11.05. Kernel. The program always crash after the 2sec warmup.
Gesendet von meinem Optimus 2X mit Tapatalk 2
Click to expand...
Click to collapse
Ok, I need some more info I think. First of all, is the app the latest version? If yes, do you get a superuser message the first time you start the app after a reboot? Which values do the bottom sliders show right after starting the app for the first time?
Tried it myself today on temasek 100 with both 3.0.31 OC and the latest beta (OC-only of course), worked on both for me. One installation however failed, and I had to repair the system-partition before the app would work again. (Superuser pretended to give access, but /system wasn't really writable, so it failed.) Check which apps are listed in superuser, if you see the same app listed a lot of times, that's your problem.
TrymHansen said:
Ok, I need some more info I think. First of all, is the app the latest version? If yes, do you get a superuser message the first time you start the app after a reboot? Which values do the bottom sliders show right after starting the app for the first time?
Tried it myself today on temasek 100 with both 3.0.31 OC and the latest beta (OC-only of course), worked on both for me. One installation however failed, and I had to repair the system-partition before the app would work again. (Superuser pretended to give access, but /system wasn't really writable, so it failed.) Check which apps are listed in superuser, if you see the same app listed a lot of times, that's your problem.
Click to expand...
Click to collapse
Sooorry I'm too stupid, tried the 216 Mhz only which is too slow for the total phone use and test. Program works fine!
Again sorry and thanks for the tool
kennbo82 said:
Sooorry I'm too stupid, tried the 216 Mhz only which is too slow for the total phone use and test. Program works fine!
Again sorry and thanks for the tool
Click to expand...
Click to collapse
Ok, good to know, thanks. I will have to look into it anyway, it shouldn't crash even at 216Mhz, but I'll take that as low-priority, in other words tomorrow ;-)
Our phones have become an increasingly more important part of our everyday lives. They have become more and more powerful and the batteries drain even more quicker. The nexus 5 is a powerful device it has a quad core CPU and 2 GB of ram and It can still keep up with most of the new flagships that have come out this year. However with great power come great battery drain. To follow this guide you will need a rooted Nexus 5, and a custom ROM installed I'm using Euphoria OS. (This guide has many useful tips it can be used for other devices not just the nexus 5)
1. Get rooted
You can find help on rooting the nexus 5 all over the Internet by doing a simple Google search, or even here on XDA
2. Install a Custom ROM
Although you don't really need to install one I recommend doing it because they offer extra features. That can help you save battery. I like Euphoria OS.
3. Install a custom kernel
There are many good ones out there I'm using elemental x. Although you could also use Franco or code-blue.
4. Get an app to manage your kernel.
You will need some kind of app to manage your kernel again there are many good ones out there like "kernel Tweaker", I'm using Elemental X which is a paid app but it is definitely worth it.
5. Change CPU settings
Go to the CPU section of the Kernel Manager app and set the governor to elemental x if you are not using the elemental x kernel set it to conservative.
Set the max CPU frequency to less than or equal to 1574MHz, and set the min CPU frequency to 300MHz. Set the max screen of frequency to 729MHz.
6. change the LCD display settings
Go to the graphics section and set the minimum brightness settings to 1. Don't go below one otherwise the display won't light up.
7. Undervolt
Under volt your CPU so it uses less juice and runs much cooler. If you undervolt too much than your phone might reboot randomly
8. Turn off the LTE
Other than your display LTE consumes the most battery. This is why I suggested flashing a custom rom. You can add a toggle to the quick settings menu for LTE so when you need LTE you can turn it on. Personally I can get by with 3G and HSPA+.
9. Edit wifi settings
Go to the settings menu and hit wifi, then hit the three dots to go into advanced wifi settings and turn off scanning always available and turn on avoid poor connections.
10. No animated wallpapers
Turn of all live , animated, or active wallpapers. Whatever it may be called on your device /rom.
Your done.
Now you can hopefully use your device for a couple for hours longer. Let me know your results.
I cannot be held responsible if damage is caused to your device.
Besides screen...3g is placed second...followed by lte...follwed by wifi..then 2g. In battery consumption
Cool little guide. Will help the lesser experienced users starting to learn the ropes of everything
doctor_droid said:
Besides screen...3g is placed second...followed by lte...follwed by wifi..then 2g. In battery consumption
Click to expand...
Click to collapse
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
apatel321 said:
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
Click to expand...
Click to collapse
Although controversial ...i still support my answer
http://www.electronics-eetimes.com/...phones.html?news_id=222920157&cmp_id=7&page=0
Do a more wiki abt envelop tracking..and nexus 5 has that chip
But nothing specific has been given...
apatel321 said:
I did some research on this and I tried it out myself for a few days before I posted this. And my research and my experience tell me that LTE does drain more battery than 3G or HSPA+. How good or bad your signal is can also impact the battery.
Click to expand...
Click to collapse
In the Anandtech review they showed that under identical circumstances LTE is slightly more efficient than 3G on this device. Close enough that in practice it should come down to whichever has the better signal.
{
"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"
}
bblzd said:
In the Anandtech review they showed that under identical circumstances LTE is slightly more efficient than 3G on this device. Close enough that in practice it should come down to whichever has the better signal.
Click to expand...
Click to collapse
OK I've been proven wrong however you could still set you preffered network mode to 2g and toggle LTE when you need it. (This might be a bit too slow for some people.)Didn't know that its that much more effient my last phone was a sgs2 skyrocket and turning of LTE made a difference of day and night I'm battery. So I continued to do the same with my nexus 5
apatel321 said:
OK I've been proven wrong however you could still set you preffered network mode to 2g and toggle LTE when you need it. (This might be a bit too slow for some people.)Didn't know that its that much more effient my last phone was a sgs2 skyrocket and turning of LTE made a difference of day and night I'm battery. So I continued to do the same with my nexus 5
Click to expand...
Click to collapse
Sgs2 skyrocket didnt had envelop tracking chip...the first qualcomm device to have it was sgs5 mini
i have samsung note right now , my previous device N5 is the worst compare to my note according to battery
apatel321 said:
Our phones have become an increasingly more important part of our everyday lives. They have become more and more powerful and the batteries drain even more quicker. The nexus 5 is a powerful device it has a quad core CPU and 2 GB of ram and It can still keep up with most of the new flagships that have come out this year. However with great power come great battery drain. To follow this guide you will need a rooted Nexus 5, and a custom ROM installed I'm using Euphoria OS. (This guide has many useful tips it can be used for other devices not just the nexus 5)
1. Get rooted
You can find help on rooting the nexus 5 all over the Internet by doing a simple Google search, or even here on XDA
2. Install a Custom ROM
Although you don't really need to install one I recommend doing it because they offer extra features. That can help you save battery. I like Euphoria OS.
3. Install a custom kernel
There are many good ones out there I'm using elemental x. Although you could also use Franco or code-blue.
4. Get an app to manage your kernel.
You will need some kind of app to manage your kernel again there are many good ones out there like "kernel Tweaker", I'm using Elemental X which is a paid app but it is definitely worth it.
5. Change CPU settings
Go to the CPU section of the Kernel Manager app and set the governor to elemental x if you are not using the elemental x kernel set it to conservative.
Set the max CPU frequency to less than or equal to 1574MHz, and set the min CPU frequency to 300MHz. Set the max screen of frequency to 729MHz.
6. change the LCD display settings
Go to the graphics section and set the minimum brightness settings to 1. Don't go below one otherwise the display won't light up.
7. Undervolt
Under volt your CPU so it uses less juice and runs much cooler. If you undervolt too much than your phone might reboot randomly
8. Turn off the LTE
Other than your display LTE consumes the most battery. This is why I suggested flashing a custom rom. You can add a toggle to the quick settings menu for LTE so when you need LTE you can turn it on. Personally I can get by with 3G and HSPA+.
9. Edit wifi settings
Go to the settings menu and hit wifi, then hit the three dots to go into advanced wifi settings and turn off scanning always available and turn on avoid poor connections.
10. No animated wallpapers
Turn of all live , animated, or active wallpapers. Whatever it may be called on your device /rom.
Your done.
Now you can hopefully use your device for a couple for hours longer. Let me know your results.
I cannot be held responsible if damage is caused to your device.
Click to expand...
Click to collapse
We already have two threads dedicated to battery stuff. Not sure why we would need another.
http://forum.xda-developers.com/google-nexus-5/general/nexus-5-battery-results-t2509132
http://forum.xda-developers.com/google-nexus-5/help/battery-life-help-troubleshoot-battery-t2785128
From that same AT article:
"Nexus 5 has ... QFE1100 envelope tracker for its cellular power amplifiers, which lowers power consumption by up to 20 percent"
Interestingly, that same article demonstrates close to 9 hours of wifi surfing time, presumably with screen on. I have yet to get anywhere close to that.
testinguser said:
From that same AT article:
"Nexus 5 has ... QFE1100 envelope tracker for its cellular power amplifiers, which lowers power consumption by up to 20 percent"
Interestingly, that same article demonstrates close to 9 hours of wifi surfing time, presumably with screen on. I have yet to get anywhere close to that.
Click to expand...
Click to collapse
It's not a real world usage test but one designed to put all phones on an equal footing so they can be accurately compared.
For instance their test is running a script that opens up new web pages every 30 seconds and has all background services disabled. This eliminates unpredictable drains and allows the test to be repeatable.
I was struggling with my Nexus 6 performance very badly. It was almost unusable. First, its battery used to drain fast. I felt the low performance was due to battery. So I replaced the battery. I also factory reset the phone. After factory resetting the phone was at least smooth. But as soon as I install some apps (not a lot of them), it started to slow down. I used to run 200+ apps without any lag on my Nexus 6. But now it was struggling with 50+ apps. So I felt it must be stock Naugat. So I went to flash lineageOS 15.1 (my first successful experience with MODing android, earlier I bricked one phone and after that never thought of trying it out again). The performance is a bit improved. But its definitely not smooth. Also this is the case with no extra apps installed. Only basic gapps are their. So I am getting fishy about whats going on. So I googled and found this thread.
Someone their said that its working on only two cores!!! And something immediately clicked to me what I have seen but never observed well. Recently I bought poco f1. Just to do performance comparison, I installed antutu on both Nexus 6 and poco. Also whenever I opened Antutu CPU monitor, it always showed two cores are sleeping. That was not the case with poco. All cores are always working. For example, I just charged my Nexus 6 battery to 100%. Also its not in battery saver. Still it says two cores sleeping and only two cores active:
{
"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"
}
People at reddit said installing custom kernel fixes this issue. There are some recommendations on reddit page: Franco, b14ckb1rd and elementalX. I googled and found that there is elementalX app in play store which says to automate whole process. I bought it for ₹250 and installed, backed up current kernel and installed elmentalX. It went into TWRP and installed elementalX successfully. But now my lineageOS is not booting up. It is animating its icon for last 15 minutes? Is it bootloop. I didnt read much earlier about kernels. I felt as offical app installs it, it must be working one. But now reading this thread, it seems that my lineageOS got screwed again. So I have some questions:
1. Is my lineageOS screwed now?
2. If yes what should I do? Flash backed up kernel through TWRP. If yes, how? I never done. Is the procedure same as installing custom ROM? Putting kernel zip in phone and then installing ZIP from TWRP?
3. Is their any custom kernel out their compatible with lineageOS 15.1 which can enable my CPUs two sleeping cores?
Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.
After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor,
hotplug mpdecision, I enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also can all feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life?
(Will be testing battery life soon for few days.)
Mahesha999 said:
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.)
Click to expand...
Click to collapse
I don't know much about LOS and how close it is to AOSP but in ABC ROM you can go to Settings --> Battery --> click three dots in upper right corner --> select Battery Optimization to set what apps run in the background.
Mahesha999 said:
Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.
Click to expand...
Click to collapse
- Install the latest LOS nightly 20180926
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision
if that still isn't fast enough, install this custom kernel:
https://forum.xda-developers.com/nexus-6/development/testers-oreo-8-1-custom-kernel-t3798205
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision and CPU hot plugging