21–30 of 68 posts
Here's a quick summary from the SDK release notes: * Alarm clock APIs * ability to detect first install time and last update time of an app * Download manager API * Mixable audio effects API * A lot more locales (including indic language support) * SIP VOIP support * Front camera support * 5-point multi-touch API * Barometer * Gyroscope * NFC support (near field comminucation) - can interact using high frequency wire…
Here's a quick summary from the SDK release notes: * Alarm clock APIs * ability to detect first install time and last update time of an app * Download manager API * Mixable audio effects API * A lot more locales (including indic language support) * SIP VOIP support * Front camera support * 5-point multi-touch API * Barometer * Gyroscope * NFC support (near field comminucation) - can interact using high frequency wire…
Barometer = Altitude.
iPhones and such have long had the ability to drive PC-based instruments by sending MIDI or OSC signals through bluetooth or wifi, I have been to many gigs in the last year and seen people using iPads running touchOSC in their performance setups; however the high specs seen in current devices are easily enough to run fullblown synths, samplers etc on their own. This will open up the burgeoning art of musicians creating their own instruments to a much wider audience.
We're going to be hearing some pretty fun noises over the next year :)
The integrated SIP stack look excellent, but from http://developer.android.com/sdk/android-2.3-highlights.html : "Support for the platform's SIP and internet calling features on specific devices is determined by their manufacturers and associated carriers." This is disappointing, but not unexpected.
You can always install a SIP app, but yes, I'd much rather have access to the integrated client.
I'm finding more and more people outside of tech-circles are doing this as it allows you to run WifTether, extra apps, etc.
Those "Mobile Phone Repair Shops" that used to unlock Nokias are doing a roaring trade rooting and changing firmware on 'regular' user's phones.
The integrated SIP stack look excellent, but from http://developer.android.com/sdk/android-2.3-highlights.html : "Support for the platform's SIP and internet calling features on specific devices is determined by their manufacturers and associated carriers." This is disappointing, but not unexpected.
A phone OS which allows the networks to be totally supplanted wouldn't be marketed positively (by the networks).
Doesn't this preclude using your phone as an NFC payment device (which would be transmit, not receive)?
Can someone confirm if I'm parsing this correctly:
"An NFC Reader application lets the user read and interact with near-field communication (NFC) tags. For example, the user can “touch” or “swipe” an NFC tag that might be embedded in a poster, sticker, or advertisement, then act on the data read from the tag. A typical use would be to read a tag at a restaurant, store, or event and then rate or register by jumping to a web site whose URL is included in the tag data. NFC communication relies on wireless technology in the device hardware, so support for the platform's NFC features on specific devices is determined by their manufacturers."
Love how you can't read the android site in a android phone Unless you send a android user agent, then it changes most of the css to enable it. Really a dumb move
