yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] :
on make bootimage

okay so,don't get excited,

in an attempt and on a thought/hunch about things concerning vold

i wanted to build just bootimage. i still having issue making correct entry in boardconfig,mk

for #TARGET_KERNEL_CONFIG, i want a full build of kernel, not prebuilt.

i encountered the error Restl3ss got libc_common.a (memchr.o): multiple definition of 'memchr'.

so [MENTION=5378432]Restl3ss[/MENTION] i was wondering if you solved that, and if that means you got rom build to run that far.

if so i have A LOT of questions, savvy? :p

m
[Galaxy Tab 3 General] Hazou:
For the framework patch, forget that one. It is only needed for the RAZR I. And maybe it isn't needed anymore.

The last error is resolved by removing the extra memchr entry from android.mk in the libc folder.

Hazou
[Galaxy Tab 3 General] :
hmmm

Hazou,

thank you. are you referring to bionic/libc ,the entry under the mips section? i've started anyway but it's good stuff for everyone to know.

a question in C, do uninitialized/ignored and unassigned functions lead to bugs?

thank you again for your help.

m
[Galaxy Tab 3 General] Hazou:
The entry under bionic/libc. And remove there the memchr.* under the x86 section in the Android.mk

Nope. They only lead to extra code and a larger lib. But sometimes they are used by other library from the past.

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

Hazou,

okay, i did it wrong...:eek:

that explains why my comp is trying to kill me now.....:eek: RENT UM UER LIBEN ! HERR HATNE PANZERFAUST!!!

:D

m
[Galaxy Tab 3 General] Hazou:
:D I hope you got it right this time :P

Something about the patches from my git. Only the cwm and twrp can be used without any problem. The framework is only for the RAZR I, the power top only work when pciutils source is included in the tree and the same goes with libva.

For other things have a look at the commits in the different Repo's. In the commits are the actual solutions for most of the x86 problems while building. But keep in mind that those are for cm10.1 April and not for 4.4 or higher

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

powertop patch is good, when i get through a complete build i wil reassert/verify, but it solved

the initial build error concerning powertop. as for my error, the build is actually still going....i'm nervous

and excited. and i've been doing a lot of git-hopping, it's a good thing i don't have a life. :victory:

m
[Galaxy Tab 3 General] :
hmmm

Hazou

Dude you ****in rock!!!!

ahem, i mean thank you sir for your invaluable assistance.

okay enough goofiness, i haven't tested yet so keep that in mind but,

Made boot image: /home/cm11/out/target/product/santos10wifi/boot.img

:highfive:

will report back

m

verdict=bootloop which is bad and good, i did make bootimage with prebuilt kernel/zimage android 4.2

so the boot loop i expected, the bad is logcat makes my eyes bleed!

i had to get the memchr issue solved and thanks to you that's done.

now the issue i have is with make bootimage using kernel source which is how i want to

do it. in regualr build of kernel i am square but, building through cm11 environment i encounter the

error No rule to make target `zImage'.

what i require is knowledge of the correct command to resolve that WITHIN cm11 build environment.

build outside of cm11 build environment defeats my purpose.

any meaningful help would be appreciated.

thank you for reading.

m

okay, back to the rom building, i am stuck here: external/skia/src/core/SkPaint.cpp:

the accompanying text shows the full errors

my understanding is skia manages 2d text rendering?
[Galaxy Tab 3 General] Restl3ss:
i wasnt able to resolve it myself but i'll try hazou's solution tonight
[Galaxy Tab 3 General] Restl3ss:
Hmm, there's a weird error i'm now getting that seems to have emerged out of nothing. Every time i run make (on a completely clean source with twrp / cm / framework patches and external/powertop from hazou) i'm now getting

at first i ran without the framework patch at the advice of hazou, tried applying and running make again since it's frameworks/base. no difference

host C++: validatekeymaps <= frameworks/base/tools/validatekeymaps/Main.cpp
cc1plus: error: unrecognized command line option "-arch"
cc1plus: error: unrecognized command line option "-Wno-nested-anon-types"
make: *** [/Volumes/android/out/host/darwin-x86/obj/EXECUTABLES/validatekeymaps_intermediates/Main.o] Error 1
[Galaxy Tab 3 General] Hazou:
For kernel building just add the following to the boardconfig and make sure the kernel source is in "kernel/(vendor)/(device)"

TARGET_KERNEL_CONFIG := (defconfig)

it should work.

Another thing, are u sure u use a zImage or in the Razr I case a bzImage. If i am correct all x86 kernels are bzImage. For the solution for that look in my android/build repo ifthe tab is using bzImage.

For the SKIA thingy, I fought this problem a couple of times. unfortunately I dunno how i solved it. It has something to do with the x86 implementation in SKIA if i am right... It calls for something it can't find in the x86 source. But will keep u posted if for some reason i come across the solution

edit: Have a look at those commits: add support for non-arm, Fix support for non-arm

Just forget the framework patch, isn't needed for your device. For the error. it look like u have those 2 parameters somewhere in your device tree. Maybe in the boardconfig.mk and it doesn't understand those commands.
[Galaxy Tab 3 General] :
on patches

Restl3ss,

so apply powertop /cwm&twrp , ffamework is not for us, and libva i don't know yet. so replace the framework files you patched with

originals, get em from git [get it? :silly:] the skpaint.cpp issue might take a bit. once you fix your current issue can you post your next log

go or no in a text file?

m

---------- Post added at 01:42 PM ---------- Previous post was at 01:30 PM ----------

hazou,

the bzimage is bzimage just renamed.

my boardconfig is square when using prebuilt.

when set to use source instead is where i get no rule to make target zimage.

that's the compiler, now what i'm not sure of is if i am suppose to add

export ARCH=x86 to the make bootimage command, or nav to kernel source within and export ARCH=X86 & make menuconfig first,

though the latter i think would be made old on a new run. with skia it would help to know what registers are and where they point to since c,cpp

seems to always be pointing to something/file external, which is driving me mad [mad i tell you!].

also may we can [borrow] steal from androidx86 project ?

now keep in mind i am searching on my own

but i always ask questions anyway, two heads being better than one.

thanks as always.

m
[Galaxy Tab 3 General] KingUsman:
Thanks for the fix, everything's seems to be working fine
[Galaxy Tab 3 General] kb8no:
[MENTION=6587211]nels83[/MENTION]

If you are nels83 you can call me mons49. :)

Used twrp 2.8.6.0.

Dirtyflashed latest 0503 ROM after wipe of cache and Dalvik

Everything came up perfectly, ROM runs smoothly, apps all seem to work, and long press now works

Hoping for Hangouts to work but no luck yet.
[Galaxy Tab 3 General] forrealgames145:
[MENTION=6587211]nels83[/MENTION]

Wow, thank you very much for porting CM12 to this device. I thought devs had already given up on it when i had checked on it's progress at the beginning of the year. A lot of talking between devs but no releases, haha. I, myself, own the p5210. It works very well and runs better than stock, in my opinion. it's nice to see that the device doesnt slow down because of too much RAM usage. I will report the following though:

-Screencasting doesn't work. It works in YouTube. Have not tested out Netflix or Hulu, etc. But the "Cast Screen" button on the notification does not detect my nexus player.

-When trying to get rid of lock screen shortcuts, the camera shortcut on the right side of the screen disappears, but the phone shortcut stays.

-I'm not sure if this is a problem for anyone else, but if you use the auto-brightness and you're indoors, sometimes it dims to the point where the screen doesnt seem like it works. Obviously, the fix for that would just be to turn off auto-brightness, so.. not really a top priority bug. but just wanted to report it.
[Galaxy Tab 3 General] Parley!:
flashed the new release (20150503). works great so far, except for camera-app which crashes on start. I tried to install google camera from playstore, but it has the same behaviour as the camera app which comes with the build ....
[Galaxy Tab 3 General] bbr999:
Multi-users works fine, except i can t rename user name. When i click on the user in parameters, pop up said contact does not exist or something like that.
[Galaxy Tab 3 General] MBAAC:
Hi,

you must edit the me contact in the contacts app. it is the first contact in the contact list.
[Galaxy Tab 3 General] japg2000:
Thank you very much!! It's really smooth :)

I've had little time to test, but for now i have just a question, is there a way to activate magnetic lock / unlock with this rom?
[Galaxy Tab 3 General] nels83:
Sorry, it seems I'm not nels83 :D (I just chose this name because nels was already taken)

I had a look and it seems to be caused by libcronet.so which is also available in youtube which does not have the problem. I hope next update will fix this problem.

I'm sorry I don't know how screencasting works. But you say it works but doesn't work, I don't really get it. You can screencast in youtube but your nexus player is not detected ? You cast to another device then ?

I noticed that on all CM roms I tested. In fact, at least in this one, the phone shortcut does not appear until you remove it using the settings :confused:

I'll fix it in the next upload. It just needs a min brightness setting.

Did you make a full wipe ? Can you send me a logcat ?

What is magnetic lock / unlock ? If it works with the magnetic sensors there should be no problem.

Thanks to everybody for the tests :good:

---------- Post added at 04:48 PM ---------- Previous post was at 04:38 PM ----------

Thanks to the work of [MENTION=5227588]Deltadroid[/MENTION], you can now flash a "proper" gapps package :)

I just replaced arm libs with x86 ones but no faceunlock for now... If someone has an intel version of libfacelock_jni.so maybe we can make it work.

For newcomers, just flash gapps-511-base-20150501-1-x86.zip (MD5)

For those of you who flashed my first playstore-only and/or contactssync package, you'll have to flash remove-nels83-gapps.zip (MD5)before to get rid of this old mess :D
[Galaxy Tab 3 General] LegendSmoker:
There are more ways to screenmirror.

You can mirror whole screen with everything what you do via Google chromecast APP

or you can stream Videos directly Form YouTube APP to chromcast dongle

or you can pull down notification bar and then screen mirror .

The 1st method doesn't work if you Start mirroring via chromcast APP my TV with chromcast gets black then there comes up an info wich tells that screen mirroring will get closed. It didn't work for me even on TW 4.4.2.

The 2nd method work . tested this after i read about this here.

The 3rd method doesn't work and i don't know nothing about this.

By the way your Rom is the best thing wich could happen to this tab.
[Galaxy Tab 3 General] pauh5306:
message error

I have an message error when i flah zip gapps-511-base-20150501-1-x86.zip, the .zip is not good.
[Galaxy Tab 3 General] nels83:
I did not signed the zip files. I will upload a new version.
[Galaxy Tab 3 General] patl_o:
The Zip works well for me.

The whole ROM is awsome! [emoji3]
[Galaxy Tab 3 General] blits01:
logcat camera
[Galaxy Tab 3 General] nels83:
I uploaded signed versions:

TWRP 2.8.6.0: P5200 (MD5) / P5210 (MD5)

gapps-511-base-20150501-1-x86.zip (MD5)

houdini-5.0-20150504.zip (MD5)

If you need to remove old gapps:

remove-nels83-gapps.zip (MD5)

Old posts now updated with new links.

---------- Post added at 08:21 PM ---------- Previous post was at 07:52 PM ----------

It seems you have a corrupted Email database and other problems. Can you try to Wipe to see if it works better ? (Don't forget to make a backup before, just in case)
[Galaxy Tab 3 General] Parley!:
Here's my logcats, now that I found out how to post them ;)

I hope they are of use to you, as I grabbed a logcat the first time...
[Galaxy Tab 3 General] nels83:
Thanks, just found the problem: a missing update in the vendor tree for P5200. Next upload should work.

[MENTION=6614161]blits01[/MENTION] Do you have a P5200 ? If so I think you have the same problem.
[Galaxy Tab 3 General] patl_o:
Do I have to flash Houdini again?

Is this a new version (because of the new date) or is it the same verion as before?
[Galaxy Tab 3 General] nels83:
Sorry I should have specified. It's the same version as before, just signed.
[Galaxy Tab 3 General] social-design-concepts:
In the spirit of opensource if you could show your support

In the spirit of opensource if you could show your support see : http://xdaforums.com/dell-venue/general/dell-venue-tablets-developer-edition-t3100367
[Galaxy Tab 3 General] japg2000:
Well, I have a case (i think it is magnetic) that automatically makes the lock/unlock when i close/open it. I dont know how its called (smart cover?) , but it works with stock rom. With the latest CM12 rom i cant get it working...

Thank you for your great work [emoji106]
[Galaxy Tab 3 General] KingUsman:
+1

Sent from my Nexus 5
[Galaxy Tab 3 General] nels83:
After calibrating the compass I installed Magnetic Lock from the Play Store and it seems to work. I only tested with a magnet because I don't have a smart cover...
[Galaxy Tab 3 General] blits01:
I tried wipe data, dalvik, cache. After wipe the Cyanogen camera disappeared from the menu. Google camera crash. My device 5200
[Galaxy Tab 3 General] nels83:
Dev thread created

I created the thread in the development forum. You will find the first Alpha of the ROM :)

I hope I did not forget anybody. Development of this ROM will continue there.

[MENTION=6614161]blits01[/MENTION] Can you try Alpha 1 ? It should fix the camera bug.
[Galaxy Tab 3 General] Parley!:
Just flashed Alpha1 built for P5200 from the aforementioned new thread and camera works now :)

thx nels83
[Galaxy Tab 3 General] blits01:
Camera on Alpha 1 working, but I found new bugs

-otg mouse works, but no cursor

-screencasting not working(my device chromecast)

-show touches in developer options not working

-when I change language, app settings crash

-WiFi Hotspot

-Dialer not working(do not call)
[Galaxy Tab 3 General] Restl3ss:
[MENTION=6587211]nels83[/MENTION]

Replaced the wrong e with a 3 ;) it's restl3ss
[Galaxy Tab 3 General] irfanjunaid:
Any help to port AOSP to Intel Z2520 clover trail plus x86 platform will be greatly appreciated! I am a loney dev trying to port AOSP to Asus Fonepad 7 FE170CG... Please help me guys!
[Galaxy Tab 3 General] ballerd:
Hey great thread thanks for making and I am all for the do it for yourself I completely agree It still amazes me how many people and cheeky to put lighty are like gimme, I want ,i was wondering if you could add me to the developers list please havent currently got any of my own developments but plan to have many soon I don't expect spoon feeding I have alot of free time so 95℅ I will be learning and hopefully developing for your team. sorry about the rant, my thanks and appreciation to All Concerned peace
[Galaxy Tab 3 General] Hazou:
1.

i totally forgot u are using the new 4.4 kernel from intel. There is a huge chance that, that one wont work. it doesn't have the right defconfig (the file that tells the builder what to make for your device) and most likely all the drivers that the tab needs. That's why there are so many different kernels laying around for android. Always use your stock kernel source. it should be somewhere on the internet because it must be opensource. If your stock works, than u can upgrade/move components from your stock to the new 4.4 kernel.

2.

For the bootloops. Always try to make a recovery first. A kernel wont boot an OS by it self without the right ramdisk (both make bootimage, but u already know that), while u have all the parts in cm11 to make a recovery. There are no extra's needed for building a recovery than having a device tree with some basic functions in it. (like: kernel make parameters, device parameters, partition tables) So always make a recovery first. if it boots u have the basics under control.

3.

About the SKIA problem. in this case it doesn't call for an outside file, nah sort of. Libc doesn't know the parameters because they are for ARM, that's why according to the commits we will use our own memcpy (libc x86 memcpy) parameters that should work. It is a bit fizzling around and get everything on the right track. I can make a patch for you for it, but it may take some time (or maybe not :P) and i can't test it.
[Galaxy Tab 3 General] :
[MENTION=4479363]Hazou[/MENTION],

whatever you whip-up i will test.

i have my baseball bat ready should my comp try to kill me again....:silly:

m

quick question in C : when i get <error> 50:12 for example, that message means

[this is screwy] from line 50: through to line 62, meaning a block of code from for example

50 #indef

to however many lines

62 #endif

is that right? understanding that better would be helpful.
[Galaxy Tab 3 General] Hazou:
As far as I understand it, it means that on line 50 at character 12 is the error.

Verstuurd van mijn GT-P5110
[Galaxy Tab 3 General] :
by the numbers

meaning 1st character/space in line 50 =1 or =0 ?
[Galaxy Tab 3 General] Hazou:
As example:

50: This is an example line tot say that the string "example" is at 50:12.

So the "e" of example begins after character 11.

Take 1 her or there. But that should be it

Verstuurd van mijn XT890
[Galaxy Tab 3 General] :
mount points - vold - fstab

hazou,

sorry to be pesty, where in build system do i address mount point, vold, fstab, device nodes etc. ?

m

also these messages

"ebtables is disabled on this build"

warning: [options] bootstrap class path not set in conjunction with -source 1.5

and for some reason still getting these

Trying dependencies-only mode on a non-existing device tree?

and

find: `src': No such file or directory
[Galaxy Tab 3 General] Hazou:
i dont mind to give some information ;)

It is quiet difficult to say in word how a device tree looks like and were to put all those files. The think i can recommend you is to look at official CyanogenMod device repository's. I myself have started with this one, Turl SMI Git. This one can build a fully working recovery for the Razr I. After that i used my other experiences with my old Wildfire and had a look at other device trees on how to set mine up. Mine is still a mess, but that will change in time.

the first 2, i don't know. they are new i think. Haven't had any experience with them. Will look at that when 4.4 is out for my device.

The last 2 are common. The 'src' one, i dunno. The dependencies is a file within the device tree what CyanogenMod uses to get extra sources for your device. How it works? look on the internet.

Edit:

Here u got the patch that u can try (for cm-11.0):

memcpy_76: fix behavior on non-ARM architecture.patch

I just copied over the patch from the author to cm-11. At this moment when this patch is patched, it will use the generic memcpy, eventually we will use the x86 variant of it if it is possible.
[Galaxy Tab 3 General] :
grrrrrrrr

okay so,

so i built through with no system apps and framework files, meaning the ones i actually need.

recovery cwm registers sdcard and goes through the motions of backup but writes nothing

edit recovery-recovery.fstab incorrect/inaccesible - backs up to /data/media

i know this has to do with vold llvm? going to take a diversion over to aosp to test out a theory and then

scream for a while.....and maybe run around in circles in the yard till i barf and/or pass out

m :crying:
[Galaxy Tab 3 General] Hazou:
Going to AOSP wont solve anything. Can u upload your device tree to github or in any other way. Then i can have a look. Building roms take patience, patience and even more patience to get it all set up. Sometimes the smallest typo lead to the biggest problems and it take ages to find it.

If u mean by 'vold' the vold.fstab, then yes. Maybe u miss configure it.

But in the mean time, i will just use my shovel to throw dirt in the circle shape in your garden. So u wont dig through to china.
[Galaxy Tab 3 General] :
will running in circles and barfing help.... =P

hazou,

link to the tree http://d-h.st/Pti , i know it's a mess i haven't posted an updated more proper [stock boot,recovery]

version yet as it takes HOURS :eek: . is llvm related to volume management?
[Galaxy Tab 3 General] Hazou:
llvm is an android compiler. The thing that translate code into binaries.

That device tree is hugh O.o

But on the other hand, why not use the device tree from angel? It looks fine.
[Galaxy Tab 3 General] :
hmmmm

on the tree, it's only a little bigger than angel_666's. on llvm, i did not know that, a lot has been answered

i have to go back through my build log. how big should a dev-tree be on average? i absent mindedly

included my personal setup for boot.img and recovery.img and i think vmlinux is in there too. with using

prebuilt kernel being deprecated since cm9 i can pull those out right?

m
[Galaxy Tab 3 General] Hazou:
Hmm nothing wrong I think. Its large because off all the prebuilt files. Let m have a couple of more time to look into it. See what u can get out of the logs, also u can use logcat to see what is happening at the backup in recovery

Verstuurd van mijn XT890
[Galaxy Tab 3 General] :
bootstrap error

the bootstrap classpath error if you get it is a java related warning/error.

i've read that like 90-something percent of the time it doesn't mean anything.

just the same, when i find out how to fix/address it, i will update this post specifically.
[Galaxy Tab 3 General] Restl3ss:
i figured out what was causing my error posted earlier. (this is a little far behind, i know haha) I recently installed the OS X 10.10 yosemite beta and apparently in the upgrade my gcc installation got f**ked, basically half installed. reinstalling via macports. OS X is starting to piss me off a bit actually. debating removing it and just going full linux, currently distro hunting.
[Galaxy Tab 3 General] :
hey hey

Restl3ss,

hey good luck on the switch, i'm still running into issues but, largely i think i have down to sorting out

java and llvm which i didn't know was a compiler till hazou told me.

i get recovery to build through but the fstab is giving me a hassle. backup does actually write but, to data/media

instead of data/media/0 but restore doesnt read either so ... screaming running in circles and barfing/passing out :silly:

swapping java version to openjdk from oracle-sun and trying again.

m:good:

on distro- debian compile my kernel [gcc4.7] no prob, so it's issues with cm/aosp

being UNRELENTINGLY ANAL ABOUT JAVA.....[guys, there's no call for that, sell your own souls,

not ours.]

[MENTION=4479363]Hazou[/MENTION] update- okay so i build through wit no apps in system and missing .jars in framework. help please?
[Galaxy Tab 3 General] :
No apk.s or framework.jars building

okay so this deserves a post,

i build through but when i check system.img /system/app is empty framework too, meaning none of the actual apps and framework files

needed to run android are present. this is a problem. i get the same with cm11 and aosp.

i am stumped and every search i make return with endless lists of asshat apk this and dumbass apk that.

grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr.... sigh......

for my sanity, for puppies and sunshine and gypsy jazz help me obiwan kenobi , you're my only hope.

i really need to sleep.

m:eek: