Related
http://www.engadget.com/2011/02/22/android-3-0-honeycomb-sdk-now-available-to-all-api-level-litera/
http://developer.android.com/sdk/android-3.0.html
Let the games begin! Time for a new Honeycomb release for NC?
http://forum.xda-developers.com/showthread.php?t=965108
Yippie!!!
Sent from James' HTC Evo 4G
I just saw this on google. Very exciting!
So does this mean we sshould be seeing some serious honeycomb roms coming our way?
SDK and AOSP are not the same thing
dont get too excited yet
Just like norazi said. An SDK ain't what is needed to port 3.0. Just wait till the Xoom gets out THEN soon afterwards....week or two....just a guess....... In the meantime, deeeeeeep breath....lol
ahhhh okokok
well. any step that is closer towards 3.0 all up in my face is fine by me.
has anybody heard anything about aosp honeycomb, cause the xoom's been out for about a week now and still no aosp honeycomb :/
I agree, I am highly anticipating this. The preview or whatever based on the SDK isn't working well for me.
Its almost like Motorola got an exclusive deal with HC for a while. I don't blame them- within a month a NC would be 80% as good as a Xoom at less than half the cost...
Honeycomb is incomplete. Xoom currently has an SD slot but HC can't use it yet. They said they're waiting on google for an update to turn that feature on. Then there is no flash support either yet its promised with a future update, probably around the time when the SD slot gets enabled.
So I'm betting thats the reason why the source hasn't been released yet, Its actually not done being developed and Xoom was rushed out the door before it was complete.
virual said:
Honeycomb is incomplete. Xoom currently has an SD slot but HC can't use it yet. They said they're waiting on google for an update to turn that feature on. Then there is no flash support either yet its promised with a future update, probably around the time when the SD slot gets enabled.
So I'm betting thats the reason why the source hasn't been released yet, Its actually not done being developed and Xoom was rushed out the door before it was complete.
Click to expand...
Click to collapse
The SD slot not being usable is almost certainly a driver issue; Motorola's job. Flash is an app, that's Adobe's job.
Google is probably making sure all their i's are dotted and t's crossed, especially in light of the litigation with Oracle over contents of Android source.
Has everybody noticed how this has slipped thru the cracks with all the distraction of Google I/O 2011 news?
Google I/O Google has said that the next version of Android, dubbed "Ice Cream Sandwich", will be open sourced "by the end of the year," and that it will not open source the current Android incarnation, the tablet-centric Honeycomb, before that time.
Source:
UU UU UU dot theregister.co.uk/2011/05/10/android_ice_cream_sandwich/
Andy Rubin has backtracked on making the Honeycomb source available until after it is no longer relevant (if even then). There is no promise any more of EVER getting the Honeycomb source, so it looks like the best we'll be able to do is SDK11 unless B&N updates stock to Honeycomb (don't hold your breath).
I wouldn't say Honeycomb will no longer be relevant after ICS. After all, ICS is a smart phone OS, whereas HC is designed for tablets. What I'm getting from this is that ICS is basically going to be the smartphone version of HC. Google has stated that they don't want people porting HC to smartphones. By delaying the release of source for HC until after ICS hits the shelves, Google is trying to forestall the translation of HC to phones by waiting to release HC code until it no longer makes sense to do so (beacuse there'll be no point in doing so).
dsf3g said:
I wouldn't say Honeycomb will no longer be relevant after ICS. After all, ICS is a smart phone OS, whereas HC is designed for tablets. What I'm getting from this is that ICS is basically going to be the smartphone version of HC. Google has stated that they don't want people porting HC to smartphones. By delaying the release of source for HC until after ICS hits the shelves, Google is trying to forestall the translation of HC to phones by waiting to release HC code until it no longer makes sense to do so (beacuse there'll be no point in doing so).
Click to expand...
Click to collapse
Actually, from the presentation, ICS is just as much for tablets, since the UI is supposed to scale based on the device.
However, they keep saying ICS for quarter 4, which is half a year away. Frankly, i am pissed that they yanked devs around for so long HOPING we might see the code, when in reality, i have no doubt they held it back solely on the request of Moto and others, to help maintain a monopoly on HC market..
Other media reports are characterizing the discussion as Rubin saying that they will never release the Honeycomb AOSP. Yet another reason to ignore the Xoom, et al. tablets if they're going to pull this bull****.
Brilliant plan -- release a closed buggy version, refuse the community to do de-bugging work for free and then hope that it will be magically fixed by merging with the OS that originally was thought to not be up to snuff.
Google thinks that they can "merge" Honeycomb back into Ice Cream Sandwich (after they "get it right").
What I want to know is, how is Andy Rubin justifying withholding the source of an "open source" OS? And what is to keep him from doing the same thing again next year with ICS?
There are more comments over in the developer thread on this subject. I started this one first, but I don't have enough posts to start one over there (grumble, grumble). I'm slowly getting closer to being able to post there though (grin).
One school of thought over there is that the Honeycomb AOSP is a hacked up kludge "not ready for primetime" and that's why Google doesn't want it out.
While that is very likely true and (and will probably continue to be true now that 3.1 is released), that is no justification for opposing "opening" the source.
Since I expect the kludges will be "grandfathered" throughout future releases, I don't expect to ever see HC AOSP. I could be wrong, but it really doesn't matter because ICS will be out by then and everybody will be wanting to port to it.
What I'm concerned with is the "promise" of ICS being released in a timely fashion. Mr. Rubin has made earlier "promises" that have later been rescinded. I don't think he EVER wanted HC released and was just trying to "buy time" until Google I/O 2011 so that he could take the heat off with the announcement of ICS.
I hope I'm wrong, but ... fool me once, shame on you. Fool me twice....
Divine_Madcat said:
However, they keep saying ICS for quarter 4, which is half a year away.
Click to expand...
Click to collapse
Fiscal, or calendar? Because fiscal Q4 is July-September.
zombieflanders said:
Fiscal, or calendar? Because fiscal Q4 is July-September.
Click to expand...
Click to collapse
Technically, i don't think they have said, but i have never seen any other Google release announcement refer to a fiscal quarter instead of the calendar. I would love for it to be fiscal, but that is a real pipe dream.
DM -
Tell them over in the other thread that Andy Rubin's quote was in a Q&A w/press after his keynote.
DiDGR8 said:
DM -
Tell them over in the other thread that Andy Rubin's quote was in a Q&A w/press after his keynote.
Click to expand...
Click to collapse
Consider it done.
Divine_Madcat said:
Consider it done.
Click to expand...
Click to collapse
Thanks (just one more post and I can get into Dev!!)
I have a cousin who works with B&N, and he says that they are rushing to get the 3.0 kernel on the NC to accompany their locked-down skin. He says that there are some incompatabiliies, but that they have made progress. What are your thoughts? Is he crazy? Are we ever going to get a proper ICS OTA?
If B&N drops 3.0 kernel source for the Nook Color, the devs here will be quite happy because the current old kernel is the major impediment to ICS on Nook Color.
You sure they aren't doing this just for the Nook Tablet?
3.x is honey comb, not ICS. They'll prolly skip that all-together.
gallahad2000 said:
3.x is honey comb, not ICS. They'll prolly skip that all-together.
Click to expand...
Click to collapse
Talking about the linux kernel.
It makes little sense to me for them to update the core Android OS and Linux kernel if their reader, custom apps, and the apps in their store work fine with Froyo. But if they're going to keep selling the NC as the budget media tablet model for a while longer then a more up-to-date Android version makes sense in avoiding any possible compatibility issues down the road that could prevent them from seamlessly bringing the latest and best versions of Android apps across to the B&N market. Their separate B&N market wouldn't be very sustainable or a good selling feature if they had to only offer older versions and/or ask developers to add backporting compatability fixes for a two year old version of Android. Then again, that's just a lot of speculating on my part
I don't have hope for that, in fact, I doubt it.
They just released v.1.4.1 and it still is Froyo, I don't think they implement ICS for NC.
I could actually see them doing this just so that it will be easier for devs to convert their already tablet friendly ICS apps for the BN market.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I would think they would like to keep the operating environment the same across units (if possible). This will cause less customer confusion/dissatisfaction and fewer support issues. Apple IOS is a good example of this IMO.
gmanvbva said:
I would think they would like to keep the operating environment the same across units (if possible). This will cause less customer confusion/dissatisfaction and fewer support issues. Apple IOS is a good example of this IMO.
Click to expand...
Click to collapse
Apple allows old devices to upgrade to newer iOS versions (my gf's 3g is running iOS 5). They just cripple the features they don't want those devices to have (siri, folders, etc). Apple's relative lack of issues comes from controlling the hardware (no powerVR, tegra, qualcomm incompatibilities, short driver list), OS (no carrier or manufacturer modifications) and app store (too many bugs and your app is gone).
I doubt B&N would drop the full functionality of ICS on their customers (especially when they've fenced them in from froyo). ICS would open the door to tablet-centric apps which would help them compete with Amazon. It will most definitely come to the Tablet but I wouldn't expect it to come to the Color (since they need to differentiate the models to justify the price difference).
Would be great if they did release it, but lets face the truth, its unlikely.
If you guys want ICS your best bet is buying dalingrin and / or fattire a beer.
Sent from my NookColor using Tapatalk
MrColdbird said:
Would be great if they did release it, but lets face the truth, its unlikely.
If you guys want ICS your best bet is buying dalingrin and / or fattire a beer.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Maybe true, but if this works it would certainly give dalingrin and fattire some help with the issues they're having, not to mention speed up the entire process.
Limvot said:
Maybe true, but if this works it would certainly give dalingrin and fattire some help with the issues they're having, not to mention speed up the entire process.
Click to expand...
Click to collapse
If what works? I'd love to have official ICS on my NC, but as others have said, they're still using a fluffy coating on Froyo. No GB and no HC means ICS is highly unlikely.
Now what would be very nice would be an updated kernel, as well as some direct contact with B&N techs about drivers for the chipset and other hardware. But I find that to be unlikely.
The newer Nook Tablet is based on Gingerbread, isn't it? Perhaps they're working on this first and foremost to crank out a third future device that supports APIs from ICS such as fragments. The updated code would then trickle down to Nook Tablet and possibly eventually NC.
Sent from my Nook Color!
zombieflanders said:
If what works? I'd love to have official ICS on my NC, but as others have said, they're still using a fluffy coating on Froyo. No GB and no HC means ICS is highly unlikely.
Now what would be very nice would be an updated kernel, as well as some direct contact with B&N techs about drivers for the chipset and other hardware. But I find that to be unlikely.
Click to expand...
Click to collapse
No HC doesn't mean anything as it was not open source... This is not completely unthinkable. Remember the NC was on 2.1 before the 1.2 release where they upped it to 2.2.
Sent from space
votinh said:
I don't have hope for that, in fact, I doubt it.
They just released v.1.4.1 and it still is Froyo, I don't think they implement ICS for NC.
Click to expand...
Click to collapse
Of course, 1.4.1 came out just before ICS source was released, so maybe B&N figured they do a quick patch of the existing ROM, rather than go through all the work to do a rebuild on GB and then to ICS...
any news/rumors about this?
speedfreak007 said:
any news/rumors about this?
Click to expand...
Click to collapse
Other than slow but steady progress on the CM9 build (and no new releases for now), no.
traumadog said:
Of course, 1.4.1 came out just before ICS source was released, so maybe B&N figured they do a quick patch of the existing ROM, rather than go through all the work to do a rebuild on GB and then to ICS...
Click to expand...
Click to collapse
You have more faith in the B&N corporate staff than I do, but your optimism may be warranted, given that the NT doesn't seem to be totally ignored by the press in the same way the NC was.
zombieflanders said:
... You have more faith in the B&N corporate staff than I do, but your optimism may be warranted, given that the NT doesn't seem to be totally ignored by the press in the same way the NC was.
Click to expand...
Click to collapse
I wonder how much other integration B&N is looking for with other content providers to match what Amazon is doing. I would think upgrading to ICS would make some business sense, in that with a fresher underlying OS, you might be able to keep app developers in the fold working on the NT.
cmstlist said:
The newer Nook Tablet is based on Gingerbread, isn't it? Perhaps they're working on this first and foremost to crank out a third future device that supports APIs from ICS such as fragments. The updated code would then trickle down to Nook Tablet and possibly eventually NC.
Sent from my Nook Color!
Click to expand...
Click to collapse
From what I understand... The new Nook Tablet has a locked bootloader, more or less precluding it from easy rom replacement.
Though, perhaps I have been misinformed.
Yoinx said:
From what I understand... The new Nook Tablet has a locked bootloader, more or less precluding it from easy rom replacement.
Though, perhaps I have been misinformed.
Click to expand...
Click to collapse
Difficult if not impossible for 3rd parties providing roms but not for B&N. They have the security keys allowing them to provide whatever rom they choose within the hardware limits.
After receiving a shiny used Nook Color from Ebay, I immediately flashed the latest daily of CM9 (ICE) to EMMC and played around with it for a while. I installed several "tablet" apps from the Market, and I was very impressed by the formatting and presentation.
Unfortunately, performance was marginal at best, so I decided to flash the "official stable" version of CM7. I installed the same tablet apps as before and noticed that they were not displaying in "tablet mode". Landscape, yes, but not tablet-formatted.
For example, running Pocket Informant in landscape mode in CM9 provides a nice graphical notebook-like format, but CM7 displays the same as a simple landscape calendar, much like on my DROID Bionic.
So from this, I conclude that CM9 is a "real" tablet OS, while CM7 presents the Nook Color to the apps not as a tablet but as a high-resolution phone. Can anyone else confirm this? I absolutely LOVE the performance of CM7--it really flies and is very responsive--but long for the true "tablet" functionality of CM9.
That said, I'd love some input about how landscape mode works on the OS you have installed, and what "tablet-mode" apps actually render as a tablet.
1. What version of the OS are you running?
2. What "tablet" apps are you running?
3. Of those "tablet" apps you are running, what actually render as "tablet" apps?
Thanks!
Jim Barr said:
So from this, I conclude that CM9 is a "real" tablet OS, while CM7 presents the Nook Color to the apps not as a tablet but as a high-resolution phone. Can anyone else confirm this?!
Click to expand...
Click to collapse
Yes, that is 100% correct. CM7 is based on Android 2.x and CM9 is based on Android 4.x. Android 2.x was designed for phones, Android 3.x was the first version to be designed with tablets in mind (and only tablets; phone functionality was stripped out), and Android 4.x folded both capabilities back into a single OS version. Because of the rush-job Google did in order to release Android 3.0 to compete with the iPad they didn't release the source code, which means it couldn't be properly ported over to the Nook Color or other Android tablets that were built with Android 2.x. However, they did release the full source code for 4.x in November which means this is the first time we have the source code for a version of Android actually designed for tablets
Because of these differences many apps have been built to require Android 3.x or higher (which includes CM9) in order to show the tablet layout. Maybe some of those are arbitrary but I'm sure others are taking advantage of system calls and/or UI calls that have only been added to the API since Android 3.x
Wait for the new hardware accelerated build fattire & co. work on right now.
It should be able to speed up things quite a bit thanks to a new SGX driver release.
It's still really early in the game. There's only one official ICS tablet out there - the Asus Transformer Prime. People were expecting many more ICS tablet announcements at CES a few weeks ago - didn't happen. I expect it's because ICS is based off of Honeycomb which didn't exactly set the world on fire and wasn't a big draw for app developers. But now that the ICS is going to be a joint phone/tablet OS - it should spark developers to greater heights. I also think the 7" form factor is going to be more and more popular also... and apps will be developed accordingly. Reader apps like Kindle look great on the nook because they were developed for the smaller form factors... others should follow suit.
Only a few games built for phone (Monopoly and some dice game the kids play are the ones that come to mind) don't render properly on the NC (running CM9). Otherwise, there are a few that won't do landscape (some of the ESPN and some cookbook apps), but I've had good luck otherwise.
Huh - Monopoly runs fine on my emmc install of the latest 2/2 nightly - and it did on the others as well...
I was playing with X-Plane on CM7 with great success. Can't wait to see if it works on the 2/2 nightly.
I agree with the OP. As I am currently going back and forth between cm7 and cm9 the apps are not responding in the same way. Perfect example is gmail. Love the interface on ICS! However, it's just not the same experience on cm7. Google's Currents is the same on both. Google Docs (the newly updated version) seems to work the same on the both as well.
Jim Barr said:
After receiving a shiny used Nook Color from Ebay, I immediately flashed the latest daily of CM9 (ICE) to EMMC and played around with it for a while. I installed several "tablet" apps from the Market, and I was very impressed by the formatting and presentation.
Unfortunately, performance was marginal at best, so I decided to flash the "official stable" version of CM7. I installed the same tablet apps as before and noticed that they were not displaying in "tablet mode". Landscape, yes, but not tablet-formatted.
For example, running Pocket Informant in landscape mode in CM9 provides a nice graphical notebook-like format, but CM7 displays the same as a simple landscape calendar, much like on my DROID Bionic.
So from this, I conclude that CM9 is a "real" tablet OS, while CM7 presents the Nook Color to the apps not as a tablet but as a high-resolution phone. Can anyone else confirm this? I absolutely LOVE the performance of CM7--it really flies and is very responsive--but long for the true "tablet" functionality of CM9.
That said, I'd love some input about how landscape mode works on the OS you have installed, and what "tablet-mode" apps actually render as a tablet.
1. What version of the OS are you running?
2. What "tablet" apps are you running?
3. Of those "tablet" apps you are running, what actually render as "tablet" apps?
Thanks!
Click to expand...
Click to collapse
AFAIK Tablet mode only exists for honeycomb and newer. Any Android device on a 2.x build is seen as a handset.
That should explain what you are seeing
---------- Post added at 11:30 AM ---------- Previous post was at 11:28 AM ----------
Sam Adams said:
It's still really early in the game. There's only one official ICS tablet out there - the Asus Transformer Prime. People were expecting many more ICS tablet announcements at CES a few weeks ago - didn't happen. I expect it's because ICS is based off of Honeycomb which didn't exactly set the world on fire and wasn't a big draw for app developers. But now that the ICS is going to be a joint phone/tablet OS - it should spark developers to greater heights. I also think the 7" form factor is going to be more and more popular also... and apps will be developed accordingly. Reader apps like Kindle look great on the nook because they were developed for the smaller form factors... others should follow suit.
Click to expand...
Click to collapse
I never used early builds of Honeycomb, but the version on my wife's transformer is great. Granted I prefer ICS on my transformer prime... but the versions (which I assume are more stable and way less buggy) of honeycomb out now seem really good