yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] punshkin:
i wonder if cyanogenmod 9 will keep all the lockscreens that are in CM7?

i dig the sliders more than the circle one
[Captivate Android Development] airtower:
Anyone been able to figure out how to get OC/UV settings to stick through a reboot?

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

I hope the devs are able to figure out how to add more elements to the stock lockscreen. I dug the ring lock on CM7 because I could configure it to unlock directly to 4 apps of my choosing. Accessing the camera directly is nice, but I rarely use it.
[Captivate Android Development] zmore:
Nothing in /system/etc/init.d is being run yet. (and you have to manually mkdir it, so, I'd assume this is on the todo list. I'd also note that some other ics roms have listed "init.d support" as a feature...)
[Captivate Android Development] nakedninja42:
SetCPU has been working for me
[Captivate Android Development] StrykerGT:
I tried putting the card with the phone turned off. After 3 or minutes after the telephone boots up I get the error on the notification bar "Removed SD Card"
[Captivate Android Development] pixbuf:
I thought I tried that before but couldn't tell anything from it. I went back and found, lo and behold, k-9 mail was taking up 53MB!! I deleted it and now things are fine, except I need to find another mail app: the built-in one sucks.
[Captivate Android Development] airtower:
That's what I figured. Thanks.

SetCPU implements OC/UV boot settings differently (without using init.d) than voltage control.
[Captivate Android Development] radraz:
managing contacts in ice cream sandwich

im having a hard time figuring out the contacts in ics... i cant delete more then one contact at a time and cant hide contacts with no numbers.

also, when i receive texts, i only see their number, no names. anyone else getting these errors as well?

thanks!
[Captivate Android Development] dman1x:
Try rebooting the phone with the card in like the post you quoted said.
[Captivate Android Development] technobabble042:
I get the same issue, even if I reboot with the SD card in, if I insert the SD card post-boot, during-boot, or while the phone is off. Haven't found a fix yet, let me know if you do.

(I also had the same issue with CM7.)
[Captivate Android Development] StrykerGT:
I tried but I still have the same problem.
[Captivate Android Development] jeet49:
I got both - name and number. I am on ICS 5.
[Captivate Android Development] iphone=closedsystem:
Build 6, after flashing form recovery, build 5 >>> build 6: "random offset:0xf7"

Also, cannot synch with gmail for contacts, have tried restoring a nandroid, wiping factory, etc, and still same issue. Also, the market place is missing and I cannot reinstall it from the browser. may do a full wipe and restore when I get to my Comp at home.
[Captivate Android Development] nakedninja42:
Is there a difference using voltage control and init.d than using SetCPU?
[Captivate Android Development] baghera1979:
I dont know of the specifics but from personal experience I can say voltage control has worked better for me

sent from your inner ear. ..that's right. ..look behind you
[Captivate Android Development] everest.deth:
You my friend need to start reading OPs and FAQs, the random offset is nothing to be afraid of. It is merely a security feature being implemented in ICS.

As far as your Gmail not syncing and market place being missing, I don't want to assume, but it seems like you may need to reflash the Gapps (if you didn't then you definitely should now!).
[Captivate Android Development] Lollipop_Lawlipop:
SetCPU runs as a service in the background, while Voltage Control does not. You can save a bit of ram by using VC. That said, SetCPU has frequency profiles you don't get by using Voltage Control. SetCPU has no IO scheduler setting though. Personally, I use both. Once support for autoexec scripts gets added though, I don't plan on using VC.
[Captivate Android Development] johnhazelwood:
Agreed, I was just going to recommend Gapps and OP points to FAQ which points to offset :)
[Captivate Android Development] airtower:
Effectively, no. But as lollipop noted, you will save a bit of RAM, CPU, and battery by implementing the control through init.d (voltage control method) versus running an independant service (setCPU method) I ran something, either a ROM or kernel awhile back that didn't get along with setCPU so I came to prefer voltage control.
[Captivate Android Development] _jeremiah_:
I just flashed build 6 about an hour ago, and I've come across a few things.

I have two questions:

1. Is there any way to change the camera shortcut on the lockscreen?

and

2. How can I get my People app to display JUST my SIM contacts? When I take off the gmail ones, i get nothing, and everytime I import contacts from SIM, it just puts another copy to the Google account.

Any help is appreciated, and I absolutely love the work Teamhacksung is doing. Keep it up!
[Captivate Android Development] gangpe:
No sd errors anymore...for now

Hey technobabble042 etal,

I had the same problem this morning (in fact, I PM'd you hoping you had a solution for this).

I ended up creating a nandroid backup, wiping everything, then trying out the SD card again. I left the card in , let it sit for about 30 mintues to see if I'd get the same error. Once an hour had passed, I restored the nandroid backup, and I haven't had errors since (it's been close to 4 hours now).

The only two things that would make this perfect for me now would be to be able to play my videos (tried rockplayer and a few others; no dice), and to have

the external SD card behave the same way it did in GB (gonna try pointing the external_sd folder to emmc and see if that will do it).

You devs are rockstars and you know it.

Thanks for getting me some sweet sweet ice cream sandwich!

*Update*

After a reboot, I'm beginning to see the errors again. It was good while it lasted.
[Captivate Android Development] nakedninja42:
I used VC a long time ago and was usually unstable for me, I couldn't figure out if my phone did not like OC or the kernel. I stuck to stockish kernels by using xcal when gingerbread first dropped but eventually stayed on I897 stock gingerbread. Started using tegrak so I know my phone is stable at 1.3. Got use to using SetCPU for OC on my GTab10.1 so I decided to use it on my phone.

Good point on using init.d instead of SetCPU in the background, maybe I'll try VC again when there is support.
[Captivate Android Development] pawitp:
Next BUILD will have a fix for those having troubles with their external SD.
[Captivate Android Development] skynet11:
I use an app called Control Freak; it allows for GPU overclock, but only on supported kernels (the stock ICS kernel does not support it, but Glitch does). Still, I've found the interface to be more intuitive than Voltage Control.

Has anyone seen John Connor?
[Captivate Android Development] goob1284:
Uh, do you know how to keep the voltage settings to stick through reboot?
[Captivate Android Development] yguns76:
I flashed Build 6 on Friday and noticed battery drain quicker than on build 3. For whatever reason, the battery drain has dropped off marginally today (monday). This is just an observation, not scientific analysis.

Great ROM.
[Captivate Android Development] treo750ii:
Can't do that at the moment
[Captivate Android Development] airtower:
No init.d no sticky Voltage Control settings. Makes me wonder why they didn't leave the old implementation in place. While i prefer init.d, the VC service worked fine.
[Captivate Android Development] Lhernandez0105:
Someone posted it a while back. I just check and it worked on build 6 for me just give script manage a min after boot.

Download script manager

Save as boot setting in voltage control

Go to /etc/int.d/s91voltctrl with script manager

Set it to run as root and run at boot

Save

Should be good after that. The s91 file might be different for people but its whatever file VC tells you it creates.
[Captivate Android Development] JBM12G:
Not sure if this has been asked before, sorry if it has, but why do some of my apps have gingerbread styled menus and sliders?
[Captivate Android Development] skynet11:
You might have seen my post before I thought better of it and removed my comment about CPU settings not sticking on reboot. It had already occurred to me that there was a way to make your settings stick. However, what the stock kernel does not support, as I stated before, is GPU overclock.

Has anyone seen John Connor?
[Captivate Android Development] RootTheMachine:
The OP says there is hardware acceleration but no hardware composition

Sent from my ICS i897 Captivate
[Captivate Android Development] skynet11:
I'm sorry I meant GPU overclock.

Has anyone seen John Connor?
[Captivate Android Development] MikeyMike01:
It's backwards compatible. Your apps will have to be updated to use the ICS. Voltage Control and AndroIRC for example have been updated.

Sent from my SGH-I897
[Captivate Android Development] aryn.galadar:
Reboots?

OK, first of all, this ROM is pretty awesome - great job!

Everything that should be working is working for me, with one exception: my phone keeps rebooting (not a bootloop, just every now and then). It's driving me nuts.

I've been trying to pin it down, and it seems that it only reboots after it's been sitting for a while with the screen off, not doing anything. Maybe something happens when it tries to deep sleep? It has NEVER rebooted when I'm using it.

I've tried flashing, reflashing, factory resets, data clears, cache clears, back to stock - just about everything I can think of.

Any ideas?

(This is on build 5 and 6, btw)
[Captivate Android Development] nkrick:
Some Captivates manufactured before Nov 2010 have a hardware issue that can cause reboot, sleep death, and/or charge death. You can either try to get AT&T to replace your phone (there was an internal AT&T notice about the issue last year) or you can try the various fixes/workarounds used successfully by others. The one that I am aware of is to increase your minimum CPU speed from 100 Mhz to 200 Mhz which seems to work for most people. If that doesn't work, start searching around, there have been many posts and discussions about the problem and various fixes for it.

There is a "software" fix in every Samsung/AT&T ROM since ~JLx. I have never heard of anyone ripping apart the ROMs or source to try to figure out what the fix is, but it is probably a change in min frequency or voltage. It is quite possible that newer Captivates suffer the same hardware flaw, but since the software fix was implemented Dec 2010, newer phones never suffered the problem on Samsung/AT&T ROMs.

Edit: Since many people using this ICS ROM have never used any AOSP ROM before and so have never encountered this issue (the same issue exists in CM7 for the same reason), perhaps the OP should be updated to tell people how to deal with this issue. I have seen the problem reported at least 3 or 4 times in the last several days.
[Captivate Android Development] jeet49:
I have seen this. During the first run the media scan takes lot of battery power. Do you something "MEDIA" in battery usage list?
[Captivate Android Development] KappaG9:
Flashed BUILD 6 yesterday, found one little bug. When adding a second google account, google photos sync even if the box is unchecked (deleted account and re-added). Not a big deal, just a little annoying for me.
[Captivate Android Development] nbell13:
Annoyed me as well. Still had to come back to this though, after a brief backtrack to CM 7.1... Lol
[Captivate Android Development] ih4ckback:
I've been running build 6 for a few days now and it's been running great.

Super fast, pretty stable, and just gorgeous haha.

My only 'issue' is that the battery seems to not be lasting very long.

Seems like I have to charge my phone more often that I've had to in the past.

Anyone else experiencing sub-par battery life?
[Captivate Android Development] picklesnickles:
Telling me I have no contacts saved on my sim card. This is a big deal for me. Does anyone know how to possibly fix this? Also how do you get back into CWM recovery once I'm on ICS

I really appreciate the help
[Captivate Android Development] Darth_Munkee:
Found my first thing to complain about, and probably the only thing unless Facebook never starts working. I'm on Build 5 and I can barely hear the turn by turn with Google maps navigation. Pandora and Amazon mp3 are nice and loud through the phone speaker. And since I know someone is going to think it, yes I tried turning the volume up.

Sent from this fully armed and operational battle station.
[Captivate Android Development] everest.deth:
Hit and hold the power button, select reboot, then recovery ;)
[Captivate Android Development] TheSoaresan:
Battery life is pretty much the same as it was in gingerbread. I charge my phone once every two days and I get an average of 3.5 hrs of display time with wifi on always.
[Captivate Android Development] nbell13:
Save your contacts to your google account and you won't have to worry about it

---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------

There is no volume control for system volume in either CM7 or ICS... i.e. what I think happens is that if you turned 'system volume' all the way down in your Samsung-based ROM before flashing either CM7 or ICS, it stays turned down and there is no way to turn it back up. My camera shutter and other "system" sounds were barely audible the first time I flashed CM7 (I had turned them all the way down in the KI2 leak to shut up the stupid boot animation), but when I flashed back to stock and did it again, they were easily heard again.
[Captivate Android Development] Spritely:
Are you using a text battery indicator or anything similar? I've always found the graphical one to be very misleading. It looks much more empty than it really is.

In any case, I'm currently at 40% after almost 15 hours (about 4 or so in airplane mode) and 3 1/2 hours screen on time, so the battery seems same as always for me.

Overall Build 6 seems to be doing well for me, big thanks to everyone involved. :)
[Captivate Android Development] atinm:
Crap - bad build 7 - will upload again in a few minutes.
[Captivate Android Development] RockRatt:
Let us know when your ready. I just cancelled the download. Thanks Atinm

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] n0stalgia:
Such great progress in this ROM! Very unlike the early Gingerbread ROMs.

However, is there any indication as to when the source for Crespo ICS will be released?

Also, just a suggestion, perhaps it would be nice to have this ROM's non-vanilla features in the OP, such as Voodoo fixes, OC/UV, LED notifications, etc.
[Captivate Android Development] atinm:
Ok, build 7 (had included bad kernel modules earlier) available in OP now. Check MD5 sum to make sure you have the correct build.
[Captivate Android Development] Aphex13:
Woot! Build seven. Here we go again. Glad to see that the market doesn't download to /datadata any more. Maybe this will fix a bunch of the low storage space problems.
[Captivate Android Development] alkiter:
Nice work on Build7! Any change of getting TV Out also for Captivate?
[Captivate Android Development] everest.deth:
It was added :confused: through the Galaxy S Device Settings
[Captivate Android Development] zmore:
Yay - Build 7 also brings with it a functional - if not fully-complete - ICS Launcher preference menu (not worth mentioning in the changelog? :)

Persistent google search bar: HIDDEN.
[Captivate Android Development] alkiter:
I saw that on the OP, but I must be too excited for getting Build7 and I don't see it. Another clue?
[Captivate Android Development] whyareyou:
From the op
[Captivate Android Development] alkiter:
Geez, thanks, I completely missed it....

Yea, gotta run out and get a cable. Can't wait to see Atari Lunar Lander and Pong on big screen!
[Captivate Android Development] Holmes108:
Oh baby we have KTLO!!! Woo hoooo
[Captivate Android Development] technobabble042:
Is it just me or is Build 7 missing Superuser, etc? I checked the MD5 sums, and they appear to be the correct version.

Edit: And it erased all my TiBu backups. I'm gonna re-download and try again, I suppose.
[Captivate Android Development] airtower:
Same here, I have no root functionality. TiBu backups, and the rest of the sdcard content seem to be in place.
[Captivate Android Development] speedy_11:
Anyone else getting a random red outline when doing certain operations like when i turn off and on wifi it happens? Im on build 7 never happened on older builds. Took a few tries to get the screen shot at the right time.
[Captivate Android Development] Aphex13:
I'm getting the red screen thing as well. My super user is also missing. I think I'll roll back to 6 while this gets sorted. I'm not complaining. I just don't know enough to fix this myself.
[Captivate Android Development] NCXC:
Yeah me too... But I kind of like it
[Captivate Android Development] zmore:
The "red border" is a developer option called 'Strict mode' that lets you know when apps are being naughty by not doing work that would block in a background thread. And, yeah, unfortunately it appears to be stuck on, because toggling it didn't disable it.

---------- Post added at 04:20 PM ---------- Previous post was at 04:07 PM ----------

No need to go back to build6 for superuser. Just reinstall it from market, run it once, and you're good to go.
[Captivate Android Development] technobabble042:
Ahah! Didn't know you could just install from market on this rom. Thanks, fixed it.
[Captivate Android Development] jeet49:
Tried twice with no luck so far with TiB.
[Captivate Android Development] Spritely:
You've tried what exactly? Your post and the one you're replying to say two different things. Go to the Android market, search for superuser and try installing it from there. Then open it. See if that fixes the issue.

(For the record, I'm not on Build 7 but if it worked for someone else it should work for you also, unless something else is actually wrong.)
[Captivate Android Development] nbell13:
Worked fine for me. Also my backups are intact.
[Captivate Android Development] jeet49:
I am addressing to the same post where TiB issue is discussed. Yes, superuser install fixed it. Something new for Build 7. Prior to this TiB install worked w/o pre-requisite install of superuser.
[Captivate Android Development] alkiter:
Has anyone gotten TV Out to work? It detects cable connection, but TV shows No Signal. I checked the cable, selected correct TV System, enabled TV Out. Both audio channels output, but nothing comes out on video.
[Captivate Android Development] speedy_11:
superuser (root better to say) has always been included, you probably never took notice of it. It probably got left out by accident. tibu would have never with out root which equals having superuser
[Captivate Android Development] macropp:
AT LAST!!!! WIFI WORKS!!! THANK YOU SO MUCH ATINM!!! but I too get the red square:-(
[Captivate Android Development] johnhazelwood:
I've noticed on reboot I have two things that typically happen 1) Accounts and Sync seems to revert to disable. I turn it back on in the UI and it's fine. I'm not 100% sure it's actually off..might be a UI thing. 2) Pulse Lights turn back on during reboot..I disable them, but when I reboot it's back on again.
[Captivate Android Development] brandon_L:
Anyone else having the phone reboot into recovery when just selecting it to reboot?
[Captivate Android Development] speedy_11:
Happens to me as well, i thought i hit recovery by accident the first time, but i just test aging and i got recovery. pretty odd not too big of an issue though
[Captivate Android Development] Beny The Kid:
As someone already pointed out, it's probably always come pre-installed on your other custom ROMs. TiBu has always (for a long time at least) needed superuser permissions (root access). Quick trip to the market and it's fixed for all.

As for the red square, I have only just done it myself but it seems if you toggle ON strict mode in dev settings, it actually turns it off. Minor glitch for the next build.

Thanks Team Hacksung for the awesome work.
[Captivate Android Development] nbell13:
i turned it off, and it was still on. so then i turned it "on", rebooted, and it was still on, and then i turned it off, and it seems to have gone away.
[Captivate Android Development] atinm:
Bah . . . I'm going to have to push another build, there is something messed up on my machine and I haven't had time to actually debug it all day. Going to remove Build 7 for now.
[Captivate Android Development] dabels1961:
low on memory message that won't go away

I saw in previous posts that low memory message was datadata issue but I moved a bunch of apps and cleared cache but the message will not go away.

also noticed I could not find OI file manager and I could not get to market to

download terminal emulator to do a df ....
[Captivate Android Development] jeet49:
No worries. Take your time. Thanks for all your efforts.
[Captivate Android Development] tiuk:
If we've already installed should we restore build 6, or flash the next build over 7?

Sent from Captivate, teamhacksung ICS.
[Captivate Android Development] RootTheMachine:
Has anyone else had issues where Google Accounts constantly asks you to validate your account repeatedly on build 6? Also, sometimes when you send a message in messaging it will say "sending" forever even if it actually sent
[Captivate Android Development] devi59:
When the new build 7 comes out can we flash over the current 7 we installed?
[Captivate Android Development] nimper:
This happens to me if I ever use 3G, so I just turned mobile data off completely.
[Captivate Android Development] atinm:
You can flash back to build 6, or wait for build 7 and reflash it on top of the broken build 7 if you've already flashed it. Hopefully soon..
[Captivate Android Development] wildnux:
Mine goes to recovery too.

Btw when I remove Google search bar, the space is still empty there... I was hoping the Widgets would take the space. Is it me only ?
[Captivate Android Development] iluretar:
actually the widgets do go up a bit but they don't fill the whole space
[Captivate Android Development] Kaik541:
Build 7.1

This is what Build 7 was supposed to be (atinm's bulid environment is mucked up right now). It has simply been labeled 7.1 simply to prevent confusion. Same fixes/updates as in the Build 7 OP list. Also includes T9 dialing (not sure why that isn't in the list to begin with though). The OP will be updated to reflect this when atinm gets home from work.

ROM BUILD 7.1: tux-head.net / faramir.eriador.org (md5sum: 491f0ae9324d20d4c4ef8cb7b6536219)

Google Apps: v5.1: MultiUpload / tux-head.net (md5: 87415730a1db2e90d3588bc895f239e5)
[Captivate Android Development] atinm:
Updated the OP with the 7.1 build (renamed to 7.1 to fix confusion). Thanks Kaik541! I'm cleaning out my build tree (was saving some SGS2 stuff and there was some **** that shouldn't have been there anymore in the tree).
[Captivate Android Development] pizz0wn3d:
Yay :)

Downloading now, thanks for the update!
[Captivate Android Development] Gorship:
hey!

hey guys! i ran into a bug that has forced me to move down to CM7 until i hear its all cleared up.

Bug: during a call, the voice will stop, they cant hear me and vice versa.

My equipment:

Captivate

Rogers wireless

I was running stock modem, and also tried switching to JL2 (CM/Miui version)

Much love for the devs!

Gorship
[Captivate Android Development] radraz:
can I flash 7.1 over 6 without wipe? Thanks
[Captivate Android Development] dabels1961:
Reboots into recovery even though you don't ask to. I try to download from the market and it tries the download and says it can't due to an error.

Edit: on 7.1
[Captivate Android Development] saobang3886:
Yes, you can ^^!
[Captivate Android Development] flashman2002:
Best bet would be to wipe/format and reflash. I wiped initially in CWM and I am running flawlessly atm.
[Captivate Android Development] zeezz:
Flashed 7.1 from 7, and prior to that 7 from 6. no wipe, reflash gapps right after flashing ROM. No issues at all here, really smooth.