Android 4.1 in AOSP (opens in new tab)

(groups.google.com)

154 pointsFrancescoRizzi13y ago36 comments

36 comments

Does anyone know which commit covers the reduction in functionality for the global search (related to the sales ban on the Nexus)? My friend is trying to find the commit so he can compile Jelly Bean (for the Galaxy Nexus) with the global search restored but neither of has been able to find where the change was made.

We were thinking it might be in the QuickSearchBox ( https://android.googlesource.com/platform/packages/apps/Quic... ) but there don't seem to be any recent commits here. I'm thinking now it might be in some place specific for the Nexus, but I'm not familiar enough with the Android source to know where to look.

guelo13y ago

My guess would be that that patch is in some special factory branch that is not released publicly. Meaning that branches jb-dev and jb-release are clean and still have global search.

fpgeek13y ago

Are you sure that change is in the AOSP source? It could easily be part of the Google Apps bundle instead (in which case reversing it would be trickier).

unfasten13y ago

Hadn't thought of that, thanks. My friend compiled and installed AOSP Jelly Bean and you are indeed correct; global search works without limitation.

wcoenen13y ago

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...

FrankBooth13y ago

$100 worth of memory, so beefy.

1 more reply

_ea1k13y ago

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.

1 more reply

pkulak13y ago

That seemed pretty quick. And apparently it's a minor update, code wise, so hopefully we'll see some action from the CY devs soon. Though, ICS probably has to hit release first.

keeperofdakeys13y ago

The Cyanogenmod developers have been taking CM9 development a bit differently to the past, trying to make it less hacky, so it is both more stable and easier to port features. Since Jelly Bean is a minor update, a lot of parts should have the same, or a similar API. This means the CM developers can literally forward port and backward port features between ICS and Jelly Bean with ease. So they will be releasing ICS and JB releases simultaneously.

SoapSeller13y ago

Yes, JB will be in CM10, while CM9 dev continues. pretty much like it is currently being done with CM7&9.

More info about CM approach towards JB can be found here: https://plus.google.com/117962666888533781522/posts/PNJutPNh...

drivebyacct213y ago

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 quite wonderful.

1 more reply

yock13y ago

Could this point to an imminent Jelly Bean release for Nexus devices?

w1ntermute13y ago

You can already get Jelly Bean for the Galaxy Nexus, if you're willing to do a manual install. I've been running Jelly Belly[0], an LTE Jelly Bean rom, on my LTE Nexus for the last couple of days. There were a few issues with Jelly Belly v2.1 (tethering and camera), but as of Jelly Belly v2.4, it's been running without any hitches, Google Now and all.

0: http://rootzwiki.com/topic/28677-rom-jelly-belly-v26-0709201...

abraham13y ago

Google announced at I/O that JB would be coming to nexus devices in July and the Galaxy Nexus on the Play Store is supposed to ship with JB in 1-2 weeks. So pretty much.

nodata13y ago

Until the factory images page gets updated, I'm staying put: https://developers.google.com/android/nexus/images

beering13y ago

Does anybody know if the new text-to-speech engine is part of AOSP? I'm referring to the tech Google got by buying Phonetic Arts.

Tichy13y ago

What is AOSP?

nkurz13y ago

The Android Open Source Project.

http://source.android.com/about/index.html

nuje13y ago

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

hammersend13y ago

Is that supposed to be funny? No Jellybean devices have shipped to the general public yet the source has been released. Also, AOSP is not a sub-set of Android, AOSP is Android. Anything else is an add-on including the Google Apps.

drivebyacct213y ago

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.

1 more reply

regularfry13y ago

What the hell did Google Groups just do to my back button?

barista13y ago

Looking forward to seeing this on Kindle fire soon.

jyap13y ago

I can't tell if that's sarcasm. You mean the new Kindle Fire which will be released for Christmas 2012, right?

_ea1k13y ago

I think he means an unofficial port. I expect those will be available fairly soon.

1 more reply

j / k navigate · click thread line to collapse

36 comments

unfasten13y ago

guelo13y ago

My guess would be that that patch is in some special factory branch that is not released publicly. Meaning that branches jb-dev and jb-release are clean and still have global search.

fpgeek13y ago

Are you sure that change is in the AOSP source? It could easily be part of the Google Apps bundle instead (in which case reversing it would be trickier).

unfasten13y ago

Hadn't thought of that, thanks. My friend compiled and installed AOSP Jelly Bean and you are indeed correct; global search works without limitation.

wcoenen13y ago

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...

FrankBooth13y ago

$100 worth of memory, so beefy.

1 more reply

_ea1k13y ago

1 more reply

pkulak13y ago

That seemed pretty quick. And apparently it's a minor update, code wise, so hopefully we'll see some action from the CY devs soon. Though, ICS probably has to hit release first.

keeperofdakeys13y ago

SoapSeller13y ago

Yes, JB will be in CM10, while CM9 dev continues. pretty much like it is currently being done with CM7&9.

More info about CM approach towards JB can be found here: https://plus.google.com/117962666888533781522/posts/PNJutPNh...

drivebyacct213y ago

1 more reply

yock13y ago

Could this point to an imminent Jelly Bean release for Nexus devices?

w1ntermute13y ago

0: http://rootzwiki.com/topic/28677-rom-jelly-belly-v26-0709201...

abraham13y ago

Google announced at I/O that JB would be coming to nexus devices in July and the Galaxy Nexus on the Play Store is supposed to ship with JB in 1-2 weeks. So pretty much.

nodata13y ago

Until the factory images page gets updated, I'm staying put: https://developers.google.com/android/nexus/images

beering13y ago

Does anybody know if the new text-to-speech engine is part of AOSP? I'm referring to the tech Google got by buying Phonetic Arts.

Tichy13y ago

What is AOSP?

nkurz13y ago

The Android Open Source Project.

http://source.android.com/about/index.html

nuje13y ago

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

hammersend13y ago

drivebyacct213y ago

1 more reply

regularfry13y ago

What the hell did Google Groups just do to my back button?

barista13y ago

Looking forward to seeing this on Kindle fire soon.

jyap13y ago

I can't tell if that's sarcasm. You mean the new Kindle Fire which will be released for Christmas 2012, right?

_ea1k13y ago

I think he means an unofficial port. I expect those will be available fairly soon.

1 more reply

j / k navigate · click thread line to collapse