yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ppmz:
You're right, it is just a semaphore problem with getprop(), removing it from the script made the rest of the install work fine.

I'm running nightly 10.1-20130202 now and so far it's flawless. Please insert some bugs next time!

Now to search around for a way to make the notification light blink on the captivate...
[Captivate Android Development] lordxentris:
Unlocked means network unlocked, and besides there are tools on the internet to unlock the Captivate for any network by simply changing some data in the EFS folder. And it wont lock your phone when u change your firmware to CM 10.1. But PLEASE take backup of your EFS folder before doing anything, Some Custom ROMs are known to mess up the IMEI number.
[Captivate Android Development] Primus76:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

Well I gotta say whatever was killing my battery has stopped. Getting great life out of it again. Just gave up and kept flashing nightlies. :)
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

Maybe this change in the Feb 3 nightly is the difference:

" Fix threads running after entering call log, possibly affecting battery

life.

When having entered the call log or the call stats activities once, the

contact lookup thread (which wakes once per second) continued to run

even after leaving the activity.

Change-Id: I3209712a52371f99772f522d03bc6b209272089c"

---

If I am not mistaken, would definitely prevent sleep . . .

It is odd that the description says "possibly affecting battery life". I guess it wouldn't affect battery life if the phone was always on the charger or better yet, just take the battery out of the phone and you could go for weeks without draining the battery. :D

---------- Post added at 09:15 AM ---------- Previous post was at 08:44 AM ----------

minor bug:

FusedLocation.apk

had its English name corrupted in one of the recent builds, maybe Feb 2nd..

I think it is reporting the name in some slavic language. The process is now named 'Sloucèny Polohy'.
[Captivate Android Development] ppmz:
Hi All,

Nightly from 0202 doesn't blink the capacitive buttons when you get a missed call/message, they are just hard on. I've tried various settings, slow, fast, normal etc... but the result is the same. Can someone confirm it's the same problem with the monthly or 0205?

I'd like to open a bug report, but since it's a nightly I'm not allowed.
[Captivate Android Development] NoDze:
That actually never worked for me in the CM Settings. And I think I'm correct here if I say that you need to install the Semaphore kernel and install Semaphore manager from the store to enable blinking. You set it in the manager.
[Captivate Android Development] hollowel:
I just installed the 02/05 nightly and almost all my apps were fc'ing so I had to go back to 02/04 and everything is back to normal now. Anyone else have problems with this build?

Just a FYI
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I've been on the 0205 building since yesterday morning. I haven't any fc apps, although I did wipe cache and dalvik before flashing. I was on 0204 immediately before.

I did have problems when I tried tweaking syscntrl values with system tuner pro app 'recommended' tweaks, but when I restored syscntrl to the defaults, it is stable.

wifi, gps, bluetooth, and cell data all seem solid.
[Captivate Android Development] bsaelim:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

Been on 0205 and noticed internal storage doesn't always mount after reboot. I wonder if anyone also experiences the same problem?
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I had one boot where external sd did not mount on boot. a reboot took care of it, but a I have noticed that media storage runs @ 50% ± for about 10 minutes after boot.

something's up there, it used to finish up in a few minutes.
[Captivate Android Development] notasimpleway:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

The media process hogging the cpu is not new to CM. It really drains the battery. I wish someone could figure out why and fix it. You can use an app called Rescan Media to turn it off if it is running but you have to do it each reboot and if you want new pix/videos to show up in your gallery you have to turn it back on. It is annoying. This happened on my Evo 3D and Evo 4G. I'm new to the Captivate(2 wks). Friend gave me the phone after I left Sprint.

Anyways, I was looking over some files and noticed that the external SD card is being read as the emmc(internal) and the internal memory is being read as the SD card(external). Normally, you can go in the settings and format your SD card, but if you do it within CM10.1, you'll actually format your internal card. I don't know if this is working as intended or what since I'm new to this phone.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

Actually, the long running media storage hasn't acted that way on earlier revs of CM10.1, it generally finishes in a few minutes, not 10.

I don't think the internal external sd swap is active on my cappy. I can remove my SD card, and my apps still launch because they are all on the internal storage, I don't put any apps on the SD card.

Did you buy your cappy used? If so, it may be that the previous owner got the Encryption Unsuccessful error. If so, CM10.1 recognizes and supports the internal external swap. It is the only known fix for the EU bug that surfaced after installing ICS roms on cappy.
[Captivate Android Development] ielnats2:
data keeps going off

the data keeps going off after a while and i have to restart the phone to get data again

i read somewhere that this was caused by the switch from WCDMA to GSM so i've set it to WCDMA only .... the problem persists

anyone?
[Captivate Android Development] Primus76:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I thought about that one as well after reading the change log. Good catch. I'm now at 1 day 20 hrs with 18‰ to go :D
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

The fused location name is fixed on 0207 nightly, which I flashed earlier today.

---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------

I did not experience your problem. Check the 0207 changelog, I believe it is fixed, though.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

the alsa sound patches in 0207 messed up volume on ringtones. rebooting doesn't fix it. I am wiping caches again and assuming that doesn't fix it, I'm going back to 0205. I've already got missed calls.

edit/update: it's a problem with the way voodoo sound app is interacting with latest rom. unsetting everything in voodoo sound except 128 bit DAC output fixes it for me.
[Captivate Android Development] notasimpleway:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I am so confused since I'm new to the Cappy and internal SD storage. lol My internal and external SD storage both appear to be working. I don't think my cappy has a problem with EU. I read up on it. Does the cappy use the internal SD card over the external by default? I'm assuming so.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

yes, on the internal storage, there is a 1.5 Gb partition called data and a 400+ Mb partition called datadata, and these contain all of your user apps and user app data, unless you install some on 'sd card', which is actually another partition on your internal storage.

if you open terminal emulator, type su, then enter mount, you will see some interesting info. if, you also type df, you find a more easily readable set of info about the storage, amounts free. etc.
[Captivate Android Development] notasimpleway:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

Thanks for all the info, laughing!
[Captivate Android Development] donclary:
I have been running the 10.1 20130121 M1 version version since it came out. Yesterday, all of a sudden starting dropping the password for my home WiFi. I rebooted this morning to see if that fixes the issue.

Has anyone else had issues with the dropping WiFi access point passwords?

Update: I froze a bunch of apps and finally narrowed this down to some change in the AT&T Smart Wi-Fi app. Thanks everyone!
[Captivate Android Development] JonnehXD:
I'm having issues with the display, actually. On nightlies after the milestone release, my display has randomly gone dark, but not completely off.. just during random use, it'll get so dark that I can barely tell it's on, and there's no way to bring it back up to the correct brightness other than pulling the battery and rebooting.

Either the ROM is having issues, or I think my cappy might be reaching the end of it's usability. :(
[Captivate Android Development] mechanical tool:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I ran the M1 and now I'm on 1-30 nightly and have not had any problems with wifi passwords.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

It isn't the rom per se, as others, including me, aren't reporting the bug. Did you install another kernel?
[Captivate Android Development] Lollipop_Lawlipop:
We're moving to the ROW I/O scheduler!
[Captivate Android Development] ppmz:
How much better is it?
[Captivate Android Development] Lollipop_Lawlipop:
It makes the phone significantly more responsive when there are write operations going on in the background (eg. install app, downloading something).
[Captivate Android Development] Bane99:
Running the 2/10/2013 nightly.

Any particular reason why Media takes up 24% of the battery? Drained the entire battery in 11 hours 47 min on a full wipe and new flash.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

confirming, I noticed that with at least one background app, significantly smoother, on 0210 build.

---------- Post added at 07:34 AM ---------- Previous post was at 07:25 AM ----------

suggest you check your partitions for corruption. While I was running 0208, found corruption in datadata, 'segment' error reported by cwm when trying to do a backup.

restored an earlier backup of 0205 build, then went to 0209 and the segment error was gone. media scanner settles down about 5 to 10 minutes after boot. It only ramps up to higher cpu use when phone is idle until it finishes. If you've got it running for hours, could be the corruption I mentioned, or it could be you've got something else running that prevents the media scan from completing. maybe symptom, not cause?
[Captivate Android Development] JonnehXD:
Nope, it's just the kernel that it came with. :(
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

what are your settings for the display?
[Captivate Android Development] JonnehXD:
Nothing out of the ordinary.. sleep after 2 mins, auto brightness, daydream is off, volume rocker wake is on. Haven't messed with anything in the Galaxy S settings other than the touch key time out (never).

I'm probably going to end up getting either a nexus 4 or whatever the next nexus is. Depends on how long this phone continues to last... the power button has been having issues recently as well. :\
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

try disable auto brightness?? a bad sensor could dim screen.
[Captivate Android Development] Bane99:
How exactly do I check for corruption? This is off of a fresh install and full wipe.

I could try flashing the next nightly or just re-download and install the current build.
[Captivate Android Development] Woody:
What he said ^^^^

I have no idea either. lol
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

reboot recovery, and do a nandroid backup. if you have the file system error, then the backup will abort and report segment error.

---------- Post added at 07:09 AM ---------- Previous post was at 07:06 AM ----------

bug?

0211 nightly, there is no way to set or select the alarm tone. It does play the custom alarm tone that I selected before flashing, but no wsy to change it.
[Captivate Android Development] JonnehXD:
Right, but even that wouldn't get the screen so dark you couldn't tell if it was on or off. I managed to put it under a light once and open up the display brightness dialog and adjusting it did pretty much nothing.
[Captivate Android Development] Bane99:
Nope, no errors backing up from recovery.
[Captivate Android Development] laughingT:
possible Bug/error 20130212 build

bug??

on boot complete, started getting the following error: 'Process system is not responding' with wait/close dialog box (screenshot attached, log attached). I select wait and the phone is otherwise normal, fully responsive.

What is your--

Phone model: SGH-I897 Captivate

Radio (baseband): stock

CM version: 10.1-20130212-nightly.

upgraded from 0211, from 0209, etc.

Did you--

wipe: yes, both dalvik cache and cache

restore with titanium backup: no.

reboot after having the issue:

not for the attached log. but I have rebooted since and the problem is repeating.

Are you using--

a task killer: yes. both system tuner pro and task manager, but these have not changed, nor had settings altered, since running earier builds.

a non-stock kernel: no.

CMSettings/Performance settings (other than stock):

none. no OC, 100-1000, interactive, row i/o.

other modifications:

system tuner pro sets sd read ahead to 512 on boot completed. that is, no use of init.d scripts. the setting was the same in earlier builds.

running holo launcher hd as default. this has not changed, it was the same in earlier builds.

log is here

http://db.tt/Bhrgmv1R

screenshot here

http://db.tt/RVzbwI6Z

Provide any additional information (observations/frequency of problem/last version it worked on/etc):

problem did not occur on 0210 and earlier builds. it repeats each time I reboot the phone, or power down and then restart.

the developer options are all default, and show ANR is not set.
[Captivate Android Development] mechanical tool:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I have also gotten the "system is unresponsive" dialog box when first starting. Since there were no other problems I actually forgot about it.
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

I'd really like to get back the ability to choose the alarm tones in clock app. 0212 nightly doesn't permit it. I think when dev added the ascending volume option, the settings menu got trashed.

For now, I installed alarm clock extreme and disabled the clock alarms in the stock clock app.
[Captivate Android Development] iffatall:
4.2.2?

Does anyone know if we are gonna get 4.2.2? It seems some phones have got it in the 2/15 nightly, and since we haven't I wonder if it is because we have reached the end of Captivate upgrades... :)

---------- Post added at 10:18 AM ---------- Previous post was at 09:33 AM ----------

Oh, I just noticed the 2/15 nightly is a 2/14 build. So may be the next one is going to be 4.2.2.
[Captivate Android Development] hollowel:
From what I've read it was decided that cm wasn't going to release 4.2.2 nightlies for now and that some builds made it through, but the rest were canceled for now.﻿ I also saw that the i9000 got an unofficial release so we should be getting one down the road.

Source

https://plus.google.com/111547202590105460766/posts/9D9uEZDsgnG
[Captivate Android Development] laughingT:
Re: [NIGHTLY][ROM][4.2.1] CyanogenMod 10.1 for Samsung Captivate

From what I am reading, 4.2.2 isn't worth much , very little diff from 4.2.1, so wait for 5.x IMHO. Maybe they will call it key lime pie.
[Captivate Android Development] iffatall:
This is to confirm that the latest nightly is indeed 4.2.2.
[Captivate Android Development] laughingT:
It is indeed. And having run it for a for a few hours, it seems like they just took a few bug fixes and security hole patches and released them. No performance improvement that I can detect.

and oh, it is nice to have the alarm menu fixed so I can pick my own alarm tone, thanks!
[Captivate Android Development] jgchaval:
The power shutter for the camera is not working correctly. Even when I have it enabled, when I take a picture using the Power Button, the phone locks down. I have to disable Power Shutter and then re-enable it in order to work correctly.

Has this happened to anyone else?
[Captivate Android Development] sleeper994:
+1
[Captivate Android Development] Squeaner:
Just checked and it is working for me. I am in the 2/18 nightly with stock kernel.
[Captivate Android Development] laughingT:
Just tested power shutter, no problems. 0218 nightly.

Try clearing data and the cache for gallery app, which has camera app built into it.
[Captivate Android Development] bsaelim:
It seems hdr mode is included in 0219
[Captivate Android Development] sleeper994:
Whaaaaaaaaat? Gotta flash it ASAP !!!!
[Captivate Android Development] RCDuke:
In case anyone has missed it, the option to reboot to recovery or bootloader from the power menu has changed. You have to enable developer options (if not already), then enable the advanced reboot option. Not sure why they hid this option, but it still exists.
[Captivate Android Development] sleeper994:
Do I need a full wipe to flash nightly with 4.2.2. or can I just wipe cache and dalvik???
[Captivate Android Development] laughingT:
Are you on a 4.21 nightly? If so, I flashed from that with only wiping cache and dalvik cache - no problems.

Also did same from one 4.22 nightly to a later nightly, 0219, no problems.
[Captivate Android Development] Danilo Cvjeticanin:
They ask me for sim card pin? Now i dont have a network ?!?
[Captivate Android Development] scidon37:
It was put in Developer Options because it is not needed for a typical user. Even when enabled, it also cannot be accessed until the lockscreen is dismissed, for security reasons. CyanogenMod has posted a good expatiation on g+.

Sent from my Nexus 7
[Captivate Android Development] ppmz:
Will M2 be identical to the 02/21 nightly? Or is some special effort made to make it more 'conservative'? How does it work?
[Captivate Android Development] laughingT:
Here's a link to the cm blog explaining the M builds intent:

http://www.cyanogenmod.org/blog/cm-10-1-m-series-builds-have-arrived

I believe the M build is not necessarily updated monthly. If you check the cm10.0 builds at the cm site, you can see that the M build might be followed by a stable build, rather than another M build.

edit: The only other distinction I can see is that M builds bug reports are reported to the cm team, whereas the nightly bugs should be reported in this thread.

Frankly, the 10.1 nightlies are so darn stable on captivate, it does seem to be a minor distinction, at least for captivatemtd builds.
[Captivate Android Development] laughingT:
I got tired of having to copy my modified gps.conf file with the hellstorm fix after flashing any nightly, and figured out an easy easy way to deal with it. This will not work if I do a complete factory wipe, but it works fine when I am only wiping caches before flashing the new rom.

I just add 'etc/gps.conf' as an additional line in the list of etc files that are in the file 70-gapps.sh that is located in the system/addon.d folder. I make a backup copy before editing and make sure the permissions remain 755 on the file in addon.d folder.

The script, 70-gapps.sh, copies the listed files to a temp folder during the update, then restores them when the update is completed. That's why you don't have to reflash gapps after a nightly update.

If you find the nightly is routinely resetting a favored setting or conf, then you could try to find the related file for that setting, then add it to the script on a separate line in the list of files in the script.
[Captivate Android Development] dominuce00:
Where is developer options. Cannot find.
[Captivate Android Development] RCDuke:
It's been hidden. Go to System Settings -> About Phone ->, and tap "Build Number" 5 times to unlock the dev options.
[Captivate Android Development] iffatall:
Get CM Camera Back

I am using the latest CM 10.1 nightly.

When I first switched to 10.1, I wanted Picasa sync in the Gallery, so I flashed the gapps-jb-picasa-20121011 after flashing gapps-jb-20121212, which has been working fine.

However, after having used it for a while, I now feel that the Picasa sync feature is not worth the camera features of CM, that I lost by flashing the picasa sync add on, especially since I can access all my online photos via G+.

So now, I would like to get the latest CM camera back, and don't care about Picasa sync. How can I do this?
[Captivate Android Development] laughingT:
The stock camera app is embedded in the stock gallery.apk. So if you freeze or uninstall the picassa app, the camera should be available, unless you removed the stock gallery app.
[Captivate Android Development] iffatall:
There is no picasa app. I believe the stock gallery/camera app was replaced by the gapps-jb-picasa flashing.
[Captivate Android Development] laughingT:
Strange. I have both the picassa tool and the standard gallery.apk, I didn't install these, they are in the base cm rom.

When you say you don't have it, are you looking in the app drawer or are you looking for it in the all applications tab under the settings, applications menu? Maybe it is disabled or frozen. If you use root explorer to look in system/apps, is there a gallery apk in the folder?

if the gallery.apk is not there, then uninstall picassa, check for any scripts in init.d or addon.d that are keeping picassa active or rinstalling it, then reflash the ROM.
[Captivate Android Development] iffatall:
I see a Picasa Uploader app in Manage Apps settings. And in /system/app I have something called GalleryGoogle.apk.

What do you suggest I should do?
[Captivate Android Development] eduardo_b:
Getting same issue with same nightly. It's slightly annoying but not a deal-breaker. Haven't even looked to see if there's a newer nightly...yet.

-----

I finally did look at nightlies and found latest was for 24 Feb, so I did download and flash...no more process system error but seems slow to finish startup after boot. Or I could just be used to S3s (Captivate is only for music these days).

-----

Process error back, but it appears to be related to how slow Beautiful Widget clock is to load...at least on mine. Oh well,
[Captivate Android Development] laughingT:
I 've got two gallery apks in my system apps folder, here are the apks

http://db.tt/rKTScSVp

http://db.tt/QUnI3VwD

backup existing googlegallery app, uninstall it, then try installing the apks? they may need to be system apps to work. u csn convert to system apps with tibu.