yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] steph2:
I would like to ask what battery life is now that the JVB source has been added to the mix.

I loved the ROM but i couldnt get a full work day out of phone battrey drain was horrible. i got 9 hours max and i hardly used it that day. On an normal day i would be dead by 2:00 pm, way short of were i needed to be.

My day is about 6hrs of music play and 1/2 hour talk time about 1/2 hour net usage and mybee 12 to 20 text mesg. so kinda heavy use.

but i can get whole day of this type of use out of many 2.2 uv roms, and still have battery when i got to bed not much mind you. around 10 to 20%.

I have not used this ROM in about a 30 to 40 days. and i see a few updates sence then.

On the week ends with 2.2 rom i dont charge from sat morn till sun night i figer that's because i dont use the music player but i make many more calls and texts and more net time. i say this because this is prb more like most people,s usage.

thanks for reply,s or PM,s

P.S.

I did give it a few weeks before i left CM7 so i dont belive it was from a new ROM.

norm they settle in a few days, and you get better battery accuacy after a few days.
[Captivate Android Development] slifer315:
just create a backup in recovery and flash the new update. if you want to go back, format system, data, cache, and datadata in recovery and then restore the backup.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] mirrored:
Anyone know where I can find a MattedBlues theme for Captivate CM7?
[Captivate Android Development] EnemyOfGlaDOS:
Some are found in captivate themes and apps, more can be found in android themes. It also tells you where to find themes for CM7 in the OP. But here it is:

http://xdaforums.com/showthread.php?t=987435;;)
[Captivate Android Development] ls377:
Or you can just restore the backup.
[Captivate Android Development] Odinist:
I can't get any of the ROMs that I've tried to DL correctly. They keep coming in at 88ish MB, and the MD5s aren't matching what they should be. Any good mirrors of a recent ROM? Thanks.
[Captivate Android Development] tjsooley:
that means that you fail at life.

LOL

Just kidding

try clearing the temp files and cache in your browser and re download if that doesn't work try with a different browser.
[Captivate Android Development] gabby131:
My gameloft games are all working!

Yey!!!
[Captivate Android Development] waghoba:
what would be the procedure to flash CM7 again if I have flashed new samsung released GB bootloaders...

Thanks in advance.
[Captivate Android Development] Kaik541:
the same instructions you followed the last time (the ones that haven't changed at all)
[Captivate Android Development] waghoba:
Thanks for the help....but I am concerned about the bootloaders stuff. Do I have to go back to stock 2.1 or I can just flash the CM initial kernel (and rest of the procedure) on top of GB bootloaders and use new key combo to get into download and recovery
[Captivate Android Development] superj3211:
i still am not seeing much improvement after the gpu update, my quadrant still looks like blank textures...is this normal or is it something i did...also was wondering since there was a source code for 2.3.3 would the install ever become as easy as a custom 2.2 rom?
[Captivate Android Development] Kaik541:
you should be able to keep the new bootloaders, but I don't recommend having a bootloader not for your device on the phone as it can lead to unforeseen complications.

because quadrant == definitive result of how well a ROM works.
[Captivate Android Development] mirrored:
So I flashed this and everything looks/works except the lockscreen is just black with the notification bar. Any ideas?
[Captivate Android Development] Thnikk:
Is there a possibility of hard bricking?
[Captivate Android Development] superj3211:
i never said it was but if the graphics on that are bad then others wil be too

... i.e. like games or other apps and such
[Captivate Android Development] Kaik541:
any time you touch bootloaders there is always the possibility of hard bricking. which is why it's VERY STUPID to put another device's bootloader on your phone in the first place
[Captivate Android Development] whitesox311:
it.....does?
[Captivate Android Development] mirrored:
More than my lockscreen is messed up, everything is screwed. I'm on the latest nightly. Is there anyway to revert back off of this messed up theme?
[Captivate Android Development] TheEscapist:
Reflash the latest nightly.
[Captivate Android Development] EnemyOfGlaDOS:
There's a good chance the theme is not updated to be in sync with the latest nightly. You need to make sure in the OP. He was continuing support for CM7, just probably hasn't been updated yet.
[Captivate Android Development] mirrored:
yeah it was definetly my mistake for not double checking everything.

can't even get the nightly on my phone through usb or downloading it because the phone is so f'd. might have to go all the way back to stock and redo the entire process :mad:
[Captivate Android Development] Thnikk:
I meant past the bootloader flashing step, but I did it anyway :)

Only difference now is that I get a garbage kernel screen, but everything seems to be working fine. No more at&t screen, better button combos, boot anim isn't choppy.

EDIT: No ext-sd
[Captivate Android Development] pparavas:
Is there anyway i could get motorola multitouch keyboard on my captivate running cm7?
[Captivate Android Development] pparavas:
the same thing happened with me, i tried installing matted blues theme, and my phone got fked up, had to go back to stock and reinstall cyanogen.... it clearly stated that the themes would support cm7
[Captivate Android Development] mirrored:
He updated the theme to work but its split in 2 parts and one link doesn't work, ugh
[Captivate Android Development] waghoba:
do you mean not as external_SD right? coz in CM it is recognized as emmc.
[Captivate Android Development] Thnikk:
Yeah, not recognized at all. You did it too? Do you have the weird kernel screen?
[Captivate Android Development] Kaik541:
weird kernel screen is JVB bootloaders. just like using a JVB kernel without JVB bootloaders will produce a similar screen.

edit: to be quite honest, a lot of stuff changed in the bootloader that we can't control so your external sd card issue is also likely related. which is why we don't tell you to be on JVB bootloaders. go back to stock and start over.
[Captivate Android Development] waghoba:
I know this is probably not the best place to ask but does on click odin posted by DG in captivate development thread will flash captivate bootloader back??
[Captivate Android Development] shawn.ferris:
Ok.. I've dug a little (lot) more, and every reference I find for YAS529, also calls it an MS-3C. For instance the datasheet for YAS529:

http://html.alldatasheet.com/html-pdf/205144/YAMAHA/YAS529/215/1/YAS529.html

Same thing in the Meego tree. Even more digging and I find Arduino source for a YAS529 driver and the files are named ms3c, etc..

http://groups.google.com/group/itrs/browse_thread/thread/b3085a4ae81bc1?pli=1

While not immediately useful, it looks like it does provide both a raw interface and some sort of calculated interface too. If this is the same hardware (if not, if you could explain, I'll keep digging), perhaps these are the missing algorithms hidden in the closed binaries?

I also see the yas529 driver disabled in the current captivate source. I'm in the process of setting up a VM to build out a build environment as I wanna play with the data coming from that driver.

Anyway.. just trying to help any way I can.. HTH
[Captivate Android Development] gabby131:
I believe so....it reverts back to a fresh cappy w/o any trace or remains of custom roms....i always do that one click odin (eclair one) before flashing any rom.

EDIT: it flash boot loaders back too....coz some users who bricks their cappies just get Jigs and then flash on that one click odin to bring bootloaders back....
[Captivate Android Development] tjsooley:
anyone notic that when your on a call the data disconnects.
[Captivate Android Development] citrit:
Yep, I tested a bunch of modems and the only one I got to work and keep the data open was the JK3 modem. It also works best in my office in the dungeons of our offices.
[Captivate Android Development] atinm:
The YAS529 is enabled in all the aries defconfigs:

aries_captivate_defconfig

You can compare the drivers to see how ours is different/same and hopefully it'll tell you whether the algos are in the driver. I tend to doubt they would be, but if meego et al have the upper layer daemon code too, that would be awesome.

-Atin
[Captivate Android Development] shawn.ferris:
Indeed, I will. Though, I was a little more optimistic, since the arduino breeds simplicity. Figured they'd done it a solid by making everyone's life easier. I'm probably just that naive though. ;D

I dismissed this one fairly early. IIRC it was also labelled ms-3c, so I assumed it was still the wrong driver. But, I will find and comb through that one again since I gotta believe they'd have the upper layer oss'd too.
[Captivate Android Development] crazililazn:
Omg, one of the features I miss the most from a normal samsung rom. If the devs get multicodec decoding working, I will never use a normal samsung rom ever again :P

Sent from... Waiting for location....
[Captivate Android Development] theMaDHakkeR:
Im using JK4 modem and the latest nightly and i still get data while on a call. The only weird thing i see is that the colors seem much cooler on this latest nightly. The Auto brightness still seems to be broken too but i can deal with it and just turn the brightness down manually.
[Captivate Android Development] cesierra:
How-to: Turning LED notifications off

Go to: Settings > CM Settings > Interface > LED Notifications > Miscellaneous

Select the app you want to change (for example GMail)

Select flash color > None

That's it. Gmail won't bother you by turning the lights on anymore.
[Captivate Android Development] atinm:
Auto-brightness works. Please check your CM Settings for it Display > Automatic Backlight > Allow light decrease. You can also check Use custom and edit the levels yourself.
[Captivate Android Development] theMaDHakkeR:
So i set Allow Light Decrease but it still seems that the Auto Brightness is much brighter than it was before. When i cover the sensor it does dim the screen, but in general its like the screen is always brighter now with Auto Brightness enabled.

It will only dim when i completely cover the sensor so im not sure what else to set.

EDIT: Anyone have some suggestions for some custom light levels?

Thanks.
[Captivate Android Development] jaysix79:
They new nigthly update made my captivate very snappy. Its fast and brigth but my battery life kinda suck again. Does anyone have any suggestion?

I'm running stock cm7 with out any custom rom. And using juice defender beta on aggressive mode
[Captivate Android Development] TheEscapist:
Juice defender doesn't work properly with gingerbread. Try disabling it.
[Captivate Android Development] theMaDHakkeR:
What do you mean by bright? The only thing that happened with the latest nightly is that my battery gets destroyed if i leave auto brightness on. Because it doesnt seem to do anything but run my screen at 75% brightness and then dims when i go into a pitch black room lol. it has 2 modes, very bright, and very dim, and 99% of the time its stuck on the bright setting.
[Captivate Android Development] tjsooley:
I have used juice defender with ultimatejuice for ~3 weeks now and it has worked just like it sould.

One question how does superpower work on cm7?
[Captivate Android Development] glos7777:
hi all I have taken video capture today then I watched it but sound was very very low I dont hear it until close to speaker what can ı do ?
[Captivate Android Development] jaysix79:
Ever since update 0428 and 0501 my phone is always on full brightness unless you cover the light sensor. But back in 0421 the brigthness sensor actually work how they should be. You can customize how your brightness should be now its either full brightness or low. But the phone is alot quicker
[Captivate Android Development] theMaDHakkeR:
Yes i noticed the phone is much quicker, But im not sure whats up with the light sensors. Atinm said its working but i cant get it working properly. Its always stuck at the same brightness and doesnt dim at all unless you cover the sensor.
[Captivate Android Development] nkrick:
The binary sensor libraries from the i9000 Gingerbread release (which is what is being used because it allows the compass to work) only has 4 brightness levels that it reports. 6, 5000, 9000, & 15000. These values are basically only useful for the following situations:

6 dark room or incandescent

5000 indoor in fluorescent lighting

9000 outdoors in the shade

15000 outdoors in the sunlight

The limited testing you are doing will probably only produce values of 6 (with the sensor covered or dim lighting) or 5000 (in bright lighting). If you want to see the other two values reported by the sensor, you need to go outside.
[Captivate Android Development] nkrick:
Atinm, I asked a co-worker with a un-rooted un-modified captivate to install z-device test and report the values he saw. He is located over 2000 miles away, so I did not get to see the results myself, but what he reported was seeing the following values:

6 - with light sensor covered

1000 - most places indoors

5000 - next to a window, or near a 60 watt CFL

9000 - outdoors around 5 pm with a lot of clouds

It is possible he would have also seen 15000 if it was a bright sunny day.

It mainly looks like the Captivate (and probably other 2.1/2.2 SGS's) had a 1000 lux value that is missing in the GB source. I think there is still hope that a future release (either for the i9000 or for Captivate/Vibrant/other) will bring the 1000 lux setting back.
[Captivate Android Development] theMaDHakkeR:
So ive played with the automatic light sensor levels and its a little better. Now im not sure exactly what the "0" Lower, "9" Upper means and has a setting of Screen 15 and Buttons 255. But i have changed the "5000" setting to Screen "70" and its slightly dimmer now. Now when i cover the light sensor i get screen "50" but i can change this also.

So does anyone have any settings that they recommend to use?
[Captivate Android Development] atinm:
Play around. The ranges are the ranges that the light sensor reports. You can assign brightness values between 0-255 for each range. Since our sensor only returns 6, 5000, 9000, 15000 - the ranges are basically using those values. You can set them to 0-6, 6-4999,5000-8999,9000-14999,15000-infinite and then assign a brightness value to each. I havent' spent any time fixing those because we're just trying to get the open source code to work so we don't have to use the stupid light sensor library if we can.
[Captivate Android Development] theMaDHakkeR:
Seems like i got it just right now. Thanks and thank you for all the work you put into this, its very much appreciated!
[Captivate Android Development] ShadrachCA:
Has anyone come across a version of the KC1 modem that is compatible with CM7? I got some really good results with that modem in the LA area when I was on Froyo.
[Captivate Android Development] mirrored:
Is there a nightly that people know is the most stable or should I just stick with the initial? On the newest nightly its super buggy with tons of FCs
[Captivate Android Development] RockRatt:
Been on the most current update since it came out and no force closes or bugs here. Maybe try a reflash? What Initial are you coming from? I am not sure if it would should matter but at some point I started with the newest initial kernel and have used every update since with no force closes or anything.

Sent from My KickAss Captivated CM7 OC'd 1.4Ghz/Undervolted
[Captivate Android Development] mirrored:
I started with the newest initial from the official link to all the cm7 captivate files in the first post.

I will try a reflash. Are you using any custom themes?
[Captivate Android Development] Sarcoid:
Initial is from March and probably the least stable. If you're getting a lot of FCs, you might want to reinstall.
[Captivate Android Development] mirrored:
Ok so if I do a reflash from the newest initial/newest nightly, the only thing that could be effecting it (besides another bad flash) is the theme I was using, correct? Or are there even more things that can go wrong?

*Just to note, I'm not restoring system data or anything dumb like that. And I've been flashing for a while, so I don't think I screwed it up but I'll definitely redo it to be sure.
[Captivate Android Development] Sarcoid:
Wait a second, it sounds like you did something wrong. There's only one initial.
[Captivate Android Development] mirrored:
No, I know theres only one initial. The other user just asked so I specifically qualified it as the newest.
[Captivate Android Development] Sarcoid:
Then I guess try flashing again with the initial and updating with the latest nightly. When you mention themes, does that mean using the Theme Chooser? I've used that before without any problem.

Are you getting FCs the moment you boot up? That might be an indication the flash went wrong. Or you can retrace your steps and figure out if setting something is causing all the FCs.
[Captivate Android Development] mirrored:
Will do. And no, I did not get any FCs when I first booted up, everything worked fine. Thats whats making me doubt the theme. Here is the theme in question:

http://xdaforums.com/showthread.php?t=987435

The author said he updated it to work with the latest nightly. :\
[Captivate Android Development] Sarcoid:
Works for me...
[Captivate Android Development] papercutMS:
Are you using the stock camera app? I found that the camera does not load as fast as Samsung ROMs, but the camera is working fine for me with the latest nightly
[Captivate Android Development] XGX5309:
Well, the next nightly won't contain the JVB sensor drivers. :) They just removed them from Github.
[Captivate Android Development] Kaik541:
it's really a bad idea to use a theme that includes flashing. since this build updates often and not on a standard basis, it's very easy for them to become out of date or modify something that doesn't exist any more. framework changes happen all the time in CM7, meaning a line may get added or removed and if the theme creator does a lazy copy/paste without examining every change, they're likely going to screw something up. if you want a theme, use something compatible with the tmobile theme engine that's included

and considering it's not actually all that hard to make a theme engine apk, it's a bit silly that people are still making themes for flashable zips at all. basically though, if you use any third party modification of the ROM (i.e. flashable zip theme), don't blame any bugs on teamhacksung.

thanks to GuiPer we have a way to use our opensource light sensor and still have a working compass. things are too busy to release a build right now (lots of changes within the past few hours alone), but expect the next one to be a major change.
[Captivate Android Development] mirrored:
ok, thanks for the info/tip. I was never blaming anyone though, and this thread has proven very speedy in their extremely helpful information :D
[Captivate Android Development] TheEscapist:
Hey Atinm, with the new build system, is there anyway to force it to build from kernel/? It keeps using the prebuilt kernel, which is obviously not going to work for me, and I'm just wondering if I'm missing anything.
[Captivate Android Development] Kaik541:
./build.sh captivate kernel
[Captivate Android Development] glos7777:
any suggestion :S
[Captivate Android Development] TheEscapist:
Just copies the pre-built kernel.
[Captivate Android Development] Kaik541:
it runs a make on the kernel directory, so that isn't true, but it doesn't put it into any zip... it outputs to out/target/product/captivate/kernel which you have to do something with (is probably about a 2.5 MB image)... if you want a boot.img you're going to need to attach the recovery initramfs as well
[Captivate Android Development] TheEscapist:
Even after deleting all traces of the kernel in the out directory, and running make mrproper in the kernel directory, it's not building anything.

EDIT: And after deleting "kernel" in the device tree, make fails because it can't find the pre-built.
[Captivate Android Development] android158:
Maybe someone here will be able to help with spoof phone as different model for MMS. Anytime I try and change to a different "phone mms" it doesn't actually change it. I've even changed it, rebooted, powered off ect and no luck. Anyone know how to get this to work? Thank you in advance!!!
[Captivate Android Development] atinm:
There is a lot more we're doing now, and things are in flux. You're going to have to debug some yourself as well I'm sure.
[Captivate Android Development] Kaik541:
all I can tell you is what I know:
[Captivate Android Development] TheEscapist:
Okay, I was just wondering if there was any new command or something to force a clean kernel build. I'll dig through the make/build files.

EDIT: Got the change from github. Thanks Atinm. ^^

Yeah, must have gotten changed. Thanks for the help though, Kaik.
[Captivate Android Development] mirrored:
went back to stock to latest nightly, everything works great but what happened to my awesome new gallery? I'm back on the old one for some reason
[Captivate Android Development] android158:
Anyone?

10 char
[Captivate Android Development] deuceduzit:
MMS retrieval

Sorry if this has been mentioned... But does MMS retrieval work on this rom? Mine keeps saying unable to retrieve MMS texts.... Any help would greatly be appreciated.
[Captivate Android Development] phaedrusiszen:
Works fine here. Received several today.
[Captivate Android Development] matt310:
If you have another phone available, take your SIM card out and put it in the other phone, turn it on and let it register on the network. Send a text message to yourself (or someone else) and do the same for MMS. Then remove the SIM and put it back into your Captivate.

Apparently sometimes flashing will remove the SMSC (SMS Service Center number; for AT&T it's +13123149810) but there's not an easy way to enter it when on CM7, so if you don't have another phone handy you'll need to flash back to a Samsung ROM (stock, for ex) and manually enter it back in if, once you've re-registered on the network, it doesn't push the number to your device.

I wonder if removing the SIM when flashing an update would minimize this risk?
[Captivate Android Development] Kaik541:
cm settings, led notifications... set it to dark colors... anything but bright
[Captivate Android Development] kublis:
Can I back up cm7 with rom manager restore it after I load up the bootloader or do I have to do a fresh install? If not with rom manager, is there any way to do a back up?

I would like to know in case I want to play with other roms or a nightly update screw something up.

Thanks!

Sent from my SGH-I897
[Captivate Android Development] mirrored:
just do a nandroid
[Captivate Android Development] kublis:
What exactly does that do?

Sent from my SGH-I897
[Captivate Android Development] mirrored:
in recovery -> backup & restore -> backup

it creates a mirror image of everything on the phone so you can just flash that in recovery if you screw up anything. be sure to take your sd card out though (when backing up and recovering)
[Captivate Android Development] slifer315:
boot into recovery with the button combination, choose backup and restore, then pick backup. it will take ~5 minutes and create a backup of every partition. to restore a backup, go to the same menu, pick restore and pick the oone you want to restore. their default names are the days and time of the backup.

blah, a little late..

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] dieselstation:
How come i don't see the Bluetooth/GPS/Wifi/etc bar on my notification area like this? Mine is just empty.
[Captivate Android Development] papercutMS:
Menu>Settings>CyanogenMod settings>Interface>Notification power widget>>Widget buttons

Then customize to your hearts content.