yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] tuvi123:
gokhanmoral

I wiill try v18rc1 soon.

I have some questions:

1) do you plan automatic ntfs support for v1.8/9? (so it will load the modules at boot and all the user have to do is to insert ntfs formatted sd card / dok and it will work and get recognized).

2) is the latest v18rc1 based on 2.3.5 sources? I want to make sure of that because I have KI8 rom with the original stock kernal and I noticed it has some sound improvements and batterty-life is nice, music is also sound more clear now, so I want to make I will not lose those when I use your kernal.

3) is v1.8rc1 stable as v1.7? and what abou performance and touch responisvness using the default stage? (what is the stock governor if there is one at all..?).

thank you man, your are really talented.
[Galaxy S II Original Android Development] eybee1970:
Ok mate...will give it one mor:)e try
[Galaxy S II Original Android Development] gokhanmoral:
Did you move any apps to sd?
[Galaxy S II Original Android Development] d3l1:
Mine does that, too. No idea why, today it rebooted after sending a SMS.

Sent from my GT-I9100
[Galaxy S II Original Android Development] AndreiLux:
>KI3 (2.3.5) sources haven't been released yet so no, sadly no new sound drivers here yet.
[Galaxy S II Original Android Development] :
2) Did you see Samsung released sources for 2.3.5? No. So there's your answer, but sound and battery life is great in Siyah and fully .14 which Samsung is not even close to or so it seems.

3) It is more stable than 1.7 already.
[Galaxy S II Original Android Development] 2bullish:
I have two routers in the house one just used just to boost signal. Latest kernal does not switch to stronger signal and stays locked on original signal. A2/A4/A5 Didnt have problems "locking on" to stronger signal.

Sent via bacon mind sandwich
[Galaxy S II Original Android Development] coolfire:
And may I add that touchscreen responsive-ness is simply perfect, especially on my SGP Glas sp! :)

Sent from my SGSII
[Galaxy S II Original Android Development] spelaben:
Just checked with app2sd and there are 2 apps on my sd card. They were there from the beginning because I stopped using app2sd after trying different mods all the time.

When I tried to move them to the internal storage my phone crashed again.

Are there any logs I can provide you with?
[Galaxy S II Original Android Development] dtekkt:
Gokhan, just wanted to inform you that superuser 3.0.4 is released
[Galaxy S II Original Android Development] tuvi123:
yeah but earlier I saw that this kernal is based on SGH-I777 (AT&T version) leaked sources which are v2.3.5, or am I wrong?

also it's said to support 2.3.5 so I though maybe this kernal has the new sound drivers and all the 2.3.5 improvements

then If you 2 are right, then I will wait a bit untill gokhanmoral

wii include v2.3.5 improvements.
[Galaxy S II Original Android Development] AndreiLux:
The AT&T sources are older than KI3 which brought the sound improvements. Also, 2.3.5 didn't bring any improvements, the firmware (KI3) which coincidentally came with 2.3.5 brought the improvements with it. 2.3.5 itself doesn't mean nor do ****.
[Galaxy S II Original Android Development] tuvi123:
OK thank you mate, I understand more now.

from your expreience, is the battery-life in siyahKernel is better then stock KI3/8 kernal or not? (when you not use UV/UC or different governors -etc)

so now i have to choose:

stock kernal KI3/KI8:

1) better sound, battery life is improved.

3) can change bt time, more fixes.

siyahKernel v1.8:

1) a lot of fixes, no AOS bug.

2) some features like oc/uv governors /root, auto calibrete battery, etc..

I wish the new stock KI3/8 sources will be leaked soon, then we can enjoy both worlds.
[Galaxy S II Original Android Development] crypticc:
When i was using tegrak app lowering internal too much caused some screen responsiveness issues and DB read write suffered in quadrant. For me anyway
[Galaxy S II Original Android Development] :
Superuser 3.0.4 is out.
[Galaxy S II Original Android Development] gokhanmoral:
Since samsung has already releases ki8 officially new sources will be released soon. and a soon as they release it I will update the drivers. I put 2.3.5 to the thread title to stop people asking questions about if this kernel is compatible with ki3 or not. This kernel is using drivers from samsung sources but it is not based on samsung sources but it is based on vanilla linux kernel 2.6.35.14.
[Galaxy S II Original Android Development] AndreiLux:
Btw it seems the soft limit of 900mV is still in the gpu voltage control interface I think. I'm setting it to lower values but it reverts back to 900.
[Galaxy S II Original Android Development] jdmcivic:
+1 for that.

stucked at 900mV
[Galaxy S II Original Android Development] gokhanmoral:
I set it in rc1 to prevent people reporting bugs because of ineffective low gpu voltage becoming active

I will lower it in release.
[Galaxy S II Original Android Development] tuvi123:
gokhanmoral

do you plan automatic ntfs support for v1.8/9? (I mean that it will load the modules at boot and all the user have to do is to insert ntfs formatted sd card / dok and it will work and get recognized).

I can test it for you, I have a 64gb sandisk sdxc (it works fine with fat32, also works with ntfs but I have tired to put the commands each time...

thank you.
[Galaxy S II Original Android Development] spelaben:
Okay, I reverted to 1.7.8 and now I'm getting crashes too. I think it has something to do with SetCPU.

Probably got some unstable settings, can someone make screenshots of stable and energy efficient voltage settings, profiles etc.?
[Galaxy S II Original Android Development] MrPhilo:
So I flashed the gpuuv file on the first page.

When into the init.d folder and changed the value from '160 267' to 400.

I tried benchmarking (Nenamark2) and I didn't see any fps changes. Am I doing something wrong?
[Galaxy S II Original Android Development] gokhanmoral:
In my todo list. I'll do it in the next version.
[Galaxy S II Original Android Development] AndreiLux:
Did you literally change '160 267' to '400' or as it should be to '160 400' ? Also, 400MHz needs a lot of overvolting to be stable so be warned. It's also, except for benchmarking purposes, useless for us right now.
[Galaxy S II Original Android Development] tuvi123:
thank you! :)
[Galaxy S II Original Android Development] pac213:
A bit out of topic. But can someone point me to some definition of CPU Governors? :)
[Galaxy S II Original Android Development] jdmcivic:
yes there is. stay stock! i dun think everyone's sgs2 hardware is the same. some settings will work for others but for some unstable. u gotta find the right settings for yourself.
[Galaxy S II Original Android Development] gokhanmoral:
I think I will revert the cfs low latency patch (it was funded by nokia) because even if it seems snappier at first it becomes laggy in time.
[Galaxy S II Original Android Development] AndreiLux:
It's written in huge blue letters in the 4th line of the first post of the thread to read the FAQ first :p Please follow the advice people.
[Galaxy S II Original Android Development] MrPhilo:
I just did '400' and is that wrong? Or do I have to do '160 400'?

Yeah but I guess I don't need to change any volt if I clocked it at 267 right?

So the question is does just putting '267' work? Or I need to value?

Thanks
[Galaxy S II Original Android Development] jonamd26:
how to activate smoothass governer:(
[Galaxy S II Original Android Development] jdmcivic:
u will need to input two values no matter what. one normal usage and the other for intensive usage.
[Galaxy S II Original Android Development] jonamd26:
sorry smartass v2 governer...how to enable it
[Galaxy S II Original Android Development] tomascunill:
setCPU or voltage control. You candownload them from the market. setCPU is 2 bucks and voltage cntrl is free.
[Galaxy S II Original Android Development] MrPhilo:
Awww right. Because on Tegrak Kernel + UI, I was able to use a solid 267Mhz. Damit :(!

EDIT: Wait.. So can I do '267 267'?
[Galaxy S II Original Android Development] AndreiLux:
Yes you can. It's the same as what Tegrak did.
[Galaxy S II Original Android Development] Spl1tz:
ROM is awesome but the camera is a turndown...

The quality went down pretty hard and there is a bug when u preview your photos and delete it u get stuck at a black screen until u hit back.
[Galaxy S II Original Android Development] jdmcivic:
yay. 10char
[Galaxy S II Original Android Development] MrPhilo:
Aww okay. Thank you for replying. Finally Asphalt 6 can run smooth again :)
[Galaxy S II Original Android Development] gGabi:
right... so... what's that has to do with this thread you ***** * ****** **** ?
[Galaxy S II Original Android Development] Spl1tz:
Wait i think i posted this in the wrong section.

Does kernel affect camera? or is it the ROM? I use Deodexed ROM.
[Galaxy S II Original Android Development] jdmcivic:
anyone has the beta2 on hand?. dont mind uploading it here cos i accidentally deleted it. i believe its the snappiest of them all.

while a4 being the most batt efficient...
[Galaxy S II Original Android Development] darkflyer1983:
any clue about this issue?
[Galaxy S II Original Android Development] bala_gamer:
One request, can 1500 mhz option while overclocking can be implemented?
[Galaxy S II Original Android Development] AndreiLux:
First of all, those frequencies won't ever work at those voltages. Most people need 1200mV for 400MHz and 850mV for 200MHz doesn't work until the current kernel version is finalized.

Secondly, are you applying the script correctly? Does it run fine from a terminal?

Btw Gokhan: You have a big fanboy apparently :p
[Galaxy S II Original Android Development] MrPhilo:
Im having this issue. Thought I fixed it as well. Asphalt still lags at '267 267' and I thought I did it right.

I also tried benchmarking '100 100' and it achieves 49 and I tried '267 267' after and I get 49.3. Doubt 167mhz more can just get 0.3...

I might fiddle around with the voltages abit, see if I need more for the 267Mhz but I doubt it as Tegrak I didnt have to change anything.
[Galaxy S II Original Android Development] newHere:):
its only me, or the device is getting hotter with this kernel than speedmod kernel.. ?

i didn't preform overclock
[Galaxy S II Original Android Development] gokhanmoral:
Can be implemented but it requires a lot of changes not only in the source code but in the scripts that people are using. Therefore I will not add any new step.
[Galaxy S II Original Android Development] mihapodb:
Can someone please upload working GPU OC/UV script please :)

With tegrak, I got stable:

100 MHz @ 750 mV

400 MHz @ 1100 mV
[Galaxy S II Original Android Development] syahrulzaman:
Hi,

Anyone having problem with twlauncher when rearrange icon using 1.8rc1?

Mine always force close
[Galaxy S II Original Android Development] Daniele150cv:
UP! :(

I need BNL for stock sms please...anyone can help me? :(
[Galaxy S II Original Android Development] :
Nope :)
[Galaxy S II Original Android Development] :
Use ROM that has corrcect (patched) app for SMS/MMS nothing to do with kernel.
[Galaxy S II Original Android Development] sendhiloo7:
Cyanogenmod ROM

Hi ,

After installled this kernel (1.8) , my mobile not booting up..

I am facing AOS bug , please help me
[Galaxy S II Original Android Development] bala_gamer:
Thanks for the info! ill try using some custom scripts for that, the reason is 1.6 ghz doesnt pass the benchmarks , it seems to be unstable (raised the voltage till 1.5 mv). So 1.5 would be better to stay with for me.
[Galaxy S II Original Android Development] AndreiLux:
This kernel doesn't support MIUI/ Cyanogen. Flash your default kernel back in Odin.
[Galaxy S II Original Android Development] Daniele150cv:
Uhm thank you for the response!

But, You say that I need a patched mms.apk & mms.odex (i'm running stock KI3..) to work BLN and the problem isn't kernel but sms app..

What are the roms that contains this patch?

Thank a lot man! ;)
[Galaxy S II Original Android Development] syahrulzaman:
Erm...dont know why mine always force close..change diff governor also same.

V1.7.8 no issue...
[Galaxy S II Original Android Development] rinoa19:
+1

......me too.......:)
[Galaxy S II Original Android Development] :
Try here, second post ;)

http://xdaforums.com/showthread.php?t=1183774
[Galaxy S II Original Android Development] sendhiloo7:
Oh really :( . i already flashed back to Cyanogen.

Thanks
[Galaxy S II Original Android Development] jdmcivic:
the scripts provided here works fine. its just that gokhan turns on and off certain features with each new release due to the fact that he wants to avoid unecessary bug reports due to etc etc..

i've been running on 100@750 267@850

stable for me even while playing asphalt..but will crash the moment i do a gpu stability test. haha
[Galaxy S II Original Android Development] crypticc:
Hey. Try nandroid backup (so you can get back) and them wipe twlauncher data in settings applications
[Galaxy S II Original Android Development] AndreiLux:
Touch screen driver control patch by Tegrak for touch sensitivity adjustement. Some people might want that feature.
[Galaxy S II Original Android Development] _cummoo:
This ist the first time ever the device is getting hot with 1.8rc1, and sadly the performance is not as good as with 1.8axx - 1.8bxx!
[Galaxy S II Original Android Development] Daniele150cv:
OMG!! You are great!! :) :)

I will try istantly :D

thanks!!! :cool:
[Galaxy S II Original Android Development] superleeds27:
I have to say;

Charging the phone from around 3% whilst turned on has took longer than usual i think.

Also, Temperature whilst charging has been around 44C.
[Galaxy S II Original Android Development] Sangrias:
1.8rc1 runs great, no issues at the moment.
[Galaxy S II Original Android Development] :
Also you may need modified liblights, maybe you should just flash full sicopat ROM as it is close to stock.

And do backup :p
[Galaxy S II Original Android Development] Daniele150cv:
Yes..infact the bln not work for sms after i flashed the attached zip file...

There is a method to put inside the liblight maintaining the stock rom? :confused:

Anyone can extract the liblight from the Sicopath rom and make me a zip flashable? :(
[Galaxy S II Original Android Development] AdamHayton:
I have had a Touch Wiz force close with this RC1 also. As well a freeze up. However I am slightly undervolted. Did not happen with previous versions
[Galaxy S II Original Android Development] :
Don't know. Maybe extract from his ROM or ask in his thread or in Q/A forum.

Lets not hijack kernel thread :)
[Galaxy S II Original Android Development] syahrulzaman:
Still the same...twlauncher forceclose even after clear data
[Galaxy S II Original Android Development] Daniele150cv:
Oh man...you are right

Excuse me....
[Galaxy S II Original Android Development] yoplaboum:
1.8rc1 Works fine with criskelorom v23
[Galaxy S II Original Android Development] jdmcivic:
@Andrelinux

traced back ur post to this.

TL;DR: GPU voltages min: 900mV up to 1200mV in 50mV steps, CPU voltages min: 650mV up to an amazing 2225mV in 25mV steps, charger current from some value I don't remember up to 950mA in 50mA steps.

does this mean that the min gpu voltage is set at 900mv? in the scripts provided here shows 500mV

# CLOCK INFO:

# 100 114 133 160 200 267 400 are valid values

# 160 267 are default

# VOLTAGE INFO:

# 500000 min / 1200000 max

# 950000 1000000

so which is which? i really dun want another placebo effect. its kinda frustating to echo out certain values that reflects on the system but only to find out that the system doesnt support it and thereforw thw stock values are applied.
[Galaxy S II Original Android Development] goldbergx:
A small thank you for the great work mate!

05U32777AL195290W

54 minute video :D :D (wish I understood German ;) )
[Galaxy S II Original Android Development] AndreiLux:
I had some more fun in the source code (The touch screen driver is a clusterfuck written by monkeys) :

/drivers/input/touchscreen/mxt224_u1.c

pr_emerg("%s: dvfs unlock\n", __func__);*/
} else if ((msg[1] & DETECT_MSG_MASK) && (msg[1] & (PRESS_MSG_MASK|MOVE_MSG_MASK))) {
/*pr_emerg("%s: dvfs lock\n", __func__);*/

if (lock_status == 0) {
s5pv310_cpufreq_lock(DVFS_LOCK_ID_TSP, CPU_L3);
lock_status = 1;
}

The touchscreen driver locks the CPU frequency to CPU_L3 when the screen is being touched, but because of the steps in Siyah look like:

CPU_L0,	/* 1.6GHz */
CPU_L1,	/* 1.4GHz */
CPU_L2,	/* 1.2GHz */
CPU_L3,	/* 1GHz */
CPU_L4,	/* 800MHz */
CPU_L5,	/* 500MHz */
CPU_L6,	/* 200MHz */
CPU_L7,	/* 100MHz */

It then makes it lock to 1GHz instead of the 500MHz it is supposed to be in the stock kernel.

CPU_L0,	/* 1.2GHz */
CPU_L1,	/* 1GHz */
CPU_L2,	/* 800MHz */
CPU_L3,	/* 500MHz */
CPU_L4,	/* 200MHz */
CPU_LEVEL_END,

If you fix this please also consider the improved driver I mentioned a few posts ago :D

---------- Post added at 07:38 PM ---------- Previous post was at 07:31 PM ----------

At the beginning we didn't know of the hard-limit on voltage and really thought it would work but then I got suspicious because all voltages worked. The script is no longer up to date, well at least those min values are not.

Right now Gokhan set up a minimum voltage in the GPU interface to 900mV because there's a lot of people who have the scripts set to voltages of around 800mV, as they thought it would really work and it's stable but it's not. Because now that hard limit has been fixed, there's a very high probability when people flash the kernel where the limit will be removed, that it will crash a lot of devices since they will really get that voltage, and it will be unstable. Also note: Everybody who undervolted with Tegrak under 900mV was also all just placebo since the hardlimit was not changed.

For now it is recommended that *EVERYBODY* raises the minimum voltages up to at least 900mV in their scripts to avoid this problem.
[Galaxy S II Original Android Development] jdmcivic:
@Andrelinux

thanks for the detailed explaination.

you said that the hard limit has been fixed but as of which release onwards? or is it just been discovered as of rc1?

ahhh damn you placebo effect. haha
[Galaxy S II Original Android Development] gokhanmoral:
another great post!

thank you...
[Galaxy S II Original Android Development] incubus_fr:
Nice find!

As you are digging into the code, do you know the reason why the CPU frequency has to be locked when the screen is being touched?

It seems silly to me...
[Galaxy S II Original Android Development] dimkrom:
does this in change log "lowered min GPU voltage to 800mV and max AC&MISC current to 950mV" mean that the new version has already the settings for 950mA charging at misc and ac? didn't need for running the script ?
[Galaxy S II Original Android Development] incubus_fr:
Gokhan, thank you for your huge work!

2W95191634976903M
[Galaxy S II Original Android Development] Orka82:
I sure dont think so. The travel charger delivered with my s2 is rated at 750mA..
[Galaxy S II Original Android Development] AndreiLux:
My guess is it would be so that touchscreen interactions are smooth and don't lag / have delay (if they were at 200MHz). But honestly I don't know.

Check these confusing bits of code in the driver:

ret = get_object_info(copy_data, DEBUG_DIAGNOSTIC_T37, &size, &object_address);
/*jerry no need to leave it */
#if 0

ret = get_object_info(copy_data, DEBUG_DIAGNOSTIC_T37, &size, &object_address);
/*jerry no need of it*/
#if 0

}
/*jerry no need of it*/
/* error = mxt224_load_fw(dev, QT602240_FW_NAME); */

mxt224_init_touch_driver(data);
/*jerry no need of it*/
/* qt602240_initialize(data); */

WHO IS JERRY AND WHY DOESN'T HE NEED IT???

No, it just means that the charging interface is now correctly set up that it accepts 950mA maximum current, as that's what the device can eat at most. The actual values are still set to default (650 I think?).
[Galaxy S II Original Android Development] megazz:
is this kernel compatible with Lite'ning rom 6.1?
[Galaxy S II Original Android Development] pachinkosan:
gokhanmoral, thank you for u'r awesome kernel, keep it on!

little amount

4A2053659V994013D
[Galaxy S II Original Android Development] newHere:):
there is any way to solve the heat problem?
[Galaxy S II Original Android Development] incubus_fr:
Well, if that's the reason it looks like a fast and dirty workaround :eek:

The trainee who wrote the fast and dirty workaround? :D
[Galaxy S II Original Android Development] jmblazquezh:
Installed version 1.8rc1. Very very fast performance. The deep sleep is working properly. I have not installed SetCPU because I do not like to play frequencies and voltages. I've only installed CPUSpy to check the proper functioning of deep sleep.

Regards
[Galaxy S II Original Android Development] tolis626:
Hey Gohkan,kernel's getting better and better here! :D

Had an issue with Superuser,where it denied superuser permissions upon boot for all apps that were set to do something on boot.Seems fixed after deleting all entries and regiving su permissions by hand,so I'm okay for now.

On a side note,as the point was raised earlier,I wanted to ask you something.Could I,using a script or something,change the max speed to 1.5GHz instead of 1.6GHz?Because the performance gain of those extra 100MHz ain't phenomenal,and for me it needs 100mV of extra juice to run.1.4GHz is out of the question,I'm too mad for such a conservative overclock. :p If it's not possible...Well,I'll just have to live with 1.6! :p
[Galaxy S II Original Android Development] gokhanmoral:
I do not experience any heat problem and cannot think of a reason.

do you have any app running in the background which keeps your cpu running at high frequencies?

I don't think this kernel will produce more heat than any other kernel running at the same freq with the same voltage level.

"maybe" a driver can cause it but I don't think that would be so noticeable between update2 and at&t version drivers.
[Galaxy S II Original Android Development] bandit79:
Where's the DL for 1.8rc2? In First Post there still 1.8rc1?!
[Galaxy S II Original Android Development] netchip:
Hey gokhanmoral,

Like it to be my kernel developer for a upcoming ROM?
[Galaxy S II Original Android Development] dimkrom:
i don't understand this, if i connect it to my car charger which it is 2100mah does it charge with 950mha ?
[Galaxy S II Original Android Development] newHere:):
i have this problem only when i use the device...

when i do not use it there is no heat...

so i guess the "deep sleep" is not the issue...

this is not very hot, but it is hotter than i was used to...

anyway, your kernel is really good :)
[Galaxy S II Original Android Development] gokhanmoral:
I will develop kernels and you can use them in any rom you want.

I will also make a custom kernel for CM7 but first I want to finish this one...

I would be honored if you choose my kernel in your rom. so the answer is kinda yes already.
[Galaxy S II Original Android Development] gokhanmoral:
it is not possible to please everybody...

if I had only 1400MHz above 1200 then I could add 1500 and that would be a bonus.

but if I remove 1600 and make it 1500, those who use 1600mV without increasing the voltage very much will be very upset.

if the 100MHz gain is not phenomenal then please think the same for increasing the freq from 1400 to 1500 :)
[Galaxy S II Original Android Development] gokhanmoral:
not if you have increased the current :)

if you have not then it will charge @650mA

and even 550mA if that charger is detected as MISC.

I have no idea why samsung has chosen such a low value.

my previous HTC could go upto 870-890mV without modifying anything.

there were some rumors about charging slow would make your battery last longer. however if I charge slow my battery lasts less as I am never able to charge it to 100%.
[Galaxy S II Original Android Development] AdamHayton:
This kernel is superb, tempted to switch cognition rom to something else now!
[Galaxy S II Original Android Development] dimkrom:
ok if i run the script from cwm then how can i go back to stock if i want to?