yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] bveditz:
My 32gb microSD didn't work correctly on my captivate or on my nook either, both running CM7, I assumed it was a hardware issue. It kept wanting to format it. Since it does work on yours but not on mine or ColonyDudes, maybe there are certain types that don't work. I never looked into it since it turns out that I really didn't need the 32gb anyway and I found that the phone performs better without any SD at all. The 16gb onboard seems to be enough for me.

For reference, my 32gb was a Sandisk Class 4 also, same as ColonyDudes. Maybe there is an issue with that model and CM7.
[Captivate Android Development] anishz:
Are nightly change logs down for everyone or just me? it's been 3 days now.

Battery life for me is phenomenal on cm7, i get almost 4 hrs of screen time on cm7 whereas i used to get 2-2.5 hrs on a samsung rom. the people complaining about battery life don't seem to be using the phone that much. cm7 has faster battery drain than samsung rom i guess due to some proprietary code, so:

if you keep your phone in your pocket the whole day: Samsung Rom

if you are a heavy user: CM7.
[Captivate Android Development] mcala:
Sometimes the device specific site goes down. #176 didn't have any changes but #177 does!
[Captivate Android Development] tiuk:
I've personally found with undevolting i use practically no battery when the screen is off, ie. less than 10% over the course of a few hours.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] makelegs:
Anyone have any feedback regarding the usefulness of THIS CHANGE to /data/data capacity management? If it's even remotely effective, I'll give it a thumbs up on gerrit to try and help it get merged into the official builds.
[Captivate Android Development] Aus_Azn:
What formats does the emmc slot support? I was trying to get my phone to recognize a FAT (not FAT32) microSD, but it didn't even see the card. Do I have a problem with my external SD slot or is it a software/kernel problem?

I'm not really prepared to flash to Samsung stock just for this...
[Captivate Android Development] sixstringsg:
The emmc slot should support everything that the phone supports. You could even run ext4 on it if you so chose.
[Captivate Android Development] sixstringsg:
Theoretically, it should help. I can't test, since I don't ever have /datadata issues, but if it works like it says it does, then it should help.
[Captivate Android Development] makelegs:
Do you keep a low # of apps on your phone? or do you employ an a2sd alternative solution? I've seen the /datadata issue occur (I think) where everything pretty much locks up until apps are moved. Short of using 3rd party a2sd methods, which I gather many are reluctant to do, it seems the native a2sd would be the only other alternative, which most agree has its own drawbacks.

I just hate not being able to personally provide any feedback on that pick :eek:
[Captivate Android Development] sixstringsg:
I wouldn't say low, I have 162 user apps. I've just never had any /datadata issues, but granted I keep my eye on it.
[Captivate Android Development] makelegs:
I've always wondered how S2E works on captivate, but I've never heard from a user of it. Works well for me, all things considered. I have 111 user apps. In my case, they would NEVER "fit" without an a2sd option.
[Captivate Android Development] r3ferrei:
I would like to see this change implemented. I've hit the datadata wall many times. Its annoying getting force closes (disk io exceptions) and having to manually clear caches. It would be nice to have the system do it for me.

For some things, app2sd has no effect since relatively large library files are stored on datadata so that starts to eat up space.
[Captivate Android Development] makelegs:
Have you tried it out, yet? If so, can you tell if it actually "helps"??? If not...would you please? :)
[Captivate Android Development] r3ferrei:
Pardon my ignorance but is it in the current nightly? I'm on 177.

If not, how do I go about enabling it?
[Captivate Android Development] makelegs:
Sorry...I forgot to mention that it's in my signature. The icon links directly to newest Kang for captivate. Treat exactly as you would any cm7 nightly build. Additional included features are listed in the directory at the far right side of that page. ;)
[Captivate Android Development] r3ferrei:
Thanks. Ill give it a shot. Right now I'm 30mb free on datadata. Should take a gameloft game or two to fill it up (thanks gameloft with your libs stored on datadata). Ill see if it recovers from a full state gracefully.
[Captivate Android Development] makelegs:
Thanks. That's the kinda feedback we need!
[Captivate Android Development] cesierra:
Does PPTP VPN work on this Rom?

Sent from my Atari 2600
[Captivate Android Development] r3ferrei:
I installed a bunch of apps from my titanium backups and got down to 21mb free. I was actually surprised by the low phone storage alert since it's the first time I've seen it. It appears to be working ie it recognized low storage on my datadata partition. Now through regular use caches should build up triggering a cache clear (if I understand the change correctly). Ill see how it goes over the next few days.
[Captivate Android Development] CalvinL:
I have the Nightly 177. Battery life is still pretty bad. It drains 3% on standby per hour.

I use Go Launcher and I don't have anything/very little syncing.

Is this just how bad the battery life is supposed to be? I've been using the GS2, so I don't even remember how Captivate is supposed to behave.

I don't use any Task Killers.

I want to make sure there are no bugs before I sell the phone for $.

Also, when I charge the battery, it never seems to reach 100% so I can't calibrate it. It just reaches 99% and then stops.

Is it perhaps an issue with the way I installed it?

I used SuperOneClick, downloaded CWM, put update file into sd, downloaded Cyanogenmod 7.0.1 RC from CWM, and then put the Nightly in the sd and installed it.
[Captivate Android Development] gstern:
Changelog for upcoming nightly = GIGANTIC LIST!!!
[Captivate Android Development] Caz666:
oups...I thought it was a Kingston, but it seems to be an adata class 10, 32GB. I got it from ncix.com
[Captivate Android Development] shaolin95:
A specific model number would be great to have. probably there is only one but want to make sure.

Thanks!
[Captivate Android Development] makelegs:
Yup. It was a serious merge party last night!! The /data/data change was merged along with a bunch of other stuff, too.

Already built with miui battery feature (which may never get merged at this rate)

edit: if anyone flashes the Kang, lemme know if there is a soft reboot when unlocking with middle ring. It was merged along with another change which previously caused this behavior. If so....expect the next nightly to do the same.
[Captivate Android Development] mcnutty:
You should upgrade to at least 7.1 instead of the RC build. As for battery, CM shows battery more accurately than others by returning the actual value instead of the averaged value.
[Captivate Android Development] makelegs:
Middle Ring Unlock SNAFU

For anyone who has encountered or is concerned about the current SNAFU with the middle ring unlock....a patch will be submitted, soon. I would advise not to even enable it for now.
[Captivate Android Development] Caz666:
I could not find a manufacturer model...but here is exact link of what I bought:

http://ncix.ca/products/?sku=62042&vpn=AUSDH32GCL10-RA1&manufacture=AData Technology
[Captivate Android Development] shinobi26:
I'm not sure if this has been posted but someone please pass this along to the higher ups of CM (if they don't already know).

Android 4.0.1 sources have been released.

goo.gl/8ISOs

Edit: woooohooooo!
[Captivate Android Development] zmore:
EDIT: I removed my SD card, put it in a card reader, and it mounted fine. Also ran a "fsck.vfat -r /dev/sdd1", which found a single unrelated music dir error to fix. Then, put it back in my phone, and... it's fine. Odd.

---

I just updated to 179 from 174 and noticed that I can no longer mount my external 16GB SD card at /mnt/emmc. Anyone else running into this, or is it just a coincidence that my SD card decided to die today?

D/VoldCmdListener( 156): volume mount /mnt/emmc
I/Vold ( 156): /dev/block/vold/179:9 being considered for volume sdcard
D/Vold ( 156): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/StorageNotification( 325): Media {/mnt/emmc} state changed from {unmounted} -> {checking}
I//system/bin/fsck_msdos( 156): ** /dev/block/vold/179:9
I//system/bin/fsck_msdos( 156): Invalid signature in boot block: aa51
I/logwrapper( 156): /system/bin/fsck_msdos terminated by exit(2)
I//system/bin/e2fsck( 156): /system/bin/e2fsck: Bad magic number in super-block while trying to open /dev/block/vold/179:9
I//system/bin/e2fsck( 156): /dev/block/vold/179:9:
I//system/bin/e2fsck( 156): The superblock could not be read or does not describe a correct ext2
I//system/bin/e2fsck( 156): filesystem. If the device is valid and it really contains an ext2
I//system/bin/e2fsck( 156): filesystem (and not swap or ufs or something else), then the superblock
I//system/bin/e2fsck( 156): is corrupt, and you might try running e2fsck with an alternate superblock:
I//system/bin/e2fsck( 156): e2fsck -b 8193 <device>
I/logwrapper( 156): /system/bin/e2fsck terminated by exit(8)
W/Vold ( 156): Filesystem check failed (not a FAT or EXT filesystem)
W/Vold ( 156): /dev/block/vold/179:9 does not contain a FAT or EXT4 filesystem
E/Vold ( 156): /dev/block/vold/179:9 failed to mount via NTFS (No such device)
E/Vold ( 156): Volume sdcard found no suitable devices for mounting :(
D/Vold ( 156): Volume sdcard state changing 3 (Checking) -> 1 (Idle-Unmounted)
I/Memory ( 1273): Received storage state changed notification that /mnt/emmc changed state from unmounted to checking
I/Memory ( 1273): Received storage state changed notification that /mnt/emmc changed state from checking to unmounted
I/StorageNotification( 325): Media {/mnt/emmc} state changed from {checking} -> {unmounted}
D/VoldCmdListener( 156): volume shared /mnt/sdcard ums
D/VoldCmdListener( 156): volume shared /mnt/emmc ums
[Captivate Android Development] tiuk:
Mine mounted alright (also 16gb)

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] comdei:
Anyone have the problem of gallery constantly draining battery? it keeps the phone awake for hours...

Also whats a good radio? JK4 sucks
[Captivate Android Development] shaolin95:
Thanks mate.

I see model # AUSDH32GCL10-RA1

I will give it a shot :-)
[Captivate Android Development] bveditz:
I see part of the difference there... My (non-working in CM7) Sandisk 32gb was only $35. :)
[Captivate Android Development] makelegs:
Middle Ring Unlock patch

Compiling, now, with the middle ring unlock patch to (hopefully) solve the reboot issue. If anyone wants to help verify the success or failure of the patch, feel free. Build will tweet when uploaded.
[Captivate Android Development] z28james:
My friend was having that problem on his vibrant. He said he had to disable picasa syncing.
[Captivate Android Development] JoshJ22:
Is it just me or did this latest nightly (179) give a major performance boost? My phone is running faster than ever
[Captivate Android Development] airtower:
There was a ton of commits in 179, most of which I don't understand but surely there's a bunch of copious stuff in there.
[Captivate Android Development] comdei:
i ****ING LOVE YOU:eek::eek::eek::eek::eek:
[Captivate Android Development] tiuk:
I think google must have added that very recently, I'm sure i had never seen it until a week or two ago (not that i look in there very often, mind you).

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] simple man:
I agree, my phone has never ran so good/fast/smooth! This is how a handset should run. Great work all involved! :-D
[Captivate Android Development] Aus_Azn:
Hmm? No build today?

I don't really want to put a day-old build on my phone... :P
[Captivate Android Development] br123:
So was mine! and it also doesn't work in CM7, but other roms are fine with it.
[Captivate Android Development] kimocal:
I tried that 32 GB Class 4 1SaleADay deal card and didn't have any luck. So I returned it for a refund.

Anybody have any luck with the Sandisk 64GB MicroSDXC card in CM7? I was running CM7 nightly 172 but that didn't seem to like that card. I then tried the latest nightly today (179) after Odin'ing back to Froyo then doing a fresh install of CM7 but nothing I tried could get it work. The phone would format the card, then freeze during the card check. I even let it sit for 3 hours to see if it was just thinking really hard but no luck getting past the freeze.

So after reading the NZ Android post again it mentions using a Darky Froyo ROM in the Galaxy S that works with this card. So I DL'd my last favorite Froyo ROM (ApeX 5.3) got it up and running and it sees and formatted the card fine.

TL_DR...Anybody else using the Sandisk 64GB MicroSDXC successfully with CM7 nightlies?
[Captivate Android Development] Caz666:
So this is some elitist move by the CM team to weed out cheap memory cards?

:)
[Captivate Android Development] readitodie:
Is there an option to change pull down bar menu?

I only have 4 icons( wifi, bluetooth, gps, volume).

I am on the latest nightly. (179 i believe)
[Captivate Android Development] skyxliner:
I would say the 179 nightly is running better than the stable builds right now. No lag.
[Captivate Android Development] RichMD:
Settings, Cyanogen Settings, Interface, Notification power widget, widget buttons > select the ones you want and then you can change the order under widget button order.
[Captivate Android Development] simple man:
CM settings-interface-notification power widget-buttons. There you can pick what buttons you want, and in the order you choose.
[Captivate Android Development] simple man:
You beat me to it! ;-)
[Captivate Android Development] makelegs:
Version bump to 7.2.0 rc0
[Captivate Android Development] littlewierdo:
Im sure I missed what happened as I have been away for a couple of weeks not following the development of CM...

A couple of quick questions...

1. Google Navigation not only is unable to locate me but also hard crashes when I try to exit the app (yes, I tried clearing the data for Maps).

2. When receiving a call while on another call, my phone crashes and both calls (the current call and the incoming call) are dropped.

3. Once again, Im unable to stream phone calls to my BT FM transmitter.

Im running CM nightly 179, a few of these problems starting showing up and Ive just been updating to later builds hoping that these problems would be addressed (I think I started noticing them around Nightly 175).

I noticed that a few others are having similar problems when reading the comments in Rom Manager...

Oh, and Google Navigation, I might be able to fix this by rolling back on the maps update done a week or two ago, it seems this may be part of the problem...
[Captivate Android Development] nbell13:
Nightly 179 broke my USB connection... Will try to re-install Nexus S drivers tonight when I get home from work, see if that fixes the problem. No issues until then.
[Captivate Android Development] ghost13:
ok i installed cm7 for the first time a few weeks ago and i love it. now i want to try the 179 nightly build. if i update from recovery mode will i loose all my apps and data on my phone? sorry for stupid noob question. came from wm 6.5.3:)
[Captivate Android Development] nbell13:
No, just make sure to wipe the cache and dalvik cache. No need to factory reset, all apps/data will remain intact. :-)
[Captivate Android Development] nkrick:
The Picasa-Gallery sync has been part of Android since Eclair (2.1) and has been part of CM since before started using it back in March. Nothing new there.
[Captivate Android Development] loraque:
I had assumed they were referring the the Picassa option in MENU-ACCOUNTS-SETTINGS where you find gmail and calendar sync options. That is new for me recently, certainly not since way back in March.
[Captivate Android Development] ghost13:
should i wipe the cache first or the dalvik cache first? does it matter? thanks!
[Captivate Android Development] Gromlakh:
It does not matter.
[Captivate Android Development] ghost13:
cool. do i need to do a nandroid backup? what is that? saw it on the first page.
[Captivate Android Development] Gromlakh:
Yes, do a nandroid backup. It will be the easiest way to restore your current working configuration if something goes wrong and/or you decide you don't like the latest nightly.

Boot to CWM, backup/restore -> backup. I believe it will dive straight into a full and complete backup of your phone in its current state at that point. When it's done, flash the nightly. If it doesn't work out for you for some reason, head back to CWM and hunt around in backup/restore for the restore option. I've personally never had to use it.
[Captivate Android Development] jmtheiss:
Just as a follow up - I don't know if it matters with CM7's nightlies, but nandroid usually requires you to be on the same rom you did the backup on. So, if you're going to flash a new nightly, you may want to keep a copy of your current nightly available to flash back to first, then restore the nandroid.

Unless CM7 doesn't work that way, then ignore what I just said.
[Captivate Android Development] ghost13:
ok so i just did the backup. next is wipe partition cache and then wipe dalvik cache. then update to new nightly. ct?

thanks again guys! after the first time i'll be good to go for future updates:)
[Captivate Android Development] Gromlakh:
Correct.

And I could also be wrong, but I don't think a Nandroid restore will require you to flash back to the same version of CyanogenMOD you were on at the time you made the backup. I'm fairly confident you could just restore. You'd almost certainly have problems if you were on, say, Apex (i9000 ROM) and tried to do a Nandroid restore for a CM7 backup from there, but I think you'll likely be fine to just do the restore.

That being said, I always keep a copy of the latest stable files on my SD card anyway just to be safe. ;)
[Captivate Android Development] ghost13:
WORKED LIKE A CHARM:) thanks guys!!! on new nightly build 181
[Captivate Android Development] Gromlakh:
Woohoo!

omg10char
[Captivate Android Development] nimper:
As I understand it, as long as you're on the correct CM7 partition layout and recovery version, nandroid backups will restore regardless of which nightly you are on.

edit: beaten
[Captivate Android Development] johnhazelwood:
I noticed android os is #2 on my battery use list at 20% after flashing 179.
[Captivate Android Development] zj4x4:
Is there something special about the email.apk that comes in CM7? I'm not able to install any other email.apk, and none of the fixes in other threads/forums (wiping dalvik and cache, fixing permissions, etc.) seem to help. I just get "Application not installed" every time.

Any ideas?
[Captivate Android Development] nimper:
Make a backup copy of the existing Email.apk and then copy the new one into /system/app. You can't just install system apks at will.
[Captivate Android Development] bveditz:
So, at least we narrowed it down to the model, I'm pretty sure that's where my non-working 32 gig card came from also. It does work on a PC and it gives pretty good speeds when I tested it, so I didn't return it... I'm sure i'll find a use for it somewhere, just not with cm7.

Hah! That's the theory I have about really bad Android App ports... some apple aficionado works at those places making crap in order to get people to convert to iOS. :)
[Captivate Android Development] nkrick:
Menu | Settings | Accounts & Sync | "google" | Sync Picasa Web Albums is the only place I am aware of the option ever having been. I disabled my Picasa sync way back in the original Samsung firmware and it has been disabled ever since. While I suppose it is possible that it was missing from CM until recently, I don't know why it would have been. My memory is that the current location in CM is the same location that I disabled Picasa sync from on Eclair.
[Captivate Android Development] zj4x4:
If I replace Email.apk and reboot it doesn't show up anywhere except in the file system. I used to swap email apks all the time before CM7 using this method. Should I follow a different process?
[Captivate Android Development] RichMD:
FYI that from what I have read/seen the dalvik cache is part of the overall cache.
[Captivate Android Development] sixstringsg:
Partially correct, yes. Part of the dalvik-cache is stored in /cache, but not all of it. On that note, it is irrelevant which order you wipe them in.
[Captivate Android Development] skyxliner:
notification status bar

I'm on build 179 right now and I have brightness and sound in my notification status drop down bar.

when I turn them on, they stay on and get stuck. They don't change to off or anything else anymore.

Anyone else have this problem?

I'm updating to 181... hopefully that problem will go away....

edited: nvm i didn't change the extensive settings at the bottom so it was only set to one.
[Captivate Android Development] JiroPrinz8:
CM Server seems to be down, anyone got a mirror of 181..?
[Captivate Android Development] CptTwinkie:
+1

Anything newer than 179

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] tiuk:
http://goo-inside.me/cm/captivatemtd/nightly/cm_captivatemtd_full-181.zip

For future reference they're also mirrored at kanged.net

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] mcala:
Google blocking CM7 device page?

I am all of a sudden unable to browse the Captivate device page over @cyanogenmod.com.

Conspiracy maybe?

I am getting this:

http://safebrowsing.clients.google....www.cyanogenmod.com/devices/samsung-captivate

Advisory provided by	Google

Safe Browsing

Diagnostic page for cyanogenmod.com/devices

What is the current listing status for cyanogenmod.com/devices?

Site is listed as suspicious - visiting this web site may harm your computer.

Part of this site was listed for suspicious activity 1 time(s) over the past 90 days.

What happened when Google visited this site?

Of the 4 pages we tested on the site over the past 90 days, 2 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 2011-11-17, and the last time suspicious content was found on this site was on 2011-11-17.

Malicious software includes 2 exploit(s). Successful infection resulted in an average of 4 new process(es) on the target machine.

Malicious software is hosted on 1 domain(s), including blameincise.org/.

This site was hosted on 1 network(s) including AS13335 (CLOUDFLARENET).

Has this site acted as an intermediary resulting in further distribution of malware?

Over the past 90 days, cyanogenmod.com/devices did not appear to function as an intermediary for the infection of any sites.

Has this site hosted malware?

No, this site has not hosted malicious software over the past 90 days.

How did this happen?

In some cases, third parties can add malicious code to legitimate sites, which would cause us to show the warning message.

Next steps:

Return to the previous page.

If you are the owner of this web site, you can request a review of your site using Google Webmaster Tools. More information about the review process is available in Google's Webmaster Help Center.

Updated 7 hours ago
[Captivate Android Development] johnhazelwood:
Definitely had the android os bug come back in build 179 (not sure how that happens), but trying 181 to see if it's fixed.
[Captivate Android Development] iphone=closedsystem:
It seems to me that from 176+ I have had issues with activity launcher and Google sign ins showing me a verify log in Captcha any ideas why? ... Love CM7 through and through though. Thanks for all the hard work. I will be donating soon.

Quackafella Records INC