yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] Restl3ss:
hmm, apparently the problem lurks in my GCC installation. Apparently, homebrew isn't installing it properly, and the built in apple gcc only contains clang. Considering trying to cross-compile normal GCC myself instead of using homebrew. Or possibly, I could try installing my toolchain via fink, which is another alternative that does the same job as homebrew / macports (and has the added benefit of adding the actual apt-get command to mac, which I quite like)

Having a couple beers and hacking away.

As for cross compiling, how are you compiling for our tab? are you doing it on the actual device?
[Galaxy Tab 3 General] Restl3ss:
[MENTION=5864662]moonbutt74[/MENTION]

I seem to have fixed building on OS X. The problem was actually xcode. At least, the version I was using.

Was running xcode 6 beta 1. Switched back to xcode 5.1.x, now build is moving along. (past the error I was having anyway, don't know if i'll run into anything else or not. Will keep posted.)

Just downloaded Xcode 6 beta 7, gonna try it with that one if this build finishes successfully, in order to see if Xcode 6 entirely breaks it, or if it was just a problem in beta 1.

Either way, it seems to be fine on 5.1.x, so worst case scenario i'll keep the .app handy and switch to it for building. I'm gonna get some sleep. Will post in the AM how the build turned out.

Edit: [MENTION=5864662]moonbutt74[/MENTION]

Build for d2lte went through perfectly, posting from it now. Darwin building is a go. Still haven't tested with xcode 6 beta 7 but 5.1.x is working so either way. Now I've got an i7 to build with instead of a 5 year old atom processor. Should make things move a lot faster
[Galaxy Tab 3 General] :
i'm built prebuilt toolchain i686-linux-android 4.8 through ndk, then kept hammering away till i put together a formula

for makefile that doesn't need too much changing, then from then i compile patch recompile till i get going

right. i'll put an example it your folder if you want to check it out. the whole setup does the cc, packs it into

recovery flashable and pushes to device, the cleans up everything to original state.

compiling your own toolchain sounds like a good idea.

m
[Galaxy Tab 3 General] Restl3ss:
[MENTION=5864662]moonbutt74[/MENTION]

So Xcode 6 definitely wholly breaks OS X building. I got my hands on the final release via an app store update. Same problem with all the "unknown command" errors.

Luckily I made a backup of Xcode 5.1.1 on my external hard drive (which I build off of anyway) so I'm gonna switch to it every time I want to build.

might make a custom build script that switches to 5.1.1 before building then back to 6 after. Then again, I can't see any benefit to using 6 over 5 so far, as literally my only use for Xcode ever is android building (I don't own any iOS devices and I don't develop mac apps. The mac itself was a christmas gift, but I'm actually rather fond of it functionality wise, once you cut out some of the stupid apple safe-guards and add some standard linux utilities)

After a little more digging the problem isn't necessarily that Xcode 6 has less functionality, but rather that the darwin-specific things in the CM11 source aren't updated to work with it (some commands are slightly different) I don't see it being updated for a while, as most mac users who build are still likely on 5.1.1.

Script would probably look like this, tell me if I'm missing anything

echo "xcode-switcher / android builder"
sleep 2
sudo xcode-select --switch /Volumes/TOSHIBA_EXT/Xcode-5.1.1.app
sleep 3
cd ~/
mountAndroid
cd /Volumes/android
source build/envsetup.sh
sleep 1
lunch
sleep 2
mka recoveryimage
sleep 2
mka bootimage
sleep 2
mka systemimage
sleep 2
make otapackage
sleep 2
sudo xcode-select --switch /Applications/Xcode.app
sleep 1
echo "Done!"

One thing i'm unsure of is whether to use "mka otapackage" or "make otapackage"

Anyway, I think that about sums it up. Build is scrolling along, off to bed for me. Will post results in the A.M (or P.M, depending on how long I sleep in)

Cheers
[Galaxy Tab 3 General] Hazou:
Mka is the fastest way to build.
[Galaxy Tab 3 General] :
hey hey

Restl3ss,

sorry to take so long in getting back to you.

at this point i've lost track of how many builds i've run and all the things i've tried.

i am at a complete loss but, still trying anyway. i would be interested in seeing

your boardconfig and device make files and knowing what you have in hardware_intel.

with the 4.4.2 kernel and x amount of builds i still hang at the same fatal libc error for surfaceflinger,

with no clear hint in the log of where to look. the hex/dec/oct [i will never get those straight] :silly:

looks like this (0x00000000) . is that a bad address, null pointer, segmentation fault, something?

and what do i do with about it ? i'm running another build, so i'll have another log soon.

maybe something will change. [sigh]

m
[Galaxy Tab 3 General] sscsps:
I would like to be a dev for t211, if you are considering that, I have it and I really want to make something for it before it is dumped in the trash can (as I might get a new device)

I do have a basic knowledge of command lines and I am currently doing B.Tech in computer science and I have some experience of writing some big programs, and some good algorithm, if you guys willing to teach me the advanced part, I am totally willing to do it :)
[Galaxy Tab 3 General] No Expert:
Restl3ss ,

could you use any of the work done by the guys here?

http://www.android-x86.org/
[Galaxy Tab 3 General] social-design-concepts:
personally haven't tried this source yet it's another clover trail plus based device :

https://github.com/gpdroid
[Galaxy Tab 3 General] :
from my earlier post

i am repeating this post as i have yet to resolve this issue.

i have learned that the fatal error from below;

F/libc ( 1893): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1893 (surfaceflinger)

is a segmentation fault - wiki quote

i do not have the experience or knowledge to address the issue and require assistance from

experienced developers/programmers.

I/SurfaceFlinger( 1893): SurfaceFlinger is starting
I/SurfaceFlinger( 1893): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
[COLOR="Purple"]D/libEGL ( 1893): loaded /vendor/lib/egl/libEGL_POWERVR_SGX544_115.so
D/libEGL ( 1893): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX544_115.so
D/libEGL ( 1893): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX544_115.so[/COLOR]
[COLOR="Red"]E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 14
E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 15
E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 16
E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 16
E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 16
E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 18[/COLOR]
[COLOR="Purple"]D/hwcomposer( 1893): bool IntelHWComposerDrm::drmInit(): successfully. mDrmFd 19[/COLOR]
I/ServiceManager( 1893): Waiting for service display.intel.mds...
[COLOR="Red"]E/IMGSRV ( 1893): :0: PVRDRMOpen: TP3, ret = 24[/COLOR]
I/hwcomposer( 1893): Sprite count: 0, Primary count: 2, Overlay count: 1
I/hwcomposer( 1893): PixelFormatConverter: initialized
I/SurfaceFlinger( 1893): Using composer version 1.3
I/SurfaceFlinger( 1893): EGL informations:
I/SurfaceFlinger( 1893): vendor : Android
I/SurfaceFlinger( 1893): version : 1.4 Android META-EGL
I/SurfaceFlinger( 1893): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable
I/SurfaceFlinger( 1893): Client API: OpenGL_ES
I/SurfaceFlinger( 1893): EGLSurface: 8-8-8-8, config=0xf
[B]THIS--->[/B][COLOR="Red"]F/libc ( 1893): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1893 (surfaceflinger) [/COLOR][B]<----THIS !!!![/B]
[Galaxy Tab 3 General] Restl3ss:
Damn, this is frustrating. I understand what the problem is but I don't have the sweetest clue how one would go about fixing it. I've got a couple hours tonight so I'm gonna go on an ultra google / trial & error / hammer smash session.
[Galaxy Tab 3 General] Restl3ss:
Also, surfaceflinger is the problem on your P5210 build, but [MENTION=1649190]Angel_666[/MENTION] 's P5200 build had working surfaceflinger and stopped at optimizing apps. Really wish we had the other ROM to look at, might be able to figure something out
[Galaxy Tab 3 General] :
hey,

yep, still banging my head against this. [boink] :silly:

still trying to figure out how to mod kernel sources to swap hardware/firmware.

the kernel isn't sacred, it's meant to be chopped up and stitched back together. ;)

m

note- the issue occurs when using the 4.4.2 kernel.

[MENTION=1649190]Angel_666[/MENTION] ,

dude, can you post your most recent build or the one with the hang at app optimization ?
[Galaxy Tab 3 General] social-design-concepts:
Where can I clone your device branch from?
[Galaxy Tab 3 General] Restl3ss:
He posts his stuff on devhost, just download and place manually
[Galaxy Tab 3 General] Restl3ss:
[MENTION=5864662]moonbutt74[/MENTION]

Alright. I've got a 6 pack in hand, 2 1/2 hour Rammstein concert playing in the background, and a bag of york peppermint patties. Let the incessant google / trial and error session begin.
[Galaxy Tab 3 General] :
okay,

sdc rest3ss,

my current trees are posted on my devhost archive http://d-h.st/users/moonbutt74/?fld_id=40549#files

on 4.2.2 tree - sdc, search out this thread for all of hazou's patches and restless's setup instructions.

this tree will result in a rom which boots with no sound,comm,video decoding,external storage, i am uncertain of sensors

root may be twitchy and power options are missing something somewhere, meaning forcing reboot/power via terminal or

button crash.

on the 4.4.2 tree still fighting to get this one to boot. this is the one with the segv problem i was whining about.

if the logcat is to be believed, comm mat be registering properly, as is external storage, sound is still no go BUT, need to solve

the boot issue with surfaceflinger, unlike tre 422 you will need to use the stock ramdisk and rig it to boot to animation

which will ultimately hang. 422 tree should boot out of the box.

some assembly required on either tree adjust boardconfig fstab entry for recovery you will build, either twrp.fstab or recovery.fstab.

as i am now getting a stupid python error involving as missing module bz2 i am going to take a day or two to downgrade my system and shove my head into a blender [again].

major note- some of hazou's patches are official now . i dont recommend using commits that remove them.

i am fairly certain that for most everything our problem now lies in the display drivers in the 4.4.2 kernel source hence my

need to learn how to frankenstein the damn thing. i want to use the display drivers from the 4.2 source in the 4.4 source.

blender's away !! :silly:

m
[Galaxy Tab 3 General] Restl3ss:
I have a small experiment I'm gonna try, I'm gonna take libc from WIP 1 and replace the one in WIP2. Fairly simple experiment but hey, occam's razor may prove true. No successful blends of the two sources, so why not the finished product?
[Galaxy Tab 3 General] Restl3ss:
Well, Darwin / OS X building seems to once again be broken for me, so it seems I'm going back to VMs for the time being (it's so much slower. gaah)

I have no idea what happened. one moment it's working. the next, this

make: *** [/Volumes/android/system/out/host/darwin-x86/obj/lib/libbcc.dylib] Error 1
info: reading model symbols external/srec/config/en.us/models/models128x.map
make: *** Waiting for unfinished jobs....

it's also important to note that mkvendor.sh is saying unpackbootimg isn't found despite the fact that i've run make -j4 otatools multiple times. It's borked for an unknown reason.
[Galaxy Tab 3 General] :
okay, first error looks like a toolchain problem but as i don't run mac i couldn't tell if you need a patch or swap to a different toolchain.,

on otatools do you need to run that? building on linux that was already set up from mka recoveryimage/bootimage

search cyanogenmod github and clone/download zip and drop in, double check locations in .sh's and .mk's

would like to see more of the output for the first error.

ran a new build just to hit surfaceflinger problems again going to resync after one more go.

m
[Galaxy Tab 3 General] Restl3ss:
Make otatools is just a way of taking care of the host tools without running an actual build, it's useful if you're trying to create a new device tree on a fresh source (which I was attempting to do to expand my knowledge)

On toolchain, i tried reinstalling, reconfiguring, symlinking, and everything in between. I have no idea what's going on but for me Darwin building is borked again and I've given up trying to fix it for now. Just spent the night setting up a new Debian VM, syncing as we speak. Gonna sleep and start anew in the AM (actually, PM in my case since i'm nocturnal at the moment)
[Galaxy Tab 3 General] Restl3ss:
I'm honestly considering trading for a tab 2 10.1 haha

looking at their development forum is making me cry.

Why samsung, why

My latest build attempt seems to have yeilded a frozen terminal for some unknown reason. It's been on contacts.apk for about 10 minutes. Any luck on anyones end?
[Galaxy Tab 3 General] :
Yeah, i know what you mean, i am slowly drifting away from this and back to my own projects.

i got hold of note 10.1 [old] about a month ago and have been playing with that too.

but on the tab 3 front, i am currently compiling gcc 4.8 and make as well as depenencies. starting to get the hang

of things, at this point i'm treating android like i would gnome3 or kde and focusing more on gnu/openbsd-linux stuff.

my hang-up with cm11 continues to be with surfaceflinger. i have been using netbeans and tutorials to get a better understanding

of c/c++ as far as understanding how to patch/modify/correct but that will be a while coming.

outside of that i got nuthin'. :(

m
[Galaxy Tab 3 General] Restl3ss:
I honestly have been too, i've been putting my own device tree together for the samsung galaxy discover (it's a cheap little device samsung pumped out and never updated past 4.0.3, pretty crappy but meh) and so far even starting from scratch has been easier than working with an x86 tablet. I'm still wondering where angel_666 went, would be really nice to see his logs since his surfaceflinger is supposedly working.

Guess this all comes down to resolve in the end. How badly do we want this
[Galaxy Tab 3 General] :
What it comes down to for me is we're not working with a well worn standard here.

the arm crowd has it easy by comparison. also keep in mind the source modification we need

exists, but samsung has it. :mad:

ketut is right about using the androidx86 project to a degree. My bet is still swapping display source from 4.2 kernel to 4.4

just haven't managed to get it right yet.

m
[Galaxy Tab 3 General] Restl3ss:
Hmm, i've considered working with the android-x86 source code actually, but there remains a slight problem, in that it's designed to compile into a .iso so getting a flashable zip from that would be an absolute pain in the ass, though not so much of a problem as it sounds. What i'm thinking is maybe use the CM makefile and hybrid the two sources, adding things as they become necessary to complete the build.
[Galaxy Tab 3 General] mzheng086:
The wifi tab has a new firmware released at Sep 22nd. Maybe that helps?
[Galaxy Tab 3 General] Restl3ss:
Nah, it's just another area based release, same firmware. Appreciate the eye-out though

[MENTION=5864662]moonbutt74[/MENTION]

I've synced the android-x86 source code and I'm gonna start experimenting.
[Galaxy Tab 3 General] Restl3ss:
[MENTION=5864662]moonbutt74[/MENTION]

I've created a hybrid source between cm11 and android-x86, I'm using android-x86 as the base and copying things from CM11. Build seems to be moving without error, will post results tomorrow.
[Galaxy Tab 3 General] xTear:
Samsung Source

I'm not sure about this, but isn't the Source-Code published from samsung @ opensource . samsung . com ?

But could this be the samsung source code for Kitkat for the p5200 be?

if it is the source-coude would'nt be possible to use the code?
[Galaxy Tab 3 General] :
xTear,

hi,

you are prtially correct in that the source available is for the kernel only. The samsung aosp/touchwiz source/build environment however, is not available to the public.

m

ps, my spelling is super awesome ... :silly:
[Galaxy Tab 3 General] Restl3ss:
Well, so far the kernel has built succesfully, on the systemimage i'm running into missing header file hell so still tweaking the source a bit. Will keep posted.
[Galaxy Tab 3 General] :
Restl3ss,

hey hey,

some of your header issues may be connected to you toolchain, check your toolchain's directory in it's /include and /bin

sub-directories. in the /bin directory there may be some symlinks pointing to the wrong/inappropriate version of python, also

in some prebuilts /bin/toolchain-name-version-ld may be a bad actor in which case you may be able to point to an alternate

instead as long as it's same/similar version. in the /include sub-directory [if present] you may symlink to headers in

/usr/include.

m
[Galaxy Tab 3 General] Hazou:
I still dont think that this is a toolchain error.

Shouldn't be because i and the geekphone can use the stock one. It looks more like a library error. A missing one, in the wrong place or even a library needs renaming. I already got cm11 working on the razr without any difficulty.
[Galaxy Tab 3 General] :
Hazou ! :)

hey, hey

I'm jealous....:p

Do you have any thoughts on the surfaceflinger problem that's holding me up ?

It's a few posts back, I'm not really sure where to go. :(

is cm11 fixed mostly now for x86 ? :confused:

I really need to stop using these smiley faces . :D
[Galaxy Tab 3 General] Hazou:
Y, cm11 has some fixes (mine included :victory:) . Not all of them. Have a look at github.com/geekphone/cm11_patches. Those hold almost most fixes, but also has to much that isnt needed for your device. And it is missing the pixelflinger one. Just pick what u need and add mine.

Get me a cm11 zip and a link to a fast downloading stock rom(official all so slow...) . I will have a look tomorrow and see if i can find any.
[Galaxy Tab 3 General] :
Hazou,

i will have to run a new build so give me a day or two. my two builds are here

wip one [4.2.2 kernel/proprietary sources up'ed to selinux support, no comm,audio, video]

http://d-h.st/01Q

wip two [4.4.2 source/proprietary needs to use stock 4.4.2's boot.img - this is the one with the surfaceflinger problem,

if i read logcat right it seems the rest of the hardware may actually be working so, RAAARRRGH !.

http://d-h.st/ma1

the are my current trees [4.4.2 and 4.2.2]

http://d-h.st/users/moonbutt74/?fld_id=40549#files

and this is how i look right now :silly:

Restl3ss' repack of the official 4.4.2 release for gt-p5210 is square.

http://xdaforums.com/galaxy-tab-3/development-10/rom-100-stock-4-4-2-kitkat-p5210-wifi-t2848279

I can't seem to find the geekphone patches on git hub , could you provide the users name ?

thanks.

m

[MENTION=5378432]Restl3ss[/MENTION] going to dump my repo and start over.
[Galaxy Tab 3 General] Hazou:
Sorry, got the wrong name. The maker is geekphone. It is github.com/gpdroid
[Galaxy Tab 3 General] :
okay , i am seeing from https://github.com/gpdroid

https://github.com/gpdroid/revo_cm11_patches <------ this one ?

https://github.com/gpdroid/revo_android

https://github.com/gpdroid/revo_android_external_libvpx

and a device tree https://github.com/gpdroid/revo_android_device_geeksphone_revolution

i posted what mess i have in previous post and link to restl3ss' repack of official 4.4.2 for gt-p5210

m
[Galaxy Tab 3 General] Hazou:
The revolution is almost the same device as yours. U could in theorie use his device repo to build yours. With small modifications offcourse. Especially look into the proprietary-files.txt. Everything u have on your device that's matches the ones in that file is needed, but u will need to add some extra special to your own device.

The "revo_cm11_patches" were the ones i talked about. Don't use all of them, just some.

If u do copy over all the vendor files and all things needed for graphics u should be good. 1 thing u could try is removing the 'gralloc.santos10wifi.so' and only have one of them (e.g. gralloc.clovertrial.so). I dunno how android reacts to 2 hw files with different names but with the same function.

If i have a look at the revolution (they will match yours) u will need the following from the proprietary-files.txt from your device:

Everything under (only for graphics, the rest is yours to decide):

- system/etc/atomisp/*

- System/lib: libdrm*, libglib?, libmultidisplay*, libsepdrm*, libsepipt?, libtbd?, libva*, libwsbm, libpvr2d, libsrv_um, pvr_drv_video

- system/lib/hw/hwcomposer*

- PVR (1 gralloc (if they match in size), not 2)

- From your device everything under vendor (just to be sure, see gralloc!)

- system/lib/drm/*

- system/lib/egl/* (not sure about libgles_android atm)

Don copy over: libegl, libgles*

With the following commands u can see if files are related to others:

"readelf -d -t" (-t maybe not needed, dunno atm). U can list the shared dependencies of files. So do this for all non-cyanogenmod files (build cyanogenmod without your files, so just an x86 build and compare). Only library's. Map it, write it up.

Better then the above:

"grep -rnw -e "word" cd to the system. and use the string and change word with 'libdrm' to get all files that have libdrm in it. Most of the time all files that have libdrm in it will make use of it. I did this to eliminate all extra files or include some etc/* files i needed. U can also use this on libs that don't have a shared dependency. Sometimes the library will load a library from within the code. Not as a normal shared library. See libril from samsung as an example.
[Galaxy Tab 3 General] :
concerning hardware_intel

[MENTION=4479363]Hazou[/MENTION],

hey, thanks for the lead, i finally got to bootanimation with boot.img [cm] from 4.4.2 kernel source with adb root a go and adb remount

functioning correctly ! :) Currently backtrack to work out hwc hang.

[MENTION=5378432]Restl3ss[/MENTION] [MENTION=1649190]Angel_666[/MENTION] ,

guys, quick question, what do you have under hardware_intel ?

thanks.

m
[Galaxy Tab 3 General] social-design-concepts:
you guys taken alook at any of the intel code in android-5.0.0_r2 yet?
[Galaxy Tab 3 General] Hazou:
Do you mean the "hwcomposer unsupported event 1?" Then i got the solution :D
[Galaxy Tab 3 General] :
Yup, so what's the fix ?

m
[Galaxy Tab 3 General] Hazou:
It all has to do with the surfaceflinger.

The bug literally means that an event pushed to our hwcomposer isn't recognized and cant be executed. It just doesnt know that event. From the AOSP tree is the only event available the 'EVENT_VSYNC'. But in Cyanogenmod there is a second event, namely 'EVENT_ORIENTATION'. As long as the hwcomposer of the device doesnt know this event it will come up with that error. We can maybe fix it if we get the source code. Maybe even by using the hwcomposer from gpdroid we can make it work.

The EVENT_ORIENTATION came with this patch: EVENT_ORIENTATION Patch

There is a fix for hwccomposer from 1.0 and under and that is: Undo EVENT_ORIENTATION patch for hwc 1.0

I tried to get us in that patch above, but it is more integrated than i know at the moment. So another way to fix it is to never let the surfaceflinger call the EVENT_ORIENTATION. To do this we need to remove the extra code from the first patch that started it in surfaceflinger.cpp. This is a quick fix and need some fine-tuning, but it will do the job.

Got a more or less stable build now. Still some denials and small things.

Edit:

See this: https://gist.github.com/pawitp/7891444 I will use that fix from now on.