yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] renaud:
Well, in fact 250 or 1500 does not really change anything on battery life. 1500 will give better response time than lower values. The drawback being that your phone makes more interrupts, so raw performance will be negatively affected.

However, most people want a snappy interface, not something which can write 2Gb the fastest possible way. This is also where quadrant score comes, a snappier phone will generally give lower quadrant scores as quadrant only measures raw speed.

Values higher than 1000 are not permitted in a stock linux kernel, you have to patch the kernel to get over 1000. Some drivers break at values over 1000 as they have never been intended to run at so high values. For example, the camera driver breaks over 1500, that is why I choose to settle at 1500 and not go over.
[Galaxy S I9000 Android Development] Jumba:
Great, thanks for the explanation, I'll be trying your kernels out in future.
[Galaxy S I9000 Android Development] ragin:
Will this work on JPX? Voodoo seems to work
[Galaxy S I9000 Android Development] renaud:
It seems JPX is about the same as JPU, so there are no reasons why it wouldn't work
[Galaxy S I9000 Android Development] Freexter:
just want to let you know,since I went into 3br i never had that black screenbug again.no idea why i didnt do anything but tried to apply update.zip for cwm but didnt work,still on 0.18.2
[Galaxy S I9000 Android Development] Freexter:
i wanted to switch to xxjpx and i started with a fresh new ROM

but i keep on having this on the screen

update media. please wait

E:Can't mount /dev/block/stl10

(No such device)

E:copy_dbdata_media:Can't mount DBDATA:

your storage not preparded yet, please use UI menu for format and reboot actions

copy default media content failed

what can i do to get this in order again?

edit: the second time(the first time it was still there) when i started reflashing from XWJM8 to XXJPO it disappeared, so i think the problem is solved
[Galaxy S I9000 Android Development] renaud:
You can use Grimmvarg tuxility app to flash your kernel which can be found on the market.

I experienced the black screen bug today, so I will research what could cause this.
[Galaxy S I9000 Android Development] DEagleson:
Happened to me too.

Did a XXJPO clean flash, formatted the Internal SD card and then continued with the flashing of XXJPX.

Think the lagfix remained even after repartition or something. :(

Still this is a great kernel, and i hope the "black" screen is fixed.

I have no idea why it even appears. xD

DEagleson
[Galaxy S I9000 Android Development] Arise:
That error for /dev/block/stl10 seems to be for a missing /cache partition. Don't know the easy solution and why this problem appears, but I wonder if people can see the /cache partition after the phone boot.

Missing that partition could go unnoticed easily, but could give headaches if trying the market, cause download won't work. :)

The kernel should feature a BIG warning, don't know what would be the best way to inform the user about this, but definitely, if the /cache (/dev/block/stl10) is missing the user should know about this!
[Galaxy S I9000 Android Development] renaud:
0.20 is out based on JPY
[Galaxy S I9000 Android Development] Freexter:
nice to hear that. is the batterylife better than stock?
[Galaxy S I9000 Android Development] ragin:
Will you puff some STEAM into your kernel?
[Galaxy S I9000 Android Development] renaud:
I am mainly tracking the black screen bug. I haven't been able to see it again at the moment.
[Galaxy S I9000 Android Development] KMino:
Sounds like FS corruption, I had this before it got fixed. Solution, use Odin, flash old rom with re-partition and 512pit..
[Galaxy S I9000 Android Development] ragin:
Any development on this?
[Galaxy S I9000 Android Development] renaud:
I am still developing that kernel although at a slower pace during holidays.
[Galaxy S I9000 Android Development] joeonxda:
Hi there. Thanks in advance for some good work here.

I just got this one in Darky's 7.5 and everything seems fine so far. Gona run this a few more days to be sure =)

However, at recovery, I got some funky red lines

E:Missing bitmap indeterminate1

(Code -7)

E:Missing bitmap indeterminate2

(Code -7)

E:Missing bitmap indeterminate3

(Code -7)

E:Missing bitmap indeterminate4

(Code -7)

E:Missing bitmap indeterminate5

(Code -7)

E:Missing bitmap indeterminate6

(Code -7)

#Manual Mode#

--Applying Muti-CSC...

Minor compatibility issue I hope ;)
[Galaxy S I9000 Android Development] renaud:
This is happening because some recovery pictures are missing. That does not cause any harm besides the error messages.
[Galaxy S I9000 Android Development] ragin:
But why applying multi-csc?
[Galaxy S I9000 Android Development] zzapall:
maybe you could do two versions jfs and ext4. on your file server is zImage.ext4conv but I do not know if I can use it in my SGS
[Galaxy S I9000 Android Development] renaud:
Don't use the ext4conv yet it will wipe your system. This is a conversion tool from jfs to ext4 but it doesn't work at the moment.
[Galaxy S I9000 Android Development] zzapall:
and you can count on versions already based on ext4?
[Galaxy S I9000 Android Development] Freexter:
hey nikademus are you actually working on a new version with jpx sources working with xxjpy?
[Galaxy S I9000 Android Development] joeonxda:
Hi I am back. Wanted to post this earlier. After just a couple of days of use with Darky's, I had to switch kernel. Seems the kswapd0 process spiked pretty badly and drained batt critically. I had been testing that without any other apps except Watchdog lite or lagfixes.

Anyways will keep an eye out for future developments here.
[Galaxy S I9000 Android Development] rajuki:
I had an issue where the phone just didn't come back from Standby a couple of times. Battery drain is moderate. Will keep on it and post back any issues that I encounter.

Keep up the good work!
[Galaxy S I9000 Android Development] rajuki:
Sorry if this is a repeat question but search is not available for me for at least last 30 minutes.

I wanted to install the APK mods so I needed CWM. I install CWM first and then reboot to CWM recovery with update.zip also in SD Card. Now the goddamn thing is stuck in a loop because it just fails to update the package. In Recovery 2e it says "Finding update package".

I took out the battery, reset the phone, even flashed the Kernel again but of no avail. Its still stuck in this loop. Now, before I flash a image from scratch and lose everything, I would like to check if there is a way out of this without flashing the new image?
[Galaxy S I9000 Android Development] Tricky103:
I have the same issue. I just moved onto the so kernel. I though I would wait for an update to this kernel. It was nice up until then. Cwm is important to me
[Galaxy S I9000 Android Development] rajuki:
How did you get out of the loop?
[Galaxy S I9000 Android Development] ragin:
He means he flashed Super Optimized kernel over it by the looks of it.
[Galaxy S I9000 Android Development] rajuki:
Tried that. It doesn't matter what Kernel you flash since it bypasses that.

So I had to flash over new ROM again.

@ nikademus: maybe integrating CWM is a good idea in one of your next releases?
[Galaxy S I9000 Android Development] ragin:
I have asked him a few times, he says he doesn't require CWM.
[Galaxy S I9000 Android Development] renaud:
You can try 'adb reboot', that should allow you to reboot out of recovery.
[Galaxy S I9000 Android Development] renaud:
The thing is, since you can go into recovery, do 'adb root' and then 'adb shell' and the shell is not linked to /system, you can apply and modify everything without using CWM and in a safer way. This of course involves some basic unix knowledge.

I will think about integrating CWM again.
[Galaxy S I9000 Android Development] Tricky103:
I think it would be worth having cwm. Unfortunately my unix knowlegde is rather slim. I can only learn about it though... I'm sure there are many like me
[Galaxy S I9000 Android Development] ragin:
Mine is worse, whenever I come across a problem, I restart my computer into linux, search for the solution to what I want, do it. If I come across the same problem in a weeks time, I again have to search for a solution, I am that bad at linux.
[Galaxy S I9000 Android Development] renaud:
0.21 is released. Not much changes, based on JPX sources and some kernel cleaning.
[Galaxy S I9000 Android Development] renaud:
My phone is now up for more than 130 hours and I haven't been able to see the black screen bug again
[Galaxy S I9000 Android Development] SupaDuckie:
you should implement some of hardcores tweaks make it even better experience and battery ;)
[Galaxy S I9000 Android Development] zzapall:
when new version ?:)
[Galaxy S I9000 Android Development] renaud:
What do you wish in new version? I mean 0.21 is already great., I don't see much to add.
[Galaxy S I9000 Android Development] jaju123:
Can you add voodoo sound? And does this support conversions from ext4 to jfs?
[Galaxy S I9000 Android Development] renaud:
I will see if voodoo sound has source code.

It does not support ext4 to jfs, you have to revert to rfs first.
[Galaxy S I9000 Android Development] SupaDuckie:
yeah supercurio has the source out for his voodoo sound :)
[Galaxy S I9000 Android Development] renaud:
0.22 is out with voodoo sound
[Galaxy S I9000 Android Development] Freexter:
nice job
[Galaxy S I9000 Android Development] renaud:
0.23 is out with tiny RCU
[Galaxy S I9000 Android Development] renaud:
0.24 out with better battery life
[Galaxy S I9000 Android Development] Arise:
What about the "surprise"?

And what do you mean by "better battery life"?

I want to know something. If I convert from a voodoo kernel like (voodoo or advanced voodoo) on ext4 to laststufo kernel (superoptimized) on jfs and I write your kernel should it work?

voodoo ext4 -> laststufo ext4 -> laststufo jfs ->nikademus jfs

Also is it possible after your kernel to use laststufo's kernel again?
[Galaxy S I9000 Android Development] renaud:
You will know by installing :)

10 to 20%

It's probably better to revert to RFS from voodoo, then flash my kernel
[Galaxy S I9000 Android Development] Arise:
You can tell me in a short PM. :P

Ok but where this improvement come from?

P.S. Github not working right now...
[Galaxy S I9000 Android Development] dehem333:
Why dont you add CWM?
[Galaxy S I9000 Android Development] renaud:
Some undervolting mainly
[Galaxy S I9000 Android Development] cr4zy.b0y:
:)

CWM version plz ? willing to test but i dont trust ODIN :) .... thanks:D:D
[Galaxy S I9000 Android Development] renaud:
You should not trust odin, but heimdall works fine. Honestly I trust heimdall more than cwm.
[Galaxy S I9000 Android Development] cr4zy.b0y:
one more question :) ... i have read rom creation tutorial and now tring to build one and would like to include your kernel . which version shoud i include heidmall or odin ? thanks:)

PS : i'm completly noob , take me easy :))
[Galaxy S I9000 Android Development] renaud:
You need to use the heimdall version, the odin one is the same kernel, but in a tar achive, that's all.
[Galaxy S I9000 Android Development] Tricky103:
Here you go. I made a CWM version. (not tested, should be good)

I will also test the kernel later on..
[Galaxy S I9000 Android Development] Freexter:
if I apply this kernel how do I get back to rfs?

somebody already tested cwm version
[Galaxy S I9000 Android Development] renaud:
As written in the first post, by flashing a full rom :D
[Galaxy S I9000 Android Development] Freexter:
thanks I read that but thougt maybe something changed :)

with which ROM version do you use your kernel?
[Galaxy S I9000 Android Development] renaud:
At the moment I am using DOC 9.1.2_XWJS3
[Galaxy S I9000 Android Development] x86-Dark:
When do you implement Voodo Sound 2?

I will give a try when it's ready!
[Galaxy S I9000 Android Development] renaud:
0.25 is out with voodoo sound V2
[Galaxy S I9000 Android Development] Freexter:
does jfs also use less power than rfs?
[Galaxy S I9000 Android Development] renaud:
As it seems, yes.

But for extreme battery life, I would definitely recommend "juice defender" with "extreme juice" add on.
[Galaxy S I9000 Android Development] Sarutobi:
Hmm i try version 0.25 and i'm waiting now 15 Minutes and i only see the Penguin is it normal?

I've the normal RFS on my Phone.
[Galaxy S I9000 Android Development] renaud:
That seems a little bit too long. Did you have enough space on your internal SD?
[Galaxy S I9000 Android Development] Sarutobi:
i've 3,8 GB free on Card
[Galaxy S I9000 Android Development] Freexter:
is there a way i can create a cwm version so i can include it in insanity rom,cwm flashable.this way i would be able to use newest ROM non wipe but still use your kernel without flashing a new ROM every time
[Galaxy S I9000 Android Development] renaud:
Someone created a cwm version a few posts before, maybe you can use that as a template
[Galaxy S I9000 Android Development] Freexter:
k I'll try
[Galaxy S I9000 Android Development] renaud:
version 0.26 is out featuring Voodoo sound V3
[Galaxy S I9000 Android Development] dakine:
Doesn't that just cause another set of issues, poor battery life being one. I'd much rather see it use the internal SD myself as I believe that wear isn't really an issue if the controller takes care of wear leveling as so many have stated.
[Galaxy S I9000 Android Development] renaud:
I don't really see much of a difference running on the external SD. But the goal is indeed having everything on the internal one. My first kernel mod will be an external one, I don't want to kill everything at the first attempt.
[Galaxy S I9000 Android Development] nrg:
In JFS spec it says you can have the journal on a different partition/device. Have you thought/tried about moving the journal to the last 128mb of the external SD?
[Galaxy S I9000 Android Development] renaud:
I know this feature, but I did not try. I think it may be interesting if jfs is on the internal SD and the journal on the external one. But I am not sure the performance will really increase that much.
[Galaxy S I9000 Android Development] nrg:
The only disadvantage about this would be battery usage. I guess writing to 2 devices could use more power (not sure though).
[Galaxy S I9000 Android Development] renaud:
my power consumption, even on the external SD is not bad, better than stock system anyway
[Galaxy S I9000 Android Development] [Ramad]:
I may be wrong, but I think that the best way is to make it as easy as possible for the user. What if the external card fails...or the user wants to remove it for any reason. Maybe it is best to keep all the eggs in the same basket this time..:)
[Galaxy S I9000 Android Development] nrg:
You are absolutely right but... what if i want to take the risk? Many people used ext4 on ext-sd without issues before. A simple hidden file like .jfs_external_journal or just automatic use if existing would be enough for power users.
[Galaxy S I9000 Android Development] [Ramad]:
What I meant was not to divide the fix between two cards (Internal and External) but use one of them for the whole package.
[Galaxy S I9000 Android Development] nrg:
If JFS is working properly/faster then their is no reason to use it on the external sd.
[Galaxy S I9000 Android Development] jodue:
hey, thanks for the full busybox build ... great to finally have wget on the device :D
[Galaxy S I9000 Android Development] renaud:
It is easier in fact and speed can probably vary if you use a class 1 or class 10. I can only test on a class 2 at the moment, but it would be interesting to see benchmarks on a class 10 one.
[Galaxy S I9000 Android Development] dupel:
From what I remember from time of mimocans lagfix (ext4 on externadl sd) it didnt really matter because even class 10 cards are limited by the phones ability to transfer data to and from external card.

That is why in the end people started using internal sd =)
[Galaxy S I9000 Android Development] renaud:
I would have thought that. The interesting point may be the class limit. I mean what is the class giving the most throughput while being the lowest possible.

Also class 2 means minimum 2Mb/s, but that does not mean the device is not 6Mb/s capable, this may distort benchmarks a little bit.
[Galaxy S I9000 Android Development] sztupy:
Where and how did you compile the jfs tools? Was it using bionic or a generic linux arm-eabi compatible compiler?
[Galaxy S I9000 Android Development] renaud:
At the moment those are statically compiled binaries, they use glibc. I will probably compile everything using bionic or uclibc when I am ready to release the mod.
[Galaxy S I9000 Android Development] renaud:
Note that I have been able to reduce the size by 20% now.
[Galaxy S I9000 Android Development] renaud:
OK, for those that feel brave enough, I have http://www.llorien.org/samsung_galaxys/jpm/zImage-inject_0.1.tar which can be flashed as kernel and mounts /dev/block/mmcblk1p2 on jfs by default at boot time. Of course partition must exist and must be formatted appropriately like it is done by the script http://www.llorien.org/samsung_galaxys/jpm/jfslagfix.sh

Please don't try if you don't understand what the script is all about. I plan to release a user friendly version at a later date.

Note: if the partition is not created, or fails to mount, the system will just revert to the stock RFS on the internal SD.

WARNING: don't flash if the script jfslagfix.sh has not been run or /data won't mount
[Galaxy S I9000 Android Development] sztupy:
Made a bionic port of jfsutils. (although I had to strip some mounting checks the same way as e2fsprogs did). http://github.com/sztupy/android_external_jfsutils
[Galaxy S I9000 Android Development] spoidar:
I really don't understand why you wouldn't just use voodoo as the base, and mod it to use JFS - it has proven migration and an option to disable so that things like clockwork function... make sense not to re-invent the wheel. Sounds like not-invented-here syndrome.
[Galaxy S I9000 Android Development] Arise:
Why don't you make a voodoo version of the JFS filesystem?

And on top of it add your extra improvements?
[Galaxy S I9000 Android Development] SupaDuckie:
is it safe for efs to be on jfs D:
[Galaxy S I9000 Android Development] renaud:
I have discussed this more than once with supercurio. The key is what would you expect from such a move?
[Galaxy S I9000 Android Development] renaud:
Even safer than stock because it is only working with a copy, that means, if you accidentally erase efs with my kernel, it will be recreated (as long as you haven't forcibly crashed the original partition of course).
[Galaxy S I9000 Android Development] SupaDuckie:
Is this file system stable :)?

No blacks out :D?
[Galaxy S I9000 Android Development] renaud:
I haven't experienced the black screen for quite a while if that's what you mean.
[Galaxy S I9000 Android Development] SupaDuckie:
the only thing turning me off from this is cwm :(
[Galaxy S I9000 Android Development] Flozzo:
Is it just me or is recovery not working -XWJS3-;

get a few bitmap errors :S (yes i have searched for bitmap in this topic, but no solution there -few pages back-)

Is there anything I can do about this or should I just give up on this one... :(

Really like the idea, keep up the good stuff!
[Galaxy S I9000 Android Development] Freexter:
i tried this kernel with insanity ROM but it doesnt work, every time after reboot it sais system is inconsistent you need to wipe your data if you do that you get stuck in recovery at data wiping
[Galaxy S I9000 Android Development] SupaDuckie:
should add bootanimation.zip support :D
[Galaxy S I9000 Android Development] Arise:
CWM Recovery, the same framework, easy way to jump from your kernel to other kernels. I often like to test new kernels and features (or revert to a previous one).

JFS support should come as an addon to the kernel. In your case the JFS is the main point and everything spins around it. And this is a "non-standard" way to do it. :D
[Galaxy S I9000 Android Development] phalanger:
Is there a way to revert from this kernel without reflashing the whole firmware?

eg. is it compatible with speedmod? (which has jfs support too i think?)
[Galaxy S I9000 Android Development] joymishra:
Lost my original boot animation. Flashing successful. Definately better performace and Quadrant score than EXt4. Voodoo Sound 3 is awesome!!

This one seems to have better battery life too, although have to check thoroughly but as of now it seems to give me a better battery life.

Thank you so Much!!!! any idea as to how to retrieve the original boot animation???
[Galaxy S I9000 Android Development] rdcosta:
+1

"E:Missing bitmap indeterminate1

(Code -7)".....

add support for bootanimation.zip pls!
[Galaxy S I9000 Android Development] gamin92:
I tried this kernel, and seems very fast. But when I needed to flash a theme I met a wall. I rebooted in recovery, then choose "apply sdcard update.zip" to go into CWM recovery, but the phone frozed here. So no way to go into CWM to flash a theme. Too bad ! Back to SpeedMod till an update...

Thanks for your work, waiting for more !
[Galaxy S I9000 Android Development] renaud:
There is no built in way to revert the changes, I haven't tested speedmod, but as long as it supports having all partitions (efs is not required) on jfs, it should work.
[Galaxy S I9000 Android Development] renaud:
What do you mean by your original bootanimation? The S logo? If yes, that's strange because I only remove the sound, not the animation itself. You should be able to get it back from any custom rom having this animation.
[Galaxy S I9000 Android Development] renaud:
Isn't CWM included in Darkys ROM? I could definitely frop recovery from the ramdisk and let it run from the ROM.
[Galaxy S I9000 Android Development] matticala:
I've been reading all the previous 59 pages with growning interest about this project.

It would be interesting to know how it performs compared to latest btrfs implementations, which pulled ahead of both EXT4 and ZFS on desktop systems
[Galaxy S I9000 Android Development] renaud:
btrfs is hardly usable on the phone as you cannot make a partition smaller than 256Mb, so you would have to either use the external SD or only convert /data. I made an old kernel which supported almost all filesystems on the external SD, and btrfs was a good performer but not by a great deal.
[Galaxy S I9000 Android Development] renaud:
Well, I prefer to do my kernel my way and allow people to rip off ideas. Don't forget that I was the first one to try jfs, the first one to convert /system, still the only one to have /efs on something else than rfs, and the first one to make network stack changes. I just don't want my kernel to be yet another example of what everyone else does, this one is different.

To say the truth, this kernel is definitely not for compulsive flashers but for people who want a responsive system that works and don't intend to flash their phone 10 times a day.
[Galaxy S I9000 Android Development] Flozzo:
Problem is, a non-working recovery is a big problem, really big. Look I like the idea of this kernel, but a failing recovery (missing bitmap stuff) is why I dont use it :$
[Galaxy S I9000 Android Development] Arise:
You are pretty right when it comes to this, but at least you can add CWM support so people could apply update.zip files. Changing files on the /system partition with root explorer is a pain an often leads to FCs that makes everything damn hard and annoying.
[Galaxy S I9000 Android Development] renaud:
If I can get a good CWM binary which works and does not wipe the filesystem, I will put it n the kernel.
[Galaxy S I9000 Android Development] rdcosta:
...please!

i like you project, very interesting!

i will wait for that.... :cool:
[Galaxy S I9000 Android Development] gamin92:
Yes it is. I tried your kernel on Doc's Kitchened rom. But it seems your kernel "replace" recovery, with a buggy one (couldn't flash cwm's update.zip, just frozed).
[Galaxy S I9000 Android Development] renaud:
Well, I don't run the /system recovery by default. The strange thing is that the recovery binary I am using is the same one as all others which use 2e recovery.