Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
apheonixboy
Old
#1  
apheonixboy's Avatar
Senior Member - OP
Thanks Meter 41
Posts: 602
Join Date: Sep 2010
Location: Eagle Pass

 
DONATE TO ME
Default Honeycomb now testing on Nexus 1!!

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
 
msavic6
Old
#2  
msavic6's Avatar
Senior Member
Thanks Meter 223
Posts: 1,060
Join Date: Jun 2010
Location: Vancouver
:eek:

Sent from my Nexus One using XDA App
 
apheonixboy
Old
#3  
apheonixboy's Avatar
Senior Member - OP
Thanks Meter 41
Posts: 602
Join Date: Sep 2010
Location: Eagle Pass

 
DONATE TO ME
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
 
BiTXBoi
Old
#4  
Member
Thanks Meter 4
Posts: 53
Join Date: Aug 2010
Quote:
Originally Posted by apheonixboy View Post
]

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
 
bewA
Old
#5  
Senior Member
Thanks Meter 6
Posts: 460
Join Date: Feb 2010
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
Samsung Galaxy Nexus
Asus Nexus 7
 
Mokurex
Old
#6  
Mokurex's Avatar
Senior Member
Thanks Meter 20
Posts: 562
Join Date: Nov 2009
Location: Bangkok
Dear Google, where is my gingerbread?
 
BiTXBoi
Old
#7  
Member
Thanks Meter 4
Posts: 53
Join Date: Aug 2010
Quote:
Originally Posted by bewA View Post
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
 
ptrrrrrck
Old
#8  
Senior Member
Thanks Meter 30
Posts: 1,066
Join Date: Jun 2009

 
DONATE TO ME
Quote:
Originally Posted by Mokurex View Post
Dear Google, where is my gingerbread?
+1
/10chars
Black apps for energy saving on AMOLED screens

Nexus One with
- CyanogenMod 7 Build by fitsnugly
- wildmonks' kernel
- Clockwork Recovery
 
G0belet
Old
#9  
Senior Member
Thanks Meter 27
Posts: 121
Join Date: Mar 2010
Location: Nice
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.
 
GldRush98
Old
#10  
GldRush98's Avatar
Senior Member
Thanks Meter 113
Posts: 1,809
Join Date: Jun 2006
Location: Taylorville, IL.
Quote:
Originally Posted by G0belet View Post
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.
---Phone---
Galaxy Nexus (AT&T)
Android 4.2.2 JDQ39, Baseband I9250XXLJ1, Unlocked, rooted, Clockwork Touch 6.0.2.3
---Tablet---
Nexus 7
Android 4.2.2 JDQ39, 16gb, Unlocked, rooted, Clockwork Touch 6.0.2.3
---Past---
Samsung Galaxy Tab (AT&T)
Android 2.3.3, 16gb, Smartass CPU Governor
Google Nexus One (AT&T)
Android 2.3.6 GRK39F, 5.08 Radio, Unlocked, rooted, Amon_RA 2.2.1
AT&T Fuze (Touch Pro)
AT&T 8525 (Hermes)
AT&T 8125 (Wizard)

 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...

XDA PORTAL POSTS

Boot Animation Paradise for your Android Device

The default boot animations on any device, no matter whichmanufacturer, are generally pretty … more

Flash Custom ROM and Recovery to Samsung Galaxy S 4

After reading about Dan Rosenberg’s bootloader exploit for the Samsung Galaxy S 4,I … more

Windows-Based Multi-Tool for the Sony Xperia U

If you are a flashaholic and an owner of the Sony Xperia U, you may be interested in the … more