Hi! > > Hmm. Interesting. Anyway, for me ttyUSB4 is interesting, as it seems > > to react to AT commands, and in particular reacts to ADT123; (; is > > important). > > Is that to dial a voice call? Yes. And it is ATD123; not ATD. > > AT+CMGF=1 > > AT+CMGS="123" > > foo^Z > > > > Works for SMS sending. Good. > > So what do you use for reading notifying and reading sms? Well, did not try that, but they should just be displayed in the serial terminal. Anyway, "good" solution is to get ofonod running, then use ofone from here: https://github.com/pavelmachek/unicsy_demo But parsing AT commands is easy enough that I can probably hack it together in few days if neccessary. > > Now, if someone knows what needs to be done to get GSM audio working, > > let me know. That's something I'd really like. > > I think it's the cpcap based config to route voice call audio > to SoC, Sebastian knows the details :) > > The way to figure that one out is to dump the cpcap registers > before and during voice call on android with cpcaprw, then > diff the output for the audio registers. Probably some SoC > registers need to be diffed too with rwmem or similar tool > for the mcbsp instance(s) used. That sounds like hard way to do it. There's source available, I'm now trying to understand it / fit it into Sebastian's driver. https://raw.githubusercontent.com/NotKit/android_kernel_motorola_omap4-common/hybris-11.0/sound/soc/codecs/cpcap.c Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
