yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] gr8nole:
Is that file not available in your stock rom? If not, then I don't know.

Don't scrap it just yet. Just try to get this missing files do it can boot.
[Galaxy Tab 3 General] Hazou:
Libdrm is tied to the device. Is a property file from Intel. The sources are available to make it, I already uploaded them if I remember correctly. But just take it out o your stock ROM.

Verstuurd van mijn XT890
[Galaxy Tab 3 General] :
on libva

hazou,

hey thanks, i'm learning alot from you guys.

my question is what is the exact placement of the libva-cros directory in the cm11 directory tree?

i will revisit your github, as i go on i'm getting a better understanding of what to look for but, i am

still fairly dopey on most things. :laugh:

wifi and bluetooth are going to be fun :eek:

m

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

gr8nole

okay thanks, i found it, i'll just dupe the entire /system/lib for quick push/pull in adb

m :good:

[MENTION=3034891]gr8nole[/MENTION] libdrm drop-in worked, meaning i boot to black screen ... YAY !!!!!!
[MENTION=4479363]Hazou[/MENTION] i think it's this keeping me at black screen

D/AndroidRuntime( 6875):
D/AndroidRuntime( 6875): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 6875): CheckJNI is OFF
D/dalvikvm( 6875): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 6875): Added shared lib libjavacore.so 0x0
D/dalvikvm( 6875): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 6875): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 6875): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
D/dalvikvm( 6875): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
E/memtrack( 6875): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 6875): failed to load memtrack module: -2

zygote needs to grab to boot through. seperately rfkill list all picks up only 0 Bluetooth. am/will research more tomrrow.

time to sleep.

m
[Galaxy Tab 3 General] Hazou:
That's not the whole logcat, u are missing some part under the memtrack if i am correct :confused:

The jni_onload is just a warning (from the internet), the memtrack could be the issue.
[Galaxy Tab 3 General] ketut.kumajaya:
I also got memtrack error on a working CM 11:

# logcat | grep memtrack
E/memtrack(27668): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(27668): failed to load memtrack module: -2
#

It's depend on your platform but this memtrack module optional for exynos4. Please check on stock firmware if this module available.

To mount a stock system.img you have to convert it from sparse ext4 to raw ext4 first:

$ simg2img system.img system.img.ext4
$ mkdir /tmp/system
$ sudo mount -o loop system.img.ext4 /tmp/system
[Galaxy Tab 3 General] :
Hazou,

Yes, only a snippet from logcat, i'm working by the numbers. Did you run into anything like this is cm10?

Ketut,

memtrack and memtrack_share live in /system/xbin of the rom. i am wondering if there's a misfire because they might be arm binaries?

meaning a houdini service problem, not starting soon enough? are you still in possession of the cm11 rom you were speaking to?

i've been hunting for a clue to this and i found this http://stackoverflow.com/questions/19945008/failed-to-load-memtrack-module-2

it talks about AndroidManifest.xml but there are a BAZILLION of them ....:silly:

So still looking. will attach memtrack stuff in case it's useful. I have the rom as a backup now so i can just restore. I'l post logcat too.

m

edit - okay, running memtrack in adb, memtrack seems to function though i don't know how to find the data it generates, attached screen shot. so the process looking for memtrack is looking ing the wrong place? will dupe to /system/bin and see. result negative
[Galaxy Tab 3 General] Hazou:
Now i know what i always did wrong with my cm10 system.img :P Thanks!!

Never had any issue with cm10.1 x86. Just needed to change some sourcecode so it would build and add some specific ones from motorola/intel. (github). And add missing libraris files.

What i did for looking for the extra missing files is looking into the loaded libs on android. Follow those libs that are not specific for android (moto/intel/etc.) in what they load (other libs). And then u have a rough amount of property libs that are needed. Sound all easy, its not. So u know :P

And look at the logcat offcourse. Most of the time it tels you what is missing/wrong. Can take days offcourse. If u past the logcat here as u did last time we can all check ;)
[Galaxy Tab 3 General] ketut.kumajaya:
Error occurred because memtrack module not found in /system/lib/hw https://github.com/CyanogenMod/android_system_core/blob/cm-11.0/libmemtrack/memtrack.c This is hardware specific module. On CM 11 for Tab 3 8.0, I ignored it without negative issue.
[Galaxy Tab 3 General] :
on memtrack.c

ketut,

are you suggesting that i modify/patch and rebuild, or are you suggesting that while the memtrack issue is an error, it is non-vital?

if so then i would like to move on to my next red-lettered issue which is this-

I/SurfaceFlinger( 2394): SurfaceFlinger is starting
I/SurfaceFlinger( 2394): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 2394): loaded /vendor/lib/egl/libEGL_POWERVR_SGX544_115.so
D/libEGL ( 2394): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX544_115.so
D/libEGL ( 2394): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX544_115.so
I/GrallocFB( 2394): framebuffer opened
D/hwcomposer( 2394): bool IntelHWComposerDrm::drmInit(): successfully. mDrmFd 18
I/ServiceManager( 2394): Waiting for service MultiDisplay...
I/hwcomposer( 2394): Sprite count: 0, Primary count: 2, Overlay count: 1
I/hwcomposer( 2394): PixelFormatConverter: initialized
I/SurfaceFlinger( 2394): Using composer version 1.2
W/SurfaceFlinger( 2394): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 2394): no suitable EGLConfig found, giving up
F/libc ( 2394): Fatal signal 4 (SIGILL) at 0xb768051d (code=2), thread 2394 (surfaceflinger)

and help with audit.log ? i'm not sure if this is just a permission issue if so what are correct perms and chown?

I/auditd ( 1907): Starting up
E/audit_log( 1907): Could not stat audit logfile /data/misc/audit/audit.log: Permission denied
E/auditd ( 1907): Failed on audit_log_open
I/auditd ( 1907): Exiting

edit audit.log doesn't exist

m

can i mmm libc ?
[Galaxy Tab 3 General] ketut.kumajaya:
Better rebuild your ROM, "make clobber" first and then brunch your target. About auditd error, not sure but you can completely disable auditd for a while by rename /system/bin/auditd or create a special boot.img without auditd service and a kernel without SELinux. As a quick fix, over "adb shell" please try manually create audit.log:

busybox mkdir -p /data/misc/audit/
touch /data/misc/audit/audit.log
[Galaxy Tab 3 General] Hazou:
Looks like he meent non-vital.

Do u have the directory system/lib/egl in your system with the file egl.cfg

That should fix this fatal message.

And y, u can mmm libc

Verstuurd van mijn GT-P5110
[Galaxy Tab 3 General] :
running on empty

guys,

ketut, thanks, i didn't know how to create file .log from command. will try. also no breakfast,brunch only lunch.

this is making me hungry.....

hazou, thanks entry for egl config is;

0 0 android

0 1 POWERVR_SGX544_115

i am starting to reconsider my device tree. will try all suggestions and report back in a few days, need a rest,

butt hurts, eyes bleeding, WAY too much coffee. :eek:

m :good:
[Galaxy Tab 3 General] Hazou:
Don't burn your self out, lol.

This should be for fun, unless u get paid for it :P

Will see it when u have something.

Verstuurd van mijn GT-P5110
[Galaxy Tab 3 General] :
not dead yet =)

No worries about that, i enjoy it, taking a break from cm11 and trying to build philz and then maybe aromafm.

and drink more coffee. :laugh:

m
[Galaxy Tab 3 General] :
EGL hell [ARRRRRRRRGH!!!!]

[MENTION=4479363]Hazou[/MENTION]

i am still htting this egl hangup, on the razor thread you mentioned:

And u did include all the patches from steven about the pixelflinger?

if you have already pointed me to these sorry to ask again but i'm a little frazzled.

now on egl.config entry,

0 0 android <===maybe===> cm , samsung, santa claus ? :silly:

0 1 POWERVR_SGX544_115 <==== maybe explicitly pointing to ===> libEGL_POWERVR_SGX544_115

for your cm10 build is the above same/similar?

mind this is two builds forward from my last post i am including logcat :rolleyes: [yay.....]

coffee time! :eek:

another thought, i think kernel modules are being called/loaded from /system/lib/modules and shouldn't be, meaning maybe there

is a conflict causing ...?
[Galaxy Tab 3 General] Hazou:
For cm10.1 i don't need the patches from steven, but maybe now u need.

The egl.cfg is the same as mine for cm10.1. It is loaded correctly if i see it right in the logcat, it only can't load somethin.

I got this error message too in CM10.1 and solved it after a couple of months... Did u include all the files in the folder "vendor"? And did u include the file in your lib/hw folder "gralloc.(device).so"

In my case i included all of those, but i had named one of the gralloc files: gralloc.mrst.so (stock) and that should be for my device gralloc.sc1.so or gralloc.smi.so (because of the device name set in boardconfig.mk). I just had it wrong, corrected it and i had graphics.

Kernel modules can indeed be loaded from /system/lib/modules as stated in init.cm.rc iirc. But if u use the stock ramdisk they will also be included from /lib/modules. There can only be a conflict if u have 2 of the same named drivers in both directory's.
[Galaxy Tab 3 General] :
hmm

hazou,

okay i am revisiting vendor to discover when i compare to my running 4.2 rom the real gralloc is gralloc.redhookbay.so.1.9.2291151 and is pointed to by two symlinks

named gralloc.redhookbay.so and gralloc.santos10wifi.so , whereas in my dev-tree vendor they appear to be solid duplicates of

the real file, i am assuming that makes no difference and works like hard linking a busybox applet? i will emulate what i see in stock rom probably by adding symlink commands for the above to updater script. I have the similar setup in egl directory so will try the same.

what do stephens patches do and could you link me to them? was that the libenc trick?

also i am interested in your framework patches, those i have, what do they issue address?

also , sorry, do you know how and where i can implement -xlint command for java code in make files or will i have to go to each

offending part individually and run it that way?

again sorry for so many questions, thanks as ever

m
[Galaxy Tab 3 General] Restl3ss:
Hello all! apologies for my absence, I was on vacation for the past bit.

I see a lot has been done since i've been gone, good job all!

gonna set up a new vm tonight and hopefully join the discussion tomorrow

Edit: it appears my old VM is still working fine (i thought i deleted it)
[Galaxy Tab 3 General] Hazou:
If they appear like solid duplicates, than the most likely are. I always thought that symlings can't be copy-pasted. But never tried it.

The libenc is not like one of the patches from stevan. I never looked into his patches because i didn't need them. They are specific for x86 kitkat. Angel has used them, because i know them through him. He has used them for cm i think.

[LIST]
[*][URL="https://gist.github.com/steven676/7276901"]https://gist.github.com/steven676/7276901[/URL]
[*][URL="https://gist.github.com/steven676/7276913"]https://gist.github.com/steven676/7276913[/URL]
[*][URL="https://gist.github.com/steven676/7287471"]https://gist.github.com/steven676/7287471[/URL]
[*][URL="https://gist.github.com/steven676/7287482"]https://gist.github.com/steven676/7287482[/URL]
[/LIST]

This are 4 of his patches, there should be 2 more somewhere on his git.

The framework patch was to disable 'hspap'. Why i needed it for the device i don't know. But i don't need it anymore.

I don't know about the -xlint. Maybe u can do something in the boardconfig.mk. Make a common flag there, but i don't know if that will work.

Hazou
[Galaxy Tab 3 General] :
hazou,

thank you much :fingers-crossed:

i believe these are the other two

https://gist.github.com/steven676/7667657

https://gist.github.com/steven676/7667680

i ran a build with the first four just to see the diff in logcat and i am hopeful. :good:

m
[Galaxy Tab 3 General] :
Completed Boot

okay so,

the patches worked and i am looking at a fairly ugly wallpaper ! :good:

I'm sorry, it's ugly. As expected no wifi no audio no extSdCard graphic lag isn't too bad, i was expecting worse.

hardware buttons work which i didnt expect.

power functions [power off / reboot] do not work, which i expected. to power off you must

su and poweroff -f.

so now, audio, power functions, camera, wifi.

i think solving wifi will do alot to sort out bluetooth

[MENTION=5378432]Restl3ss[/MENTION] pm please ?

[MENTION=4479363]Hazou[/MENTION] do you know steven's xda handle if he has one ?
[Galaxy Tab 3 General] Hazou:
Glad that it boots :) Heuray

No, i don't know his username.
[Galaxy Tab 3 General] :
dalvik houdini patch

Hazou,

hi, i was wondering about your patch for dvm/lib-houdini.

i was wondering if it is applicable to this effort.

i tried it out just to see what would happen :silly:

build stops with no rule to make target which i'm guessing

is referring to a static library that hasn't built yet libhoudini_hook.a

the message itself wasn't very informative outside of missing include libhoudini_hook

i'm pretty sure there is something missing in android make file.

but like i said, just experimenting and was curious :confused:

thank you for reading.

m

and...resyncing.....yay !
[Galaxy Tab 3 General] Hazou:
libhoudini is the translator for arm to x86 code on the fly. As far as i know it needs to be implemented in the dvm code to work and the static lib must be build. We don't have the source code for it, so the people at android-x86 did a great job at implementing houdini with all they had. It worked on my cm10.1, although i haven't tested it with every application.

When all hardware things work it is the next step to make more apps working on android. But when ART becomes available it isn't necessary anymore. as far as i know ART has x86 support implemented.

But why all those resync? U can reset specific git's. And for most changes a "make clean" is not always needed.
[Galaxy Tab 3 General] :
okay so,

after a resync i am dying on this error during busybox when i make recoveryimage

target C: libbusybox <= external/busybox/android/selinux/stubs.c
external/busybox/android/selinux/stubs.c:29:5: error: conflicting types for 'security_compute_relabel'
In file included from external/busybox/include/libbb.h:90:0,
from external/busybox/android/selinux/stubs.c:1:
external/libselinux/include/selinux/selinux.h:179:12: note: previous declaration of 'security_compute_relabel' was here
make: *** [/home/cm11/out/target/product/santos10wifi/obj/STATIC_LIBRARIES/libbusybox_intermediates/android/selinux/stubs.o] Error 1
make: *** Waiting for unfinished jobs....

from stubs.c:29:5:

/* this was changed after 4.4.2 */
int security_compute_relabel(const security_context_t scon UNUSED_PARAM,
const security_context_t tcon,
security_class_t tclass UNUSED_PARAM,
security_context_t *newcon)
#endif

from libbb.h:90:0

# include <selinux/selinux.h>

from stubs.c:1

#include <libbb.h>

from selinux.h:179:12:

extern int security_compute_relabel(const char * scon,
const char * tcon,
security_class_t tclass,
char ** newcon);

and i am mystified, i remember applying a patch to busybox but cannot remember when or where i came across it.

ALWAYS MAKE BACKUPS DUMMY! [i know, i know...sigh]

anyway i am looking but just the same...help :eek:

:laugh:

m
[Galaxy Tab 3 General] Hazou:
Just what it says. The "security_compute_relabel" is mentioned twice. Ones is busybox stub.c and ones in selinux.h. so I assume that the patch in busy box added the string. But to be sure look at the history of both busy box and libselinux. See if in the past there was a patch that included it. Look at the one that was last and try to reverse that patch.

Verstuurd van mijn GT-P5110
[Galaxy Tab 3 General] :
Okay !

[MENTION=5378432]Restl3ss[/MENTION] [MENTION=4479363]Hazou[/MENTION] [MENTION=3034891]gr8nole[/MENTION] [MENTION=4021423]ketut.kumajaya[/MENTION]

okay so i am back in business ! yay! :p

My cat is not impressed.

i need to know if there is any things i need to do special before i start dropping things into /hardware

meaning are there any entries i need to add to my local manifest or project list and if i have to add include entries

to any android.mk files and if so where.

i am going to jump in anyway, but if i am missing something please let me know ?

thank you for reading.

m

starting with /hardware/clovertrail - it would be nice to turn off/reboot the tab the right way
[Galaxy Tab 3 General] Restl3ss:
Hmm, build is rolling through for me then stopping at the same point with the same error. What did you change to get past that point?
[Galaxy Tab 3 General] :
Hey, i downloaded a different version of external_libselinux and external_busybox from cyanogenmod git

and swapped i believe both branches being cm11 shipping. mostly trial and error. the busybox with all

the tty patches/commits is skunky , avoid it.

m

[MENTION=5378432]Restl3ss[/MENTION] a tip- don't clobber when your build dies and don't close your terminal,

minimize it and do the libselinux source swap then re-run your make command [up cursor button to get back to it] the idea is to muscle through till the selinux error is overcome and you hit the busybox error. at that point clobber and run mka recoveryimage, you may not need the busybox

one but if you do, for that one you do have to clobber after swap and re-run mka recoveryimage

when it goes through you're good. then run mka bootimage then mka systemimage.

and run mka otapackage.
[Galaxy Tab 3 General] Hazou:
Okay i looked further into the problem with busybox and selinux. The last patches of busybox and selinux got them both out of sync for x86. Although it stated that it would fix it sort of. But the line /* this was changed after 4.4.2 */ already said it would be a problem for android 4.4.2 or higher for x86. And we are building 4.4.3+.

Have a look here (stubs.c) :

/* Compute a relabeling decision and set *newcon to refer to it.
Caller must free via freecon.
Stub not implemented in bionic, but declared in selinux.h */
#if defined(BIONIC_L) || !defined(__i386__)
int security_compute_relabel(const char *scon UNUSED_PARAM,
const char *tcon,
security_class_t tclass UNUSED_PARAM,
char ** newcon)
#else
/* this was changed after 4.4.2 */
int security_compute_relabel(const security_context_t scon UNUSED_PARAM,
const security_context_t tcon,
security_class_t tclass UNUSED_PARAM,
security_context_t *newcon)
#endif

And here (selinux.h) :

/* Compute a relabeling decision and set *newcon to refer to it.
Caller must free via freecon. */
extern int security_compute_relabel(const char * scon,
const char * tcon,
security_class_t tclass,
char ** newcon);

In the last patch of busybox the line with i386 was added so that when building for x86 (i386) the code gets directed to the "else" code. But that code has last been changed by the last patch of selinux. And gets out of sync because of the "else" code doesn't want to work with the latest selinux.h code.

X86 and ARM (mips too) are using the same selinux code. So we need to change busybox to not redirect the code for x86. If the fix will brake other platforms i don't know. The above stubs.c needs to be changed to this:

/* Compute a relabeling decision and set *newcon to refer to it.
Caller must free via freecon.
Stub not implemented in bionic, but declared in selinux.h */
int security_compute_relabel(const char *scon UNUSED_PARAM,
const char *tcon,
security_class_t tclass UNUSED_PARAM,
char ** newcon)

I don't get the BIONIC_L (heard of it, but don't know what it is) part, but i don't think it will be a problem.

Just use the latest and change that part and u will be good to go.
[Galaxy Tab 3 General] Restl3ss:
so after playing around with the successful 4.4.4. build moonbutt74 pumped out a little while ago I discovered there's one more isssue of note, can't get GApps loaded on it what-so-ever. PA-gapps won't flash. okay. first thought is update binary. so i swap that out. No go.

so i take the gapps files and make my own flashable zip just made to drop them in, made it as basic as possible. (also included nonsensical from all my other work, for reference) That went through, however, nothing meant to get dropped in /system actually got dropped in /system.

ran a few other tests to verify it wasn't just the updater binary, or updater script, but yeah. nonsensical got dropped in data/app and was there and playable upon booting (haha, something that actually works better as opposed to tw. nonsensical never works on first boot without a little user tweaking on tw roms) however, as far as system goes, nothing.

so in one final test i take the CM11 flashable zip and add gapps to it. Doesn't even get to boot animation, just hangs on splash.

On another note, all this was done while waiting for a build rolling through, that seems to be working well after following [MENTION=5864662]moonbutt74[/MENTION] 's advice.

Will keep you posted on progress. Now while I wait and see I think i'm gonna start work on a new Pimpdroid build as, according to samsung, there's no information available on a possible 4.4 launch, meaning whether or not we get kitkat could boil down entirely to this thread. (I know that doesn't necessarily mean nothing, but the fact that there's NO info is a little disheartening)

Keep hacking away my friends.
[Galaxy Tab 3 General] :
on gapps and boot hang

Restl3ss,

try pulling the cm setup/wizard app/s there might be a conflict.

also it seems legacy apps crash in art.

m
[Galaxy Tab 3 General] Hazou:
The gapps libs (maybe apps too) that are in all gapps files are ARM only. x86 isn't supported yet. Take them out of the asus memo pad 7 android 4.3 system img. They can work for android kitkat aswell i think. but don't know for sure. When an android kitkat x86 (razr i in a month, i hope) comes out we have them too for x86.
[Galaxy Tab 3 General] Restl3ss:
ahhhhhh. That makes sense.

i'll stitch together a little GApps package. Thanks for the heads up
[Galaxy Tab 3 General] Restl3ss:
[MENTION=4479363]Hazou[/MENTION]
[MENTION=5864662]moonbutt74[/MENTION]

dell venue 8 is clovertrail based and is running 4.4.2 kitkat. I wonder if this could be of any use.

Gonna attempt to build a GApps package from it. Meanwhile, might be some goodies to help with overall build.
[Galaxy Tab 3 General] Hazou:
The newer the better!
[Galaxy Tab 3 General] Restl3ss:
very true, but finding a firmware of use is proving to be more difficult than an X86 cm11 port :P

haven't been able to find a single rom for it, stock or otherwise