yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] YodaEXE:
Is there a known sleep of death issue still? I just flashed 7.1 and, perhaps I've done something wrong but, the screen will turn off and every once in a while I'll manage to get it to wake back up, but for the most part the minute the screen kicks off I have to forcefully reboot it to be able to do anything. It's been that way with most of the builds I've tried. I flashed a GB bootloader, so I don't think that that is the issue, but then again, who knows?
[Vibrant Android Development] rudy847:
Now that cyanogen officially supports the vibrant what does that mean for my phone? What's the major difference between what we had before and what we have now?
[Vibrant Android Development] KWKSLVR:
I finally had to wipe and start fresh this morning after running into several FC problems AGAIN. They're almost always related specifically to Google Framework/GAPPs/Facebook App. This last time I had avoided restoring APPS + DATA thinking it was making a difference, apparently not.

I get the impression that there are a lot of people that are running CM7 that never have these issues and flash new nightlies regularly, so I figure it HAS to be something I'm doing in the way I set my phone up. For fun, let's compare notes, and I'm trying to think of the things that may be relevant.

Things I change:

1) I've been running a CM7 Theme called "RC Blue" for a LONG time. Maybe it causes issues?

2) I use the built in ADW Launcher, but I stretch each home screen to 5 icons wide and my dock is stretched to 5 icons over three. I also have tried restoring ADW settings/layouts, it never seems to restore and never makes a difference if I try to restore it or not.

3) I run 2 Gmail Accounts

4) I use the Facebook/Tweetdeck/Google+ Apps a LOT. I use Gmail a LOT. I also link Facebook under Accounts/Sync

5) Stock kernel or Neo (I've tried to many to list) - neither option seems to matter.

6) I use Swiftkey

I've started from fresh Odins a couple of times. I suppose the one continuing "theme" with that is that each time is that I restore to stock 2.1, Root, Install Bionix 1.3.1, Install CM7, Install GAPPs so unless there's some inherent issue with going from Bionix to CM7, I don't see it being a problem. I give that CM7/GAPPS install a LOT of time to settle in, 10+ minutes. I don't always give the Bionix install longer than about 4 or 5 minutes.

Typically, things run GREAT for about a week, then start to get a little slower, and a little slower. My system will go from opening an app immediately, to taking 2 seconds, then 3, 4, 5 seconds to 5+ seconds and, "This app is not responding, close/wait" and finally after about 2 weeks, it's FC city.

Initially, booting into recovery and doing some combination of the kernel cleaning script, fixing permissions, manually deleting dalvik/cache partition, reflashing gapps and massaging my Vibrant just right ;) will buy me a couple of days, but eventually, there's nothing I can do to "fix" it without a full wipe. It's not that a full wipe is THAT big of a deal, it's just that the way I set my home screens/widgets/ring and notification tones takes SO long to set back up, and when I can restore my home screens it takes FOREVER to get it back the way I like it.

Maybe everyone experiences these problems and I'm just not understanding that it should be expected, but I just want to be sure I'm on the same page as everyone else. I've also stayed on the same nightly from initial flash to FC and it doesn't seem to matter.
[Vibrant Android Development] strictlyrude27:
Now you can file bug reports against the stable ROM.

For instance, the 911 calling issue can now be formally addressed by the CM7 system. I might do this sometime this week.
[Vibrant Android Development] Nabeel10:
Oh yess!! Please 911 needs to be fixed, that's the only reason I'm not on CM7

Sent from my Vibrant
[Vibrant Android Development] rogerchew:
would be interesting to see how they fix it considering not a single dev has a vibrant and people have said it might be a tmobile isolated issue.
[Vibrant Android Development] nerve101:
Hey guys,

I have a issue with my vibrant today.

I was on my phone during class and my phone completely crashed after letting it sit for a bit to see if it would catch up to closing the programs i gave up and removed the battery to restart the phone.

The phone went into a boot loop so i re installed 138# and it continued to a boot loop. and now re installed 128 and same problem came up. Then i figured i would try to install 145 still same issue. I wipe cache and devilk. I am trying to find a way to do this without using odin?

im still in my classes and have a full day.

I just want to know if i am out of luck or is there a way i can do this quickly? thank you
[Vibrant Android Development] Oxirane:
Try wiping data?
[Vibrant Android Development] atinm:
And how does one test 911 calls anyway - by calling 911 . . . I don't think this is going to get addressed unless someone can figure out what is going on just based on looking at the code.
[Vibrant Android Development] nerve101:
im trying to not do that but i think thats my only choice so im doing some hard back up then wipe everything. then try to install the rom again.

*edit* i fixed the issue, i dont know what casued the boot loop but i wiped all data restored factory and it worked. and i just installed 145# and it went threw fine.

but anyone know why the looped continued and had to be factory restored?
[Vibrant Android Development] realcyberbob:
Does the newest version 7.1, have everything working other than calling 911? Trying to decide if I should switch from Toxic, which has no problems whatsoever.
[Vibrant Android Development] Phateless:
I'll bite. Why do you go from stock to bionix before flashing cm7??

I have just as much on my phone. 2 google accounts, etc. Here's what I do.

Odin to stock 2.1. Don't bother rooting.

Use update.zip to get into recovery.

Wipe data/factory reset.

Format /system.

Flash cm7. It automatically reboots.

Flash gapps, wipe data again.

Boot and wait, good job on the 10 mins.

Cancel the market search app, Google will download all your apps automatically anyway.

Do all of this manually through recovery, don't use rom manager.
[Vibrant Android Development] SamsungVibrant:
So you can go straight from stock JFD 2.1 to CM 7 or MiUi?

For some reason I thought you had to be on 2.2 first.
[Vibrant Android Development] mifac:
Compass is not working after i updated to CM 7.1. Any solution for that?
[Vibrant Android Development] s0niqu3:
You can flash my fix here: http://xdaforums.com/showpost.php?p=18151999&postcount=8334

I honestly have no idea how on earth their build-bot doesn't error on the make for the vibrant without including these files.

It leads me to believe that the source on github is not the source that they actually build from, because building the github source will error every single time if these two files can't be found. And the resulting 'kang' zip created when I build the github source, does include these files, and yet the official releases don't anymore.

Hope this works for you, its working fine for me still on 7.1

Cheers, :)
[Vibrant Android Development] atinm:
Are you sure this works? These are meant for the other phones that have a different GPS chip . . . but if it works, we'll happily put it back!
[Vibrant Android Development] ford4u:
Just installed the stable build and I am having a few issues. I am unable to get into clockwork and when I flashed the gapps from rom manager it did not install them. If I try to reboot into recovery it shows the status bar as if it was installing something and then reboots. Any help?
[Vibrant Android Development] s0niqu3:
Hi,

I'm probably the wrong person to really comment, since I'm not a programmer and well my compass was always terrible, even with samsung/touchwiz roms. But these seem to work at about the same mediocre level for me; e.g. still requires calibrating multiple times a day, but they do actually work after calibrating for a while.

Cheers, :)
[Vibrant Android Development] KWKSLVR:
Ah, see, I was under the impression we had to be on 2.2 as well. I'll try your method the next time around. Thanks for the tips!
[Vibrant Android Development] SamsungVibrant:
I did too, I thought to install CM or MiUi you had to be on 2.2 first. Hmmmm
[Vibrant Android Development] atinm:
It's ok - our init files actually seem to call them, so I'll take your word for it. There will be a 7.1.0.1 release happening for Vibrant soon.
[Vibrant Android Development] Oxirane:
If you came from a different rom then wiping data is a must- If not then I guess some changes that have been made since your last nightly weren't backwards compatible. What were you on previously?
[Vibrant Android Development] Jasonhunterx:
Look like im gonna have to go fire up my half broken vibrant an try out that new Cm7 looks awsome
[Vibrant Android Development] jzero88:
Yes you can. What I really wish was out there is a JFD Odin flashable that is already rooted, and has ROM manager installed. Makes it much easier to flash JFD, download ROM, flash recovery, install!
[Vibrant Android Development] Phateless:
Yep! That's what I've always done.

Nope! :)
[Vibrant Android Development] Phateless:
Root is 100% irrelevant from 2.1.

Use update.zip method to get into clockworkmod recovery. Reinstall packages and you're on your way.
[Vibrant Android Development] Emama:
Is there any gps fix for the stable version?

cox it does not lock at all
[Vibrant Android Development] nedlog:
No, I've tried all the "fixes" and they never work for me; also 911 doesn't work either..just FYI
[Vibrant Android Development] boothten:
http://xdaforums.com/showthread.php?t=1199613

That one works for me, just flash the Vibrant_CM7_GPSFix_V1.5.1-CWM-signed version through CWM and it locks within seconds.

;)
[Vibrant Android Development] enzomtrx:
If you backup, wide data, system, and cache then install CM7 then latest gapps, reboot, let it sit, theb go back ito recovery and restore data only, this never fails for me. I do it every nightly I choose to flash.
[Vibrant Android Development] nedlog:
Not to take away from those who worked on this fix, but if its so great why isn't it been included into the regular code? Just saying:)
[Vibrant Android Development] duboi97:
Whats the best nightly as of right now? I'm running the stable Cyanogenmod 7.1, but the battery life is horrible compared to what I ran a few months back.
[Vibrant Android Development] gunks:
Dude... You cant judge the stable version for battery life yet. It hasn't even been out a full day...
[Vibrant Android Development] nerve101:
i was on 138#
[Vibrant Android Development] Oxirane:
Well... I dunno. But something went funky somewhere in there, maybe it was an app or something you tweaked, but when you have a bootloop, wiping data is a good thing to try.
[Vibrant Android Development] strictlyrude27:
Because I haven't had the time to merge it. It took forever to get V1.3 in there in the first place. And I/others mess with config settings so often that it doesn't make sense to merge it. It's not a "stable fix", it's been on-the-fly as far as I can remember.
[Vibrant Android Development] duboi97:
But I just finished calibrating it. It hardly lasted 7 hours
[Vibrant Android Development] thekurst:
Headset mic not working

Was this ever fixed in a later build? I moved back to a 2.2 ROM and my headset mic and button works just fine. I want to try CM7.1 but not being able to talk on my headset is a problem for me...
[Vibrant Android Development] junglerumble:
wanna try cm7 again. which build is the most stable snappy and long lasting?
[Vibrant Android Development] cwalker29:
It's sad how we are force to buy a new phone before our contact is up. I mean there are no new Roms being built for the vibrant Because of the lack of source codes. And the only one that are still making updates (cm7) is the BEST but yet worst thing that i could put on my phone right now. The best and latest firmware but it's infected with too many bugs for my liking.

This phone could easy make it another 6 or 7 months with new source codes. But the lack of support is killing this phone to me. The g1 had custom roms months after having my vibrant. Wait wait, I'm tripping. This is not the right time or place for me to be wilding out. Forgive me
[Vibrant Android Development] mifac:
Thanks Sonique...Your fix solved the problem :)
[Vibrant Android Development] KWKSLVR:
Weird, because I'm at 65% after 11 hours 50 minutes.

I get around this problem by not participating in contracts in the first place. ;)

Look, realistically, there's nothing wrong with the phone. Just because it doesn't run the latest version of Android doesn't mean that it's outdated. It's far from outdated. Shoot, most Android devices are running Gingerbread. There's absolutely nothing wrong with a SGS or any other 1GHz Android device with a fair amount of RAM. We all like to tinker, or we wouldn't be on XDA, but perspective people (and I'm the worst about not keeping perspective :D)
[Vibrant Android Development] nedlog:
That's what I figured. I tried the fix early on (couple months ago) and that's why I said it didn't work, cuz I could never get it to. Maybe I'll try again. Thanks.
[Vibrant Android Development] EricDET:
I'm on 142 with Glitch.... Battery life is the best I've ever had on CM7. It's usually around 35-40% after 18 hours when I plug it in at night.
[Vibrant Android Development] zmattmanz:
Couldn't agree more! I'm the exact same way. In a completely unrelated tangent, is there any solution for the Insufficient Space problem when trying to download some apps from the Market? Clearing Cache doesn't do anything and it seems like the discussion on another thread to fix this has died.
[Vibrant Android Development] cwalker29:
yeah i see where you are coming from. but i really want the gs2 from t mobile but my bank account is screaming don't do it.. O'well
[Vibrant Android Development] AustinKnight45:
Figured it out EDIT
[Vibrant Android Development] t1h5ta3:
flashed 7.1.0.1 this am, still not seeing any birds.
[Vibrant Android Development] tonie972:
Has anyone tried flashing this fro Miui without flashing back to stock? Does it work?
[Vibrant Android Development] db3:
it works. 10char
[Vibrant Android Development] tonie972:
Thank you....
[Vibrant Android Development] zinite:
I'm getting terrible battery life as well. About 6 hours - GPS/Wifi off, brightness on the minimum. I even tried to charge it up and run Juice Defender, but it still depleted very quickly.

Battery usage:

Android System 45%

Display 18%

Cell standby 14%

Phone idle 6%

Voice calls 5%

Wi-fi 3%

Android OS 3%

Google Services 2%

Seesmic 2%

Facebook 2%
[Vibrant Android Development] junglerumble:
I'm on build 147.

Super fast and snappy.

battery is ****ing absolute horse **** though. it's just sitting on my table unplugged at 100% and I check an hour later and it's 90%. 10% of battery drain PER HOUR idle time????!!! my mind is ****ing blown
[Vibrant Android Development] t1h5ta3:
what are you seeing for voltage at 100% , have you run a full calibration cycle? 10%/hr? sounds like a bad flash/ rouge app or some thing. hows your signal strength?

i know you dont want to hear it, but some things messed up on your end.

your realy not contributing any thing to the thread, and honestly , you come off sounding like a whiny little *****.

try useing system monitor to track what apps are doing, do a fresh install with a full wipe etc, dont restore from titanium etc...

if your looking for help, try giving some info other than spouting a ton of profanity all it does is make you look ignorant.
[Vibrant Android Development] ipugh:
Okay -- a couple of odd problems. Not sure if it's CM7 related, or if I have a messed up phone, but I'm running CM7 #71 and have the following problems:

1) Phone will not ring -- vibrates only. Under Settings -> Sound Settings, I have Vibrate set to never and under Volume everything is set to max. I do hear message notifications, however.

2) Phone vibrates like crazy, at random times, when I'm on the phone. Doesn't seem to be any rhyme or reason to it, but it just seems to happen. I originally thought it may have something to do with the proximity sensor, but I can't correlate the times it happens to when it is or is not close to my face or if it is or is not moving.

3) When trying to update to a more recent nightly build, Rom Manager will download the more recent ROM, but won't boot to CWM/Recovery. If I manually boot to CWM/Recovery, I can select the ROM to flash, but nothing happens. It goes through a few steps, then reboots back into the version of CM7 that I am currently running.

Does anyone have any suggestions?

I suspect I'm overlooking something obvious here, as everything else with CM has been great.

Thanks for your advice --

Ian
[Vibrant Android Development] bigtom624:
I suggest you Odin back to JDF and start over. I had a similar problem and that was the only thing that helped me. It took me a few tries before I figured out that it was restoring my apps and data from Titanium Backup that was messing me up. If you do it that way just restore the apps but not data and see if it helps.
[Vibrant Android Development] igor.ibit:
after flashing #146 my market FC all the time. I uninstalled the update and it doesnt FC but it pops up errors and wont let me download anything.

What else can i do?
[Vibrant Android Development] nedlog:
Had similar issues and had to do a clean flash from ROM Manager, checked Google Apps with data wipe.

Not sure in the gapps is fully compatable with version 2.3.7. If its installed separately it says its for 2.3.5...not that it matters
[Vibrant Android Development] Phateless:
It's compatible. Do a manual install through recovery and format /system before you flash. After the auto reboot, go back into recovery to manually install gapps, then wipe data/factory reset again.

Give it 10 mins to settle on first boot and cancel the market search app.

You should be good to go.
[Vibrant Android Development] layzer253:
I've been using custom roms and CM7 since shortly after the vibrant came out. I've found that so far Nightly 85 his the best all around. It has working wifi, and great battery life. I use bali 2.2.1 for my BLN and voodoo color as well as OMFG 1.4 for GPS. Any nightly past 85 seems to get progressively buggier. My phone was purchased the day it debuted and I did do the GPS antennae fix as well since it was known issue for the first few batches of phones.
[Vibrant Android Development] wyvernwaddell:
anyone finding that wifi doesn't work in the latest nightly? tried toggling from the bar and from settings.everything else works great
[Vibrant Android Development] krntehknik303:
For those with the battery issues I have the same with miui as well. Someone told me to come from a fresh Odin flash. Use the phone normally with battery cycles to let it settle in. That's what I am doing and gonna test and see if it works out. I have system panel and its the android system using all the battery not the apps or anything else.
[Vibrant Android Development] nettoxx7:
Can i flash miui from cm7?thx
[Vibrant Android Development] syl0n:
Installed 7.1.0.1. I also installed the GPS Fix version 1.5.1. The gpsd in CM7 is very unreliable for me, so the older one in GPS Fix 1.5.1 at least works reliably.

Working great so far. Getting decent battery life too. This is at 64% after a days use, but this included overnight idle no use for about 8 hours.
[Vibrant Android Development] jammy_22:
How do i get the gps 1.51 ..please let meknow
[Vibrant Android Development] SamsungVibrant:
Vibrant_CM7_GPSFix_V1.5.1-CWM-signed.zip

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

The zip I used is:

Vibrant_CM7_GPSFix_V1.5.1-CWM-signed.zip
[Vibrant Android Development] syl0n:
Go to this thread http://xdaforums.com/showthread.php?t=1199613

And download Vibrant_CM7_GPSFix_V1.5.1-CWM-signed.zip

Make sure you don't get the newgpsd one. That one also works but after a while GPS breaks and requires reboot. With the one above GPS keeps on working although cold locks can take 2-3 minutes it works well.

Just flash it through CWM and then use GPS Status app and go to menu > Tools > Manage A-GPS State and choose "Reset". Then reboot your phone and open GPS Status and go outside, you should lock soon. Afterwords the next locks are a lot faster.
[Vibrant Android Development] jamesgg:
I been hesitant to switch from bionix-v 1.3.1, but it seems like CM7 is pretty reliable and coming along. Can anyone tell me if there is an option in wireless settings to enable Mobile AP (for creating hotspot). That's one of the features that is really handy in Bionix-v. Thank You.
[Vibrant Android Development] syl0n:
Yes there is mobile hotspot.
[Vibrant Android Development] TR88:
Yes
[Vibrant Android Development] jamesgg:
Sorry for this noob question but, I just flashed a nightly, so if I want to upgrade to another nightly, will I need to backup data and flash using rom manager every single time? Or is a quicker path?
[Vibrant Android Development] Phateless:
No backup needed. Use recovery and do it manually.

Wipe cache, dalvik cache, flash, reboot, reboot again.

Oh, and search. This has been asked and answered on almost every page of this thread .....
[Vibrant Android Development] bucket19:
The change log indicates that the 911 problem will be fixed in the next nightly.
[Vibrant Android Development] jammy_22:
Does anyone knows how to activate music control from headphone...or is it not possible?

---------- Post added at 05:47 PM ---------- Previous post was at 05:16 PM ----------

Does anyone knows how to activate music control from headphone...or is it not possible?
[Vibrant Android Development] techbeck:
Anyone care to post their battery stats? Curious what people are getting with moderate use and how long their battery lasts.

thanks
[Vibrant Android Development] avelec:
TV/Video Out is missing?

Hi everyone, just wanted to verify that the TV/Video out function is not suppose to be in the CM7 rom? Thanks.
[Vibrant Android Development] TR88:
Indeed. I would love this feature myself.
[Vibrant Android Development] pelmenept:
Has the issue with GPS not allowing phone go into deep sleep mode, been fixed ?
[Vibrant Android Development] jammy_22:
Does anyone knows how to activate music control from headphone...or is it not possible?
[Vibrant Android Development] nedlog:
Not possible on this ROM
[Vibrant Android Development] nedlog:
That's a really good thing,I think more folks will use cm7 again
[Vibrant Android Development] atinm:
We don't know if it is truly fixed - more people need to test it (get permission to test first - though I don't know how one does that), but as of now we think it might still have issues.
[Vibrant Android Development] iynfynity:
lol that's a hard one to test.
[Vibrant Android Development] jzero88:
I find it so funny not to be checking my battery life every thirty minutes anymore. I even got rid of the percentage in the statusbar and went back to a battery icon. All my battery anxieties are gone. How?

Any build I use I use with Glitch ML undervolted and a newly purchased 1800mah battery. Greatest feeling in the world.
[Vibrant Android Development] nedlog:
Tested it and the call disconnects

right away. thanks for the effort.
[Vibrant Android Development] styllballyn:
Thanks for the semi-snark reply, but I already did attempt a search and all the results I got were similar to yours - they explained why, not how to prevent or correct it. I was more so looking for a possible resolution.

As far as the version Im using its simply a matter of personal preference, its the one that has the features I want and lacks the features I dont want (like the glowing buttons for missed notifications, I dont need the world knowing I missed a call/msg when my phone is on silent).