yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mikehe:
good morning all, i am new to cyanogen, was running Mosiac, battery life was killing me for some odd reason, so i ended up jacking up my Cappy figured I might as well give Cyanogen a try since i have to start from scratch, after pulling hair and getting back to froyo stock and then rooting i finally got it loaded, now for the heck of me i cant seem to get voice option on keyboard to work, Mic isn't there am i doing something wrong.
[Captivate Android Development] mnjm9b:
The real issue is that we (captivate users) are using a cm7 build that is built for a different device...

It just happens to be modded to work for us.

So if what you are saying is true...

Then what is really needed is a cm7 build that is truly a captivate build.

And that equates to having another device team just like the dozens of others.

Sadly it seems very unlikely being that this "hacked" version already has such good support.

I hope you are talking out your ass when you make such definitive statements. I really think a choice is coming.
[Captivate Android Development] Time_Zone:
I switched from stock because calls kept dropping and I would lose data connections all over Denver. I9000 fixed this but then I had no audience chip and a battery bug. I fixed the audience problem by using a bluetooth with built in noise cancellation. I fixed the battery bug by switching to CM7. What is really sad is that it is ATT and not samsung that hobbled this phone. We as consumers should be able to fight back against this sort of thing. It is abusive to consumers. I wonder how much the decision to hobble the captivate centered around iphone profits. Does this post seem off topic to you? I think we should all get to talking about improvements, changes and the awesome work that is done here by the CM7 team instead of complaining about something that could be solved by going to stock. You wan cruddy reception but great noise cancellation? Stock is waiting for you.
[Captivate Android Development] EnemyOfGlaDOS:
Sup dude from Denver!

- dude from Boulder.
[Captivate Android Development] nkrick:
I am wondering the same thing since "HSPA" should have no direct relation to enabling Audience support. HSPA is separated into two things, download (HSDPA) and upload (HSUPA). AT&T allows HSDPA on their modems, but they disable HSUPA (they allow UMTS for uploads). Since an AT&T modem with HSUPA disabled works fine for data on CM, I can't imagine why the entire ROM needs to be changed. Even if changes have to be made to only support UMTS for both download and upload (which I would find strange since AT&T modems currently work fine for data), there is already a change to toggle HSPA/UMTS in the latest nightlies, so that part of the work is already done.

I don't know much about Android development, but I know a bit about Linux. It seems to me that it should be possible to include Audience driver support in the kernel and put a toggle in the Aries app menu to toggle the support on and off. To actually enable/disable support in the kernel could use something like the modprobe blacklist.

It is entirely possible that it is more involved because there are other framework requirements and/or modem issues related to using software noise cancellation in the modem. If the issue is in this area (and not related to HSPA), then I can understand that it may not be possible to allow Audience support without a different build tree.

If it truly is the case that there are significant changes necessary and there can only be one official CM build for the Captivate, then (and only then) I think the official version should have Audience support and not HSUPA support. My reason for saying this is because it should be possible to flash the i9000 CM build and then flash a re-oriented kernel (like the current Glitch) to still have CM with HSUPA support on a Captivate.

Until Kaik, Atinm, or another recognized member of Team Hacksung comments on this, the issue is not closed. Even if the information was obtained legitimately, until there is official word from Team Hacksung, I will assume there is no final decision.
[Captivate Android Development] RichMD:
I think we all want everyone to have a choice of which radio support to use. It really isn't helpful to suggest anyone wanting a different option to go to stock, etc. There are a lot of reasons that people would want either option but still have the awesomeness of CM7. This thread is becoming more negative than I have seen before.. I mean no offense to anyone but let's try to keep it a little more "friendly" - my two cents...
[Captivate Android Development] mikehe:
Nothing on pointing me in the direction of how to enable the mic on the keyboard
[Captivate Android Development] loraque:
Make sure you have Voice Search installed. if not, install from the Market. If it is, select a different keyboard. Should be there...
[Captivate Android Development] mcala:
Go to the market and install Voice Search by Google. While there install any other missing Google apps under "more by Google". Don't forget Flash player also.

Nvm, he beat me to it.
[Captivate Android Development] shopealope:
Has anyone else had problems with sound quality when recording a video in HD? I'm considering reflashing but wasn't sure if that would do anything for me. I first flashed cm 167 and now I'm on 171 and none of them have fixed it for me.

Sent from my Cappy
[Captivate Android Development] bmwenger:
Bootloop issues

OK, this is the second nightly I've tried since the stable version and all I'm getting are boot-loops. I can do a clean install (factory wipe/data wipe) and then it will install. I am then able to get all my apps re-installed using TiBu (I'm only restoring user apps and data, not system apps). I then get the phone setup the way I want and it starts to boot-loop for no apparent reason. Before I go back to a backup I made, is there anything I can do to prevent this?

Thanks so much.
[Captivate Android Development] RichMD:
Are you restoring/reconfiguring anything like voltage-control or other kernel related apps? Are you using a custom kernel?
[Captivate Android Development] bmwenger:
I have voltage control installed, but I'm not doing anything with it. I am also using the stock kernel. The last adjustment I made before the boot-loops started was to set a ringtone.

I've restored my backup since I needed the phone for work, but I'll try again tomorrow.
[Captivate Android Development] littlewierdo:
Lets put it this way, if they are going to provide a choice between audience chip and HSPA, great (based on my VERY limited understanding, this is not doable without having to flash something to switch between the two, it cant just be a toggle between one or the other, again, based on my LIMITED understanding of the two).

If this is not the case, then all the information I have read on the problem is wrong.

So yea, if speaking from the knowledge of all of the information I have read is 'talking out my ass', fine, I can accept that notion. Based on that assumption, 99% of all the posts here are people 'talking out there ass'. In fact, most of the information we learn in school/college, documentaries, books, etc. is 'talking out your ass'. In fact, I can state Mount Everest is 29,029 feet above sea level but again, that is 'talking out my ass' because I didnt actually measure it myself, I read it in a book (go figure, its one of those weird factoids I remember).

I am fine with being wrong and I do agree that if it is implemented as a toggle in the rom, that would be great. But my point in this whole thing was, I dont think Cyanogen is going to have two different rom downloads, one with audience (without HSPA) and one without audience (with HSPA).
[Captivate Android Development] Gromlakh:
I strongly suspect it's not going to take two different distributions to make audience chip support a reality. The issue, as I understand it, is kernel + modem, and little else. I'm certainly not going to say it would be easy to do, especially if Samsung isn't releasing the source to the modems that support the audience chip. But it appears doable.

I don't think too many people honestly expect a toggle. More likely this would have to be accomplished with an alternate kernel that supports the audience chip + a Captivate modem, both of which would have to be flashed over the stock CM7 files.
[Captivate Android Development] nkrick:
"...if they are going to provide a choice between audience chip and HSPA.." directly contradicts your previous statement which was, "The CM team has decided to go with HSPA." In your latest post you do not seem sure what Team Hacksung is going to do. In your previous post you made a direct statement saying that Team Hacksung decided to go with HSPA. This is where "talking out of your ass" comes in.

The issue is that you presented your previous post as absolute fact when it is actually your understanding of what is going on. Kaik has mentioned the difficulties and the fact that HSUPA and Audience support cannot exist at the same time. But unless there is another source of information from Team Hacksung outside of this thread, there has been no definitive statement from Team Hacksung saying that they are, or are not going to work on Audience support. The last official word from Team Hacksung on this issue was from Atinm who said:

"For now" implies that this is an issue that Team Hacksung will revisit in the future. So, people have been making their opinion known about whether or not they want Audience support so that in the future Team Hacksung can make a decision based upon what people are asking for. This in no way means that Team Hacksung has to take our opinions into account, but if no one says that Audience support is a feature they want, then there would be no reason for Team Hacksung to consider adding it in the future.
[Captivate Android Development] RichMD:
Agreed. If it is possible (which many of us are assuming) then I would "guess" that most of us would expect a flash/reboot to switch back and forth. That could "probably" easily be scripted so you could be using one and click an icon that would reboot into recovery, flash a different kernel and modem and reboot and you would be set for the other. That's assuming you don't have a complicated setup where you run other scripts all the time dependent on a certain kernel, etc.
[Captivate Android Development] mark72501:
Ditto on this. Links are broken for older versions, though they are in the list. Another mirror somewhere?
[Captivate Android Development] nbell13:
I have it saved on my computer... May try to post it somewhere when I get home from work (around 11:30 pm central time)
[Captivate Android Development] cfili:
I have all kinds of problems recording in HD including stuttering and audio lag. I've tried overclocking and that did not help much.

Sent from my SGH-I897
[Captivate Android Development] techguy615:
I had the same issue. I was in a reboot loop myself. I pulled the battery and 3 keyed it to get out of the loop and back into CWM. Did a fix permissions and flashed again. Seemed to have worked fine after that. YMMV, but worth a shot.
[Captivate Android Development] mnjm9b:
just fyi...

i never accused anyone of talking out their ass...

i was HOPING that you were...
[Captivate Android Development] nbell13:
Here's the link to nightly #163, for those who wanted it...

http://www.multiupload.com/SBMV8B6ORN
[Captivate Android Development] mgfjd:
163? 171 is superior than any past builds. My quadrant scores are 2500 now, and the phone speed is unbelievable.

Btw, anybody playing with governors and set CPU? The phone is too fast and don't mind decreasing the speed to increase battery life. My governor settings are:

Conservative

up: 75

down: 30

Sampling: 200000

CPU scaling: 15

Anybody with better settings?
[Captivate Android Development] littlewierdo:
I suppose I should have been more clear for the 'literal net'. For now, they have decided to go with HSPA.

But, to make my point LOUD AND CLEAR, someone please point me to where the audience chip support is if they havent decided to go with HSPA.

The fact is, they dont support audience chip and the statement I made was absolutely true.

I never said or implied this would not change, I simply stated they decided to go with HSPA, even if it is only temporary.

This seems so black and white to me and a debate over semantics is a waste of all our time.

Right, well, its been about a 50/50 split, thus my point. People voicing their opinions for one or the other doesnt really change the fact that 'if' one is implemented without supporting the other, you are going to irritate the other half. Some people want better voice quality, some want faster upload speeds and we can all see that the split is pretty even. I dont think there is a point in users continuing to say 'I want audience chip support' or 'I want HSPA support' along with listing the many reasons why they want one or the other.

This 'is' two different distributions. Two different kernels means that all changes made to one kernel have to be made to the other. This also means that changes made to one kernel may affect the other kernel in adverse ways, thus BOTH kernels have to be supported.

Again, this doesnt stop another developer from picking up the kernel and reworking it to support audience support (Glitch kernel is an example of a kernel that does something along these lines, while not to support audience support, it supports other features CM doesnt have).

Im also not saying hacksung wont ever support it or that it cannot be done, Im just saying that based on what I know of the problem, how Cyanogen builds are made and common sense, you wont see two different versions of CM for our phone (or 2 different kernels, which would be practically the same thing).

So, the only way this will happen is one of four ways (based on my understanding).

1. Modifications to both the kernel and modem to allow support for both (assuming the hardware can do both at the same time). Since I dont believe we have source code for the modem portion, this would be a problem (I could be mistaken here).

2. Separate kernel + modems for one feature or the other. Again, I dont see CM doing this, it would be a support nightmare.

3. A 'settings' toggle that would require a reboot that might either toggle between the two using the same existing kernel/modem combo (I dont buy into this being easily doable, if it was, it would have already been done) or would flash a different combination of kernel/modems (again, not likely because we are talking about two different kernels).

4. Another developer picking up the kernel to make the required changes for audience chip support (which would require all Cappy users to use the modems that ALSO have audience support) and incorporating the changes CM is making along side with the nightlies.

I think number 4 is the most likely.
[Captivate Android Development] bmwenger:
Thanks for the help. I have had it working on nightly 170 for a few hours now with everything but voltage control restored. I'm guessing that even though I wasn't using it, that may have been my problem.
[Captivate Android Development] dave1977nj:
Ever since Build 169 it broke my USB connection to my computer. All it does is charge the phone. Any help would be appreciated thanks.

:confused:
[Captivate Android Development] RichMD:
I would just make sure it isn't the cable. There are some that will only charge the phone but not connect USB storage.
[Captivate Android Development] loraque:
Did anyone notice if those camera tweaks that went in a few nights ago had any effect on the HD video recording 'skipping'?
[Captivate Android Development] ghost13:
i'm still running 168 and have to admit it is LIGHTNING fast compared to the stock froyo i was running previously!

any advantage of updating to 171? i will loose everything that i have installed if i upgrade ct? i guess i'll have to learn how to use titanium
[Captivate Android Development] mikehe:
I am enjoying my CM7, Thank You All
[Captivate Android Development] RockRatt:
You can always update nightlies without losing your apps, Widgets, settings. Just wipe dalvich cache ONlY before flashing then nothing g will be lost.

Sent from My KickAss CM7 Captivate
[Captivate Android Development] Aus_Azn:
Just out of curiosity, how often do you guys update the nightly on your phone? I flash once every 10 nightlies.
[Captivate Android Development] Time_Zone:
That is pretty much what I was doing. I updated to 171 because I was curious about the hsdpa/umts toggle though.
[Captivate Android Development] cotr:
Nightly 172 killed my phone

hey guys,

I went from 168 to 172 and have been getting constant FC. I wiped Dalvik and went back to 168 but still got FC. So I wiped Dalvik and went to CM7.1 but still get FC. went to 171 nightly and still get FC.

Any ideas?
[Captivate Android Development] nkrick:
For anyone using Nightly 168-172, you may want to update to 173 sooner rather than later. The changelog shows a fix for Aries Common (which includes all SGS phones) to fix a symlink for /datadata /data/data. The symlink was apparently inadvertently removed in the aries cleanup that was first implemented in Nightly 168.

I am actually somewhat surprised that the missing symlink isn't causing noticeable issues.
[Captivate Android Development] Kaik541:
it only affected fresh installs (hence how it was discovered). since the symlink was created in /data and /datadata, it would only be noticeable to a current user if they were to factory reset.
[Captivate Android Development] dave1977nj:
it's not the cable.. I have 2 cables. Tried both. the only thing that works is reverting to 168.:confused: I have done a full wipe to 173 and still the same issue. Still can not connect to usb storage or debugging. Tried another computer also...
[Captivate Android Development] Time_Zone:
Have you tried rebooting your computer. I have a server at home that loses usb connectivity on this phone until a reboot.
[Captivate Android Development] dave1977nj:
Yes I have still no go :(
[Captivate Android Development] tiuk:
Do you have the Nexus S drivers installed (not the Samsung ones)?

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] cotr:
constant FC from nightly 168 up to 173

I keep getting FC when installing any nightly or RC7.1. I always wipe Dalvik before install via CWM.

Any ideas to restore other than a full wipe and rebuild?

BTW, had been using 168 perfectly fine. Issues started on update to 172.
[Captivate Android Development] mikehe:
i flash nightly evey day now since becoming a CM7 user, another question please, how can i disable the lights from coming on when ever i get a email or Im or so....
[Captivate Android Development] RockRatt:
Once you ha e flashed the .sweat nightly and IF you have an issue just go back and reboot to recovery, wipe dalvich cache, THEN flash the nightly again right on top. I think it may be due to the kernel changes sometimes between the RC and nightly versions but I could be wrong. BUT I do know from my experience that flashing it twice helps out for weird issues lime this.

Sent From My KICKASS CM7 AT&T SGS2

Try going into SETTKNGS, CYANOGENMOD SETTINGS, INTERFACE, LED notifications, ADVANCED, UNCHECK PULSE AND MAYBE RESET ALL COLORS AND APPS. Or you can go into Unconfigired and or miscellaneous, EDIT CATEGORY SETTINGS, LED MODE, FORCE LED OFF

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Android Development] cotr:
wow... all that flashing and rebuilding but i never thought to just double flash. thanks!
[Captivate Android Development] ghost13:
sounds like i need to flash 173 and get rid of 168! first time updating hope i dont F stuff up lmao
[Captivate Android Development] tiuk:
I check the changelog daily, and flash if there's a change specific to our devices.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] ThisWasATriumph:
Thank you. This was helpful.
[Captivate Android Development] Aus_Azn:
For some reason, the UMTS signal isn't particularly good here (i.e. I see a drop to EDGE/GPRS speeds). So I have to remain on HSUPA for a serviceable signal.
[Captivate Android Development] SnakeHaveYou:
So.. If i flash Nightly 173 over 168-172, my "new" /data/data (1.72GB size :) and ALL my apps installed in the internal memory without any FC) will be the "old" /datadata (170MB :mad: ) again???
[Captivate Android Development] hauj0bb:
The 'Sound' toggle in the notification power widget hasn't worked for me since the last several nightlies.

Can anyone else confirm?
[Captivate Android Development] mcala:
U must configure it under CM settings. I think its under interface/notification power widget/widget buttons, go to the bottom to set sound modes.
[Captivate Android Development] pvr:
I can confirm the "error" and the fix. It simply changed something that required a reconfigure of all options under the power widget :)

working perfectly as usual after that though ;)
[Captivate Android Development] gilpdawg:
On 172, running glitch and undervolting everything -100, I currently have 3 hrs. 40 min. display time and still have 10 % left, which is almost as good as I could do with Pinnacle, so the last reason to not use CM is gone if you have everything configured right, IMO.
[Captivate Android Development] mikehe:
is there some reason why i cant download my nightly 174
[Captivate Android Development] mcala:
Downloaded fine on my PC.
[Captivate Android Development] psycho2097:
Did a full and complete wipe , everything including sdcard. Installed cm7.1, got lots of fc's , wiped , then loaded up 173. Perfect!

This is the first time i am using cm7 after about 4-5 months...i usually use miui(galnet's version, i love his theming) both for battery life as well as perf and choice of theming.

Last time i used cm i was horrified at the battery life, but i guess it got better as did miui(well since miui came from cm).

Now, using go launcher, green power, stock kernel and modem i get 13-20ma standby, which is as good as miui, which lasted me 36-40 hrs with 2hrs screen(1800mah gs2 battery). Thoroughly impressed with the performance and speed! even looks are awesome(using ICS cm7 theming, loving the overall theming!)

Looks like cm just earned 2 months of my phone time..!

PS- to improve on the battery life, any1 got any ideas about kernel modem options?

I know glitch battery is worse than stock as far as battery (on miui), i used it only for voodoo color. Since color settings are included in cm (and i love the default color), i dont see particular need for glitch. how about neo? always gave me fcs on miui.

As for modem, kg3 gave me best coverage, but its standby is like 25ma...so staying with stock, unless anything better is suggested. I have tested out jk4, jv5, jve, jvk, jl2 on miui, nothing beat kg3.
[Captivate Android Development] SweetwaterBurns:
If you make script with whatever commands you used to put move things around in /data/local/userinit.sh it will persist across installs and readjust things for you.

I'd be more specific but I don't know exactly what you did.

If all you did was delete the /data/data symlink and replace it with a directory, it will persist. Look at my past posts, I've written two different ways to deal with the datadata issue that persist across flashes but i'm too lazy to look them up right now.
[Captivate Android Development] psycho2097:
okay noob here... care to explain pls? i have never had probs with my datadata.but i read up on it and found that cm/miui are not able to use the full NAND datadata capacity that samsung roms can. i did full factory reset, kernel cleaned, everything formatted and installed 173. What do i run the risk of, and how do i prevent it?
[Captivate Android Development] Gromlakh:
I would also be interested in anyone's recommendations as far as modems for battery life. I'm on Glitch and undervolting right now with the stock modem; anything I can do to squeeze just a little extra juice out of my Cappy is nice.