yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] akira02rex:
Frank, I think you may be wrong. This was the last news I heard from them:

http://www.gsmarena.com/clarification_ti_not_giving_up_on_its_chipsets_omap_5_on_track-news-4866.php

Not only that, but the OMAP5 section is still on TI's website regarding development.

I love how people post these rediculous claims with nothing to back it up. :rolleyes:
[Samsung Galaxy Nexus] ak:
Very good work .... Go to your goal :thumbup:
[Samsung Galaxy Nexus] Savant:
No reason to be disrespectful.
[Samsung Galaxy Nexus] bbedward:
I'll look at your source tomorrow
[Samsung Galaxy Nexus] eng.stk:
Would be awesome to have some of kernel devs that already replied on this thread, working on this kiss a** v3.4 kernel.

Our GNex would feel so good with the vitamins :fingers-crossed:
[Samsung Galaxy Nexus] akash3656:
The developers of ZenX and AK have commented. Franco even commented in here and got shot down by someone. I don't see what more are you asking for. :confused:
[Samsung Galaxy Nexus] Sparx639:
We better get upgrading then huh?
[Samsung Galaxy Nexus] Loureiro:
That just means we wouldn't receive updates anymore, nothing to worry about.

Get a 3.4 working is not that simple, need all the drivers revised to work with 3.4, not a easy task.
[Samsung Galaxy Nexus] Pasquale91fg:
WATCH THIS THREAD : http://xdaforums.com/showthread.php?t=2474428

There is in these thread the link for the download of the kernel 3.4 for galaxy nexus !!!! need developers !!!
[Samsung Galaxy Nexus] bsmitty83:
What are we watching for ? Source ? Because until that happens it might as well be a 5.8.01 kernel for all that it matters
[Samsung Galaxy Nexus] creepinm3:
So I've found that random 3.4 kernel from that thread. Will upload here so someone can have a crack at it.
[Samsung Galaxy Nexus] bsmitty83:
If its not the source code its useless, not to mention against GPL to post a kernel without source .
[Samsung Galaxy Nexus] Sparx639:
I thought amperific was working on it anyways? Just wait.
[Samsung Galaxy Nexus] mrgnex:
No he sold his gnex and now has a broken one..
[Samsung Galaxy Nexus] Castro27:
Oh well, nexus 5 here I go
[Samsung Galaxy Nexus] drive2droad:
The developer mentioned in the thread who created the 3.4.x kernel is the same guy who put out HyperKernel on xda , may be he can help us out !!
[Samsung Galaxy Nexus] creepinm3:
Wrong, his GNEX broke and I am taking over his kernel work for Maguro.
[Samsung Galaxy Nexus] Vekhez:
[MENTION=5310723]Amperific[/MENTION] is rewriting them already I believe.
[Samsung Galaxy Nexus] mrgnex:
Awesome I was afraid his kernel would be eol.. But are you going to build 3.4?
[Samsung Galaxy Nexus] creepinm3:
As soon as I study and understand what I am doing I will give it a try. I don't want to do it blind and end up frying some one's device.
[Samsung Galaxy Nexus] Pasquale91fg:
I tried a Kernel 3.4.33 for galaxy nexus create by Jijonhyuni! It work but after usage it freeze!!
[Samsung Galaxy Nexus] drive2droad:
I have removed the attached kernel zip as many people are trying to flash a kernel with GPL violations & no source code . I am not the developer of this kernel & merely linked it from another thread .
[Samsung Galaxy Nexus] Pasquale91fg:
Yes, this is the kernel !
[Samsung Galaxy Nexus] miseusegau:
tried but does not start, hangs after the bootanimation ...:rolleyes:

** so it is not developed for our nexus?

★sent by zio★
[Samsung Galaxy Nexus] Pasquale91fg:
Yes this kernel is create for gnexus !!! I tried and work!!
[Samsung Galaxy Nexus] Sik-1:
Works on wah???? ROM????
[Samsung Galaxy Nexus] miseusegau:
I tried to mount it on AOSP ROM, use the lean kernel, I did wipe cache and Dalvik but the nex did not finish the boot ....

★sent by zio★
[Samsung Galaxy Nexus] Pasquale91fg:
Aokp mr2 nightly 18/10
[Samsung Galaxy Nexus] jhonnyx:
that 3.4 kernel worked on stock rom & cataclysm on my side;

note: tried to change governors and rebooted. It's very unstable & laggy; that's why it's unreliable; also just wanted to test it; not for a daily driver
[Samsung Galaxy Nexus] Sik-1:
Sounds fun I'll give it a try lol
[Samsung Galaxy Nexus] Sparx639:
It boots on cm10.2 but it had the phone stopped unexpectedly problem like other kernels
[Samsung Galaxy Nexus] Grarak:
That has nothing to do with the kernel itself

These kernel guys are just too lazy to update the ramdisk
[Samsung Galaxy Nexus] Sparx639:
I know, I was just putting that out there for anyone else on cm10.2 to try it. I might fiddle with it and try to get it working
[Samsung Galaxy Nexus] Saythis:
After converting it to any kernel format it seems to run nicely on codefireXperiment ROM.
[Samsung Galaxy Nexus] thegtfusion:
share plz!!! :D
[Samsung Galaxy Nexus] Sik-1:
Plz do share I was jus downloading the latest just now, would love a clean flash test
[Samsung Galaxy Nexus] Saythis:
Assuming since development is halted its safe to post this. So here you go :)
[Samsung Galaxy Nexus] jhonnyx:
Please comment what happens if you tune it with governors. Hanged a few times already.
[Samsung Galaxy Nexus] Edward Stanbury:
wow im amazed how fast it is when it doesnt hang omg i hope the development continues !

edit: just realised i had an undervont script running haha time to remove that and try again
[Samsung Galaxy Nexus] adio201:
Will this work with toroplus?
[Samsung Galaxy Nexus] Edward Stanbury:
it should, but like everyone said its not very stable :P
[Samsung Galaxy Nexus] thegtfusion:
Maybe [MENTION=4544860]osm0sis[/MENTION] and [MENTION=3292224]franciscofranco[/MENTION] could take a look. :D :D
[Samsung Galaxy Nexus] Edward Stanbury:
i hope so! it seems faster and smoother to me ;) could just be my mind playing tricks but hey it would be awesome to get a stable version
[Samsung Galaxy Nexus] adio201:
Booted up fine just got frezze screen twice after boot
[Samsung Galaxy Nexus] thegtfusion:
Couldnt resist. Flashed it. Its faster, but really unstable. I would love to see franco working on this

---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
[Samsung Galaxy Nexus] Edward Stanbury:
+1 to that haha !
[Samsung Galaxy Nexus] drive2droad:
The problem here is no one except Amperific is interested to develop it any further .
[Samsung Galaxy Nexus] bsmitty83:
Besides someone coding the drivers themselves , we need a source to start with . can't do anything with the kernel posted . without source how do you even know its a 3.4 kernel ? Anyone can change the makefile . idk but until someone coughs up a source the posted kernel is as close as your gonna get , don't expect a dev to work their magic on a .zip
[Samsung Galaxy Nexus] drive2droad:
It seems you haven't read my prevoius posts before coming to a early conclusion , I have clearly stated that this kernel is a dud since the developer has shared no information on source . I understand no one will work on this mysterious zip file but now no one wants to develop the 3.4 kernel at all , this project has hit a roadblock .
[Samsung Galaxy Nexus] Vekhez:
I can extend the time before freezes, by UNDERCLOCKING and overvolting (+10), and changing the govenors.. get about 1m of usage...but eh. Went to the new Faux till tomorrow (KitKat hopefully :D :D )
[Samsung Galaxy Nexus] MBQ_:
Might as well join the party.
[Samsung Galaxy Nexus] Pasquale91fg:
Maybe! Could you help us???
[Samsung Galaxy Nexus] Grarak:
faster?

I flashed that too but no difference from my previous kernel

I doubt that is a 3.4 kernel
[Samsung Galaxy Nexus] MBQ_:
Kernels aren't my thing.
[Samsung Galaxy Nexus] aosp:
Google ain't got time for no tuna kernel but OMAP is still working on the chip set past 3.4y take a look at ;) http://omapzoom.org/?p=kernel/omap.git;a=summary
[Samsung Galaxy Nexus] MWisBest:
Exactly. There's even a 3.10.y kernel somewhere if I remember correctly.
[Samsung Galaxy Nexus] creepinm3:
So this link is a sign that people are still working on GN? http://omapzoom.org/?p=kernel/omap.git;a=summary
[Samsung Galaxy Nexus] siddardha21:
Let me give my 2cents of advice.

As ti has stopped developing for our board and killed the program. There is no reasonfor ti to keep the drivers closed. They should release the drivers which will make developing 3.4 kernel easier. So instead of shouting at google for not releasing the 4.4 update and signing petitions. Just request texas instrumentation to release the required drivers as they already killed the program and won't need them. Hope people understand what I'm talking about. They could keep it closed if they were still continuing in this business. But they are out of this game. So they don't need them anymore. So ask them them to release so that we could use.

Cheers!! :thumbup:
[Samsung Galaxy Nexus] drive2droad:
As far as manufacturers go they rarely change their stance . I doubt that TI will release documentation relating to 3.4 kernel source .
[Samsung Galaxy Nexus] MWisBest:
Not exactly, but it shows that the OMAP4 isn't abandoned entirely.

I agree with this, but I doubt there will be enough demand and pressure in order to really get a message through to them. Look at the Linux GPU Drivers for instance: Intel is completely open-source with no proprietary driver whatsoever, Nvidia has been completely closed-source with only a reverse-engineered and unsupported open-source driver until recently where they now are apparently trying to release documentation and assist the open-source reverse-engineering developers, and AMD has had both a closed-source proprietary driver and open-source driver, and the open-source driver had been pretty lackluster until more recently and their open-source driver does have official support and whatnot.

Do you want to know what it took to push such a change to improve Linux GPU drivers? Valve, the company behind Steam and multiple successful video games, who is pushing to build their own Linux-based gaming console. It took a HUGE company with lots of user support to make a change. That should put into perspective what it would probably take to get TI's attention.

I wouldn't doubt if they release some documentation at some point, we'll just have to wait and see. Regardless, like I've already stated, there is a 3.4.y OMAP4 kernel and at the very least a 3.8.y one as well. I believe Ubuntu has been using OMAP4 as a step into the ARM platform, and that may be why there is still some interest in it. Maybe we can get Canonical (the company behind Ubuntu) to push TI around a bit.
[Samsung Galaxy Nexus] siddardha21:
Ya. Just hope that ti gives us some sort of documentation.

Little off topic

There's this amazing dev called NAa who brought 3.4 kernel to xperia 2011 which was stuck at 2.6.xx kernel. He built it frm scratch. And all of qvga phones running cm9 and use his sources to build. When i was on x10 mini pro. He moved to galaxy nexus. So i thought he should be here somewhere. May be we could request him to get 3.4 working for us. He was a legend. :confused:
[Samsung Galaxy Nexus] Godra:
nAa is insane dev haha He created custom ROMs for all 2010 and 2011 Xperia phones. Deffinitly one of the best devs out there and he has a Galaxy Nexus,but once he told that he won't make anything for GN as there are already enough devs for it. Well, nAa, we need you now :D
[Samsung Galaxy Nexus] drive2droad:
CAN'T WE PERSUADE NAA ?? (All caps added to show desperate measures required)
[Samsung Galaxy Nexus] :
here: http://xdaforums.com/member.php?u=788040
[Samsung Galaxy Nexus] jhonnyx:
Let's hope he does not receive a mass-flow of PM's
[Samsung Galaxy Nexus] tommrazek01:
Maybe a mass-flow of PM's is what will convince him (I imagine, it can be annoying too) :D. Let's just hope...
[Samsung Galaxy Nexus] aosp:
You guys might want to send over a spare GNex over too [MENTION=4243514]Hashcode[/MENTION] he does great OMAP 3.4 kernel work on the kindles https://github.com/KFire-Android/kernel_omap_otter-common/commits/p-android-omap-3.4

https://github.com/KFire-Android/android_device_amazon_otter/commits/cm-10.2-k34

https://github.com/KFire-Android/android_device_amazon_omap4-common/commits/cm-10.2-k34

;)
[Samsung Galaxy Nexus] kuronosan:
Wish I could spare one.
[Samsung Galaxy Nexus] tobiascuypers:
Lets hope he can! He is a pretty busy guy tho, with 4 kindles and nearly every Motorola device in the past 2 years
[Samsung Galaxy Nexus] Sdobron:
He abandoned his 3.4 kernel for Kindle, most likely permanently.
[Samsung Galaxy Nexus] eternal70:
I think no. He just update something 5 days ago........
[Samsung Galaxy Nexus] Sdobron:
My mistake, looks like just a temporary break due to lack of time. He's back in the game now.
[Samsung Galaxy Nexus] tobiascuypers:
Ive been keeping in touch with him even after I sold me kindle. Hes working on getting on kernel for all4 or the kindles. Tough project
[Samsung Galaxy Nexus] nixholas:
Please dudes. Use google. (: The OMAP 4 3.4 Sources are available a long time ago. it's on my github. But I'm unable to work on it anymore though.
[Samsung Galaxy Nexus] bsmitty83:
If your source on github for your 3.4 is private can you make it public if your not continuing your work ? Just a humble request from an amateur :beer::beer:
[Samsung Galaxy Nexus] Utkarsh-ezzo:
[MENTION=4790322]kufikugel[/MENTION] may be this could help you...
[Samsung Galaxy Nexus] eternal70:
Found this....... 3.12 for omap4 ????

https://github.com/robclark/kernel-omap4/tree/global-thermonuclear-war-2
[Samsung Galaxy Nexus] Pasquale91fg:
I just sent an email to the developer!
[Samsung Galaxy Nexus] ilgimmy:
It seems that also a 3.12 OMAP tree is mantained here: http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git

More info here: http://omappedia.org/wiki/Linux_OMAP_Kernel_Project

But I suppose that a Kernel dev already have this info.
[Samsung Galaxy Nexus] creepinm3:
Looks like we still have some hope after all. Amazing.

-----------------------------------------------------------------------

So with this 3.4 and 3.1x kernel source upon us we can choose to have either one or which ever seems more logical to use? Or are we just looking for someone who is capable of developing on the source?
[Samsung Galaxy Nexus] Utkarsh-ezzo:
IMO 3.4 has all that is needed for kitkat,

also our main kernel developers are either on holiday or busy with personnel life which is not at all a bad thing, so we have to wait ,

mean while kufikugel and garak are working real hard , may be theybcam buid from the available sources,

hope the sources are correct and complete..
[Samsung Galaxy Nexus] drive2droad:
Just my 2 cents here , Linux kernel 3.12 is much faster & STABLE but may be much harder to port for the galaxy nexus . I have one question too : what is the kernel version for nexus 5 ?
[Samsung Galaxy Nexus] Utkarsh-ezzo:
its 3.4
[Samsung Galaxy Nexus] creepinm3:
Sidebar: But what version of MPK kernel are you running on your GN.
[Samsung Galaxy Nexus] :
A kernel does not get ported, but needs to be compiled for another architechture. However, updating to 3.12/3.4 would mean rewriting drivers, because of the different way the kernel reads and handled drivers different.

Note: im not a developer, hope i exlained it enough.
[Samsung Galaxy Nexus] Maromi:
fyi

Amazon's 2013 Kindle Fire HD 2nd gen is omap4 with a 3.4 kernel and they released their source code http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
[Samsung Galaxy Nexus] eternal70:
But, at least we need a developer who is interested in porting the kernel..........
[Samsung Galaxy Nexus] bsmitty83:
It doesn't matter , there's many devices that are omap4 on 3.4 , the problem is there is no tuna specific 3.4 board files in existence. Unless it shared the same board , and hardware it doesn't really help . it sucks but that's the problem , finding a 3.4 source isn't .
[Samsung Galaxy Nexus] drive2droad:
I am using the 1080p version on CM10.2 Nightly !!
[Samsung Galaxy Nexus] Culex316:
But doesn't that SOC include everything? I mean the OMAP4460 kernel source should have the drivers for the IVA hardware accelerator/Ducati, CPU scaling, GPU, etc., basically anything that isn't an external component (Touchscreen, display, etc), and is included in the OMAP4460 SoC package right?
[Samsung Galaxy Nexus] bsmitty83:
yes and no

there is no tuna files in the kindle source but i might be able to use the board file as reference to re-write the tuna board file , idk but i do think it might help

..........I just looked at that source and it really no help , it uses all different GPU , touchscreen, ect . All the drivers from the 3.0 nexus kernel would need to be rewritten for us to get a 3.4 kernel , there's just no way around it .
[Samsung Galaxy Nexus] Prasad:
I'm relatively a noob and just trying to understand, hopefully contribute too. I've been following this up for a while now and wondering why the 3.4 Linux kernel can't use our gnex drivers from a 3.0 kernel? I mean except for the lack of OpenGL 3.0 support, where are we really behind? Sure we don't have updated drivers, but why can't 3.4 use the 3.0 drivers??
[Samsung Galaxy Nexus] bsmitty83:
No worrys man thats what were all here for , I'm by no means an expert but I've been trying to build a 3.4 kernel for a while now and there's just ALOT of code changes , different files etc ...
[Samsung Galaxy Nexus] Prasad:
Okay. I'm downloading the source myself now to try and understand. Aren't many subsystems in our smartphones running on binary blobs as-is ? I take it these are the parts that we can't edit/port to elevate upto 3.4 compatibility?
[Samsung Galaxy Nexus] nixholas:
Let's give everyone a simple explanation a'right?

OMAP has released the sources needed for us to start.

BUT.

Without any TUNA specific codes, it means devs would have to write the codes. Moreover, writing the codes take a veryvery long time for one person. you'll need a team. Why? See the manufacturers. they have a team to develop a phone. Just like that. And also, writing the drivers for the hardware is very painstackingly hard. We need to tri and error at times due to insufficient information on the specific module.

Just my two cents.
[Samsung Galaxy Nexus] Vekhez:
0.o AOSP on MAKO?! You still working on 3.4 for the Galaxy Nexus? Or have you abandoned use like AK?

That's sounds like I am being brutal.. nope, just asking :D
[Samsung Galaxy Nexus] Prasad:
Got it all. Bottomline: not feasible (without a paid team)
[Samsung Galaxy Nexus] mrgnex:
Why paid?
[Samsung Galaxy Nexus] TinyFeather:
Why is 3.4 so hyped?
[Samsung Galaxy Nexus] gnustomp:
It's the kernel version that current Android devices run on, and has more features and fixes than our current EOL'ed 3.0 kernel.
[Samsung Galaxy Nexus] tommrazek01:
So, to make this clear, would 3.4 anyhow help the current graphics glitches occurring on Maguro and Kitkat? I see how this is useful, but if this could also "heal" those glitches, than this would probable be the most important thing to get done with Maguro at the moment.
[Samsung Galaxy Nexus] gnustomp:
On its own, no, but with the kernel and all the compatible blobs and drivers would mean everything working kernel-wise. Problem is OMAP is sort of abandoned.

This is at least part of the reason Google isn't updating the gnex to 4.4.

(Do I sound like I don't know what I'm talking about?)
[Samsung Galaxy Nexus] Carlos_Manuel:
The issue should be in frm-native and/or in the imgtec vendor files.. ? and not in the kernel. Evem if nexus would get working 3.4 kernel it doesn't fix any graphic glitches...
[Samsung Galaxy Nexus] aosp:
Wanna talk about a team how about the TI OMAP dream team?

robclark https://github.com/robclark

andygross https://github.com/andygross

mturquette https://github.com/mturquette

nmenon https://github.com/nmenon

kontar https://github.com/kontar

Hey you never know they might care and be willing to help ;)
[Samsung Galaxy Nexus] Mevordel:
Exactly. If we need a team, then let's find one or start one!
[Samsung Galaxy Nexus] eternal70:
Yes, why don't we start a team. If we are not a developer, maybe we could ask for help :)
[Samsung Galaxy Nexus] aosp:
OK as you this pic shows

Google don't care for our GneX so no support for our device as you see the last update our GPU received from them is outdated

gpu: pvr: Update to DDK 1.8@2198402

http://goo.gl/hgt5D0

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

http://goo.gl/YvA69z

But lucky TI and IMGTEC support what they create long after releasing it to the market yeah 18 months is crap support and a horrible way to set an example thanks Google

Thanks for the tip and yeah no hard feelings TI and IMGTEC are cool with me ;) So yeah with the commit below I was told you can patch the GNeX kernel and use the updated ducati, sgx gpu, and gralloc bins provided

IMG*DDK*Release*1.9@2166536*for*Android.

http://goo.gl/pCss4q

They also might be updated soon so stay tuned and like I said thanks Google for no support that's how you show the OEMS how to do it ;)
[Samsung Galaxy Nexus] Loureiro:
That is really great aosp, will definitely stay tuned ;)
[Samsung Galaxy Nexus] Castro27:
Hold on. Let me get this straight, are these new GPU drivers? If so, do 4.4 devs know about this?
[Samsung Galaxy Nexus] nikodr:
Does that mean that the roms that are alpha now for maguro that are 4.4 could have proper kernel ?The gfx bugs and all the glitches would be gone?Is it for toro also ?Thanks
[Samsung Galaxy Nexus] aosp:
Oh yeah I forgot this was committed soon after the patch Google gave us look at the dates ;)

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

Nexus support from Google lol
[Samsung Galaxy Nexus] Castro27:
I've forwarded your posts on the A taste of kitkat threat. I hope that's not a problem
[Samsung Galaxy Nexus] nikodr:
Me too,i wanted to inform developers about it.Hope there is no problem ?
[Samsung Galaxy Nexus] tacosrdelicioso:
Wait what the hell just happened?!!!! This is getting interesting
[Samsung Galaxy Nexus] nikodr:
It seems to me that after google gave the last 4.3 android for galaxy nexus,ti and imgtec posted updated binaries for it.so the new updated binaries were given after google's update,t maguro could have proper gfx support if a new kernel is updated to use these binaries.

hahaha
[Samsung Galaxy Nexus] tacosrdelicioso:
And toro! I have toro haha. Google why you make us sad when there IS hope
[Samsung Galaxy Nexus] nikodr:
AOSP could answer that to us.The kitkat on nexus 4 or other devices does it use ddk 1.9 ?

It seems that we have to wait for developers to make new kernels and update the roms :)
[Samsung Galaxy Nexus] Injek:
Things are getting exciting!
[Samsung Galaxy Nexus] Kaemo:
Can some do a ELI5 on what just happened?

What does this mean and how can we use this?
[Samsung Galaxy Nexus] Castro27:
Looks like AOSP found some updated binaries for the phone's GPU
[Samsung Galaxy Nexus] Prasad:
Epic progress is epic. You guys pave the way and remind Google why Android exists in the first place!
[Samsung Galaxy Nexus] nikodr:
So i think the following days we would have updated kernels and fixed roms with no glitches and proper gle 2.0 support :)
[Samsung Galaxy Nexus] sefirosu0522:
This is insane! Looking forward to the next few days.
[Samsung Galaxy Nexus] Pasquale91fg:
Who kindly explained to me what happened?? 've missed a few hours and I can not understand ..
[Samsung Galaxy Nexus] nikodr:
http://xdaforums.com/showpost.php?p=47151583&postcount=282
[Samsung Galaxy Nexus] tacosrdelicioso:
Read. Its been told several times
[Samsung Galaxy Nexus] Pasquale91fg:
I have read but I did not understand much! We have received an update to the kernel?
[Samsung Galaxy Nexus] fk.gregor:
Does this mean the graphics glitch will be fixed.
[Samsung Galaxy Nexus] tobiascuypers:
It doesn't mean anything until we get a semi-functional kernel. I'm taking a look at it now actually, seems there might be since hope. I'll see what I can do with my limited resources ATM:p
[Samsung Galaxy Nexus] AbhishekS:
This is getting interesting. I have a good feeling about this. :D
[Samsung Galaxy Nexus] creepinm3:
Subscribed to this right away.