yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 10.1 Android Development] xTear:
I'm a trainee with a car and an own flat ;) i don't get much more mony than you but my VPS costs 15€/month (I'm from germany , i dont know the prices in ur country)

If i compile the kernel without any edits and flash it to my device it wont boot, and i got this log

E/IMGSRV ( 1912): :0: PVRDRMOpen: TP3, ret = -1
E/IMGSRV ( 1912): :0: OpenServices: drmOpen failed
E/IMGSRV ( 1912): :0: PVRSRVConnect: Unable to open connection.

any ideas? e_e
[Galaxy Tab 3 10.1 Android Development] Jacker31:
well, I am on my way home, so i might help you check out that error by night time. It cost about rm60+/per month so yea, you can buy 40 cans of cola with it.....
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
jijiji. I am currently unemployed. So figure!
[Galaxy Tab 3 10.1 Android Development] Jacker31:
same here in malaysia, 12-24 months of contact and beside the fastest speed i can get are 20 mbps which cost me about rm200+ per month (about 100-200 cans of coca cola) unless i can get an industrial uplink connection... got your self recoverded yet?
[Galaxy Tab 3 10.1 Android Development] xTear:
lol hard.

i pay in 3 Months for 32Mbit 20€/month in My Company we pay 40€ per Month for 100 Mbit oo

And my VPS costs me 15€ per Month, its an Contract with one year.

I Think its hard with the Price in ur Country, i'm really happy to live in germany o_O

And i Compile the kernel from Opensource.samsung.com and its for Android 4.4.2 :)

(i like kitkat ;) )
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
This is sad, well not really. The truth is if we had money we would not be here with a device that has around 2 years old.

[MENTION=5707708]Jacker31[/MENTION] a can of coca cola here is about $0.75 USD, I guess you guys have a good deal with coca cola. Now in the other hand my sister about 80 miles from me get 10gbitps ( I know they sell in bits to impress) for about 100 coca colas. Witch is 1.25GBps, they even give free IP TV Channels, that is nice. But she is to far from me to drive there. ups I see xTear is talking about Mbit, so that is wird, are you sure.

[MENTION=6109572]xTear[/MENTION]

LISTEN I found the Kernel-GT-P5210_EUR_KK_Opensource so I am re compiling to see what I get. For get the below instruction I will post what I am doing see the end of the thread

http://xdaforums.com/showpost.php?p=59593913&postcount=63

I do not have much experience with 4.2.2, I got so much troubles with selinux that I got tire an downgrade. I did compile a few times but most of it creating modules for KK4.2.2. I do not recall if I did in fact build and tested my own Kernel.

[MENTION=5864662]moonbutt74[/MENTION] Can you help us here?

xTear version matching, that could be one possible reason.

moonbutt74 post here is suggestion to create a compatible tool chain http://xdaforums.com/showpost.php?p=59395010&postcount=2

He suggested the following script for toolchain creation for KK 4.2.2. Please note that all this start from downloading androidndk

#!/bin/bash
/<$NDK-TOP>/build/tools/./make-standalone-toolchain.sh --ndk-dir=/<$NDK-TOP> --system=linux-x86 --toolchain=x86-4.8 --platform=android-19 --install-dir=/opt/toolchains/NDK-x86-4.8-KK

Then you need to recall to do the recommended settings. I lost my KK 4.2.2 files i guess I deleted. But in the 4.2.2 you are ask to do

HOW TO BUILD KERNEL
1. How to Build
- get Toolchain
From google aosp(http://source.android.com/source/downloading.html)
recommend : android-4.2.2_r1 release.
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
ex) CROSS_COMPILE ?= [COLOR="Red"]{your google aosp}/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/i686-linux-android-[/COLOR]
edit "ANDROID_TOOLCHAIN_FLAGS" to right option.
ex) ANDROID_TOOLCHAIN_FLAGS ?= -mno-android
- make
$ cd kernel_src
$ make ARCH=i386 {defconfig_file}
$ make ARCH=i386

* defconfig_file
- android_santos10_open_r00_user_defconfig : GT-P5200/P5210/P5213

2. Output files
- Kernel : arch/x86/boot/bzImage
- module : drivers/*/*.ko

I guess you need to adjust the RED part to point to your new toolchain /opt/toolchains/NDK-x86-4.8-KK

I guess something like this if you run his script

CROSS_COMPILE ?= /opt/toolchains/NDK-x86-4.8-KK/bin/i686-linux-android-

I do not recall having troubles compiling.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
no wonder i fall in love with cola, my foreign friends keep saying that cola are pretty cheap here.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
but we got unlimited bandwidth, i heard from my US friends said that broadband in US have limited bandwidth quota
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
I live in a US Territory in the Caribbean Sea called Puerto Rico. Internet cost has been dropping and a Higher Bandwidth with time. Cellphone Internet still have a quota. Even though my Island has mountains on the center making it difficult. The truth is that we are small 100 miles by 35 miles for About 4 million people. So that in fact helps distribution of Internet. Mainland US is one of the biggest territories in the world. They have big desert to huge cities. There are places in US that almost no body leaves to the big metropolitan areas where people literary leave on top of the others. So depending where the person you talk with leaves, it may influence the cost.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
same apply here, few miles away is like hundred miles away from the coverage
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=6109572]xTear[/MENTION]

So I found the Kernel-GT-P5210_EUR_KK_Opensource.

I open the README_Kernel.txt and reads:

################################################################################
HOW TO BUILD KERNEL FOR GT-P5210_EUR

1. How to Build :
i) Get Toolchain
From google aosp(http://source.android.com/source/downloading.html)
recommend : android-4.4.2 release.

ii) Edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
ex) CROSS_COMPILE ?= {your google aosp}/prebuilts/gcc/linux-x86/x86/[COLOR="Red"]i686-linux-android-4.6[/COLOR]/bin/i686-linux-android-
edit "ANDROID_TOOLCHAIN_FLAGS" to right option.
ex) ANDROID_TOOLCHAIN_FLAGS ?= -mno-android

$ cd kernel source
$ make ARCH=i386 android_santos10_open_r00_user_defconfig
$ make ARCH=i386

2. Output files
- Kernel : Kernel/arch/arm/boot/zImage
- module : Kernel/drivers/*/*.ko

3. How to Clean
$ make clean

4. How to make .tar binary for downloading into target.
- change current directory to Kernel/arch/arm/boot
- type following command
$ tar cvf GT-P5210_EUR.tar zImage
################################################################################

You see here is where I disagree with moonbutt74. The readme tell yo to use gcc 4.6. So using moonbutt74 script I modified to match 4.6 instead.

Assuming that my androidndk is at $HOME/bin ( That is where I place it or equivalent /home/<user>/bin) here is my change to moonbutt74

#!/bin/bash
$HOME/bin/androidndk/build/tools/./make-standalone-toolchain.sh --ndk-dir=$HOME/bin/androidndk --system=linux-x86 --toolchain=x86-4.6 --platform=android-19 --install-dir=/opt/toolchains/NDK-x86-4.6-KK

If we look at Makefile line 196 I changed to

ARCH	?=i386
#CROSS_COMPILE	?=/opt/toolchains/i686-linux-android-4.6/bin/i686-linux-android-
CROSS_COMPILE	?=/opt/toolchains/NDK-x86-4.6-KK/bin/i686-linux-android-
ANDROID_TOOLCHAIN_FLAGS ?=-mno-android

Then following instructions in readme

cd $HOME/bin/Kernel-GT-P5210_EUR_KK_Opensource ( match your kernel location)
make ARCH=i386 android_santos10_open_r00_user_defconfig
make ARCH=i386

In fact I have an 8 core Desktop so I did "make ARCH=i386 -j6" instead to speed up process. It dedicate 6 of my 8 cores to make.

Not a single error.

Now test that kernel with your boot image. As I said I use AIK to build the boot image. I do not have install KK so I can not test the produce kernel.

if for any reason you have trouble I did also setup gcc 4.6 in my Ububtu as default. By using

sudo apt-get install gcc-4.6 g++-4.6 gcc-4.6-multilib g++-4.6-multilib
sudo update-alternatives --remove-all gcc
sudo update-alternatives --remove-all g++
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.6 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.6 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++
sudo update-alternatives --config gcc
sudo update-alternatives --config g++
[Galaxy Tab 3 10.1 Android Development] xTear:
I've changed the toolchain, still the same issue..
[Galaxy Tab 3 10.1 Android Development] :
X,

hi when you run adb shell logcat use grep to jump to the fatal error which is preventing boot, meaning after flashing your test kernel,

connect tab via adb, run adb shell and issue

logcat -d | grep F/

see what process is failing, sigkill abort etc.

then run logcat again and grep the process or pid number, for example

logcat -d | grep 1234

or

logcat -d | grep surfaceflinger

the pvr error message is not/should not be an issue, angel666 confirmed that a while back, r2 is right to use gcc 4.7 or 4.6

the problem with gcc 4.8 isn't major but requires some correcting in the kernel source code, it's been a while since i've seen the errors or

worked with that source so i would need to see those errors if you use gcc 4.8 to remember and find the fixes. do not use gcc 4.9.

m
[Galaxy Tab 3 10.1 Android Development] Jacker31:
[MENTION=5688554]r2d23cpo[/MENTION] AHAHAHHAHAHAHHHAHAHHAHAHAHAHHA, after so many hours of waiting and thats what i got...
[Galaxy Tab 3 10.1 Android Development] xTear:
Could it be possible that i use a wrong method to replace the boot.img ?

First i got this errors

W/ResourceType( 2410): Failure getting entry for 0x7f0e0058 (t=13 e=88) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f0e005d (t=13 e=93) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f0e005d (t=13 e=93) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f0e005d (t=13 e=93) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f0e0055 (t=13 e=85) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f020349 (t=1 e=841) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f02034d (t=1 e=845) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f020349 (t=1 e=841) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f02034b (t=1 e=843) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f02034a (t=1 e=842) in package 0 (error -75)
W/ResourceType( 2410): Failure getting entry for 0x7f02034c (t=1 e=844) in package 0 (error -75)

if i use in recovery

adb push ~/Desktop/image-new.img /
/sbin/dd if=image-new.img of=/dev/block/mmcblk0p10 bs=1

Do i something wrong?
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=5864662]moonbutt74[/MENTION], nice to see you. Still arround. Thanks for helping. I know you do not have a TAB3 any longer.
[MENTION=5707708]Jacker31[/MENTION], I told you I got around 60 gig for 10.1! I bet you 12 will be bigger!

[MENTION=6109572]xTear[/MENTION]

if i use in recovery

adb push ~/Desktop/image-new.img /
/sbin/dd if=image-new.img of=/dev/block/mmcblk0p10 bs=1

Do i something wrong?[/QUOTE]

I never done it that way. But looks ok except "bs=1". I think "bs" blocksize 1 is weird. When I backup I use 4096. The smallest I seen is 512. I am not sure about that, but just skip it for a test.

Now from the name "image-new.img" I guess you are already using AIK. Look at moonbutt74 footer he advertise AIK. http://xdaforums.com/showthread.php?t=2073775.

So take the original stock boot.img.

copy it to AIK.

Do

./unpackimg.sh boot.img

From your Build Kernel get "arch/x86/boot/bzImage". And copy it to "AIK/split_img/boot.img-zImage". You know something like:

rm <AIK>/split_img/boot.img-zImage
cp <kernel>/arch/x86/boot/bzImage <AIK>/split_img/boot.img-zImage

then do

./repackimg.sh

Now the method I use to program is using an update.zip via sideloading. In fact I do not do the .repackimg.sh. This seems complicated bot it is not. By using a script.

Crete a file called pack.sh inside the AIK folder. Type the following inside.

#!/bin/sh
rm -f test_boot_00.zip;
rm -f test_boot_00$1.zip;
rm -f ramdisk-new.cpio*;
rm -f boot.img;
./repackimg.sh;
mv image-new.img boot.img
zip test_boot_00.zip -r META-INF boot.img;
mv test_boot_00.zip test_boot_00$1.zip

Now when you are ready to create your image just after copying your kernel then do

.pack.sh 1

Where 1 can be 2.3.4.5 etc.

The script will pack it for you.

Now clearly you need the META-INF folder. For that folder read => http://xdaforums.com/showpost.php?p=59332380&postcount=16

at the end is the file attached. Just unpack and copy the META-INF folder in AIK pluss the pack.sh

Now you go in to recovery I use TWRP. Select install zip with sideloading. And do

adb sideload test_boot_001.zip

If you are lazy you can even add this inside pack.sh. But I prefer that separately.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
lol, it used up about 23+gb of space and now i need to add in more space for it to use adding in another 30 gb of space...
[Galaxy Tab 3 10.1 Android Development] :
X,

hi, unpack a copy known working, existing boot.img for your android version

and replace the kernel AND the modules.

After building the kernel you must run

make modules

then you must locate and copy modules, the command escapes me at the moment but,

goto the thread in general that [MENTION=5378432]Restl3ss[/MENTION] started and search the thread for the term

strip modules
[MENTION=1434892]ketut[/MENTION]_kumajaya laid out the process solidly, i believe it's somewhere between page 16-19

bookmark,copy or script out the entire process to a script named go

so when you make changes/apply patches etc. then at the top of the kernel source you can run

.go

and get your build going. Note-write that script build into a seperate directory in your source or outside of it

to keep your source clean. I'll see if i can find my old laptop and try recover a scripting

example for you. ......COLA !!!!:silly:
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=5864662]moonbutt74[/MENTION] Nice. [MENTION=6109572]xTear[/MENTION] I totally forgot about modules! What a dummy I am. I know once I had that issue, it did not work until I changed or really replaced the modules.

Yes the problem of version verification. When insmod new kernel will not like Old modules. Then they may not load due to version mismatch!. That may be the reason why his pvr module is complaining. I feel stupid. I am not sure if this also apply to JB4.2.2 but definitely I bet you KK4.4.2 will do.

I never was in the talk about "term strip modules". Neither know the possible go script.

You see this is why I like the guy. I know he has tell me many time to stop, but moonbutt74 is the man. Thanks. Please keep those good advises coming. [MENTION=5378432]Restl3ss[/MENTION] [MENTION=1434892]ketut[/MENTION]_kumajaya [MENTION=1649190]Angel_666[/MENTION] and others I love you guys too, but moonbutt74 has time after time after time help me.

So mean while we find the "go script" you can use the following.

Open a new file call it "packkernel.sh" and paste the following code.

Now edit line 5 [kernel="$HOME/bin/Kernel-GT-P5210_EUR_KK_Opensource";]

with

your actual Kernel location

. Then you can execute ./packkernel.sh #, where # is a number. This create the update.zip.

#!/bin/sh
# r2d23cpo @ xda-developers
echo '';
#Adjust kernel Location to yours
kernel="$HOME/bin/Kernel-GT-P5210_EUR_KK_Opensource";
echo 'Kernel location at:';
echo $kernel;echo '';

#Adjust AIK Location to yours,$PWD set current script location
aik="$PWD";
modules=$aik/ramdisk/lib/modules;
echo 'Modules location at:';
echo $modules;echo '';

#Copying and moving and renaming bzImage
echo "Copying $kernel/arch/x86/boot/bzImage";
echo " to $aik/split_img/boot.img-zImage";echo '';
cp $kernel/arch/x86/boot/bzImage $aik/split_img/boot.img-zImage

#Copying and moving modules
echo "Copying modules to $modules";echo '';
for i in `find $kernel -name *.ko`
do
echo $i;
cp $i $modules
done

rm -f test_boot_00.zip;
rm -f test_boot_00$1.zip;
rm -f ramdisk-new.cpio*;
rm -f boot.img;
./repackimg.sh;
mv image-new.img boot.img
zip test_boot_00.zip -r META-INF boot.img;
mv test_boot_00.zip test_boot_00$1.zip;

echo "Next to program firmware do";
echo "adb sideload test_boot_00$1.zip";
[Galaxy Tab 3 10.1 Android Development] Jacker31:
OMG! haha, it this a p52xx developers reunion ? is like calling every available/popular developers of this device XD
[Galaxy Tab 3 10.1 Android Development] xTear:
You are my Hero.. My Devices boot now <3

Stupid Modules.. -_-
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=6109572]xTear[/MENTION]

I am happy you got it. In fact I am thank you for the report on KK 4.4.2. Now we know that is the problem.

[MENTION=5707708]Jacker31[/MENTION]

I like to thanks them all. What I know I ow it to them. They are my heroes.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
haha, I may not know about them, but i am sure they are good developers.
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
In fact thats the team responsible we have an alpha CM10.2. They works for more than a year to get there. To sad it still have issues.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
true, but we shall never give up right? else there will be no more development going on and it will lead this model into the death.
[Galaxy Tab 3 10.1 Android Development] xTear:
I love CM, i got it on my old SGS3 and on my M8, i flashed the Alpha build, and was possible to fix the wifi issue and to disable hw-overlay on boot (to disable the green rendering stripe). But i recognized that the device wont vibrate, if i call the vibrate function over the shell the device vibrates, i wont got any idea to fix this.

//EDIT:

Wouldn't it be better to start porting CM12? I've read something about that CM12/AOSP Lollipop would support x86 Devices. And i think android 5 is really nice.
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=3957009]Xtea[/MENTION] that is what Jacker31 is trying to do. At least until his ripo consumed all his drive space. jijiji
[MENTION=5707708]Jacker31[/MENTION] I know you are right I should not be that negative. But I seen so many waist their time.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
hahaha [MENTION=5688554]r2d23cpo[/MENTION] dont worry hehehehe i am getting my new HP laptop with 1tb storage sshd XD so i will spare 300gb for my kali *keep your evil idea off jijijijiji*, I will need your help with p5210 because i have a p5220
[MENTION=3957009]Xtea[/MENTION] yes i am trying to port cm 12 for our device
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
Interesting

So I am looking into kvm-qemu. KVM (Kernel-based Virtual Machine). And see its relation with XEN. The I recall seeing it.

In JB4.4.2 Kernel we have only

android_santos10_open_r00_user_defconfig

Now I new in JB4.4.2 Kernel we have more like engineering

android_santos10_open_r00_eng_defconfig

I just realize that JB4.2.2 also has also Virtual capable config!!!!

android_santos10_xen_open_r00_eng_defconfig

I wonder if that will helps!!!. If you see in the wiki kvm has support to emulate other general x86 devices see

h_p://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine#Emulated_hardware

like

Cirrus CLGD 5446 PCI VGA card, dummy VGA card with Bochs VESA extensions, or Virgil as a virtual 3D GPU.

I wonder if using XEN config and deactivating powervr driver we can make it go natively in Linux!!!
[Galaxy Tab 3 10.1 Android Development] Jacker31:
Em....Can you help me out with the local_manifests? I cant find additional repo for our device, I thought our device are "santos10" and i cant find it, I tried "p5210, p5220" and i just cannot locate it in the cyanogen git. *please dont ask me to look one by one from those thousand of folders in their git*
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
First do not feel bad for what I am going to say. It is not an insult.

You are funny or lost in space. I prefer funny. You then have no Idea what you are getting into. That is what you are saying I am going to try.

Now the Bad Part

Listen you will not find any OFFICIAL reference to our series "santos10". There is none.

You need to study how to Port Cianogenmod to a new device. That is whats makes it difficult.

In general if the sources for the drivers needed where opensource you could have a chance. But some of the drivers are none. In particular GPU Powervr. Now the last aproach is to use the binaries as provided in the hope you can make them work. Al that without any knowledge what is in them!!! Remeber in general they are suposed to be binaries there should not be in c code. Well the thruth is that there is code in the kernel. But figuring out what they do to a unknown hardware is not that easy neither.

Now the Good part. There are some people that had bit the Huge Bone that it is getting weaker.

Here is where I think all started with our Retired Dinasours Developers trevd and DutchDanny on September / 2013, well moonbutt74 is also of that era. jijiji

[Source][Manifest] CM-10.2 => http://xdaforums.com/showthread.php?t=2461756

The best you can do is read Restless/Angel_666 post on

[SIGNUP] [DEVELOPMENT] signup sheet for aosp build team => http://xdaforums.com/showthread.php?t=2792872

[Development][Source]CyanogenMod 11 for SGT-3 10.1 => http://xdaforums.com/showthread.php?t=2633554

Angel_666 Git=> https://github.com/Angel666/

Angel_666 Git on santos10 => https://github.com/Angel666/android_device_samsung_santos103g

ketut.kumajaya git => https://github.com/kumajaya

and many others

Now you have at least a few weeks of reading.

But to help you start looking at

[Development][Source]CyanogenMod 11 for SGT-3 10.1 => http://xdaforums.com/showthread.php?t=2633554

At the very top Angel_666 tels you how he did it.

And this may be useful is some hint Angel_666 gave to social-design-concepts on some graphics => http://xdaforums.com/showpost.php?p=58666012&postcount=453

OHHHH MYYYYY GODDDDD
[Galaxy Tab 3 10.1 Android Development] Jacker31:
I am actually laughing at my self, because i am lost out of the sudden. Then i found their (Angel) post and I am back on track. AND i am extremely agree with the cyanogen team "ridiculously easy or ridiculously difficult".
[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
Listen do not get me wrong, keep going. I am even curious about your findings. Do not forget to report good or bad. Does not matters we always learn. Who knows Angel_666 tree may be all you need. I have not try my self.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
Hopefully, this gotta be a long way....
[Galaxy Tab 3 10.1 Android Development] xTear:
Mah.. i want this stupid fastcharge on the Tab -.-

Does anybody know which devices use the same processor like the P52XX series?

I've searching for the kernel source code to know how to add this feature..
[Galaxy Tab 3 10.1 Android Development] Jacker31:
u can get the kernel source code from opensource samsung. Idk if this hack are related to the topic but check this out https://www.youtube.com/watch?v=EpXfGnqXM7I.

*mean while struggling with cm12 porting...*
[Galaxy Tab 3 10.1 Android Development] xTear:
I tried this, but i think its not working because the kernel do not compile /arch/arm directory into kernel.
[Galaxy Tab 3 10.1 Android Development] Jacker31:
Dude, we have a x86 device, not arm device. So we will have to compile it into x86 folder not arm folder. YOu will have to do the same method but to the x86 folder.
[Galaxy Tab 3 10.1 Android Development] xTear:
Yea i know, but in the yt link u post is for arm devices, and the structure with files etc is not the same in the x86 directory. so i gave it a try to do it in the arm directory but it wont work. If i'm at home i try it to find the same files in the x86 directory.