yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zj4x4:
It reports to enforce the policies but does not. The admin can still do more advanced blocking, or in the case of using a totally different platform (Good, BES, etc.) they can simply disable Activesync altogether to block any of these clients.

Personally I ended up splurging on Touchdown after running one of these for a while because the experience is so much better. I would have used Enhanced Email but it doesn't support device encryption (yet).
[Captivate Android Development] joeybear23:
Atinm,

I have the sneaking suspicion that the sensors are all turning on and staying on when the softkey backlight is activated for notifications, and pulling the device out of sleep.

Would a logcat help? There is not an error, this is just me trying to track the time the backlight is on compared to the time Android System is clocking in Spare Parts under the sensor usage.
[Captivate Android Development] gabby131:
Nah....still same wifi error....but i got a changelof txt....i just too dumb on pinpointing the part in the file that can tell the disconnection.....i did not know that an interval on one minute can produce such log!
[Captivate Android Development] atinm:
No, a logcat doesn't have anything in it. We know about some devices not going into deep sleep - it is the same bug we've always had, and as we discover more gpios etc we can disable, we do.
[Captivate Android Development] Ben74:
i'm using nightly 13, and i can't get into download mode. i've tried every key combo in the book, and "adb reboot download". i've tried:

hold vol+ and vol- and plug in usb

hold vol+ and plug in usb

hold vol- and plug in usb

none of them work. the phone just boots normally. anyone have a solution?
[Captivate Android Development] Ben74:
might be a good idea to add that to the FAQ, or even the OP.
[Captivate Android Development] cease:
Download

Try these:

Method 1: (ADB - from recovery or normally booted with usb debugging on)

1.Open a cmd prompt/console/shell

2.adb shell

3.adb reboot download

Method 2: (KEY COMBO)

1.Remove the battery, sim card, sdcard if you have one

2.Insert the battery

3.Hold Volume Up + Volume Down + Power

Method 3: (KEY COMBO)

1.Remove the battery, sim card, sdcard if you have one

2.Insert the battery

3.Hold both Volume buttons (from i9000 just down, don't touch the power button)

4.Plug in the USB cable and continue holding both Volume buttons

I've had to use one of all three at one time or another.
[Captivate Android Development] cease:
MIC, WiFi not working and time not correct

I too had these problems. I went back to base, re-rooted, then installed Initial Build, then GAAPS, then did a restore of my Titanium Back Up of all apps and data, then Flashed 14. All is well. Battery seems good also.
[Captivate Android Development] joeybear23:
thanks for the feedback
[Captivate Android Development] SeriousBizznass:
The tags at the bottom of this thread bother me. This has been the smoothest rom I've ran to date.

Haven't flashed 14 yet, I think I'm still on 12 to be honest.
[Captivate Android Development] nkrick:
The fact that this ROM even exists bothers some of the Samsung ROM fanboys. It's all good, most people don't look at the tags and the CM developers don't want the people who add those tags to use CM anyway. They just complain that feature X from Samsung's ROMs doesn't work on CM or when will feature Y work right, etc.
[Captivate Android Development] cpk86:
Anybody have any ideas on this? I feel like it's just some stupid mistake I made somewhere (undoubtedly...).
[Captivate Android Development] grasshands:
Just updated to full14 from 05-11-2011 and all looks good, was able to install gapps via rommanager and got all my email and contacts synching again....but the provider set time is not getting my time zone correctly...I'm in EST -4, and it keeps it at 0...I've searched and see a few mentions of time being incorrect from full12 on...is this still an issue or is there a fix other than using manually set time and zone?

Thanks
[Captivate Android Development] RockRatt:
#14 has issues. You will need to download #13. If your on #14 try to make a call and the other person will not hear you at all. Also what you mentioned you would need to set the time zone, just unclick auto, then choose your timezone from the line listed as all zeros. But like I said you will need to go to #13 which works great or wait until #15 or whatever the next nightly they put out is.

Sent from My Captivated JVB Gingerbread Toy
[Captivate Android Development] SynGamer:
I'm trying to flash a different ROM (need better battery life) but every time I do it says my phone doesn't have USB debugging enabled when in fact it does...
[Captivate Android Development] Ben74:
thanks for trying to help, but as i said, i've already tried those things (btw, #2 is for recovery, not download mode). i'm quite familiar with the standard methods of entering download mode. what i'm saying is that the standard methods don't work with this rom.
[Captivate Android Development] ronii1123:
Anyone else having issues with calls on the latest build? When I get a call no one can hear me, I tried voice recording and no sound is heard during recording :(
[Captivate Android Development] BL4zD:
Yes; as mentioned just a couple posts above yours is the recommendation to roll back to #13.
[Captivate Android Development] cwgannon:
I had a similar problem here. Install the USB drivers (through Device Manager in Windows) that are included with the Android SDK, if you haven't yet.
[Captivate Android Development] RockRatt:
Have a jig on hand? That might be your only way then. I have ALWAYS just been able to have the phone powered off and Odin open. Then plug ina USB that is already connected to the laptop/desktop and download mode would come up and Odin would show it was connected. I have also used a jig at times since it is easier sometimes.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] waghoba:
anyone tried build #15? any issues so far?
[Captivate Android Development] Yaantra:
Looks like build #15 is up... Any words of wisdom (do/don't) while i charge my phone up for a flash? Going straigt from #9 to #15...
[Captivate Android Development] Smasher816:
That is controlled by the bootloaders (not flashed when installing CM7, fyi).

A jig is a 100% way. I have also had luck with this method (not mentioned).

Take out everything (battery, external-sd, sim card).

Plug in the usb

Hold both volume buttons.

While holding both volume buttons, put back in the battery.
[Captivate Android Development] Johnston212:
Are you sure about that? I'm getting complaints about not being heard clearly on calls with #13. I'm currently going through the modems to see if that is related, but I just thought I would mention the issue.
[Captivate Android Development] stuff:
Looking at the update for #15, I see a lot of changes.

Downloading #15 right now. Will make a backup for sure from now on though :P
[Captivate Android Development] NiXXeD:
So far so good. Anything I should specifically test?
[Captivate Android Development] danduv:
Since flashing 15, my display seems to have a blue tint. Anyone else?
[Captivate Android Development] mirrored:
team hacksung should just take down the 15 nightly
[Captivate Android Development] pigrew:
My display seems normal with build #15. So far the wifi seems fixed (I'm able to download a 30 MB file over 801.11g). Also, the auto date-time is showing the correct time. I'm happy with the build so far.

EDIT: I lied. wifi breaks after about 60 MB of downloading..... and even though the TZ is correct for me, I assume that it is wrong for other people since #16 is supposed to fix the TZ issues.

-Nathan
[Captivate Android Development] Smasher816:
Im gone to flash 15 soon, so i will compare.

Im pretty sure the blue tint came in 12/13 (ish). Edit: nvm, it was 6 "cm_captivatemtd_full-6.zip

prebuilt kernel and modules - color adjustments (android_device_samsung_captivatemtd)".

You can always flash a kernel with voodoo color (Platypus)

Care to elaborate why?

I know the #14 nightly sucked.
[Captivate Android Development] joeybear23:
Gonna tell us why, or do we just have to guess?
[Captivate Android Development] squishy5:
Can anbody provide google gaps. Zip

Please
[Captivate Android Development] waghoba:
just observed a funny bug on build #15. If you hold the power button while phone is locked but screen on, you can still get access to power menu. nnow is anyone else getting same error or its just me?
[Captivate Android Development] r3ferrei:
Got it as well.
[Captivate Android Development] georgem106:
Its been like that for awhile. Not sure its a bug. Anybody else ?
[Captivate Android Development] cgugino:
I think it's like that in stock.
[Captivate Android Development] Smasher816:
Its been like that on every rom I use. I do have widgetlocker though.

I count it as a feature

http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps (http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip)

You can also get it in rom manager (Download Rom->Gapps). I had to install it manually through recovery though.
[Captivate Android Development] EthanMG:
this statement is correct, im on stock
[Captivate Android Development] Neckrobeard:
Not a bug I'm pretty sure.
[Captivate Android Development] georgem106:
So far so good for #15

So far so good for #15.

One thing I noticed is the no service stays on for an exceptionally long time before AT&T shows up. Anybody else having the same issue?
[Captivate Android Development] jaysix79:
my experience is a little different... I get the ATT sign right away right after the boot when it power up.... but when I use different kernel (Kangs kernel so i can have my light sensor working) no service at all no matter how many times I do the lock and unlock....

Also what I have notice is my Wifi (signal) seem to be weaker than before. I am connected to my network with out any problem .. it could be just the icon is giving me a lower signal than what it actually is....
[Captivate Android Development] joeybear23:
It's probably a good idea to not use a custom kernel until the kernel dev has had a chance to play with the update...
[Captivate Android Development] joeybear23:
Which modem are you using?
[Captivate Android Development] bdbsubscribe:
anyone else have this:

im getting data (i can do up and down) but my 'data arrows' for lack of a better term, don't seem to indicate anything while the data is being transfered
[Captivate Android Development] jaysix79:
I don't if this is just my phone.. does anyone experiencing phone reboot when your talking to someone... it only happen if you change the screen for example if you talking to someone and your surfing the web or using other app the phone would reboot within five minutes

also when using your headset to talk to someone.... the mic on the headset doesn't pick up your voice so you have to put the phone's mic right next to you
[Captivate Android Development] joeybear23:
I'm actually getting better data... my speedtest scores are better (2.33 Mbps down, 1.23 Mbps up, and ping was only 149ms)

The only thing strange I have noticed is switching between H and 3G

I am using the JK4 modem
[Captivate Android Development] bdbsubscribe:
its not the actual data transfer thats the problem - thats working just fine, its that the (what would be an activity indicator on a computer) up and down arrows above the H do not seem to work. this doesn't seem to be having an effect on the transfer rate. its a small thing, just something i noticed which was a bit disconcerting for a few minutes
[Captivate Android Development] cashyftw:
Edit: Kidding.
[Captivate Android Development] kinubic:
anyone have any fixes for the gps? everything else seems find for me battery life is awesome

edit: using 9th build and cm7-captivate-radio-JK4.zip modem !gps locks fast
[Captivate Android Development] skeepon:
im looking for a new modem. any recommendations?
[Captivate Android Development] EnemyOfGlaDOS:
what are you using?

I like JK4.. lol... i just said this in the q&a's... but i hear JP9 is working well.
[Captivate Android Development] stuff:
KC1 modem works wonderful for me. Plus I get like (at max) 3648kbps download 1270 upload @ 264ms.
[Captivate Android Development] iakovl:
just installed nightly 15... great rom, works fast but somehow i ended with CWM recovery 3.1.0.1 should i go back to 2.X.X.X?
[Captivate Android Development] oxlong27:
+1 jp9 and cm7 gives me the best signal i have ever had with this phone
[Captivate Android Development] Jemack:
No. CM7 requires 3.x recovery.
[Captivate Android Development] atinm:
We don't touch the bootloader, and the standard methods are something the bootloaders do. (#2 requires you to then let go of the power button after the second time the wheel stops showing).
[Captivate Android Development] XGX5309:
I'm having an issue... well maybe not an issue, but odd... when initiating data transfer over WWAN it's cycling from IDLE to FACH to DSCH, then when data slows it drops down to DCH, then back to IDLE. That cycling is causing the icon to flip out going from 3G to H to 3G and back to H.

Any idea what is causing that? Power saving feature in the modem firmware? I know IDLE sucks a lot less battery that DSCH or DCH, but it's almost as if the connection is being handled as an "on-demand" connection, and not "always on".
[Captivate Android Development] kofijay:
My Captivate Does NOT Charge [Charging Problem]

I was on Firefly and everything was alright but decided to switch ROMs to see what Cyanogen would look and feel like.

I love it and I thought all was cool until I had a low battery prompt.:(

I plug up my charger and I see the thunder-like sign in the battery that indicates it recognizes the power cable has been plugged in but after an hour or so, the battery is still at 7%. Meaning it wasn't charging.

Could someone help me out on this?:confused::confused:

Thank you.

:(:(:(
[Captivate Android Development] georgem106:
I am using the original modem. I did not change anything.
[Captivate Android Development] gabby131:
Wifi...connection lost, download error, failed to conect to network, reply unsuccessful, cant do anything on wifi here lol! :D

EDIT: that's #15
[Captivate Android Development] Hickeroar:
When someone checks out #16, let us know how it goes. :-) If the time issue is resolved and there isn't anything nasty and new, Ill probably update today.
[Captivate Android Development] georgem106:
I didnt have a time issue after installing #15. There were no major bugs I noticed with #15. I will be installing #16 in a few though....So try #15 and see if your time is fixed.
[Captivate Android Development] Hickeroar:
I'm actually on #13. I just didn't want to update to a rom that has the issues #14 did. :-P

I'm anxiously awaiting your verdict on #16. :-)
[Captivate Android Development] The Boxinator:
I am trying out 15 as we speak, I will report back shortly :)
[Captivate Android Development] Hickeroar:
15? The 16 nightly is out.
[Captivate Android Development] georgem106:
So far all is good with #16
[Captivate Android Development] gabby131:
wifi settings and advanced settings? anyone? im kinda sick of getting all the builds from 3 to 16 and all of em gives me the wifi connection of death....:D
[Captivate Android Development] cease:
They worked for me.
[Captivate Android Development] cease:
...follow-up. What you typed is not what I typed as methods to try. Your list does not read the same as my list. Try the last one, it does work. Battery removal is key. It's the only way I got out of a completely locked up Captivate.
[Captivate Android Development] cease:
15 ok, 16 is too.
[Captivate Android Development] kofijay:
SOLVED!!!

I just got this solved!
[Captivate Android Development] pvr:
Care to share?
[Captivate Android Development] r.iqbal87:
Is it impossible to somehow integrate Samsung dialer codes into cyanogen?

I would assume it is, since it hasn't been done as yet, or is it because a lack of demand?
[Captivate Android Development] droid_does:
Hows #15 and #16?

If they're stable, I'll flash to 16 tomorrow after I wake up
[Captivate Android Development] joeybear23:
16 is working well for me thus far...
[Captivate Android Development] EnemyOfGlaDOS:
I'm taking a stab in the dark here, but I'm gonna say no. Samsung uses closed source, and CM7 is all open source stuff. You will not be able to use samsung apps as well as the dialer codes. Sorry 'mate.

BUT-- i have at&t roadside assistance which requires dialing *help.. I know it's a little different than the dialer codes but that works.. if you have the same policy.:)

If I'm wrong, someone please correct me.
[Captivate Android Development] kofijay:
Sure ...

I believe it was a kernel problem.

Using ODIN, I flashed the SpeedMOD Kernel [i897-k13e], then flashed CM7 Captivate INITIAL Kernel.

Going into CW Recovery Mode, I installed cm_captivatemtd_full again.

That solved it for me.
[Captivate Android Development] jellysweep:
What's the latest build that doesn't suffer from the wifi disconnect issues? I had to revert builds previously. Considering installing #16.
[Captivate Android Development] mkatforum:
Is anyone facing issues with the dialer dialing numbers more than once when using it to enter codes and such? Its becoming a pain now. I am on the nightly from 19th.
[Captivate Android Development] hkk:
Does anyone have a problem with WiFi hotspot? I can enable it, the client devices can connect and get IP addresses, but they can't connect to the internet. Currently on #13.

thanks,

HK
[Captivate Android Development] joeybear23:
FYI -

occasionally with #16 the soft keys will be non-responsive within an application.

To resolve this, you just turn the screen off then back on.

Not a big deal. Just an observation.
[Captivate Android Development] matt310:
I'm experiencing overall sluggish dialer performance and random crashes when dialing numbers. Strange and irritating and seemingly a new issue on the latest five or so builds.
[Captivate Android Development] mkatforum:
My regular dialer works but I have lots of fun entering stuff like voicemail passwords as the digits will double dial most of the time.

I just upgraded to #16 and wiped both caches but no luck.
[Captivate Android Development] hkk:
I am seeing that on #13 too.
[Captivate Android Development] EthanMG:
i have flashed quite a few roms, but they have all been 2.2 samsung based roms (took a break for a while) and what i used to do was put specific apps that i like, but that dont come with the rom, into the rom zip so that everything is done in one flash. i would do the same thing with the modem that works best in my area (jk4) and with the kernel. my question is: with cm7 can i do the same thing? to be specific, can i replace the modem in the initial zip with jk4 and also add gapps (including the apps and libraries and the other stuff thats in the gapps.zip) to the initial zip so that its all done in one flash? thanks for the help!
[Captivate Android Development] :
Is the "modem dance" still required to install JP9 on CM7?
[Captivate Android Development] Lhernandez0105:
I would believe so. I remember reading a while back that the only reason gapps isn't included in the zip is bescuaee Google asked that copy righted apps not be included.
[Captivate Android Development] EnemyOfGlaDOS:
you can.. but you wanna make sure the radios (modem) you are using is for CM7, and also need to check with the Dev of the kernel you want to use, and make sure it is up to date with whichever CM7 build you want to use. Since Nightlies are being pushed out, there is a good chance the kernel may not be up to date with the latest nightly- which would result in broken fixes.

As far as the apps go.. you should be able to do that as well, but know that CM7 is Open Source. Meaning, any of your samsung apps will not work
[Captivate Android Development] Hickeroar:
Hotspot worked fine for me on #13. Haven't tried it on #16.

#16 seems pretty solid thusfar.
[Captivate Android Development] EthanMG:
thanks!
[Captivate Android Development] EthanMG:
ya I'm not flashing a kernel, just a modem and gapps, so I think I'm good. thanks for the help!
[Captivate Android Development] jellysweep:
I have to try to download build 16 like 10 times because the wifi is unstable, and keeps getting disconnected. Please tell me it's fixed in 16.
[Captivate Android Development] bdbsubscribe:
i think one thing from the sammy setup that would be an awesome feature would be the ability to dial just a few numbers (or letters) and have the associated contacts pop up.

i.e. dial 4321 and any contact that have 4321 (in sequence) come to the top ; or dial 5(j)6(o)4(h) and any 'john' contacts would pop up.

not sure how difficult that type of thing would be?
[Captivate Android Development] ls377:
You can find other dialers in the market that do this, such as Dialer One
[Captivate Android Development] bdbsubscribe:
i get this quite a bit - seems to vary frequency depending on the boot. some boots its more (a LOT more), some less.
[Captivate Android Development] bdbsubscribe:
coo, thanksl! ill give it a try - none the less it would be a nice integration. perhaps something that could be enabled/disabled under cyanogen settings as i can see some people not wanting it and others finding it useful
[Captivate Android Development] nkrick:
I have this problem, but only when calling certain automated systems. This morning I was trying to dial into a conference call and every time I hit "0" the system thought I was hitting "00." On a different conference calling system, I had no issue. It could be that the dialer tones are slightly longer than normal, causing some systems to interpret them as a double tone.
[Captivate Android Development] jaysix79:
I am to is experiencing random crashes on build 16 when using the dialer (when talking to someone and switching app) also when using the stock Samsung headset (haven't tried other headset) you have to use the phones Mic to talk or else the other person won't hear you same as build 15. When listening to music you can't use the headset to skip to the next song
[Captivate Android Development] nkrick:
If you think this would be a good feature enhancement, then make a feature request to TeamDouche (the maintainers of CyanogenMod). CM is built for something like 30 different phones and is essentially the same on each phone. Team Hacksung is not going to make changes to the CM source to add new features to the SGS phones that do not exist in the source.

In the meantime, with the dialer open, hit your "search" button and type the name of the person you want to call. You can't search for phone numbers (unless you use the phone number for the contact name), but it works pretty much as your described for names. Also, try using Google Voice Commands. Why type in a phone number or name when you can simply say, "Call so_and_so on mobile" or "Dial 555-555-5555."
[Captivate Android Development] jellysweep:
I installed build 16, and it seems to have fixed the wifi disconnects. So far so good!
[Captivate Android Development] mkatforum:
This is precisely the problem I face. My voicemail service and work conference system just wouldn't play nice with the phone. A longish tone is interpreted as double tone.
[Captivate Android Development] ls377:
You can also search for contacts from the home screen using the search button. No need to enter the dialer.
[Captivate Android Development] MentalDragon:
First off great job and very happy to have these updates part of RM now. I have been experiencing a problem where everytime I make or receive a call, after I am done I have full blank screen and no response from phone. To get phone back up I have to either pull battery or plug phone into a charger. Just wanted to see if I was only one or if this is another bug. I see from earlier posts problems with dialer and voicemails but nothing duplicating my situation. Thanks and keep up good work.