yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] djm3ph:
I knew there was a problem with the GPS. I hoped it would have been fixed by now so i didn't read 450 pages of posts to figure it out.
[Vibrant Android Development] masr1979:
For those that are having bootloops, as was previously said, format/wipe cache, dalvik cache AND system (through the mounts & storage menu in CWM recovery). I had bootloops for the first time going from 30 to 31. I flashed and wiped only cache and dalvik 2 times, before I remembered to also format system and it worked right away.

You'll have to reinstall gapps, but since you won't touch the data partition all your apps will still be there and they will be associated with your account when you log in.
[Vibrant Android Development] db3:
there appear to be two other gingerbread roms that claim gps is working. you might give one (or both) of those a try if you need gps now...
[Vibrant Android Development] Cesarp 24:
#31 with glitch kernal. Success, very nice.

Sent from My CM7 Monster
[Vibrant Android Development] noakcess:
I notced a slight bug....or is it?

when you plug in any earphones the audio keeps playing from the speaker and not through the earphones. I thought that I had burnt out the audio jack but just to try i installed a prior rom and it worked without a hitch.

is that a "on my list of issues" list or the functionality isnt going to be incorporated in the near future?

Thank you for any replies
[Vibrant Android Development] jimmyhawk:
I just tried and all is good here. Maybe your phone, not sure. Make sure volume is up and earphones are all the plugged in. I'm sure you did that but its the only answer I got...lol. sorry
[Vibrant Android Development] xriderx66:
just tried as well.

its just you.

Try a clean odin and a reflash.
[Vibrant Android Development] gamikzone:
yes re flash/ wipe factory reset if that doesnt work odin to JFD :D
[Vibrant Android Development] djf8:
I know it's a work in progress and I'm not whining/griping at all. I am just curious though if other peoples audio quality while on a call was bad/worse on the CM nightlies compared to a TW rom?

I know my call quality was really really bad on nightly #30, I would have full bars and it was still hard to hear people and people on the other end had a hard time hearing me most times. (I know about the mute/unmute glitch, this is all above and beyond that.
[Vibrant Android Development] xriderx66:
being with CM7 from start, it has gotten better.

still doens't match TW. but if you still have those issues

theres a fix:

mute and unmute and its fixed. have to do it every phone call it happens though
[Vibrant Android Development] jrod33084:
Does the latest nightlys have BLN implemented with the stock kernel yet or still disabled? I'd rather use the stock kernel but will flash another for BLN.
[Vibrant Android Development] Joy2DaWurld:
It's not activated anymore. Custom kernel needed
[Vibrant Android Development] apollo15rover:
Wifi and phone are good but bluetoof broken .... anyone else?

Edit.. nevermind.. just popped on..
[Vibrant Android Development] bigtom624:
My Bluetooth works just fine and I never had any problems with my phone bootlooping after flashing any nightly's ever. Today however I did have a network problem. I could not connect to T-Mobile's network at all. After a reboot it was fine. I think it might be from trying out some of the other kernels. I'm gonna Odin back to stock and start from scratch and see how it goes from there.
[Vibrant Android Development] brnagndan:
There's this awesome thing about Rom Manager. People leave comments on each nightly build and let you know whether or not GPS works because that's all they ***** about every ****ing time.
[Vibrant Android Development] movieaddict:
+1 brnagndan lol
[Vibrant Android Development] mulcahyd:
I did that and still my external does not see my files. It says folder or files does not exist. Any possible work arounds.Thanks.
[Vibrant Android Development] barribow:
I checked, I don't have that file. I also noticed that my ringtone has changed as well. But, it was not in the external sd card.
[Vibrant Android Development] zmattmanz:
Any option to get line out working on the desk dock? It seems like I tried this on an earlier build and used sounddock redirector but not it says the kernel is not supported.
[Vibrant Android Development] Phateless:
For those of you with flashing issues, check out what I did. First attempt gave me no boot loops and no bugs.

Install as normal, let it boot. Reboot into recovery and flash your google apps, but before you reboot do another wipe data/factory reset and also wipe cache and dalvik. Then reboot and give it a few mins to settle before you set up.

This made things much more stable for me.
[Vibrant Android Development] xriderx66:
the battery on this new 31 is murduring my vibrant

i havent done ANYTHINg but got on facebook for 10 minutes and my battery's down to 56% lol
[Vibrant Android Development] hockeyrcks9901:
Anyone else having an issue with the proximity sensor when on a phone call?

I can never get the screen to turn back on when I pull the phone away from my face. I had the same issue occasionally on other ROMs but it was normally just a dirty screen and the sensor thought it was covered. This time, the sensor is totally clean but it still does this.
[Vibrant Android Development] beren28:
This gives me a wonderfully wicked idea . . .
[Vibrant Android Development] kinghorsey:
I know that battery drain is higher for some but everyone has to keep in mind that flashing your phone takes a toll on the battery.

If you're flashing nightlies your battery isn't going go get enough time to calibrate properly.
[Vibrant Android Development] droidfan77:
Sorry to hear 31 is killing your battery. I have found that I'm getting much better battery life on 31 over 29. 29 seemed to kill my battery. Have you tried reconditioning your battery since you flashed 31? I've found that it can make a huge difference.
[Vibrant Android Development] nedlog:
Old news but 31 flashed no problems.
[Vibrant Android Development] Pmasonfirth:
How would you condition a battery properly then ?

EDIT : Never mind.. Google was my friend :)
[Vibrant Android Development] patpat09:
I just got a vibrant spent quite a while to install the CM7 following the instruction given.

sorry for being stupid, is the camera not working on this?
[Vibrant Android Development] atinm:
try screen off/screen on before trying camera. there is a glitch which forces us to do that right now sometimes.
[Vibrant Android Development] atinm:
20110509

- 720p recording

- libcamera hacked to support gtalk video

is uploaded.

Please reinstall GApps 0503 after you install this update.
[Vibrant Android Development] core123:
downloading now will try it out and report back
[Vibrant Android Development] ferhanmm:
god dam you are dedicated. Thanks for working on this so much man.
[Vibrant Android Development] core123:
720p recording working great for me. awesome addition. didnt try gtalk because i dont have a front facing camera though
[Vibrant Android Development] awolbrin:
still, i have updated both cm7 and the kernel this week...

(cm7-05042011),(kang05042011)

what can i do?
[Vibrant Android Development] numberoneoppa:
Flashing now. U+me -> babies?

Edit: I could be wrong but it seems all of my notification sounds changed...

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] cojonesx:
stop using the kang kernel if you have problems, revert back to the one that comes with the nightly downloads and see if you still have the problem before you report it here
[Vibrant Android Development] Chortles:
Install error

Attempting to go from a rooted JFD (as in Eclair/2.1) to CM7, using CWM 2.5.1.2 (the latest version that ROM Manager seems to support in Eclair?)... now, the "initial" kernel seems to install fine and gives me CWM 3.0.2.8, but here's what I get when I then try to install the CM7 "initial" ROM:

Before the progress bar can fill up though, the device reboots and I end up back at CWM. What gives?

FWIW, when I would try to install the "initial" from CWM 2.5.1.2/JFD, I would get an error message about the modem.bin failing to install, aborting the installation. Do I actually need to flash a 2.2 ROM or something first?

(I keep using JFD as the base because it's the only one I have "an" Odin for.)
[Vibrant Android Development] GameOver69:
Yep happened to me too. All my notifications are changed.
[Vibrant Android Development] skater4690:
I had the same problem just read the op more carefully install kernel and have initial cm7 on root of SD card and after you install the kernel reboot if it doesn't automatically start reboot again and it should install
[Vibrant Android Development] atinm:
Already got the one - and he's all I can handle!

If it happened, it happened due to upstream changes - we don't change that stuff. Teamhacksung only does SGS specific stuff, so the rest of the stuff comes from CyanogenMod repositories.
[Vibrant Android Development] cojonesx:
FWIW it didn't happen to me, my notifications are unchanged after 20110509 build
[Vibrant Android Development] adyscorpius:
On the phone mute/unmute thing, just noticed something I'd like to share... Might help the users temporarily and the devs in troubleshooting...

I used another phone to call my number and simultaneously check for various methods to figure out when exactly does the voice issue happen...

If you pick up the call and immediately put it to your ear, or technically, turn off the screen using the proximity sensor, then the other phone can hear you clearly, in short, you dont need to use the mute/unmute fix.

If however, your screen remains on during the 1st 1-2 secs of the call, the sound goes awry...
[Vibrant Android Development] archie53:
To the people, like me, who's notifacations changed. Did you also flash the newer gapps? I did and mine changed also, for mail and messaging. Just wondering if that is what caused the change.

Sent from my CM7 Powered Vibrant
[Vibrant Android Development] cojonesx:
I didn't have a custom notification on mail and messaging, I always change just the default ring and notification.
[Vibrant Android Development] hitman818:
Is anyones camera working on the new update? The wait and force close option comes up everytime I use it, and I cant go back without pressing home or force closing it.
[Vibrant Android Development] apollo15rover:
No, my regular camera works well but the cool ProHDR program I got for it keeps crashing. I'm going to wipe cache, Dalvik, reset permissions and see if that does the trick. It's something I can live without but would still like it back eventually.. I get some cool effects out of that and it's not the same trying to do the same with photoshop..

[Edit: Fixed! The solution above did'n't work but one thing I forgot to do was simply uninstall and reinstall - did so and fixed permissions and back in business now! One thing I didn't try was wiping program cache and data - that might do it also.. ]
[Vibrant Android Development] atinm:
Wipe camera data. Wipe everything you can think of if that doesn't work.
[Vibrant Android Development] fernkomoyo:
Oh Gosh, Mute/Unmute Problem, Not Yet Fixed :(
[Vibrant Android Development] dxtrlabs:
yea same here i tried reconditioning but same im getting a 15% drane per hour. and only using wifi face... some im.... itust be the gps stuff or the new aries stuff???? or maybw im unlucky like you... j/k
[Vibrant Android Development] locoarmo:
Changelog for tonight says added galaxy s phones. Any idea what that means?
[Vibrant Android Development] Phateless:
Hopefully that means they're adding the vibrant 4g. That would be awesome, although unlikely.
[Vibrant Android Development] treyvaporizer:
Maybe it means they are making a release candidate! Idk haha but that would be cool.

Sent from SGH-T959 (CM7)
[Vibrant Android Development] scrizz:
that wouldn't change a thing.

it's just a name. ;)
[Vibrant Android Development] treyvaporizer:
True, true. Hell, these are pretty stable when you don't flash them wrong.

Sent from SGH-T959 (CM7)
[Vibrant Android Development] hoquangthaiholy:
I lost 10% battery drain only with 7m standby phone ??? very bad :confused:

I see a next build: "new prebuild kernel to fix video recording issue". :). I hope it good now. I praying .....
[Vibrant Android Development] treyvaporizer:
Which nightly?

Sent from SGH-T959 (CM7)
[Vibrant Android Development] hoquangthaiholy:
with #30. kernel Glitch V10C, modem i9000UKC1 (try testing).
[Vibrant Android Development] masr1979:
I don't know if you figured it out, but your external sdcard should be under /emmc not /sd/emmc. If that doesn't work, I would suggest you back up your sdcard on your pc, go into "Storage" under settings and reformat your external sdcard if you can.
[Vibrant Android Development] carlosmann22:
I had that exact same issue a couple hours ago. I had to pull out my battery because the screen wouldn't turn back on even after the call ended.
[Vibrant Android Development] ShermCraig:
Very true!!
[Vibrant Android Development] xriderx66:
no man, im dead serious.

I've been texting right now, but my phone's batterys been going DOWNNNNNNNNNnn

fast.

I always recondition, the CM7 way the manual way.

but it just is not working.

I have nothing on.

I dont have a data plan sooo thats not it.

I was just at the mall for 2 hours where there is no wifi so i turned it off, and i lost like 30% more

now i have 11% left i usually have 50% left at end of day because i barely use my phone. wtf is this **** lol i might flash back to 29 or something.
[Vibrant Android Development] boothten:
how exactly are you reconditioning? through recovery via "wipe battery stats"?
[Vibrant Android Development] ShermCraig:
31

31 is up now!!
[Vibrant Android Development] njuncos:
Reconditioning your battery should entail the following...

1) use your phone until it dies

2) charge your phone to 100% (in cm7 the only way to do this is with the phone on)

3) while plugged in, reboot to recovery and wipe battery stats

4) unplug and enjoy

5) repeat as necessary
[Vibrant Android Development] Trev420:
theres a battery calibration app on the market that works very well.
[Vibrant Android Development] wizern23:
has anybody had random reboots on 31 with the Glitch kernel?
[Vibrant Android Development] xriderx66:
In cm7 it's best to go into data/system and delete the battery stat.bin file

And that's what has worked for me on the other nighties
[Vibrant Android Development] hoquangthaiholy:
I flash this rom #31 on the way:

1. Flash stock ROM JFD.

2. Enter samsung recovery to flash update.zip (clockworkmod recovery from ROM manager). Reboot.

3. Enter clockworkmod recovery, flash this ROM.

4. Reboot once.

5. Flash KB5 Modem for CM 7.1. So, from the stock vibrant ROM, modem is KA7.

6. Finally, flash Glitch kernel V10C.

I charge to 100%. now, I'm 81% with 2h 54m 20s.

- Voice call 25% with 4m48s.

- Display 36% with 12m36s.

- Standby phone 18% with 2h54m19s.

- Idie phone 7% with 2h54m19s too.

- Android System 4%.

I thinks, in CM7, the phone and voice call make battery drain more than samsung rom. but, the display is less than. With Glitch kernel, the game is smooth, but SystemUI some lags. From #29, no voice in-call is gone (I guess).

While you ?
[Vibrant Android Development] Cesarp 24:
Ur probably getting reboots because your UV settings are too aggressive.

Sent from My CM7 Monster
[Vibrant Android Development] bearsfan85:
thats ~15hrs of battery use, beats my 8
[Vibrant Android Development] treyvaporizer:
Switched back from 31 to 25 after I saw my battery draining while on the charger...... :mad:

Sent from SGH-T959 (CM7)
[Vibrant Android Development] mikeku:
which are they ?
[Vibrant Android Development] defconoi:
Since they are troubleshooting GPS I think they re-enabled some logging, glad is causing battery drains and possible wakeups.
[Vibrant Android Development] ironlood:
I believe one is Blitzkreig and the other one is Simply Honey 3.8 Revolution ... the reason they work is because the are JVP based roms
[Vibrant Android Development] barribow:
Thanks for reply, no haven't

been able to fix it yet. I will try that too. Strange thing is that my ringtone changed too into something random.
[Vibrant Android Development] barribow:
It just got fixed by itself. Also the emmc works, first we have to hit the mnt on top of the page and then emmc. I have audio book player and before out was saying there is no book here and now it works again :)
[Vibrant Android Development] gamikzone:
What do you mean? I'm on build 31 but for some reason my external sd can't be read at all
[Vibrant Android Development] krazie1:
Nightly #32 is UP and Posted!
[Vibrant Android Development] ironlood:
Well I was gonna flash this but I had a drive by at my house and I figure for the time being I can't afford to have a phone boot looping if I jack something up and I need to use ODIN on my computer which is right by the Windows :-(
[Vibrant Android Development] jimmyhawk:
I noticed yesterday while on 31 that watching vids on youtube with wifi on I had to continuously wait for buffering, now this morning on build 32 no waiting and I'm using the same wifi. Not sure but 31 was the only build that gave me probs with youtube. 32 is kicking ass so far.
[Vibrant Android Development] jaikat:
Did it kick the mute/unmute problem's ass yet?!
[Vibrant Android Development] Binary100100:
How do you recreate the problem? I've never experienced it.
[Vibrant Android Development] jimmyhawk:
Not sure I haven't received a call yet, but while on 31 I never muted/unmuted and never got a complaint.
[Vibrant Android Development] jaikat:
Thanks for the feedback guys..

The problem happens when recieving a call, the other side can't hear you, or you sound like as if you're talking from another room.. Then you have to mute/unmute to fix the sound..

I'd love to know that this problem is gone for good.. Its the one thing thats keepin' me away
[Vibrant Android Development] wergeld:
Boot loop coming from 30 to 32. I installed via recovery. I wiped dalvik cache as mentioned earlier. I just got back to recovery and re-installed 32 and all was good. But I no longer have gapps. I had already installed the 6/13 gapps for 30.
[Vibrant Android Development] jimmyhawk:
Just flash gapps again, its no biggy takes but a minute and all should be fine
[Vibrant Android Development] jzero88:
WOW!!

Insane godliness battery life with Glitch Kernel. I'm flipping out right now. GLITCH is a must if you plan on using CM7.
[Vibrant Android Development] jimmyhawk:
I'd love to know that this problem is gone for good.. Its the one thing thats keepin' me away[/QUOTE]

Its no big deal to push twice, it can be done before the other party even knows you answered the phone
[Vibrant Android Development] jimmyhawk:
Agreed, battery life on 32 so far this morning appears to be much better than 31 for sure. On my phone at least.
[Vibrant Android Development] nedlog:
Just flashed #32 via Rom Manager, only did a Dalvik wipe (which is all I've been doing lately); Had to reinstall Gapps (which is also normal for me). Never had fruit loops (boot loops) as others have reported. So far all running stable.:D
[Vibrant Android Development] Hung0702:
What's the point of saying fruit loops if you're going to explain that they are boot loops? I don't think calling boot loops as fruit loops is something that'll catch on...
[Vibrant Android Development] crazy25000:
lmao...fruit loops....reminds me of cereal when I was younger :p
[Vibrant Android Development] dgsmith90:
I just tried the combination of GLITCH and #32. I started with 44% battery and was amused when it trickled up to 47%. Lol I'm going to have to let it drain all the way and charge it all the way.
[Vibrant Android Development] jaikat:
Yes it can be done, swallowing rice without chewing can be done also, but its just not the right thing to do..
[Vibrant Android Development] Phateless:
I do everything manually in recovery mode. Much more stable that way.

Wiped cache and dalvik, flashed 32, booted, deleted email and file manager, wiped cache and dalvik again, rebooted and running flawless.

For those with issues, slow down and let it finish booting before you set stuff up, especially on first flash/first boot.
[Vibrant Android Development] Oskiee:
Went from 26 to 32, and splurged a little installing glitch, all from recovery. I had a boot loop, so i ended up re-flashing 32, letting it boot, and then flash glitch again, no problems so far. Is there any kind of set up i need to do for glitch to get the amazing battery life ive been hearing about?
[Vibrant Android Development] nedlog:
What can I say...suppose I was just trying to be funny...I do like fruit loops though. Anyway #32 still smooth. Was on a full battery about an hour ago and now at 76%; have been an a long phone call and have been trying all my apps...so far so good.
[Vibrant Android Development] scrizz:
LOL the more people use customs kernels, the more they're going to be ignored.

;)

Just don't say I didn't warn you.

If you use a custom kernel, don't complain here.

:)
[Vibrant Android Development] apollo15rover:
Arrrgh.. curses! I'm melting I'm meltiiiiiiiiing....
[Vibrant Android Development] stncldtex:
could use some help

I flashed 32 w/ the glitch kernal and my bottom mapping is all screwed up. When I get into recovery to install my backup I get the top hat when I use the power button to select any option. Could someone please lend a hand.
[Vibrant Android Development] mohamobo:
They're actually already have been ignored..

no support for custom kernel here..

btw, skip to then next post...
[Vibrant Android Development] xriderx66:
Try asking that in the Glitch kernel thread, more help.

Anyways what I think is you flashed the I9000 one, theres a vibrant one in the I9000 section you flashed wrong probably.
[Vibrant Android Development] stncldtex:
Thanks, figured I did all working good now. Thanks for the help and not being a douche about it.
[Vibrant Android Development] aloxotls:
This is just an idea, but would it be possible to make an app that mapped the mute button to the power button during a phone call? Would make it easier to deal with the mute/unmute issue until it gets fixed.
[Vibrant Android Development] Arr MiHardies:
Flashed 31 yesterday. No custom kernel. Phone shut itself off last night while charging. had to pull the battery to power back on. Noticed if you accidentally swipe up on the app icon in the launcher, the dock disappears and you have to reboot to get it back. However, my main question is, what is the difference when your signal meter is green vs white. I'm seeing it both ways on this build, but its almost always white.

Also, I came straight from build 4, which had bln. Any clues to why it was disabled? will it come back? I'd rather not run other kernels
[Vibrant Android Development] ChristoA1:
I love this idea! You go to mute it, and it turns off the phone :D That way, you never are worried about the other side not hearing what you're saying...

....or did I read that wrong? ;)
[Vibrant Android Development] Phateless:
Green means connected to google services, white means not. Open google talk to reconnect.

Swipe up again to remove the hidden dockbar. Go into adw settings and either disable that feature or add some icons to it once you've swiped up to reveal it.
[Vibrant Android Development] Stevenjcarney:
Actually that's a feature in ADW. You can change the swipe gesture setting to show/hide the hidden dock. No reboot required.
[Vibrant Android Development] aloxotls:
I thought I seen the camera button mapped to take a pic and it did not turn the phone off as long as you were in the camera app. Same concept but with the mute button. honestly do not know if it is even possible just throwing ideas out there.
[Vibrant Android Development] ChristoA1:
I was only joking ;) It's actually a precent decent idea, except that I've noticed sometimes I have to use the power button to wake the phone up if it doesn't automatically do so when I remove it from my ear...
[Vibrant Android Development] treyvaporizer:
Do you have any tips about stopping the force closes? Sorry if this has been covered, I searched the thread before posting