Slashdot Mirror


Honeycomb To Require Dual-Core Processor

adeelarshad82 writes "According to managing director of Korean consumer electronics firm Enspert, Google's new Android Honeycomb tablet OS will require a dual-core ARM Cortex-A9 processor to run properly. That means that many existing Android tablets will not be upgradeable to Honeycomb, as they lack the processor necessary to meet the spec. Currently, Nvidia's Tegra 2 platform is the only chipset in products on the market to include a Cortex-A9, although other manufacturers have said they're moving to the new processor architecture for 2011 products."

177 comments

  1. So, system requirements-wise... by Kitanin · · Score: 5, Funny

    Honeycomb's big, yeah yeah yeah, it's not small, no no no?

    --


    Teach your kids: "C++ made baby Jesus cry."
    1. Re:So, system requirements-wise... by MrEricSir · · Score: 0

      Let's go to the Honeycomb Hideout!

      --
      There's no -1 for "I don't get it."
    2. Re:So, system requirements-wise... by Anonymous Coward · · Score: 0

      My Manwich. :(

    3. Re:So, system requirements-wise... by Joce640k · · Score: 1

      Java strikes again...

      --
      No sig today...
  2. Wrong choice by QuantumBeep · · Score: 0

    It doesn't seem right. It's just out of fucking line that a cellphone OS would require a dual-core processor. Somebody needs to trim some bloat.

    1. Re:Wrong choice by Microlith · · Score: 2

      Well hold on here, isn't Honeycomb supposed to be a tablet OS? And since dual core mobile processors are on their way, is it unreasonable to make them a requirement?

      I mean, you can restrict yourself to the capabilities of an ARM11 based processor from six years ago but then all of the performance and technological gains since then would be completely wasted. And if such a processor is your target, don't use an OS made for more capable devices.

      Personally, I want an A9 based device running MeeGo. Something even more open than Android, and more familiar underneath.

    2. Re:Wrong choice by MobileTatsu-NJG · · Score: 1

      You wouldn't want a core dedicted to UI and telephone-related operations?

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    3. Re:Wrong choice by Holi · · Score: 1

      These are not "cell phones", they're small handheld computers with cell phone capability.

      --
      Sorry, teleporters just kill you and then make a copy. A perfect, soul-less copy.
    4. Re:Wrong choice by yuriyg · · Score: 5, Insightful

      No one (well, almost no one) seems to mind when a mobile OS requires a faster processor, but the number of cores is suddenly an issue. Wake up and smell the 21st century. The not-so-recent improvements in performance come from the number of cores and not the clock speed. And it looks like this is the way it's going to be for a while. Get used to it.

    5. Re:Wrong choice by QuantumBeep · · Score: 1

      My point is that the performance requirement progression is pointless, useless, too fast, and stupid. Gingerbread is leaving behind almost every device already on the market.

      That's a lot more forced progression than I'm used to seeing from any OS.

    6. Re:Wrong choice by exomondo · · Score: 1

      It doesn't seem right. It's just out of fucking line that a cellphone OS would require a dual-core processor. Somebody needs to trim some bloat.

      That 'bloat' you speak of is 'applications' and people want to run applications on their devices. People want to run multiple applications on their devices simultaneously so naturally a multi-core CPU is the ideal choice.

      It's funny how some people are so ignorant they just assume that because system requirements go up it means the software is wasting clock cycles. Do you think added stability, security and features all come with no computational cost?

    7. Re:Wrong choice by Lord+Byron+II · · Score: 1

      I don't even see how this is possible. From a processor standpoint, a 1800MHz single core is *roughly* equivalent to a 900MHz dual core. TFA is claiming that Google cares about the chip and not the relative performance? That doesn't make sense.

    8. Re:Wrong choice by exomondo · · Score: 2

      My point is that the performance requirement progression is pointless, useless, too fast, and stupid.

      Why? We want more security, more stability, more responsiveness and more capability...these things don't come free. No-one's forcing you to upgrade so it's moving too fast for you then stick with what you've got.

      Gingerbread is leaving behind almost every device already on the market.

      That's a lot more forced progression than I'm used to seeing from any OS.

      Well firstly it doesn't even have a release date yet and secondly of course at some point the OS will leave most existing devices behind, look at all the problems with the older iPhones running the latest OS, and the original 2G and early iPods don't get it at all. They want to start fresh to provide a consistent user experience and this is the way to accomplish that, seems reasonable since there are already some devices on the market that will support the OS even though the OS doesn't have a release date yet.

    9. Re:Wrong choice by exomondo · · Score: 1

      I don't even see how this is possible. From a processor standpoint, a 1800MHz single core is *roughly* equivalent to a 900MHz dual core.

      Probably going to get better battery life and responsiveness in multitasking since you'll spend less time context switching.

      TFA is claiming that Google cares about the chip and not the relative performance? That doesn't make sense.

      Getting the same performance for the same software out of different chips is very difficult even if they are capable of the same performance. Optimising for a particular instruction set? Optimising the scheduler and power management for multi-core CPUs?

      I don't actually know, i'm just throwing out some guesses.

    10. Re:Wrong choice by mwvdlee · · Score: 1

      I'm just surprised dual-core would be a requirement for any OS. To the best of my knowledge, there has not been an OS (apart perhaps from research OS'es) that require more than a single core.
      Sure, most OS's today can utilize a multitude of cores, but none of them actually need more than one.
      What is it in the architecture of Honeycomb that would necessitate two cores?

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    11. Re:Wrong choice by perryizgr8 · · Score: 1

      i'm not sure about this but i think a computer with two 800Mhz processor cores is much faster than one with a single 1.6Ghz core.

      --
      Wealth is the gift that keeps on giving.
    12. Re:Wrong choice by Narishma · · Score: 1

      The UI doesn't need a core of it own and phone operations are already done on a separate chip in most if not all smartphones.

      --
      Mada mada dane.
    13. Re:Wrong choice by AvitarX · · Score: 1

      Gingerbread is already out.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    14. Re:Wrong choice by GameboyRMH · · Score: 1

      Are they saying it really requires dual cores to run, as in it just won't run on a single core (which sounds like an unholy level of bloat and some seriously bad programming), or are they saying that it requires dual cores in the same way PC software system requirements do, as in "dual core 1Ghz" is a rough estimate of the amount of processing power required to run smoothly?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    15. Re:Wrong choice by Rich0 · · Score: 1

      Well, first, this is nothing new for Android. You could have bought an ADP from Google a week before the N1 was released, and I don't believe it ever received android v2. Ditto for any of the other 1st-gen android phones.

      The only difference now is that a lot more people bought Droids, N1s, and Galaxies, and now they're feeling the pain that all the first-gen owners felt when their platforms came along.

      I wouldn't throw stones at Apple though. While I prefer Android to iOS, the fact remains that Apple has supported old hardware for upwards of three years - FAR longer than anybody has supported Android-based phones. The G1 was finally discontinued in July of 2010 (per wikipedia), and it never got a release beyond v1.6, which dates back to October 2009! So, the first flagship Android phone was supported for negative one years after discontinuance...

    16. Re:Wrong choice by Dr.Dubious+DDQ · · Score: 1

      I'm lusting after a small MeeGo-based device myself, but am rapidly losing hope that Nokia can be convinced to loosen their desperate clinging grip on Symbian long enough to put some actual effort into getting it into actual devices.

      Android's okay (especially if one has a phone for which CyanogenMod is available and can get full root access), but I also would rather have a more traditional and complete Linux environment to play in on my portable devices.

    17. Re:Wrong choice by exomondo · · Score: 1

      Gingerbread is already out.

      Not for all devices yet.

    18. Re:Wrong choice by exomondo · · Score: 1

      The only difference now is that a lot more people bought Droids, N1s, and Galaxies, and now they're feeling the pain that all the first-gen owners felt when their platforms came along.

      How are they 'feeling the pain'? Because of a rumor that a future OS that doesn't even have a release date may not support their devices?

      In any case it's not the makers of Android but the handset manufacturers and carriers that handle the updates, so it isn't an Android problem but a HTC or Samsung or Motorola or Archos...etc... problem.

      I wouldn't throw stones at Apple though. While I prefer Android to iOS, the fact remains that Apple has supported old hardware for upwards of three years - FAR longer than anybody has supported Android-based phones.

      Just because it runs doesn't mean it will run well, there have been heaps of issues with the older 'supported' devices like the 3G and 3GS running the latest OS. There's little point supporting devices that won't run the system well anyway.

    19. Re:Wrong choice by exomondo · · Score: 1

      Gingerbread is already out.

      And on a side note i just assumed QuantumBeep was referring to Honeycomb and not Gingerbread in his post.

    20. Re:Wrong choice by Anonymous Coward · · Score: 0

      architecture? more like marketecture amirite? amirite? uknowimrite...:-D

    21. Re:Wrong choice by Hucko · · Score: 1

      Hmmm... I have a 3G running iOS4.2 and no noticeable problems (I don't play much music, perhaps that a factor). My point is that it seems not all recommendations by manufactures are realistic or universal. Some understate and some overstate. At the end of the day you just have to give it a go.

      I do suggest waiting until the warranty runs out.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  3. Breakfast Cereal Computing. by suso · · Score: 5, Funny

    How many cores will Total require? Probably just 1 right?

    1. Re:Breakfast Cereal Computing. by HelloKitty2 · · Score: 0

      The reason they've put that requirement is because otherwise it will run slow, so instead of making people run it on single-core stuff and receiving bad publicity due to "slowness" complaints, they've just put that artificial requirement. It usually goes that way.

    2. Re:Breakfast Cereal Computing. by Anonymous Coward · · Score: 0

      How many cores will Total require? Probably just 1 right?

      Just wait for Colon Blow. It should be even more efficient.

  4. Just thread it by Gothmolly · · Score: 1

    Be like BeOS, use pervasive multithreading, and those with extra CPUs win, no loss for the older ones. Why REQUIRE it?

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:Just thread it by tepples · · Score: 5, Insightful

      Why REQUIRE [a sufficiently fast CPU]?

      So that people don't blame Google for the molasses performance of a bargain-basement Android device.

    2. Re:Just thread it by izomiac · · Score: 1

      I believe the GP was suggesting that Google optimize their code with newer releases so the hardware requirements remain the same or decrease. Kinda like how Windows 7 runs better on weaker hardware than Vista.

      Realistically, most android applications aren't that complex. Compare something like a BeBox to a modern android phone. The phone will be much less responsive despite far superior hardware. Efficiency in code counts for a lot. OTOH, you can compensate by throwing more hardware at the problem. Of course, I am certain that phone makers welcome the increasing system requirements.

    3. Re:Just thread it by Anonymous Coward · · Score: 0

      So that people don't blame Google for the molasses performance of a bargain-basement Android device.

      Reality check -- Outside of tech circles and places like Slashdot, most people have no idea that Google has anything to do with Android. I doubt most of them understand what Android is.

    4. Re:Just thread it by AmazingRuss · · Score: 1

      The dual core tablets are pretty damn slow and jerky. I can't imagine what the single cores must be like.

  5. Nexus S by teh31337one · · Score: 4, Insightful

    So Google are going to leave their shiny new baby on gingerbread? Yeah... no.

    1. Re:Nexus S by Enderandrew · · Score: 4, Informative

      Where have you seen any announcement that Honeycomb will run on any phones? Everything we've heard is that Honeycomb will have a new interface specifically for tablets.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    2. Re:Nexus S by teh31337one · · Score: 2

      Tablet optimised != tablet specific.

    3. Re:Nexus S by Enderandrew · · Score: 1

      But it isn't a given either that it will run on phones. They mentioned that there will be a new API for developing apps that can run on either, but there might be a new phone version coming out after Honeycomb that includes these improvements.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    4. Re:Nexus S by ouachiski · · Score: 1

      Just to point out this article is about the tablet version. The Nexus S is not a tablet.

      --
      sorry for my comments, I'm drunk
    5. Re:Nexus S by Anonymous Coward · · Score: 0

      I even doubt they'll leave their aging first born in the dust.

    6. Re:Nexus S by victorhooi · · Score: 1

      heya,

      Are you referring to the G1 or the Nexus One...lol...

      Beause the G1 was the first "born" from Google.

      Cheers,
      Victor

    7. Re:Nexus S by exomondo · · Score: 1

      But it isn't a given either that it will run on phones.

      Just like how iOS has tablet and phone versions.

    8. Re:Nexus S by amRadioHed · · Score: 1

      Well, Andy Rubin said it. For what that's worth. See here starting around 6:00.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    9. Re:Nexus S by hitmark · · Score: 1

      android 2.3 hold within it flags for larger screens then 2.2 and earlier had. This allows a app to load custom graphics and such for larger resolutions and screen dimensions, adapting to the larger surface area in the process.

      Hell, there is a demo out there where webos adapts the interface of the email app as the screen size (browser window, as they where using chrome to demo it) changed. Basically it went from a single pane to a 3 pane as the available space got wider.

      I can see something similar be done in android now that the right information is provided to the apps.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    10. Re:Nexus S by Dr.+Spork · · Score: 1

      If Honeycomb were a tablet-only fork of Android, I don't think it would have been given a version name of "2.4" - i.e., the successor of 2.3, which we have on our phones. If it weren't a phone operating system, but a first release of a tablet-only system, it would have a different version number.

    11. Re:Nexus S by Desler · · Score: 1

      Honeycomb does have a different version number...

    12. Re:Nexus S by Rich0 · · Score: 1

      Or at least the ADP, which Google sold directly. It was left in the dust at the same time as the G1, and does not officially support even Eclair, let alone Froyo.

      You could probably have bought an ADP the week before they started selling the N1, too.

      Google so far has shown no reluctance to completely abandon their flagship products.

    13. Re:Nexus S by scotjam · · Score: 1

      No announcement, but Phandroid claim to have a trusted source that confirmed that "Google's going to create a less-capable fork of Honeycomb to work well with low-end tablet devices and mobile handsets" http://phandroid.com/2011/01/03/rumor-honeycomb-to-require-dual-core-processor-hi-def-resolution/

  6. Rumour by ArtDent · · Score: 5, Insightful

    And wasn't it an equally "reliable" source within an OEM that told us about minimum hardware requirements for Gingerbread? What ever happened with that again?

    Oh yeah, it was total bull.

    1. Re:Rumour by Anonymous Coward · · Score: 0

      Hehe! Yes, It was total bull. or ... bit-something... bit-trash, bit-bin or... bit-sh*t,
      or as my article on the aerodynamics of fruit went,
      "Utter Rubbish"

    2. Re:Rumour by mobets · · Score: 1

      Wasn't that back when we thought Gingerbread was going to be 3.0? There was no talk about 2.3 at the time. These new specs aren't too far off from the previous reports for 3.0.

      --

      It was me, I did it, I moved your cheese
    3. Re:Rumour by Anonymous Coward · · Score: 0

      No, just a blog site. Google made a statement that the rumors were junk and no such hardware limits were required for gingerbread, just the usual recommended minimum spec.

    4. Re:Rumour by Anonymous Coward · · Score: 0

      *ding ding ding* We have a winner. You're absolutely right.

    5. Re:Rumour by BatGnat · · Score: 1

      But Google never said Gingerbread was 3.0, it was an assumption made by the community.

  7. My Two Commandments (tablet? anyone?) by e065c8515d206cb0e190 · · Score: 4, Insightful

    If an OS can to take advantage of dual processors it's a good thing.
    If an OS needs a dual processor to function properly it's a bad thing.

    1. Re:My Two Commandments (tablet? anyone?) by Enderandrew · · Score: 5, Interesting

      Google is trying to eliminate the fragmentation that everyone is complaining about, and also trying to reduce the crappy tablets out there giving Android a bad name.

      By setting the minimum bar for Honeycomb at a dual-core A9 they can guarantee a certain experience and consistency for all the apps. They can probably also move to hardware acceleration for composite effects, which they can't do for all the Android cell phone hardware out there.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    2. Re:My Two Commandments (tablet? anyone?) by markdavis · · Score: 2

      They would not do it by something as asinine as dictating the NUMBER OF CORES. They might put out a guideline about total CPU & GPU power recommended, however.

      But do you really think their brand new Nexus S reference phone is going to be stuck on 2.3 because it is "only" one core? I seriously doubt it.

      Finally, much of what makes most of the tablets out there crappy is just plain bad and cheap design and support. Slow CPU is not the highest on the list of what makes things like Pandigital "crappy". It is things like being released with ancient versions of Android that have been mucked up. Then lack of Android Market. And resistive screens. Poor build quality. Lack of documentation. Missing basic features (camera, accelerometer, jacks), etc, etc. None of those will be a problem for the NICE tablets coming out over the next few months from names like HTC, Motorola, Asus ...

    3. Re:My Two Commandments (tablet? anyone?) by symbolic · · Score: 1

      Absolutely - this really kinda ticks me off - I just paid $600 for a tablet that has been effectively dead-ended. I wonder how many of the original customers they screwed on the first round will feel like bending over to take another jab when they fork out another $600 to upgrade their OS. What a freaking waste.

    4. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 2

      Google is trying to eliminate the fragmentation that everyone is complaining about, and also trying to reduce the crappy tablets out there giving Android a bad name.

      And that's a fantastic thing to do, just like MS is doing with WP7, it provides a consistent experience as the developer intended.

    5. Re:My Two Commandments (tablet? anyone?) by Lord+Byron+II · · Score: 4, Interesting

      Why would this tick you off? Did the manufacturer promise you that Honeycomb would run on it? If so, then you have a right to complain. But realistically, you should buy a phone or tablet because of the features it has today, not because of the features it may have tomorrow or next week.

      This whole "more features later" promise BS is how we got stuck with Patch Tuesdays. Microsoft sold us a buggy OS and we knew it was buggy, but we bought anyway, because of the promise that they would fix it later.

      The expectation should be that your $600 tablet does, out-of-the-box, at least $600 worth of stuff. If it happens to run Honeycomb or some other OS later on, then that's a great bonus for you.

    6. Re:My Two Commandments (tablet? anyone?) by citizenr · · Score: 2

      Google is trying to eliminate the fragmentation that everyone is complaining about, and also trying to reduce the crappy tablets out there giving Android a bad name.

      That, or lack of GPU accelerated GUI realistically requires two cores to deliver smooth experience.

      --
      Who logs in to gdm? Not I, said the duck.
    7. Re:My Two Commandments (tablet? anyone?) by samkass · · Score: 0

      The expectation should be that your $600 tablet does, out-of-the-box, at least $600 worth of stuff. If it happens to run Honeycomb or some other OS later on, then that's a great bonus for you.

      That's all well and good, but the 800lb gorilla in the tablet room is Apple and they've set higher expectations. The last major iPad OS upgrade was free for all iPad owners and capable of running on current hardware, and it's likely the next one will be as well. At this point, the "expectation" of any Android device should be that it competes well against the alternatives on the market.

      --
      E pluribus unum
    8. Re:My Two Commandments (tablet? anyone?) by symbolic · · Score: 1

      That model doesn't work for me. $600 is way to much to be spending on a mobile device with such a limited scope. I can get a good laptop for that kind of money.

    9. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 2

      Absolutely - this really kinda ticks me off - I just paid $600 for a tablet that has been effectively dead-ended. I wonder how many of the original customers they screwed on the first round will feel like bending over to take another jab when they fork out another $600 to upgrade their OS. What a freaking waste.

      But Android is open source, isn't that the beauty of it? Also you'll still upgrade to Gingerbread and who knows if there'll be a 2.4 so it's hardly 'dead-ended'. I mean Honeycomb doesn't even have a release date yet!

    10. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 1

      The last major iPad OS upgrade was free for all iPad owners and capable of running on current hardware, and it's likely the next one will be as well.

      Gingerbread for Android tablet owners is a free upgrade too. In fact many Android tablets have gone through more free OS updates than the iPad.

    11. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 1

      That model doesn't work for me. $600 is way to much to be spending on a mobile device with such a limited scope. I can get a good laptop for that kind of money.

      So you bought it under the expectation that it would be able to upgrade for how many releases? Or for how long? I mean this doesn't affect the lifespan of the device or anything.

    12. Re:My Two Commandments (tablet? anyone?) by SJ · · Score: 1

      But but but...

      I thought having no single company control the whole product was supposed to be a good thing. Do you mean to say that there are advantages in having one company make both the hardware AND the software?

      Well, I'll be a monkeys uncle.

    13. Re:My Two Commandments (tablet? anyone?) by grumpyman · · Score: 1

      I'm not trying to troll but why doesn't iPad require to set a minimum bar of a dual core CPU? Ok they have one branch of OS and one manufacturer but the fact is, how would setting that minimum bar of dual core guarantee a certain experience and consistency of apps? Why not at 800MHz single core? Why not quad core?

    14. Re:My Two Commandments (tablet? anyone?) by FatAlb3rt · · Score: 1

      Didn't Mr. Gates allegedly say something similar? One core should be enough for any OS.

    15. Re:My Two Commandments (tablet? anyone?) by Rich0 · · Score: 1

      Open source does you no good if your hardware is locked down so that you can't actually install anything. Also, just because a user community CAN exist doesn't release vendors from the responsibility to support their products. Imagine if Dell sold you a computer and two months later the next windows update didn't run on it? Do you think that they would say, "well, just keep running your unpatched version of windows - after all you bought it for what it did at the time, flaws and all."

      Now, vendors have generally botched their hardware lockdowns so that jailbreaks exist for almost everything. However, it was NEVER the intent of those vendors to allow modded firmware - the INTENT of the vendors is that your device runs the version of the OS they release. So, the ability of customers to circumvent the vendor incompetence doesn't excuse it.

    16. Re:My Two Commandments (tablet? anyone?) by GooberToo · · Score: 1

      They can probably also move to hardware acceleration for composite effects

      They specifically want software compositing. I've even read threads where the core Android devs are flipped with a third party developer who didn't realize it was on purpose (as in a designed "feature") and even offered to re-write that portion of Android so as to allow for proper GPU sanity. The developer had even made some modest changes in his own code base which showed massive speed ups.

      Even in recent reads, they show absolutely no sign of ever wanting to move away from software compositing. If they ever move away from software compositing, its because someone smart, who is now empowered, is in a position to make such changes.

    17. Re:My Two Commandments (tablet? anyone?) by bonch · · Score: 1

      They're trying to eliminate fragmentation by creating another development target for Android developers?

    18. Re:My Two Commandments (tablet? anyone?) by Enderandrew · · Score: 1

      They specifically want software compositing on current builds designed to be compatible with tons of different phones.

      When they demonstrated Honeycomb, they specifically bragged about using the Nvidia Tegra 2 processor for effects.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    19. Re:My Two Commandments (tablet? anyone?) by GooberToo · · Score: 1

      And was that using an OpenGL interface or the standard interface? That's been the party line all along. For the standard interface it will use software compositing. For higher end phones, which has a custom interface, they'll use OpenGL and benefit from GPU acceleration.

      That's why you see so many custom interfaces for Android from different manufacturers - so as to better expose their underlying hardware capabilities. It may very well be that for tablet computers, they have an alternate, OpenGL interface which leverages GPU capabilities. Frankly, I wouldn't be the least bit surprised given that one of the comments I read from a core Android developer was actually fairly recently - and it seemed to indicate software compositing was not going anywhere any time soon.

    20. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 1

      That all depends on which vendor you've chosen to go with, not all vendors have included hardware lockdowns.

    21. Re:My Two Commandments (tablet? anyone?) by Rich0 · · Score: 1

      True. Exactly one Android vendor has not. So, people are free to obtain the benefits of the open-source android platform as long as you disregard about 98% of the android devices out there...

    22. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 1

      True. Exactly one Android vendor has not. So, people are free to obtain the benefits of the open-source android platform as long as you disregard about 98% of the android devices out there...

      Well im not sure about your percentage figure but that's partially true. You can put an unofficial version of android on if you either go to the source and buy your hardware there, or take the unofficial - but perfectly legal - option of rooting the device which is not unreasonable given you are intending on using an unofficial OS then anyway.

      There are obvious dangers to have phones come pre-rooted so most manufacturers wont do it out of the box and some will make it quite difficult to get root access.

      In any case it's going to be an unofficial route to an unofficial result.

    23. Re:My Two Commandments (tablet? anyone?) by Rich0 · · Score: 1

      So, my point is that vendors are dropping the ball. The fact that android is open source doesn't negate the fact that vendors are dropping the ball. It might if the vendors didn't go out of their way to keep you from jailbreaking your phone.

      You do realize that there is no guarantee that in 2011 a phone won't come out that never gets jailbroken, or not in any reasonable period of time, right?

      My point is that most Android phones do not get good long-term OS support - certainly not compared to Apple. I don't think that this is appropriate considering their price.

    24. Re:My Two Commandments (tablet? anyone?) by exomondo · · Score: 1

      You do realize that there is no guarantee that in 2011 a phone won't come out that never gets jailbroken, or not in any reasonable period of time, right?

      There's also no guarantee that a company like synapse phone won't take off providing pre-rooted devices as well. And as far as a 'phone that never gets jailbroken' is concerned, if such a device were to ever come out it's just as likely to face competition from breakable devices, that's the beauty of android, you don't have to stick with one vendor. And given the rate at which devices are jailbroken it's seems extremely unlikely we'll see an unbreakable phone anytime in the near future. Look at how hard Apple work at it on just one device and their best efforts are knocked over in a matter of hours.

      My point is that most Android phones do not get good long-term OS support - certainly not compared to Apple. I don't think that this is appropriate considering their price.

      And my point is the consumers get the choice of which vendor to go with. It's becoming clearer which vendors are offering better support over time and if you want you still have the choice to go with something like a Nexus.

      If you want official support then choose a vendor with a good track record or go with a Nexus, otherwise go the unofficial route.

      And in terms of good long term support Apple's iOS4 hasn't been much of a success for devices more than 18months old. Sure those users can jailbreak, but they still can't do anything about improving the OS.

  8. Java overhead by whiteboy86 · · Score: 1, Insightful

    Pretty much everything that is called through Java bindings shows up in profiles. One wonders what is the purpose of that language? Why is such a slow platform enforced in Android-OS in the first place ? You know the low-power, low-performance mobile platform. Smart operating systems sure can run without Java, see iOS or Bada. And then there is the dreaded "automatic garbage collector" that is always kicking in and stalls the entire system when you least need it -- no wonder Google needs another core to tame such a lousy system.

    1. Re:Java overhead by mswhippingboy · · Score: 4, Informative

      Sorry, but you need to update your arguments.
      Java is NOT slow and hasn't been for quite some time - that argument is so old it's not worth discussing anymore.

      Most benchmarks put it ahead of other languages (with the exception of C and C++ to a lesser extent).

      In terms of performance it's well ahead of Objective-C due to the overhead of it's dynamic dispatching (oh, and Objective-C 2 now has GC as well - it's about time).

      http://www.javarants.com/2010/05/26/android-dalvik-vm-performance-is-a-threat-to-the-iphone/

      The current crop of 1Ghz Android phones are every bit as fast and responsive as the iPhone4 (with it's 1Gz A4 CPU - essentially a custom Cortex-A8) so your fanbois argument just doesn't pass the smell test. Rumors are that the iPad2 and iPhone5 will ship with dual-code A4 cpus (based on the Cortex-A9), so if iOS and Objective-C are so much more efficient why does it need dual-core? It's needs it to compete against the flood of dual-core devices that will be coming in 2011 and it will need the horsepower to stave off the attack from Android which IMHO, has already surpased the iPhone in terms of features as well as usability (and I'm an iPhone user - for now).

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    2. Re:Java overhead by c0lo · · Score: 1

      Why is such a slow platform enforced in Android-OS in the first place ? You know the low-power, low-performance mobile platform.
      no wonder Google needs another core to tame such a lousy system

      Huh, why complain?! This is an opportunity for you my friend. Fork Android, come with another dev medium/language, make it faster and reap the benefits.

      --
      Questions raise, answers kill. Raise questions to stay alive.
    3. Re:Java overhead by exomondo · · Score: 1

      http://www.javarants.com/2010/05/26/android-dalvik-vm-performance-is-a-threat-to-the-iphone/

      Im not disagreeing with you, personally i don't really have an opinion on java performance as I rarely use it and where I see it is in places that you can't isolate Java as being the cause of a performance bottleneck. But it occurs to me that the linked article seems to compare message passing in objective-c to function calls in java, which isn't really a fair comparison and the overhead should be pretty low since the dynamic lookup should only occur once per method after which it should be a hash lookup, which is quite fast.

    4. Re:Java overhead by whiteboy86 · · Score: 3

      Java might be fast enough for your fancy calendar app, but seriously, we need to access NEON the SIMD ARM extensions directly on the CPU to get some decent speed, because the hardware itself is still slow even the A8 Cortex is far underpowered, and do not want to wait hundreds of cycles for Java binding to even start. Java is a nightmare to code mission critical real-time applications and professional grade games. Java should be optional, nobody serious would even consider it then. GC and "managed code" was Sun's marketing ploy to deceive those exec fools to believe that Java is somewhat better then anything else, it looks like many still drink the Sun stirred Java coolaid here.

      Objective-C is in the same slow lane league as Java, it is intended for weekend code warriors and calendar app coders. Our iPhone apps, surprise, do not use ObjC at all (except for some tiny binding code snippets).

    5. Re:Java overhead by Anonymous Coward · · Score: 1

      Then program in C and stop complaining:
      http://developer.android.com/sdk/ndk/index.html

    6. Re:Java overhead by terminal.dk · · Score: 1

      Have you used the Galaxy Tab ? It's hardware is supposedly no worse than the iPad, yet the GUI seems sluggish and in a very different league that the iPad, which even has higher screen res.

      Android, given that it started out as a mobile OS shuld be way faster and smoother. Apple is just using an adaption of an old resource hog of a Desktop OS, but still performs way better than Android.

    7. Re:Java overhead by Joce640k · · Score: 1

      It's not slow in microbenchmarks, sure, but performance in real applications? Not there.

      There's a reason there's no desktop apps written in Java ...

      --
      No sig today...
    8. Re:Java overhead by Anonymous Coward · · Score: 0

      Oh, nevermind Java in general, but Dalvik is certainly pretty slow, even after Froyo's 2-5x speedup. Heck, there are 300MHz J2ME devices that crunch numbers faster than newest androids.

    9. Re:Java overhead by Anonymous Coward · · Score: 0

      According to your own link, "Froyo" introduced a 2-5 speedup. So how can it be true that "Java has not been slow for quite some time?" Presumably Java was 2-5 times slower on Android as recently as...whatever the hell was before Froyo!

      But that's beside the point, as it was a very technically deficient article. The real point is this: the current crop of Android phones are not as responsive as the iPhone 4. Android has a stuttery UI, in large part because of the pauses introduced by the garbage collector. This is a very well known problem on Android and a direct result of their choice to use Java.

    10. Re:Java overhead by Vectormatic · · Score: 1

      i just want to point out that android does NOT run java.

      When you write an android app, it gets compiled into dalvik bytecode, and any android phone only has a dalvik virtual machine. The way the app runs on the phone has nothing to do with the actual java VM

      --
      People, what a bunch of bastards
    11. Re:Java overhead by hitmark · · Score: 2

      well the VM used in android is a custom one (dalvik), 2.2 introduced JIT (with noticeable speed improvements vs 2.1).

      And if one really want speed, Google do provide a NDK so that one can compile parts as ARM code (basically having them sit as ARMv5, v6 and/or v7 libs in the APK).

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    12. Re:Java overhead by Anonymous Coward · · Score: 2, Informative

      http://shootout.alioth.debian.org/u64/which-programming-languages-are-fastest.php

      Java is very very fast, though its main performance problem is memory usage:
      6x more memory usage than C
      5x more memory usage than Go
      2x more memory usage than C#

    13. Re:Java overhead by lehphyro · · Score: 1

      real-time applications

      I don't think it means what you think it means.

    14. Re:Java overhead by lehphyro · · Score: 1

      direct result of their choice to use Java

      No, it's a direct result of their choice to implement their own Java VM. Sun has been developing theirs for 20 years now, why not use that? The HotSpot beats C in many benchmarks already.

    15. Re:Java overhead by Desler · · Score: 1

      You mean still having your code run within the VM so it's still slower than it should be?

    16. Re:Java overhead by Desler · · Score: 1

      The HotSpot beats C in many benchmarks already.

      So is claimed but hardly ever backed up in anything but highly contrived examples that use poorly optimized C code.

    17. Re:Java overhead by mswhippingboy · · Score: 1

      Unfortunately, large portions of iOS including libraries are ObjC so there is no getting around it.

      As far as you objection to GC, that horse has already left the barn. GC is everywhere (.Net, JVM and in ObjC2). With multiple cores, incremental collection and other improvements in the GC algorithms the GC "pause" is hardly noticeable anymore. For truly time-critical portions of code there is the NDK. Besides, the JIT in android is fairly new and has a long way to go to catch up with that in a desktop/server JVM but will no doubt get there.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    18. Re:Java overhead by AmazingRuss · · Score: 1

      "The current crop of 1Ghz Android phones are every bit as fast and responsive as the iPhone4 (with it's 1Gz A4 CPU - essentially a custom Cortex-A8) "

      Bull. Fucking. Shit.

      They have the hardware, but the UI is glitchy, jerky, and responds to touch very unevenly.

    19. Re:Java overhead by Rich0 · · Score: 1

      That is my observation as well. I have a memory-challenged system running Gentoo, and I can build just about anything I like without much issue (chromium does challenge it, but not horribly). However, if I try to build android it just utterly kills the system. The culprit? Java. The android build system uses quite a bit of it, and it gobs down VM by the gigabyte.

      I also have ulimits set to limit process VM. That NEVER causes me problems, except when I run java apps. If I run anything in Java I have to release the ulimit or it dies after about two seconds.

      Sure, "RAM is cheap" and all that, but all things considered it is still a waste of money that could be spent on something else, and that RAM is very useful for disk cache when it isn't loaded up with whatever the VM does with it.

    20. Re:Java overhead by Anonymous Coward · · Score: 0

      Objective C message dispatching is slower than C++ member calls, but it's hardly slow. The NextStation ran at 25Mhz (33 Mhz for turbo). Objective C was plenty fast then and it's plenty, though fast now, 20 years and 200x faster. Java's a turd, though.

    21. Re:Java overhead by mswhippingboy · · Score: 1

      The android team did not have the luxury of gigabytes of memory. They had to re-invent many parts of the JVM when they created Dalvik. The hostspot technology trades off memory utilization for speed in many cases. Originally Android was built assuming very minimal resources (something like 128mb memory, 350mhz cpu, etc). These resource constraints prohibited full implementation of the JVM. This is easing somewhat now with 1Ghz processors and 512Mb ram as well as the JIT technology in Dalvik maturing.

      Interestingly, Oracle ran some benchmarks of their JavaMe platform against Android and JavaMe came out about 2.5 times faster. My guess this is mostly due to the maturity of the the Oracle JVM over android, but I expect the gap to close over time.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    22. Re:Java overhead by lehphyro · · Score: 1
      MIDP 1.0 was designed for even less system resources (32KB for the Heap). Are you referring to this benchmark? http://blogs.oracle.com/javaseembedded/2010/11/how_does_android_22s_performance_stack_up_against_java_se_embedded.html It's not JavaME, it's JavaSE embedded. I hope Oracle forces Google to use it instead of Dalvik.

      I expect the gap to close over time

      Me too, but it'll take a LONG time...

    23. Re:Java overhead by mswhippingboy · · Score: 1

      Yes, that's the story I was referring to - sorry I misstated it - you're correct that it was SE and not ME.

      Personally, I hope Oracle loses that fight and allows Android to go their own way. Oracle can always revamp their ailing JavaME platform and try to compete in this space. The more competition the better as this will force everyone to innovate and continue to advance.

      As far as how long it will take - I'm not sure. Dalvik may not perform as well as the JVM now, but as I noted, it was designed to run in a highly resource constrained environment and while the JVM may be faster in a particular benchmark, it's unclear whether a full implementation of a Mobile OS stack based on JavaSE could even be created to fit within the constraints of these systems (which is why JavaME is a subset of JavaSE functionality rather than a superset).

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    24. Re:Java overhead by ne0n · · Score: 1

      Hey... just to inject a bit of truth into this debate. I've got an ancient 2007-era iPhone and a Samsung Galaxy S, and the iPhone is smoother in many ways. Android just isn't as polished, smooth, seamless, no matter how much we might wish it were so. Noticeable pauses when scrolling, the hiccups in screen animations, but I put up with it since the alternative is living in Steve Jobs' pocket using Steve-provided apps and subsisting on Jobs' own precious Koolaidapps. Same for iPad vs Galaxy Tab; it doesn't match up perfectly, though Froyo is 85% as seamless as iOS4.

      For the record, I haven't used the iPhone since August when I got the SGS but I'm pretty sure the hardware in that first-gen iPhone is crap compared to the SGS 1GHz hummingbird, 512MB etc etc.

      Reasons to keep Android: once you try those extra buttons you'll never want to go back; unlock stays unlocked; no more hanging on iPhone dev team's every twitter; install CM eventually :)

      --
      $ :(){ :|:& };:
  9. If that's true... by romanval · · Score: 1

    I'm not sure if that's in the best interest of tablet devices, which are generally used for basic content consumption (with light data input) or casual gaming.

    It's not like you can swap out a motherboard/CPU/RAM and upgrade it incrementally (like the DIY PC crowd); the end user will constantly have to buy a whole new tablet in order to stay current with the next generation touch-OS.

    Maybe that's the plan after all.. since it would be in the manufaturer's interest to make all of them all final devices that are hardly upgradeable so it'll force to users to shell out $500 every 18 months or so.

  10. Handheld computers that aren't phones by tepples · · Score: 2

    But is there a market for small handheld computers without cell phone capability? Google doesn't seem to think so, or it'd have licensed the Android Market application to Archos.

    1. Re:Handheld computers that aren't phones by Holi · · Score: 1

      It's not the phone capability, it' the cell data network. Adding voice capabilities is easy and limits the number of devices you have to carry.

      --
      Sorry, teleporters just kill you and then make a copy. A perfect, soul-less copy.
    2. Re:Handheld computers that aren't phones by Kitkoan · · Score: 1

      But is there a market for small handheld computers without cell phone capability? Google doesn't seem to think so, or it'd have licensed the Android Market application to Archos.

      May I introduce you to the Samsung Galaxy Tab?

      --
      Attention... all grammer nazi"s! Is they're anything; wrong with: my post,
    3. Re:Handheld computers that aren't phones by bfree · · Score: 1

      I was going to reply that the Galaxy Tab is a phone ... but according to wikipedia that's only true everywhere except in the USA.

      --

      Never underestimate the dark side of the Source

    4. Re:Handheld computers that aren't phones by Kitkoan · · Score: 1

      It doesn't say it's a phone. It says it "supports phone functionality (as speaker phone, via provided wired ear piece or Bluetooth earpieces.)" Thats like claiming my laptop is a phone as it can do that too as either a speaker phone-only function or buying the extra bits. A phone has typically been something you can hold to your ear, but the Galaxy Tab isn't designed for such a functional use.

      --
      Attention... all grammer nazi"s! Is they're anything; wrong with: my post,
    5. Re:Handheld computers that aren't phones by exomondo · · Score: 1

      It says it "supports phone functionality (as speaker phone, via provided wired ear piece or Bluetooth earpieces.)"

      Isn't that essentially what the GP wrote " cell phone capability ", as opposed to the Archos tablets?

    6. Re:Handheld computers that aren't phones by steveha · · Score: 2

      But is there a market for small handheld computers without cell phone capability? Google doesn't seem to think so

      Here is my take on things.

      Google announced both Android and ChromeOS. You might ask yourself, "Why do we need both?"

      So far, Google has been saying that Android is a "phone OS" and ChromeOS is a "device OS". Google has also said that Android is "not really designed" for tablets.

      So it looks to me like Google is trying to artificially segment the market, and is using the one tool they really have, Android Market, to try to enforce their idea that Android is only a "phone OS". This is to encourage the uptake of ChromeOS. But ChromeOS isn't ready and isn't compelling, so device makers are pushing hard to just use Android. And in several cases, they are doing so even if it means they have to put up their own app store!

      This is hurting Android and it is therefore hurting Google. And I really don't see any payoff that compensates. I cannot think of any logical reason for this.

      Meanwhile, I have read up on ChromeOS and I still can't figure out why I would want it. It's Linux, but set up to discourage me from using local storage? Huh? Device makers don't want it and I don't want it. Who wants it?

      I expect that Google is going to change the policy, probably with Honeycomb. I predict that the official Honeycomb will not require a phone capability.

      Also, I have read that the nVidia Tegra 2 is going to be the reference platform for Honeycomb. We can expect to see many tablets using it. I consider that an 8-core chip, but most of the cores are special-purpose; the general-purpose cores are a pair of Cortex A9 cores at 1GHz (which is why many articles call the Tegra 2 a "dual-core" chip). One of the special-purpose cores is a 3D accelerator; I'm hoping that Honeycomb will be able to go direct to that hardware for top performance.

      I really want a small, light device with a Tegra 2 and a Pixel Qi screen. It should be dramatically faster than the current iPad, better in bright light, and potentially have longer battery life.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    7. Re:Handheld computers that aren't phones by oakgrove · · Score: 3, Interesting

      Heh, I use my tab as a phone everyday. And hold it right up to my ear like, "What?". I just run skype and google voice and away I go. The speaker at the bottom turned down is no louder than a phone earpiece and the mic is conveniently located right on the side. All this for 20 bucks a month for data and ~5 for skype number. And it makes a great machine to make posts on Slashdot talking about it to boot!

      --
      The soylentnews experiment has been a dismal failure.
    8. Re:Handheld computers that aren't phones by Joce640k · · Score: 1

      What use is a small handheld computer without Internet connection?

      I mean, yeah, there'll be a bunch of basement dwellers who can think of something but that's probably not a viable business for anybody.

      --
      No sig today...
    9. Re:Handheld computers that aren't phones by Anonymous Coward · · Score: 0

      But is there a market for small handheld computers without cell phone capability? Google doesn't seem to think so, or it'd have licensed the Android Market application to Archos.

      I think you need to look up Samsungs new Galaxy Player -- it has the full market and no cell phone capability.

      You're welcome.

    10. Re:Handheld computers that aren't phones by nyctopterus · · Score: 1

      The iPod Touch would argue: yes.

    11. Re:Handheld computers that aren't phones by tepples · · Score: 1

      All this for 20 bucks a month for data and ~5 for skype number.

      Do the U.S. carriers even let one get data service for such a device without voice service at that price?

    12. Re:Handheld computers that aren't phones by tepples · · Score: 1

      Then why hasn't Google been more proactive in licensing the Market to makers of competitors to the iPod touch?

    13. Re:Handheld computers that aren't phones by oakgrove · · Score: 1

      That's part of the appeal of the Tab. As far as I know, it's the very first device anywhere near the form factor of a phone that allows data without voice so affordably. I'm actually glad the US version doesn't have voice. If it did, the carriers would probably require it.

      --
      The soylentnews experiment has been a dismal failure.
    14. Re:Handheld computers that aren't phones by camperslo · · Score: 1

      But is there a market for small handheld computers without cell phone capability? Google doesn't seem to think so...

      Apple doing very well with the iPod touch proves there is a market. At first glance one would think that the competitive situation for portable phone-less versions of devices would be similar, but I see several large differences.

      The iPod touch doesn't carry any AT&T-only disadvantage.
      The phone-less devices don't get subsidies.
      The phone-less devices would need retail distribution/space, probably a slower tougher task than working through the phone vendors.
      The iPod touch and iPad are already very well established with a robust well-integrated ecosystem for product, media, and app distribution, and the experience is well polished with aggressive development.
      Some devices are used without a net/data connection, not a situation where Google sells ads.
      There are fewer viable business models since there's no monthly access fee to profit from.

    15. Re:Handheld computers that aren't phones by Zebedeu · · Score: 1

      I think Samsung is about to release some sort of media player version of it's Galaxy S phones.
      Of course, being Samsung, expect customized (read: shit) OS and no updates.

      Or you could go the DIY route and hack an Archos player, or something.

  11. Probably not true by Anonymous Coward · · Score: 2, Interesting

    The source for this is a tablet maker claiming that its competitors' tablets won't be fast enough. So there's an obvious conflict of interest. And anyways, requiring a dual core processor doesn't make any sense; Google isn't stupid, they won't release something that's too slow for the majority of hardware already shipped.

    1. Re:Probably not true by EEPROMS · · Score: 1

      they won't release something that's too slow for the majority of hardware already shipped

      As far as I know Google hasnt given any tablets a thumbs up so from Googles standpoint there is no hardware and what is available is a just a big phone.

    2. Re:Probably not true by bored_engineer · · Score: 1

      This one is one that that gets to use the Android marketplace.

    3. Re:Probably not true by Anonymous Coward · · Score: 0

      They wont release something that is too slow?
      How about if they want to sell new/faster hardware,
      just like Apple Did? Huh?

    4. Re:Probably not true by EEPROMS · · Score: 1

      To be able to use the market you just need an android device with a cellphone data connection, doesn't means google approve of the galaxy tab as being a suitable tablet device (in fact Google have stated that they do not consider the Galaxy Tab as being a tablet but a big phone).

    5. Re:Probably not true by Rich0 · · Score: 1

      They've already released stuff that is too slow for the majority of phones out there. When Android v2 came out, most phones could not support it. Even today almost a quarter of phones don't run v2 yet, and probably never will (though their market share will of course fade away).

      Android has been more than happy to live with the assumption that people throw out $550 smartphones every year or two...

  12. False rumor... move along by markdavis · · Score: 4, Interesting

    This is already been discussed at length on androidcentral. The consensus is that this stupid rumor is false. It makes absolutely no sense to require any particular number of cores to run Android.

    Who is writing this stuff and what is their motive???

    1. Re:False rumor... move along by aristotle-dude · · Score: 2

      This is already been discussed at length on androidcentral. The consensus is that this stupid rumor is false. It makes absolutely no sense to require any particular number of cores to run Android.

      Who is writing this stuff and what is their motive???

      You do realize that androidcentral is not an official google site but rather one run by android fanboys right? I would not consider consensus at a fanboy site to be worth much.

      Given the anecdotal evidence of the poor performance of the UI in current android version from the Dalvik VM when garbage collection occurs, I am not surprised by this rumour at all.

      See:

      http://tech.slashdot.org/article.pl?sid=11/01/04/1756245

      Google needs to work on providing a HAL for graphics acceleration and fix the GC strategy of Dalvik or create a "universal binary" standard for C based development on android if it wants to compete against Windows Phone 7 let alone iOS.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    2. Re:False rumor... move along by brian.swetland · · Score: 3, Informative

      Android has a HAL for GPU integration (we call it gralloc), Gingerbread brings incremental and concurrent GC in Dalvik, and the Gingerbread NDK provides for all-native development options, among other improvements. You're welcome.

      http://android-developers.blogspot.com/2010/12/android-23-platform-and-updated-sdk.html

    3. Re:False rumor... move along by exomondo · · Score: 1

      The consensus is that this stupid rumor is false. It makes absolutely no sense to require any particular number of cores to run Android.

      Or perhaps they are requiring a Cortex A9 instruction set and don't think the 'low power ... into cost sensitive devices' option would suffice?

    4. Re:False rumor... move along by amRadioHed · · Score: 1

      The rumor is just stupid on the face of it. Google would not have just released a phone that could not be upgraded to the next version of the OS, due out just a few months later.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    5. Re:False rumor... move along by Threni · · Score: 1

      > Google needs to work on providing a HAL for graphics acceleration and fix the GC strategy of Dalvik or create a "universal binary" standard for C based development on
      > android if it wants to compete against Windows Phone 7 let alone iOS.

      They're already outselling ios. There's nothing to fix in the GC - you can write stuff to avoid random glitches if you do obvious stuff like stop allocating/freeing memory on then fly. I'm I'm not sure what your problem is with C/C++ on Android - it's already there and it works (should you need it).

    6. Re:False rumor... move along by aristotle-dude · · Score: 1

      Outselling iOS on phones? Not in the most recent quarters and if you compare OS to OS. Not by a long shot. When you combine iPhone, iPod Touch and iPad sales against Android there is no comparison.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    7. Re:False rumor... move along by bill_mcgonigle · · Score: 1

      Who is writing this stuff and what is their motive???

      Somebody with a competing interest who's well-versed in spreading FUD.

      Frankly, I can't imagine who it could be.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    8. Re:False rumor... move along by Anonymous Coward · · Score: 0

      "who is writing this stuff and what is their motive"

      clearly its an anonymous AMD executive as they have the Most to loose in all of this ARM expansion as they dont have any spare cash to buy into any ARM vendors chip licences :D

      and OC they have No real Gfx sway in the ARM/NEON SIMD market place eather with the new MALI T 604 hot on the heals of the 400 coming soon.

    9. Re:False rumor... move along by 4phun · · Score: 1

      Outselling iOS on phones? Not in the most recent quarters and if you compare OS to OS. Not by a long shot. When you combine iPhone, iPod Touch and iPad sales against Android there is no comparison.

      I have mental problem with people trying to compare the market for Android to Apple. It is like comparing the market for Apples to Bananas.

      These are trying to compare the market for just one phone company against almost virtually every other phone company combined. Many of these manufacturers and cellular carriers are the ones that made such a mess out of the Windows Mobile phone market with the piles of crap mixed with a few standouts that were very expensive. Apple changed that with the release of the world changing iPhone and Google is determined to change it back again.

      Android is like buying bananas, they may or may not be ready for use and within a short period they need to be thrown away as they are past perfection and don't last.

      Verizon used to bow to such by allowing Verizon customers to get a discount after about 12 months on a new phone on a two year contract. Verizon indicates this week that will end in less than two weeks with the coming release of the more stable and reliable Verizon iPhone on the Verizon network. New customers buying an Android will have to keep them 22 months before any discount on a new Verizon phone will be available. The days of hardware churn on Verizon are coming to an end in 2011.

  13. And WHICH honeycomb would that be? by Anonymous Coward · · Score: 0

    After a few flippant remarks by a know-nothing, I actually READ THE DOCUMENTATION.
    Imagine that!
    But, Android OS 2.3 Honeycomb does not require a dual core processor and.
    Android OS 3.0 Honeycomb Which the Toshiba pad announced at CES is expected
    Does not *require* a dual core processor but will run much faster with it.

    Hint: Both the 2.3 Honeycomb scheduler and the 3.0 Honeycomb scheduler are very
    good both at task switching, and threading, which runs both well on a single core,
    and very well on a dual core.

    I did email some of the primary core kernel developers about it,
    but have yet to hear back. they.. are ... well... kinda BUSY?

    Real artists ship. Real Pirates SHIP to SHIP.
    Make it so!

    1. Re:And WHICH honeycomb would that be? by exomondo · · Score: 1

      Isn't 2.3 Gingerbread?

  14. Just great... by Born2bwire · · Score: 1

    It used to be that all I needed for Honeycomb was a bowl, a spoon, and some milk. I'm getting sick of the superfluous inflation of requirements.

  15. What about the Battery implications of Dual Core? by dakohli · · Score: 1
    OK, so maybe they will require a dual processor to run Honeycomb on a tablet device. I get that. In order for tablets to compete against iPad they must be smooth, super responsive and sharp looking. The extra processing power will help with that. I get it.

    Now, lets think about the phone side of the fence. The current crop of 1Ghz processor equipped phones are pretty snappy and sharp. I have a Galaxy S phone, and although I had concerns at first about the battery performance, I don't now. But what about when the first dual processors show up in the very small form factors, where space and weight is more of an issue than in a tablet? I am not sure at all that I would sacrifice battery performance for a few extra glitzy perks on the UI. In fact, I switched from a G1 to a 3gs for that very reason. Now, a year later I've picked up the Captivate and it is holding its own in this regard. I really don't want a phone that has to be plugged in every eight hours.

    So, the question I have, is: Would moving to a dual processor negatively affect the batter life of a cellphone? -No Sig Req'd

  16. Sorry to burst your bubble but Java still slow by S3D · · Score: 0

    Specifically on Android (I diIdn't have latest Java experience on PC). Java adequate for non time critical games&buisness applications, but for heavy, real-time calculations, for example computer vision apps, Java just is not acceptable. Attempt to write Comp Vision app on Java make it unusable at all. Even thin java layer like copying data from camera make app unusable in real-time. The same goes for other heavy calc apps, like compressive sensing(started to be used in mobile medical app), speech recognition, etc.

    1. Re:Sorry to burst your bubble but Java still slow by TrancePhreak · · Score: 1

      I was able to do just this at 15fps on the Nexus 1. Before the NDK had debugging I had to debug my code somehow, so I made a java version and ran that (since the code was almost identical). Now, the NDK code is faster, but then again that removes your argument since you can just use the NDK.

      --

      -]Phreak Out[-
    2. Re:Sorry to burst your bubble but Java still slow by S3D · · Score: 1

      Show me your android java markerless tracker running at 15fps ans I believe you. At least video. About NDK - that was argument *for* the use of NDK, as opposite to java.

    3. Re:Sorry to burst your bubble but Java still slow by TrancePhreak · · Score: 1
      Let's address this a small piece at a time.

      Even thin java layer like copying data from camera make app unusable in real-time

      This guy is running a G1, incredibly slow compared with the N1 running froyo. http://nhenze.net/?p=107

      --

      -]Phreak Out[-
  17. How to not reduce fragmentation by SuperKendall · · Score: 2

    Step one: allow a million tablet devices to be released with Android
    Step two: Make a new version of Android for Tablets that runs on none of them and only on a new wave of tablets.
    Step three: Developer making tablet specific software now required to target two classes of devices.
    Step Four: Mu-ha-ha

    So what are you to do now if you are an Android developer? Ignore millions of Galaxy Tab units sold?

    If I were an Android developer I would be THIS PISSED.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:How to not reduce fragmentation by Anonymous Coward · · Score: 0

      Step one: allow a million tablet devices to be released with Android
      Step two: Make a new version of Android for Tablets that runs on none of them and only on a new wave of tablets.
      Step three: Developer making tablet specific software now required to target two classes of devices.

      If I were an Android developer I would be THIS PISSED.

      I just read that with this CES the Android tablet offering are heavily fragmented overnight adding to the fragmentation already overwhelming the phone hardware.

  18. Expectations by SuperKendall · · Score: 1

    Apple's bar is that you get OS upgrades for about three years after buying a device.

    Even if you ignore that bar, saying that a device just released is not getting an update just months later, is pretty harsh.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Expectations by Rich0 · · Score: 1

      Agreed. Android has really dropped the ball on this one. Not supporting devices with new releases is just par for the course for android. Most phones are completely abandoned within a year of initial sale, and only months after they are no longer sold.

      Half of the latest generation phones from last summer aren't even running 2.2 yet. Cyanogen was able to get that working on my G1 - there is no excuse that next-gen phones with several times the RAM/storage aren't running it. The vendors don't even have to reverse-engineer the drivers - they have the full source to the whole thing.

      Everybody keeps saying "buy the phone for what it does now" - but I'm not sure that this is nearly as compelling as the advocates of this approach think. Sure, if the phone were $75 like a feature phone I might not expect updates. However, we're talking about $550 devices (or cheaper up-front if you make various contractual commitments that essentially cost you as much). That is a lot of money to pay for a device that isn't intended to be future-expandable. Existing apps may even lose support when devs target newer APIs, and with data in the cloud there is no guaratee that last year's facebook app version will work next year/etc.

  19. Re:What about the Battery implications of Dual Cor by VortexCortex · · Score: 1

    So, the question I have, is: Would moving to a dual processor negatively affect the batter life of a cellphone?

    Dual cores will likely increase the battery life since one core can be underclocked or disabled when appropriate (saves battery life).

    However, I have no idea how multi-core hardware will affect batter... Hmmm, are you planing a fast food themed competitor to "Will it Blend?"

  20. Seperate 2 and 3 series phones by imaginieus · · Score: 1

    That's close but what Google has been saying for a while is that they are planning to split android into two tracks. The new 3 series track (starting with honeycomb) will be designed to support tablets as well as new "super phones". Existing phones as well as future bargain phones stay on the 2 series track.

    Basically, google is looking to diversify the android platform in order to expand its market appeal. The 2 series phones will be targeted at feature phone customers. The 3 series phones will be the cutting edge iphone competitors.

    Google has never said that honeycomb is only for tablets, just that it will require new hardware.

    1. Re:Seperate 2 and 3 series phones by ArtDent · · Score: 1

      Source please? As was pointed out above, Andy Rubin recently demoed Honeycomb on a tablet and said at that time that it would run on both tablets and phones. You really think he would have said that if Google's about-to-be-released Nexus S wouldn't run it?

      You really want to take random-guy-from-some-Korean-manufacturer-you've-never-heard-of's word over Andy Rubin's?

  21. "Allow"? by Namarrgon · · Score: 1

    Step one: allow a million tablet devices to be released with Android

    Misconceived. Android is open source; Google can't disallow anything except their own (non-open) apps & services like the Android Market (which they have been doing, on almost all released tablets).

    Step two: Make a new version of Android for Tablets that runs on none of them and only on a new wave of tablets.

    A bit like iOS 4 not running on older devices? Anyway, we've only got some random, non-Google suit's claim that this is even the case.

    Step three: Developer making tablet specific software now required to target two classes of devices.

    Hardly. An Android developer need merely target an earlier version of the OS like Froyo or Gingerbread, and their app will run just the same on a Honeycomb tablet.

    Step Four: Mu-ha-ha

    Huh? Is that just there to make Google look evil or something? Are they supposed to be pleased about this hypothetical situation?

    I don't get why you so regularly attack anything non-Apple. Is it just platform insecurity?

    --
    Why would anyone engrave "Elbereth"?
    1. Re:"Allow"? by SuperKendall · · Score: 1

      Misconceived. Android is open source; Google can't disallow anything

      They could lean very heavily on vendors and tell them to wait for the tablet Android.

      A bit like iOS 4 not running on older devices?

      No, because iOS4 runs on devices almost three years old. Android Tablet when it arrives will not run on things an order of magnitude younger.

      their app will run just the same on a Honeycomb tablet.

      So they aren't taking advantage of Honeycomb features then?

      Are they supposed to be pleased about this hypothetical situation?

      They sure don't seem to care because what they DO have control over is minium specs.

      I don't think "pleased" is the right works but it is according to the Google Plan (if it's real, which I'm wondering now).

      I never did buy into the whole "Google is evil" meme that is going around, I still think they are a great company. But making a tablet just out a legacy device, sucks and frankly is some kind of evil.

      I don't get why you so regularly attack anything non-Apple.

      Well if I did that would sure be annoying! I have said repeatedly Android is an excellent platform. What is not excellent is having a few million people buy a Tab and then hanging them out to dry.

      You must be awfully insecure, reading one critique of a single aspect of a platform into a general attack.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    2. Re:"Allow"? by Enderandrew · · Score: 1

      Rumors are that Google has leaned on vendors not to push tablets until Honeycomb is out, which is why most of the current Android tablets are from odd small companies. You'll note that Google hasn't allowed the Android Market on most of them.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    3. Re:"Allow"? by Namarrgon · · Score: 1

      You must be awfully insecure, reading one critique of a single aspect of a platform into a general attack.

      Except that it's hardly one critique, is it? A quick glance over your comment history shows you with multiple comments in virtually every Apple- or Android-related post, pointing out flaws in Android (or Microsoft, Windows etc) and defending flaws in iOS or Apple. These "critiques" seem to make up about 80% of your total comment volume (even your sig is a clue). And you've been doing this for literally years.

      But yeah, this is Slashdot, it gets the same platform wars as the rest of the net, and I'm often guilty of getting into arguments myself. Nonetheless, it's clear that you're pretty quick to leap on the slightest unconfirmed rumour (like this one) to gleefully "critique" anything that might be a threat to your beloved Apple.

      --
      Why would anyone engrave "Elbereth"?
  22. Why REQUIRE it? by Joce640k · · Score: 1

    Because Android will fail if consumers see it as slow/unresponsive. Failure is not an option, so minimum number CPU cycles becomes a mandate.

    --
    No sig today...
    1. Re:Why REQUIRE it? by Anonymous Coward · · Score: 0

      Because Android will fail if consumers see it as slow/unresponsive. Failure is not an option, so minimum number CPU cycles becomes a mandate.

      I have a ton of friends who swear they will never buy another Android. It seems the damn things slow down at the oddest moments like in the middle of playing a video or a game which plays perfectly on the iPhone. Google hasn't bothered to fix a nine month old random SMS bug so I doubt they are in a hurry to fix this random sluggish problem that is ripping people.

      Several have mentioned they feel like victims and would love to join a class action lawsuit to get their money back and damages for deceptive advertising.

      I tell them it is a waste of time just junk the Android or Ebay it, eat the loss and move on!

  23. kinda sorta by LostMyBeaver · · Score: 2

    I hate Apple... to prove it, I don't even run OS X on my Mac Book, I use Windows 7 instead. I have no idea how, but I was resolved not to own an iPad because tablets with telephone operating systems sound really stupid to me, yet, I was given an iPad against my will. I use it as a coffee cup saucer.

    Though, I love my iPhones. My daughter runs iOS 4 on her 3G, my son runs iOS 4 on his 3Gs and my wife and I both have iPhone 4s. They're great devices and the #1 reason I like them is that my daughter's iPhone 3 is still getting Apple love after all this time. I've owned HTC's, Nokia's etc... and the bitch of it is, that when you buy the phone, unless there's a major issue, you are stuck with what you bought. I've worked on Nokia phones (internally with Nokia) and know for a fact that after a phone ships, the least valuable asset on the development team becomes the new support team for that phone.

    Apple at least makes a commitment to their phones for a long enough time that you feel that you weren't just abandoned after purchasing.

    I also have a stack of Android devices. I don't use them. With the exception of the REALLY high end ones, I find them to be clunky as hell. If anything Google needs to set a specific standard requiring a minimum CPU, a minimum GPU (and a minimum set of functions that MUST be hardware accelerated as part of the GPU), a minimum amount of RAM, a minimum performance speed for RAM and Flash, and a minimum screen refresh time.

    By leaving the platform as open as they have, they've made it a joke. It's the "I couldn't afford and iPhone, but this Android thing was affordable, too bad it's not fast enough to run Angry Birds" platform.

    What Google did wrong was this. They waited until after Christmas to hit us with this bomb. It's like "Samsung sold X millions of Galaxy Tablets for Christmas 2010" followed right by "Be ready to by the new Galaxy Tablet in February 2011 since Samsung will not be able to provide support for newer OS versions on the model you got for Christmas".

    So, now either Samsung needs to fork Android and maintain it for a year or so to keep users from being pissed that their $600 Christmas gift to the family is a brick in January. Or Google needs to specifically support the fork themselves. Just imagine how cool you'd be if you got to work on the development team at Google that has to support that shitty old OS that was superseded by something better.

    Let's not forget the thousands of stores around the world that has a stock of these things and they'll sell them and three hours later, the purchaser will come back saying "I just read this thing won't run new software starting in February". What kind of scam are you pulling!

    1. Re:kinda sorta by lp_bugman · · Score: 1

      I hate Apple, to prove it... You buy every single product on their catalog
      You just listed
      iBook x 1
      iPad x 1
      iPhone 3G x 2
      iPhone 4G x 2

      --
      BSD licensed software can't be stolen....
    2. Re:kinda sorta by Zebedeu · · Score: 1

      What Google did wrong was this. They waited until after Christmas to hit us with this bomb. It's like "Samsung sold X millions of Galaxy Tablets for Christmas 2010" followed right by "Be ready to by the new Galaxy Tablet in February 2011 since Samsung will not be able to provide support for newer OS versions on the model you got for Christmas".

      Dude, it's Samsung. You wouldn't get an update even if Google compiled it for them.

  24. Fuck Total! by Anonymous Coward · · Score: 0

    How many cores will Total require? Probably just 1 right?

    Fuck Total!

    Sincerely, the TourettesGuy

  25. Java is faster than Android by ChunderDownunder · · Score: 1

    Java SE embedded vs Android 2.2.
    Perhaps if Larry wins the court case against Android, Google will be forced to license Java and Android will finally get some decent performance by using Hotspot instead of Dalvik! :)
    In any case, these dual core ARM machines are more than powerful enough to run the desktop version for light applications.

  26. Re:What about the Battery implications of Dual Cor by kangsterizer · · Score: 1

    That doesn't make sense. A single core.. guess what.. can be underclocked as well, and there's no second core to turn off, as it doesn't exists. In a perfect (and very simplified) world a single core CPU would use as much or less power than a multi-core of equal technology level.

    However, ARM 9 multi-core CPUs are more power efficient - this means they are "faster" while using less energy than the ARM 8 generation (single core). So in practice, battery life depends on the implementation of the CPU, and ARM 9 dual core CPUs use (average) less power (battery) than the ARM 8 single cores. At least, recent implementations such as the OMAP4 follow that trend.

  27. Nintendo DS: It prints money by tepples · · Score: 1

    What use is a small handheld computer without Internet connection?

    What use was there for a Pocket PC, whose apps could sync to the Internet through Wi-Fi? What use is there for an iPod touch or Nintendo DS?

  28. Where can I try Galaxy Player? by tepples · · Score: 1

    I think you need to look up Samsungs new Galaxy Player -- it has the full market and no cell phone capability.

    I've heard good things about Galaxy Player, but I live in the United States, and I haven't seen one at Best Buy or Sears. On the other hand, Best Buy has a floor model of every iPod, iPhone, and iPad. Where can I try Galaxy Player?

  29. Retail space and ads by tepples · · Score: 1

    The phone-less devices would need retail distribution/space, probably a slower tougher task than working through the phone vendors.

    In other words, unlike Archos and Samsung products, iPod touch rode the coattails of the click-wheel iPod products to establish space on retailers' shelves and a chance for end users to try before buying.

    The iPod touch and iPad are already very well established with a robust well-integrated ecosystem for product, media, and app distribution

    Is Android Market not "a robust well-integrated ecosystem"? If so, then why has Google been so slow to offer it on Android-based Wi-Fi tablets and media players that compete with Apple products?

    Some devices are used without a net/data connection, not a situation where Google sells ads.

    You know, Google can still sell ads for display on devices with intermittent net connections. It could download a new set of ads whenever the device syncs based on the browsing history. Then it could use something like the Read It Later extension for Firefox so that when the user clicks on an ad while offline, the device downloads the landing page at next sync.

    There are fewer viable business models since there's no monthly access fee to profit from.

    No monthly access fee from the users, or from the developers (like Apple's $8.25 per month fee for iPhone developer program access)?

  30. nVidia advert? by TheRaven64 · · Score: 1

    Nvidia's Tegra 2 platform is the only chipset in products on the market to include a Cortex-A9

    Really? Because I'm fairly sure that the PandaBoard is shipping now (and has been for a little while) and includes a TI OMAP4430, a SoC that contains a dual-core ARM Cortex A9 at 1GHz, a PowerVR SGX530 GPU, and a few other things. I've not seen anything actually shipping that includes Tegra 2, although it's been coming Real Soon Now for a year or so.

    --
    I am TheRaven on Soylent News
    1. Re:nVidia advert? by AstroByte · · Score: 1

      I've not seen anything actually shipping that includes Tegra 2, although it's been coming Real Soon Now for a year or so.

      Toshiba's AC100 netbook and Folio 100 tablet both use Tegra 2. The AC100 is definitely available, as I'm using one to type this! It came with Android 2.1 installed, which isn't usable in the netbook form factor. However, I've put Ubuntu onto it and it works OK (I bought it with this intention, I never intended to run Android on it).

    2. Re:nVidia advert? by Mr+Z · · Score: 1

      I had a similar reaction when I saw that comment. Of course, I guess that's understandable, given that I work for TI. ;-)

      Now I just wish I could get a version of my Nokia N900 with a 4430 instead of the 3430 that's in it now. Ah well...

    3. Re:nVidia advert? by TheRaven64 · · Score: 1

      I don't suppose you lend them out to open source developers? I'd love to get proper ARM ABI exception support for Objective-C working, but I don't have an ARM system to work on.

      --
      I am TheRaven on Soylent News
    4. Re:nVidia advert? by Mr+Z · · Score: 1

      I couldn't tell you, since that's not actually my department or platform. I'm working on the C6600 family DSPs, actually. I just heard about the PandaBoard from a coworker just before Christmas.

  31. Fragmentation by bonch · · Score: 1

    Fragmentation? What fragmentation?

    *whistles*

  32. Re:What about the Battery implications of Dual Cor by AmbushBug · · Score: 1

    Yeah, that's initially what I thought. But I read Nvidia's presentation on the Tegra 2 and they claim that there is power savings for various reasons. You can read it
    here (PDF).

  33. Re:What about the Battery implications of Dual Cor by kangsterizer · · Score: 1

    Unfortunately it's more of an advertising paper. It's just another ARM9 as far as I'm concerned, with nvidia extensions (each vendor adds it's extensions - usually just a "own" GPU)

    According to the ARM9 papers (which I'm too lazy to link, sorry :p) most of the efficiency comes from the CPU architecture itself, aka 1 ARM9 core is more efficient than 1 ARM8 core.

    Then both ARM9 cores at middle capacity use less energy than 1 ARM8 core at full capacity.

    Both ARM9 core at full capacity uses still slightly more than 1 ARM8 core (but also is a lot more powerful)

    Eventually, since most really intensive apps use 3D, the GPU will play a big part in really intensive apps anyway, and this part seems to be always different. Some other optimizations depending on the vendor might also make some differences, as well as the software part, yada yada.

  34. vy by ivy23 · · Score: 1

    This year is the year, android ... future technology Natural Health Cures
    Colour Laser Printers