Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android 4.1 in AOSP

groups.google.com

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Android 4.1 in AOSP

#31

Post by mariuz »

_ea1k wrote: post #29
wcoenen wrote: post #25

Earlier quoted context omitted.

Building android requires a beefy developer workstation. Does your friend have the recommended 16GB of RAM[1]? [1] https://groups.google.com/d/topic/android-building/N1exifTpP...

16GB may be recommended, but I have built it before on a machine with 6GB. The initial build ran overnight, and subsequent builds seldom require a rebuild of the entire tree. I think it's certainly possible to manage a small change without 16GB available.

I build it on a 2G machine also on a 4G machine building process works just fine

Re: Android 4.1 in AOSP

#32

Post by drivebyacct2 »

mtgx wrote: post #21
drivebyacct2 wrote: post #17

Earlier quoted context omitted.

Yes. CM has rewritten their modifications for ICS so that they integrate side-by-side with the OS settings. If you didn't see the boot screen or the ROM version, you would just think that you got a whole bunch more features and nice little performance tweaks. They did an amazing job of keeping it stock and adding functionality where it made sense. All without the awkward, disorganized "CMParts" of CM(<9). It's all qu…

I'd rather CM sticks as close as possible to AOSP. Fewer potential issues for them in the future, and they get more time to port to more devices, and to make the "master" ROM more stable.

You can always just take the vendor overlays and build JB-AOSP. Then you don't have to wait for merges.

Re: Android 4.1 in AOSP

#33

Post by drivebyacct2 »

nuje wrote: post #22
Tichy wrote: post #18

What is AOSP?

It's the subset of Android that is released as open source some time after the proprietary versions are shipped.

Your snarky comment isn't even accurate. The only thing not released in AOSP is Google's propreitary APKs of the Google Apps (Market, Gmail, etc). One can build AOSP and have Android almost identical to Galaxy Nexus or what not. A small zip later, and it's nearly byte for byte identical.

Re: Android 4.1 in AOSP

#34

Post by binarycrusader »

drivebyacct2 wrote: post #33
nuje wrote: post #22

Earlier quoted context omitted.

It's the subset of Android that is released as open source some time after the proprietary versions are shipped.

Your snarky comment isn't even accurate. The only thing not released in AOSP is Google's propreitary APKs of the Google Apps (Market, Gmail, etc). One can build AOSP and have Android almost identical to Galaxy Nexus or what not. A small zip later, and it's nearly byte for byte identical.

You also forgot the proprietary drivers needed to actually use almost any of the devices on the market (including Google's own that they sell directly now).

While the original poster was being somewhat disingenuous, let's be honest here, Android isn't a completely open platform. To obtain full functionality from Android devices requires more than what Google distributes source code for.

I say this as a somewhat angry and disappointed Android developer :-(

Re: Android 4.1 in AOSP

#35

Post by hammersend »

binarycrusader wrote: post #34
drivebyacct2 wrote: post #33

Earlier quoted context omitted.

Your snarky comment isn't even accurate. The only thing not released in AOSP is Google's propreitary APKs of the Google Apps (Market, Gmail, etc). One can build AOSP and have Android almost identical to Galaxy Nexus or what not. A small zip later, and it's nearly byte for byte identical.

You also forgot the proprietary drivers needed to actually use almost any of the devices on the market (including Google's own that they sell directly now). While the original poster was being somewhat disingenuous, let's be honest here, Android isn't a completely open platform. To obtain full functionality from Android devices requires more than what Google distributes source code for. I say this as a somewhat angry…

How is that Google's fault though? How many modern mobile devices have completely open drivers including wifi, camera, accelerometer, bluetooth, and GPU? Exactly none. Even the raspberry pi has binary blobs. It doesn't make sense to blame Google for not being able to provide what doesn't exist.

Re: Android 4.1 in AOSP

#36

Post by mikegreenberg »

binarycrusader wrote: post #34
drivebyacct2 wrote: post #33

Earlier quoted context omitted.

Your snarky comment isn't even accurate. The only thing not released in AOSP is Google's propreitary APKs of the Google Apps (Market, Gmail, etc). One can build AOSP and have Android almost identical to Galaxy Nexus or what not. A small zip later, and it's nearly byte for byte identical.

You also forgot the proprietary drivers needed to actually use almost any of the devices on the market (including Google's own that they sell directly now). While the original poster was being somewhat disingenuous, let's be honest here, Android isn't a completely open platform. To obtain full functionality from Android devices requires more than what Google distributes source code for. I say this as a somewhat angry…

Android is the software that runs on many devices. Full functionality is the responsibility of the hardware manufacturer to offer compatible drivers and software to enable the full functionality you're seeking.

The entirety of the OS is there for anyone who wants to hack together the functionality that you're "missing" but the OS is complete and open so far as I can see.

Re: Android 4.1 in AOSP

#37

Post by binarycrusader »

hammersend wrote: post #35
binarycrusader wrote: post #34

Earlier quoted context omitted.

You also forgot the proprietary drivers needed to actually use almost any of the devices on the market (including Google's own that they sell directly now). While the original poster was being somewhat disingenuous, let's be honest here, Android isn't a completely open platform. To obtain full functionality from Android devices requires more than what Google distributes source code for. I say this as a somewhat angry…

How is that Google's fault though? How many modern mobile devices have completely open drivers including wifi, camera, accelerometer, bluetooth, and GPU? Exactly none. Even the raspberry pi has binary blobs. It doesn't make sense to blame Google for not being able to provide what doesn't exist.

I'm not blaming google; I'm just suggesting that Rubin's snarky twitter post about the "definition of open" is somewhat misleading.

Put simply, I'm just trying to point out the sad state of affairs.

Android is primarily run on Phones, but you can't actually use some of them as a Phone if you build AOSP and install it because some of the binaries required for the phone functionality can't be distributed.

That's my point. It's misleading to say "here's an open phone OS" -- when you can't actually use it on your phone, because the things that make your phone work as one aren't open and can't be redistributed.

An open platform doesn't do much good if you can't actually use it on hardware with full functionality.

As I said before, I'm just a disappointed and somewhat angry Android developer, somewhat. Google could have done a better job here and made life easier for me and other developers.

Re: Android 4.1 in AOSP

#38

Post by drivebyacct2 »

binarycrusader wrote: post #37
hammersend wrote: post #35

Earlier quoted context omitted.

How is that Google's fault though? How many modern mobile devices have completely open drivers including wifi, camera, accelerometer, bluetooth, and GPU? Exactly none. Even the raspberry pi has binary blobs. It doesn't make sense to blame Google for not being able to provide what doesn't exist.

I'm not blaming google; I'm just suggesting that Rubin's snarky twitter post about the "definition of open" is somewhat misleading. Put simply, I'm just trying to point out the sad state of affairs. Android is primarily run on Phones, but you can't actually use some of them as a Phone if you build AOSP and install it because some of the binaries required for the phone functionality can't be distributed. That's my poi…

This is true of every smart phone in existence. Period. Even when OpenMoko tried it, they still had binaries. Luckily they were given permission to redistrib the binaries.
Post reply on HN