Linked by Thom Holwerda on Sun 6th May 2012 10:10 UTC, submitted by bowkota
Google This is absolutely fascinating. Steven Troughton-Smith has gotten his hands on one of the two early Android prototypes - the Google 'Sooner'. The Sooner is the BlackBerry-esque Google phone, which was supposed to be released first, followed by the much more advanced Google Dream (yup, what would eventually become the G1). Lots of high-res screenhots to get a good look at early Android. Update: Fascinating comment.
Thread beginning with comment 517253
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: A little misleading
by Morgan on Sun 6th May 2012 21:59 UTC in reply to "RE: A little misleading"
Morgan
Member since:
2005-06-29

btw did you manage to fix scroll on Android or you still waiting for more powerful hardware to mask this problem?


This is still an issue on Android? It was my understanding that this kind of thing was fixed for good in Froyo or Gingerbread (I don't remember which specifically). I know that every device I've used with Gingerbread or higher, including my lowly Moto Cliq with CM7 that I just gave to my best friend's sister, has no scrolling issues.

Oh wait, I forgot you are a huge Apple fan. My apologies, troll on my friend.

Reply Parent Score: 3

RE[3]: A little misleading
by kovacm on Sun 6th May 2012 23:32 in reply to "RE[2]: A little misleading"
kovacm Member since:
2010-12-16

last what I read from Dianne is that scroll issue will be fixed with better hardware - this approach remind me a little bit to Microsoft but ... who know why this is good ;)

btw I am a fan of god-like optimization ;)

Reply Parent Score: -1

RE[4]: A little misleading
by Morgan on Sun 6th May 2012 23:38 in reply to "RE[3]: A little misleading"
Morgan Member since:
2005-06-29

Hey, all I know is switching to CM7 from the official ROM on that Cliq fixed all the UI issues the phone had.

Since we're on the subject, do you have any suggestions for the terrible UI sluggishness and other performance issues on my girlfriend's iPad? Since everyone knows you can't put a different OS build on Apple iDevices, I mean. ;)

Reply Parent Score: 2

RE[4]: A little misleading
by Neolander on Mon 7th May 2012 08:26 in reply to "RE[3]: A little misleading"
Neolander Member since:
2010-03-08

last what I read from Dianne is that scroll issue will be fixed with better hardware - this approach remind me a little bit to Microsoft but ... who know why this is good ;)

btw I am a fan of god-like optimization ;)

Well, you know, that's not exactly an Android-specific problem.

Symbian smartphones used to last a week of light use on a single charge and deal well with 266 MHz CPUs and 256MB of RAM. I believe Blackberries were also able of similar feats at the time. Nowadays, you'll have a hard time seeing something running iOS, WP7 or Android achieving something similar.

For an example from Apple, look at the statements that Siri cannot be ported to pre-4S hardware because the hardware is not powerful enough, or that the iPhone 3G couldn't multitask. I tend to doubt it myself, but if it's true, it says something about optimization at Cupertino, since they used to be able to do voice recognition and multitasking on hardware that was much weaker than that, without the assistance of external web servers for "cloud" processing.

The reason why smartphones OS manufacturers don't care about optimization is not a secret either. People switch phones once every two years at most, and are lured into believing that this is a minor expense through carrier subsidizing. In the end, why bother with making optimized software for disposable hardware that will be "powerful enough" pretty soon anyway ?

Edited 2012-05-07 08:28 UTC

Reply Parent Score: 1