yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] w_bovine:
Maybe I didn't understand. What I was saying is, even if you have the larger NAND you can get Voodoo to work if you follow the instructions on the OP regarding the use of Froyo-no-brick then back-to-stock. I can say this definitively, as I've had success in installing Voodoo.

I also meant to say that once I had Voodoo installed I did not have to do the Froyo-no-brick routine again to go from 1.7 w/Voodoo to 1.8 w/Voodoo.

And even if have the larger NAND and don't do the Froyo routine you can still flash the ROM for Voodoo without consequence other than Voodoo not working.
[Vibrant Android Development] Argusi:
In most cases this is okay. I flashed from 1.7 to 1.8 and my compass didn't work, my screen rotate didn't work and a few other issues that have been reported here. I odin'ed back to JFD, booted, waited... Then went in to recovery, loaded clockwork and flashed 1.8. Everything was fixed that was wrong before. I took out disabling/enabling Voodoo and restoring via TB, but you get the picture. Before doing that, I reflashed 1.8 (twice).

I noticed the same behavior in the G1 days. Just sometimes, you had to go back to stock to reset and go from there even with a "no wipe" update and wiping anyways. Residuals from somewhere just stuck around and mucked things up. I used to do it as a practice, but this phone is so big, it takes longer to go through my full procedure and I get lazy. Sometimes it pays off, sometimes it doesn't. :)
[Vibrant Android Development] crisarn:
Ok so I am in need of some help... First love the look and feel of the bionix roms, but I was having trouble with pandora on 1.8 so I decided I was going to wipe and reinstall pandora to see if that would help, I know it was a long shot. Also I should mention I was running JAC's voodoo kernel with voodoo enabled.

First I fixed permissions via clockwork, rebooted into recovery...

Next I wiped data, and every thing else that is wipable via recovery and then fixed permissions one last time

On reboot I got and still get Vibrant screen then I get a screen that is 1/3 static, yep like rabbit ears, and the rest black... and this just loops over and over.

With the charger/ usb cord plugged in I get the battery icon, the progress wheel doesn't spin then the screen goes to black followed by the static screen.

Any attempt to boot it recovery or download mode results in the same result, i.e. vibrant screen then the static screen.

any ideas?
[Vibrant Android Development] moonfire711:
GPS and Compass?

I have run 1.7/voodoo and 1.8 with and now without voodoo (running King). With all 3 versions I have run, I am not able to get a quick or good lock on gps and compass never seems to be calibrated (I've tried to calibrate using several methods suggested in this thread). I had these working better on stock (I know it's not the ROM, but probably my user settings.)

I don't have a data plan because I only get the edge network in my area and can't justify the cost. Is my understanding correct that the gps (and/or compass) will not work quickly or correctly without a data plan? I have tried running gps with and without wifi enabled as well as using it with and without grabbing my location via wifi.

If anyone is willing to give a few pointers (probably again) on what affects the gps/compass and which settings in the phone are best, I would be ever so grateful.

Awesome ROMs regardless!!! Thanx!!!:D
[Vibrant Android Development] w_bovine:
I think this has something to do with why Voodoo can be made to work with the larger NAND. My guess is that doing the Froyo-no-brick-back-to-stock routine clears things out in such a way that it will allow Voodoo to work.

I'd venture to say that it may not at all be a bad idea to do a complete wipe every now and then if one is going to continue experimenting with various and sundry ROM's.
[Vibrant Android Development] Xyber3364:
going to do a stab in the dark, but sounds like a voodoo problem, due to do anything with out disabling it. Try steps in OP to fix the voodoo problem
[Vibrant Android Development] bvc:
I flashed 1.8 JI2 stock kernel... so I tried to recalibrate the battery after that... one problem: after I fully charged and wiped the battery stats the battery it's not draining out yet... gps on, wifi on, online music player on, white screen on, max brightness, played some homerun for about half hour, like half hour of talking, widgets etc , after couple of hours I went to sleep... woke up this morning and the sucker was still on (31% juice left,the screen was off all night long) ... so after 11 hrs still alive... sorry if I'm too excited but until now the battery wouldn't last this long in these conditions...
[Vibrant Android Development] sombionix:
I run all my tests using the Vibrant stock kernel to get the most accurate test results as possible. The fact that I provide downloads with OC and Voodoo kernel's is just a bonus and everyone needs to realize that I do not program those kernels. I simply like to provide options for the end user, and including those kernels within my rom with a single flash is much easier then having to download my rom with a stock kernel, and then performing a second flash for an aftermarket kernel.

To everyone concerned, yes, the kernel does control the cpu. While I understand that not all of the issues are being caused by the aftermarket kernels, a lot of them are. Keep in mind that you are over clocking a cpu that in all honesty, isn't meant to be over clocked. Not only do we not have the proper cooling for over clocking, but we don't have the proper voltage output. None then less, we do it, I do it, but with that comes risks and consequences. Many of those consequences include random freezes, locks, reboots, increased battery drain, FCs, etc.

The file structure of a custom rom is quiet different than an 'out of the box' stock rom. We have to modify and optimize files, move files, give certain files permissions, put files where they normally wouldn't go, create additional files that never existed to get things to work. While the files are the same, the file tree is different, thus making the phone operating differently and often times, causing problems. Once again, this is one of the small sacrifices we all make in order to boost the performance of our phones and add additional features. Us devs do out best to make these roms as stable as possible, but as stated in a previous post, we simply do not have the resources like the large manufacturers to perform large scale tests. We have the one phone we own, just like the rest of you, to perform tests. Its literally impossible for a single person to find all of the flaws.
[Vibrant Android Development] megatherian:
Play avatar with full brightness turned on and "outdoor visibility" checked - that'll drain it right quick
[Vibrant Android Development] kas21:
Amazing ROM!

I am one of the chosen ones that have the larger NAND and was able to use the Froyo-no-brick method to "correct" the NAND size. 1.8 has been running flawlessly and I cannot get over how fast and snappy this thing is. It's like I have a brand new phone! Huge thanks to everyone's hard work on Team Whiskey!!

I also wanted to share that the Large NAND fix wiped my internal SD card. I am not sure if that is typical or I am just special :cool:. I did not click the format option in Odin. Might want to move those pics, mp3s, and Titanium app backups off to your other SD card to be safe.
[Vibrant Android Development] Argusi:
I agree, I did the froyo thing a few weeks ago when there were rumors of it allowing Voodoo to work. That was the first time my internal SD actually partitioned. It changed the slices. When all of this started, I would randomly select partition in Odin, but it never actually deleted the contents on my internal SD for some reason. When I did it after Froyo, it did. That allowed Voodoo to work on my NAND and completely cleared everything out. This last time, I just did JFD, no format and no Froyo. It cleaned it up enough to allow Bionix to work like it was supposed to.

I'm a flashaholic. I have a very dirty phone. I flash everything to try it out. So complete resets are 2nd nature to me. ;)
[Vibrant Android Development] ttabbal:
You are boot-looping, sometimes called a "soft brick". Do the same recovery process as if you flashed a ROM without disabling voodoo.

You can get to download mode, as long as you aren't hardware locked. Try removing the USB and battery. Install the battery, then hold both volume buttons and plug in the USB. It should boot you right to download mode, works every time for me.
[Vibrant Android Development] peaman427:
O M G. This rom kicks ass. Super smooth. After reconditioning the battery, 1% went down after 1hr 49min of standby. Keep up the good work somb!
[Vibrant Android Development] Dragoth12:
Cool. I didn't think of the Kernels in that way. It's interesting to get a very small peek into what it takes to program a new ROM, I for one have no clue what it takes to do so, but I know it can't be easy, and it can't be quick. Thanks for your work Sombionix, you are truly a great DEV. (You have some thick skin too. :D ) Love learning new stuff.

EDIT: And the more I think about it, the way you test your ROM's on stock kernel makes perfect sense. You can't be sure every Kernel is going to play nice with your ROM, so if your ROM works flawlessly on stock Kernel, than that's all you can do, other Kernels will likely play nice, but could cause 'gremlins' but there isn't anything you can do about it anyways. :)
[Vibrant Android Development] w_bovine:
Surprise! I found that out the hard way too. Fortunately, I had backups on the PC. I think I'll remember this next time!
[Vibrant Android Development] DaSmittyman:
yes it does, on 1.7 i lasted about 35 hours maybe more with pandora on 60% of the time use gps about 10% of the time and texting all the time and calls about 30% of the time. screen was usually on all the time but when i slept
[Vibrant Android Development] hotadef:
was bout flash 1.8 until i saw THIS Samsung releases Froyo update source code for the Galaxy S looks good to me lol i think there is a new kernal in there maybe king can bless it with his platnuim treatment. but ill flash 1.8 anyways cause my battery is horrible and my gps in not good either so ill get 1.8 until someone does something with the source code
[Vibrant Android Development] Frizzmmm:
I am just droping a note to say thank you for the hard work put into each release.

As a bug report ( tried looking for it and didnt find someone who had posted it and didnt ) I am running 1.8 stock kernal and fresh after the requested reboot, i switched the lock screens from the puzzle lock to the android lock screen. The lock screen can be unlocked by pressing the menu soft key instead of swiping.

Its a minor issue and not that important, jsut wanted to bring it to your attention... THANKS FOR ALL THE HARD WORK!
[Vibrant Android Development] castro_OO:
I wish I had that problem I recalibrated and my battery is worse I think ill try again I unplugged at 730 am its now 1040 and im at 67%...i think ill flash stock then back up to 1.8...been flashing alot lately

Samsung Vibrant 1.6 Bionix/Voodoo on Zeam Launcher
[Vibrant Android Development] sombionix:
Dammit, you're right. I had originally fixed that when I decompiled the framework-res and forgot to change it back. Its literally a matter of changing a 'false' to 'true' in one of the strings. lol. Thanks for pointing that out, unfortunately I won't be able to get a fix out for that until the next release.
[Vibrant Android Development] turbosix:
i dont think everyone understands this so well.

*****ing about a GPS fix from samsung? *****ing about 2.2 from samsung?

THIS IS WHY IT TAKES ****ING FOREVER! they have hundreds of people not only going through all of the lines of code, but testing, retesting, over and over, every combination of this or that to make sure the thing just works.

its like video game testers. they have to play the same game over and over and do every possible combination of this or that to make sure the game is as polished as possible when it launches.

and then once a few hundred thousand gamers get their hands on it and start doing things in the game that the testers never thought of, more bugs are found and patches are released.

it really sounds like a lot of these guys need to sell their vibrants, go buy an iphone4 and just leave it stock.

dont jailbreak it.

dont do **** to it.

leave it locked down and stay in that walled garden. sure you wont be able to do all the cool **** you can with android and custom roms, kernels...

that's just the price you have to pay.
[Vibrant Android Development] brunobf:
One thing that I noticed from 1.6 to 1.8 is that LbsTestMode is not working any more. If you use the usual *#*#1472365#*#*, it just blanks out the number and the application doesn't show up. In case it matters, I'm using Jacs kernel, and this is the 1.8 with the fix already.
[Vibrant Android Development] castro_OO:
Hmmmm just brought up music player here in the train....and went to options to show visualazations and got and fc...

Samsung Vibrant 1.6 Bionix/Voodoo on Zeam Launcher
[Vibrant Android Development] sombionix:
Yeah, unfortunately, the JI6 update did something to it. If you google it, you'll see that its not just our phone. Captivate users are also having the same issue after their update. I believe there is a workaround but I couldn't tell you off the top of my head. All the changes I do within lbstestmode are done directly through the source code of the app and then repackaged.
[Vibrant Android Development] w_bovine:
Try this:

Shortcuts > Activities > LbsTestMode > com.sec.android.app.lbstestmode.LbsTestMode
[Vibrant Android Development] SkOrPn:
I asked Master to point this out in the NAND fix thread. Thanks and sorry about forgetting that fact...

Not only that, the kernel in question was designed and tested with the stock Rom in mind so it goes both ways. Someone like JAC is trying to make better kernels for the official Rom, and someone like Sombionix is trying to make better Roms for the stock Kernel, lol....
[Vibrant Android Development] sombionix:
Yeah, I found that issue today too. Its the only issue with the music player. I believe the issue is when I deodexed it, I forgot to point the boot paths to a secondary .jar file. Aside from the visualizations options, everything works fine.
[Vibrant Android Development] ebullient:
Try getting the lbstestmode shortcut from the market, it's still working for me.

Edit: beaten, it's the same thing.
[Vibrant Android Development] i0nicx:
As always amazing job sombionix, every rom is buttery smooth.

aaaannnnndddd I'm just going to be a pain and ask if we can get a flashable zip, apk or theme files for the black stock android keyboard. I LOVED the black keyboard in 1.7.

or if someone can put it up somewhere where i can grab it, it would be much appreciated.(i deleted the 1.7 zip from my sdcard and computer when I pulled down 1.8 like an idiot)

whiskey money coming your way on payday =)
[Vibrant Android Development] SkOrPn:
Hey quick question:

Anyone know why since 1.4 I cant get my "Tweeters" notification sound to be the ONLY sound? 1.4-1.8 gives me a musical riff that is endless when someone messages me. On the stock rom I could select "Tweeters", and when a text came thru it would only Tweet me once. Now its an endless musical riff, even if I select my own sound. lol

Just curious... search gave me nada
[Vibrant Android Development] ram130:
What the hell did you do to this rom??

My batter life is amazzzzing!!!!!!!!!!!! going now for 13hours..with 1hr 30min display on time..15min pandora and 30min listening music browsing the web for 11min with 3G only..I have 64% left..using KK kernel without setcpu...LOVING IT!!!!!!!!!!
[Vibrant Android Development] ebullient:
To be clear, is this the swype keyboard that currently has all the keys outlined with a line of white? I have the nakedswype stuff that makes it all black (aside from the letters) but you'll need to apply it through MetaMorph.
[Vibrant Android Development] knicks235:
ok i know i sound like a worry wort but if i flashed the voodoo kernel and it did not enable due to nand can i flash kk kernel and delete the voodoo folder or should i stick with a voodooless kernel and wait for beta 5 for it to work? btw im so loving this even without a lagfix
[Vibrant Android Development] Gusgom:
I love this rom alot its so smooth but It freeses on me when i use Pandora or play MP3 is anyone else having this issue?
[Vibrant Android Development] Br1cK'd:
Have been running your roms since 1.3, and I love what you do with these roms, smooth, and exactly what the phone should have been out of the box, thank you!

to address your above comment, I wonder if people that are having funny issues are running jacs 1.1 with voodoo. When I flashed 1.1 over your rom, I had a ton of issues that didn't seem to be directly linked to anything. I flashed it back to jacs first kernel, re-enabled voodoo, and haven't had a single issue, even better battery life than when I was on 1.1. I hope this info is helpful to some, as it seemed the root of my issues was the jacs 1.1, not voodoo, and not your beautiful rom.

Keep up the great work, as soon as I can afford to, whiskey fund donations shall abound.
[Vibrant Android Development] sombionix:
Check the first page of the thread. I added a link in the OP.
[Vibrant Android Development] Spiffywerks:
I'm running your 1.8 Bionix, I noticed something with the MMS. I can't click on the To: window to bring up my contacts. I have to actually start typing a contact before it brings up a quick pick window below the To: Box. Was this intentional? It is nice tha it shows the name/phone number. But if the contact is associated with an email addy, it doesn't show anything. I'm using the contacts off the SIM card.

I had an earier issue once, but haven't been able to duplicate it again yet. My call Volume became attached to my media volume. Turning up/down In Call Volume didn't change my voice call level. I had to turn up my Media Volume before In Call Volume went up. After it happened, I rebooted and it seemed to stop doing it. I dunno. If it comes up again I'll let you know, but just thought I'd mention this little fluke.

Another question, my system manage apps shows I have SIMS 3 installed, but I see it no where in my applications. Any ideas? I did run Ti to restore missing applications after installing 1.8, not sure if that had anything to do with it.

Great Rom. :)
[Vibrant Android Development] w_bovine:
If you're certain Voodoo is not enabled you can go ahead and flash another kernel and delete the Voodoo folder. Kingklick's kernel is a popular choice with 1.8.
[Vibrant Android Development] jimmytran817:
Love BIONIX 1.8

Just wanted to say Thanks! Keep up the good work!
[Vibrant Android Development] sombionix:
Are you running voodoo? If so you can try a couple things. Try enabling and re-enabling voodoo, then try it. If that still doesn't work, try re-flashing all together, preferably a non-voodoo kernel. I'm 100% sure that pandora and the music player work just fine. I've been running pandora at work everyday and I use the mp3 player at the gym and have no problems.
[Vibrant Android Development] smashpunks:
Visualization works for me.... I seriously think my phone is on steroids..... No issues
[Vibrant Android Development] i0nicx:
omg i love you haha :D
[Vibrant Android Development] Gusgom:
Sombionix Thanks for the response I actually Im running the stock 1.8 I've tried several times re-flashing and even tried the hard reset, the mp3 plays a couple of songs and then freeses and Pandora just plain freeses even b4 a song comes onits extremely weird cause everything else is running amazingly on this rom...please help. I need to show this off at the gym today..LOL
[Vibrant Android Development] DaSmittyman:
time for a logcat
[Vibrant Android Development] ram130:
WOrking fine here too!! I notice it FC when I first enable it ..but when I did it again..it worked fine :D

14hrs now with 62% left..
[Vibrant Android Development] ram130:
Try the KK kernel build!
[Vibrant Android Development] mk262:
I followed that guide but after flashing eugene's I can't get back to download mode. It just reboots endlessly into recovery. :(
[Vibrant Android Development] sombionix:
Unfortunately, it seems like you're one of the few that has experienced this issue with pandora and the music player. As much as it sucks, my best suggestion at this point would be to odin back to stock, re-root, then reflash my rom. Sometimes flashing back to stock is the only way to get the proper base to work on. I never experience these issues because I am constantly flashing back to stock, and re-rooting for testing.
[Vibrant Android Development] knicks235:
ok im flashing from voodoo kernel to kk kernel, i really diddnt feel like going through odin to make it work. hopfully beta 5 will come out so i can expirience voodoo.
[Vibrant Android Development] sombionix:
Yeah, kings kernel is amazing. I've been running it on my phone and its incredibly smooth and responsive.
[Vibrant Android Development] jmerchant:
Another setcpu question, is it normal for it to keep going back to 100/1000 after a reboot? I'm using the OC kernel but everytime I reboot the phone it goes back to normal.
[Vibrant Android Development] Gusgom:
I will def give it a shot I just DL the stock Rom then I'll Re-Flash thanks again for all the work and for the suggestions....
[Vibrant Android Development] ebullient:
Yes, you want to keep 'set on boot' UNchecked.
[Vibrant Android Development] Insomaniac10:
Edit: nevermind, please delete.
[Vibrant Android Development] w_bovine:
Yep...that's normal. You have to reset SetCPU every reboot as Set on Boot is not something we should be using right now.
[Vibrant Android Development] sombionix:
Yes, that's normal. You don't want to check the 'set on boot' box. Every time you reboot, you have to set the clocks manually.
[Vibrant Android Development] superchi:
Anyone having trouble sending emails through gmail? I can receive them just fine but am unable to send anything out

ETA:

Did not have any problems on 1.7
[Vibrant Android Development] Blkegk:
Im one of the few that still have this problem. I reflash between jac's and kk kernal and still have freezing problems with pandora and music player. I do notice that everytime I revert back to the stock kernal, none of the freezing issues appear. I rather have a custom kernal then stock so I pretty much gave up on having pandora on my phone.

Hey sombionix, when I reflash should I also do a complete wipe of all data also? Maybe that will rid me of some bugs that has been plauging me.
[Vibrant Android Development] jmerchant:
Good enough...

Another thing, I flashed the stock tw framework from the first page, and I can't remember if i read it somewhere, but it brings back the right colors, except for the swype keyboard...I can live with the black keyboard, but is there a simple way to get it back to the normal theme?

And to anyone thinking of flashing this, but is scared because they are new to the whole flashing business...DO IT!!! The instruction page linked on the first page of this post is simple enough to follow, and it was rather painless...now I'm all hooked on flashing things on my phone...lol

I appreciate all the help and this AWESOME ROM!!! and these great forums...
[Vibrant Android Development] DaSmittyman:
if you reflash it should do a complete wipe for you but maybe wiping your davik could help
[Vibrant Android Development] Blkegk:
I will try this, thanks.
[Vibrant Android Development] willsnews:
I flashed stock kernal 1.8 with rom manager as I don't have a computer and I'm just kinda confused as to how I get back to stock I'm sorry if this isn't a smart question or even in the correct place but I could use the help as I would like try different roms and don't wanna brick my phone any help?

The guy on the couch
[Vibrant Android Development] superchi:
Sorry guys I remembered reading somewhere about clearing the gmail cache, did that and now it's working fine.

Thanks very much sombionix for the great rom-so far, so AWESOME!