yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ezadel:
headset Bionix please

OK this is a problem with all the Froyo Roms (this one and macnut), maybe its a problem with the leaked stock one too but um sure sombionix can fix it PLEASE PLEASE TRY, i am going back to fusion 1.2 :(

" 3.5 mm jack only works with songs and system sounds but DOES NOT route phone calls to headphones :( :( :( PLEASE simbionix fix it please" Also anyone else can confirm??? try using just a simple pair of headphones see if i works with the phone calls.. mine does not :(...

is there a dialer app i can try other than the one included .. maybe its a dialer app.. !
[Vibrant Android Development] shawn605:
Yeah I lost completed access to my SD card (which as it turns out was NOT corrupt). I also have issues dragging and dropping files to the phone's internal memory.
[Vibrant Android Development] frankencat:
Yes, this is the issue I am talking about.
[Vibrant Android Development] raduque:
It did that for me, but that's because I noticed it was set for sunday, 8:45am. A week from last night (I set the alarm last night before i went to bed). I went back and changed it to Monday and it showed the correct time on the toast popup.

Edit: It went off at the correct time, too.
[Vibrant Android Development] moonfire711:
I use Switchpro to turn off data, wifi, bluetooth, gps, and sync when I am not using them. So, no, wifi calling was not on because wifi was not on.
[Vibrant Android Development] VICosPhi:
Has to be a bug... I had the same problem on two different vibrants...
[Vibrant Android Development] VICosPhi:
Same here, its definitely a bug...will post logcat later
[Vibrant Android Development] GalaxyS2k10:
Did you already mounted USB? As in does your computer see both 16 and 2GB SD card? You need to unmount USB if your phone does not see it. It should start Media scanner and detect both drives again. Or just unlug the USB cable.
[Vibrant Android Development] GalaxyS2k10:
It doesn't work, you can hear when a call is coming in.... but once you pick up.... the sound drops out of the headset. It is a known bug with all previous Froyo build. i"m surprised the leaked ROM has the same problem.
[Vibrant Android Development] ivanmmj:
If you're referring to the market, you can always use the Nexus One's 2.2 Fingerprint for now:

ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
[Vibrant Android Development] sombionix:
That's not a bug....its supposed to be like that.
[Vibrant Android Development] Alex530:
Does this have the data connectivity issues?
[Vibrant Android Development] sombionix:
nope, no, nadda

no, no, nadda
[Vibrant Android Development] sombionix:
I've been mounting and dismounting this this all night/morning, haven't had a single FC with this.
[Vibrant Android Development] rakeshchn:
@sombionix is the flash 10.1 running smooth?
[Vibrant Android Development] rbirg:
Oh... heh, just not used to it I suppose. Guess I liked it portrait better.
[Vibrant Android Development] Dragoth12:
I flashed this almost right when they released it, and am barely getting past the "let it sit for 10-15 minutes"....no wonder you are getting FC's. You really should read and follow installation instructions. If you flash properly, it will take you at least 20 minutes before you can actually start using the device. (10-15 after the initial flash, another 5 minutes after signing into google and letting things sync) That doesn't include any app restores either.
[Vibrant Android Development] hburn:
Will this work on bell sgs i9000m ? I want to try this rom but first time I flashed this phone with odin I brick it and get pba replacement from repair...now I just want to be sure that this flashing method is safer than odin I'm on stock ugjh2
[Vibrant Android Development] rbirg:
hahaha that makes sense. I got too excited and forgot to reboot
[Vibrant Android Development] PaiPiePia:
Nice!!! Gear job team whiskey!

A question, was there an official vibrant 2.2?(jk2) I thought that it dorsnt exist?
[Vibrant Android Development] grennis:
Can somebody posted straight leak stock ROM instead of this with all these mods?
[Vibrant Android Development] krylon360:
your sq3lite keeps crashing when trying to call an audio file from your sd card. 1st, reboot, and try again. if that doesnt work, reflash.
[Vibrant Android Development] harabinger66:
Chargers ftw! :D
[Vibrant Android Development] gunks:
Apparently, from what Ive been reading, it was leaked within the last day or two.
[Vibrant Android Development] krylon360:
We have been asked not to post it at this time.
[Vibrant Android Development] ciervo5389:
Aww poop....just flash bionix1.2
[Vibrant Android Development] rbirg:
yeah... i'm a moron. that fixed it. thanks <3
[Vibrant Android Development] lqaddict:
Missing the black status bar, and the TouchWiz is back, but so far so good, got a single FC when connected to Market, but it looks like it resolved itself.

Will report of any issues, restoring my apps now.
[Vibrant Android Development] oquinones:
Does this work with the FFC mod?
[Vibrant Android Development] biigreen:
No logcat needed for this. I checked with ViralBlack and it will be fixed in R2.
[Vibrant Android Development] atlaswingpasaway:
no problems with YOUR alarm clock issues.

here's a video of tests i did a couple of minutes after i flashed.

watch and reflash.

http://www.youtube.com/watch?v=sfe7pILcnvs

http://www.youtube.com/watch?v=IHT4NBWRzKE

the back key issue is really present as it is connected to a critical

apk with Froyo framework. THAT is the bug.
[Vibrant Android Development] Beefvvl:
Looks like this hasn't been answered. I was wondering the same thing.
[Vibrant Android Development] ezadel:
anyone else? does everyone's phone call go to headphones ??? is it only me ??? um sure its a Froyo problem i had it with this and macnut... never had it with eclair , i think another guy or too did as well
[Vibrant Android Development] ezadel:
ok so everyone has that or just us, I heard Eugene saying his phoe does not do that could it be a problem only with some patch or hardware?
[Vibrant Android Development] Ashex1:
Another bug in the clock app. Morning mode is not activated when the sound is set to Mist.

To replicate, create an alarm and turn on Morning mode then select Mist for the sound, when it goes off the alarm sounds instead of the melody and animation.

Having issues getting a proper logcat as it fails when the phone goes idle.
[Vibrant Android Development] eminembdg:
Anyone else having strange data issues? I'm connected, and even the little arrows in the 3G icon are lighting up but I have really slow speeds and sometimes no connection errors
[Vibrant Android Development] spimonkey34:
I just tested USB mass storage with my Windows 7 PC successfully as well.

It is all working great.

This was my process when I flashed the rom:

1) I ODIN back to stock JI6.

2) I backed up my internal SD card then formatted it in Android.

3) Rebooted into CW recovery NOT using ROM Manager.

4) Wiped user data & cache.

5) Flashed ROM.
[Vibrant Android Development] fudo jay:
This rom works perfect. I have no bugs whatsoever. everything is working. gps camera this and that. good job bionix. keep it up.
[Vibrant Android Development] atlaswingpasaway:
yeah! high five! lolz

many people here experience the usb thing but not for us.

also Win7-64bit
[Vibrant Android Development] moonfire711:
R2 beta is in the alpha/beta/RC thread of the team whiskey forums now. Many bugs addressed and fixed, but remember it's still "beta" and not for everyone. Be patient as it's tested before being released to everyone. USB mounting still an issue, so don't expect that to be fixed yet in R2

Edit: Wifi Calling was also removed as it was a source of lag and several FCs.
[Vibrant Android Development] atlaswingpasaway:
mine does. even with a bluetooth headset. flash back to stock and reflash obisdian.
[Vibrant Android Development] atlaswingpasaway:
moonfire, my USB mounting to PC works. I didn't do any fixes or MediaPlayer mounts, or whatever. right off the bat it connects. Check the video i posted a page back.
[Vibrant Android Development] tjsynkral:
Swype and HTC IME are both multitouch keyboards.
[Vibrant Android Development] GalaxyS2k10:
I tried macnut R2 long time ago, it was a problem then. I don't know if he fixed it in R10.
[Vibrant Android Development] GalaxyS2k10:
Are you saying you can call people while using the 3.5 headset? The bluetooth headset works. the analog 3.5 however drops when the dialer starts to dial out.

I can also hear incoming call, but once i pick it up the sound drops from the headset. I have to use it like a normal phone :(
[Vibrant Android Development] xaymaca:
How are so many people having so many issues? Haven't had one yet and I've done just about everything, from mounting it to testing out the tethering, GPS and everything works great

will try eugene's version just to see
[Vibrant Android Development] hkfan:
Yes....same issue with me......i hate bluetooth so i use stereo in car for my calls...plz plz fix this
[Vibrant Android Development] atlaswingpasaway:
oh, i havent tried a 3.5mm headset yet, sorry.

but 3.5mm headphones, no mic, it works nice..
[Vibrant Android Development] moonfire711:
It is most likely due to the way it is set up with each OS. For many people (me included), the OS they are using is giving the mounting issue. You may not have the wrong OS on your PC.
[Vibrant Android Development] ezadel:
yes same here, maybe it works with the official samsung headset , I lost it so i donno...but I need this because i like to connect sound to my car thru 3.5 mmjack and talk on the phone... please people can u confirm it works with any pair of headphones???? "talking on the phone NOt other things"
[Vibrant Android Development] Beefvvl:
I haven't had any issues with usb either. I tested transferring different file types also.
[Vibrant Android Development] ithsburtondwight:
Data issues is not a result of the rom nor it is a bug. It is because of your data plan which has reached a limit of 5 gigs. According to tmobile, when you have reached 5 gigs of data, they will slow down your internet to make sure extreme users will not abuse and to ensure average users will get a comfortable data surf.
[Vibrant Android Development] smashpunks:
I agree, some people have major issues.. Not I, working fantastic..
[Vibrant Android Development] Insomaniac10:
You should probably remind everyone that if you want to Nandroid back to 2.1 after flashing Obsidian you have wipe then flash a 2.1 kernel before restoring. Its not in the OP, and im not sure if its in the "Installation Guide" because that link is broken for me. But i am now softbricked and i cant even access stock recovery via adb or button combo (adb says im in recovery when i type "adb devices", but all i see is Vibrant screen)

Please dont jump on me guys, im only saying this to help people out, im not trashing Team Whiskey at all, what i do with my phone is my own responsibility and i undertsand that perfectly. However, this is definately something that should be in the OP
[Vibrant Android Development] eminembdg:
I haven't even come close to my data limit. It is due to this ROM or something in it. I was fine then all of a sudden after flashing this I'm having these odd data issues
[Vibrant Android Development] ezadel:
i just flased back to fusion without doing that(because of headset issues) , no soft brick ....but I guess that would be safer anyway
[Vibrant Android Development] GalaxyS2k10:
I head the official headset, it doesn't work. It has never work on any froyo build i tried.
[Vibrant Android Development] ezadel:
I think this maybe only on some vibrtants (hardware patch or something) because others seem to have it working mine only works with 2.1.... also I feel this problem may have been in the leaked rom too... otherwise why would it be in this one and on macnut and all others....
[Vibrant Android Development] Insomaniac10:
well im pretty sure with Eugene's froyo ROM you have to do that. but if thats not the case then what can explain my problem?

I love Fusion so i figured id try Obsidian. I Nandroid backed up, then flashed Obsidian, no problems but i only wanted to check it out. So then i rebooted into recovery, wiped and then went to restore my Fusion, now im stuck at vibrant screen. cant get into stock recovery at all, even though adb is telling me im in recovery.....im searching and searching and cant find anything on this
[Vibrant Android Development] tjhart85:
Here are my attached settings (screenshots).

Windows 7 Ultimate x64

I'm pretty sure we won't know that until it's officially rolled out. None of the other leaks on Eclair were 100% exact (even if they had the same build numbers).

We shouldn't have to remind anyone anymore since it's been brought up dozens (+1 now) of times already.
[Vibrant Android Development] atlaswingpasaway:
it couldn't be the PC OS. As long as drivers for the hardware are present on the OS, it will automatically look for the registry and driver files in order for it to know it is one of those devices installed in it.
[Vibrant Android Development] ezadel:
yea with Macnut I had to ODIN back to stock.... with this one no, but also macnut wiped all my internal sd card
[Vibrant Android Development] GalaxyS2k10:
I'm sure every OP post says something along the line of "we are not responsible what may happen to your phone". With that said, again common sense tells me not to use 2.1 ROM with a 2.2 kernel. You must realize that nandroid backup doesn't backup KERNEL. But you should be fine if you ODIN back to stock, get into the download mode, load pit and tar file then you're set.
[Vibrant Android Development] tjhart85:
Same here ... After Macnut R8 it also thought that my internal SD was my external and vice versa.

Odin to Froyo that doesn't brick and then stock and then to Obsidian before it was working properly again.

Shouldn't have to go that far even, just grab a Bionix with Stock kernel (or whatever ROM with stock kernel.....or the kernel by itself) and flash that and then apply your Nandroid.
[Vibrant Android Development] Insomaniac10:
In that case there shouldnt be installation instructions at all, since all of that has been said thousands of times before......what about people who have never dabbled in Froyo for the Vibrant, how are they supposed to know if they just see this? It its not necessarily common knowledge whereas disabling Voodoo is, and so is using volume +/- buttons to navigate recovery.........thanks for your help
[Vibrant Android Development] tjhart85:
They're supposed to READ THIS THREAD.

Maybe do a search IN THIS THREAD for how to get back to stock rather than posting another reply and waiting for an answer and cluttering the thread up.

You're welcome FOR THE HELP!
[Vibrant Android Development] Insomaniac10:
please see below

-----------------------------

when did i ever ask how to revert to stock??.....im asking why adb says im in recovery even though im at vibrant screen....go ahead and tell me where the answer to that question is located in this thread.......
[Vibrant Android Development] mr2t32:
you can't restore from CWR because it doesn't flash the 2.1 kernel. When do a fresh install of fusion, it flashes the kernel and that's why it works. What you can do is flash fusion and then do the restore after.
[Vibrant Android Development] jpnelson40:
Such a list would probably cut down traffic on Team Whiskey's threads (TW), especially if it were a "sticky" post right next to the original one (OP), and even better if there were another Frequently Asked Questions (FAQ) one next to that, which explained each of the acronyms used in these posts.

But I fear the addictive quality of the process would be broken by this scheme, so many would-be posters would sneak away to other, less worthy, projects; or find themselves bored and listless, catching up on sleep, or drinking instead. Maybe one or two of them could substitute volunteering to keep up the Issues or FAQ posts, but that would still leave so many....

So maybe these aren't such good ideas.

Jack
[Vibrant Android Development] Insomaniac10:
yah i know what i did wrong and how to correct it, only problem is i cant correct it because i cant get into recovery (obviously i want to avoid ODIN

IF

possible). it was through my own carelessness, but this adb recovery issue is still stinging me...ive never seen it before...i didnt know a kernel/ROM mismatch could lead to STOCK recovery problems.
[Vibrant Android Development] tjhart85:
My apologies, I was referring to the top half of your post (telling people to put a 2.1 kernel on).

For your issue, can you normally get into Recovery with the button combos.

Can you currently get into Download mode with the button combos? Not saying to Odin, just trying to see what you can and can't do.
[Vibrant Android Development] GalaxyS2k10:
The only problem with this method you mention is he already soft bricked. He can't get to the recovery menu at all.
[Vibrant Android Development] Insomaniac10:
Access download mode via adb: yes

Acces recovery via adb: no

Access download via button combo: havnt tried

Access recovery via adb: no

if i try recovery via button combo it sticks at vibrant screen....right after doing that i will type "adb devices" and my phone will show up as in recovery mode, even though i see the vibrant screen >>>>> same goes for if i type "adb reboot recovery", my phone screen will go black as if its booting into recovery, but it just sticks on vibrant screen, but "adb devices" still says im in recovery
[Vibrant Android Development] moonfire711:
Well, regardless of what is causing the issue, it is a known issue and may even be causing a problem with the phone when it's plugged into the charger. You can read what I am talking about if you read the OP of the thread for R2 on the Whiskey thread. All I'm saying is that something is conflicting in this rom with my usb connection. Has been working fine with 2.1 but now with 2.2 it is not working. Whether it is due to the ROM or the way certain OS's are set up, the problem still remains and that is the point. Not that it is there for everyone, but still for some.
[Vibrant Android Development] tjhart85:
I was quoting someone else & didn't trace it back to see that he was talking to the same guy I responded to (sorry).

I've seen other sites that have a WikiPost that's immediately after the OPs that people can edit themselves with common issues or updates.

This site REALLY needs something like that so all relevant information and updates can be kept in one place (since it's too much work for the OP ... not sarcasm! please don't take it as such!).

Make it so people who ask questions in it get a temp ban to prevent it being used as a chat board and we'd have a very nice tool at our disposal.

Well, sounds like the simplest way to fix you is to get you to Odin back to stock (since you have access to download mode, but can't access recovery). Once you're on stock, you can just Nandroid yourself back to where you want to be.

Have you used Odin before and can you access Download mode with the key combos?

Take out battery

Plug into USB

Hold down both volume keys

Put battery back in

Sometimes Odin can crash and then if you can't access with the key combos, you'll have a real brick rather than a soft brick. As long as you can access it with the key combos, you should be nearly fullproof.

I've never had my SD card get cleared doing an Odin, but if you want to careful, you could try 'adb pull /sdcard ./' and see if that'll pull all your files off just to be on the safe side (your nandroid and Titanium backups if you have them would probably be important enough to warrant this at least).
[Vibrant Android Development] funeralthirst:
gps still isn't working. 0/10 sats. anyone else have broken gps?

should i post a logcat?
[Vibrant Android Development] icandy75:
I'm having issues as well. They suggest we do a factory reset but I haven't had a chance to try it yet.
[Vibrant Android Development] Insomaniac10:
no ive never used ODIN but if i have no choice i guess ill have to bite.....its just bugging me that I cant access stock recovery, what would cause that?.....id rather see if theres a fix for that first before wiping my entire phone and going through that headache (is there any way to ONLY flash stock recovery via odin without wiping phone??)

PS - i updated my explanation, check it out...i feel its a little more clear
[Vibrant Android Development] ScratchSF:
Count me in that same boat. I'm going to reset/reflash when R2 comes out and see if things improve. It was working under Bionix and Fusion. But given that *everyone* isn't complaining about it, I'm going to assume that I just did something wrong in the flash and reinstall.
[Vibrant Android Development] icandy75:
Don't be scared of ODIN, just use one of the newer versions and it will be a piece of cake. I avoided it like the plague myself until I had no choice two weeks ago. Now I wish I would have tried sooner. It's nice to get a fresh start.
[Vibrant Android Development] GalaxyS2k10:
Odin is cake man, just make sure the driver is loaded in your device manager. Start odin, you'll see one of the com port lit (meaning it detects your phone) set the pit and tar file on the right and hit START, wait and then your done. It is easy if you want to learn something, very hard if you resist with all your might :P
[Vibrant Android Development] djkdawg:
if you can access the stock recovery, download clockwork and rename the zip file to update.zip, put it on your internal memory card using a flash drive or something, and then boot into the stock recovery and then choose reinstall packages.
[Vibrant Android Development] atlaswingpasaway:
if everyone else is using Vista well, that COULD be a problem because sometimes drivers arent found and installed properly. Vista has a lot of problems, one of which is the bluetooth stack that made me spend a day just to connect my BT adapter.

with windows 7, it connects right away and there's not even a need to break a sweat.

i've been using windows 7 a week before i got my first vibrant so i've no experience with vista+vibrant.
[Vibrant Android Development] tjhart85:
But, the problem is he can't get into the stock recovery at all.

Well, this link:

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

Has a link to a stock kernel ... since it's in reference to a previous version of clockwork that was actually flashed to the phone rather than just an update.zip, I think that might solve all your issues.

You would need to Odin flash it though.

Either way, I would assume you would be able to boot since you would now have the proper kernel for the ROM you have loaded currently.

If you go the Odin route, make sure you get Odin 1.3 (or higher if one now exists)....1.0 was buggy and crashed for a lot of people.

Also, at this point, we're kind of trashing this thread.

If you need any help, drop me a PM and I can try and give you a hand over GTalk or AIM or something and then the latest post can just be updated with what eventually had to be done to fix you (that way the info is shared for others w/o needing all the back and forth in the thread)
[Vibrant Android Development] Insomaniac10:
ill try when i get home....thanks for your help FOR REAL this time ;)
[Vibrant Android Development] tjhart85:
Yeah, my apologies for that. I either need to edit my quotes or address the whole thing rather than half-assing it like I did & making sure no one knows wtf I'm talking about :-)

Worst case, Odin back to stock, it sounds scary and time consuming, but it literally takes no more than 10 minutes tops.

Generally, when things are really bad, flash Froyo That Doesn't Brick and then flash stock JFD over it.

Once you've Odin'd, your recovery should be good again, and then you can just apply your Nandroid.