yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] XsceneXhippieX:
I agree, afaik the "rom" source has been released because android = open source

BUT no carrier/whatever has the legal obligation of releasing their modem/radio source, leading me to believe that the i9000/i897/i896 combined modem theory floating around these threads will never happen, my personal opinion with the stock cm7 modem in my area, call quality=VERY acceptable, i mean if i can call somebody, they hear me, and i hear them, im okay with the call quality, you know? i have never noticed anything "bad" about call quality, and a SMARTPHONE is only SMART because its data capabilities (processing and networking), thus if you use your phone primarily for calls then why do you have a custom rom on your phone? why put so much time tweaking something you occasionally punch numbers into and talk to people on? i dont know how this is an argument if calls still work on the HSUPA/HSDPA enabled modems, I personally have an android to USE its internet connectivity for unlimited means, and faster data speeds make that MUCH MUCH more enjoyable, i think others have the same views or i897/i896 modems would be stock on cm7

my 2 cents
[Captivate Android Development] nkrick:
I don't think anyone who is asking for audience support is suggesting that audience support should be the only option. Personally, I realize that there are people who prefer faster data to better voice call quality. What I am asking for is the option to choose either a audience kernel or a HSUPA kernel.

While I can generally use i9000 modems, I do experience some problems. For example, my data will randomly drop off or drop back from HSPA to UMTS when I am using my phone. Generally within a few seconds it will pick back up and start working again, but I need to refresh or reload my app because the drop was enough to cause an error. I would appreciate the flexibility to use an AT&T modem where I do not have this issue. Unfortunately, I do have to make early morning conference calls from my cell phone, usually while driving, so currently the voice quality issues that exist with CM and an AT&T prevent me from being able to use it. (Also, the audience noise cancellation would be nice for driving.)

Android is all about choice, and while you can point out that I can choose to use an AT&T based Samsung ROM so that I can use an AT&T modem, I think most people using CM realize that this is a poor option when CM could support an AT&T modem. All some of us are asking for is a choice between 2 (or more) kernels, 1 with Audience support and 1 with HSUPA support. If Team Hacksung has no interest in adding Audience support, perhaps one of the other MTD kernel devs has some interest.
[Captivate Android Development] cotr:
The past four nightly builds have borked the ringer volume/vibration thing. Can't change modes using the status bar.
[Captivate Android Development] RCDuke:
You have to go to settings, interface, notification power widget, widget buttons, then at the bottom are the settings for that.
[Captivate Android Development] MechaGen:
I haven't seen many complaints about SOD (sleep of death) which is strange, since mine & my wife's, both on CM7 Nightly's, have been suffering from them for several weeks. I'm on n167 & the wife's on n130.

I thought it might have something to do with OC/UV but her's hasn't been modified and I've removed all UV, only running 1.3ghz.

The other thing these two phones have in common is the baseband. Both are using UGKG3. The original baseband sounded terrible and didn't support 850mhz, which is necessary where I work.

Could the modem I'm using be causing the SOD's? Any other suggestions?

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Captivate Android Development] cotr:
the button is there, but pressing it doesnt do anything. the only way to change modes is to hold the power button and change it there.
[Captivate Android Development] tiuk:
I did this yesterday and have been using my gps every time i drive to test. It works a lot better now, on one drive it consistently tracked me the whole way. Huge improvement.

I also noticed if i use nav in compass mode and it isn't calibrated it actually causes me to lose tracking more frequently, especially when i turn. If i use overhead mode it rarely if ever loses me, and when it does i regain the lock much faster. I guess i thought the compass would only effect the visual display of the map, didn't expect it to mess with tracking. So I'll have to make sure to calibrate more frequently. Not sure why i lose calibration so quickly, guessing it either happens when i flash a nightly or is caused by the holster i use at work, which contains a magnet.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] nkrick:
I don't think a modem will affect sleep death. You can try increasing the minimum clock speed to 200 Mhz, this helps some people.

As far as modems go, the default modem (JL3) does support 850 MHz. If for some reason 850 Mhz is not enabled by default for you on a modem that supports it, the Samsung dialer codes work on recently nightlies, so you can go in and enable the comi-bands.
[Captivate Android Development] RCDuke:
At the bottom of the widget button page, there are toggles to set how you cycle through the sound modes. It isn't set to anything by default, so pressing the status bar button wont do anything.
[Captivate Android Development] dave1977nj:
Build 169 Broke my USB connection to my computer reverted back to 168 all is well now.
[Captivate Android Development] raz123:
Dear Devs,

Thank you for your impressive work. CM rocks.

Christmas is around the corner, and I was wondering if it would be possible to throw in-call recording? :)

The latter is already present in the stock (asian) rom.

With Samsung-based roms, copying over 3 (originally from asian roms?) library files (libaudio.so, libaudioflinger.so, libaudiopolicy.so) will allow call recording by applications (3rd party or SGS), as long as Samsung's phone.apk is present.

Is it possible to have something like that under CM7?

Cheers.
[Captivate Android Development] Kaik541:
cyanogenmod will never support call-recording as it's illegal in, like, 90% of the world.
[Captivate Android Development] nbell13:
Curious why anyone would want that feature, anyway. I sure as heck don't.
[Captivate Android Development] raz123:
Source?

It's legal in many, many places.

It's also illegal in others.

Case in point: Asian Samsung roms.

Moreover, concerning the legality aspect, isn't a lack of shutter sound also illegal in SOME places? Yet, cyanogenmod allows you to disable it.

The shutter sound issue was solved by letting the user choose depending on his local laws. Why wouldn't that be the case for call-recording?

That's what Android is all about: choice.
[Captivate Android Development] Gromlakh:
I can't speak for the rest of the world, but at least in most of the U.S. it's legal to record calls as long as one party consents to the recording even if the other person has no idea it's being recorded. Not all states allow that; some require that both parties consent to being recorded. But, as to why someone would want that, the "legal" (as in, use in legal proceedings of any kind) implications are obvious. Regardless of what your claim in court is, it is always much better to have the other party/defendant/cop/whoever on tape saying whatever damning thing they said than just coming before the judge/jury/whoever without any evidence to back you up.
[Captivate Android Development] shopealope:
I'm on nightly 167 (about to update to 169) and the only problem I have seen so far is that my sound quality on video recording is really bad. I have it set to HD and I'm overclocked at 1.4ghz with the glitch v12 kernel.

Sent from my Cappy
[Captivate Android Development] pvr:
Disclaimer: this is not CM7 dev for Cappy - simply a few thoughts on in-call recording.

Let's not confuse phone recording to phone tapping since the latter is by a 3rd-party where the former is one of the parties involved.

Anyhow, the case is very interesting as noted - disabling camera shutter sound is illegal in a few countries (have not searched throughly for links) so why would two related features have different justifications?

Quite a few examples where it is legal and illegal:

http://en.wikipedia.org/wiki/Telephone_recording_laws

I for one don't think I'd ever use - I say nothing of interest on my phone calls neither do the other participants.

Food for thought...
[Captivate Android Development] mystichobo:
Tell me how it goes! I'm on 166, and I've managed to beak my market trying to do zdunes ics status bar mod. So I'll probably update and do a clean install very soon.
[Captivate Android Development] :
Audience Chip

I read earlier that one of the devs said they could put audience chip support in, but would lose HSUPA.....Can you upload a version with audience chip support for those of us that actually enjoy call quality and get the best quality/signal with Captivate modems? I mean, after all it's taking away from a major feature that was put into the phone for a reason. This and judging on the comment, you seemed like it would be easy to implement it.
[Captivate Android Development] zeroonea:
I cannot use adb when I flash cm7. Anyone work fine with adb on cm7? I already turn on usb debugging, install usb driver. But when I plug usb cable, my window say, they need install driver, and I tried to install but failed :(. Usb storage is work fine.
[Captivate Android Development] CptTwinkie:
You should have continued reading. All of the details concerned were discussed and the reasoning behind the devs decision to use the current modem. It's a situation of one or the other and faster data wins out over voice quality.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] mystichobo:
Which USB driver? CM7 requires the google nexus s driver.

Not the captivate USB driver.
[Captivate Android Development] goob1284:
Is there an app or setting in which I can long press the back button and it will close the app? It was on miui and I liked it
[Captivate Android Development] cbasse:
Application menu - Development - stop app
[Captivate Android Development] goob1284:
Thank you!!!!:)
[Captivate Android Development] mnjm9b:
Well if your following the changelog...

It appears that we might just have a choice. (soon...?)
[Captivate Android Development] :
I did continue reading, and what I am saying is that, once again, this is a phone, and in the long run I know many people would prefer voice quality over data speed.
[Captivate Android Development] shaolin95:
The problem ...is there is NOTHING wrong with voice quality so why lose speed for what? I dont think anyone is planning to record a CD album over the phone. ;)

Currenty quality is just as good as any phone...never had a complain except when I tried some wacko modem that is bad..so far only 2 modems have done that for me.

If it was a case were voice quality was a problem indeed it would be a priority but that is not the case.
[Captivate Android Development] RockRatt:
+1

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Android Development] :
I agree that voice quality is the same, but the noise cancellation is unmatched. Using multiple modems in a somewhat noisy environment people said they had trouble hearing me, but on stock UCKB2, the first thing people told me, was that they noticed a significant change in background noise. Ex: I was walking past my college's rather large band practicing and the person on the other line had no idea there was a band in the background.

I am by no means saying I will not use CM7, I just think it would be nice to possibly implement this in (maybe a second version).
[Captivate Android Development] littlewierdo:
Regarding recording phone calls, there are apps on the market that provide this functionality, maybe look there.

Regarding HSPA vs audience chip support, based on my understanding, essentially we are stuck using one or the other because while we have the source for Android 2.3.3 that makes MOST of the phone work correctly, we dont have the source for the modem. If we did, Im sure it would be very easy to implement BOTH. And the devs arent going to try to write the modem from scratch without a source, therefore, HSPA wins. The problem is, the majority of folks on ATT arent even in an HSPA area and therefore do not benefit from it. Im sort of mixed on how I feel because I live in an area that DOES support HSPA so I dont know which I would prefer given the choice.

And on a more personal note, I certainly would like to know why I can stream audio to my Bluetooth FM transmitter but the instant a phone call comes in, the bluetooth option is disabled on the phone screen and it stops routing audio until I end the phone call, at which point, it begins streaming audio again.

I understand the Bluetooth spec is a messy pile of steaming poo, its amazing BT even works given how messy the BT stack is, but, this is really strange. It seems like every time I mention its a problem, it gets fixed on the next nightly (or two) and then broken again one or two nightlies later...

Oh, and Id love for the Nightly changelog to be fixed, its making it impossible for me to track down the changes that are being made that might be affecting my BT device (plus Id love to have a current understanding of what was included in the Nightly change wise).
[Captivate Android Development] tiuk:
Er? i don't see anything wrong with the changelog..

http://cm-nightlies.appspot.com/?device=captivatemtd

Edit: or are there additional changes that aren't being displayed?

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] raz123:
Been there ;)

None that work with CM7.

In regards to the data speed vs sound quality issue, having the power to choose would again be the best of both worlds.
[Captivate Android Development] loraque:
Even for people that don't use it as a phone a lot... the Audience chip also improves the accuracy of Voice Search. That I do use quite a bit, to send texts in the car or just in general. Better than typing. Non-Captivate modems you can tell from looking at the crummy waveform it shows when you use Voice Search. You can literally SEE that the phone does not read your voice as clearly from the background noise with a far larger waveform and very little dipping between words.

It really does make a difference :). I won't give up data speed for the less than 100 minutes per month I spend talking on the phone, but I do talk AT my phone much more, and especially while in the car at freeway speeds, Voice Search is way more accurate with a Captivate modem.
[Captivate Android Development] ThisWasATriumph:
My dad basically uses his phone for a living. He has to talk to customers in noisy environments all day long. I put CM7 on his phone because the samsung roms were unstable and constantly freezing and slow. It works much better now but now he says that customers are having a hard time hearing him... He doesnt need fast speeds as he is usually in rural areas anyway. I, on the other hand, would take speed over noise-cancellation because I rarely use mine to call. -Just my anecdotal reasoning supporting a choice for i897 modem support.
[Captivate Android Development] double RL:
Try kg3 modem. Only one that is clear for me
[Captivate Android Development] RichMD:
Voice-search is a good point. I'd love to have the option. It would obviously require a reboot to switch but that would still be great. I would probably leave it on a captivate modem most of the time and switch only when I plan to spend a lot of time on the net.
[Captivate Android Development] mnjm9b:
Anyone know if there is an archive for the changelogs?

I need to lookup some older changes that are no longer listed on the main changelog page.
[Captivate Android Development] Smasher816:
May I ask why?

Anyways i think this will suit your needs: http://review.cyanogenmod.com/#q,status:merged,n,z
[Captivate Android Development] tiuk:
As far as voice recognition accuracy is concerned, you could install vlingo and switch your voice recognition service to that (gingerbread lets you set this globally, which i love). I've found it does a far better job than Google's. I realize this has nothing to do with the audience chip, but i thought it might help.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] mnjm9b:
I am actually looking for changes that went with a particular nightly... the site you give doesn't break it down by build #.

But thanks...
[Captivate Android Development] RockRatt:
So what exactly is the Settings/Device settings/ HSPA actually do? I can see it allows for the faster upload/download speeds HSUPA and HSDPA, or HSDPA ONLY, and UMTS ONLY. So I know it is allowing us to change the speeds for those that don't get the hspa increase in certain areas.

BUT I guess with the talk about getting the Audience chip support in I wanted to know if this is for that purpose?

Like we CHOOSE it to use UMTS only and use a captivate modem and get the audience chip support?

Or it is just easier to lock in the speeds for the areas we are located in? Like those that ONLY get UMTS can set it to that to save battery life switching between 3g and H?

Sent from My KickAss CM7 Captivate
[Captivate Android Development] zeroonea:
Thankyou, I managed to make it work with google nexus s driver. Why those things are not listed on first post :p?
[Captivate Android Development] Kaik541:
UMTS > HSPA for battery life. Also, no more animation/flipping between H/3G on the bar when using UMTS only. Persists through reboot unlike the SamsungServiceMode method. It's all about user preference.
[Captivate Android Development] bshouse:
Does anyone have a copy #163? I cannot find a download anymore.

Thank you.

Hunt-and-pecked from touch screen.
[Captivate Android Development] RCDuke:
Go here, it has all the versions. I can see that 163 is on here.

http://download.cyanogenmod.com/?device=captivatemtd
[Captivate Android Development] bshouse:
The link there is broken. It seems to have the last 5 or so versions...

Hunt-and-pecked from touch screen.
[Captivate Android Development] RockRatt:
Try clearing your browser cache and then check. I just clicked on his link and nightlies from #150-#171 show up.

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Android Development] bshouse:
The links show up, but when you click to download #163 it gives me a "not found" error.

I was hoping some one had it on their phone from a cwm download or kept a copy somewhere.

Hunt-and-pecked from touch screen.
[Captivate Android Development] tercel59:
Nightly 171 Rocks

I had found that Nightlies 168 and 169 were feeling quite sluggish compared to slightly older versions and I read from the comments on Rom Manager that people wanted to go back to Nightly 163. I didn't have it and the links are broken, so I tried the 171 and it is a real improvement.

Big thanks for the devs for this correction!
[Captivate Android Development] dave1977nj:
I would rather have voice quality then download speeds. What are you downloading that you need HSUPA? Torrents? 3G is fine LoL...

:rolleyes:
[Captivate Android Development] tiuk:
How about uploading files to dropbox, social networking, hell even online gaming? I don't doubt there are people who would rather have the audience chip, but for myself i use the phone very little, and it's not like voice quality is worse than any other phone that doesn't have it to begin with, so if i had to choose I'd take HSUPA any day since i use data far more.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Gromlakh:
That's all fine and good, but I also don't think anyone (or, at least, too many people) is advocating for a move to only audience chip support and completely foregoing HSUPA support. It would be nice if there were some way to support both. If they can't be done together, that's fine, but a choice would be nice, even if it meant having to flash an alternate kernel/modem to get it. I mean, sure the speed is nice and all, but for those of us who use our phone more of...well, a phone, would generally prefer audience chip support if it were available.
[Captivate Android Development] tiuk:
Hey, I'm all for having the option. As i said, if it's one or the other I'd pick HSUPA, but i acknowledge that others would just as easily choose the audience chip. I think it's silly for people to write off either one. We all use Android because we like choice and a custom experience, right? ;)

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] shopealope:
You are correct on that for sure.

Sent from my Cappy
[Captivate Android Development] bveditz:
Just thought i'd post this if it helps anyone out. I was getting complaints about the audio quality when i talked to people, so what I did was install a bunch of modems on CM7 and called a voicemail number that I have that emails me the messages.

Modems tested: JK4, JL3, JPG, JVK, JW2, KB1, KC1, KE3, KG3, KH3, KP1

I only tested audio quality of playback, not gps or speed. Enough discussions of that going on. The top three I had in order were KP1, JW2 and JK4. Actually, the JW2 and KP1 are a tossup. The JW2 might have been a little bit clearer, but sounded like I was speaking in an auditorium, the KP1 was a a little more realistic sounding.

The worst ones were pretty much most of the K series modems, specifically KB1, KC1, KG3, KH3. They had lots of static and hard to hear.

Anyway, just thought i'd share, obviously a case of the YMMV. I'm certain my results are specific to CM7 as I know the K series modems sound just fine on a stock rom. If anyone knows of other modems with clear audio quality, let me know. My next step is to test my top modems with the gps and then with speed. I also read that KP1 has some battery issues, so... who knows. :)
[Captivate Android Development] littlewierdo:
If I can just say this (it will probably not be liked by many).

The CM team has decided to go with HSPA.

In order to do Audience support, we loose HSPA OR drivers have to be written or reworked (which would require some specific source code that the devs dont have).

So, since a complete rewrite is not likely to happen, we are stuck with one or the other, the decision appearing to be HSPA.

I dont think any amount of discussion is going to change this because it would fork Cyanogen into two different versions that would BOTH have to be maintained. This means, all the changes made in one would have to be made to the other and require testing to be done on BOTH versions, it would require two separate teams.

Correct me if I am wrong, I am sure other phones have limitations very similar to ours in that one feature has to be dropped because another feature conflicts with it. And to my knowledge, Cyanogen doesnt have multiple versions for one phone which allows the user to 'pick' from.

Im sorry if this is offensive to anyone and I dont mean to offend the CM folks by speaking for them, trying to provide 'choice' is not likely to happen, and having a discussion wishing we could have the feature we currently DONT have would only offend the other 50% of those that would loose the current feature (in other words, if audience support is added, it would offend the people that want HSPA, just as currently, HSPA is supported and bugs the people that want audience support).

If you want the 'other' feature, it is likely that another developer would have to pick up CM and maintain it to keep it current with Nightlies, similar to MIUI or other forks of CM.
[Captivate Android Development] RichMD:
Interesting. Personally, I am in the camp that prefers this choice. However, I know many people will not be happy with it. How did you find this information out? I haven't yet searched on it but is it documented anywhere or do you communicate with the devs for our phone directly?