yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] DonutYankee:
Not sure where people are getting recovery issues. My phone boots into recovery just fine, did so with 1.0 and 1.1. Are these the "newer" hardware locked phones that are having trouble booting into recovery with this new kernel? (I got mine the day it came out, apparently before they started selling them hardware locked.)
[Vibrant Android Development] deutscher3891:
Is anybody else experiencing the issue of swype not picking up words that are double lettered? like apple, settle, etc ... of course after i type them in manually and then space they get picked up because they were manually added to the dictionary.
[Vibrant Android Development] xitsxjack:
Not sure, I just flashed the update for the hardware locked phones, gonna re-flash this rom when I get home to see if that helps.
[Vibrant Android Development] mulcahyd:
I can get into clockwork recovery fine. Thanks.
[Vibrant Android Development] Malike25:
I just loaded the calendarprovider apk and it started working after I did a reboot
[Vibrant Android Development] y2k1ltd:
Just curious, anyone else having issues with bluetooth? I just noticed if I have a bluetooth HS connected (Jawbone Icon) and I disconnect or turn off bluetooth, my audio sounds do not play.
[Vibrant Android Development] ram130:
So majority of the clockwork soft brick are from using an outdated version..oh well your fault :D..

Well I did some research on this and found that when the phone shut off, it was doing it a lil early and the indicated was off by a few. I noted it when I plugged the phone in to charge and the battery icon started charging from 20% or so (how much the icon was filled with green). In other words not from a supposedly dead battery. This would in turn mess up the calibration which comes from flashing so much.

Anyways, the method corrects that and give that extra back to the rom to learn. If you will, note how after your phone dies after doing my method you can no longer turn it on after 4 trys compared to before? That means the battery have been calibrated properly and the rom now knows the real value. It's along story, you just got to trust me on this one.

I've done battery research with the nexus one with these guys:

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

Feel free to read through and you will see we've done alot :D

So I've picked up quite alot along the way.

And my method corrects it. Just trust me :) ..
[Vibrant Android Development] xitsxjack:
Out dated version of what?
[Vibrant Android Development] ram130:
clock work..at least I think thats what is causing it. I remember they release a new version just last week for 2.2 support on the Vibrant.
[Vibrant Android Development] ram130:
having issues with bluetooth cutting out here.. Not sure why. Works for 5min of music and then cuts out at random intervals. Never had the issue before.
[Vibrant Android Development] DrunKenG:
Did they change the bluetooth stack in this build? I'm wondering if someone could test if Wiimote controller/IME app works on this ROM.
[Vibrant Android Development] ram130:
this might be samsung doing..
[Vibrant Android Development] ram130:
Dear Anderdroid,

I got two issues which might just be out of your control. I realize with just 15 apps using memory (50mb free) the phone was doing alot of swap activity which causes a lag here and there and cpu usage. So I hope you can optimize the way the phone swaps.

I used my phone moderately today in between my mid term classes. Uptime was around 20hours with a charge over night. Unplugged at 7am(7hours). Take a look at how hard it was working:

phone started to slow up:

CPU was constantly being pinged even while sleeping and guess by who?

Seems the memory issue is causing more issues than it should:

Never had the issue before this rom. SO I don't know what is up. Otherwise everything else is ok. Or I could just be going crazy :D

I just have ONE other issue right now and that is with Bluetooth streaming CUTTING OUT for long lengths at random times. Any thoughts?
[Vibrant Android Development] DonutYankee:
Speaking of which...I'm trying to recondition my battery again. Trying to run it down. It's been on critical low for over an hour. Took 15 minutes of Asphalt HD and then first 20 minutes of Avatar to finally kill it. Talk about metering being way off.
[Vibrant Android Development] ludachez:
Im going to try that battery recondition from Ram...anyways, you also say the soft brick was from an old CWM? i have Rom Manager pro and right before i tried to boot into recovery i reflashed the latest and then hit boot into recovery. app is also up to date so i have no idea why it would be outdated. i see in the OP it recommends flashing the recovery, and then manually booting into stock recovery, and reinstall package. been scared to try recovery since, should this work?
[Vibrant Android Development] hurrpancakes:
I downloaded v1 of jk2 aosp, and installed the oclf. Later, I noticed that v1.1 was available, so I installed the lag fix and flashed the new rom. Now, when I try to install the lag fix, it says I appear to have a lag fix already installed, and "playlogos1 less than 5kb"

Does anyone know how to fix this? I don't have any fixes installed.
[Vibrant Android Development] _Donovan_:
I am having an issue. When I log into "what the doodle" I get logged into some one else's account. Not random people but the same account. And I can see others are getting logged into it too. i don't know who's it is but if the dev had a wtd account and the profile pic was green white and red looking flag, well someone changed it to some man parts. Not,me.
[Vibrant Android Development] murse:
I've noticed this same issue with the kswap0d process. I use an app called Watch Dog to alert me of processes using too much CPU. After loading this ROM, this process throws alerts a few times a day for using over 40% of the CPU.
[Vibrant Android Development] player4lifeov:
Phone says

E:<ossomg bitmap indeterminate1

(code-7)

E:<ossomg bitmap indeterminate2

(code-7)

E:<ossomg bitmap indeterminate3

(code-7)

E:<ossomg bitmap indeterminate4

(code-7)

E:<ossomg bitmap indeterminate5

(code-7)

E:<ossomg bitmap indeterminate6

(code-7)

----Install from packages

"Finding UPdate packages"

THis happened when i tried getting into recovery. :(

NOw the phone won't boot or anything it just stays stuck at the above screen or whatever.

Oding won't recognize and I can't get into ADB

Please help!

UPDATE: so I read earlier post and figured out how to reboot but now I can't get into clockwork recovery or else the same thing happens. Basically anything that has to do with recovery won't work on the phone
[Vibrant Android Development] stevewabc:
Recovery HOSED:

This is how I got it repaired.

First off Install Odin and Adb

Start up Odin plug your usb into the phone: turn on the phone and you should see a yellow block show up: ID:COM

Then Open the commandline (cmd) start adb reboot downloads

after the download screen comes up the use Odin to restore the phone

3 days later I got it!:D:eek:
[Vibrant Android Development] player4lifeov:
So the little yellow block comes up but then it goes away when i reboot into download mode? Any idea why?

Odin only sees phone when its actually on.
[Vibrant Android Development] krazykidd:
Earphones as headset

Another issue I'd like to report is that I used to be able to use my line in -> tape deck as a way to have the call come through my car stereo (don't hate, I drive a car with an older receiver) and now that function is kind of broken. I can play back music through the 3.5mm jack, but it won't pick up calls.
[Vibrant Android Development] HYE_TECH:
yeah, I was thinking about that as well. I just recently got a replacement Vibrant and this one is hardware locked because I can't press the 3 button combo to get into recovery/download mode.

I flashed 1.0, it seemed fine then I notice 1.1 came out so I flashed that but it had some minor bugs I didn't like, my wifi would connect and my data didn't work. I like 1.1 because it did run pretty smooth for me especially over 1.0 and it had the samsung cam app but I always use wifi so I flashed back to 1.0. As soon as I flashed back to 1.0 i couldn't enter recovery. I keep getting that E:Missing Bitmap Indeterminate1 screen. Now I'm stuck on 1.0 because I don't have access to a PC.

I'm still looking for a solution to my problems...I haven't found any but ODIN.
[Vibrant Android Development] deutscher3891:
I am having the same issue with my recovery and I pre-ordered my Vibrant
[Vibrant Android Development] player4lifeov:
I got my phone when it first came out. I never had an issue with recovery until I flashed this rom. Not to flame the rom or anything.
[Vibrant Android Development] johndoe411:
V1.1 comes with ROM Manager pre-installed, right? I assume this version of ROM Manager already has the latest version of Clorkwork Recovery, no?

Just checked ROM Manager, I was using Clockwork Recovery version 2.5.1.2 and experienced soft brick.
[Vibrant Android Development] johndoe411:
I have one of the older ones (not hardware locked) and also experienced soft brick when getting into clockwork recovery.
[Vibrant Android Development] stevewabc:
No Clue but l am taking it that your phone is not booting up.. My Question is after the install of the rom did it boot up? and if so this should work. it was after rebooting my phone is when I found I had a problem getting it back up.

Start up Obin

Plug the usb into the phone and install the battery you should get a green battery showing up if not pull the battery out and repeat up to 6 times to get it. you may need to unplug the usb in and hold down the up/down and power keys and let the Vibrant boot screen slash 5 times ( power circle ) then repeat the steps. must get the green battery or you will not get any ware.

We got the green batter? good now unplug the usb then hit the power button it will reboot your going to get the vibrant screen plug your usb in and now the phone will boot up.. ( KEEP IN MIND ODIN BETTER BE RUNNING) now you will or should see the yellow box and it will not go away.

Phone is up and we got a yellow box we are ready to start the adb.. and reboot it to download. then your phone will show the download screen and your ready to re-flash with odin... so you no it took 3 hrs to re-flash it. lol what a ***** this was. I love the rom it rocks but this recovery problem needs to be fixed.. I will try it again but WOW is all I can say.. I hope that helps someone to restore there phone.
[Vibrant Android Development] player4lifeov:
I'm able to boot and have Odin in the background. It even says Com4 or whatever and in the bottom it says added. THen i go to adb reboot download and it goes into download mode. The moment it does that, it disconnects me from Odin and it says removed in the message box. In the COm4 is gone also
[Vibrant Android Development] zoid_99:
Yep.. I can't get into recovery either with my pre-order. I guess I will attempt to oden.
[Vibrant Android Development] stevewabc:
Ok now im lost because when your in download mode it has to communicate and if it wont do that then your doa. When its in download mode try this once.... open your cmd

and try adb reboot.... if that works then its Odin if not im lost other then calling it dead..

This may be worth a try if nothing else works...

http://xdaforums.com/showthread.php?t=834297
[Vibrant Android Development] ohnoezmahfone:
This might not be a problem specific to this ROM, but I can't delete the default browser bookmarks. Anyone else experiencing this?

Btw, great rom, it's running really smoothly for me!
[Vibrant Android Development] ram130:
Downloading now..flashing in 3mins

I was gonna flash that my self today but I just said the feedback is not looking so hot..so I decided to hold off..then I see this rom come up, couldn't resist anymore :D
[Vibrant Android Development] DonutYankee:
Well it flashes the 2.2 kernel, so you should theoretically be good to go. Might wipe the internal SD due to going from 2.1 to 2.2 and the changes in how things are organized.
[Vibrant Android Development] anthonys2r:
Did you rebuild the ROM from the source leaked or did you just update the GPS & Wifi calling drivers?
[Vibrant Android Development] ram130:
Flashing now...i feel nervous :(

Oh..well good thing I followed my mind and backed up :D
[Vibrant Android Development] richiehd:
If I flash this and then want to go back to the J16 rom, what would I have to do? Flash a J16 Kernel first in clockwork and then flash the J16 rom afterwards? I just want to make sure I have a way back to J16 in case the battery isn't as good as the Eclair release.
[Vibrant Android Development] ram130:
Rebooting now after flash..gonna make this bad boy sit for 10mins after it boots then reboot.

I see you have the 1.6 ANDROID boot up screen :D

+1
[Vibrant Android Development] ram130:
THe rom booted up!! waiting on that 3G icon now...not bad so far!!

OK ITS UP..waiting 5mins..any questions??

+2
[Vibrant Android Development] ram130:
Everyone..Remember to do a Battery ReCondition after flashing this rom!!

Here are the steps:

http://www.teamwhiskey.com/home/battery-conditioning
[Vibrant Android Development] aczarney:
Make a nandroid back up. If you want to go back, use ODIN to flash JFD, then restore your back up. Then flash JI2 or JI6 (depending on your preference) because your modem will be JFD.
[Vibrant Android Development] Anderdroid:
Flash any of my Vibrant AOSPish v1.4 JI6 builds straight through ROM Manager or Clockwork Recovery to go back to Eclair. They will flash a JI6 kernel and JI6 for you right from this, and you're good to go.
[Vibrant Android Development] ram130:
OK i think i have 6 mins left out of 10 before I reboot..anyways' it's smooth so far(scroll through home screens)..anyone else flashed yet?
[Vibrant Android Development] ram130:
You should note this as an FAQ in the OP :rolleyes: so those that see your rom for the first time won't have to second guess and ask.
[Vibrant Android Development] Anderdroid:
You don't really have to wait that long. Just wait for the 3G/E and media scanner to finish.
[Vibrant Android Development] aczarney:
It's funny, I love Bionix Fusion. But Obsidian felt so unfinished, I was really disappointed. Until this showed up I was just going to wait until the official 2.2 release hoping one would be perfected by then. But here's hoping this is not too bugged to use!
[Vibrant Android Development] DonutYankee:
I'll flash this in a few. Just went back to JFD to start a clean slate.
[Vibrant Android Development] ram130:
Well I'm gonna find out soon!! :D
[Vibrant Android Development] ram130:
Oh ok, this thing boots fast..Guess I'm a lone ranger on this one then :D

Yea I do it as a pre caution to make sure everything has settle..anyway I just rebooted..gonna explore a bit..any bugs you forgot to mention?
[Vibrant Android Development] richiehd:
No need for me to reflash the kernel myself? You're the man.
[Vibrant Android Development] glensta:
Just flashed this - waited about 7 minutes, no 3g or E signal. Tried toggling airplane mode - didn't work - reflashing again.
[Vibrant Android Development] ludachez:
VERY excited here...ive been using AOSP 1.4 ji6 and its my favorite ROM by a LONG shot. i really hate TW and the samsung look but like most of us love the hardware. i metamorphed the ji6 rom and its great so i have high hopes for this, its downloading. Anderdroid thank you, i would love to donate next pay day. keep up the great work.

Would Eugene's kernels work on this ROM? He has several OC kernels for 2.2, ad i guess they would work, i will try and let everyone know.
[Vibrant Android Development] Bugdog:
My recovery works fine - thank god, b/c I'm flashing back to JI6 AOSPish. Not the fault of this ROM in particular, I think JK2 is just way, way too unreliable. Yesterday, while on wifi calling, the person on the other end was unable to hear me. Today, wifi calling just doesn't work, but with wifi turned on (necessary due to poor service in my house) it shuts off my cell radio - so no way to use the phone at all. I think JK2 is just clearly not ready for prime time.

Love your ROMs Anderdroid, look forward to one built off a more stable Froyo base. Thanks!
[Vibrant Android Development] stevewabc:
Bugdog let me ask you this what steps you took to install this? if you don't mind me asking... it maybe the way you all are installing the rom. Being there are a few ways to install rom's it could vary well be us with the Problems. I want to test it by installing it the way you all did that were successful. now that I recovered form 3 days of hell. :p;)
[Vibrant Android Development] tomm454:
Thank You 100x
[Vibrant Android Development] zoid_99:
Recovery - adb shell

When I boot into recovery it gets stuck at the vibrant screen however I can adb shell into the phone at this point. Is it normal to be able to adb shell into recovery? Is it useful for anything?
[Vibrant Android Development] player4lifeov:
Tried it adb reboot in download mode and it just said error device not found
[Vibrant Android Development] diaa08:
It's likely a kernel issue. It's a problem on all our froyo roms. TW has it as a bug, and eugene is aware of it too, but might have to wait for source before it's fixed. Out seems that the developers thought it would be better if it ignored headphones without a mic during phone calls.
[Vibrant Android Development] Bugdog:
I don't think it had anything to do with that - I've installed a good number of roms on this phone, and with this one was extra careful (wiped dalvik/cache/factory reset, flashed thru recovery). It mostly works great, but I can't afford to have it be inconsistent - I need a reliable phone. Thanks, but I'll be happy using JI6 while waiting for more stable Froyo ROMs!
[Vibrant Android Development] stevewabc:
Thanks, and I sec that back to JI6 as well.
[Vibrant Android Development] JD76:
Last night my Rom Manager updated in Market... im scared to use it though.. Ive been lucky that the last few times I get stuck on the Vibrant screen, it automaitically reboots after pulling out the batt 5-6 times... im scared that magic wont work again. Anyone else updated and tried?
[Vibrant Android Development] zoid_99:
That's the version I used today to try and get into recovery. No go... Stuck at Vibrant screen.
[Vibrant Android Development] Bugdog:
I had not tried before the update b/c I was scared of the soft brick - I have a mac, so no Odin - but after the RM update, I figured at some point I was going to have to try, and it worked. So I don't know if it changed anything from before, but it did work for me ... If I were you, I don't know if I'd try it unless/until I really needed to.
[Vibrant Android Development] JD76:
Im on a Mac too so im afraid but sooner or later im going to have to... My batt life is about 10 hours I wanted to wipe batt stats and recondition.
[Vibrant Android Development] CappyQ:
I was eager to try this, but I decided to watch the thread for a few days before replacing JI6. Guess I'll wait for the next official Froyo leak, as this one seems to have some issues with WiFi calling, battery life, RAM swap and recovery. But I do hope to go with AOSPish when it's stable--it'll be my first custom ROM on the Vibrant!
[Vibrant Android Development] rbirg:
This rom is pretty sexy. Gonna try this for a day or two and see I have any similar issues.

Thanks for making this.
[Vibrant Android Development] krazykidd:
Hmm, I would have thought it would have been a hassle for any user if they were listening to music via headphones (non-mic) and then got a call... Looks like someone along the line dropped the ball. I wouldn't really consider it a "bug" though. Oh well, time to go find that PS3 headset again. Thanks for clarifying that it's likely a kernel issue.
[Vibrant Android Development] deviusdragger:
Ive been rocking this rom since it was released, currently on 1.1 and have no complaints. wifi calling acted up a little bit, but nothing a simple restart of the application couldnt fix. This is my daily driver phone, took it off the charger at 10 a.m yesterday and by 10p.m i was at 5 percent. Which is so much better than what any other roms gave me. I have i constantly syncing 4 email accounts and messaging all day long!!! I did some web browsing probably about 30 mins worth. I also have the oclf running on it, followed instructions on the first page and it worked just fine. So to everyone thats scared to run this, quit being a pansy and just do it. You wont regret it!
[Vibrant Android Development] andeeroid:
I too had the same problem with Recovery mode with this Rom. I had tried 4 times and all soft bricked, I had to use Odin 4 times to get out.

I would not recommend going into recovery mode if you do not have PC. :O

I suggest that you guys wait until the fix comes along.
[Vibrant Android Development] zenchili:
I really liked this ROM. Actually it was my first time and I thought it went really well. I was enjoying it then read about reconditioning the battery. When I went into recovery to wipe the battery stats I soft bricked. I didn't woery too much since I'm not hardware locked and I knew I could Odin back to stock, which I did. I switched to Obsidian V2 and although its stable I really likes the vanilla experience of AOSP.

Obsidian v2 is not as fast as this ROM but at least I can get into recovery.
[Vibrant Android Development] enuro12:
Alright... Soft Bricked for the 2nd time!

This time i'm %100 of the steps i took and i can apparently reproduce it... This is my first rom attempt so flame me if necessary....

Also thought i should note, i ODIN back to stock and started over. The first time i did restore all my apps, the second i ONLY imported my contacts from CVS, no other changes.

Steps i took to brick for the 2nd time (same button pressed to brick it the first)

1. 1 Click Rooted the phone

2. Installed Titanium Pro

3. Backed up Phone

4. Flashed using Clock Work

5. After the phone Rebooted i went back to Rom Manager & Clicked Boot to Recovery (so i could do the battery reset)

Wham Vibrant Screen....

A note for the others stuck here (I'm up to page 42 and saw several)

Here is a video on how to use Odin & Get into Download

I'm now reading lots of guys with the same issue... Knew i pulled the trigger to soon.

sorry
[Vibrant Android Development] ugokind:
TESTED OK BUT 3 issue please read .. :)

disabled voodoo, and the applying was perfect

the OS is very good and fine, sometimes it slow down.. specially if I use SET CPU and the battery is below 30%

1st: I tried to manage some ways to kill Unwanted Apps.. because of the battery that goes down very quicly (and has less of 30days!) and I see that some service never kill (I say.. never!)

they are:

Mailservice (tha icon with the pink optics)

Download Manager

SNS service

WiFi Calling

SO even with battery improver or Task Killer I can't remove them..

how to do?

2nd: I'd like to use Voltage mod and the beautiful and good

Default [KERNEL] SetiroN i9000 SuperOptimized ReOriented v1.2.5/1.3.4 ULF OC/UV BFQ 343Mb BLN

this kernel has a lot of features.. but i'm afraid to decide if use it or not..

3rd: is better to apply all EXT4, or JFS?

4th: how to change the bootup and shutdown logo? I tried to replace System/app/playlogo and playlogos1 but still no working

the main issue is that when I plug Earphone the audio is not switching in the small earcaps.. it's not automatically, and that problem repeats if I switch on a bluetooth earphone
[Vibrant Android Development] ugokind:
I did the same damn things.. but the cause was that I used Odin and clicker REPARTITION.. so the only way to revirginize the vobran is to follow only one Odin package that, respect to others.. was good for me

***********************

GUIDE and FILES HERE

http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
[Vibrant Android Development] sablemonster:
Anyone else having issues with certain apps not showing up in the app drawer? For instance, Angry birds us only accessible through market downloads for me.