Related
Battery drains very fast with the CM 7.2.0, why?
I installed CM 7.1.0 for everyday use, it was great, but the CM 7.2.0 doesn't let me a normal use, the battery drains really fast. In one night of sleeping the battery drains about 10% with the airplane mode! Same usage, same applications, everything the same, I changed only the version of CM.
Flash LordModUE 8.9b7 kernel by Lord Clockan, set your CPU settings to 122-1075/1152 MHz with ondemand/smartassv2 governor.
http://forum.xda-developers.com/showthread.php?t=1085725
Also flash undervolting scripts and set it to -50mV or ultra undervolt using the LordModUV application which is installed when you flash the scripts. You can try Pinky undervolt and stable pinky undervolt but if your phone keep rebooting then those are too much. Ultra undervolt should be fine, if not then -50mV.
Note: This kernel has 2WCR (2-way call recorder) functionality so you can record calls using the specified call recorder application, if you want.
All information and links are available in that thread.
Sent from my Desire HD using xda premium
Thank you very much!
Now I'm testing MIUI, I will come back to CM testing your tips.
Hello,
I search the best rom official or custom and the best kernel for the battery, only the battery.
Can you help me because i had only a utilisation intensive!!
Best regards
xamou711 said:
Hello,
I search the best rom official or custom and the best kernel for the battery, only the battery.
Can you help me because i had only a utilisation intensive!!
Best regards
Click to expand...
Click to collapse
at the moment i use the android revolution hd 6.0 rom with a perseus 29.1 kernel. the battery drain is 1,5%/h (betterbatterystats: 2d 42m battery 25%) and the cpu setting is stock. i will see if it change after the next charging.
i already downloaded the redpill rev1.00 kernel and i want to test it the next time.
unfortunately i've got some l2_hsic wakelocks with the perseus kernel (2h in 2 days) and will see what happens with the redpill kernel.
tenofnine
ROM and Kernel have only a small effect on battery life. The main culprits are processes that wake the phone up from deep sleep and engage the CPU or data transmittion.
When I lowered all auto-update intervals of apps from once-per-30-minutes to once-per-4 hours, my battery life nearly doubled itself.
i presume that you already disabled/lowered these "useful" things to improve your batterylife.
i don't play games on my cellphone, just some surfing and calling on viber (2-3h per day) however my battery lasts longer compared to the stock rom.
Hi all,
I am proud to be a small silent part of this community and to see how much the Galaxy W has grown due to the collective work of our members. I feel like the phone has damn near doubled it's value now with all the custom ROMs, kernels, tweaks, etc, etc that have been implemented in such a short time. Really, I can't see how this phone could be any faster! That being said I feel their is a void in resources dedicated to focusing on battery life while still retaining acceptable speed.
Moving on to Kernel 3.X has really brought great features and speed to our phone, but at the cost of extreme battery loss. It's early on in it's development, so I think there is room for improvement. I have noticed that members are starting to complain about battery life and I for one agree that this is a problem. I wanted to open a forum where we could collect ideas here so our precious phones could ideally make it through the day (or at least a half of a day!).
Anyway, I hope this will be a good jumping off point for discussing. I only ask if members could refrain from the old, "Just change the battery!" unless the user is reporting the battery is more pregnant then a Kardashian sporting twins.
Ideas
Some ideas to post about
ROM
Kernel
Governor
I/O SCHEDULERS
Tweaks
Apps
It would really help if contribute ideas on how to improve our battery life even for just a little.
Sent from my GT-I8150 using xda premium
I've had some success using conservative + row.
I'm really hoping to find a kernel that has more optimized conservative governors. Anyone have any tweaked conservative governor experience? I was looking at Scary or Lion heart, etc?
Btw I'm on RC 6 + Chronos kernel.
tebor8 said:
I've had some success using conservative + row.
I'm really hoping to find a kernel that has more optimized conservative governors. Anyone have any tweaked conservative governor experience? I was looking at Scary or Lion heart, etc?
Btw I'm on RC 6 + Chronos kernel.
Click to expand...
Click to collapse
I'm going to try Governor: Conservative. Is it better than SmartassV2? Anyway, I'm going to find out, just finishing the charge to 100%. I'm gonna test on CM10 Alpha 6 + Athena Kernel. Will report back after draining.
Okey bro, im using smartassv2 with athena on cm10. I'll post my observation here.
Sent from my GT-I8150 using xda premium
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Btw how much brightness are u guys using?
Sent from my GT-I8150 using xda premium
I'd love to get a CM9 or CM10 RC7 with 2.6 kernel along with a kernel 3.0 version for people who loves kernel 3.0
I am not asking to develop 2.6 kernel further. Previous 2.6 kernel is very good, but we need a ROM (base updated/sources updated) which can support 2.6 kernel fully. 2.6 Kernel was giving me much better battery life compared to kernel 3.
i tried flashing respective 2.6 kernels on CM9 and CM10 RC6. It seems to work fine but if i plug the usb cable to pc then all memory cards get unmounted. ie.. i can't copy files to phone or vice verse. I hope arco gives us a updated source for 2.6 kernel with RC7 release..
My suggestions for better battery life:
1. First thing first: make sure your battery is not dying; if it's bulging, replace it immediately.
2. Use a kernel that's undervolt-able. I use ICS, and Yoon.Kernel is perfect for me.
2a. Then, undervolt your phone. The Incredicontrol app is usually compatible with the method used by your kernel. Or, read the kernel's thread to find out which app to use.
3. Use Greenify (app) to 'hibernate' apps you don't need to run in the background at all times.
4. If you have the money (and can purchase apps via the Play), purchase "Autostarter" and disable apps' starting points. You should focus on the "After Startup" and "Connection Changed" events.
5. Every now and then, while the phone is on, turn off all data connection (wifi or 2G/3G), turn off sync, and let your phone charge to 100% *and* keep charging for awhile (trickle charging, 1-2 hours should be enough), then let the battery drain until your phone shuts down (by using it normally). Let the phone cool down, plug it into the charger, and power it on, and let it charge until 100% again.
6. Use BetterBatteryStats regularly to find apps consuming too much power and/or holding wakelocks too often; complain to the app maker, and replace it if the maker won't/can't change it.
7. Remember to turn off wifi and/or use 2G only mode when you're no longer using them.
Sent from my GT-I8150 using xda app-developers app
Pep, with full respect to your suggestions that are legit, but this can´t fix the battery drain issue CM9 is having with it´s new 3.X kernel.
They all will reduce the battery drain of course,but wont bring it down to the level you will reach with 2.6 kernel.
I´m still not sure what exactly is causing this, but in my case it´s for sure not my batteries nor other apps causing this.
As I already posted in the Bug report threat, I now flashed RC6 by going totally pristine. Formated both SD Cards and whiped everything, just installed BatteryMonitorWidget to control the battery drain. It´s twice as hight in DeepSleep compared to RC2 and RC3 with it´s old 2.6 kernel.
So first of all we need to narrow down what exactly is causing this.
Therefore I suggest to install first the BatteryMonitorWidget to comapare our results and to share the settings whe have changed after installing RC6 the pristine way.
First my configuration:
1. SDCards swapped
2. Dithering disabled
3. 16-bit Transparency enabled
4. Freeing up resurces enabled
5. Kernel sample Merging enabled
6. Zram disabled
7. default governor and scheduler
8. Syncing Accounts disabled
9. Updates and notifications in GooglePlay disabled
10. Wlan and MobileData disabled
11. Baseband XXLMB
My results with 2.6 Kernel are:
~16mA at daytime in DeepSleep
~ 5-8mA at night in DeepSleep
with kernel 3.x
constantly ~35 - 50mA in DeepSleep
and I checked it´s really in DeepSleep Mode.
So it looks like the radio is consuming more power while keeping the phone connected with the radiostation while the phone is in DeepSleep.
but....
I once also tested hadi´s 1.6 yoon Kernel with RC2, which is basing on Arcos RC2 kernel. By using the Ondemand govarnor in his kernel to compare the battery consumprion against Arcos Ondemand governor, hadis Ondemand governor also comsumed more than Arcos Ondemand Governor. With his OndemandX givernor the consumption was pretty much the same like with Arcos Ondemand.
So maybe it´s also something that changed in Arcos ondemand governor in 3.x kernel.
honeyx said:
Pep, with full respect to your suggestions that are legit, but this can´t fix the battery drain issue CM9 is having with it´s new 3.X kernel.
They all will reduce the battery drain of course,but wont bring it down to the level you will reach with 2.6 kernel.
I´m still not sure what exactly is causing this, but in my case it´s for sure not my batteries nor other apps causing this.
As I already posted in the Bug report threat, I now flashed RC6 by going totally pristine. Formated both SD Cards and whiped everything, just installed BatteryMonitorWidget to control the battery drain. It´s twice as hight in DeepSleep compared to RC2 and RC3 with it´s old 2.6 kernel.
So first of all we need to narrow down what exactly is causing this.
Therefore I suggest to install first the BatteryMonitorWidget to comapare our results and to share the settings whe have changed after installing RC6 the pristine way.
First my configuration:
1. SDCards swapped
2. Dithering disabled
3. 16-bit Transparency enabled
4. Freeing up resurces enabled
5. Kernel sample Merging enabled
6. Zram disabled
7. default governor and scheduler
8. Syncing Accounts disabled
9. Updates and notifications in GooglePlay disabled
10. Wlan and MobileData disabled
11. Baseband XXLMB
My results with 2.6 Kernel are:
~16mA at daytime in DeepSleep
~ 5-8mA at night in DeepSleep
with kernel 3.x
constantly ~35 - 50mA in DeepSleep
and I checked it´s really in DeepSleep Mode.
So it looks like the radio is consuming more power while keeping the phone connected with the radiostation while the phone is in DeepSleep.
but....
I once also tested hadi´s 1.6 yoon Kernel with RC2, which is basing on Arcos RC2 kernel. By using the Ondemand govarnor in his kernel to compare the battery consumprion against Arcos Ondemand governor, hadis Ondemand governor also comsumed more than Arcos Ondemand Governor. With his OndemandX givernor the consumption was pretty much the same like with Arcos Ondemand.
So maybe it´s also something that changed in Arcos ondemand governor in 3.x kernel.
Click to expand...
Click to collapse
Ah, I misunderstood the intent of this thread, then, my bad :banghead:
Hmmm... I'm willing to do some experiment... but there are several apps called "Better Battery Widgets"... which one?
Sent from my GT-I8150 using xda app-developers app
i don't know how will you classify my battery life because for me if the battery is enough to last at least for 8-9hours(hours spent in college) then i call it good enough
i use athena with no UV.
gov lulzactive 245-1024 scheduler row io
1 think usually done wrong in forum i'm following is they're using task killer or app to manage their free ram. this app is THE REAL BATTERY KILLER. they stop needed service and make your phone awake . not to mention the choppyness because the os needs to restart services and many bad effect it causes
Sent from my GT-I8150
pepoluan said:
Ah, I misunderstood the intent of this thread, then, my bad :banghead:
Hmmm... I'm willing to do some experiment... but there are several apps called "Better Battery Widgets"... which one?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Oh I see there are several apps out now using the same name.
I´m using this BatteryMonitor Widget from 3C.
So when using it:
1. Do not recalibrate the battery as it will otherwise need much more time to show you accurate readings.
2. The App needs at least one or two charging cycles to recalibrate itself (not the battery) as it needs to determinate the exact capacity of your battery.
hadidjapri said:
i don't know how will you classify my battery life because for me if the battery is enough to last at least for 8-9hours(hours spent in college) then i call it good enough
i use athena with no UV.
gov lulzactive 245-1024 scheduler row io
1 think usually done wrong in forum i'm following is they're using task killer or app to manage their free ram. this app is THE REAL BATTERY KILLER. they stop needed service and make your phone awake . not to mention the choppyness because the os needs to restart services and many bad effect it causes
Sent from my GT-I8150
Click to expand...
Click to collapse
Hm well I´m used to recharge my battery every 3 to 5 days because it´s most of time in DeepSleep Mode. I´m just doing calls and surf the net in my breaks at work. So only turning on MobileData if it´s needed. At home I´m having my PC for surfing the net, so MobileData and WLAN is disabled as well.
With RC4 my battery drain was so high it even wouldn´t last as long till I´m back home from work. With RC6 i think it would last at least 12 to 18 hours, but it´s still a huge difference compared to the RC´s with it´s 2.6 Kernel.
Agree with you about using such apps like Task Killer or scripts like V6 Supercharger. They all need extra CPU time to do their jobs and often are causing more problems than they are solving.The Android OS can manage such things better itself and terminate unneeded services itself too.
---------- Post added at 08:23 AM ---------- Previous post was at 07:51 AM ----------
Additionally you can use BetterBatteryStats in case your phone is keeping a long time active to see what is causing this. It´s free for XDA members.
honeyx said:
My results with 2.6 Kernel are:
~16mA at daytime in DeepSleep
~ 5-8mA at night in DeepSleep
with kernel 3.x
constantly ~35 - 50mA in DeepSleep
and I checked it´s really in DeepSleep Mode.
So it looks like the radio is consuming more power while keeping the phone connected with the radiostation while the phone is in DeepSleep.
Click to expand...
Click to collapse
I can testify to this, my BBS shows the phone going into deep sleep normally but the drain with data on is immense even in deep sleep. Your initial findings already point to the most likely source of the problem. Given the varying opinions on this(some say it's fine I others don't agree), is it possible we have the same device but different hardware revisions, some of which are much more power-friendly than others? Because for the life of me I couldn't NEVER anything more than a day from kernel 3.x(CM10) but some people claim they could get upto 3-4 days on light use!
Sent from my Wonder powered by CM10
I don´t think it has something to do with different hardware revisions, else it wouldn´t matter which kernel is in use. But it does.
There is for sure something strange going on. I´ve additionally installed BetterBatteryStats and now the phone started keeping very often in awake mode. Not sure this has something to do with this app, because it didn´t happen when I had it installed on an older CM9 release.
However I can´t find any suspicious processes that are causing this. But to be sure I will have to go back to RC2 to compare with.
So here my results:
Within of 5 hours it keept Awake for 25 minutes.
BBS also says NO Data Connection and No or Unknown SIgnal during that time
But I´m sure it was connected to the radiostation and made a short testcall.
About wakelocks:
KernelWakelocks:
"mmc0_detect" 4m 32s
"DPRAM" 3m 11s
"alarm_rtc" 2m 21s
"PowerManagerService" 1m 36s
"radio-interface" 1m 10s
"alarm" 36s
"mmc1_detect" 13s
Partial Wakelocks:
AlarmManager 44s 997 Counts
GSM 20s 4 Counts
ActivityManager-Launch 18s 104 Counts
sleep_broadcast 4s 23 Counts
RILJ 2s 146 Counts
*backup* 1s 109 Counts
NotificationService 1s 113 Counts
Ok I´m back to RC2 and am having some results from BBS to compare with.
After fully charging the battery I unplugged the phone and left it over night at the same place I´m always leaving. So the conditions were the same like with RC6, though in RC6 there were no apps exept BatteryMonitorWidget and BetterBattery Stats installed.
To make it short the results are nearly identical. Even the Awake time is almost identical in a period of 5 hours.
There is also the No or unknown Signal entry for the whole time. So I guess this is due to the MobileData being disabled.
But what I´m missing in RC2 is "mmc0_detect" and "mmc1_detect" in the Kernel Wakelocks. They are not showing up there.
So now we need some other results to compare with my results.
Been using this phone for 1 and half year now..is it normal to have a battery life of 5 hours with 3G on? Currently using cm10
I think the 3.0 kernel really makes a big difference in a negative way in regards to the battery life.
To fight against this, I have used the following settings for some success:
Conservative + Row... still very fluid with Yoon Chronos
245 - 1024 MHz
Screen off after 30 secs
Under volt
Its much better than before, but still I would like more battery life. Probably 8 hours with heavy use up to 16 hours lite.
Sent from my GT-I8150 using xda app-developers app
Agree on that. I tried now RC6 together with hadis chronos kernel and the consumption is the same like with Arcos 3.x kernel.
The "mmc0_detect" and "mmc1_detect" entries also appear with hadis chronos kernel. Not sure they are responsible for it, but they didn´t appear with 2.6 kernel.
So what I can say for sure it´s not the governor but something else in the 3.x kernel and so far these mmc detect entries are under suspicion.
First of all, sorry for not testing against the two kernels; there's a major project going on in my office, and I totally can't risk to be offline... plus with the random times I'll receive calls, the battery usage might be skewed...
honeyx said:
Agree on that. I tried now RC6 together with hadis chronos kernel and the consumption is the same like with Arcos 3.x kernel.
The "mmc0_detect" and "mmc1_detect" entries also appear with hadis chronos kernel. Not sure they are responsible for it, but they didn´t appear with 2.6 kernel.
So what I can say for sure it´s not the governor but something else in the 3.x kernel and so far these mmc detect entries are under suspicion.
Click to expand...
Click to collapse
I did some Google search and arrived at the following thread:
http://forum.xda-developers.com/showthread.php?t=1827676
scroll down to the second post. The OP of that thread noticed that mmcX_detect will utilize a lot of wakelocks if the SD Card is defective.
Since the battery drain issue with kernel 3.0 does not seem to happen to everyone, could people experiencing such drain try the experiments without an SD Card being installed?
Sent from my GT-I8150 using xda app-developers app
No problem pep. I need my phone too during the week, so only can do some tests at the weekend.
So to narrow down this problem we need to know how it works without a SD Card installed and if all who are having this issue are having the SD Cards swapped.
Due to some requests via PM´s I decided to make my kernel finally public, but remember:
This kernel is a personal kernel for my private use, so it´s only containing the tweaks I´m also really using
It´s the older 2.6.35 kernel basing on latest 2.6.35 sources from Arco, so only use it with Arcos CM9 RC2 or RC3 or a custom ROM with 2.6.35 kernel
This kernel is not filled with a lot of governors and schedulers, but only the ones I´m also personally using.
I have made this kernel because non of the custom kernels worked stable for me in the past, even at stock voltages. With this kernel I´m able to run at extreme Undervolting rock solid.
So this kernel was created with stability and battery life in mind. Each modification was tested separately, so everytime I added a tweak or a new feature, I tested the new kernel for a couple of days before adding the next one.
So why I decided to tweak this older kernel rather than going with 3.x kernel?
- Because this kernel is giving me a much better battery life than the 3.x kernel, is running rock solid and also because I don´t really need the new features added into 3.x kernel.
So what it has included:
- UV and OC options
- lowered WiFi voltage
- lowered lcd voltage
- slightly lowered standby / deepsleep voltage
- Battery life extender
- Fixed 100% battery notification after charger unplug
- 377MB RAM
- NO-OP scheduler as default scheduler
- Lulzactive governor as default governor
- tweaked Lulzactive for battery life and smoothness
- added 518, 633 and 902 MHz (new)
- screen off frequency set to 518 MHz max.(new)
- some more voltage tweaks
- no other compilation tweaks just to make the list longer
With this kernel and a new battery my SGW can last up to 7 days in standby. This is without WiFi and Mobile Data. With the stock kernel I got 3-5 days. It´s also working absolutely stable and smooth for me without any issues.
So if you run into some issues that are/were also discussed i the CM9 Bug report thread, don´t blame me for them.
other suggestions:
- enable KSM
- enable 16bit Dithering
- disable CPU rendering
- greenify your apps
If you follow these suggestions, your ROM should run absolutely smooth without the need for other tweaks.
To use Battery Life eXtender:
Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions.
Just as a note. Should you encounter the white screen bug in some apps, this is because you whiped the cache in CWM Recovery after flashing the kernel. To fix this go into settings -> apps and delete data and cache of those specific apps.
Credits are going to:
- Arco (for his great work and sources)
- educk (for helping me doing the first steps)
- Christopher83 (for his great commits)
- ivendor (for his tweaks)
- Ezekeel (for Battery Life eXtender)
----------- 18.08.2013 -----------
- added frequencies
- incrased RAM
- lowered screen off frequency in Lulzactive
- some voltage finetunning
CM_9-2.6.35-7up-kernel.zip
----------- first release -----------
Download.
XDA:DevDB Information
[Kernel] [CM9 - RC2 & RC3] honeyx 7up 2.6.35 kernel [for better battery life], a Kernel for the Samsung Galaxy W I8150
Contributors
honeyx, http://forum.xda-developers.com/member.php?u=4410351
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2013-09-24
Last Updated 2013-09-24
First, thanks :good:
Edit: can i have your permission to use this kernel on my ROM?
ipromeh said:
First, thanks :good:
Edit: can i have your permission to use this kernel on my ROM?
Click to expand...
Click to collapse
Sure No problem mate.
honeyx said:
Sure No problem mate.
Click to expand...
Click to collapse
nicely done
I have tested this before with rc2 and I have to say battery life was very significantly longer compared to hurtsky 2.5 + QAsR v2.3. However, the white screen issue persisted in 2 of the apps I used the most, namely boat browser and Gmail so I have opted out again. But if you guys don't care about white screen, do give this kernel a try
Yeah, kernel 2.6 is always better battery life... i recomended it
- screen off frequency set to 768 MHz
Click to expand...
Click to collapse
What mean of that ?
is we get trun off the screen it auto lock on 768Mhz ? it's not deepsleep any way CMIIW
hepi_hape said:
Yeah, kernel 2.6 is always better battery life... i recomended it
What mean of that ?
is we get trun off the screen it auto lock on 768Mhz ? it's not deepsleep any way CMIIW
Click to expand...
Click to collapse
This is the max frequency the clock might rise to if the screen is off but for example an app or a service awakes the phone from deepsleep. So it will not drain so much the battery if the phone gets awake for some reason and if you undervolt your cpu, you can reduce the consumption for such a case even more.
This is preset in the Lulzactive governor, which Christopher83 fixed to make this working, so it´s only related to this governor, which is also my default governor.
So when in screenoff the phone only maximum can use CPU clock at 768Mhz
Yeah i get it. .thx for explain it
I think arco might be able to help you fix the white screen. Long back skull kernel experienced the same and acro helped him to fix it.
coolbuy said:
I think arco might be able to help you fix the white screen. Long back skull kernel experienced the same and acro helped him to fix it.
Click to expand...
Click to collapse
Uhm, well I´m not sure this is exactly the same because Keff (Woohooo..) is modding the 3.x kernel for CM10. But thanks for the suggestion. I will aks Keff first to not to bother Arco in the first place. It will be for sure interesting what caused it for him.
Just to clarify some things about the white screen bug. The one I described in my first post is not the real white screen bug, but only what happens to some apps after whiping the cache in CWM Recovery. This can easily be fixed like described above and will not bother you anymore.
The real white screen bug came all of the sudden (without whiping anything before). So for example you opened facebook, everything was fine, but a few minutes later by relaunching facebook you got a white screen. The procedure to get rid of this was the same as I already mentioned but with the difference it happened again after a while.
So well I have had this issue with facebook too in the past, but it´s gone and now even not happening after whiping the cache in CWM Recovery. It´s not gone because I updated the rom (still using RC2), but because facebook updated their app.
Edit:
I already found what you was talking about. It´s called the white noise issue where you get a white screen by turning the screen on, so it´s not the same.
And how is games performance ?
Sent from my GT-I8150 using xda premium
mps42 said:
And how is games performance ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Mind you: This is battery saving rom. It is meant to have low game performance. It MUST have a lower gaming performance than those v3.0 kernels. If you want gaming, this is not for you.
Doplgangr said:
Mind you: This is battery saving rom. It is meant to have low game performance. It MUST have a lower gaming performance than those v3.0 kernels. If you want gaming, this is not for you.
Click to expand...
Click to collapse
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
honeyx said:
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
Click to expand...
Click to collapse
Thank you for correcting my ignorance. :laugh: Maybe I'll give the kernel a try and tell more about that
Honeyx, I hope you continue to develop and share this kernel in the future because I decided to start everything over from scratch because of your work here. I love this kernel. I get so much better battery life now. If you would ever consider adding Lionheart in the future, I would be very grateful. Is there any way to add Row or does it require kernel 3? Thanks again!
Sent from my GT-I8150 using xda app-developers app
honeyx said:
Yes, this is a battery saving kernel, but why should it have low gaming performance? Just because it´s optimized for low consumption in standby and because you can undervolt it? It´s like you were comparing an older Pentium4 against an Intel Atom CPU and saying the Atom must be faster because its newer. Or by comparing a Atom against a 286 CPU and saying the 286 will be faster than the Atom because the Atom is more battery friendly.
Sure, it´s not optimized to get the highest scores in benchmarks, but the games I´m playing once in a while are running totally smooth.
The newer releases of CM9 might be of course faster in games, but not just because of the 3.x kernel, but also because Arcos ocessionaly is updating the GPU drivers.
Click to expand...
Click to collapse
Not for hard gaming.....thats sure....if you want battery play with puzzlebubbles
Inviato dal mio GT-I8150 con Tapatalk 2
tebor8 said:
Honeyx, I hope you continue to develop and share this kernel in the future because I decided to start everything over from scratch because of your work here. I love this kernel. I get so much better battery life now. If you would ever consider adding Lionheart in the future, I would be very grateful. Is there any way to add Row or does it require kernel 3? Thanks again!
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I may add some tweaks in the future, but this may take a while till I have some spare time to test them. About adding other governors...well I tested a lot of them but finally decided to use Lulzactive because it was the most battery friendly governor in the one hand and because there is also the Lulzactive app you can use to tweak it to your needs. So for example tweak it that way it behaves like for example Lionheart. I also tested the ROW scheduler but it wasn´t as stable as I presupposed to be. So the best compromise between stability and performance was to use the noop scheduler. It´s nearly as fast as the row but way more stable.
djdu90 said:
Not for hard gaming.....thats sure....if you want battery play with puzzlebubbles
Inviato dal mio GT-I8150 con Tapatalk 2
Click to expand...
Click to collapse
LoL. I´m quite sure with extreme undervolting you can still save some battery juice even while playing action games on this device. Beside this it´s not the CPU or GPU that consumes most, but the display and its backlight LED´s.
it is for battery saving but for me its not good to play with games cuz playing for like 40-60 minutes consume 60% battery ? lol
thats quite alot and might burnt up my battery life.
Dwama said:
it is for battery saving but for me its not good to play with games cuz playing for like 40-60 minutes consume 60% battery ? lol
thats quite alot and might burnt up my battery life.
Click to expand...
Click to collapse
So did you thought it will consume just as much as being in deepsleep????????? The kernel is tweaked to consume less in deepsleep and in daily use but not to consume less in games. Beside this it´s not the CPU nor the GPU that consumes most, but the backlight LEDs in your screen. So even by undervolting and underclocking it will still drain a lot if playing games.
There is no and will not be a magical Kernel that is using witchcraft to reduce the consumption of the LEDs, exept someone compiles you a kernel which turns out the LEDs completely, if you can with a complete dark screen.
honeyx said:
So did you thought it will consume just as much as being in deepsleep????????? The kernel is tweaked to consume less in deepsleep and in daily use but not to consume less in games. Beside this it´s not the CPU nor the GPU that consumes most, but the backlight LEDs in your screen. So even by undervolting and underclocking it will still drain a lot if playing games.
There is no and will not be a magical Kernel that is using witchcraft to reduce the consumption of the LEDs, exept someone compiles you a kernel which turns out the LEDs completely, if you can with a complete dark screen.
Click to expand...
Click to collapse
Im not expecting anything from ur kernel, im glad that u shared ur kernel taht could last longer than arco's stock kernel.
I was just giving up my comments about ur kernel that i have used for 2 months , Not complaining and whining lol.
I am sorry and thanks for sharing ur kernel , keep it up. :fingers-crossed:
I have rooted my Redmi 1s via native root method because i only want to underclock it.
I am using No Frills CPU app and its config is as follows:
Max - 1.19
Min - 384
governor - ondemand
IO scheduler - cfq
I am having worse battery drain than before rooting!! :crying:
Earlier i had one day battery life with normal usage. Now it dosent even last for half a day! I am having 20-25% battery drain in one hour...
I am running stock MIUI v45.
anybody facing the same issue? Please help me...
Upgrade to V50 or flash MiUi V6 or CM11 R22,I get around 1.5 days of battery backup on normal usage on R22
I am using carbon rom RC7 with carbon kernel v1.3 beta.i am getting awesome battery life.At night if i leave my phone with wifi on ,after waking up in morning(nearly 10 hours),yeah i sleep that much ) it consumes only 1% battery.
Note:
1)i have no sim in my phone.
2)i use greenify to hibernate all apps even some system apps too.
My kernel setting:
96-1190mhz,ondemand,sio