Been silent for a while. Well, that’s the silence before a lot of things come to all of us!
First quick updates:
- We are pushing the Eden 1.5 update on Monday, so click that update buttons on your Adams! It comes with more than 150 changes as compared to Eden 1.0 (you can check out the documentation on Conclave on Monday).
- We are pushing one more update on Wednesday, specially for those who want to test rich features of 2.3 Gingerbread!
- We discussed about Kindle and Dolphin Browser coming bundled on Adam, well, there are more apps coming in (some in this update like Chords (with Panel), To-Do (Panel) and some around next week)! Some for the 2.2-2.3 clients, and more for Honeycomb!
- The kernel update is on its way. The reason this update took little longer than expected end of third week was to dis-associate it from the kernel up-gradation which is required for Honeycomb. Right now you can see the images on Tabletroms working pretty well, but there are lots of errors and broken pieces.
- Last 6 weeks we were integrating all support pieces to an advanced online system, which you will soon see go live on support.notionink.com. This system is used by right from FedEx to Samsung, and we are expecting it will cut the time to response further down, get you one system to track all your issues, get live support and get to scan through a large documentation of past issues.
- @Home (from Google) announcement is a very good news for Adam users. We have a team here working on automation systems, and after their study we will release few DIY system using which you can do interesting things!
- Adam is going live again! We are going to open sales coming Monday (evening to be precise)! Those who have subscribed at http://store.notionink.com/subscribe.php will receive an email invitation.
- Good News for Indian customers. Now they will receive products with all duties pre-paid.
- We have moved all our resources from current Eden 1.5 and Gingerbread to Honeycomb, and near the end of next month, you all should have Honeycomb on your devices!
Last line actually reminds me a sudden burst of criticism we had seen earlier from some people on Harmony and Ventana matters. I think now we can put it to rest. Images which you download are 120MB in size and you can see 1GB space alotted for your OS, also one more things you can notice is the 1GB RAM. It will take you a lot of effort to cross 512MB RAM usage on Adam right now. If you try to run heavy games, the load is then shared by the GPU, and still healthy amount is left un-utilized. Even the bus supports up-to 400MHz of bandwidth.
While Google gets to choose who they support officially, there is little we can do. But when we get friends like Andy, Stephen, and rest (I think like you I also know them with their nicks: Reobeet, Rothnic, Dougie187, IntuitiveNipple, TwoSpirits, MyGuy, AlbertWertz (same as his name), josh4trunks, jerryaycock, gamepro, newbe5, RaYmAn, red_herringx, Covrus and blazingwolf) we can do much more than the Bilderberg Group!
I think there is one area where you can agree with me. When it comes to fluidity of the User Interface, there is no other OS than iOS. I have failed to see any missing frame on it when I see moving images, icons or lists or even motion animations. The reason is the missing GPU support for UI on Android. You can follow this conversation here: http://code.google.com/p/android/issues/detail?id=6914 This conversation is 14 months long and is still continuing!
Currently I am in love with PowerVR architecture. Probably because there is a lot to read about it, and little less on the Tegra’s internal GPU (GeForce). iOS accelerates a lot of their UI using PoverVR SGX GPU, specially using their PVRTC format for textures. PVRTC is also an interesting lossy, fixed rate texture compression format and has a native support on SGX and has far greater implementation potential. iOS is bound to get faster and smoother, and that’s what you can do is you have control over the hardware and software. Lack of NEON, CUDA and OpenCL on Tegra also concerns me (as of now though, as roadmaps can be surprising). It’s high time we start developing for GPGPU. Currently even on Tegra, if you have 2 threads it doesnt mean they are running on 2 different cores. First it is decided to use one or two based on the processing requirement (e.g. if more than 500MHz is required then use 2 cores else one), and second you can’t program it to handle 2 threads. Even in OMAP you get to choose if you want 2 cores for an app or one, but not on Tegra (having said that, you can find instances when running an app on one core is better than on two when bench-marked against performance and power consumed).
Again, apologies for little silence here, but I did told you, busy weeks are coming ahead! :)
With Warm Regards