yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] Hazou:
Hey,

What commands are u using when starting a build? And did u get some sort of errors somewhere?

Did the SKIA patch work?

I looked into your recovery problem and mounting problems of the rom and boot/recovery image.

I changed the following files so they should be compatible with 4.4.x from now on: init.santos10wifi.rc, fstab.santos10wifi and storage_list.xml

Make a backup and replace the init and fstab file in the inits folder. Same for the storage_list but then in the overlay/frameworks/base/core/res/res/xml folder. and try again :P

But keep in mind, this can screw up your storage in other roms. So make a full backup and if needed wipe everything including your internal storage and restore your nandroid.

For your compiling problems i need some more time. I think it has something to do with, that the build system asks for the wrong compiler. Fixed it in 10.1, but 11 should be a little bit different.
[Galaxy Tab 3 General] :
hmm

hazou,

okay, neat, will try, on compiler meaning gcc,llvm and can those be swapped around like java? i have been to the homepage for llvm and had

thought about chaninging version.

on errors

for cm11= i continue to get the bootstrap classpath not set and find src no such file or directory = these are java errors the bootstrap error

referring to -1.5 sources. skia patch- ican't say if it does or doesn't work till i have a rom i can run, if by work meaning does it resolve/silence the error and permit the build to continue then yes.

on aosp= find src no such file or directory and aapt warnings about missing language resource , compiler complains less and i've been slowly adjusting my device tree which seems to be correcting the errors i haven't mentioned.

for cm11 & aosp I = [prompt]# cd /builddir/top && make clean && . build/envsetup.sh && lunch # && make -j10 or make recoveryimage -j10

in cm11 i've done ./get-prebuilts but not in aosp. I will post my aosp build log though i know we are focusing on cm11 i thought it

would be interesting to put the two against each other to see the differences.

thank you for reading , thanks for helping.

m

also get Xlint messages - java again right?

i'm using oracle-sun java cm11=1.7 aosp=1.6

[MENTION=4479363]Hazou[/MENTION] - on fstab and xml - extsd still doesn't grab. i tried different combinations using the mmcblk1 entries and either result in panic/reboot or bootloop or null effect. now i understand there is some quirky stuff that's been done to kitkat by google but, angel_666 built the rom with the extsd write fix already in place as far as i can tell, so i'm guessing vold. a question- hwcomposer works like hal?
[Galaxy Tab 3 General] javee:
P5220! I'm on! Let's test this!
[Galaxy Tab 3 General] :
concering the removal of twrp from build

okay so,

i need to remove twrp from build, completely all references. there are places in the device tree that still reference it and i haven't

found them all yet. as to why, a while back i noticed an issue concerning fstab and vold, and i feel that i am mostly if not completely on target as per the following when i run make otapackage -j#

-------------------------------------------------

Traceback (most recent call last):

File "./build/tools/releasetools/ota_from_target_files", line 1057, in <module>

main(sys.argv[1:])

File "./build/tools/releasetools/ota_from_target_files", line 1000, in main

OPTIONS.info_dict = common.LoadInfoDict(input_zip)

File "/home/aosp/build/tools/releasetools/common.py", line 155, in LoadInfoDict

d["fstab"] = LoadRecoveryFSTab(zip, d["fstab_version"])

File "/home/aosp/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab

raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))

ValueError: malformed recovery.fstab line: "/system ext4 /dev/block/mmcblk0p8"

make: *** [out/target/product/santos10wifi/aosp_santos10wifi-ota-eng.root.zip] Error 1

-----------------------------------------------------

i have attemtpted an edit to common.py suggested from this thread;

http://xdaforums.com/showpost.php?p=44382892&postcount=1219

to no success. what i need is the correct recovery.fstab V2 entries for our device.

As to the problem with my system applications and associated framework jars not building, i still need help with a solution,

for the moment to push this annoying **** of a process along i am pulling needed files from other roms [4.4.x]

this is not a solution.

m

[MENTION=4479363]Hazou[/MENTION]

i am building aosp as you may have noticed until i have a span of time to rerun cm11 repo setup.

don't misunderstand me, i am greatful for all of your help, but, the patch addressing the kernel defconfig issue

went...um...boom. so i dont think that is a go in it's current state. when i get repo redone i will try modifying and see what happens, i was really due for a resync anyway =p .

However, the fstab, vold issue i think holds true in cm11 which is where i first noticed it.

aosp just seems to confirm it.

Aaandd ....resyncing......yay!
[Galaxy Tab 3 General] Hazou:
Haha Kaboom...

No problem, just trying to help ;)

Aosp is almost the same as cm, but my patches won't work on them most likely.

The fstab mentions that a line is wrong. Will have a second look in a day. Will make a patch for the kernel building also, need it myself in a few months for my device.

Verstuurd van mijn XT890
[Galaxy Tab 3 General] :
screaming

okay so resynced, patched as before and now at beginning i get

"ebtables is disabled on this build" ==========> still no answers

find: `src': No such file or directory ===========>still no clue

edit- i am one step removed from being a flaming moron simply because i have yet to strike the match.

ANYWAY, this is my local_manifest.xml entry

-------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="CyanogenMod/android_device_samsung_santos10wifi" path="device/samsung/santos10wifi" />

<project name="CyanogenMod/android_device_samsung_santos10wifi" path="kernel/5210" />

<project name="CyanogenMod/android_device_samsung_santos10wifi" path="device/samsung/santos10wifi/vendor" />

</manifest>

----------------------------------------------------------

match locations with boardconfig and your kernel source will register

but now i am getting every damned error i can get from bionic/libc/kernel

if tinkering fails, i will post log.

m
[Galaxy Tab 3 General] gr8nole:
Is that really what your local_manifest looks like? That looks messed up to me.

I would make it look like this, then update BoardConfig.mk to match.

<manifest>
<project name="CyanogenMod/android_device_samsung_santos10wifi" path="device/samsung/santos10wifi" />
<project name="CyanogenMod/android_kernel_samsung_santos10wifi" path="kernel/samsung/santos10wifi" />
<project name="CyanogenMod/android_vendor_samsung_santos10wifi" path="vendor/samsung/santos10wifi" />
</manifest>

Also, it doesn't look like the projects you have listed even exist. Is it because this is x86? If I go to https://github.com/cyanogenmod/android_device_samsung_santos10wifi I get nothing.

Feel free to ignore me if I am completely wrong, but this is how I do it.
[Galaxy Tab 3 General] :
gr8nole !!!!!

gr8nole,

HA, yeah you won't find it because it isn't supported,

kernel/5210 is where i placed my kernel source

now vendor i was a little iffy on, to get a full idea of what's going on here you have to start with angel_666's

thread for cm11 on santos103g and then start at the start of this thread.

my issues are like a raging battle [final fantasy preferably] i lose ground, i gain ground.

i originally use angel' device tree , then started cros referencing whith trevd's and hazou's then adjusted a seperate tree

to conform with aosp build then went back to cm11 and so on and so forth. my main problems right now

are with bionic/libc/* and trying to find an answer as to why my needed system applications and their associated

framework jars do not build, i also have a seriously annoying problem with fstab relating to twrp, i get the base system to build

and in a seperate turn i get some of the missing frameworks to build, but at plain make -j# a lot is missing and at make otapackage -j#,

i get stopped by fstab malformed line error. It's maddening, this is a journey into the final frontier and i'm the guy wearing the

red shirt. :eek: :p

any meaningful help would be appreciated.

thanks for reading

m

if vendor should point to /top/vendor/device what exactly belongs in that directory?

can i duplicate vendor/cm and rename it to [device] and modify it from there?

I don't ignore anyone who actually has something meaningful to contribute.
[Galaxy Tab 3 General] gr8nole:
If you will upload your device tree (device/samsung/santos01wifi directory) to github, I will take a look when I get back from my weekend camping trip.
[Galaxy Tab 3 General] :
device tree

gr8nole,

my device tree is here dev-host http://d-h.st/users/moonbutt74?fld_id=37380

as git is still a bit of a mystery to me. i set up an account but as of yet am not familiarized

with how to's. i'll work on it but in the interim this will have to do. alternately you can look at angel_666's tree which

is on github, they are mostly similar. my current tree has evolved some. i will get that uploaded soon.

thanks man

m

[MENTION=3034891]gr8nole[/MENTION] github link to dev-tree https://github.com/moonbutt74/device_samsung_santos10wifi
[Galaxy Tab 3 General] gr8nole:
To get it to build the packages you are missing, add this to your device.mk.

$(call inherit-product, build/target/product/full_base.mk)

Also, in your cm.mk, I would use this

$(call inherit-product, vendor/cm/config/common_full_tablet_wifionly.mk)

instead of the call to build the phone stuff.

(Sent from my campsite that has 4g coverage)

Sent from my SCH-I605
[Galaxy Tab 3 General] :
hey hey

hey thanks will try asap.

i could've waited man, now go enjoy nature !!!!

:good:

m

okay, so according to my build output, system apps are building!

give me a few days to update my dev-tree as i have yet to learn how to do that.

gr8nole, thank you again.
[Galaxy Tab 3 General] :
okay so,

this is where my build hangs, last night while going through the webkit stuff i exited with a compiler bug error but i lowered the job number to 4 and went at it again and it seems to have gone through, but this error is consistent/persistent. as usual i am looking

up how to fix/address it, i post anyway to speed up the process. getting closer.

external/chromium_org/third_party/WebKit/Source/core/html/HTMLTextAreaElement.cpp:199: error: undefined reference to 'WebCore::RenderTextControlMultiLine::RenderTextControlMultiLine(WebCore::HTMLTextAreaElement*)'

collect2: error: ld returned 1 exit status

make: *** [/home/cm11/out/target/product/santos10wifi/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1

-----------------------------------------------------------------------------

this is the entry from line 197-200 from HTMLTextAreaElement.cpp

197 RenderObject* HTMLTextAreaElement::createRenderer(RenderStyle*)

198 {

199 return new RenderTextControlMultiLine(this); <=========this is the error, comment out or fake?

200 }

-----------------------------------

currently i approach build this way;

. build/envsetup.sh && lunch ##

make libandroid_runtime -j#

make framework -j#

make services -j#

make bootimage -j#

make recoveryimage -j#

and then

make -j#

i do up to recoveryimage then reboot and do make -j#
[Galaxy Tab 3 General] tgalal:
I'd like to join. I have access to Galaxy Tab 3 7'', 10'', 8'' and several other tablets including the Tab 4 series. I am a developer, linux user, my experience with building roms is not that much yet. So far I managed to port custom recovery (cwm/twrp) to Tab 4 7'' and 10'' and working on digging deeper into that rom porting game.
[Galaxy Tab 3 General] :
build complete?

okay so,

my build completes/ends after creation of system.img [669.9 mbs]

inspection of system folder in output/* appears to show all present and accounted for, though

size of image has me a little confused.

my approach this time was

make modules and then

make -j4

my question is now how do i turn this into the flashable cm11-*-.zip that i thought was supposed

to be the endpoint of make -j* ?

meaningful help would be appreciated.

thank you for reading

m [MENTION=3034891]gr8nole[/MENTION] - sorry to bother you

edit- i ran make otapackage -j4 which resulted in this:

Package target files: /home/cm11/out/target/product/santos10wifi/obj/PACKAGING/target_files_intermediates/cm_santos10wifi-target_files-445fb7cfa1.zip

Package OTA: /home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip

MKBOOTIMG= \

device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files -v \

-p /home/cm11/out/host/linux-x86 \

-k build/target/product/security/testkey \

--backup=true \

--override_device=auto \

\

\

/home/cm11/out/target/product/santos10wifi/obj/PACKAGING/target_files_intermediates/cm_santos10wifi-target_files-445fb7cfa1.zip /home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip

/bin/bash: device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files: Permission denied

make: *** [/home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip] Error 126

do python scripts need to be made execuable?
[Galaxy Tab 3 General] gr8nole:
I don't know about that.

I always use the 'brunch' command to build instead of the individual 'make' commands. It will make everything (boot, recovery, ota and full flashable zip).

Sent from my SCH-I605
[Galaxy Tab 3 General] :
unsupported device no breakfast brunch or bacon, only lunch

alright, thanks though, :good:

[MENTION=5378432]Restl3ss[/MENTION] [MENTION=4479363]Hazou[/MENTION] [MENTION=1649190]Angel_666[/MENTION] starting at two posts up.

okay, so i mad python scripts execuable and again i am hit with the malformed fstab error among others ;

Package OTA: /home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip

MKBOOTIMG= \

device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files -v \

-p /home/cm11/out/host/linux-x86 \

-k build/target/product/security/testkey \

--backup=true \

--override_device=auto \

\

\

/home/cm11/out/target/product/santos10wifi/obj/PACKAGING/target_files_intermediates/cm_santos10wifi-target_files-445fb7cfa1.zip /home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip

unzipping target target-files...

running: unzip -o -q /home/cm11/out/target/product/santos10wifi/obj/PACKAGING/target_files_intermediates/cm_santos10wifi-target_files-445fb7cfa1.zip -d /tmp/targetfiles-bXhdxu

Traceback (most recent call last):

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 878, in <module>

main(sys.argv[1:])

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 821, in main

OPTIONS.info_dict = common.LoadInfoDict(input_zip)

File "/home/cm11/device/samsung/santos10wifi/releasetools/common.py", line 160, in LoadInfoDict

d["fstab"] = LoadRecoveryFSTab(zip, d["fstab_version"])

File "/home/cm11/device/samsung/santos10wifi/releasetools/common.py", line 232, in LoadRecoveryFSTab

raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))

ValueError: malformed recovery.fstab line: "/efs	ext4	/dev/block/mmcblk0p2"

make: *** [/home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip] Error 1

thanks for reading

m
[Galaxy Tab 3 General] gr8nole:
I think you need to update recovery.fstab to the newer version 2 format.
[Galaxy Tab 3 General] :
the correct layout for fstab v2

okay so,

this should be the correct format/layout for a recovery.fstab v2 though if i understand correctly system need to be listed first, and would someone please tell me how to do the scrolling text box thing so i could free up a little real estate in my posts?

---------------------------------------------------------------------------

#GT-P5210 santos10wifi Recovery,FSTAB cm11

/dev/block/mmcblk0p2 /efs ext4 defaults defaults

/dev/block/mmcblk0p10 /boot emmc defaults defaults

/dev/block/mmcblk0p11 /recovery emmc defaults defaults

/dev/block/mmcblk0p6 /cache ext4 defaults defaults

/dev/block/mmcblk0p8 /system ext4 defaults defaults

/dev/block/mmcblk0p9 /data ext4 defaults defaults

/dev/block/mmcblk0p13 /preload ext4 defaults defaults

/dev/null /sdcard datamedia defaults defaults

/dev/block/mmcblk1p1 /external_sd auto defaults defaults

--------------------------------------------------------------------------

okay so, resolving that now when i make otapackage -j4 i get:

using device-specific extensions in device/samsung/common

unable to load device-specific module; assuming none

Traceback (most recent call last):

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 878, in <module>

main(sys.argv[1:])

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 846, in main

WriteFullOTAPackage(input_zip, output_zip)

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 440, in WriteFullOTAPackage

Item.GetMetadata(input_zip)

File "device/samsung/santos10wifi/releasetools/santos10wifi_ota_from_target_files", line 181, in GetMetadata

name, uid, gid, mode = line.split()

ValueError: too many values to unpack

make: *** [/home/cm11/out/target/product/santos10wifi/cm_santos10wifi-ota-445fb7cfa1.zip] Error 1

please help me or.....or.....well. something.....:silly:

m
[Galaxy Tab 3 General] kindlefire39:
I would like to try developing. I've Linux from scratch like gentoo and arch. I know basic command lines but learn quick. I've been working with computers for years now. Sounds like fun!
[Galaxy Tab 3 General] :
python anyone?

T,

i need help with the python script santos10wifi_ota_from_target_files in releasetools

if you know python or of someone who does either way would help. go a few posts back

to see what's hanging me up. or just start building.

thanks,

m
[Galaxy Tab 3 General] Hazou:
Dunno any solution, it should work just fine. But from a few at your device tree it seems that u are ussing your own ota_from_target_files script. If u comment out that line (last line in boardconfig.mk) and see what happens, it doens't look like it is for 4.4. Never needed to have a custom one for my x86 device.
[Galaxy Tab 3 General] bithunter_99:
I'll hope, that we have soon an image to test.

i didn't know, how difficultly that is to create an Image.
[Galaxy Tab 3 General] :
CWM v6.0.5.0 GT-P5210

okay so,

got cwm to build through. see thread for details

http://xdaforums.com/galaxy-tab-3/development-10/clockworkmod-recovery-6-0-5-0-gt-p5210-t2830871

on rom- i boot to a black screen, i would like to know if this is fstab related.

i will rebuild bootimage anyway but the answer to the above question could be helpful to others.

m

okay so, otapackage built and using latest recovery [look up]

i am now being repeatedly punched in the **** by set-recursive-metadata errors [yay!]

my question is do i need to cull bad/nonexistent refs from manifest as well as updater script?

OR, can i use a straight push kind of script like mod57's updater script from grievous rom?

will tool around a bit more. if i can't get it i will post recovery log and updater script.

okay so it dies here;

ApplyParsedPerms: removexattr of /system/etc/install-cm-recovery.sh to 0 failed: Operation not supported on transport endpoint

script aborted: set_metadata_recursive: some changes failed

set_metadata_recursive: some changes failed

E:Error in /data/media/0/cm_santos10wifi-ota-b08846e210.zip

(Status 7)

Installation aborted.

attached log and script.

edit- running a new kernel build then recovery to see if i missed something with selinux

edit - rebuilt kernel and recovery with support for extended attributes, no result

has to be update binary [MENTION=4479363]Hazou[/MENTION] is there a way to build just that binary to test my changes?
[Galaxy Tab 3 General] Hazou:
After a bit of searching, it doesn't looks like the update-binary is the problem. people have reported almost the same error and it was resolved by using a recent CWM recovery. Another solution could be by commenting out the line itself. The rest still works, but only that line gives errors. The errors about data can be forgotten for now.

I dunno if a update binary can be made.
[Galaxy Tab 3 General] :
yikes!!!!

HA, so that's the thing, i just built the latest recovery. cwm v6.0.5.0 for gt-p5210. :confused:

so i am trying the following

Change the file in (cm11 source):

<cm11 source dir>/bootable/recovery/updater/install.c

in line 694 (under the function ParsePermArgs(int argc, char** args):

694:- parsed.has_capabilities = true;

694:+ parsed.has_capabilities = false;

on the good side i things i have this potential rom just sitting that I CAN'T FLASH !!!!!!!! :eek: .....sigh.

m
[Galaxy Tab 3 General] Hazou:
Already tried outlining the line? The file in question does nothing for this device at the moment.
[Galaxy Tab 3 General] :
yup,

comment didn't work, the reference is in updater script manifest.mf and cert.sf the resources are located correctly as best

as i can tell, but let me run this test, fail or no i will have the rom posted hopefully tomorrow as dev-host uploads

are really slow.

m
[Galaxy Tab 3 General] gr8nole:
Post your kernel defconfig.
[Galaxy Tab 3 General] :
this is my current defconfig

nsa selinux support

default security module = unix discretionary access controls

CONFIG_EXT4_FS=y

CONFIG_EXT4_FS_XATTR=y

CONFIG_EXT4_FS_POSIX_ACL=y

CONFIG_EXT4_FS_SECURITY=y

[MENTION=3034891]gr8nole[/MENTION] [MENTION=4479363]Hazou[/MENTION] - same kernel for recovery, boot
[Galaxy Tab 3 General] gr8nole:
Most of it looks okay to me. Try changing lines 3570 and 3771 of defconfig to this:

CONFIG_DEFAULT_SECURITY_SELINUX=y

CONFIG_DEFAULT_SECURITY="selinux"

Not sure if that will help or not, but that is how I did it when I implemented SELinux into my our kernel.
[Galaxy Tab 3 General] :
location of this setting?

CONFIG_DEFAULT_SECURITY="selinux"

in menuconfig search [/]

Symbol: DEFAULT_SECURITY[=selinux] │ Type : string -------- nvm found it
[Galaxy Tab 3 General] CAG-man:
[MENTION=5864662]moonbutt74[/MENTION] the scrolly text thingy you asked about on the previous page is the button with the # sign. Which inserts the [ CODE ] [ /CODE ] tags.

Also good stuff going on here. I took some time to catch up with the thread. Might have to re read it one more time.
[Galaxy Tab 3 General] :
Ah!

okay so

scrolly text thingy ... and i am going slightly mad....=)

:p
[Galaxy Tab 3 General] :
rebuilt recovery,ota stuff and logs

okay so, rom flash "addressed" by slight change to recovery mentioned in previous post, in conjunction with suggestion by gr8nole with regard to kernel configuration. boot.img "corrected" fstab.santos10wifi, problem with external sdcard detection persists, need correct fstab entry? or vold problem. rom does not progress to boot animation [stops at sanmsung logo] YET, adb shell is fully functional.

LIBVA is needed for camera. java issues abound [i need answers] logcat and build log attached.

Strap on your diapers folks, it's a hell of a read ! :D

will upload latest recovery. will also be uploading meta folder with update binary and updater script as it should prove helpful [maybe]

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

i have been working on this round for a square 24 hours, it's coffee time. :good: ......zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz*

m
[Galaxy Tab 3 General] gr8nole:
Just a quick glance at the logcat shows this:

"caused by library "libdrm.so" not found"

That missing file is causing some egl issues.
[Galaxy Tab 3 General] :
good deal

okay so, here's is the question, is libdrm.so tied to a device or will any kitkat incarnation do the trick?

i understand the build issue but, just as a temporary fix ?

One more question, with all issues being essentially a failure as to the build should i post rom or scrap it?

m