yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] Angel_666:
Hi! thank for thinking with me. :) I'm allready implement this in sepolicy config, and it's working as must be.

I can see it in /dev folder. I apply all fugu sepolicy staff for our device. I think the problem is, that our GFX can't initialize and waiting for surfaceflinger forever. The bad news, if we found that is 100% not a selinux or access problem, that will mean a more deeper problem...
[Galaxy Tab 3 General] :
hey hey,

stuff and things,

[MENTION=4479363]Hazou[/MENTION], since my last build of cwm it went to 6.0.5.1 and i am back to the lag again. Yay!

the libenc thing doesn't seem to do it now. Any ideas ?

on cm11 still unresolved problem with mounting as before. dvm bails, no boot.

Nothing like a hot needle in the eyeball ! syncing repo cm12. ooohh ... sparkly... :silly:

Finally ! Snow !! :)

m
[Galaxy Tab 3 General] Angel_666:
[MENTION=4479363]Hazou[/MENTION] It seems to be that kernel cmdline is not affected by any stuff in BoardConfig.mk. It does'nt matter what i set in config - cmdline is always the same when boot.
[Galaxy Tab 3 General] :
you can use [MENTION=4544860]osm0sis[/MENTION] AIK tool kit to disassemble the boot.img and edit the commandline then repack the image.

this is the thread link http://xdaforums.com/showthread.php?t=2073775

also on my devhost archive in utilities is the android version .

also in kernel source is the option to ignore the bootloader and specify a custom command line.

kind of hit and miss through. need to at least specify init=/init and i believe location of root as well.

m
[Galaxy Tab 3 General] Angel_666:
Hi. I don't need repack boot.img - i build it by my own. As about kernel source - thanks, will check those options.
[Galaxy Tab 3 General] Hazou:
Could it be a permission problem in somewhere in your init/ueventd files? Has a problem like that with another lib (tcmd) and with changing the permissions i could get it to work.

In cwm of cm-11.0 it should give no problem. Nothing changed there. In cm-12.0 pixelflinger is no longer used. So the patch won't work there.

Even when rebuilding your kernel through the normal Cyanogenmod build?
[Galaxy Tab 3 General] Angel_666:
Yes, even if i rebuild in normal CM - cmd is the same. As for PVR initialization, i think i found a problem. Need to apply some patches and fixes from Fugu kernel tree i think..

https://android.googlesource.com/kernel/x86_64/+/1ab88a105a5be03a2d6745d9ca1d272b184c59fa

https://android.googlesource.com/kernel/x86_64/+/e46d75fc85d2777065b259cd533ef89f555d37f7
[Galaxy Tab 3 General] Hazou:
Hmm, maybe those patches work, but i doubt it. But u gotta try. Or isn't it possible to port back the drivers tab 3 needs to the x86_64 kernel. Most of the drivers are the same, i think. Just some don't.

That it didn't changed the kernelboot line i don't really understand. Most likely that it is defined elsewhere and overwrite the settings in the boardconfig.

If CM11 works correctly on my device (it almost does :D), i will also have a look at CM12. Same problems probably (no kernel version update, grrr).
[Galaxy Tab 3 General] Angel_666:
I'm allready ported back all Intel HW folder from Lolipop AOSP to our CM11 source yesterday... All new stuff building ok but AGAIN new error in hwcomposer when booting.. (100 times Grrrr!!!)
[Galaxy Tab 3 General] Hazou:
I did notice that all others are quick to backport. Just small modifications are needed. But the hwcomposer, oh god... That will take ages to backport. I am hoping for some sources from motorola to speed that up.
[Galaxy Tab 3 General] Angel_666:
Finally, i boot this devil! The new CM launcher is BEAUTIFUL!
[Galaxy Tab 3 General] bithunter_99:
Nice job .. pls an image please. i cant wait.
[Galaxy Tab 3 General] Hazou:
Can u pls share your changes/tree with all new and upcoming fixes:)

I definitely like to have a look how you fixed it for your device with the new intel sources:P
[Galaxy Tab 3 General] mzheng086:
[MENTION=1649190]Angel_666[/MENTION] you are my hero!
[Galaxy Tab 3 General] Angel_666:
device_samsung_santos103g: https://mega.co.nz/#!xUAEnTQD!2SPJMZGVUZYFyh9PqW0tN9azHk3reRLsBsXpBlC8SG8

hardware_intel: https://mega.co.nz/#!gNgh2K5B!LOrbhTXJI29fG3M2518ptx9xVYpNoRRRJfgzmnPVT94

I tried to leave some comments in config files. And sorry for unclean sources - trying everything usefull.. :D
[Galaxy Tab 3 General] bithunter_99:
is the first link an image to flash?
[Galaxy Tab 3 General] Rubenyz:
Yeah...

What's the first thing we're goin' to do?
[Galaxy Tab 3 General] :
stuff to do

hi,

for testers, while you are waiting for product you can help with grunt work by way of locating

relevant info concerning:

adding hardware/firmware/device support to kernel

construct a list of all intel atom clovertrail,medfield,merrifield,x86 devices similar in large or small

to gt-p52XX.

rather than flood thread with this information send it to me via pm. [i don't mind.]

i am VERY interested in the kernel portion of this project. All meaningful help in rounding

up this needed information in a speedier fashion would be greatly appreciated.

thank you for reading

m

edit- i have dl'd android4.4.x kernel/common.git/tree from androidx86.org and will be goofing around

with that for a time [and BOOM goes the dynamite...] =P
[Galaxy Tab 3 General] Restl3ss:
so as of right now, i've successfully configured [MENTION=1649190]Angel_666[/MENTION] 's device tree with cm11 and ran the patches listed on his thread successfully (i think, output was cryptic) santos103g showing up fine and well in lunch. Now on to the problem.

when i attempt to build, about 20 seconds in i get this

build/core/tasks/kernel.mk:63: ***************************************************************
build/core/tasks/kernel.mk:64: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:65: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:66: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:67: * source repository to kernel/samsung/santos103g
build/core/tasks/kernel.mk:68: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:69: * for more information *
build/core/tasks/kernel.mk:70: ***************************************************************
build/core/tasks/kernel.mk:198: warning: overriding commands for target `/home/restl3ss/android/system/out/target/product/santos103g/kernel'
build/core/Makefile:44: warning: ignoring old commands for target `/home/restl3ss/android/system/out/target/product/santos103g/kernel'
make: *** No rule to make target `bacon'. Stop.

and the build haults. This output is a bit cryptic, but i think it may have to do with using an older prebuilt kernel with present-day source (though it should work fine if it builds)

any input would be appreciated.
[Galaxy Tab 3 General] :
hey thread moved?

hey,

you could check build/core/tasks/kernel.mk in text editor with line numbers on and maybe hunt down/hack out an ovveride,

else get source for both kernels and drop/patch in the tasty bits. build/core/makefile might be worth a look too.

is there a menuconfig in rom building like with kernel?

those warnings correspond to line numbers in files.

m
[Galaxy Tab 3 General] Restl3ss:
looking at kernel.mk seems to be pointless, all I can seem to find is the trigger for the warning (when disabled, build still haults, only without warning) thinking I might try to build based on cm 10.1 as a, it's older and i might not run into the same problem, and b, since it's also 4.2.2, it might work better with the sammy bits and maybe working wifi / sound?

edit: i suspect the device tree may be broken. That or there's something i'm missing. but, despite reconfigure after reconfigure the last error remains the same (it's not the kernel). looking at the makefile, it's apparent Angel_666 didn't use the same configuration to build the released images as he now has on the tree. I may attempt to build my own source tree, unless someone can point out something i missed?
[Galaxy Tab 3 General] :
hmmm grrr hmmmm

Restl3ss,

hey,

okay so i got your message

will tinker a bit and see if i come up with anything

m:good:
[Galaxy Tab 3 General] Angel_666:
You don't need to make "bacon". Just run ". build/envsetup.sh" then "lunch", select your device number and type "make" (without bacon or any). As for Kernel message - it's not an error, it just a warning. And read this for basics: https://source.android.com/source/building-running.html
[Galaxy Tab 3 General] :
Hello

angel,

Hello *2

would you by any chance have your kernel source?

will a tester owning santos103g please run

#parted /dev/block/mmcblk0

and then

(parted) print all

and post what you get ?

thank you for reading

m
[Galaxy Tab 3 General] :
small successes

Restl3ss,

got mtp access to internal card sorted out mostly

platform.xml push to /system/etc/permissions

till i fix boot.img evry reboot you'll have to chown root:root /mnt and chmod 777 /mnt

m
[Galaxy Tab 3 General] Restl3ss:
What I did was after running envsetup I tried to build using "brunch"

I'll try just trying make. Thanks for the help

Cheers
[Galaxy Tab 3 General] Restl3ss:
That seemed to work sir, the build is moving along. Thanks!
[Galaxy Tab 3 General] Restl3ss:
[MENTION=1649190]Angel_666[/MENTION]

build runs for a while, then stops at this

target SharedLib: libc (/home/restl3ss/android/system/out/target/product/santos103g/obj/SHARED_LIBRARIES/libc_intermediates/LINKED/libc.so)
/home/restl3ss/android/system/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/bin/../lib/gcc/i686-linux-android/4.7/../../../../i686-linux-android/bin/ld: error: /home/restl3ss/android/system/out/target/product/santos103g/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(memchr.o): multiple definition of 'memchr'
/home/restl3ss/android/system/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/bin/../lib/gcc/i686-linux-android/4.7/../../../../i686-linux-android/bin/ld: /home/restl3ss/android/system/out/target/product/santos103g/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(sse2-memchr-atom.o): previous definition here
collect2: error: ld returned 1 exit status
make: *** [/home/restl3ss/android/system/out/target/product/santos103g/obj/SHARED_LIBRARIES/libc_intermediates/LINKED/libc.so] Error 1

any thoughts?
[Galaxy Tab 3 General] pug1:
How did the build go pal
[Galaxy Tab 3 General] :
gcc 4.7 libc.so and memchr, header file maybe?

Restl3ss,

quick question, can you retry build using gcc 4.6?

i'm looking up error with 4.7 right now will post/pm when/if i find solution/answer

m

so from what i get so far, ld: error: has to do with linking of multiple references/functions/instances of X,[memchr]

this was interesting

http://www.pressinganswer.com/26745...n-linker-error-building-on-gcc-makefile-issue

https://bbs.archlinux.org/viewtopic.php?pid=979948#p979948

did you get anything [files] from out/target ===> libc_common.a(memchr.o) , libc_common.a(sse2-memchr-atom.o) ?

maybe a clue there?

also does cyanogen mod have it's own prebuilt gcc, or are you using /google/aosp or the debian/kali setup?

so, on further reading, if the problem is a multiple definition in a header [blah.h] file this has a suggestion

http://stackoverflow.com/questions/...-multiple-definition-first-defined-here-error

http://cboard.cprogramming.com/cplu...line-function-header-multiple-definition.html
[Galaxy Tab 3 General] :
hey hey

Restl3ss,

okay quick question, do you mean hardware/intel/libva/[contents] or hardware/intel/libva/libva-cros/[contents]

as for patches they come up in kompare as malformed, i applied most of them manually, the cwm&twrp patches have me stumped though.

would you mind posting your local_manifest entry so i can check mine, compiling on mac is darwin toolchain right?

i was good with tree and vendor but didn't know about the other stuf, thanks

as for go time

#cd /home/cm11 && . build/envsetup.sh && make clobber && lunch 11 && make -j16 (went through 2,4,8)

stuck at this now which in my mind is progress from before

system/core/libcorkscrew/arch-x86/backtrace-x86.c:24:22: fatal error: ucontext.h: No such file or directory

target C++: libutils <= system/core/libutils/BasicHashtable.cpp

compilation terminated.

attempted odd suggestion of striking include ucontext.h ref. from backtrace-x86.c = no change

good luck with mac, i working on (using angel's example) the dev-tree for santos10wifi, but the goal is to build

angel's setup through first.

m

without the part that ****s your gui update all the tool you installed to setup your build/env, python 2.7.7

your java is square? android sdk?

in between build and yard work i will search for clue/direction

on adding libva my build process completely tanked - removing

ok 3 builds later and i am still unable to resolve the ucontext.h error in

system/core/libcorkscrew/arch-x86/backtrace-x86.c:24:22: fatal error: ucontext.h: No such file or directory

target C++: libutils <= system/core/libutils/BasicHashtable.cpp

compilation terminated.

this is the entry in backtrace-x86.c from line# 21-25 the errors stand at 22&24

21 #ifndef __BIONIC__

22 #// glibc has its own renaming of the Linux kernel's structures.

23 #define _GNU_SOURCE // For REG_EBP, REG_ESP, and REG_EIP.

24 #include <ucontext.h>

25 #endif
[Galaxy Tab 3 General] Restl3ss:
cloned to hardware/intel/libva

though I didn't think to clone to hardware/intel/libva/libva-cros, "doh". The build is moving along on OS X at the moment but it hasn't gotten to the point where it halts on linux, if it does again i'll try that.

As for local_manifests, I actually haven't set that up properly haha, i've just been using git clone manually.

as for building on OS X - i'm not entirely sure what you'd call the toolchain, if there is a darwin specific one i'm not aware of it, as with the exception of the java sdk you get pretty much everything from macports / homebrew / fink depending on which you prefer (I personally use macports). There's a couple of quirks to building on a mac, couple edits need to be done to bash_profile and you need to build inside a case sensitive image file so that git works properly. If you want to attempt a build in OS X I could walk you through what I did (you can install OS X inside a VM if you don't have a mac, google hackintosh)

as for your problem, could this be of any assistance?

http://www.nongnu.org/nsl/libutils/libutils.html

not exactly a fix but might help point you in the right direction.

as for the android sdk, you don't actually need the whole thing, just platform-tools (spesifically, adb) reason being for the extract-files part (which i don't believe is needed for this build, since proprietary files are included)

if you were attempting to build with just device and vendor, maybe you should try cleaning? Might have some files built with incomplete sources that the build is trying to reuse.

also, on the topic of creating a proper santos10wifi tree, in the end that's definitely the right way to do it, but if we can get the 3g version to build properly i can get it to work on the wifi version with a little ramdisk hack (though it's not the right way to do it, and it's very clunky / hackey) so we can test on p5210 to a degree, just not cellular related stuff.
[Galaxy Tab 3 General] Restl3ss:
[MENTION=5864662]moonbutt74[/MENTION]

Building on OS X may have proven to be more fruitful than I thought, though not in the way I was hoping. End up with the same output files, and the build stops at the same place with the same error code (1) however, terminal output looks significantly different. Ends with this

host C: third_party_yasm_genperf_libs_host_gyp <= external/chromium_org/third_party/yasm/source/patched-yasm/libyasm/phash.c
In file included from external/chromium_org/third_party/yasm/source/patched-yasm/libyasm/phash.c:2:
external/chromium_org/third_party/yasm/source/patched-yasm/util.h:78:23: error: libintl.h: No such file or directory
make: *** [/Volumes/android/android/system/out/host/darwin-x86/obj/STATIC_LIBRARIES/third_party_yasm_genperf_libs_host_gyp_intermediates/third_party/yasm/source/patched-yasm/libyasm/phash.o] Error 1

edit: installed libcxx via macports and swapped out libva for one from a different repo, seemed to get the build going again, will post results

edit 2: no go. build did a few other things but still stopped at the same point.
[Galaxy Tab 3 General] :
hey

Restl3ess

i am repo syncing

too many changes i didn't keep track of

dead tired it's almost 2:00 am

so where's angel?

found some interesting stuff in that thing you sent

i'll pm you in morning.

m
[Galaxy Tab 3 General] Angel_666:
There is nothing to flash for now. I mean, that we can build image offcourse, but it's only "skeleton" - just to test for developers. This need to debug and fix all needed feauters.
[Galaxy Tab 3 General] bithunter_99:
what a pity... I thought, i can test now. i dont like the original TW from Samsung.

But its good to see, thats the devs makes advances with a cm1x.x for this device now

>sry for my bad english<
[Galaxy Tab 3 General] Hazou:
The changes look right, but nog everywhere i agree. I thought cloverfield is more like mrst and nog baytrial. But if it works then i am wrong :P

Did u try this hwcomposer as is? No more changes? I have the feeling all the pnw files needs to be backported to work good, but if this works, would be great.
[Galaxy Tab 3 General] Angel_666:
The must funny is that hwc compiled from sources is not working properly. U are right. It even was not compiling "as is". But i make it compile with libdrm without errors for now, will see what we can do next. As for Clovertrail Plus (our platform) it based on old good medfield (as all other by the way with some modifications). My problem was that old medfield hwc not compiled properly. But! If u see at "old" hardware_intel (in my git), u will see that that sources are much more closer to our hardware then "new" lolipop hwc i think. I saw commits in CM git, that it's not work properly with libdrm. As for now KitKat CM working on prebuilded hwc blob (not idealy, but works). Anyway, we must fix it i think.
[Galaxy Tab 3 General] Hazou:
My device the xt890 is using the old medfield board platform and should not work with this hwcomposer. I do have the source of the medfield hwcomposer (looks (almost?) like the one u have) for JB. But that one needs updates to get it work on kitkat.

The difference between medfield en cloverfield isn't that much. just some small modifications afaik. So almost everything that works under cloverfield will work on medfield and visa versa. So we can work at each others software.

I am waiting for the new hwc source from motorola. Normally they release that kind of stuff, but our kitkat update is still in beta. Luckily for us all proprietary libs work "flawlessly" on CM 11
[Galaxy Tab 3 General] Angel_666:
Yes. Agree with U. One more thing - when i try to boot aosp lolipop or cm12 it says, that we need updated proprietary LibEGL's from pvr new ddk sources...

Anyway - i make WiFi working (we have internet!), Ril working for now .. :)
[Galaxy Tab 3 General] Hazou:
Logcat or it didn't happen,

No, just kidding. I dunno about that. Never worked on L and will not do much till cm11 works great, which it almost is
[Galaxy Tab 3 General] xTear:
Is there any to-do list what have to be fixed if the first version can be released?
[Galaxy Tab 3 General] Hazou:
Sorry for the misunderstanding, I am building for the Motorola Razr I (XT890|SMI) where cm11 has only wifi tethering issues. I don't own a tab 3 10.1. But because the tab 3 10.1 is almost like the razr i, also a x86 device and the only other x86 device on xda, i help here where i can and if i can. The tab 3 10.1 is just more complicated or something.
[Galaxy Tab 3 General] Angel_666:
More than this - my first build was based on your sources. But in moto hwc haven't unsupported event error, like we have.. :D Btw. tethering works like a charm :)
[Galaxy Tab 3 General] Hazou:
The unsupported event error is not a fatal error (should boot just fine). I have disabled it with a patch from another person. Dunno his name atm. But i shared the patch a few pages ago. See on my git the cm-11.0 tree. I don't have it as my master tree so u need to change it manually.

But u figured it out i suppose :D
[Galaxy Tab 3 General] Angel_666:
Yea, i saw this patch, but it only turn off err message in rotation event. But we need another event : E/hwcomposer: int hwc_eventControl(hwc_composer_device_1*, int, int, int): unsupported event 1. It more like the error in intel hwc itself...
[Galaxy Tab 3 General] Hazou:
The intel hwc doesn't support an event the surfaceflinger in slinging to it. U should in theorie can insert a logv into surfaceflinger to see what it asks from the hwc.

The patch indeed shuts off the future orientation in surfaceflinger which is a future for some new qcom devices. But if u still get the error, it is very weard. The only other event the surfaceflinger gives is VSYNC. or i could be wrong here.

U could try to use the surfaceflinger service from aosp and see what happens. They are most of the time interchangeable.
[Galaxy Tab 3 General] Angel_666:
Yes. I think it's vsync too. Cos error is still here after patch. Most weird thing that this error call microglitches in ui and slowdown it.

P.S. Just for fun:

HWC freezes only in android interface. In fullscreen games all ok, as u see. Strange...

OK. Whats working for now:

GSM/3G

Wi-Fi

All sensors

Buttons backlight

Autobrightness

Internal and external storages

3d acceleration

OMX components

What we can build from source:

Drm lib

sensors

lights

wi-fi

gsm/3g

OMX decoders\encoders

Bluetooth

What not working yet:

camera (hall module can't connect to interface)

Sound (need to add and setup routes)

Bluetooth (need to check permissions for socket creating)

MTP (need to check inits )

As for Intel HWC source - it builded, but not working with our PvrSGX (vendor) prop libs (crash in libsrv_um and clovertrail gralloc). Using prebuilded hwc for now...
[Galaxy Tab 3 General] xTear:
Does the HWC works?

Did you fix it? :o

Is there any eta for the P5200?
[Galaxy Tab 3 General] Angel_666:
Prebuilded hwc works, 3D games works fine. But i want to build our own hwc from sorce. This give us possibility to modify it as we need.
[Galaxy Tab 3 General] :
angel_666,

hi , in the interim would it be doable to push out an alpha/beta to play with

while you work on getting hwc proper ?

m

i am still working on this, but am still being hung up at the mount issue with external storage.
[Galaxy Tab 3 General] Angel_666:
Some facts about our audio:

1. audio driver called "cloverview_audio" and based on wolfson wm1811 sound chip. Info: http://www.wolfsonmicro.com/products/audio-hubs-%28codecs%29/audio-hubs/wm1811/

Datasheet: http://www.wolfsonmicro.com/media/76197/wm1811a.pdf

2. There is special framework called "parameter-framework". It have plugins, that can drive audiosystem, filesystem, vibrator and other things by xml config files (see dev tree).

3. I tried to build audio.primary lib from 5 (!) different device trees close to our device with same chip and routing, but audiorouting does not even starting. When system started mixer switches (in tinymix) are set to -1 value, default audio device is set to 2 (hdmi-audio). It is wrong.

4. But! If we use stock samsung audiopolicy lib with same audiopolicy.conf - all routes starts OK without errors, and another problem appear - mediaserver crashes and stops all system. What so special can be in samsung audiopolicy??

Any help? :silly:
[Galaxy Tab 3 General] Hazou:
I dunno why the mediaserver crashes. We had it in the 4.1.2 version and Motorola fixed it (for us?) in 4.4.2. Is it an idea to use the audio blobs from the razr i and use the parameter-framework from yours. As i see it the parameter-framework sets the lines to the hardware for the audio.primary and policy. So our routes are outside it (parameter-framework xmls) and the blobs ask for it. It's worth a try..