Currently, I am building mVoIP service for Android. I chose FreeSwitch as a SIP server, and there is no problem talking through PC. However, all Android open source make voice delay. Here are data we faced so far.
Case 1 - FreeSwitch + PC
FreeSwitch 1.2 Stable version
Linux CentOS 6.5
Xlite Softphone for PC Windows8
Voice delay - less than 50ms
Case 2 - FreeSwitch + Android Sipdroid
FreeSwitch 1.2 Stable version
Linux CentOS 6.5
Sipdroid for Android
Voice delay - 80 ~ 200 ms
Case 3 - FreeSwitch + Android Csipsimple
FreeSwitch 1.2 Stable version
Linux CentOS 6.5
Csipsimple for Android
Voice delay - 150 ~ 400 ms
Case 4 - FreeSwitch + Android SipDroid ==> PC
FreeSwitch 1.2 Stable version
Linux CentOS 6.5
Sipdroid for Android
Xlite Softphone for PC Windows8
Voice delay - 50 ~ 100 ms
Some of Android mVoIP applications, such as Skype, make less than 50ms voice delay. We've tried many SIP open sources for Android, but all of them make horrible delay. We are looking for a open source that make less than 50ms for Android. Is there someone who can solve this issue? Thank you.
Is it maybe Android device is slow to encode and decode audio sound?
it's a known problem with CentOS 6. You need to choose a different distro (Debian works fine with me)
http://wiki.freeswitch.org/wiki/Download_%26_Installation_Guide#Release.28es.29_6_and_Later
Related
I downloaded the Showcaseapp-1.9.6.apk. (I am on android)
I downloaded 1.9.0_hr_wakeup_DFU.zip
The showcase app does not show my Smart Sensor (movesense) in the app under "movesense connection" also can't select device because its not listed.
The following message from the readme is confusing me:
WARNING: in case the new firmware is not based on the latest Movesense stack, the device looses the capability to be updated!!!
Does this mean I have to update from 1.1 to 1.2 to 1.3 and so on?
Kind regards
No worries, you can update directly from 1.1 => 1.9. However, since your firmware is that old you need to use the "_w_bootloader" DFU packet (contains updated bootloader which was introduced in v1.2). Basic rule is that you'll need the "_w_bootloader" DFU packet if there was softdevice / bootloader change between the two versions.
There may be some issues updating the sensor if you are using the latest Android showcase app (1.9.x). In that case you can download older version from movesense-mobile-lib bitbucket site / downloads. iOS sample app should not have that limitation but you will need also the nrf connect / nrf toolbox apps.
Full Disclosure: I work for the Movesense team
When I try to install Smartface.io the installer freezes completely when it reaches about 160 MB of 172 MB.
I've checked the boxes for the .NET Framework, iTunes, JDK 1.7, Android SDK and Node.js. It also starts with SmartfaceAppStudio.exe already checked.
I have tested with both Windows 10 and 7, but the problem still persists.
ok, solved
i installed hotspot shield and connected with a United States IP
and the download completed without any problems
My device driver for nexus 4 is not installing on my windows, after trying several times.
My sdk tools and platform tools are updated to the latest version.
I had the exact same thing, i'm using windows 7 btw.
On your phone:
1) Connect your Nexus 4 to your pc with usb
2) Revoke USB debugging authorizations
On Windows
1) In windows go to your device manager (called MTP for my case)
2) Uninstall the current driver
3) Re-install the driver from disk (\extras\google\usb_driver)
In my case the device was visible again in Eclipse, and after authorizing it on my phone I was able to use it like before. Hope this helps
I've been making adjustments to a websocket server I'm using, but I'm finding my efforts in vain since I haven't been able to determine which spec (hixie/hybi?) of websockets the most recent version of iOS is using.
Is it Hixie 76 or Hybi? Thanks!
Here is test link, use any device / platform to test it: http://websocketstest.com/
On iPhone 4 (Version 5.0.1) supports drawft-76.
And here is overall support statistics of availability of technology over different browsers / platforms: http://caniuse.com/#feat=websockets
I have installed android tools and eclipse successfully (making the hello World and hello widget examples) and have run these successfully on the Xperia X10 add-on that I downloaded from the developer site of SE.
However, my phone is running the updated Android 2.1, and any apps that I make will either have to run on 1.6, or will not be able to be tested on the Xperia X10 during development without moving it to my physical phone.
I have contacted Sony and they told me there is no add-on with 2.1 on it. And that is all they would say.
My Question:
Is there anyone out there who has developed for this phone, who knows what to do? Do I somehow run the SE update tool on the virtual phone to upgrade the OS of the image? Or am I missing something much more obvious?
As of April 2011, this is (an estimate of) Android usage share:
That's 3.5% for Android 1.6 and 2.7% for Android 1.5. As time goes by, those percentages will only decrease.
Just develop for 2.1.
Why do you prefer to use the emulator, anyway? Most Android devs (myself included) have found that the emulator is painfully slow, and it's just plain easier to plug in a real phone and test on that.
You can use the adb for getting your phone in debug mode.
Or you can just install your APKs via OTA or via USB in your physical phone.
Or you could just develop on 2.1 knowing that almost everything will work. I don't get the problem, really.