yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] pvr:
Cool thing though... I've actually got "recognized" in my company while I worked at support for applications because I've started responding to my internal users that "No ticket, no problem."

They said I was encouraging other ppl to follow company standards.

Of course, I'd call procrastinating but it's cool... :)
[Captivate Android Development] cropythy:
I am getting non stop force closes on the browser and fix permissions didn't help, anyone have any suggestions?
[Captivate Android Development] ClaPik:
My wifi doesnt work...it says "Error"

Can I download the 4/2 and install it? Does it brick the phone by going backward?
[Captivate Android Development] NiXXeD:
No I went backwards and am sticking with 4-2 until the problem is figured out.
[Captivate Android Development] atinm:
You can flash older 4/2. There is most probably a bug in our new install process scripts - but will take a day to figure out (I cannot work tonight). But we'll have this solved soon.
[Captivate Android Development] ninjuh:
I flashed cm7 for the billionth time today. Loving it as usual. Here are my only complaints.

Keyboard. I use smart keyboard pro religiously. On 2.1/2.2 roms its the smoothest keyboard ever. On this it kind of lags, especially if I have sound presses enabled. I keep those disabled & its smooth but not as smooth as on froyo.

What's with my signal bars and the H turning white at random times?

Kernels. The only kernel I've had stable success with is exists version 3.5, not a problem with this rom itself, just letting everyone know my experience.

If you backup data in certain apps with tibu, while ON CM7, and try to restore that data on a 2.2 rom, it causes an FC. I've tested this in many variables of different 2.2/2.2.1 roms, happens EVERY time with all versions of angry birds.

Other than those few things this is nice!
[Captivate Android Development] superj3211:
was wondering if going back to 4/2 if it would fix my browser force close
[Captivate Android Development] EnemyOfGlaDOS:
All that means is that your google acct isn't sync'd. Green=sync'd. White=not sync'd.
[Captivate Android Development] ninjuh:
Oh that's stuuupid. I never have auto sync on, I'd rather see my email when I check it myself. I like the green :'(
[Captivate Android Development] Kaik541:
to anyone wanting to stay on the latest build for dual sd card support, but also wants working wifi/wifi tether, you *should* be able to flash the attached odin-flashable zImage.tar

this is the same zImage pulled from the update zip so it should work fine, but I am not on this build and cannot test it at the moment.

NOTE: this process *should* be fixed in the next update, so this is only a temporary fix. also, if you don't have access to odin, you can extract the zImage and flash with heimdall as well. this comes with no warranty and no guarantee it'll work, but I'm going to put it out there for anyone who wants it. if you don't know how to use this, don't ask for instructions/complain that it doesn't work

edit: MD5 E8E4A0F4AD27B6CBA4A31AD27F5C67A1

SHA1 018AD835C69A429D818EC2601F4E9D0516858A15
[Captivate Android Development] emcnelly:
On the latest nightly and Wifi works perfectly but the swipe down, show notifications gesture on adw launcher isn't working any more don't know if this is a related...
[Captivate Android Development] bazald:
worksforme. Thanks. Have fun resolving the installation scripting issue ;-)
[Captivate Android Development] prayii:
+1 same for me
[Captivate Android Development] dancer101:
I just installed CM7 and I was wondering if I was able to change the fonts either by flashing zips or another way.

Love CM7 so far!
[Captivate Android Development] Kaik541:
the installation script issue has possibly been identified. it's related to a new test to verify a lack of bad blocks in kernel (it's hard to test for certain as we can't force bad blocks, so it can only be tested on a device WITH bad blocks) that causes the ROM and new modules to get installed, but not the new kernel... will hopefully be resolved soon.
[Captivate Android Development] smanzor88:
the official release of cyanogenmod 7 just released?! would this ROM be complete also?! i wanna try it so bad..had a g1 bfore and this is the only ROM i needed..
[Captivate Android Development] EnemyOfGlaDOS:
Did you try searching market for different fonts?
[Captivate Android Development] dancer101:
I found an app called font changer but i'm not sure if it will work.
[Captivate Android Development] Kaik541:
we are not a part of mainline yet, so our release schedule is not in line with theirs.

reports of font changer working has shown up once or twice, but they do not use the "flipfont apk's" from samsung ROM's
[Captivate Android Development] soypoi:
Font Changer works as long as the font is .ttf. You can use dafont.com or any other font to load it. For some reason though, you need to have a regular and a bold for it to be selected. If you don't have the font as .ttf you can always convert.. this is what I used to convert Neutraface.

Font Converter
[Captivate Android Development] dancer101:
I figured it out! I was able to flash edify versions of fonts. Seems to work fine..no problems!

I got them here: http://xdaforums.com/showthread.php?t=801160

Thanks!
[Captivate Android Development] Johnston212:
Are you sure? I almost never have auto-sync on and mine turns blue (using a different theme atm) not long after I turn on my phone or turn off Airplane mode. So I doubt that is the case. Could it be your modem?
[Captivate Android Development] Kaik541:
this is exactly what it means. uncolored (default: white) = no connection to your google account, lit up (default: green) = stable connection to your google account

it can be different with themes as they can have the same image for both or even no image for the uncolored one. the only way to *know* what's expected is on stock (and then to correlate that to each theme)
[Captivate Android Development] r.iqbal87:
Anybody getting track skipping/distortion with flac audio files? Occurs on all kernels available. Even initial.
[Captivate Android Development] beavisrp:
WIFI says error after last update. Anyone else got this issue?
[Captivate Android Development] xnoctis93:
i'll quote what atinm said earlier
[Captivate Android Development] bobmcgee:
I don't use FLAC, but any audio was skipping. Found the problem was that I had initially moved the music from my compy to the internal SD and then used root explorer to move it to the emmc drive. That lead to the skip on every output the phone has (I.E. bluetooth, wired headset, internal speaker). I could copy a file back to the internal SD card and the skip went away, but only for those moved files. Made me think that there was a problem with accessing the emmc drive on music playback.

Now that the new update contains the ability to copy direct to the ext sd I haven't encountered this problem. Perhaps root explorer screwed up the transfered files during the move? I don't really know.
[Captivate Android Development] Funzy32:
I just wanna say that Cm7 is awesome. Battery life is unreal. :)

Sent from my HTC Thunderbolt
[Captivate Android Development] atinm:
For anyone who has had problems with wifi after flashing the latest, can you please link the /sdcard/bmlovermtd.log file that is on your phone after your bad flash? You should still be able to access that via "adb pull /sdcard/bmlovermtd.log . " from your desktop. It'll really help us debug this problem. The bug seems to be in our checking for bad blocks on your boot partition and if found, trying to work around these bad blocks when flashing. What seems to be happening is that the whole flash is getting skipped on seeing a bad block but we're not sure because none of our dev's phones seem to have bad blocks.

In the meantime, I have posted a 04112011 update, but please take the time to flash the 04102011 update and get us the log if you had trouble flashing it. If you didn't have trouble, 04112011 doesn't have anything else in it so no need to flash it.

Thanks,

-Atin
[Captivate Android Development] TRusselo:
Is the CM7 for cappy out of RC yet?

the main XDA portal says most are as of today...
[Captivate Android Development] Kaik541:
we are not mainline, our release schedule is not at all associated with mainline devices. pre-beta it stays until we say otherwise.
[Captivate Android Development] TRusselo:
this ....http://www.xda-developers.com/android/cm7-final-available-for-all-cm-supported-devices/

talks about "all cm-supported devices" right in the title

also says all RC are coming out to FINAL

rc is not pre-beta, post beta but you would know that... (alpha, beta, release canditate, final)

and it no longer says RC or beta /whatever in this thread title.

so, thought it would be worth asking.

once again you are coming off a little snobby... (until WE say otherwise)
[Captivate Android Development] david717:
The galaxy S line isn't supported by cyanogen.
[Captivate Android Development] cropythy:
How is it snobby for the devs to be the ones to decide when this is no longer pre-beta? Honestly read the first posts and other posts in the thread before posting and it becomes obvious this is not integrated into the mainline yet and as such the release schedule has absolutly nothing to do with what cyanogen posts about. Just accept what the devs give you or learn some yourself and try to do better on your own.
[Captivate Android Development] shaolin95:
Dude they have said the same thing a MILLION TIMES...I am surprised they even bothered answering this again so to call them snobs because you cant research is quite childish. Appreciate what we got thanks to them and stop the nonsense. :rolleyes:
[Captivate Android Development] Benny1234:
SIP dialing in CM7/ Gingerbread

Can anyone verify SIP integration is working on this mod. Planning on using sipgate and wanted to verify before installing. Thanks in advance.
[Captivate Android Development] TRusselo:
well when XDA posts this.. hours ago...

http://www.xda-developers.com/android/cm7-final-available-for-all-cm-supported-devices/

thought it would be worth a

simple

YES OR NO...

monday mornings suck but you dont have to get on everyone elses case!
[Captivate Android Development] cropythy:
You're the one who jumped on the devs over an issue they have already explained literally dozens of times, which is why I said simply read a bit of the thread and realize cyanogen timelines don't apply to us.
[Captivate Android Development] TRusselo:
I didnt jump on anyone, i asked a question and the answer came off snobby.. and had inaccuracies in it.. CM7 (even for captivate) has been out of pre-beta for a LONG TIME. pre means before, before beta? its in RC (still from what i just found out) RC comes after beta stage.

someone who wants correct someone should be correct, NO?

i wasnt jumping on anyone, just correcting as i was corrected.
[Captivate Android Development] beavisrp:
Tnx man ;)
[Captivate Android Development] atinm:
The post you linked just says "CM7 Final Available for All CM-Supported Devices" but SGS phones aren't supported yet as shown here.

1. CyanogenMod 7 for supported devices is now final.

2. SGS is not officially supported.

3. teamhacksung is the only team working on CM7 directly (everything else CM7 related for SGS phones is using pieces of what we've ported from the Nexus S to our devices).

3a. Kaik is part of the teamhacksung support team.

4. teamhacksung calls CM7 for SGS phones pre-beta because we feel that we're past alpha but not beta.

Therefore, CM7 for SGS phones is pre-beta.

And by the way, Kaik answered your exact question a page or two before you posted, and he responded to you with a totally factual post including the "until we say so" part because he is part of the team that is doing CM7 for SGS phones. It isn't his monday morning that was the problem here (just defending my designated support guy, who I appreciate very much for taking the time to answer the same questions again and again so I don't have to as I would completely stop even looking at XDA if I had to be the one answering). But to reiterate, ignore CM7 (or 7.1 now) timelines until we say so.
[Captivate Android Development] atinm:
Can you please re-install the 04/10/2011 update, and run the:

adb pull /sdcard/bmlovermtd.log .

command and put up a link so we can debug the script? We need someone who had the problem to send us the log so we can debug.

Thanks a lot,

-Atin
[Captivate Android Development] Johnston212:
The theme that I am talking about is part of CM7, it's just a different color for notification settings and such. And just to be clear, when you say connected to your Google Account, do you mean have auto-sync enabled or something else?
[Captivate Android Development] HaiKaiDo:
Well after trying to pretend this project didnt exist for a month or so(to let development happen) I flashed back to cm7 just to see how things were going. I noticed that pretty much all the problems that were there before, that were big problems such as the external sd card not being shared were fixed which is awesome. I was just wondering tho, with these things being fixed (including wifi and i guess only excluding ril polling cause that seems to be one of the only "larger" problem left) I was scratching my head pondering where the battery drain would be coming from at that point. Also ive heard various answers to this(none of which seemed correct) but, can anyone tell me why cyanogen decided not to officially support SGS phones in the first place? was it lack of interest or something? And i guess my last question is how are things coming along as far as this being merged into the official dev channel (which i believe was trying to be done unless i was mistaken?)

Thanks for all the hard work bringing cyanogen mod to our phone guys.
[Captivate Android Development] atinm:
1. Battery drain - we don't know yet, no one has taken the time to debug this yet as there are other things we considered higher priority (like external sd card).

2. Cyanogen deciding not to officially supporting SGS phones - they did no such thing. The way cyanogen supports phones is by having a community of developers that own the device model and sends stuff upstream to the main CyanogenMod repositories. Teamhacksung/cmsgsteam is the team that is doing this for the SGS phones and when we're done, it'll be "officially" supported, but we'll most probably still be the only primary team that deals with the SGS device specific stuff. Think of us as the Cyanogen team developers for SGS phones if that makes you feel better - the main developers on Cyanogen know of us, work with us, and aren't shunning the phone in any way.

3. We are in the process of merging upstream - but it is a moving target because development isn't complete. Until we are at a point where nothing in the source tree is forked because it isn't merged upstream yet, we will not be "official". There are some reviews pending, and some merges still to be done.

Finally, there is nothing that will change when we are "official". Our team will still most probably own development for SGS phones, and so the goal is mostly a development team rather than a user visible goal except for the fact that it would be the CyanogenMod build bots that do nightlies and the RC, Final etc designations would have another layer of reviews from the core Cyanogen team on top of what teamhacksung/cmsgsteam does.
[Captivate Android Development] HaiKaiDo:
Ah thank you very much, very informative. As i was reading one more question popped into my head. Since we are using Gingerbread from another phone is that whats causing us to have to install this in a very different way than normal. and i ask this because i was thinking "what happens if we get an actual 2.3.3 for our sgs phones". would that change the way things are going for you guys?
[Captivate Android Development] ninjuh:
I don't think you're right at all. my account is still not auto syncd, I rarely check email or anything, and 90% of the time everything is green.
[Captivate Android Development] Kaik541:
so I guess the fact that they don't turn green until you tie a google account means nothing? or that it's what google said it means? or that it's fairly common knowledge that this is what it does? (a quick google search for "nexus s green status bar icons" shows a lot of results about being connected to google)

edit: if you'd like I can be even more specific and point out that page 27 of the "Android Users Guide" provided directly by google has this to say:

http://static.googleusercontent.com...m/en/us/googlephone/AndroidUsersGuide-2.3.pdf
[Captivate Android Development] techmik67:
not syncing with it, not downloading from it.... *connected* to it. as in you *could* sync if you wanted. you want to test? wipe your phone..... *dont* install gapps..... watch how it *never* turns green......
[Captivate Android Development] atinm:
I doubt it very much unless Samsung puts in MTD, yaffs2 support instead of BML in the bootloader which they are unlikely to do. The problem is that Samsung's bootloader is closed source and only understands a proprietary flash format (BML). All that is different from other ROMs is the flashing of the initial kernel to allow a reformat to the new partition scheme, after that updates get installed as always so we're not that different really anyway. The Reboot into Recovery and Reboot into Download mode will never work unless they open source the bootloader or start using an open source filesystem for the params.lfs that is used to pass arguments to the kernel.

The things that will change when Samsung releases source code for Gingerbread is that many of the things we cannot fix in the kernel, or have been having trouble with (like Audience chip support) will start working because we will have source code for the chips we have no documentation for and whose drivers have changed a lot in going from froyo to gingerbread.
[Captivate Android Development] HaiKaiDo:
Ah thanks once again! That was actually a nice little read haha. Been wonderin about some of that stuff like the no download mode commands and what not :].
[Captivate Android Development] nkrick:
Does that mean that the N1 Audience drivers can't be used on the Captivate?

Edit: Sorry, looks like some of that was addressed in the Q&A thread yesterday which I hadn't gotten to yet. Too bad it isn't a little easier to get it working. Has Samsung said they will release Gingerbread source for the Captivate? I know the i9000 is supposed to get GB, but I hadn't seen any official announcements about "other" SGS's.
[Captivate Android Development] atinm:
Answered ad nauseum in the last day or so.

Not directed only at you, but I am done reading XDA . . . I asked for help from the people who had trouble flashing the 4/10/2011 release and have received nothing while I've been wasting my time answering questions that have been answered multiple times already.

I will update the thread title when I upload new updates, but am done answering stuff until I am ready to deal with this again. Kaik and techmik will answer questions as they see fit, so you do have teamhacksung representatives around.
[Captivate Android Development] c0ldburn3r:
Don't blame you. Seems like XDA has the effect on everyone. Nice work though!
[Captivate Android Development] nkrick:
Looks like I didn't do my edit in time.

Since Audience support is not usually a hot topic of conversation, I made the mistake of responding without getting up to date on the Q&A thread first.
[Captivate Android Development] joedon3:
I personally wouldn't use an ATT Gingerbread ROM. I get much better performance out of an i9000 ROM and even better from CM7.
[Captivate Android Development] skoNuff:
Sorry I haven't had time to do this yet atinm.. but when I get home from work today, I will install the 4/10 update again to receive the WiFi error and post the logcat.

Just so I post the correct linked file.. I would do exactly what I mentioned above then immediately go into Terminal Emulator and type:

logcat > /sdcard/logfile.txt

Correct?
[Captivate Android Development] atinm:
No, please just install and then on your desktop that is connected to the phone, in a terminal window on the computer:

computer command line prompt$ adb pull /sdcard/bmlovermtd.log .

Or just mount the disk over usb - the mounting of the internal sdcard should still work, and copy that file off the phone. We want the log file that was created during install - we explicitly created that log file to help us debug this.

Thanks,

-Atin
[Captivate Android Development] skoNuff:
Ok.. since I'm a lot more comfortable with mounting the disk via usb then I am running adb.. I will do that.. I'll install, then grab that log file and post it here. Thank you and the team again for all your amazing work thus far.
[Captivate Android Development] zas0006:
That explains why I couldn't find the file... I am redownloading the 4-10 update now. Will post back once I have the log for y'all.

Edit: I just flashed from a clean download via my PC and now I don't have the problem. Which I guess would explain why that file Atin wants is not on my sdcard. Any thoughts as to anything else I can do to help will be gladly accepted as I don't want cm7 to suffer because the users can't help when asked.
[Captivate Android Development] atinm:
Make sure you got the 4/10/2011 update if that is the one that failed for you. I put in a workaround for the 4/11/2011 update and that might show up as the latest file on sourceforge.
[Captivate Android Development] hernan078:
hi i have been using this.rom over a month i dont know when but somewhere in this time an update started vibrating my phone while.i was talking with someone, i turn the settings off and today im getting the vibration again please help me, this is the only bad thing i have experienced with theme, thanks!
[Captivate Android Development] waffle418:
I had the issue, however the file doesn't show up on my sdcard at all... could it go to another location?
[Captivate Android Development] rabi347:
has anybody been able to find a modem or radio with good high in call volume? i have tried KC1, JL3, JK4. But the,in call volume is so low, I have to go to a really quiet place to hear someone at the other end.
[Captivate Android Development] Denoh:
Almost home from work Atinm. I will post a link to my log pronto.
[Captivate Android Development] skoNuff:
Atin,

I re-installed 4/10, WiFi error still occurring. I can not locate the log file on my sdcard. Its on the root of the card right? I ran a search on the sdcard and phone system just to be sure, for a file name as such and could not locate it at all.

Maybe the bad flash is causing the log file to not show up as well?
[Captivate Android Development] Denoh:
+1.

1)Tried adb pull and got: remote object '/sdcard/bmlovemtd.log' does not exist.

2) Mounted sdcard on PC and cannot find logfile.

3) Used root explorer and went through the contents of the sdcard and cannot find file
[Captivate Android Development] skoNuff:
Figured out how to run adb...and also get the "does not exist." when trying to pull the file. :confused:
[Captivate Android Development] zacharias.maladroit:
seriously guys:

don't brainlessly copy & paste a command with a typo: :D

/sdcard/bmlovemtd.log

should be

/sdcard/bmlovermtd.log

mark the "r"
[Captivate Android Development] Denoh:
Tried both, bmlove and bmlover. Got brains too. Learn to express yourself in a less condescending manner. I even did a search of my sdcard using root explorer and no such file exists.
[Captivate Android Development] atinm:
Thanks - I see something that was overlooked by me before, so the file may not exist anyway. Sorry about that. I'm working on a fix right now. Thanks for trying though, not your fault the file wasn't there!

-Atin