Google Posts Images, Binaries For New Nexus 7
In the wake of AOSP maintainer Jean-Baptiste Quéru's resignation, there was speculation that there would be no factory images or binary drivers released for Google's new Nexus 7 tablet. Happily, that's not the case — whatever other open source gaps there are in the Android world, Ars reports that those images and binaries have been released for the Nexus 7.
Get an iPad instead, there's more apps and the ecosystem is far far more secure anyway.
I'll take neither. Apple is one of the few companies I trust less than Google.
Every season the usual idiots tell us Google won't release the source and binaries for new, proper Android devices, and every season the usual idiots are proven wrong. Why does Slashdot keep dribbling this same old rubbish?
There is ZERO mystery as to what Android is, or what strategy it is pursuing. Too many cretins who claim some expertise in computing actually don't know the first thing about the subject. Look at all the morons who claim 'protected path' for DRM video rendering in Android somehow "locks the device down". One minute of research explains exactly what the 'protected path' initiative actually is, and how it will NEVER infringe on the ability to decode non-DRM video.
The REAL question about Google's relationship with Android is when they will finally release the DESKTOP version, and provide a free alternative to XP, Vista, Win7, Win8 and all the funny Linux distributions no-one wants to use that way. Most Android hardware is already far better than the first PCs that ran XP. Google merely has to choose a windows interface and shell, and stand behind that choice. The current Android kernel and API sets are already good enough (although they can always be improved for the coming muti-core 64-bit ARM parts).
In the meantime, the new Nexus 7 is a killer tablet that shames Apple, Microsoft, Intel and Nvidia. It projects Qualcomm to the top of the game as the 'new' Intel. And this is before Qualcomm even goes A15 or one of the new 64-bit cores. And worse for Intel, Qualcomm has the leading GPU solution in its space.
Again, for those to thick to get it- Google is NOT going to close source Android. It is NOT going to prevent you from watching your own videos, or reading your own books, regardless of the source or the file format. This would be technically impossible, since by design Android gives apps access to their own rendering surface, just like Windows. Now, if only Google would make the new Android (desktop version) as much like XP on the surface, a true workhorse desktop/laptop OS for people who need to get things done, we could actually move into a true post-Microsoft era.
I am a long time Apple fanboy, really love the iPad. But honestly, I am starting to get annoyed with some missing customizations that Android has had for ages. Not talking themes.
For example: Intents. iOS 6 looked like Apple was headed that way with the way you share pictures or links. However, only a few select companies are integrated with it. I want to be able to add a screenshot right into Evernote. Use a different "read later" provider. I use Chrome on the desktop, which doesn't integrate with iCloud reader. Same thing goes for bookmarks. I use xmarks for syncing across multiple machines and I primarily use Chrome. Xmarks is also awesome for having work profiles. iOS xmarks integration is very limited because of Apple.
Widgets: I can't believe that after all these years of widgets in OS X they haven't brought them over to iOS. It would be very nice to have a dashboard for lets say system status at work. I don't want anything too abusive on system resources, but allowing one of these widgets to update in the background or via notifications would be awesome.
I was honestly considering picking up a Nexus 7 once the LTE version is announced. The announcement of factory images for the Nexus 7 has sealed the deal for me. Will I customize it to that level ? Not sure. But I would like the option.
until (succeed) try { again(); }
Oh why am I responding to this? Dumb I guess.
The whoie thing about Google devices and the AOSP is that people can get the source and make their own custom (filtered and examined) system load. And the reason many of us will use the Google devices at all is because of AOSP. AOSP gives us the chance to trust the platform a little more than we would if it were completely closed.
Now there are lots of binary blobs in this and that's disturbing enough, but at least it narrows down potential sources of any compromises of unwanted data movement and such. (And there are definitely people who are watching the data I/O from their devices. We've had some stories right here on Slashdot on that very topic.)
But the other thing I wanted to add to this is that while "the drama is over" the damage is still done. We lost a guy with much experience on the matter. (I don't know the guy personally. Was he good at his job? Don't know... but who is doing it now?)
Trusting Google is a hard thing to do. It's getting harder and harder. But trusitng Microsoft and Apple is even harder still. So there just aren't so many options.
Trusting Google is a hard thing to do.
The really funny thing is that this conversation about it being hard to trust Google is in response to an article disclosing that Google has fulfilled its promises and, indeed, been trustworthy.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Is there a point of posting images of the phone nowadays? They all look the same.
I do not believe in karma. "Funny"=-6. Do good and forbid evil. Yours, Oft-Offtopic Flamebaiting Troll.
If Google was trustworthy we'd have the source for blobs and there wouldn't have been a delay in the first place
Google still doesn't own all that source. And you really can't expect the source to Google Apps themselves. You get source to everything you need to run the device, except for drivers. That's not up to Google.
I have my own concerns about Google but your objections aren't among them, because they are nonsensical.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"