Dingoonity.org

Other Portable Consoles => JXD Devices => Topic started by: skelton on June 14, 2016, 04:35:18 pm

Title: MINI GUIDE - Compile s192 source
Post by: skelton on June 14, 2016, 04:35:18 pm
This is just a basic start to compile the JXD firmware as it is, a very vasic guide to begin with.

You need a x64 linux version, I personally use Ubuntu 14.04. You can virtualize it too with Virtaubox.
Once ubuntu is installed, download packages according to your ubuntu version. Ignore the java installation (we'll do it later)

https://source.android.com/source/initializing.html

You can obvious the java part, because we'l install java manually.. We?ll need Oracle Java 6 to compile  android 4..4. other Java versions like 1,7 or openjdk can give you use issues.

To download Java run terminal and run the following commands:

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update && sudo apt-get install oracle-java6-installer

With this we are ready to begin:

Download the source and untar it whenever you want.

https://mega.nz/#F!Utg3xR5B!1phxtRLppKCB4Kb18CsyMQ

Before starting we need to modify a couple of mk files that are wrong in the source.

Go to  packages/apps/Gamemap and edit the file android,mk, like this:


Code: [Select]
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := GameMap
LOCAL_MODULE_CLASS := APPS
LOCAL_MODULE_TAGS := optional

LOCAL_SRC_FILES := $(LOCAL_MODULE).apk
LOCAL_PACKAGE_NAME := GameMap
LOCAL_OVERRIDES_PACKAGES := Game
LOCAL_CERTIFICATE := platform
LOCAL_PREBUILT_JNI_LIBS := $(LOCAL_MODULE)/libhello-jni.so
include $(BUILD_PREBUILT)

# Use the following include to make our test apk.
include $(call all-makefiles-under,$(LOCAL_PATH))


Now we do the same with packages/apps/keyMaster. We edit android,mk file so it keeps this way:


Code: [Select]
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := KeyMaster
LOCAL_MODULE_CLASS := APPS
LOCAL_MODULE_TAGS := optional
LOCAL_CERTIFICATE := platform
     
LOCAL_SRC_FILES := $(LOCAL_MODULE).apk
LOCAL_PACKAGE_NAME := KeyMaster

include $(BUILD_PREBUILT)
# Use the following include to make our test apk.
include $(call all-makefiles-under,$(LOCAL_PATH))]

Yoy are ready to start. Go to yout folder where untar the source and run setup_ardbeg.sh from terminal with ./setup_ardbeg_sh

Be patiente because compiling can take hours , depending on your machine
Once finished, take files from  out/target/product/ardbeg (ignoing the folders)

You'll need to flash with nvflash and APX drivers like the firmware JXD released here:

https://mega.nz/#F!Ewp2FQgD!_4ThgwYYR8oiwwl0mbsH6w

Download file called 00 firmware and tools,unrar ir under widnows and you can replace tour compiled files with the ones oncluded in the original firmware to flash.Inside the JXD there are drivers and instructions to flash it

In next post I will explain how to compile stand alone kernel.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 14, 2016, 04:36:14 pm
HOW TO COMPILE stand alone KERNEL binary:

first of all, tegra devices doesn't allow kernel in tree compilation, that means we need to compile whole SDK, unless we do the following.

STEP 1: copy your kernel folder from the source to another directory, because we need to make a change a compile kernel only that won't alllow us to compile whole SDK later.

STEP 2: download this file and copy it to arch/arm/boot/dts (to the folder where you copied kernel)

https://mega.nz/#!U5gw1DqK!UNONoBdfahGtmIwMxdDiv-LW1VwYGDzPlzPjGKFSr-E

STEP 3: We need to edit the following file located at  drivers/staging/ozwpan/ozeventtrace.h

The end of the fle should be that way:

#define TRACE_INCLUDE_PATH ../../drivers/staging/ozwpan/
#undef TRACE_INCLUDE_FILE
#define TRACE_INCLUDE_FILE ozeventtrace
#include <trace/define_trace.h>

With that we are reasy compile kernel binary. Nvidia uses arm eabi 4.7. It's located in prebuilts/gcc folders of your whole SDK source. I personally a folder called Toolchains with all the toolchains I use. So if you have your toolchain in other location, just change my example with your path to your toolchain:

Now we open terminal, we go to our new kernel directory and run followin command.

1-  make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- clean     (this step is optional to clean previous buils if there are any)

2-  make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- tegra12_android_defconfig

3- make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- tegra124-tn8-e1780-1100-a03-battery.dtb

4- make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- -j5

After it compiles we'll see out zImage binary kernel under arch(arm/boot

If we add new modules to the kernel we can run the following commands:  make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- INSTALL_MOD_PATH=build_modules modules
and then

 make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- INSTALL_MOD_PATH=build_modules modules_install


we will get our new modules under build_modules directory





Have in mind this is only a binary kernwl without a ramdisk, so we need to include it inside our boot.img. You can get boot.img from your already compiled source, or just take from the firmware JXD provides.

We can use a tool like Android Image Kitchen to umpack and repack a boot,img, we just need to replace our new zImage for the one included in boot,img. We can also can make changes to the ramdisk if we want to. there are many image kitchen tools to do that, like this one:
http://forum.xda-developers.com/showthread.php?t=2073775

And that's all. Happy compiling.



Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 14, 2016, 04:36:24 pm
Include superSU guide:

This is what I do when I compile AOSP to include supersu and binaries. I do it in my GPD too, so hope that works:

Extract this to packages/aliasapps


https://mega.nz/#!tgRHzTqJ!O06r2OEXcdd4dMF5_d9JMIJRhz7CgSW089GoINTHL_g

You will see user_apk.mk file and a root file. Everything is set up, nothing to chamge in there. I included busybox locally because nvidia sources comes without busybox.

Obviously we need to call our new user_apk.mk file so, we edit the file device.mk located in device/nvidia/ardbeg

You can place after this line so it keeps like this:
include packages/aliasapps/user_apk.mk

You can use that line after the following line:
include packages/aliasapps/alias_apps.mk

Now, open the file called init_no_root_device.rc located in device/nvidia/ardbeg
 Look for the service console so that it remains that way :

service console /system/bin/sh
    class core
    console
    disabled
    user root
    group log

Also look for the service flash recovery so that it keeps that way:
service flash_recovery /system/etc/install-recovery.sh
    class main
    oneshot

Basically I remove the # though I think it is removed after compiling anyway.

With that just recompile and in theory you should have root and superSU in your system (It compiles well, but I cannot test). It could also to ask you to update binaries. If it does, select normal option in SuperSU app. If this does not work , we need a different approach I am afraid



Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 15, 2016, 05:57:06 am
The two code changes fixed my compiling errors.  Didn't have much time to spend with it tonight though.  Made the changes and recompiled.  Came back 20 minutes later and everything was done.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 15, 2016, 01:40:59 pm
Glad you got it working. I uodated second post for kernel only.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 16, 2016, 01:51:01 am
Glad you got it working. I uodated second post for kernel only.

Thank you for the guide.  I'll try it tomorrow.  Had too busy a day today to do anything with the ROM.  Since I have Android built, I am going to go after the kernel next, so this is perfect timing.  Then, I am going to start building a ROM, adding in all JXD changes, and seeing if I can spoof the Shield even more.
Title: Re: MINI GUIDE - Compile s192 source
Post by: leafar on June 16, 2016, 02:00:09 am
hoping you peoples do a good job,for the benefic of this device,can be done something like the shield tablet a monster,skelton knows that in XDA are a lot a resources,i use to owned the shield tablet. there is a spanior person called Bitob he doing a tremenduos job with the shield,if the 192 get better a will buy
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 17, 2016, 03:42:19 pm
Glad you got it working. I uodated second post for kernel only.

Thank you for the guide.  I'll try it tomorrow.  Had too busy a day today to do anything with the ROM.  Since I have Android built, I am going to go after the kernel next, so this is perfect timing.  Then, I am going to start building a ROM, adding in all JXD changes, and seeing if I can spoof the Shield even more.

There are the config. mk files for the shield tablet in the source. So editing board config..mk should do the trick to spoof it even more from source.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 18, 2016, 01:46:59 am
There are the config. mk files for the shield tablet in the source. So editing board config..mk should do the trick to spoof it even more from source.

I noticed all the shield stuff in there.  I want to try spoofing the android version in the file too, to see if that helps the Play Store allow the games we want.  I've asked for a weekend of nothing for Father's Day, so I should have time to get it all done. as long as it really happens.  Although, I picked up a new Tacoma Limited last weekend, so I may want to hit the road for a bit. ;-)
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 19, 2016, 05:35:32 am
4- make ARCH=arm CROSS_COMPILE=~/toolchain/arm-eabi-4.7/bin/arm-eabi- j5

Mine is compiling now.  I think you may have a typo though.  Do you mean -j5 at the end?

Also, doesn't the Shield Tablet use tegra_ardbeg_mods_defconfig?  Would using that one make any difference?
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 19, 2016, 10:23:25 am
-j5 is the number of jobs. No idea what is the config used in the shield, but shield will have different drivers so it doesn't make sense  to use that config. If you want to add modules or something to your config you can just run menuconfig after loading config.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 19, 2016, 05:30:34 pm
-j5 is the number of jobs.
I know that. :-)  You don't have the dash in front of it in your instructions.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 19, 2016, 05:50:30 pm
-j5 is the number of jobs.
I know that. :-)  You don't have the dash in front of it in your instructions.

Oops, you are right. I edited,
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 20, 2016, 02:02:56 am
FYI - Everything is compiled and built.  I am going to put together an update and see if it will install. 
Title: Re: MINI GUIDE - Compile s192 source
Post by: Elronza Williams Jr. on June 20, 2016, 03:37:29 am
Skelton and LordDavon awesome work brothers!😂 Thank you both for your hard work improving the quality and performance of the Jxd S192.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 20, 2016, 05:08:09 am
Skelton and LordDavon awesome work brothers!😂 Thank you both for your hard work improving the quality and performance of the Jxd S192.

It was much easier with skelton's help.  He really gets most of the credit for getting me this far, this quickly.  Luckily, compiling all this is not much different than compiling andLinux, or any of my other projects, and his instructions have been very straight-forward.  I am going to duplicate the build environment on MacOS, so I can take it with me when I am sitting at the doctor's office, or at the in-laws.  Right now I am using VirtualBox, and RDPing into it directly with the Mac anyway.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 20, 2016, 06:29:53 pm
@skelton My system.img is 555MB, and the one in their firmware is 600MB.  Shouldn't we be compiling the same sized?
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 20, 2016, 06:31:54 pm
When i compiled it was also about 550. I suppose they included some additional apps or something in their first firmware.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 20, 2016, 10:13:03 pm
When i compiled it was also about 550. I suppose they included some additional apps or something in their first firmware.

Is there something better I should name the controller?  In gpio_keys.c, it defines it as jxd_key.  I'd like to change it to something a little more common.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 20, 2016, 10:15:51 pm
You can try something like playstation 3, like un gpd firmware, or try to what shield controller is called (i don't know thw exact name for shield controller). But probable it implies to rename the file jxd_key.kl in system/usr/keylayout
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 21, 2016, 01:05:36 am
Installed the firmware.  Everything is working well.  Shield Hub is working with the auto-generated build.prop.  Need to remove the development packages that installed, and root the system.  Kingsroot doesn't work because it thinks it is a Shield Tablet.  Going to see if I can get the store seeing the unit as a Shield Tablet also, since those apps still won't install. 
Title: Re: MINI GUIDE - Compile s192 source
Post by: Elronza Williams Jr. on June 22, 2016, 03:53:21 am
Sweet this update sounds like it will take care of all the issues I have with the S192. One question can either of you fine gentlemen get Jxd to confirm if the S192 has a fan for cooling as this would give a good idea as to overclocking potential?
Title: Re: MINI GUIDE - Compile s192 source
Post by: ClawShrimp on June 22, 2016, 05:34:36 am
In the videos JXD posted to YouTube about part replacement I didn't spot a fan.

Loving your work, LordDavon. Once my unit arrives I'll probably just keep it boxed until your rom is ready.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 22, 2016, 02:20:45 pm
Included a guide in third post to include supersu and binaries from source. No idea if this ill work though, I cannot test it myself.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 04:28:28 pm
Included a guide in third post to include supersu and binaries from source. No idea if this ill work though, I cannot test it myself.

I've actually put all the binaries for busybox, su, SuperSU.apk in my ROM, but setting the permissions has been the issue.  I will try your approach and see if that works for me.

UPDATE: Okay, compiling now (this will take a couple hours).  If this doesn't work, I have another su system that I can use, and know how to set the permissions now. :-)
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 08:31:31 pm
@skelton - The root didn't work.  I am going to make sure I set everything up correctly for the scripts.  The binaries are there.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 22, 2016, 08:34:31 pm
Mmm. Strange, is the same i do in the gpds... when you open supersu shows some message or something? Maybe you can try with superuser from kousa. It's the one included in most cyanohen, etc...
https://github.com/koush/Superuser
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 08:48:45 pm
Mmm. Strange, is the same i do in the gpds... when you open supersu shows some message or something? Maybe you can try with superuser from kousa. It's the one included in most cyanohen, etc...
https://github.com/koush/Superuser

I have another one I want to try first.  It may work, I hope. :-)  I also need to add ShieldHub to the image.  So, those are my projects for the day. :-)
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 22, 2016, 09:05:48 pm
I thought shield hub was included in the source. So does supersu appear installed when you compiled it? Does it show something when you open it? I think editing boot.img setting permissions or loading daemon su from ramdisk could be better than from install-eclvery.sh scripts. I can try uploading a boot.img tomorrow
Title: Re: MINI GUIDE - Compile s192 source
Post by: anthonws on June 22, 2016, 10:12:36 pm
Hi skelton and LordDavon,

Would it be possible to share some pointers on how you where able to run Shield HUB with your custom firmware?

Steel01 (at XDA), has been trying to check how to run Shield HUB in the original Shield Portable using CM13, but it seems that not even the first level API are loading.

http://forum.xda-developers.com/nvidia-shield/development/rom-cyanogenmod-12-shield-portable-t3042192/page34 (post 334 has the most juicy info).

Thanks for your attention!

Cheers,
anthonws.

p.s. Congrats on your great efforts with this cool handled!
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 10:27:20 pm
I thought shield hub was included in the source. So does supersu appear installed when you compiled it? Does it show something when you open it? I think editing boot.img setting permissions or loading daemon su from ramdisk could be better than from install-eclvery.sh scripts. I can try uploading a boot.img tomorrow

Yes, SuperSU is there, as well as the binaries.  I ran a terminal on the system and tried running su, and it gives the error that use 10080 unable to use it.  So, it has the same issue as the one from the sources.  I think the permissions aren't being set (4755, I think) on the binaries.  I can change add them to the recovery script, and see if that makes it work.

Shield Hub is from Nvidia, and the one that JXD included in their patch was very old.  I am including the latest.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 10:35:52 pm
Hi skelton and LordDavon,

Would it be possible to share some pointers on how you where able to run Shield HUB with your custom firmware?

Steel01 (at XDA), has been trying to check how to run Shield HUB in the original Shield Portable using CM13, but it seems that not even the first level API are loading.

http://forum.xda-developers.com/nvidia-shield/development/rom-cyanogenmod-12-shield-portable-t3042192/page34 (post 334 has the most juicy info).

Thanks for your attention!

Cheers,
anthonws.

p.s. Congrats on your great efforts with this cool handled!
I actually outlined them as I did them.  Pages 63 to about 67 of the JXD S192 thread.  When I get the ROM out, I should have time to do a step-by-step.

Sent from my Pixel C using Tapatalk

Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 22, 2016, 10:37:55 pm
Hi skelton and LordDavon,

Would it be possible to share some pointers on how you where able to run Shield HUB with your custom firmware?

Steel01 (at XDA), has been trying to check how to run Shield HUB in the original Shield Portable using CM13, but it seems that not even the first level API are loading.

http://forum.xda-developers.com/nvidia-shield/development/rom-cyanogenmod-12-shield-portable-t3042192/page34 (post 334 has the most juicy info).

Thanks for your attention!

Cheers,
anthonws.

p.s. Congrats on your great efforts with this cool handled!
i am not making any firmware for this jxd, just made the guide.

Lordavon, su permissions are 6755 and install-rwcovery.sh should be 0755. But install-recovery is called in init.rc. shouldn't be needed to set permissions manually. I don't understamf why it doesn't work though. I will try to edit ramdisk inside boot.kmg tomorrow to see if i can find another approach. I don't promise anyrhing though, i am spending too much time on a device that i will never own, lol.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 22, 2016, 10:47:47 pm
Lordavon, su permissions are 6755 and install-rwcovery.sh should be 0755. But install-recovery is called in init.rc. shouldn't be needed to set permissions manually. I don't understamf why it doesn't work though. I will try to edit ramdisk inside boot.kmg tomorrow to see if i can find another approach. I don't promise anyrhing though, i am spending too much time on a device that i will never own, lol.

I don't know what su's permissions are, but they aren't working.  What I am suggesting is setting the permission for the files in install-recovery.sh, just to make sure they are set correctly.  If it doesn't work, I will try a simpler package.

UPDATE: I looked into the permissions and they are fine.  I am going to pull out some of my other changes from the image and see if doing just the su additions work.

UPDATE2: I've gone over the changes over-and-over, and they are all correct.  I'm giving a try to moving the user_apk.mk entry below the third_part_apps.mk line, just in case that matters.  I doubt it.  I suspect the daemon isn't getting run, but not sure why.  Once I do the install, I will install a terminal emulator and run ps to see if it is listed.  After that, I am going to have to try a different package.  @skelton, I will email you a link to another package we can consider.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 23, 2016, 09:53:50 am
I think the problem is that for some reason system is not running the install-recovery.sh even though it should, so the daemon su is not running. It think the best approach is running daemon su from kernel ramdisk, or we'll need to make a custom recovery and just flash a supersu file.

LordDavon try flashing with this boot.img (rename to boot.img), to see if root it's working. If not I am out of ideas. Maybe bootloader is locked and we'll need a custom recovery,

https://mega.nz/#!lpBn3ZLQ!ygPWadggCT8rMPq6h8Zy0uNyUFoCZ-FIelxh3nc_1_U

Here is it is a repacked CWM recovery taken from Shield tablet mixed with JXd binaries. (rename it to recovery,img)

https://mega.nz/#!cpxBhD4J!E4etojQU0UW-wfWM6PycPVSmGL1-kFPzSUbgdejAWQU

To install it you probably need fastboot and unclock the bootloader following this:

http://forum.xda-developers.com/showthread.php?t=2399737

If bootloader can be unlocked then run follwing commands:

fastboot flash recovery recovery.img

fastboot boot recovery.img

And the device should reboot to CWM (if it works.....)

I am out of ideas, because I don't understand why it's no working. If CWM works, just flashing a SuperSU zip file should enough. https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip


Another choice is try to sign an update,zip, but not sure if JXD just use the standard test keys to sign a zip or a diferent one.



Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 23, 2016, 02:18:38 pm
I think the problem is that for some reason system is not running the install-recovery.sh even though it should, so the daemon su is not running. It think the best approach is running daemon su from kernel ramdisk, or we'll need to make a custom recovery and just flash a supersu file.

LordDavon try flashing with this boot.img (rename to boot.img), to see if root it's working. If not I am out of ideas. Maybe bootloader is locked and we'll need a custom recovery,
I agree.  I put a command to write a semaphore file in the install-recovery script, and it wasn't created.  So, it is not being run.  When I used your boot.img, it didn't make any difference.

I have an app that you can run, and it will root the device.  I may just include the app, so people who want root can have it, and anyone not wanting root can just not run it.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 23, 2016, 02:57:16 pm
Yep. That's also a choice
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 24, 2016, 04:19:11 am
I've emailed JXD about the recovery script.  Hopefully, they will give me a way to run the daemon on startup.  Until then, I am going to include the rooting application.  I am also including spoofer app, which allows you to spoof the device as a different device, without it changing the build.prop.  It does contact the Google servers to change it on their side, so I am hoping that it will give a little more flexibility for the device.

My issue right now is Shield Hub.  It needs to be installed, because it adds so much to the system.  If I use JXD's update version, then we are a bit behind in versions.  I am trying to include the latest Shield Hub package, and create an icon on the desktop that will install it.  This way it is nice and tidy.

Once these changes are in place, I will release the first beta of the image.  After that, I'd like to cleanup the install process (there are just too many files there), change the bookmarks to be things that S192 users will need, add a few more apps, and install a 3rd party store that will update Shield Hub as the new versions come out.

I hope to have the beta out any day now.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 24, 2016, 10:56:10 am
In theory my boot.img should load dameon su at init.. No idea why it doesn't, perhaps there is something I miss, or tegra devices are more tricky than I expected. In my shield tablet I had to use TWRP to make a proper root in Marshmallow.

I'll get a shield TV today, and perhaps will try to compile a kernel etc, so I think I have entertainment for some time XD
Title: Re: MINI GUIDE - Compile s192 source
Post by: bagmouse7 on June 24, 2016, 04:02:37 pm
This is getting VERY interesting!

Looking forward to testing your release.
Thanks!
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 24, 2016, 04:08:05 pm
This thing is getting aggravating.  The VM started locking up on me 2 days ago (after a Windows Update too).  Now, my changes aren't compiling in, even though they are all there.  I may just re-extract the sources, copy over my changes, and try a fresh compile.

UPDATE: Extracted the sources again and plugged in all my changes.  Everything is compiling again, except for my Shield Hub installer.  Getting close.  It is the final piece. ;-)

Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 25, 2016, 04:30:32 am
@skelton - Are you getting this error when you compile?  Maybe this has something to do with the issue...

Code: [Select]
Modifying ramdisk contents...
cp: cannot stat ‘out/target/product/ardbeg/root/init.recovery.*.rc’: No such file or directory
make-3.8: [out/target/product/ardbeg/recovery.img] Error 1 (ignored)
----- Made recovery image: out/target/product/ardbeg/recovery.img --------
Construct recovery from boot
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 25, 2016, 09:27:24 am
Nope, in fact recovery.img is compiled too.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 25, 2016, 06:28:18 pm
Nope, in fact recovery.img is compiled too.

I've been talking with JXD and they don't understand why it isn't working.  Hopefully we will get it figured out with their help.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 25, 2016, 06:40:25 pm
I asked them a root firmware but didn't get an answer. So no idea, I think they prefer I work in their RK model. I personally won?t get invloved too much. If JXD wants me in, they have it easy, sending a sample of a tegra k1 and I can try more things, but developing "on blind",,,mmmm no.
Title: Re: MINI GUIDE - Compile s192 source
Post by: suikoden82 on June 26, 2016, 08:03:14 am

I'll get a shield TV today, and perhaps will try to compile a kernel etc, so I think I have entertainment for some time XD
We want  to know your gamecube experience with this awesome device, even better with a video in your you tube channel :) I heard nvdia shield tv comes with a software able to record gameplay easily.
Title: Re: MINI GUIDE - Compile s192 source
Post by: leafar on June 26, 2016, 07:27:24 pm


I'll get a shield TV today, and perhaps will try to compile a kernel etc, so I think I have entertainment for some time XD
[/quote].

i wish you all the good luck  Skelton,its has been a year and nobody , even in XDA developer has built a kernel yet,dont get frustate and i wish you get it done.
so far the shield tv have an android room from Zullu99 in videomap.it. and steel its trying to get work in Cyanogenmod 13.0 no luck.
the shield tv so far its the best hardware for android in the market and i am even playing PC games and steam in my LiquidSky app cloud server gaming with the shield controll, pretty good, check liquidsky app.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 26, 2016, 07:40:27 pm
I personally prefer to use Android TV in the shield TV rather than cyanogen or a full android. I have seen kernels in XDA though,
http://forum.xda-developers.com/showpost.php?p=65682781&postcount=202

So I don't think I need to build another one, mainly because I don't want cyanogen in this device. I didn't even root it yet XD. The nvidia controller has been a big dissapointment though, I expected more. Luckily I can use other controllers with it.
Device is good though, but it would need more exclusive games that take advantage of his GPU.
I know about LiquidSKy, but even with geforce now in the shield I have never been interested in gamestreaming to be honest.
Title: Re: MINI GUIDE - Compile s192 source
Post by: leafar on June 26, 2016, 10:10:53 pm
nothing official yet,but for i want i want both worlds android and android tv,we know the shield tv is a close platform i think dictate from google android tv, thats what its,but so far it seen is like is frustrate for no having touch capabilities or not full google store,its something that we have get use it.
i do have my shield tv root,stock room,using omniswitch app running for quick acces application and droidmote app to use my smartphone as air mouse remote controll, pretty nice.
i am not a hard gamer,i used to have a xbox360 ,no more, i do like to play the fifa franchise,MassEffect,Rocket League, to mention. and do play those trough LiquidSky from Origin and Steam.
dont need any more those chinese android box, i am pretty happy with my shield tv,and i am waiting just for PGS lab to buy the device.but i want too the s192 for two reason tegra k1 and built in controllers.
take care yourself
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 27, 2016, 05:01:16 am
I was just notified by JXD that the battery fix is NOT included in the sources.  ARG!  I've asked them for the fix.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 27, 2016, 11:00:22 am
Probably is a kernel change. Jxd is sending me a s192, but unfortunately with rk3288 model. So my guess is that they won't Support s192 k1 much longer.
Title: Re: MINI GUIDE - Compile s192 source
Post by: danny.69 on June 27, 2016, 03:33:20 pm
You may be implemented ntfs support?
Here a link on how to do: https://getmovil.com/aplicaciones/ntfs-patch-android/
this in Spanish, but you can translate
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 27, 2016, 03:46:38 pm
If the kernel Support ntfs you just need to include ntfs in the kernel config.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 27, 2016, 04:33:03 pm
Probably is a kernel change. Jxd is sending me a s192, but unfortunately with rk3288 model. So my guess is that they won't Support s192 k1 much longer.

They told me that after the 3288, they plan on going with the 3388.  Probably in V2 though.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 27, 2016, 04:46:01 pm
Probably is a kernel change. Jxd is sending me a s192, but unfortunately with rk3288 model. So my guess is that they won't Support s192 k1 much longer.

They told me that after the 3288, they plan on going with the 3388.  Probably in V2 though.

Probably, it makes more sense.
Title: Re: MINI GUIDE - Compile s192 source
Post by: adamantibus on June 27, 2016, 05:29:58 pm
Really? Are they going to release a new model every month?  ::)
Title: Re: MINI GUIDE - Compile s192 source
Post by: siliconmessiah on June 27, 2016, 05:32:48 pm
Wow...the more I hear about this new chip-debacle, makes me so happy of having a powerful JXD s192 with a K1 beside me. Very interesting where this will take everything...
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 27, 2016, 06:02:32 pm
Really? Are they going to release a new model every month?  ::)

I don't think they release anything with rk3399 before december at least. Rk3399 won't start massive manufacturing until october, and first chips will be for tvboxes.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 27, 2016, 06:18:53 pm
Really? Are they going to release a new model every month?  ::)

This will most likely be next year, or the end of this year.  The RK3388 hasn't been released yet.  Once it is, it will take a bit to get the boards made, firmware done, etc.
Title: Re: MINI GUIDE - Compile s192 source
Post by: adamantibus on June 27, 2016, 06:38:26 pm
Still, releasing three versions of the same device -one that costs 300 bucks- whithin 9 months is just crazy.

None of the models is going to have any lasting support (probably not even community support).
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 27, 2016, 06:51:45 pm
Still, releasing three versions of the same device -one that costs 300 bucks- whithin 9 months is just crazy.

None of the models is going to have any lasting support (probably not even community support).
Jxd Support has never been good in terms of updates. But i agree, i don't understand jxd to be honest.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 28, 2016, 02:47:25 am
@skelton - Can you help me with a MacOS error I am having.  Basically, I am getting an error and it is frustrating me:

preparing StaticLib: libc_common [including  out/target/product/ardbeg/obj/STATIC_LIBRARIES/libc_tzcode_intermediates/libc_tzcode.a]
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/mod/mk_elfconfig
/Volumes/android/k1/kernel/scripts/selinux/genheaders/genheaders.c:13:10: fatal error: 'classmap.h' file not found
#include "classmap.h"

Makefile for genheaders has:
hostprogs-y     := genheaders
HOST_EXTRACFLAGS += -Isecurity/selinux/include

always          := $(hostprogs-y)
clean-files     := $(hostprogs-y)

This is ticking me off, because the file is there: kernel/security/selinux/include/classmap.h
Title: Re: MINI GUIDE - Compile s192 source
Post by: Elronza Williams Jr. on June 28, 2016, 06:48:17 am
Hey I'd for sure buy a rk3399 4gb ram 64gbs of storage Jxd S192k Singularity!
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on June 28, 2016, 09:14:43 am
@skelton - Can you help me with a MacOS error I am having.  Basically, I am getting an error and it is frustrating me:

preparing StaticLib: libc_common [including  out/target/product/ardbeg/obj/STATIC_LIBRARIES/libc_tzcode_intermediates/libc_tzcode.a]
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/mod/mk_elfconfig
/Volumes/android/k1/kernel/scripts/selinux/genheaders/genheaders.c:13:10: fatal error: 'classmap.h' file not found
#include "classmap.h"

Makefile for genheaders has:
hostprogs-y     := genheaders
HOST_EXTRACFLAGS += -Isecurity/selinux/include

always          := $(hostprogs-y)
clean-files     := $(hostprogs-y)

This is ticking me off, because the file is there: kernel/security/selinux/include/classmap.h

Mm. Difficult to know why the error is. I never compiled on mac, only under linux. Probably something in the environment is not ok. Or file is corrupted when you extracted the source.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 28, 2016, 11:05:29 pm
Oh, that makes sense.  I pulled the sources off of the VM, and they weren't compiling correctly there.  Let me see if that works.  Otherwise, I am putting a VM on the Macbook Pro and just compiling it there.  I think I have Parallels on the Mac.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 29, 2016, 01:00:32 am
I've officially given up, and installed Parallels on my Macbook Pro.  Installing Ubuntu now.  At least I know I can get everything going in Ubuntu, and now that it is on my laptop, I can happily play Doom or Total War:WARHAMMER while things compile.

UPDATE: Parallels wins!  I'm compiling completely again.  Time to get this first build together.
Title: Re: MINI GUIDE - Compile s192 source
Post by: adamantibus on June 29, 2016, 05:49:50 am
Did you manage to include the battery fix?
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on June 29, 2016, 05:58:40 am
Did you manage to include the battery fix?

I have asked JXD for it.  If I don't hear from them by morning, I am just going to pull apart the patch.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on July 01, 2016, 09:50:33 am
@LordDavon , my compiled source is test-keys too.
Title: Re: MINI GUIDE - Compile s192 source
Post by: LordDavon on July 16, 2016, 12:19:11 am
@skelton can you look at your instructions for the GameMap and KeyMaster apks?  Both files copy over without the .apk extension, and the lib file is never copied over.  I just copied and pasted your text into my Android.mk files.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on July 16, 2016, 09:41:49 am
@skelton can you look at your instructions for the GameMap and KeyMaster apks?  Both files copy over without the .apk extension, and the lib file is never copied over.  I just copied and pasted your text into my Android.mk files.

In my compilation seems they are fine with the apk extension and all,, so i think it's ok.

You can try changing this:
LOCAL_MODULE := GameMap.apk
and
LOCAL_CERTIFICATE := PRESIGNED



and the same for keymaster apk but it shouldn't be needed.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on July 16, 2016, 10:25:47 am
If still doesn't work perhaps you can just add them manually after compiling your system.img, but it's srange it doesn't work.
Title: Re: MINI GUIDE - Compile s192 source
Post by: skelton on July 16, 2016, 10:31:24 am
Another thing you can try is just use the ones from thr RK model (the apps seem just the same) replace everything including the mk files.


https://mega.nz/#!YwJGRQoZ!v_KG3jDofVmBe-jM8mxB7XmkCi7ybS31DYJLS6Tt6s4

I still doesn't work for you, i will try a different approach (maybe copying lib maually during compiling and just setting those apps in a different way) I cannot trying compiling at the moment because I am compiling Lollipop that needs different linux environment,