yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] lpsi2000:
It looks like this question was already answered. Nonetheless I am using the latest kernel available right now (Build 13)
[Galaxy S II Original Android Development] lpsi2000:
SOD

There is definitely something wrong with this kernel. I left it charging using the wall charger, when I came back the phone could not wake up until I took the battery out.
[Galaxy S II Original Android Development] ferreinf:
Are you using some app like setcpu for example with screen of profile?

Had the same issue when using screen off 200>200
[Galaxy S II Original Android Development] avetny:
Linpack even cant touch 90 !:( come on man !

example: NINPHETAMINE (hate him:)) kernel gives 94 linpack!!
[Galaxy S II Original Android Development] lpsi2000:
Nope, I have been using a few of the previous versions without any issues on the same setup. As matter of fact, I went back to build 12 and everything is fine.
[Galaxy S II Original Android Development] BoneMo:
also problem

i just wake up....then i just pressed power button...i see lockscreen and then reboot :eek::eek::eek:

just for sure also going back to XXKG6 Lulz

I think that problem is in *built from the latest kernel source. (SHW-M250S EG14)

So now we need to wait for Tegrak to be online
[Galaxy S II Original Android Development] malavan:
Yes it's really strange same here
[Galaxy S II Original Android Development] BoneMo:
I think that i would be easiest to make Lulz kernel build 12 XXKH3
[Galaxy S II Original Android Development] malavan:
Maybe his using this chanise source which is older with random reboot.
[Galaxy S II Original Android Development] drelite08:
Why is it that when i flash this kernel the scaling doesnt go past the stock max speed? Am I missing something?
[Galaxy S II Original Android Development] mark2222:
Just woke up and phone was on battery logo with 43% charge. It was on and charging all night, guess it's back to kg6 for me as well.
[Galaxy S II Original Android Development] nme2:
Maybe add some extra voltage if you are extremely undevolted in low freqs and see if the phone crashes again...
[Galaxy S II Original Android Development] blackmumba:
I had a similar problem. The battery had about 90% when I went to sleep. When I woke up today the phone was turned off and needed a long press on power for a reboot, then the battery had only 27% left. Really weird.

By the way, why does the xda app tell me that the screeshot I want to upload has he wrong format when I try to upload it?

Cheers
[Galaxy S II Original Android Development] comnam90:
I had same issue trying to upload screenshots
[Galaxy S II Original Android Development] sebarkh:
Where is our beloved Tegrak? :-) we need you badly with the kh3 issues. Thx.
[Galaxy S II Original Android Development] eXnikaru:
I have the same issue too...the phone is always awake and battery drains fast..sometimes, phone will hang too....
[Galaxy S II Original Android Development] Ivan_Belarus:
My phone sometimes doesn't wake-up on Lulz 13. I tried to add voltage on 200MHz, bun in vain. Some sleeping-pills are hidden inside the kernel :D Tegrak, hello, where are you?! ;)
[Galaxy S II Original Android Development] koven:
yup, something is wrong with this kernel. It reboots by itself, it hangs. Didn't noticed battery drain though..
[Galaxy S II Original Android Development] xeq544:
Didn't have reboot yet, but something is really wrong. Battery life is worse, on lulz 12 I lost 1 percent of battery overnight, tonight it was 7 percent. Cpu spy shows 28minutes of 1204mhz during night(9 hours of not touching the phone). It was barely few minutes on previous version. The battery drain seems to be higher even when using the phone, lost 10 percent after few minutes of browsing the net.

Gonna roll back to v12 when I come home
[Galaxy S II Original Android Development] tegrak:
I'll return to the I9100's source and add XXKH3 initramfs.

it seems some codes of Korean S II cause this problems on I9100
[Galaxy S II Original Android Development] grisha1:
:p

:rolleyes:

:eek:

:eek:

**** happens!
[Galaxy S II Original Android Development] blackmumba:
What does that mean - in noob language? ;-)

How will it affect the performance of the kernel?

Thanks for your work!

Cheers
[Galaxy S II Original Android Development] tomj777:
This is a mea culpa thing but just to let you folks know, in case you replicate...

Whilst on holiday (still on hols, borrowing a PC) I noticed that my phone was freezing rather a lot on Lutz 13 kernel so I flashed back to 12 using CMW prog from chainfire, not booting to CMW. Phone then stuck at first (Samsung Galaxy) screen. I could get `download` but not `CMW`.

Just tried flashing 12 through Odin with no joy - shall have to wait 'till home on Tuesday and I suspect will need to reflash from scratch (EFS backed up, thankfully).

So good friends - always boot to CMW before playing, especially in the back of beyond. There endeth the lesson for today.
[Galaxy S II Original Android Development] tegrak:
Beta Live

Lulz-Kernel-Build-14-Beta-1-for-I9100-XXKH3.tar

built with new I9100 source from OSRC (named Update2)
[Galaxy S II Original Android Development] Reno_kun:
Few tests but wake up seems to work fine with build 14 whereas with build 13 I've got problems. I will continue to test.

Thank you Tegrak
[Galaxy S II Original Android Development] BoneMo:
CWM flashable XXKH3 Lulz Kernel build 14

is here for you to use with CWM recovery,,

CWM zip repaired...you can flash it now
[Galaxy S II Original Android Development] :
And here :(
[Galaxy S II Original Android Development] :
Flashed build 14... Testing!
[Galaxy S II Original Android Development] :
So far that bug from build 13 is gone! Eheh :D
[Galaxy S II Original Android Development] tonysac:
Ok till now..no kernel panic..

Sent from Galaxy!
[Galaxy S II Original Android Development] jlevy73:
So far so good.
[Galaxy S II Original Android Development] comnam90:
will download and test tonight
[Galaxy S II Original Android Development] Ivan_Belarus:
14b1 being tested. Seems ok.
[Galaxy S II Original Android Development] tonysac:
Hey I remember you said you oc only to 1300 because of some lags you had..I noticed exactly the same and with no uv now but only with oc to 1300 things seems a lot better..do you uv? Also in what launcher you had lags? I'm using adw ex

Ps

Almost 24 hours in use with beta..no problems so far

Sent from Galaxy!
[Galaxy S II Original Android Development] jlevy73:
I had a couple of kernel panics with beta so I am on Ninpo 2.1.1 for now. I need reliability because I used my phone for business.

I had lags in TW, LauncherPro and Go Launcher.

These are the settings I use:

200 - 950

500 - 950

800 - 1050

1000 - 1175

1200 - 1250

1300 - 1275

1400 - 1300

1600 - 1425
[Galaxy S II Original Android Development] tonysac:
Oh noo you had kernel panics? Ahh I need my phone also to be steady for business..ill try ninpo with settings you wrote..thanks for your answer..

@Tegrak you must really check this problem (kernel panic) please..

Edit

I think no 1300 step correct?(8 steps with this lol)

Sent from Galaxy!
[Galaxy S II Original Android Development] BoneMo:
.

lags, kernel panic ?? i had no problem since i flashed build 14 beta 1, no restarts...nothing bad happening...maybe i just have a luck

These are the settings I use:

200 - 950

500 - 950

800 - 1050

1000 - 1150

1200 - 1250

1400 - 1300

1600 - 1350
[Galaxy S II Original Android Development] jlevy73:
Lol, yeah no 8 steps. I was using 1400 not 1300 :o
[Galaxy S II Original Android Development] lpsi2000:
You are not alone there; since build 14 beta 1 I had no issues (except for the standard issue I have with all Lulz kernel when playing YouTube videos it gets pretty hot and drains battery like crazy). My settings are in my signature.
[Galaxy S II Original Android Development] tegrak:
no critical issues with beta 14?

I'll try to add vitalij's "touch screen fix" on official build 14.
[Galaxy S II Original Android Development] BoneMo:
no issues for me, thx for the kernel ;)
[Galaxy S II Original Android Development] m444266:
nice battery

performed well on my battery benchmark.
[Galaxy S II Original Android Development] :
Stable here :)
[Galaxy S II Original Android Development] lpsi2000:
Anyone seeing a drop in battery performance comparing to build 12?
[Galaxy S II Original Android Development] jlevy73:
Yes, definitely. Hacre believes that something with the new source has degraded battery life. He doesn't have time to investigate further due to his honeymoon but others are noticing the same issue.
[Galaxy S II Original Android Development] ferreinf:
Wrong thread mate... ;-)

Sent from my GT-I9100
[Galaxy S II Original Android Development] lpsi2000:
Good to know thanks. I am going back to build 12 this weekend to test it out.

Not really, it is good to know that others are seeing the same issues from the same source.

edit: After further testing with build 14, it seems as the issue with YouTube making phone hot and burning battery like crazy no longer exist. So I am back into testing it a little longer:)
[Galaxy S II Original Android Development] m444266:
bet 14 didn't so bad with my benchmark.
[Galaxy S II Original Android Development] jlevy73:
Beta 14 has been doing good. Stable on my end.
[Galaxy S II Original Android Development] tonysac:
No kernel panics???

Sent from Galaxy!
[Galaxy S II Original Android Development] :
Here, no! Very stable!
[Galaxy S II Original Android Development] nme2:
it works great :p
[Galaxy S II Original Android Development] tegrak:
it seems "touch screen fix" isn't required.

his TouchScreenTune app is enough to control it! simple but provides a perfect solution.
[Galaxy S II Original Android Development] shr33kant:
Tbh I think you should add it into the kernel, that way you won't have to rely on an app to fix touchscreen.
[Galaxy S II Original Android Development] ghmail2:
Yes add to kernel pls
[Galaxy S II Original Android Development] jlevy73:
TegraK please add the fix. It's annoying to have another service running in the background. Every time the screen turns on the service starts. It can easily be the source of wakelocks and lag. Adding it to the kernel would remove those issues.
[Galaxy S II Original Android Development] jlevy73:
No panics over the last several days. Seems nice and stable with very good performance and battery life
[Galaxy S II Original Android Development] shr33kant:
Currently using build 14, beta1. Everything seems to be running fine with no problems. Great Stuff!
[Galaxy S II Original Android Development] xeq544:
Im running on B14 without a single issue from the moment tegrak posted it. Its rock stable didnt have a single (unwanted) reboot or errors or anything.
[Galaxy S II Original Android Development] ferreinf:
Thanks, pretty happy with latest ninph, but as usual gonna give a try to luzactive... ;-)
[Galaxy S II Original Android Development] tegrak:
so, do you want to fix it to 0?

I tried with 0, but, actually, I couldn't catch the difference from 15.

hardcore set this value to 5 in his SpeedMod kernel.

what value is the best choice?
[Galaxy S II Original Android Development] shr33kant:
I never noticed it until i tried playing N.O.V.A. Couldn't aim for crap. After applying this at 0 I make headshots all the time :D.

Also..

I just got a wakelock in the middle of a skype call. I had some undervolting so that might be the issue...using beta1.

When using beta1 the tegrak overclock ultimate app doesn't show the startup confirmation of set on boot profiles.

P.S. Is there a way of adding GPU settings into profiles in tegra ultimate overclock app?

Edit: I just figured it out, if you keep screenlock/waking up, the phone crashes and won't wake up after the fourth one. I tried this with build 13 and no such crashing.
[Galaxy S II Original Android Development] tegrak:
about NOVA, it is too persuasive!

I just want to know what we get a harmful effect at value 0.

why did Samsung set it to 15? hm...

GPU profile.. I'll consider. and freezing issue is not happened on mine.

sometimes, you have to give more voltage when you change the kernel or upgrade the firmware.

some updated codes can make this happen. Samsung just test new code on stock voltages. then don't care about under-volted.
[Galaxy S II Original Android Development] vnvman:
Wow, this kernel+app combo made my week. I was getting a little bored with my "main" ROM (Oxygen, AOSP), so i decided to try out something different just for fun, but your awesome work on this project got me hooked so i just HAD to buy your app. Great performance, awesome battery life and full control of the kernel: i didn't know it was possible to get so much from a slightly tweaked stock ROM. Thanks so much Tegrak, you're awesome!

Hey i was wondering, ever thought of making some AOSP based kernel build? It would be great to have all of this fun avalable also on AOSP ROMs like CM or Oxygen, their default kernels run nicely but they lack any oc-uv feature :-/
[Galaxy S II Original Android Development] jlevy73:
I find setting it to '5' to be best. Where you can see the difference is when using the free app from the Market called Multitouch Visual Test. If you put your finger at the top of the screen and slowly drag it down at 15 you will see an initial lag. You still see it at 10, but at 5 is almost gone. 0 would be the best unfortunately the screen becomes too sensitive under certain conditions. So 5 seems to be the ideal if setting it to one number IMO
[Galaxy S II Original Android Development] shr33kant:
I tried it on 5. In games and such the jump is quite apparent. Perhaps setting it to 2 or 3 might be a good idea. The heightened sensitivity works well for me at 0 because I'm using sgp screen protector. I will have to test the beta kernel on higher voltages I'm regards to crashes on screen lock.

Edit: just tested on 2 and 3..using multi touch test it's still jumping slightly..enough for me to put it back to 0 (I can't get enough of being able to aim on fps games tbh lol).
[Galaxy S II Original Android Development] lpsi2000:
Unfortunately I don't use screen protectors and 5 seems to best settings around.:) I think if you are using screen protector then the app would be better for you. It is a difficult choice to set the setting to work well for PPL with screen protectors (considering the device did not come with a screen protector). Just my 2cents
[Galaxy S II Original Android Development] shr33kant:
Yeah..I guess I could live with using the app anyway.
[Galaxy S II Original Android Development] tegrak:
Guys, thanks for good opinions.

I think the best values is 2.

did you press "FF" button in video player?

see what happens with value 0 and 1 :)

edit) sorry, try long~ press
[Galaxy S II Original Android Development] steveman29:
I also think that the best value is 2.:)
[Galaxy S II Original Android Development] jlevy73:
I'm ready to flash it :D
[Galaxy S II Original Android Development] shr33kant:
Hadn't tried that..it would seem that 2 is the magic number then!

Trying beta 1 again with default settings and having no problems now. Excellent kernel!
[Galaxy S II Original Android Development] monkeydrufy:
sorry guys,

what is the difference between lulz kernel e tegrak kernel?

for the installation I have to flash the stock kernel before?

thanks
[Galaxy S II Original Android Development] NoPompem:
So will we ever be able to undervolt in smaller increments than 25mv? Is that possible by way of the kernel/app? I would love to get my i9100 tuned down by at least 5mv or lower.
[Galaxy S II Original Android Development] lpsi2000:
LOL, you must be pretty bored and have a lot of time in your hands. Stop tweaking the phone and start using:p. kidding but more power to you.
[Galaxy S II Original Android Development] cmd512:
Alrighty Tegrak, finally trying out your kernel. Hopefully KH3 battery life will improve...! :)
[Galaxy S II Original Android Development] cmd512:
OK, yeah, that touchscreen sensitivity app thing is annoying. Everytime I take the phone out of standby, I get the SuperUser Access granted message. Why would it need to get permission every single time?

Where is Beta 2 at... :)
[Galaxy S II Original Android Development] jlevy73:
That's the exact reason why we want it included in the kernel. The original code only worked while the device was on, once idled, it would kill the service. He tried to make it work but was unsuccessful.
[Galaxy S II Original Android Development] jlevy73:
Not possible. Voltage is done in steps of 25mV. This is hardcoded and atm, there is no way to change that.
[Galaxy S II Original Android Development] cmd512:
Yep, bring on Beta 2! Where's Tegrak at...! :)
[Galaxy S II Original Android Development] vnvman:
Same goes for the gpu clock values right? It would be great to have a step between 267 and 400, which i'm not likely to use on a daily base...that would be nice: we could have a more viable overclock option to improve performance without heating too much, maybe even keeping the stock voltage. My gpu settings right now are 267mhz@950mv and 160mhz@750mv super stable even stressing it with heavy games: is it just me or i got some lucky piece of hardware here? ;)
[Galaxy S II Original Android Development] jlevy73:
I'm not familiar with how the gpu clock works so I can't say for sure what can be done in terms of voltages. TegraK or someone with more experience would need to address that. I have similar gpu settings and never have heating etiher
[Galaxy S II Original Android Development] vnvman:
Yep, ofc it doesn't heat because it runs at a lower voltage compared to stock, that makes quite a big difference, even for battery saving purposes, especially if you're browser abuser like me. I'm quite sure i could afford something like 300-320 mhz@1000mv on my device, and ofc with minor heating because that is supposed to be stock voltage...i just hope that the lack of steps between 267 and 400 isn't due to some hardware factor, there are even 2 steps below 160, which is overkill to me because 200mhz is stable even at the minimum voltage on my device, so i don'even need those steps for underclocking purposes...
[Galaxy S II Original Android Development] cmd512:
Curious, you guys aren't posting internal voltages as of late, is it an accepted no no now to not mess with those? I know if those go too low, you can get data corruption, weird 3G issues, etc.
[Galaxy S II Original Android Development] vnvman:
Personally i tried tweaking them hardcore for days as well, but i found that battery life doesn't really take advantage from that (nothing i could notice at least). I could lower internal voltages without issues by 25 at every level, and at some even by 50, but if i go further down my uv setup is no longer stable at the core voltages i'm using now. I'd rather keep the internal value untouched as far as this allows me to play more with core voltages, while instead even a 1000mv nerf of the internal values doesn't seem to give a noticeable advantage in terms of battery life.

Just my 2 cents ofc...
[Galaxy S II Original Android Development] cmd512:
Hmmm, ondemand scaling is definitely smoother than lulzactive. When I open up my app drawer and I flick it from one end to the other (continuous scroll), there is 0 lag with ondemand. With lulzactive however, there is noticeable lag.

Minimal side effect if lulzactive give serious battery savings though. :)
[Galaxy S II Original Android Development] vnvman:
There's some bug with that governor right now, as Tegrak himself stated. Let's hope he can fix it because it'pretty good ;)
[Galaxy S II Original Android Development] cmd512:
Last post I saw was Tegrak saying he used beta lulzactive code for beta 5... but that was over a month ago. I'm thinking he should be using the current code, it's still not as smooth as ondemand though.
[Galaxy S II Original Android Development] scorpion667:
Good kernel. I love the GPU undervolt option.

Not too keen on playing with internal voltage (just did -25mv for all) I will wait for others to be the guinea pigs. As far as I understand this voltage affects the subsystems as well such as ram and radio which I sure as hell don't want to mess with.

Mhz Cv Iv

1204 1150 1075

1152 1125 1075

1100 1100 1075

1000 1075 1075

500 925 975

200 850 975

GPU

267 @ 950mv

160 @ 750mv

Leo 2.6 RevolutionROM

KH3 Modem

The CPU settings are solid as they were when I used SetCPU and did 30 minutes stress testing per clock speed, never had a crash since I started to UV a month ago. GPU I have no idea, ran Antutu like 5 times, Quadrant 5 times and played fruit ninja for 45 mins with no issues and best of all very little heat produced.

This kernel is the best I have used in terms of the phone producing the least amount of heat, which is a big deal for me. Undervolting, in my experience, does not do much for battery life unlike underclocking, but it makes having a dual core millimeters away from your skin much more bearable =D. Heat also degrades hardware over time as it causes electromigration.

I have only used it for a few hours so far and I absolutely love it. I have read in this thread that Youtube makes the device heat up under this kernel, my phone is actually cold when running YT =P.

The overclocking app is very intuitive and pretty cheap too. As long as future kernels remain stable, I will never use another kernel again. The only reason I used Ninphetamine was due to the sensitivity fix, but now that I found the screen sensitivity app there's no need for that. 0 sensitivity is mandatory for me, as an old time FPS veteran I have grown to despise any amount of input lag.
[Galaxy S II Original Android Development] caanda45:
Been playing all day with this kernel very very nice!!!!!
[Galaxy S II Original Android Development] scorpion667:
Ye I tried it today too I've yet to find anything wrong with it.
[Galaxy S II Original Android Development] cmd512:
The kernel is good, but I've gone back to ondemand governor. Lulzactive caused strange lag here and there...
[Galaxy S II Original Android Development] scorpion667:
Curious are you using touchwiz or a different launcher?

I'm running a modded touchwiz and I have yet to notice any lag, that's why I ask maybe there is a problem with custom launcher not triggering rampup clock from lulzactive
[Galaxy S II Original Android Development] cmd512:
I'm currently using ADW Launcher Ex. It is specific to lulzactive, lag disappears after switching back to ondemand.
[Galaxy S II Original Android Development] scorpion667:
using this combo:

leomar 2.6

lulz 14 beta1

kh3 modem

I have zero issues. Zero. The undervolts are rock solid, everything is smooth, and the phone does not heat at all anymore. The GPU undervolt seems to have helped with this. The sensitivity fix would just be icing on the cake. I am extremely impressed with this kernel, and I've tried almost all of them. I vote for release!
[Galaxy S II Original Android Development] :
+1 *10 chars*
[Galaxy S II Original Android Development] vnvman:
Yep, it rocks. Btw Tegrak oc is an app i didn't regret buying at all, i like to know that my money goes to the maker of this masterpiece. Just buy it people, it's cheap for what it offers. Keep it up man :)
[Galaxy S II Original Android Development] antiochasylum:
Maybe I'm just being retarded here. So feel free to call me dumb lol, however OP says supports 4.0.1.4 cwm. So I was assuming that recovery and not Tegrak recovery....am I wrong here?

Unless support meaning it has the same functions as cwm built into Tegrak recovery??

Sent from my Cognition powered SGS2
[Galaxy S II Original Android Development] vnvman:
You got 2 of them: cwm 4.0.1.4 AND the Tegrak recovery. You can choose which one to access when you reboot into recovery from the menu that will appear (vol up/down and home button to choose).
[Galaxy S II Original Android Development] tegrak:
I finished to modify touch screen driver.

applying the value without a background service and rooting. (but need supported kernel, I'll share this patch code.)

Now I am going to make a control app.
[Galaxy S II Original Android Development] shr33kant:
Woot! Does that mean we will be getting build 14 beta 2 soon? :)
[Galaxy S II Original Android Development] vnvman:
Hmmm, i smell build 14 final instead ;)
[Galaxy S II Original Android Development] kbnguy:
TEASER! :p