yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shane87:
Mine does not turn on unless i tap the capacitive buttons, or i just unlocked the screen.

Now that you mention it, though, i do remember my capacitive buttons lighting up on screen taps on both gb and froyo.
[Captivate Android Development] shane87:
Deleted - hit quote instead of edit, lol
[Captivate Android Development] whyareyou:
There is a setting for this under Settings > Device > Advanced > Backlight Timeout
[Captivate Android Development] shane87:
That only affects how long the capacitive buttons stay on after being lit. It doesnt affect what will cause the capacitive buttons to light up.
[Captivate Android Development] p1gnone:
Having CWM'd build 17 I get a persistently repeated message that Email application stopped. I can access mail via app Maildroid so wonder if I even need the native app Mail.apk?

adb [from the pc] not seeing the device? How do I get this tool working?
[Captivate Android Development] zmore:
Install Adaway (open source) or Adfree. both simply download updated ad server lists every couple days, and merge them into /etc/hosts
[Captivate Android Development] diabolik711:
gapps

what is the difference between the link posted "gapps-ics-20120213-signed.zip" and gapps7.1?

Thanks
[Captivate Android Development] zmore:
Fwiw, I have very good headphones too, but the audio is only horrible when plugged into the noisy computer USB port. Charge via the a/c adapter instead and the interference is gone.
[Captivate Android Development] andeke07:
Seem to be having issues with SMS Crashing... When I converted to ICS I imported my texts by SMS Backup/Restore... it was a lot of them, and had some trouble at first but finally got it working.

Now, more recently (having been with ICS since build 8 or 9), I am noticing the Messaging app crashing. When I am typing a text it will sometimes kick me to the main messages screen, and sometimes the home screen. I loose everything I have typed and it will sometimes happen 3 or 4 times before it finally lets me type a whole message.

When it does it, I notice all my messages in the list have no name associated to them, just the phone number from the conversation. It will then go down the list and repopulate the names, but once it gets to the bottom of the list it will kick me out again and do it all over.

I thought I just had too many messages to I turned the cap on to 300 messages and deleted a whole bunch of old threads. That hasn't seemed to have helped though (I did a search for this issue and someone said it had something to do with restoring the text messages from a backup and that the cap wouldn't work, but it seems to be working, as all my threads are capped at 300 now)

Anyone have any thoughts? It started on 16 and it still happening on 17.
[Captivate Android Development] Joecascio2000:
Settings/apps/all/messaging/

Clear data

Clear cache

-might delete all messages, not sure but always solves my problems.

PS: Message hoarding is bad. Anything over a hundred per thread lags down my phone.
[Captivate Android Development] pizz0wn3d:
I think the problem is that persistent notifications aren't kept at the top when new notifications come in like they were in previous versions. =/

Herp derp Captivate XDA Premium.
[Captivate Android Development] grkmaster:
Definitely worth a try if someone has a chance or if i flash this one of these days, i will try it
[Captivate Android Development] wildnux:
does not work with Tibu restore :(
[Captivate Android Development] airtower:
I know this isn't exactly a feature request thread, but is it at all possible to change the way changing the input method is handled? There was nothing wrong with the way it was handled in GB and prior (longpress text field). Raising a notification is ridiculous, and if you lock the screen while in a text field the notification stays there on the lockscreen leading you to think you have some sort of notification.

I know it's a google thing, but the notification bar is for notifications. Not context settings. Honestly I'd rather have to back out all the way to system settings to change the input method.
[Captivate Android Development] Lhernandez0105:
Just tried. It will install but it isn't working.
[Captivate Android Development] kant5t1km3:
+1 10 char
[Captivate Android Development] dman1x:
They probably wont change something like that. Seems irrelevant in the grand scheme of things.
[Captivate Android Development] wildnux:
+1 from me as well.

Also is there anyway to mount the internal storage as mass storage device opposed to MTP device? it says here that it is supported by android 4.0 ICS just not in galaxy nexus.
[Captivate Android Development] joedon3:
Check your notification when you're connected. tap "Connected as a media device" and select 'Camera (PTP)'
[Captivate Android Development] wildnux:
Thank you, it works but its awfully slow. (I am using opensuse 11.4 linux)
[Captivate Android Development] nbell13:
when i plug it into my windows 7 desktop, i can just click the "usb storage" option that appears under "sgh-i897" in windows explorer and drag and drop all the crap i want into my internal sd card just like if it was in mass storage mode. I don't get what the big deal is.
[Captivate Android Development] airtower:
same here on ubuntu
[Captivate Android Development] space_eyes:
flashed version 3, however can't seem to download anything from market, gives and error message content cannot be downloaded.
[Captivate Android Development] nbell13:
Mine too, dev said it should be fixed with next build. In the meantime, just use the online market for purchases.
[Captivate Android Development] joedon3:
MTP works with Windows. I'm not running Linux, so I can't say for sure, but apparently there are problems with it or it doesn't work correctly. Therefore "camera mode" or mass storage device may be required to transfer files.
[Captivate Android Development] nbell13:
Ahhhhh, wasn't aware of the Linux issues
[Captivate Android Development] speedy_11:
The op says that u can use mass storage in recovery mode. Its kinda of a pain going in to recovery to use it, but hey it beats not having mass storage at all. Coming from dual booting windows Ubuntu user.
[Captivate Android Development] wildnux:
I had the same problem, and it was because I forgot to wipe cache and data partition

I wiped cache and data partition next time and it worked. I had to accept that market notification around 10 times to get it working though.
[Captivate Android Development] nbell13:
*anxiously awaiting build 4* :D
[Captivate Android Development] joedon3:
+1

10 char
[Captivate Android Development] RootTheMachine:
Uh guilty... 14000+ messages held and counting

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] andeke07:
Thanks, will try it out, hopefully it works.
[Captivate Android Development] belyle:
What purpose does saving text messages serve? I guess I view texts differently than most people. I think they are disposable, and actually clear mine out about once a week (if I haven't flashed a ROM anyway), just because I don't like the clutter.

On a thread-related note: I've been running this for a couple of weeks now, and also tested out ICSSGS rom. This rom is MUCH MUCH smoother and more responsive! I was glad that I had a nandroid backup of my THS rom after a couple of days of ICSSGS so I could return to the best. Battery life on B17 is better now that I bought a new battery for my phone.
[Captivate Android Development] MrSwiss876:
has anyone experienced any freezing right after u click the "call" button to make a call? .....i notice the phone froze at the dial screen and when i clicked the button to make the call it got stuck there but the call still went through ....and had to pull the battery to get it off.
[Captivate Android Development] RootTheMachine:
I don't know, there's something about being able to reread important conversations. I'm sure it's taking a huge toll on my performance though.
[Captivate Android Development] drktigger:
You could get an sms backup app. Then read old texts as xml files. I use an app called sms backup & restore. When my texts start piling up I just backup and delete all the texts.
[Captivate Android Development] voldomart13:
Is anyone else having problems sending text messages? Sometimes i have to reboot before I'm able to send messages.
[Captivate Android Development] RaptorOne3:
MMS works just fine for me...

My touch buttons not lighting up when I tap the screen is starting to bother me though... lol

Does anyones touch buttons light up when you tap on the screen?

They're supposed to light up when you tap the screen. But mine do not. They only light up when I tap the buttons themselves.

Obviously not a huge problem but is defintely a bug...
[Captivate Android Development] J0ESK0:
Are you sure this is a "bug"? ICS is only officially running on the Galaxy Nexus which doesn't even have touch buttons. And I'm pretty sure the on-screen buttons don't light up when you touch anywhere on the screen. That would be annoying. As would having the touch buttons on the Captivate light up anytime you touch the screen. Sorry it bothers you.. but I prefer it the way it is, that they only light up when touched.. not when you touch anywhere on the screen. ;)
[Captivate Android Development] RootTheMachine:
Pretty sure it's not a bug. You can set them to stay on though

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] RaptorOne3:
You do make a good point. Perhaps it isn't a "bug", so to speak... Instead, I suppose it's a device related feature that hasn't been implemented. I just thought I'd bring it to attention because so far, no one has said anything about it and it was a standard feature on FroYo and Gingerbread. The buttons have always lit up when you touched the screen. It was an important feature if you were using your device in the dark.

I'm aware that you can set the timer on the buttons to "never" and they will stay on while the screen is on. Which is what I have it set to currently. However, what is the point of the other settings if they don't light up when you touch the screen?

If you have the button light timer set to, lets say, 5seconds and you're using your device at night, in the dark, how will you see the buttons before you tap them if they don't light up when you touch the screen? Ya might accidentally tap the wrong button. Which can be much more annoying than the buttons lighting up when you tap the screen, in my opinion.

For now, mine will stay on all the time. But I'm beginning to not like it. I miss the original functionality of the buttons... Sometimes I like them to shut off but I need to see the buttons before I tap them in the dark...
[Captivate Android Development] nkrick:
I think it is accurate to call this a missing feature. I don't think it was ever implemented in CyanogenMod 7 either (though I don't remember for certain). If it is a feature you want, you can either wait and hope, or if you have some coding skills, you can contribute to the project to add this as a devices specific feature. Ideally, it would be nice to add an additional option in the same area where you can set the buttons to stay lit.

Personally, I actually like having the buttons stay off, I find that having them turn on every time I touch the screen is annoying and I know where the buttons are without being able to see them.

edit: It is also possible that another CM9 device already has this feature implemented. If so, most of the code can probably be reused along with hardware/device specific code needed to get it working on the SGS devices.
[Captivate Android Development] Jesterdtm:
Yeah, pretty sure this is not a bug. I recall they implemented something that removed the soft keys from the bottom of the visible touch area, and redirected those functions to the touch keys at the bottom of the captivate. So it was probably designed this way. I also like it this way, it would annoy the crap out of me if every time i touched the screen those lit up.

Which reminds me, how do you open the recently opened programs menu? (on regular soft key ICS it's the third icon.
[Captivate Android Development] MrSwiss876:
what happened to the option to set a timer when taking pics?
[Captivate Android Development] shane87:
Hold home to open recent apps.
[Captivate Android Development] drktigger:
Is there anyone having trouble with the calendar? When I try to add a new event it just gets stuck on "loading..."
[Captivate Android Development] vcallas:
Am not on this exact ROM but have no issues with calendar.

sent from my SGH-I876 on FusionCM9
[Captivate Android Development] cjpp78:
goo

Has anyone got the new google voice to integrate with android 4.0's call log? just downloaded new version but voice mail doesn't show up in call log.
[Captivate Android Development] Jesterdtm:
It's a setting in the Google Voice APP, you may need to update your app.

"Google has released an update to the Google Voice app for Android that gives it greater integration with the native dialer in Android 4.0 Ice Cream Sandwich. The new integration lets Google Voice users access their Google Voice messages right from within the call log of the native dialer app. Users can control the playback speed of voicemails to speed up or slow down the message as they listen to it. The new feature can be activated by toggling the "Voicemail display" option in the settings section of the updated Google Voice app. The update is available for free from the Google Play Store now, though the new integration is only available to Android 4.0 devices."

http://www.mobileburn.com/19028/news/google-voice-gets-tighter-integration-with-android-40-ics

(this probably should be in the other thread)
[Captivate Android Development] p1gnone:
Same. It lead me to look at the sync on the account: All syncs work except calendar and browser[not used anyway].. find a solution drktigger?
[Captivate Android Development] billyjed:
Try running the gapps fixer. It will wipe your synced data and you will have to enter your account induration again. That had worked for me in the past. Before you do that, try charting the app data in settings.
[Captivate Android Development] drktigger:
I've tried using the gapps fixer but it didn't work for me. Is your calendar working alright now?
[Captivate Android Development] nok6100:
From the OP:

A reset from android settings cleared up the problem of calendar sync for my device, the bad part is you will have to set up your phone again.
[Captivate Android Development] bazald:
Mine stopped working eventually, after updating from some revision before the gapps fixer was posted through revision 16 or 17. I ended up wiping data + cache and reflashing the ROM + Google apps. I would assume wiping the data was the important part.

Titanium Backup is your friend.

Edit: As regards not using Titanium Backup, it's good advice to avoid using it for anything that nests itself deeply in your system like Google Voice. Additionally, if you set the restore mode in settings to the basic version supported by free Titanium Backup, the installations are less likely to screw things up.
[Captivate Android Development] Fallon:
I ended up doing a full wipe & upgrade from 16 to 17 to get my calendar synch to work. Didn't put that much effort into trying to fix it though. Just ran the Gapps fixer a few times.
[Captivate Android Development] drktigger:
Running gapps fixer multiple times did the trick. Thanks.
[Captivate Android Development] Xp3r7:
Im on Build 17 right now but didnt start noticing it untill Build 16 but I get a reboot during about every call Im in whether I made it or someone else called me.

I did a search on this thread and saw it was a common problem and someone put up a test kernal that was suppose to fix it.

When I clicked the link on post 5750, it was dead.

Anyone have this kernal or know another solution to fix this cause its really freaking annoying!

Im on the stock kernal btw.
[Captivate Android Development] drktigger:
You could try using the icy glitch kernel. It's the only kernel that I know of that works with this rom. I think it helped with my occasional random shutdown problems.
[Captivate Android Development] voldomart13:
I can agree with this. Ive always installed glitch right after i update and Ive never had a phone call reboot problem.
[Captivate Android Development] Joecascio2000:
And I'm stock and have never had a phone call reboot. I was just on the phone for 20 mins last night too. Also never had a charge death too. I have had a sleep death twice since being on ics (not a big deal though).
[Captivate Android Development] drktigger:
I guess I should make it clear I didn't have any phone call reboots when I was on the kernel that comes with teamhacksung ics. Just random shutdowns while I was using it or sometimes when the screen was off.

I haven't had problems since I got the glitch kernel except a few times while overclocking to 1200.
[Captivate Android Development] thangphysk48:
How to make light control appear on notification bar like aokp rom?
[Captivate Android Development] Xp3r7:
Thanks for the help all.

I installed Glitched last night but I didnt make/receive any calls afterwards/today.
[Captivate Android Development] Silencer96:
Install "ReLoaded" 1.7a and you'll have an adjustable brightness and sound slider.

Hope this helps!
[Captivate Android Development] thangphysk48:
I'm using forum runner, if can,pls give me that "reloaded".
[Captivate Android Development] scash:
I don't know how I found it but I'm pretty sure this is it

http://xdaforums.com/showthread.php?t=1531222
[Captivate Android Development] thangphysk48:
It's worked. Very well, many thanks.
[Captivate Android Development] argus1185:
I give up on ICS Roms for now (went back to GB MIUI). This sleep death is killing me. Ive tried everything i can do. If anyone knows a way that they had used to get rid of the sleep death please share. =)
[Captivate Android Development] daskanda:
Did you try increasing you voltages a bit or setting the minimum frequency to 200?
[Captivate Android Development] color0:
What is "everything"? Starting from a KK4 base (includes AT&T bootloaders) and a clean install (wipe data -> install CM9), I have not had any sleep death problems since the very early builds of CM9.

I'm assuming you've reinstalled the ROM, kernel, bootloader, etc. several times. Did you check the md5? Once in a while I get a corrupted download and if you don't know that it's corrupted, can really ruin your day as you try to troubleshoot stuff that you really don't deserve to trudge through.

When you install, of course, keep a baseline stock setup: don't stray from stock CPU speeds, governors, IO governors, and voltages, and if you have Glitch avoid using Deep Idle.

Sleep death, as far as I understand at least, is correlated with too low of a voltage in the system at the sleep frequency (aka 100MHz). The stock settings of the CM9 kernel are tested and should be stable for everyone, though, so if your phone still dies when screen off with everything stock, we can diagnose the behavior frequency step by frequency step... use NSTools or similar to lock the frequency at 1000MHz, then screen off, wait, screen on. Death, no death? Try a couple more times.

Repeat this experiment at 800MHz, 400MHz, 200MHz... all phones should still be fine with 200MHz locked, just super slow. If yours is NOT OK, then you have a problem there and we can try adding a little voltage. I would attempt to raise the CPU voltage ("ARM Voltage") to 1050mV, matching the 400MHz setting, and try again. IMO, you definitely should not experience sleep death at 200MHz at 950mV ARM/1100mV Int. voltages. I would not know what to think if you do.

Repeat the test at 100MHz: it should now be really slow, yes, but it still should not die. If it does, try raising the internal voltage ("Int Voltage") to 1100mV, matching the setting for the other frequency steps. If it still dies on sleep, try raising "ARM Voltage" to 1050mV, matching the 400mHz setting. If it still dies on sleep now, you can probably rule out low voltage being the cause and consider other factors such as bad/wrong bootloader, bad kernel, etc... and bad download is a big cause of those.
[Captivate Android Development] argus1185:
i tried to lock the frequency at 1000 mhz using NSTools, did the same with the other frequencies till 200mhz. Ill tried adding a little voltage. and ill try the 200mhz at 950mV ARM/1100mV int. voltages.

When u say locking at 100mhz. Is that the min. and max. freq. set to 100mhz? I'll downloading all the stuff again, in case of the bad download possibilities.

I will also try using a KK4 bootloader. I had initially tried coming from JF6 and also GB bootloaders. Havent tried KK4 yet.

Thanks Color0. Ill give it a shot.
[Captivate Android Development] drktigger:
I've had a problem with the camera for a while that's been bugging me a bit. When I flash to stock eclair there are no problems with the camera, but when I flash this the camera would open sometimes and sometimes open with a black preview screen.

I just tried factory resetting and that didn't work. I have flashed eclair several times and came back to this, so I'm not sure what I can do.
[Captivate Android Development] belyle:
I'm not sure if it's a known bug or not (haven't bothered to check the logs), but I have the same issue. You can work around it by restarting the camera app, or by switching to video and back to camera within the app. I've also found that the camera is still working, you just don't get a viewfinder.
[Captivate Android Development] argus1185:
i tried everything that you said. And still no luck

=(...any other ideas?
[Captivate Android Development] Radukk:
http://download.cyanogenmod.com/?device=captivatemtd

New builds available here NVM it was CM7 :yaoming:

and gapps http://goo-inside.me/gapps/
[Captivate Android Development] imb951:
edit: nevermind........

I'll just update my gapps... :(
[Captivate Android Development] dpaik:
you need gingerbread bootloaders when using ICS roms...maybe your flashing eclair bootloaders everytime you go back to stock and not flashing GB bootloaders afterwards
[Captivate Android Development] Kaik541:
You do not need any specific bootloaders to run cm7 out cm9

Sent from my Galaxy Nexus
[Captivate Android Development] nok6100:
Ditto, I am running i9000 bootloaders and no issues with the camera on build 17.
[Captivate Android Development] drktigger:
I was having problems with a i9000 gb bootloader and changed to a i897 gb bootloader and the camera seems to be having fewer problems. I'm still getting only a black preview screen sometimes.
[Captivate Android Development] WindRunnerXC:
Since March 6, my phone has refused to sync anything Google-related. Been running build 16 since well before then, and no significant changes occurred to my system at that point in time. Since then, I've been able to force it to manually sync only twice (on the 10th and 16th), with various versions of gapps from 7 and 13 Feb, combined with the fixer sometimes in between.

Today I flash Build 17 - quite a few small improvements, definitely worth the bump, and flash gapps for 15 Feb (didn't realize how quickly they were being pushed). Sync worked again - at least initially. I get emails pushed, and everything that was initially set up on the phone was listed as 'synced at xx:xx' - but that was the extent of the syncing. Have since tried to set up my Google Music, and that refuses to sync. Also tried to send emails from phone, and the emails just hung in the outbox until I deleted them, at which point they actually sent!

This evening, trying my last efforts to mess with this from a gapps-only perspective, I pushed up to the 17 March version of gapps, but no changes from earlier.

Anyone have any advice as to which version of gapps works the best/is the most stable here? I think it was really a bit foolish to start point people at ROM Manager for updates. (I have not once been able to get gapps to load from there, FYI, this is all via the direct goo links.) I'd like to get a straight answer here because I feel I'll be doing a full reset in the near future and would like to pick a 'good egg' from the start, if possible...