yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Stefanauss:
I read your template update.zip kernel topic and the original one, but i couldn't figure out how to run the correct redbend_ua binary through adb.

Right now the correct binary is on my computer, extracted from Voodoo's update.zip.

On the phone, redbend_ua is in folder /sbin, which is in $PATH.

executes the binary not allowing cli parameters, on the phone. (i didn't gave root permission, so it fails all its checks)

How could i run the correct one?

Does it need to be loaded on the phone? If so, in which location?

Or could i run it with the correct binary still being on my pc?

Thanks for your patience :o
[Galaxy S I9000 Android Development] atinm:
Disabling the lagfix does not replace the kernel - it just converts your filesystem back to RFS (you should have heard the voice telling you that it is converting back to RFS). Kies has nothing to do with the kernel though - it has to do with how you are set up to connect via USB. Look in the Settings > Applications > USB Settings to make sure it is set to Kies.
[Galaxy S I9000 Android Development] dutchcow:
It doesn't restore your kernel, it just disables the lag fix.
[Galaxy S I9000 Android Development] atinm:
Actually it can be anything with disable*lagfix, so disable-lagfix is fine too and that is easier to create for most people rather than putting a space in a file or directory name.
[Galaxy S I9000 Android Development] Stefanauss:
Oh, i was just reporting what the docs says and what worked for me.

But nice to know we have the original option, thanks. ;)
[Galaxy S I9000 Android Development] M3xital:
Thanks for the information about the Kernel.

The phone it's always setup to ask how do i want to connect, and haven't had problems connecting with Kies before applying the lag fix.
[Galaxy S I9000 Android Development] supercurio:
if Kies don't work with lagfix disabled, the problem comes from elsewhere.

lagfix disabled means that your /data partition is in RFS, not that you're back with a stock kernel.
[Galaxy S I9000 Android Development] supercurio:
Sorry, if you're not 100% comfortable with shell, i recommand you don't attempt to use redbend_ua AT ALL.

To risky. This is a tool for experts only.
[Galaxy S I9000 Android Development] Stefanauss:
So i guess i'm an expert now. :)

Just kidding. :D

I really am comfortable with shell, i'm a six years linux user. It was just that this stuff is barely documented and you didn't provide any way to restore stock kernel, which i needed to. But i really understand your reticense, because i can really see how you're just pressing a single wrong key on your keyboard away from the total disaster.

Anyway, it's an awesome tool!

I really hope we'll soon be able to do magic with this. :eek:

Is there any work active on this, from your side or by the Heimdall Project?

I managed to succesfully dump and restore. redbend_ua dump and dd produced same md5 but different image's size.

The reason because you use dd in your update.zip for Voodoo is the reboot thing?

Ok, turning back to Voodoo:

Now that i'm on stock i'll continue my battery runs for comparison. But i really should said something about Voodoo Color. Brightness was a lot WIP, but now that i'm back on stock after 5 days, missing new sharpness and temperature, i feel like i'm looking at my SGS through an empty plastic bottle. And it's not nice. :rolleyes:

Just donated.

As i said in the bounty, i'll be glad to do some more when this will be fully opensourced and documented.

Really nice work Curio, hope you keep up. ;)
[Galaxy S I9000 Android Development] thunderteaser:
I totally agree. On the other hand, let's just keep in mind this project is still in BETA status.
[Galaxy S I9000 Android Development] Stefanauss:
I don't doubt it will be :)

Oh, i forget (another) question.

Is there any plan to include BackLightMod Notifications "officially" into Voodoo Project?

I reeeeeeeeeeeeeeeeeeeeeally hope so.
[Galaxy S I9000 Android Development] thunderteaser:
Uhm, don't know about that, but BLN developer is planning to add Voodoo compatibility from the next versions! I think the result you're asking for should be the same. :)
[Galaxy S I9000 Android Development] supercurio:
Oh yeah but he was talking about redbend_ua of course, which is not opensource.
[Galaxy S I9000 Android Development] Stefanauss:
The result i hope for would include Color, which is not the case from what i read on BLN thread 1st and 2nd post.
[Galaxy S I9000 Android Development] Stefanauss:
I wasn't talking about redband_ua, i read the thread and know it's not opensource. ;)

I read in the bounty thread that you was going to setup a git repository. But maybe you released by other means, and i just missed that. =(
[Galaxy S I9000 Android Development] supercurio:
Ahaha alright, i'm glad you understood the fact that i don't try to make redbend_ua a popular choice for live command typing in adb ;)

Bricking for good your phone because you type bml2 or something instead of bml7 is quite not fun ^^

An automated - restore my previous kernel - feature is envisaged for future versions.

About project-voodoo work, everything is already opensource, and if any info miss (a .config file to build something, etc) you just need to ask.

There is even a fine team on IRC, more and more skilled each day, because we share info very quickly, faster than we can write it in any documentation.

About color yeah the difference is incredible.

Of course the 100% mode eats battery badly :D

Personally it's the the sharpness i love the most, the Voodoo ones gives so much higher perceived sharpness without artifacts.

The same screen... next generation.

And thanks Stefano !
[Galaxy S I9000 Android Development] supercurio:
And I will include BLN too in Voodoo
[Galaxy S I9000 Android Development] dutchcow:
I have to say the difference between stock kernel and lagfix kernel when it comes to battery is very big. At least on my phone. In a few hours down to 70% with lagfix, whereas stock kernel will still be in the 90's.
[Galaxy S I9000 Android Development] supercurio:
For your issue, we will have to wait for the next source drop from Samsung, including hopefully better drivers.

I'll maybe find interesting things in this department when merging I9000/Vibrant/Captivate kernels.
[Galaxy S I9000 Android Development] Stefanauss:
What a Voodooday this is :cool:
[Galaxy S I9000 Android Development] thunderteaser:
What the f...!!! Is there really anything we could blame you for?! Oh, yeah! I don't like the name "Voodoo", it's totally unrelated to "Galaxy"!

... Just kidding, of course! :p
[Galaxy S I9000 Android Development] M3xital:
I just went back to stock kernel and now i can connect with Kies again.
[Galaxy S I9000 Android Development] mbriody:
Despite my WiFi and battery issues I've come back to Voodoo. Its just too slow without it!

Hope these things get found/fixed in a newer version.
[Galaxy S I9000 Android Development] kenkiller:
Wonderful. Using BLN with voodoo, but still missing the lowest brightness settings.....makes me blind in the night. :D
[Galaxy S I9000 Android Development] dtgeorge:
Many thanks to You! Great job!

I started use voodoo since sunday, after nearly 1.5 month with CFLagFix. Voodoo is much faster!

But it seems battery drain also faster. I using Beta 4.

May be there are some additioanl settings????

And another q about brightness. When trying to adjust it manually there some unsmooth transition at about 15%. On 14% it is pretty dark, but at 15% it becomes muchmuch lighter. Can you made it more smooth? :)

I use i9000 with JM2. Voodoo Beta4 was installed after full wipe. Install method ober update.zip.
[Galaxy S I9000 Android Development] Qazz~:
To get it clear, does voodo just change the stock RFS filesystem into ext4 only?
[Galaxy S I9000 Android Development] ashwinds:
Voodoo-lagfix does just that (for /data).

Voodoo-colour-lagfix does that AND also toys around with the video settings for brightness, sharpness and colour a bit.
[Galaxy S I9000 Android Development] Devhux:
Just installed the lagfix. Surprised me when the robotic voice announced what it was doing, but otherwise it seems to be faster. Time will tell me how my battery holds out but at least I have an external battery if needed.

Thanks for all your hard work on making our phones better. Your work is definitely appreciated.

____________

Any typos or other oddities in this post are brought to you by the letters G & T, the number 9000, and Swype.
[Galaxy S I9000 Android Development] fawaad:
And I thought I was the only one with battery issue. Is it the journal bit that causing it?
[Galaxy S I9000 Android Development] StuBouyer:
Appears that there is a marked difference between beta 2 and beta 4 with regards to battery usage.

I've tried lagfix3 - with and without colour - and overnight it goes from 100% to 75% in 8 hours. This is with plane more turned on.

The same settings with beta 2 only drops from 100% to 96%.

So I'm sticking with beta 2 for the time being.
[Galaxy S I9000 Android Development] Qazz~:
since it only changes the filesystem from RFS to EXT4 how does it affect the battery life so significantly o.o?
[Galaxy S I9000 Android Development] jootje:
I installed the beta4 pack.

Unfortunately, my screen doesn't turn off automatically anymore.

After the time out, it goes back to a lower intensity of the screen.

Is there any parameter that has been changed? How can I restore this, because I'm not used to turn off the screen every time manually and now, my battery is reducing very fast.
[Galaxy S I9000 Android Development] ashwinds:
Its not certain that it does. There are many issues - for e.g. I thought it was voodoo but found that my wifi never went to sleep with jm8.

As for why it *could* affect - its because the voodoo fix uses a custom kernel compiled by curio from sources provided by Samsung - now if Samsung's source is not in sync with what build is there in firmware, we'd lose out on those optimizations. But thats speculative.
[Galaxy S I9000 Android Development] bub181:
I found the exact same thing happened with my phone. Beta 4 uses much more battery than beta 2.
[Galaxy S I9000 Android Development] AndyCr15:
Please add an archive to the project voodoo site :)

Can someone upload Beta 2 please?
[Galaxy S I9000 Android Development] evensteven:
There is an archive. ;-)

http://project-voodoo.org/downloads/
[Galaxy S I9000 Android Development] AndyCr15:
Ahh, well done :) Thanks.
[Galaxy S I9000 Android Development] supercurio:
Beta2 == Beta4

Both run exactly the same code, same kernel, same configuration :)

What differs between both ? Migration code, partition and file autodetection at boot etc.

What i know, is that JM8 is known for causing battery life problem (Firmware actually uses power, not the kernel itself)

I can't see scientifically how beta2 and beta4 can provide different battery live... Is Voodoo battery live becoming an urban Myth ?

If a lot of people talk about it, will it become be "true" for everyone ?

I don't think so..

A lot of people say that they're perfectly happy with battery live on Voodoo, as I do.

Considering Color : the new 100% brightness level eats a bit more power but the added low brightness mode saves a ton.

Well anyway, I'm still waiting for a reproducible test-pattern.

If you're affected by a battery problem, please send me a detailed description, of conditions can experience here.

That's why it's still in beta stage. I need your help if you're affected by any related to Voodoo battery problem.

Thanks ;)
[Galaxy S I9000 Android Development] distortedloop:
No value added here, but I'll say it anyways.

Now that you've fixed, really and honestly fixed, the lag on the SGS with voodoo, we still need something to ***** about, and battery life is always the easy target with rom-flashing addicts, and the latest patch we've applied usually takes the blame.

In my experience, no change in battery life with or without voodoo (b1 or b4). I'm on JM8, and had been using it on other firmwares as well.

Battery life on smartphones sux, period. Buy an extra battery, they're available at ebay for $13 (two batts, two chargers).
[Galaxy S I9000 Android Development] dutchcow:
I'm not sticking a non-genuine battery in my expensive phone. How much does a genuine cost?
[Galaxy S I9000 Android Development] StuBouyer:
Definetly a difference in the process level of android system as seen by watchdog and top between beta 2 and beta 4. I'm running the stock australian firmware - dtjg4. With beta 4 z android system never drop below 10%, usually around 16% or so. I originally thought this was due to the colour changes, but that didn't really make sense either.

[QOUTE]Considering Color : the new 100% brightness level eats a bit more power but the added low brightness mode saves a ton.[/QUOTE]

Rarely have the brightness over 25%, and that shouldn't make much difference over night with the screen off.

Do you need/want a list of all apps that are running/installed? Do you want logs - if so what ones? I'm looking for a background app that will monitor cpu usage and snapshot the results but haven't had any luck yet.

Thanks for your continual had work, much appreciated.
[Galaxy S I9000 Android Development] oddsocks:
Just wondering to everyone complaining about battery life did you all reset the battery stats after flashing? Personally didn't really notice a battery drain with beta 4.
[Galaxy S I9000 Android Development] bwfc:
No issues for me on the battery issue using Lagfix 3. Great job Curio! keep up the good work!
[Galaxy S I9000 Android Development] bub181:
I found that the idle CPU usage was higher in beta 4 lag fix than in beta 2. This should be easy to test by just installing a CPU usage meter. You don't have to bother looking at the battery life because that is a side effect of the higher idle CPU usage.
[Galaxy S I9000 Android Development] raspdeep:
To those that say b4 uses more battery than b2, can you write you steps in upgrading?

For example, did you try these scenario:

scenario 1

1) install b2

1a) check CPU usage

2) install b4 without disable lagfix

3) check CPU usage

4) install back b2 without disable lagfix

5) check CPU usage

scenario 2

1) install b2

1a) check CPU usage

2) disable lagfix

3) install b4

4) check cpu usage

5) install b2 without disable lagfix

6) check CPU usage

please report back
[Galaxy S I9000 Android Development] ashwinds:
Battery Issues and such

Voodoo does seem to be taking a lot of bad rap - but I guess its understandable that people first relate bugs to it since it makes some system-wide changes :)

Just to illustrate (this is apart from my troubles with JM8's wifi and power) my first suspicion was voodoo when i was configuring APNs and was unable to save any - all the more strengthened because this was a factory-wiped JM1R3 and i *was* able to save an APN before deploying voodoo. After a reflash, 2 factory wipes found that it was the software Market Access to blame (which had been auto-restored by titanium backup) - it was not letting me update APNs. REmoved it and everything was fine again.. with voodoo.

Moral of the story: its easy to blame Voodoo - but often its not.
[Galaxy S I9000 Android Development] g0c:
great job curio !!! installed quickly and it works ... even the clockworkmod works

battery goes from 100% to 94% over night (wifi off)

quadrant 2242

waiting eagrly for new releases !!!

THX
[Galaxy S I9000 Android Development] daClaus:
as far as I've read here it's also possible to disable the lagfix and flash the original JM8 kernel with an update.zip file instead of odin, is that correct? If yes, can anyone please provide me the original JM8 kernel as update.zip? Thanks!
[Galaxy S I9000 Android Development] mdalacu:
it's zImage from CSC_I9000OXXJM1.tar.md5 archive.
[Galaxy S I9000 Android Development] daClaus:
so if I rename this to update.zip I can flash it over the recovery menu?

There's also a file called bml7-zimage-kernel-backup.img in my root, can I use this too?
[Galaxy S I9000 Android Development] drknezz:
website is down, can anybody upload the necessary files please?
[Galaxy S I9000 Android Development] supercurio:
website is up ^^ (again?)
[Galaxy S I9000 Android Development] raspdeep:
like i said, i've already tested it with ext2 and the difference is just about 100 pts... you dont hv to touch the partition, thats the beauty of it but u do need a kernel that formats it to ext2 and then mount it as ext2.

i did it just for testing cos i'd like to know.. i've done a lot of different testings, even swapping /system and /data so /data mounts on stl9 and moving /system to mmc.. quardrant is around 1000pts and there are many things to fix if i go that route so i dont know if its worth the time.. i may try yaffs2 next weekend when i have time just to see if it really makes a difference but i really doubt it

ive tested ext4 without journaling too but the benchmark difference is too little to tell..
[Galaxy S I9000 Android Development] justcme:
I'm with Ryan on this one. The fact is, we have a very stable system, limited hardware resources, and rather non-critical data residing on the /data partition. (at least for me anyway)

I don't see any harm in letting those who have a reasonable idea of what they're getting into testing this out for the masses, and reporting back. I for one, am interested in this.

Mind you, most linux netbook distros ship with ext2 by default. Those are a bit closer to home (our SGS), but are still by far more powerful - and keep far more sensitive data. Plus we've been using FAT32 on our external SDs for the life of our android devices so far, and how many of us have had issues with this? I can't say I've lost any data yet. If this were a big problem, android devs would surely have looked into journaled FSs on our SD cards by now.
[Galaxy S I9000 Android Development] justcme:
Not really interested in benchmark performance or lag-fix usability - that's a given.

How does it fare on the battery? Any noticable difference? That's my question right now. If flash read/writes are really not causing any noticable battery issues (regardless of FSs used) then maybe we can (should?) leave it at that.
[Galaxy S I9000 Android Development] raspdeep:
well, my kernel is uv so battery life is always better than stock
[Galaxy S I9000 Android Development] gshklover:
stock images support ext2 out of the box. From what I saw, stock kernel also had initramfs uncompressed inside, so theoretically one could reformat whatever he likes to ext2 and modify the init.rc inside the stock kernel. If the only change is type of the filesystem, the change is small enough to be done in place without the need to recompile and wander if the kermel is "compatible" or not...
[Galaxy S I9000 Android Development] RyanZA:
I'm actually more interested in resizing /sdcard FAT32 partition in place, after unmounting it. I want to re-partition some of the 6GB FAT32 partition into EXT2/4/XFS/whatever for easy testing and whatever else, without having to mess with anything samsung specific. Pretty much just need gnu parted compiled for ARM, I believe. Amonra recovery has it included, but I don't know how to pull the binary out of the .img file. Currently trying to compile it using sourcery android toolchain, but this is all new to me. :D
[Galaxy S I9000 Android Development] gshklover:
if only for testing, you could probably do these comparisons on external sd. To be fair, you would need to compare to rfs on external sd too.
[Galaxy S I9000 Android Development] rui.mamede:
RyanZA, I don't mean to offend you but why don't you start a thread of your own instead of spamming this one with your great alternatives?
[Galaxy S I9000 Android Development] lyno:
Because it's still on-topic and he has some very good ideas?
[Galaxy S I9000 Android Development] lyno:
I disagree since most users want this fix to be done on the internal phone sd rather than external and the best way to test this would be on the internal sd.
[Galaxy S I9000 Android Development] captive:
ok, just my 2 cents..

I tested sc zimage for 4 days on a XFJM6 firmware, stock settings, no external task killer or power management software, with something like 60-70 user apps installed, alternating sessions of heavy usage with session of very poor usage (a couple of phone calls, some sms, some twitter, almost no browsing).

IMHO, the fix make SGS much more responsive, in some situations, while is less noticeable in others.

Phone will never stall on installing apps, on (very) quick switching between apps, and wiil complete startup and media scanning faster.

Restoring an entire set of apps with titanium backup is waaaaaay faster than with stock firmware.

Once system is started, btw, you may not find any difference in performance if you make a "normal" use of it, swithing between apps is not a nightmare on JM6, games are smooth just as they are with sc lagfix.

The major downside is, in my experience, battery draining: on a fully charged device, I tried to start nibuzz, browsing a bit, and playing some games, always with nimbuzz open. With lagfix kernel battery was going down by 2% every 10 minutes, with stock kernel draining is the half.

Obviously this is not a "scientific" test, but draining is something you can "feel" with supercurio kernel.

I don't even know why, maybe ext4 transaction management is just more cpu-intensive than rfs, who knows.. btw, I'm back on the stock kernel, battery life does matter to me, but I miss that kind of "snappyness" supercurio gave us!!! :D:D

@sc: thanks for your work!!! maybe you can investigate the problem some of us are experiencing, meanwhile I'm looking forward a public beta2..
[Galaxy S I9000 Android Development] ags29:
I saw that lol. Want came our as wasn't on Swype (Before your edit lol). I knew it wasn't just me.
[Galaxy S I9000 Android Development] jjwa:
I have used it for a few days now, and have 60 apps on it now. Yesterday it had become sluggish in use. I had installed several home/launcher replacements, and was trying out all of them in a short duration, switching between them a lot. At the same time I was trying out Quickdesk and Smart Taskbar. Which both put a homescreen/appdrawer-like overlay on the currently running program. So that got a bit messy. I had not restarted the phone for quite a while.

It was certainly not unusable, but some of the heavier programs could take up several seconds before popping up. Crazy usage, but still, I did manage to find proof that Voodoo is not made of real Voodoo!

So I guess I am still real happy with it :). I imagine the above scenario would have been a real horror without Voodoo.
[Galaxy S I9000 Android Development] supercurio:
;) jjwa

Yes it is just an Eclair/2.1 Android phone, at least there is no more sporadic super slow filesystem I/O problem.
[Galaxy S I9000 Android Development] lyno:
Hehe yea. Swype is amazing most of the time and a lot of my eyephone friends (fools) envy my SGS for it (amongst other features), but sometimes guesses wrongly.
[Galaxy S I9000 Android Development] sharky34:
I think that this scénario gave à hard time too the garbage collector.

Not to voodoo lagfix imho.

What you perceived were probable major gc.
[Galaxy S I9000 Android Development] oskariunit:
I've been reading this and other voodoo threats and I'm very curious to see where its heading. But i'm not a coder, I'm just everyday normal user and most of the time I dont have a clue what you're talking :D

What I would like to know is that is there any drawbacks from ext4 usage? file corrupting, product lifetime and is the phone still usable from windows (kies, mass memory). Anything else?

And whats the colour part in beta2?
[Galaxy S I9000 Android Development] supercurio:
To every people experiencing reduction in Battery life.

- Compared to ?

- Did you try mimocan's or any other kernel ?

- What is exactly your measurement procedure ?

- Are you far from the cell towers, how is the signal reception ?

- which % use "Android OS" (not "Android System") ?

Thanks for your answers.

PS : Android OS equals power usage of the whole Linux Kernel.

Ext4 driver for /data represent a fraction of that.

I hope your answers will help better understanding the power usage of our little shiny device :)