Is the HTC / Google Nexus one the king of the crop anymore?
Not if the following rumor has any validity.

More and more rumors appear everyday about new devices coming from HTC and this latest leaked build file looks like its from the HTC Scorpion. I can’t confirm the validity of this information as this was anonymously sent to us but it is mentioning the HTC Scorpion and possibly Android 2.2 and 1.5Ghz processor. It would be nice to think that this is true as the evolution on Android devices just keeps snowballing.

If you know anything about this device please give us some information in the comments.

  1. # begin build properties
  2. # autogenerated by buildinfo.sh
  3. ro.build.id=FRE65C
  4. ro.build.display.id=htc_scorpion-userdebug 2.2 FRE65C eng.xxxxx.20100206 test-keys
  5. ro.build.version.incremental=26741
  6. ro.build.version.sdk=8
  7. ro.build.version.codename=REL
  8. ro.build.version.release=2.2
  9. ro.build.date=Sat Feb 6 13:42:06 CST 2010
  10. ro.build.date.utc=1264645720
  11. ro.build.type=userdebug
  12. ro.build.user=u40000
  13. ro.build.host=builder00101
  14. ro.build.tags=test-keys
  15. ro.product.model=HTC Olympian
  16. ro.product.brand=generic
  17. ro.product.name=htc_scorpion
  18. ro.product.device=scorpion
  19. ro.product.board=cortex1.5ghz
  20. ro.product.cpu.abi=armeabi-va8c
  21. ro.product.cpu.abi2=armeabi
  22. ro.product.manufacturer=HTC
  23. ro.product.locale.language=mdpi
  24. ro.product.locale.region=
  25. ro.board.platform=qsd8672
  26. # ro.build.product is obsolete; use ro.product.device
  27. ro.build.product=scorpion
  28. # Do not try to parse ro.build.description or .fingerprint
  29. ro.build.description=1.47.3.2 CL2***** test-keys
  30. ro.build.changelist=2*****
  31. ro.build.modelid=DF4732***
  32. ro.build.fingerprint=generic/htc_scorpion/scorpion/scorpion:2.2/FRE65C/26741:userdebug/test-keys
  33. keyguard.no_require_sim=1
  34. # end build properties
  35. #
  36. # system.prop for scorpion
  37. #
  38. ro.sf.lcd_density=240
  39. #
  40. ro.home.ui.defualt.=0
  41. ro.home.ui.media.scorpion.=1
  42. ro.home.ui.sense.=0
  43. ro.home.ui.define.=0
  44. #
  45. #
  46. rild.libpath=/system/lib/libhtc_ril.so
  47. wimax.interface = tiwlan0
  48. # Time between scans in seconds. Keep it high to minimize battery drain.
  49. # This only affects the case in which there are remembered access points,
  50. # 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

  • http://blackgin.altervista.org blackgin

    My opinion is: too many devices if all rumors are true

  • http://blackgin.altervista.org blackgin

    My opinion is: too many devices if all rumors are true

  • enveed05

    I really enjoy hearing about all these great devices that get leaked to your site… what I’d enjoy even more is actually being able to get my hands on one. Keep the news coming but please tell the manufacturers to get the phones out to us… quickly.

  • enveed05

    I really enjoy hearing about all these great devices that get leaked to your site… what I’d enjoy even more is actually being able to get my hands on one. Keep the news coming but please tell the manufacturers to get the phones out to us… quickly.

  • i2Fuzzy

    wimax.interface = tiwlan0

    Also, no Sense. Home UI is set to Scorpion. What’s that mean?

    • Dr. Droid

      Umm…
      ro.home.ui.defualt.=0
      ro.home.ui.media.scorpion.=1
      ro.home.ui.sense.=0
      ro.home.ui.define.=0

      ro.home.ui.sense.=0 Looks to me as if it will have sense.

  • i2Fuzzy

    wimax.interface = tiwlan0

    Also, no Sense. Home UI is set to Scorpion. What’s that mean?

    • Dr. Droid

      Umm…
      ro.home.ui.defualt.=0
      ro.home.ui.media.scorpion.=1
      ro.home.ui.sense.=0
      ro.home.ui.define.=0

      ro.home.ui.sense.=0 Looks to me as if it will have sense.

  • smikwily

    May just mean they don’t have a sense wrapper for 2.2 yet.

  • smikwily

    May just mean they don’t have a sense wrapper for 2.2 yet.

  • Dr. Droid

    We don’t speak russian here kthx

    • David

      Es un trackback . No es un comentario

    • NecroPsyChroNauTron

      Me either, but it doesn’t take a genius to read “Is a trackback. Is not a comment”

  • Rich

    ro.product.model=HTC Olympian

    HTC Olympian… What’s that refer to? Another upcoming HTC model??

  • Rich

    ro.product.model=HTC Olympian

    HTC Olympian… What’s that refer to? Another upcoming HTC model??

  • SAI

    omg waaaay too many devices. I REALLY need a new phone(my g1 is getting to slow for me). I want the N1 but then the Bravo comes out. I want the Bravo but this device is speculated. AND YET THERE STILL A SNAPDRAGON ANDROID PHONE WITH QWERTY KEYBOARD (for tmobile)!!!! arggghh….what phone should I get now? Do I wait? Do I get N1 now? /end rant

    • Edgar

      what is the name of the phone with QWERTY keyboard and snapdragon that’s coming for tmobile? I havent heard of that one yet.

    • Moose09876

      I’m in the exact same boat. My G1’s touchscreen is getting more buggy every day, and the battery life has always been terrible. All I want is a 4.3″ capacitive touchscreen, hardware keyboard, and a HUGE battery. I don’t care at all how thick it is. I NEVER want to have to charge a phone 3 times in one day. The N1 is my best bet right now, and if there’s nothing better in the works by the time it goes on Verizon, I’ll probably end up getting that. (sigh)

    • Brett

      I sold my G1 for a MyTouch, sold my MyTouch for a N1. The N1 is so unreal at processing that I don’t think that another phone is necessary. If something releases that’s faster than the N1, big deal. I have never seen a split second of lag on my phone. Apps stay in my RAM so they are accessed immediately and the screen is the exact size I need. Any larger would be too big for my hands. About the Keyboard, I heard about it too and I know where you’re coming from. But, once you trade in your keyboard for a sleeker thinner phone you’ll realize that you never want a keyboard again. I want a keyboard but the sleek, slim design of a phone without a keyboard wins it for me. I can type just as fast with my soft keyboard as I could with my G1. Once you use it for about a week or two you’ll forget about the hard keyboard.

      My wife wouldn’t get away from the G1 because she wanted the Keyboard. I got her to use the MyTouch for a week and she sold her G1 because she likes it a lot better.

  • SAI

    omg waaaay too many devices. I REALLY need a new phone(my g1 is getting to slow for me). I want the N1 but then the Bravo comes out. I want the Bravo but this device is speculated. AND YET THERE STILL A SNAPDRAGON ANDROID PHONE WITH QWERTY KEYBOARD (for tmobile)!!!! arggghh….what phone should I get now? Do I wait? Do I get N1 now? /end rant

    • Edgar

      what is the name of the phone with QWERTY keyboard and snapdragon that’s coming for tmobile? I havent heard of that one yet.

    • Moose09876

      I’m in the exact same boat. My G1’s touchscreen is getting more buggy every day, and the battery life has always been terrible. All I want is a 4.3″ capacitive touchscreen, hardware keyboard, and a HUGE battery. I don’t care at all how thick it is. I NEVER want to have to charge a phone 3 times in one day. The N1 is my best bet right now, and if there’s nothing better in the works by the time it goes on Verizon, I’ll probably end up getting that. (sigh)

    • Brett

      I sold my G1 for a MyTouch, sold my MyTouch for a N1. The N1 is so unreal at processing that I don’t think that another phone is necessary. If something releases that’s faster than the N1, big deal. I have never seen a split second of lag on my phone. Apps stay in my RAM so they are accessed immediately and the screen is the exact size I need. Any larger would be too big for my hands. About the Keyboard, I heard about it too and I know where you’re coming from. But, once you trade in your keyboard for a sleeker thinner phone you’ll realize that you never want a keyboard again. I want a keyboard but the sleek, slim design of a phone without a keyboard wins it for me. I can type just as fast with my soft keyboard as I could with my G1. Once you use it for about a week or two you’ll forget about the hard keyboard.

      My wife wouldn’t get away from the G1 because she wanted the Keyboard. I got her to use the MyTouch for a week and she sold her G1 because she likes it a lot better.

  • kingkurryq

    guys….. do you have any idea how easy it is to modify a build file??? any idiot could do it, then put it into a rom and make what looks like a legit screenshot of the phone……. it can be done in like 10 minutes tops…..

    and 1.5 ghz??? i dont even think qualcomm has released thier 1.5 ghz snapdragons yet. It was supposed to be Q3 or Q4 2010.

    • Steven58

      1.5 ghz snapdragons.. hmm…

      I’m due for an upgrade. I was drooling over the DROOOOOID a couple of months ago, but now it seems to be out of date. Heh. The technology is improving so fast. So fast, it is improving, that I am having trouble finding a place to jump into it and deciding on a new phone.

    • Brett

      I agree. I can make my prop file look like this in 10 minutes so I’ll believe it when we get some screen shots.

      About the 1.5ghz, my question is…why? Nobody will need 1.5ghz. as I have posted before my N1 is so unreal at processing things that there is no need for anything faster. Example, I drop down my notification bar to select my text message to read..before the notification bar has time to slide back up to the top the message is already open ready for me to reply…There isn’t any room for improvement. This is one of the reasons I got this phone. If something else beats it…so what? So your phone is just as fast as mine with better specs. The snapdraggon is unbelievably fast. Now what I can say is that we should be looking more forward to the dalvik turbo…that sounds like something I will be interested in.

  • kingkurryq

    guys….. do you have any idea how easy it is to modify a build file??? any idiot could do it, then put it into a rom and make what looks like a legit screenshot of the phone……. it can be done in like 10 minutes tops…..

    and 1.5 ghz??? i dont even think qualcomm has released thier 1.5 ghz snapdragons yet. It was supposed to be Q3 or Q4 2010.

    • Steven58

      1.5 ghz snapdragons.. hmm…

      I’m due for an upgrade. I was drooling over the DROOOOOID a couple of months ago, but now it seems to be out of date. Heh. The technology is improving so fast. So fast, it is improving, that I am having trouble finding a place to jump into it and deciding on a new phone.

    • Brett

      I agree. I can make my prop file look like this in 10 minutes so I’ll believe it when we get some screen shots.

      About the 1.5ghz, my question is…why? Nobody will need 1.5ghz. as I have posted before my N1 is so unreal at processing things that there is no need for anything faster. Example, I drop down my notification bar to select my text message to read..before the notification bar has time to slide back up to the top the message is already open ready for me to reply…There isn’t any room for improvement. This is one of the reasons I got this phone. If something else beats it…so what? So your phone is just as fast as mine with better specs. The snapdraggon is unbelievably fast. Now what I can say is that we should be looking more forward to the dalvik turbo…that sounds like something I will be interested in.

  • Salpiche

    base on the line “rild.libpath=/system/lib/libhtc_ril.so
    wimax.interface = tiwlan0” it is to be assume that it is going to Sprint.

    • Salpiche

      that was more of a question not a statement.

  • Salpiche

    base on the line “rild.libpath=/system/lib/libhtc_ril.so
    wimax.interface = tiwlan0” it is to be assume that it is going to Sprint.

    • Salpiche

      that was more of a question not a statement.

  • Rich
    • Steven58

      Yeah baby!

  • Rich
    • Steven58

      Yeah baby!

  • Crowwalks

    ro.home. means it will support differnt home UI’s same thing as bravo supports sense, android default launcher etc etc seems like scorpion has a new Ui, I hope the buzz is as real as it sounds!

  • Crowwalks

    ro.home. means it will support differnt home UI’s same thing as bravo supports sense, android default launcher etc etc seems like scorpion has a new Ui, I hope the buzz is as real as it sounds!

  • conan

    Wow this is amazing, mutiple homes oh yea I can’t wait

  • conan

    Wow this is amazing, mutiple homes oh yea I can’t wait

  • stefan

    Its fake. Yor are not allowed to use spaces before and afte “=”. See
    wimax.interface = tiwlan0

    • Jackson R.

      false. it was like that for the nexus one

  • stefan

    Its fake. Yor are not allowed to use spaces before and afte “=”. See
    wimax.interface = tiwlan0

    • Jackson R.

      false. it was like that for the nexus one

  • AKSnoopy

    gimme gimme.. 1.5ghz sounds awesome. As an early g1 adapter, I hope this will be out before or around when my contract is up with TMobile. :)

  • AKSnoopy

    gimme gimme.. 1.5ghz sounds awesome. As an early g1 adapter, I hope this will be out before or around when my contract is up with TMobile. :)

  • Drizzy

    “its fake” check the datez, they do not match also my source hasn’t even heard of 2.2… I’m stuck on 2.1 dumps but no 2.2 :p. Sorry folks but this is bogus

  • Drizzy

    “its fake” check the datez, they do not match also my source hasn’t even heard of 2.2… I’m stuck on 2.1 dumps but no 2.2 :p. Sorry folks but this is bogus

  • Jubeh

    Well, that’s funny because this would be the first time I’ve seen a build.prop list processor speed.
    Not only that, but several other parts, seems doctored to me, for example, how two automatically-generated build.props managed to get created at exactly the same time, mdpi being a locale language, specially after a 240 dpi (hdpi) density was specified somewhere else. And, best of all, how the unix time tag (ro.build.date.utc=1264645720) reads “Wed Jan 28 2010 02:28:40 GMT” but the date tag (ro.build.date) reads “Sat Feb 6 13:42:06 CST 2010”. That tells me somebody living in CST doctored those build.props.
    Sorry, guys, they’re fake.

  • Jubeh

    Well, that’s funny because this would be the first time I’ve seen a build.prop list processor speed.
    Not only that, but several other parts, seems doctored to me, for example, how two automatically-generated build.props managed to get created at exactly the same time, mdpi being a locale language, specially after a 240 dpi (hdpi) density was specified somewhere else. And, best of all, how the unix time tag (ro.build.date.utc=1264645720) reads “Wed Jan 28 2010 02:28:40 GMT” but the date tag (ro.build.date) reads “Sat Feb 6 13:42:06 CST 2010”. That tells me somebody living in CST doctored those build.props.
    Sorry, guys, they’re fake.

  • Drizzy

    I have looked into this and it seems only one thing is correct and thats the build id, there is a froyo rebuilt eclair but I do not know what the numbers mean :(

    drc = donut rebuilt cupcake
    drd = donut rebuilt donut
    erd = eclair rebuilt donut
    ere = eclair rebuilt eclair

    and etc etc well thats maybe the only accurate part in this build.prop :)

    the latest I have is the moto dump 2.1 and i havent heard anything esle about 2.2 from source

  • Drizzy

    I have looked into this and it seems only one thing is correct and thats the build id, there is a froyo rebuilt eclair but I do not know what the numbers mean :(

    drc = donut rebuilt cupcake
    drd = donut rebuilt donut
    erd = eclair rebuilt donut
    ere = eclair rebuilt eclair

    and etc etc well thats maybe the only accurate part in this build.prop :)

    the latest I have is the moto dump 2.1 and i havent heard anything esle about 2.2 from source

  • Rowanator

    I contacted HTC regarding this… of course, they denied that they were working on any devices for use with the 1.5-GHz Snapdragon. I still think they’re building one. :-)

  • Rowanator

    I contacted HTC regarding this… of course, they denied that they were working on any devices for use with the 1.5-GHz Snapdragon. I still think they’re building one. :-)

  • K A Cheah

    THE REAL 4 G SERVICE PROVIDERS COULD SEAMLESSLY OFFER THE BEST WITH BOTH WIMAX
    AND LTE FIRMLY INTEGRATED IN WHATEVER BANDWIDTH SPECTRUM ALLOCATED TO THEM BECAUSE THEIR TRANSMISSION EQUIPMENTS’ SOFTWARE AND HARDWARE COULD BE UPGRADED TO TRANSMIT BOTH SIGNALS VIA orthogonal frequency-division multiplexing (OFDM) JUST THE SAME FROM THEIR EXISTING TRANSMISSION INFRASTRUCTURES, THE ONLY PROBLEM IS THE RECEPTION DEVICES THAT MUST ALSO SUPPORT BOTH SIGNALS JUST THE SAME THEREFORE ANDROID 2.2++ MOBILE PHONES SUPPORT BOTH WIMAX AND LTE WITH BUILT-IN ANTENNAS WHICH COULD HAVE GREAT RECEPTION FOR BOTH COULD BE THE BEST BET OF CAPTURING THE 4G EMERGING MARKETS THE WORLD OVER WHEN THE SAID 4 G SERVICES ARE LAUNCHED WORLD WIDE.

  • http://www.promoteamsrbija.rs/ PromoTeam

    This is a
    great and informative post.Well, the points given were facts that could never
    go wrong. I have visited so many pages with the same discussion and topics

  • http://www.mojpolovniauto.com/ Limun

    Good work. Thanks for the info. very useful tips indeed.

  • http://www.lplast.com kese

    thanks for info… good job