yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] mar72:
I use Siyah 2.0, my settings : Clock-Voltage 100-800, 200-800, 500-825, 800-950, 1000-1025, 1200-1125, Scaling : ondemandx , is very stable. I tried Siyah 2.1 RC1 and any change network from 2G to 3G will cause freeze phone.
[Galaxy S II Original Android Development] Tsukihime:
what's the version of busybox ? Is it 1.19.2 ?
[Galaxy S II Original Android Development] victaaaa:
Can anyone get keyboard/mouse connected via USB OTG on this kernel?

Its not working for me, but it works on Ninphetamine.
[Galaxy S II Original Android Development] GDT:
I'm using these voltages:

1600MHz	1400mV

1400MHz	1300mV

1200MHz	1175mv

1000MHz	1075mV

800MHz	975mv

500MHz	875mV

200MHz	825mV

100MHz	825mV

As you can see they're very close to yours.

A little question: I'm using Voltage Control App and ma min/max clock values are 200/1400MHz. But if I reboot my device they will turn back to 200/1200MHz. What can I do?
[Galaxy S II Original Android Development] aDEO:
It is 1.19.1
[Galaxy S II Original Android Development] :
Ah well.. Hard life.
[Galaxy S II Original Android Development] aDEO:
Just save them as boot settings from Voltage Control menu and reboot to try them :)
[Galaxy S II Original Android Development] GDT:
Is what I do... I checked the generated file under init.d folder and it seems to be correct.
[Galaxy S II Original Android Development] chadouming:
Mannualy erase the one there with root explorer or super manager then re-do save as boot setting with the good settings.
[Galaxy S II Original Android Development] the^one123:
did you choose "save boot settings" in menu?

Theone

edit: sorry too late have a bad connection here.
[Galaxy S II Original Android Development] atlaswingpasaway:
I wanna try this but my gs2 is from US... :(

So it should be subtitled, "ONE KERNEL TO RULE THEM ALL IN EUROPE"
[Galaxy S II Original Android Development] philip979:
USB host

Please add usb host, to support connect devices such as mouse
[Galaxy S II Original Android Development] GDT:
tried this one too. Doesn't work.

This is my init.d script folder with generated file from voltage control app:
[Galaxy S II Original Android Development] YG007:
I'm not sure if it happened before 2.1b13 because I started to use this kernel since then, but with this kernel, b14, and RC1, when I play HD mkv and mp4 files, I get a microstutter every 5 seconds, and every other kernel plays mkvs totally fine.

I'm running RC1 with nothing added, and with Cognition 1.6 rom.
[Galaxy S II Original Android Development] WLamers:
Have exactly the same problem, appears from b13 till rc1. I'm on Ceckrom Revolution 1.0. File in init.d looks ok. Voltage settings and charger settings work.
[Galaxy S II Original Android Development] gcrutchr:
Just tested using QQ Player and rc1. No microstutter. Runs okay. Using JPKJ2 ROM.

Played a 1080p .mkv file
[Galaxy S II Original Android Development] YG007:
I'm using the stock player.... and I just tested copying the file to the internal memory, runs fine with no microstutter whatsoever. ...but from the microSD card, there is a microstutter every 5 seconds or so. I know my card is good enough because on the stock kernel, and with Ninphetamine-2.1.3, the files play smoothly off the microSD and with the stock player. (BTW, the Cognition 1.6 ROM is KI3)
[Galaxy S II Original Android Development] gcrutchr:
Actually, I had copied the file to my microSD and ran it from there.
[Galaxy S II Original Android Development] GDT:
Same rom. Did u try to revert back to b12?
[Galaxy S II Original Android Development] _cummoo:
Had no time for extensive testing, but from my point of view 2.1 rc1 feels very good, snappy, smooth and fast with no issues on RevoHD in the last 5 hours.

mkv playback is very fluent here.

So i would say the magic is back ! :p
[Galaxy S II Original Android Development] incubus_fr:
No, "ONE KERNEL TO RULE THEM ALL EXCEPT IN THE US". That's a huge, Worldwide, difference :D
[Galaxy S II Original Android Development] Molitro:
Is there a thread with the description of the schedulers like the one with the goverors?
[Galaxy S II Original Android Development] tolis626:
Exactly.Gokhan is from Turkey,which *technically* is in Asia(although Greeks and Turks almost share the same seas),and there is a version for NTTDoCoMo in Japan.So yes,only Americans are unlucky this time! :p

Guys,I want to report a bug.My relatively heavy undervolting(in my sig) still works in RC1.No crashes,no reboots no nothing.What is wrong with my phone? :( :p

Gok,along with the busfreq stuff,will you let us control internal voltages too or is that irrelevant?
[Galaxy S II Original Android Development] spaxx24:
Haha, "I found a bug, my phone is working.." x)
[Galaxy S II Original Android Development] jim-bo:
*sigh* don't people ever use search anymore? You're not supposed to use your own undervolt settings, you are meant to copy them from some random user who posted them up on the thread for a completely different kernel!

If you absolutely insist on using your own, you'll need to knock at least 50-75 mV off the figures in your sig to ensure proper crashing and instability!
[Galaxy S II Original Android Development] Guetta1:
RC1 is a good one ;)

works like a charm and fast like hell :D
[Galaxy S II Original Android Development] tolis626:
Exactly!I fixed it by undervolting 1600MHz at 800mV! :D :p

Oh,ok...I didn't know,sorry! :)

I searched as you told me and found some nice undervolt settings over at the Sensation forums.I hope they crash my phone properly this time... :p

(I think we should stop this here.Some guys won't understand it's a joke :p )
[Galaxy S II Original Android Development] lpsi2000:
I have magic trick for you, when your MIUI phone is ringing with the black screen, put your hands over proximity sensor quickly, then remove your hands, voila your phone should come alive:D so you can answer it.

This American is not so unlucky because I picked up a unbranded SGS II when it came out months ago. I also have the same bug you mentioned above my phone works. I only had issues with beta15 and I think all of us did.
[Galaxy S II Original Android Development] CA3iR0:
And also making calls! A few minutes ago i made a call and as soon as i pressed the call button, the screen went black. WTF? Weird...
[Galaxy S II Original Android Development] lpsi2000:
LOL, I have no plan on fixing that bug..
[Galaxy S II Original Android Development] Denwa:
Which model are you guys talking about?
[Galaxy S II Original Android Development] Schindler33:
Are you intending to include the sharpness and color saturation tweaks from hardcores kernel? If find them quite pleasant.
[Galaxy S II Original Android Development] JaviLoL:
MIUI 1.10.28 here.

When plugging usb to pc, drives don't mount. They did when using default MIUI kernel.

Am I missing something?
[Galaxy S II Original Android Development] droidphile:
Have you seen this ? :)

http://xdaforums.com/showthread.php?t=1241590
[Galaxy S II Original Android Development] nerotix:
You were just late with buying the best phone in the world.. u dont have the INTERNATIONAL version ;) So its still all over the world, u were just late! bleeeh:p
[Galaxy S II Original Android Development] Vulpix:
Does 2.1RC1 have auto-root? Or is this option removed altogether now?
[Galaxy S II Original Android Development] Zanr Zij:
with one laptop ( HP Elitebook 6930p ) same 2 U, with another ( VAIO TT ) usb storage mount ok. I think the reason is adb. I installed adb on Elitebook and not on VAIO TT.

Edit adb text build.prop make USB debugging notification disappear when unplug.

So 2.1RC1 could have problem on adb :D
[Galaxy S II Original Android Development] chadouming:
Auto-root was removed. If you want to root your phone, try to flash CF-root first then flash siyah ^^

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

Using it in canada :D thats worldwide :P
[Galaxy S II Original Android Development] psychoid:
are u on sammy or cm?i never got antutu score like that.. i only got 7109 max.. if u on sammy.. how the hell did u do that? pm me for your secret please :D
[Galaxy S II Original Android Development] Zanr Zij:
Totally, that app fake :)

---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------

Using 2.1RC1, set CPU clock min = max frequency = highest possible ( 1696 ), governor = performance, scheduler = vr, gpu clock 2D=3D=400MHz. You will rule almost benchmark if you do about atleast 10 times a test soft :D
[Galaxy S II Original Android Development] droidphile:
??!! Are you implying that Supercurio doesn't know about screen rendering and calibration? You kiddin' me? :confused:
[Galaxy S II Original Android Development] chadouming:
Are you really telling that supercurio is fake ??
[Galaxy S II Original Android Development] minidou-77:
Its not fake but its not really important right now

Just wait one month ;)
[Galaxy S II Original Android Development] Entropy512:
Or just use ADB to push su/Superuser.apk to the right places, or flash one of the su packages in CWM...
[Galaxy S II Original Android Development] Galaxy_Fan:
Ok, but this is the first time that a beta kernel is working better for me. I tried all versions from day to day (or hour to hour like gokhanmoral published :-) ) and the best one for me is b14.

- App Protector works without flashing loggerscript (perhaps logging is enabled in beta?!)

- highest score in antutu

- no stuttering in SBP3D Drawer with ondemand/1200MHz

On RC1 I have stuttering, lower score and app protector don't work proberly, so I stay on b14 :D
[Galaxy S II Original Android Development] maxeli:
Search this thread, it's been mentioned 15 times now, and 15 users have posted links to the specific thread
[Galaxy S II Original Android Development] psychoid:
i've tried max 1696 @ 1475mv and got freezed when i just start the test with antutu ..
[Galaxy S II Original Android Development] :
Sammy :) don't know I was surprised also :)
[Galaxy S II Original Android Development] the^one123:
My score.first run with rc1.1600mhz performance gov.no gpu oc.
[Galaxy S II Original Android Development] xuxuzao:
but black screen when receiving call persists =( heheh
[Galaxy S II Original Android Development] h20pt:
I'm using Andrev OC with a script to undervolt CPU/GPU and another one created by me to keep sampling rate at 10000us to avoid any kind of lag.

Working great so far..

Battery life and performance are amazing :p

Waiting for v2.1 final :D
[Galaxy S II Original Android Development] galanakop:
watt rom????
[Galaxy S II Original Android Development] the^one123:
CheckRom Revolution 1.0
[Galaxy S II Original Android Development] olifee:
I can confirm USB-OTG is broken with 2.1 for non-mass-storage (don't know since which beta exactly).

This means neither mice, keyboards, nor the usbserial-devices work (although the modules are there and load, I tried just now to connect something and the mobile did not react!).

You basically get

hub 2-0:1.0: USB hub found
=> case SetPortFeature -USB_PORT_FEAT_POWER
=> OTG HCD Initialized HCD, bus=C110 OTG Controller, usbbus=2
usb otg host : registered
host_notify: ndev name=usb_otg: from state=2 -> to state=1
usb change mode ret=0
=> case SetPortFeature -USB_PORT_FEAT_INDICATOR
=> case SetPortFeature -USB_PORT_FEAT_RESET
usb 2-1: new full speed USB device using s3c_otghcd and address 2
usb 2-1: parent hub has no TT

Thanks to DarkEN_ANGEL for giving me the hint to really check it ;-).

@gokhanmoral: Seems some features are wrongly expected / detected in current usb-drivers? In case you can not identify the problem easily, I can confirm it worked with 1.8 and 2.0. If you want, I can try to do a binary search on your 2.1-betas ;-). EDIT: see below, the culprit is present at least since 2.0 (I only tested the modules with FTDI, mice and keyboards for 1.8...).

Did you see this:

http://xdaforums.com/showthread.php?p=18825615#post18825615

which appears to fix things for people complaining about CWM5 not working?

EDIT: Found something. Starting 2.0, the line "dev_err(&udev->dev, "parent hub has no TT\n");" is included in "drivers/usb/core/hub.c" (which source brought that one in? Update3, or the update to 2.6.35-14?).

Some people had problems with the experimental staging usbip-stuff on desktops which looked exactly similar, caused by some missing support for TT in usbip. The fixed their problem by commenting the corresponding lines (see http://www.incentivespro.com/forum/viewtopic.php?p=905&sid=92e1d6ba3399bf8b9fabded94f4c69b9 . This is now fixed in usbip.

So the easiest route to go would be to comment the TT-checking-stuff after determining what source brought it in so we have something to blame :P.

EDIT2: TT means "transaction translator" and is needed for USB 1.1-support, so I guess, all USB 1.1-devices should not work (which mostly includes input-devices, FTDI-chips and stuff).

If device is connected to a hub which is connected to the phone, it can not activate the hub-port because it fails to enumerate the device. But I guess this is also a TT-problem.

This means only USB 2.0 works since Siyah 2.0 :P.
[Galaxy S II Original Android Development] cheewaca:
Can you share that scripts?

Thank´s
[Galaxy S II Original Android Development] blader_rr:
My score with 2.1 rc1 at 1600mhz governor perfomance, stock rom XWKI8 brand H3G (italian).
[Galaxy S II Original Android Development] :
1600 performance, not sure why I continue to benchmark, but it's like a game of some sort.
[Galaxy S II Original Android Development] psychoid:
i dont know what happened with my phone... cannot get higher from 7109.. i just cant figure it out :mad:
[Galaxy S II Original Android Development] h20pt:
Sure, but i'm not at home right now.. I still need to optimize my script a little more, but when i do it and when i get home i'll send them to you :)
[Galaxy S II Original Android Development] DarkEN_ANGEL:
about some usb flash drives

Have a Goodram Edge 32 Gb usb flash drive with fat32 fs.

Log shows that driver works but not mounting drive's fs. In this case i need to mount it manualy with

mount -t vfat /dev/block/platform/s3c_otghcd/sda4 /mnt/usb

but it can't be unmounted.

gokhanmoral, can you fix it?
[Galaxy S II Original Android Development] JPxM0Dz:
meh couldn't get 2.1 rc1 to run criskelorom v2.9

Flashes fine, but boots into black screen
[Galaxy S II Original Android Development] yoplaboum:
I use Criskelorom 29.1 and 2.1rc1

and that works fine !!!

Do wou wipe data dalvik cache in Recovery Mode before install criskelorom ?

P.S : In my signature, I post a link to siyah kernels. This is my web server : http://www.aideadsl.com/sgs2/kernel
[Galaxy S II Original Android Development] cheewaca:
Thanks because i still apreciate lag in transitions with rc1
[Galaxy S II Original Android Development] LockeOn:
I am using 2.1 RC1 and my A-Data and Kingston Pendrives are working fine via OTG on MIUI 1.10.28; USB keyboards and mouses are still not working but it probably is because of AOSP source.
[Galaxy S II Original Android Development] olifee:
This is very confusing...

I just checked a pendrive and it is working.

However, mice and keyboards stay silent in CheckRom RevoHD (which is Sammy-based, after all... ).

As DarkEN_ANGEL confirmed, the error when connecting FTDI-chips is similar, so it appears to be something general. I will do some more testing with hubs and stuff now.

@DarkEN_ANGEL: I guess your pendrive did not work automatically because you have several partitions on it (support for that would be perfect, but I never saw it up to now). Although I do not understand why unmounting would not work, did dmesg / umount give any errors?

EDIT: The culprit for the TT-feature-problem is present since some change in 2.0-source, look here (edited that post so gokhan can find everything in one place):

http://xdaforums.com/showpost.php?p=18849223&postcount=7786
[Galaxy S II Original Android Development] LockeOn:
Do You think that USB mouse/keyboard support via OTG could be fixed on AOSP based roms by making changes in the kernel? It seems that it is kernel dependent or am I wrong?
[Galaxy S II Original Android Development] olifee:
I am not sure how AOSP handles input devices on the userspace-side (never used AOSP up to now, but I guess I will have a look once dual-boot is built into Siyah just for the fun of it :P).

However, I can confirm NOW that for me, non-mass-storage stuff is broken since 2.0 release (just at some point after 1.8).

As 2.0 is the first unified version, your problems might be kernel-related only... But don't get your hopes too high ^^.
[Galaxy S II Original Android Development] fasst:
Problem!

Max value, 1400Mhz, in s_volt_sceduler reverts back to 1200Mhz in Voltage Control after reboot. The set min. value, 100Mhz, holds. Saved as boot settings.

Tried to delete s_volt_sceduler and created it again. The value shows 1400Mhz, but Voltage Control still revert back to 1200Mhz.

Any solution to this?

Read a few post back that some others had similar problems after reboot but didn't say anything about what to do.

Edit: On 2.1RC1, Ondemand
[Galaxy S II Original Android Development] dragon546:
You using Miui? If so it's a rom issue and can be worked around by changing answer settings and turn off enforce proximity sensor.
[Galaxy S II Original Android Development] ebliss:
Search for scaling_max_freq in this thread
[Galaxy S II Original Android Development] fasst:
What do you mean?

My s_volt scheduler has:

echo "Set MAX Scaling Frequency" | tee -a $LOG_FILE;

echo "1400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo ""

echo "---------------"

Still gets 120000 after boot.
[Galaxy S II Original Android Development] ebliss:
Look at what the script is doing. ie. it is setting the value of "1400000" to this "file" called scaling_max_freq which is resided at "/sys/devices/system/cpu/cpu0/cpufreq/". But somehow, the value doesn't stick.

So, when I say search for scaling_max_freq in this thread, I mean search the term "scaling_max_freq" in this thread. You will find the solution.
[Galaxy S II Original Android Development] fasst:
Thanks, got it :)
[Galaxy S II Original Android Development] janreiviardo:
I am experiencing the same problem. I tried editing the permissions or setting it using chmod 444. But still when I tried to reboot, the max freq still reverts to 1200. I checked the permission I changed for the file and also saw that it reverted back to having all read permissions write for owner (using root explorer). Could you help me solve the issue too?

---------- Post added at 10:18 AM ---------- Previous post was at 10:17 AM ----------

Could you post what exact procedure you did? Did'nt work for me.
[Galaxy S II Original Android Development] ebliss:
That is because you didn't actually read the solution after you searched.
[Galaxy S II Original Android Development] Zanr Zij:
I apply many times! See many objects, compare carefully!

First, when you run that app, your sreen applied samsung profile. You press Native button: no change, no effect! You have to press Samsung button then press Native again to effect. You will see something change. But infact the Native profile same as Samsung profile before you run this app.

You could also take screenshots to compare. Exactly same!

Sent from my GT-I9100
[Galaxy S II Original Android Development] Zanr Zij:
Oh my run smoothly with 1450mv on RC1 and 1425mv on b14. Please control your temp!

Sent from my GT-I9100
[Galaxy S II Original Android Development] Zanr Zij:
Don't save boot setting in Voltage control, use script only and edit by Root explorer!

Sent from my GT-I9100
[Galaxy S II Original Android Development] janreiviardo:
Lol, thanks for pointing that out. Thanks, problem solved. =)
[Galaxy S II Original Android Development] ebliss:
Glad to hear that you have solved the problem.

I was waiting for you to curse me for not pointing it out clearly for you. But then, how to learn if you don't do the leg work? :p
[Galaxy S II Original Android Development] fasst:
Now I see my max_freq on top in Cpu Spy.

But it seems Voltage Control can't be used after this. It reverts the value max. back to

1200Mhz, even without Save on boot.

So the only way is to edit the scripts manually? What about SetCPU?
[Galaxy S II Original Android Development] janreiviardo:
I am able to edit my settings in voltage control, I just dont save the boot settings. And if Im good with the settings I made, Im just manually editting it in etc/init.d. This works for me. =)

Btw what is the safest charge current? And what is misc?
[Galaxy S II Original Android Development] droidphile:
Meanwhile, in Hacre's thread
[Galaxy S II Original Android Development] kwerdenker:
SetCPU is even worse then Voltage Control in this aspect.

1) You can't control every aspect the kernel supports like in Voltage Control

2) Even if you don't use it's widget or profiles, it's constantly running in the background.

If you've found the settings you like, make yourself a init-script with them and be done with it. This is the easiest and cleanest way to to it in my opinion. Changes can later be made relatively easy once you have your script set up and there are many good examples in this thread as a template.
[Galaxy S II Original Android Development] eiraku:
Are you running it while your colour profile is set to "standard" (not "movie" or "vivid")? Otherwise the screen tuning settings wont work.

That said, the crappy text hinting due to the sharpening being removed (to remove colour banding) is not to my taste. But it DOES work.

@droidphile: A sad, sad day for the XDA community. But not entirely unexpected seeing the amount of asnine "oh I don't wanna search, just tell me" and "give me my free stuff NAO because I deserve it" crap happens around these here parts.

I just pray that Gokhan has more patience to deal with them idiots.
[Galaxy S II Original Android Development] Zanr Zij:
It works but compare between 2 profiles themseft. Of course I used std color profile :)
[Galaxy S II Original Android Development] LockeOn:
@gokhanmoral

Is it possible that USB keyboard/mouse support via OTG on AOSP based roms could be fixed by patches in your kernel?
[Galaxy S II Original Android Development] netchip:
I hope it also, ninpo and netarchy are very nice devs.

I am sad ninpo has leaved SGS2 community :(

Sent from my GT-I9100
[Galaxy S II Original Android Development] psychoid:
Zanr Zij, how to control the temp. ?
[Galaxy S II Original Android Development] spradling:
:D
[Galaxy S II Original Android Development] kwerdenker:
After seeing the changelog, you bet I am :D

Thank you for all your work. Have fun on your time off and enjoy it. You most definetly earned it!
[Galaxy S II Original Android Development] tudort:
Boot Loops with 1.7 on Miui Galnet .23
[Galaxy S II Original Android Development] kendragon:
Can I mount ntfs external drive with this kernel? Is there a script to lunch?
[Galaxy S II Original Android Development] gokhanmoral:
this kernel doesn't support miui or cm7.

there should be no kernel supporting them since cm team asked everybody not to release any custom kernels.
[Galaxy S II Original Android Development] tushar.das:
I see changelog 1.8 but where is the attached kernal version 1.8..
[Galaxy S II Original Android Development] gokhanmoral:
check out http://xdaforums.com/showthread.php?t=1131924

there is a tutorial in that link.

ntfs.ko is in the kernel already. you don't need to put it in your sdcard.

mounting external sdcard with ntfs requires some additional scripts in init.d and it is not automatic.

I'll be working on it in the next version.
[Galaxy S II Original Android Development] gokhanmoral:
it is not released yet.

I've released v1.7 today and I started to work on 1.8 last night.

since it is not stable now, I'll keep it on my phone for a while before releasing but it will take some time.
[Galaxy S II Original Android Development] rahmat87:
Noob question: its automatically set on uv/oc?? Quite not sure
[Galaxy S II Original Android Development] kwerdenker:
No, you'll have to do that yourself.