At #io12 Hugo Barra announced the new Android Platform Development Kit. The PDK was described as helping hardware developers port Jelly Bean to their devices and was said to be available “two to three months before the platform release date”, and that selected hardware partners had been given access to the JB PDK a few weeks before #io12 (around the 30min mark in the video below). Personally I felt it was this years attempt to reassure users their devices would get updates after last years attempt (The 18 month update guarantee) failed so miserably.
One phrase from last nights Amazon.com Kindle launch makes me think they’re going to take over the #Android tablet space and have big consumer support; “…people don’t want gadgets anymore. They want services that improve over time. They want services that improve every day, every week, and every month.” This has been true for a long time. Consumers buy devices from washing machines to TVs because they want it to do something, not because it has the lastest bit of technology from the manufacturer.
This is the P&L; for Diaspora, a project which raised two hundred thousand dollars on Kickstarter (http://goo.gl/Yf3Pi) and has now decided to turn it over “to the community” (http://goo.gl/yH9W9) (read; all the money has gone, they’ve not managed to create any revenue streams, and they’re not putting any money in to keep it going). Looking over the figures a couple of things jump out at me; The only income is the Kickstarter money.
One of the changes in #IceCreamSandwich was the introduction of a lower SMS usage monitor rate which restricts how many SMSes can be sent by any application in a given time. My guess would be that the aim is to prevent malicious apps sending huge amounts of SMSes to premium rate numbers, but unfortunately some users seem to be hitting the limit with the default SMS messaging app (https://groups.google.com/d/msg/android-discuss/bsDO0jQVdTI/Ns7oaTCcIa8J), and it’s possible developers may see users complaining about this if their apps rely on SMS usage and are heavily used, so I thought it’s worth letting people what the limits are in case people ask them.
TL;DR: Implementing it in your apps is more hassle than it’s worth. To answer the most common question; Yes, the two apps on one screen functionality of the Galaxy Note 10.1 is limited to a few apps. All of them ship with the device. The code to support multi-window mode is baked into the core Android framework on the device (so much so that the classes are in the framework library odex), which means that it could be submitted to the #AOSP to become part of Androids core functionality.
After a comment on a previous post from George Medve on Flash I though it best to share my take on it. I’m doing this as a post because it’s probably of interest to some people who wouldn’t read the comments on the other post; In terms of Flashes security, I think this article says it all. 2 days ago Adobe were patching a bug which could crash machines and/or allow remote users to take control.
The #Ouya Kickstarter has nearly crossed the US$5million mark. I’ve read all the negative press, a lot of which was written before this weekends Android XBMC posts by Kieran Gutteridge and Jason Parker. If you bear in mind that Apple apparently sold more than 2.7 million Apple TVs' in the first half of this year (http://goo.gl/K9ldI), a US$99 XBMC capable device which has the ability to run apps and games as well seems to me to have a good chance of being a success.
Building AOSP JB on OS X 10.7 with XCode 4 takes just a little tweak to your build. Instead of running just make you need to run; make CC=“gcc” CXX=“g++” Which will allow the build to complete.
It’s always fun when you can pull the birds on a new device :) Hopefully my posts messing around with the NexusQ have shown you that it is just an #Android device and that most apps would work on it with little to no effort as long as they don’t require things like a camera or multi-touch input. If the Q were combined with a simple control system (e.g. an app on the phone which worked as a touchpad for the Q) you’d have yourself, in my opinion, one of the best Android living room experiences currently available.
If you enable USB debug mode on the Q, then use adb shell you can start the settings app using the command; am start -a android.intent.action.MAIN -n com.android.settings/.Settings Once you have done this you can “configure” it using; input keyevent xxxx where xxxx is one of the key events from http://developer.android.com/reference/android/view/KeyEvent.html (e.g. input keyevent 20 is the same as pressing down on the dpad). It’s a bit time consuming, but it should be enough to get the Q working with a mouse ;)