yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] sombionix:
To get into download mode:

1. Unplug phone from computer if its plugged in

2. pull battery

3. remove sim card and sdcard

4. open odin on computer

5. with your battery, sim, and sdcard still removed, plug your usb cable from your computer into your phone.

6. hold BOTH the volume down and volume up (not the power button)

7. while holding just the volume down and volume up, insert the battery.

8. you should now be in download mode and have a connection to odin.
[Vibrant Android Development] Paging Dr B:
lol, thx. When I got home I flashed the tar using odin. For future reference will this .zip work using clockwork?
[Vibrant Android Development] Keslynn:
Voodoo still didn't work for me so I ended up flashing the version with King's kernel. Nice work, Sombionix! Love the look and how fast it is even without lagfix. Also, GPS was really fast and accurate even on the first run.
[Vibrant Android Development] amandadam:
I'm not sure,since I've been using the stock kernel,from day one..I save all of the roms,kernels,mods etc to my mac for easy access.
[Vibrant Android Development] masterotaku:
Getting into download mode the usual way can be a time consuming and frustrating procedure.

By the usual way, I mean holding down VOL-UP & VOL-DOWN, holding POWER, then releasing power when you get a blank screen. I've noticed that I have to at least wait until I cycle through the Vibrant logo screen at least once and release POWER at just the right time to get it to work. Mine is one of the first batch of phones available in the U.S. (July 11th, recieved directly via Fedex from T-Mobile corporate before launch..long story...don't ask lol), but at times it seems as tricky to get into download or recovery mode as some of the newer phones.

The secondary method I use though works every time, and doesn't require the POWER key. Pull battery, hold down VOL-UP & VOL-DOWN, insert battery, while continuing to hold down VOL-UP & VOL-DOWN, insert USB Cable into phone (cable must be plugged to PC beforehand). After a second or two the download screen appears, and you can then release the VOL keys. This is also the only way I've been able to get download mode after seeing the dreaded OMGIBROKEMYPHONE screen (the phone/caution/disk thingy).

I'd also strongly recommend using Odin3 v1.30 instead of Odin3 v1.00. For some reason all of the dev section rom releases use/bundle v1.00, and it gives me loads of problems. It may be related to the quirks of running under Win7 x64, but v1.00 tends to hang more often than it works here.

Odin3 v1.3 can be found here. http://xdaforums.com/showthread.php?t=788640

Best of luck!
[Vibrant Android Development] smashpunks:
What are y'all using to oc it? Setcpu? I keep getting rebooted with that? Is there a certain version to use? Or a trick? I really wanna use setcpu
[Vibrant Android Development] JeremyNT:
I reflashed and everything worked great - until I restored from Titanium. Afterwards I started getting FC's left and right; tried permissions repair to no avail. So it's definitely not your ROM's fault.

Right now I'm guessing that I picked up some bits of Eugene's Frankin TWiz ROM in my Titanium batch job, and they're not playing nice with your ROM. I'm going to mess with it more today to try and track down just what's causing the problem so I can nuke it. I do have an older backup from when I was running stock, but that's pretty crufty now :\
[Vibrant Android Development] rizzxx7:
this is the reason why I never restore "ALL SYSTEM DATA" from titanium, just simply restore apps and data
[Vibrant Android Development] Silrocco:
Very true!! I encountered that the hard way the first time too when I restored "ALL APPS & SYSTEM DATA(215 of them) ."

Unfortunately, It does change alot of the ROM, one that I noted was the Market it changed the third button to right of the screen from "Downloads" to "T-Mobile."

Anyway fellas, just Restore the Apps under Titanium backup and you'll be fine.
[Vibrant Android Development] pelmenept:
I understand bionix. I am just saying that I have NO problems at all with those settings.
[Vibrant Android Development] sil3ncer7:
I'll give that a try, thanks
[Vibrant Android Development] wease:
Just wondering if this is happening to anyone else, running 1.8 w/1.8 fix and I get a FC on my market app every time, did re boot and no luck.just started happening after I installed the 1.8 fix??

Thanks
[Vibrant Android Development] thenikeman:
I didn't think I needed to include HTML sarcasm tags...I was totally kidding about my post earlier about him "photoshopping" the GPS screenshot.
[Vibrant Android Development] flintpez:
Wow, this thread has gotten ridiculous. If only I could harness the power of all of the tears and confusion. I'd build an evil weather machine.

I'm having the Pandora freeze issue and video player crash issue. Tried to search for solutions and even that just brings me to more whining. Any real solution for these problems discovered? Running Bionix 1.8 w/Jacs OC/UV/VOODOO kernel.

BTW: My GPS works great, thank you very much. ;)
[Vibrant Android Development] zaphod_fl:
Interesting problem that has happened to me twice with the J12 modem. The phone will not dial, at all. It says "dialing" but nothing happens. I put the phone in airplane mode and after quite some time (3 - 4 minutes) it closes down the cellular radio. After re-enabling I can make calls again... but the radio will not go into 3G until I do a complete reboot of the system. It is like the modem has crashed.

Has anyone else had a similar experience? I may try the JI6 radio to see but for the short time I was running JI6 on Bionix 1.6 I did not have this issue so I am not sure if they are related or not. Looking for confirmation of either craziness (GTFO) or "Yes, I've had that happen" before I begin deep troubleshooting.

I don't have logcat because both times I was in the car and did not have a computer handy (obviously) and cannot reproduce it.
[Vibrant Android Development] MrGibbage:
I have seen the wandering, and I know exactly what you are talking about. The little triangle moves around, and the error circle stays small, leading you to think it is an "accurate" fix. But it is clearly not in the right spot. I have not seen this though since installing 1.8. but that doesn't mean it isn't still present.
[Vibrant Android Development] zaphod_fl:
Running 1.8 with JACS (no lag fix) and the Bionix fix. Market works fine.
[Vibrant Android Development] Oxirane:
If I an no longer using voodoo, can I just delete that voodoo folder in my storage? Its disabled.
[Vibrant Android Development] darksandz93:
anyone know how to do this? Sorry, didn't wanna lose this in the thread
[Vibrant Android Development] IDtheTarget:
@Sombionix:

I'm loving the ROM, eagerly awaiting your receipt of the FFC so that we can get video chat working!

I would like to point out one fallacy, however, in all due respect:

If you are using a kernel that you aren't posting for us to download, can you truly say "it works for me, so it should work for you"? If the problem that the gentleman is having is due to his kernel, rather than the modem.bin or whatever, wouldn't you have to run your tests using the same kernel that he's downloaded from the OP?

Thank you once again for a terrific ROM. You've made me happy once again to be a Vibrant owner!
[Vibrant Android Development] icandy75:
I had the same issue after my initial 1.8/Jacs oc/uv/Voodoo with J12. I flashed the J16 and couldn't be happier. No issues what so ever and I'm actually getting great battery life.
[Vibrant Android Development] Oxirane:
I think he can't post it because its king's new one- you need to be a paying member of his site to download it.
[Vibrant Android Development] flintpez:
I'm assuming that you're referring to IDtheTarget's post. I believe that he's not concerned about getting the kernel (although that would be nifty), but the environment the ROM is being tested in. The factors are different than what is publicly available. Compare it to testing a program in Windows 7 and saying that it works great in Windows XP.
[Vibrant Android Development] shoerhino:
I just recently loaded Bionix 1.7 and yesterday upgraded to 1.8. Before that, I was using a stock phone except I had the one click lag fix and the JI6 GPS files. On the stock phone, I would have the same thing happen. I would dial a number, the phone would say dialing but it would never connect. You can even hang up and try dialing again and it sometimes wouldn't go through. I would just lock my phone, unlocked it, and it would typically go through.
[Vibrant Android Development] Dragoth12:
Bionix tests all his ROMS with all the different Kernels. So he is simply using a different Kernel at the moment, but he (and others) have tested the ROM extensively with all the different Kernels he offers.
[Vibrant Android Development] creator2456:
Flash a different kernel.
[Vibrant Android Development] silow:
Follow the instructions in this post. You can pull the necessary Swype files from any ROM that has Swype or you can go with the files from this post.

http://xdaforums.com/showthread.php?p=8490342&highlight=swype.apk#post8490342
[Vibrant Android Development] ebullient:
Try a reflash and be extra careful with the disable Voodoo steps, if that doesn't work then your best bet will probably be to flash to stock and then back to 1.8. I didn't have your specific problems but doing that worked out pretty much all the gremlins for me.

Only if you're using a kernel without Voodoo.
[Vibrant Android Development] lqaddict:
I don't think Clockworkrecovery can install from the external SD card, try moving it to the internal SD card - some people prefer to have /sdcard/ROMS directory to keep the install files for different ROM's - and install again.
[Vibrant Android Development] ebullient:
That is irrelevant if he is claiming something works and as proof shows a screenshot from a phone running a completely different kernel, is the point they're trying to make.

I'm not saying he doesn't test his ROMs either, and for myself my GPS seems fine (as it is for others).
[Vibrant Android Development] Jdom58:
Hey just wanted to chime in and say thanks to those who answered on questions I had concerning the voodoo kernel and the hiccups people were having with it.

I had been running 1.8 JACS OC/UV which was running very nice and smooth and when the fix was posted for the audio I also decided to try the KK OC/UV V3 kernel to test out. Man both of these are two great roms, to my untrained I can't really tell a difference in speed or performance between the two. Both are extremely fast and smooth and up until now I have had zero issues with them. Even the GPS is on steroids now, 11 viewed locked on 10 in under 3 seconds sheeeesh, amazing!

Sombi and Team great job!!! you guys are definitely the A Team :D
[Vibrant Android Development] djkdawg:
this happens to me from time to time, but it also used to do it when i was rooted and just using a stock rom
[Vibrant Android Development] mk262:
Since updating to the 1.8 Jacs OC/UV/VOODOO kernel it seems like my performance has gone way down. When I open apps and navigate the phone it "sticks" a bit, it never did that with 1.7.

I wondered if perhaps voodoo wasn't installed, but I don't have a \voodoo folder to remove the lagfix file.

Here's a mount dump:

rootfs / rootfs rw 0 0

proc /proc proc rw 0 0

sys /sys sysfs rw 0 0

/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc

harset=utf8 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx

,iocharset=utf8 0 0

/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha

rset=utf8 0 0

/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar

set=utf8 0 0

/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset

=utf8 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=

1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s

hortname=mixed,utf8,errors=remount-ro 0 0

/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g

id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-

1,shortname=mixed,utf8,errors=remount-ro 0 0

I assume the bolded part indicates voodoo is disabled. Can someone please point me to my "fail" here?
[Vibrant Android Development] Master™:
You probably have a larger NAND chip & Voodoo never was installed..

Follow this guide to fix it: http://xdaforums.com/showthread.php?t=805222
[Vibrant Android Development] w_bovine:
Indeed...do as Master™ instructs. I have the larger NAND and did this, and can confirm that it does work. And Voodoo is cool! :)
[Vibrant Android Development] w_bovine:
Oh no! ardchoille...I get a 404 on that link for the wallpaper. Throw this dog a bone? I'd like to get that wallpaper too.
[Vibrant Android Development] Dragoth12:
Yeah. I see your point, however, what does your kernel have to do with gps locks? Thought it was your modem and/or ROM that handles the gps. Doesn't the kernel simply control your cpu? I really am curious as I don't know for sure.
[Vibrant Android Development] CamachoInc:
I've been looking on here to see if anyone else having same problem but I seem to be the only person. When I'm on Bionix ROMs, I can't connect mass storage to my PC to transfer movies. I had this problem before when I was using Bionix 1.5 and now having that same problem with 1.8. I restored one of my back ups which is, I guess stock is Rom and now I'm able to connect to my PC. Anyone else having that problem?
[Vibrant Android Development] smashpunks:
Yes you can....
[Vibrant Android Development] Dragoth12:
Haven't heard this before. Have you double checked that your usb is set to"mass storage"and not something else? Also. Try making sure "usb debugging" is turned off. It is on by default on som's roms, however my windows 7 64 bit won't let me use mass storage when it is turned on for some strange reason.
[Vibrant Android Development] Gusgom:
I'm loving this rom but just found out when I play mp3 music it shuts down the phone...any fix for that...?..it just automatically restarts...i haven't found a solution on here any ideas...?

Samsung Vivrant Galaxy S Rooted Running Bionix 1.8 Stock
[Vibrant Android Development] Lavundra21:
i just hit my software update button on my phone and i got the message "DM Initialization is not ready. Check network or Sim card." what does that mean? im running the stock 1.8 bionix, does that mean i missed the update?
[Vibrant Android Development] ardchoille:
Oops, sorry about that. Here it is:

http://ardchoille.nfshost.com/tmp/wallpaper_rose.jpg
[Vibrant Android Development] ebullient:
Bear with this wall of text.

Team Whiskey doesn't get paid to do this. They'll gladly take your donations, sure, but you can't expect them to do rigorous testing on every single Vibrant ever released. If they don't have phones with the larger NANDs then they can't test issues related to that (only an example). If your particular phone is not behaving the way you think it should, reflash. If it's still not behaving the way you think it should, Odin flash to stock and then reflash. If it's still not behaving the way you think it should, then you're going to have to live with what you get. These guys are not pros in an industry lab with a large budget.

Even further, they don't have any obligation to pander to every need. Sure, posting a screenshot from a phone running a completely different kernel than what is offered here doesn't give you any apples-to-apples evidence but Bionix is not a kernel! If Sombionix chooses not to load a given configuration, because it takes time and he's not getting paid to do it, then them's the breaks. Maybe you can convince him to load a matching testbed, he's certainly gone above and beyond before, but don't expect him to.

Tl;dr version: Team Whiskey is not paid industry professionals. You're going to get 'best I can do' troubleshooting and testing. If you're not happy, reflash. If you're still not happy, flash to stock and then back. If you're still not happy, then there's not much that can be done and you'll have to accept that.

Before flashing any ROM ask yourself these questions:

Am I inherently unhappy with what I have now?

What will xxx ROM give me that I don't have now?

Does what I get from xxx ROM justify living with whatever issues it gives me?
[Vibrant Android Development] KerryG:
That feature won't work when you are using a custom rom.
[Vibrant Android Development] xxwhitehawk:
Team Whiskey > ALL

@Sombionix & Team Whiskey,

Thank you so much for another outstanding release. Each one just keeps getting better and better. GPS works great! In fact, I'm getting the same accuracy and locks I did with the OTA JI6 modem, but with improved battery life... seems like a win/win to me. Keep up the great work guys! It is appreciated. :)
[Vibrant Android Development] JD76:
Guys... help me!

So I got Bionix working great... everything is fantastic... I wanted to now recondition my battery.. so last night i fully charged it, wiped battery stats, let it sit while playing movies, gps on, wifi on, bluetooth on, screen high... and when I woke up this morning, the battery still had juice! about 14% left.. so I started up Pandora.. a few songs in, the phone shut off...

and now the phone seems dead!... I plugged it in and still no signs of life... no batt pic on screen, cant turn it on while plugged in...

whaaat happened?
[Vibrant Android Development] Lavundra21:
ok thanks. but i read somewhere that as long as i run a stock kernel i will still receive the update. is that right? if not i might as well just flash one of the custom kernels.
[Vibrant Android Development] mk262:
Will I have to perform this process every time I want a new custom rom or is this a one time deal?
[Vibrant Android Development] smashpunks:
Day 2 on this rom. I run it about 18 hours a day non stop. Pandora, movies, music, games etc.....

Still have no issues....

User error is the problems on this rom....

Y'all don't know what your doing.

If not everyone haas the issue, its not a issue, its either your phone, user error or just a bug with your phone or app your using causing a bug ,not a rom bug.......

Hard reset after every reset and y'all will be good...

This rom is almost perfect.and I say almost because nothing perfect...... 0 problems here...

I say in caps THIS ROM IS FUKING BAD ASS WITH NO ISSUES....... ALL YOU PEOPLE CRYING ABOUT HOW BIONIX DOES HIS **** NEEDS TO GO ELSEWHERE.....

WHEN I GET my hd2 friday I'm taking a gps video for proof of how bad ass this is.
[Vibrant Android Development] ttabbal:
Anyone? Please post/PM if you know. We aren't going to get app devs to fix this if we don't tell them how. I've got one that will implement the code if I can tell him how to do it, he can't find an example, and neither can I. If we are going to say the app devs are doing it wrong, we should be willing to tell them how to fix it.
[Vibrant Android Development] ttabbal:
Every time until JAC updates his kernel with support for the large NAND chip. And the ROM devs include it, but you can just flash kernels over the top of the ROM. I do it all the time. :)
[Vibrant Android Development] w_bovine:
Got it! Thank you sir.
[Vibrant Android Development] ebullient:
I honestly don't know. I can say that running a different kernel could change enough on how the phone behaves that it could be an issue (no certainty in that sentence). Standard practice for replicating issues is to have the same environment as far as possible, but I don't blame Sombionix for not doing that. See my wall of text above. At the very least, if he's running at 1.3GHz then he's definitely processing it faster.

I've noticed on XP (or it could be the older usb port) that I have to unplug the cable from the computer and then plug it back in before it will mount, after I've unmounted from that cable already. It's probably not the ROM but it might be USB debugging mode which the ROM enables, it acts a bit different. If unplugging from the computer's port and plugging back in doesn't fix it, then I don't have the answer.

You need to post a logcat. Search the market for 'aLogcat', dump your logs to a file, and attach the file.

Current thread arguments aside, you already have the update and will not receive updates as long as you run a custom ROM/kernel.
[Vibrant Android Development] ardchoille:
You won't receive OTA updates as long as you're running a ROM. And it's a good thing because the OTA update would likely remove your Bionix.
[Vibrant Android Development] smashpunks:
Remove battery?
[Vibrant Android Development] mk262:
Wow that seems really brutal to do that for every new version of whatever rom. Maybe I'm just a candy ass.
[Vibrant Android Development] w_bovine:
I had that same question, and apparently the answer is no, you won't have to. I first flashed 1.7 w/JAC's w/Voodoo. When it came time for 1.8 w/Voodoo I was able to successfully flash it without having to do the Froyo-no-brick routine.
[Vibrant Android Development] jokerz99:
bionix i dont know if you still read the post 800 pages in but for team whiskey i saw this on digg and figure i would share with you.

Source: http://digg.com/news/lifestyle/the_official_u_s_whiskey_map_graphic

Source: http://www.sloshspot.com/blog/10-11-2010/The-Official-US-Whiskey-Map-369

http://www.sloshspot.com/photos/blog/full/photo_1286903761.jpg
[Vibrant Android Development] JD76:
aah.. thanks!.. I removed battery, put it back in and Voila.. the screen shows the batt symbol with it charging... thanks!
[Vibrant Android Development] ardchoille:
Not sure if this helps, but I've been flashing from 1.3 > 1.4 > 1.6 > 1.7 > 1.8 and have never touched odin or flashed back to stock in between. One of the great things about some ROMs is you can just flash to the next release without having to do any extra work.
[Vibrant Android Development] ebullient:
The bolded part is incorrect, and you contradict yourself by admitting that it could be 'just a bug'. The issue is that Team Whiskey is not paid to do this and don't have the resources for industry-level testing. Folks need to realize that modding your phone is not something to be done lightly.

I agree with the second statement, if nothing else seems to work go back to stock and then flash.
[Vibrant Android Development] smashpunks:
I meant bug on your phone from a app or something, not the rom...... Thanks for having me clarify.......
[Vibrant Android Development] rogerchew:
Per master, they found a way to use voodoo with the larger nand. I have the larger nand and I have voodoo enabled.
[Vibrant Android Development] mk262:
If I understand, isn't the question about whether voodoo works, not whether you can flash the rom?

I mean, I was able to flash the rom, I just apparently don't have voodoo.
[Vibrant Android Development] Dragoth12:
@Sombionix: Great ROM man. I am loving 1.8. The new background is pimp. My wife was jealous and I had to go find her some cool backgrounds. :D

Everything is working great, get a couple FC's with Zeam every now and than, but I don't give two craps. GPS is spot on, 10 birds locked in within about 5 seconds, and accuracy in the 30's if not better. I appreciate all the work you do and am glad the Vibrant community has such an awesome down to earth DEV giving us the best ROM's around.