yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] fulmerville:
I tried using 1.6 on my NTT version and couldn't get the tv to work. It would just hang on launch. I flashed back to the stock kernel (rooted) and i could launch it. Will 1.7 fix the issue ?
[Galaxy S II Original Android Development] vandanh15:
who guide me in detail how to set GPU.
[Galaxy S II Original Android Development] gokhanmoral:
i removed v1.7.1 as I made a huge mistake :)

if you have flashed it please revert back to 1.7.
[Galaxy S II Original Android Development] kalpik:
LOL! Just flashed 1.7.1 :p

Would be nice to know what the mistake was :D
[Galaxy S II Original Android Development] superpuper:
On stock KI3 rom gpu uv is not working , or my gpu is stable 160@500mv./

And locking to 160/160 do not affect benches compared to 160/267
[Galaxy S II Original Android Development] kwerdenker:
That would probably explain the hang I got after rebooting from flash ^^

On another note: I don't know why but with the 1.7-stable release I get lockups while screen-off using UV settings that are rock-stable in 1.7rc1. Did you change anything that could explain this?
[Galaxy S II Original Android Development] gokhanmoral:
no, nothing has changed to cause that except for the optimization flags... hmm...

let me revert back to rc1 flags then... I will compare what else I have changed..
[Galaxy S II Original Android Development] BoneMo:
flashed via recovery or a .tar file ??
[Galaxy S II Original Android Development] Dark_Lord0122:
flashed 2.2 beta 1 ( CWM ) and its working perfectly :)
[Galaxy S II Original Android Development] KennyLegend:
Flashed fine from Speedmod k2-16
[Galaxy S II Original Android Development] BoneMo:
CM7+Syiah 2.1.1 >> CM7+Siyah 2.2b1 = no problems

so now i do not understand why someone had problems when so many people dont have problems...also me :)

Thx for kernel Gokhanmoral
[Galaxy S II Original Android Development] Molitro:
I forgot to say CWM. Also, 2.3.5 KI4.

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] xan:
Cant get 2.2 to run.

Logcat output attached.

tried flashing from CWM and from Odin (took CWM's zImage)

Stock (Odexed!) Samsung KI3 + Jkay,

flashed from 2.1 and ninpheatamine 2.1.3
[Galaxy S II Original Android Development] joeyfong:
I am fine for upgrading to 2.2 beta on cm7
[Galaxy S II Original Android Development] ludow:
Stuck on white Samsung Galaxy S II logo. Updated via CWM.

Stock KI8 odexed. Talking anout 2.2 beta 1. :p
[Galaxy S II Original Android Development] hausmanis:
I went from Siyah 2.1.1 to 2.1 beta1 with insanity rom CM without any problems at all, running smooth
[Galaxy S II Original Android Development] energie:
flashed via CWM and its going percetly.

good performances battery.

MIUI+ 2.2b1
[Galaxy S II Original Android Development] chanw4:
Flashed CM7 + Siyah 2.1.1 >> CM7 + Siya 2.2 b1 via CWM Recovery (not CWM app) and no problem at all.
[Galaxy S II Original Android Development] xavihernandez:
Where to find v2.2b1 please?

It seems that owner site is not reachable (at least siyah part).
[Galaxy S II Original Android Development] fasst:
I think I, maybe, see a pattern here now and what the above postings shows.(Maybe exept posting #9038 that says fine on Ki4(stock?)

That 2.2.b1 has problems with stock Samsung roms.

Tried reverting from KJ2 to KI8, same problem.

Back on KJ2 with 2.1.1 for now.
[Galaxy S II Original Android Development] sebsasko:
http://www.gokhanmoral.com/

It's working... I just tried
[Galaxy S II Original Android Development] :
You might be correct, I just tried on stock XWKJ3 ;) with new and old bootloader and it gets stuck on first screen.
[Galaxy S II Original Android Development] lpsi2000:
You right the issue might be with just stock odexed ROM, because I don't use stock personally. But I have tried the Kernel with VR30 (Samsung custom deodexed ROM), CM, and MIUI and I don't have any issues. I am now back on VR30 and things are pretty smooth for me.
[Galaxy S II Original Android Development] Dark_Lord0122:
ever since flashing 2.2 beta 1 my battery is acting weird . it won't charge to 100% .. it gives notification that it did as soon as i remove the AC charger it shows 98% .. i plug it in again and after few minutes it gives notification that its full i pull it its 100% .. i close the phone and plug it again it still charges! this is weird .. going to wipe battery stats just in case .
[Galaxy S II Original Android Development] yoplaboum:
Or in my mirror... in my signature
[Galaxy S II Original Android Development] aegeuss:
I don't share the common idea of the new beta problems with stock roms.

I have used and am using this last beta with both KI8, made with Rom Kitchen and stock KJ2, v8, uploaded by Tricky103 in the same thread last night.

I do believe there's a problem for some users; but there are of those who installed and use this last beta without a problem; I have used the .tar version with Darky's tool by the way. I never had a reboot or stuck problem etc. I was using Siyah kernel 2.1 before the beta.

Regards.
[Galaxy S II Original Android Development] antt00:
2.2 beta 1 is really smooth and fast. No issues encountered yet.
[Galaxy S II Original Android Development] kwerdenker:
The idea with the odexed stock roms is a good one. My theory so far is, that some change in the new kernel invalidates the dalvik-cache, so on reboot the system tries to rebuild it (as it happend to me). But somehow this fails with odexed roms and these get the stuck at boot error.

So maybe everyone on ODEXED roms should refrain from flashing the new beta until this gets sorted out.

Apart from this problem, the new kernel is running as smooth as the 2.1.1 with equal battery life for me so far

---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------

Are the kitchen roms odexed or deodexed?
[Galaxy S II Original Android Development] :
Kitchen roms are deodexed.

And yes, cannot get 2.2b1 running on odexed no matter what I try.
[Galaxy S II Original Android Development] idealforyou:
EnableLogger.zip don´t work on SiyahKernel 2.1.1. With Siyah 2.0 work EnableLogger.zip fine. Please fix it on Siyah 2.1.1.
[Galaxy S II Original Android Development] kwerdenker:
Hmm... well, there goes this theory ^^ This is indeed a strange thing. I still think though, that my cache rebuild and these stuck at boot errors are somehow connected.
[Galaxy S II Original Android Development] :
As I wrote yesterday, even on deodexed ROM's if I flash CSC pack (which contains cache.img and hidden.img) via Odin 2.2b1, fails to boot (other kernels and 2.1.1 work fine). So yes, definitely something to do with cache rebuild.
[Galaxy S II Original Android Development] kwerdenker:
Sorry, I must have missed that post. Probably not a good thing to read the thread on my mobile inbetween BF3 rounds ;)

We propably have to differntiate a bit, what we mean by cache. I refer to the dalvik-vm cache under /data/dalvik-cache which shouldn't be touched by an image you flash, since it's build by the vm of your phone and it's this build up process, that looks like the culprit to me. Do you by any chance have a log of the boot process after the csc flash?
[Galaxy S II Original Android Development] timberwolf60:
I was on deodex xwkj2, siyah 2.1.1 kernel, flashed multi OXAKI3 CSC. Phone stuck at Samsung splash screen. So I used Odin flashed stock kernel and CSC as once go. It fellow a full wipe to factory state. After I used DarkyROM2 to flash siyah kernel.tar and restore back my programs. Done and enjoy!
[Galaxy S II Original Android Development] Molitro:
Mine is a deodexed KI4. It isn't stock, but isn't a common rom either, I made it myself based on Exynos and an AOSP theme.
[Galaxy S II Original Android Development] :
Unfortunately not, and I am on XWKJ3 stock already now. Well you are more knowledgable than I am, but in CSC pack from Intratech thread there are 2 files cache.img and hidden.img that are flashed via Odin. So I guess I am talking about /cache, right?

---------- Post added at 02:26 PM ---------- Previous post was at 02:24 PM ----------

Yep, that way works.. I incorporated Siyah zimage in deodexed ROM and after flashed CSC.
[Galaxy S II Original Android Development] kwerdenker:
[This post has been superseeded by the progression of time :) ]
[Galaxy S II Original Android Development] gokhanmoral:
can you try beta2 and tell me if same problem exists? (bootloop or stuck on boot)
[Galaxy S II Original Android Development] iron@ss:
Beta2 is showing as beta2 for .tar but as beta1 for CWM .zip file! :confused:
[Galaxy S II Original Android Development] :
Unfortunately still the same on stock odexed ROM - stuck on boot.
[Galaxy S II Original Android Development] gokhanmoral:
updated.

thanks for reporting.
[Galaxy S II Original Android Development] kwerdenker:
Flashed 2.1.1 and then flashed 2.2b2 and I'm still getting the cache rebuild on reboot after flash. So the cause still seems to be there.
[Galaxy S II Original Android Development] gokhanmoral:
it takes longer to boot and rebuilds the cache (just like when you clear cache in CWM recovery and boot)

but it is fixed in beta3 :)
[Galaxy S II Original Android Development] BoneMo:
no problems on CM7 nightly106
[Galaxy S II Original Android Development] :
Confirmed.. stock ROM's work now with b3 :).
[Galaxy S II Original Android Development] kwerdenker:
The dalvik-vm keeps a cache of optimized versions of the apps you have installed on your phone. Normally, this cache is only rebuild on boot if there are mayor changes to the system. That's why the first boot after flashing a new rom takes longer but it shouldn't happen when flashing a new kernel
[Galaxy S II Original Android Development] xavihernandez:
Thanks for replies men. Well it seems that I can't access site with mobile. Then I have downloaded file thru PC.
[Galaxy S II Original Android Development] kwerdenker:
I can confirm this too. With beta3 the reboot is as fast as ever :)
[Galaxy S II Original Android Development] iron@ss:
Just used Recovery (not CWM kernel flash) to flash 2.2b2 with no problems at all.

Booted up straight away.

On CheckROM Revolution.
[Galaxy S II Original Android Development] droidphile:
+1

No problems with beta3.

Even with beta1, there was no bootloop which halts the booting, it just took longer than usual. That's all. (Running GingerMod 0.7 ROM)

Btw, with lulzactive gov and min freq set to 25, voltage control doesn't show cpu settling down to 25 mhz after jumping around a bit. The stepping rather stops at 200 mhz as if 200 is the min frequency.

With ondemandx, i can see freq settling down to 25 mhz after a while.

Anyone else facing this issue?
[Galaxy S II Original Android Development] mark2222:
Finally 2.2b1 seems stable with lower voltages at 100 and 200 just like 2.0 was. Also and this is strange, with 2.0 I use the app 'smart app protector' where you enter a pin for certain chosen apps. You only have to do this once after unlocking but with 2.1 I had to keep entering the pin for each app i open but with 2.2b1 I don't again (thankfully). If you have any idea why this is please keep it in future versions.

Also has something changed re stability at lower voltages?
[Galaxy S II Original Android Development] fasst:
2.2.b3 confirmed working with stock Samsung KJ2, that was stucked on boot with 2.2.b1

Everythings back to normal.

Thanks gokhanmoral.
[Galaxy S II Original Android Development] lpsi2000:
Logging is working well on beta 2.2, try that one.
[Galaxy S II Original Android Development] droidphile:
Just noticed that on every reboot, time spent on boot logo is a little longer on 2.2 betas (including beta3). Some times, i think time spent on displaying boot logo is more than the time spent on playing boot animation :)

Btw Gokhan, reverted touchscreen sensitivity parameter to 5? :)

No other issues with beta 3. GingerMod rom and Siyah kernel makes GS2 sweeter everyday!
[Galaxy S II Original Android Development] :
but touch sensitivity acts strange while on charger.. maybe it is just me.
[Galaxy S II Original Android Development] yoursong:
Hi,

a few people already noticed that transparent proxies like orbot/tor are not working.

Is is possible to include iptables match "owner" module in your next builds?

Keep up the great work!

Thanks

yoursong
[Galaxy S II Original Android Development] yoplaboum:
2.2 beta3

Mirror updated: http://aideadsl.com/sgs2/kernel/
[Galaxy S II Original Android Development] SupraN0va:
@gokhan

I would call the betas , nightly like CM does. Every night a new beta-> nightly.^^
[Galaxy S II Original Android Development] droidphile:
You mean on wall charger? No probs here on wall/usb charger.
[Galaxy S II Original Android Development] :
Yeah.. don't know why, maybe it is KJ3 or just me. Didn't happen with this kernel ever.
[Galaxy S II Original Android Development] iron@ss:
Siyah kernel beta3... again, no problem flashing using Recovery (not CWM kernel flash) and no problems with boot animation (Nexus Prime).

Much better than 2.1 on 100MHz. No touch problems.

Using CheckROM RevolutionHD with JKay theme.

:)
[Galaxy S II Original Android Development] peachpuff:
Of course, just flashed 2.2b3 and the usb charging option doesn't show up in Voltage control with a kj2 rom.

Sent from my GT-I9100
[Galaxy S II Original Android Development] droidphile:
Are you using the original Samsung charger?

The electromagnetic noise injected by some bad chargers (onto our capacitive touch panel) can cause decreased touch sensitivity since the noise can alter the signals detected by touch controller.

And, are you using sgp screen protector?
[Galaxy S II Original Android Development] chadouming:
All options are ok for me with 2.2b3 and Galnet MIUI 1.11.6
[Galaxy S II Original Android Development] :
Yes, original samsung charger, no screen protector. Just stared to happen with 2.2.. As I said it never used to happen with this kernel before. Strange.
[Galaxy S II Original Android Development] 0355:
Just to say thanks,

standard Siyah 2.1.1. Great kernel, hands down.
[Galaxy S II Original Android Development] kalpik:
@Gokhanmoral: 2.2b1 was super smooth for me! b2 and b3 have a bit of stuttering here and there.

It might be the config change you talked about earlier.
[Galaxy S II Original Android Development] midreestaj:
Very much pleased with performance of 2.2beta3.. absolutely no issue of any sort at all. Battery life is great and as desired easily lasts 30 hours with 40 mins voice calls, 4 hours of screen, and continuous data ON state. Antutu scored 7560. Less heating up issue on camera area.. no force closes.. running ICS v2 and well there as well no issue. lag free menu and moving between emails, messaging and browser on CheckROM v2.2.0

A+ work from Gokhan.
[Galaxy S II Original Android Development] :
Benchmarks, benchmarks again! I don't even care on changing anything.. All default.
[Galaxy S II Original Android Development] frankcilo:
Ho, Goh,.I have update to beta 3, but cpuspy continue to not read my modified frequency value...

Why?

Thanks
[Galaxy S II Original Android Development] KennyLegend:
Anyone know the optimal charger setting and should the usb charger be set to the same as ac?
[Galaxy S II Original Android Development] sebsasko:
Have you tried to clear CPUSpy Datas in settings->applications->"manage applications" ?
[Galaxy S II Original Android Development] kwerdenker:
If you want the optimum, look at your charger, find it's maximum output current and use that one. Since most chargers for phones dont exceed 1000mA/1A output current and since the phone will only draw as much as the charger ist willing to give, you can probably just set AC and Misc to 1000. You shouldn't under any circumstance change the USB setting though, because that one is used if connected to a data usb port like the one on your pc. USB specification dictates that a device should not draw more than 500mA from such a port and most mainboard usb ports are properly capped to that value so that nothing bad happens, even if you would allow your phone to take more. But sometimes this is not true and you could do some serious damage to the usb port, your mainboard and/or your phone if it tries to exceed these specifications.

Keep in mind, that the increased loading current might lead to a shorter battery lifetime.
[Galaxy S II Original Android Development] KennyLegend:
Thanks for that. I guess optimal current is the default one so.
[Galaxy S II Original Android Development] AndreiLux:
What exactly did you do to the TVout driver? The MHL routines are still in there and kicking as far as I can see from dmesg logs. Maybe I'm mistaken.
[Galaxy S II Original Android Development] frankcilo:
Yes, but not work!!:(
[Galaxy S II Original Android Development] gokhanmoral:
hmm...

I have disabled CONFIG_VIDEO_TVOUT and it prevents the compilation of s5p_tvout.c where tvout_resume workqueue is defined and used.

I did not look into the code thoroughly. maybe something else needs to be disabled as well..
[Galaxy S II Original Android Development] gokhanmoral:
are you sure that you modify the steps and the modified step is used?

if it is not used it will not be updated.

for example: if you modify 100 mhz and make it 25 but you use 200 as minimum nothing will be updated and you will see 100MHz in cpuspy...
[Galaxy S II Original Android Development] AndreiLux:
I actually looked through the config files a few weeks ago and there's a lot of entries regarding the video functions, entries for HDMI, several for TVOut itself, MHL, and so on. The interesting one would be the one that triggers the MHL IRQ on every wakeup, maybe that helps you.
[Galaxy S II Original Android Development] frankcilo:
Yes, sure!

The funny thing is that when I installed 2.2beta1, everything worked perfectly. Then after an hour did not work anymore, even updating the kernel to v2.2beta3.

In sys / devices....freq_tab my new value are present (1500 1400 1200 1000 800 600 300 100)
[Galaxy S II Original Android Development] gokhanmoral:
you are right. there is another part in the config for "Samsung Mobile HD Link Interface"

I'll check it.
[Galaxy S II Original Android Development] olifee:
At least, that first change was already sufficient to break the Samsung MHL-adapter for me (so I cannot get a picture via the HDMI-adapter anymore).

Apart from that, the new version is running great, I am looking forward to the next beta(s) with TVout-module(s) ;-).

EDIT: It appeared (when the adapter was working), that the device outputs native device-resolution via the adapter in normal operation. FullHD appears to be used only for hardware-decoded FullHD-videos. That might explain several different parts of the driver. With 2.2b3, both those functions are broken for me ;-).
[Galaxy S II Original Android Development] AndreiLux:
Well that's the point, it's supposed to be broken. Ripping it out completely might reduce wakeup times and improve power drain by a little bit.
[Galaxy S II Original Android Development] olifee:
I know, I would also like it to be broken and then use a module to activate it when needed.

I was just not sure if gokhan knew that this first change was even affecting the tv-out-support, because as you noticed, the battery-eating mhl-stuff is still kicking in the logs.
[Galaxy S II Original Android Development] m00moo:
51% left and so far 20 hours and 45 minutes basic usage. Few phone calls, emails and about 50 texts. FB/Twitter sync every hour, some web browsing and games too. Awesome! 2.2b1 100/1200 100/267 uv Smartassv2.

I think screens been on about 2 hours. Having a problem where my phone is showing an accumilated display on time and not since last boot. Any idea how to revert it to since last boot? Tried asking in MIUI but no replies.
[Galaxy S II Original Android Development] cmd512:
I think the default touchscreen is set to 5. Anyway we can modify this to 0? :)

Thanks!
[Galaxy S II Original Android Development] Grimmy1st:
To all the people who likes to play around with charging limits: every secondary Battery has an optimum for charging, this is checked by so called c-rate tests. Charging with changed currents will cause in long term damages of the Battery or at least limited capacity after some circles. I just want to warn you...

Written by a chemist, working in a group with lot of Battery topics...
[Galaxy S II Original Android Development] Silberpfeil3110:
This kernel is only one thing...

AWESOME!

No lockscreen lag, when turning on, everything smooth, low battery drainage...

There is only one thing to top my enthusiasm... Option to run on CRT! :D
[Galaxy S II Original Android Development] tolis626:
Gokhan,for me even beta3 did something akin to what happened with beta1.First boot after flashing(No,I didn't wipe cache or anything and flashed the .tar with Darkytool) took a while.Not as long as after wiping dalvik(On my device it takes ages to boot when I wipe dalvik.Keep in mind that I have 300 megs left in app storage. :p ) but longer than normal.A simple reboot was maybe faster than ever.Strange...

Anyway,that and...Did you think about actually overclocking the bus? :D
[Galaxy S II Original Android Development] nikzDHD:
These scripts are working well using the newest beta. Small bump for those wanting to try these out. Thanks, I would of been lost without these ;)
[Galaxy S II Original Android Development] r8zer:
Wow this kernel is amazing look at this

(joke)

But this kernel is amazing though.
[Galaxy S II Original Android Development] crypticc:
Deleted: probably talking cr4p
[Galaxy S II Original Android Development] Bloodloaf:
@r8zer

Whats the name of this app ?
[Galaxy S II Original Android Development] r8zer:
what app, i took the screenshot with the inbuilt screen shot key press.
[Galaxy S II Original Android Development] kapa75:
Hi gokhan :)

I have a lot of bugs (screen of death, freeze etc...) since the 2.1.1...

I tried the latest 2.2 beta, and GC's version of the kernel, still have bugs... :(

(I use no uv/oc)
[Galaxy S II Original Android Development] nikzDHD:
Seems like battery indicator.

---------- Post added at 09:14 PM ---------- Previous post was at 09:14 PM ----------

What rom are you on? Did you wipe data?
[Galaxy S II Original Android Development] psychoid:
he meant the one that showing the hours since unplugged :D
[Galaxy S II Original Android Development] r8zer:
ohh sorry, yer battery indicator. My bad!!
[Galaxy S II Original Android Development] Bloodloaf:
Thx :)
[Galaxy S II Original Android Development] lpsi2000:
@gokhanmoral,

I don't know what was going on with 2.2 B1 but please do not lose these settings or configuration. I think the only issues I saw with that one was the odexed ROM which I don't use:p. But on the serious side, B1 is a serious performer both at battery life and 0 lag for me.

Unbelievable, but I am at 85% right now after 7 hours of light usage. Pushed e-mail on, Weather updates every 15 mins, social medial and news every hour, and a few more things running in the background.

I believe there is an app for that (Touch Move) in the market from the retired kernel dev:rolleyes:

LOL, I am afraid to try beta3 right now, but I will soon after testing some more with beta1.
[Galaxy S II Original Android Development] kapa75:
=> Yep, I wiped cache/data/dalvik/fix permissions :(
[Galaxy S II Original Android Development] r8zer:
No problem, getting late brain switching off, it only reads that cause i forgot to wipe battery stats.
[Galaxy S II Original Android Development] zorkis:
Confirmed. Its quite laggy for me. Everything is microlagging in MIUI. :(
[Galaxy S II Original Android Development] maxeli:
Same here... Plus extreme overheating
[Galaxy S II Original Android Development] _cummoo:
..nice to feel that, but i have to say the good old days are back :cool:

This kernel now has to be called "Supersonic Siyah" ..hehe..

After an extended period of testing 2.2b1, 2.2b2, 2.2b3 (on AOSP and SAMSUNG ROMs), 2.2b1 has finally made the job !!

Although there are the 'well known' boot-issues on 2.2b1, the performance is totally awesome !! :D

P.S. ..still the best kernel and there is nothing you can do about it :p