Live data from Hacker News

Android 4.1 in AOSP

groups.google.com

11–20 of 38 posts

Re: Android 4.1 in AOSP

#11
post #6

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

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

Re: Android 4.1 in AOSP

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

Re: Android 4.1 in AOSP

#13

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/package…

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

Re: Android 4.1 in AOSP

#14
post #10

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.

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.

Re: Android 4.1 in AOSP

#15

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/package…

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.

Re: Android 4.1 in AOSP

#17
post #10

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.

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 an…

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.
Post reply on HN