Develop Bugs

Jelly Bean kernel question

Like many of you others out there, the past few days, I've been flashing all different kinds of Jelly Beans on my GSM Galaxy Nexus. First, I installed bigxie's 4.1 (v1 and v2), then I installed bigxie's 4.1.1 (AOSP). It might be important to mention that my Gnex is originally a yakju and obviously all these versions of JB are for takju, so my phone has essentially been "converted." Later I reflashed the stock 4.1 from the I/O and then installed the official Google .zip file (from xda) that updates from the I/O 4.1 to 4.1.1. After doing this, I noticed this morning that my kernel version was different from others who had just installed 4.1.1 via OTA with the System Updates. So this afternoon I used the Galaxy Nexus Toolkit v7.4 to download and flash the Google factory ICS 4.0.4 image, which obviously deleted everything from the phone. Then I turned wifi on and went to System Update and it was already downloading the Jelly Bean official update, as pictured below:
View attachment 1194468
After installing the above update, I checked the phone's info section and I still had a different kernel version than everyone else, as see below:
View attachment 1194471
While I have kernel 3.0.31-ge8de0e2, it seems like other people have 3.0.31-g6fb96c9. As mentioned before, I had to resort to going back to stock, vanilla 4.0.4, then downloading/installing the update and I still don't have this newer kernel. What is different about this kernel and why is my phone unable to get it?

I have that build of the kernel (g6fb96cp), it really shouldn't matter which one you have.

Something strange just happened to my phone.
After doing some searching online, it seems that the 3.0.31-ge8de0e2 kernel is the same one that comes with the developer preview of JB 4.1 from the Google I/O phones. Just now, I downloaded an update for Google+, and when I restarted my phone, I was suddenly magically on the 3.0.31-g6fb96c9.
Is it even possible that a single app update could carry a kernel update as well?!?!?

arathur said:
After doing some searching online, it seems that the 3.0.31-ge8de0e2 kernel is the same one that comes with the developer preview of JB 4.1 from the Google I/O phones. Just now, I downloaded an update for Google+, and when I restarted my phone, I was suddenly magically on the 3.0.31-g6fb96c9.
Is it even possible that a single app update could carry a kernel update as well?!?!?
Click to expand...
Click to collapse
Now that I couldn't answer, it's possible but unlikely. All an app has to do is replace boot.img, something that many other kernel apps are capable of (franco.kernel's app, ezekeel's app).

Proper verbiage for roms built from recently released Jelly Bean binary code...

Hey all,
I read that a few days ago, Google released the official binary code for jelly bean for verizon phones.
What terms should I be looking for to make sure that the new rom I decide on will make use of (and be built from) the new, proper code for the CDMA binary code for Jelly Bean?
Thanks,
Matt!
Sent from my Galaxy Nexus using Tapatalk 2

KillerQ said:
Hey all,
I read that a few days ago, Google released the official binary code for jelly bean for verizon phones.
What terms should I be looking for to make sure that the new rom I decide on will make use of (and be built from) the new, proper code for the CDMA binary code for Jelly Bean?
Thanks,
Matt!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
When Jelly Bean code was released in AOSP originally they released proprietary binaries. The new binaries just bring those binaries, whatever changes they might have, up with the current build number of Jelly Bean source. The blobs they didn't have license to release (mostly affecting camera and GPS) still haven't been added and need to be extracted from a released Jelly Bean image.
So mostly versions of the same released proprietary blobs for us, that was what they announced.

Thanks, I guess I'm just waiting to see in official release from one of the well-known ROM producers....like those unicorn people, lol. It seems that everything is unofficial as of yet
Sent from my Galaxy Nexus using Tapatalk 2

[Q] "Take bug report" disabled on 4.2.1

Running Takju Android 4.2.1 and the "Take bug report" under the developer options is disabled. Anyone know how to enable this? (Tried googling to no avail).
[I don't konw if the issue occured on 4.2. I'm running on a GSM Samsung Galaxy Nexus running googles Takju Android 4.2.1 (a Canadian phone which was originally running running yakjuux)]

funr said:
Running Takju Android 4.2.1 and the "Take bug report" under the developer options is disabled. Anyone know how to enable this? (Tried googling to no avail).
[I don't konw if the issue occured on 4.2. I'm running on a GSM Samsung Galaxy Nexus running googles Takju Android 4.2.1 (a Canadian phone which was originally running running yakjuux)]
Click to expand...
Click to collapse
Option is available on Yakju 4.2.1 through OTA, option was also available on 4.2 self built.
Sent from my i9250

[Q] What makes android 4.0.4 vary from 4.0.3 and how to manually update a rom

I was just wondering if it was possible to Manually update a android 4.0.3 ROM to 4.0.4? Like if we knew the files that defines and classifies a 4.0.4 rom. I am not sure if these two android roms are built on different bases or code but all 4.0.3 apps work on 4.0.4 and vice versa. Seeing how 4.0.4 just seems to be a patch of 4.0.3 with minor fixes and improvements it doesn't seem so far fetched.

xdarkmario said:
I was just wondering if it was possible to Manually update a android 4.0.3 ROM to 4.0.4? Like if we knew the files that defines and classifies a 4.0.4 rom. I am not sure if these two android roms are built on different bases or code but all 4.0.3 apps work on 4.0.4 and vice versa. Seeing how 4.0.4 just seems to be a patch of 4.0.3 with minor fixes and improvements it doesn't seem so far fetched.
Click to expand...
Click to collapse
This, I'd like to know too

I dont know how to manually update but here are the changes http://androidandme.com/2012/03/sma...s-verizons-samsung-galaxy-nexus-not-included/
Sent from my r800x using xda developers app

[Q] somebody can do 4.2 or 4.1 rom?

the new nexus7 rom is 4.3,but I want use ubuntu on android,ubuntu is run on 4.2 or 4.1 very good.
but now ,it's run on new nexus 7 had some bug ,the big problem is java couldn't install on ubuntu.
somebody can help me ?
make a 4.2 or 4.1 rom?

I don't think that either of those is compatible with the new hardware in the N7 2013. I've only seen 4.3 builds.

danvee said:
I don't think that either of those is compatible with the new hardware in the N7 2013. I've only seen 4.3 builds.
Click to expand...
Click to collapse
thanks for your reply,it's too sad

No kernel. No drivers = no 4.2
4.2 and 1 were broken anyways. Way less problems with 4.3.

tweaked said:
No kernel. No drivers = no 4.2
4.2 and 1 were broken anyways. Way less problems with 4.3.
Click to expand...
Click to collapse
Yes, but no chroot gnu/linux in 4.3, that's a MAJOR issue with 4.3 :/ Still waiting for a fix from Google or a workaround from the community...

Only time will tell. I guess sooner or later either Google or the community will have the solution