yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] atinm:
Brightness is working on both my vibrant and captivate. I can get it so dark I can barely see the screen (down at 5 at the moment). I was testing it and had auto-brightness off and was doing it manually up and down and then just turned it back on to test. I am using the new tables, but I changed the lower values down to 5 to test. But just flashed another latest, and that works too. Nothing has changed in the driver. Maybe it was a temporary upstream thing (though I doubt it, in my debugging we were sending lower values to the driver).

No need for pics. I see that the driver gets lower values, so as long as the driver works, auto-brightness will work. And it is getting lower values now and confirmed within our testers that lower values are working.
[Captivate Android Development] mnjm9b:
Funny how some of these things just seem to fix themselves...lol

This "feature" should be highlighted.

display is usually the #1 killer of battery.

Stock Samsung roms are Way too bright.

The higher brightness levels are nice when you need them

But its really awesome that we (cm7 users) can control the brightness this way.

Thanks
[Captivate Android Development] droid_does:
just wondering.....is there a stock kernal zip or tar file I could use?

platypus seems to be great without my apps....but once I restore my apps, my phoen practically slows to a crawl...cpu spy indicates its running at 1.2ghz nearly 70% of the time o.O

using the interactiveX governor right now

i'm thinking of rolling back stock (kernel) without wiping all my apps and waiting to restore them again by reinstalling cm7 and then restoring via TiBu
[Captivate Android Development] Desg90000:
Hey guys every since I installed the 5/21 nightly I can't connect to my wifi. what is the problem?

Sent from my SGH-I897
[Captivate Android Development] cpk86:
So I was on 12 all day yesterday and got an easy 24 hours out of the phone with some decent usage (~30 min call time, 25-30 min of Google Listen, ~5 min netflix, almost always on wifi).

My battery problems seem to be fixed. I did have the brightness all the way down, but it has been like that for a couple of days now.

Anybody else with terrible battery life (I was getting a max of 8 hrs from full to dead) seeing better results?
[Captivate Android Development] makelegs:
Have u tried using the on-demand governor?
[Captivate Android Development] :
I found that lock/unlock cycle restores capacitive button function.

i897 with CM7
[Captivate Android Development] mnjm9b:
Just updated to 13

I can adjust brightness down to 1

But still nothing under 20 makes any difference.

I even did a full wipe this time.

I just don't get it...

If it weren't for it working on 5-15

I would just figure that this is just the way it works. And probably wouldn't even care...lol

Maybe there is a setting I am forgetting...idk
[Captivate Android Development] APE992:
Since these are automatic nightly builds I'm correct in assuming there aren't changelogs about either?

I don't mind playing a game of Russian Roulette with my phone, but without knowing what changes for better/worse there are I'll probably stick with my current build.

But hey, free is free and CM7 is still sweet.
[Captivate Android Development] cwgannon:
The "backup existing ROM" option is your friend.
[Captivate Android Development] mnjm9b:
There is a link to changelogs in OP
[Captivate Android Development] cwgannon:
Edit: Solved; see post below mine if you're having a similar issue. Here's the FAQ with the details.

I've not been able to get my phone listed as an ADB device when plugged in with a USB cable. (ADB debugging is enabled on the phone; phone drivers are installed and work for file transfer when connected as a storage device.)

ADB does work wirelessly, though, without any issue.

Does anyone have an idea what might be causing this? Thank you.
[Captivate Android Development] ls377:
Did you install the Nexus S drivers? Not just through the SDK, you have to manually install them using the instructions in the FAQ.
[Captivate Android Development] tonyzz:
Sorry if asked before but with cm7 for captivate it uses eclair or froyo bootloader I do not have to flash my bootloader to use cm7 captivate?

Thanks for you help I have been reading and reading some 2000 posts and can't figure it out currently running continuum v4 is it possible to flash to cm7 from it or wipe back to stock then to cm7
[Captivate Android Development] Barsky:
I install the nightly 05222011 after returning my phone to factory default (2.1update1) Finding the wifi pretty much unusable. up/down/up/down.

Would trying a different modem help this?

Updated to JVO. Seems better. hopefully. And since when does cyangenmod report 100% on a fully charged battery? :-)
[Captivate Android Development] cpk86:
Yes you can flash from Continuum. Just use Rom Manager. It will wipe your data automatically so make sure you back up everything you still want.
[Captivate Android Development] mnjm9b:
Doesn't that have the gb I9000 bootloaders????

If it does I hope your advice didn't brick his phone....
[Captivate Android Development] RKight:
I had the same issue with the 5/21 nightly. My Wifi wouldn't stay connected. I rolled back to the 5/19 nightly and my problem went away. Both updates were using the TLJL3 modem.
[Captivate Android Development] Barsky:
well, JVO doesn't seem to have helped anything. Oh well, this is Cyanogenmod. When has there ever been one that wasn't broken in some way? :-)

Even back when I had a Droid Incredible and 6.0. Always something major broken...that is the only thing I have learned to count on with this rom :)
[Captivate Android Development] tonyzz:
Thanks will try later after phone charges 100% also I'm on continuum 4 so I think I am okay with froyo thanks for your help last thing I would want is a bricked phone that's why I was trying to stay away from having to flash GB bootloader
[Captivate Android Development] cwgannon:
Continuum v4 is 2.2; shouldn't be a problem.
[Captivate Android Development] cwgannon:
Have you checked the wifi settings to see whether it isn't set to turn off when the screen is off? CM by default had mine set to this, and I thought something was amiss with my wifi until I set wifi to be left on.
[Captivate Android Development] Barsky:
Absolutely. Part of my new rom installation routine is doing all those settings. From what another person said, it appears to be a known issue.

Thanks for the suggestion, all the same.

Currently, I have more than enough data plan to stay on 3g for now. At least until the next nightly comes out to try. Then I will decide whether to stay on this or slap Gb-12 or one of the other gingerbreads back on.

Of course, with the ever present CRAP battery life using cyanogenmod, I may just dump it now. sorry. don't mean to flame, but I am just very frustrated...more at myself for trying a new cyanogenmod again and not learning from the past :D
[Captivate Android Development] bird333:
I am running Cognition 2.2B6. I have a complete backup of my current rom. Can I just install CM7 from this? Also, if I want to go back can I just restore my nandroid backup and be good?

Thanks!
[Captivate Android Development] mnjm9b:
To flash, follow the directions.

They are super easy.

To flash back you need oden.
[Captivate Android Development] bird333:
So I can't just use my nandroid backup. Can you explain why I need Odin to go back? Just trying to understand here.

thanks
[Captivate Android Development] mnjm9b:
The new "simplified" method of installing cm7 includes converting partition formats. And unless someone includes a flashable file to convert it back, you need to use oden. Once you oden back to stock you can restore the backup.
[Captivate Android Development] novagator:
Since 5/16, I believe.
[Captivate Android Development] jaysix79:
have you guys tried using different modem? I used to have the same problem but changing my modem to jl4 seem to fix it.. never have a problem since then

Anyone have a way of fixing light sensor? I tried wiping cache, dalvik and wiping data.. none is working for me... on custom setting when i change the value setting with different numbers the screen stay the same... no matter what the filter is sensing the scree stay the same
[Captivate Android Development] phaedrusiszen:
Just a coincidence. The radio ROM shouldn't have anything to do WiFi
[Captivate Android Development] jaysix79:
thats what i thought too but just saying... thats the only thing that fix my problem... My phone used to connect on my network for the first 2 minutes after data wipe, cache or dalvik wipe... then it wont let me use wifi to go online but the phone would show that I'm still connected (wifi icon is not color though it stays white)...

they could try changing modem it shouldn't hurt the phone and they can always go back with out doing a data wipe
[Captivate Android Development] mnjm9b:
Good...I'm not the only one...lol

Although I only have issues with values under 20 not doing anything.
[Captivate Android Development] makelegs:
Values under 20 should be nearly impossible to discern, as it pertains to screen brightness. 25 would be nearly 10% of total brightness, so 20 or 15 would be negligible, if even noticeable at all. For example, my lowest value is 0-199 = 35 (buttons 255). If ur talking about button backlight, just use 255 for whatever ambient light levels with which you want the buttons to light up. They tend to be all or nothing. My buttons only light up < 400. If ambient light is greater, then I don't have trouble seeing the buttons anyway.

YMMV
[Captivate Android Development] mnjm9b:
In an effort to not repeat myself yet again...

The last few pages me and atinm have been discussing this...

To sum up... settings worked on previous builds 5-15 and before

Settings are very much different at levels below 20.

I keep it at 10, and dim setting at 5.

And if I am reading at night in bed I use 1.

Btw 1 is almost completely black if there are any lights on in the room.
[Captivate Android Development] makelegs:
Sounds like u have it all figured out. :P
[Captivate Android Development] mnjm9b:
If I had it figured out

it would still be working.
[Captivate Android Development] Aus_Azn:
Alright, I'm done with experimenting with GB.

My first Captivate has just died by internal SD removal and apparent corruption of mmcblk0 files, claiming my external SD as well. I'm going to ride out the rest of my contract on Serendipity 6.4 Froyo.

Odin didn't help, it seems to echo the i9000M's internal SD failures.
[Captivate Android Development] makelegs:
Just saw an @cmsrc backlight related commit.... but I still can't seem to figure out which of those are captivate relevant. Sounds like this one may not be, either.
[Captivate Android Development] mortuus.x:
I can't seem to do so either. Tried #9, 11 and 13 and the lights remain on constantly. That can't be helping battery life.

Anyone have any suggestions?
[Captivate Android Development] jaysix79:
Exactly that's my problem to. I'm thinking of going back to 0515. Since that's when I did my nandroid back up.

By the way where can I find the chnagelog. Just wanna know what I'm missing if I go back to 0515.
[Captivate Android Development] mnjm9b:
Link to changelog in OP
[Captivate Android Development] HaiKaiDo:
well I poked around but I dont see much on either of these things. Did the RIL polling issue ever get solved? and I know the graphics end of things works decent, but its been a while since i tried CM7 way way before it was part of the official. I was just wondering if it was good enough to handle things like an snes emulator, or have a livewallpaper running in the background without that killing the performance.
[Captivate Android Development] rwells813:
Deleted
[Captivate Android Development] Kaik541:
I have no trouble running n64oid and psx4droid.

... how do you think apps like gmail and market update? just install the update... it's fine.
[Captivate Android Development] rwells813:
Deleted

Sent from SGH-I897 using xda premium app
[Captivate Android Development] HaiKaiDo:
Awesome, and i guess the last thing is about the ril polling.
[Captivate Android Development] phaedrusiszen:
RIL polling is fine now.
[Captivate Android Development] HaiKaiDo:
Ah wonderful thanks.
[Captivate Android Development] votum:
Only thing I noticed is my touch buttons on the bottom dont work sometimes. I ahve to power the screen on and off to get them to work, not a huge deal.

Oh and NetFlix streaming works flawlessly :D
[Captivate Android Development] mrflips:
Many kudos and thanks to the devs and SGS team, I love this ROM.
[Captivate Android Development] dadams312:
Can I flash right to CM7 from Paragon RC6 w/speedmod kernel?
[Captivate Android Development] EnemyOfGlaDOS:
Yessir

10 char
[Captivate Android Development] dadams312:
thank you very much!

i've been on paragon since rc6 was released, i'm past due on trying gb. i assume i can just follow the "easy way" method on the first page then?
[Captivate Android Development] EnemyOfGlaDOS:
Yep. I was on Paragon forever, you've chosen a fine ROM sir :D
[Captivate Android Development] dadams312:
No complaints from me with Paragon, it was pretty rock solid the entire time I was on it.

I'm excited to check out CM7 though!
[Captivate Android Development] EnemyOfGlaDOS:
Totally. Come on in, the waters nice!
[Captivate Android Development] HaiKaiDo:
I know atleast this first question has been asked before and i cant remember or find the answer but, is there a way to disable the feature that sends the phone into like...super power conservation mode when it hits less than i think 10% battery? And if i use voltage control with kangs kernel (which i know isnt supported here) will that messup the whole "in rom" oc control factor? And is there still some issue with using the newest Gapps?
[Captivate Android Development] CougarBroker:
3 Issues

Wondering if anyone has the same issues, or has remedies.

1. I don't have a lock screen, I have tried everything to restore any tweaks, but if I power the screen off, when I power it up, I have no lock screen.

2. I have no monitor screen on the camera, it takes pictures, but I have no way of seeing what I am taking pictures of.

3. Home button does not function.
[Captivate Android Development] tiuk:
Don't use kang's, he stopped sgs kernel dev when he got an sgs2, last release was 05/12 and a lot has changed since then. I've been using tk-glitch's since then and have been quite happy.
[Captivate Android Development] dadams312:
Well, I'm attempting to...but, i did as the instructions said and when rebooting into clockworkmod recovery from rom manager it shows the recovery but gives a couple errors and i can't select anything (vol. buttons work ok, can't select anything).

doesn't look like rom manager is placing an update.zip for clockworkmod?
[Captivate Android Development] zuN!:
The only issue I've encountered with the 0503 or 0507 Gapps is that Talk can keep disconnecting.
[Captivate Android Development] EnemyOfGlaDOS:
So when you open RM you flashed clockwork recovery? Also when I've installed from RM, I dont have to select t anything in recovery. RM does it all for you. Only time ive had control is when I do it manually. (I.e. put the zip on SD and flash from recovery myself)

*when you choose flash cwm in RM you'll be ask what device- captivatemtd.. it'll ask if you've already installed a clockworkmod (coming from paragon you would have the speedmod kernel with cwm) you would choose 2.x. and I think RM does the rest.
[Captivate Android Development] jaysix79:
have you tried wiping data (factory reset)... and restore your app using titanium back up without restoring the system data... (just the app and data)
[Captivate Android Development] dadams312:
I was just following the instructions, and when I go to see if I can boot into clockwork mod from rom manager it doesn't work. it attempts to boot into 3e(?)recovery (only about 5 or 6 options), where nothing works aside from being able to go up and down.

I pull the battery and it reboots into clockwork mod (green), everything works fine here.

...

When I choose Captivate (MTD), select yes....click clockworkmod 2.x, says rom manager has been set up to use your existing recovery installation.
[Captivate Android Development] EnemyOfGlaDOS:
Then you should be able to boot back into recovery from RM. That's strange. You can always dl the zip and put on your SD card then flash from recovery 2.X (the green menu). If you dont have the nightly on your SD card you can mount storage in recovery (green menu) and do it that way.
[Captivate Android Development] dadams312:
I went ahead and tried to download and proceed with installing everything. after it downloads the latest nightly and ask if i want to wipe everything it says it needs to reboot into clockworkmod to continue.

it reboots into the other recovery, i pull the battery and replace it....it powers on and into clockworkmod and does a backup and wipes everything, but won't load CM7.....just wiped everything clean and rebooted back to paragon..:confused:
[Captivate Android Development] EnemyOfGlaDOS:
dude, that is strange. Even stranger that it boots to the other recovery. I'm assuming you waiting long enough before you pulled the battery to determine it wasn't doing what it was supposed to?

I would just get the files you need, the latest update from the link in the OP. Boot into recovery. Do your nandroid backup and wipe your caches. Install zip from sd card like we all know and love.. and you should be good. You'll have to install GApps separately.
[Captivate Android Development] droid_does:
i select CWM 3.xx for my MTD recovery.....maybe try that?

I was on CM7 nightly #12 and I flashed to #13 with no issues
[Captivate Android Development] atinm:
Dunno why you are having trouble. I can go down to 1 - basically completely dark on both captivate and vibrant and others on our testers can do the same on galaxys. Screen Dim > 1. And then use custom, allow decrease. Try just turning off AutoBrightness from Settings and see if you can move the slider down and get very dark after setting Screen dim to 1. Reboot. :P

Though I have seen that sometimes I don't get the dim screen - even though the driver thinks it is using like 5. We're not going to spend a lot of time on this anytime soon though - so keep it on the bug report I guess and we'll do it when we can. Given that it is just unreliable, I'm going to say the hardware doesn't really like values below 20.
[Captivate Android Development] Linwood.Ferguson:
Wireless disconnects

Using nightly #13. Had a heck of a time getting it flashed the first time, had to go through the process maybe 4 times before I ended up in CM7 instead of back in Frodo. No idea why (flash odin, root, RM Premium, etc.; also tried with just CWM). Anyway....

Most things seem solid but one major problem is wifi. I saw it mentioned but did not notice much attention from others so maybe this is a "me too" but when using Wifi (local, my access point, no competing traffic) it disconnects regularly. Downloading my initial e-mail sync it dropped 3 times. Some apps prompt for "retry", some just give an error. Cellular (AT&T) has been solid, no disconnects (though I have not tried voice, just data).

This is with CM7 #13 nightly, no other mods, modems, etc.
[Captivate Android Development] dadams312:
yeah, i don't really get it. it reboots to the other recovery and doesn't do anything, pull the battery and power it back on and it goes to clockwork and automatically starts whatever it was supposed to do....just doesn't install cm7.

after it wiped everything i tried with rom manager premium again to get clockworkmod recovery working, this time from a freshly wiped phone.

select captivate mtd, say yes, clockwork 2.x, it tells me that rom manager has been set up to use your existing recovery installation....still boots to the other recovery (3e) with errors:
[Captivate Android Development] droid_does:
in that case....since we can't figure out whats the issue

I would flash back to stock using Odin 1 click JF6, root and try again
[Captivate Android Development] dadams312:
I think this will be the next plan of action. i just find it odd that everything seems to carry on with the install as usual but it still won't install cm7.

rom manager prompted me to send a log file of the issue when the phone rebooted and I reinstalled rom manager.
[Captivate Android Development] Hickeroar:
Quick question:

I've currently got the #13 nightly installed. If I go through ROM Manager and use the "Check for ROM Updates" option to "upgrade" to the latest nightly, will I lose any data, settings, etc?

Thanks!
[Captivate Android Development] cpk86:
Nope. Just don't select the 'wipe data' option. I always wipe the dalvik and back up of course.
[Captivate Android Development] Hickeroar:
Perfect! Thanks!

Has anyone tried the #14 yet? Any issues of note?
[Captivate Android Development] fatalexception87:
Soooo... At the risk of getting myself in trouble, I have to ask, has the noise cancelling audience drivers been worked into CM7 yet? That was the one reason I had to jump off back in the early stages, because people on the other end of my calls were complaining about way too much background noise.

I HAVE read the last few pages of the thread, but when I last paid attention the thread was at 130 posts, and it would take me days to read all the way to up current..

Sorry if this had been mentioned recently, but I just really wanna get back onto this rom, as it was THE BEST rom i've used on this phone yet.

Thanks!
[Captivate Android Development] droid_does:
oh gawd theres a nightly #14?

I jsut got #13 working this afternoon :p

I guess I'll flash 14 tomorrow night
[Captivate Android Development] atinm:
No. It's a total pain in the ass because the drivers we do have are from froyo and the code has changed quite a bit since then. Maybe when Captivate gets 2.3.3 someday and Samsung drops the source code for it. We keep attempting to do it as part of the headset fixes, but haven't quite managed to get it worked in yet.
[Captivate Android Development] dave1977nj:
5-23-11 [Build 14] broke my Soundhound *Edit tried Shazam also it will no longer pick up any sounds... and my time is off by a few hours I guess the time zone settings are incorrect. [Going back to Build 13] fixed these issues}
[Captivate Android Development] sixstringsg:
My time got set to GMT as well. Just go in and manually set it.

Sent from my CM7 powered captivate
[Captivate Android Development] sixstringsg:
Can you provide a link to that kernel? I can't seem to find it.

Sent from my CM7 powered captivate
[Captivate Android Development] Hickeroar:
That's the thing about nightly builds. They come out...nightly! :-P

#13 is working great for me, so I'm gonna wait a little while and check in a couple weeks to see who is on a specific daily that is panning out well.
[Captivate Android Development] tiuk:
It's in the I9000 forum, but he also does captivate and vibrant builds. Be sure to download the right one for your phone, and that it is compatible with the current nightly you are running.

http://xdaforums.com/showthread.php?t=1041532
[Captivate Android Development] cpk86:
I can confirm the time problem. I had a sliver of hope when the clock on my phone read 2:20 pm (it was in reality only 9:20 am)....ah, 'tis a Monday indeed.
[Captivate Android Development] darkfalz:
#14 is giving me problems. After flashing, I have no servive. Toggle airplane mode, fails to come out of it, even after reboot. Data/cache reset clears airplane mode. Checked modem version in settings, says unknown. Flashed a different modem, still says unknown. Flash back to #13, modem is indeed changed, and everything works again. Go back to #14, unknown modem and no service.
[Captivate Android Development] cpk86:
Ew. That sounds like zero fun. Just wait till tomorrow and see if 15 gives you the same problems...

Edit:

I actually have a question too... Every time I reset the phone it signs me out of my Twitter and Facebook. I have a feeling it's just some stupid check box I didn't tick along the way somewhere. Any insight on this? Thanks
[Captivate Android Development] matt310:
I had *major* probs with that kernel. Back on the stock kernel, though Kang's still works on the latest nightly, fwiw.