yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] xan:
Are you in contact with neldar, developer of [MOD] BackLightNotification v0.9.8 RC3 - Use the touchkey backlight for notifications?

I'm really looking forward to combination of these two :)

(my humble suggestion - clean OP of outdated info, it can be confusing)

//edit: migration from b1 was easy -> just flash and restart!
[Galaxy S I9000 Android Development] cba1986:
i'm still not sure. i'm afraid to the kernel cause instability on the system. Such as music player crashing or the phone don't waking up after a long time sleep.
[Galaxy S I9000 Android Development] xan:
Use overclock widget and set frequency to 100-1000.

Make sure u dont undervolt.

Test these settings and pls report about not wakingup or mp crashes.

If it will be stable, ur CPU is uncapable of 1200Mhz and/or UV.
[Galaxy S I9000 Android Development] raspdeep:
he has to release source code before any of our kernel mods can be added.
[Galaxy S I9000 Android Development] raspdeep:
some of your concerns are already things of the past. if your cpu doesnt handle o/c properly, u can control using apps per suggested by Xan (either oc widget or setcpu) should do just fine.
[Galaxy S I9000 Android Development] dupel:
Voodoo has been updated to beta 3. Think we need new kernel )
[Galaxy S I9000 Android Development] raspdeep:
looking at the changelog, it just bug fix that doesnt create /sdcard/Voodoo? If so, there is no need for new build cos we can just create Voodoo folder in /sdcard

I will talk to curio later and see what he says
[Galaxy S I9000 Android Development] dupel:
unrelated post
[Galaxy S I9000 Android Development] ufuuu:
That voodoo support is awesome! Thanks very very very much guys.

And what should I do if I wanna revert back to a stock kernel? (from oc120_voodoo_b2)

just load stock kernel's tar file in PDA using ODIN and flash,

or create a disable lagfix folder,

or wipe data and cache from recovery (I have .apk of all of my apps,so it's not a problem)

And could somebody write down the recommended uv and oc values for battery saving, if it exists?

Thanks again
[Galaxy S I9000 Android Development] xan:
Reverting to stock:

1. Create file /sdcard/Voodoo/disable lagfix (any file explorer, adb touch)

2. Reboot normally (wait till finished converting from EXT4 to RFS -> process duration depends heavily on amount of data on /data partition)

3. Reboot into download mode (VOL- + Home + Power)

3. Flash stock kernel by Odin (load kernel as PDA, make sure repartition is unticked, do NOT select .pit file)

That would be all,

voodoo lagfix reverted.

No wipe/format needed...

About UV values, it solely dependent on your specific device. Try using -0mV and check if its stable (12h or sth!, normal usage, 10-15mins of stress benchmarks). After u got stock values tested (on this kernel) proceed to lowering values. I suggest doing it one by one, step by step. Most devices can handle -25mV on 100-800Mhz, but its not guaranteed! After similar testing (12h or sth!, normal usage, 10-15mins of stress benchmarks) u can go 1 step further with undervolt. BEWARE, undervolting CPU can lead to CRASHES and DATA LOSS, so make sure you dont have anything important not backed up.
[Galaxy S I9000 Android Development] Tayutama:
Hey raspdeep.

Would it be possible to get a kernel with init.d support? :)
[Galaxy S I9000 Android Development] raspdeep:
uploaded voodoo_b3 with init.d support. Let me know if it works for ya
[Galaxy S I9000 Android Development] Tayutama:
Cool ill test it when i'm done editing some .9.png images...
[Galaxy S I9000 Android Development] Tayutama:
Just a quick question.

If i include a file called S_Overclok in init.d folder which have the following content:

#!/system/bin/sh
sleep 1
/system/xbin/busybox cat /system/etc/init.d/freq_volt_table >/sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table

and then in freq_volt_table is has this:

1200000 200000 1050 1100
1000000 200000 1050 1100
800000 200000 1050 1100
600000 200000 950 1100
500000 200000 950 1100
400000 200000 950 1100
300000 200000 950 1100
200000 200000 600 1100
100000 100000 600 1000

Would it then be able to use that?

Also what do the files in init.d need to start with since they arent running at all on boot when i called them something with S_
[Galaxy S I9000 Android Development] kindaichi24:
if im using jm 7 which stock kernel should i flash back with? jm5's?
[Galaxy S I9000 Android Development] elghouchd:
Hey...does anyone know if this kernel is safe to install on a captivate running the stock firmware??
[Galaxy S I9000 Android Development] cba1986:
ok raspdeep. Thanks for the answer. I will wait for beta4 to flash.
[Galaxy S I9000 Android Development] dupel:
Guys! No one can help you unless you actually tell us what firmware you are on, what kernel you used, etc.
[Galaxy S I9000 Android Development] elghouchd:
Sorry! Im still a noob at this....So im running the JF6 firmware and i am currently using Unhelpful's OC kernel...is there anymore information that i should include?:confused:
[Galaxy S I9000 Android Development] raspdeep:
this sysfs table you have made is for Unhelpful's kernel mod, my approach is different and described in post #1.. I only allow UVLF (100-800mhz) and UVHF (1 - 1.2ghz) variables with xan's app to change the two values easily using GUI

On a side note, are you sure the chip will run with those values? I really doubt it can run 1.2ghz @ 1.05v.. Really?
[Galaxy S I9000 Android Development] raspdeep:
you can flash with jm5 stock kernel but before you go back to stock, disable voodoo first or it wont boot.
[Galaxy S I9000 Android Development] raspdeep:
there are some differences between i9000 and captivate, i think it will boot but some things might not work properly.
[Galaxy S I9000 Android Development] Unhelpful:
The orientation sensor will be all wrong, probably the sensor is mounted differently on each phone.
[Galaxy S I9000 Android Development] Tayutama:
Tose values was taken from the captivate board so no idea :)

Anyway other question was what do the files need to be called for init.d to execute them?
[Galaxy S I9000 Android Development] raspdeep:
It will run all the files in /system/etc/init.d folder regardless what they are called

If you want to run the files in a specific order, you can named the files with numeric numbers in front, for example:

20do_this_first

40do_this_second

60do_zipalign

99do_last_initialization
[Galaxy S I9000 Android Development] Tayutama:
In that case then it doesn't work :)

Since it doesn't run the following file i got: S_setup

/system/xbin/busybox chmod 777 /system/etc/hosts
/system/xbin/busybox rm -R /data/dalvik-cache/*.*
/system/xbin/busybox rm /data/system/batterystats.bin
/system/xbin/busybox mv /system/temp/data/app/*.* /data/app
/system/xbin/busybox rm -R /system/temp
/system/xbin/busybox rm /system/etc/init.d/S_setup

And well the file is still there on boot and no files have been moved to /data/app
[Galaxy S I9000 Android Development] ufuuu:
thanks for the clear answer. do i need to disable voodoo beta2 before update it to beta 3?
[Galaxy S I9000 Android Development] raspdeep:
i will check and let u know
[Galaxy S I9000 Android Development] raspdeep:
you can flash over to b3 without disabling
[Galaxy S I9000 Android Development] ufuuu:
cool :) thanks
[Galaxy S I9000 Android Development] raspdeep:
fixed with oc120_voodoo_b3.1

i made a mistake in init.rc, thanks to curio for correcting :D
[Galaxy S I9000 Android Development] raspdeep:
voodoo4 is out

i'd suggest to uninstall lagfix because the parameters for creating ext4 partition has changed.

you can either do:

1) flashed b4 followed by disable lagfix and reenable lagfix or

2) disable lagfix first with ur current b2 or b3 then flash to b4 and reenable lagfix
[Galaxy S I9000 Android Development] Tayutama:
Cool also can confirm init.d works now :)
[Galaxy S I9000 Android Development] bratfink:
Black Screen

No matter which kernel i use when the phone is left asleep for a few minutes and i try to turn the screen back on i get no reaction and i must do a soft reset (battery out then back in) to get it to wake up. What am i doing wrong?

Also how do i activate voodoo using the latest kernel?

Do i flash kernel on stock firmware then flash voodoo? Or simply flash the kernel and voodoo is activated already?
[Galaxy S I9000 Android Development] xan:
bratfink, try one of stock kernels, or just voodoo v4 kernel (not o/c one).

Check voodoo's website for details. Its easy.

I would love to see any possibility of overvolting 1.275v@1,2ghz. I'm dying to know if it is be stable on my device!
[Galaxy S I9000 Android Development] jodue:
same here ... and i guess it's because the cpu is running @ 1000 mhz all the time while in standby ... i guess it's because of the bug in the voodoo kernel but this should be fixed in betav4??!
[Galaxy S I9000 Android Development] raspdeep:
are you using setcpu and do profile that set min and max frequencies when screen is off? that would account for phone not able to wake up if the max frequency is set too low

if u install the latest o/c voodoo b4 kernel, voodoo will be enabled, you should hear some robot talking during the conversion process tho.. lol

or you can use terminal and do a mount command

if you see /data mounted as ext4, then voodoo is enabled.. can also check /sdcard/Voodoo folder with some log files inside
[Galaxy S I9000 Android Development] raspdeep:
that problem is already resolved in b4 and dude, you are quoting a post that is long time ago..
[Galaxy S I9000 Android Development] dreamtheater39:
just flashed b4 and its looking good! :)

thanks a lot for your effort! cheers
[Galaxy S I9000 Android Development] jodue:
sorry my bad. i had severe battery drain with oc12+voodoob2 (~30% during the night) so i browsed through the thread and have (obviously & without intent) quoted old stuff :D ... installed oc12b4 again and it's working now. maybe i had some program running in the background which kept the cpu@1000 while i tested it ...

anyway: thanks for your great work! ;)
[Galaxy S I9000 Android Development] ufuuu:
which scheduler do you suggest in xan's voltage control app? When I open it says noop, anticipatory, deadline, [cfq]. So, is this an ordering to use? The app says current scheduler is cfq.

edit: after a bit searching, noop looks like best. But I still appreciate the masters's opinions/experience :)
[Galaxy S I9000 Android Development] midijunkie:
update.zip would be very nice. dont like software like odin :D

great work
[Galaxy S I9000 Android Development] FadeFx:
hmm, sounds intersting here, cant wait for my device to return from repair... :(
[Galaxy S I9000 Android Development] jodue:
same here but you can easily build your own:

* download testsign

* download the corresponding update.zip from project-voodoo.org

* update.zip: replace the zImage in the zip with the oc-zImage

* update.zip: delete CERT.RSA, CERT.SF, MANIFEST.MF in META-INF/

* save the update.zip & run: java -classpath testsign.jar testsign new-update.zip new-update-signed.zip

the last command will sign your new update zip with a testkey so that you can flash it with the stock recovery...there you go :)
[Galaxy S I9000 Android Development] raspdeep:
the differences between the schedulers are very small but noop is really good for conserving battery because it uses least overhead from cpu. you should try different scheduler for a few days and get a feel how each works for you.
[Galaxy S I9000 Android Development] raspdeep:
this will not work without the redbend_ua binary and a properly written updater-script.. Supercurio has a thread that explains how to put the kernel in update.zip for recovery flashing..

Personally, i feel its easier and quicker to flash with Odin unless those with Mac / *nix box that cannot run Odin. The solution can be found with VBox

http://www.virtualbox.org/wiki/Downloads
[Galaxy S I9000 Android Development] jodue:
thats why i wrote:

which contains the redbend_ua and a proper update script. of course i did this before and verified that it works just like that!

i can run odin with virtualbox on ubuntu but i HATE IT and it's a pain in the ass. also i feel that i am faster just replacing the zImage & re-signing it that to boot up that crappy dozeXP in vbox...
[Galaxy S I9000 Android Development] FadeFx:
raspdeep, did you already consider implementing BLN into your kernel? i think your project is the one that has most potential for being the "all-in-wonder" for SGS
[Galaxy S I9000 Android Development] kindaichi24:
hi rasdeep, as supercurio's kernel drain batt abit fast so i decided to try ur kernel. wad does scheduler cfq noop deadline and aniticipatory means? i read and the suggested setting is noop? if i out -25mv on the high and -50mv on the low frequencies means hw much mhz it will be running at? and how do i overclock my phone if i decided to overclock instead of undervolt? i assume over clock is +25mv or smth like this or am i wrong. sorry 1st time use this voltage control application :(

PS: i got 1965 benchmark even when i underclock it? it seems very smooth man. And my kernel version is jw@jw-ubuntu #3, this is the latest 1 rite??? And i suppose this kernel dont support clockwork recovery too rite??
[Galaxy S I9000 Android Development] MZWiZard:
I'm still watching this topic every day :) Currently, I'm running the Voodoo-lagfix beta 4, with your oc that supports it. Its running just fine. Keep up the good work! :cool:
[Galaxy S I9000 Android Development] raspdeep:
i need a way to disable this mod for peeps that do not want to use this or are using LED notification mod. yes, i will look into adding this mod
[Galaxy S I9000 Android Development] raspdeep:
The answer to most of your questions already in post #1 so i suggest you take sometime to read it.

Undervolt does not change the frequency. It is running the cpu at a lower voltage to safe battery consumption and possibly lower voltage means cooler temperature.

To control frequencies, you can use OC widget or SetCPU. To undervolt, use Xan's app. If you do not control the frequencies, it is by default frequencies range from 100-1.2ghz
[Galaxy S I9000 Android Development] zond:
ClockworkMod gets stuck

After I installed this kernel I can no longer boot to clockwork mod recovery...

It gets stuck trying to replace regular recovery with itself while booting.

Any idea how this happened?

regards

//Martin
[Galaxy S I9000 Android Development] raspdeep:
Read this:

http://project-voodoo.org/changelog

CWM will only work when you disable lagfix and go back to RFS
[Galaxy S I9000 Android Development] raspdeep:
BLN support in oc120_voodoo_b4.1. All credit goes to neldar for the patch.
[Galaxy S I9000 Android Development] datagrid:
maybe stupid question but is the voodoo lagfix is ok on JPH ???

;)
[Galaxy S I9000 Android Development] zond:
Oh... so, how should I go about it if I want to install both a deodexed ROM (xdaforums.com/showthread.php?t=743506) and this kernel? Can I install the ROM first? (I have the impression, perhaps false, that the kernel is needed for the ROM to work...?)

Or can anyone recommend a good kernel that doesn't break CWM?

regards,

//Martin
[Galaxy S I9000 Android Development] jodue:
no, voodoo does not work with 2.2 firmware atm.

you can install the custom rom first (already includes a kernel) and after that flash this kernel (over it).
[Galaxy S I9000 Android Development] zond:
I actually tried that, but when I rebooted after flashing the rom the phone booted up to a black screen. I was unable to get the screen to turn on, even though adb shell worked fine which showed that the phone was working apart from the screen...

I may try again, but I am a bit hesitant :D
[Galaxy S I9000 Android Development] dupel:
Mate, if you have vibrant - do not install this kernel, its for international lagaxy only.

If you have I9000 - do not install the rom =)
[Galaxy S I9000 Android Development] raspdeep:
the link you posted is a vibrant ROM.. what phone do you have?

when you install stock firmware, it comes with stock kernel so you dont need another kernel to install custom ROM. Custom ROMs are mods that they make replacing stock files.

all you need to install that signed custom ROM is to rename the file to update.zip and copy into your /sdcard.. Boot to recovery and pick the flash update.zip option. You dont need CWM to flash unless the ROM is unsigned.
[Galaxy S I9000 Android Development] zond:
Right I have an international galaxy... what is a good ROM for a I9000 then? :)
[Galaxy S I9000 Android Development] zond:
I have an I9000, so the ROM is evidently not a good idea. Do you guys have any other ROM that you could recommend for an international galaxy?
[Galaxy S I9000 Android Development] FadeFx:
try tayutamas rom, it comes in full or light flavour and is sayed to be verry snappy...

ah, and please forget about CWM for now, its not fully working and seems unsupported by the dev atm.
[Galaxy S I9000 Android Development] raspdeep:
tayutamas rom indeed, it has my kernel too :)
[Galaxy S I9000 Android Development] bratfink:
2.2

Is there any change the kernel from the JPH rom can me extracted and the edited to have features similar to this kernel i.e. UV/OC?
[Galaxy S I9000 Android Development] FadeFx:
dont think so, i guess it could be hard to decompile the whole kernel, and eaven if you manage to, youd have a hard time analizing the code since there will be no comments...
[Galaxy S I9000 Android Development] jodue:
the kernel can be extracted but it's just about 2.5MB of hardcore machine code. we have to wait till samsung releases the source ...

hehe, i guess "decompilation" of the (whole) kernel is impossible, or at least making sense of it. maybe just replace the frequencies with a hexeditor :P ... even if someone could do it i wouldn't want that kernel! eeeik. sounds very dirty :D
[Galaxy S I9000 Android Development] zond:
I'll try that. But what is the recommended way to flash updates if the CWM is discouraged?
[Galaxy S I9000 Android Development] FadeFx:
edit: remove any lagfix first!!!

put the rom in your /sdcard (internal), rename to update.zip, power your phone off, start with [vol -]+[home]+[power] to stock recovery mode and select "apply update.zip" using [vol +] and [vol -] to navigate and [home] to select, navigate to yes and wait...
[Galaxy S I9000 Android Development] zond:
Oh, I thought the Clockwork and other rom manager things were needed since regular update.zip-files were not signed properly, or with test keys, or something?

So that is no longer the case? I will try that then :D

EDIT: How do I remove a lagfix?

EDIT2: Oh, you mean lagfixes I have installed now, I thought you meant in the rom I wanted to load :---------)
[Galaxy S I9000 Android Development] dupel:
VEry big thanks again for this kernel. Your doing such awesome job. Really, really awesome.

Wish my phone actually supported uv... (still want to test playing music on ext cd (crashes) vs internal sd. Maybe it wont crach there...

BTW, why did you drop the unhelpful patch for gpu (im not even sure what it did, but as I understood it allowed for underclocked gpu)? Was it the clock lag?
[Galaxy S I9000 Android Development] midijunkie:
everything works well(colorfix would be nice!).

if you touch the display the clock will go up to 1000mhz. is that something build in the samsung kernel? why doesnt it go to 1200mhz?

discovered through setcpu, info page.
[Galaxy S I9000 Android Development] kindaichi24:
erm im having random hang 2-3 times per day, the screen stuck there and cant do anything till i pull out the battery and restart. i set hf to -25 lf to -25 but still having the same problem. if i set it to 0 0 is it running at 1.2ghz and will it eats up alot of battery juice this way??
[Galaxy S I9000 Android Development] KLoNe1:
This is exactly my problem as well. Screen turns off when 'power' pressed and STAYS OFF occasionally. HF to -0 LF to -25 will hang on music played on ext SD. CHEWS through the battery.

I can't use this at all until it's fixed. Unfortunate because I love the speed increase :(
[Galaxy S I9000 Android Development] distortedloop:
I'm on a Mac, and while I can get Odin to run in both VMWare and Virtual Box, I have never been successful in getting the VM/VB to recognize the SGS long enough to get Odin to connect to it; it just sort of disappears. I've also never seen a Mac user post success with Odin in any way other than boot-camp (blek) and booting to real Windows.

If you know otherwise, I'd love to be pointed in the right direction! :confused:

Really, it's that easy? I will investigate further...I've been without rasdeep's kernel for a couple of days because I'm too lazy to get Windows boot going. Thanks for the tip.

EDIT: Just re-read the latest update to the first post and see rasdeep offering update.zip method, now. Nice! Still will learn of modifying my own for future reference.
[Galaxy S I9000 Android Development] raspdeep:
this is frequency scaling, the frequency goes up depending on load. it will not go up 1.2ghz if there is no need to.
[Galaxy S I9000 Android Development] raspdeep:
it will not eat up a lot of battery, 0 0 is the same as stock voltage
[Galaxy S I9000 Android Development] raspdeep:
if you system cannot take UV, just set it to 0 0. Not all phones can take UV
[Galaxy S I9000 Android Development] raspdeep:
Yes, it is very simple, search for Supercurio thread with a template to do that easily.

I've no choice for BLN because it also requires an additional lib file for it to work and the easiest way is to go update.zip method. Dont hold your breathe tho, i still prefer Odin tar because its fast :D
[Galaxy S I9000 Android Development] AndyCr15:
If I use v4.1 does it come with a standard UV or do I have to install the tool and adjust myself?
[Galaxy S I9000 Android Development] raspdeep:
all future kernels will have user adjustable UV cos every phone reacts differently to different voltage levels
[Galaxy S I9000 Android Development] AndyCr15:
Ok... but... does this come with one already applied or just give me the option to do it myself?

If I have to do it myself, is there a guide anywhere?

Thanks.
[Galaxy S I9000 Android Development] raspdeep:
Read post #1, use Xan's app. You just have to test different levels yourself and see what works best on your phone. I would start off with UVLF 50 (affects 100-800mhz) and if it runs stable, move it lower or higher. UVHF affects 1ghz-1.2ghz so means when phone is under heavy load. If you face weird problems or hang/unstable, reduce the UV. 0 level means no undervolt which also means stock voltage level
[Galaxy S I9000 Android Development] AndyCr15:
Okay, thanks.

Might be worth expanding this a little?
[Galaxy S I9000 Android Development] raspdeep:
Which file did u download? The zip or the tar?
[Galaxy S I9000 Android Development] AndyCr15:
I flashed the zip.

I'm just saying, maybe add 'download this apk' and adjust voltages blah blah :)
[Galaxy S I9000 Android Development] zond:
Well, after having tried Tayutama ROM and getting the same results (turned off screen but working adb shell), I gave up using a custom ROM.

The original bloatware will have to do :D

But I installed this kernel anyway, and it seems to work perfectly fine, apart from one problem.

My phone is no longer detected by my linux box when I connect it with USB. And sometimes (for some reason, it seems to depend a bit on the USB cable used?) the phone doesn't even recognize that the USB plug is connected.

Any idea what could cause this?
[Galaxy S I9000 Android Development] dupel:
Thats voodoo issue, if im not mistaken.
[Galaxy S I9000 Android Development] zond:
Oh. Well, voodoo is still in beta 4 if I am not mistaken, so hopefully that will be fixed.

Do you think it will be possible to just flash this kernel again when it is updated with a voodoo version that solves this problem?
[Galaxy S I9000 Android Development] distortedloop:
Hi Andy, it actually already says that in the original post, but I agree, it's a bit buried in the fine print! (see my highlight/bold of OP below).

But it might be less difficult to miss if the link were also by the downloads.
[Galaxy S I9000 Android Development] AndyCr15:
Yeah, fair enough.

So, beta 3 seemed to have better battery life for me, although I didn't try the UV/OC version. Where can I download oc120_voodoo_b3.1? :)