yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aosp:
Some of you are finally getting it nice but my info was intended for devs ;) [MENTION=4608636]bsmitty83[/MENTION] you missed my other posts Google only patched pvr and reverted cause it's the gnex is not worth the effort but seriously other changes to our kernel are required to leave the ics gpu drivers they gave us for starters

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

And yes the surface flinger will benefit as this patches ducati and gralloc I linked the source and the binaries are included but kernel video and gpu drivers need to be patched with the source first before using the bins ;)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] IMG*DDK*1.9@2166536*for*Android

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

Included*in*this*release:

-*User*space*and*Kernel*module*binaries

-*Kernel*module*source*code

TI's*Patches:

-*084d3db*SGX-KM:*sgxfreq:*Enable*on3demand*governor*as*default

-*c1e1f93*SGX-KM:*on3demand:*Added*polling*based*on*timeout

-*1baf19c*Build:*Compile*OMAP4*kernel*modules*with*arm-eabi*toolchain

-*e166956*Build:*Add*production*build*option*to*build*script

-*9efd5d3*SGX*UM:*Properly*update*vertex*shader*constants*when*recompiled

-*f6e71f1*Revert*"Build:*Add*optional*flag*to*disable*uKernel*logging"

-*a49e042*SGXKM:*Inherit*PVRSRV_HAP_GPU_PAGEABLE*flag

-*f05da87*SGXUM:*Creates*a*new*PVRSRV_HAP*MAPPING*CTRL*mask

-*0e6ac23*SGXKM:*Creates*a*new*PVRSRV_HAP*MAPPING*CTRL*mask

-*5044cbb*SGXKM:*Divorce*Sparse*Mapping*from*GPU*Pageable

-*4abdd37*SGX-KM:*sgxfreq:*Header*for*GPL*license

-*7a1e61b*gpu:*thermal:*adding*cooling*device*for*"case"*management

-*1221aba*SGX-KM:*Add*'userspace'*governor*to*sgxfreq

-*7cc1319*SGX-KM:*Add*on3demand*governor*to*sgxfreq

-*c3283ff*SGX-

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

http://goo.gl/94ZTEM

http://omapzoom.org/?p=device/ti/pr...2abfc8ed97d7;hb=refs/heads/d-jb-mr2.0-release
[Samsung Galaxy Nexus] akash3656:
[MENTION=2838735]aosp[/MENTION] if you can suggest the commits to add, I'm pretty sure you maybe can build a kernel with the binaries as a flashable zip? I'm not entirely sure if you own the Galaxy Nexus, it would be great if you whipped up a build especially if you own a Galaxy Nexus.

I was just thinking about it haha.

I myself have built from source, but I stopped there. Never really tried to venture into cherry picking or building custom kernels and all that. I don't really even understand how git and stuff works in detail.

And we can gladly test it out. Right now, I think most users want something that can solve that nasty surfacelinger glitches and not really a 3.4 kernel. But a 3.4 kernel would be nice, but its a lot of work from what I hear.

PS: I'm not basing aosp or anything or saying he owes us something, I'm just asking nicely if he could build something in addition to pointing develops to the right direction.
[Samsung Galaxy Nexus] kenshin33:
except from the kernel drivers (modules or built-in) my guess is you need an updated GL libraries and gralloc

which may be you can find here http://omapzoom.org/?p=device/ti/proprietary-open.git;a=summary

http://omapzoom.org/?p=device/ti/proprietary-open.git;a=summary
[Samsung Galaxy Nexus] nixholas:
In other words, we have everything we need to make the kernel work.

But the major leap required is to gather a GNex dev team to work on the kernel if not it would take years.

If you'd like to join the Open Galaxy Nexus Project, Please PM Me. I'm forming a team to work on 3.4.

Take note. I'm only going to commit fixes report by the other team members as I do not have the phone itself already. Ok I have it, but like you guys know, it's just a useless paperweight due to a fried circuit.
[Samsung Galaxy Nexus] bsmitty83:
I did try that at one point I used the prebuilt sgx gralloc module and still still nothing but I probably screwed that up since I was getting snowblind from looking at code for so long .

Its a strange commit since all the PVR files are updated , yet the hang up is the second commit uses new omaplfb files at a different location than where it currently is , on top of that the 2nd commit assumed your using a 3.4 kernel which its sourced from , so there's lots of .h files missing . after a few hours of finding and adding all of them , I'd start to get build errors , lots of redefinitions across multiple files , so yea its not as straightforward as I'd hoped .

IMHO its as if they started to try to integrate the DDK1.9 into the 3.0 branch but 4 days later reverted the commit and updated the DDK1.8 one last time . so I'm sure it can be done , but I'm not sure how much success I'll personally have . I'll still work on this tho , i love a challenge :cool:
[Samsung Galaxy Nexus] creepinm3:
I am willing to sell my Galaxy Nexus to help a dev in need. Got my new phone now.
[Samsung Galaxy Nexus] misterk267:
What model do you need? I have a toro that I may not need after my contract is over. If I don't need it, I would be willing to donate it to the project. Since I don't know yet what my situation will be like then, I can't guarantee anything though. :P
[Samsung Galaxy Nexus] IT_Blackbelt:
Have you talked to the major kernel developers here on XDA, it seems like getting the best together for this only makes sense.
[Samsung Galaxy Nexus] Vekhez:
[MENTION=5310723]Amperific[/MENTION] ?
[Samsung Galaxy Nexus] ashclepdia:
Seems that person wants to at least get something back for their investment into the hardware which I do not blame them for at all.

But I also do not expect a developer(s) to buy a device just so we(users) can benefit afterwards from their hard work AND their hard earned money put up for said device.

If a Dev DOES buy gnex just to help us all out I'd be forever grateful no doubt, but maybe it would be better to pool together and purchase said device for a willing developer in HOPES(aka NO GUARANTEE, MAYBE, NO EXPECTATIONS OF A FINISHED PRODUCT, merely "HOPE that things will continue moving forward for this device" kind of thing) to show that the users still have faith in the devs and devixe .

In other words, SHOW that we care, SHOW we dont feel entitled, SHOW we are grateful for everything we have gotten THUS FAR (which has been AMAZING THANK YOU DEVS! just imagine if all devs looked at gnex like Google is doing right now as a "dead device"..... ugh I cannot imagine....)

BUT

Do NOT turn THIS thread in A DEVELOPMENT SECTION into another "bounty thread"

I'm not even saying to start a "bounty thread" kind of thing.... I'm just saying, showing the appreciation goes a long way.

I admire any who are willing to keep this device "alive" as we know it to be and thank all that are currently trying also!
[Samsung Galaxy Nexus] galapagos:
LOL. Selling a phone to a dev?
[Samsung Galaxy Nexus] creepinm3:
You make it sound unethical. I do have bills to pay and don't have need to an extra device to sit around. I've sold 2 devices to HTCClay and it was for the same cause.
[Samsung Galaxy Nexus] kuronosan:
Developers don't have a lot money as is, and your phone isn't really worth much anyways.
[Samsung Galaxy Nexus] ashclepdia:
I tried to quote you but got error(bug report sent to tapatalk)

NO NO NO PLEASE DO NOT TAKE OFFENSE!

I MEANT NOTHING BAD TOWARDS YOU I AM SORRY!

that is why I clearly stated that "I DO NOT BLAME YOU FOR TRYING TO GET ANY RETURN ON YOUR HARDWARE INVESTMENT"

Honestly, I THANK YOU for posting here first about the device being available.

My main point was that I would love to see community step up to purchase YOUR device (which is why I quoted YOUR post) in hopes of future development. I meant NO disrespect towards you for the offer you gave. I mean to actually THANK YOU!)

My only wish is that I could encounter enough $$ to purchase device FROM YOU to give to a developer.

Again, apologies, I did not try to imply that you were trying to hold ransom or anything for your device. In the contrary, I fully support you and hope that your device ends in the hands of a developer.

Sorry ;(

---------- Post added at 02:19 AM ---------- Previous post was at 02:17 AM ----------

No no no

That is NOT what I meant by my reply.

I was suggesting that we all group together and purchase this device from a loyal user and GIFT IT towards a willing Dev
[Samsung Galaxy Nexus] creepinm3:
Okay, I wasn't going to price it expensively.

Understandable, I don't mind helping out at all. Once I got my N4 I mainly use my GNEX as a Pandora station while at work.
[Samsung Galaxy Nexus] Prasad:
This thread is about giving, my friend. And if you haven't really figured that out, I suggest we stop talking about your outdated phone that needs a lot of organized volunteer effort to be updated in the least.
[Samsung Galaxy Nexus] ashclepdia:
Are you talking about the gnex?

Am I the only one confused about what you are trying to say here?
[Samsung Galaxy Nexus] chongns:
[MENTION=2875964]dhiru1602[/MENTION] , any interest in this challenge ?
[Samsung Galaxy Nexus] Prasad:
Yeah. This is a developer's thread, isn't it? Hardly a marketplace. If I were buying a new phone within this window, I'd give away my gnex to another dev. But you see, that's just as useless as saying I'd sell a developer a gnex. ;)
[Samsung Galaxy Nexus] michie:
Guys keep the dev thread clean please, discussions like this dont belong here.
[Samsung Galaxy Nexus] kaijura:
Out of curiosity which toolchain are you building with?

The surfaceflinger problem is a hurdle and hassle to figure out, we had a similar issue previously with adreno205 when Google pushed ics and we were still on drivers made for gb.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I use linaro toolchains normally , but for this I've been using googles 4.6 toolchain .
[Samsung Galaxy Nexus] aosp:
Not sure who told you the omaplfb patch is from the 3.4 branch but that's false all the code I posted applies to 3.0.31 the branch you need to fetch is p-android-omap-3.0

OMAP:*remove*pvr*services*and*omaplfb*from*kernel

These*sources*are*now*defunct

http://goo.gl/HBLSpf

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/7XE33g

Merge*latest*changes*from*google*kernel/common.git

Kernel*version*updated*to*3.0.31

http://goo.gl/AgRrWI
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] p-android-omap-3.0 http://goo.gl/dXCKJh
[Samsung Galaxy Nexus] bsmitty83:
No I'm wrong , i should have said that the commit adds omaplfb to drivers/video/omap2 instead of where's its currently at drivers/GPU/PVR/ . and there's more files in the commit than what we already have , and when you add that commit , its missing a lot of .h files , and it overrides the current omaplfb files . that's where the problem is for me

Edit totally missed the commit to remove the old omaplfb , I was doing it blind before , but now I'm back on it . thanks [MENTION=2838735]aosp[/MENTION]
[Samsung Galaxy Nexus] jaizero:
I have a Toro GNex I'd be willing to "donate"... As long as I get it back someday with a shiny new kernel... If you're serious about getting this done PM me and we can work something out.
[Samsung Galaxy Nexus] dhiru1602:
Hello everyone,

I have been developing CM for Samsung Galaxy SL I9003. It is a OMAP3 variant of the most popular Galaxy S I9000. It was not so popular phone because of its limited availability. It came with 2.6.35 kernel and 2.3.6 Gingerbread. I have ported the omapzoom 3.0.8 kernel to the device with all the drivers and everything working fine. Most of the OMAP3 stuff in 3.0.8 kernel is based on OMAP4. I have a good understanding of the OMAP kernel. I had a choice between 3.4 and 3.0.8 kernel when porting for Galaxy SL, but I have chosen 3.0, since 3.4 kernel didn't have proper support for android since it lacked most parts of the DSS and PVR. I have no clue as to why you guys want to port 3.4 kernel. As far as my observation goes, it wouldn't be worth the effort, since it would require a lot of backporting (DSS, DSSCOMP, PVR, V4L2, Ducati). Is there any specific reason as to why there is a need for updating the kernel?

Here is the 3.0.8 omapzoom kernel that I have ported for Galaxy SL: https://github.com/dhiru1602/android_kernel_samsung_latona
[Samsung Galaxy Nexus] tacosrdelicioso:
The only thing people want really is kk with no glitches
[Samsung Galaxy Nexus] Vekhez:
I believe that people want an updated kernel to 'fix' the 'problems' in KitKat, there are graphical glitches when rotating, in screenshot preview and when the screen locks. Also I believe that people just want a number bump..
[Samsung Galaxy Nexus] dhiru1602:
Kitkat problems are due to the GPU. So unless there is a new gpu driver released by TI, we cannot completely fix it. I don't think that is going to happen since TI stopped working android and it makes complete sense as to why Google wouldn't update the Galaxy Nexus to 4.4

Number bump seems good, but I don't think it's worth the effort involved in porting a kernel from scratch.
[Samsung Galaxy Nexus] kuronosan:
I'm sure it's possible to build a non 3.4 kernel using the updated binaries, yes?
[Samsung Galaxy Nexus] Vekhez:
http://xdaforums.com/showpost.php?p=47151583&postcount=282

?
[Samsung Galaxy Nexus] dhiru1602:
Actually 1.9 DDK is old. It was meant to be used for Jellybean (4.1). DDK 1.10 is released for Jellybean 4.3 which is available from rowboat. Rowboat drivers are a bit different and don't include support for HWC, DSSCOMP and they use different gralloc pixel formats, which don't go so well with the OMX. So essentially what we need is PVR DDK 1.10 released from omapzoom with dsscomp support. If such a driver was released (Which I highly doubt), we could patch it against the 3.0 kernel.

3.4 kernel on the other hand would need some more work with backporting the DSS and DSSCOMP from the 3.0 kernel to make it work with the PVR drivers. DSSCOMP is required for HWComposer and the Display Subsystem (DSS) in 3.0 kernel is different from that of 3.4. Hence, backporting stuff from 3.0 to 3.4 wouldn't be of much gain for the effort that is involved when it comes to porting drivers to the newer 3.4 kernel.

1. 8 DDK which is currently on the GNexus was intended for ICS. On Jellybean, Google implemented the Asynchronous VSync which was the backbone for project butter, but didn't update the driver to 1.9 DDK for some reason.

However, when it comes to 3.4 kernel, it seems like an exciting project although I don't have a GNexus. Count me in guys!
[Samsung Galaxy Nexus] Vekhez:
I understand.

Well, you seem like you know what your talking about, so I won't argue :P
[Samsung Galaxy Nexus] TheMan0790:
Nodding my head in agreement, despite not knowing a single thing about what you mentioned in your post...lol....
[Samsung Galaxy Nexus] bsmitty83:
Although the DDK1.9 is old , the DDK 1.8 is older , so I think the general thought is it will help ...

Although I still find the commit odd , it removes the PVR from being built inline and instead gets made as a module from a source outside your kernel ..

Which I guess is because there's no PVR support (?) anymore . so its like taking a few steps back to take a bunch forward . also I have no idea how it'll work on 4.4 since its a module and selinux is in enforcing mode now . just food for thought I guess ,
[Samsung Galaxy Nexus] aosp:
Pretty much like I said Google gave us ICS drivers sprinkled with Jellybeans then denied us kit Kat's on Halloween. Welcome to the Nexus program :/
[Samsung Galaxy Nexus] shriom_manerker:
lol. so for now, if we do use 1.9 ddk drivers with 4.3, wont that improve performance on 4.3 itself ? what i mean is, if we have these drivers. might as well use it with the current stable verion of androdi the gnex can run
[Samsung Galaxy Nexus] aosp:
[MENTION=4243514]Hashcode[/MENTION] uses them on the kindles

remove SGX from config (use kernel modules now) · f265033 · KFire-Android/kernel_omap_otter-common · GitHub - http://goo.gl/wsqyUp

fixed OMAPLFB config item (thanks chris!) · 3ee6abe · KFire-Android/kernel_omap_otter-common · GitHub - http://goo.gl/GKHnBe

omaplfb: Add omaplfb to the kernel tree · cb0a115 · KFire-Android/kernel_omap_otter-common · GitHub - http://goo.gl/wuVSr6

fix PVR building · 71eca7f · KFire-Android/android_device_amazon_otter-common · GitHub - http://goo.gl/Sw7seH

use sysfs instead of prebuilt egl.cfg · e6ef2aa · KFire-Android/android_device_amazon_otter-common · GitHub - http://goo.gl/jBFDRe

move PVR builds back into devices · 748044e · KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/IcTyPV

Fix PVR symlink for galloc · c6d9e0d · KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/oudVaj

move imgtec files to vendor/imgtec · cc47925 · KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/cUq5BQ

move pvr kernel source to omap4-common · ade6ee7 · KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/JhbJhz

sepolicy: removed buggy powervr policy for now · db63d58 · KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/r49Njq
[Samsung Galaxy Nexus] bsmitty83:
heres my git , still working on it , but if anyones bored .......https://github.com/bsmitty83/SpecialKang-II/tree/ddk1.9-exp

If it needs to be taken care of on the rom side the best I can do is apply changes cuz my computer cant build roms ATM , Ive taken it as far as I can go until roms are made with these changes correct?

Edit : I recently took apart a 4.4 stock ROM and replaced all the libs , bins, and everything else the prebuilt sgx package comes with and still a no go so I might try on a straight up 4.3 or even 4.2 to see of I can at least verify what I'm doing is not moot , also I'm using the prebuilts since I still can't get the external modules to compile with my source , that's my main goal and focus right now .

I found even more commits that are needed maybe tomorrow I can get time to do it , its slow but I'm starting to see the big picture with this update , I think its a matter of time before I get it to work :thumbup:
[Samsung Galaxy Nexus] kuronosan:
Samsung recently started the Tab2 series was going to get Kit Kat. Don't they use the same hardware as the Nexus?
[Samsung Galaxy Nexus] kergefarkas:
well it is using 4430 which is basically the same i guess and if they indeed update it and open source the kernel and make a stable version i think it could be a great place to start. but devs can say mor on this i think :)
[Samsung Galaxy Nexus] MWisBest:
[MENTION=2838735]aosp[/MENTION] you keep talking like you know what needs to be done, yet I don't see you doing anything... why is that? :S I don't mean to be rude, I'm just confused is all.

Aaaand before people are quick to chew me up alive, https://github.com/MWisBest/ projects kernel_samsung_tuna and proprietary_vendor_imgtec branch android-4.4-exp

Kernel stuff is a little out of my league in my opinion, I'm just frustrated with all this talking and no action taking.
[Samsung Galaxy Nexus] aosp:
I was wondering why I was even posting here thanks for reminding me. Guys never feed the trolls they go away once you ignore them I promise [MENTION=4608636]bsmitty83[/MENTION] you on it dude good luck ;) GNeX ain't finished have a little faith fellas.
[Samsung Galaxy Nexus] Vekhez:
http://www.youtube.com/watch?v=HpixdTlYlKU

Please stay! You know what you are talking about, we just need a strict mod here that'll ban all the trolls. Got anyone in mind?
[Samsung Galaxy Nexus] MWisBest:
Guys, I meant no disrespect, I was just wondering what's up, like if he's busy with things in life, etc. He has pointed us devs in the right direction, don't get me wrong, it just seems like he'd know how to get things done. I don't mean to be a troll. TBH, I have Asperger's Syndrome, a form of autism. One of the big struggles I face with it is social skills, part of that being not always understanding how things come across to others. Every time I'm faced with a situation such as this though, I'm able to use it as a learning experience to avoid similar ones in the future. I'm not asking for your sympathy, just your understanding.

I did give it a shot myself, hence why I had linked what I had up on GitHub.

[MENTION=2838735]aosp[/MENTION] I apologize for how I came across, I really didn't mean to be disrespectful, and I appreciate what you have done here for the community. We'll have these updated drivers working soon enough, and nobody could do it without the help and advice you've provided here.
[Samsung Galaxy Nexus] aosp:
None taken dude it's the internet. We all want the GNeX to win and that mission will succeed no worries ;)
[Samsung Galaxy Nexus] N00BY0815:
Since I dont know if it helps or not, I ll just post it and let you guys decide :)

I own a LG Optimus L9 and its' chipset is TI OMAP 4430, which is quite similar to yours I guess.

my /proc/pvr/version says:

Version

blaze_sgx_ogles1_ogles2_GPL sgxddk 18

1.8@869593 (release) omap 4430_android

System Version String: SGX revision = 1.2.0
[Samsung Galaxy Nexus] bsmitty83:
OK so after a weekend of trying to get the sgx modules to build , I'm still stuck on this error, I obviously know it has to do with the framebuffer , but I don't know how to fix it , there's still a lot to try but this one is killing me .

I've seen a commit to keep ddk in GPU/PVR , seen it in video/omap2. It looks like that's where it should be but it doesn't build like that , it builds if you keep it in GPU , but no working screen so idk guys , that's where I'm at with it

Here's the error

MODPOST vmlinux.o

GEN .version

CHK include/generated/compile.h

UPD include/generated/compile.h

CC init/version.o

LD init/built-in.o

LD .tmp_vmlinux1

KSYM .tmp_kallsyms1.S

AS .tmp_kallsyms1.o

LD .tmp_vmlinux2

KSYM .tmp_kallsyms2.S

AS .tmp_kallsyms2.o

LD vmlinux

SYSMAP System.map

SYSMAP .tmp_System.map

OBJCOPY arch/arm/boot/Image

Kernel: arch/arm/boot/Image is ready

AS arch/arm/boot/compressed/head.o

GZIP arch/arm/boot/compressed/piggy.gzip

CC arch/arm/boot/compressed/misc.o

CC arch/arm/boot/compressed/decompress.o

SHIPPED arch/arm/boot/compressed/lib1funcs.S

AS arch/arm/boot/compressed/lib1funcs.o

AS arch/arm/boot/compressed/piggy.gzip.o

LD arch/arm/boot/compressed/vmlinux

OBJCOPY arch/arm/boot/zImage

Kernel: arch/arm/boot/zImage is ready

bsmitty@bsmitty-HP-EliteBook-8730w:~/android/omap$ cd eurasia_km/eurasiacon/build/linux2/omap4430_android

bsmitty@bsmitty-HP-EliteBook-8730w:~/android/omap/eurasia_km/eurasiacon/build/linux2/omap4430_android$ export KERNELDIR=~/android/omap/bsmitty@bsmitty-HP-EliteBook-8730w:~/android/omap/eurasia_km/eurasiacon/build/linux2/omap4430_android$ make TARGET_PRODUCT="tuna" TARGET_SGX=540 WARNING: Android version is older than this DDK supports

../config/core.mk:274: Setting SGX_DISABLE_VISTEST_SUPPORT=1 because PVRSRV_USSE_EDM_STATUS_DEBUG=1

eurasiacon/build/linux2/kbuild/kbuild.mk:36: *** BUG: Unknown kbuild module "bufferclass_example" should have been caught earlier. Stop.

make: *** [build] Error 2