yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] dsellers2:
ok looks like everything converted with 1.5. Cache is ext2 data and dbdata is extra 4. Didn't even have to revert to Rafe first. ;) I'll report back soon with my findings.

Awesome work ttaball, looks like your the only Dev working on the Ozcan mod for The vibrant. You'd think more people would be on top of this with all its potential.

Thanks again. Ill definitely be donating to you 40 or 50 bucks once we get something stable.
[Vibrant Android Development] dsellers2:
Jeesh my spelling is horrible on swype today. ;)
[Vibrant Android Development] VICosPhi:
I have uploaded alogcat output when the phone got locked up with 1.4 kernel. It was locked up before applying z4mod. It seems there's something with the Kernel.
[Vibrant Android Development] VICosPhi:
Is it possible to patch the zimage file from bionix fusion final package to support ext3/4 while keeping the recovery intact like your kernel has?
[Vibrant Android Development] rogerchew:
hey, so you're running the JAC UC/OC kernel right? Worst case I have a feeling that it may be your cpu not able to handle the undervolting. In addition, did you use setcpu to go conservative and 200-1000mhz? There were a lot of specific rules you had to set in order to successfully use the UV/OC kernels. Oether People using those kernels also had random freezing issues etc. Just check out the bionix rom thread and you'll see 90% of the posts are about kernels freezing, not working properly, etc.

I'm currently running JI6 stock no roms, in order to do this mod I would like to hammer out the proper instructions:

1. boot into clockwork NOT from rom manager to flash the z4 modded kernel 1.5 posted here.

2. reboot

3. reboot into clockwork NOT from rom manager and run the script 1.5 to convert files because it won't unmount /cache if you don't.

Right/wrong?
[Vibrant Android Development] The_Chrome_Coyote:
Trying various combinations of kernels while Z4Mod was in place, I didnt have any issues with using your kernel before I converted the filesystems. Since I rebooted each time fully, I always let the phone return to a calm post boot state before moving onto the next step. Before the conversion to EXT4, the phone didnt freeze after booting, after the file conversion it would freeze everytime shortly after fully booting up. And since it was a hard freeze logs would just stop.

I also never had any trouble with UV/OV kernels before and freezing, as the Bionix series w/ JAC UV/OV was my daily driver for some time before now.
[Vibrant Android Development] dsellers2:
Ttabbal, I wasnt sure if you wanted to see the init.log file in the event of a "Freeze" but I have posted it just in case. I've installed the 1.5 and all seemed ok for a while.

Do you think the possibility exist that Swype is causing these freezes? I've now had the freeze happen 5 out 7 times when swyping. Just a thought. I'm going to try disabling swype and see if that changes anything.

Let me know if you need anything else from me. Thanks for your help.
[Vibrant Android Development] VICosPhi:
For me, the phone would freeze after a hard reboot. There were no custom apps installed either, just standard Bionix final. For me atleast, its not swype, its something else...
[Vibrant Android Development] kas21:
Fixed my own issue. I was able to get into CW recovery from Stock recovery using the CW update.zip. I then was able to flash the z4-update zip and it successfully converted /cache volume. My phone booted fine and mount shows /data, /dbadata, and /cache as ext4. Thanks!
[Vibrant Android Development] biigreen:
Just got done installing and then reverting and everything went fine. Will be putting it thru the wringer today and will report back. I never experienced any freezes before and I hope I don't today.

Thanks and nice work!
[Vibrant Android Development] dsellers2:
What Rom were you running previously Biigreen? If your running Fusion or Bionix, then what apps do you usually run on your Roms?

I want to get mine exactly like yours. Then we can see if it's an application or the kernel.
[Vibrant Android Development] gehzumteufel:
What size NAND do you have? You can check by using this method.
[Vibrant Android Development] biigreen:
I am running Fusion 1.1. I started with my regular setup running some typical apps. Handcent, Titanium Backup, Rom Manager, Terminal Emulator, etc... nothing special. I was running voodoo so I reinstalled the regular JAC OCOV kernel. Next I installed TT's kernel. Did a full reboot. Then installed the z4mod. All done through clockwork.

I'm not really running anything major. Simple setup. And I don't have the large NAND.
[Vibrant Android Development] rogerchew:
2 guys with larger NAND having issues with freeze, 1 guy with smaller NAND no issues....

I have the larger NAND! doh!
[Vibrant Android Development] aloxotls:
I am still freezing after everything is booted up.

I cleared everything off of my internal and external sd and flashed Fusion 1.1 w/JAC. Followed the sequence of reboots as instructed and then flashed 1.5. I still did not do the Z4mod because the regular kernel still freezes. With a fresh install it without any extra apps and it does last on average about 3-4 min longer before freezing than with all my apps loaded. My phone did have problems with JAC's earlier OC kernels and I do have a FFC installed.
[Vibrant Android Development] Ashex1:
I flashed the 1.5 kernel then ran z4mod under stock (did not convert /data beforehand) recovery. It converted /cache and but for some reason /dbdata and /data were not. I rebooted into clockwork and ran z4mod again and it successfully converted /data and /dbdata as they are now mounted as ext4.

I did a restore with titanium and rebooted one more time. So far everything is working well.

As a note I do have the larger NAND. I'm going to keep experimenting to see if I have any lock-ups/crashes.
[Vibrant Android Development] VICosPhi:
I have smaller chip and still have freezing issue

Sent from this new Tapatalk thing...
[Vibrant Android Development] Ashex1:
Just throwing this out there. With everything except /system converted running Bionix Fusion 1.1, I've got a quadrant standard score of 1404.
[Vibrant Android Development] rogerchew:
ugh, would NOT boot up with T4's kernel until I updated with the back support kernel in the development section. I think that should be made BOLD somewhere.

Edit:

Finished converting

/data ext4

/cache ext2

/dbdata ext4

gonna open/close run programs hard for the rest of the day to try to reproduce a crash people are talking about. btw, i came from stock JI6 -> flashed back support kernel found in development -> flashed TT 1.5 kernel -> flashed TT 1.5 script to convert.

quandrant score of 1528

question:

will the accurate circular battery mod signed for JI6 work with this kernel? Answer: Yes
[Vibrant Android Development] dsellers2:
I have the smaller NAND, so does the guy a couple of post above me. 1 guy with a larger Nand is not having issues apparently but others have. It doesnt seem to be consistent.
[Vibrant Android Development] dsellers2:
Just a Simple Test

As I said I was getting most of my freezes when typing on swype. So I disabled swype and ran another test.

I started texting myself as many text as possible without stopping on the regular keyboard. After about the 5th test it froze.

It seems to me it's locking up because the processor is being over worked or is unstable.

I've never had an issue with over clocking or using voodoo so I'm not sure why this is happening, but I was able to reproduce this freeze every single time by doing this.

Give a try guys and let me know.

Dave
[Vibrant Android Development] geoffcorey:
I have the smaller NAND and had 2 lock ups on the 1.4 kernel, both under almost no use (latest when I swiped the text thread to view, first when I left my phone in standby). Since the new kernel, haven't seen issues yet.

But as a side note, the new script converted my cache to ext2 with data and dbdata as ext4. Not sure if that's what it's supposed to do or not. But mo issues here so far.

EDIT: I just locked while using the xda app and trying to view a text. Not around a computer so no logcat.
[Vibrant Android Development] dsellers2:
I odin back to stock, then installed fusion 1.1 with stock kernel. Then I tryed reproducing the freeze the same way I did when my data and dbdata was ext.4 and cache at ext2 but was unable to freeze the phone. Note I've installed your kernel but have not ran the script.

Maybe this isn't a kernel issue? I was able to reproduce the freeze on numerous occasion when the script was installed.

Any ideas Ttabbal?

I take this post back. I was able to freeze it after reinstalling all my apps through Titanium. So I guess it is the kernel.
[Vibrant Android Development] stephenj37826:
Haven't upgraded to 1.5 yet but been running this for 24 hours and have had one freeze on an incoming call. Voodoo never worked for me so I must have the larger chip and my phone was great with ocuv so idk
[Vibrant Android Development] Ashex1:
Try using CPU Benchmark to stress the processor.
[Vibrant Android Development] kas21:
I tried uploading the Stock and JAC kernel from Fusion 1.1 to the site (here) that automatically patches the kernel. Both of them failed with different errors. I would be curious to see how the phone performs with the JAC kernel. I am running 1.4 TT Kernel/ext fix and am having good performance but it doesn't feel as good as Fusion Stock w/ OCLF v2.

Also, can you go from TT 1.4 > 1.5 or should you Odin back to stock first?
[Vibrant Android Development] Ashex1:
I don't know about 1.4 but I went from 1.3 to 1.5. Flashing the kernel will not break anything, as long as you convert back to rfs before using the 1.5 TT z4mod you should be okay (but I strongly recommend using Titanium to backup all apps/settings).
[Vibrant Android Development] rogerchew:
could it be with titanium? i installed all apps onto my phone while phone was bone stock. Then i converted to ext4. I was not able to freeze using swype yet, but still testing. will get back.
[Vibrant Android Development] ttabbal:
Interesting. I have no idea why some people have crashes/lockups while others don't. I do have the large NAND, and used Titanium to restore, and do many of the things people have posted about here. I downloaded the CPU Benchmark app mentioned before, and have the stress test running on my phone now. About 5 min in, while using various apps. I'll report back what I find. I'm also going to check the CPU config info in the kernel source. I didn't think Unhelpful's stuff did any OC/UV unless you tell it to, but it's possible I missed something.
[Vibrant Android Development] VICosPhi:
So has anyone seen any freezes with new 1.5 version from ttabball? I just installed it on my Bionix fusion 1.1. I'll update if I see any issues... btw thanks for your work ttaball I see the error is stock recovery has been fixed in 1.5 now...
[Vibrant Android Development] kas21:
Those that are restoring via Titanium, are you restoring system data/settings? If so, that could be causing some of the lock ups.

I typically only restore user data and never have a problem.
[Vibrant Android Development] gatesmarch123:
This worked beautifully on my vibrant with the rom posted in my sig. With the exception of the power button having no function in stock recovery....which is pretty huge. Hope to see it fixed soon!

Sent from: my Vibrant juiced with Eugene's 2.2 Froyo JPM
[Vibrant Android Development] Ashex1:
I've been running the stress test for about 15 minutes now. I just launched yahoo messenger, fring, trillian, and tweetdeck. Despite the stress test everything has been running ridiculously smooth with no hangups.

Edit: 37 minutes and the only time I had a freeze was when the Email app lagged while replying to an email.
[Vibrant Android Development] blinksilver:
Someone who is having lockups should do the following:

Convert back to RFS, but leave the kernel intact. I believe the hanging is due some improper voltage setting in the kernel and not the zmod. I still have the occasional lock up in this state.

My best guess is that it has something to do with the unhelpful overclocking modifications(not that it should be taken out, I use it.) Perhaps a proper voltage table maybe the answer to our little gremlins.
[Vibrant Android Development] VICosPhi:
Ok, so I installed clean ODIN JFD>ODIN JI6> Clean Bionix Fusion 1.1 and after running the latest 1.5 kernel with 1.5 ext4 script, everything worked fine for 10 minutes. Multiple apps open, browser, messaging, wifi etc. It seemed all issues are fixed but then just wanted to try a reboot. After reboot, opened up better terminal to check the file system type and used swype to type the word "mount" and the phone is now frozen with a blue swype trail on keyboard and screen is stuck lit.

Hopefully we find a solution to this....
[Vibrant Android Development] dsellers2:
Also did the stress test with no hang ups. The minute start typing though all bets are off. Swype being the worst. I know the keyboard is not causing this issue, but im just stumped.
[Vibrant Android Development] dsellers2:
Yes, ive had multiple lockups with the new 1.5 kernel and script.
[Vibrant Android Development] Ashex1:
Can everyone who is having lock-ups/freezes post their upgrade path (and if they have a larger NAND)?

For example Mine is such:

ODIN JFD > Bionix Fusion 1.1 w/Jacs > 1.3 TT z4mod /data > 1.5 TT z4mod /data /cache/ dbdata

Larger NAND
[Vibrant Android Development] dsellers2:
Can everyone report here what size nand they have, what rom, and if there having freezing issues. Ive noticed many more people with the larger nand having better success.

Im on fusion 1.1, Smaller Nand with the freezing issues.
[Vibrant Android Development] dsellers2:
Ha, you beat me to it.
[Vibrant Android Development] VICosPhi:
Already stated it earlier but here we go again:

Upgrade path: ODIN JFD>ODIN JI6> Clean Bionix Fusion 1.1 then a clean install of ttabbal 1.5 kernel and script

NAND size: Small

End Result: Phone worked fine for 10 minutes, after a reboot it froze while typing in terminal
[Vibrant Android Development] gregc2009:
Odin JFD stock> Fusion 1.1 stock> TT 1.5 z4mod

small NAND

Locked up after kernal installation (was just going through the app drawer). Converted the file system and had two lockups within a couple minutes of bootup.
[Vibrant Android Development] rogerchew:
haven't locked up yet...*knock on wood

ODIN JI6 -> back support kernel -> TT 1.5 kernel -> TT 1.5 Script

Small NAND

my baseband version is T959UFJI2

my build number is ECLAIR.UVJI6
[Vibrant Android Development] biigreen:
ODIN JFD -> Root via oclf -> install CWR -> Fresh Fusion 1.1 -> TT 1.5 kernel -> z4mod

Small NAND

No freezes or issues of any kind.
[Vibrant Android Development] blinksilver:
ODIN JFD > ODIN JI6 > 1.5 Kernel+Backcomp> 1.5 z4

Larger nand.

Its definitely load related. Open the web browser, touch the url textbox and go crazy swyping in as many words as you can, as fast as you can. It will hang, every time.
[Vibrant Android Development] VICosPhi:
ttabball, instead of compiling the JFD kernel from source, do you think if we can patch the zimage from bionix fusion 1.1 package to work with z4mod?
[Vibrant Android Development] rogerchew:
i just tried that, didn't hang. will let it run with this setting for a few more days.

ttabbal: loving the backlit kernel, i don't have to turn my phone on anymore to check for any missed messages/calls.
[Vibrant Android Development] blinksilver:
I am running the JI6 baseband, you don't think it could be as simple as that?

If it is not load related, its the larger nand, or the JI6 vs JI2 baseband. Unless anyone else has some good ideas we may have narrowed down the problem a bit.
[Vibrant Android Development] rogerchew:
i noticed you also went straight from JI6 -> back comp kernel. When I did that, I immediately went back to JI2. How were you able to keep JI6?

This was where I found my back comp kernel:

http://xdaforums.com/showthread.php?t=796425

curious if that's the one you used too, since you can't just flash the TT kernel without doing this apparently from stock.
[Vibrant Android Development] ttabbal:
http://www.tabbal.net/files/Kernel-ttabbal-v1.6.zip

This is a bit of a punt, but I hex-edited /sbin/init to break all references to format commands and most references to block devices. I've been running it all day with multiple reboots. I don't KNOW that this is the problem, but the symptoms sound like the time I forgot to patch init with the /data mod and it started causing all sorts of weird issues. It would also help explain why some people have issues while others don't, if your data happens to be where the format command hits, you get problems. And yes, I type on my phone all the time, swype nearly all the time. In fact, about half of my board posts are on the phone.

If you are currently having issues with the kernel/mod, try this, but flash a fresh ROM first please. If your data is corrupted and that's causing crashes, the only real fix is a fresh install. To do the fresh flash, you should convert back to RFS, then flash your ROM, boot the ROM, make sure things work, then the kernel, again, make sure things work, then try z4mod. If you use Titanium, please restore ONLY user apps/data. Restoring system data is known to cause stability problems sometimes, and you can't seem to predict when it will or won't.

I also posted some info on the freq_volt_table file in my kernel thread. I posted an undervolted file there you can try if you like, but please, change only one thing at a time. We can't diagnose issues when there's a huge list of things you have done. :)

For the guy running on Froyo, wow.. I'm surprised you are booting at all. Last I heard, people trying to boot a Froyo ROM on an Eclair kernel got boot loops. Perhaps Eugene worked some magic for us. :)
[Vibrant Android Development] blinksilver:
I use this:

http://xdaforums.com/showpost.php?p=8470451&postcount=15

As my back-ports package (the first one that says "rather here")

And it did not touch my baseband, I am running JI6.

If you can link me to a flash-able JI2 Baseband, I can give it a go.
[Vibrant Android Development] blinksilver:
Going to run the same procedure I ran before, be back in 20 with some results.
[Vibrant Android Development] stephenj37826:
Flashed from odin jfd to bionix 1.91 then to bionix fusion with jacs ocuv. Clockwork tt kernal 1.4, rebooted. Booted into stock recovery. Installed packages. Then in clockwork team ttbal z4mod . Converted then rebooted. Works great
[Vibrant Android Development] rogerchew:
http://www.teamwhiskey.com/home/downloads
[Vibrant Android Development] blinksilver:
Currently wiping my device to give the new kernel a go. If I've still no luck, I will flash JI2 on top.

Man my Vibrant is getting a workout today.
[Vibrant Android Development] rogerchew:
I was thinking maybe you can try taking the back comp kernel that I got from Eugene which automatically flashes to JI2. That way you'll have an identical setup with mine and confirm i'm not just lucky.

i have the larger NAND
[Vibrant Android Development] scrizz:
you guys know that 1.6 is out now.....

;)
[Vibrant Android Development] blinksilver:
You caught me right in time (Just finished rooting JI6, after odining JFD and then JI6), I will use the one Eugene posted with the new 1.6 kernel (hopefully it does not introduce any new bugs.)
[Vibrant Android Development] geoffcorey:
just for laughs on v1.5, i tried loading web and using swype with a ton of random swiping. it froze. I am now going back to JFD stock through odin (repartition w/ .pit file) and then going to JI6 (with .pit file through odin). From here, i will nandroid for a JI6 ROM to start fresh again. Then i will flash back support, JI2 modem, and then v1.6 and see if i get freezing (without restoring apps first).

I will update this post after i finish the process.
[Vibrant Android Development] rogerchew:
haha, not gonna touch what isn't broken. for the most part 1.5 is working just fine for me :D
[Vibrant Android Development] blinksilver:
I can say with some serious certainty that its the kernel not the mod.

Did another clean ODIN JFD -> ODIN JI6. However this time I used the backcomp package that rogerchew linked over(the one made by Eugene with the JI2 baseband cooked in) and the new 1.6 kernel.

Before I ran the 1.5 zmod, I did the "swype test"(I guess that is what I am calling it now) and it hung like a horse.

Any other suggestions, because I am really digging this mod and want to continue helping with the debugging process.

Also in an unrelated note: I'm a mobile engineer by trade(iPhone, not Android), so if there is something small I can do to help in that regard... (small being the optimal word.)
[Vibrant Android Development] rogerchew:
not sure exactly how ODIN works, but from what i've gathered from reading on these forums and a ton of bricking threads, you don't truly have a clean flash unless you ODIN using Eugene's no brick froyo first THEN flash to either JFD or JI6. I'm not a developer of any sorts, but I'm wondering whether your flashes are truly cleaning your phone and removing any remnants of anything you've done in the past.

i guess my understanding using a PC analogy would be:

just flashing JFD through ODIN = reinstall windows

flashing Eugene's no brick froyo through ODIN = formatting pc
[Vibrant Android Development] VICosPhi:
Tried again with a clean ODIN JFD> Bionix Fusion 1.1> ttabbal 1.6 kernel and 1.5 z4mod and unfortunately froze again while turning Wifi on....

thanks for continued support on this, ttabbal
[Vibrant Android Development] gehzumteufel:
I think you kind of have this presumed. Reinstalling windows can include formatting pc, as can using ODIN to flash a device. The repartition thing? That is the "format" of sorts. That is why you need that pit file, but I could be wrong.
[Vibrant Android Development] rogerchew:
definitely correct me if i'm posting misinformation. I want to be clear on things too.
[Vibrant Android Development] blinksilver:
The reason I do a JFD ODIN step in the first place is to use the pit file to do a repartition(you cannot repartition using JI6 for some reason, it refuses to boot). So, unless repartition in ODIN means something different, (and it may, I am in no way trying to be condescending with that remark, I simply just don't know) this about as stock as you can get without having a virgin Vibrant.
[Vibrant Android Development] gehzumteufel:
The way I understand it, is the PIT file directs ODIN in how to destroy the current partitioning and formatting scheme, but again, I could be wrong in this understanding.
[Vibrant Android Development] rogerchew:
ohhh...so without a pit file it won't format, it'll just overwrite?
[Vibrant Android Development] gehzumteufel:
From everything I can gather, yes, but I am sure there is room for error in my understanding. I am still pretty new to the Android world after finally ditching the WinMo world.

What it appears, is that the PIT file + repartition checked is the same as a task 29 on WinMo HTC devices. If this is the case, then that is exactly what it does. Although, with HTC WinMo devices, partition information is hard coded as opposed to using a pit file to specify the partitioning scheme and formatting.
[Vibrant Android Development] Ashex1:
I believe the pit file is instructs ODIN on the partition layout, as you use a pit file with both the JFD and JI6 tar. The JI6 tar does not overwrite the partitions.
[Vibrant Android Development] blinksilver:
In a very interesting turn of events, it hasn't lock out on its own. I proceeded to the 1.5 z4mod anyway and it been behaving very well.

Perhaps the swype related crashes, are just that swype related. Anyone without the 1.6 kernel care to give it a go? You really have to go for the goat though. As fast as you can, don't even try to make words, just run your finger over keyboard like there is gun to your head.