liyuanwei / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

Performance degradation over call time when using h264 #167

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. set in codecs to use only H264 BP2 or BP3
2. have poor connection with server (poor wifi signal reception level)
3. make call and watch its slowing over time (poor wifi=packet loss i guess), 
more packet loss = more slowing, video getting very high delay, up to 5 or more 
seconds, if you try to press menu reaction will also be delayed by 5-10 seconds.

If connectivity quality restores this effect will no go away so until you stop 
call there will be huge delay\unrespoinsive GUI interface.

If i end call and start it again - its perfect again and again it will slow 
over time

What version of the product are you using? On what operating system?
Last version from trunk of IMSDroid\Doubango
Last versions of SDK\NDK.
Android 2.2
HTC Desire (Snapdragon 1Ghz processor with NEON)

Please tell me if you need any additional info.

Original issue reported on code.google.com by yes....@gmail.com on 5 Feb 2011 at 3:29

GoogleCodeExporter commented 9 years ago
Which client are you using on the remote site?
What are the stream configs (size, framerate, refs, ...)?

Original comment by boss...@yahoo.fr on 10 Feb 2011 at 12:03

GoogleCodeExporter commented 9 years ago
Mostly its linphone on Ubuntu and MCU(conference server), configs are always 
the same 
CIF, 15 FPS, H264(using only this codec).
Also i have noticed very strange thing - this is never happened on huawei s7 
tablet with android 2.1, no matter how long call time is.

ps got Nexus S with android 2.3 for test...will try to test it in next few 
days, will report results here.

Original comment by yes....@gmail.com on 21 Feb 2011 at 8:28

GoogleCodeExporter commented 9 years ago
Tested on Nexus S - it also happens, and also tested it more on huawei s7 
tablet with android 2.1 - same thing, dunno why and what causes it..its mostly 
random. It can happen even with good wifi signal level.
If you need more info - just tell, i think i can collect it in debug mode...

Original comment by yes....@gmail.com on 28 Feb 2011 at 10:37

GoogleCodeExporter commented 9 years ago
Issue 289 has been merged into this issue.

Original comment by boss...@yahoo.fr on 21 Sep 2011 at 3:45

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 26 Sep 2012 at 9:29