yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] °Dexter°:
Thanks Ryanza,i know i shouldn't have done this,but i wasn't complaining about "professionals' " work...i came here just to gather information about future uninstall (i read many posts of "uninstalling problems",but maybe they are captivate users)

Thanks a lot,anyway
[Galaxy S I9000 Android Development] RyanZA:
EDIT: Changed my mind. :D

If you can get hold of the beta kernel, then good luck testing it! Just be careful! :)
[Galaxy S I9000 Android Development] tomthetank:
anyone know how long this is away from being released? like full version for everyone :)
[Galaxy S I9000 Android Development] lokhor:
So how do we sign up to the beta of this?
[Galaxy S I9000 Android Development] Treggs:
I tried voodoo this morning and I was getting the wireless problem i.e. it doesn't sleep when the screen is off regardless of wireless sleep policy.

I uninstalled it using the blank file thing and reflashed with JG4 (Australian Optus standard firmware) but this hasn't fixed the problem. Any idea's?
[Galaxy S I9000 Android Development] Bajo76:
No problems here with WiFi, using jm7 and voodoo b1
[Galaxy S I9000 Android Development] Treggs:
What install method did you use? I'm wondering if it makes a difference. I flashed using odin but I'm currently trying an install and uninstall using the APK method
[Galaxy S I9000 Android Development] Bajo76:
1. Flaseh 512pit with repartition untill success apeared

2. Flashed jm7 and modem jm3 without repartition

3. Went to recovery did facrory reset anf wiped cache

4. Flasehed voodoo with odin
[Galaxy S I9000 Android Development] Treggs:
I didn't use a pit. That might be the problem. Will give it a try.

Edit: Nope that didn't work...
[Galaxy S I9000 Android Development] MiMikri:
Same here, no Problems with jm7.

512.pit, no repartition cause coming from Richthofen w..6 firmware. ...

flash jm7,jm3,dbt-csc.

Some days later flashed vooodoo b1.

No wipe or reset.....work flawlessly.

only one time fault..... had to switch away from kies to something other in USB-Settings and back to kies to use with PC.

There must be an internal bit set to indicate that usb debug is enabled.

Greetings

MiMi
[Galaxy S I9000 Android Development] chrissyg123:
so is there definitely no workaround for beta1 re: the wifi problem?

it's the only issue i've found with it! i'm even going to leave the lagfix on and just get into the habit of disabling wifi with a widget now, the lagfix is THAT good..
[Galaxy S I9000 Android Development] RyanZA:
Gotta say, it's almost impossible for this lagfix/kernel to cause your wifi to not switch off after removing the kernel.

When you remove the kernel - it's gone. You are probably just being confused by regular behavior for the wifi, which takes a minute or so to turn off after you turn off the phone.

It might be possible that the kernel is actively changing a setting on install, but I don't think it does this.
[Galaxy S I9000 Android Development] raspdeep:
the wifi problem has nothing to do with voodoo kernel. stock jg4 firmware has never been able to sleep the wifi when screen off.. this was tested way back before there were custom kernels.. so i suggest u look for newer firmware with the wireless problem fixed like what others suggested (tho, i've not tested the the jm7 firmware)
[Galaxy S I9000 Android Development] lpy:
Just to clarify, how can you check for sure that the kernel is removed and no longer has any effect on the phone?
[Galaxy S I9000 Android Development] Treggs:
I've tried numerous other kernels since this popped up and none of them are sleeping. JG4 wireless sleep was working on my phone prior to the voodoo install.

I know it doesn't make sense but it's happening.
[Galaxy S I9000 Android Development] raspdeep:
settings->about phone->kernel version.. if you see something with SE, its stock samsung kernel
[Galaxy S I9000 Android Development] lpy:
Ok, yep that's what I got.

Agreed with Treggs, I know it doesn't make sense, since the kernel is removed.
[Galaxy S I9000 Android Development] RyanZA:
Well... my wifi isn't sleeping, but I have the custom kernel installed. Battery usage has also been higher than with the Samsung kernel.

I'm 99% sure that changing the kernel must revert it back to normal though. I'll test it out later when I have time. If it doesn't, then that is one freaky bug. :D Doesn't seem possible to me, since replacing the kernel should remove all traces of it.
[Galaxy S I9000 Android Development] raspdeep:
maybe u can try create a thread for those jg4 firmware users that has not installed any custom kernel and ask them to give you feedback. all singapore phones are jg4 stock..
[Galaxy S I9000 Android Development] RyanZA:
09-04 09:42:25.412: DEBUG/WifiService(2337): ACTION_SCREEN_OFF

09-04 09:42:25.442: DEBUG/WifiService(2337): setting ACTION_DEVICE_IDLE timer for 900000ms

May have something to do with this? 900000ms is 15 minutes. I'm going to leave the phone off for 15 mins and see if the wifi goes off by itself...
[Galaxy S I9000 Android Development] Treggs:
Any chance you could try the uninstall and see if it corrects? I'm 99% positive you are a better Android hacker than me lol
[Galaxy S I9000 Android Development] RyanZA:
Alright, wifi does turn off after 15 minutes of the screen being off, even with the kernel installed.

I don't remember if it was always 15 minutes though. If someone who still has a stock phone could follow these steps:

1. Connect your phone to logcat in some way

2. Turn off the screen

3. You should see something like this in logcat:

09-04 09:42:25.442: DEBUG/WifiService(2337): setting ACTION_DEVICE_IDLE timer for 900000ms

Report back if the value is also 900000ms

Thanks in advance! :)
[Galaxy S I9000 Android Development] lpy:
I remember when my phone was stock, the Wifi sleep was almost instant. I could hit the power button to shut off the screen, then a few seconds later I'd hit the middle button, the screen would wake, and 3G would be showing. Then a couple of seconds later the Wifi would replace the 3G.

Thank you very much RyanZA for taking a look into this. Hopefully we can get to the bottom of it.
[Galaxy S I9000 Android Development] Treggs:
See I was right, you are a better Android hacker than me :D

I have no idea what logcat is but if the time out value is different to a standard kernel, can it be changed? and is it possible for this setting to be retained after flashing and system resets? if so then it probably explains what is happening.
[Galaxy S I9000 Android Development] RyanZA:
Almost guaranteed it can be changed. (Since I'm guessing voodoo kernel has changed it. ;) )

I'm guessing the kernel is writing the value to disk somewhere. It might not actually be voodoo either, it could maybe be JPC or some firmware we have tried. ;)
[Galaxy S I9000 Android Development] RyanZA:
Boom! long idleMillis = Settings.Gservices.getLong(mContext.getContentResolver(),

Settings.Gservices.WIFI_IDLE_MS, DEFAULT_IDLE_MILLIS);

inside http://www.netmite.com/android/mydr...ices/java/com/android/server/WifiService.java

Okay, so it looks like the default value for android is DEFAULT_IDLE_MILLIS = 15 * 60 * 1000; /* 15 minutes */

However, if 'Settings.Gservices.WIFI_IDLE_MS' is set, it will use that value instead. Default value for the SGS for that appears to be 30000 ms, or 30 seconds. Anybody have any idea how to change Settings.Gservices.WIFI_IDLE_MS?
[Galaxy S I9000 Android Development] fane1:
jm7 with voodoo fix and i confirm that its 15 minutes here.Is there a way to get this time shorter like 1 minute? It would be great thank you
[Galaxy S I9000 Android Development] RyanZA:
Man, I love this stuff

// we used to go to sleep immediately, but this caused some race conditions
// we don't have time to track down for this release. Delay instead, but not
// as long as we would if connected (below)
// TODO - fix the race conditions and switch back to the immediate turn-off
long triggerTime = System.currentTimeMillis() + (2*60*1000); // 2 min

Haha!

And this one:

if (mScreenOff && shouldWifiStayAwake(stayAwakeConditions, mPluggedType) &&
!shouldWifiStayAwake(stayAwakeConditions, pluggedType)) {

shouldWifiStayAwake AND NOT shouldWifiStayAwake

Yeah, that'll work. :D

from http://www.google.co.in/codesearch/...va&q=android WifiService.java&sa=N&cd=1&ct=rc

Anyway, changing the Settings.Secure stuff seems difficult, and requires root of course. I'm not really sure how to do it. I'll play around with it later. I'm sure someone with knowledge of this stuff can step in and help us out here! :)
[Galaxy S I9000 Android Development] RyanZA:
Okay, I've done it. I may put something together to make this easy. (Actually, to edit any secure setting, since it seems pretty cool! :) )

This is the hard way, but it's not too bad. Good luck!

You will need:

1. ADB root shell access.

2. SQLite3 Explorer - http://www.singular.gr/sqlite/

What to do:

1. shell command: busybox cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db

2. adb command: adb pull /sdcard/settings.db

3. Open settings.db in SQLExplorer

4. Right click on gservices or secure folders**, choose 'Show Data'

5. Click on the green plus icon "Insert Record"

6. Double click on name column, insert "wifi_idle_ms" - Double click on value column and insert "3000" for 3 seconds for wifi to turn off.

7. Click on the green tick.

8. Right click on the folder again, choose show data, scroll to the bottom and ensure that your change has been made.

9. File -> Close Database

10. adb command: adb push settings.db /sdcard/settings.db

11. shell command: busybox mv /dbdata/databases/com.android.providers.settings/settings.db /dbdata/databases/com.android.providers.settings/settings.db.bak

12. shell command: busybox cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db

13. shell command: chown system.system /dbdata/databases/com.android.providers.settings/settings.db

** I'm not sure if the correct folder is gservices, or secure. I believe secure is the correct one though. I just added it to both. :D

And there you go - 3 seconds after turning off your screen, your wifi will turn itself off. Profit!

EDIT: You can actually change your android_id with this, which could have some interesting uses. :)
[Galaxy S I9000 Android Development] Treggs:
You Sir, are a god!!!
[Galaxy S I9000 Android Development] Narcissus85:
Ohhh thanks for this!! : >

I just removed the voodoo lagfix for too much battery draining and i noticed the wifi problem....thanks thanks!!

MMM do u think that removing the lagifix (with the /sdcard/disable-lagfix no extension file) bring back the battery efficiency as before or i need to reflash my current rom? (M6)

Or is there a way to reflash the previous kernel without data loss?

umm ummm
[Galaxy S I9000 Android Development] Treggs:
No reflashing doesn't fix this problem which is why I was scratching my head.
[Galaxy S I9000 Android Development] supercurio:
Ok, proof that Wifi "issues" are just Android settings, that may have changed to between the whole bunch of firmwares we got.

Thanks for your insight.

Voodoo kernel don't and can't save settings permanently somewhere that would survive to flash

Please use the new thread for technical or anything other than bounty-related topic

Thanks, and keep coming with bounties:)
[Galaxy S I9000 Android Development] chrissyg123:
nice one ryan for looking at this..

overnight though I had it set to 'sleep wi-fi with screen off' and it was unplugged.

checked the batt stats in spare parts this morning and wifi was on 100% of the time, I'd lost 31% batt life in 8 hrs! it wasn't even connected to a wireless network, it was just on.

also noticed that even with wifi disabled I'm losing about 6% an hour with the screen off :(

this is jm7 clean on with voodoo b1 applied
[Galaxy S I9000 Android Development] xan:
[size=+2]For WIFI up bug:[/size]

http://xdaforums.com/showthread.php?t=774507
[Galaxy S I9000 Android Development] Treggs:
SC, I haven't done any other flashing except for the stock JG4 optus so I can't see where else this bug came from? Love your work and I'm trying to be constructive (as a newbie can be ;))
[Galaxy S I9000 Android Development] supercurio:
Thanks but please use the proper thread for that (you even quote it!) :)
[Galaxy S I9000 Android Development] ewok666:
Excellent find. It would be worth pointing out that you also need to press the Update button.
[Galaxy S I9000 Android Development] Project1.exe:
isn't the second invoking of shouldWifiStayAwake has a different second parameter? (first one is mPluggedType, and second is just pluggedType) or do they have the same value?
[Galaxy S I9000 Android Development] jim_panse:
I think my flight mode is broken. Anyone experience the same? Voodoo Beta 1.
[Galaxy S I9000 Android Development] networkdood:
Did the location of this download move?? No longer available or not found.
[Galaxy S I9000 Android Development] supercurio:
Beta2 Release approches, you can take a look at http://project-voodoo.org/ while waiting ;)
[Galaxy S I9000 Android Development] emelie:
Good stuff curio, congratulations!

Been using wordpress again eh? ;)
[Galaxy S I9000 Android Development] ago2007:
I detected a possible error in the beta3 with Kies, because at first install JM8 and I could connect and then install beta3 and I was not able to connect.

I made several tests by removing and installing beta3 and always says the same Kies, "can not connect at in development mode" and in settings-> applications-> develope is disconnected.
[Galaxy S I9000 Android Development] mikelyon:
Cancelled post
[Galaxy S I9000 Android Development] Arde:
Cancelled post
[Galaxy S I9000 Android Development] distortedloop:
Time to pay curio/supercurio folks...

It's pretty clear to me that supercurio has done enough with voodoo lagfix 3.0 and/or beta4 to claim and be paid off on this bounty.

All lag is gone.

All apps open "instantly".

Filesystem is changed to ext4 (the bounty wasn't specific to any particular version of ext).

The fix is permanent, yet easily reversed.

It's as easy as flashing an update.zip from recovery, and it doesn't get any easier than that for the "regular/inexperienced" user.

It works on all Eclair (2.1) firmwares.

Those of you who pledged, if you haven't paid up on the bounty, or donated privately via paypal to curio@free.fr, what else are you waiting for?
[Galaxy S I9000 Android Development] vitalij:
Well it's not working on JPC and other froyo firmwares. Also it requires custom kernel, which many people don't like. So the solution which uses original kernel and ext2 filesystem may be more appropriate.
[Galaxy S I9000 Android Development] mssmison:
There are many reasons that ext2 is not a good way to go, and ext4 is better.
[Galaxy S I9000 Android Development] supercurio:
Yay, let's set everybody's phone on an crash-prone filesystem...

:eek:

Voodoo is fine, stable, and even come with bonus features if you want.

Froyo ? it will be ported as soon as we will have the source.

distortedloop is right. I followed exactly what was asked by the bounty request... and more.

About presumed battery life problem, every one I had to debug was related to recent firmware problems (JM7, JM8)

What would you ask more ?
[Galaxy S I9000 Android Development] atinm:
Well, if ppl are using the ext2 filesystem - they should support RyanZA by donating to him, if they are using the voodoo EXT4 lagfix, then they should support supercurio. It isn't that hard . . . my suspicion is that many are using EXT4 for the benefits even if it does need a kernel built from samsung's sources as opposed to a kernel that they put on the phones.
[Galaxy S I9000 Android Development] jeanveupas:
- LAG still present when LOW memory is avaible (when +-60Mb it lag horribly)

- Only /data is using ext4 the filesystem still RFS for the rest...

- Needed to use a not up-to-date kernel

it's the wrong points for me, still a good job but not ended :cool:
[Galaxy S I9000 Android Development] fane1:
As far as i can remember the bounty was not for a "system" that we officially dont have.It was for Eclair system by the time it was posted here at xda.So i think that the bounty should go to Curio for sure i will send my share next friday.Thanks again Curio for a great job :)
[Galaxy S I9000 Android Development] supercurio:
Topic :

[BOUNTY] Community help is needed for fixing the poor IO performance (lag) of the SGS

Done :)

PS : you are free to use other memory settings with dedicated apps if you want.

RFS is fine for /system. It would be a compatibility nightmare to use ext4 on this (very bad idea!)
[Galaxy S I9000 Android Development] supercurio:
Exactly, i do my best to produce a solution to the I/O lag problem, but, you know.. i'm not Samung :D

And note that I did everything in order Voodoo became the standard

Website, doc, community building, help to other developers, and i think I succeed to ;)

Now you can find almost every ROM or custom kernel build (OC, BackLightNotifiations) with Voodoo/Ext4 support.
[Galaxy S I9000 Android Development] distortedloop:
Not available on froyo? Froyo's not even available unless you're willing to run what are leaked firmwares that are obviously BETA builds and not official. :confused:

So we're gonna deny the bounty reward to a guy who's fulfilled all the requirements of it, plus made the basis for several of the newer alternate fixes coming out because it doesn't work on unofficial betas? Really? Wow.

I'm pretty sure that Voodoo *will* be ported to Froyo when froyo is officially released, unless Samsung fixes the lag in Froyo, which they haven't yet, correct? What more can you ask for in the bounty?

Maybe we should not pay up when voodoo is ported to froyo because it won't work on leaked versions of Android 3.0, as well, right? :D

Let your conscience be your guide. Curio's given us voodoo, the redbend_ua discovery and template (which all the other devs are building off of now), a way to fix color and brightness as an option, and some interest stuff in the sound area. This guy really rocks my SGS world, and probably yours as well, whether you know it or not. ;)
[Galaxy S I9000 Android Development] supercurio:
By the way, putting captivate version online... Vibrant version will be back in a few hours too, max 1 day.

Even if the bounty was on I9000 forum only ;)
[Galaxy S I9000 Android Development] jeanveupas:
What will happen when froyo will be official if Samsung did release the source right now, it means stuck on 2.1 firm's with voodoo and waiting for Samsung?
[Galaxy S I9000 Android Development] distortedloop:
NOT unique to the SGS, and easily fixed with FreeMinMgr or Autokiller. Google around and you'll see that.

But the lag is gone with just /data.

There's a saying here in the US "If it ain't broke, don't fix it!" If the other partitions work fine with RFS, why mess with them?

It uses the only official kernel for which the source has been released, doesn't it?

Also, as previously mentioned, it's supercurio's redbend_ua and his template for jamming what you want into an update.zip that others are using to make alternate fixes that use the stock kernel (from newer UNOFFICIAL builds) and that don't include complicated and messy loop-mounts, playlogo hacks and all that stuff.

Give the guy his due, folks! ;)

(P.S. _ I'm surprised at how many consider samsungfirm's and @richthofen's firmwares to be official. Richthofen himself says in EVERY release first post that his stuff is INTERNAL and NOT OFFICIAL.)
[Galaxy S I9000 Android Development] supercurio:
Samsung has a legal obligation to release sources.

If they are super-slow to do so, we have a backup plan with recent kernel unpack/repack techniques discovered.

We shouldn't be worried about the source release, they release Eclair source for I9000 even before the phone hit the market, and they continue to release it quick for every US model.

Trust me, Voodoo will not become obsolete like that, it's too late to stop it ^^
[Galaxy S I9000 Android Development] RyanZA:
He did actually say that JGH was official! ;)

As far as the bounty goes - I don't think you're gonna be able to strong arm people into donating. If they're not satisfied with the fix, telling them to be satisfied isn't going to make them donate anything, it's just going to make them not want to donate.

And you're never going to be able to please everyone. Words to live by! :)
[Galaxy S I9000 Android Development] jeanveupas:
supercurio & distordedloop thanks for infos complement
[Galaxy S I9000 Android Development] captive:
My .02€:

To me lag is fixed with SC lagfix, which does not break anything, is safe to apply, and has no remarkable downsides, unless you don't want a perfectly rooted system. Btw, there's no way to fix the lag without changing the filesystem OR hacking the kernel (or both of them), which means you already void your warranty, no matter which lagfix you are using.

Moreover the fix is perfectly reversible, and as a bonus comes with some visual enhancements (which I don't use, but, hey, they are for free!)

I'm pretty sure Samsung will release sources as froyo will come, and SC will do the magic on the new kernel, applying his scripts, compiling ext4 support..

If he won't do it, well, he released the sources of the fix, it's available for everyone who wants to hack it.

I couldn't ask more.

Even if I never told I'd have donated for a fix, well I just donated a small amount, because I do think he deserves it.

Sometimes it looks like here we have a few good devs, and a bunch of people who like to complain for everything: take a look to froyo topics, first JPC is too buggy, then (when Samsung announces froyo to be delayed, probably for some bugfixing), everyone is complaining again for the delay..
[Galaxy S I9000 Android Development] distortedloop:
Hmmm...you lost me there. Not really sure what you're asking.
[Galaxy S I9000 Android Development] distortedloop:
I'm not trying to strong-arm anyone, just point out that supercurio and voodoo have, in my opionion, fulfilled the bounty requirements.

This particular thread had fallen out of the discussion loop for a while and I just wanted to bring it back into the limelight in case people forgot there was a bounty thread for this issue.

To everyone, of course, let your conscience be your guide. If you're using voodoo and pledged a bounty, consider paying up. I didn't pledge, but I've dontated because voodoo is the first and only fix to make my phone a delight to own instead of a nightmare (or at least annoying bad dream with mimocan method). :D

re: JGH - he also isn't the one to leak it, though, is he? My original statement is correct, I believe.
[Galaxy S I9000 Android Development] dopeee:
Totally agree with distortedloop. supercurio did far more than I expected and has given a quality product with excellent service. I'm surprised how many people still complain as if they dont remember how laggy this phone was without this fix.

I'll paypal my bounty amount as soon as I get home tonight. Thanks supercurio!

EDIT: woo work lets me get on paypal. donated already!
[Galaxy S I9000 Android Development] kramus:
Never said I would donate, but for your good work (and putting up with some B$ from people in no position to comment) Curio, I just donated €15.
[Galaxy S I9000 Android Development] ashwinds:
Some Gratitude Please

Agree completely. Far as I am concerned - supercurio has done enough and though I did not pledge, I too paid up soon as I saw Beta 1. Ryanza also got a donation because I used OCLF while curio worked on his fix.

So people - forget the discussions over Ext2/Ext4, forget Froyo, forget all those features you wish but dont have - let your conscience be your guide. Remember that you paid $$s to get a phone which was a laggard from Samsung - and these guys have done and indeed are doing great work - a little appreciation, atleast a sign that we are thankful rather than cribbing all the time will only encourage more good work from these devs and also enthuse more devs to join in the community. In time, be certain that Samsung is going to stop development to focus on their next shiny device - building a strong dev community will stand us all in good stead for the future. Coming across as nitpicking idiots wont encourage devs.

Pick your dev - say your thanks - with a few $s ideally.