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.
Related
Just read the news about these two getting the update that fixes the SMS bug but no mention of any other 2.2.x O/S'd phones getting it. Can't be far off surely?
http://phandroid.com/
I just want that SMS fix, I've seen two I9000Ms do it. I pinged Samsung Canada on Twitter, we'll see what their response is.
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
Click to expand...
Click to collapse
maybe ayes maybe naws
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
(American variant releases not guaranteed)
Click to expand...
Click to collapse
Fixed that for you.
i somewhere read that we can expect 2.3 for SGS for the end for the first quarter of the year...but are you people using stock ROMS ? i think Darky's ROM is working on a multi-device able to detect and flash devices accordingly, shouldn't that fix your sms problems ?
ps: i have the i9000, but what is "the sms problem", i don't think i have it..
Everybody bug samsung to skip 2.3 and prep for 3.0.
With carriers charging 15-20¢/SMS and having a free replacement (google voice, google talk, emails)
I really couldn't care less about SMS. I should even remove the SMS app from my phone.
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
It's for both.
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
So wrong, it hurts.
rumor
the rumor is here :
i like the way they say
"site called SamFirmwares – one we’ve never heard of before."
Click to expand...
Click to collapse
they better all listen to these site ! i wonder how these big companies would react to
all the amazing roms out there !
JCopernicus said:
So wrong, it hurts.
Click to expand...
Click to collapse
Is it? Then prove me wrong...
From google:
Honeycomb is the next version of the Android platform, designed from the ground up for devices with larger screen sizes, particularly tablets.
Click to expand...
Click to collapse
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
t1mman said:
Is it? Then prove me wrong...
From google:
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
Click to expand...
Click to collapse
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
JCopernicus said:
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
Click to expand...
Click to collapse
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
t1mman said:
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
Click to expand...
Click to collapse
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
JCopernicus said:
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
Click to expand...
Click to collapse
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
t1mman said:
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
Click to expand...
Click to collapse
The large screen views (which never existed) are built from the "ground up" because, guess what? They never existed in the first place.
The reason it's taking 3.0 is because it's a huge jump in feature set, and qualifies as a version realease and not just a point release.
If a device has a certain feature it can access certain API from the android OS. If a device doesn't, then it can't. It's that simple.
"tablets" have the big screen feature and they can access the nested view API's. You don't know how android works. there is ONE line, which sits at 2.3.2, and it's device independent.
Just like the Nexus S can access the NFC api's because it has an NFC chip.
AOSP is the code that google/samsung/moto/acer/etc pull from, and build more on top.
Cyanogen roms are on par and equivalent(better actually) as google's roms, you can't get more "official" than AOSP. MFG roms are actually less true to AOSP as they are modified. You probably won't see 3.0 on the current galaxy line at all, but that has nothing to do whether it works on there or not.
Chill out dude! Take a deep breath....
This is getting nowhere, running in circle...
I'm pretty sure we won't see Honeycomb as a release by the makers (Samsungs, Motorola, LG, HTC, name em) on any smartphone. Don't know why this is such a big deal for you and what you don't get on the whole deal but if you want,
You can bookmark this thread and if you see an official honecomb as an official release by samsung or LG or HTC or google on a Smartphone, revive it from the archives and rub it on my face, I'll gladly take the fall...
Chill out? I think I'm just typing normally on a keyboard? Maybe I'm smashing keys, and don't recognize it?
You don't understand how android works if you think it won't appear on phones, we're not going around in circles. You're just wrong.
Does anyone know when Barnes and Noble will drop the official Froyo update for the Nook Color? Back in December every tech site was saying it was due in January, but that obviously did not happen. I am trying to decide whether to root mine now or wait for the official OS update before I start messing with my NC. Thanks
brendan6q66 said:
Does anyone know when Barnes and Noble will drop the official Froyo update for the Nook Color? Back in December every tech site was saying it was due in January, but that obviously did not happen. I am trying to decide whether to root mine now or wait for the official OS update before I start messing with my NC. Thanks
Click to expand...
Click to collapse
I wouldnt ever expect it officially. Most of these rumors started with nameless sources, and employee talk. They also made the claim that we would have the appstore but we know how that went. As many have stated, the nook is an E-Reader first. It doesn't need anything past what it has now, to do what its designed to do.
I still think B&N is working on their app store. It's an opportunity to make more money. How long it will take to get released, who knows.
Ultimately I think it depends on what you're looking for in the software. Even if B&N updates it to 2.2 it won't be the same look and feel you get on other android devices. I don't think it's going to happen that they release a software update that upgrades this thing from an e-reader to a tablet pc. The talks are they'll incorporate some customized market for software in an update, so maybe we get the android market, but probably just some bastardized form of it. I think if you want a true tablet experience with the NC, you'll never get that without rooting it. Don't think of it as a Froyo update, but rather a NC update, if it comes from B&N. Just the same e-reader with a different foundation.
there is no consequences of rooting your nook. you can always flash your nook back to stock. thay being said i would suggest you try nookie froyo. even if froyo DOES come out from B&N there is no gurantee it will give the full tablet experience that AOSP froyo does.
I realize the update was never intended to bring the full 2.2 experience to the NC, but i had heard that it would offer more or less the homescreen experience along with a curated B&N app store. I just think this thing has so much more potential then B&N is currently offering on it. I think it is in dire need of more basic stock apps such as email, a calendar, calculator, etc. I bring my NC with me everywhere... classes, on the subway. I think the addition of these apps would make it a complete device rather than just an e-reader. And it is not just an ereader... that designation went out the window the second it got that beautiful color display. Also, I think 3rd party apps like dropbox, instapaper, and an rss reader that syncs to google reader would be amazing on the NC. I realize I can get all of this by rooting, but I would feel much more comfortable if they were eventually offered by B&N
brendan6q66 said:
I realize the update was never intended to bring the full 2.2 experience to the NC, but i had heard that it would offer more or less the homescreen experience along with a curated B&N app store. I just think this thing has so much more potential then B&N is currently offering on it. I think it is in dire need of more basic stock apps such as email, a calendar, calculator, etc. I bring my NC with me everywhere... classes, on the subway. I think the addition of these apps would make it a complete device rather than just an e-reader. And it is not just an ereader... that designation went out the window the second it got that beautiful color display. Also, I think 3rd party apps like dropbox, instapaper, and an rss reader that syncs to google reader would be amazing on the NC. I realize I can get all of this by rooting, but I would feel much more comfortable if they were eventually offered by B&N
Click to expand...
Click to collapse
Look, if I burn the desk I'm sitting at and I find that it burns well, that doesn't mean the company that makes it actually makes firewood. If by "complete device" you mean a tablet pc, then B&N could have released it as such when it first came out. But what you're refusing to acknowledge is that this thing wasn't created for that, however capable it may be. At this point all I've heard is we may get some form of a software market, which doesn't need a kernel update from 2.1 to 2.2, so even with that, we may not get an android update. Like I said, just stop thinking that, because this can be an effective tablet, B&N will go out of their way to make it one. For that matter, you shouldn't expect it to have the look of an android device any more than it currently does. It seems to me that B&N would be pretty particular about the appearance of their software.
Listen, just wait it out if you don't want to root the thing. Maybe they will give us a decent app list, and maybe it won't take forever and a day to get to us. But don't expect them to offer any software from a competitor, or book/magazine/newspaper reading software that doesn't require you get the material from them.
At the end of the day, BN would be insane to release a full fledged version of the market onto the NC. The absolute last thing they want is Amazon, Borders and others competing with them on their own platform. I think we will see a market of some sort released down the road. When I don't know, but I'd be surprised if we never see one. BN intends for this thing to just be an e-reader. They don't want people to buy it and use it as a tablet. They want it to be an e-reader because it's then basically tied to their store for content. That is what they want.
Second Tuesday in the first week of June
March 7th. Note no year specified.
February 31st
How would we know?
Nobody knows. Just speculation and guesses out there.
"When it's ready."
That's the only answer I would actually believe, and even then I'm not inclined to accept it as truth.
What if they are planning to go straight to HoneyComb?
Holy ****! It never ends
V.A.T.Juice said:
What if they are planning to go straight to HoneyComb?
Click to expand...
Click to collapse
In what ways will Honeycomb make the NC a better ereader for B&N-purchased ebooks?
The only reason I believe they would even go to an underlying 2.2 is for Flash. I could imagine them coming out with some very cool eReader applications for it such as in-magazine videos and other book/magazine related media features like that. It's a very capable little device and I positively love mine, but I feel like there are many people buying it as a $250 Galaxy Tab competitor, and it's simply not. The community here is great and tons of people are doing absolutely outstanding work unlocking a wealth of potential, but at the end of the day we will never get fully featured android support from B&N and it would be silly to expect it.
miemens said:
The only reason I believe they would even go to an underlying 2.2 is for Flash. I could imagine them coming out with some very cool eReader applications for it such as in-magazine videos and other book/magazine related media features like that. It's a very capable little device and I positively love mine, but I feel like there are many people buying it as a $250 Galaxy Tab competitor, and it's simply not. The community here is great and tons of people are doing absolutely outstanding work unlocking a wealth of potential, but at the end of the day we will never get fully featured android support from B&N and it would be silly to expect it.
Click to expand...
Click to collapse
Exactly right, it won't be supported as a tablet. If/when someone cooks up a rom for this thing based on honeycomb, it'll be the same as autonooter and nookie froyo now. What I mean is we'll get a device that reports itself as some other device, the xoom or some other thing, just so the market has an idea of what apps we should have available. But they'll have such higher powered tablets with better cpu's and more ram, better screens, and they'll have nifty docks and bluetooth attachments, and we'll be luck if someone just gets our bluetooth runnning smoothly.
Once they get the textbook thing straightened out, do you think they might need flash for streaming classes? I know some unis have classes where you can either attend virtually or at least replay lectures.
Homer
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!!)
We’ve been hard at work on CM9 since Google released Android 4.0 (Ice Cream Sandwich) into the wild last month, and things are slowly starting to come together. Google did a great job with ICS and added some really awesome features which in some cases replace or deprecate functionality that we had in CM7, so we are reevaluating all of our customizations. A number of devices are already up and running with CM9, and the focus is currently on getting as many devices ready as we can. The first devices (besides the Nexus S, which you can already get from Koush’s section on ROM Manager) that we’ll have ready will mostly likely be devices based on OMAP4, MSM8660/7X30, and Exynos. We also have some Tegra2 tablets in the pipeline such as the Galaxy Tab 10.1 and Asus Transformer. Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. I don’t want to make any promises at this time, but that is the plan. And sorry Droid1 owners, we’re dropping support for you. Time to upgrade.
What do you recommend if we have to keep our Droid1?!?
I have no philosophical problem with the Droid1 not having the latest and greatest CM ROM. I can get along without CM7 on the Droid1, since I will be going that way with my Droid Bionic "real soon now". (I'm kinda, sorta, used to this class of support, since I have about 6 Win XP/Pro boxes and a SBS 2003 server here on my SOHO network. All the current best boxes for me and my digital nerds are dual booted running top end Win7 and several flavors of Linux.
So, what is the last build that we should use, how long will it be supported and will security fixes be available?
Thanks,
/s/ BezantSoft
aoidcool said:
And sorry Droid1 owners, we’re dropping support for you. Time to upgrade.
Click to expand...
Click to collapse
And you plan to make this seem official... How? If the CyanogenMod developers actually said that, I might have a few unkind remarks about forced hardware upgrades to share.
For the record, I am not complaining about the lack of official CM9 support, the fact that ICS on the Droid1 would likely be a slow/buggy/needless upgrade, or anything along those lines.
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Until a developer phone appears that meets my stingy requirements, I will continue using my Droid and experimenting with Linux software on it. I only wish that waiting for other people to do what I should be doing was easier, secure in my knowledge that someone else in the world cares about the same things I care about. What can I say, I'm lazy.
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
gTan64 said:
And you plan to make this seem official... How? If the CyanogenMod developers actually said that, I might have a few unkind remarks about forced hardware upgrades to share.
For the record, I am not complaining about the lack of official CM9 support, the fact that ICS on the Droid1 would likely be a slow/buggy/needless upgrade, or anything along those lines.
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Until a developer phone appears that meets my stingy requirements, I will continue using my Droid and experimenting with Linux software on it. I only wish that waiting for other people to do what I should be doing was easier, secure in my knowledge that someone else in the world cares about the same things I care about. What can I say, I'm lazy.
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
Click to expand...
Click to collapse
That first post is a quote from the cm blog. So it is 100% true.
VISION 1.5Ghz
I think a kang will show up sooner or later. There are plenty of other interesting OMAP3 devices (Nook Color for one) which should get ports, and OMAP3 doesn't have to lose 60-100MB of RAM to the radio, so with compcache and good tuning 256MB might actually be enough.
It really depends on if OMAP3 HW accell can work fully under ICS. If the Nook Color runs well, so should the Droid...
gTan64 said:
What I might complain about is that the Droid1 is the most recent Android phone I would buy. Nothing newer has an unlocked bootloader, a better physical keyboard (well, minus the Nokia N900, but that's not without its issues either), a comparable screen, and the second-hand advantage: No carrier contract/spying or data plan required (Google Voice over WiFi FTW), cheaper than dirt for mobile software development, and wide availability (unlike certain Maemo/MeeGo phones).
Click to expand...
Click to collapse
so your complaint has nothing to do with software development, but with handset manufacturers. What does that have to do with CM saying they won't support what amounts to a 1st gen device?
TL;DR: Telling people to upgrade when they don't have a choice is counterproductive IMHO.
Click to expand...
Click to collapse
but you do have a choice. either upgrade, or you're stuck with whatever they've already built.
:|
Well, someone'll port ics to this 3 year old POS i'm stuck with for another year.
I'd rather have a current os that doesn't run well than a outdated os that does.
Sent from my Nook Tablet using Tapatalk
Mr. Argent said:
I'd rather have a current os that doesn't run well than a outdated os that does.
Sent from my Nook Tablet using Tapatalk
Click to expand...
Click to collapse
Why????
Sent from my VS910 4G using xda premium
Having no money for a off-contract phone and not being able to upgrade for a year, I have to do something to keep my original droid usable for a year. I find knowing there's a major update available and not getting it due to hardware issues annoying when the g1 got it (even if it was a laggy mess, at least it's not 2.3), which impacts it being what I consider usable.
(Also, I don't want ics launcher. Beneath the veneer of modernity it's still that stale old gingerbread.)
Sent from my nook tablet (eagerly awaiting a bootloader workaroiubd and ics) using Tapatalk.
Mr. Argent said:
Having no money for a off-contract phone and not being able to upgrade for a year, I have to do something to keep my original droid usable for a year. I find knowing there's a major update available and not getting it due to hardware issues annoying when the g1 got it (even if it was a laggy mess, at least it's not 2.3), which impacts it being what I consider usable.
(Also, I don't want ics launcher. Beneath the veneer of modernity it's still that stale old gingerbread.)
Sent from my nook tablet (eagerly awaiting a bootloader workaroiubd and ics) using Tapatalk.
Click to expand...
Click to collapse
I'm in the same boat as you, I have no upgrade for a year. so i'm stuck with my D1. and i agree with your other statement a g1 can handle it yet no one is making an attempt in porting it to the D1 on top of that a 6 year old htc windows mobile phone has it with like 134mb of ram. and yet the droid still has no port whatsoever
In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!
rushless said:
In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!
Click to expand...
Click to collapse
Check the OP of the CARBON thread.
Unless a serious bug is identified, these early November builds will be the final updates for the 4.3 branch, as the Carbon Team has started working on 4.4
Click to expand...
Click to collapse
Be patient, it's coming!
Indeed, yes. It's true that KitKat will run on lower specification devices, however, that doesn't mean EOL devices will be resurrected. The lower specification "thing" is more of OEMs to consider, so they can push budget devices with the latest version of Android, KitKat; instead of still producing Gingerbread devices.
Of course, away from that subject. It should effectively mean, our devices currently on ICS/4.0.x+ should see an increase in performance, including our Nooks.
So when will we receive 4.4 KitKat on our Nooks? The general rule is never to ask for ETAs, but CyanogenMod has provided for us. CM10.1 is complete and finalised. They're trying to complete work on CM10.2, instead of jettisoning all of the current developers efforts. So they/CyanogenMod will be working on CM10.2 for some time, until they can finish it. That doesn't mean to say CM11 will come after CM10.2. No, you can expect CM11 nightly builds by the end of this month. And yes, it'll be called CM11, not CM10.3.
CM11 release date source.
Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app
psyberian said:
Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.
famewolf said:
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.
Click to expand...
Click to collapse
im so excited for 4.4 on our nooks!