yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] viny2cool:
same here....launcher is being weird on me and it takes me to the search bar automatically..idk why
[Captivate Android Development] kangi26:
I just reflashed to Stock JF6, Master cleared, installed CM7 Nightly, installed Build 11, gapps 7(didnt need the gapps fixer) and changed my modem to JK4. The stock launcher is FC'ing when I remove a widget from the home screen. I installed ADW EX, and I am getting an occasional "Wait for ADW to respond" or "Close". Rebooted and am not seeing it quite as often
[Captivate Android Development] kapnkool:
Here's a first for this thread...

I did a search before asking this question. I installed the Amazon App Store and when I try to login it tells me that my info is wrong. But I know it to be right since I successfully installed the amazon web app and logged in. As a veteran of captivate rom installs, this is the first time this has happened to me. Anyone have a clue as to what is going on here?
[Captivate Android Development] zuN!:
I'm having the same issues as well with the stock launcher and the updated Trebuchet from wherever that link is. I'm on GoLauncher and no FC's so it definitely is a stock launcher issue. Trebuchet will get their eventually since it is undergoing development while each new build is rolled out.
[Captivate Android Development] Mauijpm:
I've had this happen to me before and I had to Google it to find out what to do. When you flash a ROM, Amazon registers it as a new digital device on the app store. They have a limit of 20 different devices or so. So, if you are a flashaholic like me, you hit the device limit and can't log in.

Just log into your Amazon account and go to the "Your Account" section. Towards the bottom of the screen is Digital Content. In there is your apps and devices. Go in there and delete old "Devices" which are just old flashes.

After that is done, try logging on again and you should have no issues.
[Captivate Android Development] kapnkool:
I am floored. It worked.

Mauijpm, you are a genius. Thank you...thank you...thank you. Your fix worked beautifully.
[Captivate Android Development] mbc663:
Hit the thanks button for the guy, can't hurt :)
[Captivate Android Development] Pechkin000:
It did for me.
[Captivate Android Development] billmouthclinton:
Corporate (exchange) account doesn't work... any one else having issues?
[Captivate Android Development] kataishin:
if I had a penny for all the bugs in this rom... this is cm7 nightly mods all over again

:sigh: alright here we go..

messaging lags to the point to where I want to throw my phone

the browser lags all day every day. wifi struggles. the focus function crashes my browser when scrolling pages. music crashes. Gmail crashes. gallery crashes. system crashes. screen flickers upon reboot. screen drags during boot animation. YOU CANNOT CHANGE YOUR RINGTONE WITHOUT YOUR WHOLE SYSTEM DOMINO EFFECT CRASHING. setting the wall paper crashes. during the first boot while gapps is being propagated, there is a mysterious crash there as well. I expect these things to get looked into and I'm trying to help tie up your loose ends.

Anyone else wanna throw in your build bugs right this second so that way there is the possibility of a not so crash happy future build? its not gonna fix itself.

PS. how could I forget... it was tastefully plastered all over my dock.
[Captivate Android Development] kangi26:
I just came from Stock JF6 and Master Cleared, and have only had 1 FC; it was the launcher and as far as the lag is concerned, not much to speak of. I have a little bit when I open messenger. I can change ring tones till my hearts content. So I might first take a look at what your flash procedure was
[Captivate Android Development] alkiter:
That's weird, I don't have any of these problems. There's a bug alright but it's not in the rom.
[Captivate Android Development] BL4zD:
Well, I can point out one bug, at least, and that's when I use the sound/mute toggle nothing changes. I have to manually turn the volume down to off/vibrate.
[Captivate Android Development] angryscientist:
To the guy you quoted, exchange works fine. Follow the instructions (wipe before install) then use gapps fixer. Email worked straight away, calendar worked after gapps fix.

As for the rest of this ocular diarrhea, you're an idiot. The problem is you.
[Captivate Android Development] jswclw:
A new issuer last night for me. The phone died after a full charge. Had to reboot in the morning. First time for such a thing. The difference was, no pending alarms last night. Not sure if that was the cause, but it was a difference.

Also interesting that the battery was draining while waiting for am estimate 6 hours to be rebooted. Then the battery recovered half way. Weird.
[Captivate Android Development] ryandelman:
Anyone else reporting non-working GPS with this build? I've reflashed numerous times to no avail.

Thanks,

Ryan
[Captivate Android Development] pawitp:
Read the first post. It's long, but please read it, it's worth it.
[Captivate Android Development] olo567:
Did you flash the GPS fix from the first post?

My GPS works okay after that post, but every app looking for location complains when GPS is off; it seems my location by Wifi/mobile network doesn't work, regardless of the checkbox.
[Captivate Android Development] ryandelman:
just now saw the tiny little "fix" download link in OP.

Legit mistake on my part for missing that little needle in the proverbial haystack.

Thanks for pointing out!

Ryan
[Captivate Android Development] pawitp:
Test kernel

http://faramir.eriador.org/pawitp/captivate_kernel_test_build11.zip

Comment on

Color

Dock audio

Charging death

Any new bug

(To revert, just reflash the build)
[Captivate Android Development] dabels1961:
flashed the kernal and now when I go into recovery I do not get the flashing yellow screens. that was the only issue that I was able to see so that is all I can report on. even though with subjective opinion, the color does look better when running as well..
[Captivate Android Development] jswclw:
So far, so good. Unfortunately I cannot ready dock until tonight, and charging death until Friday night/Saturday morning.

Thanks for the update though. I was really missing dock audio.
[Captivate Android Development] mbonus:
1 - I still get yellow squiggly screen when rebooting into recovery. Does not happen on shut down, or normal reboot

2 - unknown

3 - unknown
[Captivate Android Development] dabels1961:
after this post I thought I should try it again and I did get the yellow screens this time when booting into recovery, strange.
[Captivate Android Development] J0ESK0:
*Color

-Looks good, seems to have a bit of a crisper/deeper color. However, when rebooting the phone to recovery.. the screen still goes yellow and flickers/distorts like crazy.

*Lock screen

-Still having issue sometimes where lock screen is unresponsive and have to wake, unwake screen to fix.

Also, am having problems with CWM Recovery since updating to Build 11. Whenever I try to reboot after flashing anything or not, rebooting from the recovery menu brings me to the Green Android stating, "Power Reset or Unknown Upload Mode". Happens every single time. I have to either bull the battery to reboot or 3 button combo.
[Captivate Android Development] singlebeam:
*new bugs resolved for me with test kernel:

1. Yellow bars flashing on reboot

2. Lockscreen response issues

3. Yellow tint on auto brightness

Thanks devs.

Sent from teamhacksung SGH-i897
[Captivate Android Development] M3drvr:
OK my install procedure was this:

Flash to KF1 stock with bootloaders

Flash CM7 nightly

Flash this rom

My biggest gripe is things are slow opening, and the browser is really slow for me! Takes close to 1 minute for my bookmarked page of captivate android dev page to load up. As well once I zoom in, for the phone go clear up all the words takes 5 seconds average. Sometimes faster sometimes slower.

Other than that I don't have any FC or any glitches. I find when I get into low service area the calendar will start FC like crazy though. Ever 5 seconds. But if I turn sync off for it there is no FC. But that only happens in low cell service areas otherwise it sync fine.
[Captivate Android Development] dabels1961:
yellow when going into recovery

well I really hate when I can not get things to be consistent, I re flashed the latest kernal and have gone into recovery mode like 10 times now. 3 times in a row right after loading the new kernal and then after trying a bunch of different things (i.e. changing to the auto brightness, going into apps, rebooting from different places) I have not seen the yellow flashing screen again. I have no clue what causes the issue. is there a way to capture logs or anything when it happens? I am running 11 with gapps 6 gps fix and the new kernal and that is it.
[Captivate Android Development] devi59:
Yay, fixed!

Well I think my original post about the problem got moderated but anyway. The problem was not this ROM NOR was it Glitch. I was using Voodoo Display Filter from the market and it seems like that was causing "my unable to hit the install problem". I'm not on glitch now and the same thing was happening but I couldn't figure it out until I took the filter off (which using it saves TONS of battery because it lowers the "brightness" to WAY down) and once I disabled it I was able to hit the install button again. I have no idea why it causes the issue but at least now I know (and I am able to share the "bug fix") with everyone else.
[Captivate Android Development] space_eyes:
I got the yellow flashy today, first time, was rebooting to recovery from in the middle of the "box.com" app, (was getting my 50 free gigs, and worked btw). I was like omg, like so much yellow, so much yellow, then my phone was like "I'ma gonna reboot anyways" and I was like omg its rebooting, then my phone was like "OMG, I'm ready now" and that was it.
[Captivate Android Development] bakacary:
The OS itself is stable so far - only issue I experience is Trebuchet would crash itself every now and then. Most apparent when I have more than 3 apps open (FB/Browser/GMail). Would say Trebuchet has to close and drops me to the phone app?!

Sorry if this has already been mentioned previously.
[Captivate Android Development] Mauijpm:
I noticed that when I do a normal reboot, I no longer have the yellow flash. I only get it when I reboot into recovery now.
[Captivate Android Development] kangi26:
1. On rebooting to recovery, I get the yellow flashes at the top and bottom of the screen. I don't get it on a normal reboot though. Otherwise the color in normal use seems to be good to me

2. N/A for me, don't have a dock

3. Also, N/A for me, wasn't getting it on the stock kernel. I'll check tomorrow when I get up after charging overnight

4. Lock screen responds well for me, no issues with that. I'll test thru the day today and get back tomorrow if I find any issues
[Captivate Android Development] speedy_11:
With the test kernel

-Color is a bit yellowish (my opinion), still getting yellow distortion in boot to recovery

- Still having the lock screen misbehaves sometimes still

- Ics background gradient seems to have gotten brighter (black to grey going down, seen in settings/other place). The gradient would blend into the black of the status bar. But know its a dark grey and abruptly black of the status bar. -Maybe its just me or it was wrong before or now? It's just an observation
[Captivate Android Development] Mauijpm:
Something I started noticing and I'm not sure if this has been mentioned previously, but if you are using an app like gallery or quickpic or zedge where you are scrolling through a bunch of images, if you go too quickly it will force close. This has happened quite a few times to me recently.

Edit: I believe that it is more related to scrolling than images loading as a text page on Dolphin Browser just force closed on me for that very reason.
[Captivate Android Development] cole26:
After 3 or 4 flashes coming from stock Rogers GB, I've got everything up and running and, wow, this seems to be better than factory GB. Thank you devs. I would like to mention bugs I'm experiencing, some of which have already been mentioned.

-Yellow flashing on reboot to recovery only (not normal reboot).

lockscreen freezing, which goes away with a couple power button presses.

-trebuchet crashing when viewing widgets.

-low space error after restoring from TiBu. When I get the low space error, my google account stops syncing. Remove some apps, low space message disappears and account starts syncing again. I currently have only 1/3 of the apps I used to have installed.

-2d hardware acceleration causes Tiny Tower to FC, but runs great when unchecked. (probably not an issue of this rom, but thought it was worth mentioning).

-200Mhz minimum CPU clock.

-Touch to focus on stock camera app. Not sure if this is a bug, or something not available on this rom.

Running Build 11. Will try the test kernel to see if that clears anything up.
[Captivate Android Development] Hasher76:
everything in there has been addressed already in previous posts, there are fixes out there and some work arounds you can search for.
[Captivate Android Development] singlebeam:
I'm confirming yellow flash on a reboot into recovery only now.

Also, my lockscreen has started acting up again....unresponsive until I press the power button a couple times.
[Captivate Android Development] TheSoaresan:
I can confirm this happens to me too
[Captivate Android Development] kusabikuri:
A lot of people are getting the unresponsive touch screen upon wake up. you actually don't have to press the power button just wait a few seconds and it'll become responsive again. I think someone said it has something to do with the wifi going to standby.
[Captivate Android Development] jswclw:
Ok...charged and didn't sure this time...good.

However, music stopped working. Crashes immediately upon attempting to start it. New kernel its all I have changed.
[Captivate Android Development] jswclw:
Just thought to clear data, now music is back in business. Sorry for the false alarm.
[Captivate Android Development] Aztecbandit:
Flashed back to JF6, flashed a kernel, flashed build 11 through CWM, bootlooping and i tried it twice, cant use Rom Manager because I don't have premium... help? :(

EDIT:Now even Flashing CM7 bootloops, never did before
[Captivate Android Development] Mauijpm:
Do you have CM7 on your sd card? I believe people have had success flashing that first and then build 11. Read back through the thread though to make sure.
[Captivate Android Development] Saint Wacko:
What makes you think you need Premium to flash through ROM manager? And try flashing CM7 before you flash ICS.
[Captivate Android Development] loserskater:
Since nobody has reported it yet, I would like to say that dock audio is working with this kernel.
[Captivate Android Development] jswclw:
Sweet! Glad to hear it.
[Captivate Android Development] Aztecbandit:
I could've sworn you need ROM Manager Premium to install from SD card.. and i cant even flashing CM7 bootloops now
[Captivate Android Development] whyareyou:
Have you tried flashing twice in the same recovery session? It sometimes takes two flashes to get it.
[Captivate Android Development] Mauijpm:
I haven't noticed you mention it, so that is why I am asking, but are you doing a Wipe as instructed in the OP?

WIPE (wipe data/factory reset + wipe cache partition)
[Captivate Android Development] Saint Wacko:
No, you don't. I ended up having to flash through Rom Manager to get my ICS flash to take, and I don't have Premium.
[Captivate Android Development] Aztecbandit:
Hey it worked, thanks never had to flash CM7 twice

Yeah, wiped those each time.

Oh, I see what my problem was.. got it to work thanks.
[Captivate Android Development] M3drvr:
I posted a few pages back that included my install method, but does anyone else have really slow browsing speed?
[Captivate Android Development] kangi26:
Mine works fine. My first thought for you is to change modems

OR

Go to settings/apps/Browser and clear cache
[Captivate Android Development] Mauijpm:
I just had a complete reboot when trying to get from the Gmail app back to the home screen. I pressed the home key once and got no response. I pressed it again and my phone completely rebooted.

I am on Build 11 with the most recent kernel.

Edit: This is the first time this has happened.
[Captivate Android Development] M3drvr:
I'm using same modem as before that always managed to deliver the best speeds and reception., and even on wifi its slow! Even once the page is fully loaded up if I zoom in its terribly slow. Usually at least 5 seconds to focus all the words.

I tried clearing cache and still slow.

I'll swap modems now to others that seemed to work good before and report back.

Update:

Tried a couple other modems, still slow. Any more suggestions to try?
[Captivate Android Development] BlkSquad:
I'm not sure if anyone else had said anything, but my home button does nothing now. It will light up and vibrate but doesn't effect what is on the screen. I have to use the back button to get back to the home screen.
[Captivate Android Development] BlkSquad:
Also, no notification sounds. Phone calls show up in the call log but don't do anything otherwise, no ring no show on screen. Build 11, GApps fixer and GPS fix used.
[Captivate Android Development] timpac:
Okay, I've loved these so far, still on build 6 because it worked so well. My power button has stopped working now, at least for locking and unlocking the screen. I can still do a hard reset.

I put the build 11 on the sd card, but I can't wipe or flash because the power button also doesn't work in clockwork mod. I'm sure I can Odin or whatnot, but I'd prefer not to go that extreme if there is an easier fix. Anyone else having this problem? Help?

I also can't get android market to install apps for a workaround. It's stuck downloading. Unrelated I assume, but it adds to the frustration.
[Captivate Android Development] Voltage Spike:
I was having an identical issue with my router (D-Link DIR-615). I switched the WPA cipher type from "TKIP and AES" to "AES" (when I noticed the Android phone was using TKIP) and now everything works great.

This was after a lot of attempts to hunt down the wpa_supplicant code. (As far as I can tell, it is using the version from Cyanogen. The official source appears to be 0.5.11 whereas the onecosmic build, which I am running, is 0.8.x).

So it looks like we need to prefer AES to TKIP and possibly fix this particular issue. I think I know what to do, but without the source...
[Captivate Android Development] speedy_11:
You can use the soft keys to navigate in recovery
[Captivate Android Development] kangi26:
The last thing I would try would be another browser, and if that doesn't fix it, I'd be backing up my stuff, flashing back to stock/master clearing and starting over again
[Captivate Android Development] flashman2002:
I haven't seen this mentioned with the test kernel but my haptic is broken. It is very faint, almost nonexistent. Reboot fixed it but it was almost instant from when I flashed the kernel that it stopped. Obviously this must be an isolated incident.
[Captivate Android Development] SkitchBeatz:
I'm having an issue where the home screen Widgets fail to update based on OS and application information.

I'm on a fresh flash of build 11 with gapps 6/gapps fixer
[Captivate Android Development] dutch55:
So it looks like we need to prefer AES to TKIP and possibly fix this particular issue. I think I know what to do, but without the source...[/QUOTE]

AES is also preferred because it is more secure and should be configured in WiFi routers and access points. The I.E.E.E. 802.11n standard which applies to newer WiFi devices limits maximum speeds to 54Mbps if AES is not configured. In other words, if the WiFi router is configured for Open, WPA, or TKIP, the speeds are deliberately limited.
[Captivate Android Development] double RL:
Does anyone have working wireless tether? I did a full wipe and fresh install yesterday hoping to fix it and everything is smooth except wireless tether still will not work.

Sorry if I missed something about this somewhere.
[Captivate Android Development] billmouthclinton:
I can't add a Facebook account nor corporate exchange account.... Are these known issues, any work around?

Other than that I have no complaints, nice ROM.... Beta Swype is nice working nicely too
[Captivate Android Development] caleb4992:
Colors are better but I still get charging death. Still blinks yellow when going to recovery.
[Captivate Android Development] alkiter:
Works for me.

---------- Post added at 05:04 PM ---------- Previous post was at 04:48 PM ----------

Color - Good

Dock audio - Audio plays but Music gives message "Unfortunately Music has stopped", but music still plays. If press OK, music stops. Pandora works fine.

Charging death - none

Still have blinking yellow screen on reboot to recovery.

Does not charge while in dock. No charging indicator, and battery monitor shows discharge. If plug usb connector directly into phone instead of into dock, charges fine.
[Captivate Android Development] djf8:
I miss you in the vibrant section Atinm. =(
[Captivate Android Development] derek4484:
I think you are correct. I installed Build 9 over CM7.1 and it's worked extremely well for me. A few little naggy issues here and there but nothing serious at all. And this build 9 actually gets better battery life for me than CM7.1 did. I havent left build 9 because I keep reading about all the issues that 10 and 11 are having.

I was hoping that since the source code for ICS on the Nexus S had been released that the newer builds would be better, but seems like they arent.
[Captivate Android Development] Demonic240:
The Android Facebook app does not support contact sync with ICS. To get around this, download the FriendCaster app from the market. It's free, and allows contact sync.
[Captivate Android Development] b-eock:
To flash any Odin bootloaders you have to be on a stock ROM or the current ROM will not BOOT up. This is because the partition mapping.

Also you can brick your device(HARD BRICK) if you don't have a good connection.

Use these, it is easier. I897 GB BL
[Captivate Android Development] imb951:
Thanks, but this is contradicting what Sixstring and others in this thread have recently said, and I quoted in my above post. They are saying that one can flash GB bootloaders ONLY from CM7 or (presumably) CM9 Alpha (build 11)...

Not saying anyone is wrong, just looking for clarification, as well as an easy way to get on GB bootloaders without repartitioning back for an RFS based rom.
[Captivate Android Development] b-eock:
Really, THEY CAN ONLY BE FLASHED ON A FILE SYSTEM THEY WERE NOT MADE FOR!?! that makes real sense, not saying anyone is wrong, but I have never seen sixstringsg say that... and it isn't RFS partitioned, it is BML partitioned.
[Captivate Android Development] imb951:
I honestly don't know if it will work, that's why I'm asking and reading up on these threads.

I don't want to spread misinformation any more than you do but don't discredit the folks I've quoted already. Apparently the CM7 bootloader issue was fixed, but I'm not going to risk it without more responses that it does in fact work with those aforementioned GB UCKF1 bootloader ONLY packages.
[Captivate Android Development] b-eock:
I replied to your Glitch thread post, go check it out
[Captivate Android Development] yguns76:
I had facebook working on build 11.

PS. I am back to CM7 for now.