yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] sada23:
I have been flashing CM7 without wiping since the last stable build. From build 160 forward,

1. I am not able to connect my phone to my PC or Mac.

2. The sound toggle switch in notification area is broken and

3.The battery life seems to have worsened.

These are my observations and not complaints.

I am on Platypus R17 Kernel and whenever I clean (using the ultimate kernel cleaning script) the kernel and try to install a newer kernel, I get into boot loops. Need to find some solutions or work around.
[Vibrant Android Development] MizSxxyBych:
UGH

My APN and baseband is disappearing everytime I reboot and APN restore doesnt seem to be helping.... I got it back somehow (dont ask how..lol)...but I'm sure when I reboot it will be gone... Any ideas?
[Vibrant Android Development] KWKSLVR:
I Odin'd back to stock and flashed #163 just for fun because I was having some issues as well. On a fresh install, I too have a broken sound toggle switch in the notification area. I can't comment on battery life yet. I'm also able to connect to USB storage on my PC via USB (dur ;) ). I haven't tried adbWireless yet. My APN's are fine as well.
[Vibrant Android Development] karimsaud21:
Yeah ive been meaning to do this, i have just been busy.

How would i test the 911 call though?

And as i have never performed a logcat before, some instructions would be nice.
[Vibrant Android Development] Urukiora:
I have been on Bionix ROM since it came out and have been very reluctant to flash a gingerbread rom but I flashed CM7 last night and wow... just wow fast
[Vibrant Android Development] sada23:
Guys,

Was playing with settings and found that the sound toggle in the notification area could be set to the way it was before I/we reported it as broken. Seems like it was set as a default before and now we need to set it exclusively. The way to set it back as it was before is:

Settings->CyanogenMod Settings->Interface->Notification power Widget->Widget Buttons->Sound Modes.

here select any combination you want. I selected Vibrate,Sound and Sound+vibrate to get back to what was default before I thought it was broken.
[Vibrant Android Development] KWKSLVR:
Pure genius! Good find man. I've never even noticed that option before. I was kinda wondering because everything else has been great on #163. Shoot, yesterday I popped in a spare battery and booted up @ 95% and I'm @ 60% 17 hours later. :eek:
[Vibrant Android Development] Goten310:
I was wondering if anyone is having problems with installing some apps from the market. I tried installing Flash and Netflix and I was geting the message "your device is not compatible " message on top of the screen. Any work arounds for this?
[Vibrant Android Development] ironlood:
Has any one had any issues with the new VibrantMTD kernel by Eugene
[Vibrant Android Development] bartek25:
just go to build.prop in system directory and find line which say vibrantmtd and rename it to SGH-T959 instead it should help fix incompatible issue
[Vibrant Android Development] bartek25:
but to flash new nightly u will have.rename it back to vibrantmtd :/
[Vibrant Android Development] Goten310:
Agh tried to edit the build.prop file. Renamed it but still having incompatible issues dang it.
[Vibrant Android Development] jzero88:
Bad ass dude. Had no idea we had this option.
[Vibrant Android Development] ezraf:
What what? 60% after 17 hours? What kernel? Are you doing anything special?

Last time I was on CM I was getting about six hours to dead battery.
[Vibrant Android Development] quick_:
Having an issue where the phone will not go to sleep, com.android.settings (Androi System)

Is what's keeping the phone awake, this process has a few things associated with it like cyanogenmod settings etc.. I'm build #163

Any ideas?
[Vibrant Android Development] KWKSLVR:
http://xdaforums.com/showthread.php?p=18885872

[ROM] CyanogenMod 7 for the Samsung Vibrant :: V7.1.0.1 (10 Oct 2011)

Nope, nothing special, just a proper install, stock kernel, stock everything. Like I said in the linked thread, "battery life" is subjective. My app/email syncs, use, signal, etc is not the same as someone else's.

Most people aren't installing CM7 right and then they're playing on it all day wondering why their SAMOLED isn't magically getting eleventy billion hours.
[Vibrant Android Development] DxTcmix:
Try Disabling GPS and rebooting your phone. That fixed the issue with CM7 based roms for me, now i get pro battery life :) Keep GPS Disabled when you are not using it, you will see the battery life difference for sure :)
[Vibrant Android Development] quick_:
Thanks I will try that! So what do you do when you need GPS, just turn it on then disable it when you are done, reboot your phone.. and continue on?

Thanks
[Vibrant Android Development] fishman0919:
Yes... that's it
[Vibrant Android Development] paypalbid:
I have never been able to use my gps with this rom. time to explore other options.
[Vibrant Android Development] sada23:
Try installing GPS fix 1.5.1 and make sure you ahve angrygps installed. Use GPS test to check your GPS. If that doesnt work, install GPSrestore from Samsung( you can find it in market). To use GPSrestore from Samsung, you will need to get into build.prop and change the line conatining soju to SGH-T959. Save it, reboot the phone and then execute GPSrestore app. If the app fails to lock any satellites, dont worry. Get out of the app and start GPS test app. You could set the phone not to sleep in the preference of GPStest settings so that you could test the GPS.

Note: You need to have a kernel that supports GPS. The latest by Eugene does.
[Vibrant Android Development] HaloMediaz:
Battery seems to work great. I have no heavy usage, just some music and stuff.
[Vibrant Android Development] Phateless:
Wow, that's impressive. I have a friend with a vibrant, maybe I should update her...
[Vibrant Android Development] swa2k4:
Depends on if you want her! If you really do you'd buy her a sensation and sell her vibrant lol cm 7 runs super fast on alpha9 with that.. also she could call 911 safely too then!
[Vibrant Android Development] Phateless:
Lol, definitely not like that. Roommate's gf.
[Vibrant Android Development] aldawood14:
Hello

I am working journalist in Saudi Arabia, and I would like to record calls

Can you help me

vibrant nightly rom cy.

rom on 166
[Vibrant Android Development] Goten310:
Setup a Google Voice account.
[Vibrant Android Development] creeve4:
Is the "Stable" release (7.1.0.1) any more stable than the newest nightly?

I've been running nightly 157 since it came out and have not experienced any problems until this morning. I charged my phone to 100% with the phone off, booted to recovery, and wiped battery stats. Now my phone won't boot past the CM logo screen (Yes, I've tried all methods of wiping).

I'm not looking for help with the "no boot" problem, just wondering if the "Stable" release is any more stable than the newest nightly?
[Vibrant Android Development] Dougfresh:
I never have the gps on.I get a approximation of about 500ft-1000ft w/just the cellular triangulation.It dramattically saves battery and phone overheating
[Vibrant Android Development] droidfan77:
Have you changed your screen resolution at all? I get this message from the market all of the time, but only when my screen is set at 200. When I switch it back to 240 the market stops giving me that error message. I just download all of the apps or updates that I need and then switch my screen back to 200.
[Vibrant Android Development] Goten310:
By the gods you're right. I have it set to 200. Going to set it back to 240 then switch it again when I get my apps back... thanks!!!
[Vibrant Android Development] HaloMediaz:
Look for auto callrecorder by Roman g in the market. Another one is record my call by Nathaniel :) hope that helped.
[Vibrant Android Development] aldawood14:
Welcome dear

Thank you for helping me and find a solution to this problem

In fact I used this application earlier in addition to other programs

But the problem is that these applications do not work even with the use of loudspeaker

Is the problem due to the modem or the kernel?

I am very sorry for my poor English language
[Vibrant Android Development] HaloMediaz:
When i go to the internet i cant access any sites nor can i google search. Any one know how to fix this?
[Vibrant Android Development] Dougfresh:
Same thing happened on my phone yesterday after using 3g watchdog and sns app.if your using these sorts of apps,uninstall,go to web cache and clear,go to recovery clear cache and dalvik cache. Reboot
[Vibrant Android Development] chadhoard:
How do I mount my phone, so I can see it on the computer as a drive?
[Vibrant Android Development] ew:
Reset CM7 Governor and clock settings (If I have trouble)

In order to improve the performance of my phone, I am trying to shed as many programs as I can - especially since CM7 provides so many utilities that could be substituted for third party utilities.

So, I have used SetCPU to set up Governor and clock settings on startup. Well, I can do that in a CM7 setting. One question - if I run into a stability problem (and have these items to configured to "set on boot" - is there a way to get back to the default - so that I don't set anything on boot? I have tried the kernel cleaning tools, but those don't do anything. Any ideas. I would think that a CWM flash-able script would be great for this - if I could find one.

Thanks
[Vibrant Android Development] creeve4:
You need the Nexus S USB drivers. The CyanogenMod wiki has the info you need:

Where can the Nexus S drivers for use with ADB be obtained?
[Vibrant Android Development] paypalbid:
anyone having trouble with Nightly 170? I get the boot loop CM7 screen. Had to restore my backup of 168 release.
[Vibrant Android Development] danilkov:
Same here, sits on the logo screen
[Vibrant Android Development] nedlog:
Yes, you have to wipeout data and reformat partition and reinstall gapps, them install 170.
[Vibrant Android Development] ew:
I installed 170 without a wipe over 164. I have not noticed any problems yet.
[Vibrant Android Development] nedlog:
Everyone please do a backup before flashing 170. I tried updating through ROM manager without wiping data and got boot loops. I was able to get to recovery and wiped everything and tried again. Seemed to work, but then I noticed my phone kept checking my SD card for errors. Also my datadata folder is missing. Needed to go back to my restore. Going to try redown loading the zip after work and try again.
[Vibrant Android Development] roffee:
anyone meet SOD problem. weird. i have meet several times.
[Vibrant Android Development] hurtz777:
170 works fine for me with Neo17R18 doing a JFK Odin fresh install. Call audio quality is also clearer for some reason.
[Vibrant Android Development] user900:
camera sound and calendar

hello. can anyone tell me how to remove the camera sound or flash another camera that works with this rom?

and how can i use the calendar? it asks for my e-mail when i open it.

i try to set it and i get unable to retrieve info from server - error or something like that.

thanks.
[Vibrant Android Development] tbrar:
For the camera sound try settings>cm settings>sound>mute camera shutter.

Are you trying to use google calendar? Can you provide details about exactly what you are trying to do.
[Vibrant Android Development] user900:
tried the cm settings but it doesn't work.

and i want to use the calendar and when i open it it asks for email and password.

then i open wifi and use my google email > retrieving acc info > server settings (tried with ssl accept ssl certificates checked and everything) > unable to open connection to server.

that's the problem.
[Vibrant Android Development] ironlood:
This is the MIUI camera as an installable .APK file no need to flash or push to the system folder just install like normal.

In the settings there is an option for muting the camera sound.

http://min.us/lbojqGILtuY9jB

Hope it helps

also with your calander issue i would suggest using a free app called jorte
[Vibrant Android Development] Se7eN43:
90_callvolume script

if you are experiencing low in-call volume with any of the outputs and you do not use glitch kernel, there is an init.d script in the miui forums - glitch thread.

the script is set to stock volume gains. i personally raised them to the max as well as the mic gain settings and tested with no complaints of distortion on both ends. detailed instructions can be found on the thread as well as within the script itself.

forum link:

http://forums.miui.us/showthread.ph...27-08-11-Glitch-V12-Beta-1.7GHz-OC-UV-Voodoo&

direct dl link:

http://androtransfer.com/tk-glitch/CM7-kernels/Glitch/90call_vol.zip
[Vibrant Android Development] jimmynguyen91:
Did you restart your phone after you applied the setting to silence the camera shutter? I'm on nightly #168 because #170 gives me bootloop, but my camera shutter is silenced. Everything works except for gps :[
[Vibrant Android Development] KWKSLVR:
#170 gave me a boot loop as well, Checksums matched. I restored my Nandroid and all is well.
[Vibrant Android Development] zmattmanz:
170 gave me a bootloop as well.
[Vibrant Android Development] mattb6288:
170 isn't giving me bootloops, but gapps runs good then i restart and everything gives fc pop ups. going back to 165 for now. that worked the best for me along with streamline from eugene
[Vibrant Android Development] bigtom624:
Me too as well
[Vibrant Android Development] paypalbid:
170 and 171 both have bootloop problem. Who know maybe every ROM beyond 168 will have problems
[Vibrant Android Development] sleepy222:
Try this. Go to settings > account &sync. Delete your account then add it back.
[Vibrant Android Development] zmattmanz:
Anyone know how to access both the internal storage and SD card? It seems like I had this set up correctly on earlier build but now I can either select only the SD or internal storage when I use a file explorer.
[Vibrant Android Development] bosox86:
For me 170 bootloops, 171 did the same. I odined to stock, re-installed packages twice, them flashed 171 again. I worked, but now it wont stop preparing sd card and checking for errors.
[Vibrant Android Development] nedlog:
Yes you need to mount and unmount it manually to get it to clear. Settings>storage. I had boot loops just needed to wipe data first. With glitch no need to mess with sd card
[Vibrant Android Development] layzer253:
I came from the Galnet ICS rom, to 171. In the clockwork bootloader i formatted every partition, and installed 171 and the newest Gapps manually. No problems to report yet. Installed all my apps over wifi.
[Vibrant Android Development] sada23:
Guys,

I usually install the newer builds over the older builds without any wipe. they used to work wonderfully well until the builds 170 and 171. Builds 170 and 171 gave me bootloops like others got.

Today I downloaded build 171 via ROM Manager and here is what I did.

1. Went into recovery by pressing the power button and choosing to Reboot.

2. In the recovery installed build 171 over 168.

3. Installed the newest Gapps.

4. Ran Fix permissions.

5. Installed Eugenes latest kernel.

6. Rebooted the phone.

I could get the build 171 to work without bootloops this time.

I think the boot.img in this one is different from build 168 and also the changelog mentioned about kernel 2.6.34.4 being used. I am not sure if the kernel was the cullprint. I just thought it could be and hence flashed Eugene's latest Kernel. Prior to build 170, I never reinstalled the kernel.

Hope this helps.
[Vibrant Android Development] paypalbid:
Ill just stick with 168 till tge next stable build. Not gonna go through reinstall all the apps not knowing if 170/171 is any better.
[Vibrant Android Development] sada23:
You dont have to worry about re-installing all the apps. Flash build 171 over 168 without any wipe. Then Flash Gapps 0828. Flash any of the kernels you are currently using.
[Vibrant Android Development] Phateless:
No need to reflash gapps. Wipe cache and dalvik and flash nightly.
[Vibrant Android Development] jzero88:
No matter how many ROMs I try, or what mods I do, I always come back to my nightlys.

I am experiencing the SD card error and have to unmount then remount. Hopefully the next nightly will have a fix.

SIDE NOTE: Does anyone know if MIUI uses the stock CM kernel? I seemed to have gotten much better battery life when trying MIUI, definitely noticeable, HOWEVER, I did have GPS off always, since I read it caused battery drain. I will be trying CM now without GPS.
[Vibrant Android Development] paypalbid:
which kernels do you guys use? I was using whatever kernel that came in the Nightly as a package. I never flashed the kernel separately for the vibrant before. I came over from the HTC Magic
[Vibrant Android Development] Jasonhunterx:
Neo
[Vibrant Android Development] lawalty:
My wife's Vibrant time zone keeps automatically switches to Mountain time, when we're Central.

Anyone eles experiencing this little bug?
[Vibrant Android Development] Jasonhunterx:
Omg having so much problems with this rom the market fcs sometimes an apps fc then I go to recovery an wipe cache reboot then everything is fine for a little bit
[Vibrant Android Development] sada23:
I am using Eugene's latest BLD support ROM. It works for me.
[Vibrant Android Development] alpha2beta:
I am having the exact same problem too, I live in central and it changes to mountain time.
[Vibrant Android Development] beren28:
Any chance it is just changing for daylights savings time and you guys forgot?
[Vibrant Android Development] alpha2beta:
No, it keeps going from Central to Mountain I've had to change it back to central twice now, so instead of going back one hour it went back two hours this morning.
[Vibrant Android Development] muleyman:
I am seeing the time zone issue on 7.1.0.1 as well. I am in the Mountain time zone and my phone thinks it's in Pacific. Curiously, my wife has a motorola Cliq running a recent Cm7 nightly and her phone shows the time correctly.
[Vibrant Android Development] lawalty:
This is how this bug has been found out. My phone the G2 is ok. I have it set to automatic time adjustment (in settings). My wife an I both run CyanogenMaod nightlies.

My wife's phone which is the Vibrant is an hour off. When I got into settings, her's is also set to automatic adjustment, but I see its set for mountain time, not central. So when I turn off automatic adjustment and manually switch it to central (which adjusts the time correctly). When I turn automatic adjustment back on, it pops back to mountain time zone.

???
[Vibrant Android Development] muleyman:
Edit: I am running Streamline kernel, fyi
[Vibrant Android Development] nedlog:
I saw the same issues; rebooting fixed it for me. Stays on the Mountain now.
[Vibrant Android Development] creeve4:
My phone switched to the wrong time zone as well. Should be MST, but went to PST. I manually set the timezone, rebooted, and set it back to automatic update, it seems to be staying for now.

I also noticed that Maps is not able to determine my location from cell towers (data network), keeps giving me the error: "your current location is temporarily unavailable"
[Vibrant Android Development] Genesis3:
I think this is a T-Mobile thing - the time zone in "automatic" mode comes from the tower along with the rest of the NITZ update. I'll see if I can "catch" it doing it.
[Vibrant Android Development] bosox86:
Has anyone tried 172 yet? Ever since flashing 171 I get SOD, even after restoring a backup.
[Vibrant Android Development] wxaxgxs:
Switching between automatic and manual time in addition to a few reboots finally fixed the Central --> Mountain thing.

Royally f'ed my day up. My (battery powered) clock managed to die overnight (coincidentally at 8:30). I checked my phone and it said 7:30. Slept in another hour only to find out it was 9:30. Pwnt.

On an unrelated note: does anyone else have the problem of their phone IP address locating them in Washington? This is not a ROM issue perse as I've had this problem as long as I've had my Vibrant, but it's annoying when any IP-sensitive APP or website places me in Washington when I'm in the midwest.
[Vibrant Android Development] creeve4:
My wife's phone, which is also on the T-Mobile network, updated to the correct timezone last night.
[Vibrant Android Development] danilkov:
Rebooting fixed it for me as well, sort of. The time is correct, but the automatic time zone is Easter Island Time, not Eastern Standard Time
[Vibrant Android Development] flipper2006:
I think the problem with the Time zone is that Manuel, the guy who flips the switch for Tmobile for time zone changes was sick and Elroy, Leroy's brother, pushed the wrong button at 2am.:rolleyes:
[Vibrant Android Development] royalkalana:
i installed this rom and i there is no market app. i tried to download a market.apk and it didnt work either.it installed but didnt work.. anyone can help me ?
[Vibrant Android Development] paypalbid:
i suppose you can download the gapps.zip(google apps) to get all the stock apps. Sorry to hear you are having trouble. I don't know what is going on with the Nightly Rom lately. Everyone has some kind of issues. I'm still on 168 and will probably stay here.
[Vibrant Android Development] PigProtist:
Try reading the OP.
[Vibrant Android Development] Phateless:
+1.
[Vibrant Android Development] chui101:
172 is basically the same as 171, doubt it would help.

Incidentally, has anyone managed to figure out how to get the /mnt/emmc removable sd card mounted? It keeps getting stuck on checking the SD card for errors.
[Vibrant Android Development] javacody:
+1 What the heck is going on here?
[Vibrant Android Development] Jasonhunterx:
Mine works fine what wrong with yours?
[Vibrant Android Development] bosox86:
It is, but 172 flashed fine for me, 170 and 171 didn't.
[Vibrant Android Development] sada23:
Same here. 172 flashed fine and not issues with SD card or any other.
[Vibrant Android Development] wyvernwaddell:
Flashed 172 and got the sd card checking for errors problem. If I dismount and remount it quits looking for errors but can't see the external sd card at all after that..checked all the places it could be mounted and it's not there.Anyone got any ideas?

I did a clean install..didn't carry over any data, so not sure what happened...

No emmc folder under mnt, no sd-ext under mnt.

Went back to 168 and emmc is under mnt and is accessible..flashed 170 and it's gone. Gonna try 171 and see if anything changes, but will probably stay on 168 until this gets sorted out..

Tried 171 and same thing..no external sd card under mnt.

174 shows emmc and all is back to normal!

Thanks guys-you rock!
[Vibrant Android Development] CM Wave:
The next build will fix that issue: http://review.cyanogenmod.com/#change,9944
[Vibrant Android Development] paypalbid:
I installed 174 rom via rom manager for the first time. I wasnt able to keep my old apps and settings. What am i doing wrong?
[Vibrant Android Development] nedlog:
You probably wiped data which wiped everything. Some say they do that all the time and then reinstall their apps with Titanium Back-up or just let the Market reinstall. I've had good luck with downloading the latest nightly and manually installing from Recovery with only wiping the cach and Davik cach. This works most of the time for me.
[Vibrant Android Development] paypalbid:
Thanks for your help. I went back to the good old recovery mode method. I guess the trick is to wipe Cache Partition and Davik Cache. The reason I attempted the Rom Manager update method because I was getting the bootloop on realease 170 and up. Prior to 170 release I didn't have to wipe the cache and the new Nightly release would just install on top of the old version.
[Vibrant Android Development] beren28:
There was an error with 170 causing the loops. It appears to be better in the most recent version.