yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mnjm9b:
The great thing about cm is that anyone can jump in and work on fixing something that they find important...

So it will be implemented when someone (maybe you?) gets there hands dirty any figures out a fix and submits it for review.

There are already tvout services running as we speak....just check the running processes with a program like "os monitor" or "system tuner."

Just make sure to show system processes.
[Captivate Android Development] shadvich:
Any way to change the vibration pattern for notifications? I only found settings to change haptic feedback for the touch buttons.

Sent from my phone using something
[Captivate Android Development] ou812bkewl:
Does anyone know what all those OMAP changes in the changelog mean for us Cappy users? It looks like a huge update, but I would like to know how all that translates to real world use. Is there a jump in performance or smoothness between nightlies 159 and 160?
[Captivate Android Development] sixstringsg:
OMAP changes have nothing to do with us.
[Captivate Android Development] Javs2010:
Anybody else's notifications not playing through phone speaker? Music player plays through it so idk what's going on

Edit: nevermind just read the changelog should be fixed next nightly
[Captivate Android Development] Smasher816:
Look through the settings, im sure its in there somewhere.
[Captivate Android Development] brandon_L:
Is anyone else having trouble recording HD videos? When I play them back they skip and jump around. I'm running nightly 160 and glitch kernal.
[Captivate Android Development] cfili:
Same here - running a slightly older nightly.
[Captivate Android Development] SweetwaterBurns:
If I remember correctly, there's a batch of patches in gerrit(cm7 code review system) dealing with hd video. It's been a few days since I looked, so I'm not sure how it's progressing.
[Captivate Android Development] Jusrertiner:
Great product love cyanogenmod

If you can, you should send me a galaxy s 2.
[Captivate Android Development] littlewierdo:
Ok, Im a bit confused.

On Nightly #155 and prior (probably around 10 nightlies or so), I was unable to use my bluetooth fm transmitter for phone calls, but streaming audio (both the Audible app and BeyondPod worked). Nightly #157 fixed this and it worked thru to Nightly #159. When I flashed #160, I was again no longer able to use my BT FM transmitter for phone calls (audio streaming however worked fine).

To be specific, while listening to a podcast / audiobook everything works as it is supposed to. When a phone call comes in, any playing audio is paused (as it should be) and I 'swipe' to answer the call, which then gives me the phone GUI (End Call, Hold, Mute, Bluetooth, Speaker Phone, etc). The Bluetooth button is greyed out and I cannot select it.

What is supposed to happen is, the call, if I am currently 'connected' to a Bluetooth device, the audio from the phone call should automatically be routed thru the Bluetooth device (so the Bluetooth button in the 'in-call' GUI is already enabled) and pressing this toggle should change between the handset speaker and the BT device (this should only be greyed out if I am NOT connected to a BT device).

Forgive me if this is 'too' descriptive, but another user stated he could not turn Bluetooth on and several posts complained this was not descriptive enough.
[Captivate Android Development] RichMD:
The only thing I can think to check is long-press on the bluetooth pairing (for the device) and select options. Ensure that Phone and Media are both checked. Your description sounds like maybe only Media is checked. Worth checking even if that probably isn't it.
[Captivate Android Development] Overgloc:
Is there a setting where you can change the vibrate style? I can't seem to find it. thanks
[Captivate Android Development] CptTwinkie:
I have never found it either and I've been through the menus dozens of times. If it was in there I would remember having seen it. I don't think it's an option. I had custom vibration settings on stock and I miss them when I'm at work.

FEATURE REQUEST for cm lead: custom vibration settings lol.

There I'm sure I broke a rule somehow. Maybe it will help :p

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] just2good4u3434:
You can customize your Messaging vibrate pattern.

Messaging > Settings > Notification Settings > Vibrate Pattern
[Captivate Android Development] Kaik541:
jt1134 (the fascinate maintainer) has done some work toward audio over USB for car dock

if anyone here has a car dock, we would like you to test this teamhacksung approved KANG build.

it should work and does *not* need xcaliburinhand's "dock sound redirector" application from the android market. In regards to anything else that may or may not be working on this build, please do not post that... all we care about is car dock audio.

Download Link: http://www.mediafire.com/?5s5riqe8f6ysmfb

md5sum: 50bcf848f4f335720f4785b44e1edec2
[Captivate Android Development] littlewierdo:
Phone and media are both checked and I tried unpairing and repairing, no dice...
[Captivate Android Development] loserskater:
Just tested. And it works great! Uninstalled xcal's redirect app to make sure it wasn't interfering, and I didn't have any bass issues or anything. Worked just like other kernels + redirect app.

Now to test phone calls.

EDIT: Phone call audio is not routed. But music/media works just fine.
[Captivate Android Development] jt1134:
working on that one :)
[Captivate Android Development] goob1284:
Does anyone else have issues with Google Services eating up a lot of battery and what is the fix? Its really killing my phone. Thanks.
[Captivate Android Development] comdei:
No mine just says gallery is using up all my battery LOL
[Captivate Android Development] johnhazelwood:
Anyone notice the following:

1) Upgrading via Rom Manager, I lose apps and need to reinstall via titanium? Doesn't seem to happen when I manually upgrade.

2) Email client connects via push, rather than using fetch at the interval I have it setup for? Email push tends to eat up a lot of battery too, so that could be one reason for poor battery life.
[Captivate Android Development] RichMD:
Stock CM7 kernel for a given build

I currently am running #158 and I flashed a new version of a custom kernel. I seem to have really bad battery drain compared to "normal" and I have been running CM7 for a while. I want to flash the stock kernel for CM7 so I decided to look in the zip for boot.img so I could put it in another update zip file. It (and many other files) show as modified 2/28/2008 which obviously doesn't make sense. How do I tell when the kernel is updated in a build? I found a zip file (can't remember where I found it) that is named "CM7StockKernelRevert.zip" dated 10/14/11 which I assume should be fine. However, I would like to know for future reference how to tell if a zip has an updated kernel, etc - as well as confirming it should be OK for #158.
[Captivate Android Development] sixstringsg:
Just reflash the nightly. It puts the kernel back in. It could cause problems just putting the boot.img back in, because there are various modules that need to go, and also various custom kernel files that need to get deleted. The changelog says when a new prebuilt kernel is coming.
[Captivate Android Development] RichMD:
Did that change someone recently? I thought any custom kernel and modem stayed unless you flashed back to stock.
[Captivate Android Development] RCDuke:
I have experienced the same thing. I would flash the latest Glitch kernel over a CM7 nightly. Every time I flashed a new nightly, I had to re-flash the Glitch kernel over it. Not that big of a deal, but just another step I had to do.
[Captivate Android Development] shaolin95:
Yep,the modem stays the same I had when flashing nightlies but the kernel is replaced.
[Captivate Android Development] CptTwinkie:
That's only the message setting and I don't use cm's messenger to begin with. When I was on stock I had custom vibrate settings for each app that had notifications. After I got used to it I could tell exactly what app was notifying me without looking at the phone. Now all vibrating is the same

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] CptTwinkie:
I had that happen somewhere around nightly 110. I was having trouble getting my contacts straightened out so I was making regular changes and those changes were keeping sync active. I just assumed it was related because the battery hogging stopped after that. It either went away on its own or went away the next time I flashed.

Fyi, when I flashed back then I used rom manager with clear cache and gapps checked. I have since changed methods but what I'm saying is that it got a fresh gapps when I flashed.

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] tiuk:
Use Tasker.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] CptTwinkie:
I lost apps with rom manager and I had gapps problems regularly. I update manually now and have no problems. Backup, clear cache partition, flash, reboot...

About the email, push notification should use no battery except when it goes active to receive mail. Regular interval checks will use battery not only in checking, which also eats data, but also in preventing the phone from sleeping to conserve power. I'm sorry but I don't have a working knowledge of the mail app. I use the Gmail app and it does a good job of not bothering me.

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] CptTwinkie:
Well that answers the original question I suppose. I'll leave it there because at this point I'm satisfied with what cm brings to the table (and I dislike tasker) My request was just an idea I offered to the devs and not something I needed solved. Thanks anyway

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] forlack:
I am experiencing charging death where the phone goes into low power mode when plugged in at night. It happens maybe once every 4 or 5 days. I use my phone as an alarm clock and this is very annoying. I love everything about CM7, but I never had this happen until I flashed it. I also just tried going back to stock and flashing the latest nightly but it happened again a few days later. I have searched this massive thread and found some experiencing the same problem but no real solutions. Can anyone help?
[Captivate Android Development] nkrick:
Did you restore anything gapp related with TiBU? If so, try doing a factory reset, install the gapps package, and don't restore any gapp related apps or data with TiBU.

That could be due to picasa gallary sync. If you don't feel the need to have all your picasa images synced to your gallery, can you disable this and save battery.

---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------

Try changing the minimum CPU clock speed to 200 Mhz. This works for a lot of people. There is a known issue in Captivates manufactured before Nov 2010 that can cause a sleep death. Bumping the clock speed up to 200 Mhz is normally enough to prevent the issue. Supposedly this issue was fixed in software in a November update, but the software patch may have been a clock speed adjustment or something similar.

You can also flash to stock and try to get AT&T to replace your phone. There is supposedly an AT&T internal document from Samsung related to the problem (the doc was leaked, if you search around you will find it). Back in Dec/Jan, lots of people with the problem were able to call AT&T, tell AT&T they had the problem, and get their phone replaced.
[Captivate Android Development] forlack:
Thanks I'll give that a try. Does voltage control work on CM7 for the minimum clock setting? Now that you mention that I think I remember my minimum clock setting being 200 when I was overclocking back a few ROMS ago. Thanks Again
[Captivate Android Development] wizurdofawwz:
I'm currently not getting any sound/vibration when receiving a text message. I have checked every setting and cannot come up with something. Anyone having a similar issue?
[Captivate Android Development] Kaik541:
did you open the text messaging application, hit menu, choose "notifications" and select "vibrate"->"always" and a notification sound?
[Captivate Android Development] tiuk:
Handcent also lets you set custom vibe patterns, can even do it by contact

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Techronico:
Hi guys, i'm a neighbour from the EVO3D forums and have a friend with a Captivate. I wanted to know which nightly is the most stable... (I know oxymoron). Thanks!
[Captivate Android Development] tiuk:
I can't even remember the last nightly I would call unstable. Just flash the latest, it'll be fine.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] wizurdofawwz:
Yes. I have checked that, profiles, system sound, etc.
[Captivate Android Development] phlunkie:
periodically i lose notifications. Either rebooting or going back into the sound settings will kick start it again.
[Captivate Android Development] EnemyOfGlaDOS:
+1 well said :D
[Captivate Android Development] shaolin95:
+1 well said for well saying the previous comment! :eek:
[Captivate Android Development] EnemyOfGlaDOS:
Lol :p thank you sir, that was well said!

:D
[Captivate Android Development] pandakh:
Hey, everytime i use odin to flash to stock, and then flash cyanogen back again i get a boot loop, which shows a cwm command list and then it reboots again and again, i can get into download mode with a jig, but how do i fix this, its the second time this happens to me...thanks in advance
[Captivate Android Development] ninjuh:
I'm running build #160 & am having a new problem. No sound with sms notifications. I'm running stock sms app, all volume controls(that I know of) are turned all the way up. Is there a new setting I'm unaware of that controls this? Calling notifications work fine as do all other sounds. Phone does vibrate with new texts just no sound...can't figure it out
[Captivate Android Development] nimper:
Stop flashing to stock? You don't need to do that unless as a last resort to fix something.
[Captivate Android Development] pandakh:
I was using another rom before flashing cyanogen over it, and i had a bunch of fcs and problems, so i flashed to stock....and that happened when i tried to install again.
[Captivate Android Development] ninjuh:
I experienced that when flashing this last time to build #160, I just reflashed the rom in cwm & it worked fine after that
[Captivate Android Development] nimper:
edit: NM misunderstood
[Captivate Android Development] pandakh:
flashed 3 times, stocked 3 times, no luck yet.
[Captivate Android Development] nimper:
Quit flashing to stock. Just do a factory reset in recovery if it happens again, or flash an earlier nightly.
[Captivate Android Development] Techronico:
Thanks, I also would like to know if anyone could tell me what the best kernel and settings would be for CM7 for the best battery life on the Captivate. Again, thanks for helping me out as I do not have this phone and I'm just looking to help my friend.
[Captivate Android Development] sixstringsg:
I would recommend the Glitch kernel. But I would also be slightly biased....
[Captivate Android Development] makelegs:
Sorry to just pop up outta nowhere with a random question, here...

Any of you folks had a chance to test drive the NEW PREBUILT KERNEL yet? It hasn't been merged, but not sure how many kangs floating around.
[Captivate Android Development] RichMD:
I posted this earlier in the Glitch thread - http://xdaforums.com/showpost.php?p=18875578&postcount=1657

I am not biased and I do realize that this was a very simple test of standby compared to full usage but it is at least something to give you some input.
[Captivate Android Development] XsceneXhippieX:
Glitch boot loops me in the latest, never happened before, I'm on the v12b3 though which is probably the problem
[Captivate Android Development] cfili:
Waiting for v13 to be released to give it a run.
[Captivate Android Development] RichMD:
I am running nightly 163 with V13RC1 (I bought the app) and I have no problems so far.
[Captivate Android Development] jjtitus098:
Starting to get tons of FCs for no reason. Haven't changed anything at all. Tried reflashing and didn't fix it. Any suggestions? Just weird since I did nothing.
[Captivate Android Development] RichMD:
Just a guess but maybe datadata has filled up which will cause many FCs and I imagine can happen without you consciously doing anything.
[Captivate Android Development] jjtitus098:
What's the best way to fix that? I've never had it happen in the past. Do I have to wipe and reinstall apps?
[Captivate Android Development] shaolin95:
Use an app like APP2SD and move some programs to the external card then verify the /datadata again....well actually start by checking the data data by opening terminal and typing df
[Captivate Android Development] makelegs:
Has anyone tried the S2E app, yet?? Seems like that would solve it. Moves apps, dalvik, and even data if chosen
[Captivate Android Development] jjtitus098:
Sure enough, it was 100% full. Moved stuff over and it seems to have worked. Thanks guys.
[Captivate Android Development] br123:
Had the same issue a few weeks ago. I moved to a Samsung ROM but had to come back to CM7 because it was simply so much more superior - if the FCs keep happening I'll know why!

On another note: atinm/Kaik47, any plans to fix support for 32GB microSD cards? sounds like lots of people have been having issues with 32GB cards. my 16GB card work fine and I know it's not the card's issue because it works with samsung roms.
[Captivate Android Development] kschumake83:
I just had that happen to me yesterday, if you pull the battery for a minute or two you can get into recovery and wipe data and reflash nightly, it works then
[Captivate Android Development] CptTwinkie:
I flashed 163 over 158 yesterday and I've noticed two instances of odd behavior. I read about both of these either here or in the glitch thread. I thought I had better start here to see if it's the update itself or the update with glitch.

Issue #1: the battery will not charge to 100%. This I can deal with as long as there isn't a problem. As I said I read about someone else having this problem recently so I'm just wondering if it's common with the latest nightlies.

#2: Google services ate my battery today ...twice. I was using my phone a lot today. I would guess maybe 6 hours with the screen on. Google services used over 40% of the battery on both charges. I tried killing everything Google related and it didn't help. Again I read about someone else having the same issue.

So what do you guys think? Bad flash? Bad nightly? Glitch kernel problem?

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] bigbooty:
6 hours with the screen on and your complaining?
[Captivate Android Development] CptTwinkie:
Yes. I was mostly just reading and I keep the brightness the entire way down. Normally I get maybe 4 hours out of a fresh battery. Today I got about two and a quarter, then charged it for about two hours (it stopped charging at 94%) and then I got another two hours. Google services used a lot of power all day. I mostly had opera mobile, facebook and xda open. I use these apps a lot and don't usually have a problem. I'm going to restore my nandroid backup of nightly 158 in the morning to see if that puts things right again.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] CougarBroker:
Change Font?

Any way to change font without a 3rd party app, like in settings?
[Captivate Android Development] nbell13:
Nope. :-( you can flash them through CWM also
[Captivate Android Development] CptTwinkie:
Good news. I reflashed everything and issue #2 is all better. Facebook is back to being my biggest power drain as usual!

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] XsceneXhippieX:
So the change log for 163 says something about NEON acceleration, anybody know what that change was specifically? I'd like to know because 163 "feels" smoother than I've felt cm7 run for a while with a full wipe running everything stock, I have an urge to blame that smoothness on the NEON acceleration change made and would like to be corrected if I'm wrong :)

Sent from cyanogen mod 7
[Captivate Android Development] nkrick:
Based on the information about the change (http://review.cyanogenmod.com/#change,9257) it seems that NEON optimizations could be a likely culprit in the smoother feel. To my untrained eye, it appears they changed the floating point calculations from double precision to single precision, allowing for faster mathmatical calculations resulting in faster GPU 2D drawing. Single precision calculations for increased graphics speed is probably a good compromise for most people (unless you are using your cell phone for protein folding or something).
[Captivate Android Development] jkl555:
SOD

This is probably not something new to cm7. I still experience Sleep of Death. I have no idea what is causing it but it is going to affect my daily use. It happens once a while even if I am on the stable 7.1 build.

I followed some suggestion in some forum that to increase the minimum CPU frequency from 100 to 400. But I tried with 200 first and it still happens. So I am going to try 400.
[Captivate Android Development] XsceneXhippieX:
Awesome, and guess what? On top of that I got the tegra2 optimized version of shadowgun to run on my cappy today! Hell yes cm7! I love this rom, all i did was use the CF3D drivers and basically check both boxes to make quality worse, and overclock for smoothness reasons and its completely playable, I never guessed my captivate could run basically xbox/ps3 graphics

oh yeah, i couldnt get it to run on nightly 158 at all and thats why this is an accomplishment for me :p, must be the NEON changes right? jk, but it probably didnt hurt

Sent from cyanogen mod 7
[Captivate Android Development] GRACO:
I went from Cognition 4.5.3 to Pinnacle 1.3 looking for better battery life, getting like 14 to 16 hours light use...

Calibrated the battery a thousand times, and no luck.

I just flashed the latest NIGHTLY + glitch, and battery improved like 200%!! im getting more than 24 hours... and still have 30%, rom is super extra smooth compared to Cognition and Pinnacle. I will try to UV or something to see if a can get more battery life.

Regards!

---------- Post added at 02:06 PM ---------- Previous post was at 02:00 PM ----------

What about Issue #1?...

I have the same "problem" using glitch, will not charge to 100%, but battery life is quite a lot better than before...
[Captivate Android Development] CptTwinkie:
There were recent updates to chainfire also. I'm not sure which one made it work. I'm just glad that it does. The android gaming experience just improved a lot

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] CptTwinkie:
Battery life is much better on glitch. That's the only reason I keep going back to it. My phone has a problem with 1440mhz and it limits my overclocking unless I want to lock in the clock speed to something higher which then kills my battery. So I'm stuck at 1400 which isn't much better than the 1300 available on cm7 stock. It's all about the undervolting for me. Pardon my rambling...

I charged my phone today while I slept (working graveyard shift) and it went to 100%. Idk if it had something to do with reflashing or battery learning.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] WillyWonka23:
Alright guys, my sound toggle in the notification dropdown doesn't work anymore. It is stuck on 'Sound on'. I can change it through any of the other methods the phone has except that dropdown toggle.

I've been flashing maybe every 5 nightlies or so and on the Glitch V13 kernel. Any help on fixing this would be great!

I wasn't sure what to search for an answer so sorry if this was brought up before.
[Captivate Android Development] SweetwaterBurns:
You have to go into CyanogenMod settings - interface - notification power - widget buttons - sound modes and choose the ones you'd like to toggle between.