yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mbriody:
I have the WiFi issue (it won't turn off) and have just upgraded the standalone version 3. Hoping this might fix it.

As this fix is based on changing the file system and should therefore be a static process is there any reason why things like WiFi settings and clock speeds should have to be touched by it?

If not then it would be nice to get a "lite" version which just did the file system change and nothing else.

Nope, WiFi still turning itself on after I turn it off :-(

I was on beta 2 and a couple of nights ago I went to bed with about 90% charge and woke up to the phone completely dead and turned off. I'm guessing this was now the cause.

Any easier way to apply the WiFi fix than than using ADB etc? I don't have any of that stuff installed though the phone is rooted.
[Galaxy S I9000 Android Development] kenkiller:
wasn't it established that the wifi not going to sleep didn't have anything to do with voodoo kernel? It's a firmware issue.
[Galaxy S I9000 Android Development] ewok666:
It does turn off after about 15 minutes which seems to be the default with newer firmwares (if not all firmwares). There is a setting (wifi_idle_ms) under gservices in the /dbdata/databases/com.android.providers.settings/settings.db database that can change this.

I've set mine to 15 seconds (15000 as the value is in ms) and it works just fine.
[Galaxy S I9000 Android Development] mbriody:
I am on stock firmware and had no WiFi or battery issues before this fix.
[Galaxy S I9000 Android Development] mbriody:
Mine turns itself back on every couple of minutes.
[Galaxy S I9000 Android Development] jana999:
+1 Thx a bunch bro! This is seriously the first time I'm hearing of this:eek::eek: Its a great trick!
[Galaxy S I9000 Android Development] AndyCr15:
I appear to be having battery issues with Beta 4 too. Has this been 'proved' as such? Is it a known problem?

I ask, because if it is, then a fix might be in the works...

With Beta 3 my battery life (although people talked of it being 100% CPU) was the best I've had.
[Galaxy S I9000 Android Development] Davith:
How bad are your battery issues?
[Galaxy S I9000 Android Development] AndyCr15:
To be fair, it's hard for me to tell. I usually judge either overnight drain or while I'm at work. I've had a few days off, so can't judge that way. Overnight it dropped about 50%!!! but then I think an automatic backup app had kept the device awake (maybe even screen on) so I'm not sure there.

HTC event day, it dropped 70% in about 7 hours, but then it was used quite a bit, tethering and such.

So, I can't be sure, but with Beta 3 I was down to about 3-4% an hour, which was the best I'd had with the SGS.
[Galaxy S I9000 Android Development] Legolas_85:
I've flashed the stock rom JM8 and then applied the update.zip voodoo lagfix only v3.0, without installing anything else, but my battery life suck. I left the phone on the entire night, offline mode, to use the alarm, but this morning I found it off and I was not able to turn on the phone cause the battery was completely without power.

I tried with both the beta4 lagfix including voodoo color fix and the lagfix only version, with three different stock rom, JM8, JF7, JM5 but the results were always the same. So it's useless for me. Does anyone alse have the same problem?

Thank you!
[Galaxy S I9000 Android Development] AndyCr15:
Maybe try beta 3? I'm thinking of rolling back...
[Galaxy S I9000 Android Development] Legolas_85:
Where do i can get the older version?
[Galaxy S I9000 Android Development] Frederic1968:
I had also the Wifi issue but I had it also before installing Voodoo. In my case it was Fringe that prevented my wifi to go in standbye. After uninstalling Fringe, the issue disappeared.
[Galaxy S I9000 Android Development] AndyCr15:
Hmm, I thought I had it, but I can't find it now. Here's the overclocked version of beta 3 -

http://hemorrdroids.net/files/oc120_voodoo_b3.tar

Anyone have the regular version?
[Galaxy S I9000 Android Development] Legolas_85:
uhm... I think I'll wait before installing this fix. Maybe with the next version these problems will be fixed. Thank you anyway!
[Galaxy S I9000 Android Development] raspdeep:
The OC version of beta3 already has that problem fixed:

oc120_voodoo_b3

- remove performance governor from startup cos i9000 dont need that

- added init.d support
[Galaxy S I9000 Android Development] yc1437:
Hi I had the color fix, how to inside it without reflash the rom?
[Galaxy S I9000 Android Development] Davith:
I lost 70% overnight as well but I have no idea if it is because of the voodoo lagfix. It turned off before I could check Spare Parts.

Currently using beta4 without the color fix with JM8.
[Galaxy S I9000 Android Development] aideno:
I have a query about the logfile simply called Voodoo in /sdcard.

It prevents me creating a directory to do a disable lagfix. Is the file able to be moved/renamed/deleted safely?
[Galaxy S I9000 Android Development] Onraad:
I'm also experiencing quite a big battery drain. In about 3 hours I lost 12% in standby. I'm using JM8+Tatuyama+beta4 with color fix.
[Galaxy S I9000 Android Development] Bhonka:
my data connection keeps dropping off and i have to go into flight mode and back out to get it going again.
[Galaxy S I9000 Android Development] bub181:
I found the battery drain to be higher in beta 4 too. I went back to beta 2 and it seems to be back to normal now. I noticed that the idle CPU usage was higher in beta 4.
[Galaxy S I9000 Android Development] dagrim1:
Can you just flash back to the beta2 (from beta4) using odin without any additional steps?
[Galaxy S I9000 Android Development] Onraad:
I think so. I upgraded from beta3 to beta4 using the update.zip method without any additional steps. It's working but I don't like my battterylife now :(
[Galaxy S I9000 Android Development] Davith:
Looks like it's settled a bit for me, no more crazy battery draining.

I've been losing 1% only in the last hour.
[Galaxy S I9000 Android Development] tomthetank:
Is there a link for the update.zip file for the beta 2 file? I think my battery has got worse with beta 4:-(
[Galaxy S I9000 Android Development] tjkk:
Im also experiencing severe battery draining. The phone is completely stock JM1 and all i've done is installed voodoo beta4 using update.zip. Before installing the lagfix my battery lasted almost 2 days. Now im lucky if it lasts 10 hours. Before the fix the battery drained about 5% during night. Now it drains 40%. Android Os seems to be taking much more power than before (now 27%).

The worrying thing is that even though i disabled the lagfix the battery draining still remains. I dont have the 3 button recovery/download working so im hesitant to use odin to flash back to the stock kernel. Is there a safe way to get completely rid of the fix?

The problem started right after i installed voodoo and i haven't installed anything new on the phone afterwards so i cant think of anything else that could be causing this.

Other than this problem the lagfix has been working well and the phone feels fast.
[Galaxy S I9000 Android Development] iammichel:
I guess that the battery drain problems are caused by some incompatibility or interference with other software or firmware, because I've been running beta 4 on my xwjg5 for a few days now and overnight I have maximum 1% battery loss...

No battery issues whatsoever for me.
[Galaxy S I9000 Android Development] Davith:
Draining is starting again. It's dropping by 1% every few minutes or so.

The phone also feels a little warm on the upper part of the device, so there's definitely something going on.

It's a bit worrying that disabling the lagfix doesn't stop battery draining. I'm hoping Curio will be able to work out something quickly because I really like this fix. Makes the phone very very fast.
[Galaxy S I9000 Android Development] bilboa1:
i lose approx %30-40% per day with low usage (HSDPA + Wifi on)

samsung claims 576h of standby (24 days) but I suppose thats with network off :s
[Galaxy S I9000 Android Development] RyanZA:
The lagfix (using EXT4 instead of RFS) has nothing to do with the battery. So disabling the lagfix won't affect battery draining, if there is any. You'd have to flash another kernel.

Personally, I've had battery issues with every custom kernel based on the Samsung source, compared to the Samsung stock kernels. I believe the GPLed drivers are not the same as the drivers inside the stock kernels (especially wifi). The kernel binary is definitely very different between a custom compiled kernel and a Samsung compiled kernel.
[Galaxy S I9000 Android Development] bajica:
Im on JM8 tayutama with voodoo b4 and my battery is fine, no problems for me, tnx curio

Sent from my spaceship
[Galaxy S I9000 Android Development] Onraad:
So you used Tayutama's latest ROM with voodoo b4 included? If so I will give that a try cause I'm using V1 and flashed voodoo b4 myself after that..
[Galaxy S I9000 Android Development] Davith:
Installing the voodoo lagfix definitely has something to do with my battery draining though. Android OS has been constantly increasing for an hour and a half now and the phone feels warm. During that time, I've been losing around 20 %.

When going in Spare Parts in 'Other usage', 'Execution' has been going up as well. Usually, it would go to sleep.

I've never had these issues before since I was using another lagfix.
[Galaxy S I9000 Android Development] RyanZA:
You misunderstood what I said, I think. Voodoo consists of a custom kernel. The custom kernel will replace your RFS with EXT4 on boot if the Voodoo /sdcard file isn't there. If the file is there, it will convert the RFS back to EXT4. So even if you disable the voodoo lagfix using the file, the voodoo kernel is still running. If there are battery issues inside custom kernels, then using RFS or EXT4 with or without voodoo enabled won't affect the battery issues.

Make sense? :D

That said - I get the same issues when I use a custom kernel myself. Others seem to have no battery issues at all with custom kernels, or at least they say they don't. It might be hardware dependent (different revisions of the handset may work better or worse with the GPLed drivers? I have no idea.)
[Galaxy S I9000 Android Development] ashwinds:
I agree there is something fishy about wifi - the only time i've got good battery is when I disable wifi or if i set to sleep in 3sec on screen off.

PS: having said that, I must also add once I set 3 seconds the battery life is good as ever.
[Galaxy S I9000 Android Development] Stefanauss:
Size-wise? Or what else?

Could it be that custom kernels are not given properly optimized compilation flags/options? (I'm just guessing, i compiled custom linux kernels for my pc a couple of times and flags/compile options definitely make a difference)
[Galaxy S I9000 Android Development] kindaichi24:
im on jm7 tatuyuma rom. no prob with battery. off 3g everything go slp for 10 hours. wake up still literally 100 percent. :)
[Galaxy S I9000 Android Development] kevo:
I havent used Voodoo before. I'm on an i9000, stock JF3 with root.

Voice prompts all went ok, started to boot up but just sticks at a blanck screen. If I press the capacitive buttons they light up, but nothing on the screen.

abd cant see the phone.

Trying odin now to try and revive it.

Any tips?!?!?!
[Galaxy S I9000 Android Development] kevo:
odin didnt make any difference.

Is there anyway I can get access to the internal SD card from this point?
[Galaxy S I9000 Android Development] vM00:
Clockworkmod

@supercurio:

Have you found a solution for Clockworkmod yet?

I've looked at this problem and it seems the problem is in the killrecovery.sh script that CWM uses, more specific here :

if [ -f /init.smdkc110.rc ]

then

/sbin/recovery &

fi

Since init.smdkc110.rc insn't there any more...CWM hangs. I've tested and repacked your kernel with smdkc110.rc and smdkc110.sh included and voila CWM works again :) This with and without your lagfix. Will do some more testing and report back later.
[Galaxy S I9000 Android Development] Mull1s:
Incase i want to go back to my stock kernel, not saying im going to because my phone flies right now :)

After disabling the lagfix do i need to flash another kernel using odin (if this is the case, where do i get the JM1 kernel?) or do i get it back by doing a wipe?

thanks in advance :)
[Galaxy S I9000 Android Development] Quiksilver78:
Damn I guess I should have read this thread before attempting this, but I started encountering FCs after messing around with Titanium Backup and after installing Voodoo Beta 3.

I reflashed the firmware using JM8 (I was using JM7; figured, what the hell if I am going to flash again, I may as well upgrade) and now the phone won't display anything.

I get to the Samsung S splash screen, hear the default startup sound and then the screen goes black. No vibration, no lights on the touch keys, nothing.

I can still get into Download Mode and/or Recovery Mode but unfortunately ADB won't detect the phone and neither does Windows so I could perhaps try to go in to disable the lagfix and flash again.

Does anyone here have any ideas to get my phone back up and running?

PLEASE! :D
[Galaxy S I9000 Android Development] supercurio:
Sure !

At each conversion process, RFS to Ext4 - Ext4 to RFS.

You know that each time you hear the scary voice ;) battery stats are wiped too.

This was done to prevent false reports after Odin flashs, and it seems it worked !
[Galaxy S I9000 Android Development] Stefanauss:
Thanks for the answer. =D

After 3-4 days with Voodoo + Color, it seems indeed that battery life is unaffected. Changed ROM at the same time though, so i'll probably uninstall it and do a comparison.

On this related subject Curio, another question.

Is it correct to reflash the original kernel backup back with:

# redbend_ua restore bml7-zImage-kernel-backup.img /dev/block/bml7

?

After disabling lagfix of course.
[Galaxy S I9000 Android Development] supercurio:
Absolulty, as long as your previous kernel was stock, you'll have your previous kernel back.

Be super cautious with this command. If you make a mistake in the command line you can brick you phone for good

:)
[Galaxy S I9000 Android Development] Quiksilver78:
So with this idea, am I correct in assuming that I can reflash JM7 (the firmware I used with flash Beta3) and my phone will work again?

As I said earlier, as long as I was flashing, I figured I may as well 'upgrade' to JM8 and I got a black screen (despite Odin saying "PASS")
[Galaxy S I9000 Android Development] leoon:
Well after few days with the beta #3 I noticed some slow downs,

At the end I removed it and returned to AutoKiller with strict rules and its like faster than voodoo fix,

Maybe because I install A LOT of apps it become slow after few days but I dunno
[Galaxy S I9000 Android Development] yc1437:
Hi how to remove the color fix without reflash?
[Galaxy S I9000 Android Development] kalpik:
Just install the lagfix only kernel :)
[Galaxy S I9000 Android Development] yc1437:
I already have the lagfix + color fix, so I reflash the lagfix only will do?
[Galaxy S I9000 Android Development] kalpik:
Yes.

10char
[Galaxy S I9000 Android Development] sturmeh:
I just got my new phone, which seems to have a different colour tone to my previous phone, and when I installed voodoo, it maintained this however in the 100% and the 0% brightness settings instead of 'correcting' the colour it jumps to warm colours.

Will you be adding some sort of calibration settings to let users choose the white balance?
[Galaxy S I9000 Android Development] mbriody:
Exactly what happened to me. I'm on the stock JF3 ROM, never changed it. I'm going to uninstall until the issue is identifed and fixed.
[Galaxy S I9000 Android Development] raspdeep:
CWM works even with ext4 voodoo. Only caveat is CWM will unmount /data after nandroid backup and you will not be able to remount /data in ext4 until you reboot back to recovery. Also, do not unmount /data unless you dont need to remount /data in ext4

i've added CWM support back in my oc kernel
[Galaxy S I9000 Android Development] supercurio:
There is a problem with this approach, this is why I let CWM disabled.

CWM Recovery is working 100% in RFS mode, this is why i re-enabled it when you're in RFS.

But in Ext4, there are issues and a program that has the ability to read, write and delete every data in your phone has to be 100% reliable and not sometimes let you with a broken phone.

This is part of the quality control present in Voodoo which make it a solution people can trust.

I talked with Koush on IRC yesterday and he is working on a new Voodoo-Ext4-aware CWM Recovery version.
[Galaxy S I9000 Android Development] supercurio:
Seems like you didn't read the doc ^^

2 solutions :

- Wipe /data in recovery (recommanded)

- Flash Voodoo with odin (since you ****ed up your /data and /dbdata with Titanium previously, i don't recommend this option)
[Galaxy S I9000 Android Development] supercurio:
raspdeep, I strongly discourage enabling CWM with Ext4 mode until CWM is fixed and work reliably with Ext4.

Because you know, you better have a software that don't start than a software that looks like working, but when you need to restore your data bang! half of it is restored and you have no solution knowing why. So You're pissed, loose your time and you have good reasons to.
[Galaxy S I9000 Android Development] Quiksilver78:
LOL thanks for the reply.

I reflashed with JM7 and everything is working fine. I still'd like to try the JM8 firmware, but how do I know if Voodoo has been disabled?

I created a folder called "disable lagfix" inside the already-existing "Voodoo" folder but like I said, how do I know that it has been disabled? I read the log files and makes no mention of anything for Sep 18th.

Any help?
[Galaxy S I9000 Android Development] Davith:
Lucky you. :(

I don't know what can be wrong with some of us. I did a fresh wipe and everything before flashing Voodoo (without color fix).

Mine turned off again this night with 40% left. Android OS was the culprit again I guess.
[Galaxy S I9000 Android Development] yc1437:
It works thanks!
[Galaxy S I9000 Android Development] NetCopAD:
This battery problem with Android OS happens to me also, but it is random and I can not reproduce it. A couple of restarts and it's back to normal. Another restart and it's bad again. But I'm pretty sure it has something to do with the Voodoo kernel. Never had this issue before.

I'm on JM1 official and Voodoo beta 4.

Another strange battery problem I sometimes have (also as random as this one) is my cell standby shows 50% no signal when my signal is 100% OK and the funny thing is that cell standby time on is double the time the phone was switched on. So for example it has been 5 hours since I last unplugged the charger, but the Cell standby time shows 10 hours and it shows 50% no signal and the battery usage is more than the normal. This one is also solved randomly by restart or by turning the radio off-on a couple of times.

EDIT: This second issue has nothing to do with Voodoo. I just mention it now that we are talking about battery issues.
[Galaxy S I9000 Android Development] Davith:
Yeah it definitely is random. A reboot and draining is gone, but it comes back eventually.

I guess there's some form of incompatibily with some devices.
[Galaxy S I9000 Android Development] teletin_andrei:
Curio!!! Absolutely no lag! U r the best! :) Jm8+voodoo 3
[Galaxy S I9000 Android Development] FadeFx:
nice to hear koush is working on sgs clockwork recovery again, hope he will fix some of the other issues also...
[Galaxy S I9000 Android Development] supercurio:
We couldn't finish our discussion yesterday, he disappears suddenly.

Once you can reach him he is alright ! but it's obvious that he has many concurrent projects and few time to work on it.

That's why i asked him to free ClockWorkMod recovery... I'm sure that in his position, maintaining recovery for every phone/model/variant is boring as hell.

..But it's an exiting task for people who are specialized in this model.

I hope he will consider it.
[Galaxy S I9000 Android Development] M3xital:
Just applied Voodoo lag fix without problems, the only thing i have noticed is that I can't connect with Kies to my PC anymore.
[Galaxy S I9000 Android Development] Stefanauss:
Curio, i did this for the first time just now.

Connected to SGS with adb under Linux.

My SGS rebooted automatically and it seems to work normally.

But i wonder, could you explain what that "fail!" is and if i should be worried about it?

Thanks a lot.

JUST NOTICED: it didn't flash my original kernel back. It's still Voodoo.

I post my mount, just in case:

rootfs / rootfs ro 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Galaxy S I9000 Android Development] supercurio:
@Stefanauss you need redbend_ua binary provided in update.zip.

Some other version don't accept command line arguments, like you experienced.
[Galaxy S I9000 Android Development] supercurio:
Does is work if you disable-lagfix ?
[Galaxy S I9000 Android Development] erunamor:
That has happen randomly to me, too. And I don´t have (and never had for the moment) installed voodoo lag fix. So I wouldn´t be so sure what the problem is. I think the problem is in the firmware or in the android itself.
[Galaxy S I9000 Android Development] Stefanauss:
If i read correctly through updater-script in update.zip, the redbend_ua included is a one-off, it is extracted, set on permissions and just used for the flash but it is not flashed into the system, is that right?

If so, how could i manage to get it run into the phone? Just replacing? Or is it possible to use it through adb?
[Galaxy S I9000 Android Development] Davith:
I never had this issue before though. I'll try flashing again tomorrow, without the lagfix and with exactly the same apps.

That way I'll know if Voodoo (most likely the custom kernel) has something to do with my draining issue.
[Galaxy S I9000 Android Development] krille85:
I just want to check if I understood this right. If I create a folder named disable-lagfix in the voodoo folder and then reboot, is it then safe to flash the official froyo thru kies when that glorious day comes ?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Stefanauss:
It's "disable lagfix", with a space.

Then yes, a complete reboot and it is safe (as flashing a firmware can be..)
[Galaxy S I9000 Android Development] supercurio:
Yes i use it through adb to install kernels, and do that extremely often ^^ (not failed once)
[Galaxy S I9000 Android Development] supercurio:
Yes :)

hopefully Froyo build will be worth it ^^ and come with sources !!
[Galaxy S I9000 Android Development] M3xital:
I've just disabled the lag fix, and still can't connect with Kies.

Just notice also that the Kernel didn't change back to my original, it's showing this on Kernel info " 2.6.29 curio@carton #666"
[Galaxy S I9000 Android Development] krille85:
Yepp. But I have to say that since your great fix froyo isn't as urgent, big thanx!

Sent from my GT-I9000
[Galaxy S I9000 Android Development] oskariunit:
Feels snappy and flashed without probs, thanks!