Google Confirms Gingerbread Android OS

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
In its own stylistic way, Google has ‘officially’ confirmed the addition of another Android Operating System by the somewhat unceremonious installation of a giant gingerbread man statue on its campus lawn. One would have to be grateful Google doesn’t make sex toys. :p
 
and I probably won't see it until I upgrade to a new phone next year in September.
 
And I just ordered a new phone today with froyo on it. I don't care, it's a huge upgrade from my old dumb phone.
 
It's kind of sad how long it takes companies like Motorola and Samsung to update their phones. Community tends to have builds out based off of AOSP within a week or so.

Based off of Froyo's launch, we should see the SDK next followed by an update for the Nexus One followed by the release of the source. Anyone care to place a bet on the timeframe for that? I'm running an AOSP-based custom ROM on my Droid, itching for an update :)
 
Gobs of money. What some can do with it. :p

Kinda what I was thinking. If I was a company on the path to taking over the world, large mock-ups of pastries (associated with product launches or not) would be on my list of things to acquire post-haste.

In all seriousness though, I feel sorry for the poor son of a bitch/gallery of cube ants that has their window directly behind that thing.
 
It's kind of sad how long it takes companies like Motorola and Samsung to update their phones. Community tends to have builds out based off of AOSP within a week or so.

I think the sad part is how google made the updating process, rather than having every android phone being able to use the same update, companies like samsung/motorola/htc have to make updates for each and every phone. Imagine if dell/acer/hp/toshiba had to make specific windows updates for each and everyone of their pc's... lunacy i tell ya.
 
I think the sad part is how google made the updating process, rather than having every android phone being able to use the same update, companies like samsung/motorola/htc have to make updates for each and every phone. Imagine if dell/acer/hp/toshiba had to make specific windows updates for each and everyone of their pc's... lunacy i tell ya.


but is that really googles fault? i mean unless you want some insanely bloated OS that has all the hardware drivers for every single phone that uses the android OS.. thats about the only way to allow all the phones to update..
 
It's probably more like a reminder that they need to do a good job on the Gingerbread release...they'll be seeing it every day when going to work.
 
I think the sad part is how google made the updating process, rather than having every android phone being able to use the same update, companies like samsung/motorola/htc have to make updates for each and every phone. Imagine if dell/acer/hp/toshiba had to make specific windows updates for each and everyone of their pc's... lunacy i tell ya.

No, they just need to checkout the source, add their drivers (many of which are in the Android source code), and compile. Then they sign the output with their keys and bam, done and done. The process is very quick - which is why the community is able to do it in hours instead of months. Takes longer to setup the build environment than it does to actually create an update.

Samsung, Motorola, and HTC all need to spend a ton of time updating the crapware they slapped on top of Android (TouchWiz, Sense, Motoblur, etc...), which isn't Google's fault.

Of course, carriers probably aren't helping matters. Who knows how long Verizon sits on an OTA update before it actually gets sent out, for example.

No ones complaining about windows 7, having more files/drivers in memory doesn't make it bloated, just add more memory.

Does Microsoft maintain and update those drivers? Nope. Why should Google? In case you don't know, Linux doesn't have a stable driver ABI or worry about backwards compatibility. Drivers that work with the 2.6.10 kernel might not work with the 2.6.11 kernel, for example. So Google either needs to maintain everyone's drivers (which hardware manufacturers won't like since it means open sourcing everyone's drivers), or they need to go with what they've chosen - only maintain the drivers for some things (such as the N1's stuff)
 
It's kind of sad how long it takes companies like Motorola and Samsung to update their phones. Community tends to have builds out based off of AOSP within a week or so.

Based off of Froyo's launch, we should see the SDK next followed by an update for the Nexus One followed by the release of the source. Anyone care to place a bet on the timeframe for that? I'm running an AOSP-based custom ROM on my Droid, itching for an update :)

I'm already running Froyo on my G1, thanks to cyanogen. I'm just waiting for CM6.1 to come out.

Hacking your phone means you don't have to wait for companies to catch up. Plus, you get apps they normally won't let you have, like tethering.
 
No, they just need to checkout the source, add their drivers (many of which are in the Android source code), and compile. Then they sign the output with their keys and bam, done and done. The process is very quick - which is why the community is able to do it in hours instead of months. Takes longer to setup the build environment than it does to actually create an update.

Samsung, Motorola, and HTC all need to spend a ton of time updating the crapware they slapped on top of Android (TouchWiz, Sense, Motoblur, etc...), which isn't Google's fault.

Of course, carriers probably aren't helping matters. Who knows how long Verizon sits on an OTA update before it actually gets sent out, for example.

I wish Google would have a mandatory OS look. I hate custom UIs. NinjaBlur isn't terrible, but I want a normal Android UI with the Google apps that work and not the horrible, clunky, pieces of crap Motorola thinks are good. Toss on crapware like Amazon MP3 or Blockbuster if it helps keep costs down, but ditch the ugly custom UIs. Or don't lock the damn bootloaders so people can release good ROMs that fix that crap.
 
I'm already running Froyo on my G1, thanks to cyanogen. I'm just waiting for CM6.1 to come out.

Hacking your phone means you don't have to wait for companies to catch up. Plus, you get apps they normally won't let you have, like tethering.

I wish Cyanogen would support the Droid X.
 
I wish Google would have a mandatory OS look. I hate custom UIs. NinjaBlur isn't terrible, but I want a normal Android UI with the Google apps that work and not the horrible, clunky, pieces of crap Motorola thinks are good. Toss on crapware like Amazon MP3 or Blockbuster if it helps keep costs down, but ditch the ugly custom UIs. Or don't lock the damn bootloaders so people can release good ROMs that fix that crap.

Yes, but just because the current UI's are terrible, doesn't mean all future ones will. Recall what TouchFlo3D did for Windows Mobile 6, it single handedly made it almost modern. Give the market time, eventually they'll get it. With the mobile space now a software game just as much as a hardware one, anyone who keeps putting out crap will lost out as customers refuse to buy.

And while even the Nexus One comes with Amazon MP3 installed ( and Twitter too, yuk), that stuff NEEDS to be uninstallable. I really don't want to have to look at it, though with 5-7 homescreens common in today's launchers, maybe I won't have to.
 
I think the sad part is how google made the updating process, rather than having every android phone being able to use the same update, companies like samsung/motorola/htc have to make updates for each and every phone. Imagine if dell/acer/hp/toshiba had to make specific windows updates for each and everyone of their pc's... lunacy i tell ya.

Hm... Did you ever seen Windows Mobile and how they "update" ? Yeah, they had Windows Update built in. But that was all, 0 updates through Windows Update. Imagine if HTC/HP/... had to make specific ROM updates for each and every of their phone models. Wait, they had to :D.
 
tmobile is doing an over the air update by the 31st of the month for 1.6 and later to 2.2
 
Yes, but just because the current UI's are terrible, doesn't mean all future ones will. Recall what TouchFlo3D did for Windows Mobile 6, it single handedly made it almost modern. Give the market time, eventually they'll get it. With the mobile space now a software game just as much as a hardware one, anyone who keeps putting out crap will lost out as customers refuse to buy.

And while even the Nexus One comes with Amazon MP3 installed ( and Twitter too, yuk), that stuff NEEDS to be uninstallable. I really don't want to have to look at it, though with 5-7 homescreens common in today's launchers, maybe I won't have to.

Custom UIs had a place in 1.6 and prior since Google's UI was utterly terrible and didn't have a lot of options. Now that they do, I wish they'd either go away or make it optional. All the custom UI stuff means the updates are delayed when they should be launching day and date with Google's release of them.

To be fair, the Twitter app on the N1 is a Google designed app. I agree that they need to be uninstallable. Rooting helps a lot, but even then there are some apps you simply can't uninstall if you want to keep getting updates. Thats a big bothersome. I wish the custom apps were optional, you could download them if you want and get rid of them at any time without rooting.
 
Back
Top