Related
with all the new honeycomb roms coming out for other phones (Nexus 1, Dinc, Evo) is there anyway to bring it to milestone and if is possible can someone do it?
/nothing here
I'm fairly certain that since 3.0 is a tablet OS, phones with ports of the new firmware are having severe problems (ex. can't make phone calls, landscape doesn't display properly, touch screen doesn't respond as expected, etc.)
Besides, the community is still working on getting 2.3.2 stable enough for daily use.
thenotdone said:
I'm fairly certain that since 3.0 is a tablet OS, phones with ports of the new firmware are having severe problems (ex. can't make phone calls, landscape doesn't display properly, touch screen doesn't respond as expected, etc.)
Besides, the community is still working on getting 2.3.2 stable enough for daily use.
Click to expand...
Click to collapse
2.3 is fairly stable as of this moment, and I too would LOVE a honeycomb port to our beloved milestones
The honeycomb roms are pretty much useless at the moment, what works in them is... pretty much nothing. I would wait for 2.4 first, which will implement some of the important honeycomb features to smartphones, and then try porting honecomb apps. Maybe high-end smartphones will be able to run honeycomb when the ports will be better, but I don't think our Milestones with 256mb ram will even handle it.
THX for the answer but I have another question
is honeycomb hardware accelerated?
if it is shouldn't it run better on our milestone than on the Nexus 1 because of the GPU??
i still believe that the locked bootloader on Milestone will prevent anything that has a kernel that is TOO different from the Froyo-Kernel (i.e. with new features/procedures baked right into the kernel itself instead of Apps and Modules) will not be ported properly to our phones.
Gingerbread seems to be an exception since many people that cook ROMs said that it´s okay to use the latest leaked Kernel from 2.2 because it is not THAT much different to 2.3´s kernel.
I doubt that 2.4 or even 3.0 ´s kernels will still be similar enough to "fake" Honeycomb or Ice Cream Sandwich on a Milestone just like they faked Gingerbread (which is surprisingly good though!)
I haven't tried any of them yet, but it seems 2.2 or 2.3 or 3.0 have issues or are rough around the edges. It's understandable with honeycomb, but I thought by now there might have been a solid, stable 2.2 or 2.3.
Not complaining, but just thought something would be better than the stock 2.1 by this point. I was hoping for a speed increase with 2.2+ as there are some android git optimizations that 2.1 lacks, but yet I read that 2.1 for nc is still the most responsive.
Many people have reported much better bechmark scores with 2.2 and 2.3, and overall the feeling from those who run 2.2 or 2.3 is that they are more snappy than the stock 2.1. So far as being faster, the custom builds are probably generally better.
However, in terms of stability and compatibility it is my humble opinion that the stock 2.1 is still the winner. The CM7 build of 2.3 is getting pretty close, but still lacks some pretty important features. They will get there eventually...probably pretty soon....but I actually use my device quite heavily (at home and for work) and don't want to have to deal with 'minor' issues on a daily basis. I think that the Froyo build is going to fall out of favor - the CM7 build is better, more updated, and much more supported by the CM7 team with nightly builds. I am not sure about Honeycomb...haven't heard any real updates there in a while.
I am waiting for most of the wrinkles to get worked out for the CM7 version of 2.3. They do great work and if past performance is any indication once they get a solid and stable build it will be hard to beat. For now, my overclocked version of 2.1 does everything I want, is extremely stable, has very few software compatibility problems, and is certainly fast enough.
Thanks for the reply. You say the froyo build is probably going to fall out of favour over the cm7 build. Isn't the cm7 build based on froyo?
CM7 build is based on Gingerbread.
CM7 is based on 2.3 which is Gingerbread (Froyo is 2.2)
Confusingly, the upcoming 2.4 is also Gingerbread (http://en.wikipedia.org/wiki/Android_version_history)
EDIT: What he said! ^
As of this time, for day to day stable use, stock rooted. That's my opinion. Too many quirks and resets and "can't boot again" and other misc stuff that seems to randomly happen on the rest.
That'll change eventually, hopefully soonish, I would really love me some solid Froyo.
xdajunkman said:
I think that the Froyo build is going to fall out of favor - the CM7 build is better, more updated, and much more supported by the CM7 team with nightly builds.
Click to expand...
Click to collapse
But right now the Froyo build is where its at. CM7 lacks working Youtube among other things. With the current Froyo build you get speed, working Youtube, and many working apps.
Stock rooted has no Flash correct? I think I'll be waiting until CM7 is finalized before I start rooting anything.
poofyhairguy said:
But right now the Froyo build is where its at. CM7 lacks working Youtube among other things. With the current Froyo build you get speed, working Youtube, and many working apps.
Click to expand...
Click to collapse
I have plenty of speed on 2.1 overclocked at 1.1ghz, my YouTube works just fine (the app that is), and I have yet to find an app I want that doesn't work that would work on Froyo.
Yes...no Flash...but from what I have heard the Flash on Froyo is far from perfect...a bit choppy at best. Actually, no Flash is not quite correct...there is an older version of Flash that runs on 2.1 (Flash 9.something)...so you can veiw some older Flash content on the stock Eclair.
To each their own...
Can't fine that damn grail ANYWHERE
xdajunkman said:
Many people have reported much better bechmark scores with 2.2 and 2.3, and overall the feeling from those who run 2.2 or 2.3 is that they are more snappy than the stock 2.1.
Click to expand...
Click to collapse
It amazes me that people say this. Not saying they are wrong, I just wonder what magic nooks they are using that I don't have.
I've tried two different cards (a class 4 and a class 10, which really is class 10 fast) on two different nooks (mine and my wife's) and almost a dozen different install attempts of 0.6.7. and 0.6.8 and they have all been less "snappy".
It took me quite awhile to even get decent wifi speeds, and I still don't know what I did differently to get it right on the last install (different cards, different nooks, different wifi routers, clear-market-caching and clear-framework-data-ing till I'm blue in the face didn't do it).
I get back on my rooted BN1.1 eclair and breath a sigh of relief at the improved responsiveness and usability. Does anyone know what the secret sauce is to get froyo to REALLY feel better?
That said, I'm more than happy with the 2.1 nook; it's a great tablet and loads of fun. The dev community is fantastic and I've had a ball with all of the experimentation. Keep it up!
xdajunkman said:
I have plenty of speed on 2.1 overclocked at 1.1ghz, my YouTube works just fine (the app that is), and I have yet to find an app I want that doesn't work that would work on Froyo.
Yes...no Flash...but from what I have heard the Flash on Froyo is far from perfect...a bit choppy at best. Actually, no Flash is not quite correct...there is an older version of Flash that runs on 2.1 (Flash 9.something)...so you can veiw some older Flash content on the stock Eclair.
To each their own...
Click to expand...
Click to collapse
Can I ask whether a 10-min youtube playback is choppy in your nc? Cause mine is choppy sometimes...
I tried nookie froyo and it was really slow. Stock rom is much faster and reliable. I've heard honeycomb runs much better than froyo. I've seen videos and it looks good. The only think i can complain about stock rom is the lack of flash player
I've tried stock rooted, sdcard froyo, and emmc froyo, and I've run into minor issues/flaws with all of them, but the current emmc froyo (for me, at least) has the least amount of problems and the speed over slow eclair and my class 4 sdcard made it worth flashing. It's currently my daily driver.
If/when official CM7 comes out with, I'll probably give it a whirl, but I'm happy with my froyo build right now.
Maybe it'll bite me eventually... But i just put froyo 2.2 on my nook, and it runs so much better off the internal memory
wintwelve said:
Can I ask whether a 10-min youtube playback is choppy in your nc? Cause mine is choppy sometimes...
Click to expand...
Click to collapse
I don't use YouTube much...but when I have used it I do not notice any problems. I am sure that it depends on the quality of the video, but I have played cartoon episodes that are several minutes long without any delays or playback problems.
swoozle said:
It amazes me that people say this. Not saying they are wrong, I just wonder what magic nooks they are using that I don't have.
I've tried two different cards (a class 4 and a class 10, which really is class 10 fast) on two different nooks (mine and my wife's) and almost a dozen different install attempts of 0.6.7. and 0.6.8 and they have all been less "snappy".
It took me quite awhile to even get decent wifi speeds, and I still don't know what I did differently to get it right on the last install (different cards, different nooks, different wifi routers, clear-market-caching and clear-framework-data-ing till I'm blue in the face didn't do it).
I get back on my rooted BN1.1 eclair and breath a sigh of relief at the improved responsiveness and usability. Does anyone know what the secret sauce is to get froyo to REALLY feel better?
That said, I'm more than happy with the 2.1 nook; it's a great tablet and loads of fun. The dev community is fantastic and I've had a ball with all of the experimentation. Keep it up!
Click to expand...
Click to collapse
I agree on all accounts. I also have played with Froyo and Honeycomb on SD and have not personally seen the speed improvements others have reported. Perhaps it is better if installed to internal memory.
Definitely better installed to emmc. Been through Stock rooted, nookie 0.6.8, and HC. HC is sweet, softkeys and interface are great. but lack of key apps in the market is a bummer. nookie 0.6.8 ver 3 has been my everyday driver, no complaints over here.
I'm using cm7, nightly 7 and I like it better than stock. It does feel a bit snappier (but honestly I never had any issues with speed on rooted 2.1 so it could be in my head.) I know there's no DSP, but I don't plan on watching movies any time soon so that's fine for me. I like the UI alot...I like having built in copy/paste, I like having flash, and I like not having to worry about BN pushing out updates that could screw up my root. I'm only a few days into having used CM7, but as of now I'm really happy with my choice.
I've been running Honeycomb v4 2ed on a development Nook for awhile. I think it shows great potential! But the Nook I take with me is 1.1.0 with a 1.1ghz kernel. Fast, stable & very reliable.
I have to say. I'm really looking forward to seeing the Honeycomb AOSP drop! This thing is going to be Great.
I'm really enjoying stock 1.1 rooted. It has everything I could ask for in a value tablet and more. (Browsing, video, music, apps) The stability has been great...knock on wood. I was hell bent on buying an iPad before I purchased the nook color. I dont think I'll need an ipad, or anything else for that matter anymore.
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
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)
Hey folks. I have a Galaxy Captivate from Rogers, which currently runs on Firefly 3.0. I was impressed with how Firefly improved a lot of the machine's function as well as the appearance options.
My only distaste in Firefly comes from seeing all the new options available in ICS & Jellybean. I would like to experience some of these new features for myself.
I know that the Captivate is a fairly dated device, but my understanding is that the newer releases actually speed things up. . . I'm wondering if I should be upgrading or if I'm as shiny as I can get with FF 3.0
Thanks for any suggestions.
JavaMac said:
Hey folks. I have a Galaxy Captivate from Rogers, which currently runs on Firefly 3.0. I was impressed with how Firefly improved a lot of the machine's function as well as the appearance options.
My only distaste in Firefly comes from seeing all the new options available in ICS & Jellybean. I would like to experience some of these new features for myself.
I know that the Captivate is a fairly dated device, but my understanding is that the newer releases actually speed things up. . . I'm wondering if I should be upgrading or if I'm as shiny as I can get with FF 3.0
Thanks for any suggestions.
Click to expand...
Click to collapse
CM9 RC2 just got released, and it is pretty much stable. The rom runs fast and you can OC it to 1.2 Ghz stable.