yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Scandy:
No anarkia please. Imoseyon maybe
[Samsung Galaxy Nexus] Hetalk:
Thanks buddy. Haven't seen you for some time, so thought you weren't active lately.
[Samsung Galaxy Nexus] Nephilim:
Yea, I'm active, bouncing around the 4.4 rom threads lately, hoping fairct will start building a PA4 4.4 rom.

Just messaged Stefano, left him a link to this thread. :D
[Samsung Galaxy Nexus] AbhishekS:
Just wanted to pop in and say that a potential fix to the screenshot animation glitch is discovered. :D
[Samsung Galaxy Nexus] ak:
I was hired by @ Nephilim, I saw that you're still trying to bring the 3.4 kernel omap platform.

We had already discussed this porting, very difficult because all the drivers are based on current linux 3.0.x completely different level core language.

What you need is:

common source

https://android.googlesource.com/kernel/common.git/+log/android-3.4

omap drivers

http://www.omappedia.com/wiki/LinuxOmapKernelGitTrees # Feature_Branches_for_OMAP4430

google source

https://android.googlesource.com/kernel/omap/+log/android-omap-tuna-3.0-jb-mr2

and bam a team of engineers who take all this and pulls out something that worked.

I think if google does not pull out a woriking source, porting is nearly impossible.

Sorry to be so direct.

Thanks a lot.

ak

Nb:

whether there was source wich makes boot, I can try to lend a hand to solve any problems.
[Samsung Galaxy Nexus] Vekhez:
Did you make a 3.4 Kernel, because there was a 3.4 kernel with your name on it floating around in the 20-30 pages of this thread (now gone, but can be downloaded from HTC Mania)..
[Samsung Galaxy Nexus] andreskafe:
For ICS on the Motorola Atrix porting the kernel of Samsung Galaxy R. This is similar?
[Samsung Galaxy Nexus] aosp:
Don't stop believing amigo ;)
[Samsung Galaxy Nexus] ashclepdia:
"Hold onto that FeeEeeEeeEeelinnn!!!"

Sorry couldn't resist :D
[Samsung Galaxy Nexus] aosp:
GNeX users if you just read [MENTION=3685904]ak[/MENTION] last post you might think it's impossible but Motorola Defy users don't agree they said all you need is [MENTION=513620]Quarx[/MENTION] and [MENTION=4855459]Blechd0se[/MENTION] google search that OMAP device and see what has been accomplished on such a ridiculously locked down device by only a few dedicated devs ;)

If you still in doubt ↓

omap: add mapphone board and uart

* Add all kind of board files like on 3.0

* Currently stage is around 21.10.12,

so UARt *should* work

* Notice; we don't need phys_offset to be

in header files, we can set it in defconfig.

3.4 introduced a nice feature for us :)

https://github.com/Quarx2k/jordan-kernel/commit/f21e18a2b93d10275f3cd982d21d33286d29c5cf

She just a small town girl ;p
[Samsung Galaxy Nexus] mosca_:
As they say, while there is life there is hope ... :p
[Samsung Galaxy Nexus] Mevordel:
So I took one look at that replicant page and realized I had derped the entire time I was working on UART. I forgot to change the console UART on the command line. I don't have a GNex anymore, but if anyone who has a serial jig wants to try my kernel (both branches) with a fixed command line it might work. (Just pack it with a twrp ramdisk.)

Sent from my Nexus 5
[Samsung Galaxy Nexus] wisefreakz:
Don't let it die guys!!!!
[Samsung Galaxy Nexus] bsmitty83:
Lol , I've been crazy busy with life , plus been building my own vanir kk ,

Mostly I've been reading things here and there , looking at other gits , and I know I don't have the talent to rewrite code to make it a full 3.4 kernel so I've been focusing on doing whatever I can do to make the old drivers work with the 3.4 base I guess , them maybe somebodys can take it from there , honestly I just want to get a 3.4 with the display up . that would be great . I'm sure the people who tinker with this are still doing their thing , nothings dead yet :beer:

Edit : I was looking around and it seems that there is a few changes I missed / didn't know about in our vendor folder (all the new libs use different names so the vendor/partial-board and android.mk files need to be changed to reflect the new names ) to use the new ddk , I got a kernel and module . gonna give it one more shot with theses changes which I'm still doing lol but it may be progress (3.0 kernel )
[Samsung Galaxy Nexus] MWisBest:
Quick question that's somewhat related to the whole graphics thing...

Does anybody know what version of HWComposer the Galaxy Nexus is using or how to find out? Would be useful for something I'm working on with this, and I'm not all that familiar with it.
[Samsung Galaxy Nexus] Mevordel:
My first guess would be

logcat -d | grep -i hwc
[Samsung Galaxy Nexus] dhiru1602:
Its VERSION_0_1

https://github.com/CyanogenMod/android_hardware_ti_omap4xxx/blob/cm-10.2/hwc/hwc.c

I mean no disrespect but why don't you start porting yourself? I have been following your posts right from the start. You are just googling around and posting irrelavent stuff which is no way related to what is trying to be accomplished here.

As stated by a lot of senior developers porting 3.4 would be hard and wouldn't necessarily bring in improvements since much of the OMAP drivers have to be forward ported, leaving little room for improvement. Instead or trying to prove the developers wrong, why don't you start by taking the initiative yourself?
[Samsung Galaxy Nexus] Garridon:
Called him out, help him with it.
[Samsung Galaxy Nexus] aosp:
Not sure you read my posts but I was not trying to prove anybody wrong I did not only post about the 3.4 Linux kernel but also missing OMAP4 optimizations from omapzoom for the Galaxy Nexus too. Anyway sorry for adding irrelevancy to the thread enjoy the holiday's and have a happy new year dude ;)
[Samsung Galaxy Nexus] MWisBest:
Actually, not quite. This was the one I was looking for: HWC_DEVICE_API_VERSION

https://github.com/MWisBest/android_hardware_ti_omap4xxx/blob/cm-11.0/hwc/hwc.c#L2135

So it's HWC_DEVICE_API_VERSION_1_0, but you did point me in the direction of the right file, so thanks. :P
[Samsung Galaxy Nexus] :
Why is everybody talking about whats possible and whats not?

The main question is, is it worth the work?

Well, for some part it is. I know there are some beasts out there that only care about numbers.

If you would compile a kernel and name it kernel 3.11 they would freak out, only because they know how to count.

As [MENTION=2838735]aosp[/MENTION] already says, there is a lot of code that TI made available, that has not even been integrated in our kernel, if i where you,

i would expect the most of that.

Me myself, i know how difficult it is to port a new "feature" into the kernel. I ported (a big part of) the ION for the Desire HD kernel.

And trust me, non-kernel developers, it's a real pain in the a**. I "only" enabled/ported a new/other memory allocator on that kernel,

and that was already a ton of work. But upgrading to a new kernel version, man, thats a lot of work.

Please respect guys like [MENTION=2838735]aosp[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION] , because trust me, what they do , is gold worth.

Thanks guys, you rock.

Rinse

Also guys, please stay on-topic. the title says [DEV/WIP] Dev stands for Developer. Please Keep it like that ;)
[Samsung Galaxy Nexus] bsmitty83:
Just for the record , I realize that we kinda jacked the thread with new ddk drivers , it is relevant to me because if I can ever get a 3.4 kernel to the point of GPU drivers , then the new ddk is the way I'd go .

I apologize for adding to the clutter , I was going to start a new dev thread but since I haven't seen the OP complain yet , I'm good with it .

Still compiling vanir 4.4 with the new ddk , my laptop is a dual core Intel with 8gb ram , not a speed demon
[Samsung Galaxy Nexus] kaijura:
Getting a 3.4 past bootscreen sounds past the skill of a novice developer, I think it won't be a straightforward job for most people including myself, it will need some talented devs who are able to write code.

http://kernelnewbies.org/Linux_3.4 - changes of the linux kernel to 3.4.

But I think a 3.0 with patched video drivers could be better and perhaps less work than rebasing it all to 3.4.

Many of us devs here can tweak, merge implement, cherry pick stuff that is already out there, but fewer of us know how to write or engineer code. For example just look at the 4.4 ROMs available, nobody knows how to implement desired features from scratch without cherry picking (or fix features) except the original devs/sources. Of course ROM developing is different than kernel, but the point is that few of us are talented enough to do this.

One way I think can get the ball rolling is to find seek the assistance of those devs who have done this kind of kernel rebasing developing before.. For ex, all these devs took their 2011 devices (which were like 2.6/2.x kernel) to 3.4:

[MENTION=788040]nobodyAtall[/MENTION] - took 2011 Xperia mini to 3.4

[MENTION=4243514]Hashcode[/MENTION] - took 2011 Kindle Fires to 3.4

[MENTION=4922835]educk[/MENTION] - took 2011 Galaxy S Plus to 3.4

But it appears only hashcode has worked with OMAP SoC, many other devs did MSM/Snapdragons SoCs, and Hash has already said in here that he knows it won't be an easy job.

We can always just change a version number of a 3.0.x kernel to 3.4 and most of the (novice) flashaholics wouldn't notice a thing. :angel:
[Samsung Galaxy Nexus] dhiru1602:
Oops.. That was a typo.
[Samsung Galaxy Nexus] shriom_manerker:
true i agree with you.lets forget 3.4 just for a moment here. its a lot of work and isnt that easy to make. why dont we implement the omap optimizations to our existing kernel 3.0 kernel ? im sure it'll benefit us in a lot of ways.
[Samsung Galaxy Nexus] Vekhez:
I think that is already in the works. 3.4 is on the back burner.
[Samsung Galaxy Nexus] shatteringlass:
The petition on change.org has over 30k subscribers. If each of them donated as little as half a dollar we could crowdfund this project with a crazy $15k (good maths, I know). This kind of thing would probably appeal to great devs in here like [MENTION=4243514]Hashcode[/MENTION], [MENTION=2838735]aosp[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION] who deserve to monetize their efforts. They would probably work more happily and possibly full time. The four of them could get as much as $4k each from this hackathon. Let's talk this through.
[Samsung Galaxy Nexus] Pasquale91fg:
Fine by me! Open a petition and begin to send money! $ 1
[Samsung Galaxy Nexus] McDuffSmith:
@#!%in' right!

lets do it!
[Samsung Galaxy Nexus] bsmitty83:
I'm definitely honored by this , but the only donations I'll take are thanks , im just an amateur tech nerd with ocd , so I tend to get stuck on projects , especially ones that are complicated . $ doesn't motivate me and I'll work on this just as much with or without a bounty .

Aosp , hashcode , and dhack are the stars of this show

Also my build finished finally last night , flashed it and it acted just like building just the kernel , Google screen just hangs as the background turns white . but I looked at the installed-files.txt and I didn't see any of the new libs , unless the .o files are named the same as the old , but the module built , I can't pull a log but I think its something in the libs . I'll try to sort it all out . if I can get it to boot like the commit Google pushed for an inline new ddk to a black screen did , then I can pull a log and see what's the error
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Getting omap4 optimizations from omapzoom working on the tuna devices with the 3.0.x kernel is irrelevant Google told me ;p
[Samsung Galaxy Nexus] bsmitty83:
About that , am I correct in that those commits your talking about

need the new/newer/newish :p ddk to work ? Or can you use them on the current kernels ? If I can't get the ddk to work I would still be cool with adding these to a current kernel .

As you said before Google ain't got time for gnex anymore lol
[Samsung Galaxy Nexus] bsmitty83:
For any of you rom builders out there , does it take forever to optimize the .apks ? It takes 2x longer to do that on my machine than the actual compile
[Samsung Galaxy Nexus] metalspring:
What are you using as a base? I know when I built vanir, it seemed like that but I edited this line in /vendor/vanir/tools/parallelizer removing the /2 and it worked much faster optimizing the apks

PP=`expr $(grep -c ^processor /proc/cpuinfo) / 2
[Samsung Galaxy Nexus] bsmitty83:
Yea , vanir is my source , thanks again bro , I'll definitely try that . last time it took like 10 hrs to optimize .

---------- Post added at 07:59 PM ---------- Previous post was at 07:44 PM ----------

Holy crap that's like 20 times faster , thank you bro you saved me countless hours
[Samsung Galaxy Nexus] kenshin33:
10 houres ?

used to build on macbook pro 2-3h first build, and less after that

now, an i5 with 8GB, a bit faster, but a clean build is about 1-2h (CCACHE enabled)

I noticed that problem was the hard disk (as it is almost full)

but once the system is built, if your fiddeling just with the kernel ... no need to rebuild the whole think

just rebuild the kernel (if it is inline as with cm, make/mka bootimage with give you a bootable/flashable -as in fastboot boot|flash- boot.img)
[Samsung Galaxy Nexus] Mevordel:
With an SSD, you can even get it down to 20 minutes. And mka installclean is so much faster than mka clean
[Samsung Galaxy Nexus] metalspring:
I've always just used make -j[number of processors/threads + 2] (like for a quad core pc it would be make -j6) and adding a -pipe cflag to TARGET_arm_CFLAGS, TARGET_thumb_CFLAGS, TARGET_GLOBAL_CFLAGS, and TARGET_RELEASE_CFLAGS
[Samsung Galaxy Nexus] kenshin33:
yep, but the cost is still prohbitive (for me at least).

I never clean (unless forced to).

I'm trying the modules (rmed the pvr directory from kernel source)
[Samsung Galaxy Nexus] bsmitty83:
Yea the actual build only take a few hrs , but the optimizing .apks took FOREVER until I deleted that bit of code , now it takes about 10min
[Samsung Galaxy Nexus] Shidell:
You might want to adjust that if you have an Intel CPU that supports HyperThreading. For example, a quad-core CPU with Hyperthreading would really act like 8 logical processors, so you might want to try make -j10 instead. Might show better performance.
[Samsung Galaxy Nexus] Prasad:
I've seen no noticeable difference between make -j9 and make -j10 with modern quad Intel CPU. Anything below -j9 however begins to show a performance degradation.
[Samsung Galaxy Nexus] bsmitty83:
I use a dual core Intel , -j4 is about as fast as I can build , but using the mka command uses as many threads as possible anyways .
[Samsung Galaxy Nexus] Shidell:
Yeah, I've seen mixed performance between -j9 and -j10; it was just stated to try "a little above" what your CPU logical count is, so for a quad with hyperthreading, that'd be 9 or 10. Makes sense.
[Samsung Galaxy Nexus] Prasad:
Yep. As my friend's formula goes, apparently it's ideally -j{(core_count*2)+1} :cyclops:
[Samsung Galaxy Nexus] PlayfulGod:
I use -j12
[Samsung Galaxy Nexus] sheffzor:
I7 hexa?
[Samsung Galaxy Nexus] PlayfulGod:
6x amd ;)
[Samsung Galaxy Nexus] dhiru1602:
The only thing that we need to follow is http://omappedia.org/wiki/4AJ.2.5_OMAP4-Panda_Jelly_Bean_Release_Notes
[Samsung Galaxy Nexus] kenshin33:
this device seems to use the pvr modules from omapzoom

https://github.com/CyanogenMod/android_kernel_samsung_piranha

https://github.com/CyanogenMod/android_device_samsung_piranha
[Samsung Galaxy Nexus] style2345:
IS This Thread Is Dead

Guys IS This Thread Is Dead Or Silently Work Is In Progress
[Samsung Galaxy Nexus] drive2droad:
I think our worst fear may be true !!
[Samsung Galaxy Nexus] AbhishekS:
I guess [MENTION=5310723]Amperific[/MENTION] is working on it.

BTW no 3.4 kernel yet for the GNex is disappointing. Today I saw a cheapo (very cheapo) phone in a friend's hand, and even that had Android 4.2.2 with 3.4.5 kernel. It's a shame that a beast like Galaxy Nexus is still struggling to get it. All the mess due to Google.
[Samsung Galaxy Nexus] Sparx639:
Well it isn't the hardware specs that determines what kernel it has, TI just stopped after 3.0 while the devs of whatever chip your friend has are still updating it is all
[Samsung Galaxy Nexus] PlayfulGod:
yup and updating a kernel like that is no small task or else it would been done already.
[Samsung Galaxy Nexus] bsmitty83:
I'm starting to patch up the 3.0.8 tuna kernel to 3.1 and if all goes OK , I'll keep going . I have no clue how this will pan out but so far I think I can fix all the rejected patches , its a lot of them but I didn't expect less

This thread will see lots of inactivity , due to the nature of the work involved , I don't post here unless I got something to post lol .
[Samsung Galaxy Nexus] aosp:
Bookmark ;)

https://github.com/zlatinski

https://github.com/icepeda/omap

https://github.com/icepeda/panda

https://github.com/robclark/kernel-omap4

https://github.com/swetland/omap4boot

https://github.com/tonylo/kernel-omap4

https://github.com/karltsou/omap4-panda-3.4
[Samsung Galaxy Nexus] shriom_manerker:
lol dude you wont know if the phone is actually using 3.4 or just 3.0 knernel renamed to 3.4 haha Chinese phone have that **** in them :p
[Samsung Galaxy Nexus] madhavs:
What do you mean even phones like samsung core had 3.4 kernel which is not even comes closer to galaxy nexus
[Samsung Galaxy Nexus] pvkiniyan95:
I started to feel comfortable with 3.0.101 kernel, the devs did a gr8gr8 gr8 job, never felt missing a 3.4 kernel
[Samsung Galaxy Nexus] RevengeFNF:
And if a 3.4 kernel comes to life, you won't notice much diferences.

Galaxy Nexus works fine with 3.0 kernel and for now, Android don't requires 3.4 kernel to work.
[Samsung Galaxy Nexus] Vekhez:
Exactly. Android 4.0 was updated to the 3.0 kernel and there are still devices that were stuck on Gingerbread that have ICS/JB working fine.

We'll get CM support just like the Galaxy S (some EOL'd 2.1) since we got open source everything.
[Samsung Galaxy Nexus] AndyYan:
...till when a new Android version (e.g. Android 6.0) comes out that requires 3.4+ kernel and people start asking, begging and threatening devs to do it. Better do it now before it's too late.

Sent from Motorola Flipout @ CM7.2
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION]

This has the newer omapzoom omaplfb sgx goodies and tuna board files are included diff the tuna board and defconfigs with superior ;)

https://github.com/ljzyal/android_kernel_samsung_piranha/tree/cm-11.0

https://github.com/ljzyal/android_device_samsung_piranha/tree/cm-11.0

https://github.com/ljzyal/android_device_samsung_superior/tree/android-4.4

https://github.com/ljzyal/android_device_samsung_superiorcmcc/tree/cm-11.0

use 1.9.RC2 pvr driver · 3074b31 · ljzyal/android_device_samsung_piranha · GitHub - http://goo.gl/3eODk5

Update piranha SGX DDK to 1.9@2291151 · 0c4ce84 · ljzyal/proprietary_vendor_samsung · GitHub - http://goo.gl/QtJdIS
[Samsung Galaxy Nexus] bsmitty83:
Interesting I'll take a look as soon as I can , I'm stuck at work ATM lol
[Samsung Galaxy Nexus] Vekhez:
I come from the Atrix 4G a phone with the 2.6 kernel. On anything above Gingerbread there was no HWA, camera, video or video playback. We didn't threaten we grin and beared it and found work arounds.
[Samsung Galaxy Nexus] piterdemon:
Galaxy mini/ace/i551/gio phones with 2.6 kernel android 2.2/2.3 and now running very good with android 4.4 kernel 2.6 with working camera, video and hw . review.androidarmv6.org jenkins.androidarmv6.org

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy Nexus] Vekhez:
They have open kernel source. There was never any kernel source for the specific Tegra 2 chipset. They just rewrote all the drivers and made a 3.1.10 kernel
[Samsung Galaxy Nexus] piterdemon:
Half of sources is closed

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy Nexus] Vekhez:
Well they still had the other half. The Moto Atrix 4G had no source and there was only one device that had the same chipset and was it in the same boat.

So they just rewrote everything and just told Motorola to stick it.
[Samsung Galaxy Nexus] 3n3rg1c:
Agreed but we were helped by 3.1 kernel of galaxy r..
[Samsung Galaxy Nexus] CataHd:
Amazon Kindle Fire that has TI OMAP 4430 it has kernel 3.4

http://xdaforums.com/showpost.php?p=41483586&postcount=18

Can this help Galaxy Nexus?
[Samsung Galaxy Nexus] bsmitty83:
It does only for reference since the main problem is there is no tuna specific code . there are plenty of omap4 devices using the 3.4 kernel , although the kindle is about the closest to our device , its still no copy and paste job lol .

About the best I can do is work on using all the common 3.4 stuff and try to make our current tuna files work with that . I can't rewrite the tuna files
[Samsung Galaxy Nexus] aosp:
But the Tate has the same chip as the GNeX ;)

OMAPDSS: DSSCOMP: Remove PVR_SGX dependency. · f90ca2b · KFire-Android/kernel_omap_bowser-common · GitHub - http://goo.gl/ac9ppE

KFire-Android/android_device_amazon_tate · GitHub - http://goo.gl/8K5Ul9

KFire-Android/android_device_amazon_bowser-common · GitHub - http://goo.gl/nn0BHo

KFire-Android/android_device_amazon_omap4-common · GitHub - http://goo.gl/0aDS4d
[Samsung Galaxy Nexus] aosp:
Modify tuna board files like cepeda did for the panda you got this ;)

Panda: Updating board and clean up · d5bc5a4 · icepeda/omap · GitHub - http://goo.gl/y8JXqd

Panda: Updates for ducati and display · d1c8a0d · icepeda/omap · GitHub - http://goo.gl/WPMMNK

OMAP4: Panda: Adding board version and ID · dfde981 · icepeda/omap · GitHub - http://goo.gl/xKlNSx

Commits · icepeda/omap · GitHub - http://goo.gl/mdAl4E
[Samsung Galaxy Nexus] bsmitty83:
These are very useful to me . :thumbup: I've been looking for something like these for a while . but I cloned the op's source , reverted it back to before he started axing code to make it build , tossed in all the tuna files and its dependents , and am working on squashing the build errors one by one . but I think there is more promise with the new ideas you just gave me . I need sleep bad , been working hard doing prototype carbon fiber body panels for the new Honda nsx . I'll try to squeeze some more time in soon . till them I compiled a 4.4 kernel with linaro 4.8 and I'm using it now on vanir + art and its the smoothest combo I've ever had on this phone hands down . I'm working on that as well so well see how far I get with the 3.4 but this gave me one more piece to the puzzle I think
[Samsung Galaxy Nexus] Nephilim:
Hey smitty, is the 4.4 Linaro 4.8 you are using the one called Dirty_V over on your dev-host? If so, is it meant just for vanir or is it all good to try out on other roms?

I am all about Mpokang SuperRam kernel but I see how much hard work you put in here and would totally give your kernels a nice run and review. ;)
[Samsung Galaxy Nexus] 3n3rg1c:
[MENTION=2853378]Nephilim[/MENTION] it think 4.4 Linaro 4.8 is Dirty_V & yes it works with other 4.4 roms also...
[Samsung Galaxy Nexus] bsmitty83:
Yea it should work on everything . I used vanirs awesome kernel as a base but its any kernel format . I haven't had a chance to start a thread for my new one yet , I honestly just put it out to show I got linaro 4.8 to not freeze up , so other devs could use the fix , but if people like this kernel , ill see about starting one . BTW mpokang SR is the only other kernel on my phone, its an amazing kernel . I wish the op had of gotten a chance to update his git , but only for selfish reasons lol :p
[Samsung Galaxy Nexus] clnzx2:
Bsmitty your 4.8 kernel is awesome. If you could make it have more free ram like mpokang I can't imagine.
[Samsung Galaxy Nexus] pianistaPL:
I'm not a dev and i don't know if this is good idea but wheter would be possible to make Mpokang SR Linaro version? (+ updated kernel to 3.0.101 and some other possibly optimizations which came after last Mpokang update)
[Samsung Galaxy Nexus] clnzx2:
If mpo would release his source
[Samsung Galaxy Nexus] pianistaPL:
He did do it https://github.com/mpokwsths/mpokang_kernel
[Samsung Galaxy Nexus] Godra:
It's outdated
[Samsung Galaxy Nexus] Grarak:
What are you talking about?