Menu

#2831 No audio with Android Lollipop

Need-Details
nobody
None
Medium
Defect
2014-11-26
2014-11-14
Anonymous
No

Originally created by: massimo....@gmail.com

What version of the product are you using? On what device / operating
system?
Samsung Galaxy S5 with Android Lollipop 5.0 preview.

Please provide any additional information below.
I'm running CSipSimple with codec G729 but no audio (outgoing/incoming) can be heard. Working fine with KitKat.

Related

Tickets: #2889

Discussion

  • Anonymous

    Anonymous - 2014-11-15

    Originally posted by: into...@gmail.com

    Hi! Use device Nexus 5 d821 updated to Android 5 lollipop, audio work has improved, there is no latency microphone, there is no such as echo on Android 4.4.4 Kit Kat! Good

     
  • Anonymous

    Anonymous - 2014-11-19

    Originally posted by: massimo....@gmail.com

    Reproduced also with Nexus 5 updated to Android 5.0.
    No audio using codecs G729 or PCMA.
    From the logs I can see a lot of strings like:

    11-19 11:17:08.796: D/libpjsip(6645):  11:17:08.796   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.797: D/libpjsip(6645):  11:17:08.797   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.798: D/libpjsip(6645):  11:17:08.798   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.798: D/libpjsip(6645):  11:17:08.798   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.799: D/libpjsip(6645):  11:17:08.799   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.802: D/libpjsip(6645):  11:17:08.802   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.803: D/libpjsip(6645):  11:17:08.803   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.804: D/libpjsip(6645):  11:17:08.804   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.805: D/libpjsip(6645):  11:17:08.805   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.897: D/libpjsip(6645):  11:17:08.897   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.898: D/libpjsip(6645):  11:17:08.898   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.899: D/libpjsip(6645):  11:17:08.899   Master/sound  Underflow, buf_cnt=0, will generate 1 frame
    11-19 11:17:08.900: D/libpjsip(6645):  11:17:08.900   Master/sound  Underflow, buf_cnt=0, will generate 1 frame

    and

    11-19 11:17:12.696: V/libpjsip(6645):  11:17:12.696 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 1 empty/lost)
    11-19 11:17:12.796: V/libpjsip(6645):  11:17:12.796 strm0xafe7f9b4  jb updated(1), lvl=16 pre=0, size=9
    11-19 11:17:12.898: V/libpjsip(6645):  11:17:12.898 strm0xafe7f9b4  Frame lost, recovered!
    11-19 11:17:12.899: V/libpjsip(6645):  11:17:12.899 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 2 empty/lost)
    11-19 11:17:12.899: V/libpjsip(6645):  11:17:12.899 strm0xafe7f9b4  Jitter buffer empty (prefetch=0), plc invoked
    11-19 11:17:12.996: V/libpjsip(6645):  11:17:12.996 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 1 empty/lost)
    11-19 11:17:12.998: V/libpjsip(6645):  11:17:12.998 strm0xafe7f9b4  Jitter buffer empty (prefetch=0), plc invoked
    11-19 11:17:13.096: V/libpjsip(6645):  11:17:13.096 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 4 empty/lost)
    11-19 11:17:13.099: V/libpjsip(6645):  11:17:13.099 strm0xafe7f9b4  Frame lost, recovered!
    11-19 11:17:13.102: V/libpjsip(6645):  11:17:13.102 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 4 empty/lost)
    11-19 11:17:13.198: V/libpjsip(6645):  11:17:13.198 strm0xafe7f9b4  Frame lost, recovered!
    11-19 11:17:13.199: V/libpjsip(6645):  11:17:13.199 strm0xafe7f9b4  Jitter buffer starts returning normal frames (after 2 empty/lost)

    Any clue? Is there any parameter (like ptime or default frequency) to be changed?
    Thanks

     
  • Anonymous

    Anonymous - 2014-11-19

    Originally posted by: lainest...@gmail.com

    I unfortunately have no cycles available to provide more detailed debugging info ATM, but I am also experiencing no sound in calls (sound is lacking in both directions) after upgrading my Nexus 4 to Android 5.0. If it's not solved by next week I may be able to spend time then gathering more data.

     
  • Anonymous

    Anonymous - 2014-11-20

    Originally posted by: ja...@lansky.biz

    Same problem, Nexus 4 - Android 5.0_r6 build from AOSP.

     
  • Anonymous

    Anonymous - 2014-11-20

    Originally posted by: krzyszto...@gmail.com

    Same problem with newly updated Nexus 5.

     
  • Anonymous

    Anonymous - 2014-11-20

    Originally posted by: r3gis...@gmail.com

    Hi

    Android 5.0 should be properly supported by nightly build version (that you can get and test from : http://nightlies.csipsimple.com/trunk/ ).
    It is supported from last month but I am waiting for most my devices to actually switch to 5.0 so that all features can be validated before I release something stable on playstore.

    So can you test with nightly build?
    (For those using g729 codec plugin, it should still be compatible)

    Status: Need-Details

     
  • Anonymous

    Anonymous - 2014-11-21

    Originally posted by: ja...@lansky.biz

    Thanks, tried [r2440] trunk and it's _working_ fine (also with G729 codec)

    Nexus 4, Android 5.0_r6 from AOSP.

     

    Related

    Commit: [r2440]

  • Anonymous

    Anonymous - 2014-11-21

    Originally posted by: massimo....@gmail.com

    Thanks. Since i'm using an older version could you please point me to what area of the code specifically addresses the support for android 5?
    Thanks in advance.

     
  • Anonymous

    Anonymous - 2014-11-22

    Originally posted by: krzyszto...@gmail.com

    Latest nightly works ok, thanks.

     
  • Anonymous

    Anonymous - 2014-11-26

    Originally posted by: lainest...@gmail.com

    Works well here (N4) too. You may want to reconsider waiting to put an updated build on the playstore. After all, what's there currently is apparently guaranteed to not work on 5.0, so a new build could only be an improvement :-)

     

    Last edit: Anonymous 2017-06-23

Log in to post a comment.