yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ScardracS:
It's time to work on kernel 3.4!!

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] parthipanramesh:
I'm reading this discussion now for almost a month and I must say it's getting interesting!! :D
[Samsung Galaxy Nexus] eternal70:
Wow, big challenge huh........
[Samsung Galaxy Nexus] goast:
Just going to put this here http://www.androidheadlines.com/201...-binaries-breath-life-two-year-old-phone.html
[Samsung Galaxy Nexus] tacosrdelicioso:
Hashcode! He knows his stuff folks. He's magic

Sent from toro on KITKAT
[Samsung Galaxy Nexus] mrgnex:
So if we get a booting 3.4 kernel we wont have a working phone? And when it boots we have to build the Galaxy Nexus kernel on our own to get the phone working? Like wifi and video playback and camera?
[Samsung Galaxy Nexus] goast:
Read my last post may be helpful
[Samsung Galaxy Nexus] mrgnex:
Sorry didnt see it. It was lost between the long posts. But still if we get 3.4 working we wont have working wifi and camera and video playback right? Thats what I read in the q&a from [MENTION=4243514]Hashcode[/MENTION].. So we need to build a 3.4 kernel and then put 3.0 features in it? (The reverse engeneering.)
[Samsung Galaxy Nexus] goast:
Honestly not sure just saw the article and seems that it would fix issues. Not sure how much or many.. But could be a start.. Would like someone with more knowledge to read it and dumb it down lol
[Samsung Galaxy Nexus] gigsaw:
A fully working 3.4 ION kernel? Almost impossibile IMHO because the effort to make is too big. A group of talented hackers skilled in reverse engeneering si needed..and the time required is huge. Probably is better a 3.0 kernel..
[Samsung Galaxy Nexus] eternal70:
If anarkia share his 3.4 kernel source to us........:confused:
[Samsung Galaxy Nexus] nikodr:
I think that the picture shows what is available to our nexus,it's not 1.9 but 1.8 ,in order for the phone to show 1.9 it would mean that someone has already made a new kernel that has the new binaries.AOSP simply posted the updated web link with the new files.Someone has to make a new one kernel.Then we could have the new image that would show that on the phone 1.9 is installed.
[Samsung Galaxy Nexus] aosp:
[MENTION=4243514]Hashcode[/MENTION] The third commit is the newest drivers for the 3.0.X OMAP Linux branch us GneX users are currently on the pic is what Google gave us ;)
[Samsung Galaxy Nexus] aosp:
They decided to offer half arse support for the GneX cause it ain't money but the .gits don't lie Google we got limited hacky patches from you rather then the proper patches and optimizations from TI and IMGTEC I forgot to link a important commit from TI

omaplfb:*Add*omaplfb*to*the*kernel*tree

omaplfb*has*dependencies*on*several*kernel*components*and*it*will

be*easier*to*maintain*it*in*the*kernel*tree.

Sync'd*to*DDK*omaplfb*patch:

omaplfb:*Allocate*a*clear*buffer*with*8*pixel*stride*per*GC*requirement

http://goo.gl/XOwS3V

Google will know that no GNeX stays behind ;)
[Samsung Galaxy Nexus] tobiascuypers:
Awesome of you to shed some light and help us out. Appreciate you reading my PM. :confused: Thanks a lot Hash. Im sure some of the awesome guys here can figure something out
[Samsung Galaxy Nexus] bsmitty83:
I'm really confused as how these binarys are new , all the commits have 7/12 dates on them , or are they just new to the nexus ?
[Samsung Galaxy Nexus] aosp:
I posted the initial newer updates but they updated the kernel again and posted newer GPU bins after those

Rebuilt*sgx*binaries*required*because*of*a*kernel*change*that*requires*sgx*to*be*rebuilt.

http://goo.gl/FbBWDN
[Samsung Galaxy Nexus] tacosrdelicioso:
Okay. This one says June 2013. Still. I feel like our legs might be being pulled

Sent from toro on KITKAT
[Samsung Galaxy Nexus] gkilah:
Not all commits are from that date ( IMG DDK Release 1.9@2166536 for Android. Eric Luong (TI) [Mon, 5 Nov 2012 16:34:22 +0000] )

But Google DDK 1.8@2198402 are from Fri Nov 16 16:50:27 2012 -0800 by Alistair Strachan ( IMGTEC )

Something its not right from my point of view...
[Samsung Galaxy Nexus] fairct:
I'm thinking these files are the same ones here: https://github.com/TheMuppets/propr....1/omap4-common/proprietary/system/vendor/lib

I'm already using these in my toro 4.4 build, and it has graphical glitches.
[Samsung Galaxy Nexus] aosp:
This was google half arse attempt to update our gpu drivers Revert "gpu: pvr: Update to DDK 1.9.RC1.JB@2113614"

http://goo.gl/COM7N6

They missed this

http://omapzoom.org/?p=kernel/omap..../video/omap2;hb=refs/heads/p-android-omap-3.0

And especially this

omaplfb:*Add*omaplfb*to*the*kernel*tree

omaplfb*has*dependencies*on*several*kernel*components*and*it*will

be*easier*to*maintain*it*in*the*kernel*tree.

Sync'd*to*DDK*omaplfb*patch:

omaplfb:*Allocate*a*clear*buffer*with*8*pixel*stride*per*GC*requirement

http://goo.gl/XOwS3V

Guys check my links again Google updated us with old GPU drivers I even posted a pic just read the .gits [MENTION=3813155]fairct[/MENTION] when you update the kernel too you would benefit from with all these fixes http://omapzoom.org/?p=device/ti/pr...f6271aab1b02abfc8ed97d7;hb=d-jb-mr2.0-release Our GNeX kernel source needs to be patched first with the supplied code to properly use the updated drivers.
[Samsung Galaxy Nexus] bsmitty83:
I get what your saying about the dates and I was thinking that's what they did , thanks for clarifying
[Samsung Galaxy Nexus] Hashcode:
I'll see your Nov 2012 commit here:

http://omapzoom.org/?p=device/ti/pr...it;h=8137028adad92178573b3448f833e1f0338c20db

And up you 1 more commit (Apr 2013):

http://review.omapzoom.org/#/c/32447/

:)

This was never posted to the actual omapzoom git and stayed on review for whatever reason. I use these bins for my 4.3 builds.
[Samsung Galaxy Nexus] aosp:
No I saw that but it's still pending approval for the 3.0.X kernel branch and it was merged for the 3.8.X kernel reason I did not mention it ;)

kernel SGX-BIN:*Binaries/KM*source*with*GPU*thermal*integration

DDK*1.9@2291151

Branch:*origin/1.9/2291151_k3.8

http://goo.gl/CuwTUw
[Samsung Galaxy Nexus] misterk267:
Can I ask what all this means exactly? I get that these are updated GPU binaries and may help with 4.4 rendering issues, but will they give us opengl 3 support? Or do they just fix the rendering? Thanks!
[Samsung Galaxy Nexus] Hashcode:
there is no opengl 3.0 support for any pvr chip that I know of (yet)
[Samsung Galaxy Nexus] misterk267:
Ah okay. Would've been nice haha. Anyways, can't wait to see where this leads. From what I've gathered after reading the thread, fully functional KitKat may be a possibility.
[Samsung Galaxy Nexus] aosp:
Which PowerVR graphics cores support OpenGL ES 3.0? - Imagination Developer Forums - http://goo.gl/15r82s ;)
[Samsung Galaxy Nexus] aosp:
PowerVR Insider - http://goo.gl/RR0ulD

If you really like to know what our GPU can do ;)
[Samsung Galaxy Nexus] aosp:
Remember guys Google decided not to give us kit kat because they would have to update our video and graphics drivers and that would be called support don't let them tell you any different and we can do a better job anyway ;p
[Samsung Galaxy Nexus] kuronosan:
hey you make it happen I don't think anyone will care at this point :p
[Samsung Galaxy Nexus] niels72:
So been reading this thread from page 1 to the last page after feeling a buzz in Gnex community. I am not a dev and can't follow you guys at all.

But I tried to cut it down to a none dev brain in simple English. In short Google never used those alleged latest binaries in Jelly Bean ?

Meaning the performance of the GPU is trailing behind because didn't use those binaries ?

But the most important Q I guess will be eventually; Will those binaries give us the beloved KitKat ?
[Samsung Galaxy Nexus] Link_of_Hyrule:
Well I'm interested to see where this goes. Hopefully it won't be too hard to sort through the bugs and get all the drivers working in this kernel.
[Samsung Galaxy Nexus] RedDeadDorito:
Damn, our hopes and dreams just got ****ted on.
[Samsung Galaxy Nexus] mrgnex:
Can't we create a thread in the devlopers only section about this and ask them to make a team and build this kernel? Or send every dev a pm?
[Samsung Galaxy Nexus] aosp:
Yes you are correct Google supported the Galaxy Nexus by only supplying it with ICS focused gpu and video drivers but once the updated code and binaries are applied that I linked the Galaxy Nexus can truly enjoy jellybeans and kitkats ;)
[Samsung Galaxy Nexus] Ashtrix:
Lets hope a good 4.4 rel :D !!

Thanks buddy for the update on the NP :good:
[Samsung Galaxy Nexus] tacosrdelicioso:
Everyone seems to be against aosp's side so...um..
[Samsung Galaxy Nexus] tobiascuypers:
Honestly have no idea what your talking about...
[Samsung Galaxy Nexus] tacosrdelicioso:
Lol sorry. It just looks like there's a lot of evidence to show that it may be not be helpful at all
[Samsung Galaxy Nexus] misterk267:
Don't be negative, you'll jinx all of us and we'll never get 4.4! xD
[Samsung Galaxy Nexus] tacosrdelicioso:
Well negative is a strong word. Maybe I'm being realistic haha
[Samsung Galaxy Nexus] misterk267:
They'll figure something out. Don't worry, we'll have our kitkat. :P
[Samsung Galaxy Nexus] tobiascuypers:
I think well have kitkat semi-fully working anyway with or without a kernel upgrade... As [MENTION=4243514]Hashcode[/MENTION] said, it may or may not help.
[Samsung Galaxy Nexus] Carlos_Manuel:
Hi guys!

Sorry for a bit off topic question, but I need some help with kernel building for AOSP KitKat..

I am trying to build Tuna's JB Mr-2 kernel (3.0.72) with the ROM but I got error: no "?something?.." to create boot.img... As what I think I have to edit something from kernel to make it build-able with the ROM..?

I have already added these to tuna device repository for building kernel rather than using kernel image from Tuna's device repository:

https://github.com/CyanogenMod/andr...mmit/74b3fd97cd88fc96c018ec0dc911038a827d264d

I also checked the defconfig name..

What am I missing?

Thanks if someone can help. :)

[MENTION=2838735]aosp[/MENTION] maybe you can help me with this? :)
[Samsung Galaxy Nexus] aosp:
If you looked at the .git commits I linked it should be very obvious it would only help especially on kitkat but linaro will help too Android 4.4 KitKat release impressions at Linaro Connect 2013 - YouTube - http://goo.gl/5fuhJ4

James Dean - Google+ - Oh Yeah +Linaro Android supports +KIT KAT on the Galaxy… - http://goo.gl/iBq84z
[Samsung Galaxy Nexus] aosp:
[MENTION=4022928]Carlos_Manuel[/MENTION]

tuna: Add kernel parameters to BoardConfig · db036f5 · VanirAOSP/device_samsung_tuna · GitHub - http://goo.gl/Sg7PIl

tuna: Build the kernel from source instead of relying on the prebuilt bl... · 54dc9f6 · VanirAOSP/device_samsung_tuna · GitHub - http://goo.gl/YllbiV

tuna: Grab kernel from PRODUCT_OUT instead of in-source build · 7559448 · VanirAOSP/device_samsung_tuna · GitHub - http://goo.gl/UqfwhF

Try those ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
Thanks a lot! :good: :silly:
[Samsung Galaxy Nexus] aosp:
In case you still doubting that Google has the GNeX using old ICS gpu and video drivers even though we got so called JB support ;)

TI:

SGX-BIN:*DDK*update*1.8@945322

http://goo.gl/JmPf3x

*e579ec6*Merge*branch*'img_ddk_1.8'*into*ti_ics_1.8*(DDK*1.8@945322)

SGX-BIN:*jb*built*bins*(1.9@956766)

DDK1.9*is*the*officially*supported*SGX*release*for*JB

This*package*depends*on*the*p-android-omap-3.0-dev*kernel*with:

b49820d*omaplfb:*Add*omaplfb*to*the*kernel*tree

48501089*blaze_defconfig:*Add*KPROBES*and*RELAY*dynamic*instrumentation

1558094*blaze_defconfig:*Enable*SCHED_TRACER

http://goo.gl/JpIf7n

omaplfb:*Add*omaplfb*to*the*kernel*tree

omaplfb*has*dependencies*on*several*kernel*components*and*it*will

be*easier*to*maintain*it*in*the*kernel*tree.

Sync'd*to*DDK*omaplfb*patch:

omaplfb:*Allocate*a*clear*buffer*with*8*pixel*stride*per*GC*requirement

http://goo.gl/XOwS3V

Google:

gpu: pvr: Update to DDK 1.8@2198402

http://goo.gl/hgt5D0

Revert "gpu: pvr: Update to DDK 1.9.RC1.JB@2113614"

http://goo.gl/COM7N6
[Samsung Galaxy Nexus] Carlos_Manuel:
@aosp

No private recovery resources for TARGET_DEVICE maguro
make: *** No rule to make target `android_kernel', needed by `device/samsung/tuna/kernel'. Stop.

device.mk

# Everything in this directory will become public

ifeq ($(TARGET_PREBUILT_KERNEL),)
TUNA_LOCAL_KERNEL := device/samsung/tuna/kernel
[B]$(TUNA_LOCAL_KERNEL): android_kernel[/B]
cp -f $(PRODUCT_OUT)/obj/kernel/arch/arm/boot/zImage $(TUNA_LOCAL_KERNEL)
else
TUNA_LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

DEVICE_PACKAGE_OVERLAYS := device/samsung/tuna/overlay

# This device is xhdpi. However the platform doesn't

I have no ideas right now. :D

Gotta try this:

https://github.com/VanirAOSP/device_samsung_tuna/commit/8f435c4b20170b0bc3bbd62301ca8db7a68b1998

Edit:

EDIT: I forgot android_build

Building kernel.. :3
[Samsung Galaxy Nexus] Pasquale91fg:
Great job man! Now you create a kernel with these new binary?
[Samsung Galaxy Nexus] aosp:
Trust me the purpose of me posting my findings we're not for the sites to get hits but for /boot & /system on all tunas I just figured I would share it here early before Google responds with poo and for any dev to do with the info as they please just stay tuned fellas the GNeX is not irrelevant ;)
[Samsung Galaxy Nexus] aosp:
And like I always say don't believe everything you read on the internet but understand that the .git don't lie :)
[Samsung Galaxy Nexus] kuronosan:
Having gits are one thing. Having a build is another.
[Samsung Galaxy Nexus] thomstrack:
I'm not a developer, but that's not what was missing (or at least part of it)?

https://android.googlesource.com/platform/hardware/ti/omap4xxx/+/android-4.4_r1
[Samsung Galaxy Nexus] mirhl:
Dafaq?? Monday 22 april 2013? :what::what:
[Samsung Galaxy Nexus] Castro27:
Just curious, in layman's terms ?
[Samsung Galaxy Nexus] mageos:
I am not sure if this helps or not...

http://omappedia.org/wiki/4AJ.2.5_OMAP4-Panda_Jelly_Bean_Release_Notes

But it seems as if there is an OMAP release for Linux 3.4.
[Samsung Galaxy Nexus] minhna:
Hopefully we have 3.4 kernel soon. :good:
[Samsung Galaxy Nexus] tiny4579:
Just checked. It's the same point as Android 4.3. No commits since 4.3 to this project. It was just tagged with 4.4_r1 - probably since they're going to support Google Glass with 4.4 - this I think will be invaluable to fix most of the main graphical issues with Kitkat.
[Samsung Galaxy Nexus] niels72:
Ahh link to the Google sources been posted here already.

Hmm so Tiny4579 this won't help a bit ?. I surely hope so but I aint a dev. So can't help at all. I wish I could though.
[Samsung Galaxy Nexus] :
Noobs like us should stop ****ing on this thread over and over and over. Leave the devs alone, you're all not adding anything, or stop asking/posting stupid comments :|
[Samsung Galaxy Nexus] galapagos:
You can't stop the zombies. They'll continue to come.
[Samsung Galaxy Nexus] meghjagad007:
POST IN A TASTE OF KITKAT..BY YOBOOH

Texas instrument has released 4.4kitkat optimized library for the Galaxy Nexus GPU, that will solve the glitches and allow a perfect Kitkat Experience!

NEWS: http://www.tuttoandroid.net/development/galaxy-nexus-aggiornamento-file-binari-gpu-154649/ (you have to translate the page, tuttoandroid it's the bigger italian Android community)

---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------

link to d thread..

http://xdaforums.com/showthread.php?p=47212043
[Samsung Galaxy Nexus] -Jesco-:
if you bother reading anything that you post , the thread ultimately links back here so yeah pointless in that sense
[Samsung Galaxy Nexus] meghjagad007:
whatever mahn..main thing is..itz a good thing for gnex..:)
[Samsung Galaxy Nexus] bsmitty83:
Lolz

On another note , I used the commit that asop linked and built a few different kernels with the ddk1.9@2*** , but it doesn't work on any 4.3 or 4.4 ROM I've tried . just get a Google lockscreen no boot animation .so I think Google reverted this commit for a reason .
[Samsung Galaxy Nexus] fcisco13:
Yes please stop posting what's been said hundreds of times! Im sure devs know about it! Let them work!

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] ASHURiCAN:
I understand nothing about all you, pros, are talking when it's about sources, gits and co, but I thank you all you guys for your knowledge, experience and professionalism! :D. You're really amazing! :) Thx again! ^^
[Samsung Galaxy Nexus] sherincal:
Everyone who doesn't know what they are talking out, stop posting. I would love some good dev discussion here, not random people talking out of their ass.

Yes that involves me.

Save your thank you posts and other things like that til we are making some REAL progress.

Kthxbye
[Samsung Galaxy Nexus] cujo6801:
Horse=dead

Thread police=beating it

You guys make me laugh...

Thanks.....

sent from the DOG pound
[Samsung Galaxy Nexus] tobiascuypers:
This seems to be a problem... This would probably have something to do with the surfaceflinger that was talked about by [MENTION=3678397]stefanz08[/MENTION], I think :confused: So fixing this would help with the graphic issues from what I understand.
[Samsung Galaxy Nexus] bsmitty83:
Yup that's where it loops at , but there's many errors in the log , alot fails to load
[Samsung Galaxy Nexus] eng.stk:
THey didn't said they could/would help, so my wish is this: hope they can help, and hope even more of our skilled kernel devs enter the fun :)

What I ask for, better yet, what I hope for is that somehow we can get a working verison in future, would be awesome :good:

Big shouts to all the GNex kernel devs
[Samsung Galaxy Nexus] crixley:
you're a machine

ada= pure gold
[Samsung Galaxy Nexus] stenka85:
Renaud (fugumod kernel) in the past, he ports kernel 3.0 to galaxy s on gingerbread 2.6.35 to 3.0, renaud can help you.
[Samsung Galaxy Nexus] akash3656:
Well this is a start wouldn't you agree?

AK wants to see the source and then he can help. And AK likes to experiment new stuff :)

bbedward also is going to look at the source soon. I'm currently using his kernel, and it's quite well put together without the insane heat issues or peculiar slowdowns I have on other kernels from big names.

And certain developers have ported a newer Linux kernel in the past, and have their own reasons why they may or may not help this round.

Lastly, projects like this will probably take quite a while to be a daily driver, so be very patient.
[Samsung Galaxy Nexus] JackpotClavin:
Agreed. This is gonna cool if it gets off the ground. Right now my main priority is to get the display working. I'm currently stuck here

<3>[ 14.668609] omapdss DSI error: can't get FRAMEDONE irq
<3>[ 14.674011] s6e8aa0 display0: failed to enable DSI
<4>[ 14.679077] omapfb omapfb: Failed to enable display 'lcd'
<3>[ 14.684753] omapfb omapfb: failed to initialize default display
<3>[ 14.691253] omapfb omapfb: failed to setup omapfb
<4>[ 14.696228] omapfb: probe of omapfb failed with error -22

and I'm running out of ideas. I've looked at other OMAP boards and replicated what they did from the 3.0 kernel to make it work with 3.4, but nothing really did the trick. I think there's a new method of probing the display device that I've completely skipped. It used to use omapfb_set_platform_data, but it's obsolete now so I had to remove it from the tuna-display.c file, so I'm actively looking to find its alternative and maybe that will probe the display device.

We should also look into this commit from Google for OMAP: 51157eda471eb8b65a9ed9be709fd969aa497291
[Samsung Galaxy Nexus] JackpotClavin:
I got past the old error, it was just one line that needed to be adjusted. A newer error that cropped up is:

<4>[ 0.209411] omap_hwmod: dss_rfbi: softreset failed (waited 10000 usec)
<3>[ 15.016754] omapdss DSI error: VC(0) busy when trying to configure it!
<3>[ 15.023651] omapdss DSI error: VC(1) busy when trying to configure it!
<3>[ 15.030517] omapdss DSI error: VC(2) busy when trying to configure it!
<3>[ 15.043090] omapdss DSI error: VC(3) busy when trying to configure it!
<3>[ 16.246856] omapdss DSI error: Failed to set dsi_vc_enable to 1

The line on the bottom is the actual error. On the 3.0 kernel, I had the "VC(X) busy when trying to configure it!" errors, but the screen still initialized despite those errors for the 3.0 kernel, not so much for the 3.4 one. More digging to do... Anybody out there got a tip on this??
[Samsung Galaxy Nexus] Dameon87:
I'd have to take a serious look, but one of the big things from a port i helped with on the epic 4g was ensuring that all the right interfaces are exposed. I know we had a similar issue back in the day. But once again I'd have to sit down and do some trial and error. Ill see if i can this week.
[Samsung Galaxy Nexus] r_data:
Good Work :D It's great! Thank you
[Samsung Galaxy Nexus] josip-k:
Too bad none of the devs would help this guy,he's only one that did something,great work buddy. Renaud,we need you!
[Samsung Galaxy Nexus] ak:
panel

I must apologize for the little support but time is very short.

Maybe a stupid question, you've implemented all the commits related to "OMAP: DSS: panel-s6e8aa0"?
[Samsung Galaxy Nexus] JackpotClavin:
Yes I did a cherry-pick of all the Tuna related drivers up to a certain point from the 3.0 kernel that I know had a working display and touchscreen and whatnot. I just found out that the 3.0 kernel that Google uses has a very outdated dss driver, so perhaps using the old dss video drivers would be the way to go, but when I tried using those, the device locked up on boot wouldn't even enable USB debugging so I couldn't get any dmeg logs
[Samsung Galaxy Nexus] tomixdev:
i wonder which kernel version comes with ubuntu for phones :confused:

good luck :good:
[Samsung Galaxy Nexus] Lesicnik1:
Since it'll use the android kernel that is supported natively on that device, it won't be any help here.
[Samsung Galaxy Nexus] renaud:
Why did you choose to use a vanilla 3.4 kernel instead of the android 3.4 kernel?
[Samsung Galaxy Nexus] JackpotClavin:
Because the Android 3.4 doesn't have the newest mach-omap2 parts like the head of the Linux 3.4 kernel did. I merged them anyways so we have all the Android kernel parts now for 3.4

Anyways, this project is pretty much dead now unless somebody can help get the display to work as I've run out of ideas
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't know if you guys could help each other http://xdaforums.com/showthread.php?t=2044262

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] deepayanneogi:
I wonder why all the Kernel devs are not taking this project seriously, this really is a great project to show off your skills.
[Samsung Galaxy Nexus] renaud:
Because it's a long work and it can break your device. Now if you want to offer devs phones on which they can work, there will be more people. But in my case I need a working phone. I don't mean I will not work a little bit on this, but it's not on my priority list. Also, when I ported 3.0 to the SGS, it was released a little bit afterwards, which may still happen with 3.4 for the nexus.
[Samsung Galaxy Nexus] JackpotClavin:
I thought 3.0 came out on the Nexus S when ICS came out?
[Samsung Galaxy Nexus] thegtfusion:
No, 3.0 came out with the Gnex with ics.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] pvkiniyan95:
Guys what's this https://android.googlesource.com/platform/hardware/ti/omap4xxx/+/android-4.4_r1
[Samsung Galaxy Nexus] tobiascuypers:
Yes there are, but I think we should focus at the Fatal errors first, those are more important.

---------- Post added at 10:14 AM ---------- Previous post was at 10:12 AM ----------

It seems to be the same thing mentioned here:
[Samsung Galaxy Nexus] fcisco13:
Its the same thing that's been posted here, there, and everywhere. If you don't know what it is don't touch it!

WHATCHOO TALKING BOUT WILLIS?