yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Daddy_617:
Ok... So I was on the market and found this kernel booster for m3 for galaxy, and youtubed it. It looks really solid was wondering if a dev can look into it maybe it some treasure ;)

Its seems to convert things to ext formats also http://m.youtube.com/index?desktop_uri=/&gl=US#/watch?xl=xl_blazer&v=DJ4XzH1zv7o

Check it out :)
[Vibrant Android Development] blinksilver:
Scratch that, we just crashed. Okay, I think I am done for the day.
[Vibrant Android Development] biigreen:
No problem swyping as fast as I could.
[Vibrant Android Development] velocd:
So I have been up and running without freezing for over 24 hours txting and using swype all day. As I was responding to a post in this thread about what my upgrade path was it froze on me. It was a really long post and it froze on the last word.

Here was my upgrade path though just in case this helps

Odin back to JI6

Flashed Bionix Fusion 1.1 with stock kernel

Flashed the 1.4 kernel in clock work

Rebooted into stock recovery and "installed packages" to get back to CW

Flashed 1.4 script.

I also have a larger NAND

Outside of freezing I noticed that my battery is draining a little faster than normal. Anyone else notice this?

Again it did not freeze until the end of typing what I would consider a long post.

I am going to continue to use this since it worked all day long texting without freezing. The phone is actually running the way it should be and I dont know if I could take it going back to stock.
[Vibrant Android Development] geoffcorey:
So it just froze on me when I went to type a text as the HTC_IME keyboard was popping up. Before then, it froze on Pandora almost instantly, (but didn't happen after I restarted. Pandora lasted forever) I went from almost no use of the phone to waking it up to text and it froze.

I love this mod but I'm worried about relying on my phone as a daily alarm with this mod.

:-(
[Vibrant Android Development] mafaesto:
I'm having the same sorts of issues, it will freeze randomly without any specific pattern to it. I started with 1.4, and it froze while sleeping after I got a text. Then later on that day while I tried accessing an app, and again after a reboot while trying to access the home screen. Sometimes it just flat out won't respond but I know its working because I can see the symbol that flashes (flashing on and off).

This is a little over my head, but TO ME this seems to be load related, with no specific timing to it or reason. I had even turned the cpu clock down to 100 MHZ to see if maybe I could get it to not lock up (yes obviously gonna be laggy) it again locked up.

Not to mention, I was trying to do the steps to get 1.5 working and it would lock up while converting /data when it was very close to finishing.

I hope this helps. :P
[Vibrant Android Development] gehzumteufel:
Yeah, this is why I haven't done this mod yet. It is promising, but there is something wrong.
[Vibrant Android Development] VICosPhi:
Ryanza is going to post the updated script to patch the kernels. It shouldn't be too long then we can use any zimage and get it patched. Atleast this way we'll have more options...right now only ttabbal is working on it...hopefully more developer start working on this....
[Vibrant Android Development] ttabbal:
I wish I could reproduce it, but haven't been able to. I even tried the swype test. I sat there for 10 min or so scribbling on swype in the stock browser.

My current setup.

Fusion 1.1 w/jac non-voodoo kernel (the others should work as well)

1.6 kernel

1.5 z4mod

About 85 apps restored via titanium.

The freq_volt_table posted in my kernel thread.

I just remembered I also flashed the JI6 modem. That shouldn't matter, but to be complete I should mention it. I also have the large nand.

Battery use seems a little higher on this latest version, but that could just be my changing the governor settings to make the cpu scale up faster. It could also be that I haven't "conditioned" the battery since the last flash. Could also be the JI6 modem. Or just me fooling with the phone trying to crash it.

I haven't tried pandora but jam11 and slacker work well. I'll download pandora and try it.

Just wrote this post on my phone w/swype in tapatalk. No problems.
[Vibrant Android Development] ttabbal:
For those with issues, try deleting some or all of the init.d scripts. they just try to boost performance a bit and might contribute to problems. Just throwing ideas out for people to try.
[Vibrant Android Development] Ashex1:
If anyone is running LauncherPro can they try backing up their settings? For some reason when I convert all the partitions (this was occurring yesterday when the conversion failed spectacularly) I'm unable to backup the settings in LauncherPro or send out an update with Tweetdeck.
[Vibrant Android Development] blinksilver:
Found it! Its the 1ghz CPU state, the voltage is wrong or something.

If you want a quick test, run setcpu and set max CPU speed to 800mhz, and torture your device. (The swype test in landscape is a good start)
[Vibrant Android Development] geoffcorey:
are you sure it's the 1GHz state? i just flashed the rfs convert back script and was going to run back at stock (and see what is working with patching the JI6 stock kernel in the online z4mod patcher later) for a while until there is a fix found. I think i'll try running w/ setcpu @ 800 for a while and see if i get the errors.

I did notice that the lockups seemed to be similar to me running the 1.2 OC/UV kernel where it appeared my phone could handle the OC, just not the voltage setting. I'll reflash back to ext4.

Is there a script for init.d to set max cpu_freq to 800MHz? i'd rather not use setcpu if i don't have to (heard a lot of media troubles w/ setcpu and kernels).

EDIT: i'm trying a modified OC script from JAC to set max cpu_freq to 800 MHz.
[Vibrant Android Development] blinksilver:
Does the jacs script actually work?
[Vibrant Android Development] geoffcorey:
nah, it didn't work for me. so i pulled the cpuinfo_max_freq and the scaling_max_freq and edited it to 800 MHx. testing it right now to see if it worked.

EDIT: damn, that didn't work either.
[Vibrant Android Development] blinksilver:
I have been trying for hours to overclock to 1.2GHz, no luck(worked fine with JACS and KK). There is something wrong with the way this kernel handles speeds of 1GHz or greater.

If you remove the 1Ghz state, everything is okay. If you try to add in 1.2Ghz state, it hangs at media scanner. If you try to do both, you will get a no boot, or the same behavior as you would get if you added in 1.2GHz state. The problem is mostly likey not a side effect of the CPU governor, I used setCPU to change it and still see the same behavior. On a side note, undervolting does works well.

Also, I tried removing all the the scripts in /system/etc/init.d, nothing really happened. Well, my Quadrant score went up(by a 100 point, if you add in the other 100 I get from overclocking the GPU I am seeing quadrant scores as high as 1776. Which is another great reason why I want this mod to work). So while the scripts were not the greatest performance hacks, they are not the cause of the problem.

Also #2, the fact that the phone hangs when you add in the 1.2GHz state to voltage table implies that the code used to limit the startup to 1GHz maybe borked, perhaps that is the problem?

Also #3, The big mystery in all this is: Why does it not hang when I run quadrant a whole host of times, or when I use the setCPU stress test? why does it only hang when something like swype goes heavy on the CPU, and why only at 1GHz? I have even tried to isolate it. Using setCPU, I made the max and min freq = 1GHz. It, as expected, hangs the phone when I run the swype test. Same setup with max and min set to 800Mhz and all works well.

Any more ideas?
[Vibrant Android Development] kas21:
lagfixes

So, just wanted to throw this out and see if anyone had any thoughts about it.

I have used many of the lagfixes over the months of owning my Vibrant. I have used a symlink of data to dbdata (nand), OCLF v1, v2, Voodoo, and now this ext4 fix for all partitions. For the most part, all have been pretty equal, IMO, while using it for most apps and activities, however, I am a heavy Touchdown user and this app is very sensitive to the performance of the filesystem. Touchdown is basically my benchmark based on perceived performance versus benchmark numbers like Quadrant.

Out of all the lagfixes, the OCLF versions are the ones that always give me the best (perceived) performance while using TD. I can bounce in and out of emails without any lag, while this fix and Voodoo tend to hesitate a bit more while loading up emails. I would imagine this activity is mostly a read activity with maybe a small write to "mark the message read" in the database. Does anyone know why that is? It's hard to use something more stable like this current fix when the OCLF performance noticeable better.

(I have never had corruption issues with OCLF but I have heard that the risk is there)
[Vibrant Android Development] zenlakin:
Anyone using any lagfix with any of the Froyo ROM's that are currently out right now?
[Vibrant Android Development] geoffcorey:
voodoo flashes a new kernel which messed up the key mapping and audio issues. This doesn't work because a) it's a 2.1 kernel in this thread and b) the z4mod patcher breaks power button in recovery.

The only thing that is really working (to my knowledge, haven't really looked into it) might be the OCLF. It might bork your phone though.
[Vibrant Android Development] ttabbal:
The types of tweaks don't really help with anything a benchmark will see. They are more about smoothing performance during use. Things like changing how fast the cpu speed scales up/down and such. Also, take benchmarks with a grain of salt, a spoonful on Android or any VM based platform. There are far too many layers between an app and the hardware to really reliably benchmark anything on Android.

OCLF will be a little faster as it uses ext2 which has no journal to keep up with. You can easily modify my ZIP to use ext2, there's even an example as that's what /cache is on in the latest version. Data loss is much more likely on ext2, but only as a percentage really. The difference is vanishingly small, I just like the extra reliability of journaled file systems. There's also the fact that the type of corruption you experience on ext2 will be random, while ext3/4 will protect the filesystem structure with the journal. You might still lose data, but the filesystem is less likely to be rendered unmountable. OCLF also uses a loopback filesystem, so you have 2 filesystems worth of buffering, basically a larger cache. It also means 2 places for issues to cause data loss, so pick your poison.

IMO, when we get the stability issues worked out, we can tune the ext4 settings and the kernel I/O settings to try to get more performance out of it. That's also the reason I haven't been messing with OC much, I want these stability problems worked out first. I might revert the OC/UV code from Unhelpful and go back to Samsung defaults. It's possible this is caused by a bug in that code. It doesn't seem to cause problems for Captivate users, but it won't be the first time I've found problems with Captivate patches on Vibrant. If that works, I can port KK or JACs patches over, the ones that they publish anyway.

The thing that has me scratching my head is that some people are fine with the existing setup. My phone is VERY stable and I've been beating the hell out of it trying to reproduce the problem. With the same hardware and software, one would expect similar results. Could just be minor differences in the CPUs I guess, much like how some people can OC and some can't.
[Vibrant Android Development] dsellers2:
Looking forward to a stable release. I have been playing around with the voltage levels most of the day today, but have not found one that solves the issue.
[Vibrant Android Development] geoffcorey:
Right now setting setCPU to 800 has the most stability for me. So maybe a bump in the voltage for 1 GHz might do the trick for people with stability issues there.
[Vibrant Android Development] ttabbal:
http://www.tabbal.net/files/Kernel-ttabbal-v1.7.zip

OK. The only change here is STOCK clocks/voltages. I reverted to Samsung released source for CPU/Clock/Voltage related files. It's running fine on my phone, but I haven't been able to reproduce the crash on my phone anyway, other than when trying to go above 1Ghz. I was even locking the phone to 1Ghz and running fine. I tried the swype test, and a large download just to stress wifi/I/O. I've got a game running now, Dungeon Hunter. The CPU Benchmark app's "Stress Test" has also been running for a while now, didn't check the start time on it. 100% CPU use, 1Ghz. I've also got the media scanner running to hit the SD I/O. Oh, and I just started up Pandora. Might as well have some tunes while I stare at the phone screen. :)

Those with issues, please let me know if this helps or not.
[Vibrant Android Development] geoffcorey:
Thanks for this. I'll test after my math midterm.
[Vibrant Android Development] gehzumteufel:
You seem to be pretty knowledgeable, but are you aware of how CPU clocking and yields work? (This applies to pretty much all computer related silicon yields)
[Vibrant Android Development] rogerchew:
other than today on the road, where my gps was completely borked (it was literally 10 miles off and said locked, it corrected itself later when i got to another area), my phone has been running great. did the swype test multiple times and could not lock it up. running 1.5 for about 24 hours now.

edit: just flashed 1.7 and tried the swype test again. no issues either.
[Vibrant Android Development] blinksilver:
Moneymaker. This solved the problem!

As for the overclocking code might I suggest having a talk with team whiskey and getting your hands on this:

http://xdaforums.com/showpost.php?p=8844947&postcount=41

Or perhaps showing off your now stable zmod for the Vibrant, and seeing if they will toss it into their kernel?

Good work man.
[Vibrant Android Development] gregc2009:
Working here too. I would freeze within 2 minutes every time before.

Going to convert to ext4 now to see how it goes.

Thanks!
[Vibrant Android Development] dsellers2:
Sweet, awesome job ttabball. This thing is running like a champ! Problem solved and better than any lag fix out there for sure....
[Vibrant Android Development] gehzumteufel:
Since it appears it was related to voltages/clocks, here is my take on why it happened.

In basic CPU yield and clocking, what they do, is test a few CPUs from every batch. Where ever these clock stably, is where they will set the clock. Some CPUs are perfectly fine (ttabal and a couple others) at the settings that were modified, but others (dsellers, Vic, blink, roger, etc) were ones that had CPUs that while they are fine at stock voltages, they aren't at non-stock when operating optimally. As a result, this instability is what happens.

This is why you can OC some CPUs, even of the EXACT same model and from the same lots numbers, to different extremes. It is just an unfortunate side effect of silicon manufacturing.
[Vibrant Android Development] dsellers2:
Would your logic apply even though when I'm on Jac's oc/uv and using set cpu I set to 1200 and have no issues at all.

Ttabbal,

Where did the Volt_Freq_Table goto in the cpufreq folder? I wanted to take a look to see what the setting were. Or, is it that when on stock they are a constant and does not need a lookup table?
[Vibrant Android Development] gehzumteufel:
Did JAC and King Klick use the same values? I don't know, but I presume that they may use different values. I have no clue.
[Vibrant Android Development] rogerchew:
it would be logical that they would use different values, cause otherwise why would one be more preferable over the other if they are both the same? your analysis looks to be the culprit because we can't assume TT's values were the same as JAC or KK's.
[Vibrant Android Development] Ashex1:
Flashed 1.7 and everything is still stable. Currently running Stress test to verify. The Tweetdeck issue resolved itself, I'm suspecting both issues were due to a stale cache but I can't confirm with LauncherPro as it's behaving a bit oddly (different issue)
[Vibrant Android Development] rogerchew:
this is a stability unrelated question, but more targeted at dseller2 and blink who flashed MANY times already. Does a kernel need a reboot after each flash or can you flash multiple kernels in succession without rebooting?

for instance, can I do

flash kernel back support -> flash TT 1.7 -> reboot

or does it have to be

flash kernel back support -> reboot -> flash TT 1.7 -> reboot

thanks for any answers.
[Vibrant Android Development] geoffcorey:
if you're coming from JI6 with the stock JI6 kernel, you'll need to flash the kernel back support first, then flash a JFD based kernel. If you reboot in between, you'll be stuck at the vibrant boot screen.

so yes, flash in succession.

BTW, the back support doesn't have a kernel, it's just libs to support the older kernel.
[Vibrant Android Development] dsellers2:
delete. Because I have to have 10 Characters I'm typing this.
[Vibrant Android Development] dsellers2:
Here was a installation instruction or how I install TT's mod. You may be doing something different than me but your def need to reboot after installing TT's kernel, then you can install the Z4mod.
[Vibrant Android Development] biigreen:
These are the steps I followed to a T and had no issues.
[Vibrant Android Development] ttabbal:
Yep. I was under the impression that Unhelpful's code defaulted to stock values, and that's what the source seemed to be doing, but there is obviously something different as when I reverted the changes he made people started working properly. At least we figured it out.
[Vibrant Android Development] ttabbal:
Yep. I'm already talking with them. Hopefully I'll get my hands on source today so I can start porting the changes over. It shouldn't take too long once I get a good build. I don't see any reason to duplicate effort. They seem to have overclocking handled, so if they are willing to work together, I certainly am.
[Vibrant Android Development] ttabbal:
That was one of the mods that came from Unhelpful's code. It was removed as part of the revert. I happened to pull a table yesterday, this is what was in there.

1000000 200000 1275 1100

800000 200000 1200 1100

400000 200000 1050 1100

200000 200000 950 1100

100000 100000 950 1000
[Vibrant Android Development] blinksilver:
I do:

flash kernel back support -> flash TT 1.7 -> reboot.

it really doesn't matter with Eugene back-ports since they include JFD kernel. However, if you use the one I linked, you have to do it this way, Since no kernel is included and the JI6 kernel will probably hang with the back-ports installed.
[Vibrant Android Development] ryangera:
Love to see this as part of the Bionix movement. Props to all devs, you have my respect and gratitude.
[Vibrant Android Development] gehzumteufel:
Cool, just figured I'd ask. Good between you and blink for figuring it out. Now we can have a full on ext4 based system, and no more bull**** RFS.
[Vibrant Android Development] aloxotls:
I am having no issues since 1.7 great work. I converted /data /dbdata /cache and /system over to ext2 and so far running great with a 1835 quadrant.

Great work ttabbal!
[Vibrant Android Development] ttabbal:
Most excellent. I'm glad to see it works for you, you were able to reproduce it easily. :)

You converted /system? Does market work? I might have to try it again just to see.
[Vibrant Android Development] gehzumteufel:
That is the only other thing I am waiting for.

Also, while I have been following the thread, where do I get the backports libs?
[Vibrant Android Development] ttabbal:
http://xdaforums.com/showthread.php?t=796425
[Vibrant Android Development] geoffcorey:
There is one thong I've noticed about the 1.7 kernel. It's acting almost as if I haven't applied the z4mod yet.

I've checked using the mount command and they are ext4. But it lags (especially when installing from market).

I'll try a fresh install tonight and see if that fixes it.
[Vibrant Android Development] mafaesto:
Honestly I noticed the same thing it seems to hang when converting to ext4 for me. It converted successfully but, I'm having the lag you've mentioned. I have a smaller nand as well.
[Vibrant Android Development] aloxotls:
So far market is working I restored all of my apps and then updated all in the market and downloaded angry birds without a problem.
[Vibrant Android Development] dsellers2:
There is a little bit of hangs up off the market, but nothing like stock. It is also moving a little slower after changing the clocks and voltage, it still feels faster than Voodoo and touchdown, sms, and google voice is launching very fast. I'm sure once TT gets the OC/UV figured out with out the freezing it will really be flying.
[Vibrant Android Development] blinksilver:
Mind posting the ext2 scripts you used?
[Vibrant Android Development] kas21:
What was the reason for going with ext2 on /cache? Just curious because I am currently running all partitions formatted as ext4 and I am trying to determine if I should convert /cache to ext2.
[Vibrant Android Development] rogerchew:
sounds like ttabbal needs to get a ext2 version and ext4 version :p

thanks for the awesome work!!!
[Vibrant Android Development] aloxotls:
Here is what I used. It is just ttabbal mod and I edited the updater-script file to format to ext2 instead of ext4.
[Vibrant Android Development] dsellers2:
Do these work when installing over ext 4 our does it require going back to rfs first? Tt latest doesn't require you to convert back to rfs.
[Vibrant Android Development] blinksilver:
Thats what i figured, i really like the idea of system being ext2, seeing as it usually not being edited and hence data corruption is less of a worry.
[Vibrant Android Development] aloxotls:
I do not know I tried it with ext4 and then used Odin to go back to stock before converting to ext2.
[Vibrant Android Development] dsellers2:
Which version of tt file did you mod? That will tell us.
[Vibrant Android Development] blinksilver:
Market works fine here as well.

So now I have system and cache as ext2 and data and datadb as ext4. This is pretty ideal in my mind.

I'm finally free of that dreaded RFS. My quad score is now 1785 on a completely stock JI6 with the Z4MOD, that is twice what I scored with the same configuration on RFS. Who was smoking what at Samsung?

Now how about a 1.6Ghz kernel? Any takers?
[Vibrant Android Development] geoffcorey:
just a quick question. When ttabbal posts a new kernel, do we have to go back to rfs, reboot, then flash new kernel, then reboot, then go back to ext4?

that's what i've been doing and with the 1.7 kernel, i've noticed insane lag (which is weird, it shouldn't be there) even when getting 1 text. i'm going to start fresh again and see if that helps.

Also, i like the 1.6 kernel the most and dropping down to 800 MHz doesn't bother me. I'm going to see if i can edit the 1.6 voltage table and change the voltage for 1GHz to see if i can get stable.
[Vibrant Android Development] gatesmarch123:
Ttabbal,

Whitehawkx had mentioned someone over here was working on a fix with the power button issue on Eugene's Froyo Rom...can you confirm this? Thx.

Sent from: my Vibrant juiced with Eugene's 2.2 Froyo JPM
[Vibrant Android Development] rogerchew:
what was the significance of converting /system again? I totally forgot the reason why tt left it out.

another question regarding backups. after converting, can we nandroid properly or do we have to revert back before nandroid? or do we just have to prep the file system to whatever the nandroid backup is using before restoring?
[Vibrant Android Development] aloxotls:
I am using the 1.7 kernel
[Vibrant Android Development] kas21:
ext4 tweak

/data type ext4 (rw,noatime,nodiratime,barrier=1,nobh,data=writeback)

If we are in writeback mode, do we need barriers? Also, ext4 does commits every 5 seconds by default. Any performance gain in upping this and reducing commit frequency?