yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] scorpion667:
No need to be anal. I don't recall seeing an indication in your post that the kernel you speak of was for i9100. As a result, I assumed it was for a different device as in the 4 months of owning this phone and trying every kernel I have not seen any that have the UV tweaks you speak of.

I am not trying to shoot your idea down at all. In my experience using the Lulz kernel which allowed the lowering of internal voltage (not cpu voltage) by 50mv rendered my touchscreen unresponsive and unstable. Where as others have lowered it by 100mv and had no issues. Having a kernel that may-or-may-not work on my phone with PRE SET undervolt values that are not changeable is not very attractive. However, if there was a way for the user to manually tweak the undervolt values for different components than that is something most people in this thread would consider, since we are already doing so but with CPU/GPU only.

I was just trying to say -125mv might work fine for your phone, -50mv might brick mine.

I'm at work so I didn't have time before to write a longer reply which left room for misinterpretation, for that I apologise.
[Galaxy S II Original Android Development] gokhanmoral:
sorry that I was kinda busy tonight.

@droidphile: I think I made a mistake by only enabling sched_mc. I read some more about arm topology and it seems that I need to enable AFTR as well (just as hardcore did).

I have used more aggressive settings with screen filter today and the battery drain decreased significantly. I was already using lowest brightness level before. so, you (or some of you) are right, we need to have a configurable part for brightness level in the kernel.

I checked the gamma decision part. there is a linear approach which maps 0-255 to 0-24.

I think It will be better to use an exponential function which will result in staying at low gamma (which results in lower brightness for amoled) for lower to mid light conditions.

I also want to make it configurable and you will probably supply two values (maybe three at most) and I will set them to be close to stock as default. if you know a little math you will be able to customize the response curve to your taste. if you don't you will use other people's experience or some examples I will provide.

anyway.. I have one more item in my list.

for the touchkey backlight problem: I could reproduce it. it is strange that it does keep enabled only when set to off. I will try to fix it in the next beta.

I will also remove all experimental codes from v2.2 branch and leave the to v3.0. I think that will fix new bugs that are new in latest betas.
[Galaxy S II Original Android Development] metze.b:
Hi,

I do have problem;

:confused:

Had flashed the latest miui, installed via cwm siyah v2.1, wiped cache and booted into miui - was fine - then I wanted to boot into recovery; now my phone doesn't boot at all, can't boot into miui and can't boot into cwm!

I can just see the boot screen with the yellow warning on it;

Have to get up for work in 5 hours... :D

Do need my phone to wake me up!

Flashing a new kernel is possible on a mac?

Only did in the past @ work on win!

Thanks for your quick help guys - I'm really in trouble now!
[Galaxy S II Original Android Development] CamoGeko:
So turning off your phone, then pressing vol up + home + power and holding doesn't boot you into CWM?

Kinda hard to believe lol, but you should still have recovery.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] fidorulz:
Im trying out this kernel for the first time and have the following issue. No matter what governor I select in SetCPU (set on boot selected) after a reboot it always goes back to conservative

Also it seems not to go into deep sleep for some reason

Any ideas?
[Galaxy S II Original Android Development] CamoGeko:
Ditch SetCPU and download Voltage Control from the market instead. That works much better with this kernel.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] metze.b:
exactely;

if phone is turned off, vol up + home + power - i got the samsung galaxy + yellow warning - if I keep hold it then it gets black for a few sec and then back to samsung galaxy + yellow warning...

vol down + home + power puts me into the Warning! a custom OS blablabla...

any idea how I could flash a new kernel via mac osx?

cheers!

I'm running out of cigarettes as well, it's not my day today... AAAAHHHH
[Galaxy S II Original Android Development] BoneMo:
my only one idea is ...make a virtual PC with windows :confused:
[Galaxy S II Original Android Development] fidorulz:
Voltage control works to select governors too?

Last time I used it it was only to select voltages
[Galaxy S II Original Android Development] override182:
it happened to me once.. i flashed back a stock romvia odin then reroot it with CF root then im back on Galnet MIUI once again..
[Galaxy S II Original Android Development] CamoGeko:
Yes, it can even select I/O schedulers lol

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] metze.b:
probably to much work at the moment (I know what you mean - thx anyway) - should find a wake-me-up-tool for the mac now and flash a kernel tomorrow at the work's win-pc;

normally, just flashing the kernel via odin and then cwm should be on it?! or do I have to install it separately?

cheers
[Galaxy S II Original Android Development] fidorulz:
Tried with voltage control and it still reverts back to conservative governor and 200min-1200max after multiple reboots
[Galaxy S II Original Android Development] CamoGeko:
So going to menu - save as boot settings, and save profile options don't do anything for you?

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] CamoGeko:
CWM is included with CF-Root, flash that via ODIN and you should have your recovery back.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] metze.b:
cheers, will try this 1st thing tomorrow morning!
[Galaxy S II Original Android Development] fidorulz:
Thanks for the tip tried that and the freq changes save but the governor always goes back to conservative.

Tried selecting Smartass V2 and Lulzactive but still the same
[Galaxy S II Original Android Development] tomdot:
Maybe its not getting SU properly. Delete SetCPU from Superuser and start setcpu again...
[Galaxy S II Original Android Development] dave6018:
Reflash cwm with Odin then boot into recovery and reflash your rom oh and never use rom manager with miui as it screws it up
[Galaxy S II Original Android Development] YaocH:
I dont know if this is considered a bug. I'm using galnetmiui latest with latest siyahkernel. My wireless router is set at channel 13, so I have to set the number of regulatory channels of phone's wireless settings to 13 or 14, but whenever I restart, the values goes back to the stock 11. Any ideas?
[Galaxy S II Original Android Development] Nirvana1000:
I know i'm being lazy,but does anyone have the link for Siyah 2.2beta6 download?

:)Thanks.
[Galaxy S II Original Android Development] timberwolf60:
http://www.gokhanmoral.com/
[Galaxy S II Original Android Development] Nirvana1000:
Thank you sir.:)
[Galaxy S II Original Android Development] hedayat7:
hi gokhan ,

just found out that sgs2 i9100G version ram usage is 0.91Gb ..

just an idea that maybe you can include this to next release ?

thanks
[Galaxy S II Original Android Development] droidphile:
Gokhan, hardcore says that sched_mc is a replacement for hotplug mode, and enabling ARM Off Top Running (AFTR) swtiches cpu from high-overheads caused by hotplug mode to multi-core aware process scheduler.

So AFTR actually supports idling more, compared to hotplug.

But then, won't having our gs2 in default hotplug mode affect AFTR? Or can they go hand-in-hand.

Anyways, if AFTR really transforms our cpus to multi-core aware processors, our gingerbread based roms will become semi-ICS!

Keep up the good work Gokhan :)
[Galaxy S II Original Android Development] veyka:
I'm sure he will get to work adding software to change the soc to a omap 4 with the next kernel. I9100G is nothing like the normal I9100, it's almost a totally different to phone apart from the name and screen.
[Galaxy S II Original Android Development] Idan73:
Strange that set cpu does not work for you. Are you sure you did not restore that app from titanium. If that's the case please make sure you delete data and set it again. Also make sure you are running latest set cpu. In any case it should not be defaulting to conservative with this kernel.

Voltage control issue with saving and reboot with this latest beta is actually known since it was xan that actually mentioned it as well. Save for voltage control is in init.d folder

Go back to beta 8 or 6. Seems this beta does not run init.d at startup at all including charging voltage script. For me at least! Went back to beta 8.

Sent from my GT-I9100
[Galaxy S II Original Android Development] metze.b:
cheers for that!

---------- Post added at 08:10 AM ---------- Previous post was at 07:45 AM ----------

I know I'm off topic now, but...

which cf-root kernel do I take if I don't know my kernel-version?!

:cool:
[Galaxy S II Original Android Development] metze.b:
working now - thx for your support guys.
[Galaxy S II Original Android Development] crypticc:
Rather than change gamma, which might mean the kernel becomes incompatible with supercurio's app. Why not just use the framework apk edits to change brightness thresholds and values?
[Galaxy S II Original Android Development] AndreiLux:
Of course they use voltage regulators, everything is hooked up to the power supply IC.

/arch/arm/mach-s5pv310/mach-c1.c

REGULATOR_INIT(ldo1, "VADC_3.3V_C210", 3300000, 3300000, 1,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo3, "VUSB_1.1V", 1100000, 1100000, 1,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo4, "VMIPI_1.8V", 1800000, 1800000, 1,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo5, "VHSIC_1.2V", 1200000, 1200000, 1,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo7, "CAM_ISP_1.8V", 1800000, 1800000, 0,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo8, "VUSB_3.3V", 3300000, 3300000, 1,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo10, "VPLL_1.1V", 1100000, 1100000, 1,
REGULATOR_CHANGE_STATUS, 1);
#if defined(CONFIG_TARGET_LOCALE_NAATT)
REGULATOR_INIT(ldo11, "TOUCH_2.8V", 3100000, 3100000, 0,
REGULATOR_CHANGE_STATUS, 1);
#else
REGULATOR_INIT(ldo11, "TOUCH_2.8V", 2800000, 2800000, 0,
REGULATOR_CHANGE_STATUS, 1);
#endif
#if defined(CONFIG_MACH_C1_REV00)
REGULATOR_INIT(ldo12, "CAM_SENSOR_CORE_1.2V", 1200000, 1200000, 0,
REGULATOR_CHANGE_STATUS, 1);
#else
REGULATOR_INIT(ldo12, "VT_CAM_1.8V", 1800000, 1800000, 0,
REGULATOR_CHANGE_STATUS, 1);
#endif
#ifdef CONFIG_FB_S3C_S6E8AA0
REGULATOR_INIT(ldo13, "VCC_3.0V_LCD", 3300000, 3300000, 1,
REGULATOR_CHANGE_STATUS, 0);
#else
REGULATOR_INIT(ldo13, "VCC_3.0V_LCD", 3000000, 3000000, 1,
REGULATOR_CHANGE_STATUS, 1);
#endif
REGULATOR_INIT(ldo14, "VCC_2.8V_MOTOR", 2800000, 2800000, 0,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo15, "LED_A_2.8V", 2800000, 2800000, 0,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo16, "CAM_SENSOR_IO_1.8V", 1800000, 1800000, 0,
REGULATOR_CHANGE_STATUS, 1);
#if defined(CONFIG_MACH_C1_REV02) || defined(CONFIG_MACH_C1Q1_REV02) || defined(CONFIG_MACH_P6_REV02) || defined(CONFIG_MACH_TALBOT_REV02) || defined(CONFIG_TARGET_LOCALE_NA)
REGULATOR_INIT(ldo17, "VT_CAM_CORE_1.8V", 1800000, 1800000, 0,
REGULATOR_CHANGE_STATUS, 1);
REGULATOR_INIT(ldo17_rev04, "VTF_2.8V", 2800000, 2800000, 0,
REGULATOR_CHANGE_STATUS, 1);
#else
REGULATOR_INIT(ldo17, "CAM_AF_2.8V", 2800000, 2800000, 0,
REGULATOR_CHANGE_STATUS, 1);
#endif
REGULATOR_INIT(ldo18, "TOUCH_LED_3.3V", 3000000, 3300000, 0,
REGULATOR_CHANGE_STATUS | REGULATOR_CHANGE_VOLTAGE, 1);

REGULATOR_INIT(ldo21, "VDDQ_M1M2_1.2V", 1200000, 1200000, 1,
REGULATOR_CHANGE_STATUS, 1);

Everything is hooked up on a low-dropout regulator. One could undervolt a lot of things but it needs to be tested how much for it to be still safe/working.
[Galaxy S II Original Android Development] Nucleardwarf:
What are the best set cpu settings and voltages with this?
[Galaxy S II Original Android Development] :
Default ones.
[Galaxy S II Original Android Development] xBlackDroid:
Reporting a issue with the BT using CM7 113 and beta9 i cant see the device.

Motorola Xoom, Overclock 1.4 Ghz, Tiamat Moray
[Galaxy S II Original Android Development] tombond:
Atm I'm using 2.1.1 and CheckRom 3.1.1, is there a way to get BLN working again? I can't find it on the KitchenApp.
[Galaxy S II Original Android Development] CamoGeko:
Something to ask in CheckRom thread maybe?

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] rauschkugl:
Search the market! And this is not kernel related.

Sent from my GT-I9100
[Galaxy S II Original Android Development] bgx:
Yeah! +1 for this! Since I use siyah kernel and that's from the beginning I have lowered my backlight per modding the framework and also using a tasker script witch determine the sunset and sunrise and switch on screenfilter for the time after sunrise! It would be great if that can the kernel by default and I can change the highlight per tasker like I do at the moment without screenfilter app.

Perhabs there is a way to lower the highlight on the lowest step that would realy great!
[Galaxy S II Original Android Development] Ferdimage:
Back to Beta 8 for now, incoming call wakeup delay issue, regardless of what Gov is used.
[Galaxy S II Original Android Development] crypticc:
-1 :]
[Galaxy S II Original Android Development] brack11:
I'm on ginger miui now with your kernel v2.2beta6 and this is the latest version that has proper behavior of softkey backlight - if I disable backlight in settings it won't light, the later betas have those buttons backlighted independent from settings. There is also checkbox in screen filter app which says "enable softkey backlight" or something like that, so, when I enable that proper behavior is backlight disabled when screen filter run, but this behavior is only works in versions before 2.2b6. Custom kernels based on Sammy firmware have a bit different behavior but I think the best of all - the buttons are light only a few sec on press the button. Is that possible to implement this behavior for miui in this kernel? Very difficult to read at night when those buttons are lit.

Sent from my GT-I9100
[Galaxy S II Original Android Development] el_tute:
You must install 2.2beta6, then boot, you'll see that bln is workin' again, ok, now you can flash 2.2beta9 and bln will work (there is a problem with libraries of bln in beta9)
[Galaxy S II Original Android Development] byobodybag:
Anyone have a quick workaround with disabling the scripts from init.d? I installed the uv/uc scripts for Siyah in the init.d folder, rebooted and now I'm stuck at the screen with a yellow triangle.
[Galaxy S II Original Android Development] cheewaca:
The same issue here with Beta 9. Good performance, no lag but sometimes when the phone is in deep sleep incoming calls don´t wake up the phone. With stock rom and stock values of corse.
[Galaxy S II Original Android Development] kenkiller:
Noticed something strange with Beta9.

Button lights are wonky, sometimes stays on constantly even when set to 1.5s in settings. Also, screen filter has an option to off button lights when activated, but in beta9 it stays on. Sometimes it happens, sometimes it works properly after exiting/running screen filter.

Going back to beta8, everything is fine again.　On Hyperdroid rom, not CM or MIUI.
[Galaxy S II Original Android Development] droidphile:
Stuck in yellow triangle can not be because of init.d scripts. Those scripts are run after booting + 30 seconds.

Still if you suspect scripts, try flashing any kernel that does not support init.d scripts. (Use Odin), boot normally, remove init.d scripts, flash siyah and boot again.

---------- Post added at 07:57 PM ---------- Previous post was at 07:49 PM ----------

Beta 10 changelog says backlight not turning off is fixed. Wait for some time. All will be well!
[Galaxy S II Original Android Development] myfluxi:
From my understanding AFTR is enabled by default on our device, check arch/arm/mach-s5pv310/cpuidle.c

I'm testing SCHED_MC in my own kernel for ~ 2 weeks after Guittots commit.
[Galaxy S II Original Android Development] byobodybag:
Would love to flash any kernel but the ROM is MIUI and it being AOSP, I don't think it'd take just anything. Now if only I had the default kernel for that.

I'm flustered what works, without actually wiping.

EDIT: I finally found a kernel that works, something for MIUI itself. Got back in the phone, whew...

For the kernel, its FLUXI http://www.android-hilfe.de/custom-...3-rom-miui-sgs2-1-11-04-german-xx-kernel.html
[Galaxy S II Original Android Development] tolis626:
Gokhan,seeing as you disabled SCHED_MC for beta 10,will you later re-enable it along with AFTR or will you leave everything as it was?Just out of curiosity,I've disabled SCHED_MC myself. :p

OT: Does anyone know what one could expect from increasing/decreasing VM Heapsize?Because I've upped mine to 128mB up from 64mB that is stock and I THINK it's a little smoother,although it must be placebo.I changed it via Rom Toolbox's build.prop tweaks menu btw. :)
[Galaxy S II Original Android Development] teo91:
What script do you recommend with SiyahKernel 2.1.1. I Have Baptista Rom (2.6)
[Galaxy S II Original Android Development] kenkiller:
Thanks....Darknight version is out, will just use that since I dun play with the voltage settings anyway. :D
[Galaxy S II Original Android Development] droidphile:
I haven't downloaded the sources yet. Will dig into see if AFTR is enabled. But Gokhan said he forgot to enable AFTR in Beta 9, and now in beta 10 sched_mc will be disabled completely. May be we should read the feedbacks from speedmod users too. Afaik, hardcore enabled sched_mc and aftr in his kernel only 3 days ago.
[Galaxy S II Original Android Development] gokhanmoral:
hmm, both yes and no.

you are right. we have the required code in cpuidle.c

but I think you need to add a bitwise-OR to enable_mask ( | ENABLE_AFTR) to have it enabled.

I enabled it in beta10 but disabled sched_mc because beta10 release is a darkknight edition (with gadgetcheck's recommendations) so I wanted it to be stable not experimental.

I will re-enable it in beta11.

meantime I will read more about sched_mc when I have time :)
[Galaxy S II Original Android Development] SilverMist1:
so in beta10 wont we be able to UV? and will the bt for miui be fixed?
[Galaxy S II Original Android Development] smitna:
Hi, you can boot into recovery mode and then work with "adb shell" (from Android SDK or from SuperOneClick http://xdaforums.com/showthread.php?t=803682)

Steps:

adb shell

Only if the /system -partition is not already mounted read/write:

mount -o remount,rw /dev/block/mmcblk0p9 /system

rm /system/etc/init.d/yourscript (delete the script)

or

mv /system/etc/init.d/yourscript /system/etc (move the script from startup folder to /system/etc)

mv

exit

Then reboot and all should be fine.
[Galaxy S II Original Android Development] myfluxi:
That's the kernel I mentioned one post above you. ;) Watch out for an update to XX.06 possibly tonight.
[Galaxy S II Original Android Development] gokhanmoral:
you will be able to UV, but not as much as in other versions.

I put some limitations to undervolting.

you won't be able to undervolt below 900mV

you won't be able to undervolt a step more than 100mV (if your stock voltage is 1050, you won't be able to undervolt below 950).

or another limitation is that you won't have charge current more than 800mA, because 800+ may cause overheating and some instabilities during charging.

in other words, darkknight edition is a safer version which has all the functions but with some limitations.
[Galaxy S II Original Android Development] kalpik:
B10 tar link is fine, but CWM gives 404.
[Galaxy S II Original Android Development] gippy2:
Just a heads up before people whinge that the B10 Zip dont work, You left the `D` out of Dark :D
[Galaxy S II Original Android Development] droidphile:
In the rom i'm using, it's already set to 70mb.

But i wonder how much performance gain we can achieve by setting it to 128 mb. OK, big apps won't result in running out of memory at increased heap size since our device has a lot of ram.

For apps with low memory requirements, lower heapsize would be better because the cycles will take lesser time to complete.

I don't think at 64mb, or 70 mb, any apps can end up in infinite garbage collection cycles.

And because of 1 g ram, 128 might not hurt either.
[Galaxy S II Original Android Development] gokhanmoral:
thanks for reporting it. fixed. (it was "arkKnight" edition :D )
[Galaxy S II Original Android Development] kalpik:
Yep.. Just figured that :p
[Galaxy S II Original Android Development] kenkiller:
Must be the Arkham City edition. :D
[Galaxy S II Original Android Development] fidorulz:
I'm not using the beta but the last official release. I removed setcpu completely and tried voltage control and governor goes back

I went back to my old kernel and the issue followed so I'm not sure if something was installed in init.d folder that may be causing this

I restored a backup via cwm and everything went back to normal
[Galaxy S II Original Android Development] kalpik:
Just had a reboot with Beta10. Camera was making clicking sounds for like 5 seconds. Let me see if I can reproduce it.

Ok, rebooted again! Was just scrolling through app drawer. Let me remove voltage control init.d file and see..
[Galaxy S II Original Android Development] iamsmallpang:
hi gokhanmoral

beta10 download CWM zip file link ERROR
[Galaxy S II Original Android Development] gokhanmoral:
oops. I fixed it but forgot to update. try again.
[Galaxy S II Original Android Development] :
Just flashed b10 tar using chainfires Mobile ODIN app and worked great.

Heads up for the little tool and also for beta 10.
[Galaxy S II Original Android Development] julianico:
Problem beta 10 voltajes a + de 100000mv
[Galaxy S II Original Android Development] navodwickra:
BLN behaves funny on MIUI :(
[Galaxy S II Original Android Development] kalpik:
Ok, I think Voltage control script is broken with B10. You need to delete the voltage settings file, and then UV/OC again.
[Galaxy S II Original Android Development] gokhanmoral:
hmm, strange. I did not have any reboot with 100mV undervolting for each step

I still have some questions about undervolting. for example, the device uses 800MHz before going into deep sleep and the voltage level of 800MHz is used before changing the frequencies between 500 200 and 100MHz. but for my case, lowering everything by 100mV doesn't cause any instability but lowering only 100MHz by 100mV causes instabilities. therefore, there may be a dependency for the "voltage distance" between steps in terms of stability.

anyway... I will go back to stock voltages for my daily usage :)

maybe darkknight edition should disable undervolting to be more stable...
[Galaxy S II Original Android Development] kalpik:
Actually all my UV settings were working on previous beta versions. The only thing fishy I noticed was that when I opened Voltage Control on Beta 10, it warned me saying something like "new kernel detected old profiles might be incompatible".
[Galaxy S II Original Android Development] antt00:
Beta 10 make my device freeze. Even after removing voltage control script (meaning on stock kernel setting). When i run voltage control app to make my changes again, the device freeze before I can even apply. On Checkrom Rev 2.0.
[Galaxy S II Original Android Development] kalpik:
I was having same issue. But it was solved after removing init.d script. Please check your /etc/init.d folder once again to be sure that the script was deleted.
[Galaxy S II Original Android Development] Vaedryn:
Beta 10 the same as beta 9 , no internal sd card found under cm7 :(

SGS II Cyanogen Tapatalk