yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Katze Pavilion:
Very hard to add a widget to home screen. It does not respond when I touch and hold to move it to home screen. And another issues when unwanted widgets keep overlay in home screen (it overlays all objects in your home screen, always overlays).

Screenshot: music player widget overlays bookmark widget and I can not remove it.
[Captivate Android Development] lordxentris:
Caught me by surprise when I used the CMUpdater this morning. Worth it :D
[Captivate Android Development] Bane99:
Been running 10.1.3 RC since it came out

Over time though it has slowed my phone down to almost being unusable, even after a cache and dalvik cache wipe.

Has anyone seen benefits with 4.3 so far? I'm running Gingerbread stock KK4 right now and I want to pull my hair out :P
[Captivate Android Development] Val D.:
Try ported CyanAOSP v4.0.0 with Semaphore 3.0.0c kernel (works best in my experience). It's basically stripped down version of CM10.1. Runs good, no lag when updating apps, scrolling is very smooth. In Performance leave default Ondemand CPU governor and Noop I/O scheduler, leave Allow purging of assets disabled. In Data usage / More... disable all Cell Broadcasts. In Developer options set all animations to .5x, make sure Force GPU rendering is disabled. If you decide to use a different kernel, disable zRAM, it actually slows down the phone. In Settings / Apps check available RAM immediately after boot, must be around 140-160MB. If it's less, you have an app installed that runs as a background process and eats a lot of RAM/resources. Remember, Captivate is a 3y old hardware with single core CPU and limited RAM. If you need more capable hardware, just upgrade the phone. No software fix for hardware issues/limitations.
[Captivate Android Development] psg:
for stable CM 10.1.3 (2013-09-23 14:43:40) should i also use

to disable services and stop drain batt ?
[Captivate Android Development] besembel:
what is the effect?. is a service?.
[Captivate Android Development] Val D.:
Not needed. It was a bug on RC1 release. Fixed on Stable release.

Something else is draining your battery. Check battery condition too.
[Captivate Android Development] psg:
I asked, becasue just want to switch from 2.3.6 i9000XWJVZ + CF-root to CM10 and didn't knew that. Somewhere i read about batt drain but it was in 10.1.3 RC1 not in final stable version
[Captivate Android Development] FerociousAndroid:
Hello does anyone have this Rom that they can share?

cm-10.1.3-captivatemtd.zip

Thanks!

EDIT: July 6, 2017

Found it!

http://www.filewatcher.com/_/?q=cm-10.1.3-captivatemtd.zip

This was a CM Stable Rom that preformed smooth and fast compared to 10.2.1/9.1.0/7.2.0.
[Captivate Android Development] meZQureshi:
Yeah. I just flashed new Version. Yesterday's built. Didn't notice any change. Did you?

---------- Post added at 04:25 PM ---------- Previous post was at 04:18 PM ----------

Aren't You facing any Gallery Stopped issues with this touchwiz theme? Mine Gallery doesn't open while I am using this theme.
[Captivate Android Development] Katze Pavilion:
Gallery works fine to me. Just having trouble with adding widgets to home screen.

Setting/Notification toggle icon (in notification drawer) move out of screen if you show AM/PM on status bar.

I like the new full-screen camera interface so much!
[Captivate Android Development] lordxentris:
I can confirm that two, having those problems, not much of an issue. But still love to keep AM/PM on the top.
[Captivate Android Development] Katze Pavilion:
Transition animation is not sensitive as it has been in CM10. If you do not swipe your finger fast and hard enough, current sceen page will not move to the next page completely (it stucks in half of current page and half of next page). Example screenshot:
[Captivate Android Development] Primus76:
Same issue.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] mundocapi:
The same used to happened sometimes in CM10 also.
[Captivate Android Development] thangphysk48:
From cm10 to cm10.1, my cappy stay at boot screen. Cannot access recovery.

PS: My cappy's internal storage was broken so i have to run with external sd card. But cm10 can run, why cm10.1 cannot?

My install log here

+ /tmp/busybox true

+ /tmp/busybox mkdir -p /radio

+ /tmp/busybox grep -q /radio /proc/mounts

+ /tmp/busybox umount -l /dev/block/mtdblock5

umount: can't forcibly umount /dev/block/mtdblock5: Invalid argument

+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock5 /radio

+ /tmp/busybox test -e /radio/modem.bin

+ /tmp/busybox umount -l /dev/block/mtdblock5

+ /tmp/erase_image radio

+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock5 /radio

+ /tmp/busybox cp /tmp/modem.bin /radio/modem.bin

+ /tmp/busybox umount -l /dev/block/mtdblock5

+ /tmp/busybox test -e /sdcard/cyanogenmod.cfg

+ /tmp/busybox rm -f /sdcard/cyanogenmod.cfg

+ /tmp/busybox umount -l /system

+ /tmp/erase_image system

+ /tmp/busybox umount -l /cache

+ /tmp/erase_image cache

+ /tmp/busybox test -e /sdcard/cyanogenmod.cm7upd

+ /tmp/busybox umount /data

umount: can't umount /data: Invalid argument

+ /tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p2

Creating filesystem with parameters:

Size: 2013265920

Block size: 4096

Blocks per group: 32768

Inodes per group: 560

Inode size: 256

Journal blocks: 7680

Label:

Blocks: 491520

Block groups: 15

Reserved block group size: 119

Created filesystem with 11/8400 inodes and 8964/491520 blocks

+ /tmp/busybox umount -l /datadata

umount: can't forcibly umount /datadata: No such file or directory

+ /tmp/erase_image datadata

mtd: not erasing bad block at 0x03e80000

+ /tmp/busybox true

+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin

+ /tmp/busybox umount -l /efs

umount: can't forcibly umount /efs: Invalid argument

+ /tmp/erase_image efs

+ /tmp/busybox mkdir -p /efs

+ /tmp/busybox grep -q /efs /proc/mounts

+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock4 /efs

+ /tmp/busybox cp -R /sdcard/backup/efs /

+ /tmp/busybox umount -l /efs

+ exit 0
[Captivate Android Development] mx828:
I've also noticed that the page indicator on the homescreen doesn't fade and when swiping between homescreens quickly it can lag and often skips from one page to another. One thing i would also like to be brought back is the "smart" behavior of the quick settings panel that would auto appear if there were no notifications, regardless of which side of the status bar i swipe down from. Very much appreciate it if it can be added Pawitp. Also appreciate the hard work. Can anyone else confirm?
[Captivate Android Development] Katze Pavilion:
I've never met this before.
[Captivate Android Development] Lollipop_Lawlipop:
The launcher taking more effort to swipe is not a bug. AOSP 4.2 on other devices also exhibit the same behavior.

Or maybe it is a bug. Either way, it's not new.

The page not moving if you swipe too fast is new to me though.
[Captivate Android Development] Katze Pavilion:
Font is a little bolder, nice. :)
[Captivate Android Development] Katze Pavilion:
New build 20121221 http://get.cm/get/5os has fixed problem about hard to place widgets on home screen.

But there are some (maybe some) widgets do not appear in home screen, although it is placing there, but it's invisible, I can't see it but I can remove it. Example Apollo 1x1. I don't know if is was an app, rom or launcher error, I just notice for other guys to check. :)
[Captivate Android Development] meZQureshi:
Facing Downloading Issues. :(

Sent from my SGH-I897
[Captivate Android Development] gstern:
Building issues

So, I recently synced against the cm-10.1 branch (was on jellybean before),

and when I'm trying to build i get this error:

build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/captivatemtd/BoardConfig.mk. Stop.
Device captivatemtd not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_captivatemtd
CyanogenMod/android_device_samsung_captivatemtd already exists
Syncing repository to retrieve project.
Fetching projects: 100% (1/1), done.

Repository synced!
Looking for dependencies
Done
build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/captivatemtd/BoardConfig.mk. Stop.

** Don't have a product spec for: 'cm_captivatemtd'
** Do you have the right repo manifest?

Never had this before. I am compiling from source since cm9 (on a weekly basis).

Ideas anyone?
[Captivate Android Development] Jolufa:
Exactly the same here... every time stuck in the kernel splash.

Internal memory RIP

Salu2
[Captivate Android Development] Primus76:
Did you wipe and restore factory? Same thing happened to me too. Make sure you have the right gapps handy. I didn't pay attention and just installed the latest cm update when it popped up. Just stayed in boot screen. When I flashed older cm 10 it kept failing on launch saying initial setup failed.

Grab gapps grab cm10.1, reboot factory reset and flash.

---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------

Also pawitp, for the love of all that is good keep the bluetooth stuff as is. Having come from cm 10 my BT works in my Ford sync again with both phone and media. Some time in October it started disconnecting shortly after connect unless I disabled the media portion.

Happy to have it working again!

---------- Post added at 01:00 PM ---------- Previous post was at 12:30 PM ----------

Direct message widget works fine for me now. Did not before today.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] mrlengfung:
love the full screen camera..

looking good..

been using this for a day..

still testing this awesome rom..

thanks!
[Captivate Android Development] AriaOfSorrow:
Are you still unable to purchase apps with bill to carrier on 10.1?
[Captivate Android Development] 26.2man:
Nice Rom, very smooth and still learning all the new little goodies, but what a battery hog.
[Captivate Android Development] pawitp:
Correct your branch in .repo/local_manifest.xml
[Captivate Android Development] mechanical tool:
I definitely enjoy the smoothness, but coming from CM9.1, I definitely find it uses more battery. I'm not sure if its due to Google Now/Search or something else since I skipped CM10.

I have also noticed a few quirks with bluetooth but I haven't had a chance to record a log yet.
[Captivate Android Development] thangphysk48:
When I replaced boot.img inside archived, I can install and boot into screen, but my cappy got phone process FC. So, I think that new boot in cm10.1 was difference with cm10, and not support system run with ext sdcard like cm10. Hope they can improve
[Captivate Android Development] Primus76:
I was having bluetooth issues on cm 10. Didn't quite know how to capture a log while in the truck. Cm 10.1 seems to have cleared it up but in case it comes back how do you capture your log?
[Captivate Android Development] pawitp:
The next build should contain a fix.
[Captivate Android Development] meZQureshi:
I am on latest Build and Still facing 1*1 widget issue. Can't add them on Homescreens.

Sent from my SGH-I897
[Captivate Android Development] meZQureshi:
NEW Build 23/12/2012

New Build is Up on website dated 20121223!!
[Captivate Android Development] brianray14:
I'm currently 10/21 version with the stock kernel. When I reboot on low battery it causes loss of data signal. Only way to regain my data signal is to reflash either the same rom or a newer build. Replacing the EFS folder and flashing a new modem doesn't correct the issue. I haven't seen anyone else with this problem so it could be an issue specific to my POS cappy

Sent from my SGH-I897 using Xparent ICS Tapatalk 2
[Captivate Android Development] Edwardayy:
Are there any problems with the 20121223 build? Little skeptical on installing.
[Captivate Android Development] lordxentris:
Verification failed for some reason but it installed on my cappy without any problems.
[Captivate Android Development] Edwardayy:
No problems booting up or anything? I was looking back in the thread and saw people saying that they couldn't boot or go back to recovery.
[Captivate Android Development] meZQureshi:
No Problem at all. Using nicely! No verification or booting problem at all...

Sent from my SGH-I897
[Captivate Android Development] bsaelim:
Similar problem with sdcard0 permissions getting reset after flashing 1223. Restored from 1222 the permissions are back.
[Captivate Android Development] davidlb512:
CyanogenMod completely changes the Android experience, and it is outrageously improved with CyanogenMod! Just upgraded my Captivate to this most recent Nightly, and currently installing the newest Gapps. Also have my "daily driver" Skyrocket on the latest Nightly and latest Gapps too. Call me stupid, but I have just now seen where there is a "Donate" button on http://www.cyanogenmod.org/, I know it's not much, but I donated for each of my phones that I've updated with CyanogenMod. Keep the developments coming guys!
[Captivate Android Development] meZQureshi:
Latest build is Up at the website dated 24 December 2012 (20121224). :thumbup:

Sent from my SGH-I897
[Captivate Android Development] umanko:
smoothest ROM ever, my thanks to whole cyanogen team for giving new life to my phone.
[Captivate Android Development] sjs87:
I'm trying to flash this rom for my dad on his captivate but I'm having a little trouble. His captivate is currently running stock 2.3.5 but is rooted and running CWM already. When I tried to flash the rom the first time, it booted me right back into the stock 2.3.5. The 2nd time I tried, it went into a bootloop. I restored it with the backup I made previously. My personal device is a GS2 skyrocket running the 4.1.2 pacman rom. And my secondary device is an inspire 4G also running the 4.1.2 pacman rom. I'd appreciate if someone can shed some light on why it wont work for me.
[Captivate Android Development] scidon37:
Try flashing twice before rebooting. I have done this anytime I install cm for the first time coming from stock on any device since cm 7 and never had issues booting.

Sent from my Nexus 7
[Captivate Android Development] lordxentris:
FYI - Just Downloaded and Installed 24/12/2012 Build, Signature Verification Failed, but can be still installed, Installation took a little longer to complete but failed to confirm state "Install from sdcard complete." So without rebooting, I re-installed again, and on the second time it confirmed setup completion. And rebooted. And its working.
[Captivate Android Development] sjs87:
Thanks for the quick reply guys. I'm going to try that and hopefully I can can some more life out of his captivate before he gets something new.

Edit: I just tried to flash twice in CWM (3 times after that) again after wiping and I'm still having the same problem. I'm going to post the problem in another more appropriate thread as to not clog this one up. I appreciate the help guys.

Edit#2: Looks like I got it working. For some reason, it wouldnt flash the latest rom from the 24th. I downloaded the version dated from the 22nd and it started right up without a hitch. Thanks again for the help guys.
[Captivate Android Development] thangphysk48:
I have Alarm clock force close on my Captivate. Anyone got same problem?
[Captivate Android Development] scidon37:
This is an issue when first flashing cm10.1. Clear clock data.

Sent from my Nexus 7
[Captivate Android Development] thangphysk48:
Thank you. I just think that I have to install 3rd party app for alarm.
[Captivate Android Development] BitteredBro:
Hi. I updated to 10.1 since the pre nightly but just found out Ndrive (navigation software) stopped working.

Some people mentioned the same problem on stock JB update and lack of support from the developers of the app.

So be warned and test your Ndrive before going out this holidays. I know I didn't...
[Captivate Android Development] vileladelima:
Wi-Fi AP Issues

Hi, i'm on 20121226, and since i've flashed cm 10.1 when tur my wifi ap on, and try to connect my pc on it, apperas that the pc has limited connecvity on that wirelles network!

i happens with my captvate, and my wife's sgs2

both with cyabogem mod 10.1.

when i was using cm 10, it didint happns!

thanks!
[Captivate Android Development] meZQureshi:
Try clearing the data of clock app. Might work.

Sent from my SGH-I897
[Captivate Android Development] lordxentris:
Just downloaded and installed 27122012, So far no issues with WiFi. If you are trying to connect with connection sharing from your PC then I suggest you restart your PC and try again.
[Captivate Android Development] sivextien:
Come from CM10 and flash Pre-Nightly, experienced Dead Sleep then flash Nightly 26-Dec but cannot fix. Never got this issue since CM9. Is there any one experienced same problem ?
[Captivate Android Development] lordxentris:
Are you using the stock kernel? If so, then try a custom kernel like Devil Kernel.
[Captivate Android Development] JoeCastellon:
Clearing the Clock application data fixed the Clock crashing for me.

I love how the latest nightly feels so much like the stock Nexus 4. I'm loving this build so much.
[Captivate Android Development] fernman1:
Cool!

I just put this 4.2.1 build on my samsung I897(my old phone before upgrading to the I717) I have laying around and so far so good. I will keep an eye out for any bugs I run into and report them.

CV-10.1-20121228-NIGHTLY-captivatemtd

Kernel version- 3.0.54-geedof0c inky-ghost@cyanogenmod #1
[Captivate Android Development] shariqm:
Please forgive my noob-ness

I am currently on JB Lanight which uses Devil Kernel and Devil Recovery. Can I simply wipe and install this CM 4.2.1 on it or do I need to go back to CWM recovery?
[Captivate Android Development] carlosgardel:
I dirty flash from Lanight 9.4.1 and didnt have any problems, maybe you dont have the same luck and need to wipe reset.
[Captivate Android Development] Gromlakh:
There isn't really a "devil recovery". It's just a themed CWM basically. You should be fine, flash away.
[Captivate Android Development] meZQureshi:
Search Using Camera function not working in Google Now. Causes FC.

Sent from my SGH-I897
[Captivate Android Development] Primus76:
My phone randomly called my wife without anyone being in the room with it. Her phone on cm10.1 (9100m) called me from the night stand while we were both asleep. Are out phones trying to mate or is there a ghost in the machine?
[Captivate Android Development] Jolufa:
hehe.

I got happening something similar ...

I thought my phone had gone mad by the number of falls to the floor having ...

I solved installing Tiny Call Confirm ...

Salu2
[Captivate Android Development] hayslett4:
Random Screen Illumination

Since flashing to 10.1, my screen will come on for no real apparent reason. The only real annoyance is when I forget to dim everything while driving at night and it will come up at full brightness. Normally, it would only do this during a call... The front buttons would illuminate for a notification, but this is the first time I've seen the entire screen come up to the lock screen for no reason. Any ideas?
[Captivate Android Development] mik101:
Happened to me too. I ended up restoring my Dec 15th CM10/semaphore 2.6.6sc nandroid because it blinded me a few times while driving.
[Captivate Android Development] thangphysk48:
Hello buddy. There're no multi-users support for captivate, right?
[Captivate Android Development] cnu4u:
To my knowledge multi user support is only for Nexus7 (tablets).
[Captivate Android Development] scidon37:
Multi user support is for anything that is not a phone. I believe that Nokia has a patent for it on phones that they won't license or Google doesn't think that it's a feature that phones really need to justify paying for it.

EDIT: it seems like the latter is closer to the truth: http://news.cnet.com/8301-1035_3-57543535-94/nokia-not-blocking-multiple-users-on-android-phones/ (although it is CNET, so who knows).

Sent from my Nexus 7
[Captivate Android Development] hayslett4:
My phone is sitting on the counter top right now... coming on to the lock screen... then dims.. then back off... (and repeat every so often) I'm on WiFi, have a good signal, have Sync on... I'm going to update on the next nightly (1/6) and see what happens...
[Captivate Android Development] mechanical tool:
I found this code patch posted in the Encryption bug thread that will apparently prevent the problem:

https://github.com/cozybit/aosp-omap-kernel/commit/cea631bdac53f85cc3bfd720da04f726aae33eaa

Unfortunately I have no idea how to tell if this is merged into CM, but given that it appears to fix the problem, it looks like a good idea. I'm sure theres a more appropriate way to submit it but I have no idea what that is. Hopefully someone more familiar with the process can assist.
[Captivate Android Development] sleeper994:
I just updated to the latest nightly via cyandelta and found out that when i place chronus widget on my homescreen it instantly becomes digital watch widget. Is this known issue or what?
[Captivate Android Development] NoDze:
Swipe the clock from top to bottom to reveal the full glory of it. It isn't a bug, it's just how lockscreen widgets work on Android 4.2. Glad I could help.
[Captivate Android Development] sleeper994:
no man it maybe something wrong with my update it just gives me digital clock widget
[Captivate Android Development] Lancered:
Bootloops

:confused:

So I've had the same CyanogenMod version for well over a year, out of the blue (2 days ago) my phone refuses to start up, it just keeps looping on the "xiaomi.com" screen. Can someone remind me the combo to enter the phone on safemode? (Power button + Vol up + what?)

I don't remember what version I'm on because it has been so so long since I've been on here. Can anyone help? I guess I'll update to the latest version once I get it up and running again.
[Captivate Android Development] jerkysh:
Xiaomi?? That sounds more like MIUI , not CM... Vol Up + Pwr Button for recovery, Vol Down + Pwr Button for download mode
[Captivate Android Development] Lancered:
OH yes! I DO have MIUI...geez. It has seriously been a long time since I've last been on...I'm sorry I got confused as before the Xiaomi screen, I have a "Galaxy S Cyanogen(Mod)" screen. Thank you for the recovery buttons!
[Captivate Android Development] NoDze:
Did you TRY swiping the clock down? xD If the problem still persists, do a full wipe(cache, data, dalvik cache and stuff). I flashed the latest nightly earlier and all worked fine.

EDIT: Oh, and did you set everything correctly under the clock/weather settings for the lockscreen?
[Captivate Android Development] sleeper994:
I did try swiping but nothing happens I still just get digital clock with date under. And there are no clock/weather settings for the lockscreen, so I guess full wipe should be solution. Thanks anyways.

EDIT : I did a full wipe and tried to use chronus again and I've got same thing as I did before. But after searching a little bit I found that those clock/weather setting are under system, not lockscreen, panel. Thanks for your help :D
[Captivate Android Development] lordxentris:
I am currently on CM10.1 20130103 Nightly, I am getting annoyed by SOD (Sleep of Death) for a few days now. And it only happens during the night after I go to sleep. I am wondering whether my Alarm Clock app ("Alarm Clock Xtreme Free") is responsible for this. I might switch to a different alarm app and see. I might update to latest nightly to see if it fixs the issue. Will report back on my findings.

Update:

Seems like the Alarm app would have been the problem, so far no SODs.
[Captivate Android Development] NoDze:
I probably should've mentioned that it's there. Well, there you go :D Enjoy your latest OS version on an almost 3 year old phone :D