yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zmore:
So after 2 days on build12, I can say it's just about flawless, 'cept for a few things that are mostly known:

The finicky lock screen. (It also makes my kid cry! :)

I've had one random reboot (not OC'd with stock), but no sleep deaths. (sorry, no logcat)

Sometimes when taking a bunch of photos and vids you'll end up with 0-byte pics. There's enough free space, but maybe not enough free buffermem to save 'em in time?

I'm not sure if this is an ICS issue or a WeatherBug app issue (probably the latter), but in 4.0.1, WeatherBug's notification background matched the system theme (black), but in 4.0.3 builds it's light grey, and there've been no app updates inbetween.
[Captivate Android Development] cfili:
Even with jk4 I still have wireless issues :(

The router I am connected to has several devices connecting to it without any problems. Any setting I should be looking at? My router is running Tomato firmware with WPA/WPA2 tkip security if that helps.

I really like the work that is being done here and this is my only problem (which may be on my end) Anything else I should try?
[Captivate Android Development] bentonhall:
Then I guess that is why it appeared as though it wasn't working. If you use the power control widget to toggle it, the full bright is right before auto bright and it was not dimming the screen. If you toggle it through the menus after manually dimming the screen, it does brighten.

Forgive my ignorance but I am unable to find where to change the default behavior. Can you point me in the right direction?

Thanks!
[Captivate Android Development] airtower:
will report back once i get to place I can obnoxiously play ringtones. not in my office.
[Captivate Android Development] Ikonomi:
Regarding the lock screen lag/freeze, I previously observed that it SEEMED to be related to the wifi, but I just experienced the lag while not on a wireless network. However, I do have the wifi transceiver running though there are no available networks where I am.

One other bug which I have only experienced once: I woke up this morning to my phone alarm going off, but with a completely unresponsive phone or power button. The screen would not come on when I pressed the power button, and the soft keys registered presses, but didn't produce a response. The situation was the same on and off the charger. I had to pull the battery and the phone worked fine after reboot. I'll see if it happens again tomorrow morning, but I have never had it happen before so it may have been a fluke.
[Captivate Android Development] throwawayaccount9500:
Seems as if Build 12 is a huge regression from the past two builds. I'll hold out
[Captivate Android Development] vercro:
Build 12 is nearly perfect and fixes many things from previous builds... what issues are you having?
[Captivate Android Development] icebergisonfire:
I wanted to pop my cherry with my first post in this thread by saying that I've been using the rom in its various incarnations and builds and I sincerely appreciate the work that everyone is doing towards this. For this rom to be this functional in such a short amount of time is a beautiful thing. I've been able to show off my phone to various people and even those at AT&T that hadn't used ICS yet so that they could see the cool features on the OS. I've had my issues with datadata and other things like some other people, but by far and large, I look forward to every update of this rom. Thank you and keep up the good work.
[Captivate Android Development] throwawayaccount9500:
Apparently GPS doesn't work on Build 12...that's a pretty big deal for many people.
[Captivate Android Development] glassd:
Build 12 has been amazing. I have one issue though. The News & Weather app doesn't seem to be functioning correctly. It can sometime take quite a few tries for it to actually get the weather information for my city (not a big deal) but the application crashes when I try to look at the detailed weather view. This started happening in build 9 or so.
[Captivate Android Development] nimper:
Works fine for me, I got a lock in 10 seconds.

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------

How about a logcat of when it crashes? Use Catlog (available in the market) if you don't want to mess with ADB.
[Captivate Android Development] :
There's a flashable zip in the OP at the Known Issues section. That will give you the CM Settings
[Captivate Android Development] Raikia:
These seem related. This seems to probably be a bug in the build.
[Captivate Android Development] squire366:
GPS is working fine on my Cappy. In fact I just used it last night. I also use Endomondo to track my rides when I'm mountain biking and that works fine as well.
[Captivate Android Development] cfili:
Well guys, my wifi problems are definitely related to my router somehow - works absolutely fine on another access point.

Sorry to pollute the thread :) I'll try to troubleshoot on my end.
[Captivate Android Development] bentonhall:
Ah. Thank you.
[Captivate Android Development] ryandelman:
Have you tried applying the GPS fix in the OP?

This should solve your problem.

-Ryan
[Captivate Android Development] umanko:
May be this can be bug in my eyes as I can see black border of 1 px thick surrounding the display getting used for nothing .
[Captivate Android Development] glassd:
Here is log during the whole process. It is not the whole logcat file, if you want the whole thing I can make another paste.

pastebin/ygZjVfQP

It would be a link, but the admins don't trust that I'm human.
[Captivate Android Development] Mauijpm:
GPS has been amazing for me and I have one of the original Captivates with huge GPS issues. I ran this test from the middle of my living room.
[Captivate Android Development] zmore:
Post a 800x480 screenshot or it didn't happen.

Didn't happen (no border):
[Captivate Android Development] pixelens:
Thought this was for the "Notification power widget"? I flashed the zip and don't see any additional CM settings anywhere... am I missing something?
[Captivate Android Development] gangpe:
Proximity sensor issues?

I might be the only one who has this issue, but when I make a phone call, the screen stays lit until it times out. Is there anywhere we can adjust the proximity sensor settings?

BTW, I love build 12. It's got all I could ask for. If I could get my games running, that's a different story, but that's an ICS issue, not necessarily this rom.
[Captivate Android Development] nimper:
There should be an app called Cyanogenmod Settings in your app drawer.
[Captivate Android Development] Geoff-dev:
I had on the phone:

Build 11 w/GPS fix with full data wipe

No problems:

- Battery death

- Setting up exchange email

- Camera

- Video recording

Defects:

- GPS still did not work

- Calendar from Gmail or Exchange does not work

Applied Build 12 with no wipe, did not reinstall GPS fix

Fixed the GPS

Defects:

- Calendar from Gmail or Exchange does not work

- Experienced a single instance of battery death overnight (suspect bad app)

Current screenshots as I am in a building with poor cell reception:
[Captivate Android Development] modmyphone:
Issues with Audio Volume Control

Build: 12

Kernel: Stock

Issue: Can not mute ringtone/notification. I am unable to lower the volume completely using any ordinary method (Menu>Settings>Sound, or using rocker buttons, or even using the controls in the notification drop down. The notification drop down will give me a haptic saying it's getting a command, but does nothing. The rocker buttons and the sound menu just keep resetting the volume to 3.
[Captivate Android Development] slayp00n:
Can anyone confirm that calender sync is broken even with the gapps fixer?
[Captivate Android Development] glassd:
My Calendar syncs fine on build 12. I only used the fixer on the build it came out with. It has synced fine ever since.
[Captivate Android Development] modmyphone:
Calendar sync works for me, both Exchange and Google.
[Captivate Android Development] nimper:
I can't confirm this. My calendar sync works fine without the gapps fixer. Build 12, gapps 7.1.

My suggestion is to do a factory reset from recovery then reflash the latest gapps package. That worked for me back when pawitp suggested it.
[Captivate Android Development] TwinkyOfHope:
Hey guys, I was just wondering if the "Google" text in the persistent search bar on the home screen is gone in Build 12. It seems plain now. It's no big deal, I was just curious.

Whoops, I meant to click quick reply, not quote :/
[Captivate Android Development] Keland44:
i had to do a clean install in order to get calendar sync to work right for me

clear data twice and reinstall build 12 and put gapps 7.1 after got everything going had a problem restoring backups from titanum more so wifi and accounts but no big
[Captivate Android Development] pixelens:
Awesome, thanks - hadn't thought to look there!
[Captivate Android Development] gstern:
i remember reading somewhere it was removed by google in 4.0.3
[Captivate Android Development] Geoff-dev:
Applied gapps_fixer.zip and that corrected the calendar sync issues with both Gmail and Exchange.
[Captivate Android Development] angryscientist:
Anyone else having intermittent success with auto bright? Sometimes I get sane values (as seen in cmsettings level edit screen), and sometimes the values are all -1 and auto bright is obviously not working.

Not able to consistently reproduce one way or the other yet
[Captivate Android Development] Monfro:
I have too the calendar sync problem.

Gapps_ fixer didn't fix the issue.

Other than that this rom is amazing!!!

Sent from my Captivate
[Captivate Android Development] mbc663:
goto the top of the page, "search this forum" and type in "auto brightness"

its even been brought up today. stop being lazy.
[Captivate Android Development] Raikia:
What app did you do that test with?
[Captivate Android Development] mbc663:
"gps test" in the market.
[Captivate Android Development] RootTheMachine:
This is correct, I have it working and never used the fixer. Wipe and reflash will fix this for you. However, browser sync still doesn't work

Sent from my ICS i897 Captivate
[Captivate Android Development] Raikia:
With this application, my GPS looks like it works completely fine. 30 foot accuracy (while not the best, but I am inside) with 9 locked satellites. So...why does Google Maps show my inaccuracy to be about 1000 meters? Is there a way to fix this? Obviously GPS working isn't very helpful unless there is a map to go with it :p
[Captivate Android Development] Kaik541:
ask google
[Captivate Android Development] Raikia:
I was kind of hoping for a more helpful comment, like if anyone had any similar problems or experiences, and if there were any known fixes or attempted fixes. but thanks ;)

Additionally, I have figured out (at least on my captivate) that I only get the "unresponsive lock screen" if my phone is connected to Wi-Fi. It never happens if it is only on data, but if I connect it to Wi-Fi, I consistently get the unresponsive lock screen (where I have to turn the screen off and on again). Can anyone confirm this with theirs? Not a big problem for me, since I rarely use wifi (unlimited data ftw), but just trying to pinpoint the bug.
[Captivate Android Development] mcnutty:
If that ever happens again, try unlocking the phone like you would if the screen was on and showing the lock screen.

I had this happen, and the screen refused to turn on but was actually responding to input and let me unlock even though the backlight wasn't on.

Sent from my SGH-I897
[Captivate Android Development] vercro:
I've had that happen to me quite a few times. Screen doesn't turn on, but it responds to input. Seems to happen randomly, both on wifi and with it off.
[Captivate Android Development] know50:
I had the same issue and I found the fix with Google. Apparently a lot of people have had this issue and its as simple to fix as taking the back off of your phone and using your thumb to press down on the speaker hard. Sounds crazy I know but it worked for me and many others so give it a try. As far as I can tell its just a simple case of bad connection. If you've dropped it or something even mildly this can happen. I dropped mine on a carpeted floor and this happened
[Captivate Android Development] gilpdawg:
Build 12 is the first one I feel good about using as a daily driver. Bad flash maybe? When this thing gets done it will be the best Cappy ROM by far after it gets merged with CM and all that.
[Captivate Android Development] gilpdawg:
Browser sync works for me. Oddly enough, it doesn't work on my Honeycomb tablet, but that's OT.
[Captivate Android Development] TwinkyOfHope:
When you guys boot your phone up in Build 12, does the AT&T logo pop up twice before the nexus Boot animation? I also don't get the cyanogen mod splash anymore.
[Captivate Android Development] nok6100:
Is the dsp manager app suppose to be working yet in build 12? I messed around with the settings a little bit however changing the settings seem to have no effect.Thanks. :)
[Captivate Android Development] J0ESK0:
Yes this exact same thing has been happening to me before build 12. I think it was build 10 that started this trend for me.
[Captivate Android Development] theytalkalot:
Can confirm after removing volt control, still getting sleep death..One person suggested clean build..one thing I didn't do while upgrading, I did not wipe any data...should I try to reinstall and wipe all the data....is that considered a clean install? Thank you!!
[Captivate Android Development] TheSoaresan:
It works for Google music
[Captivate Android Development] nok6100:
OK thanks for that, I am using Xiialive to stream audio so I guess it won't work with that application.
[Captivate Android Development] Darth_Munkee:
Is anyone else still having the issue where the incoming call notification only plays once?

Sent from this fully armed and operational battle station running ICS.
[Captivate Android Development] Saltatrix:
Compass and GPS

After doing a clean install to build 12 i was having GPS issues. Using GPS Essentials i could identify satellites but the phone/software would not hold a lock. I flashed the GPS fix from build 11 which fixed that issue. However i noticed that the compass feature in that app was not working, no matter where i pointed the phone the heading did not change relative to the phone, North was always the top right corner of the phone. I installed GPS Test and am having the same issue. I then also installed "Compass" by catch.com and it also is having the same issue. At this point Im thinking there is an issue with the magnetometer in the phone not working with this build yet. Build 12 though was supposed to resolve compass issues. Can anyone that is having good success with the compass let me know what app you are using. For what its worth, im on an ATT Captivate.
[Captivate Android Development] pawitp:
Don't flash something meant for build 11 on build 12
[Captivate Android Development] k2ham:
Wifi icon?

Good evening all,

Today I flashed CM9, ver 12 over CM7 Kang and most things appear to be working great. One problem I'm having is that even though I turn on Wifi the icon doesn't show up. Toggling Bluetooth appears to work fine with the icon appearing as expected.

Has anyone else had this issue? Workaround?

Thanks!
[Captivate Android Development] Saltatrix:
In general i agree. In this case i did a backup in case it caused other issues and flashed it to see if made a difference. I have no idea if the parts of the os that it affects are consistent between builds or not. In this case it fixed my GPS issues and made no change to the compass.
[Captivate Android Development] whyareyou:
For those having lock screen issues try this, when the screen appears to be frozen at the lock screen, wait a few seconds, you'll see the capacitive buttons light up, after which the screen is responsive again.
[Captivate Android Development] Xp3r7:
http://wireless.amazon.com/Samsung-...INDIVIDUAL_NEW&sr=1-21-entd&qid=1325639525855

Amazon Wireless has the Cappy for a penny with a contract for those of you a few pages back looking for a deal on one.

I got mine there for the same price!

[/offtopic]

Build 12 is awesome!

Best build so far!
[Captivate Android Development] angryscientist:
Hey thanks for nothing. I took my lumps, did the search and got jack. Not sure what I would expect to find outside of the thread for this specific port, which is what I would care about.

A more useful answer would have been to tell me to look at the OP which was updated to say auto brightness does NOT work in build 12. How about that.

Try to be right if you are going to troll.
[Captivate Android Development] Mauijpm:
MBC663 isn't even close to being a troll, so don't continue down that path. If you are on this forum with any frequency, you end up answering the same questions over and over and over again. It can be thoroughly exhausting, especially when the answer you were looking for was in the OP. As a word of advice, always go there first, then read the other posts in the forum. 9.5 times out of 10 you will find your answer. If you don't, post your questions. We (the other users of the ROM) will be happy to help.
[Captivate Android Development] nok6100:
Auto brightness does work in build 12, just need to make sure its enabled.
[Captivate Android Development] pizz0wn3d:
Confirming that it is, indeed, working.

Herp derp Captivate XDA Premium.
[Captivate Android Development] modmyphone:
Trying not to sound anxious or anything, but is volume control working for everyone else? For the life if me I can't set to mute or even Max volumes.

Sent from my Cappy flavored Ice Cream Sandwich utilizing Tapatalk
[Captivate Android Development] jindorwas:
I don't know if I'm the first one here who bricked my captivate trying to flash this rom.

I was on original cm7 before and decide to try ICS; however, after I installed the zip file with cwm its kept playing this cool animation over and over after at&t logo, but it won't start.

I tried multiple ways to get into the download mode(ive been doing this since this phone came out), but it was no use.

I made a jig myself, but I can't still get to the download mode.

It just does the same thing when i'm trying to do with three way button.

after i plug my jig in, atnt log appears, and it shuts off and back to atnt and start non stoping animation over and over again.

Does anyone have any idea how to fix this brick?
[Captivate Android Development] Mauijpm:
That isn't a brick, it is a bootloop. Have you powered off then held volume up and power and after the first AT&T screen let go? That should get you into recovery.
[Captivate Android Development] jindorwas:
Yes I tried to get into recovery, but it won't work; however, I just made a jig with soldering which i didn't do it before being lazy, and now I could get into download mode.

anyway thanks for your info though.

since i got the jig to play around, now its time to flash again :p
[Captivate Android Development] olo567:
I've had the phone turn off on its own several times with Build 12. On Captivate GB bootloaders. Just to report.

Like everything else about the build!
[Captivate Android Development] oscataleptic:
did you have a microsd in during the boot? if so remove it
[Captivate Android Development] b-eock:
WTF, don't give unneeded info... -_-
[Captivate Android Development] devi59:
Isn't that the cause of a lot of Bootloops?
[Captivate Android Development] b-eock:
no, the boot loop on the first install is setting up partitions and installing new kernel. Then you have to reinstall the ROM to get it to take.
[Captivate Android Development] randomafk:
How does this compare to the other dev rc2 version based on the gs2 floating around here?
[Captivate Android Development] mcnutty:
This one is by teamhacksung, the other isn't.

Couldn't resist... I feel this one is more polished and stable, but each may have their own interpretation. Only way to know for sure is to try them both out for a couple of days each.

Sent from my SGH-I897
[Captivate Android Development] goosefraba91:
I'm trying to flash Build 12 over [DEV] ICS RC1 using the instructions on the OP, however everytime I try to flash the package in CWM, I get a long script: "assert failed: .............." - Installation aborted.

Is there any way I can fix this? The main reason I am doing this is to figure out if my speaker is faulty because it decided to stop working on me. So I am trying another ROM to see if that will fix it, or if I just need to get a replacement. Thanks.
[Captivate Android Development] devi59:
There was a thread about fixing your speaker somewhere.there is like a screw to tight or something
[Captivate Android Development] goosefraba91:
Yep I found it and now the speaker is working, however, I think I still want to switch over to this ROM. Is there a way for me to flash build 12 over RC1 without the "installation aborted" problem?
[Captivate Android Development] extreme300:
I've had the same thing happen on my phone too.

I had the same problem but fixed it by flashing a different version of CWM.
[Captivate Android Development] pawitp:
Flash a captivate ROM first, or remove the assert line in the installation script if you know how (if you don't, just flash a captivate ROM first, it's easier and cleaner that way).
[Captivate Android Development] Mauijpm:
I don't care if he posts on every forum on XDA, Rootz Wiki, etc. He provides valuable and accurate information at no cost. Flaming him for no reason is fruitless and an irritant to the rest of us.
[Captivate Android Development] Moronig:
I searched and nobody has reported the issue I'm having with gtalk (on this thread at least). Gtalk is not working for me, I'm running build 12, with the gapps 7.1, I've tried running the fixer, but that doesn't fix it. Everytime I try to start an audio call on gtalk, the app freezes. Chat works normally.

Forgot to say, otherwise this rom works perfect for me, and thanks!
[Captivate Android Development] Geoff-dev:
I'm not having any issues with GTalk in Build 11 or 12. Did you do a WIPE (wipe data/factory reset + wipe cache partition) before the install?
[Captivate Android Development] Moronig:
I did not, but I'll try that and report.
[Captivate Android Development] angryscientist:
So after all that, turns out I wasn't full of sh*t after all.

It worked for me in build 12 for a few days and now is a no go. Given the OP says its broken I don't see any reason to pursue it further though.
[Captivate Android Development] koukobin:
About "Sleep of Death"

Hello,

i am running build 12 and i noticed that for long periods, the device runs at 100mhz. I used setcpu for root users and manually increased the lowest speed to 400mhz and then back to 200mhz (as it supposed to be). From that moment, the lowest speed of the phone is 200mhz and i didn't had the "sleep of death" problem again (24 hours since the change). I also stopped having the problem with the frozen screen after waking up the device.
[Captivate Android Development] J0ESK0:
Just trying to help here.. My auto-brightness is also working on Build 12. The OP can be a bit confusing if you glance at it too quickly. However, it does not say its broken... Under Fixed Issues is "Automatic brightness not working". Meaning, that issue has been fixed in Build 12.
[Captivate Android Development] airtower:
All fixed issues are like that, but yeah it confused me at first as well
[Captivate Android Development] richsale:
Teamhacksung wallpaper doesn't seem to be in the same place (drawable-hdpi) as usual. Anybody know where it is?

By the way GREAT rom no problems so far. Been on it about 30 mins.
[Captivate Android Development] angryscientist:
Ah yeah, you are right. Well then, sounds like it is a bug then.

Does anyone know about the magical threads that evidently address this issue?

Should I just restate the original question, anyone else intermittently getting no values from the sensor?
[Captivate Android Development] modmyphone:
Auto brightness seems to be working fine for me. The only thing broken for me is volume control.