FORUMS

Mysterious GG1 Google Device Stops by FCC. Glass v2?

As the year progresses, we draw further away from Google’s annual I/O … more

Material and Material Dark Hit Samsung’s Theme Store

The latest version of Touchwiz, launched alongside the Galaxy S6 and S6 Edge, … more

Swappa’s New App Helps You Value Your Device

There comes a sad time in everyone’s life where you must part ways with your … more

Xiaomi Sold 34.7 Million Phones In 6 Months

2015 has been a phenomenal year for Xiaomi so far. With a stellar rise in 2014, 2015 saw … more

Honeycomb now testing on Nexus 1!!

622 posts
Thanks Meter: 56
 
By apheonixboy, Senior Member on 28th November 2010, 08:24 AM
Post Reply Subscribe to Thread Email Thread
Honeycomb 3.0 on nexus 1?

http://www.airbenchmark.com/reports/results/83

Sent from my Overclocked, FroYo'ed-up 2.2.1 EVO 4G
 
 
28th November 2010, 08:26 AM |#2  
msavic6's Avatar
Senior Member
Flag Vancouver
Thanks Meter: 558
 
More
:eek:

Sent from my Nexus One using XDA App
28th November 2010, 08:36 AM |#3  
apheonixboy's Avatar
OP Senior Member
Flag Eagle Pass
Thanks Meter: 56
 
Donate to Me
More
Look at this list:

http://www.airbenchmark.com/reports/devices

Devices number 61 and 62 both have firmwares 3.0

Sent from my Overclocked, FroYo'ed-up 2.2.1 EVO 4G
28th November 2010, 10:12 AM |#4  
Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by apheonixboy

]

Devices number 61 and 62 both have firmwares 3.0

Sent from my Overclocked, FroYo'ed-up 2.2.1 EVO 4G

59 as well
28th November 2010, 10:25 AM |#5  
Senior Member
Thanks Meter: 7
 
More
sorry i call bs on this one...
the first 2.3 entry might have been legit but os version says 3.0 but the build says 2.3. its like someone was trying to figure out how to change the info in the build.prop or whereever it gets that os info from to say the right thing.

Code:
HRI83D
Code:
passion-userdebug 2.3 GRH47B 77346 test-keys
Code:
passion-userdebug 3.0 HRI783D 77346 test-keys
Code:
passion-userdebug 3.0 HRI83D 77346 test-keys
You have to admit the pattern is a little bit suspect
28th November 2010, 11:13 AM |#6  
Mokurex's Avatar
Senior Member
Flag Bangkok
Thanks Meter: 20
 
More
Dear Google, where is my gingerbread?
28th November 2010, 11:32 AM |#7  
Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by bewA

sorry i call bs on this one...
the first 2.3 entry might have been legit but os version says 3.0 but the build says 2.3. its like someone was trying to figure out how to change the info in the build.prop or whereever it gets that os info from to say the right thing.

Code:
HRI83D
Code:
passion-userdebug 2.3 GRH47B 77346 test-keys
Code:
passion-userdebug 3.0 HRI783D 77346 test-keys
Code:
passion-userdebug 3.0 HRI83D 77346 test-keys
You have to admit the pattern is a little bit suspect

I noticed that as well, but apart from suspicious, what else could you say?
Not that Honeycomb is close, but could be that Google made a first trial of Honeycomb on a Nexus One.

Nothing conclusive, nothing deceptive either
28th November 2010, 01:26 PM |#8  
Senior Member
Flag Lüneburg
Thanks Meter: 35
 
Donate to Me
More
Quote:
Originally Posted by Mokurex

Dear Google, where is my gingerbread?

+1
/10chars
28th November 2010, 02:11 PM |#9  
Senior Member
Flag Nice
Thanks Meter: 34
 
More
Has to be fake. Why would there be GRH83D (which is FRG83D with F and G incremented), and more obviously, why would Honeycomb be the same deal, with G and H incremented too?

And why would all three builds have the exact same test keys? That makes no sense at all. Try to type passion-userdebug on Google, and you'll see every build had different test-keys:

ERD72 : 22132
FRF50 : 38042
FRF51 : 38176
FRF85 : 38988

I don't want to believe that all three build have the same test keys, something doesn't add up.
28th November 2010, 04:48 PM |#10  
GldRush98's Avatar
Senior Member
Flag Taylorville, IL.
Thanks Meter: 286
 
More
Quote:
Originally Posted by G0belet

Has to be fake. Why would there be GRH83D (which is FRG83D with F and G incremented), and more obviously, why would Honeycomb be the same deal, with G and H incremented too?

And why would all three builds have the exact same test keys? That makes no sense at all. Try to type passion-userdebug on Google, and you'll see every build had different test-keys:

ERD72 : 22132
FRF50 : 38042
FRF51 : 38176
FRF85 : 38988

I don't want to believe that all three build have the same test keys, something doesn't add up.

This. Obvious fake is obvious.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes