Lead Android developer thinks a 5 month wait for an update is 'very rea


Recommended Posts

Lead Android developer thinks a five-month wait for an update is 'very reasonable'

Jean-Baptiste Queru, technical lead on the Android Open Source Project (AOSP), has revealed his opinion on the current state of the project and the lengthy waits users face for updates. In a Google+ post, Queru congratulates Sony on its Android 4.0 update for the Tablet S and describes the Japanese company as being the biggest contributor to Android, leaving everyone else playing catch-up. By contributing code to the project, Sony should be able to ensure timely updates for its own devices as well as helping out the community at large. So why the long wait for Android 4.0?

Queru actually thinks the five months it took Sony to update the tablet from 3.0 Honeycomb to 4.0 Ice Cream Sandwich is "very reasonable," as the two Android versions are "quite different" under the hood. He also adds that the differences between Gingerbread and Ice Cream Sandwich are huge, and so phone upgrades are likely to take longer. When asked why Asus updated its tablet much faster than Sony, Queru states that Asus worked together with Nvidia. Given the Transformer Prime's status as the flagship Tegra 3 tablet, it comes as no surprise that both parties would throw as many resources as they can at the tablet to ensure a timely update.

What really bothers Queru is that some Google-engineered devices still don't have the latest version of its own OS, thanks to delays in the carrier approval process. He's very glad that Google is back to selling devices directly, and will be "even happier" when he sees the program expanded to more countries.

Source: The Verge

If he agrees that Asus and Nvidia churned out update very fast for Transformer Prime, why the F*** others take so long? Does he know that he is contradicting himself?

nVidia and Asus worked together a lot, most development was parallel. Most other manufacturers don't get access to all needed drivers and HAL-stuff from their SoC-source that fast, and then it obviously takes a while to port all the included apps. That, and most companies (looking at you, Samsung) are just lazy.

Sony and Sony Mobile/Sony Ericsson), as it has been said, contribute a lot of their work to the Android source code, and they have very good developers. They improved memory management on ICS over the "standard" edition, and their software is rock solid. Good job Sony!

Sony Mobile is also the only manufacturer to date that actually completely reskinned their Android interface to match the ICS guidelines. With the 4.0 update (and on the Xperia S) all icons and almost all interface graphics got a major overhaul to fit Holo.

(For the record, Sony tablets are made by the Sony VAIO team, Sony Mobile (/Ericsson) Xperia smartphones are made by the SEMC (Sony (Ericsson) Mobile Communications) team. They work completely independent, but both of them contribute a lot of code to Android. They are slowly merging some development in common areas (mostly media-related such as Bravia Engine, Music Player, ...), but all of that is in a very early stage.)

If he agrees that Asus and Nvidia churned out update very fast for Transformer Prime, why the F*** others take so long? Does he know that he is contradicting himself?

I assume it's because ASUS goes about Android the proper way. They are putting a few apps and widget that are theirs but their Android installation is pretty much stock which makes them updated it very fast. I just got an upgrade on ASUS Transformer 1 to the latest ICS only few days ago. They are super fast.

  • 1 month later...

oh really when's the last time you had a blackberry or Symbian update???

Last month. In fact, at this point my BlackBerry Torch 9860 received more updates than my HTC Legend ever did.

I still loathe BlackBerry OS 7.1 though.

I assume it's because ASUS goes about Android the proper way. They are putting a few apps and widget that are theirs but their Android installation is pretty much stock which makes them updated it very fast. I just got an upgrade on ASUS Transformer 1 to the latest ICS only few days ago. They are super fast.

ASUS just mash together anything and send it out, they released 3 consecutive ICS builds for the TF101 to fix a major random reboot and sleep of death bug present since ICS day 1 and each update made things worse, one of them killed the volume and all of them made the bugs happen more frequently

They obviously either don't test their releases or they couldn't care less and send out useless crap anyway

They got together LOADS of (2) beta testers out of the 40+ that asked to be testers on XDA and then completely ignored them when they reported that the beta update did not fix the bugs, and sent them out to everyone anyway, three times.

Their amazing story they were telling everyone was "We can't replicate it"

How can you not replicate something that is happening to 99% of your customers when you own every revision of the TF101

I swore never to buy asus again after this, my TF101 was a paper weight for most of this year

oh really when's the last time you had a blackberry or Symbian update???

*chirp* * chirp*

The Belle update just came out a few months ago and Carla is due soon, so that's both your points invalidated. (mainly because you didn't bother to research them)

oh really when's the last time you had a blackberry or Symbian update???

Considering Android and Windows Phone are both playing catch up on even basic features, I wouldn't complain much about slow Symbian updates.

It's not so long ago Android people were all "Ooh myyyyy" over tethering. It made me laugh myself to tears.

I'll say it again Android would be soo much better if the adopted the iOS approach to OS updates... F*ck the carrier push it all out, that is... if the vendors get their drivers done in time....

I'll say it again Android would be soo much better if the adopted the iOS approach to OS updates... F*ck the carrier push it all out, that is... if the vendors get their drivers done in time....

That doesn't change anything about different manufacturers slapping on their custom interfaces and stuff.

Android will never be successful unless the versions can be updated quickly amongst different devices. Don't even get me started on it taking the manufacture so long to release their version because it is time consuming. If they would [***Motorola I'm singling you out for my Xyboard***] allow their devices to be unlocked and release their software in open source standards, then we'd have releases within weeks with such groups as Cyanogen.

So no, the guy is a jackass, I think a 5 month rate is very unacceptable.

Considering Android and Windows Phone are both playing catch up on even basic features, I wouldn't complain much about slow Symbian updates.

It's not so long ago Android people were all "Ooh myyyyy" over tethering. It made me laugh myself to tears.

Firstly, you do realise that had little to do with Google and a lot to do with carriers, right? And secondly, what basic features is Android missing?

I'll say it again Android would be soo much better if the adopted the iOS approach to OS updates... F*ck the carrier push it all out, that is... if the vendors get their drivers done in time....

Do you even have a clue how Android works? The code for the OS is pushed into the open source projects, and the developers build and customise it for their devices from source. Google have NO CONTROL over how updates are pushed they just provide the OS. There's no conceivable way for them to forcibly update devices they didn't manufacture.

Android will never be successful unless the versions can be updated quickly amongst different devices. Don't even get me started on it taking the manufacture so long to release their version because it is time consuming. If they would [***Motorola I'm singling you out for my Xyboard***] allow their devices to be unlocked and release their software in open source standards, then we'd have releases within weeks with such groups as Cyanogen.

So no, the guy is a jackass, I think a 5 month rate is very unacceptable.

56% of the smartphone market worldwide says otherwise

Android will never be successful unless the versions can be updated quickly amongst different devices. Don't even get me started on it taking the manufacture so long to release their version because it is time consuming. If they would [***Motorola I'm singling you out for my Xyboard***] allow their devices to be unlocked and release their software in open source standards, then we'd have releases within weeks with such groups as Cyanogen.

So no, the guy is a jackass, I think a 5 month rate is very unacceptable.

You're thinking like a geek and not like an average consumer. The average user won't give a toss about updates if the device already works well for them, most people that I know that have owned iPhones didn't even understand what the software updates were for and i'd wager the situation isn't much different for Android and BB users

It definitely lowers the value of a device.

While I never wait a single minute for an update on my iPhone, I always get all the features for the time that I own my phone. My phone is used at 100% of its potential for all the time that I own it.

On the other hand, on Android, if you?re always 4 months late, it?s like your device is used at 80% of its potential for 12 complete months in its life cycle, if your phone is good for 3 years and a new version is released yearly.

No thanks, Android. You see, deploying software updates right away on every phone is not good. It?s nothing, it?s neutral. But making users wait for updates is completely negative.

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!