Related
Im not going to update this thread anymore.
It has been a terrible experience here.
All the updates from now on will be on irc channel ..
I hope everyone will be happy and excited about this closure.
Cheers.
Cant we have dual boot on the HD2. it will be cool to have android 2.0 and windows 6.5 on the phone, it will surely kick some ass. and do you think that this phone is upgradable to windows 7
Only possible for dual boot as you need to run harret to get it to boot into linux - android stuff.
Acer Liquid, coming on november will bring Android powered by a Snapdragon processor and wvga screen, I don´t know how it works but maybe it´s rom could be ported easier to HD2? and adding the Sense ui from Hero? I´m sorry I know it´s not easy, but since I´m not a developer I just can see these steps inside my head
kindadevil said:
Acer Liquid, coming on november will bring Android powered by a Snapdragon processor and wvga screen, I don´t know how it works but maybe it´s rom could be ported easier to HD2? and adding the Sense ui from Hero? I´m sorry I know it´s not easy, but since I´m not a developer I just can see these steps inside my head
Click to expand...
Click to collapse
And what if I tell you that's posible
heres the qsd git https://www.codeaurora.org/gitweb/q...ortlog;h=refs/heads/aosp/android-msm8k-2.6.29 , cant wait till this gets to a bootable form =], my acer f1 is arriving tomorrow xD.
xmoo said:
And what if I tell you that's posible
Click to expand...
Click to collapse
Cool! I like WinMo, but I would prefer to try Android, and since no hardware is better than HD2´s, and new possibilities to port Android successfully are coming, I think a new monster could be born here
yes, i`m definitally for this thing.... there will be no problem if leo won`t support wm7, if it will be able to run android...
In fact it will support wm7, but thats up to the OEM's if they want to release a wm7 test rom for these cortex 8 devices =].
HTC have says no to android on HD2, so if its going to happen your going to have to do it yourself.
What would be required? Android 1.6+ supports other CPUs including Snapdragon so what else is required to get it to work with Android? Would be very neat.
xmoo said:
And what if I tell you that's posible
Click to expand...
Click to collapse
that would be great, but what makes you so shure??
who wants andorid 1.6 on the hd2. what we want is the full version of android 2.0
Definitly 2.0
maybe the release of a htc android device with the same hardware as the hd2 will make it easier for developers - but better off getting in the mindset that it won't work
the hero has the same processor as the hd1 doesn't it (and android development on that seems very difficult and slow)?
heromilkshake said:
Definitly 2.0
Click to expand...
Click to collapse
that would make me forget my iphone and buy a hd2
shure2 said:
maybe the release of a htc android device with the same hardware as the hd2 will make it easier for developers - but better off getting in the mindset that it won't work
the hero has the same processor as the hd1 doesn't it (and android development on that seems very difficult and slow)?
Click to expand...
Click to collapse
yeh but look at the possibilities of where we were and where we are today. progress is being made every day now, i hope you go throught the irclogs if so, and it takes time to achieve every goal. a seed doesnt grow into a tree in a day, it takes time and thats whats being talked here. so it wont be hard enough for us to get to the deep of the phone when it comes. cheers.
tids2k said:
yeh but look at the possibilities of where we were and where we are today. progress is being made every day now, i hope you go throught the irclogs if so, and it takes time to achieve every goal. a seed doesnt grow into a tree in a day, it takes time and thats whats being talked here. so it wont be hard enough for us to get to the deep of the phone when it comes. cheers.
Click to expand...
Click to collapse
it would be good to see the progress.. I have read the last few pages on the blackstone and haven't seen anything from the developers. Last update was the 18th where it went back from v1.6 to v1.5?
I can't see why time is being devoted to 1.5, surely the focus should be to work on the most up to date version of android than taking a step back.
Obviously i'm not a developer for the android project on the hd1, but if one comes to the hd2 I will donate to a project with quicker progess on android 1.6, preferably 2.0.....
I have one of these HD2's on pre-order just for this reason I hope I can get something accomplished, and am willing to work on flashing and dumping things
if anyone so asks, as soon as I have it in hand.
Ill be working on it myself too.
borillion_star said:
I have one of these HD2's on pre-order just for this reason I hope I can get something accomplished, and am willing to work on flashing and dumping things
if anyone so asks, as soon as I have it in hand.
Ill be working on it myself too.
Click to expand...
Click to collapse
wow .. so do i man !! im buying only for the sole pupose of seeing android on this phone
Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1? i know we have limited memeory and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
THanks!
does this mean we get 2.1!!!
Posted by Cyanogen in Home on May 21, 2010
A whole bunch of us have been working hard to get Android 2.1 (CM 5.0.7) running perfect on the HTC Dream and Magic phones and I think it’s nearly ready to go. This release is almost exactly the same as the Nexus One and Droid versions of CM now, minus a few of the heavier apps.
This was an incredible community effort and I hope everyone likes the result. Breathing new life into old hardware is always awesome.
I expect that a stable release of 5.0.7 should be ready for all devices in the next few days.
And after that.. Google has confirmed that Android 2.2 (FroYo) will be available for ION phones, so it’s guaranteed that CM-6 will continue to support the G1 also when the source code hits AOSP.
Cyanogen 5.0.7test7 runs pretty sweetly on my G1 and its based on 2.1
does it lag at all? are there any limitations that i should know of
I find it ok with comcache enabled, around the same speed (if not a little quicker) then the stable based on 1.6.
It is still a "test / experimental" build though, so proceed at your own risk etc...
Link to the download and details - http://forum.cyanogenmod.com/index....ic-would-you-like-a-pony-v507-test7-05222010/
Changelog for test7 - http://wiki.cyanogenmod.com/index.php/Release_Notes#5.0.7-DS-test7_.28experimental.29
omgkush said:
Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1? i know we have limited memeory and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
THanks!
Click to expand...
Click to collapse
Running the Rom on my signature which is CyanogenMod5, latest version themed and tweaked. It is a 2.1 and is running very fast/stable so far. Major downside is the battery life however and is a bit hard to get used to vs. a 1.6 Donut Rom.
In all honesty Id say you try SuperD v1.11 (Best Donut Rom in my opinion) first and then flash the Eclair Roms later on. Sooner or later I am sure a developer will improve the battery degradation problem on the 2.1's.
vixsandlee said:
I find it ok with comcache enabled, around the same speed (if not a little quicker) then the stable based on 1.6.
It is still a "test / experimental" build though, so proceed at your own risk etc...
Link to the download and details - http://forum.cyanogenmod.com/index....ic-would-you-like-a-pony-v507-test7-05222010/
Changelog for test7 - http://wiki.cyanogenmod.com/index.php/Release_Notes#5.0.7-DS-test7_.28experimental.29
Click to expand...
Click to collapse
Its been released "stable"
omgkush said:
Hi guys,
im trying to get my phone jtaged so i can finally have it rooted. are there any suggestions on the best mod to use for the g1?
Click to expand...
Click to collapse
And what, might I ask, is a "g1"?
This phone you speak of is an HTC phone called "DREAM".
i know we have limited memeory
Click to expand...
Click to collapse
That statement is absurd. EVERYTHING has limited memory. Unlimited memory is by definition IMPOSSIBLE, even the smallest memory component possible would consume more than the total available space in the universe to produce unlimited/infinite memory. In fact, it would consume the space consumed by INFINITE UNIVERSES. Inconceivably huge, eh?
and i beleive we cant even run 2.0 or 2.1 on the phone is that correct?
Click to expand...
Click to collapse
And just where did you come up with this nonsense? Do you realize that all the chicken littles in the world will always say "your old hardware will never see this!" -- fact is that this is NOT WINDOZE!! Just because windoze phones don't get to see the newer versions does NOT mean that WE won't get to see our newer versions.
**** this guy is annoying with this rooting ****...
You push too much dude. People don't want to work on your phones cause your too pushy
You start threads about the same thing.....useless
So now that Android 2.3 is out, what would it take to get it on the Gtab?
wiredmonkey said:
So now that Android 2.3 is out, what would it take to get it on the Gtab?
Click to expand...
Click to collapse
+1 I would also like to move my gtab from 2.2.0 to 2.3.0.
+1
Sent from my GT-P1000 using XDA App
My guess, since ViewSonic hasn't released source is that it will be some time. Perhaps the Vega or Zpad devs will get to it first.
Sent from my DROID2 using Tapatalk
I think there is supposed to be a official update of the 20th.
I bet it will be Android 2.3 plus whatever app store Viewsonic managed to dig up.
The best thing about 2.3 for tablets like this without 3G is the VoIP phone calling.
Android 2.3 SDK is out. There's no OTA update for Nexus One yet. Nexus S release was announced for December 16th, so there will be something out by then for N1 presumably.
Not sure how much luck we'll have rolling our own Gingerbread build quite yet. We still have no kernel source or any other source code from Viewsonic for that matter. Basically, I'm pretty sure I'll have Gingerbread on my Nexus One well before my G Tablet.
BTW, there is some explicit stuff surrounding large screen support in the Gingerbread SDK. Sort of a recognition that there are now tablet devices out there even though they won't be blessed until the 3.0 release.
popezaphod said:
My guess, since ViewSonic hasn't released source is that it will be some time. Perhaps the Vega or Zpad devs will get to it first.
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
I'm new to Android, but why do we have to wait for Viewsonic? Can't the standard Android 2.3 source be compiled for the Gtab?
I'd recommend everyone calling Viewsonic support and asking them, if they get enough questions they may find some type of answer so we can guage their actions.
I do know that 2.3 has been worked on for this specific OEM device by Malata(zpad). The Woow! device is supposed to be released fairly soon with it. There are nvidia engineers working for Malata who will be on top of this, and I doubt it will take over a month to get it on our device one way or another.
wiredmonkey said:
I'm new to Android, but why do we have to wait for Viewsonic? Can't the standard Android 2.3 source be compiled for the Gtab?
Click to expand...
Click to collapse
Android 2.3 "source" hasn't been released, only the SDK (Software Developers Kit).
You can download the SDK and start coding applications for OS 2.3 but you can't start building 2.3 ROM's until the source is released.
rothnic said:
I'd recommend everyone calling Viewsonic support and asking them, if they get enough questions they may find some type of answer so we can guage their actions.
I do know that 2.3 has been worked on for this specific OEM device by Malata(zpad). The Woow! device is supposed to be released fairly soon with it. There are nvidia engineers working for Malata who will be on top of this, and I doubt it will take over a month to get it on our device one way or another.
Click to expand...
Click to collapse
One month is better than six. With what we've seen so far, I wouldn't expect 2.3 any time soon, at least from VS. I know you Devs will get it to us way sooner.
Everyone excited about this VS "update" coming this month, I wouldn't get too terribly excited. Definitely wouldn't expect more than Flash for the Stock ROM. If VS is smart they'll pay Roebeet for his efforts and make TnT Lite the "update"
tcrews said:
Android 2.3 "source" hasn't been released, only the SDK (Software Developers Kit).
You can download the SDK and start coding applications for OS 2.3 but you can't start building 2.3 ROM's until the source is released.
Click to expand...
Click to collapse
Ah, gotcha.
Umm, I wouldn't expect anything but 2.2 from Viewsonic. Looking at the quality of their release software, besides bugfixes to make the stock ROM "usable" I doubt they will care about supporting this thing.
Once the source is released your time would be better spent thanking whichever dev decides to take this massive undertaking of porting 2.3.
tcrews said:
Android 2.3 "source" hasn't been released, only the SDK (Software Developers Kit).
You can download the SDK and start coding applications for OS 2.3 but you can't start building 2.3 ROM's until the source is released.
Click to expand...
Click to collapse
not quite. you can use the sdk to build a rom.
its very hard and time consuming. but it can be done.
just look at what punk.kaos has done with the eris. there is already a (Very Buggy) gingerbread rom for the eris.
No, you can't use the SDK to build a rom but you can use the crippled system.img they provide in it and try to hack something together. Hacking that and using an older kernel isn't really the way to go. Compiling a rom is going to require source.
Building a rom, to me, is compiling from source. Otherwise you are tweaking someone else's rom or worse...trying to use an image created for the emulator.
Not to downplay his efforts or skill...but that is not a rom to use other than for experimenting or "learning" from.
babybacon said:
not quite. you can use the sdk to build a rom.
its very hard and time consuming. but it can be done.
just look at what punk.kaos has done with the eris. there is already a (Very Buggy) gingerbread rom for the eris.
Click to expand...
Click to collapse
Sent from my Viewsonic 10" GTab...
tcrews said:
No, you can't use the SDK to build a rom but you can use the crippled system.img they provide in it and try to hack something together. Hacking that and using an older kernel isn't really the way to go. Compiling a rom is going to require source.
Building a rom, to me, is compiling from source. Otherwise you are tweaking someone else's rom or worse...trying to use an image created for the emulator.
Not to downplay his efforts or skill...but that is not a rom to use other than for experimenting or "learning" from.
Sent from my Viewsonic 10" GTab...
Click to expand...
Click to collapse
Idk man. kaosfroyo on my eris has been wonderfully fast and stable (especially for as slow as the eris is) ever since v22. these things take some tweaking.
Android 3.0 Preview SDK is now available
More infos you can find here:
http://developer.android.com/sdk/preview/index.html
Saw that yesterday.
But as far as I know it is Tablet only.
Yes,but multiple screen support is there,but needs developing
again!
Well since it is not going to work on a Hero, Don't see the use in posting it here, but maybe better for general dev?
Some similar threads about Gingerbread,Android 2.1 SDK
here to,so think we can stay here!
Android 2.3 works,maybe 3.0 too,Devs can make it possible!
I'm not a developer, but Honeycomb would be difficult even for the likes of Desire. It is very tablet orientated. The next Android for mobile phones is 2.4 Ice Cream, by the time it comes out a lot of the devs would've moved to a different phone.
Sent from my Hero using XDA App
As i understand it google have anounced it there not goung to be any hardware ristrictions on android 3.0. I have a feeling that differnt features will atomatically enabe/disable themselves dependind on the specs of the divice running it. You can already see an example of this in latest google maps which checks the gles version in build.prop to decide weather or not to implement tilt and compass.
Sent from my HTC Hero using Tapatalk
Their maybe no hardware restrictions, but there will be minimum requerements.
And you say devs can make it possible.
You see devs around??
Its a warzone out there....
Most of em are gone, so I am just focusing on 2.3,
and I don't get the comment you made on well there is a 2.2 SDK topic. Duh, but we all knew that is definitly possible to run on the Hero. 3.0 99% That it will never been 100% same as the 2.2 Sense is.
But we will see. The Hero is almost a dead device. So.
And you say it yourself
HTC Hero sold- not a real Gingerbread and Power to low for new Android
Sooo BTW That statement is so wrong...
If you knew anything about android, you would know honeycomb is TABLET ONLY. there is no chance of seeing this on rmthe hero. Wait for 2.4 ice cream but I can't see that on the hero either seeing as there's no devs left.
I think a mod should delete this thread
sjknight413 said:
If you knew anything about android, you would know honeycomb is TABLET ONLY. there is no chance of seeing this on rmthe hero. Wait for 2.4 ice cream but I can't see that on the hero either seeing as there's no devs left.
I think a mod should delete this thread
Click to expand...
Click to collapse
Noo needs to
rdejager said:
Their maybe no hardware restrictions, but there will be minimum requerements.
And you say devs can make it possible.
You see devs around??
Its a warzone out there....
Most of em are gone, so I am just focusing on 2.3,
and I don't get the comment you made on well there is a 2.2 SDK topic. Duh, but we all knew that is definitly possible to run on the Hero. 3.0 99% That it will never been 100% same as the 2.2 Sense is.
But we will see. The Hero is almost a dead device. So.
And you say it yourself
HTC Hero sold- not a real Gingerbread and Power to low for new Android
Sooo BTW That statement is so wrong...
Click to expand...
Click to collapse
No its not only for tablets, this has already been established.
All of the apps have multiple DPI res folders in them (MDPI, HDPI, Extra Large, NoDPI) so it will work on phones - not just tablets.
And Yes,I see Devs for 2.3 so the same Devs maybe developing/porting 3.0
http://pocketnow.com/android/android-30-honeycomb-how-it-might-work-on-smartphones-video
And Yes I said Power to low for new Android versions
does not mean this will not works.
Perhaps not so smooth and not with all functions.
but
you might be right, however 2.4 is I think going to be pretty much the same OS as 3.0 however the 2.X codeline is for phones while the 3.x codeline is for tablets.
Which is definitely the stupidest thing I've heard of in a very long time.
Any developer would twitch at the concept of two different OS codelines to maintain which would otherwise be very similar, unless of course google's keeping some bizarre building structure where it's all one shared resource except whatever is unique to each release line. But that isn't something I personally have seen done before.
Mostly the way they broke up the numbering by a huge value of, wait for it, ONE (2.x versus 3.x) to differentiate between phones and tablets... well that's pretty silly too. Numbering shouldn't be relevant. It should be called two different things, like Android versus AndTab or something like that. But then that would mean we're all talking on our Roids (versus ours tabs) which is, admittedly, kind of rude ;-)
I'm more interested in how they solve this over 20 years. Are we going to expect an Android 2.200.9132 for my phone and 3.7.20 for tablets?
riemervdzee said:
I'm more interested in how they solve this over 20 years. Are we going to expect an Android 2.200.9132 for my phone and 3.7.20 for tablets?
Click to expand...
Click to collapse
and 4.89.20 for laptops?
They will stop changing the whole OS sooner or later, and just provide smaller focused updates. It's very stupid to have 10 different major android versions running at the same time. If 80% of the devices are running Android 2.4.x, things should be easier. They're just following the Ubuntu-like releasing schedule: 2 versions a year. That's the way I see it. They WILL have to stop doing this, they can't go on improving forever.
goodnews xD
im expected.
Android 3.0 Honeycomb won’t be Coming to Smartphone, just for Tablets,says Google:
http://www.pcmag.com/article2/0,2817,2379271,00.asp
Ganii said:
Android 3.0 Honeycomb won’t be Coming to Smartphone, just for Tablets,says Google:
http://www.pcmag.com/article2/0,2817,2379271,00.asp
Click to expand...
Click to collapse
yea
it'll be 2.4 for us phone ppl
RaduG said:
They will stop changing the whole OS sooner or later, and just provide smaller focused updates. It's very stupid to have 10 different major android versions running at the same time. If 80% of the devices are running Android 2.4.x, things should be easier. They're just following the Ubuntu-like releasing schedule: 2 versions a year. That's the way I see it. They WILL have to stop doing this, they can't go on improving forever.
Click to expand...
Click to collapse
Hardware moves fast, demand for said hardware even faster. They have to keep up, if not ahead!
I had a feeling this would be the case since we first saw shots of 3.0 running on a then-unidentified Motorola tablet. Looking at it now, there's absolutely no way that this is plausible to run on handsets; for one, it likely demands a decently high hardware spec to run efficiently, and even if you've got something like the Optimus 2X for example, the screen's far too small to allow for efficient usage.
In all honesty, it's likely we'll see divergence of Android into 2 distinct OSes; handset-based (2.3 onward) and tablet-based (3.0).
Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?
gabenoob said:
Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?
Click to expand...
Click to collapse
Same reason everyone wanted DJ05, DL09 and DL30...they always want something new. Instead of optimizing what they have and being content, they rather complain and wish for something better to come along.
I get that, but whats with the wanting of this new thing if its not even meant for a phone; I mean I wouldn't want something clunky and literally designed for something bigger on a 'tiny' device. It would just be wrong. I fail to see how even those who continually ask for new shiny things would overlook the real incompatabiliteis with a phone. I can see asking for Gingerbread, but even that's a bit much. I mean, we have Froyo, and now my brother with his fancy incredible is actually jealous of my phone. I think things are great, and I understand the desire for new shiny things, but honeycomb really isn't for phones, so why be ignorant of that?
gabenoob said:
I get that, but whats with the wanting of this new thing if its not even meant for a phone; I mean I wouldn't want something clunky and literally designed for something bigger on a 'tiny' device. It would just be wrong. I fail to see how even those who continually ask for new shiny things would overlook the real incompatabiliteis with a phone. I can see asking for Gingerbread, but even that's a bit much. I mean, we have Froyo, and now my brother with his fancy incredible is actually jealous of my phone. I think things are great, and I understand the desire for new shiny things, but honeycomb really isn't for phones, so why be ignorant of that?
Click to expand...
Click to collapse
keep in mind though...froyo wasn't meant for our specific phones either...we're all running a leaked version. For all we know, after a year of addl development the next ota update may be honeycomb...
jenisiz said:
keep in mind though...froyo wasn't meant for our specific phones either...we're all running a leaked version. For all we know, after a year of addl development the next ota update may be honeycomb...
Click to expand...
Click to collapse
honeycomb is for tablets!!
ace5198 said:
honeycomb is for tablets!!
Click to expand...
Click to collapse
3.0's UI is meant to be able to scale down to phone sizes. The current developer preview doesn't work exceptionally well when that's done to it (it's buggy, but obviously meant to), but it's not anywhere near a finished product (it's really meant to show the APIs).
Android also isn't being forked, there isn't going to be a Phone version and a Tablet version, future phones will be running the 3 series (they might wait for 3.1, but they will run 3). They will pretty much have to if any of them want to use the newer dual-core CPUs that should be just about to hit the phone segment.
Also, don't forget that Android 3.0 adds a fair bit of new APIs, not all of which are meant exclusively for tablets (there's a fair bit of HW acceleration stuff, IIRC).
KitsuneKnight said:
3.0's UI is meant to be able to scale down to phone sizes. The current developer preview doesn't work exceptionally well when that's done to it (it's buggy, but obviously meant to), but it's not anywhere near a finished product (it's really meant to show the APIs).
Android also isn't being forked, there isn't going to be a Phone version and a Tablet version, future phones will be running the 3 series (they might wait for 3.1, but they will run 3). They will pretty much have to if any of them want to use the newer dual-core CPUs that should be just about to hit the phone segment.
Also, don't forget that Android 3.0 adds a fair bit of new APIs, not all of which are meant exclusively for tablets (there's a fair bit of HW acceleration stuff, IIRC).
Click to expand...
Click to collapse
im sure that it could be scaled down to use on a phone.. and actually i believe somewhere i seen that it was.. but everything ive read said its desinged specifically for tabs.. im sure there will be a 3.1 or 2.5,,6,7,8 or whatecer for the new apis.. but everything ive read says 3.0 is for tabs.. im not saying im right.. but thats just what ive read
ace5198 said:
im sure that it could be scaled down to use on a phone.. and actually i believe somewhere i seen that it was.. but everything ive read said its desinged specifically for tabs.. im sure there will be a 3.1 or 2.5,,6,7,8 or whatecer for the new apis.. but everything ive read says 3.0 is for tabs.. im not saying im right.. but thats just what ive read
Click to expand...
Click to collapse
The new user interface is designed for tablets, as well as parts of the new APIs. Nothing prevents you from replacing the launcher, and hopefully by the time Honeycomb stabilizes, the new Launcher won't just force close at lower resolutions (but this isn't meant to be a preview of the new interface, but of the APIs).
I don't understand you question.
Honeycomb is simply the natural progression of Android. Hence why its 3.0. Eventually all Android devices will be on 3.x of some kind just as iOS was able to merge its variant it made for the iPad with the rest of the family.
Google had a separate team continue to small upgrades in the 2.x line while the AAA team worked on a tablet enahnced 3.0 Honeycomb variant.
I'm sure as this year moves (early next) on we'll see a 3.1 version come out that has the appropriate scaling features to handle screens of all sizes.
This is evidenced by the same Gmail app being used in both. Just different views based on overall screen size. Also, 3.0 and 2.3 have code to allow devs to make different views based on screen size. The base code is there, its just now gotta be merged to be one line again.
So, why do I want honeycomb? I don't. I want to continue to be using the latest version of Android, what its build version is is not important. (2.3, 2.4, 3.0, 3.1) As long as its made to work with the hardware I have and adds improvements, I want it.
Stop the debate:
http://www.bgr.com/2011/02/03/google-will-not-bring-honeycomb-to-smartphones/
mexiken said:
Stop the debate:
http://www.bgr.com/2011/02/03/google-will-not-bring-honeycomb-to-smartphones/
Click to expand...
Click to collapse
All that says is 3.0 i.e. Honeycomb won't be on phones. I am sure a later 3.x version will once the code has been merged from 2.x.
I thought 3.0 is where we finally get hardware accelerated UI, is this correct?
Sent from my SCH-I500 using XDA App
superchunkwii said:
All that says is 3.0 i.e. Honeycomb won't be on phones. I am sure a later 3.x version will once the code has been merged from 2.x.
Click to expand...
Click to collapse
And this thread is about Honeycomb... Not 3.x versions.
crookshanks said:
And this thread is about Honeycomb... Not 3.x versions.
Click to expand...
Click to collapse
Honeycomb is 3.0
gabenoob said:
Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?
Click to expand...
Click to collapse
I'd want the built-in data encryption features.
-deleted-
Misread somethin'
Hmm alright; what I was asking is that where it stands now it is a Tablet OS, why would anyone want something like that on a phone. As shown in the link, google does not mean for Honeycomb to be brought to phones (3.0) but maybe at a later date a later variant of the 3.1 series will.
The original question I had in mind was why would anyone want it, in its current state, on a phone, as I've seen threads asking for it; and for the life of me I can't find a good reason.
superchunkwii said:
Honeycomb is 3.0
Click to expand...
Click to collapse
I was referring to your "later 3.x versions" comment. This thread was about why anyone wanted 3.0 specifically, not later versions.
crookshanks said:
I was referring to your "later 3.x versions" comment. This thread was about why anyone wanted 3.0 specifically, not later versions.
Click to expand...
Click to collapse
Absolutely right, my post was to the validity of the entire discussion as its obvious 3.0 is just the initial tablet offering and as Android continues through 3.x it will be on phones as well.
Basically, I find the entire constant discussion here, BGR, other sites about Honeycomb being a Tablet OS and why is Google diverging Android to just be stupid. To me the version "3.0" should have been enough to satisfy everyone that eventually features you see in Honeycomb will be on phones. Like Google's going to lock themselves in 2.x for the rest of Android phone's life.
Honestly I don't understand it. Other than a very small number of users, myself not included, do people really see a big difference in the use of their phones? I use mine for calling, texting, e-mail and occasional web browsing. Other than flash support, I haven't noticed any ground breaking improvements over DJ05 with DL30. I can't imagine Gingerbread, Honeycomb, Lucky Charms or Poptart making a huge difference in the day to day use of my phone either.
Or maybe I'm wrong and Honeycomb cures cancer.