yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] rogerchew:
i've just been flashing his kernels on top of whatever i have. it's been working fine for the most part *knock on wood. but to caveat, i was fine on 1.5 and flashed 1.7 just for kicks, so whether the changes took or not, i have no idea. :D
[Vibrant Android Development] blinksilver:
I never had the ext4 version booting, but those who did apparently had issues with the market. This does not seem to be the case with an ext2 /system. As for why we should convert /system, well RFS sucks. Even if most of its suckiness is due to its slow write speeds, its read speeds are still not that great. They are just more bearable than the write speed. This way, we are done with it and can function like a regular linux system.
[Vibrant Android Development] geoffcorey:
thanks. i'm going to try the JPM mod froyo for a while. i'll probably come back to the z4mod later.
[Vibrant Android Development] ttabbal:
That's the kind of stuff I was planning on looking into before the stability issues.

I do have system on ext2 now, market works. I haven't been able to convince it to mount with noatime, but relatime is the default, and it's not so bad for now. Oddly, the script to mount it correctly works in shell, just not at boot.

The phone seems a little snappier. And it's nice not to have rfs.
[Vibrant Android Development] rogerchew:
got the script to run through shell? just tried using the .zip posted above but got a brick (froze at vibrant screen)
[Vibrant Android Development] geoffcorey:
alright, so JPM had market issues i didn't want to deal with so i'm back at JI6.

can someone tell me what each column is for in the volt table?

thanks!

Also, if i edit the volt table, will the system follow the edits or is that stuff to change in the kernel itself?
[Vibrant Android Development] dsellers2:
So this happened last time I converted my system file to extension 4 but noone else had the issue. I've lost root, but at least the market works this time.

Now converted system to ext 2 and I've lost root again after a fresh install through odin.

So market works but, titanium and root explorer does not work. Su in terminal emulator results in access denyed.

Trying to re root with the update zip file seems to install but still no root.

What's strange is I can still get into cwm.

Any ideas? Are there any scripts to revert system only back to rfs so I can see if I can gain root again?

Is any one else having this problem? Everything else seems fine.

Since it has happened twice to me after an odin do you think I'm doing somthing wrong during install? Im sure im installing correctly.

I just don't know.
[Vibrant Android Development] scrizz:
install SGS tools and root with that
[Vibrant Android Development] blinksilver:
You can also try the one click root application. That is what I use, I've never had an issue with It. Good luck.
[Vibrant Android Development] scrizz:
I think that's what i meant.

LOL
[Vibrant Android Development] gehzumteufel:
Someone had previously said that root explorer doesn't work with ext4 FS. So that could easily be a problem.
[Vibrant Android Development] Ashex1:
I just ran Quadrant benchmark against the 1.5 and 1.7 kernel.

1.7 Kernel: 1644

1.5 Kernel: 1707

I ran each benchmark by flashing the kernel zip then killing all userland processes with Astro after a fresh boot prior to it.

Even though the scores are almost identical 1.5 feels a bit more responsive.
[Vibrant Android Development] Keslynn:
I just installed the mod (1.7 kernel) on a fresh flash of Bionix Final. All I can say is WOW! My phone flies. I have the larger NAND and a Mac so until now, ext4 goodness was out of my reach. Thanks, ttabbal for your hard work making this awesomeness possible!
[Vibrant Android Development] geoffcorey:
Alright, so i started fresh this time (i suspected that the continuous flashing revert, flashing kernel, flashing convert script for each kernel release caused file corruption cause i was experiencing stuttering like no other), and all i can say is peiece of mind. the phone works perfectly, and haven't had any lockups or lag.

thanks so very much for the hard work ttabbal!
[Vibrant Android Development] gehzumteufel:
That is because the clock/voltage stuff is different.
[Vibrant Android Development] Ashex1:
I'm aware of that, I just found it interesting that despite the changes in cpu clock/voltage the benchmark scores were almost identical.
[Vibrant Android Development] geoffcorey:
alright, can someone help me with the voltage file?

I know that the first column is frequency. What are the other columns?

Also, are the voltage settings.dependent on the source that's compiled or can they be changed later/
[Vibrant Android Development] gehzumteufel:
The second column is the minimum frequency. Or at least that is what it appears to be. The other two I have no clue.
[Vibrant Android Development] Shane_pcs:
First in either Terminal or ADB shell

Code:

cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size

Then take the output of that and multiply it by 512. If it comes out to "16005464064" Then beta4 will work for you. If you end up with a value of "16441671680" then you have the 416MB larger NAND chip and will need to wait untill beta5.

Copied from older post.
[Vibrant Android Development] dsellers2:
That's great news fast kat. I didn't have any luck with jacs kernel. The web ui gave me a return code 1 after trying to package. I hope they convert all folder soon.
[Vibrant Android Development] Ashex1:
I patched the JI6 kernel and converted data to ext3. So far everything is running very well. I'm going to try converting /cache later to ext3.

Edit: Converting /cache doesn't work, I'm assuming it's because either CWM uses it or the z4mod script mounts it.

Edit Edit: Converted /dbdata and while it successfully converted it, it is not mounting at startup. I updated the rc files and even added a script in init.d to mount but it still fails.
[Vibrant Android Development] stephenj37826:
Oh I goofed didn't flash the right kernal and now I've lost root. Any ideas? I can get into stock recovery
[Vibrant Android Development] wildklymr:
Have you tried re rooting?
[Vibrant Android Development] stephenj37826:
Yeah I re rooted I had to re root again after I went back to rfs as well
[Vibrant Android Development] swehes:
What exactly is a large NAND chip? What is the NAND chip in the first place? And how do I find out if this is what I got?

Also on a different note. What is Trolling? Or to troll? How is it properly used?

Thanks. :)
[Vibrant Android Development] Master™:
If you looked a couple posts above you then you would know :)
[Vibrant Android Development] swehes:
Got the 16005464064 so I'm good. However, is there someone who can explain what NAND is in layman terms? Googled it and it is slightly more technical than I would like. See that it is a Flash memory.

Thanks
[Vibrant Android Development] imthekuni:
the JI6 kernel does not support ext3 off the batt does it? when you say you convereted /data to ext3 was that with the update script in the other z4mod thread?
[Vibrant Android Development] Ashex1:
That's basically it, it's a non-volatile flash memory.

So far so good running ext3, I'm not sure if this is related but all my photos were deleted while working on this, I did have to do a full restore to undo converting /dbdata so something might have misfired during that process.
[Vibrant Android Development] rogerchew:
anyone got a link to just the stock JI6 kernel so I can try this as well? I too have the larger NAND and would like to try this on ext4
[Vibrant Android Development] Ashex1:
Grab the JI6 odin update and pull it out of the tar file.

Nope, that's why I patched the kernel. Additionally as the OP states I converted /data using the z4mod update script.
[Vibrant Android Development] rogerchew:
would love a small tutorial or some steps to do this =)
[Vibrant Android Development] Bernardos70:
Subscribed. This is exciting!
[Vibrant Android Development] Segnaro:
Here's a prepatched Z4mod JI6 kernel. Flash with Clockwork Recovery.

Then flash one of the z4mod update.zip variants from the original thread with Clockwork Recovery.
[Vibrant Android Development] rogerchew:
you're the man! thanks!
[Vibrant Android Development] rogerchew:
what's the difference between using this and going ext2 vs using one click lag fix?
[Vibrant Android Development] scrizz:
this gives u more space and is faster

;) :p
[Vibrant Android Development] FastKatt:
Native ext2 instead of ext2 on RFS. This eliminates space constraints. It also allows the device to natively represent available space rather than using a script or the OCLF tool to check it. I suppose it may be slightly faster though I've done no testing to confirm this. It probably wouldn't be enough of a difference to matter other than in benchmarks. I'm more concerned about user experience and I can say that my phone had never been this smooth and responsive.

I'd like thee option to use ext4 but I haven't had good luck patching a kernel that has ext4 support built in.
[Vibrant Android Development] blinksilver:
cpufreq gpufreq vcore icore
[Vibrant Android Development] dsellers2:
Ive tryed both. What's strange is super user is still installed just won't open (force close) and I can't uninstall it. I found out busy box is not installed as well. When running logcat I get an error saying

Java io pipe broken.

Along with other warnings.

I guess ill just odin back to stock
[Vibrant Android Development] aloxotls:
I was able to convert my system back to rfs with this. The only problem I had with an ext2 system is I could not flash the I9000 camera through clockwork. When it tried to copy the app into the system/app folder it failed. But I never have any problem with being rooted once I was in the OS.

I just converted everything back to rfs to check out the Manhattan kernel. Cannot wait until I can get rid of rfs and oc to 1.6+!!!!
[Vibrant Android Development] dsellers2:
I guess third time is a charm

After my third time of odin'ing back to stock and repeating the install process I was finally able to convert ext2 for all folders without issue. ;)
[Vibrant Android Development] geoffcorey:
Alright, one more question about messing with the voltage table.

If i were to edit the voltage table, would the system accept the settings? do i have to change voltage levels in the kernel source and then compile or if i edited the voltage table file for the 1GHz vcore, would the system use that value?
[Vibrant Android Development] ttabbal:
You can open that file with a text editor on the phone and when you save it the kernel should update itself. I added a 600Mhz step and it showed up fine. adb push also works.
[Vibrant Android Development] ttabbal:
Yeah, the update-scripts tend to assume the recovery will just mount the partitions properly, and the recovery only knows about the stock layout. I should probably just grab the Clockwork source and make it try different mount commands.

I'm working with the Team Whiskey guys a little on kernel related stuff. Hopefully they will either port my stuff over or let me have early access to source so I can do it ahead of the main release. If not, I'll just wait till they release source, as they assure me they will. They do plan to implement z4mod support into their kernel though.
[Vibrant Android Development] Keslynn:
I searched but alas, could not find what I was looking for. My question:

Is the backlit buttons notification built into the kernel or is it one of the init scripts? I love the mod but I don't like the button light notification and was wondering how I might go about removing it.

Thanks!
[Vibrant Android Development] ttabbal:
Push a stock /system/lib/hw/lights.default.so from the ROM you were using. That will disable the backlight notifications.
[Vibrant Android Development] dsellers2:
Looking forward to this as well, but hopefully the 1.6 mod will not be like that out the box. So the user s can enable our disable depending on our phones can handle those clock speeds.
[Vibrant Android Development] Bernardos70:
OK, so I haven't kept up with this for a couple of days, as I've been very happy with how the phone is performing. I'm still rocking Segnaro's patched JI6 kernel (which he posted on page 7) and the original Z4 script. The original patcher, as I understand, only changes the kernel so that it is able to use ext2 on /data. Would anyone know this for sure?

I would love to convert /cache to ext2 as well while keeping JI6 (which I understand ttabal isn't interested in doing since he doesn't have the source). The process seems like it became very contrived and this is my daily phone, I usually only go with surefire things as I cannot be without the phone during the day at all.

What I'm basically looking for is a way to patch JI6's kernel to be able to use ext2 on all mounts (except system, for the sake of simplifying), a script to convert to ext2. I am comfortable with using these conversion scripts, Odin, and all that, but I know diddly squad about linux or programming. I can read VERY little code. So that's what I'm looking for right now.

Maybe this will get me into programming, who knows? :D
[Vibrant Android Development] geoffcorey:
thanks ttabbal for all your work on this.

With my new and fresh setup, i flashed the 1.7 kernel, did the convert, then flashed to the 1.6 kernel. I think it seems pretty stable (i did get swype to crash it though, but it took a LOT for it to crash the phone). I really like the response and feel of my phone.

I love my phone more now than when i bought it! (and that's saying a lot) :D
[Vibrant Android Development] ttabbal:
Glad to hear it's working well for more people. Is there some reason you downgraded the kernel? Just wanted UV?
[Vibrant Android Development] geoffcorey:
I down graded because it "feels" snapping for some reason. Right now, I'm running the 1.6 with setCPU set at 800 because 1 GHz just froze. I'll flash back to 1.7 and test how that goes with my fresh setup for today.
[Vibrant Android Development] sknobs:
Anyone tell me if this looks right???
[Vibrant Android Development] rogerchew:
that looks right. you got /data /dbdata and /cache all on ext4.

my /cache is on ext2.

run a quadrant bench, see if you're somewhere in the ballpark of ~1600
[Vibrant Android Development] down8:
1900-ish with just a root and z4mod.

EDIT: ext2, btw.

-bZj

_____

-sent from my Samsung Vibrant via XDApp
[Vibrant Android Development] Ashex1:
My brother was curious how the z4mod turned out so I made a video and posted it on youtube.

See it here.
[Vibrant Android Development] jzero88:
This is a beautiful beautiful thing. Kernel is working great with ext2 right now only on /data. I do notice however that using stock kernel does drain battery quite quickly.

Wouldn't mind seeing a post or the original with an updated howto. That way for me and others dont have to spend an hour plus reading through posts to get it right :)

then again, where would be the fun in XDA :D
[Vibrant Android Development] dsellers2:
Ttabbal,

Out of curiosity, I created the config folder in my external SD card and threw this volt table in there. And I'm not sure if this is a placebo effect or not but I know this phone got way more snappy. It now feels like your earlier Kernels without the Swype crashing.

By the way, with the latest kernel you had Wake lag. Now, no wake lag.

My question is this all in my head? When you put stock values in for 1.7 did that hender the Config folder useless? Or, is the volt table being used on the sd card even with the latest kernel?

Either way my phone is feeling twice as fast without the Clock/Volt table and quadrant is showing and increase of 250. Went from 1600 to 1850.

:)

Maybe we should keep the table in the CPU Freq folder? What do you think?
[Vibrant Android Development] kangxi:
Yes, I think you need a separate thread with clear instructions that also let's you post updates to the op. Shifting through a bunch of posts to find instructions or even the release is why people end up just asking a bunch of questions.

That video was awful with the annoying music and someone teach this guy to use the back button to properly close apps.
[Vibrant Android Development] ttabbal:
Quite probably. :)

The config folder does get read as the script is still there, but the destination it writes to doesn't exist, so it can't do anything. :) That's why I posted it, someone wanted to see what we had before the stock changes.
[Vibrant Android Development] dsellers2:
Well ****, I thought I was onto something. Thanks for the clarification. :D
[Vibrant Android Development] dsellers2:
Do you think the SWYPE crashing problem will come back if you put the table back in the sys cpu folder? I'm curious? I want to try and put the file directly in there myself but dont know if it will make a difference or even keep my phone from booting.

Can you elaborate and let me know if this could work?
[Vibrant Android Development] Ashex1:
Eh, there was silence so I had youtube drop one of it's song on top. I'll see about changing that out with a less annoying song if that will please you.

And the entire point of the video was to show that lack of lag when running multiple apps which you know, is sort of the whole advantage of using z4mod ;)
[Vibrant Android Development] kangxi:
I think it would be much better if you just talked and explained what you were doing. If you don't have a microphone, I understand. And I mentioned the back button because I did notice some programs taking awhile to start up, which could be attributed to not properly closing the apps. Z4mod does make the file system better, but it does not manage your RAM or CPU stress. Completely different things.
[Vibrant Android Development] Ashex1:
I understand what you mean, I made the recording using my Nexus One so I may make a new one tonight with proper narration. That is a good point, the phone was just starting up so there was additional lag. I probably should have avoided launching the larger apps but you should remember that if I were doing this without a lagfix the phone would have locked up within the first 30 seconds.
[Vibrant Android Development] kangxi:
Yea no prob. I just tested it by opening up 16 apps and the phone started to become very sluggish. So while changing to EXT2/3/4 is a godsend, it still can't replace proper app management. I probably wouldn't been able to get that far with the stock system though so you are correct.
[Vibrant Android Development] rogerchew:
you talk about proper app management, but isn't that completely on the OS, there's nothing we can really change to make sure there's "better" app management short of upgrading the OS right?
[Vibrant Android Development] down8:
Closing apps with the Back button is "better" than hitting the Home button.

-bZj
[Vibrant Android Development] Ashex1:
Do we need to start including a newbie guide in each thread? Or is it just the lack of a good FAQ that is causes people to ask all these basic questions?

Anyways, after a full day with this fix I have this to say:

Lag is virtually gone

I've activated multiple widgets and been able to scroll freely without lag, able to open an app up and press buttons without it locking up. Additionally start time has improved significantly, within seconds of the home-screen loading widgets start loading, this is without modifying startup via the autostarts app (disabling services from being triggered at startup). However the wake lag is still present albeit not as bad as before. One thing to keep in mind is that /dbdata is still rfs so anything that accesses a database such as messaging will lag but should only be on first launch as after that it will be cached.

Battery life has improved significantly

After I applied the JI6 stock update to my phone I had constant problems with battery drain, at work I plug the phone in every 30-45 minutes for a quick charge and despite that at the end of the day when I left work I had a 30% charge meaning some days my phone was dead before I got home. Today the battery didn't drop quickly and for once was at full charge when I left work.

Wireless/Toggles activates much faster

Previously with JI6 stock it took a minute or so for the wireless to connect after being activated, now it activates and connects within about 15 seconds.

Regarding ext2 vs ext2 on rfs. With ext2 on rfs it's a partition inside another partition, think of it like running a virtual machine on your computer. Notice how the system doesn't run as fast as it would if it were actually installed on the computer outisde the virtual machine?

This is because as the virtual machine writes data to it's virtual partition, the virtual partition hosted on the computer is also being modified so those changes have to once again be written to the hard drive, meaning you've got duplicate writes.

It's a bit more complicated but that's one way to think of it. Once you eliminate that virtual partition and use a native one, read/writes become even faster as you don't have to deal with the double-writes.
[Vibrant Android Development] FastKatt:
I haven't noticed any wake lag. Is it all the time or just with certain apps left open?
[Vibrant Android Development] Ashex1:
It's very very minimal, I would say just with certain apps open. I've had it happen when I'm using an app and I let it go to sleep, the one I noticed it most with is Kindle.
[Vibrant Android Development] rogerchew:
thanks guys for the responses regarding the one click lag fix (ext2 inside rfs) vs native ext2. it makes a lot of sense now.

i noticed ashex1 is running ext3, fastkatt you're running ext2. Any reason why you chose ext2? is the stock kernel more supportive of ext2 than ext3? from what i'm reading ashex1 is experiencing wake lag on ext3 while fastkatt you're not?

gonna disable the one click lag fix and test this out using the stock modified kernel that was posted here. on another note, how did you guys get your kernels? extracted it manually yourselves?
[Vibrant Android Development] es7241:
I did the automatic z4 mod as it chooses the most fit for me , but is there a way to find out what file system I'm using?

But either way the phone is running faster than I've ever seen it before even if it was over clocked with voodoo or oclf