HTC Scorpion with 1.5GHz Snapdragon, WiMAX tipped in build file of dubious provenance
By Joseph L. Flatley 
posted February 9th 2010 8:51PM
posted February 9th 2010 8:51PM
Sure, this next item might be a little bit of a stretch, but why the hell not: according to MobileCrunch, there's a build file from an-as-yet unknown device called the HTC Scorpion making the rounds. If the tea leaves are being read correctly (and, more to the point, if they're real tea leaves and not some sort of bogus tea leaf substitute) we're looking at a 1.5GHz Snapdragon device with WiMAX support, which means it could potentially be HTC's long-rumored Android smartbook, or at least a spiritual successor to the Shift. We're also told that the mysterious device is codenamed Olympian, and that it could sport a new version of Android (build ID FRE65C -- being billed as Android 2.2). Since you're adults, and we feel that we can trust you, we're placing the alleged file after the break, so you can make up your own mind -- handset, smartbook, or nothing at all? Just remember, it was a leaked HTC that broke the news of Android 2.1's existence.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRE65C
ro.build.display.id=htc_scorpion-userdebug 2.2 FRE65C eng.xxxxx.20100206 test-keys
ro.build.version.incremental=26741
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Sat Feb 6 13:42:06 CST 2010
ro.build.date.utc=1264645720
ro.build.type=userdebug
ro.build.user=u40000
ro.build.host=builder00101
ro.build.tags=test-keys
ro.product.model=HTC Olympian
ro.product.brand=generic
ro.product.name=htc_scorpion
ro.product.device=scorpion
ro.product.board=cortex1.5ghz
ro.product.cpu.abi=armeabi-va8c
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.board.platform=qsd8672
# ro.build.product is obsolete; use ro.product.device
ro.build.product=scorpion
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.47.3.2 CL2***** test-keys
ro.build.changelist=2*****
ro.build.modelid=DF4732***
ro.build.fingerprint=generic/htc_scorpion/scorpion/scorpion:2.2/FRE65C/26741:userdebug/test-keys
keyguard.no_require_sim=1
# end build properties
#
# system.prop for scorpion
#
ro.sf.lcd_density=240
#
ro.home.ui.defualt.=0
ro.home.ui.media.scorpion.=1
ro.home.ui.sense.=0
ro.home.ui.define.=0
#
#
rild.libpath=/system/lib/libhtc_ril.so
wimax.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRE65C
ro.build.display.id=htc_scorpion-userdebug 2.2 FRE65C eng.xxxxx.20100206 test-keys
ro.build.version.incremental=26741
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Sat Feb 6 13:42:06 CST 2010
ro.build.date.utc=1264645720
ro.build.type=userdebug
ro.build.user=u40000
ro.build.host=builder00101
ro.build.tags=test-keys
ro.product.model=HTC Olympian
ro.product.brand=generic
ro.product.name=htc_scorpion
ro.product.device=scorpion
ro.product.board=cortex1.5ghz
ro.product.cpu.abi=armeabi-va8c
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.board.platform=qsd8672
# ro.build.product is obsolete; use ro.product.device
ro.build.product=scorpion
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.47.3.2 CL2***** test-keys
ro.build.changelist=2*****
ro.build.modelid=DF4732***
ro.build.fingerprint=generic/htc_scorpion/scorpion/scorpion:2.2/FRE65C/26741:userdebug/test-keys
keyguard.no_require_sim=1
# end build properties
#
# system.prop for scorpion
#
ro.sf.lcd_density=240
#
ro.home.ui.defualt.=0
ro.home.ui.media.scorpion.=1
ro.home.ui.sense.=0
ro.home.ui.define.=0
#
#
rild.libpath=/system/lib/libhtc_ril.so
wimax.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range
@artlazza well , its actually faster than an atom (the current N270 generation) since it's 1.5 ghz dual core vs 1.6 single core...
@artlazza The Atom isn't actually all that fast. Its close to being outpaced if not already.
@artlazza The disadvantage of an x86 architechture is their high power demands when idle.
Actually, from the file, I got the impression that Scorpion is the codename and Olympian is the marketing name.
Scorpion just appears in lowercase as an identifier; "HTC Olympian", on the other hand, is given as the product name, with proper capitalization and the HTC brand attached.
Please be sprint...
@Want an upgrade
You forgot to say pretty please :)
@deltatko
awww damnn I guess verizon gets it...to bad I forgot the pretty please...I guess I'll just have to replace my old moto q (stuck with it until upgrade) with the supersonic:)
@Want an upgrade
well.... if it's rocking WiMax then it's Sprint
Whatever it is me likeey! I'll take 3 please with extra green robots to go.
Can we have this as a handset with a keyboard, please? I need to replace my G1.
Well it still can't make you coffee... (does anyone else thinks Nexus One is old ? )
Not sure if this is correct but could ro.sf.lcd_density=240 be the devices pixel density? Although we can't necessarily discern a resolution from it, it may still be relevant to the type of device this could be. It has a lower pixel density than the nexus one but higher than the HD2's. Also larger screen devices are typically much lower when it comes to pixel density (in the 100-150 range). It would seem this would probably be a phone type device. Possibly a 4.2" at 480x800. If so sign me up cause that would be an extremely powerful device for that size if they can work out the inherent battery drain that processor is gonna have. Maybe a miniaturized pixel qi... alright probably not but a geek can dream.
@Warai On a 4.2' screen the vertical res would have to be 1008 if the pixel density where 240. so it would be more like 604x1,008 on a 4.2' screen. Which would still be awesome. Why 4.2 by the way
Not sure if this is correct but could ro.sf.lcd_density=240 be the devices pixel density? Although we can't necessarily discern a resolution from it, it may still be relevant to the type of device this could be. It has a lower pixel density than the nexus one but higher than the HD2's. Also larger screen devices are typically much lower when it comes to pixel density (in the 100-150 range).
It would seem this would probably be a phone type device. Possibly a 4.2" at 480x800. If so sign me up cause that would be an extremely powerful device for that size if they can work out the inherent battery drain that processor is gonna have. Maybe a miniaturized pixel qi... alright probably not but a geek can dream.
@Warai battery pff... who needs battery , i just hope it wont melt and explode just like some other famous device did some months ago
if(core== snapdragon){
win();
} else {
fail();
}
Honestly, if HTC can pull this off with a phone I'd take the battery hit. Especially if it has a removable battery. A high end desk top and a superphone is the future I want. Fuck tablets and all that foolishness.
yowsers, though when i was at an gdgt meetup the HTC rep said they'd never make another shift (which i was TOTALLY disappointed to hear...even if it was a flop). With those specs you could make the thing dual boot android and chrome. It's wimax, so it's guaranteed sprint. I'd love to see this as competition to the dell mini 5 (but with a hard keyboard and a swivel screen), though i am left wondering if HTC is trying to repeat the osborne effect.
Wow, that's almost as fast as an Intel Atom!
why does "htc_scorpion" have an underscore, while "HTC Olympian" is written normally? two types of naming schema are not good!
Could it be the google tablet?
@geegee
I think the Google tablet will run Chrome OS and not Android.... But then again I had a similar thought last time a major tablet was announced sooo...
Hey is this HD2 killer? If this is better than the HD2 well it looks like I might just check it out. Andoid hmmm?
Tablet.
hmm i thought scorpion was the next generation of snapdragon where you can double up processors in a device.
btw the band pictured above is called Scorpions,
nice try though :P
1.5ghz handset.... man how time's have changed...
This looks to be fake I'm afraid.
check the build dates
ro.build.date=Sat Feb 6 13:42:06 CST 2010
ro.build.date.utc=1264645720 that is Thu, 28 Jan 2010
they should be the same when compiling.
Also obvious spelling errors
ro.home.ui.defualt.=0
This is wrong syntax, also spaces around "=" isn't allowed.
wimax.interface = tiwlan0
If it was using Cortex A9 it shouldn't say
ro.product.cpu.abi=armeabi-va8c
because Cortex A9 uses ARMv7-A if you check ARMs specs, and there is no v8 finished yet.
sorry guys
@Fredro Good eye... :: adds salt ::
I don't know how you guys think about the snapdragon, but those guys look pretty badass
I'm going to guess that it's not a netbook. Notice in the code that there's an LCD Density value towards the bottom which sounds (and looks) a lot like a pixels per inch value. If it's 240 PPI, it indicates a device with a fairly small display and a large resolution. It puts it right around in the same ballpark as the Nexus One's display resolution, in fact.
It does look like an awfully overpowered processor (QSD8672) for a smartphone, but hey, I'm not going to complain if this is true.