Let me preface this by saying that I have nothing but the utmost respect for the dev community (NC and otherwise) and I really don't mean to step on any toes with this. I'm fairly new at all this and I've got some questions.
Alright, so as we've all heard by now, Google (whether their reasons are benevolent or not) are withholding the AOSP release of Honeycomb and that kind of rains on everyone's nook color parade. We've got a mostly working port of HC that kind of sags in the performance area. Its almost been enough to make me flash Gingerbread but there are a few things - namely the browser, email app, soft keys and notification system - that I'd miss. The new + screen is nice, but I've been using launcher pro as it runs seemingly faster than the stock launcher, so I'm already missing out on that.
Now, from what I understand, and feel free to correct me if I'm wrong, deeperblue's HC port uses parts of Gingerbread to make everything all hunky dory.
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in? i.e. Take HC's notification system replace GB's phone-style notification pane. Make it mostly gingerbread with some tablet friendly nip/tucks here and there.
I realize there are things like softkeys and the bottom taskbar mod, but HC's handling of the android buttons and the new notification system is just so appealing. Its making the choice of which rom to run unduly difficult. And while I can't cook a rom, I'm hoping someone who can sees this and runs with it, if it is feasible, that is.
Truthfully... It's up in the air like everything else, unless a DEV directly comes out of the shadows and saids, hey i'm going to do it... Then we just won't know. Honestly, I'm sad that we won't see HC right around the corner, but CM7 is pretty awesome. And the Xoom is scheduled to drop down to $599 (Wifi only) today, making it a lot more competitive than the 3g.
That's not to say that I personally have $599 to drop and go buy a new tablet, but it does mean that you'll probably see them on craigslist or ebay in a few months for a bit cheaper. =\
The honey comb preview is awsome but to many apps don't work.
Tyfighter said:
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in?
Click to expand...
Click to collapse
That was kinda the plan. CM7 development was going in a way that all the improvements (Bluetooth, partially working DSP, an accelerated interface) were going to be directly ported to Honeycomb once the source released. But without the source, that can't happen.
Basically Google has completely screwed any Nook Color fans wanting Honeycomb.
The only improvement that can be made is that a ROM could be made from the final SDK. That would be just as laggy, and will lack new features (Bluetooth, DSP, etc.), but it would be able to use Android tablet apps.
From the conversation about Google's move on the net, many are saying there won't be a Honeycomb source at all, and the next source dump will come with Ice Cream months from now.
So Honeycomb fans have a choice- either try out the CM7 modification that you talked about to make CM7 more Honeycomb-like, or start saving up for that Xoom...
[email protected] said:
The honey comb preview is awsome but to many apps don't work.
Click to expand...
Click to collapse
what apps dont work? most of the major ones have worked for me so far...
im finding that the hc rom is very usable for a daily driver...although bluetooth and dsp support would be very nice...
nolook said:
what apps dont work? most of the major ones have worked for me so far...
Click to expand...
Click to collapse
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
poofyhairguy said:
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
Click to expand...
Click to collapse
Thank you for your informative reply.
It seems now that my best bet is going to be t see what the cm7 guys cook up. Hopefully this aosp business will spark some of the innovation that the android community is known for. I'd love to help, but its not exactly my forte
With regards to what apps aren't working, my marketplace only seems to intall apps when the stars are right. I often have to attempt an install upwards of five times to have it succeed, if it even does. Otherwise i get insufficient storage errors or indeterminate error 18
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
I got the nc cause i had thought it had the best $/performance of any android based tablet. For half the price of others, it had great screen, and forgetting bt, etc., nice hw specs. With hc, it would be fantastic!
How else to counter ipads if not to get hc on as many tablets as possible?
I wonder if the fact that the playbook is running our apps has anything to do with it. If so, I don't mind anything that makes it rough for RIM.
Sent from my Desire HD using XDA App
jbinbi said:
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
Click to expand...
Click to collapse
It is open source and it WILL be released however at this time they don't think it's ready for final release (I've heard of various tweaks they need to make in the xoom) and are working those out prior to releasing it to devs
Related
Here is a thread that will be all about speculation..
I saw the honeycomb and it was smoking!!! What are the chances that the guys here will get it on the nook? And if yes, how it will run? Given that it only have a 800Mhz processor (1Ghz overclocked).
Looking forward for any opinions
I hope so, but that's a good bit away. Honeycomb uses on screen buttons, so our hardware button deficiencies would go away, if it were possible.
IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.
10equals2 said:
IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.
Click to expand...
Click to collapse
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...
paleh0rse said:
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...
Click to expand...
Click to collapse
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..
spikey911 said:
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..
Click to expand...
Click to collapse
why not......
elcape said:
why not......
Click to expand...
Click to collapse
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.
Is it bringing something amazing to the table? Haven't even bothered looking at honey just because the GUI stuff everyone likes looks ugly as hell.
Nook color was my first android device so I prefer the simple notification bar at the bottom, as well as using a taskmanager to kill/switch apps.
sent from a Nook Color using xda-app
spikey911 said:
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.
Click to expand...
Click to collapse
I hope you realize that the fine folks at Cyanogen are already working on a NC version of CyanogenMOD version 7 -- which is a Gingerbread (2.3) rom. Some of their best devs are on it, and they've even gotten it to boot already!
So, don't be surprised when you see 2.3 sooner, rather than later...
Sent from my Nooted friend.
For those brave souls using Honeycomb daily on their Nooks, what kind of tweaks are you doing to help with performance/compatibility?
Thanks in advance!
Bot
I'd also like to know if there are tweaks you can do to makc HC stable/perfered for the nook, anyone using it full time?
If you already have it installed on the eMMC with an overclocked kernel you have done all you can do.
Honeycomb development pretty much died the day Google said that their was going to be no source code release. We might never see a "stable" Honeycomb for the Nook Color.
With that said, many people has been working on making Froyo and CM7 better in Honeycomb's absence. I personally think the Tablet Tweaks CM7 version is more useable than even the Honeycomb on a Xoom I tried (at least our SD card slots work), and for people who are DYING for Honeycomb there is the NookieComb which is Froyo hacked to act like Honeycomb.
Take a look at the development forum for more information.
you can turn off all transition animations to get a bit of a speed boost...also opera mobile is much faster (but not as nice) as the HC browser
im running it off emmc and its actually very stable for web/reading...video isnt great yet and there is a bit of UI lag but IMO very usable...
I thought Google said they just delayed the 3.0 release. I read into that that 3.0 is a disaster right now and they are still trying to make it a clean product. I think Ipad is scaring them and they are moving into overdrive at Google trying to get ahead (meaning 3.0 came out before it was really ready).
I totally agree. Google doesn't want to let a half baked product out the door when you know the ipad 2 will be stellar.
Sent from my NookColor using Tapatalk
swaaye said:
I thought Google said they just delayed the 3.0 release.
Click to expand...
Click to collapse
The head developer of Android has said that AOSP won't be released until the phone features are merged, which means no code until Ice Cream.
So if the original ETA for Ice Cream was summer 2011, then I guess we see nothing until at least Christmas?
Meaning that Android tablets have been dealt a death blow for <b>another</b> year?
I am so glad for the independent developers working so hard at XDA.
xdabr said:
So if the original ETA for Ice Cream was summer 2011, then I guess we see nothing until at least Christmas?
Meaning that Android tablets have been dealt a death blow for <b>another</b> year?
I am so glad for the independent developers working so hard at XDA.
Click to expand...
Click to collapse
i could be wrong but am pretty sure something will get 'leaked' before then....
I don't think Google minds -too- much that they are slowing down tablet development anyway. They've made it clear they want the "final solution" for tablets to be ChromeOS. Android for tablets is just a stop-gap measure.
P
jahfry said:
I don't think Google minds -too- much that they are slowing down tablet development anyway. They've made it clear they want the "final solution" for tablets to be ChromeOS. Android for tablets is just a stop-gap measure.
Click to expand...
Click to collapse
When did google say this?
Sent from my always stock, EC05 Epic 4G
Is there any advantage to the overclock kernel? I have the regular kernel running at 1100 with CPU Tuner (unless the overclock kernel comes in v2 by default)
Is Nook Color in Limbo, or are we at the cusp of something new?
I hope development for the Nook Color has not stagnated. Are we waiting for the new kernel or is there just nothing new on the horizon?
I am just wondering because I have been watching and waiting and it appears development has slowed up for the time being. Not implying anything, just looking to see if something new and wonderful is on the horizon???
I was so looking forward to Honeycomb and it seems Google has pulled the rug out from under us in some back room deal.
Hopeful
migrax
What are you talking about? In limbo? Bluetooth, recent video fixes, new overclocked kernels, work on the next coming edition of kernel to prevent SOD. Man, you must be out of the loop or really impatient.
The Release Candidate of CM7 came out recently. That means a final release is eminent. That final release should include all these awesome tablet tweaks:
http://forum.xda-developers.com/showthread.php?t=1002000
I don't know why you say development is slowing down. I have been flashing a new ROM everyday thanks to mad-murdock!
Im sorry, but what ARE you talking about? In the last month, both hardware accelleration for video and bluetooth were turned on. CM7 has reached release candidate stage, and our devs have said that work is progressing on both a newer kernel version, as well as fixes to the few remaining bugs. Maybe you should actually read some of those nifty development threads around here...
If i am coming off as rude... perhaps that is the intent. There are so many needless threads like this, where some reading and critcal thinking could answer alot of questions. I mean.. developent stopped? As it is, things are ramping up, and a quick read of the forum would show that. Add in the constant misleading talk about what the nook can and can't do, and it is rather frustrating. So yeah, I am venting, but i think it is well deserved.
On the contrary, I think that things are happening real fast. CM7 is heading for a stable release, Mad Murdock's tablet tweaks are a real innovation, as are brianf21's froyo status bar improvements, and real progress is being made in the kernel area - blue tooth, hardware acceleration, etc.
What more can we ask for?
only HC is at a minor hump, the rest are busy, and b&n update is dropping soon. you crazy!
had to chime in to see what the op is smoking...
cm7: hardware video acceleration, tablet tweaks, bluetooth, kernel mods.
froyo: status bar tweaks, 'nookie-comb' looks nice, new official rom coming soon
honeycomb: who cares. google screwed that one up so we wait for IC.
Honestly, right now I'm in limbo about WHICH custom, daily updated, feature rich build to use !
Rooted Stock is good enough for what I do, but then a few games didn't work... so i went to froyo... then tried CM7... then a custom froyo, then another CM7... (and a few hardlocks and flash to stocks in between)..
At this point i just want a "1.0" release of CM7, or for HC to become available... although i'm sure the weeks following HC will be daily build after daily build.
p.s. kinda jealous about the $300 Tegra2 tablet floating around.
Divine_Madcat said:
Im sorry, but what ARE you talking about? In the last month, both hardware accelleration for video and bluetooth were turned on. CM7 has reached release candidate stage, and our devs have said that work is progressing on both a newer kernel version, as well as fixes to the few remaining bugs. Maybe you should actually read some of those nifty development threads around here...
If i am coming off as rude... perhaps that is the intent. There are so many needless threads like this, where some reading and critcal thinking could answer alot of questions. I mean.. developent stopped? As it is, things are ramping up, and a quick read of the forum would show that. Add in the constant misleading talk about what the nook can and can't do, and it is rather frustrating. So yeah, I am venting, but i think it is well deserved.
Click to expand...
Click to collapse
What madcat said
Sent via Cyanogenmod7 Encore RC4 n.35/Tapatalk Pro
roflmao
You want limbo?
My new Droid 2 Global has just one rom which works with global sim capability- flashed it shortly after I got it and no updates since.
Another crew did get D2 roms working on the D2G but no sim card use.
Nothing for months now...
My original DROID has more development work going on than THAT!
The NC has been fairly exciting as far as dev work since Christmas and the last month has been incredible...
I even saw a post fairly recently that leads me to think some folks are working on USB host.... Crossing my fingers on that one.
The last two weeks we have even had a guy working on tweaks for tablets that pretty much makes Honeycomb's issues irrelevant as far as I am concerned.
I'd say that is pretty good.
Sorry, not the intended result.
I guess I am waiting for BN to come out with Android 2.2, I wasn't denegrating all the hard work that has gone on here. A couple of developments have kinda skewed my perceptions, one of which is Honeycomb source being yanked, and the other is of course the expected update from BN not materializing yet... I guess I am getting a little impatient. Sorry for the misunderstanding.
I am using Nookie Froyo at the moment and it is working, however I really liked Stock 1.1.0. but with the NC using Android 2.1 I can't do some things I'd like to do. It just seems to me that BN is dragging their feet. Hence my concerns.
As I understood your original post you are waiting for the official 2.2, not a developer build.
The last rumor that I heard (from these forums) was that it was to go out this month. (but that was a rumor)
Not really sure why people are flaming the OP so hard. Besides CM7 nook color development has practically stopped dead in its tracks. HC is stuck, froyo has been dead for a while.
So i can see how it seems that way unless you watch CM7 development it does look very dead. CM7 is usable enough that froyo is not really relevant and with googles decision to not open source HC means its pretty much dead in the water.
Actually with Tablet Tweaks, CM7 is still seeing updates almost every day. And there's I believe an Experimental Kernel hiding in the CM7 User Thread which seems to have cleaned up the Battery Life on CM7.
As far as the official 2.2 update... Who needs it when you've got CM7? I mean, even if it does come out and we nooter it, it's still not going to do everything that CM7's custom rom can.
HoneyComb, yeah it sucks that it's not coming out right away. And I was pretty upset myself, but with tablets coming out (with similar prices to the nook) that have HC already... I can wait.
notinterested said:
Not really sure why people are flaming the OP so hard. Besides CM7 nook color development has practically stopped dead in its tracks. HC is stuck, froyo has been dead for a while.
So i can see how it seems that way unless you watch CM7 development it does look very dead. CM7 is usable enough that froyo is not really relevant and with googles decision to not open source HC means its pretty much dead in the water.
Click to expand...
Click to collapse
Why waste any more time (right now) on anything BUT CM7? I mean, yes, Froyo and Eclair are dead in the water, but that is good; it just means all the devs are working on the best system we have. When HC source drops, i expect most work on CM7 to dry up, and again move to the better OS.
So yes, dev is on one OS right now, but my oh my, what sweet dev it is. If you call that stagnation, you are crazy..
I'm eager for the bn update just because I like to actually us my nook as an ereader rather than just a tablet. I'm a big fan of the mags and the kid books. Besides, I get my cm7 fix on my dinc.
Sent from my ADR6300 using Tapatalk
Gin1212 said:
Actually with Tablet Tweaks, CM7 is still seeing updates almost every day. And there's I believe an Experimental Kernel hiding in the CM7 User Thread which seems to have cleaned up the Battery Life on CM7.
As far as the official 2.2 update... Who needs it when you've got CM7? I mean, even if it does come out and we nooter it, it's still not going to do everything that CM7's custom rom can.
HoneyComb, yeah it sucks that it's not coming out right away. And I was pretty upset myself, but with tablets coming out (with similar prices to the nook) that have HC already... I can wait.
Click to expand...
Click to collapse
if you know of such a kernel can you link to it?
Also if stock goes to 2.2 and gives us all ability to play flash and the extr speed improvements of a JIT compiler ad can then be nootered and overclocked, why would one need CM7? This way you also get the ui from B&N which includes built in back and menu buttons. It also includes the full B&N experience for reading magazines subscriptions books......You los that on custom Roms.
So while I laud the Devs work, getting nook color to froyo might make much of their work unnecessary, unless it gives them a better platform to make the NC even better.
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Divine_Madcat said:
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Click to expand...
Click to collapse
I really hope someone manages to port over the slick reader app from stock to CM7.
I like reading on my nook but not at the cost of such horrible performance in everything else.
Divine_Madcat said:
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Click to expand...
Click to collapse
Bluetooth works awful at best.
Regular headset doesn't work and range is a foot.
So far most people have keyboard trouble. Seems ext. bluettoh gps seems to be the best bet. So for me a stock rom with all the current missing goodies fixed with nooter and o/c?
I'd be happy.
Outside of bluetooth, if you had fully supported 2.2 on your device so hardware accel video and flash worked perfectly and yet you still had the B&N experience when you wanted it for free instore reading and subscriptions .....what else would you really want?
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
It sucks but I feel our best bet is just to wait for source. There are a lot of honeycomb tablets slated for release over the next few months, I think once it becomes more widely available we'll see source.
Since we dont know when will be... all the time, effort, and trouble to get it fully working witout source - will be in vain once the source drop happens.
So unless the people involved don't care, cm7 is more than enough for now. We are lucky to even have that, my phone doesn't even have cm7 working for it.
My .2 anyways
Sent from my SCH-I500 using XDA App
The problem is, Google has stated they won't be releasing Honeycomb source until it's integrated with the phone branch. I personally doubt that we see real source until Ice Cream is out.
honeycomb source will never be released, google said so, we'll get Ice Cream Sandwich source which will be awesome on our nook's i'm sure
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
Any hope for USB host support with the port or once again not till source
Sent from my Vision using XDA Premium App
deeper-blue said:
Since many people asked what I was doing these days:
http://www.youtube.com/watch?v=RJ_k4kdsaMk
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
Click to expand...
Click to collapse
hey THANKS for posting up what you've done and this very cool video... that was just awesome to see how far someone has gotten to get 3.1 running WELL on the nook.
mad props.
Nice work rafael!
Sent from my NookColor using Tapatalk
can't really help you out, but I'd just like to cheer you on
+1 !
Keep up with the excelent work !!!
botossi said:
+1 !
Keep up with the excelent work !!!
Click to expand...
Click to collapse
luigi90210 said:
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
Click to expand...
Click to collapse
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.
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
arrjaytea said:
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
Click to expand...
Click to collapse
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.
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?
Sounds like patching the launcher will be the easiest route. This is why I love you DB ahhaha, your work is amazing.
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.
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.
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
Keep at it man, we appreciate the work.
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
I'm curious what anyone who has had experience with both thinks about switching from HCv4 to CM7. I've read some of the previous posts on the subject, but it looked like most replies were back in February, so now that we're at the end of 2011, any thoughts?
I've been using HCv4 for about as long as it has been out, and it runs very, very well in my opinion. But since development seems to have died, and now ICS is maybe going to make HC development DOA, until ICS comes to the Color Nook I was thinking of checking around for alternatives.
I've seen that CM7 seems to be very popular, so is it currently the most compatible and fully functional Android version that runs on the NC? Is it better all the way around now than HCv4? Have the video and audio problems been worked out, or are there other drawbacks? Any suggestions will be appreciated.
-JTT
jttraverse said:
I'm curious what anyone who has had experience with both thinks about switching from HCv4 to CM7. I've read some of the previous posts on the subject, but it looked like most replies were back in February, so now that we're at the end of 2011, any thoughts?
I've been using HCv4 for about as long as it has been out, and it runs very, very well in my opinion. But since development seems to have died, and now ICS is maybe going to make HC development DOA, until ICS comes to the Color Nook I was thinking of checking around for alternatives.
I've seen that CM7 seems to be very popular, so is it currently the most compatible and fully functional Android version that runs on the NC? Is it better all the way around now than HCv4? Have the video and audio problems been worked out, or are there other drawbacks? Any suggestions will be appreciated.
-JTT
Click to expand...
Click to collapse
CM7 is actually usable unlike HC. Yes basically all issues have been squashed. I suggest you switch ASAP. No point using dead, and incomplete software.
---------------------------------
Sent from my LG Optimus V using Tapatalk
The main reason that it has no report/response since Feb is 'cuz nobody else uses it (a little exaggeration) except you and some others, very minor. Did I love HC, heck yes, beautiful GUI, I'd tried both HCv4 and 2 others (forgot from who), honestly, beautiful, but that's about it.
Since Feb til now, when ICS is being developed, I'm surprise that here and there, still people asking about HC.
CM7 - Gingerbread (full support)
CM8 - Honeycomb (die before born)
CM9 - Ice Cream Sandwich (in labor)
As the author of one of the ports, it still baffles me that people are using the darn thing. It was designed as an experiment, and honestly never expected for real use (without the hc source). Any remning users ould go to cm7 post haste, and hang in there for cm9 to roll aound..
Divine_Madcat said:
As the author of one of the ports, it still baffles me that people are using the darn thing. It was designed as an experiment, and honestly never expected for real use (without the hc source). Any remning users ould go to cm7 post haste, and hang in there for cm9 to roll aound..
Click to expand...
Click to collapse
You know why? 'cuz the one you've made, I believe the entire HC image file, was so beauty, seeing the GUI, honestly I didn't want to go back to CM7 but like I said, that's about it.
Yeoouch..
Hmmm, I guess I feel chastised for still using the Honeycomb SDK hack on my color Nook, but honestly, it has worked very well. Though I'm not living and dying by what I can or can't do with my Nook, it's been plenty usable while waiting for a better, cleaner, faster version of something to come along. 99% of the apps I've tried have worked, and the few that haven't have not been missed enough to change to a different mod just for them. So I'll grit my teeth and just say thanks to anyone who contributed to the HCv4 version I've been using.
I may try CM7, if only because I like knowing what my options are, and because I may give the thing as a gift to my daughter, who won't want to mess with a kludged version of Honeycomb. It's the eReader apps and their functionality that matters most at the moment, and I don't think that will matter whether I'm on CM7 or HCv4.
eh, I wish ICS was already out...
-JTT