Develop Bugs

Regarding Doomlord Kernel

Regarding the newest doomkernel, is the xLoud working for you guys??

No, pretty sure it was confirmed it was the new firmware that broke xloud, not the kernel.
However, I'm not sure if 4.0.2.A.0.42 has this issue or not, I haven't updated yet.
It seems to me that the volume has increased from the last firmware, regardless of xloud, so it doesn't bother me.

yea, it sure is louder I noticed, but not as loud as I remembered lol..
Btw, do you experience any laggings when playing games such as Backstab HD? Mine is lagging pretty badly from time to time....

eugenechiuu said:
yea, it sure is louder I noticed, but not as loud as I remembered lol..
Btw, do you experience any laggings when playing games such as Backstab HD? Mine is lagging pretty badly from time to time....
Click to expand...
Click to collapse
Try changing the I/0 scheduler to noop

It's still lagging for me =(
What's the difference between those profiles? I use the default governor.. should I change to something else?
Sent from my R800i using Tapatalk

eugenechiuu said:
It's still lagging for me =(
What's the difference between those profiles? I use the default governor.. should I change to something else?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I mean the I/O (Input/Output) scheduler not the CPU Governer You can use no frills CPU control to set it
https://market.android.com/details?id=it.sineo.android.noFrillsCPU&hl=en

I did that in the nofrills already.. even overclocked to 1.5ghz but still lags=(
Sent from my R800i using Tapatalk

AndroHero said:
I mean the I/O (Input/Output) scheduler not the CPU Governer You can use no frills CPU control to set it
https://market.android.com/details?id=it.sineo.android.noFrillsCPU&hl=en
Click to expand...
Click to collapse
Can I use this even on stock rom? I have some laggy games too..

Yea you can use it on stock rom.. But it didn't help my case at all though..
Hmm, updated to the latest generic rom but still didn't solve my lagging problems

xLoud's definitely working for me with Firmware 4.0.2.A.0.42, and DooMKernel 5v2. I haven't had even the slightest bit of lag either (once the bloatware was removed of course), in fact I find it's the fastest firmware yet for me. Or maybe it's all DooMKernel that's making it speed by. Either way, no problems to be noted.

can i overclock cpu in cm9 ？

my friend's sgw overclock cpu to 1.6GHZ and he can play "amazing spider man" without some lag , so can i overclock in cm9?

weihan1102 said:
my friend's sgw overclock cpu to 1.6GHZ and he can play "amazing spider man" without some lag , so can i overclock in cm9?
Click to expand...
Click to collapse
Check the development section, There's a kernel with OC capability
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)

reidzeibel said:
Check the development section, There's a kernel with OC capability
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1855557 is this correct？
kernel-CFS-UV-OC-29082012-V2.1.zip -

yap that is. using it till 1,7 Ghz and smooth/stable

However, no game will run fluid if it already has major lags with the stock frequency.
Especially lags that are caused by memory management can not be fully compensated by raw CPU-power.
So for better gaming experience, other control levers might be more effective, like uninstalling apps with background activities or disabling home screen in-memory-lock, if enabled. Exceptionally, before starting huge games, cleaning RAM can also avoid some lags at the beginning, as you anticipate androids low memory killer methods this way.

[Q] OC problem

i've heard some people can OC their GIO to 921MHz stable, but on my gio it can't even get stable on 883Mhz. on 864MHz is somewhat stable but i still get hung or FC randomly, im super stable at 844MHz.
Why does my phone can't be OC like them other guys?

Not all devices are made exactly the same. Processors can behave differently as do the batteries and other hardware.

bogdanwp said:
Not all devices are made exactly the same. Processors can behave differently as do the batteries and other hardware.
Click to expand...
Click to collapse
is there nothing i can do? i've tried many ROMS, on some i can get to 921 for a few seconds, but still the same. will changing kernel help?

Why not stop overclocking ? Just find a very fast rom and then you can save the overclocking , hence the instability and hotness and draining battery. That way you will have longer life on your Gio.
L.E. : just change the minimum frequency to 245 and refrain from using roms that are heavy right now , like CM 10.1 , try anything based on gingerbread like Adrenaline or Enhanced 2.3.6 or DebianDroid for example , or AOSP ICS wich i find very fast.

bogdanwp said:
Why not stop overclocking ? Just find a very fast rom and then you can save the overclocking , hence the instability and hotness and draining battery. That way you will have longer life on your Gio.
L.E. : just change the minimum frequency to 245 and refrain from using roms that are heavy right now , like CM 10.1 , try anything based on gingerbread like Adrenaline or Enhanced 2.3.6 or DebianDroid for example , or AOSP ICS wich i find very fast.
Click to expand...
Click to collapse
well currently im using AOKP milestone 6 CM9 based, i use conservative governor 245-844MHz, installed adrenaline engine 4.4, and pim my rom and set my OOM and LMK to medium settings. battery is drained only when im using data or playing games obviously. actually this ROM is superb for me performance wise, its just, i feel like i can squeeze a bit more of it for playing games you know. its like i see this slight lagging and i thought if only i could use a little more CPU power, the lag will be gone

Even you can overclock a 1st gen AMD Duron to 2Ghz with liquid nitrogen, it just doesn't make sense doing it

AW: [Q] OC problem
i can oc my cpu to 960mhz but i think it makes no sense... you don't feel the extra speed in normal use only in benchmarks... my cpu is set to 480mhz because it's enough for every app i am using (facebook, whatsapp, xda, browser and so on).

Disabling CPU Rendering (?)

Just flashed a new ROM today (OneOfAKindV11 by ipromeh) and gaming works really smooth even when its clocked at 1.6GHz... I heard Disabling CPU Rendering will make gaming more faster... Last time, when i tried it, game lags alot and overall performance is bad...
Can anyone tell me if the tweak is good or not?

Maybe it's good disabling CPU Rendering on newest CPU with newest GPU...But our GPU needs an additional support from the CPU

So its not good to disable it even with cm10 alpha 7? Just leave it as is?
Sent from my GT-I8150 using xda premium

Disabling CPU rendering diables the CPU rendering for the User Interface and forces the GPU to do it. So it affects the launcher, browser and scrolling but not games. For JB it´s not needed because of project butter which makes it already smooth.
JB also dosen´t use the exact same drivers like ICS, so what gives you a performance boost in CM9 doesn´t have to do the same in CM10.

I install seeder for disable CPU rendering... But I have problem with flash when I see flash video (ex: youtube)...

arya_ruby said:
I install seeder for disable CPU rendering... But I have problem with flash when I see flash video (ex: youtube)...
Click to expand...
Click to collapse
That´s interessting.... does the problem disappear if you re-enable CPU rendering? Also are you using CM9 or CM10?
For me there is no problem in watching youtube after disabling CPU rendering in CM9, but must agree that in both ROMs some flash videos are not displayed correctly. This is more related to the GPU drivers in CM9 and CM10 and the missing flash support in ICS and JB.
There are sites where the flash videos are not displayed correctly in CM9 and CM10, no matter you disable CPU rendering or not, but at least youtube is working well in CM9 after disabling CPU rendering. Can´t tell how about CM10, but CM10 needs both for project butter to work.

honeyx said:
That´s interessting.... does the problem disappear if you re-enable CPU rendering? Also are you using CM9 or CM10?
For me there is no problem in watching youtube after disabling CPU rendering in CM9, but must agree that in both ROMs some flash videos are not displayed correctly. This is more related to the GPU drivers in CM9 and CM10 and the missing flash support in ICS and JB.
There are sites where the flash videos are not displayed correctly in CM9 and CM10, no matter you disable CPU rendering or not, but at least youtube is working well in CM9 after disabling CPU rendering. Can´t tell how about CM10, but CM10 needs both for project butter to work.
Click to expand...
Click to collapse
I running CM10. And I was disable it, but I can't find the different.
Thanks for help me.

arya_ruby said:
I install seeder for disable CPU rendering... But I have problem with flash when I see flash video (ex: youtube)...
Click to expand...
Click to collapse
Seeder is *NOT* for disabling CPU rendering.
--- Sent from Opera on Lenovo T420 ---

pepoluan said:
Seeder is *NOT* for disabling CPU rendering.
--- Sent from Opera on Lenovo T420 ---
Click to expand...
Click to collapse
True dat...
Too much flashing! I'm blinded on my Galaxy W!

pepoluan said:
Seeder is *NOT* for disabling CPU rendering.
--- Sent from Opera on Lenovo T420 ---
Click to expand...
Click to collapse
Ohhh. Thanks for clarify this. Never dealed with seeder so am not aware atm what it is for.
So if someone is saying it disabled CPU rendering as well, I take this information as to be true.
@arya_ruby: Your postings are very irritating. In the one hand your a claiming seeders is disabling CPU rendering and this is causing problems with youtube, in the other hand you are saying you disabled it but can´t (find?) (or see) a difference.
So what?
First you should inform what seeder is for and what´s doing on your phone before making conflicting claims.

honeyx said:
Ohhh. Thanks for clarify this. Never dealed with seeder so am not aware atm what it is for.
So if someone is saying it disabled CPU rendering as well, I take this information as to be true.
@arya_ruby: Your postings are very irritating. In the one hand your a claiming seeders is disabling CPU rendering and this is causing problems with youtube, in the other hand you are saying you disabled it but can´t (find?) (or see) a difference.
So what?
First you should inform what seeder is for and what´s doing on your phone before making conflicting claims.
Click to expand...
Click to collapse
Since I was slightly involved in the development of Seeder, let me give some information:
Seeder's purpose is to quickly fill up the entropy pool used by /dev/random and /dev/urandom. If this pool gets empty, lags will happen as the kernel interrupts things (including, blocking multithreading temporarily) to fill up the pool. With Seeder running, it periodically fills up the pool to prevent it from ever draining completely.
Some people swear that installing Seeder makes their phones run smoother, because the kernel never has to trigger 'urgent refilling', which as I mentioned before, temporarily disables multithreading.
However, things learnt during the (sometimes heated) discussion about how Seeder does its magic, undoubtedly have trickled down to kernel makers; many have identified the possible bottlenecks where lags happen, and many actively took steps to prevent such situation from happening. Thus, as time goes by, the improvement Seeder brought originally gets less and less significant, even to the point that it's no longer perceptible.
Sent from my GT-I8150 using xda app-developers app

pepoluan said:
Since I was slightly involved in the development of Seeder, let me give some information:
Seeder's purpose is to quickly fill up the entropy pool used by /dev/random and /dev/urandom. If this pool gets empty, lags will happen as the kernel interrupts things (including, blocking multithreading temporarily) to fill up the pool. With Seeder running, it periodically fills up the pool to prevent it from ever draining completely.
Some people swear that installing Seeder makes their phones run smoother, because the kernel never has to trigger 'urgent refilling', which as I mentioned before, temporarily disables multithreading.
However, things learnt during the (sometimes heated) discussion about how Seeder does its magic, undoubtedly have trickled down to kernel makers; many have identified the possible bottlenecks where lags happen, and many actively took steps to prevent such situation from happening. Thus, as time goes by, the improvement Seeder brought originally gets less and less significant, even to the point that it's no longer perceptible.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Sadly, some using Seeders... Some use crossbreeder... Its the same rite?
Too much flashing! I'm blinded on my Galaxy W!

TiTAN-O-One said:
Sadly, some using Seeders... Some use crossbreeder... Its the same rite?
Too much flashing! I'm blinded on my Galaxy W!
Click to expand...
Click to collapse
Kinda similar...
Seeder uses rngd, which uses a PRNG.
Crossbreeder uses haveged, which uses a CSPRNG based on a multitude of CPU counters.
From a security point of view, haveged is more secure than rngd. But I can find no way to tune haveged's parameters, so I can't be sure that it won't be triggered at inopportune times.
rngd, OTOH, is much more tunable; the flashable-zip available in the Seeder thread has been tuned by me and @ryuinferno to be less intrusive.
(Just in case anyone is wondering: we had tuned rngd's nice value so it yields to higher-priority processes, tuned its cycle period so that it won't get triggered too frequently, tuned its 'high watermark' to make it return faster, and so on).
Sent from my GT-I8150 using xda app-developers app

pepoluan said:
Kinda similar...
Seeder uses rngd, which uses a PRNG.
Crossbreeder uses haveged, which uses a CSPRNG based on a multitude of CPU counters.
From a security point of view, haveged is more secure than rngd. But I can find no way to tune haveged's parameters, so I can't be sure that it won't be triggered at inopportune times.
rngd, OTOH, is much more tunable; the flashable-zip available in the Seeder thread has been tuned by me and @ryuinferno to be less intrusive.
(Just in case anyone is wondering: we had tuned rngd's nice value so it yields to higher-priority processes, tuned its cycle period so that it won't get triggered too frequently, tuned its 'high watermark' to make it return faster, and so on).
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
But Seeders will Conflict with Crossbreeder rite? I thought its 2 separate tweaks so that we can use both and have NO lags at all ^~^
Too much flashing! I'm blinded on my Galaxy W!

TiTAN-O-One said:
But Seeders will Conflict with Crossbreeder rite? I thought its 2 separate tweaks so that we can use both and have NO lags at all ^~^
Too much flashing! I'm blinded on my Galaxy W!
Click to expand...
Click to collapse
Not conflict, but since both will fill the same entropy pool, why install both and consume valuable RAM and CPU cycles?
There are *no* other purpose of rngd and haveged.
That said, Crossbreeder is not just haveged; there are other tunings that Crossbreeder does in addition to haveged.
Sent from my GT-I8150 using xda app-developers app

[Kernel] [CM9 - RC2 & RC3] honeyx 7up 2.6.35 kernel [for better battery life]

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: