The status of Android 3.1 Honeycomb on the Nook Color

Search This thread

surfboy

Member
Jun 21, 2009
7
1
This looks interesting: engadget.com/2011/07/22/lenovos-7-inch-ideapad-caught-by-mr-blurrycam/

"this is the company's 7-inch IdeaPad, which might be (internally) dubbed the A1-07. It's said to be powered by a TI OMAP3621 processor (which also drives the Nook Color), features a 7-inch 1024 x 600 touchscreen, a Broadcom GPS unit, 3G wireless with a SIM slot, and room for a microSD card as well. A 3,700mAh battery supposedly keeps things juiced, both front- and rear-facing cameras are on offer, and it's all wrapped in a glossy plastic styling that makes it look a little like a TouchPad with some bare metal highlights. It also features three buttons up front that we're hoping don't mean it's been relegated to Android 2.x."

7 inch Lenovo Thinkpad tablet with the same 3 button, dual camera setup as the 10inch Tegra tablets out there, and in addition it uses the OMAP3621 CPU like the Nook. I doubt that a major player like Lenovo would bring out a 2.3 tablet device if theyve just released 2 tablets with 3.1 (albeit 10 inch Tegras the pair of them).

Lets hope its out soon!
 

patruns

Senior Member
May 30, 2011
1,025
101
I think there is a reason you don't see any Honeycomb devices with a 7" screen. It is not really necessary. I trust that Lenovo knows what they are doing. Also remember there are hardly any apps out there designed for Honeycomb.
 

DigitalMD

Senior Member
Mar 16, 2010
2,931
639
Washington DC
I think there is a reason you don't see any Honeycomb devices with a 7" screen. It is not really necessary. I trust that Lenovo knows what they are doing. Also remember there are hardly any apps out there designed for Honeycomb.

Honeycomb is a lame duck bridge. It's being used as a marketing tool for new tablets. App development is market driven. Since there's not a huge market, the developers are not messing with Honeycomb apps a lot. And most apps that work for Gingerbread are fine on Honeycomb. Apple claims their market research shows that 10.1" is optimum and 7" is not very desired. I think that's a smoke screen and Apple will soon come out with a 7 or 8" IPad. I tried toting a 10 inch android tab and even played with the Ipad, but its too big for daily travel use. I much prefer the Nook's size and weight (small) , much more portable and holdable.
 

michaelg1030

Senior Member
Apr 28, 2011
574
71
meh. 7" is one thing, 10" is another, 12-14 is another.

Until I can write on one just like I can a piece of paper, it's just a toy.

Not sure I understand your logic. Its a tablet, not a piece of paper. If we wanted something to write on we'd all have saved hundreds of dollars and bought a five star notebook and some BICs.

Sent from my Droid using XDA Premium App
 

michaelg1030

Senior Member
Apr 28, 2011
574
71
The reason is that 7" devices are not supported until 3.2.

That's exactly the reason, plus what the other poster said about it being a lame duck bridge.

Google could have just used froyo with some tweaks and had it running perfectly on some larger tablets like how Samsung saw it on their tab, but they wanted to "change" how we view tablets and not just put a phone rom on a larger screen like their competitor does. So they rushed out a beta software and here in lies HC.

HC has some great features but having bought and returned a HC tablet, I find the overall experience of froyo/GB on the nook much more enjoyable. This is why I'm confused why everyone wants to have HC running on the nook. Even if we had the Aosp for HC, I think many would resort back to GB based roms. But I get it, it would be cool to say we got HC running on a $250 e-reader, something Motorola and the others had a tough time doing even with their vast resources.

Sent from my Droid using XDA Premium App
 

douginoz

Senior Member
Jan 18, 2007
199
30
Melbourne
Google have to manage a smooth transition of their development priorities, projects, and staff from one platform to another. Honeycomb likely was necessary due to h/w manufacturers coming out with a larger form factor, which was too big for the existing platform to exploit, and too immature to be seen as an investment priority to compete against Apple. So some development resources would have been channeled to come out with an intermediary, exploratory newer (Honeycomb) platform that exploits the increased real estate space and larger form factor (not a phone, not a portrait device, not a very portable device, etc.).

Honeycomb would have been a stop-gap compromise measure, and based on it's success in supporting the new devices out there and the development architecture progress for a new form factor, Google will have then pushed more resources towards this new platform. Thus, the next version of Android will reflect this increased focus, architectural consistency, and strategic focus.
 
Last edited:

patruns

Senior Member
May 30, 2011
1,025
101
The reason is that 7" devices are not supported until 3.2.

Actually, that is not the reason. The reason is the 7" screen size is not so far off that Gingerbread and related apps still look and function fine on it. Moving up to 10" and now some apps start to look.... well.... like the old Silly Putty that you put on a comic to get the impression and then stretched. That's why Google is not giving Honeycomb to manufacturers to place on 7" tablets. Ice Cream Sandwich is supposed to resolve all this so that app developers will not have to worry about the screen size. The OS will take care of it. :)
 

cdaters

Senior Member
May 16, 2009
96
14
Tucson, AZ
So I was at Wal-Mart last night, and I saw an Acer Iconia 7" tablet running Honeycomb for $260 roughly.

I just checked their website and they don't show it, so I will have to run back there tonight and take a picture of it.
 
  • Like
Reactions: Modded Darts

Top Liked Posts

  • There are no posts matching your filters.
  • 49
    Since many people asked what I was doing these days:

    The Nook Color running a healthy mix of Android 3.1 Honeycomb from the Xoom and Android 3.1 from Google's SDK.
    As can be seen towards the end the Launcher application suffers from some drawing issues. The same issues can be observed in Google's SDK 3.1 emulator. The emulator and the nook both are doing software UI rendering instead of the new in 3.0 hardware accelerated UI rendering. Sadly the PowerVR SGX530 drivers that are (publicly) available right now are lacking some features to activate the hardware UI rendering on the nook. (like support for EGL_SWAP_BEHAVIOUR = EGL_BUFFER_PRESERVED
    and the GL_OES_EGL_image_external extension). I started patching around those issues, which is hard without the access to the Android source, and can confirm that the nook's hardware is more than capable of running 3.0/3.1 hardware accelerated even though the source might need some patches if we don't get updated drivers for the SGX530.

    So the status right now is: software UI with redraw issues or hardware UI with a working home screen but tons of more issues in other applications.

    Other than that sound, wifi and opengl works. (no DSP/video decoding so far)


    So who's up for solving the redrawing issues?

    Possible solutions are:
    • getting our hands on a newer SGX530 driver than 1.1.16.4061
    • unpacking, patching and repacking Launcher2
    • ?
    • waiting until Google releases the 3.1 AOSP source

    -Rafael Brune
    7
    Not really. I don't mean to sound too frustrated, but it is almost irrelevant that 3.2 adds 7" support, since that has not been a problem (the big thing that i understand that it might fix, is the system being forced to have the tiny 120DPI).

    A system dump from a non Omap 3 device will do us almost no good at all; certainly not much better (and in some cases worse) than the SDK builds we can already get. The compiled OS'es are compiled for specific hardware; if it is different than ours (Tegra 2...), we cannot use it.

    Actually I would like to have a system dump of the xoom 3.2 - so if someone can hand me one that would be great, otherwise I'll try to manually patch the 3.1 dump I have to 3.2 with the official update file.

    Also what I actually did for 3.0 and 3.1 is mixed up the xoom dump, the sdk image and hardware drivers from the original nook images and cyanogen mod 7 into one tasty blend. The only thing really hard to get running with using the xoom dumps is hardware video decoding since that is really deeply compiled into the android binaries and tries to use the tegra hardware, patching that into using the omap hardware and drivers is not an easy task. (not that any of the other things are easy to do but this is a few steps more intense).
    7
    Thanks, Mr. deeper-blue. With the recent CM7 (nightly 86) debacle on SGX/DSP/HW Overlay front, the only serious hope remains with your Android 3.1 port for NC (though I'm afraid it will have better chances with kernels 2.6.36 and newer). Anyway, yours is a noble and daring effort, I will follow it religiously in my blog.

    lol, here we go again....The SGX, DSP, and HW overlay work fine in CM7. There is no debacle except for the one inside your head.

    If you don't like CM7/Gingerbread that's fine. Please don't use it. Surely you can understand my frustration to have someone constantly spread FUD about the work that myself and others have done. What aludal wants is hardware flash acceleration and hardware accelerated skia. This isn't going to happen on Gingerbread and it is not a reflection of how well our SGX, DSP, and HW overlay are working.
    1
    +1 !

    Keep up with the excelent work !!! :)

    ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts

    @deeper-blue
    good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here

    Completely agree, there are a couple of interesting apps in the market that take advantage of HC and would be great in the Nook.

    If you ask me waiting for AOSP don't look as such a good idea, since it's release is not so sure.
    1
    @Modded Darts :

    We landed on the moon? No way!

    Sent from my SGH-I997 using xda premium