Forgot your password?
typodupeerror
Android Google Handhelds Open Source

Google Posts Images, Binaries For New Nexus 7 80

Posted by timothy
from the not-so-bad-as-all-that dept.
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.
This discussion has been archived. No new comments can be posted.

Google Posts Images, Binaries For New Nexus 7

Comments Filter:
  • Same moronic moaning (Score:5, Interesting)

    by Anonymous Coward on Saturday August 10, 2013 @05:16PM (#44532699)

    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.

    • The REAL question about Google's relationship with Android is when they will finally release the DESKTOP version

      I was under the impression that Google intended to segment the market into Chrome OS for laptops and desktops and Android for tablets and phones.

      • That seems to be the case. Non-Google Android sticks that plug into TVs are sort of desktops, though, and have been around for some time. The newer ones, based on RK3188, are quite powerful. It's gaining ground faster than Android x86 and, as soon as some company makes an ARM processor that focuses on speed over power consumption, perhaps with active cooling, we'll have proper desktop Android, regardless of Google's plans.

        • ..."as soon as some company makes an ARM processor that focuses on speed over power consumption, perhaps with active cooling"...

          No, no, please, not another hornet in the room. A couple more watts to push the performance envelope are okay for a non-mobile system, but active cooling is the one evil in personal computing I wish would die a quick death. Typed from my buzzing AMD HTPC.

        • ARM is flawed in a way that lends well to efficiency and terribly to raw speed. Trying to make a 35 or evenis 100 watt ARM chip to compete with even a low clocked i3 will yield embarrassing results

      • I was under the impression that Google intended to segment the market into Chrome OS for laptops and desktops and Android for tablets and phones.

        Another way of segmenting the market is: products people want and products people do not want. The market has sent Google a clear message that if the gadget looks like a laptop then it better act like a laptop. As it stands, Chromebook sells only a bit better than Surface RT. Well, they make pretty good Linux laptops so from that point of view I hope Google keeps selling them. But if Google really wants an entry point to the "real computer" market then they would be better off playing the Android card. Of c

      • by drinkypoo (153816)

        I was under the impression that Google intended to segment the market into Chrome OS for laptops and desktops and Android for tablets and phones.

        What gave you that impression? I see no evidence that Google even wants to be involved with desktops. (On the other hand, Mobile Firefox 23 for Android has mouse-over support... I will have to fire up my full desktop just that much less now.)

    • by whoop (194)

      ... but they could.

      That's the entirety of every fear-mongering article of anything in the tech sector. Sure, right now DOOM is the latest awesomeness in graphics, but they could release their next game as a text adventure. That will be the end of graphics entirely. We cannot stand for this! We must revolt now, before the end is here!! Aaaaarrrrrgggghhhhhh.

    • The REAL question about Google's relationship with Android is when they will finally release the DESKTOP version,

      They're waiting until they can license the patents and source from SCO......

    • by Raenex (947668)

      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?

      Yeah, that idiot employee at Google, the one in charge of their open source release, resigned from the project because he couldn't do his job, and then miraculously a couple of days later the binaries get released.

      Nope, nobody should ever complain. We should all trust Google and their partners to eventually release the goods when the time is right.

    • While it's true that Google is "NOT going to prevent you from watching your own videos, or reading your own books, regardless of the source or the file format", it does seem to treat user-provided content like a second-class citizen compared to Play content. When I added a few video files to my Nexus 7, it took me almost 10 minutes to figure out how to actually play them, and when I did find them, they showed up as nameless video thumbnails.
  • Amazingly while we hear the usual moaning about the lack of downloadable firmware Google is actually among the fastest to release factory images for their products. No, I'm not talking about Google having a first shot at compiling the latest Android sources for Nexus X Y or Z. I'm talking about companies not releasing firmware for products that are already being sold with that firmware installed. What's preventing these companies from making available a freely downloadable backup of firmware that's already

    • by rmcd (53236) *

      Did you get your dd command backwards? Shouldn't it be "dd if=image_file of=some_device"?

      I realize you weren't writing a dd howto, but it's a potentially dangerous utility.

  • by mapkinase (958129) on Sunday August 11, 2013 @06:35AM (#44534701) Homepage Journal

    Is there a point of posting images of the phone nowadays? They all look the same.

There are worse things in life than death. Have you ever spent an evening with an insurance salesman? -- Woody Allen

Working...