yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] littlewierdo:
"Second, my lock screen randomly will not work sometimes. I will push the 'hold' button, and it will 'lock' but when it's pressed later the screen comes right back up without going through the lock screen. This isn't a HUGE problem, I just don't want it unlocking in my pocket."

I am not currently running CM7 BUT I do recall seeing a setting for this. I believe it is settings>Cyanogenmod Settings>Lockscreen. There is a setting in there that sets the phone to NOT return to the lockscreen after a specified time period after the phone screen turns off. If I recall, it is a short time frame, something like 30 seconds (so if you unlock your phone and then turn the screen off and immediately turn the screen back on, it wont re-lock the phone. But if you unlock your phone and then turn the screen off and wait 30 seconds with the screen off and then turn your screen back on, it should return to the lock screen).

As a sidenote (not in reference to the post above), people, read the original post, read the installation instructions, learn a little about what you are doing BEFORE attempting to flash a new rom. While the Cappy is pretty foolproof thanks to Odin, you should still know what you are doing and have a clear understanding of what you are getting into. All people new to flashing should have AIOToolbox and SuperOneClickRoot for starters (these two programs have all of the usual utilities for 'easy' phone stuff like flashing to stock, rooting, installing drivers, etc.).

I would not recommend new people using CM7 as their first cappy rom. Start with something like Cognition (which is basically the stock rom but has alot of crap removed and features added) which offers a stock experience without anything new really to worry about.

The reason I mention this is I see alot of people asking (quite frankly), really basic questions about the cappy that you should know about BEFORE flashing a new rom (nandroid backups and 3 button recovery were two questions I saw) and being that CM7 is probably the most difficult rom out there to install and use at the moment with more than a handful of bugs, it is NOT a rom for beginners (yet). I would say, once a 'stable' version is released, it is probably ready for everyday use.

On the xda forum for the samsung captivate (linked below this paragraph) are several sticky threads for some information you NEED to know before playing around with any new roms. Read them before asking something that is already explained in the tutorial threads on the cappy.

A good place to start is here:

http://xdaforums.com/showthread.php?t=858765

A lot of good links in there, a fantastic little 'mega' post on pretty much all of the 'basic' problems you may run into with the cappy.

And, go here and look at any of the applicable stickied threads.

http://xdaforums.com/forumdisplay.php?f=704

And here for even more stickied threads (including a link for AIOToolbox)

http://xdaforums.com/forumdisplay.php?f=706
[Captivate Q&A, Help & Troubleshooting] littlewierdo:
Note to the devs of CM7:

This is just a personal opinion but I think maybe you might want to consider consolidating the instructions for installing CM7 into one single thread and delete the instructions that are outdated / duplicated. It isnt useful to have 2 different sets of instructions both stickied and a third thread on the Epic with the same links that are included in the 'All Devices' (bottommost) thread. Maybe create an 'all models 6.1' thread (and keep the 'all models 7' thread) and structure the 6.1 thread the same as the 7 with proper instructions for installing. Just a thought.

http://forum.cyanogenmod.com/topic/13146-cyanogenmod-61-for-epic-nightly-build/

http://forum.cyanogenmod.com/topic/17037-sgh-i897-cyanogenmod-7-this-will-eat-your-kitties/

http://forum.cyanogenmod.com/topic/...d-7-for-samsung-galaxy-s-phones-experimental/

And yes, I understand the epic is for CM 6.1 but it seems to me that maybe covering all models in one 6.1 thread (like you do with the CM7 thread with instructions and links) would make more sense.

And lastly, just wondering if the four letter 'f' word is really necessary in the top most stickied faq (see question 5).
[Captivate Q&A, Help & Troubleshooting] lanisan:
Thanks for the reply. I'm really glad (especially someone with a lot more knowledge than me) someone responded with this much info. The JK4 I used for a long time worked awesome. I thought about going back but wanted to try the radios that are available with the latest cm7 update. After my last flash I really didnt have time to try anything else and I'm on jk9. Any idea why the mmi code wont work on my phone anymore?

Thanks!
[Captivate Q&A, Help & Troubleshooting] atinm:
Changelog:

20110511

- Revert samsung_modemctl to 2.3.4

May fix the disconnect issues related to modem crash.
[Captivate Q&A, Help & Troubleshooting] atinm:
Some of those aren't in our control, others are locked. And I don't know which one has the 'f' word and whether we can change it anyway.
[Captivate Q&A, Help & Troubleshooting] nkrick:
If you use a Modem for the Telus Fascinate, it is only a 850/1900/2100 device.

It could be that pdadb.net is wrong. Trying to look it up on AT&T/Samsung websites, but my internet access from here is so slooooow...

Edit: According to AT&T (http://www.wireless.att.com/cell-ph...TM)+-+Black&q_sku=sku4760319#fbid=1ys24mfZeU-) the Captivate supports 3G on 850/900/1900/2100. If it weren't for missing HSUPA and problems introduced by the Audience chip, the AT&T Captivate modems might be the most popular i9000 modems due to the number of supported bands.
[Captivate Q&A, Help & Troubleshooting] Altair4:
(Sorry for the noob question)

So I've decided to reflash the cyanogen rom from stock because of issues with FCs. I just have a quick question about the instructions:

FIRST TIME FLASHING CM7 TO YOUR SAMSUNG GALAXY S SERIES PHONE:
Make sure your phone is fully charged! Update process will take some time.
Make sure there's enough free space at your internal sdcard (200MB)
Make sure you've not disabled HSPA by using the dialer code *#301279#
Make sure you're running a 2.2 (Froyo) bootloader. If you're on Gingerbread, downgrade to JPU or something.

I'm slightly confused about the last note - make sure you're running a 2.2 bootloader. Does this mean that I need to be on 2.2 to flash this rom? If I odin back to stock and do a factory reset, do I need to update to stock 2.2 froyo first or can I flash this straight from eclair?

Pretty much my question is: what's the best way to flash cyanogenmod if I want to start from scratch?

I think the instability I'm experiencing right now is due to flashing cyanogen straight from serendipity 5.10

Again, thanks for your help to my newbie question :)
[Captivate Q&A, Help & Troubleshooting] nkrick:
Either 2.1 or 2.2 is fine. It doesn't work right if you are running a i9000 2.3 bootloader.
[Captivate Q&A, Help & Troubleshooting] :
Can I overclock CM7 to 1.2 GHz using the stock kernel?
[Captivate Q&A, Help & Troubleshooting] EnemyOfGlaDOS:
Sorry sir.. I'm afraid not
[Captivate Q&A, Help & Troubleshooting] :
Ok. How can I overclock it?
[Captivate Q&A, Help & Troubleshooting] EnemyOfGlaDOS:
Flash a custom kernel that supports OC'ng. There are a couple out there. I'm using the escapist's kernel. Kernel du jour.. look in the Dev section you find a couple kernels available for CM7. Make sure they are up to date to work with the latest nightly.
[Captivate Q&A, Help & Troubleshooting] m08:
Just flashed CM 7 for the first time, and the Home button has decided it no longer wants to do its part. Any suggestions for a fix?
[Captivate Q&A, Help & Troubleshooting] jhernand1102:
Make sure the files you flashed have captivate in the name. If not then you flashed the wrong version which will mess up your buttons.
[Captivate Q&A, Help & Troubleshooting] EnemyOfGlaDOS:
Sounds like you flashed galaxy s and not captivate.
[Captivate Q&A, Help & Troubleshooting] RockRatt:
Anyone on the newest 05112011 update phone not ring when you receive a call? I updated 2 seperate phones with it (One a 1007 build the second a 1010 build) and both wont work at all. I went in and checked the sound settings, made sure to reset my ringtone and notifications. If anyone can check or figure out what i am missing here. Been on every update for a couple months now. Thanks

Edit: Got it working. Don't know why I had to change the cm settings sound for attenuation back to default and then lower it back to the setting I was at previously. Got both phones working that way.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Q&A, Help & Troubleshooting] Kaik541:
AT&T is lying. the Captivate only supports 3g on 850 and 1900 MHz. FCC filing here: https://fjallfoss.fcc.gov/oetcf/eas...me=N&application_id=303560&fcc_id='A3LSGHI897' (read the RF Exposure Info). it's quadband GSM (aka 2G) but only dual band 3G
[Captivate Q&A, Help & Troubleshooting] :
Flashed CM7 by following the directions correctly. Everything works fine, but when I tried to calibrate the battery it wouldn't charge past 96 (brand new Captivate), and the battery life sucks. I am using official CM7 update and kernel, not nightly.
[Captivate Q&A, Help & Troubleshooting] Kaik541:
there is no official CM7 for captivate. the nightlies are just as "official" as the "initial"... also, thanks for not reading the FAQ where the 96% thing is clearly addressed.
[Captivate Q&A, Help & Troubleshooting] atinm:
Read the links in my signature.
[Captivate Q&A, Help & Troubleshooting] nkrick:
The FCC is an US organization. They only test FC Exposure to bands that people in the US will be exposed to. The FC Exposure filing that you refer to clearly only shows "850/1900 GSM/GPRS/EDGE/WCDMA." Quadband GSM (850/1800/1900/2100) is not mentioned in the FC Exposure report either (only 850 and 1900). So according to your logic, AT&T must be lying about quadband GSM too.

I have used my Captivate with 3G in Europe. Europe 3G is either 900 or 2100. There is NO 850 or 1900 in Europe. So, either the Captivate supports European 3G bands, or CM7 also "lies" and reports 3G when I am in Europe using Edge.

Because Atimn appointed you the official CM7 Captivate forum mod, people take what you say as truth. Perhaps you should keep your answers limited to areas that you have actual knowledge about so as not to mis-lead people who trust your answers and responses in this forum.
[Captivate Q&A, Help & Troubleshooting] Kaik541:
or we could look at rogers' description of the captivate: http://www.rogers.com/web/link/wire...roductType=normal&productId_Detailed=I896BLKR

which is identical in every regard except the faceplate (it's been confirmed the motherboard even states it's an i897) yet Rogers says something else entirely different than AT&T. or we can look at the LG G2x recently sold by tmobile and on their site claimed to have support for AT&T's 3G bands! clearly marketing can never make a mistake with things like this and companies never post inaccurate information.

my point being is there's clearly some confusion regarding the bands and I've never seen a single person report ANY success utilizing the 2100 MHz band or the 900 MHz band. Show me it working and I'll believe you, until then, I'm going to chalk it up to a mistake on AT&T's part. And just because the chip is physically capable of utilizing those bands doesn't mean the chip is wired to actually have access to those pieces of it (we don't use the FM radio or BT2.1 support on the broadcom 4322 either, even though they're there just not connected)
[Captivate Q&A, Help & Troubleshooting] gabby131:
i got the file titled 70zipalign on /etc/init.d which is quite new to me.

is this from the latest nightly or a kernel i recently flashed? thanks :)
[Captivate Q&A, Help & Troubleshooting] nkrick:
Just because you are one of those people that doesn't believe anything that you haven't seen, doesn't mean that others have not successfully used their Captivate in Europe (or Asia) on 900 and/or 2100. Unfortunately, I am not 100% if I was using 900 or 2100 when I was in Germany in March, but I am 100% sure that I had working 3G and it had to be one of those 2 bands. So now you have seen a single person (me) report success using either UMTS900 or UMTS2100 two times (I also stated it in my previous post). I know there are also some Europeans that are active in the Captivate thread who own Captivates and without being able to pull any exact quote, I am still fairly certain that UMTS/HSPA works for them using either UTMS900, UMTS2100, or both.

You point to the i896 and include the Rogers URL with shows UMTS 850/1900/2100. Previously you claimed that the Captivate was only UMTS 850/1900 and AT&T lies. Now you apparently believe Rogers (so you must at least believe the Captivate has UMTS2100) but not AT&T. Should I point out that Rogers also shows that the i896 runs Android 2.1, even though it now runs Android 2.2? So there is at least 1 inaccuracy on Rogers site.

It is well known that the i896 does not include the audience chip. The audience chip is wired on the PCB to communicate with the modem directly according to the audience specs and drawings, and plenty if evidence in the fact that i897 modems do not work well without audience chip support. So, we know that even if the PCB in a i896 says "i897" it is wired differently to the modem component. So, if the modem is wired differently, how can you definitively say that the i897 does not have UMTS900 just because the i896 does not? Maybe the space taken in other Galaxy S phones by the voice processing in the modem code is able to be used to support the code for an additional band (GSM900) in the i897.

You still have not addressed the fact that the FCC filing does not mention GSM 1800 or GSM2100 anywhere in the document, yet you admit that the i897 is a quadband GSM device. If the FCC does not say that the i897 supports GSM1800/2100, why do you say that it does, aside from the specs on AT&T's site that say it does (which you claim are inaccurate).?

Why don't you just admit that you were wrong to say that the i897 only supports UMTS 850/1900 and that the only specs we have to go on are what AT&T has published which state UMTS 850/900/1900/2100, and lacking evidence to the contrary there is no reason to state that the AT&T specs are wrong, or that "AT&T lies."

Edit: I found the following wikipedia entry for a list of UMTS networks: http://en.wikipedia.org/wiki/List_of_UMTS_networks

Based upon that list, i am 100% sure I used UMTS2100 (it is the only UMTS band used by O2 and Vodafone in Germany). While in Germany, I roamed on E-Plus, Vodafone and O2. I have no way of knowing if I happened to connect to UMTS900 while connected to E-Plus.
[Captivate Q&A, Help & Troubleshooting] makelegs:
Pretty sure this conversation is not gonna lead anywhere.... Not sure what the point is of picking a fight with the thread mod. Can we just call it a draw and move on???

#justsayin
[Captivate Q&A, Help & Troubleshooting] Kaik541:
you completely misunderstood my response. I was saying that just because a site says it doesn't mean it works (even if the manufacturer/carrier should be responsible for it). lots of the hardware in our phone simply isn't active even though the hardware is physically capable of it. and just because someone is using it in Europe doesn't mean they have 3G (I know people with Captivates on Tmobile US... they CERTAINLY don't have AWS support in the Captivate yet they use it). And I didn't address the FCC filing because clearly you're right about that and I can't argue against it (what else am I going to say?), but everywhere else seems to be in agreement that it's quadband GSM.

I also never said "it can't possibly support those other frequencies", I said "just because AT&T says it doesn't mean it's the truth" and until I saw otherwise I have no reason to believe AT&T doesn't just want me to believe it has more selling points than it's competitors.

I wasn't being confrontational, I was saying I have no way of proving you wrong just like you have no way of proving you're right (you can SAY you were in Germany and you had 3G there, how am I supposed to know?). you say it worked for you, ok, sure... whatever dude, I don't really care as it doesn't affect me. I have a hard time believing Samsung accidentally tossed in a quadband UMTS radio as that would have been an absurd selling point of it as there are only, like, what three or four phones with them? (Nokia N8, some INQ devices I've never heard of, and the iPhone 4?)... as for tri-band, that's more believable but I've yet to see it myself (kinda hard living in America where you don't see 2100 MHz or 900 MHz bands for independent 3G--TMobile uses both 900 and 1700 MHz simultaneously if I recall correctly or it won't work... I was always under the impression people using the Captivate in other countries either had carriers that used the same frequencies or were using 2G only, never mattered to me as I haven't lived in Germany for over 12 years).

point being, wasn't being confrontational, just there is no proof one way or the other on the forum that I've seen. back to the subject at hand.
[Captivate Q&A, Help & Troubleshooting] Palmetto_X:
Anyone getting Netflix to work? I am getting unsupported device. Some other roms continuium and mosiac are getting it to work by modding their build.prop.
[Captivate Q&A, Help & Troubleshooting] rivera151:
So once again, I, Mr Smarty pants, think I may have found a bug. I'll post here to make sure I'm not regurgitating...

With the android keyboard, If I change to the keyboard from another keyboard ("Input Method" context menu), I can slide my finger across the space key to change the language of both the keyboard and the dictation. However, when I exit the program and open the keyboard somewhere else (ie I just typed a text message and now I try to post via xda app) the language settings for the spell checker can still be changed with a slide across the space key, but the dictation language can't be changed unless I switch to another keyboard and back. Let me know if more information is needed with this issue.

Ricardo

Edit: turns out I can't change the dictation language after selecting the android keyboard; it sticks to the language the keyboard was set to when you switch to the android keyboard regardless of the language shown on the spacebar, so if the kb was set to english, I can dictate english. If I wanna switch to spanish, the spell checker changes language, but to get the dictation to recognize spanish, I have to select, spanish, select an alternate kb, and switch back to the android keyboard.
[Captivate Q&A, Help & Troubleshooting] nkrick:
I would like to keep this civil, but I don't buy that you are not being confrontational when in the same posts you are essentially calling me a lier. Where I come from, calling someone a lier is confrontational no matter what sort of nice language you use.

Whether you choose to believe it or not, the i897 is at the least a tri-band device capable of using UMTS 850/1900/2100. For a thread moderator to state that the Captivate is only dual-band UMTS in one post, then in another post say it is the same as the i896 (tri-band UMTS) confuses people and spreads mis-information about the device.

I readily admit that the i897 may not be quad-band, but, in the absence of evidence to the contrary, I see no reason to say that AT&T is lying about the i897 being quad-band UMTS. In the US we say "innocent until proven guilty." Until someone can show that the i897 does NOT support UMTS900, I see no reason to say that it doesn't. Now a reasonable amount of doubt based upon the specs of other SGS devices is understandable, but not the statement that "AT&T is lying" or challenging me and saying that you believe that I am lying (using different words).
[Captivate Q&A, Help & Troubleshooting] atinm:
Let it go - just need confirmation from a few sources and we'll know what bands it does or does not support.
[Captivate Q&A, Help & Troubleshooting] atinm:
Report it upstream to CyanogenMod as this is not something device specific.
[Captivate Q&A, Help & Troubleshooting] lethoncbon:
Great, thanks for the fast reply, as usual :)

I'll try it and see if it works ... and will not complain if it doesn't ;)

Thanks again!
[Captivate Q&A, Help & Troubleshooting] 7h3kk1d:
It's set to when screen turned off should i set it to never/.
[Captivate Q&A, Help & Troubleshooting] techmik67:
yes

10 characters
[Captivate Q&A, Help & Troubleshooting] waghoba:
If possible can you please tell me which files should I look for implementing these functionality??

Thanks
[Captivate Q&A, Help & Troubleshooting] waghoba:
Music Player from Honeycomb !!!

Just came across this thread and installed the music player from honeycomb on CM7 and its working perfectly. I am attaching the file here. Just one thing I haven't understood yet, how the music sync works OR how to use it?

can someone please care to explain me?

Thanks!
[Captivate Q&A, Help & Troubleshooting] Kaik541:
I already tried this, sync doesn't work on our phone yet it seems. crashes when attempting to grant permissions properly for streaming.
[Captivate Q&A, Help & Troubleshooting] waghoba:
ohh...I hope it works with our devices in future..just for my info how it works - will it keep our particular music folder on computer in sync with our phone?

Edit: one more Q, I dont know if it was a part of samsung framework but when you go to dialer and press the keys corresponding to T9 keyboard letters, the stock rom shows the relevant contacts. Is it possible in CM7 somehow. i mean suppose I want to find "ALAN" from contacts I can go to dialer and press 2-5-2-6 to get ALAN .

Thanks
[Captivate Q&A, Help & Troubleshooting] Kaik541:
you upload the music from your phone to google (somewhere?) and then it can be streamed to your phone. there is currently no way to selectively sync, it just pushes everything. this isn't fully fleshed out app yet (it's an early leaked version)... most likely the final release will have a front-end for computers and selective syncing
[Captivate Q&A, Help & Troubleshooting] waghoba:
one more Q, I dont know if it was a part of samsung framework but when you go to dialer and press the keys corresponding to T9 keyboard letters, the stock rom shows the relevant contacts. Is it possible in CM7 somehow. i mean suppose I want to find "ALAN" from contacts I can go to dialer and press 2-5-2-6 to get ALAN .
[Captivate Q&A, Help & Troubleshooting] nkrick:
I noticed that in the clock app, while charging and with the screensaver on, the capacitive buttons are lit up and do not turn off. Is this expected behavior, or a bug?
[Captivate Q&A, Help & Troubleshooting] nkrick:
Sorry about the separate post, but just thought of something else. When dialing, the screen immediately turns off, rather than being turned off by the proximity sensor. I find that I usually have to dial, then turn the screen on to verify the call is connecting (this may be less of am issue once back in the US). The screen does turn off fine via the proximity sensor when I raise it to my face (after turning it back on). Also related, the screen does not turn back on when removing from my face (to end a call). Are these bugs, or differences in behavior in GB/CM?
[Captivate Q&A, Help & Troubleshooting] joeybear23:
I experienced an issue last night, and could not find it specifically in previous posts, so I apologize if this has already been addressed:

While on a call, the phone goes to sleep and only a three-button combo or battery pull gets it to come back.

Steps to reproduce:

1. Receive a call and talk for a minute or so

2. Set it on speaker

3. Talk long enough for the screen to turn off

The screen does not actually "turn off" at this point, rather I can see the contact name very lightly on the screen (almost looks like screen burn-in), and all the soft keys at the bottom are lit.

At this point you cannot get the screen to come back up, even after the call ends.

I have reproduced this twice, with the same steps above.
[Captivate Q&A, Help & Troubleshooting] mcord11758:
Although I.have not experienced that exactly I have noticed sometimes while on a call screen goes black and is difficult to wake.