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.
Related
Yup Yup Yup, I've decided to make a poll on the most debated Topic on here, simply i want to know if all x10 owners here feel the same way like me or not..
And also to give any new comer an idea about the status of the community, so
what do you expect you will see first on your device ?
- Devs here cracking the bootloader and Flashing a 2.2 Rom and giving us freedom to the world of modding.
- SE release the 2.1 update at the end of the month - and don't argue about the date pleaseeeeeee, i am sick of it - followed by the 2.2 update early next year which is a lot of time, but we don't have a choice...
you can get an extra point if you explain your opinion bases
One More Thing :
For Gods Sake, don't talk about :
- screen color support
- multi***** - you can guess it -
- Any other debated topic that have been discussed Zillions of times here Cause it just makes me fall asleep while reading it..
happy voting
If you don't know what is the new features you will get by updating.. here are a few from what have been posted here :
Android 2.1 :
- 720p Video recording.
- Live Wallpaper.
- Language support ( Arabic, etc.. )
- BT voice dial ( added 2.1 ? )
- more applications supported in Market ( Twitter, etc.. )
Android 2.2 :
-Have a faster phone, with JIT.
-To have faster web browsing (V8 Javascript engine).
-To be able to run ALL apps.
-To move apps to SD, if needed, to free space.
-To not have pixelated icons and images in apps - I think that this is probably due to the new resources layout - drawable-hdpi, mdpi etc.
- Flash support.
- push support for applications.
- Hotspot Option.
- 5x faster performance.
ehm - about the ( 3.0 ) in the title, its just to make the thread intersting ( don't daydream about it )
Umm here is the problem.
What are the features that make it stand out from one tier to another.
It is basically a movement of numbers to me.
What is the real differences between 1.6 ro 2.1 ?
720 recording, live wallpaper....and what else?
Then from 2.1 to 2.2
....flash support....? what else?
then from 2.2 to the rumored 3.0
No idea, maybe it shoot beams of laser or maybe allow you to call UMA.
Seriously, there are just numbers that is moving around. Things that can live or live without it. I am perfectly fine with 1.6 right now. Sorry, i am a Window XP user with 3 other pc with vista and win 7.
I still like win xp more, it feel a lot solid.
What i do like is SE fix that problem with this "force close" on some random in-bound calls and remove that damn slider.
wrongfeifong said:
What is the real differences between 1.6 ro 2.1 ?
Click to expand...
Click to collapse
More language support ?
believe me , just thinking about the whole applications that require 2.0+ , the push in 2.2 , beside all you just said..
Knowing your phone can do many things it can't do right now cause of a stupid limitation that can be fixed ... some people can't bear that thought - including me -
mezo9090 said:
More language support ?
believe me , just thinking about the whole applications that require 2.0+ , the push in 2.2 , beside all you just said..
Knowing your phone can do many things it can't do right now cause of a stupid limitation that can be fixed ... some people can't bear that thought - including me -
Click to expand...
Click to collapse
Also, with 2.1, the X10 can finally connect to WPA wifi networks
wrongfeifong said:
Umm here is the problem.
What are the features that make it stand out from one tier to another.
It is basically a movement of numbers to me.
What is the real differences between 1.6 ro 2.1 ?
Click to expand...
Click to collapse
Fantastic to meet the only other person on the planet that isn't in a contest to get a higher number on the device
Upgrading for the sake of upgrading is .... fill in the blank.
I stopped the firmware upgrade at 024 since the phone is working "great" now so I don't see any value in an upgrade to 026 +. Unless something worth while is enhanced. Since there's no change log it's a little tough to see what the improvements are.
As to the Android 2.1, 2.2, 3.0, 99.9 unless there is true improvement in valid areas I could really not care less. (my personal feeling)
The ONLY feature I'm missing right now is Bluetooth Voice Dial which should have been in the very first release of Android.
2x-5x faster .. don't care, it's already fast. 720p video .... not interested. Hotspot, nope.
If you want and/or need those features then upgrading is great but the X10 pretty much already does what I need with 1.6. (except BT VD)
OMG, i felt in love with your post... Rly, we used to the updates, no matter what it brings. Diffrence between updates isn't important, the number of it is the main benefit. I think 1,6 of Xperia is rly well rounded. There is few things which should be improved, but it's rather improvement than hugh change. Im sick of reading the next post about how SE rude is waiting with upgrade to 2.1... Im not againts this, but ppl try to let it all hang out, just take a rest of writing next threats, enjoy your great mobile phone.
after 2.2 will android jump all the way too 3.0. or will they be like 2.3 and so on? just curios cause that would mean after 2.2 our phones wont be able to handle 3.0
The main benefit of 2.2 over 2.1 is the fact that it is at least twice as quick.. it's damned fast.. That would be my reason for wanting 2.2.. having said that though.. I'm not desperate for it.. my phone runs very well on 1.6..
I would love to just have 2.2.
3.0 . . I would never expect to see it unfortunately.
I really dont want 2.2 cooked firmware which has even 1 thing not working. I see a lot custom firmwares and there it says "...most of the stuff works" or "Camera not working" etc. I would NEVER put any ROM that is not 100% functional, I would rather use 2.1 that works than 3.0 that has no camera working. I really dont understand that, my last phone was Omnia HD and the man named HyperX is making custom firmwares for that phone, on his ROMs there can only be some extra stuff that are working and which are not in Samsung ROMS but everything else is working, and it is working better than Samsung original ROMs. So I really dont understand this Android ROMs, I always want clean ROM without some default apps and with everything else in it that makes the phone better, necer looking, who doesnt want it, he can easily remove it with Titanium Backup. That is my vision...
Nice to find other people happy not chasing the numbers ... I thinks Sony did a pretty fine job with 1.6. Looking forward to their version of 2.1, pretty sure they'll do a fine job of it too.
Only thing I'd slightly miffed about is no flash
I do like the Rachel UI, but an optimized FroYo ROM is better to me than official Eclair.
I don't care about upgrades at all. As already mentioned here I just want flash support and faster speed. The rest to me is pointless, sure 720p recording is cool but the more I think about how often I take videos the more I realize I probably wont take advantage of it. Remember when phones didn't have upgrades? When you bought the phone and used it for 1-2 years plus and it was the same thing the whole time? Those were the days...
Sent from my X10a using XDA App
wrongfeifong said:
Then from 2.1 to 2.2
....flash support....? what else?
Click to expand...
Click to collapse
Dalvik JIT and V8 engine..
mezo9090 said:
More language support ?
believe me , just thinking about the whole applications that require 2.0+ , the push in 2.2 , beside all you just said..
Knowing your phone can do many things it can't do right now cause of a stupid limitation that can be fixed ... some people can't bear that thought - including me -
Click to expand...
Click to collapse
Exactly.
Zaslav said:
I don't care about upgrades at all. As already mentioned here I just want flash support and faster speed. The rest to me is pointless, sure 720p recording is cool but the more I think about how often I take videos the more I realize I probably wont take advantage of it. Remember when phones didn't have upgrades? When you bought the phone and used it for 1-2 years plus and it was the same thing the whole time? Those were the days...
Sent from my X10a using XDA App
Click to expand...
Click to collapse
I probably won't use the 720p video recording, but probably the DLNA support.
Although, I know what you mean about the 1 to 2 years usage of phones, without an upgrade. To be honest, this only really happened with the first iPhone, and then in an even more accelerated way, with Android, and as more manufacturers are bringing out more Android phones, it means that they have to work harder to upgrade all of them at the speedy pace Google is moving at, and customize them too.
I just want the latest firmware (2.2+) to:
-Have a faster phone, with JIT.
-To have faster web browsing (V8 Javascript engine), and flash support, so that I don't have to hope that Skyfire will work for me.
-To be able to run ALL apps.
-To move apps to SD, if needed, to free space.
-To not have pixelated icons and images in apps - I think that this is probably due to the new resources layout - drawable-hdpi, mdpi etc.
- Lots more stuff that I can't remember...
BUT, I think we'll get 2.1 from SE before the custom bootloader/SPL is (nearly) bug-free, and can be flashed easily and safely. Hopefully, I'm wrong, and we'll have Froyo on our X10's by next week!
But the main problem I have, which is a bit off-topic, is that:
Will SE patch the root exploits when 2.1 is released, or even upgrade the bootloader, (or radio), without us knowing, to stop all progress completely - like Sony did, and still does, with the PSP?
aodmisery said:
after 2.2 will android jump all the way too 3.0. or will they be like 2.3 and so on? just curios cause that would mean after 2.2 our phones wont be able to handle 3.0
Click to expand...
Click to collapse
Logical fallacy.
If a supposed 3.0 update contained "X", "Y" and "Z", but got changed to version 2.3 with "X", "Y", and "Z", the phone could theoretically run it because the version number is lower?
Think before you type. A larger number means absolutely nothing in terms of whether the phone could handle it.
HunteronX said:
But the main problem I have, which is a bit off-topic, is that:
Will SE patch the root exploits when 2.1 is released, or even upgrade the bootloader, (or radio), without us knowing, to stop all progress completely - like Sony did, and still does, with the PSP?
Click to expand...
Click to collapse
Most likely yes.
And i find it normal as is a security flaw in the phone.
So, don't do any SEUS/OTA/Companion upgrades if you want to keep root.
iead1 said:
Logical fallacy.
If a supposed 3.0 update contained "X", "Y" and "Z", but got changed to version 2.3 with "X", "Y", and "Z", the phone could theoretically run it because the version number is lower?
Think before you type. A larger number means absolutely nothing in terms of whether the phone could handle it.
Click to expand...
Click to collapse
he probably heard that "minimum" requirements for Gingerbread..
aodmisery said:
after 2.2 will android jump all the way too 3.0. or will they be like 2.3 and so on? just curios cause that would mean after 2.2 our phones wont be able to handle 3.0
Click to expand...
Click to collapse
Don't Daydream ? thats what i was afraid of
damirbusic said:
I really dont want 2.2 cooked firmware which has even 1 thing not working. I see a lot custom firmwares and there it says "...most of the stuff works" or "Camera not working" etc. I would NEVER put any ROM that is not 100% functional, I would rather use 2.1 that works than 3.0 that has no camera working.
Click to expand...
Click to collapse
i totally agree with you, but i've also seen some custom ones that work 100%, take the CM for example, i saw one myself that was very stable and working for normal daily use..
applebook said:
I do like the Rachel UI, but an optimized FroYo ROM is better to me than official Eclair.
Click to expand...
Click to collapse
i think people who buy same phones think alike lol
tuxStyle said:
Most likely yes.
And i find it normal as is a security flaw in the phone.
So, don't do any SEUS/OTA/Companion upgrades if you want to keep root.
Click to expand...
Click to collapse
i think if we upgrade to 2.1, we will be able to Flash-Back to 1.6 with the tools present atm ?
note,
i aggregated the info you guys put in the 1# post so if any1 new to x10 or android sees the thread can understand a bit
i don't want it to be a poll-chitchat thread that have no point at all, that would be waste of space
Hey,
I am NOT a dev, but I would like to know what kind of work work is going to be required now that gingerbread is on the forefront?
For example, VPlayer, doesn't work... it FC... How much work is it going to take to get the program back up and running???
Im just asking because, as much as I hate to admit it, fragmentation (as everyone calls it) is going to start causing issues. I get that google wants to offer the best and the latest and greatest, but if everytime a new API get sent out, and devs' have to rewrite their work, how much time is it going to take to get the proggy back up and running??
Thanks!
Theo
theomajigga said:
I am NOT a dev,
Click to expand...
Click to collapse
You should've stop right there.
You realize that at this point only 1(!) phone is running official 2.3 Gingerbread and it's Samsung Nexus S. It's a drop in a bucket comparing to all of the phones that are running official 2.x firmware.
Furthermore, if an app is properly developed against 1.x or 2.x SDK then it will work with gingerbreadas as all APIs are future-compliant. The only problem would be is if an app is developed using 2.3 APIs and you would try to use it on earlier roms or if it used undocumented/unofficial APIs that were not supposed to be used and were discontinued in future releases.
We don't know what 's causing vPlayer not to work, could be many things (kernel, unfinished rom development, missing libs) or it could be things in vPlayer that were improperly implemented.
Send a log to developer and see if he/she can help you. Given that you're not running official (or at least stable!) release, you may not get far though.
But please, don't jump on that "fragmentation" train, it's not nearly as bad as people make it out to be.
borodin1 said:
You should've stop right there.
Click to expand...
Click to collapse
First off, I didn't ask for you to be a ****, if I would have posted this in the dev forum that would have prompted you to respond as such.
borodin1 said:
You realize that at this point only 1(!) phone is running official 2.3 Gingerbread and it's Samsung Nexus S. It's a drop in a bucket comparing to all of the phones that are running official 2.x firmware.
Furthermore, if an app is properly developed against 1.x or 2.x SDK then it will work with gingerbreadas as all APIs are future-compliant. The only problem would be is if an app is developed using 2.3 APIs and you would try to use it on earlier roms or if it used undocumented/unofficial APIs that were not supposed to be used and were discontinued in future releases.
We don't know what 's causing vPlayer not to work, could be many things (kernel, unfinished rom development, missing libs) or it could be things in vPlayer that were improperly implemented.
Send a log to developer and see if he/she can help you. Given that you're not running official (or at least stable!) release, you may not get far though.
Click to expand...
Click to collapse
Thanks for the answer, i guess.
borodin1 said:
But please, don't jump on that "fragmentation" train, it's not nearly as bad as people make it out to be.
Click to expand...
Click to collapse
Now that that is out of the way, can I ask you HOW you can honestly say that Android isn't fragmented. Seriously ask your self... I LOVE android, I really do, G1-cliq-MT3G-Nexus One-HD2(androided)-MT4G, but I can't even lie about that. There is 9 API levels!! 2.3, 2.2, 2.1, 2.0.1, 2.0, 1.6, 1.5, 1.1, 1.0.
NOW I DO UNDERSTAND THAT ALMOST 45% ARE ON 2.2 and 40% ARE ON 2.1.
Ok, so now most apps are going to be working on that 84% of phones running level 7+.
But this ALSO doesn't account for the manufacture API's that are implemented buy some of them, which I KNOW causes some problems. (skype on the Samsung Galaxy Series) just to name one very big one. Skype works on other devices with 2.1, but it doesn't on the Samsung 2.1? as a consumer, I'd ask wtf, even with their limited knowledge of android.
Fragmentation is defined as is the inability to "write once and run anywhere". Rovio complained about this. Albeit not directly, but they said that they were having issues with people on some phones, with some versions of software, and that it wasn't going to work across the board.
I hate to admit it but there are certain things that need to be done to insure that Android will not only be the "Mobile OS" but it will also be the demanded one (IMHO):
1. Cut the bull**** manufacture stuff out, make only ONE set of API's, with 0 proprietary API's. Make it stuff that you can get if you want through the Android Market (custom UI's and such).
2. Control the god-damn market, find spammers, find shady devs re-uploading their apps multiple times to get ad dollars.
3. Get everybody on board to updates, require that all devices with X specifications be updated Y months after a source is released. That will get again get everyone on the same API level, and will make all apps compatible (maybe slow).
4. For the love of all holy, USE THE BEST COMPONENTS YOU CAN FIND! AND MAKE IT A STANDARD At least for the primary functions of the phone. For example, the Nexus One (my fave so far) did NOT have a competent touch screen, 2 point, and a BAD 2 point at that, and that is considered to be the new dev phone. Well who the HELL would want to dev for a platform that can only recognize two points (barely) that doesn't always even get them right? I sure as hell wouldn't. Finally I get the MT4G, the FIRST thing i did was test the touch screen, and guess what... It still is sub-par. 4 points, where my friends Galaxy S can do 6 or something. Now you are going to ask me, who uses 6 points idiot? Some games, do, and to top **** off, if you can't recognize 2 points properly, close together, how can some of the basic multi-touch functions work? (google maps on the N1)
I'm sorry for the rant, but I'm realistic. A mobile platform can't win like this.
http://www.comp.nus.edu.sg/~damithch/df/device-fragmentation.htm
http://www.androidcentral.com/android-30-sdk-preview-2d-3d-graphics-and-dual-core-support-honeycomb
Any one insane enough to try a quick and dirty port?
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
StephanV said:
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
Click to expand...
Click to collapse
They did it with the SDK of Gingerbread, and this one will earn the devs some serious props (and mentions from virtually every tech site, I presume).
That might just be me, though. I'd certainly like to see it happen, no matter how unstable or unusable it might be.
I think the port would be more a case of. LOOK WHAT I CAN DO, then any thing else.
(Have a peek at www.twitter.com/blackal1ce , I'm posting up screenshots from the REALLY slow SDK)
M-en-M said:
They did it with the SDK of Gingerbread, and this one will earn the devs some serious props (and mentions from virtually every tech site, I presume).
That might just be me, though. I'd certainly like to see it happen, no matter how unstable or unusable it might be.
Click to expand...
Click to collapse
They started porting it - as they did with every release before - and got fed up after a while because it's too much effort for something that Google's gonna release a couple of weeks later anyway.
Although the GB SDK port was still majorly flawed, it was at least meant to run on phones with this kind of hardware. Have you seen the previews of Honeycomb? Even if someone did a pretty decent SDK port (which on itself is already quite impossible) it still wouldn't be any good because even our big-ass 4.3" screen is still nothing compared to a tablet. The UI just wouldn't be useable.
And yes I know there's gonna be people willing to give it a shot anyway, and of course that's fine by me, best of luck. Just trying to keep it real here: don't get your hopes up for a somewhat useable port because I don't see that happening before Google decides to put it in AOSP.
StephanV said:
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
Click to expand...
Click to collapse
While I agree you couldn't just compile and run this thing on a HD2, it's not just for tablets. It's optimised to be used on higher resolutions and bigger screens, but will still run fine on phones.
I reckon we'll be seeing ports of this in the near future
No, as of now it really is officially tablet-only, and I'm not talking just about the technical stuff. A tablet OS isn't quite useable on a phone, not because you can't run it, but because it's really hard to use its UI.
I did hear originally that is was tablet only, but I've since heard reports that it's viable for phones as well. You know what t'internet's like. I guess we'll only know when it's actually out proper!
Very good news, waiting to see who's the first want to put their hands dirty
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).
I know we are all waiting for 3.1 but I was wondering if Icecream sandwich will also run on the current honeycomb tablet when it comes out. I have been searching quite a bit on the internet and cant really find an answer to this question. But I bet some people here will know the answer
"Know" the answer, no. Nobody except Google "knows" the answer to that question. HOWEVER, ICS is the unification of tablet and phone versions of Android, designed to run on both platforms, so it's extremely likely it WILL run perfectly fine on the A500.
Assuming Acer release it for us, which they'd better.
I DONT THINK SO,
so if u want that, just pray so bootloader being unlocked ... so dev can make ICS for iconia
interqd said:
I DONT THINK SO,
so if u want that, just pray so bootloader being unlocked ... so dev can make ICS for iconia
Click to expand...
Click to collapse
Why do you say this?
FloatingFatMan is most likely correct with his assessment.
Well, the real question (until unlocked bootloader) isn't so much "can it run" as "will Acer push it out to the A500". The A500 appears to be, at its core, very similar to what we could call a reference Honeycomb design, so unless Google goes out of their way to make things difficult, ICS should be an easy upgrade from HC. It'll come down most likely to device drivers - A500 using a different audio chip, and not certain of whether the mSD card slot is controlled directly from the Tegra2 or another controller chip (if the latter, another driver.)
I'll admit I'll feel a bit better about Acer's commitment to the Android environment if the A501 gets released quickly, and of course even more better when they push 3.1 out, and ecstatic if they'll just unlock the bootloader and get rid of the worry factor entirely.
blazingwolf said:
Why do you say this?
FloatingFatMan is most likely correct with his assessment.
Click to expand...
Click to collapse
its from my past with android device .. my htc desire,
till now official gingerbread not released for it, only the leaks and ports
1 gb ram, dual core 1ghz CPU wat else do u need to run Ice cream sandwitch.
Sent from my A500 using Tapatalk
interqd said:
its from my past with android device .. my htc desire,
till now official gingerbread not released for it, only the leaks and ports
Click to expand...
Click to collapse
so based just of my retired htc evo then it will def be coming my evo had 2.1 ota 2.2 and now an offical ota for 2.3
I'm confused. I have a rooted a500 running Honeycomb 3.2 and I don't think i have a locked bootloader. The rooting process was super simple and i have no problem doing nandroid backups or installing new ROMs.
Am I missing something? Did later/earlier models come with a locked bootloader?
Probably, yes, it's just a matter of time. This is possible in two cases:
1. Google - as they promised - will publish full ICS source code, so we could build it.
2. Google will provide source code to some similar Tegra2 tablet vendor, and we'll rip their binaries and put them on our A500s.
The possibility of at least one of the case happening is quite high.
Bootloader is irrelevant. Even though it's encrypted and has some checks (defeated by itsmagic), it's not locked down to the extent we can't run custom kernels. And the only point of bootloader is to load a proper (i.e. from the correct partition) chunk of code in the memory and run it.
That is, unless Acer will release newer tablet revision with updated firmware (which disallows EUU/nvflash-based downgrades) and locked bootloader. But that'll be different hardware. I know my UID (thus, SBK) and no software upgrades could possible change this, so my tablet is safe.
Im sure our device will support ICS
If not officially from Acer...it will be from our great developer here
trevoryour said:
I'm confused. I have a rooted a500 running Honeycomb 3.2 and I don't think i have a locked bootloader.
Click to expand...
Click to collapse
Technically, it's "locked", but the protection was relatively lax and were defeated by sc2k's itsmagic.
OTA 3.2 upgrade introduced new bootloader, which has stronger protection, but, luckily, we can downgrade back using EUU service software (which is, technically, just an SBK calculator and nvflash).
Google said they were about to publish the source code, "soon"... Let's wait
Okay, so we've already seen Ice Cream Sandwich running on the Nexus S, but that was decidedly... unofficial. We've just heard straight from Google's Gabe Cohen that the Nexus S will definitely be getting ICS. In fact, both he and Matias Duarte think most Gingerbread devices will see an upgrade, saying: "Currently in the process for releasing Ice Cream Sandwich for Nexus S. Theoretically should work for any 2.3 device." It's hardly a surprise and there's no specific word on timing just yet, but hopefully it won't take long to move that vanilla Android device up to something with a breaded exterior.
Click to expand...
Click to collapse
Source : Engaget
So, Theoretically HC could be upgrated in ICS
Wait and see
May be this os is made natively for phone... besides who needs a full new os, a few feature from it will do me good like the swipe to close apps in background, i really like it
jodiac said:
May be this os is made natively for phone... besides who needs a full new os, a few feature from it will do me good like the swipe to close apps in background, i really like it
Click to expand...
Click to collapse
ICS is for both phones and tablets, but looking at its specs one gets the feeling that it just brings HC to the phones much more than improving the HC itself. I just wonder how the phones that are not intended for ICS would handle the UI. Sacrificing screen area for navigation while you have a perfectly good hardware buttons seems stupid.
Sent from my A500 using XDA Premium App
More than likely, Yes
http://www.engadget.com/2011/10/20/asus-says-eee-pad-transformer-tablet-will-get-ics-upgrade-som/
as others have said if ACER does not the dev community will. I have a feeling they are already working on it at acer, my guess is that since google kept 3.0 so walled off they have clear upgrade paths for 3.0 to 4.0 set for all manufactures. 3.0 is the Redheaded stepchild of android versions it exists only because it was required so that we didint have tons of android 2.3 tablets, 4.0 is what 3.0 should of been
tkolev said:
ICS is for both phones and tablets, but looking at its specs one gets the feeling that it just brings HC to the phones much more than improving the HC itself. I just wonder how the phones that are not intended for ICS would handle the UI. Sacrificing screen area for navigation while you have a perfectly good hardware buttons seems stupid.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
much like for Honeycomb now, if you dont like the buttons, with root you can use Honeybar to hide it.
qwertylesh said:
much like for Honeycomb now, if you dont like the buttons, with root you can use Honeybar to hide it.
Click to expand...
Click to collapse
I know you can hide it, the question is if the OEMs will go that way with the older phones which will receive the update or not.
Sent from my A500 using XDA Premium App
tkolev said:
I know you can hide it, the question is if the OEMs will go that way with the older phones which will receive the update or not.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
I am pretty sure the OEMs will be hiding the soft buttons and map them to the hardware buttons instead. It remains to be seen how they implement the context-sensitive soft-button, there's plenty of ways of implementing that and undoubtedly different OEMs will go different ways.