yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] gorealmighty:
New to cyanogen

Okay, so far I like it. the interface is smooth. I have a big question though, am I able to use ANY kernel with CM7, specifically the Bali Kernel (big fan) Im a stickler for battery life.

Any guidance on using cyanogen and its advantages would be greatly appreciated, I like everything so far :)
[Vibrant Android Development] RoxAbout:
Yes as long as the dev said its cm7 compatible.

Enjoy

:)
[Vibrant Android Development] Rayn1328:
bali cm kernal........plus several others...glitch is another
[Vibrant Android Development] gorealmighty:
Thanks! I'm trying to download apps...I keep getting an insufficient space message. Checked the storage info and I still have a couple gigs available ...any thoughts on this?

REVISION : Google plus wont download. Just downloaded where's my Droid. Google app problem? And if it is how do I overcome it?
[Vibrant Android Development] Ventus_zx:
What's the best kernal to use for this that helps save battery life?
[Vibrant Android Development] RoxAbout:
Reboot into recovery

1] clear cache

2] clear dalvik

3] fix permissions

reboot

LET IT SIT DO NOT TOUCH FOR AT LEAST 10 MINUTES!

---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------

im getting great life useing eugenes streamlined eb7 kernal !

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

Enjoy

:)
[Vibrant Android Development] gorealmighty:
Thanks for the help so far guys, this ROM is awesome. I have another noob question though.

When I recieve a txt or email notification, my "home, settings, back, search" buttons light p at the bottom of the phone. not only do they light up but they stay lit until I check the message (i.e. the phone s idle, i recieve a txt the bottom lights up)

Im not sure if its CM7 or ADW however, is there a way to turn it off because I cant find it, and ive definately looked. I appreciate your help!
[Vibrant Android Development] Ventus_zx:
There was 666 posts lol
[Vibrant Android Development] twotone8:
Has anyone else reported any problems with Google Navigation?

Installed cyanogenmod on my new vibrant yesterday and I swear it was working then. Now whenever I attempt to activate navigator it hangs on the blue arrow load screen as soon as I input an address. When I press the home button, it does indeed go back to the home screen, but the handset starts vibrating and won't stop until I reboot. If i try to turn the screen off during this vibration, it won't turn back on.

I've tried Bali Kernel, Streamline Kernel, and both the KB5 and KA7 modems in various configurations. I've also done a fresh install of cyanogenmod two times with the same results. Would flashing back to stock first help anything? After formatting the system, cache, and data partitions, not to mention all the factory resets, I can't imagine what else could be gumming up the works.

Also, still haven't managed to get a GPS lock, but I'm confident I'll be able to figure that out, assuming I can get past this navigation hurdle.

EDIT: Figured out the google maps navigator issue. turns out you need to at least start up the stock 'maps' application first before launching 'navigation' for each boot. that keeps things from crashing all around. was able to get a satellite lock ONCE using KA7 and streamline kernel, but it went away pretty quickly and i haven't been able to get it back. I'll keep trying. GPS works fine in stock eclair.
[Vibrant Android Development] gorealmighty:
Im not sure if by new you mean brand new, but if it helps to know, the gps in the vibrant sucks. Out of the box it sucks. You can get luck of the draw units that function properly. Im activelh on the hunt fkr a gps fix.
[Vibrant Android Development] Blars1206:
It is meant to do that. You can go into Cyanogenmod settings, interface, led notification settings and set the apps to "force off"and that will keep the lights off. You can also change to a kernel that doesn't support "bln".
[Vibrant Android Development] RoxAbout:
1st part yes but you have to go thru the list 1 by 1 and then hit save...tedious

2nd part flash eugenes nobln latest streamlined..works awesome!

3rd hope ur enjoying CM7 this is the bomb! omfg I am in love with the vibrant all over again...

other than the fact i have one of the gps retarded ones..CM7 rox!
[Vibrant Android Development] beren28:
Just set "quiet hours" to be all day and set led to"dim" during quiet hours.
[Vibrant Android Development] Jesushasadroid:
for those getting market force close or force close when installing off the market..

http://forum.cyanogenmod.com/topic/31927-new-market-force-close-on-cm71-rc1/
[Vibrant Android Development] Emama:
Suddenly enter into boot loop.

I used it normally this morning without installing anything.

I can enter recovery mode,

tried to clear cache partition, dalvin cache and fix permission but still in boot loop

Anyway to fix it?

Had many important these few days but didnt back it up yet!

Thank!
[Vibrant Android Development] Jesushasadroid:
what recovery are you using...?
[Vibrant Android Development] Emama:
I press Volume UP/Down + Power to boot into recovery mode

it says CWM-based Recovery v.5.0.2.7
[Vibrant Android Development] Jesushasadroid:
try a fresh zip..

then format system, data and cache

then wipe factory reset...

wipe cache

wipe davliche

flash cm7 , then flash gapps

then fix permissions and reboot...let it sit for 10 minutes...then sign on...let it sit some more...then have fun..
[Vibrant Android Development] Emama:
I know how to wipe and flash

but I want to see anyway to backup the app and msg
[Vibrant Android Development] Jesushasadroid:
You have to boot into rom to back up msg and apps sorry
[Vibrant Android Development] Emama:
OK..reflashed an 1month old Nandroid backup

one more question, which kernel is good for battery, or stay with this default can get best result?

I used Eugene one last month as he said it fixed the GPS (although it still not working)
[Vibrant Android Development] dinjo_jo:
I cant get into CWM Recovery Mode
[Vibrant Android Development] :
I had an unexpected bootloop too last month. Only thing I did was replace my battery. Wiped batt stats didnt help. Had to do a reset from recovery and restored my apps. Hasn't done it since. One of those things that rank up there on my weird sh*t-o-meter.
[Vibrant Android Development] wavestar92:
Streamline brought me froyo like battery. No luck with GPS though
[Vibrant Android Development] Rudyfastcat:
Have you tried using rom manager ?

I use Rom Manger Pro myself as it makes flashing CWM and entering CWM a

very easy process

Install ROM Manager Premium.

To flash ClockworkMod Recovery. Pick Vibrant (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).

Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
[Vibrant Android Development] Emama:
This time after restore to 7.1 stable default kernel.

I flash the 1.5.1 signed fix...and GPS works now!! 4-5 birds is locked!!

Didn't do anything else except flashing this!!!

And since I feel default kernel is not bad at all in battery consumption

I think my phone is perfect now:D
[Vibrant Android Development] tinyaznboi:
Thank you cyanogen team. Lovin this rom!
[Vibrant Android Development] orgwizard:
so did this hold...

I've had some instances when it worked...and then after a while stopped again...

and curious, what radio you useing...ka7 or kb5?
[Vibrant Android Development] androidmonkey:
I tried CM7 months ago and liked it but I couldnt use it because of the appdata issue. Did they fix this yet?
[Vibrant Android Development] Praetorian011:
Looking for default CM7.1 Kernel

Where did you get the 7.1 stable default kernel?

I've been looking for a flashable zip for some time now, I feel the default has better batt life than Bali & Streamline and would like to avoid reflashing the whole CM7.1 rom.
[Vibrant Android Development] DavidChill:
Worth it to install CM7 for new vibrant owner?

I know I'm kind of late to this, but is it even worth it to try to install CM7 since it's not support anymore?

Or is it still being built but not recommended to use it because of the 911 thing. I don't care about the 911 thing and want to use CM.

My Nexus One broke on NYE so I'm having to use this now as a replacement... =\
[Vibrant Android Development] bearsfan85:
download the kang version thats somewhere on here, it has 911 fixed, and is repo synced and gerrit pulled, or try the cm9 kang
[Vibrant Android Development] RoxAbout:
Info please

We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this. We apologize for the inconvenience and strongly suggest that Vibrant users use a Samsung ROM due to the 911 issues with any ROMs based on open source code.

-SGS Team/Team Hacksung/Teamdouche

Since someone has figured out how to get the E911 and 911 calling working on ICS [a link to who would be nice if anyone knows].....

Does this mean that the vibrant is now loved again and will get CM9?

obviously this thread being open again is a step in the right direction [i hope...]

I sure hope they are working on it or at least secretly on the side helping the other teams that are still working on vibrant dev roms.
[Vibrant Android Development] Dougfresh:
#229 nightly

http://download.cyanogenmod.com/?type=nightly&device=vibrantmtd
[Vibrant Android Development] tripleintegral:
Nightly 229

Does anyone know what the new nightly release means in terms of CM7 development for the Vibrant? I knew atinm said(in the original CM7 thread that was eventually closed) that they'd consider starting Vibrant development again if they found a dev to maintain the code since 911 was fixed...

Edit: Nevermind. Looks like FaultException will be maintaining the code and yes, the development is back on.

Related Android Police Article: http://bit.ly/wkG9xs
[Vibrant Android Development] bigtom624:
Read this.

http://xdaforums.com/showthread.php?p=22407932
[Vibrant Android Development] nuwanmw1988:
It's great that vibrant is supported again.Hope to see a cm9 build soon.
[Vibrant Android Development] droidfan77:
Has anyone tried the latest version yet? Is this the best thread to discuss it or is there a different thread I should look at?
[Vibrant Android Development] bush2088:
i'm running the new nightly and it is awesome, everytthing is running great....having a little gps trouble though...taking forever to get locks.
[Vibrant Android Development] jvpde:
Same. Stock kernel?
[Vibrant Android Development] bigtom624:
Try Eugene's Streamline Kernel. I always get a lock and it stays locked for me.
[Vibrant Android Development] Big Dog KMc:
you have a working link?

Eugene's seem to bee broken.
[Vibrant Android Development] Dougfresh:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs

:D

EDIT: Sorry links are down also

---------- Post added at 08:06 PM ---------- Previous post was at 07:13 PM ----------

Luckily I had it in my root explorer!

Streamline cm7 kernel

http://db.tt/W0CIfM6E
[Vibrant Android Development] bush2088:
Yep, all stock.

Sent from my Cyanogized Vibrant
[Vibrant Android Development] hurtz777:
Bush flash yagf2 GPS fix. I am getting fast locks and 5m accuracy indoors with Glitch v13.1 kernel and yagf2 on the new nightly #229. Thank you so much FaultException for being our Vibrant maintainer. I finally get to feed my CM7 nightly flash habit! This nightly runs circles around ICS as far as speed and smoothness is concerned.
[Vibrant Android Development] c-pimp:
Is the mute / un mute bug fixed? In the kangs I still had to do it because audio sounded awful to other people... I'll be trying this out tomorrow but I thought I'd ask if anyone has had the problem
[Vibrant Android Development] RoxAbout:
FFC problem

Well all went well with the upgrade to #229 for vibrant, Except now my FFC and main cam crashed ie wont run gives the following error "camera error cannot connect to camera"

I Tried going back to #182 nope - aperantly i had something installed that got it working... had a bali kernel but the ones on my sd card after I tried installing them just boot looped...

dug around on my hd and found a libcameraCWM this restored the camera to start working but wont run the FFC [its back to 4slices of crap]

so now im back on #229 with the libcamera file installed and at least I have the main rear cam working...

I also tried the FFC cm7.1.0.1 file this caused boot loop also.

anybody have a fix or ideas?

I know quite a few vibrants have the ffc mod [mines a v2 or was sold as a v2 l found out its the sgs4g cam..or so I was told]

I also know that the development has just resumed on the vibrant and I will be patient, but something to look at...sometime...please

thanks in advance

ok just tried this and ffc is working..[still sideways but hey it is at least working..

found the file with bali rom @ http://xdaforums.com/showthread.php?t=1305975

at least its back to normal and on #229! awesomeness!

now maybe to tweak it to be right side up and loose the bali kernel [no offense to bali crew] :)

:)

---------- Post added at 12:49 AM ---------- Previous post was at 12:45 AM ----------

I havent had that issue on #182...

hope that helps
[Vibrant Android Development] trailblazerz11:
Try pulling the camera file from i9000
[Vibrant Android Development] c-pimp:
Ok, the problem I'm having isn't the same as the mute un mute bug, when people try to call me they can hear me just fine but I cannot hear anything at all, mute or anything doesn't fix it...I just tell them to call back or I'll call them... Only randomly happens on incoming calls.... It has happened to me on pretty much all cm7... Oddly on previous kangs where they have tried mute unite fixes this has gone away and I randomly have bad output audio until I mute unmute... I turn off things like haptic feedback and vibrate on answer... I've read others with same problem but never found a solution.... It's been the only problem I've had on cm7 for a while... If I could only fix this problem if be golden... Any suggestions would be greatly appreciated
[Vibrant Android Development] hurtz777:
I an having the mute/unmute issue with nightly #230. It seems like I have had it every since they implemented the 911 fix because it wasn't present in #182.
[Vibrant Android Development] Dougfresh:
Don't start scaring off our new cm team with the same issues that made them abandon us.

I'm not pointing fingers
[Vibrant Android Development] nuwanmw1988:
Totally agreed.
[Vibrant Android Development] charkey:
It's always a beauty going back to this ROM.
[Vibrant Android Development] RoxAbout:
Nightly #231

works great so far

camera is also working! woot!

Thank you !
[Vibrant Android Development] eservant:
Post 313, final kernels dated 11/13

http://xdaforums.com/showthread.php?p=22523015#post22523015#313
[Vibrant Android Development] flapane:
I think that it would be nice to include yagf2 GPS software patch in the next nightlies.
[Vibrant Android Development] SLEEPYMAN01:
Is MMS supposed to automatically work?
[Vibrant Android Development] muleyman:
Do you have a FFC or are you speaking about the main camera, in general?

---------- Post added at 10:11 AM ---------- Previous post was at 10:06 AM ----------

I've had no issues with MMS. Just received a picture, actually and it came in just fine.
[Vibrant Android Development] RoxAbout:
I have a ffc mod v2 and unless I load glitch kernel I'm unable to use the rear camera on nightly #229 æ .However with #231 rear camera is again working, now the front isn't.... No big deal at the moment I can wait for front support. The new developer is very receptive for help. Thank you again for bringing the vibrant back to life!

I used adb and after pushing the libcamera.so from the i9000 like it says... I got the front camera working...again..but it is sideways...is there something I need to edit to rotate it 90 degrees?
[Vibrant Android Development] ruhrohs:
I'm on nightly 236 with Eugene's latest BLN kernel. The stock kernel was always draining my battery. I also flashed the KB2 radio. Been 12 hours on this new ROM and like Mickey D's, I'm LOVING it!

Thank you to the devs who brought back CM7 for the Vibe! :D
[Vibrant Android Development] eservant:
wifi and 3g internet calling.

When using cm7 native dialer (doesn't happen with sipdroid), whoever I am talking to hears an echo of their voice(I can't hear it). If I turn down the volume to half it disappears, but I can barely hear the person I am talking to. Don't know if it is a bug, was just wondering if any one else was having the same issue.
[Vibrant Android Development] flapane:
Is the project dead?
[Vibrant Android Development] yosup:
I think everything's moving into CM9 now. The last CM7 nightly was from 2/26/12 I believe. Haven't seen any Nightlies posted for CM9 yet - though I could be mistaken.
[Vibrant Android Development] creeve4:
There is still this
[Vibrant Android Development] buggzero:
CM for Vibrant was stopped due to E911 issues, which are driver related, and until samsung provides updates (which chances are likely hell will freeze over first) the project was halted, and no plans for cm9 support were made. That was the last I heard.
[Vibrant Android Development] yosup:
Hmm ... I believe they figured out the E911 issue and that's why they started up the nightlies again starting with #229.

From my understanding, FaultException is now maintaining the CM dev for the Vibrant. See his comments below ...

Also ... a tease that CM9 is coming ...
[Vibrant Android Development] flapane:
AFAIK new nightlies have been released in February just because E911 bug has been already fixed (I cannot say more, no 911 here in Italy).

Maybe they decided to concentrate on CM9 alpha builds only.
[Vibrant Android Development] FaultException:
:eek: There's still people that think the project is dead!?

Catch up:

* CM dropped support because of E911

* E911 cause found by Genesis3 & renard

* CM support reinstated as of mid February.

* Nightlies are weird right now, they'll probably be back up eventually, but I'm not really any part of that.

* There are some new nightlies here, you should use those rather than Stable till 7.2 is put out. (Use the second to newest nightly, the newest nightly is bugged and will make your status bar FC)

* CM9 alpha has been available since February 17th.
[Vibrant Android Development] akfelipe:
Shouldn't be a surprise that people think CM died on us.... maybe creating a new thread by say, the maintainer :)

especially when people started flocking to ICS roms, a new fresh CM 7 thread would be nice(a

atinm

like thread ). you know for us that want to stick with a stabler cm gingerbread goodie, until cm9 "matures".
[Vibrant Android Development] rogerchew:
so how is the stability now? battery life almost on par with froyo roms? went to ics, getting a lot of wakelock issues with gps still. if anyone is still running cm7, would love to hear your experiences.
[Vibrant Android Development] theking_13:
The stability has always been great, as you would expect from CM7. The battery isn't to great, I found myself staying on Froyo (Bionix NextGen v2 to be specific) until the early stages of ICS. I would recommend ICS Passion, its super stable, and a great daily driver. The ICS development is the biggest thing that I miss about my Vibrant.
[Vibrant Android Development] flapane:
The stability is great, I've never had a random reboot with all the stuff in my signature.

You'd better download the latest stable version (7.1.0.1).
[Vibrant Android Development] FaultException:
Do not use stable unless you don't want to be able to call for help in an emergency.
[Vibrant Android Development] flapane:
Oh I forgot, you're right, avoid it if you want to call 911.
[Vibrant Android Development] FaultException:
Also, a nice note, the nightlies are from 7.2, which have nice rotation animations like ICS. :D
[Vibrant Android Development] shrty4luv:
when will the changelog be back up?
[Vibrant Android Development] hurtz777:
GPS Testing Indoors On A Cloudy Day Without Wifi Enabled On CM7 Nightly Build 236

STOCK Build 236

13 Satellites visible, but no lock

STOCK Build 236 + borked-yagf2

14 Satellite visible, top 2 satellites up to 22db turn on and off, but no lock

STOCK Build 236 + yagf2

13 Satellites visible, locked in 10 secs and locked up to 9 satellites down to 7m accuracy. GPS would lock 9 satellites after about 2 minutes coming out of deep sleep but would average only 30-40m accuracy.

STOCK Build 236 + CM7_VIBRANT_20111204_NEO_XX.1_VC-led-notif kernel + yagf2

14 Satellites Visible, locked in 10 secs and locked up to 9 satellites down to 6m accuracy. GPS would lock up to 9 satellites after only 30 seconds coming out of deep sleep and it even got the same 6m accuracy as before deep sleep!

I also tried Glitch v13.1 and CM7_VIBRANT_20111203_NEO_18_VC-led-notif_didle kernel with Build 236 and they both locked between 6-7m accuracy but they couldn't initialize GPS after deep sleep. The conclusion to my GPS testing is if GPS lock accuracy is important to you and you need it to work quickly and accurately after deep sleep use Build 236 + CM7_VIBRANT_20111204_NEO_XX.1_VC-led-notif + yagf2. If you don't mind a a slower first lock and less accuracy after deep sleep you can use the stock kernel on Build 236 + yagf2. Could someone else please test out STOCK Build 236 + CM7_VIBRANT_20111204_NEO_XX.1_VC-led-notif + yagf2 and see if you get the same results I do. Thank you FaultException for being the Vibrant CM7/9 man!
[Vibrant Android Development] FaultException:
Corrected link in my sig:

http://cm-7-nightlies.appspot.com/?device=vibrantmtd

Apparently the changelog site is now for CM9 nightlies, there's the CM7 version.
[Vibrant Android Development] akfelipe:
new thread? why are we using the 7.1 RC thread to talk about cm 7 nightlies/7.2 stuff...
[Vibrant Android Development] FaultException:
http://xdaforums.com/showthread.php?p=23555391#post23555391
[Vibrant Android Development] freshjr:
I would like to run some gingerbread until the encryption unsuccessful bug is fixed in all the ICS builds.

I have a problem, with this CM7 rom.

I cannot log into my google account.

I go to settings, accounts, add an account, type in my google account and password.

Then I get a cannot connect to the server. I tried both WIFI and 3G. My phone is connected and I can use the browser.

So without this I cannot get my contacts or use the app store.
[Vibrant Android Development] c-pimp:
I'd try a different version of gapps from November I believe
[Vibrant Android Development] fishman0919:
haven't seen it posted anywhere so.... CM 7.2.0 is out for the Vibrant
[Vibrant Android Development] iTz KeeFy:
Is there a change log anywhere?
[Vibrant Android Development] FaultException:
https://github.com/CyanogenMod/andr....mkdn#changelog-notable-new-features-or-fixes

Note the "Samsung Galaxy S GSM devices: Fix emergency dialing" is only the fix before that fixed the emergency dialing death from the libaudio. There may still be issues.
[Vibrant Android Development] iTz KeeFy:
Thanks for the link
[Vibrant Android Development] Rafase282:
Is there a way to install the stock camera from eclair or a better one?

This is my mother's phone, after getting it back from a brick I decided to test either CM7.2 or CM9 for the phone. She had stock eclair on it and I know she might miss the panoramic picture features.
[Vibrant Android Development] nuwanmw1988:
This cannot be done
[Vibrant Android Development] JimDog:
CM9 camera has a Panoramic mode.
[Vibrant Android Development] SamsungVibrant:
I just realized you were talking about me. Why comment if you have nothing useful to say. Have you ever tried the search feature on xda? Nearly impossible at times and Ya, I would still not have my answer.

Why even comment if it's not something useful. People like you make the experience worse not better, everyone is here to help eachother so if you don't feel like helping just keep to yourself.