yashsingh1/xdaforums huggingface dataset:
[Nook Color General] joenathane:
He is running 3.1, which he has been working on and has yet to release because of the bugs he demonstrates in the video.
[Nook Color General] zeno07706:
Great work DB, really excited to see the progress on this. I'm just wondering - would it be feasible to run this with ADW or similar as a holdover until the Launcher2 rendering issues are resolved?
[Nook Color General] RileyGrant:
Sounds like patching the launcher will be the easiest route. This is why I love you DB ahhaha, your work is amazing.
[Nook Color General] demonofsteel:
Hi deeper-blue,

If you want, I can offer you my help. I would be able to try to patch launcher2. I've been able to work out a few stuff in launcher2 when I was doing test builds of HC 3.0 and 3.1.

I'm trying to look if I can find some drivers for the PowerVR SGX530, but I unfortunately can't help by making 3.1 available on AOSP.
[Nook Color General] screech:
Is there a pointer to instructions on how to cook from SDK ? Have been looking around and have not found anything useful.

Wanted to take a crack at the graphics driver portion.
[Nook Color General] marlonbr:
Very nice work deeper-blue.

Don't let the lazy people uninspire your work. If the Android and Open-source community in geral would wait for corporations solutions linux would never have been created. This is the open-source spirit, guys. If you come here to say that open-source hackers should wait, you're on the wrong place doing the wrong stuff.

Back to honeycomb, even before this 3.1 news I was noticing that one of the main limitations we have on honeycomb is the laucher. I suggest that while we can't hack it (but we will keep trying), we use honeycomb with another launcher just for the sake of using the great tablet oriented apps we can't have on cm7.

About the source code, for me Google made clear that they weren't releasing it for a while. So, I think this is more motivation to make a honeycomb daily driver.

Keep up the great work, Good luck everyone and all hail to this awesome community.

--

Marlon Moura
[Nook Color General] I Am Marino:
Keep at it man, we appreciate the work.
[Nook Color General] rybo80:
Unfortunately I lack the technical expertise to help keep this moving forward; however, I think an earlier poster was dead in his argument that waiting for source code is defeatist mentality for the open source "hacking" gurus out there.

I imagine that Deeper-blue could turn this into a truly polished machine....if he had the time to devote endless amounts of hours to this, but who does and that's why he's seeking assistance from other willing and capable hands.

If anything I hope others who are capable find some inspiration in the challenge and ultimately crack this one into something special.

Thanks in advance to Deeper - blue and other who continue to provide users with a cost effective tablet experience. :)

-Rt
[Nook Color General] fzr-r4:
More big thanks, deeper-blue, for your efforts in spite of no source release. It is heartening to hear that the Nook Color can conceivably take advantage of Honeycomb's hardware acceleration.

I, too, wish I could help code and patch, but I cannot do much other offer thanks and support!

(p.s. in the youtube video, you guys notice the icons for Music & Maps being switched at 1:45?)
[Nook Color General] Techienana:
+1

I can't help but I also support you moving ahead with your efforts. I like the HC apps but I could live without most of them. However, I love, love, love the 3.1 HC keyboard and if nothing else keeps me using it as a dd, the keyboard does. So, I would love to have an improved HC version.
[Nook Color General] hubtime:
Excellent work Deeperblue! Glad to see your still in the fight!
[Nook Color General] aludal:
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.

There's some indication that contrary to a popular belief that Android 3.0 has no distinct hardware limitations Acer Iconia A100 is delayed nevertheless:

Further info is here http://www.androidpolice.com/2011/05/25/unconfirmed-acer-delaying-iconia-a100-tablet-due-to-honeycomb-restrictions-on-7-inch-screens/

Mr deeper-blue project is looking even more heroic because of that.
[Nook Color General] sark666:
I'm behind on this stuff, too much goings on. What was this 'debacle'? I didn't think CM was ever trying to add hardware accel.

Btw, in the video linked in the first post, is this overclocked? I'm really impressed how smooth webbrowsing seemed. That alone makes me want this.

Opera is supposed to be hardware accelerated but it only seems slightly smoother than the other browsers. Or is there another browser for 2.x android that has hardware accel enabled?
[Nook Color General] clamder:
I'm also wondering what debacle he's talking about..
[Nook Color General] aludal:
I have a commented description of Encore commits in Nightly 86 in my blog

It's a faster, closer to (a desktop/Linux) Chrome browser with more effective Java/JS rendering engine. It was not so good in A 3.0.1. Now, in A3.1, it obviously has better (or just has) Renderscript (=A3 replacement of deprecated NEON framework)

Opera has its own render engine, its rendering operation can or cannot be accelerated by HW, all depending on availability of 2D/3D HW accelerated SGX drivers. These are not built satisfactorily yet. Or NEON framework/Open GL ES drivers are broken beyond repair (in A2.3.4). Those modules by TI claimed good are for 2.6.36+ kernels. We don't have such a luxury -- yet
[Nook Color General] joenathane:
Am I missing something? What blog? Does everyone else know something I don't?
[Nook Color General] FrasierCrane:
Aludal might have mentioned having a blog once or twice before.
[Nook Color General] racks11479:
lol :D

I just wanted to say lol, but i need at least 10 words to post a reply. So the rest of this is just ramblings.... :p
[Nook Color General] Link3737:
Getting the tablet version of Google Books sounds amazing. :D
[Nook Color General] hazridi:
You're really better off ignoring aludal.
[Nook Color General] dmbyte:
Ok. So for clarity, once DB gets his first pass out, if we can get a custom kernel greater than 2.6.36 to compile and work with it, we will have hardware accelerated video?
[Nook Color General] Narfx:
Post of the week :D
[Nook Color General] jewnersey:
Looking good. Thanks for all your work.
[Nook Color General] taylor.fowler:
+1 x infinity
[Nook Color General] skgtheblij:
Thanks everyone for all the work!!
[Nook Color General] Doward:
Looks that way... if you use the TI modules aludal alludes to :)
[Nook Color General] screech:
Anyone here who can help or needs help with this project ? I was looking at the drm driver they posted about a month ago and itself seems not that complex and/or nothing jumped out as 2.6.36 dependent (though I could be very wrong here)

So maybe back porting DRM is another option. Or are there other 2.6.36 goodness on the Omap front that is worth having ?
[Nook Color General] hazridi:
Like I said -- you should ignore Aludal. He does not know what he is talking about and constantly produces blog posts that have no technical relevance but have enough buzzwords that it sounds plausible.
[Nook Color General] dalingrin:
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.
[Nook Color General] Gin1212:
Lol, "Who else but Aludal!"

"He's Aludal! Aludal"

"Gigity Gigity Some More Nonsense~!" -Loose Interpretation of a Family Guy episode ;p
[Nook Color General] dalex7777:
Didn't Google say at I/O that they were not going to release Honeycomb's source?

The best bet is a leak from one of the Honeycomb "partners"--I'm betting Samsung as the best bet--or waiting until IceCream Sandwich is officially released.

It seems Google feels about HC the same way I do--it's a public beta!
[Nook Color General] chisleu:
NO THEY DIDN'T!!!!!!! I don't know where that crap started, but in the keynote speech on the first day they said it would be released, but probably will be delayed until they drop ice cream sandwich.

They have repeatedly said it will be released. They have no reason AT ALL to hold it back forever. NONE. They have a good reason to delay it, and they have, but they have no reason to hold it back. It would only hurt the platform.
[Nook Color General] riceboyler:
So, is there any possibility of this getting released as an Alpha or something as it sits? I don't need it to be perfect, heck, the current Hybrid RC1 from Divine_Madcat is really good, but certainly not perfect and seems to suffer from the same basic problems as I saw in the video of 3.1.

I'm not an Android Dev (not enough .NET for me;) ), but I'd love to help test and report back what I've found. So, @deeper-blue, any chance for an alpha release for messing around with? Please???? If I beg????? :)
[Nook Color General] Divine_Madcat:
OK, and when we have ICS, what is the point in caring about HC??? I mean, ICS is the combo of HC and Gingerbread, right? At that point, HC is obsolete.

So sure, they may release it, but since we will never use it, they may as well NOT release it...
[Nook Color General] iDidItAll4theNookie:
Hey, don't let it get you down. CM7 is top notch. I use the beta 3.1 everyday without a complaint. :)
[Nook Color General] botossi:
+1

Dal, you and the CM7 guys rules ;)

Thanks for making our nook look cooler than the others !
[Nook Color General] psychoace:
I think they did imply that we won't see 3.0's source and I think that's why everyone thinks it also ment honeycomb as a hole
[Nook Color General] jlt220:
How deep is this honeycomb hole you speak of? Just Kidding

but in all seriousness I am sure we will see the drop of HC even with ICS, and we should care about the HC source because it will not contain any phone pieces that our nooks do not need and it may even require less hardware capabilities given the fact that hardware seems to be changing quite rapidly. While any work done now on HC may be useless once the source drops it still would give us a wonderful experience until then. which i say is good.
[Nook Color General] Divine_Madcat:
But using HC when ICS is out is just silly. Google has already said ICS will run on everything, and with the overclock kernels, do you really think there are any OS features our device cannot handle? The nook handles games just fine, which are far more tasking than UI acceleration.

As it is, HC was nothing more than a beta for ICS anyway; I think we would all be better off using the finished OS (ICS) rather than the beta (HC).
[Nook Color General] jlt220:
Seeing as you are much more experienced in this arena than I am, you are probably right. However in the time before ICS is released HC is what we have, so if any of the devs do want to work with it i offer my support, and if not patience is a virtue here at XDA
[Nook Color General] Jaostar:
Hey Dal...

Did you already look at this? There is someone who's doing reverse engineering on the driver to implement an open source one...

May be with a little help to him, this could work for us?

https://github.com/tom3q/openfimg/wiki/Status
[Nook Color General] chisleu:
ICS incorporates 3.x and 2.x branches into one API. 3.x is still for big screens and 2.x is phones, but code written for ICS will run on both (which is the solution to "apple doesn't fork.")
[Nook Color General] dalingrin:
That work isn't applicable to us. We have a PowerVR SGX vs the FIMG 3DSE used in older Samsung devices.
[Nook Color General] Jaostar:
Ok, I guess I'm wrong... I thought it was for the newer PowerVR SGX driven ones...
[Nook Color General] dmbyte:
Check In

Hey Deeper Blue, thought we should check in and see if there is anything we can do to help at this point?
[Nook Color General] cirehawk:
I'm new to the NC (but not to rooting... I rooted my HTC Hero and now my EVO) so bear with me. What is the SGX, DSP, and HW overlay that you reference?
[Nook Color General] dalingrin:
By SGX I mean the GPU which would be used for instance for 3D games and UI compositing.

The DSP is a co-processor designed to accelerate decoding and encoding of video and images.

The HW overlay is a mechanism to transfer the decoded video from the DSP directly to the SGX and then out to the display. Thereby bypassing any work required by the CPU.
[Nook Color General] cirehawk:
lol Just what it sounds like. I thought maybe it was some overlay to CM7 which changed the appearance.
[Nook Color General] Link3737:
Just bumping to ask if there's been any updates on the redraw issues
[Nook Color General] bot2600:
I wonder if we could pull off something similar to the Chainfire3D driver wrapper, wrap the calls and translate them to something more manageable by the clunky old driver.

I would be willing to work on it, but I won't have any available bandwidth for some time, work is kind of crazy right now.
[Nook Color General] nemir:
http://www.androidpolice.com/2011/0...-day-one-7-tablet-support-bug-fixes-and-more/
[Nook Color General] Divine_Madcat:
Still not built for our chipset, do it is really unlucky to do anything more for us....sorry
[Nook Color General] I Am Marino:
It would seem like they are purposely trying to keep HC off older devices, I can't blame them though.
[Nook Color General] iDidItAll4theNookie:
I can. I would think that Google would want to keep people interested in the platform. As it is now, Apple does a much better job of keeping more devices up to date. As far as I know, only 3G iPhones are DQed from the most current iOS, and that is because of hardware limitations. Google seems fine with letting carriers decide, resulting in out of date phones susceptible to unpatched issues. Google should want us moving along, so long as our hardware passes the test. That way people develop for today's platform, NOT 1.6, 2.1, 3.1 etc. This carrier limitation doesn't make me want to upgrade phones, it makes me consider switching platforms because perfectly good hardware might never get updated software.
[Nook Color General] SCrid2000:
That would be a more valid statement if Google was the one selling the devices ;)

I can see HTC or Motorola wanting to limit the software to newer hardware (although IDidItForTheNookie pretty adequately addressed that one) but Google doesn't gain anything from limiting devices. Unless I'm wildly mistaken.
[Nook Color General] I Am Marino:
I meant to add that they want people to buy the legit HC tablets, not just port them to older devices.

Still rocking the Incredible with the XDA Premium App.
[Nook Color General] arrjaytea:
So... I think it's fair to say the status of Honeycomb on the NC is "Dead in the Water."

Was a nice dream while it lasted, oh well.
[Nook Color General] chisleu:
More like "Waiting on the source to drop with ICS" (sometime Soon(tm)).
[Nook Color General] Divine_Madcat:
Bingo..

TO be fair, i hope people didn't expect the HC builds to be more than tech demos. Despite all the work devs can do, there is still a limit, and we need source to fix all the bugs. As it is, DB has done AMAZING work on what we had, and should show how well a real HC/ICS build will run.. :)
[Nook Color General] MrPib:
Except that that's "Android 4.0 ICS on the Nook Color." Agreed that HC on it is dead.

And so much for the excuse that 3.0's source was too ugly to release -- they're up to 3.2, and I don't buy that Google couldn't clean it up by now.
[Nook Color General] chisleu:
Yeah. I dig the HC builds, but they really are just a toy until source drops. I'm excited to see 3.x on our tablet, but honestly by the time that happens I'll be on a 10" 3.x commercial tablet (one with GPS and a freaking camera) or a 10-12" windows 7 tablet (waiting for windows 8, which looks boss for tablets.)

ICS is 2.4.

OMG! They increased it another .1 version number and did just about nothing except adding integrated support for 7" tablets and support for 1 processor. OMG. They spent millions on that .1! It's all a big conspiracy!!!! Buy stock in Google!!! they are finally going to make a profit!!!!

owait.

Maybe we should just take the people at their word when they have no reason to lie. Why drop source when you are afraid of remote exploits? Many manufacturers won't update their devices, so they need to fix the bugs in the code before it drops so it's not glaring and turns a bunch of real world devices into mobile botnet zombies.
[Nook Color General] iDidItAll4theNookie:
Do you mean a front facing camera for chats? Because the rear facing one might not see a bunch of use, since a 10" device isn't exactly the best form factor for point and shoot. Sure, you could use it, but it's not going to be your first choice.
[Nook Color General] riceboyler:
Seriously though, rather than bicker about whether it will or won't ever drop, can we just keep playing with the bits that ARE available? I know I'm probably in the minority here, but I really don't mind things not being perfect on a Nook Color running an OS that was never intended for it. I just enjoy the challenge of finding ways to make things work better, and I personally MUCH prefer the 3.x interface on a 7" tablet to the phone based 2.x interface. Yes, CM7 with Tablet Tweaks makes it much more bearable, but 3.x is FAR more usable on a larger screen.

So, would anybody be willing to just put a 3.1 (or 3.2) build out there that they know isn't perfect, just so schmucks like me who don't have the time to go rebuild the SDK build can play with it and see what it can and can't do? Thanks!
[Nook Color General] dgozalie:
honeycomb 3.2

yup, i agree.. just release it and let us flash it just for the fun of it... been a long time i haven't seen any release that make me exciting with nook.. remember when they first release honeycomb in february ? that make us feel like "whoa, holy cow that's so cool! "

Donny
[Nook Color General] MrPib:
Well, nobody knows, unless I missed an official announcement. I've also heard that 2.4 will be a newer Gingerbread (like 2.0 and 2.1 were both Eclair).

That's entirely possible. But it's also possible that their "partners" who have full access to the 3.0 & 3.1 (and 3.2 now) convinced Google to sit on the code to give them a competitive advantage over the cheap-o tablets. And there are other plausible theories for the initial delay and then cancellation of a 3.x ASOP drop. So there are several possible reasons that Google has to lie about this.

I'd like to note that HC 3.1 on a Nook Color is very cool. Love the new widgets. It'll be a happy day when we'll be able to get the HC UI with CM7-like stability and richness.
[Nook Color General] DigitalMD:
Looks like everyone is on vacation or they took advantage of AT&Ts $199 Samsung Galaxy Tab deal and are too busy. LOL
[Nook Color General] Divine_Madcat:
That, or the people who have been trying this simply have hit a road block, and cannot do much more without the source. Frankly people, i think you need to step back, and be amazed at just how much DB was able to reverse engineer from compiled code to make something work, and that at some point a limit will hit where you cannot fix anything more...
[Nook Color General] DigitalMD:
You are correct. I am a very experienced software developer and I know they have done a great job considering there is no soruce code. My comment about vacation was a general comment about the slow traffic in the entire forum.

Unfortunately I expect things to get worse rather than better for the entire Android / Smart device community with Google beginning to put a strangle hold on the source code and the big cell boys throttling or tier pricing data. I expect a general slow down in progress while everyone tries to make a buck.
[Nook Color General] SCrid2000:
That'll depend on what Goog does with the source code for ICS.

If they lock it down, then yeah we're boned.
[Nook Color General] newellj79:
Actually ICS is 4.0. And the 7" optimization will be in 3.2.
[Nook Color General] dvdivx:
I'm doubting they will release the code. It's already on 3.1. Ice Cream can't be that far off. Seems like they just used the open source community until it became popular if they don't release it soon.
[Nook Color General] wakeboarder8156:
played with galaxy tab 10.1 and it lagged running HC 10.1 which i thought was pathetic if you ask me and the size is terrible.

Keep working DB who knows maybe you'll get a break through!!! the size is so perfect on the NC for 3.1
[Nook Color General] newellj79:
They have been quoted as saying the source for ics will b released. "Used the open source community", pretty harsh. How do u figure?
[Nook Color General] joshnichols189:
This
[Nook Color General] E_man5112:
I'm betting ICS is 3.3. It's not a major step up from 3.2, it's mostly about bringing honeycomb everywhere, or it sounds like it. If they call it 3.3, that would indicate that it's not a major step up for anything but devices running 2.x.

Why would they release a new major version number 9 months after the last one?
[Nook Color General] joenathane:
Let's not over version numbers, in and of themselves they are meaningless.
[Nook Color General] chisleu:
I've heard it called 2.4 repeatedly, but no it does not have a version number attached to it yet.

Also I did say 3.3 had 7" tablet support, and other than that, they included support for a new processor. That's about it.

It's not like they spent 100000 man hours on that minor release, and they are working on ICS and the source for 3.x as fast as possible, I'm sure.

THEY HAVE NO REASON TO DELAY OR BULL**** US ON THIS...
[Nook Color General] DigitalMD:
Sure they have a reason to delay and BS. Money.... Google makes no money off releasing the source code to the public. They make money just like their partners Samsung and Verizon do, by selling new stuff. Google gets a license fee for every new phone or tablet. They really have no great benefit from you making your old tablet better, especially if you can make it better than the new tablet AT&T or anyone wants you to buy. If you thiink the mod community is so important to Goggle that they wouldn't thumb their nose at us then just take a look at the Apple business model and Apple sales and net worth.
[Nook Color General] newellj79:
Golly, u make it sound like they owe u personally. This has gone far off topic though, I wont post again. I just felt argumentative.
[Nook Color General] DigitalMD:
Oh no, don't get me wrong, I'm not arguing with you. Having been a SW developer for 35 years now I've worked for a variety of corporate and government interest and the customer (post purchase) and the "rogue" community are not at the top of the list things you worry about. Nothing malicious about that, its just business. Just wanted to point that this IS business for Google and the companies that sell devices.
[Nook Color General] iDidItAll4theNookie:
I still contend that its in their best interest to get people up to date. Get people on board with the new, so we get good app support for tablets. It seems very few apps are tablet friendly, and the mish mosh support doesn't incent developers to go that way. Google needs to convince average users that android can run with iOS and Win8. Right now I question it will align sufficiently before Apple and MS leapfrog them.
[Nook Color General] ta2025:
what planet are you on???? Google does NOT get a license fee or royalty from Android period. nada, zip. They are only guaranteed a distribution channel for apps, books and music ... and of course occasional advertising.
[Nook Color General] joenathane:
Google charges companies for access to gapps(Market, Gmail, etc...), but you are correct in that Google doesn't only just make money from these licenses fees.