yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] raspdeep:
i've uploaded b3.1 for those that want to revert
[Galaxy S I9000 Android Development] AndyCr15:
Would I be a massive pain in the bum if I asked if you might upload the update.zip version? :)
[Galaxy S I9000 Android Development] raspdeep:
b4.2 unloaded, see changelog
[Galaxy S I9000 Android Development] kalpik:
Thanks! No update.zip for b4.2?
[Galaxy S I9000 Android Development] zibiksior:
What version of BackLightNotification is in b4.2? Is it RC3?
[Galaxy S I9000 Android Development] kalpik:
Is there a way to apply the UV at boot?
[Galaxy S I9000 Android Development] raspdeep:
no.. tar using odin is fastest for flashing, i do not want to maintain many formats making it confusing

4.1 update.zip includes v4 patch from neldar source code, also includes change to a modded lib file, im not sure what that equates to so you may have to ask neldar in his thread. b4.2 only includes the source code so you already flash 4.1, the modded lib file will be unchanged

you are use init.d script.. put a script file in /system/etc/init.d and it will run. The command to echo the values are in post #1.. but please ensure the values are stable enough before putting into script as it will be a mess if you have values that keep crashing your phone on boot.
[Galaxy S I9000 Android Development] kalpik:
Ok, already flashed via odin and it works great!

This works great! May i know the command to also set the scheduler to noop?
[Galaxy S I9000 Android Development] zond:
So, how do I update to 4.2 properly? What I mean is, that lib file being unchanged is that important if I run that version of BLN? If so, how can I get there from 4.1 where the lib file IS changed?
[Galaxy S I9000 Android Development] miragebg:
Could someone explain me what exactly theese shedules mean/do?
[Galaxy S I9000 Android Development] dupel:
V4.2 only changed since 4.1 as shown in first post. Is there any mentions of changes for BLN? If not, than obviously it was unchanged.

In fact you dont even need to update to it if you don't use clockwork or debugging in voodoo.
[Galaxy S I9000 Android Development] xan:
Any example of init script? Because I cant get it workin... ;(

//edit: just figured this out. Added "su"

Created file /system/etc/init.d/S_UV.sh

#!/system/bin/sh
su
#Set scheduler for stl, bml and mmc

for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*
do
echo "noop" > $i/queue/scheduler
done
#set UV -25
echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV

chmod 777 S0.sh

Also, I wonder if is there a way to apply OC using init script? Dont like SetCPU/OC widget stuff...
[Galaxy S I9000 Android Development] miragebg:
Please, tell me which schedule is best from xan's VoltageApplication?
[Galaxy S I9000 Android Development] raspdeep:
which version are you using?

also can you do a ls -l /init.rc and tell me where init.rc points to?

it is by default min 100mhz, max 1.2ghz so you dont need setcpu or oc widget

most of the information you look for is at /sys/devices/system/cpu/cpu0/cpufreq/
[Galaxy S I9000 Android Development] raspdeep:
there is no best, its just different options for you to try and see which fit you most. i would go with stock cfq or anticipatory or noop. Noop claims to be best suited for devices that uses flash memory. try each one for a few days and see how each works for you
[Galaxy S I9000 Android Development] raspdeep:
maybe its time to update your app with "set on boot" option? :D
[Galaxy S I9000 Android Development] zond:
Yeah, I suppose first post shows how it changed - but look at my quote:

It makes me suspect that if I upgrade from 4.1 to 4.2 I will have a system that assumes that the lib file mentioned is NOT modded (since the 4.2 version does not have that lib modded) even if my system will actually HAVE it modded ("the modded lib file will be unchanged").

So, my question mostly is about whether this is a problem or not?
[Galaxy S I9000 Android Development] raspdeep:
no problem
[Galaxy S I9000 Android Development] xan:
#ls -l /init.rc
lrwxrwxrwx root root 2010-09-19 17:07 init.rc -> in
it-standard.rc

Anyway, above script I posted doestn work for me.

Certainly :)
[Galaxy S I9000 Android Development] dupel:
So, how about a kernel for the new NILFS2 mod? =)
[Galaxy S I9000 Android Development] MZWiZard:
+1 for "set on boot"
[Galaxy S I9000 Android Development] xan:
Well, if I could get a working script it will certainly speed things up :)

Got it :)
[Galaxy S I9000 Android Development] miragebg:
I just found out that my phone got freeze when browsed one scene in a movie, and did this several times. This is even on stock voltages, but OC'd to 1200. Is it possible that my phone cannot handle 1200MHz? Someone with the same problems? Can we increase a bit the voltage to get stable frequency at 1.2GHz?

Also what kind of scaling do you use in SetCPU- Conservative or Interactive?
[Galaxy S I9000 Android Development] xan:
About 1.2Ghz unstability - it is common.

Yes, I would love to see OV possibility, but currently it is not avaliable.

UV works only using Conservative scaling.
[Galaxy S I9000 Android Development] ufuuu:
With xan's app sure you can't increase the voltage; but you can try the script in the first post, I guess...

I'm currently using uvhf=-0mv, uvlf=-25mv with xan's app (thanks to him again, btw :)) and SetCpu with 100-800 mhz conservative scaling. (I think I had read a comment in this thread, previous pages that conservative scaling is best/stable for SGS) And 200-200 mhz performance scaling in screen off profile. I've been using this settings about 3 days and I have no problems ;)
[Galaxy S I9000 Android Development] ufuuu:
So, UV doesn't work while my phone's screen is off? Cuz I use performance scaling in screen off profile. When I tried 100-200 mhz and 200-200 mhz conservative scaling in screen off profile, my phone wasn't waking up again and I was needing restart my phone...
[Galaxy S I9000 Android Development] xan:
AFAIK it concerns only conservative, so answer is: it doesnt.

Try not to UV on LF too much, and it should be waking up ok. Too much UV on LF might be the reason of not waking up.
[Galaxy S I9000 Android Development] ufuuu:
Ok. thanks for your advice. And I've got a second question :)

Is 400mhz -25mV setting drains the battery faster or 200 mhz -0mV ?

Edit: And 3rd question :) Is there a way to make it concerns not only conservative, but also performance/or on demand?

Btw, my UVLF is just -25mV. It not quite UV, I think :)
[Galaxy S I9000 Android Development] Unhelpful:
So you use performance, which maintains the maximum allowed frequency, whenever the screen is off? What's your battery life like? ;)
[Galaxy S I9000 Android Development] miragebg:
Currently I am using JM7+ Voodoo b3 OC/UV 1.2 kernel. Do I have to remove the lagfix before upgrade to JM8 + Voodoo b4.2 OC 1.2 kernel or I can go forward and just flash it via Odin without removing of lagfix?

In case I have to remove the lagfix- if I understood correctly I have to create a folder /sdcard/voodoo and put inside an empty file "disable lagfix", is this right?
[Galaxy S I9000 Android Development] ufuuu:
I had set it 200-200 Mhz conservative on SetCPU screen off profile, but I had no wake up problem. So, I changed it to 200-200 Mhz performance, which maintains the -yes- maximum allowed frequency (200 Mhz) and my battery life details in attachment ;)

That is Turkish, but d is still day, h is still hours and min is still minutes :)
[Galaxy S I9000 Android Development] ufuuu:
I don't know about the first question actually,but If you are upgrading a new rom, you should better disable the lagfix. You can find some information on project-voodoo.org faq and documentation sections ;)

Your method is correct, and that doesn't actually removes the lagfix, just disables it. But in the case upgrading a new rom, that will be removed, of course :) You should check the official voodoo page mentioned above ;)
[Galaxy S I9000 Android Development] xan:
VoltageControl 1.5

VoltageControl 1.5

+ added possibility of saving and deleting of init script (/system/etc/init.d/S_volt_schedueler) This is quite dangerous! Currently you need to manually create /system/etc/init.d folder.

Its quite dirty atm, gotta spend some time rewriting code, add error handling and such.

Some confirmation dialogs are planned, because leaving it this way is too dangerous.
[Galaxy S I9000 Android Development] raspdeep:
be careful of the sign you put in if you are not using Xan's app. Positive numbers are for UV, negative numbers will OV and may potentially break your chip. The spec says max VddArm is 1.31v so use your own judgement.

The logic is VddArm = Stock voltage - UVLF/UVHF (depending on frequencies you are in) so as you can see postive UVLF/UVHF values will UV the chip but negative values will OV.

Until source code is out and since Froyo is just around the corner, the will probably be changes so no, wont do this until Froyo source is out.

Yes 400mhz will use more current compared to 200mhz. Currently only for conservative cos that is what most of us is running at. Besides when the phone is in sleep mode, it will be running at 100mhz 90% of the time so putting this mod in performance has very little advantage

It is advisable to disable lagfix and reenable it back because b3 and b4 has different format options. If you have already upgrade to b4 from b3 without disabling voodoo, you can still disable lagfix to convert to RFS and re-enable it back to reformat ext4 with b4 options

have you resolved why the script not running on your phone?
[Galaxy S I9000 Android Development] ufuuu:
Thanks for those important informations.

So, as I understand, setting 200-200Mhz with performance scaling is foolish. Since , even I do not create a screen off profile on SetCPU, 100-800Mhz with conservative scaling keeps the phone at 100 Mhz 90% of the time while screen is off. Am I right? Or do I still need to create a screen off profile on SetCPU?

And, why I get no wakeup problem with just 25mV UV and 200 Mhz conservative scaling? All because of that 25mV UV?
[Galaxy S I9000 Android Development] raspdeep:
you dont need to create off screen profile as scaling and UV takes care of it..

did you try set min and max at 200mhz in conservative? will you phone wake up with this? conservative will UV even when you set min and max at the same frequency which is similar to performance min and max at 200mhz.
[Galaxy S I9000 Android Development] dupel:
Actually its very useful. As when screen is off phone still continues to work e.g. sync, music player, background tasks. I usually set at 600, optimum for still working and waking up.
[Galaxy S I9000 Android Development] xan:
Yes, it I think adding "su" in the beginning made it work. Other possibility is "chmod 777" instead of "chmod 755".

I'm considering to allow some OV in VoltageControl...

Are you certainly sure passing negative values to sysctl increases the voltage?

I tried to pass all the way to -100, and no increases in stability @ 1,2. It might be my cpu is FUBAR, but it should react to increased voltage somehow.
[Galaxy S I9000 Android Development] st3chn0:
will this anytime be coming to froyo. froyo fast as it is, just want more speeeed :D
[Galaxy S I9000 Android Development] kalpik:
As soon as Samsung releases source for froyo kernel!
[Galaxy S I9000 Android Development] xan:
adb shell:

# echo -25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
echo -25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
# cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
0
#

Negatives don't seem to work, or I'm doing something wrong here.
[Galaxy S I9000 Android Development] miragebg:
Generally it's a great idea!! Keep going with your great work!

How do you test the stability of your CPU? Is your also unstable at 1.2GHz?
[Galaxy S I9000 Android Development] xan:
Yes, it is unstable. I'm trying to increase voltage, without success.
[Galaxy S I9000 Android Development] ufuuu:
Yeap I've tried it but when i set 200-200Mhz conservative, it wouldn't wake up again... And as you told me, it is unnecessary if phone runs at 100Mhz while the screen is off, in main profile (100-800Mhz conservative) or maybe a screen off profile could be set with 100-600 Mhz conservative as mentioned above, since phone would again runs at 100Mhz ;)

Btw thanks Xan for the boot option in his app, but it looks pretty dangereous to me since UV is still unstable, for me of course :)
[Galaxy S I9000 Android Development] raspdeep:
ok, sysfs doesnt seem to like negative numbers, i have another version and here is how it works

set values above 100 will OV (works for both UVLF and UVHF)..

so if you set 125 will OV to 25mV

i did not set any limits so dont blame me if u you set some insane voltage and cause your chip to break

I've also uploaded a debug version that you can see voltages, frequencies and UVs set in dmesg. Run the normal version when you see that things are working like it should from dmesg
[Galaxy S I9000 Android Development] AndyCr15:
Was there an OC/UV of the Voodoo Beta2? A few people are commenting that battery life from Beta 2 was much better, which I think is what I experienced too...

Could it please be posted? update.zip version if at all possible :)
[Galaxy S I9000 Android Development] dupel:
Battery life is absolutely the same for all versions and is pretty much the same as stock.

Use your device smartly, and it will live like 2 days.
[Galaxy S I9000 Android Development] AndyCr15:
Yes. Thanks. I know what I'm doing :p

I would like to try Beta 2 again, as I had much better battery life, I changed to B3 and it got worse... so I would like to try beta 2 again.

Yes, I was silly to delete it :(
[Galaxy S I9000 Android Development] MZWiZard:
Its working perfectly, thank you very much! :cool:
[Galaxy S I9000 Android Development] xan:
# echo 125 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
echo 125 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
# cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
4294967271
#

O_O
[Galaxy S I9000 Android Development] MZWiZard:
What!!??? :O
[Galaxy S I9000 Android Development] xan:
Also, according to dmesg, cpu doesnt go over 1000Mhz (i guess its just logging bug, it actually goes, since quadrant is over 1900)

[ 259.936346] regulator_set_voltage =1300mA @ 1000MHz UV=0

Is ur 'standard' kernel voltage @ 1Ghz and 1,2Ghz 1300mA? If it is, is it already OV?
[Galaxy S I9000 Android Development] cba1986:
The last kernel modified the color mod of voodoo 4?
[Galaxy S I9000 Android Development] dupel:
I'll try to guess and say you meant to ask if it includes voodoo color fix.

Answer is no.
[Galaxy S I9000 Android Development] dupel:
They cannot possibly be different on your battery life.

One of the betas (i think number 3) introduced bug with cpu (all the time set to 1000mhz) - that was the only kernel that had it. And only one that affected the battery life (and if you used setcpu, it didnt).

Beta 1, 2 and 4 do not differ in any way in their reading of fs (beta 4 has slightly different type of ext4, and it only affects the first boot). So no, they are all the same, and cannot possibly affect battery life differently.

So something else (worse signal, new widget, sync gone wrong, background app, bad version of application you use and any other factor) affects your battery. (though im 99% sure it was bug in beta 3).

What is more, even different file systems have so little difference in energy requirements that you will not be able to measure them in any way on your phone or laptop.

No offense, but clearly you don't know =)
[Galaxy S I9000 Android Development] AndyCr15:
Ha ha. What I don't understand is why you're arguing? Do you think I will now say 'Oh, ok, I'll leave it with terrible battery life'

Look through some threads, a variety of people have complained about battery life after 2 (in fact, thinking about it I got quite good life from B3, even though this CPU bug was found, it was Beta 4 it went bad).

I know what I'm doing with apps/widgets and other uses that effect battery life. When things go pear shaped, I try and roll things back to how they were when battery was good.

I also find, flashing the same kernel on different occasions will give different battery life. This cannot logically be explained, but happens...

I would also ask, if it simply changes file system, how did a bug get in there that held the CPU at 100%? Could it not be possible different versions have smaller, less noticeable bugs that cause battery to drain?

I am asking if previous versions can be available so the user has the option to try different things. If you really wish to keep arguing and telling me I don't know what I'm doing, have fun.
[Galaxy S I9000 Android Development] xan:
To round things nicely...

Beta 3 had "battery life" problem, it was due to typo in code. It made CPU to stick at max performance level. This got fixed in B4. (source -> #project-voodoo)

+1, correct thinking.

It can be explained. Flashing firmware/kernel in "normal way" should be done only @ 100% battery. There is lot to explain about that, but in short:

There is a battery voltage sensor controlling charging and obtaining data for % of remaining battery calculation (doh!). It is calibrated to show 100% around ~4,235V, since its Li-Polymer battery.

When you flash a kernel, and leave cable plugged in during early startup of the device (bootloader) calculations get screwed. I dont know why, but they do. I did several kernel flashes, everytime battery life decreased.

The symptom of this is:

1) I turn off the device @ 42% battery to get it flashed

2) Flash and leave USB plugged during first startup -> battery meter shows 66%

There is NO WAY battery got charged 24% during 30sec flash. This is definately wrong reading! After that you got battery life reduced, until u do one or more 0-100% cycles.

The sensor doesnt know about real max and min battery voltages, because it is deceived at this first boot.

There are two ways of preventing such situation (one safe, second - tricky)

1) Safe - Flash kernel/firmware @ 100% battery

2) Tricky - Plug out USB cord JUST AFTER flashing. Its the time when SGS screen goes dark, and Odin shows RESET. After that you will still have correct battery reading.

Voodoo is not just about changes in file system, there are many procedures made for installation, creation, handling and uninstallation of lagfix. One of earlier betas consisted of 300+ lines of added code.

Will do :) Seriously, previous versions are obsolete and will not be supported (I think Curio's answer would be the same).
[Galaxy S I9000 Android Development] miragebg:
Why SetCPU never shows 1200MHz when I do stress test, but only reaches 1000MHz?

I have to set both max and min sliders to 1200 to make it working..

What shedules do you use in VoltageControl?
[Galaxy S I9000 Android Development] supercurio:
AndyCr15, don't belive what you read. If you search an issue, you have 99% of chances to find it in forum comments.

Any issue, even if it has only beed only a rumor.

That's the buzzing effect of forums.

My recommendation is to use it. If you find an outstanding issue, try to replicate it and send me message, so i will have a chance to correct it ^^

Trust me, you really need to build your own opinion on this one.
[Galaxy S I9000 Android Development] xan:
Well, about schedulers -> they dont make much a difference, as far I tested.
[Galaxy S I9000 Android Development] huxflux2003:
hello guys

I have JM8+vodoo beta 4.

How can I try this kernel? Do I need to remove voodoo first and revert to a stock kernel? I am sorry if this has be answered again, but its late and I want it now!!!

thanks!
[Galaxy S I9000 Android Development] xan:
Just flash.
[Galaxy S I9000 Android Development] cba1986:
What i tried to say is that if you have the original voodoo beta 4 and you applied the OC kernel based on voodoo, will this remove the color fix?
[Galaxy S I9000 Android Development] raspdeep:
it is not a logging bug, the log that display this only happens if previous voltage and new voltage are different.. so after adjustment if Vddarm is same for 1ghz and 1.2ghz, it wont set new voltage because voltage are same previously hence no log. however, you should be able to see p_lvl which indicates index of the frequencies jumped or set the min and max to 1ghz - 1.2ghz and do some load and u see it jump

yes stock are 1.3mA iirc
[Galaxy S I9000 Android Development] raspdeep:
yes (10 char)
[Galaxy S I9000 Android Development] raspdeep:
looks like a 32-bit negative representation of -25
[Galaxy S I9000 Android Development] kalpik:
Okay, I have a weird problem.. This is what I did:

1. Flashed JM8, selected language.

2. Flashed Tayutama, booted up fine.

3. Flashed ocb4.2 kernel from here, and I had the disable lagfix folder in voodoo.

Expected result: Phone would boot without converting to EXT4.

Actual result: Phone is stuch at the Galaxy S logo.

Any ideas?
[Galaxy S I9000 Android Development] cba1986:
Thanks for the info.
[Galaxy S I9000 Android Development] raspdeep:
you should use tayutama's ROM with voodoo support because i think he incorporates some stuff in init.d for first time boot.

if you dont care about those, you can do adb shell:

rm -r /dbdata/databases

that should reset all your settings and booting will take a little longer.

btw, it should be /sdcard/Voodoo/disable-lagfix, notice Voodoo with cap V
[Galaxy S I9000 Android Development] kalpik:
Ok, actually, after a while I restarted the phone, and it booted up right!

And yes, I mean "Voodoo" only, with a capital "V" :)
[Galaxy S I9000 Android Development] raspdeep:
you should use beta4
[Galaxy S I9000 Android Development] Tayutama:
My init.d scripts aren't really doing anything that should make it hang...

I got the following in init.d on first boot:

Wipe Battery Stats.

Wipe Dalvik Cache

Copy Apps to /data/app

Zipalign check

All except Zipalign check is removed after it's done so... yeah
[Galaxy S I9000 Android Development] kalpik:
I still have the following in init.d (and yes, I flashed YOUR integrated package from scratch)

01sysctl

69data2app

70zipalign

99complete

You integrated package did boot alright, but yes, if i flash only your rom and flash kernel from here, it definitely hangs on first boot. Confirmed twice.
[Galaxy S I9000 Android Development] Tayutama:
Hmm though i hadn't made data2app stay before next version... but anyway it shouldn't do anything after first boot...

Btw can you supply a logcat after when it hangs?
[Galaxy S I9000 Android Development] raspdeep:
hmm, maybe thats why it hang on first boot?
[Galaxy S I9000 Android Development] xedamen:
Sorry, bad topic
[Galaxy S I9000 Android Development] android53:
I got bored and tried your new v1.1

IT WORKS! good job!

around 10mflops in linpack

Shame that the lag on wakeup is still there in your kernel though, makes it kinda useless, you and setenza01 really need to find out why your kernels cause this.

Setting setcpu to ondemand does nothing to help it.

Linpack: 10mflops

Quadrant: 2,000 (the 3d and 2d tests see a nice improvement on fps too)

Will do some stability and heat testing now
[Galaxy S I9000 Android Development] android53:
Funny thing, 20% more cpu performance barely speeds up psx4droid if at all. Must really need some coding optimizations.

Ohh well it has only just been released...
[Galaxy S I9000 Android Development] android53:
1.2ghz

seems perfectly stable on my phone.

Ran psx4droid for about 30 mins, then setcpu stress test for 30 mins or so.

Max 50 Celsius cpu temp (while charging, 45 ish normally), no crashes or errors

I wonder what we can push these phones up to
[Galaxy S I9000 Android Development] xedamen:
Does it work with JM5?
[Galaxy S I9000 Android Development] DocRambone:
Yes, got 2120 on quadrant :D
[Galaxy S I9000 Android Development] android53:
After some testing:

1.2 ghz completely stable on my phone

Bugs:

1.Wake up delay like samset kernel

2.terrible sound glitch when touching the screen playing music with headphones on, try it
[Galaxy S I9000 Android Development] android53:
It

Yeah I saw 2100 on one run