yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] psjames:
Is anybody having an issue with Bluetooth. Every sense 30 I have not been able to get bluetooth to turn on. I could not find anything in the thread about bluetooth.

Paul
[Vibrant Android Development] ChristoA1:
Have you tried clearing the Dalvik Cache and/or doing Fix Permissions from within recovery?
[Vibrant Android Development] Argusi:
When did it start?

Suggestions. Test after each step and continue if FC's keep happening:

Check logcat to see if it gives a good reason.

Fix permissions, reboot.

Wipe Cache and Dalvik Cache.

Wipe Cache and Dalvik Cache again and reflash the ROM.

Wipe user data.

Odin to stock and try again fresh.

Did I miss anything?
[Vibrant Android Development] apollo15rover:
I had a bit of a hiccup with it myself. Then it finally popped on and now I can turn on and off normally.. and haven't the faintest clue why..
[Vibrant Android Development] db3:
if you're using ADW (the cm7 default launcher), swiping up will reveal the hidden dockbar (with, i think, unlimited space to add shortcuts). just swipe down on it get your main dockbar back. alternatively, just go into adw settings and restart it...
[Vibrant Android Development] gamikzone:
is anyone else having problems with external sd not being read? for some reason when i look at the emmc folder or mnt/emmc nothing shows up before i odin to stock JFD and flashed cm7 build 30 and the emmc was working but it was gone the next day
[Vibrant Android Development] movieaddict:
32# is fine and no bootloops for me at least
[Vibrant Android Development] tbrar:
battery problem

I am on #32 and seeing very bad battery life. I charged it completely and the battery has depleted to 44% in 4.5 hrs. I used the phone for only about half an hr that also just casual web surfing. I have background sync on for google services, data disabled and using only 2G. Also I have been connected to wifi for most of the time. Is it just me or somebody else is also seeing this. Battery life was while using 24. But recently 29,30,31 are giving me increasingly bad battery life.

It seems the phone is not sleeping properly. I see android os as using max battery

Thanks
[Vibrant Android Development] jzero88:
I can't seem to get CMparts.apk to install. I removed for another version with BLN control but when I go to CM settings, it force closes. I use Root Explorer to restore original and still continues to fc. Any ideas on how to fix this?
[Vibrant Android Development] gamikzone:
32 seemed to fix my battery problem which kernel are u using? and trying to wipe your battery stats after u fully charge it, it takes a few days for the battery to even out
[Vibrant Android Development] treyvaporizer:
Well it started after I went back from nightly 30 to 25. And now I'm on 32 and it is still happening. But I will try your tips

Edit: the first step seemed to work! Thanks!

Sent from SGH-T959 (CM7)
[Vibrant Android Development] tbrar:
I am currently on stock kernel. Although I havent wiped the battery stats but I dont expect them to make such a huge difference. On earlier CM7 builds battery used to last almost 24 hrs with average usage but now it seems it wont even last 8 hrs with minimal usage
[Vibrant Android Development] gamikzone:
try using neo7 kernel its great with speed and battery, and maybe you can go back to build 26 thats what i might do
[Vibrant Android Development] scrizz:
I can say the same to you.

:p
[Vibrant Android Development] xriderx66:
yep same here, flashed this morning and NO bootloop can yo ubelieve it? I think my luck has changed lol
[Vibrant Android Development] movieaddict:
OMg no bootloop congrats Xrider maybe ur luck is changing!
[Vibrant Android Development] Hung0702:
Does anyone else consistently encounter bugs when flashing over older versions? I flashed from 29 -> 32, but this has happened for any span (i.e. 8 -> 12).

After flashing, it consistently takes longer to boot up, and I'm not talking about the initial boot, but the subsequent ones as well (upwards of 2.5 minutes, opposed to <1.5 min). I have to keep using odin to get back to stock and then proceed to flash the latest version and then I'll get a significantly better experience.

Is there any way to have an actual clean install without having to odin? Can I format certain partitions to achieve the same effect? If so, which one?

I also encounter more issues when using a dpi changer, such as LCD Density. For example, the initial boot will have no issues, but I'll apply 200 dpi and after it boots, the phone application will fail (no signal) and restart, then I'll get signal back. From what I understand, applying a new density will not actually reboot the phone.
[Vibrant Android Development] Cesarp 24:
What? Congratulations on crossing over to the dark side.

Sent from My CM7 Monster
[Vibrant Android Development] baderfgt:
I change mine to 200 dpi with every new nightly with no problems. try to fix permissions from rom manager or terminal

su

fix_permissions
[Vibrant Android Development] HeydavidV:
I had problems with bluetooth in my car today. I could not enable it so I rebooted and tried to enable it afterwards but no joy. I tried a couple more times with the last attempt pulling the battery and then it finally worked when I powered it back up. Hopefully that was the last time that happens! :)
[Vibrant Android Development] boothten:
You'd be surprised just how big a difference wiping your battery stats could make.

I'm averaging maybe 25 hours on a single charge depending on usage.

Granted, I'm on the Glitch Kernel and UV, but OCing too.

:o

You had good battery with Neo7?

Neo7 gobbled up my battery life, it was awful.
[Vibrant Android Development] nedlog:
I too am currently on the stock kernel and have noticed the drain on my battery; started fully charged six hours ago and am now at 30% with average use. Maybe it's me but the lower it gets the faster it goes...kinda like sands in an hourglass...
[Vibrant Android Development] boothten:
When's the last time you wiped your battery stats?
[Vibrant Android Development] Phateless:
Go into recovery, wipe data, let it sit for 5 minutes on first boot before you set up.

I'm serious, 5 minutes, don't touch it.
[Vibrant Android Development] nedlog:
Never...but I'm letting my phone die; then I'm going to recharge and wipe the stats for the first time...read about that on an earlier post....see if that helps
[Vibrant Android Development] Phateless:
Long press with root explorer to set permissions to match what's nearby.

Easiest way is to just reflash.
[Vibrant Android Development] flipper2006:
i didnt get to read thru all the new posts, but 32 doesnt have Blue tooth. Didnt work at all, unable to even turn it on.. reverted back
[Vibrant Android Development] boothten:
Wiping through recovery?

That never worked for me personally.

It never did anything, battery life was the same as it was before I did that.

The only method that ever worked for me was using root explorer, going to data/system and manually deleting the batterystats.bin file that way.
[Vibrant Android Development] nedlog:
..oh, I didn't know that...should I wait until I am fully recharged or can I delete that file anytime??
[Vibrant Android Development] xriderx66:
... wel lyou can delete it anytime but that'll make your stats horribly wrong.

Full charge till 100%

delete file

and just to be safe i reboot.
[Vibrant Android Development] nedlog:
Thanks, I'll give that a try:)
[Vibrant Android Development] tsnow247:
I'm also having battery issues.

I'll charge and delete as well.

I'll report back if it doesn't help.

Sent from cm7
[Vibrant Android Development] wergeld:
Not sure if this is a touchwhiz item or not but:

If I long press the search button under touchwhiz roms it would bring up the voice command app. I tried to set that up under CM7 and ADW but I do not know what app to make it act like the way I want. I used to be able to speak and it would, depending on the context, either open up a google search, send a text message, or dial a specific number. The Google Voice Dialer does not do this, I tried.

This may be related but I am running Swype beta 3 and the microphone button does not do anything.

Anyone know which app I should assign to search button long-press?
[Vibrant Android Development] Wizeblood:
Neo 7 works fine with decent battery on #26, after editing the flags as stated in OP

~Thanx! You know what you did!~
[Vibrant Android Development] Phateless:
Make sure you have google voice search installed from the market.
[Vibrant Android Development] wergeld:
That was it!

Thanks a bunch.
[Vibrant Android Development] numberoneoppa:
Flashed 22 as I am living on an airplane for the next two days and need a good bat life. Looking forward to reports of 33, though.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] ke.laguardia:
wanted to return to stock kernel after flashing the glitch one, "kolja@UniMatrixZero #1" is what it should say in settings right?
[Vibrant Android Development] compuguy1088:
Had the same symptoms. It was caused by a lack of space in /datadata.
[Vibrant Android Development] treyvaporizer:
Battery life on 25 with glitch kernel, OC'd to 1.4 Ghz is amazing! :D

Sent from SGH-T959 (CM7)
[Vibrant Android Development] bearsfan85:
Ill be traveling as well, so I just decided to bring my old g1 and have 2 phones and an ipod
[Vibrant Android Development] jzero88:
Are you UnderVolting also?
[Vibrant Android Development] jzero88:
That's what I did but added too many permissions the first time. Works now. Thanks!
[Vibrant Android Development] treyvaporizer:
No, but I will try that. Standby battery is not that great. I'm going to change the governor.

Sent from SGH-T959 (CM7)
[Vibrant Android Development] Phateless:
Welcome! :)
[Vibrant Android Development] kinghorsey:
Anyone else get FCs with the gallery?
[Vibrant Android Development] Phateless:
Nope. Clear data in apps settings and reboot.
[Vibrant Android Development] krazie1:
Nightly #33 is UP and Posted!
[Vibrant Android Development] cal4877:
Has anyone tried #33?
[Vibrant Android Development] Binary100100:
I'm trying it now... I've been running it for about 20 minutes so don't bother asking about battery life yet. :rolleyes:
[Vibrant Android Development] Binary100100:
cm_vibrantmtd_full-33 Changelog

cm_vibrantmtd_full-33.zip

Show 'friendly name' instead of intent URI as preference summary. (android_packages_apps_CMParts)Settings: Update simplified Chinese translation. (android_packages_apps_Settings)Avoid code duplication in shortcut picking code. (android_packages_apps_CMParts)changelog: added eris maintainers (android_vendor_cyanogen)Update German translation. (android_packages_apps_ADWLauncher)DSPManager: Updated Italian translations (android_packages_apps_DSPManager)Update Russian translation. DSPManager-Loudness mode (android_packages_apps_DSPManager)frameworks/base: Added property to disable Camcorder/Camera sounds (android_frameworks_base)Changelog (android_vendor_cyanogen)L&F updates to equalizer (android_packages_apps_DSPManager)Reduce loudness compensation latency and noise (android_frameworks_base)Compression-related improvements (android_frameworks_base)ace: enable aicbootfix (android_vendor_cyanogen)
[Vibrant Android Development] numberoneoppa:
Nothing too incredible.
[Vibrant Android Development] movieaddict:
Anyone try #33 yet?
[Vibrant Android Development] sjohnjuan:
Go ahead be the first :)
[Vibrant Android Development] archie53:
Flashed it ten minutes ago, flashed fine not bootloops. Seems good so far.
[Vibrant Android Development] jwleonhart:
Holy god it's sooo fast. I came from Bionix 1.3.2 test and i'm blown away.

For some reason though I can't access my external SD card? What's up with that?

And what kernels can be used with this and which one comes stock? i'm a little lost, cm7 is totally different.
[Vibrant Android Development] movieaddict:
#33 works fine plus no bootloops for me
[Vibrant Android Development] blahbommer:
sd card is under /emmc i believe
[Vibrant Android Development] archie53:
I spoke too soon, seems that Bluetooth is borked, wont pair or even scan. Tried reflashing and wiping dalvik cache and cache. Gotta have Bluetooth so I'm reverting to 30, I know it was stable there.
[Vibrant Android Development] Binary100100:
There are a couple of kernels out there but personally I think it's best to keep it simple and stick with the original. That's just my opinion though.

Since the rom is still in development there are a lot of changes on a daily basis. Since the rom is updated more than the optional kernels are it is my opinion that it might be in your best interest to keep with the kernel that came with the rom. An example to give would be the Neo7 kernel that hasn't been updated in several days now. Yet there have been several modifications to the kernel and the rom since then. It has been reported that use of the Neo7 kernel with a combination of some of the more recent roms (like the mid #20's+) can cause instability and a sleep of death. These flaws were supposedly fixed in the more recent kernels that are currently being included in the newest nightlies. Now if you find a very recent kernel then go ahead and use that but beware of flashing any of the newest nightlies since changes may have been made since that specific kernels development thus causing instability.
[Vibrant Android Development] Binary100100:
But will it work with devices that are already paired? I haven't tried with my stereo yet but it's a must for me. An inconvenient workaround would be to pair everything up in 30 and then update to 33. That should work... right?
[Vibrant Android Development] FATEOWNZYOU:
Take a visit to my vibrant Bible. In stickies. Might help
[Vibrant Android Development] compuguy1088:
Have they fixed the broken nandroid backup and restore in 33?
[Vibrant Android Development] trepie86:
need to go back to froyo bootloader?

hey guys,

want to try out CM7. just quick question.. i am on GB bootloader. do i need to go back to froyo bootloader before flashing CM7?

thanks :)
[Vibrant Android Development] archie53:
That I don't know. I made the mistake of trying another one of the GB Roms and either when it flashed or when I flashed the GB bootloader my SD got wiped, boy did that piss me off, so I started from new yesterday on 32 and didn't notice whether or not Bluetooth worked. Give it a shot if you want, you can always just revert to an earlier build, that did work for me.
[Vibrant Android Development] archie53:
No I can confirm you don't need to, I am on GB bootloader and everything works fine.
[Vibrant Android Development] trepie86:
thanks man.. going to try the #33 now :D
[Vibrant Android Development] trepie86:
Google Addon

another question, if i not using RomManager.. where can i get the Google Addon Package ?

thanks
[Vibrant Android Development] alawadhi3000:
http://goo-inside.me/gapps/gapps-gb-20110307-signed.zip
[Vibrant Android Development] kelmerp:
Actually this is the newer app bundle:

http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
[Vibrant Android Development] xriderx66:
Is #33 safe guys?

Guess they went from 31 to 33 pretty fast. I dont even have 32 ha.

Hope battery life is good!

hope no bootloop -crosses fingers-
[Vibrant Android Development] adampdx:
33 seems ok so far. I had a different bootloop when I flashed, but I think it's because I flashed the nightly and then Glitch kernel without rebooting first. Got the ROM reflashed now everything is cool. I haven't reflashed the kernel to see if that's the issue. I'm hoping that 33 cures this stupid fast battery drain. 15 hours? I was used to 30+ with Bionix-v.
[Vibrant Android Development] offensive:
26 and 30 with Neo I was getting close to 24 with, 30+ on Bionix? Never. Maybe with full black themes, Juice Defender and limited display usage.

You might have a widget or application causing issues. For example, Minimalistic Text was having problems contacting the google api, so it was constantly polling the weather server and keeping a data connection open.
[Vibrant Android Development] numberoneoppa:
Actually 05/03 is the only one with the new google talk app. ;)

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] adampdx:
My Bionix battery life was great. As far as widgets go, I have the GV inbox, Smooth Calendar and Sense Analog Clock. I've been running these widgets Bionix and CM7, and the battery change only seemed to happen at nightly 30. 26 was much nicer.
[Vibrant Android Development] wergeld:
#33 Would not boot for me - stuck at Vibrant CM screen for over 30 minutes.

Flashed via ROM Manager and I wiped caches/dalvik.

Reflashed 32 and all is good.
[Vibrant Android Development] Phateless:
Runs smooth so far. The vibrant won't be my daily driver until we have gps though. Otherwise this rom is beautifully smooth.

Lack of aosp roms is the one reason I've always avoided samsung phones.
[Vibrant Android Development] Phateless:
flash directly from recovery, it's more stable.
[Vibrant Android Development] trepie86:
wow

just installed #33 with no problems.. thanks archie53, kelmerp, alawadhi3000 for answering some of my questions.

first time using the CM7 and i can just say wow at the responsiveness of the ROM.. came from using bionix and trigger but CM7 is way faster than those 2. now just hope the battery life will be reasonable...

going to play around it more now... :D
[Vibrant Android Development] playonline53tms:
Cm7 34 looks lame for now waiting for major breakthrough ( I hope soon) but 32 is good

Vibrant owns cm7
[Vibrant Android Development] psjames:
My bluetooth was broken and I could not even get it to turn on. I did the following and it is now working. I fully charged. booted into recovery, cleared battery stats, wiped Delvic Cache and all is now working.
[Vibrant Android Development] barribow:
I came to conclusion that "android media database" has a bug in cm7. Sometimes it is not detecting the external sd card, well most of the times in fact.

If you look at android music player, it can't see music on the external sd card either. But another player like powerAmp doesn't have any problem because it looks like powerAmp is using a different method for scanning.
[Vibrant Android Development] cal4877:
Is it just me that I've been noticing many bugs on this new nightlies aren't they supposed to get better?
[Vibrant Android Development] automatek:
I've been one of those people who have been trying all the different versions of the CM7 nightlys only to find that I have no baseband, and cannot connect to the network. (I ODIN'd stock, I ODIN'd GB, tried coming from different ROMS)

Ever since #31 I've gotten a connection to T-Mobile (YEYYY!!!) but the internet and data connection is intermitted, but more often than not, it's disconnected.

Anyone else having similar symptoms? Any solutions?
[Vibrant Android Development] automatek:
Make sure you've unchecked the option in PowerAmp to disable the media scanning of the music folders that PowerAmp uses as it's music folders. Otherwise PowerAmp will put the .nomedia files in those folders and no other media program will be able to find those files.
[Vibrant Android Development] barribow:
can you point me into that option. I just looked powerAmp and couldn't find it. Not sure, which one you are talking about.

BTW, I had this problem even before I install powerAmp. I also looked at those folders not being detected and couldn't find .nomedia file there.
[Vibrant Android Development] psjames:
found answer dumb mistake deleted
[Vibrant Android Development] Locksmith81:
Yes... when you go to the Vibrant CM7 page it tells you the build #
[Vibrant Android Development] TLX317:
Just look at the download page and match the date with the build.
[Vibrant Android Development] jzero88:
@ 50% battery life. 8 hours in with CM7 #26 and Glitch UV -25 no OC Conservative. With moderate use. Definitely getting better life after second to third day. Give it time guys, trust me. You need a few cycles before seeing any battery life.
[Vibrant Android Development] shreddintyres:
http://review.cyanogenmod.com/#change,6120

does this mean what i think it means?
[Vibrant Android Development] Cesarp 24:
Quick question how do I re enable 3g after putting 2g only settings.? I press the icon to take it off but it stays 2g.

Sent from My CM7 Monster
[Vibrant Android Development] jwleonhart:
is gps still broken? I cant seem to get mine to work at all. And i cant access my external sd card..?
[Vibrant Android Development] geoffcorey:
not sure about gps (still assuming so, i've been without internet for a week), but external sdcard = /mnt/emmc or /emmc (both point to the same location)
[Vibrant Android Development] mr smap beeve:
mmmmmaaaayyyyybbbbbbeeeee..........didn't see where it was for the vibrant though...........it says RC1 but only time will tell.
[Vibrant Android Development] jwleonhart:
it says tonights update is gonna be rc1... wats that mean? lol
[Vibrant Android Development] purple1:
rc1=Release Canidate1 we finally got a stable rom im guessing
[Vibrant Android Development] wpbcubsfan:
Nope, not for the Vibrant, it's clearly not listed in that and without GPS and the call audio issues it won't be marked as stable.
[Vibrant Android Development] ironlood:
to be included in next nightly:

cm: Bump versions for 7.1.0-RC1

Not too sure but in my mind when i see something "marked as" or "deemed as" a potential RC im assuming all aspects work in the build and there are little to no bugs (as an example working GPS or mute/unmute bugfix)

But i could be wrong this may just be a somewhat stable build for those who are a bit uneasy for flashing the nightlies.
[Vibrant Android Development] barribow:
Still nobody paid attention that I was saying "Android media database" has some problems. It is not consistently detecting external sd card.
[Vibrant Android Development] jwleonhart:
the gps thing is really a bummer. Also is there anywhere i can get a dark themed mms for cm7?
[Vibrant Android Development] cashyftw:
Rc? I don't think we're ready for that quite yet

Sent from my SGH-T959
[Vibrant Android Development] jwleonhart:
Do any of the 2.3 roms have the GPS working yet? Or any of the nightlys that have GPS working?
[Vibrant Android Development] jrafael:
http://www.youtube.com/watch?v=rCFMDLakxaY

10 char!
[Vibrant Android Development] dgsmith90:
Lol. That made me laugh a little. But, if you were serious about the question, why don't you go up one level in this forum and check out the names of the 2.3.4 threads. A couple have GPS!!!! in the name which means that they have GPS!!!! Read their disclaimers and such for more info. It doesn't take but a second to realize that there are a couple 2.3.4 roms that do have working (kinda) GPS. The nightlies of CM don't quite have it yet, though they seem to be breaking some ground based on the simple fact that it actually turns on and tries to do something now.

EDIT: I added the exclamation marks because it's also in the name. Not ranting, just trying to insert some humor.
[Vibrant Android Development] droidfan77:
Does anyone know if the 2G/3G toggle is fixed yet? I'm heading to Vegas for the weekend and I don't have a need for 3G and would love to save on some battery life.
[Vibrant Android Development] Binary100100:
This is where I'm at so far...

As you can see I'm holding at around 800mhz cpu, wifi on, bt off, gps on (for some reason), edge data, data sync on and I'm down to 28% with moderate use (mostly checking e-mail and Facebook) and it's been off the charger for 10 hours and 31 minutes.

EDIT: It finally died at 6:30pm.

Total lifespan was roughly 13 hours with minimal use.
[Vibrant Android Development] Binary100100:
to be included in next nightly:

add permissions for service "media.yamahaplayer" needed for samsung galaxy s2 (android_frameworks_base)cm: Bump versions for 7.1.0-RC1 (android_vendor_cyanogen)Change package name to avoid conflicts with OI release. (android_packages_apps_FileManager)
[Vibrant Android Development] dasunsrule32:
Nothing to really do with our phones. ;-)
[Vibrant Android Development] Binary100100:
Sorry! I thought we had the Vibrant MTD. My bad.

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