yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] buerger5:
Same here (Criskelo v22). Changed to Speedmod41, no probs.
[Galaxy S II Original Android Development] AndreiLux:
I don't have this behaviour, it seems that your battery isn't calibrated right. Once it reaches max voltage then it stops charging, if it reaches it at 96% for you it just means your real 100% is 96%.
[Galaxy S II Original Android Development] cbeckstein:
on stock ki8 (ki4 modem) it is fine as well
[Galaxy S II Original Android Development] tonysac:
Same modem..no problem

Sent from Galaxy!
[Galaxy S II Original Android Development] gokhanmoral:
beta2 is up.

I hope it also solves usb problems.
[Galaxy S II Original Android Development] :
bugs in your kernel, really? :p go out, have fun ;)
[Galaxy S II Original Android Development] AndroidGX:
Your reasoning is right :) next cycle I will calibrate my battery manually with "BatteryCalibration" app, because I'am actually trying Anker 1900mAh that I just received from yesterday and it's only my 2 firsts brand new cycles ;)

But anyway I always had this problem even with stock official one :(

Thanks for your answers.
[Galaxy S II Original Android Development] crypticc:
Reinstall su fixed both issues..thank you
[Galaxy S II Original Android Development] hausmanis:
Will the reTOUCHED kernel get updates ?
[Galaxy S II Original Android Development] AdamHayton:
Right so anyone using Cognition S2? Ill flash the latest again and see if that sorts the issue.
[Galaxy S II Original Android Development] dtekkt:
I'm sorry to say this, but I am still not able to mount my thumb drive , must be something different that changed from 1.7.8 to 1.8
[Galaxy S II Original Android Development] yoplaboum:
Criskelorom v22 + Siyahkernel 1.8beta2 + Modem KI4 ( link here CMW ) is perfect for me ! ;)
[Galaxy S II Original Android Development] gokhanmoral:
no :)

you won't ask for an update once v1.8 is released.
[Galaxy S II Original Android Development] gokhanmoral:
unfortunately a lot of things changed from v1.7 to v1.8...

I will release the next source patch to be applied against original linux kernel instead of samsung sources...

since I do not use that functionality it is hard to fix.

I will try again tomorrow.
[Galaxy S II Original Android Development] dtekkt:
Ok that's alright for me, I hope you get usb otg working again, because its such a nice feature :-P anyways,enjoy your weekend and spend a bit of time with your gf :)
[Galaxy S II Original Android Development] hausmanis:
Alright so you think regular Siyah 1.8 will be better than reTOUCHED in terms of batterylife ?
[Galaxy S II Original Android Development] jonny68:
so far so good on the AOS, will test more but after 45 mins on standby it's only at 5% which is amazing,previously it was closer to 50%:eek::)
[Galaxy S II Original Android Development] yoplaboum:
For me 1.8 beta are better than 1.6 retouched version
[Galaxy S II Original Android Development] gokhanmoral:
it is already better :)
[Galaxy S II Original Android Development] CA3iR0:
Exactly the same here, as I reported earlier...
[Galaxy S II Original Android Development] shr33kant:
I also got one of these on thursday! I'm on cycle 3 now..aparrently it starts getting more awesome after 4 or 5...and with this kernel I think we'll be in a position to have perhaps 2d+ with moderate usage! :D
[Galaxy S II Original Android Development] :
I bow down to you for this :)
[Galaxy S II Original Android Development] hausmanis:
ah ok, thx for the replies guys, then i will hessitate nomore and install the Siyah beta since i want the best possible batterylife ALWAYS! :)
[Galaxy S II Original Android Development] AdamHayton:
ROM? Modem?
[Galaxy S II Original Android Development] tuvi123:
gokhanmoral

some wishlists and questions for v1.8

1) 2.3.5 has some sound improvements, if I use your kernal will I lose all the sound goodies of v2.3.5? (like better volume and clearity)

2) please fix usb otg not working.

3) please fix mhl bug (in which the audio can't be routed through the 3.5mm jack when using mhl, on vilian ron v2.4.2 it works just fine).

4) please add a version which has no impact on touch reponisevness and performance.
[Galaxy S II Original Android Development] Skyline92:
Benchmark scores are getting worse. Tried it with CF-Bench. The best score by far has been achieved with "OnDemand" Governor. The worst with BrazilianWax. SavagedZen's also bad.
[Galaxy S II Original Android Development] Остап:
there is a problem with new recovery ....

while starting of phone or if it extinguished but on charge - there is error on the screen logo_tel.jpg draw falled
[Galaxy S II Original Android Development] shr33kant:
+1! I am now just waiting for the next nightly and i'm freeeeeee from tw roms!

Sent from inside a black hole.
[Galaxy S II Original Android Development] CA3iR0:
I updated the modem to xxki4 after it started hanging up on turning wifi off but the bug remains...
[Galaxy S II Original Android Development] alcurtis93:
In English?

Sent from my GT-I9100
[Galaxy S II Original Android Development] hayspat:
On KI3 you cant get sound via 3.5mm jack when mhl connected. It is rom related issue, not kernel. You can use KI8 which working fine for me.
[Galaxy S II Original Android Development] olifee:
For those who desperately need USB-OTG now, you can just do the following:

1) Create the folder "usbdevice" on /mnt/sdcard.

2) Execute the following as root (or using gscript or something):

mount /dev/block/platform/s3c_otghcd/sda1 /mnt/sdcard/usbdevice

As soon as you do not need the device anymore, execute:

umount /mnt/sdcard/usbdevice

The nice thing about this is, if the external drive is ntfs-formatted, just do (needed only once after each reboot, but won't hurt if you execute it another time):

insmod /lib/modules/fuse.ko

and then

ntfs-3g /dev/block/platform/s3c_otghcd/sda1 /mnt/sdcard/usbdevice

in step 2. Unmounting works like before.

If your device has more than one partition or you connect more devices with a hub, replace "sda1" by "sda2" (for second partition) or "sdb1" (for second device / drive).

I also sent some debug-info to gokhanmoral so automounting might be possible again later on :).

My many reboots have also been resolved by now with gokhans help :).

In case someone else encounters this, they were caused by >16 apps shifted to SD by App2SD, which slows down booting and apparently breaks some things.
[Galaxy S II Original Android Development] Bene2k11:
beta2 / rebooted after recieving a trillian notification(with sound)... first part of the sound was repeated 3 times and then my SGS2 rebooted.

EDIT: Doesn't seem to happen again.
[Galaxy S II Original Android Development] chadouming:
Can't wait to see this beast on CM :D
[Galaxy S II Original Android Development] deezle:
AOS down to 3%, deep sleep now triggering with Smartass v2, didn't work by default. Hoping for big things after calibrating my battery!
[Galaxy S II Original Android Development] MrPhilo:
So I flashed the GPU script via CWM.

After finding it init.d folder and changing the value from '160 267' to 400 I didn't see GPU improvement. Well I saw equal result for 100 against 400 on changing the script in the gpuv or something. This was all done by benchmarks (Nenamark2, Smartbenchmark etc).

They call gave same result nearly.

Am I doing something wrong?
[Galaxy S II Original Android Development] Dave83:
Hi, i tried to flash the versione 1.8b2 with CWM, but failed with error "no zImage was found".

Why? :(
[Galaxy S II Original Android Development] ebliss:
Flash the zip file in cwm RECOVERY. NOT cwm app. When flashing tar kernel file, use cwm APP.
[Galaxy S II Original Android Development] dragon546:
Please delete answer was given above.
[Galaxy S II Original Android Development] Dave83:
Opss, sorry, maybe it's time I go to sleep

Thank's ;)
[Galaxy S II Original Android Development] jsompis:
1.8b2 deep sleep work again tested with ondemand and smartassv2 100-1200.
[Galaxy S II Original Android Development] antt00:
Wifi turning off problem is still here with 1.8beta 2 for me. i have try clearing cache and dalvik cache also.
[Galaxy S II Original Android Development] Vulpix:
I see this "tvout resume wo" in my betterbatterystats too. Didn't see it before this kernel (B2), anyone knows what this is?
[Galaxy S II Original Android Development] AndreiLux:
I've had it I remember getting BetterBatteryStats on all kinds of kernels. I suppose it has something to do with TV out :p
[Galaxy S II Original Android Development] Vulpix:
Even with phones without tvout functionality?
[Galaxy S II Original Android Development] AndreiLux:
Uh no. I just meant on all kinds of kernels on this phone.
[Galaxy S II Original Android Development] Vulpix:
Ah OK, hope there will be a way to disable it eventually.
[Galaxy S II Original Android Development] AndreiLux:
Anyway I dug a bit into the source code since I was curious about the voltage discussions;

\drivers\media\video\samsung\mali\platform\orion-m400\mali-platform.c :

#ifdef CONFIG_REGULATOR
#if USING_MALI_PMM
g3d_regulator = regulator_get(&mali_gpu_device.dev, "vdd_g3d");
#else
g3d_regulator = regulator_get(NULL, "vdd_g3d");
#endif

Here we find out in the Mali drivers that the regulator is called "vdd_g3d".

\arch\arm\mach-s5pv310\mach-c1.c :

static struct regulator_consumer_supply buck3_supply[] = {
REGULATOR_SUPPLY("vdd_g3d", NULL),
};

We see that it's set on the buck3_supply in the regulator initialization.

static struct regulator_init_data buck3_init_data = {
.constraints	= {
.name	= "G3D_1.1V",
.min_uV	= 900000,
.max_uV	= 1200000,
.always_on	= 0,
.boot_on	= 0,
.apply_uV	= 1,
.valid_ops_mask	= REGULATOR_CHANGE_VOLTAGE |
REGULATOR_CHANGE_STATUS,
.state_mem	= {
.mode	= REGULATOR_MODE_NORMAL,
.disabled	= 1,
},
},
.num_consumer_supplies	= 1,
.consumer_supplies	= &buck3_supply[0],
};

buck3 initialization tells us the min & max voltages it's set to.

\drivers\regulator\max8997.c :

/* Voltage maps */
static const struct vol_cur_map_desc ldos_vol_cur_map_desc = {
.min = 800,	.step = 50,	.max = 3950,
};
static const struct vol_cur_map_desc buck1245_vol_cur_map_desc = {
.min = 650,	.step = 25,	.max = 2225,
};
static const struct vol_cur_map_desc buck37_vol_cur_map_desc = {
.min = 750,	.step = 50,	.max = 3900,
};

And finally in the power regulation of the Maxim MAX8997 that's being used in our phone we see that buck3 is mapped to a minimum voltage of 750mV with 50mV steps.

While we're at it you can also check out the CPU voltage settings:

\arch\arm\mach-s5pv310\mach-c1.c :

static struct regulator_init_data buck1_init_data = {
.constraints	= {
.name	= "vdd_arm range",
.min_uV	= 650000,
.max_uV	= 2225000,

And has a minimum of 650mV.

Which also explains why for some user here if I remember right, anything under 650mV ran perfectly stable, but once he reached 650mV it immediately crashed. That one guy who actually said he's running 600mV on Cyanogen and requested it here was also just placebo. The power regulator minimum is also 650mV.

And finally, but I forgot where I found it: the charging current rate has a maximum of 950mA with 50mA steps. So basically those 1000mA charge rate scrips should theoretically not work.

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.
[Galaxy S II Original Android Development] nofam:
Can someone confirm whether I need SetCPU if Daemon Controller is installed?
[Galaxy S II Original Android Development] Steven6489:
Can anyone explain what these governors do? :D

More to battery saving or performance or balance?
[Galaxy S II Original Android Development] tonysac:
In the second post of this thread you ll find a link about governors

Sent from Galaxy!
[Galaxy S II Original Android Development] Erumer:
Angry birds not starting with 1.8b2, black screen instead. I know it's not much but maybe it's reproducible. With 1.7.8 it works.
[Galaxy S II Original Android Development] twosix:
All the 3 Angry Birds work for me.
[Galaxy S II Original Android Development] tonysac:
+1 ...all 3 versions works fine

Sent from Galaxy!
[Galaxy S II Original Android Development] carlos67:
oc daemon or setcpu just for undervolting?

Do you guys recommend using the oc daemon with an undervolt script (I don't want to overclock, just want to undervolt) or, is using SetCPU to undervolt better?

I'm running Leo's ROM 2.7.1 currently with cf-root 4.2 with Tegrak app to undervolt ( I know I can't use Tegrak to uv with Siyah kernel, unfortunately :().

If I was to use oc daemon, do I put kwerdenkers script (modified of course for just undervolt) into my init.d folder? If so what do I name the script file, something like 96undervolting I presume?

This is what I want to have afterwards 100MHz~1200MHz with voltages 825,825,875,950,1050,1150 (I know these are stable for me)

Have done a lot of reading but still unsure.

Would be grateful for your suggestions guys :)
[Galaxy S II Original Android Development] gokhanmoral:
beta4 is up.

I lowered the min voltage of GPU to 800mV and max AC&MISC currents to 950 (thanks to AndreiLux for digging the source and extracting this info)
[Galaxy S II Original Android Development] Siberian Tiger:
Goodmorning gokhanmoral, nice work thank you.

Just a silly question the android os bug is samsung related because i bought to my wife a mini 10 (sony ericcson) 2.3.3 and in the battery stats i can't find android or android os running

Thanks ;)
[Galaxy S II Original Android Development] Flasher8:
can't find 1.8beta4 in the first post ...

:confused:
[Galaxy S II Original Android Development] jdmcivic:
i dun see any beta4 in the first post yet..
[Galaxy S II Original Android Development] dtekkt:
OMG you did it, usb otg is back with beta4!!! Thanks so much
[Galaxy S II Original Android Development] gokhanmoral:
I've just reuploaded beta4.

if you have downloaded as soon as I leave my previous post please download it again.
[Galaxy S II Original Android Development] coolfire:
Nope, use either or. :)

You Sir, are amazing. :D
[Galaxy S II Original Android Development] jdmcivic:
Samsung's 2000mah extended battery + Siyah's kernel = WINNER!
[Galaxy S II Original Android Development] dtekkt:
Ok just did that, may I ask what the reason was?
[Galaxy S II Original Android Development] gokhanmoral:
I was testing something about cpu scaling and it was causing lockups.

I forgot to remove it before posting the first beta4.
[Galaxy S II Original Android Development] dtekkt:
Ok, so this was it why my phone didn't want to come back from sleep :-P
[Galaxy S II Original Android Development] coolfire:
Same here. Just got my 2k mah battery from a nice bro. :D
[Galaxy S II Original Android Development] bervin:
How much did you get your 2k battery for?
[Galaxy S II Original Android Development] YaocH:
Hey, i presume you're from singapore also? Where did you get the 2000mah battery? and how much did it cost you? I'm interested to say the least!
[Galaxy S II Original Android Development] :
Guys forgive an ignorant question... 1.8 is not based on 2.3.5 source code, as AFAIK it's not been released yet, am I right?

So when it will be made public we'll see an updated siyah with all the benefits 2.3.5 kernel brought over 2.3.4 one (that's to say a much improved battery life and speed)?

Can't wait to try out 1.8 final.. I went back to cf root kernel since it provides me with more battery life than 1.7.8 with uv applied and uc to 100mhz; now aos bug is better than with previous 2.3.4 roms, but still eats more than 2hrs cpu time on a single charge, which should be a bad thing if I understand it correctly ;) hope 1.8 will solve this also on my device!!

Forgive me if I said something stupid, still trying to understand this whole kernel and battery matter :)
[Galaxy S II Original Android Development] xyzulu:
Perhaps talk about your battery in another thread, or via PM.. let's keep this thread on topic.
[Galaxy S II Original Android Development] jdmcivic:
65bucks. bro. head over to hwz forum. theres an MO going on..
[Galaxy S II Original Android Development] :
Back to vr? :D
[Galaxy S II Original Android Development] YaocH:
Sorry for threadjacking. Will take note. Peace(:
[Galaxy S II Original Android Development] Flasher8:
i heard that the battery is slightly bigger, am i right ?
[Galaxy S II Original Android Development] jdmcivic:
i haven tested out the new kernel yet as im still calibrating my new batt. but while on beta2. i switched to vr and suddenly experienced massive lag. i immediately change to sio and all seems to work well again. so much so it has become.smoother.and snappier
[Galaxy S II Original Android Development] :
I'm using sio all the time, just noticed that default is back from deadline to vr.
[Galaxy S II Original Android Development] gokhanmoral:
oops :)

I forgot to set it to deadline... anyway, I made some typos as well which means beta5 is not far.

but if nobody reports any bugs maybe it will be a release.

I will enable CFS patches in rc1 and ask you if it makes the phone snappier.
[Galaxy S II Original Android Development] idealforyou:
Astro Player make Force Close by starting device with 1.8.4beta.

Kernel 1.8.1beta make not this Force Close. Why that?
[Galaxy S II Original Android Development] :
Ok great thanks :D, also I am playing with governors a bit and ondemandx is faster and snappier than interactivex at the same settings. Just noticing, nothing major :).
[Galaxy S II Original Android Development] YaocH:
I recently updated to KI8, the one available at http://xdaforums.com/showthread.php?t=1075278. and I've flashed both 1.8b2 and b4, but both are not able to go into deep sleep. I was able to with 1.8a4 and a6. I'm using Setcpu and cpu spy to check the voltages and cpu levels.
[Galaxy S II Original Android Development] jdmcivic:
isnt both the same as ondemand and interactive? just that for both, profiles have been added?

i have been using ondemand all along as it suits me best. cos im worried that the profiling will conflict with oc daemon.

using on demand, i noticed it plays movies at 100mhz. batt saver for me..
[Galaxy S II Original Android Development] :
Yes, and interactive should be snappier than ondemand :)
[Galaxy S II Original Android Development] jdmcivic:
interactive seems slow for me when flipping through apps. am using adw ex.

i believe the scaling is not fast enough therefore causing lags.
[Galaxy S II Original Android Development] :
Yes the same and it should be other way around, but gokhan tweaked ondemand I guess.

Anyway, ondemandx, all other default settings, 200-1200, deadline, no UV, no wake from sleep followed by reboot. B4.
[Galaxy S II Original Android Development] gokhanmoral:
do you have GPU undervolting?

if so, I have lowered the min settable GPU voltage from 900mV to 800mV

if you are using anything below 900 it is now effective and may cause problems if your device cannot handle it.
[Galaxy S II Original Android Development] idealforyou:
I started the device without UV

Next Problem is the PIN Pad for Sim Card. When the device started and make Media Scann and you enable not the PIN for SimCard the device startet autmatically without Sim Card. You must the device new started for enable Sim Pin.
[Galaxy S II Original Android Development] gokhanmoral:
check the init scripts.

there is no other changes in the kernel that can cause a player to crash.

about that sim card thing, I didn't understand what you mean.
[Galaxy S II Original Android Development] aqualeris:
On beta2. No deep sleep problems and AOS is at a nice single digit %. Love your work gokhanmoral! You're the best.
[Galaxy S II Original Android Development] crypticc:
I had exact same issues. Fixed by deleting the su file in /data/.siyah and rebooting
[Galaxy S II Original Android Development] KeesStolk:
http://xdaforums.com/showthread.php?t=1239719&page=88
[Galaxy S II Original Android Development] YaocH:
Oooo.. strange.. Hmm i just unplugged the phone from the usb charger and it seems that it now goes into deep sleep. Is this uncommon or a design of the kernel itself? I have not deleted the su file in the folder as instructed.
[Galaxy S II Original Android Development] idealforyou:
Sorry Gokhammel, the problems with SIM Pin and Astro Player is not your Kernel!!!
[Galaxy S II Original Android Development] neoxack:
Thank you very much for your black core;)
[Galaxy S II Original Android Development] AndreiLux:
Here's a example GPU script I just wrote and works:

#!/system/bin/sh

echo "Previous settings:"
cat /sys/devices/virtual/misc/gpu_clock_control/gpu_control
cat /sys/class/misc/gpu_voltage_control/gpu_control

echo [B]160 267[/B] > /sys/class/misc/gpu_clock_control/gpu_control

# 100 114 133 160 200 267 400 are valid values
# 160 267 are default

echo [B]950000 1000000[/B] > /sys/class/misc/gpu_voltage_control/gpu_control

# 800000 min / 1200000 max
# 950000 1000000 default

echo "New settings:"
cat /sys/class/misc/gpu_clock_control/gpu_control
cat /sys/class/misc/gpu_voltage_control/gpu_control

Edit the echo lines accordingly. Throw it into init.d or run it from a terminal if you want to play with the settings.
[Galaxy S II Original Android Development] zvikam:
Guys where is the link for 1.5 since the 1.6 doesn't get into deep sleep mode?

Thanks!!
[Galaxy S II Original Android Development] AndreiLux:
I don't know if it was just my settings and I somehow forgot to change it, but I found it set to the performance governor when checking. For me deep sleep works just fine btw, not the kernel's fault.

As for the GPU control again: I tested it with Riptide GP, Backstab, Fast 5 and the Electopia bench. Running at 800mV for both 100MHz and 267MHz stable. Can't really notice any slowdown from going from 160 to 100MHz.

Some Gameloft games (Fast 5) stay too much or are locked to the lower stepping. Setting/locking the speed to 267 increases the fps a lot in such games.

And again:

THE LOWER VOLTAGE LIMIT IS TOO DAMN HIGH!

:p
[Galaxy S II Original Android Development] fulmerville:
Japanese SC-02C

Hello,

does the new version 1.6 work on the Japanese SC-02C version? I see that 1.5 specifically says it works on the Japanese version, but not sure of the 1.6 version.
[Galaxy S II Original Android Development] poch_1421:
3% battery drain on a 7-hour overnight period using siyah v1.6 and dlev rom
[Galaxy S II Original Android Development] dkflint723:
Any chance of getting continued support for the NTT DoCoMo SC-02C? I know there are a lot of people that would really appreciate this.

Thank you.
[Galaxy S II Original Android Development] gokhanmoral:
I have uploaded NTT DoCoMo SC-02C to the first post.
[Galaxy S II Original Android Development] Miguel-:
I had a charging problem with 1.6b1: battery drained to 1% -> phone rebooted. I started it and plugged it in - no charging and I didn't notice it that time. So at empty battery I had to plug the cord a few times to get it charging again.. After getting it doing its thing everything went normally.
[Galaxy S II Original Android Development] kairton:
I'm wanting to use this kernel, but I know if I have to do "wipe cache" I have many games and programs installed.

What are the best values ​​to configure the "SetCPU"?

I am using these values ​​to the kernel Ninphetamine 2.1.3 (http://xdaforums.com/showpost.php?p=17201111&postcount=2512)

Thanks.
[Galaxy S II Original Android Development] jsbutran:
+ 1. I would like to know what are the best values for undervolting to get the stable rom working and high battery life.