Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 11 hrs, 29 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 7 hrs ago - more...
CMB Rocks |
2011-06-13
, 15:18
|
|
Posts: 15 |
Thanked: 3 times |
Joined on Apr 2011
@ The Netherlands
|
#81
|
Originally Posted by rosh
Have you tried allowing the iLBC in the extension configuration file of asterisk? That should work, for all I know all the N900's are the same.
|
|
2011-06-14
, 01:41
|
|
Posts: 356 |
Thanked: 123 times |
Joined on Dec 2008
|
#82
|
Originally Posted by rajil.s
I have been on vacation, so I haven't been using it much (internet has been spotty), but the few times that I have tried it I didn't have any problems.
Any improvements?
|
|
2011-07-05
, 21:09
|
|
Posts: 79 |
Thanked: 332 times |
Joined on Jul 2011
|
#83
|
Hi,
I've played a little bit, because I couldn't manage to launch the script on calls via dbus-scripts.d, it happened nothing.
I don't know how good it is or not and how affect the power consumption of the phone, but it seems to be working, although it is about 1 hour old.
I start it upon boot and now SIP and Skype connections work fine.
So, here it is:
Maybe the 'code' itself is not the best, and it is my very first try to make something like a 'script', so please be patient.
I don't know its possibilities, so if anyone can advice a better solution, I'm happy to hear it.
Also, if you say it is a completely bad solution, please write your opinion.
I've played a little bit, because I couldn't manage to launch the script on calls via dbus-scripts.d, it happened nothing.
I don't know how good it is or not and how affect the power consumption of the phone, but it seems to be working, although it is about 1 hour old.
I start it upon boot and now SIP and Skype connections work fine.
So, here it is:
Code:
#!/bin/sh
let LAST=2
while true; do
if [ $(pidof telepathy-stream-engine) ]; then
let NOW=1
else
let NOW=0
fi
if [ $NOW != $LAST ]; then
if [ $NOW -eq 0 ]; then
sh /bin/speedadaptnormal > /dev/null
else
sh /bin/speedadaptfix > /dev/null
fi
fi
if [ $(pidof telepathy-stream-engine) ]; then
let LAST=1
else
let LAST=0
fi
sleep 5
done
I don't know its possibilities, so if anyone can advice a better solution, I'm happy to hear it.
Also, if you say it is a completely bad solution, please write your opinion.
|
|
2011-07-05
, 21:27
|
|
Posts: 182 |
Thanked: 40 times |
Joined on Apr 2010
@ Seatle, WA
|
#84
|
Originally Posted by VaZso
can this not be put in some event.d and the script be called when some event happen? I am not sure what event to trigger to, but just a thought.
Hi,
I've played a little bit, because I couldn't manage to launch the script on calls via dbus-scripts.d, it happened nothing.
I don't know how good it is or not and how affect the power consumption of the phone, but it seems to be working, although it is about 1 hour old.
I start it upon boot and now SIP and Skype connections work fine.
So, here it is:
Maybe the 'code' itself is not the best, and it is my very first try to make something like a 'script', so please be patient.Code:#!/bin/sh let LAST=2 while true; do if [ $(pidof telepathy-stream-engine) ]; then let NOW=1 else let NOW=0 fi if [ $NOW != $LAST ]; then if [ $NOW -eq 0 ]; then sh /bin/speedadaptnormal > /dev/null else sh /bin/speedadaptfix > /dev/null fi fi if [ $(pidof telepathy-stream-engine) ]; then let LAST=1 else let LAST=0 fi sleep 5 done
I don't know its possibilities, so if anyone can advice a better solution, I'm happy to hear it.
Also, if you say it is a completely bad solution, please write your opinion.
|
|
2011-07-05
, 21:40
|
|
Posts: 79 |
Thanked: 332 times |
Joined on Jul 2011
|
#85
|
I also would like to know this, but I haven't found anything I can trigger this script with.
It would be better though...
It would be better though...
|
|
2011-07-07
, 02:18
|
|
Posts: 79 |
Thanked: 332 times |
Joined on Jul 2011
|
#86
|
Maybe it is much better to check the 'pidof' only once a time, so like this one:
Last, it would be better to set the "LAST" variable when it really changed, so put it in the [ $NOW != $LAST ] statement.
Last edited by VaZso; 2011-07-07 at 13:12.
Last, it would be better to set the "LAST" variable when it really changed, so put it in the [ $NOW != $LAST ] statement.
Code:
#!/bin/sh
let LAST=2
while true; do
if [ $(pidof telepathy-stream-engine) ]; then
let NOW=1
else
let NOW=0
fi
if [ $NOW != $LAST ]; then
if [ $NOW -eq 0 ]; then
sh /bin/speedadaptnormal > /dev/null
else
sh /bin/speedadaptfix > /dev/null
fi
let LAST=NOW
fi
sleep 5
done
Last edited by VaZso; 2011-07-07 at 13:12.
|
|
2011-10-10
, 15:28
|
|
Posts: 23 |
Thanked: 14 times |
Joined on Feb 2010
@ Paris, France
|
#87
|
To add my two cents, I long quit any hope using SIP. It was useless : too choppy to even speak a few words : I could hear perfectly remote side but I wouldn't be understood. Skype has always been fine though, even on 3G, so I suspected my SIP provider Wengo (a service from French ISP SFR) codec to be N900 unfriendly.
Lately I tried to investigate further. I run CSSU with kernel-power. I read that SIP choppy problems could occur with that specific kernel.
But before reverting to Nokia kernel I remembered I didn't do any kernel upgrades with my recent PR upgrades
So I gave reinstall a go with :
apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher
And ... voilą !!!!!! I can use SIP again through wifi. At least this morning I was able to have a loud and clear 10 minutes conversation before restarting the call. For me it's much better than nothing.
I also played with pulseaudio in /etc/pulse/daemon.conf going from 2 to 5 in default-fragments. Don't know if it helped.
Still for me SIP over 3G is very choppy, but this can be for a lot of reasons : codec is too bandwidth consuming for my weak 3G connexion, but I mainly suspect my provider to downgrade sip port (SIP over 3g is not allowed here). I should run some further tests. If anyone is interested, just let me know.
Lately I tried to investigate further. I run CSSU with kernel-power. I read that SIP choppy problems could occur with that specific kernel.
But before reverting to Nokia kernel I remembered I didn't do any kernel upgrades with my recent PR upgrades
So I gave reinstall a go with :
apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher
And ... voilą !!!!!! I can use SIP again through wifi. At least this morning I was able to have a loud and clear 10 minutes conversation before restarting the call. For me it's much better than nothing.
I also played with pulseaudio in /etc/pulse/daemon.conf going from 2 to 5 in default-fragments. Don't know if it helped.
Still for me SIP over 3G is very choppy, but this can be for a lot of reasons : codec is too bandwidth consuming for my weak 3G connexion, but I mainly suspect my provider to downgrade sip port (SIP over 3g is not allowed here). I should run some further tests. If anyone is interested, just let me know.
|
|
2012-09-24
, 02:12
|
|
Posts: 17 |
Thanked: 17 times |
Joined on Jan 2011
|
#88
|
Hello everybody,
I think I have the same problem or a similar one. If I make or receive a SIP call, after some time the audio starts getting choppy and after a while I can't hear anything, while the other end can hear me perfectly. If I wait a few seconds it recovers, but then the problem will happen again in the same call.
This happens both with wifi and 3G.
I tried changing the codec from PCMU to iLBC, it didn't help.
I am running 1.2 (haven't tried kernel-power).
I haven't read the whole thread (yet), but would appreciate some quick help.
I know this thread is old, so I have some hope somebody already found a solution for this. I will be monitoring this thread, if somebody has an answer even 2 years from now, please post a solution here.
I think I have the same problem or a similar one. If I make or receive a SIP call, after some time the audio starts getting choppy and after a while I can't hear anything, while the other end can hear me perfectly. If I wait a few seconds it recovers, but then the problem will happen again in the same call.
This happens both with wifi and 3G.
I tried changing the codec from PCMU to iLBC, it didn't help.
I am running 1.2 (haven't tried kernel-power).
I haven't read the whole thread (yet), but would appreciate some quick help.
I know this thread is old, so I have some hope somebody already found a solution for this. I will be monitoring this thread, if somebody has an answer even 2 years from now, please post a solution here.
|
|
2013-04-27
, 18:21
|
|
Posts: 25 |
Thanked: 9 times |
Joined on Oct 2010
|
#89
|
Originally Posted by lameventanas
I am struggling with the same issue though for me it is with skype not SIP. In my own words though:
If I make or receive a SIP call, after some time the audio starts getting choppy and after a while I can't hear anything, while the other end can hear me perfectly. If I wait a few seconds it recovers, but then the problem will happen again in the same call.
The other party can hear me fine but I hear intermittent choppy audio about every 1-10 seconds from the remote party. Previously everything was perfect.
This issue appeared after installing tweaks from:
http://talk.maemo.org/showthread.php?t=73315
So far I have uninstalled/reverted everything from that post though I still use CSSU and kernel-power.
I have also looked at:
http://wiki.maemo.org/Community_SSU/...roken_packages
which recommends against using:
battery patch
speed patch
|
|
2013-04-29
, 19:01
|
|
Posts: 25 |
Thanked: 9 times |
Joined on Oct 2010
|
#90
|
I was recently able to fix choppy skype audio and restore the previous state of my n900 by doing:
sudo kernel-config load ideal
sudo kernel-config default ideal
The audio chop is thus likely affected by:
kernel-config
By simply tuning the frequencies, voltages, etc. the chop can be increased and decreased.
This is evident by running:
sudo kernel-config load ideal
and doing a skype test call to echo123
And then running:
sudo kernel-config load myprofile
(where myprofile could be whatever settings)
and doing a skype test call to echo123 again to compare audio chop
This can be repeated until a suitable kernel-config is found.
---------------
More info:
Not sure if this fix is specific to my phone. Skype still has occasional chop glitches but they are no longer significant enough to distort audio to a point where I can not understand or it is not usable.
The maemo overclocking wiki commands are what I was using with "myprofile" are listed at:
http://wiki.maemo.org/Overclocking#Overclocking
http://wiki.maemo.org/Overclocking#Undervolting
ie) myprofile
sudo kernel-config load default
sudo kernel-config limits 250 900
sudo kernel-config save myprofile
vi /home/user/.kernel/myprofile
SMARTREFLEX_VDD1=1 SMARTREFLEX_VDD2=1
sudo kernel-config load myprofile
Ironically the settings on the wiki seem to improve everything on my n900 with the exception of making more chop on skype (on my side only) as well as decreased audio volume to on the handset I am calling. I can even play video again without reboots/instability.
Going with the n900 default settings and no overclock seemed to be too slow to go back to and I haven't necessarily noticed any improvement to skype chop using:
sudo kernel-config load default
Hope this helps someone. Also, this phone is 3 years old already!
sudo kernel-config load ideal
sudo kernel-config default ideal
The audio chop is thus likely affected by:
kernel-config
By simply tuning the frequencies, voltages, etc. the chop can be increased and decreased.
This is evident by running:
sudo kernel-config load ideal
and doing a skype test call to echo123
And then running:
sudo kernel-config load myprofile
(where myprofile could be whatever settings)
and doing a skype test call to echo123 again to compare audio chop
This can be repeated until a suitable kernel-config is found.
---------------
More info:
Not sure if this fix is specific to my phone. Skype still has occasional chop glitches but they are no longer significant enough to distort audio to a point where I can not understand or it is not usable.
The maemo overclocking wiki commands are what I was using with "myprofile" are listed at:
http://wiki.maemo.org/Overclocking#Overclocking
http://wiki.maemo.org/Overclocking#Undervolting
ie) myprofile
sudo kernel-config load default
sudo kernel-config limits 250 900
sudo kernel-config save myprofile
vi /home/user/.kernel/myprofile
SMARTREFLEX_VDD1=1 SMARTREFLEX_VDD2=1
sudo kernel-config load myprofile
Ironically the settings on the wiki seem to improve everything on my n900 with the exception of making more chop on skype (on my side only) as well as decreased audio volume to on the handset I am calling. I can even play video again without reboots/instability.
Going with the n900 default settings and no overclock seemed to be too slow to go back to and I haven't necessarily noticed any improvement to skype chop using:
sudo kernel-config load default
Hope this helps someone. Also, this phone is 3 years old already!