yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] trevd:
That's probably your problem as the omapzoom gralloc is missing a reference to libcorkscrew.so which handles stack unwinding or more accurately contains the definition of the callstack class. This used to live in libutils.so.

The same problem arose on the Defy and was worked around with quite possibly one of the filthiest hacks ever. The callstack class was reimplemented with a new name of callstac2. Then armed with an hex editor the gralloc binary was edited to match. It's genius but it so very wrong lol [ More Details Here ]

This will work on the omap4 as well however CM's KindleFire have a different gralloc with same version number but the correct references, I have no idea where this has come from but if it's not from an official source I'd put my money on using elfedit to add the reference to the dynamic section of the binary which is the correct way to do binary edit IMO maybe [MENTION=4243514]Hashcode[/MENTION] could shed some light as to it's origin.

If this ain't the problem you can normally get a gist of things by using strace -ffvi surfaceflinger over adb, obviously attaching gdb and setting up native debugging is the proper way but ain't nobody got time for that

Hopefully I should be able to get my effort going today once I get my mits on my brothers GNex again :D
[Samsung Galaxy Nexus] Quallenauge:
Or you modify the CallStack classes to match the old method call, then no binary hack is needed:

CallStack.h

CallStack.cpp

This was running w/o problems on my test setup device.
[Samsung Galaxy Nexus] trevd:
^^^^^^^^

Or that

[MENTION=4636351]Quallenauge[/MENTION] I've gone with gralloc from the kindle which is good to go and no Code Mods needed either :p

Anyway I hope you are good, I keep meaning to send you one of those overly long messages but It's find the time to do all that typing lol
[Samsung Galaxy Nexus] Quallenauge:
Same for me. On the Archos G9 is used also the latest PVR driver which where mentions by hashcode earlier this thread.

Currently I try to get the 3.0.72 running on the archos device, I saw at your logcat you already there.... ;)

In the last months I also was really (really) busy ....

[MENTION=2838735]aosp[/MENTION]: Thanks for your valuable hints!

Sorry for my laziness, [MENTION=4179234]trevd[/MENTION] has some experience with my social messaging ;)

Currently it seems to only implemented for omap5 devices, and for 3.4 kernels. So maybe it can improve some things... I have to look into this in future...

Yes...No...Yes...No ;) For 3.0 development it sounds interesting, but for 3.4 kernel development difficult until we solve the remoteproc/rpmsg issue (I think I don't have the ability to do that). If we had a working backported driver I would think that hacking on this would be more fun. Also it would add a little pressure to get things done...don't get my wrong, but I also have some other social obligations, so I don't know if I have enough time for it. :confused::confused: I don't know...
[Samsung Galaxy Nexus] aosp:
[MENTION=4636351]Quallenauge[/MENTION] [MENTION=4179234]trevd[/MENTION]

You guys know of any official kernel sources for the OMAP4460 SmartQ-T20 tablet?

http://en.smartdevices.com.cn/Products/T20/201203/28-113.html

http://en.smartdevices.com.cn/Support/Downloads/T20/Firmware/201301/18-208.html

https://github.com/riversky/android_device_ti_smartqt20

https://github.com/riversky/android_kernel_ti_smartq
[Samsung Galaxy Nexus] aosp:
You might want to diff the archos g9 kernel with the smartq t20 remoteproc/rpmsg

Add smartqt20 board support · de738d1 · riversky/android_kernel_ti_smartq · GitHub - http://goo.gl/8WLh77

https://github.com/riversky/android_kernel_ti_smartq/commits/jellybean/drivers/rpmsg

https://github.com/riversky/android_kernel_ti_smartq/commits/jellybean/drivers/remoteproc

https://github.com/riversky/android...ts/jellybean/arch/arm/mach-omap2/remoteproc.c

Merge from omapzoom/p-android-omap-3.0-dev · f9f5f11 · riversky/android_kernel_ti_smartq · GitHub - http://goo.gl/MeEEOp
[Samsung Galaxy Nexus] aosp:
[MENTION=4636351]Quallenauge[/MENTION]

Just found these on [MENTION=4243514]Hashcode[/MENTION] otter 3.4 kernel

[AMZ] remoteproc changes · c9e10fe · KFire-Android/kernel_omap_otter-common · GitHub - http://goo.gl/sIi0a9

[AMZ] rpmsg changes · 4dbf7bd · KFire-Android/kernel_omap_otter-common · GitHub - http://goo.gl/GaQxHW
[Samsung Galaxy Nexus] aosp:
[MENTION=4636351]Quallenauge[/MENTION] [MENTION=4179234]trevd[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]

3.1 branch got fixes in remoteproc and display fixes with updated sgx drivers

http://www.omapzoom.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/p-android-omap-3.1
[Samsung Galaxy Nexus] Quallenauge:
I didn't encountered problems with the latest remoteproc drivers from the omapzoom kernel (3.0 series). But maybe there is a interesting cherry-pick inside ;)

He uses the newer format ducati-m3-core0.xem3 for that: remoteproc.c So we need a compatible ducati firmware which includes a proper HW driver for the camera. (On archos devices, we need some other things too, because some models have only 512MByte).

But I really like to know where the source files is, [MENTION=4243514]Hashcode[/MENTION] did you build them by your own?:

https://github.com/KFire-Android/kernel_omap_otter-common/blob/p-android-omap-3.4/arch/arm/mach-omap2/remoteproc.c#L370

/*Select the 512MB version of the firmware for 512MB memory
* configuration for IPU
*/
if (strcmp(omap4_rproc_data[i].name,"ipu_c0") == 0) {
if ((omap_total_ram_size() <= SZ_512M )&& (omap_total_ram_size() > (SZ_1M * 384)))
omap4_rproc_data[i].firmware = "ducati-m3-core0_512MB.xem3";
else if ((omap_total_ram_size() <= (SZ_1M * 384)) && (omap_total_ram_size() > SZ_256M)) {
omap4_rproc_data[i].firmware = "ducati-m3-core0_384MB.xem3";
} else if (omap_total_ram_size() <= SZ_256M){
omap4_rproc_data[i].firmware = "ducati-m3-core0_256MB.xem3";
}
}
[Samsung Galaxy Nexus] aosp:
Blaze Defconfig: Enable CONFIG_MODVERSIONS

CONFIG_MODVERSIONS allows modules to be used

with a different kernel than what it was built

against. When CONFIG_MODVERSIONS is enabled,

the kernel will add a special piece of versioning

info to every exported symbol. This versioning info

is calculated by a CRC algorithm which recursively

looks at the symbols associated structs, unions,

enums, and typedefs. When an external module is built,

it will store the corresponding symbol and version info.

When the module is inserted a check is performed

to ensure that the version for each symbol matches.

This ensures that the interface between kernel

and modules is not broken, and allows more flexibility

than an explicit kernel version check.

http://goo.gl/80k7Eh

blaze_defconfig: Remove SGX driver from blaze_defconfig

SGX driver is now built outside the kernel tree as a loadable

module.

http://goo.gl/LR4EEf

Revert "OMAP4: Android Kernel Names and Versions"

This reverts commit 222dcf5a83f2cf51181b778c963b80c0b9e54911.

We are going to use CONFIG_MODVERSIONS instead of this.

http://goo.gl/rl7oHN

TI TFW:fix for THERMAL_FRAMEWORK disable cause build error

Patch rebuilds Makefiles tree for thermal_framework

http://goo.gl/JK2c3n

blaze_defconfig: Don't specify vram size

The size of the vram is being calculated based on panel

size so do not hard code it.

http://goo.gl/3KC5Ki

omap: Adds access_process_vm to gpu platform data

This core API function is needed by modular PVR driver.

http://goo.gl/K5mQcQ

omap: remoteproc: choose ducati firmware as per platform

Ducati firmwares are different for default 1GB configuration

and 512MB system configuration. remoteproc will load

appropriate firmware as per system configuration

http://goo.gl/9nbUUf

omap: common: add kernel API to query RAM size

Add kernel api omap_total_ram_size() to query the

exact size of physical ram available in system.

Its derived from mem arguments passed to kernel via

bootargs and is expected to be used by board files and drivers.

Note: omap_init_ram_size() has to be invoked at the earliest

during board init to update memory size.

http://goo.gl/6zsL0c

omap: omap4 boards: adapt board files reserve call to dynamic changes

Since system memory size and carveouts are calculated dynamically,

omap_ion_init() calls should be invoked upfront so as the address

and sizes are initialized properly.

All omap4 board files are updated

http://goo.gl/qM2igh

omap: rpmsg: switch over vring memory to use dynamic pool for dsp

The carveout memory for DSP is being switched over to use the

dynamically reserved memory pool. The memory addresses used to

configure the vring memory is therefore being switched over to

use the dynamic memory pool.

The vring memory is allocated in the rpmsg layer, while the

memory for other firmware sections is assigned by the remoteproc

driver. The remoteproc driver adjusts for the utilization of

this memory automatically through the presence of the vring

carveout section as the first of the carveout sections in the

resource table.

http://goo.gl/Jy7lfQ
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4179234]trevd[/MENTION]

blaze_tablet: Add SGX make file to blaze_tablet

This makes sure that SGX binaries are a part of blaze_tablet build.

http://goo.gl/MhvR3H

Move ducati install to the device level

This change is the precursor to the upcoming split ducati

implementation. New versions of ducati can now be dropped into

proprietary-open along with a mk file, and the install can be dicated

on a per-device basis.

http://goo.gl/cghxcF

SGX-BIN: SGX Driver update for CONFIG_MODVERSIONS

These binaries have been built against kernel

version 3.0.31 with CONFIG_MODVERSIONS enabled.

Depends on http://review.omapzoom.org/#/c/23152/ .

http://goo.gl/DA22ps

SGX BIN: 1.9@2139099 Set ro.product.processor before loading modules

Patches included in this binaries

ad6e72e SGX UM: Set ro.product.processor before loading modules

c59e125 SGX UM: Pvrsrvinit fix typo in remount command

b5a4dca SGX UM: Remove BRN32044 for omap5

b3f0cc6 SGX UM: Fix coefficients for RGB->NV12 blit

dcd7ea1 OMAP5: WA: Race condition when SGX is powered down

http://goo.gl/R0P2ks

blaze_defconfig: Enable SCHED_TRACER

The Galaxy Nexus JB production devices support the systracer.py

script which can be used to enable tracepoints in Android. This

needs the SCHED_TRACER config flag to be enable.

http://goo.gl/OuH4nH
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4179234]trevd[/MENTION]

OMAP2: generic Android display configuration setup

Added android_display methods to allow runtime configuration of

Android display resources, such as:

- FB0's vram is dynamically calculated from the number of

buffers SGX requires in VRAM (swap chain and/or composition

buffers), and the FB0 display size.

- OMAP VRAM is calculated from FB0's vram need + any other

specified FB's vram. (If command line is used to specify

FB vrams, omap vram must also be specified.)

- TILER1D area reserved for use as DSS MMU by DSSCOMP is

calculated from default display size. It can be overriden

by board file.

- TILER2D carveout size is reduced by TILER1D area (if coallocated

with TILER2D) and by the TILER2D SGX buffers (swapchain and/or

composition buffers)

- nonsecure TILER2D carveout size is set to the backpages needed

by TILER2D SGX buffers.

All of this is coordinated by omap_android_display_setup. It

takes pointers to the DSS board info, FB platform data, and

optionally to the ION, SGX and DSSCOMP platform data. It should

be called in board_reserve before omap_ion_init.

If SGX data is provided, it is set as the SGX platform data for

FB0. Similarly, if DSSCOMP platform data is provided it is

also set. This can be used to set a preferred tiler1d slot size.

If ION platform data is provided, it is updated with the required

tiler2d carveout sizes.

NOTE:

To maximize TILER2D space, the TILER1D area reserved for android

display is not aligned to 1MB, but is aligned to 32 pages as the

smallest 2D allocation needs a 32-page band. We further reduce

TILER2D space by the container space lost by the SGX buffers,

which may be larger than the actual backpages bneeded for the

SGX buffers.

Therefore the sum of secure + nonsecure + 1D tiler space may

be smaller than the available container space.

Ported to latest SGX DDK by Dima Svetlov.

http://goo.gl/mTQs01

sgx_omaplfb: Create omaplfb platform device file to permit device configuration

http://goo.gl/UtJL0A

omap: Adds access_process_vm to gpu platform data

This core API function is needed by modular PVR driver.

http://goo.gl/lC1ds8

omap-ion: Interface to export ION handles from PVR fd

PVRSRVExportFDToIONHandles was called directly by drivers.

Exporting this interface through ion. This also helps when PVR

is built as a module as the abstraction then uses an exported

function pointer.

Since this change also changes the interface between kernel and

a module, LOCALVERSION change is required.

Kernel version = 3.0.21-00001-OMAP-Android

http://goo.gl/zyrJTX
[Samsung Galaxy Nexus] Nephilim:
AOSP, seeing as you can pretty much find anything as far as android goes and you are like the Yoda of information. You think you could focus a little of your time helping us all try to find out what Mpokthws did to his ramspeeds to gain him such a powerful performance boost over everyone else? We've all sent him like 9,000 messages but he decided he would rather violate Google Open Source Policies by ignoring us and not releasing his source. He was even logged in only a few days ago so it's evident he is ignoring everyones pleas to share. Probably because he knows that his kernel will not be anything special once other developers get his optimizations.

Anyway, it would be very helpful if you could find anything that would relate to boosting ramspeed to the extreme Mpokang SuperRam has.

Neph.
[Samsung Galaxy Nexus] aosp:
What benchmark reveals the faster ram speed and how does it compare with [MENTION=4608636]bsmitty83[/MENTION] kernel?
[Samsung Galaxy Nexus] bsmitty83:
im pretty sure what everyone is talking about is this commit to backport 3.9 zcache im testing it now , cant remember if i used it before or not on my other nexus kernel

https://github.com/bsmitty83/mpokang_kernel/commit/8676d65b71fdb0d098f36cfa7c41ce9e6fc2882d
[Samsung Galaxy Nexus] metalspring:
mpokang ram speed-

http://xdaforums.com/showpost.php?p=49800540&postcount=1028

dirtyv ram speed-

http://xdaforums.com/showpost.php?p=49800901&postcount=1029

---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------

Idk, was it enabled in any but his last release? That was the one that had the "50% ram performance"
[Samsung Galaxy Nexus] aosp:
Looks to me that all he did was overclock the memory but being that he noticed current kernels not using this kang he feels cool and important now.

[MENTION=4608636]bsmitty83[/MENTION] try the below commits ;)

configs · 17f7af0 · mdeejay/kernel-tuna · GitHub - http://goo.gl/gvm26L

tweak freqs and voltages · 12447e8 · mdeejay/kernel-tuna · GitHub - http://goo.gl/r7Ixfe

1) OC RAM 533MHz · 93beb0e · mdeejay/kernel-tuna · GitHub - http://goo.gl/iGkODC

correct mem freqs · e402c9c · mdeejay/kernel-tuna · GitHub - http://goo.gl/6GNnQm

more mem oc · 1f9c00e · mdeejay/kernel-tuna · GitHub - http://goo.gl/msvY02

typo · 9772005 · mdeejay/kernel-tuna · GitHub - http://goo.gl/qozkJW

added missed files · a632eb5 · mdeejay/kernel-tuna · GitHub - http://goo.gl/0iqpWf

Improve the performance of memcpy and memmove · 26718e3 · mdeejay/kernel-tuna · GitHub - http://goo.gl/UpSCmf
[Samsung Galaxy Nexus] Nephilim:
Omg! If this does, it all the people saying no one can match Mpokang SuperRam are going to eat their words!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Looking at them now
[Samsung Galaxy Nexus] pattyboi:):
shoot me a pm if you want a guinea pig. i got hours of free time tonight
[Samsung Galaxy Nexus] metalspring:
Same here, I get to reinstall Ubuntu all over again, re-setup my build environment, re-sync source and all that fun stuff... Stupid lvm setup didn't give enough space in /tmp and no easy way to fix it (and its causing out of space errors compiling)
[Samsung Galaxy Nexus] bsmitty83:
I got you guys I'll shoot you both some thing soon .

---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------

I run Ubuntu as my os . haven't regretted it yet . I dont miss windows at all . I hate touching my wife's laptop with win7 on it . it would probably be a lot easier to run both operating systems side by side than in VM . just my opinion tho
[Samsung Galaxy Nexus] caspboy:
Sorry for my curiosity, but how much space is needed for compiling a kernel, i got a 120GB with ubuntu 12.04.03 LTS setup and ready to go...
[Samsung Galaxy Nexus] Nephilim:
Don't forget about me!!!!!! ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
5 GB is good . the source is about 2gb
[Samsung Galaxy Nexus] caspboy:
Thats great! I thought around 10-20GB. I got about 46GB racked up in movies & music:o

---------- Post added at 10:52 PM ---------- Previous post was at 10:46 PM ----------

So I got my BE setup, and I'm not looking to make a kernel - just too build one for my device. Won't I need to edit the source to match my device (not an issue) or can I just go ahead and start.

P.S- sorry for the noob questions, first kernel I've built and a bad one can mean death...
[Samsung Galaxy Nexus] 3n3rg1c:
[MENTION=5645126]Aiko0923[/MENTION] When I was compiling & building both rom & kernel for Atrix I used about 28 Gigs.. The space needed depends on what you do ... About 5-8 Gigs is good for building kernel though...

I will start my work here as soon as I get repaired my rig's HDD & ram I got both damaged :p
[Samsung Galaxy Nexus] metalspring:
For roms though you need much, much much more lol

The source for my rom for example takes over 20 GB (and thats just the repo folder, not including the checked out files)

Then building itself takes up tons of space as well lol

And building roms also needs at least 4 gb ram and lots of swap space and hours to do a clean build vs 10-30 minutes for a kernel, although modifying roms source is far easier than kernel source (most of what you'd modify in roms is java which isnt too bad, but kernels are basically C/C++ which isnt easy)

Basically roms require a better pc to build well, but are easy to modify, while kernels dont require much but are hard to modify
[Samsung Galaxy Nexus] caspboy:
Yeah, I now about the rom & kernel space 20-40GB. I don't really bother with rom compiling, takes to long, only for personal use just to see whats under the hood;) I'm an impatient person sometimes:laugh:
[Samsung Galaxy Nexus] 3n3rg1c:
Agreed Building roms need a much better PC with at least 4Gigs of RAM & good processor tooo. thats the reason I stepped out of building things :p
[Samsung Galaxy Nexus] caspboy:
My rig has 6GB with Nvidia 9800 gt and core i5 750. I use it for gaming, sounds like much but its a minor setup - it plays gta 4 smoothly so its good enough for me
[Samsung Galaxy Nexus] metalspring:
better in some ways than mine, I have ubuntu 13.10 installed with 300 GB of space, but only 4GB ram, and an old intel core2 duo processor

Clean rom builds take about 4- 4.5 hours and I end up using at least half of my 4GB swap after my ram gets nearly full, but it works :P
[Samsung Galaxy Nexus] caspboy:
I'd trade just for the 300GB:D Also, do I need to change the source of the kernel to match my device?
[Samsung Galaxy Nexus] bsmitty83:
I build on a HP elite 17in workstation , dual core , 8gb ram (ddr2 tho) , only a 150gb HDD , but all my media is on a 1.5tb network drive so I usually vanir source which is freaking huge , and a bunch of kernel stuff on mine

Looking to upgrade soon .
[Samsung Galaxy Nexus] clnzx2:
Always willing to test and if any of the DEVs in this thread need hosting please let me know. I no longer have time to develop like I used to but at least I can help with hosting.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION] [MENTION=4179234]trevd[/MENTION] [MENTION=4636351]Quallenauge[/MENTION] [MENTION=4443334]Grarak[/MENTION] @ak

I got great news fellas I got in touch with the great Israel Cepeda

https://github.com/icepeda

http://isrcepeda.blogspot.com/?m=1

And he is willing to help our cause

just to know but how many of you would be willing to donate for his efforts or donate a GNeX his way if requested?
[Samsung Galaxy Nexus] pattyboi:):
when i get back one my feet with money ill gladly donate some $ his way (within the next 2 weeks)
[Samsung Galaxy Nexus] MBQ_:
My mom is planning on switching to T-Mobile soon, and because my sister and I are both on her plan, I may be getting a Nexus 5 soon (yay)

If that happens, I'd gladly send him my Nexus. Knock on wood, this thing is in perfect condition.
[Samsung Galaxy Nexus] aosp:
No OMAP left behind ;)
[Samsung Galaxy Nexus] dirtyreturn:
Toro Plus work??
[Samsung Galaxy Nexus] Hetalk:
I'll donate to you to cover a small part of your cost. :highfive:
[Samsung Galaxy Nexus] aosp:
I just asked him waiting on a reply ;)
[Samsung Galaxy Nexus] MBQ_:
That's awesome of you. :)
[Samsung Galaxy Nexus] MBQ_:
Sooo little update:

My mom is going to call T-Mobile here before the end of the week if time permits. If she ends up switching to them, I'll need to get in contact with someone to send the phone to.

If you could have the guy PM me on here, or Hangouts or something with an address, I'd appreciate it. If he wants me to ship the phone with my charger, I'd gladly do so too.

The phone does only have an extended battery. Its a Hyperion 3500MaH battery *with* NFC support. So I guess that's kind of a bonus.
[Samsung Galaxy Nexus] aosp:
Awesome dude I'll msg you on hangouts soon ;)
[Samsung Galaxy Nexus] Sik-1:
All I'm saying is the HTC sensation has a 3.4 kernel, so how much of a nexus do we really have????
[Samsung Galaxy Nexus] ze0:
HTC PICO(EXPLORER) has 3.0 kernel( they had 2.X kernel initially ) , they had the similar problems ..after they made it atleast bootable and usb detectable they found ways to get rid of the bugs one by one

http://xdaforums.com/showthread.php?t=1959526
[Samsung Galaxy Nexus] Godra:
All 2011 Xperia devices got 3.0 and 3.4 by nobodyAtall, you shoud ask him for advices, he is very experienced dev
[Samsung Galaxy Nexus] kaluoshi:
maybe a not respectful like you? All devs need respect, especially on xda where they post their work for free. Peace
[Samsung Galaxy Nexus] MBQ_:
I can attest to this.

I donated 10 or 20 dollars USD to Anarkia, and a month or 2 later, he sent me some donations

---------- Post added at 04:12 PM ---------- Previous post was at 04:07 PM ----------
[Samsung Galaxy Nexus] kaluoshi:
Yes dude, also there is no need to attest that cause Anarkia posted in devs thread when he re-sent them :) he sent to me 10$ too only because i maintained the Rubik/Kubo line (that for me was and is a pleasure). Stefano is a great dev, but first a great person.

P.S. he's not going to answer, and i think you know why Kyler ;)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] MBQ_:
AK ain't got time fo dat. :cool:
[Samsung Galaxy Nexus] paarthdesai:
one thing i would like to say [MENTION=1106390]anarkia[/MENTION] [MENTION=4763201]mbq[/MENTION] and [MENTION=4519152]Khizar[/MENTION]

if the dogs bark let them bark.. do not feed them, coz if you feed them once they come behind you for some more food.. if you refrain from providing it, the dog will eventually come to bite you..

same thing happened in this case.. he used anarkia's kernel, anarkia moved to n4.. so development is on a lesser aspect.. and now chaps like this are coming over him as if he has taken an oath to support till he dies :@

ungrateful people are everywhere :/

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] Sparx639:
Wow! Amazing work jackpot! Are you still working on the galaxy players or not?
[Samsung Galaxy Nexus] ScardracS:
Plz don't leave this project

I'm not the droid you are looking for
[Samsung Galaxy Nexus] motorazrv3:
+1