← Back to team overview

ubuntu-phone team mailing list archive

Re: Ubuntu Touch Audio stack for 13.10 release

 

Hi, I test on n4 with image version 20130901.1 and confirm all my previous
reported 4 polarity earjack issues has been fixed.

Cool for the great work !


2013/8/29 Ricardo Salveti de Araujo <ricardo.salveti@xxxxxxxxxxxxx>

> On Wed, Aug 28, 2013 at 2:21 AM, David Henningsson
> <david.henningsson@xxxxxxxxxxxxx> wrote:
> > On 08/28/2013 01:52 AM, Ricardo Salveti de Araujo wrote:
> >> My test results:
> >>
> >> Nexus 4:
> >> - Indicator
> >>   - Mute working
> >>   - Volume working
> >> - Aplay works
> >> - Video with software decoding works
> >> - Music Player works fine with wav and mp3 (but for mp3 you need to
> >> install gstreamer0.10-plugins-ugly)
> >> - Phone:
> >>   - Receive works
> >>   - Making call works
> >>   - Ringtone works
> >>   - Speakerphone works
> >>   - Unecessary setmode INCALL/NORMAL when declining a call :
> >> http://paste.ubuntu.com/6034445/
> >> - Jack detection:
> >>   - Working but sound coming from both jack and speaker (also just
> >> coming sound from the left side, not stereo, but might be my cable)
> >
> > I'll flash my device with the latest image and see what I can reproduce
> > of the above.
> >
> > Btw, did you make the android-platform-headers change that's necessary
> > for the headset mic to work?
>
> Finally in, check libhybris 0.1.0+git20130606+c5d897a-0ubuntu21.
>
> >> Galaxy Nexus:
> >> - Boot, exception stack when starting pulse:
> http://paste.ubuntu.com/6034603/
> >
> > This seems to be the most serious error at the moment. First, does it
> > happen at every restart of PulseAudio, or just at boot time?
>
> Happens at every first start of PulseAudio. Further runs seems to be
> fine, but I can also easily get the kernel to crash when restarting
> pulseaudio.
>
> I'm not sure this is fatal, as the device seems to be working just
> fine with latest image.
>
> > And regardless of which, could you try editing /etc/pulse/default.pa,
> > and just above the line that calls "load-module module-udev-detect", add
> > a "set-log-level 4". That will make PulseAudio's verbose log go to
> > syslog, and with some luck it won't get ratelimited before we get the
> > crash, so that we'll get PulseAudio's log correctly interleaved with the
> > crash.
>
> As pasted on IRC, you can check the logs at
> http://paste.ubuntu.com/6036955/
>
> >> - Indicator
> >>   - Mute working
> >>   - Volume working
> >> - Aplay working, but very low volume by default (handsfree, earpiece
> >> and headset volume seems to be 0% by default, in alsamixer)
> >
> > I think I already found the error in the UCM file for this. PulseAudio
> > does not (yet) support hw volume control when used together when UCM,
> > and UCM specifies this as a hw volume control.
>
> I also did a small change for the default volume regarding speaker and
> headphone. With latest alsa-lib the volume seems to be high again
> right after boot (let me know if it needs further changes).
>
> >> - Phone:
> >>   - Make and Receiving fails: http://paste.ubuntu.com/6034612/
> >
> > This is surprising, given that we have other people confirming that it
> > was in fact working. Could you be more specific about "fails"?
>
> Wasn't getting any sound yesterday, but this is fixed with latest image.
>
> >>     - Not necessarily related, but opened
> >> https://bugs.launchpad.net/ubuntu/+source/linux-maguro/+bug/1217618
> >>   - Ringtone works (low volume)
> >>
> >> So it seems that with Maguro we might still need some UCM changes, but
> >> also need to identify why the kernel is giving the exception stacks at
> >> every boot.
> >
> > Yes. I wonder if the exception stack has anything to do with bug 1217072
> > (which was reported on the PulseAudio image)?
>
> Would need a bit of more testing, but I don't think the issue is fatal.
>
> Cheers,
> --
> Ricardo Salveti de Araujo
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References