yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] pvr:
Please add this to OP. It's amazing how much only this phrase from atinm summarize the whole purpose of CM/CMSGS team and WHY it is so important that they exist.

Also, on a sidenote (lol) I've been using 0421 build and I've definetely seen improvement on battery on normal usage on my phone. Instead of the usual <50% at the end of the day I'm now at around 60~65% and the GPU driver is definetely better as well.

I think someone else commented on this but I did get slowdowns on Angry Birds with ads (I disable adblock just to test GPU) but not anymore.

I've been very impressed and happy with CM7 on SGS thanks to all your efforts (I am able to use my phone on my language as well). I try to read the IRC logs now and then just to check what's being worked on and what to expect for the next builds - you all have been doing a great job.
[Captivate Android Development] Johnston212:
I have to agree. I keep getting more impressed with this ROM. I think what may have happened with my previous issues with HD video was that MixZing removed support from the free version. Regardless, the latest version has allowed me to run Tron LEGACy 720p quite nicely with MoboPlayer.

I did want to throw out that I have started getting an increased number of force closes lately (mainly system and market), but ever since the last nightly Swiftkey no longer works. I have reinstalled and still nothing. Every other keyboard I have on here is working fine, but Swiftkey won't run at all.

Lastly, I wanted to mention my experience with JK4 so far. Battery does seem better (but I tried it in conjunction with last NIGHTLY, so can't say what is the cause), data speed is far better (broke the 5Mbps marker on it), but GPS is again finicky. I would almost say that JK4 is worse than KB1 on GPS.

Thanks again for everything TeamHackSung.
[Captivate Android Development] xThaNaturalx:
The only thing that was keeping me from sticking to this ROM was the wifi error I was getting anytime I tried to use it. For anyone that's still having this problem, all you have to do is flash a new radio and it will fix it right away. I was using the JL3 and switched back to JK4.
[Captivate Android Development] D-FUSE:
I am on wifi right now and I am using everything packed into the rom guess I got lucky
[Captivate Android Development] atinm:
Really? Flashing radio fixed your wifi? That's very cool . . . and sort of impossible as the radio has nothing to do with wifi. If your wifi driver is hosed, nothing works right - but that usually means that you're mixing/matching kernels and ROMs. But just as modem/radio has nothing to do with GPS (except maybe for when it is using the cell towers to get location), radio has nothing to do with wifi.

Think of it this way, radio == thing that connects to the cell towers.
[Captivate Android Development] jbinc:
Agreed!

Sent from my samsung captivate

Rom - Cognition 4.3
[Captivate Android Development] xThaNaturalx:
I didn't think it would affect anything either, but it did. I hadn't mixed and matched any kernels with it, still the stock kernel that I flashed when starting. But I flashed the JK4 kernel just for kicks, and it fixed the wifi immediately. Then when I flashed the Trident #30 kernel, it still worked. And to test it, I went back to the stock radio and the wifi didn't work again.
[Captivate Android Development] jpcdeux:
Can I flash this over Continuum?
[Captivate Android Development] mnjm9b:
you can flash this over any rom...

...

...

...

just follow the directions.

:)
[Captivate Android Development] mcord11758:
No concerns with the gb boot loaders?
[Captivate Android Development] nybmx:
Swiftkey is running fine for me on the latest nightly and TheEscapists kernel. I have never had a problem with it on any CM build yet so it may be something else with your setup.
[Captivate Android Development] glos7777:
I have tried to wifi speed test now.. between my captivate cm7 2.3.3 and vodafone 945.. :S

first :

captivate : DL:1552 kbps UL:502 kbps

Vodafone : DL:2127 kbps UL:623 kbps

second :

captivate : DL:1566 kbps UL:341 kbps

Vodafone : DL:2106 kbps UL:486 kbps

Third :

captivate : DL:1001 kbps UL:321 kbps

Vodafone : DL:2048kbps UL:473 kbps
[Captivate Android Development] atinm:
Oh, definitely concerns with the bootloader. We are trying not to force people to upgrade bootloaders until we actually have bootloaders specifically for the device in question because bootloader screw ups mean that instead of a nice phone, you have a nice stone.
[Captivate Android Development] mcord11758:
That its what I thought just wanted to clarify for the original poster
[Captivate Android Development] nightwanderer:
Just finished flashing this ROM and I have a couple problems. I can't seem to boot into recovery anymore, I have tired multiple ways including from ROM manager and selecting reboot to recovery, the 3 button method, and I have also tried adb reboot recovery.

What happens is that the phone will restart and it shows the I splash screen but then the display gets all distorted and then reboots into CM7, have I missed in a step in the flashing?

Any help would be great thanks!
[Captivate Android Development] sixstringsg:
The issue list specifically says three button is the only thing that works.

Sent from my CM7 powered captivate
[Captivate Android Development] mcord11758:
What did you flash from
[Captivate Android Development] nightwanderer:
I flashed from Stock Rogers ROM with root and CWM installed
[Captivate Android Development] tiuk:
Try holding down both volume buttons end power. Keep holding while it shows the initial i896 boot screen, it'll show the kernel boot image briefly then it will reboot again because you're still holding the buttons. Once it shows the i896 screen again release the buttons, it'll go to the kernel boot image briefly then cwm will come up.
[Captivate Android Development] skyxliner:
I've been reading and watching youtube videos on how to install cyanogenmod and I'm pretty confident in installing it now but I have questions.

1) I'm confused about this bootloader issue... Is it true cyanogen doesn't upgrade to 2.3 bootloaders? I do know that odin one click will revert everything including bootloader to original but i'm just curious if cyanogen even upgrades to 2.3 bootloader in the first place?

2) I should be fine using odin3 to go back to a 2.1/2.2 rom if i decide to right?

3) what are the instructions going back to stock 2.1 with odin3?
[Captivate Android Development] Kaik541:
we don't touch bootloaders as it's really stupid to flash a bootloader for another device onto your phone.
[Captivate Android Development] zerojay:
View attachment 577639

Why I hate this forum and why I hate this thread.
[Captivate Android Development] XGX5309:
That really isn't an issue specific to this thread... but I do agree.
[Captivate Android Development] jhernand1102:
Don't let the door hit you on your way out, you will be missed...:D
[Captivate Android Development] shaolin95:
Yeah its breaking my heart!
[Captivate Android Development] bames:
Why post an equally useless response then? (not to mention creating a pointless post that adds nothing to the thread and that will likely be followed with numerous useless +1's and me too's)
[Captivate Android Development] tjsooley:
the only solution to the usless post problem is to ban all Human users forever.

Problem Solved.

:)
[Captivate Android Development] TheTodFather:
Been running this since it was first released yet want to to say thanks asop is the way to go. Between this and my Nook both running cm7 ive been really happy. Graci
[Captivate Android Development] zerojay:
If it betters the signal to noise ratio here, it's worth it even if it's noise itself.
[Captivate Android Development] :
I've been running 4/21 for a couple days now. Zero problems and great improvements. The battery life is better now than the Samsung based roms I've used. 6 hours of constant use with 68% battery. That's nothing short of amazing. Brightness high with intensive application use. Couldn't be happier.
[Captivate Android Development] bames:
if you have been here or any forum long enough you would know that rarely is effective and for the most part just contributes to or multiplies the noise (similar to feeding trolls)
[Captivate Android Development] hayslett4:
Kernel updates or more?

I've been running CM7 on my Captivate after about a week of it being on XDA and have stopped updating the nightlies after the 4/2 update. The reason is that I installed Le kernel du jour! *Its yesterday somewhere.* and currently on v4.6 because I wanted to try to overclock, turn on BLN, and use the Voodoo sound and color. So far it's been excellent with the SmartA$$ governor and clocked to 1.4GHz. I tried 1.6, but it rebooted when I went to the market. Yea, still not "set to boot" in that section... way too risky right now for me.

My question is, are the CM7 nightlies kernel updates or more? Also, is there anything I need to watch out for before flashing a nightly using a different kernel? It's CM7 based (not I9000). I'm not going to worry too much about it if it's only kernel updates since Escapist is uploading updates at a pretty good rate. Any suggestion would be great! Thanks!
[Captivate Android Development] Kaik541:
there are tons of upstream bugfixes... quite frankly, it's pretty dumb to not update... all you'll have to do is reinstall your custom kernel

p.s. should add that you could just read the changelog and see things that have changed (and why it's of benefit to update)... basically not updating on this ROM is kind of like only eating at mcdonald's because you don't know what other burgers taste like.
[Captivate Android Development] zerojay:
Yep, this is my first day on the internet. I don't care about what you have to say. It served its purpose and got the chuckle out of the target audience I was going for.
[Captivate Android Development] zelendel:
Stay on topic please.
[Captivate Android Development] theMaDHakkeR:
Hi guys,

I just got back on the CM7 bandwagon. I noticed something and was wondering if anyone else noticed this. The backlights on the capacitive buttons are always on when the screen is on. This is not a huge issue but can get annoying when watching a movie or show. There was a discussion about this several months back when i was last running CM7 and the general consensus was that the backlights are either on or off for certain people.

I just flashed TheEscapist kernel and noticed something odd. I used Blinky instead of Neldars BLN app (because i aint paying to have flashing lights) and now my capacitive buttons only light up when i need them to. So when i unlock the phone the backlights are off, and they stay off until you use them, at which point they behave as usual and stay on again. Locking the screen will turn them off again until you actually click one of the capacitive buttons.

For this to work i enabled BLN with Blinky and sent myself 1 txt with the screen locked. After the lights flash and you unlock the screen, just lock it again and your backlights will stay off until you need them.

I dont know if this is something people knew but i didnt see this mentioned and thought maybe someone would find it useful.

Thanks.

EDIT: Also found this in the CM7 Forums, http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=87
[Captivate Android Development] zacharias.maladroit:
awesome stats ! :cool:

what kernel, modem and network are you using ?

what apps ?

thanks !
[Captivate Android Development] tjsooley:
ALL this is a cm7 modem for the i988ZNKP1 modem

it is 850 and on I9000 roms with the reorient kernel the battery life sucks, But I am using it on CM7 because it gave me the best GPS I have ever seen.

and I figured I would post the update.zip I made.

The issues with this modem under a non cm7 rom was

Bad battery life

Edge would not work (you would go from 3g data to GPRS data)

These may not be issues with CM7.

I will post back but so far battery life is pretty good.
[Captivate Android Development] comdei:
Just wondering, is galaxy s CM7 on rom manager(the updates)?
[Captivate Android Development] TheEscapist:
No, we aren't mainline supported yet.
[Captivate Android Development] comdei:
Just checking haven't been on in a while. With the i9000 source does mainline become more a reality?( just for driver source and such)
[Captivate Android Development] TheEscapist:
I'm pretty sure its more stuff like aosp doesn't support dual sdcards, so they have to get that merged into mainline, and all the changes Samsung made to the build system (like using a zimage, rather than a boot.img).
[Captivate Android Development] comdei:
Oh wow, couldn't that mean we will never be mainline?
[Captivate Android Development] TheEscapist:
Ignore this, Atinm knows what he's talking about.
[Captivate Android Development] atinm:
No worries on that score. We are down to one tiny merge left before we're fully merged on all common things. After that it will be Galaxys family specific stuff that is easier to do. We also have Koush monitoring us closely so he can make sure our merges are done quickly to mainline and we don't get lost in the large number of merge requests that come in for all the devices.

Our biggest challenge has never been going to mainline. It has and remains things like ease of installation, stability, battery, full functionality. We are slowly going thru the Samsung code drop, but it is only useful for the kernel stuff because Samsung does not release Android ROM stuff and a lot of their stuff uses user mode closed source binaries for things like sensors etc. No need for it, but that's what they do, When we do get it all working, it would bode well for Captivate when Samsung stops upgrading it when they put out the next new generation and people still have Captivates that are fully functional. But they'll be hoping to get new customers, and given what we know about them, I am certain a lot of us won't be repeat customers . . .
[Captivate Android Development] nkrick:
Darned Apache license... Somehow I think it was never Google's plan that manufacturers would put driver code in user space. I understand allowing manufacturers to protect code for UI customizations with the Apache license, but most drivers belong in the GPL kernel. If not, then Google should require that driver binaries be released that will work without other manufacturer frameworks/customizations required.
[Captivate Android Development] TheEscapist:
It sometimes happens, but we usually are only a day or two behind in updating. Hell, we sometimes out publish them, though we technically shouldn't.
[Captivate Android Development] Lollipop_Lawlipop:
In a way, the kernel you get from the CM7 package is 'custom'. There's no need to hold back on experimenting with others (what's the point of XDA-Dev?!) as long as the developers are relatively in sync with the releases.

Also, every time you flash a CM7 update package, the 'original' kernel is flashed. That means there's no way you can get a kernel that's wrong for the release unless you deliberately flash another kernel.
[Captivate Android Development] vizographic:
Atinm, I've been on cm7 since the start and the experiance has been pleasure. I flashed from 15 to 21 this morning, and expected to find the usual incremental improvements; was I ever wrong. I was blown away. The gpu performance is stunning. Persistant 3d rendering artifacts during benchmark testing (quadrant) have disappeared ; battery life seems more robust. Stability has been spot on, rock solid. I'd like to post a bug, but damn if I can find a real one yet. cm7 a daily driver? Hell it's formula 1. Sorry about the thread pollution, but the developer teams work on this is overwhelming - if ya'll can't handle an occasional outburst of effusive praise - then ya'll only have yourselves to blame. Guys phenomenal work.

AOSP, opensource all the way!
[Captivate Android Development] Johnston212:
Quite true, Platypus' kernel is usually updated a day or two before or after the official release. I am looking forward to getting closer to mainstream.

This ROM finally resolved one little quirk that I had been thinking about for some time. For the first time, I was able to connect my phone to my car stereo port and not have to go in and tweak my bluetooth settings. Now if I could only figure out how to get the Navigation voice to go back through the audio port and interrupt my music like it used to
[Captivate Android Development] excision:
My google apps simply won't install. I've tried downloading them when i first log in with my account but it force closes. I've tried putting the Google apps from the cyanogen site and from mobiletechvideos but niether works. each time i flash it says installing google apps for a second then just stops and says its completed. Can someone please help? i managed to get all my old apps on via titanium back up but i really need gmail and the market. Thanks
[Captivate Android Development] phaedrusiszen:
I had something similar happen on my most recent install, on a Captivate I got AT&T to replace because of the GPS, new one is perfect, btw. I ended up doing a factory reset, which I believe removed some of the Google Apps, but left the market and cured my FC problems. I just grabbed the missing items from the market.
[Captivate Android Development] pvr:
Out of curiosity, when the SGS stuff gets merged into mainline it's my understanding that you (CMSGS team) will no longer be providing updated packages and will leave this to the automated nightly process of CM itself.

It is also my understanding that you (CMSGS) will continue to focus on the development of the code/maintenace as well in order to make the devices run as perfect as possible.

Am I correct?
[Captivate Android Development] atinm:
Details still to be worked out but essentially yes. But don't hold your breath on merge to mainline - it is still a moving target. Right now there is no way to install an update via ROM Manager for example, so getting the latest update from ROM Manager won't do anything for you. But you will notice that ROM Manager now knows a "real" CM7 Captivate now - because we use MTD devices as Samsung should always have done, and Koush has made ROM Manager detect this so that once things like reboot into recovery etc are working, ROM Manager will only download CM7 updates and clockworkmod recovery rather than the generic Samsung ROM ones. So people who always seemed to worry about "Why doesn't the cyanogenmod team work on SGS", that's the answer - we're the SGS cyagenonmod team.
[Captivate Android Development] atinm:
Updating to another kernel is fine - the changes aren't that much between the kernels that we put out as part of the updates and the custom kernels. The custom kernels mostly add things that we don't want to add to the "stock" kernel for various reasons (OC/UV, voodoo sound/color, bln, etc), so there is no harm in trying those. The only time things will get weird is when one of the custom kernel starts using the Samsung code drop, because then they'll be installing a lot more than just kernel drivers if they expect things to work but flashing back to CM7 update will put you back to "stock" CM7 and so there is no harm in trying those either.

We only ask that if you are running into weird reboots etc, and are using a custom kernel, then you go complain (or post bugs :-) ) on the developer's thread. If you think it is a CM7 ROM level problem rather than a kernel problem, to first flash to stock CM7 and test there first before putting up a bug report in the issue list.
[Captivate Android Development] gabby131:
Hmmm....everything about graphics are smoother in the latest nightly.....sweet!!!
[Captivate Android Development] excision:
I've manages to use the hdpi files from cm6 and all but the market would install. I'm gonna try reflashing it tonight.
[Captivate Android Development] MrR0ng:
Did I brick it?

I am following the instructions on

http://forum.cyanogenmod.com/topic/...7-for-samsung-galaxy-s-phones-build-20110303/

I have got to step 8 (go into recovery), but I can't get into recovery at all, I can't get into download either now! I am stuck on the bootloader screen that shows "Galaxy S, cyanogenmod".

I have tried many different button combinations

Volume up, Volume down, and power

Volume up and power

Volume down and power

Remove SIM, SD, Battery, Volume up and down, plug into computer, reinsert battery (for download)

None of these combinations work, I always end up back on the bootloader screen.

I have tried to use the adb tools, but I can't get the phone to be recognized since I installed the cm7-captivate-initial-kernel.tar. I have tried installing the Google USB Driver pack through the SDK (screenshot), but I am still showing the device as a Nexus S without the proper drivers in device manager (screenshot).

This is my father in law's phone. I have rooted dozens of phones for people, and this is the first time I can't get into anything. I tried to search the forums, but I can't see anyone with this problem. Please help!
[Captivate Android Development] atinm:
How about:

Phone off (all the way off), and unplugged from USB.

Hold volume up and down and keep holding them.

Plug in USB while doing above.

Should get you into Download mode. If so, you can let go of the volume keys now and flash to stock via Odin etc. If not, you may need a jig. Did you make sure you could get into recovery etc using the button combos before you started this process?
[Captivate Android Development] alphahere:
Use ablock to block the images.
[Captivate Android Development] MrR0ng:
@atinm, thanks for the reply. Just tried the way you mentioned (just to be sure), and I still can't get into download.
[Captivate Android Development] zerojay:
You were able to go into Recovery with the 3 buttons before you started to follow those instructions? It's not bricked if you are able to get something to show up on your screen.
[Captivate Android Development] matt310:
Right now the only reason I am using a custom kernel is because I want the color balance slightly cooler than what comes stock with CM7. I know there aren't necessarily any plans to add color temperature control into an AOSP rom, but do you personally know of another way to achieve slightly cooler-than-stock-CM7 color temps without use of a voodoo-enabled kernel and associated apk?

-M
[Captivate Android Development] mnjm9b:
Check cm settings...

It's already there.
[Captivate Android Development] Yaantra:
Apologize if this has been answered previously... Can I flash CM7 directly over 2.3.3 roms with the 2.3.3 bootloaders? or do I need to go back to stock 2.1 and start over?

Thankx!

Sent from my un-captive Captivate
[Captivate Android Development] matt310:
Do you mean Settings->CM Settings->Interface->Render Effect?

If yes, then it's still a bit off to my eyes. I'll try to snap some pics using both kernels to show it.

M
[Captivate Android Development] jaysix79:
I don't know of this if this is been reported. Ever since I updated to 0421 my widgetsiod and fancy widget is kinda ac ting up. Its not a big deal but on my widgetsiod the battery perecent is inaccurate until i touch it and it will then update to the current level. On my fancy widget the time sometimes would stop. Seems like the widget is not being updated by the phone. I tried resetting the phone and clearing my cache didn't help
[Captivate Android Development] MrR0ng:
I have always used adb to get into recovery and download.
[Captivate Android Development] atinm:
You need a way to flash 3 button fix now because adb will not work as the bootloader uses Samsung closed source drivers to pass the necessary parameters and an open ROM like CM7 does not include them.

It is necessary to make sure you know how to get back to stock before flashing anything, not just CM7, and this was considered so basic that it got overlooked in the instructions. Getting back to stock implies making sure that you can get back to download/recovery mode when you happen to flash a bad kernel, or just plain make a mistake as is most likely the case this time. Adb reboot/recovery/download require kernel help, which is no use when the kernel you are flashing just got flashed badly due to user error, or just plain doesn't have support for the Samsung closed source drivers like CM7.