yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mik101:
If he's having the phone do nothing but boot into CWM then you're probably wrong.

I've been through this with my girlfriends i9000m twice now. After a flash it occasionally will do nothing but reboot into CWM over and over regardless of whether you goto "reboot phone" or "reboot recovery". Reflashing nothing but the bootloader fixes it in her case and ta-da the phone boots normally again. As an added bonus on her i9000m, using the i9000 bootloader enables her to use the three button combo to get to CWM, which doesn't work on her stock bootloader.
[Captivate Android Development] Gromlakh:
If you hit the power button and then see literally anything at all, your bootloaders are working fine. The boot process is:

- Primary bootloader -> secondary bootloader -> param.lfs -> kernel

The white AT&T splash screen pops up as soon as it gets to param.lfs, then it hands off to the kernel to finish the boot. Recovery is handled by the kernel, not the bootloaders. If your phone boots to CWM recovery, your bootloaders are fine and there is a problem later in the boot process.
[Captivate Android Development] Marko190:
which USB driver are you guys using? I am running win 7 64bit.
[Captivate Android Development] mik101:
Not using ATT BLs in either case on the i9000 or my i896 so I never see an AT&T boot screen at all. It would reboot to recovery regardless of the kernel used (default cm7, semaphore 2.7.4 and devil 0.8). Only thing I can chalk it up to on hers is weirdness with the I9000M bootloader (Bell Canada) because it did it again after a fresh 2.3.3 restore using ODIN and CWM was flashed back on it. Not quite the same as the OP but in her case that was the fix.\After flashing the boot loader I was able to restore her backup and actually boot it rather than booting in CWM over and over. *shrug* FWIW I've never had any weirdness on the Captivate (I896) whatsoever. It seems to be the gfs phone that has the issues. Hers won't overclock at all either, whereas the cappy will go all day long at 1200mhz.
[Captivate Android Development] droyd666:
Is there any way to overclock the GPU or do i need another kernel? I know the Semaphore kernel has live oc but i'm not sure what the difference is.
[Captivate Android Development] RootTheMachine:
Pretty sure the stock kernel doesn't OC the GPU or bus. You'd need live OC for that.
[Captivate Android Development] Primus76:
Lately I've been having trouble with BT pairings. My phone is listed as the primary in my ford and up until about 2 weeks ago was always snappy at connecting and staying connected. Now most times it times out trying to get it as Primary and goes to one of the secondary devices. When i force pair by selecting the device it does connect but after a few minutes it is disconnected. I've tried deleting the device from ford sync and then re-discovery but that doesn't seem to stick either.

If i recall properly BT isn't part of the modem so reflashing that won't help correct? Is that kernel related?
[Captivate Android Development] pawitp:
I've closed the bug tracker because I've found that people are more collaborative when bugs are reported on threads, helping solve each other's problem and pitching in their opinions. I forgot to update the Captivate's OP, it's updated now.
[Captivate Android Development] uhm:
Hello pawitp,

Thanks for the wonderful work you've been doing.

I have a request to make. Will you consider providing an option of using the Nexus S framebuffer or the framebuffer used with CM7? For some phones, the screen becomes heavily tinted with a color like Blue, Yellow etc with the Nexus S framebuffer used in CM9 and CM10. Or if you can fix the problem with the the Nexus S framebuffer, that would be highly appreciated.

Thanks a lot.
[Captivate Android Development] pawitp:
If anyone would provide a patch to fix the problem with the Nexus S frame buffer, I will be happy to merge it, but lacking access to a phone with such a problem, I cannot fix it myself. And the last time I tried remote debugging, it didn't go too well.
[Captivate Android Development] mik101:
Seems to me if it was that easy one of the kernel devs would have done it by now. If you want someone to blame, blame samsung for not upgrading the phone past gingerbread and giving the devs the kernel source required. Sorry for your bad luck, but unless you or someone else want to provide pawitp with an affected device to test, it's likely not going to happen. This has been requested multiple times previously by others too, to no avail. Personally I have had 4 Galaxy S1 in my hands (i896, i897, i9000, i9000m) and none of them experienced the frame buffer problem on ICS or JB.

Edit: Sorry pawitp, I replied without noticing you had already replied to this on the following page.
[Captivate Android Development] uhm:
Thanks for your quick reply. I am more than willing to try and test any patches you or others might develop. I can provide any logcats or whatever is necessary for you. But I understand this might not be the best way and also the best use of your time.But how about the following option:

Since the framebuffer used in CM7 works fine, I suggested if it could be used with CM10/CM9 kernel also as an option or a separate version. If that's something you can consider providing in your kernel then that would be great. Hope this is not an unreasonable request. If it is then I'm sorry!

I still appreciate all your work that you've been doing. Thank you very much.

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------

I don't like/want to blame anybody. The question doesn't even arise. I would rather thank and appreciate devs for doing such wonderful work.
[Captivate Android Development] mx828:
Does anyone else still have the white blurry line going across near the top of the notification pull down menu? Is there a chance this can be fixed? I'm thinking that it might have something to do with the framework or system theme because if I switch themes it goes away.
[Captivate Android Development] Primus76:
I think I'm on to something about my BT issue. My phone connects fine but if I'm connected to wifi at the same time, when my wifi disconnects so does my BT to whatever device its on.

Should I try different kernel? Currently on stock CM10 and stock kernel.

Thx

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] droyd666:
How do i get the screen to instantly turn on when i press the power button? I notice there's a slight delay although sometimes it turns on instantly but i dont know what causes it.
[Captivate Android Development] rupalazzi:
Hello everyone. A couple of days back I saw on G+ that the i9000 got cm10.1 so I was wondering if there is any chance of captivate getting it also?
[Captivate Android Development] RootTheMachine:
Look in the dev section please...
[Captivate Android Development] sinizter:
Seems to be pure AOSP but exciting nevertheless. :victory:
[Captivate Android Development] Katze Pavilion:
Is it necessary to wipe cache and dalvik cache before install new build?
[Captivate Android Development] rupalazzi:
I thought this was it. could you point me in that direction?

Edit: You can flame on me, read like 5 times and didn't see the new thread. Sorry.
[Captivate Android Development] sinizter:
It will likely prevent a number of FCs. Doesn't really affect any of your data/preferences regardless, so I would do it.

We don't yet have CM 10.1; I think he was referring to the AOSP 4.2 that pawtip posted earlier. DerTeufel1980 did say that he was going to get a test version of 4.2 Helly out today though.
[Captivate Android Development] Katze Pavilion:
Sometimes, automatic brightness stop working, I found it because screen brightness keeps in high level despite I'm using phone in low light condition.

One more about performance, phone becomes lag quickly after a short time using (daily jobs: sms, phone, play market, facebook... no gaming). Look like hardware limit can not respond to requirement of JB.
[Captivate Android Development] mik101:
I use semaphore 2.6.1sc and have none of the issues you mentioned. Autobrightness always works with that kernel (which is based on the cm10 kernel). You may want to keep checking your running apps to see what is causing you to get laggy, or do a full wipe and start again. My girlfriend has had issues with her weather app hanging and using 2/3 of the battery, for example. When the weather app would hang, the phone would get extremely laggy. Once I cleared the app data for her weather app, it was fine. Every day people bring me phones that have "hardware that is too slow" and in most cases it's a software issue, or the user doing something that they shouldn't be (such as running automatic task killers).
[Captivate Android Development] Primus76:
Hey, can I quickly ask you here why sc vs c for semaphore? Going to try it out since my BT issue is frustrating me to no avail. I even master reset my ford sync and still keeps disconnecting and its very random. Just flashed 2.6.1c using odin and saw you were using sc. Thought there may be a reason.

Sad but semaphore didn't help :confused:
[Captivate Android Development] Katze Pavilion:
I don't think it's software issue in my case. I wipe all before flash, install very selective apps, never use task killer or something like that. Just a few background running services: Google services, DSP manager, Facebook, Keyboard, sometimes Dropbox, just them, I check it very frequently, CPU governor is set to "ondemand", CPU clock runs from 200Mhz to 1000Mhz, free RAM is usually more than 100MB. So I'm confused why the phone becomes lag while I'm not running any heavy process.
[Captivate Android Development] mik101:
Honestly that's a better response than I get from 99% of people. It sounds like you're doing basically everything you can. I use 120mhz-1200mhz (120% live oc with semaphore) with the conservative governor and deep idle enabled, but most galaxys/captivates won't be stable with my settings. I'm just very lucky with my i896. My girlfriends i9000 is also difficult to get stable despite being just another version of the Aries hardware. Hmmm I wish I had more suggestions. What are you using for an IO scheduler in the performance settings? I've been using CFQ. I'm not sure if that one is available in the default CM10 kernel.

You may be able to increase the responsiveness a little by tweaking how quickly it throttles up/down, or using the "smooth ui" tunable in semaphore which will jump the clock up to the highest speed upon a touch event, but obviously this will slightly hurt battery life depending on your usage patterns.

@Primus76:

I use the SC version for the little extra ram it gives me. Generally it breaks the 720p video recording, but there are modified media libraries in the i9000 semaphore thread that can be flashed to allow the 720p video recording to still work with the larger memory configuration. [If you check 'bigmem' in the semaphore settings, the 720p camera will still break, but 480p will continue to work, and it leaves me with 403mb of RAM for the system.]

Without the library patches the SC version breaks 720p video even without the bigmem setting enabled. If I remember correctly the regular version also breaks 720p with bigmem enabled.

It's just what I've found works best for my usage patterns. If I want 720p video I can uncheck bigmem and reboot and it'll work. When I don't need it, then I have the most memory available that I can. The two versions are essentially the same other than that. For those that just want everything to work without having to play with it, the normal version is probably still the way to go.

The gap has narrowed between the CM10 and semaphore kernel though since overclocking, autobrightness, io scheduler changes etc have been merged into CM10.

Hope that helps.
[Captivate Android Development] Katze Pavilion:
At first, I want to say thank for your enthusiastic response. Your're right, based on my demand, I use my phone very basic and I would like to keep it basic. I've checked the IO which you mentioned, it's CFQ by default in CM10 stock kernel. I also watch activities of CPU clock ("ondemand" governor) and found that it's works as same as which you've described about "smooth UI": CPU clock jumps to max clock as soon as every touch on sceen. Eh... I think it's no need and/or nothing more to setup. :D

So, it's alright. pawitp has done the best. Keep almost three years old phone running newest os version, it's can not be better. About technical side, two CPUs made from a same wafer, one can OC well but the other one not, it's normal. I think it's acceptable. :)
[Captivate Android Development] Primus76:
Tried Sem and was still having my BT in the ford disconnect horribly. Tried the logging program built in and guess I just wasn't recording the log properly. Of course I just put the latest CM10 nightly on and my kernel is back to stock so I think I will try to get logging going on there properly but not sure who to submit the log to when I have an issue? For example this morning between 8:54am and 9:15am, my phone disconnected at 8:57, 9:05 and 9:08. Each time I hit the phone button on Sync and it reconnected properly. Going to try to figure out how to enable logging in CM10 so when I head home I can collect what is needed to see if there is anything fishy. To be honest this worked fine up until about 1-2 weeks ago. Always been a stable and fast connection as soon as I started the truck. So I'm down to the 3 factors:

Updated kernel in one of the nightlies

Something in CM10 changed impacting BT connections

Phone BT is starting to have issues (physical)

Ford SYNC BT is having issues.

With the latest nightly if it happens again tonight I have a few test scenarios to try. Try my wife's stock S2 on SYNC to see if it stays happy, try my work S2X that has CM10 as well with SYNC, try my Cappy with CM10 and stock kernel with my Blueant T1 to see if it stays connected.

Just want this damn thing to work again.

EDIT: Yup I have no idea how to get logs to write in CM10 with stock kernel using alogrec. Can't do this connected to a computer using adb since I will be in the truck so if anyone has any way to capture debug logs/logcat for a 20 minute recording period strictly using the phone, I'd be happy to learn a new trick.
[Captivate Android Development] opn6:
CyanogenMod 10 from android 2.2

I'm running Cognition 4.5.3 rom , firmware 2.2 . Do i need to flash a stock GB before flashing CyanogenMod 10? I'm little worried about me having the right bootloaders. thanks.
[Captivate Android Development] Primus76:
Just an update. I seem to be the only one with the issue and I think it is my BT/wifi chip.

My s2x with cm10 works without issue on Ford sync. The only way I can get my cappy to stay connected is by using Tasker to deactivate my wifi when my BT connects OR I found If I turn off the media portion of the BT connection pair and leave it as phone only it will stay connected with wifi on. I think with wifi and phone it was disconnecting me when the blue tooth audio connected for music as well.

I'll need to run some longer tests to see if it stays stable like that. Hate to think it's the phone at this point especially with the n4 sold out.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] Squeaner:
I just checked and the Nexus 4 is available for purchase.
[Captivate Android Development] Gromlakh:
If you're coming from froyo and you've never flashed the GB bootloaders, then yes, I believe you do need to flash them. There are several packages in the sticky at the top of this thread that have some maner of stock GB, bootloaders, and a CWM kernel all in one. I'd advise using one of those, since it's fastest. You don't even need to do anything after you flash one of those to get ready, just reboot after flashing straight to recovery and flash CM.
[Captivate Android Development] Primus76:
Sweet. I'll let Mrs Claus know :p

Edit: :( not in Canuckland it isn't.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] Katze Pavilion:
Anybody see that CM10 stable build runs much smooth than recent newer nightly builds?
[Captivate Android Development] mik101:
Mine benchmarks better on the newer builds and subjectively doesn't feel any different, so I'm going to say no. Are you testing on clean installs of each or are you restoring a backup of one of them and comparing to that?
[Captivate Android Development] Katze Pavilion:
I just use a few selective app, data is stored on cloud, no data need to backup (ex: evernote, dropbox, instagram...). After every build, apps which is installed is exactly the same with previous. So I usually wipe all before flash, never restore from backup. I've more than one time reverted from newer nightly builds back to stable, so I think my feeling is believable. :D
[Captivate Android Development] Ajfink:
I'm actually going to say the more recent nightlies are subjectively a touch snappier.
[Captivate Android Development] FireRaider:
If it helps any I can verify that my Ford Sync and Captivate had issues with BT being dropped if I didn't turn off the wifi before leaving my house. It did it way back before CM10.

It took me a while to figure out but it would disconnect my phone as soon as I got far enough away from my wifi. I got around the annoyance by setting the wifi to shut off when I docked my phone in the car dock.

I don't use my Cappy much anymore but I do watch this thread as I try to keep it updated.
[Captivate Android Development] Primus76:
Thanks for the confirmation. What is weird is that this worked fine up until a month ago. I do t have a dock but by disabling the media/music option under the blue tooth settings has made it stable. As soon as I put it back on I can't keep it connected. Will live without that option.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] laughingT:
on the screen brightness lagging or not responding, I found tweaking the hysteresis settings improved the reponse.

Sent from my SGH-I897
[Captivate Android Development] Katze Pavilion:
To me, new widgets never appear in widgets drawer after install new apps. I have to restart to see them.
[Captivate Android Development] laughingT:
I'm guessing you mean application icons rather than widgets.

Check your settings in Google Play. You can enable/disable automatically placing an icon on the screen.

or do you mean the app drawer? i've noticed that sometimes i have to reselect sort alphabetically and then they appear, without restart.

Sent from my SGH-I897
[Captivate Android Development] Katze Pavilion:
No no, in apps drawer we have 2 separate sections, one for app icons, the other for widgets. In my case, for example, after I install Beautiful Widgets app, the widgets do not appear in widgets section, I have to reboot phone then I can see them here.
[Captivate Android Development] Klitoni:
So its worth installing the stable one or new nightlies
[Captivate Android Development] Primus76:
Is there a change log for our kernel that comes with cm10 for cappy?

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] mik101:
http://review.cyanogenmod.org/#/q/s...oid_kernel_samsung_aries+branch:jellybean,n,z

There may be a specific branch on there for the S5PC110 humming bird soc too, but you get the idea. At this point there are very few commits happening as most of the work is going into mr1staging for the next release.
[Captivate Android Development] laughingT:
Katze,

of course you are correct for Trebuchet launcher in CM.

I am running CM10 with GO launcher ex and forgot about the diff.

I tried with Trebuchet and got the same prob you did.

Sent from my SGH-I897
[Captivate Android Development] sjorge3442:
Been having some issues with CM9 lately, and think I am going to take the jump into CM10 this afternoon. Trying out the newest nightly unless anyone suggests that I should do something different.
[Captivate Android Development] laughingT:
I am on 4.1.2 , the latest stable. You might get a baseline with stable before jumping to nightly.

Sent from my SGH-I897
[Captivate Android Development] james.arroyo:
I'm not sure what thread to post this in, in CM9, CM10, or SlimBean.

I have installed (CM9, CM10, and SlimBean), wiped and rewiped, used Odin to start from stock, I've verified my IMEI and all is good. I am getting the error below. First the signal, completely loses, then it starts to come back then it comes back and then does it again every 3-4mins and i complete lose signal for about 2-3 mins. No text, no calls, no data.

I also went to http://xdaforums.com/showthread.php?t=1870460 and installed the KG3 modem. Im all out of options and im not sure what else i can do. I cant
[Captivate Android Development] laughingT:
James,

The screen image that you posted says you are still on 4.0, not 4.1 - that is you are running ics, not jelly bean.

you might have better luck flashing back to stock gb kk4, then flashing cm10. if you want to flash slimbean, and discuss bugs, there are threads for that.

as far as modem goes, I've never changed mine, afaik. stock froyo to stock gb w corn 7 to cm 10.

Sent from my SGH-I897
[Captivate Android Development] tmroy:
The water's fine, jump on in - just have everything backed up - the partitioning changes.
[Captivate Android Development] james.arroyo:
Right, I've tried CM9, CM10, and SlimBean which are both 4.0 and 4.1 and i still get the network issues. I've flash back to stock twice and reinstall the ROMs and no matter what i do i get those errors. First I lose signal completely, then starts to come back with no data support, then comes back with data support then about 3-4 mins later it does it again.
[Captivate Android Development] AriaOfSorrow:
Is anyone else able to purchase apps by using bill to carrier? I'm on the stable release and the option is not there at all. Last time I used it was about May or so. I have someone on the same plan as me with the same exact phone that's able to bill to carrier on the same app I'm looking to purchase. The only real difference there is they're on stock.
[Captivate Android Development] laughingT:
update:

the carrier billing glitch in Google play (with Google Wallet) is not CM10 related.

I just finished phone calls with at&t support and also with Google support. they are both getting many complaints from owners of many different android phone models/makes about the missing carrier billing via Google wallet.

AT&T rep said Google didn't want to do carrier billing option. He said that my att account has never had any block on billing via google play.

The Google rep said that they recognize that have a bug in play/wallet and said they are working on a fix. Sprint users are also having the problem.

Here's the kicker (as told to me by google rep)

:

Once google fixes it, you will need to set up your phone number again in google wallet, then call your carrier to reactivate the authorization to bill.

I asked Google rep how would I know when it was resolved. She said, you can call us back and check status.

grrrrrr#&#**&##*&#**&& !!!!!!

I am supposed to do what?

They couldn't give me an ETA for fix, nor would they notify me of the fix nor could they point to a web page to check for updates.

maybe the AT&T rep was right in this case? Google really wants your CC info, I guess.

end of update.

I am deleting the remainder of old message re buildprop. it is irrelevant.

Sent from my SGH-I897
[Captivate Android Development] RootTheMachine:
Have you tried putting those in the build.prop? It might not work though.
[Captivate Android Development] laughingT:
Edit: Please see update in my previous post.

Moderator: you can delete this post, thanks

Sent from my SGH-I897
[Captivate Android Development] AriaOfSorrow:
Yeah, I would appreciate it if anyone has a fix. Or even just some kind of temporary option for the time being. The app I want to get is on sale until the 16th, and it would be nice if I could purchase it before then.
[Captivate Android Development] Katze Pavilion:
Sound toggle "vibrate & ring" mode on notification drawer do not link with sound setting. Toggle "vibrate & ring" mode only take effect when you've already ticked on "vibrate when ringing" in sound setting. And if you tick it, phone will vibrate & ring event when toggle is in "ringing only".