yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] comdei:
this is the development section, not general.

have a good day! :D
[Captivate Android Development] antonyvijai:
Pls excuse me if it is not an appropriate question in this thread. Is there any idea when CM 7 will become a final product for samsung captivate galaxy s?

from Continuum V4 on matted blue theme using XDA premium app
[Captivate Android Development] nkrick:
The first (and only) rule of CyanogenMod, "Don't ask for ETA's."
[Captivate Android Development] LOSTLOGIC89:
So does this mean that it I flash touchwiz4 jvb it will work? Well I LL try it and are lol.
[Captivate Android Development] tjsooley:
guys.

Stop pestering the dev's

the work they do is the best pure development.

Stop this ****.
[Captivate Android Development] pvr:
oh god I love to follow the IRC logs and sense that impending "doom" of a new update :D

just love CM7 :D my phone rebooted on me today but I was at work and could net get a "whatever"*cat :\ is it possible to get one now (3-4 hours later but no reboot)

will hold on update until an answer pops up ;)
[Captivate Android Development] atinm:
As long as no reboot, you should be able to pull off a /proc/last_kmsg.

adb pull /proc/last_kmsg .

And post it or link it to an issue.
[Captivate Android Development] theMaDHakkeR:
Format system/data/cache and install the CM7 Initial package.

And post stuff like this in the CM7 or MIUI Q&A section next time because im sure no one wants to reply to this.
[Captivate Android Development] antonyvijai:
Ooooh my bad! No more questions. Period :-P

from Continuum V4 on matted blue theme using XDA premium app
[Captivate Android Development] :
When its done is the most accurate answer. You can not ask for a deadline when its all voluntary work being done here. Look at some screen shots of CM. There is only one rule for CM....
[Captivate Android Development] cishos:
this.....is more of a theme question but in the Lense Lockscreen that comes with CM7. Is there anyway to customize it? for one thing I would like to make it all capital letters for AM/PM and I would like to make it a bit thinner too
[Captivate Android Development] thecellx:
Sorry for that.
[Captivate Android Development] jaxf250:
Houston, We have sensors!

Woot! Thanks Teamhacksung!

Screebl works again on the latest kernel... way cool.... this phone with CM7 just keeps getting better... been using CM7 as my daily driver for over 2 weeks now and love it!

Kudos! :D
[Captivate Android Development] pvr:
Great! I've created it under #262 - It might not lead to anything as it's just a weird soft reboot but I figured it's better to report 'cause you never know.

Worst case we rule that as poor programming of the Twitter app (possible, lol)
[Captivate Android Development] nkrick:
broken light sensor?

I just updated to update-cm-7-04282011-NIGHTLY-Captivate-signed. The compass now works great (as advertised) but I immediately noticed that my screen is on 100% brightness. I played around with the brightness settings and it seems that "Automatic brightness" is just setting it to 100%. Could the ambient light sensor be broken with the new updated sensors library?

Let me know if you want a logcat (if it is broken, you can probably reproduce it yourself without needing to wait for me to post a log cat for you to download).

edit: I should mention that I cleared cache and davlik cache after updating (as always).

edit2: It appears this is an issue on the i9000 forum too: http://xdaforums.com/showpost.php?p=13297761&postcount=7522
[Captivate Android Development] jaxf250:
My auto brightness is working fine with the latest update - it's not locked on 100%.

I did not clear any caches, just flashed and rebooted.
[Captivate Android Development] nkrick:
I just performed an indoor/outdoor test. The ambient light sensor is reporting all the correct values. 6 in a dark room, 5000 in a well lit room, 9000 outside in the shade, and 15000 in the sunlight.

The issue is not with the sensor or sensor libs, but apparently in either the kernel or Android/CM taking the proper actions and dimming the screen when appropriate.
[Captivate Android Development] nkrick:
Do you mind clearing the caches to see if it breaks your ambient sensor?
[Captivate Android Development] atinm:
Light sensor isn't working right for Captivate because we moved to using the closed binary from Samsung that is for i9000 and we don't really know what to fix in it yet. For now we only get two values, 6 and 5000.
[Captivate Android Development] nkrick:
If you follow the i9000 forum thread (which I am posting to since there is more activity) there is a lot more info. It appears that the sensor is reporting 4 preset lux values correctly. The problem may be that CM expects values between 0 and 3000, so the value that the SGS is reporting indoor (5000) is higher than the 3000 that CM treats as outdoor full sunlight and places the backlight at 100%.
[Captivate Android Development] jhernand1102:
I get about 18 hours of use for the way I use my phone. Yes there is a inverted color option in the browser.
[Captivate Android Development] mcord11758:
Looking at the nightly package, the modules are in the lib folder. Is this a change with moving to i9000 gb?
[Captivate Android Development] h0ckey10:
Just curious. With 2.3.4 coming out soon does that mean cm7 can just be updated to have all the changes it brings or would u guys have to back track and start over in certain areas. This is assuming it will even by brought to 2.3.4 at all. Like I said just curious
[Captivate Android Development] jaxf250:
I cleared CACHE and Davlik cache, and seems to be the same for me, i.e. it is not locking on 100% brightness for me. Doing most work today indoors, so no direct sun and my screen is rather dim like it tends to be in low light... not noticing anything really different is my point... :confused:
[Captivate Android Development] atinm:
I looked there - where do you see that the sensor is returning the 4 preset values correctly? Some app?
[Captivate Android Development] tiuk:
I had also cleared cache and dalvik, and mine seems to be working. I had tweaked the auto brightness settings long ago, maybe that has something to do with it?
[Captivate Android Development] atinm:
Working how? I only get two levels right now - wish it was day so I could also check outside.
[Captivate Android Development] tiuk:
I could be wrong, the tweaks I mentioned had been to force only three brightness levels, dim, medium, and high. Guess I just didn't notice because medium and high still work. I'm also reporting only values 6 and 5000.
[Captivate Android Development] Kaik541:
this is a change that was actually meant to be fixed a while back. /system/lib/modules is where they're *supposed* to go anyway, and where most apps look for them. basically, putting it in /system/modules was working, but a bad implementation that got pulled in from crespo. atinm recently agreed that this should be changed to the right settings and did so.

2.3.4 will be merged in as cyanogenmod does it. everything we use is upstream, so once CM merges it, we'll have it.
[Captivate Android Development] cesierra:
my compass is working and yay for 2.3.4
[Captivate Android Development] XGX5309:
No problem... I went through my gallery, looking in every "stack" and looking for things that wouldn't preview. The ones that don't preview, like pictures or videos, are hanging the mediaserver causing massive CPU usage. After cleaning out my gallery, I've had 0 issues, and I can usually get 20-22 hours of usage out of one charge with The Escapist's kernel... with things like brightness set on auto.

I would love to see a logcat for the issue to see what, exactly, in the gallery or what codec is causing it to hang.

I've heard about that one, but I have yet to try it. Today I decided to test things out since I cleaned out my gallery, and with an OC set at 1.4GHz with no UV, brightness on auto, and listening to music/charging/browsing the web... it never got hot enough to stop charging or shut off. It got warm, but nothing I haven't felt off default Samsung ROM's. :)
[Captivate Android Development] nkrick:
Based upon further testing (more details in the i9000 CM thread), if you are working inside in incandescent lighting (or "dim" florescent lighting meant to be like incandescent) your lux is probably at 6, which would cause your screen to be at the dimmest auto-brightness setting. You can check your lux using z-device test for the market place, or you can look in the custom brightness section of the CM settings to see your current value.
[Captivate Android Development] Scarchunk:
Accelerometer is off by some degree. Not sure of the proper tool to test it with, but I like accelerometer based games like hyperjump/megajump and there is definitely a responsiveness issue.

The accelerometer and light sensor both seemed to be functioning better prior to Samsung dump. Other than the compass, is there any other sensors that require we use the Samsung crap?
[Captivate Android Development] atinm:
No. :( I really feel like dumping compass and going back to our own open source implementations . . .
[Captivate Android Development] Scarchunk:
I'm flashing back to a build from the 23rd for the moment. I guess I might regret it if I find myself lost in the woods with no compass handy...

I'm all for going back to open source...however I have to admit I'm a bit envious of samsung's codec support:mad:
[Captivate Android Development] ls377:
Is there any chance of getting the compass working without the Samsung crap? I never even noticed it was gone.
[Captivate Android Development] atinm:
I am trying to figure out how to work around this - I'm waiting for tomorrow when I have sun to get more readings off the driver so I can see what's up with the light sensor. At the moment I thought it was just the light sensor that was a problem. If more sensors are a problem, I'll go back to our previous implementations.
[Captivate Android Development] nkrick:
z-device test shows all the sensors and the data coming from them. I am not sure exactly how to read it, but it does seem the accelerometer might be off. Sitting completely still, I see readings that make it appear that it is moving (0.6129 m/s^2 on the X axis, 0.5363 m/s^2 on the Y, and 9.8833 m/s^2 on the Z). I have never tested with other drivers though, so I don't know how it compares. For all I know those readings are "normal" and are due to the Earth's rotation.
[Captivate Android Development] Doug8796:
in b4 2.3.4 :)
[Captivate Android Development] vizographic:
Here is the link below that referenced the

weird media server behavior.

www.google.com/gwt/x?q=media+server...de.google.com/p/android/issues/detail?id=6765

I don't know if I can reliably duplicate the issue, but I'd be greatly pleased to have your analysis of the logcat should I succeed. Thanks.
[Captivate Android Development] Doug8796:
http://www.androidcentral.com/android-234-now-available-samsung-nexus-s-owners
[Captivate Android Development] Kaik541:
that's great guys... no need to keep commenting on this (seriously? like 5 in a row)... once it gets pushed to AOSP and then merged into CM, we'll have it... no need to keep commenting on it...
[Captivate Android Development] skatcat31:
Is anyone else getting a weird download size? I think there might be a problem with the zip that's been uploaded. It says 94 mb, but when I dl it it's ALWAYS 89, and when checked does not share the same MD5 sum. Checked on PC, Laptop, Cappy, Wifi, Tethered, 3g, and all have het same problem. Try uploading the zip Antinm
[Captivate Android Development] Kaik541:
you are incorrect sir. I personally just redownloaded both files and verified the MD5's are correct. the problem is somewhere on your end.

hackintosh-mini:~ shawn$ /sbin/md5 -r Downloads/update-cm-7-04282011-NIGHTLY-Captivate-signed.zip
ee42619aceeea8939560b2956102fcc8 Downloads/update-cm-7-04282011-NIGHTLY-Captivate-signed.zip
hackintosh-mini:~ shawn$ cat Downloads/update-cm-7-04282011-NIGHTLY-Captivate-signed.zip.md5sum.md5sum
ee42619aceeea8939560b2956102fcc8 update-cm-7-04282011-NIGHTLY-Captivate-signed.zip
[Captivate Android Development] ClaPik:
does anyone has the error on WIFI? my wifi says "Error" and just doesnt turn on...
[Captivate Android Development] phaedrusiszen:
I used dimmer bulbs to scale up the light level slowly and it skipped from 6 straight to 5000 as I raised the level. I don't notice any other sensors being off though.
[Captivate Android Development] nissy86:
[solved problem]
[Captivate Android Development] atinm:
What I think is going on with light sensor: http://xdaforums.com/showpost.php?p=13311726&postcount=7647
[Captivate Android Development] Roof King:
Updated to latest nightly. Problems receiving MMS this morning. Would get the text with the option to download but of course it never does. I know there is not an option to check the service center number in messaging settings but did use the following code *#*#4636#*#* to look in phone information to see what number is in there and the service center number is missing. Tried to change the number in the "smsc" field but not sure if that's the correct field and then I couldn't send any texts either. Out of time to play with it and tried to back to my previous backup but it's still borked. Any suggestions?

Edit: removed sim and put in old Blackberry, put in missing service center number, put back in Cappy and is now working. The question I have is why this would happen in the first place?
[Captivate Android Development] nkrick:
I lost my SMSC number too. I tried to manually enter it and I either get an "update error" after which I can only make emergency calls, or I get a force close on the android phone process.
[Captivate Android Development] jangeles323:
I have that same problem too can't turn on wifi
[Captivate Android Development] jgaviota:
About light sensor and compass:

Just thinking out loud here, is there a difference between the sensor drivers in JVB, JVA and JVK? I have tried JVB in my phone and it has the same bug in the auto backlight, so Samsung are the ones with a bug.

Could it be possible to reverse engineer only the compass driver? How is the driver accessed? Is there a method for the compass that could be decompiled to try to develop an open source driver?

And last, is it even remotely possible to use the sensor drivers from 2.2.1?
[Captivate Android Development] atinm:
Yes.

That is what we have been trying to do since we started this, but it is very hard without documentation and some serious math. We almost had it working when JVB came and it fixed Compass driver anyway. The code is closed, and in C so no decompilation will figure out what it does. At least, not by us anyway - we're not that masochistic.

No.
[Captivate Android Development] yogib83:
I realize what I am about to ask may or may not be directly related to our CM7 build; but, since I am running this CM7 build and just everyone in this thread are geniuses when it comes to our Captivate, I figured this would be a pretty good place to start.

Yesterday afternoon I pulled my phone out of my pocket to check the time, and strangely my phone was not powered on anymore. So, I proceeded to press the power button, and nothing happened; then I tried an extended hold of the power button, but still no dice. At this point I'm starting to get a little worried, because I know my phone has almost a full charge and it is refusing to turn on.

The next step I took was doing a battery pull, which worked, and my phone turned on. After everything finished loading, I noticed that I had no connectivity, zero bars and no 3G. Now I'm really starting to freak out. In a fury of panic I: powered the phone down, booted into clockwork recovery, cleared my caches, and reloaded the most recently nightly that I had on my phone (the one prior to 4/28). I then turned my phone back on and still the same problem, no connectivity.

Figuring that I would just skip the B.S. and cut to the chase, I flashed back to stock and did a fresh install of CM7. After that everything seemed to work just fine.

Until this morning, when I got to work and went to grab for my phone which was in my pocket again, it wouldn't turn on without a battery pull. But good news is that when It turned back on, it had connectivity. For now it is holding strong, but I am left wondering what could possibly be wrong with my precious captivate and what I can do about it. Could it be the battery itself? Could have overclocking it to 1.4ghz for the past month or so have caused this? Maybe my addiction to flashing ROMs has finally caught up to me. Somebody please help!

Moral of the story/quick fix, don't keep my phone in my pocket? I think not.
[Captivate Android Development] sixstringsg:
Remember to lock/unlock your phone when first booting to get signal.

Sent from my CM7 powered captivate
[Captivate Android Development] gutowscr471:
External SD Card

I have never tried adding an additional sd card till today to my captiviate. I'm running April 21 nightly. The system recognizes it but I have no idea to get to the files on the card. It's formated as FAT32 and has several pictures and movies on it. Any ideas? It's an 8GB card.
[Captivate Android Development] nkrick:
Look in /mnt/emmc.
[Captivate Android Development] XGX5309:
I have three Captivate's ATM, and all three of them work differently with CM7. One will not run it for longer than 5 minutes without spontaneously rebooting and it's a 1008 build with no standard 3-button recovery (I added 3-button). The other is a 1008 with standard 3-button recovery, and it works decent enough, but the screen temperature is off, and the phone is very sketchy even when using the same JK4 baseband that works with all the Samsung builds. The other is my original 1007 build with solid 3-button recovery... it works fine with CM7. It has the correct color temperature for the screen, it works very well with the JK4 baseband, it's stably overclockable to 1.4GHz, gets great battery life, and doesn't spontaneously reboot at all.

I guess what I'm saying is that until CM7 gets a bit more mature, it's hit and miss on some batches like 1008. That's what I've seen anyway.
[Captivate Android Development] NiXXeD:
My wife has a 1008 without 3 button and hers works fantastic on CM7. We have a jig for safety and we used the 3 button 'fix' to install. I think it is not related to that.
[Captivate Android Development] atinm:
dmesg or it didn't happen.
[Captivate Android Development] ClaPik:
Well...i installed the newest nightly and suddenly my wifi just returned "error" so i flashed back to 4/21 again :-\

i did clear cache and davik

not sure if anyone getting this or it's just me though...
[Captivate Android Development] SweetwaterBurns:
Part of that is that sourceforge uses 1000 kilobytes as opposed to the 1024 that most OSs use for calculating megabytes.

Second part seems like a bad download. Use a computer (or wifi with your phone.) In my experience OTA downloads are more likely to be corrupted.
[Captivate Android Development] skatcat31:
I've noticed a lot of pages with errors on 4/28, and after doing EVERYTHING that would possibly fix the bad download, I can only assume that it's because the download says it's 94.1 mb on the filehost, but when downloaded is only 89 or 90.1. The MD5 checks now(at least), but I ended up having to reflash to fix quite a few errors(notably the ones everyone is complaining about). To those that downloaded it and flashed, what file size do you(or did you) have?

EDIT: Doing the math, the sizes STILL don't add up for the download. It should report 91.89 on my end, but it never does. It's always smaller. Now it won't even unzip(Izarc error: Zip header is corrupt or bad), and it does this EVERY time.

And yes I know, you use CWM to install it, unzipping it on a PC is a quick and dirty way to check if it's corrupt.
[Captivate Android Development] yogib83:
Yep I did that, still no luck
[Captivate Android Development] yogib83:
Ive been running our CM7 release for several months now without any abnormal issues, until now.
[Captivate Android Development] cotr:
Camera

other than using Vignette, is there any way to get the camera fully utilized? I understand the framework issue...
[Captivate Android Development] atinm:
File size is meaningless. If md5sum matches, it's good.

To everyone having problems - without logcats and dmesg output, no one is going to care. There are enough people who are having no trouble at all, so without logs the reports just seem like user error.
[Captivate Android Development] skatcat31:
Hmm well I could always flash again and see what happens, but to date the files sizes have always been fairly accurate on sourceforge. Gonna go do some safety checks before I begin the download though.
[Captivate Android Development] jaysix79:
I got this problem before and I talked about it but seem like its not a problem unless you have a log cat. I have a log cat but I don't know how to use it or how to report it to. I tried reflashing with older nigthly and clearing data and dakvik that didn't work. The only thing that work for me is flash from stock rom and cm7 all over again

By the way it only happen to me when I use GPS aid. When I try to download using GPS aid then my wifi will act up till I reflash from stock again.

By the way is it possible to use a newer busy box mine doesn't install new busy box
[Captivate Android Development] Brosto:
Can I use cwm to flash the latest cm7 over MIUI, or is there other steps I need to do?
[Captivate Android Development] atinm:
Getting a dmesg if wifi is not working/giving error, from your computer where you run adb:

$ adb shell
# dmesg > /sdcard/dmesg.txt
# exit
$ adb pull /sdcard/dmesg.txt

Link the dmesg.txt somewhere - pastebin.com is fine and put the link here, or put it in an issue on the issue list.

If you get a reboot:

$ adb pull /proc/last_kmsg ./last_kmsg.txt

Same - paste the last_kmsg.txt on pastebin.com and put the link here or put it in an issue.
[Captivate Android Development] tifxalex:
Feel like an idiot but, How can I change the homepage screen orientation to portrait as a default?
[Captivate Android Development] tiuk:
Assuming you use adw, adw settings, ui settings, screen preferences, home orientation, portrait.
[Captivate Android Development] starwolf256:
Since I flashed the 4/28 update my brightness auto-adjust isn't working, the screen stays at 100% brightness all the time. Is anyone else having this issue?

Edit: nvm, found the post a few pages back.
[Captivate Android Development] tifxalex:
Neither if the last two comments has worked...Am I missing something?
[Captivate Android Development] tiuk:
Yeah. Have you fleshed a custom kernel? I know in the past auto rotate was horribly broken with platypus, other kernels didn't have that issue (this was a couple weeks ago that I tried it). Don't know what state it's in now. for me I was always stuck in portrait, but that might depend on what your orientation was prior to flashing.

That said, any chance you flashed an i9000 update by mistake? That would definitely screw up orientation (galaxy s = i9000, captivate = i896/i897). Galaxy s is a horribly confusing way to name the i9000 fwiw, since logically it could refer to any of the models imo.
[Captivate Android Development] darkamikaze:
So is JK4 the best modem by the majority? mm.. I sold my captivate and I had it returned because they said it would lose signal and the only way to get it back was to restart.. X_x.. odd..
[Captivate Android Development] ri3tn:
Hey guys,

I've been trying to move apps to ext sd using the app here:

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

It doesn't seem to recognize my external sd. I'm not really sure how to get this to work because the phone seems to recognize ext-sd as the folder external_sd inside the internal sd card. However, this isn't actually the true external sd, as that's located in the root in emmc. So, I was wondering how I get the phone to recognize that emmc is the external sd card to be able to save files there (pics) automatically, along with moving apps there.

Sorry if it's been answered before but I've searched the thread and couldn't find an answer.
[Captivate Android Development] stacio88:
So whenever I download an .apk file it comes out as a .php file. Any fix for this?