[Kernel] [.38.8] intersectRaven's Kernel (AVS/CAVS)01/08/2011 22:00
- Thread starter intersectRaven
- Start date
- Status
after spending time reading all those kernel thread, i decided to try intersectRaven kernel and now running on 850mV... didnt wipe cache... just flash... and let see how it works. Thanks for your great job intersectRaven.
Re: [Kernel - .33.2]intersectRaven's Kernel 04/12/2010 10:39pm
So far 800 runs fine but my batt is horrible. Charged it all night off and now at 93% after 1 hour. Went on the web with wifi for 2 mind then shut it off. But it runs stable
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
So far 800 runs fine but my batt is horrible. Charged it all night off and now at 93% after 1 hour. Went on the web with wifi for 2 mind then shut it off. But it runs stable
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am. 
Running on Enom and 875mV
Battery life average: 5%drop / 2hrs.
Awesome?! Ill get you some beer this Friday raven. Thanks.
Running on Enom and 875mV
Battery life average: 5%drop / 2hrs.
Awesome?! Ill get you some beer this Friday raven. Thanks.
I am.
Running on Enom and 875mV
Battery life average: 5%drop / 2hrs.
Awesome?! Ill get you some beer this Friday raven. Thanks.
What are you running that you get such good results!
Give juicedefender, automatic task killer and advance task killer a try. Set your Home screen Widgets refresh interval longer.
Using JuiceDefender and it CLAIMS I am saving >2x battery life but I don't see ANY difference. I also use advance task killer but I'll try automatic task killer.
Juicedefender helps when you are on standby.
I believe that battery life ultimately depends on how much you use your phone and what you use it for. UV or AVS helps out on moderate to low use. If you constantly hammer your phone, no matter what ROM your on or how much undervolted you are wont make a difference, typical smartphone problem. It's a USE to STANBY ratio I guess.
I believe that battery life ultimately depends on how much you use your phone and what you use it for. UV or AVS helps out on moderate to low use. If you constantly hammer your phone, no matter what ROM your on or how much undervolted you are wont make a difference, typical smartphone problem. It's a USE to STANBY ratio I guess.
STOP!!! using task killers! They are not needed on android, your just wasting battery more.
I am very pleased with the stability of the latest build. It seems that the compiler optimization I did was really the root of the problem. Good thing I keep a detailed changelog of what I changed back then.
Is this a proven fact? Can you please direct me to where it says turning off applications that run in the background drains more battery. Thanks.
Here is some raw data:
JuiceDefender is ~2.4x
SetCPU profiles on ondemand & standby 245/245
G-mail Push
TouchDown 15 minute pull
2010 Apr 13 08:11:35 100 Came off the charger
2010 Apr 13 08:16:35 99
2010 Apr 13 08:21:35 99
2010 Apr 13 08:26:35 98
2010 Apr 13 08:31:35 97
2010 Apr 13 08:37:56 96
2010 Apr 13 08:42:46 95
2010 Apr 13 08:47:46 95
2010 Apr 13 08:52:47 95
2010 Apr 13 08:57:47 95
2010 Apr 13 09:02:46 95
2010 Apr 13 09:08:49 94
2010 Apr 13 09:13:42 93
2010 Apr 13 09:18:42 92
2010 Apr 13 09:23:42 91
2010 Apr 13 09:28:42 91
2010 Apr 13 09:33:42 91 Turned off BT/WiFi/3G
2010 Apr 13 09:38:42 91 Phone call 9:37-9:43am
2010 Apr 13 09:43:42 89
2010 Apr 13 09:48:42 89 Crash/reboot 9:50am
2010 Apr 13 09:54:59 88
2010 Apr 13 09:59:52 88
2010 Apr 13 10:04:52 88
2010 Apr 13 10:09:52 88 Crash/reboot 10:13am
2010 Apr 13 10:17:05 87
2010 Apr 13 10:21:56 86
2010 Apr 13 10:26:56 86
2010 Apr 13 10:31:56 85
2010 Apr 13 10:36:56 85
2010 Apr 13 10:41:56 84
2010 Apr 13 10:46:56 84
2010 Apr 13 10:51:56 84
2010 Apr 13 10:58:41 84 Flashed 850mv 11:02am
2010 Apr 13 11:08:01 85
2010 Apr 13 11:13:21 86
2010 Apr 13 11:18:22 87
2010 Apr 13 11:23:22 86 Uninstalled/reinstalled Mobile Defense
2010 Apr 13 11:28:22 84
2010 Apr 13 11:33:22 84
2010 Apr 13 11:38:22 84
JuiceDefender is ~2.4x
SetCPU profiles on ondemand & standby 245/245
G-mail Push
TouchDown 15 minute pull
2010 Apr 13 08:11:35 100 Came off the charger
2010 Apr 13 08:16:35 99
2010 Apr 13 08:21:35 99
2010 Apr 13 08:26:35 98
2010 Apr 13 08:31:35 97
2010 Apr 13 08:37:56 96
2010 Apr 13 08:42:46 95
2010 Apr 13 08:47:46 95
2010 Apr 13 08:52:47 95
2010 Apr 13 08:57:47 95
2010 Apr 13 09:02:46 95
2010 Apr 13 09:08:49 94
2010 Apr 13 09:13:42 93
2010 Apr 13 09:18:42 92
2010 Apr 13 09:23:42 91
2010 Apr 13 09:28:42 91
2010 Apr 13 09:33:42 91 Turned off BT/WiFi/3G
2010 Apr 13 09:38:42 91 Phone call 9:37-9:43am
2010 Apr 13 09:43:42 89
2010 Apr 13 09:48:42 89 Crash/reboot 9:50am
2010 Apr 13 09:54:59 88
2010 Apr 13 09:59:52 88
2010 Apr 13 10:04:52 88
2010 Apr 13 10:09:52 88 Crash/reboot 10:13am
2010 Apr 13 10:17:05 87
2010 Apr 13 10:21:56 86
2010 Apr 13 10:26:56 86
2010 Apr 13 10:31:56 85
2010 Apr 13 10:36:56 85
2010 Apr 13 10:41:56 84
2010 Apr 13 10:46:56 84
2010 Apr 13 10:51:56 84
2010 Apr 13 10:58:41 84 Flashed 850mv 11:02am
2010 Apr 13 11:08:01 85
2010 Apr 13 11:13:21 86
2010 Apr 13 11:18:22 87
2010 Apr 13 11:23:22 86 Uninstalled/reinstalled Mobile Defense
2010 Apr 13 11:28:22 84
2010 Apr 13 11:33:22 84
2010 Apr 13 11:38:22 84
You lost 16% in 3hrs. IMO that's great!! That's over 20hr battery life. Don't you think?
I am sorry, but this statement just does not make any sense.
True, suspended tasks in Android do not consume too much CPU due to a good design with task suspension in mind, but they do consume memory and other system resources as something STILL has to keep track of their existence and internal allocations and other objects they use - and if you kill them, more resources are available to the system.
Android is not doing anything "magical" to make the resource problem go away - and if you start too many applications it >WILL< start to become slower and struggling with all that allocated memory (and garbage collection).
So, task killers DO have their use - for advanced users that do know what are they doing.
It is just that task killers are not absolutely needed as compared to some older OS-es that did not have background task suspension feature.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
655dropped from 100% to 78% in 24h its pretty impressive...
bty, what is "NETWORK TUNING"
From previous replied i found only enable the script by option 1 then 6 to save. what else I should do?
I don't have SS4N1 in front of me, I will take you through some settings from my head alone, so please excuse me if some info may be off. You're a smart guy, you'll figure it.
So; You've flashed the CAVS kernel and SS4N1. Reboot, start Terminal Emulator.
Type
su
sscfg
Look for the Load presets menu option. Go there, load a preset. I started with Moderate. Go back to main menu. Press 2 to display current settings, then press 1. It will show you the current preset. All features will have 1 if enabled. SS4N1 should have the 1 flag as well, meaning it's enabled.
From there, I press Enter to go back to main menu. In main menu I press 4 to customize settings. Press 1 to Enable/Disable features. I disable the Dewonkifier and Network tuning.
Press Enter and go back to the Customize settings page.
I enter 2 to customize the AWAKE mode.
Press 1 to customize the power governor. It will ask you for the governor you want when AWAKE, I enter 3 if I recall correctly, that's on-demand. Interactive is also very good, even more responsive but eats the battery faster. I go with On-demand, it's very good for me.
It will then ask you for the Min-Max operating frequencies when the phone is AWAKE. I go with the stock, 128000 for min, 998400 for max.
It will ask you for the Up-threshold, I enter 90 so the CPU will wait on the lower frequency until it's used 90% before ramping to a higher frequency. Good for battery and trust me, the phone is snappy.
Press Enter and you will be back to customize the AWAKE mode. I choose the 2nd option, UV Min-Max when AWAKE. For me, I've noticed my phone would consume the battery faster if undervolted. So, I press 2 to configure the UV when AWAKE. I set Min @ 0, Max @ 0. When done, it will show you the tweaked voltage table.
Press Enter and go back to the Customize settings page.
Press 3 to customize the SLEEP mode.
Choose 1 and change the SLEEP Power governor to Conservative.
Min freq 128000
Max freq 384000
Up-threshold: 98
I go back to configure the SLEEP mode, choose the 2nd option to change UV options, I again choose Min and Max 0.
I go back to the main menu, press 5 to save settings to SD card using the 1 option.
I go back to main menu and finally Apply the settings.
Exit Terminal, the settings apply on the fly, but I reboot for good measure.
Have fun!
PS. I was using SetCPU before SS4N1, I now have SetCPU but it's not enabled (no set on boot ticked), no profiles defined. i do all the tweaking from SS4N1, I just monitor with SetCPU. Why use SetCPU when thanks to fine users here we can enjoy a great kernel and a great GUI to configure it? BTW, thanks ch33kybutt for SS4N1 and IR for the kernel!5
Noboost, cfs, wififast or advantages of AVS vs CAVS?
NoBoost -> restored the volume levels of stock kernel
CFS -> ignore since I only release CFS nowadays
WiFiFast -> make WiFi stay awake while display is off; useful for WiFi calling app
AVS -> voltage settings are set at known stable (majority) levels
CAVS -> voltage settings are set same as undervolted SVS kernels (like CM) but can be altered using script or through terminal5
