Dingoonity.org
Other Portable Consoles => JXD Devices => Topic started by: LordDavon on June 26, 2016, 09:22:49 pm
-
***PLEASE NOTE: THIS IS A DISCONTINUED PROJECT AND THE AUTHOR NO LONGER HAS A JXD S192 UNIT***
LordDavon's S192 Hacked Firmware:
Latest 0.53b Test Beta Added. Please test for charge issues.
Why is it:
This was designed to be a Shield Spoofed version of the S192 firmware.
This includes Shield Hub 4.12 in the /system/tmp directory. Navigate using ES and select to install.
KingoRoot is included for an optional root (I will post instructions)
MarketHelper is included to spoof the Market (I will post instructions soon)
JXD Alias apps have been removed.
Shield Hub installed.
Fully Patched with all JXD fixes so far.
Uses the Build.Prop from a 4.4.2 Shield Tablet.
Before You Begin:
You must have a good MicroUSB cable between the device and your PC.
You must disable Windows Signed Driver support, please use the following: http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ (http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/)
Remember that this is Alpha software and may not work as well as the official Firmware.
USE AT YOUR OWN RISK!!!
Backup First -- THIS WILL ERASE ALL YOUR DATA!!!
To Install:
Extract the ZIP file to a location where you will be able to find it later.
Plug your JXD into your computer using a good MicroUSB cable.
Power off the device by holding the power button for 10 seconds.
Hold the Volume + button - do not release.
Press the power button for 1 second.
Release the Power button.
The APX drivers will attempt installation and most likely fail.
- Open Device Manager
- Select the APX device under Universal Serial Bus Controllers
- Right Click and select Update Driver Software.
- Select Browse My Computer...
- Click Browse, and navigate to the folder you extracted the firmware.
- Select the nvidia_usbpcdriver folder, and select. Make sure Include Subfolders is selected.
- Click Next and finish installation.
Open the folder where the firmware was extracted in Windows Explorer.
Double click on S192_2G_DDR.bat.
The firmware install will take approximately 1 min.
The device will reboot when done.
To Download:
Beta 0.53 - https://mega.nz/#!JVATBSra!AFz8IMHUmgRCXequZR44iz29enwP63ajcaO5fSGMZfs
-
For future use...
-
For Future Use...
-
For Future Use...
-
Having issues with the VM again. I'm moving to the Macbook Pro for development. This will take me another day.
-
I am in a move and other life duties right now and have been out of the loop lately. Will be that for at least for one/two more weeks until I can find peace and a place with decent internet connection. What is happening? Someone at the hospital. My thoughts go out to you if that is the case.
When it comes to the s192 K1. Is it realistic to see the updated Shield Hub/Gamestream/Geforce NOW in this device? Or is that some kind of impossible mission?
-
I am in a move and other life duties right now and have been out of the loop lately. Will be that for at least for one/two more weeks until I can find peace and a place with decent internet connection. What is happening? Someone at the hospital. My thoughts go out to you if that is the case.
When it comes to the s192 K1. Is it realistic to see the updated Shield Hub/Gamestream/Geforce NOW in this device? Or is that some kind of impossible mission?
My firmware will have the latest Shield Hub on it. Everything is good, as far as family and health. My virtual machine keeps corrupting, so I am trying to compile it on the Macbook Pro right now. I'm compiling, but failing at the image creation. Working on that now.
-
Thank you very much LordDavon for your hard work. I just want to know if you figured out how to spoof the Google Play and Shield Hub both in order to download Shield exclusive games?
-
Thank you very much LordDavon for your hard work. I just want to know if you figured out how to spoof the Google Play and Shield Hub both in order to download Shield exclusive games?
I haven't played with it yet. Tried moving the build over to my Macbook Pro, as Virtualbox was unstable and kept corrupting the sources. The last build killed my JXD. I'm tired of having to redo all my changes every few days. That being said, I've got it almost completely finished, but I am having an issue with the kernel compiling now. It is getting a fatal error trying to find a file that is already there. Frustrating, to say the least. If I don't get it to work by tomorrow night, I will just move it over to my Surface Book. It is part of the Windows Developer Program, so it has Ubuntu built into the command line. Should compile without too much trouble there.
-
Sorry to hear about the hassle getting your custom hack-ware done.
-
Sorry to hear about the hassle getting your custom hack-ware done.
Nah, the issue is that I had a good one. When I went to the in-laws this weekend, I tested it and it was great. I left the VM compiling some new changes, so when I came home I wanted to test the latest image before uploading. That's when I noticed the corrupt files in the VM. The image screwed up my JXD too. All I need to do is get a new build environment going though.
-
I hope you're able to fix your Jxd S192 Singularity bro.
-
I hope you're able to fix your Jxd S192 Singularity bro.
I'm not worried about the device. I am sure it will be fine.
-
It is up for anyone who wants to test.
-
Can't you install this with a Mac? :'(
-
Can't you install this with a Mac? :'(
There may be a way. Right now, I am using the JXD firmware's installation software. Considering I compiled it on Parallels on a Mac, I would like to find a way.
-
Thanks for putting that out! Just finished installing and booting up. So far so good. Going to root it in a bit and see if that market helper works or not.
update: Rooted, shield hub works, no luck with market helper or the shield exclusive apps. Going to do a little sideloading and see how that works out.
Switched over to Apex Launcher. Hell of a good improvement over the default launcher with the giant icons that it comes with.
-
Thanks for putting that out! Just finished installing and booting up. So far so good. Going to root it in a bit and see if that market helper works or not.
update: Rooted, shield hub works, no luck with market helper or the shield exclusive apps. Going to do a little sideloading and see how that works out.
Switched over to Apex Launcher. Hell of a good improvement over the default launcher with the giant icons that it comes with.
Awesome! Thank you for helping test it out. :-)
-
Did you try changing governor in kernel to interactive as default? Perhaps that help to people having issues with emulators like mame running with stuttering (it seems it's only solved puting device in high performance mode, which is the same as using performance governor all the time.) although rooting the system with a cpu app anyone can try I guess.
I cannot test it unfortunately to give feedback, I'll get a s192K on monday, the one with RK3288.
did you try the CWM i send you? Because it would be a nice adittion in case if it works. I can extract system.img if you want to see if I can suggest anything. Did they send you the kernel patch for battery issues?
-
Salut ,d?sol? je ne parle pas anglais , je pass? pour f?liciter lorddavon pour son taf , super , merci a toi , sinon je voulais savoir si c'?t? possible que tu int?gre cwm pour pouvoir flasher super su a la place de kingroot , sa serais juste g?nial , en te remerciant et bon courage pour la suite ;)
-
Did you try changing governor in kernel to interactive as default? Perhaps that help to people having issues with emulators like mame running with stuttering (it seems it's only solved puting device in high performance mode, which is the same as using performance governor all the time.) although rooting the system with a cpu app anyone can try I guess.
I cannot test it unfortunately to give feedback, I'll get a s192K on monday, the one with RK3288.
did you try the CWM i send you? Because it would be a nice adittion in case if it works. I can extract system.img if you want to see if I can suggest anything. Did they send you the kernel patch for battery issues?
I haven't tried much of anything yet. After losing the VM, and moving over to my Macbook Pro, I spent too much time trying to remake all my changes. Now that it is getting tested, I will move the governor for the next version.
While it was down, my unit was down (bad firmware flash), so I have't tried the bootloader. I can do the this weekend.
As for the patch, I haven't received any word from JXD since I last emailed them, over a week ago. I'm not having the issue on my unit though. It is one of the things I hope people report back is fine.
-
Did a little sideloading and messed around with the governor but I don't really know what I'm doing with that. Side loading wise, got Doom 3 BFG running, sound stuttered terribly but visually it seemed to have a good framerate so who knows.
Installed "no frills cpu control" to mess around with governor / performance settings but either I don't know what I'm doing or it had some issues. It only has one option listed for the I/O scheduler "noop", and it seems to be misreporting the min and max clock frequency. I guess that has more to do with the s192 than any adjustments on your end of things tho.
update: Spent a little more time with doom and had the same sound issue with the original and doom 2 that come with BFG. And, kinda funny, it automatically loaded up my savegame on doom 3 from when I was playing it on the shield tablet. Amazing world we live in.
-
Did a little sideloading and messed around with the governor but I don't really know what I'm doing with that. Side loading wise, got Doom 3 BFG running, sound stuttered terribly but visually it seemed to have a good framerate so who knows.
Installed "no frills cpu control" to mess around with governor / performance settings but either I don't know what I'm doing or it had some issues. It only has one option listed for the I/O scheduler "noop", and it seems to be misreporting the min and max clock frequency. I guess that has more to do with the s192 than any adjustments on your end of things tho.
Try with kernel Adiutor or setcpu. you must be rooted and should allow you to change governor and scheduler.
-
Ok.
Installed setcpu.
It's correctly reporting the CPU mhz and looks to be working alright. By default it's set to interactive, and no option for deadline or b/cfq, etc. Dunno if those matter or not. I haven't had any problems with stuttering on emulators even before root/install but I haven't tried mame yet. I'll give it a try and see what happens. Was there anything else I should be testing/trying out?
-
Some people reported that mame run poorly unless high performance mode was set on settings. Strange that interactive is default governor (at least in source it was userspace). try mame 0.139 without frameskip to see if scroll runs smooth with simple games like outrun. At least some people reported that mame run very poorly, but no idea....
Also, some people reported that scroll was not completely smooth in broglia's emus without frameskipping. at least that was commented during the first days of the device. But not all people notice micro-stuttering in scroll...Apparently device have thre power modes, high performance, balanced and powersaving, and apparently only in high performance mode everything works ok.
Strange thing that cpu apps don't show any scheduler...
-
Salut ,d?sol? je ne parle pas anglais , je pass? pour f?liciter lorddavon pour son taf , super , merci a toi , sinon je voulais savoir si c'?t? possible que tu int?gre cwm pour pouvoir flasher super su a la place de kingroot , sa serais juste g?nial , en te remerciant et bon courage pour la suite ;)
Please try in english, at least with google translator xD.
You mean CWM for s192? I put one in this forum (a repack from shield tablet CWM). Take a look at this post, no idea if @LordDavon or someone else tried it though. I cannot test it without a device, sorry. You'll probaly need fastboot and unclock bootloader to flash it, or an app like Flashify.
http://boards.dingoonity.org/jxd-devices/mini-guide-compile-s192-source/msg145472/#msg145472
-
@LordDavon, I noticed you spoofed using a MM fingerprint, instead of a Kitkat one. I also suggest you change the
ro.build.product=ardbeg to ro.build.product=shieldtablet. It can help to download legit ganes from play store (unless there are more checkings to avoid it) . I would put the beginning of build.prop like this in case you wanna try:
ro.build.id=KTU84Q-01-V1.4-20160701.145857
ro.build.display.id=nvidiashield-eng 4.4.4 KTU84Q-01-V1.4-20160701.145857 eng.parallels.20160701.145858 test-keys
ro.build.version.incremental=eng.parallels.20160701.145858
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Jul 1 15:00:26 EDT 2016
ro.build.date.utc=1467399626
ro.build.type=eng
ro.build.user=NVIDIA
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=SHIELD Tablet
ro.product.brand=nvidia
ro.product.name=wx_na_wf
ro.product.device=shieldtablet
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=NVIDIA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shieldtablet
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wx_na_wf-eng 4.4.4 KTU84Q 41524_664.1902 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:4.4.4/KTU84Q/41524_664.1902:eng/test-keys
ro.build.characteristics=tablet
Nothing to lose I guess, probably you will need to erase data and cache from play store and services framework.
-
@LordDavon, I noticed you spoofed using a MM fingerprint, instead of a Kitkat one. I also suggest you change the
ro.build.product=ardbeg to ro.build.product=shieldtablet. It can help to download legit ganes from play store (unless there are more checkings to avoid it) . I would put the beginning of build.prop like this in case you wanna try:
ro.build.id=KTU84Q-01-V1.4-20160701.145857
ro.build.display.id=nvidiashield-eng 4.4.4 KTU84Q-01-V1.4-20160701.145857 eng.parallels.20160701.145858 test-keys
ro.build.version.incremental=eng.parallels.20160701.145858
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Jul 1 15:00:26 EDT 2016
ro.build.date.utc=1467399626
ro.build.type=eng
ro.build.user=NVIDIA
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=SHIELD Tablet
ro.product.brand=nvidia
ro.product.name=wx_na_wf
ro.product.device=shieldtablet
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=NVIDIA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shieldtablet
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wx_na_wf-eng 4.4.4 KTU84Q 41524_664.1902 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:4.4.4/KTU84Q/41524_664.1902:eng/test-keys
ro.build.characteristics=tablet
Nothing to lose I guess, probably you will need to erase data and cache from play store and services framework.
There are more checkings, but not sure what else is needed. I was making the changes line by line, since changing some of the lines changes how the code compiles (which means I have to move ardbeg files to the wx_na_wf or shieldtablet code, or put hooks in to load the ardbeg files). I stopped at this point to get the software out, and am going to spend some time changing things one at a time for the rest.
Oh, I make the change in the code and recompile each time. This way the stuff that gets tested can stay.
-
It's faster to compile just as default and use a tool to extract/repack system.img and change build.prop. If there are also framework checkings then it will be more complicated.
-
update: Spent a little more time with doom and had the same sound issue with the original and doom 2 that come with BFG. And, kinda funny, it automatically loaded up my savegame on doom 3 from when I was playing it on the shield tablet. Amazing world we live in.
Anyone know if this happens on the original JXD Firmware?
-
Some people reported that mame run poorly unless high performance mode was set on settings. Strange that interactive is default governor (at least in source it was userspace). try mame 0.139 without frameskip to see if scroll runs smooth with simple games like outrun. At least some people reported that mame run very poorly, but no idea....
Also, some people reported that scroll was not completely smooth in broglia's emus without frameskipping. at least that was commented during the first days of the device. But not all people notice micro-stuttering in scroll...Apparently device have thre power modes, high performance, balanced and powersaving, and apparently only in high performance mode everything works ok.
Strange thing that cpu apps don't show any scheduler...
Used mame4droid 0.139u1, turned off frameskip, and no problems at all. I flipped on and off threaded video, the thread priority options, etc, no stuttering at all. I play the hell out of the broglia emulators with ninja gaiden and batman and I haven't seen any stuttering on those eithers. The one thing I did see with the broglia nes emulator is it's default screen refresh rate when installed was set at something goofy like 57 or 58hz. I let it autodetect and it came up with 59.89hz, turned off frameskip and lowered the audio latency setting to 4 frames from 8. I'm a whiny picky bitch when it comes to input lag so I would think if there was an issue on ninja gaiden then I would've noticed it.
update: Spent a little more time with doom and had the same sound issue with the original and doom 2 that come with BFG. And, kinda funny, it automatically loaded up my savegame on doom 3 from when I was playing it on the shield tablet. Amazing world we live in.
Anyone know if this happens on the original JXD Firmware?
Shit, sorry, I should've tried it before. I haven't tried any other shield games so I don't know if it's specific to Doom or if it's a broader thing. Guess I should get to sideloading something else
-
Some people reported that mame run poorly unless high performance mode was set on settings. Strange that interactive is default governor (at least in source it was userspace). try mame 0.139 without frameskip to see if scroll runs smooth with simple games like outrun. At least some people reported that mame run very poorly, but no idea....
Also, some people reported that scroll was not completely smooth in broglia's emus without frameskipping. at least that was commented during the first days of the device. But not all people notice micro-stuttering in scroll...Apparently device have thre power modes, high performance, balanced and powersaving, and apparently only in high performance mode everything works ok.
Strange thing that cpu apps don't show any scheduler...
Used mame4droid 0.139u1, turned off frameskip, and no problems at all. I flipped on and off threaded video, the thread priority options, etc, no stuttering at all. I play the hell out of the broglia emulators with ninja gaiden and batman and I haven't seen any stuttering on those eithers. The one thing I did see with the broglia nes emulator is it's default screen refresh rate when installed was set at something goofy like 57 or 58hz. I let it autodetect and it came up with 59.89hz, turned off frameskip and lowered the audio latency setting to 4 frames from 8. I'm a whiny picky bitch when it comes to input lag so I would think if there was an issue on ninja gaiden then I would've noticed it.
update: Spent a little more time with doom and had the same sound issue with the original and doom 2 that come with BFG. And, kinda funny, it automatically loaded up my savegame on doom 3 from when I was playing it on the shield tablet. Amazing world we live in.
Anyone know if this happens on the original JXD Firmware?
Shit, sorry, I should've tried it before. I haven't tried any other shield games so I don't know if it's specific to Doom or if it's a broader thing. Guess I should get to sideloading something else
do you have your device in high performance mode or balanced? It seems people reporting that issue claimed that ittndidn't work ok in balance mode. only in high performance seemed to work right. Retroarch is also a good test for testing screen refresh rate.
-
It's faster to compile just as default and use a tool to extract/repack system.img and change build.prop. If there are also framework checkings then it will be more complicated.
Okay. I will try that and see if that gets things working better. I will also change the default governor. Should I add a few more governors and I/O schedulers to the kernel? I haven't looked at the kernel config to see if there are a few I just need to turn on. One thing though, wife took the baby to the in-laws for the afternoon, so I'm installing Total War:WARHAMMER right now. ;-)
Once she gets back, I'm going to work on it. While she is gone, it is play time for me. I have a date with DOOM and TW:W. I've had these games for a couple weeks now, and am just getting TW:W installed, and have 31 minutes into DOOM (51 now). :-)
-
Shit, sorry, I should've tried it before. I haven't tried any other shield games so I don't know if it's specific to Doom or if it's a broader thing. Guess I should get to sideloading something else
Take your time. I really appreciate the help. This is great testing!
-
It's faster to compile just as default and use a tool to extract/repack system.img and change build.prop. If there are also framework checkings then it will be more complicated.
Okay. I will try that and see if that gets things working better. I will also change the default governor. Should I add a few more governors and I/O schedulers to the kernel? I haven't looked at the kernel config to see if there are a few I just need to turn on. One thing though, wife took the baby to the in-laws for the afternoon, so I'm installing Total War:WARHAMMER right now. ;-)
Once she gets back, I'm going to work on it. While she is gone, it is play time for me. I have a date with DOOM and TW:W. I've had these games for a couple weeks now, and am just getting TW:W installed, and have 31 minutes into DOOM (51 now). :-)
I saw several governors in the source. Userspave governor seemed to be the default according to kernel config. Just put interactive as default and add the ones included in the source to see if it behaves better.
-
Got HL2 ep 1 installed and it didn't have any problems so maybe it's just doom3 that has the issues. Doing to dig into it's config file and see if there's anything that can be done from there, at least get an fps counter up so I can see if there are any issues there compared to the shield.
-
@LordDavon, I noticed you spoofed using a MM fingerprint, instead of a Kitkat one. I also suggest you change the
ro.build.product=ardbeg to ro.build.product=shieldtablet. It can help to download legit ganes from play store (unless there are more checkings to avoid it) . I would put the beginning of build.prop like this in case you wanna try:
ro.build.id=KTU84Q-01-V1.4-20160701.145857
ro.build.display.id=nvidiashield-eng 4.4.4 KTU84Q-01-V1.4-20160701.145857 eng.parallels.20160701.145858 test-keys
ro.build.version.incremental=eng.parallels.20160701.145858
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Jul 1 15:00:26 EDT 2016
ro.build.date.utc=1467399626
ro.build.type=eng
ro.build.user=NVIDIA
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=SHIELD Tablet
ro.product.brand=nvidia
ro.product.name=wx_na_wf
ro.product.device=shieldtablet
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=NVIDIA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shieldtablet
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wx_na_wf-eng 4.4.4 KTU84Q 41524_664.1902 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:4.4.4/KTU84Q/41524_664.1902:eng/test-keys
ro.build.characteristics=tablet
Nothing to lose I guess, probably you will need to erase data and cache from play store and services framework.
@skelton I tried changing ro.build.product (I didn't touch it before thinking it was deprecated) in the image and reflashing. It still didn't work. I will move to these keys and see if it makes a difference. I basically have to spoof it and then recompile everything, just in case things get signed. I want them signed with these keys.
I looked inside the MarketHelper app to see what object it used for spoofing. Here is what I found:
public static DeviceSpecs m50a(Context context) {
if (f73a != null) {
return f73a;
}
DeviceSpecs deviceSpecs = new DeviceSpecs();
deviceSpecs.hardware = Build.HARDWARE;
deviceSpecs.brand = Build.BRAND;
deviceSpecs.radioVersion = DeviceSpecsUtils.m55b();
deviceSpecs.bootloader = Build.BOOTLOADER;
deviceSpecs.device = Build.DEVICE;
deviceSpecs.model = Build.MODEL;
deviceSpecs.manufacturer = Build.MANUFACTURER;
deviceSpecs.product = Build.PRODUCT;
deviceSpecs.cpuAbi = Build.CPU_ABI;
deviceSpecs.cpuAbi2 = Build.CPU_ABI2;
ConfigurationInfo deviceConfigurationInfo = ((ActivityManager) context.getSystemService("activity")).getDeviceConfigurationInfo();
WindowManager windowManager = (WindowManager) context.getSystemService("window");
DisplayMetrics displayMetrics = new DisplayMetrics();
windowManager.getDefaultDisplay().getMetrics(displayMetrics);
deviceSpecs.glEsVersion = deviceConfigurationInfo.reqGlEsVersion;
deviceSpecs.screenDpi = displayMetrics.densityDpi;
deviceSpecs.screenWidth = displayMetrics.widthPixels;
deviceSpecs.screenHeight = displayMetrics.heightPixels;
deviceSpecs.screenSmallestWidthDp = DeviceSpecsUtils.m53b(context);
deviceSpecs.deviceKeyboard = DeviceSpecsUtils.m54b(deviceConfigurationInfo);
deviceSpecs.deviceNavigation = DeviceSpecsUtils.m56c(deviceConfigurationInfo);
deviceSpecs.deviceTouchscreen = DeviceSpecsUtils.m48a(deviceConfigurationInfo);
deviceSpecs.deviceScreenLayout = DeviceSpecsUtils.m49a(context.getResources().getConfiguration());
deviceSpecs.deviceInputFeatures = deviceConfigurationInfo.reqInputFeatures;
deviceSpecs.glExtensions = DeviceSpecsUtils.m51a();
deviceSpecs.systemSharedLibraries = DeviceSpecsUtils.m57c(context);
deviceSpecs.systemFeatures = DeviceSpecsUtils.m59d(context);
f73a = deviceSpecs;
return deviceSpecs;
So, it looks like there may be a few things we can try.
Oh, I changed the default governor in the config file, and it didn't change in the code. I changed the config file you said for the kernel compile. Is there another one that gets used during the image build and creation?
-
@LordDavon, I noticed you spoofed using a MM fingerprint, instead of a Kitkat one. I also suggest you change the
ro.build.product=ardbeg to ro.build.product=shieldtablet. It can help to download legit ganes from play store (unless there are more checkings to avoid it) . I would put the beginning of build.prop like this in case you wanna try:
ro.build.id=KTU84Q-01-V1.4-20160701.145857
ro.build.display.id=nvidiashield-eng 4.4.4 KTU84Q-01-V1.4-20160701.145857 eng.parallels.20160701.145858 test-keys
ro.build.version.incremental=eng.parallels.20160701.145858
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Jul 1 15:00:26 EDT 2016
ro.build.date.utc=1467399626
ro.build.type=eng
ro.build.user=NVIDIA
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=SHIELD Tablet
ro.product.brand=nvidia
ro.product.name=wx_na_wf
ro.product.device=shieldtablet
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=NVIDIA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shieldtablet
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wx_na_wf-eng 4.4.4 KTU84Q 41524_664.1902 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:4.4.4/KTU84Q/41524_664.1902:eng/test-keys
ro.build.characteristics=tablet
Nothing to lose I guess, probably you will need to erase data and cache from play store and services framework.
@skelton I tried changing ro.build.product (I didn't touch it before thinking it was deprecated) in the image and reflashing. It still didn't work. I will move to these keys and see if it makes a difference. I basically have to spoof it and then recompile everything, just in case things get signed. I want them signed with these keys.
I looked inside the MarketHelper app to see what object it used for spoofing. Here is what I found:
public static DeviceSpecs m50a(Context context) {
if (f73a != null) {
return f73a;
}
DeviceSpecs deviceSpecs = new DeviceSpecs();
deviceSpecs.hardware = Build.HARDWARE;
deviceSpecs.brand = Build.BRAND;
deviceSpecs.radioVersion = DeviceSpecsUtils.m55b();
deviceSpecs.bootloader = Build.BOOTLOADER;
deviceSpecs.device = Build.DEVICE;
deviceSpecs.model = Build.MODEL;
deviceSpecs.manufacturer = Build.MANUFACTURER;
deviceSpecs.product = Build.PRODUCT;
deviceSpecs.cpuAbi = Build.CPU_ABI;
deviceSpecs.cpuAbi2 = Build.CPU_ABI2;
ConfigurationInfo deviceConfigurationInfo = ((ActivityManager) context.getSystemService("activity")).getDeviceConfigurationInfo();
WindowManager windowManager = (WindowManager) context.getSystemService("window");
DisplayMetrics displayMetrics = new DisplayMetrics();
windowManager.getDefaultDisplay().getMetrics(displayMetrics);
deviceSpecs.glEsVersion = deviceConfigurationInfo.reqGlEsVersion;
deviceSpecs.screenDpi = displayMetrics.densityDpi;
deviceSpecs.screenWidth = displayMetrics.widthPixels;
deviceSpecs.screenHeight = displayMetrics.heightPixels;
deviceSpecs.screenSmallestWidthDp = DeviceSpecsUtils.m53b(context);
deviceSpecs.deviceKeyboard = DeviceSpecsUtils.m54b(deviceConfigurationInfo);
deviceSpecs.deviceNavigation = DeviceSpecsUtils.m56c(deviceConfigurationInfo);
deviceSpecs.deviceTouchscreen = DeviceSpecsUtils.m48a(deviceConfigurationInfo);
deviceSpecs.deviceScreenLayout = DeviceSpecsUtils.m49a(context.getResources().getConfiguration());
deviceSpecs.deviceInputFeatures = deviceConfigurationInfo.reqInputFeatures;
deviceSpecs.glExtensions = DeviceSpecsUtils.m51a();
deviceSpecs.systemSharedLibraries = DeviceSpecsUtils.m57c(context);
deviceSpecs.systemFeatures = DeviceSpecsUtils.m59d(context);
f73a = deviceSpecs;
return deviceSpecs;
So, it looks like there may be a few things we can try.
Oh, I changed the default governor in the config file, and it didn't change in the code. I changed the config file you said for the kernel compile. Is there another one that gets used during the image build and creation?
Strange that kernel ignore that change. Did you make a make clean before compiling kernel again? Perhaps there is something in the power policy that overrides that. Or kernel is just a mess. Maybe bootloader must be unlocked i am afraid like happens with shield tablet.
I will get the rockchip modelo tomorrow probably so i think i will have my own fight with that model i guess, because jXD source will be muxh more faulty than gpd source i guess.
-
Skelton, you should sell your RK model and get a Tegra instead. ;D
-
Strange that kernel ignore that change. Did you make a make clean before compiling kernel again? Perhaps there is something in the power policy that overrides that. Or kernel is just a mess. Maybe bootloader must be unlocked i am afraid like happens with shield tablet.
I will get the rockchip modelo tomorrow probably so i think i will have my own fight with that model i guess, because jXD source will be muxh more faulty than gpd source i guess.
I always make clean unless I am just making a quick change in the system folder of the image. I may just compile the kernel manually and move it to the image. It shouldn't be this difficult. There is also 5 governors in the config selected, so it may be using a different config. Maybe I will make the changes to all of them.
-
Skelton, you should sell your RK model and get a Tegra instead. ;D
Nope,, rather the contrary, if jXD had real interest to kmprove tegra model, they should have send me a tegra one..... that decisi?n tells me that jXD is going to abandon s192 tegra users..... i don't think i use this s192 anyway except for development, i prefer something smaller like gpd xd for playing.
-
I know JXD has no interest in improving the Tegra model (nor any of their devices), that's precisely why we are interested in you improving it. XD
-
I know JXD has no interest in improving the Tegra model (nor any of their devices), that's precisely why we are interested in you improving it. XD
Yeah, but no free sample, no party, and less in my current circunstancies. With more days at hospital than at home.
-
So...umm...with this Hackware, can I use Shield HUB with Gamestream/Geforce NOW and the joysticks+buttons work as they should?
-
So...umm...with this Hackware, can I use Shield HUB with Gamestream/Geforce NOW and the joysticks+buttons work as they should?
Yes. Works great!
-
Latest status update: So, I've been through many settings and while I can get Google Servers to show this as an official (with icon) NVidia Shield Tablet, I can't get it to spoof enough. I've been trying as a 4.4.2 device, just to see if that will work. I can still get it working great with MarketHelper, I don't want to have to run it after every reboot.
So, I'm going to keep trying until I can get this to work. I was able to pull apart Market Helper and noticed that it sends the OpenGL info, radios and even an application list. I wasn't able to find exactly what is bring sent fir the Shield yet. I've emailed the author to see if he can help, but I've not heard back in days.
So, not giving up. Never giving up. ;-) I WILL GET THIS WORKING!!!
...I hope.
-
Got HL2 ep 1 installed and it didn't have any problems so maybe it's just doom3 that has the issues. Doing to dig into it's config file and see if there's anything that can be done from there, at least get an fps counter up so I can see if there are any issues there compared to the shield.
I think DOOM3 requires a newer version of Android. Under the spoofed firmware with Market Helper, it still isn't available. Half Life 2 is downloading and shows compatible. So, that may be the issue.
I've found a few OpenGL settings that may help a little though. Going to set them active for the next firmware.
-
Thanks to your works! It's great!!!!
But i've noticed that "game mapper function" doesn't works...
Can you check [email protected]@
-
Another update: My latest spoof is no longer resetting after closing MarketHelper and rebooting. I've got to be close. I do want to spoof to a higher Android version though, since many games aren't available for 4.4.x.
-
Thanks to your works! It's great!!!!
But i've noticed that "game mapper function" doesn't works...
Can you check [email protected]@
Oh no. Did I forget to include it? I will see what happened.
UPDATE: Yup. I forgot it. I will see why it didn't compile in, and get a work around until the Beta is released.
-
Thanks to your works! It's great!!!!
But i've noticed that "game mapper function" doesn't works...
Can you check [email protected]@
Oh no. Did I forget to include it? I will see what happened.
UPDATE: Yup. I forgot it. I will see why it didn't compile in, and get a work around until the Beta is released.
Thanks to your check...i'll wait your next build with pleasure!!!!
-
Is there any Update? I wanna use Keymapper~^^
-
Is there any Update? I wanna use Keymapper~^^
Sorry, I had a long week last week, and my weekend was a busy one, so I didn't have a lot of time to work on the new image. The wife hurt her shoulder, so I've been taking care of the baby a lot more than usual too. I've been able to get into things here and there, but not for too long. I am hoping to have something new in a few days though. She's seeing the doctor today, and should have something for the pain.
-
Is there any Update? I wanna use Keymapper~^^
Sorry, I had a long week last week, and my weekend was a busy one, so I didn't have a lot of time to work on the new image. The wife hurt her shoulder, so I've been taking care of the baby a lot more than usual too. I've been able to get into things here and there, but not for too long. I am hoping to have something new in a few days though. She's seeing the doctor today, and should have something for the pain.
oh~I See... I'll wait...Primarily take care of your family!
-
@kingporkcutlet I will have a new release in a few days. If you'd like to help, I can get you the latest image to test. I'd like to make sure that all of the Game Mapping issues are fixed before releasing to everyone. If you don't mind helping, I can get an image link to you.
-
@kingporkcutlet I will have a new release in a few days. If you'd like to help, I can get you the latest image to test. I'd like to make sure that all of the Game Mapping issues are fixed before releasing to everyone. If you don't mind helping, I can get an image link to you.
Oh thanks to your works! Surely I wanna check this for better device...if you're ok...I'll check it(maybe only keymapper function...becoz i have no time to check all function...I'm shift worker..haha) once again very very thanks to your efforts...
-
Since I am not hearing back from JXD about the patch for the battery issue, I may have to try a different approach for this. So, I may just release the PreBeta, and start with pulling apart JXD's firmware to create a new image.
-
PreBeta released. I'm moving to a new ROM layout. Wish me luck. Just hacking it out of JXD's stuff. ;-) This is going to delay the Beta, but should make it better. I'm hoping to get it at the end of the week.
-
good luck, we hope to see soon
-
hello lord devon
thanks for all your efforts towards this device :)
-
I just want to apologize to everyone for the delay. With my house going up for sale, we've been scrambling to get it ready for showing. I'm still working on the firmware, when I have time. I just haven't had a lot of it lately. We are looking at rentals this week, and if we find one, I should be good to take a breather.
-
Thankyou lordDavon as we wait patiently, as soon as you have managed to compile the game mapper function into the firmware i would download staright away as your hacked firmware is a much better one than the JXD stock one but the game mapper not working is a deal breaker for me so i would rather wait till its fixed
once again thankyou for your work with this device :)
-
Thankyou lordDavon as we wait patiently, as soon as you have managed to compile the game mapper function into the firmware i would download staright away as your hacked firmware is a much better one than the JXD stock one but the game mapper not working is a deal breaker for me so i would rather wait till its fixed
once again thankyou for your work with this device :)
The PreBeta that is at the download link has the mapper. :-)
-
Oh thanks am downloading straight away :)
-
Good morning Lord Davon. I think the easiest and most simple way to solve everyone's problems with the Jxd Singularity S192 is to get the complete either Android Marshmallow or Lollipop Shield Tablet software working on this device
-
That needs a New bootloader that must be provided by jxd. Tegra devices use a diferentes bootloader according to the Android version. Flashing shield bootloader into the jxd will brick your device. I wouldn't expect jxd providkng anythong, because they no longer Support this device.
Anyhow, anyone can try it. Shield tablet is open source.
http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=blob_plain;f=README;hb=rel-24-sb-r1-partner
-
I'm giving a new version to Elronza to test, and make sure the battery issues is fixed. The new version already has Shield Hub installed. Right now it is a merger of the original JXD firmware, and all of their patches. I am cleaning things up, and will get it ready for release. If Elronza verifies the battery fix is intact, I will have a new version to release soon.
-
I have installed LordDavon's latest custom firmware and am now awaiting my Jxd S192 reaching 100% full charge.
-
I have installed LordDavon's latest custom firmware and am now awaiting my Jxd S192 reaching 100% full charge.
Thank you for the help.
-
I've uploaded the latest Beta version. I'd like to get a test and see if the charging issue is fixed. This is basically a firmware that includes all of JXDs patches, the Shield Tablet's 4.4.2 build.prop and a root test (which didn't work). This is done using my new way of doing the firmware, and I hope to be using this in the future.
I uploaded this to get a wider test of the battery fix, to make sure it is working for everyone.
-
LordDavon your newest Custom Firmware is working. My battery is at 99% and states 11mins left till full charge. Thank you for all the hard work you've put into this device.
-
It is now at 100%.
-
The joystick is fully functional in both gamestream/geforce NOW/emulators and Android games?
-
The joystick is fully functional in both gamestream/geforce NOW/emulators and Android games?
If it is in the original firmware, then it is in this one. I used the original JXD firmware as the base. :-)
-
I've just installed the beta and everything so far seems good.
One question though, with the build prop being based off a Shield Tablet, should that fool Google Play in to thinking its a Shield Tablet, and thus being able to purcahase games such Half Life 2 and Borderlands 2 as it still does not :(
Or is it just wishful thinking.
-
I've just installed the beta and everything so far seems good.
One question though, with the build prop being based off a Shield Tablet, should that fool Google Play in to thinking its a Shield Tablet, and thus being able to purcahase games such Half Life 2 and Borderlands 2 as it still does not :(
Or is it just wishful thinking.
It sends more than just the build.prop info. There is an installed app listing, OpenGL version, and more. I am slowly trying to get it all sent. When I was testing, using the build.prop from the Shield Tablet didn't seem to hurt anything, so I just left it.
-
Ah, okay, thanks for that. I look forward to any progress you might be able to make with this :)
-
Ah, okay, thanks for that. I look forward to any progress you might be able to make with this :)
Thank you for testing. Since I don't have all the changes I want in it, I consider it a beta. It should be very stable though.
I need to find the last Shield Hub that was installable before they locked it to 5.0+ and get that updated. A little dissapointing, since I love using my JXD S192 with Geforce Now and Gamestream. I just hope it doesn't get blocked.
-
Hi all,
I've been following the S192 threads on here for a while - I've been one of the fortunate ones (touch wood) so far, as I've not come across the many issues detailed in said threads with my S192.
So, a little late with my contribution, but I have the lastest Shield Hub (4.12.20965591) that I got off my Shield Portable before the last update which now, I suspect, is for Lollipop or newer only as the package won't install on the S192 anymore.
If you want the APK, I can give you a copy?
The S192 K1 looks like it's being abandoned by JXD - but personally, I love it. And would love to see some TLC thrown in it's way. I'm not versed in all the dev stuff, but if I can contribute somehow I will :)
Fyi (you might already be aware of it) for gamestream, I find Moonlight (root version) much better than shield hub itself, with a typically lower latency at 1080p 60fps setting. I didn't continue my subscription with Geforce Now after the free 3 months trial, so I can't really comment on that.
-
Hi Kenneth. I've tried the latest Sheild Hub (4.13.21096871), but it doesn't install on 4.4 (tuned for 5.0+ I believe). If 4.12.20965591 is installable, I will give it a try and merge it into the ROM. Have you tried 4.12.20977108 yet?
-
I haven't tried 4.12.20977108 - I was on 4.12.20965591 on my Shield Portable then the next update went straight to 4.13.21096871.
I've got 4.12.20965591 installed on my S192 right now and when you go into SETTINGS -> ABOUT it doesn't say there is an update available anymore, where as previous versions did. So I can only assume this is probably the last/latest version of Shield Hub compatible with KitKat 4.4.2.
-
I'm dealing with the move this week, but things will be settling down early next week. I'll test that version and if it installs, I will merge it into the ROM.
-
So glad I found this forum today. I got my S192 charging now and gonna flash this as soon as it's charged. Thanks for putting time into this, I wasn't sure if anyone was gonna do any mods or firmware for this device.
LordDavin if you have PayPal please let me know and I will donate a little cash for your efforts.
-
I could also donate for improved firmware
-
I appreciate the offer. For now, just test the firmware and let me know if you find any issues. That'd be awesome!
Firmware should be pretty stable. I'm moving today and tomorrow, and unpacking the next few days. Will most likely be releasing a new firmware again next week.
-
I finally installed the beta the other night, and had been waiting for my GTX 1060 to arrive. After installing my Graphics card, and testing the S192, I can say that this firmware works really well. I had some overheating issues the first day and a half, but after resetting and wiping everything after install, that issue went away. Last night I was able to stream FallOut 4 to my S192, and it played flawlessly.
I can confirm that all of my shield exclusive games that i purchased in the past for my Shield portable and my shield tablet still show as not compatible with the S192. Otherwise everything works really well. It appears that the battery usage during standby, is greatly improved. My S192 sat for two days untouched and lost only about 2 percent battery life.
Thanks for the hard work you put into this. This weekend the kids will be at the in-laws, so I can game until my thumbs bleed, and it will give me plenty of time to test this firmware. I look forward to updates.
-
I finally installed the beta the other night, and had been waiting for my GTX 1060 to arrive. After installing my Graphics card, and testing the S192, I can say that this firmware works really well. I had some overheating issues the first day and a half, but after resetting and wiping everything after install, that issue went away. Last night I was able to stream FallOut 4 to my S192, and it played flawlessly.
I can confirm that all of my shield exclusive games that i purchased in the past for my Shield portable and my shield tablet still show as not compatible with the S192. Otherwise everything works really well. It appears that the battery usage during standby, is greatly improved. My S192 sat for two days untouched and lost only about 2 percent battery life.
Thanks for the hard work you put into this. This weekend the kids will be at the in-laws, so I can game until my thumbs bleed, and it will give me plenty of time to test this firmware. I look forward to updates.
Thank you for testing it out. I've been moving, so I haven't had much of a chance to continue work on the next version. Things are starting to settle now, so I may be able to get some work done tomorrow.
-
Hey LordDavon,
I have been lurking here for quite a while now and really admire your work.
What benefits does this new firmware bring to the table in terms of functionality and proven fixes?
Any plans to upgrade JXD firmware to a newer version of Android?
The ability to trick app stores into recognising the Nvidia Tegra K1 chipset and allowing it to purchase exclusive games (for this chipset) would prove ground breaking, allowing all owners to enjoy their devices for its intended purpose - If you can achieve this you will officially be known as Lord LordDavon 8)
-
This firmware is a combination of all of the fixes released from JXD (including battery fix and ShieldHub). I've also cleaned up the desktop icons.
In order to upgrade the Android version, we would need an updated bootloader. I've been offered a S192 with some issues, which if I can fix, I can use for bootloader testing.
-
the CWM, of shield tablet, works in the JXD S192?
and what would be the key combination to enter the revovery?
I am not able
-
the CWM, of shield tablet, works in the JXD S192?
and what would be the key combination to enter the revovery?
I am not able
We don't know if the any of the Shield Tablet boot loaders will work. Something I will have to test.
All of the install instructions are on the first post: http://boards.dingoonity.org/jxd-devices/lorddavon's-s192-hackware/
-
to try to change the recovery, I can brick the S192? or if it does not work alone would be reinstall the original recovery?
if anyone knows the key combination to enter recovery please help thanks
-
to try to change the recovery, I can brick the S192? or if it does not work alone would be reinstall the original recovery?
if anyone knows the key combination to enter recovery please help thanks
This isn't the recovery or bootloader. This is just the firmware. While there is always a risk to everything, it is pretty hard to brick these with the firmware flashes. As long as your device is healthy, you can always reflash from a bad flash.
-
sorry my bad English, I use the translator goolge.
I already have your firmware, but I want to install the CWM. I dispose of the cwm of the shield tablet, and wanted to know if I can try to install it, or is no possibility of of no return brick?
-
sorry my bad English, I use the translator goolge.
I already have your firmware, but I want to install the CWM. I dispose of the cwm of the shield tablet, and wanted to know if I can try to install it, or is no possibility of of no return brick?
It may be possible to come back from it, if it kills the device. I'm not sure yet.
-
I have fear of brick, if someone wants to try ...
Cwm here:
http://www.gitmag.com/how-to-root-and-install-twrp-recovery-on-nvidia-shield-tablet/
and here:
http://techbeasts.com/root-nvidia-shield-nvida-shield-tablet-and-install-custom-recovery/
-
I have a problem, even with its custom rom. % of the battery does not rise.
if the charge arrive at full load, but stays at 13% for example, and after this 7h or 8h at 13%, and when it reaches the 13%, begins to drop.
not if I explain.
on your custom rom with the battery fix JXD, there are problems battery? or this all sorted out?
-
I have a problem, even with its custom rom. % of the battery does not rise.
if the charge arrive at full load, but stays at 13% for example, and after this 7h or 8h at 13%, and when it reaches the 13%, begins to drop.
not if I explain.
on your custom rom with the battery fix JXD, there are problems battery? or this all sorted out?
The battery issue is fixed in the custom ROM.
-
to me continues to operate me wrong, even with the custom rom, battery fails, then this faulty hardware mine, no?
-
to me continues to operate me wrong, even with the custom rom, battery fails, then this faulty hardware mine, no?
Not sure. If you are on the latest Beta, it shouldn't be a software issue. You may want to download and reflash, then just put it down to charge and see if that takes care of the issue.
-
OK thanks
I will return to reflash if the problem persists, send it to repair under warranty
-
Hi LordDavon, hope your well. I have a question. One of my biggest wants is to increase the storage memory of my JXD S192. I have been reading a lot about editing fstab's to swap internal for external memory, and was wondering if you knew if it was possible.
I have a 128GB memory card in mine, and would love it if it were possible to do this. I also would prefer it if I didn't have to root it either, as I have tried using Folder mount, but I was never confident that it was reliable enough, plus, one of my favourite games (HIT) does not work when rooted.
Is this something that can be defaulted into a custom rom, so without rooting, you could install the ROM, and it would default to using the external memory card instead?
As you can imagine, I probably don't really know what i am talking about, so forgive me if the answer is obvious :)
-
I understand. You explained perfectly. Honestly, I haven't looked into it too much yet. I've just been focused on spoofing. Most of what I've done is in the system partition. I have access to the root partition also, but I've not tried editing it. Let me see what I can figure out for swapping the two.
-
to me continues to operate me wrong, even with the custom rom, battery fails, then this faulty hardware mine, no?
Not sure. If you are on the latest Beta, it shouldn't be a software issue. You may want to download and reflash, then just put it down to charge and see if that takes care of the issue.
I have reinstalled you custom firmware, and battery problems remain the same.
I will apply for warranty repair, if they having solves
-
someone can give me the update that fixes the battery?
JXD on the link, the update is only adding shield hub
-
someone can give me the update that fixes the battery?
JXD on the link, the update is only adding shield hub
My firmware has both the ShieldHub and the battery fix. If you want to apply JXD's battery fix, you need to install their original firmware again.
All of the official JXD downloads can be found on their Facebook page: https://www.facebook.com/JXDofficial/
JXDs Battery Update: https://mega.nz/#F!Q5wRERbT!4pMx-MU1djAT84kc9O8a5w
-
someone can give me the update that fixes the battery?
JXD on the link, the update is only adding shield hub
My firmware has both the ShieldHub and the battery fix. If you want to apply JXD's battery fix, you need to install their original firmware again.
All of the official JXD downloads can be found on their Facebook page: https://www.facebook.com/JXDofficial/
JXDs Battery Update: https://mega.nz/#F!Q5wRERbT!4pMx-MU1djAT84kc9O8a5w
I have reinstalled 1.4 official firmware several times.
And I've reinstalled your custom firmware several times.
And the problem persists, with the jxd off, the% does not go up. And turned on. sometimes rises
I want to try reinstalling the battery fix manually.
Have, if I solve it before sending warranty
-
someone can give me the update that fixes the battery?
JXD on the link, the update is only adding shield hub
My firmware has both the ShieldHub and the battery fix. If you want to apply JXD's battery fix, you need to install their original firmware again.
All of the official JXD downloads can be found on their Facebook page: https://www.facebook.com/JXDofficial/
JXDs Battery Update: https://mega.nz/#F!Q5wRERbT!4pMx-MU1djAT84kc9O8a5w
I have reinstalled 1.4 official firmware several times.
And I've reinstalled your custom firmware several times.
And the problem persists, with the jxd off, the% does not go up. And turned on. sometimes rises
I want to try reinstalling the battery fix manually.
Have, if I solve it before sending warranty
faulty console, me have changed, a new one in warranty
-
Hello everyone! Long time no speak.. haven't used my jxd in a long while but trying to sort it out and have noticed something weird so looking for advice.
I rooted official firmware, applied the original jxd fixes and thought everything was ok. Just recently though I've noticed permissions on my SD card being messed up.
C64.emu made me notice and start checking as I set it to save states within the games folder and it kept erroring and saying it hat no write permissions.
I then went to try and delete a rom and sure enough I couldn't delete it. I had to download something to reset permissions on the whole ext sd card ( something commander)
My question is this, would I be better to wipe the device and the sd card and reflash a different firmware or maybe try and re root a different way, or flash one of your firmwares etc... up until this point I never noticed any other problems what so ever (root, battery charge etc)
Thanks for reading.
Sent from my SM-G900F using Tapatalk
-
...
Mine is based on the official firmware. So unless you want the battery fix and Shield Hub, or want to refresh your firmware without needing to run patches after, I'm not too sure it matters... except for a cleaner home screen.
The issue with JXD's firmware is that there is a patch for battery, or a patch for Shield Hub. They both can't be run. This is a combo of both, with the build prop changes, and the game icons removed from the home screen.
-
Ohh ok, I already ran the battery fix and it worked ok for me.
Is there a better way to obtain root? Perhaps that's my issue. Kingroot was quite new on jxd when I did it. Is there a better alternative
Sent from my SM-G900F using Tapatalk
-
Or can you recommend a program i can run to reset the permissions on sdcard1 which is my ext card.
Sent from my SM-G900F using Tapatalk
-
Ohh ok, I already ran the battery fix and it worked ok for me.
Is there a better way to obtain root? Perhaps that's my issue. Kingroot was quite new on jxd when I did it. Is there a better alternative
Sent from my SM-G900F using Tapatalk
I'm going to start including TowelRoot in the firmware, which is probably the best one I've found so far.
-
Or can you recommend a program i can run to reset the permissions on sdcard1 which is my ext card.
Sent from my SM-G900F using Tapatalk
If your card is Fat based, the permissions should reset on a remount. You may need to insert the card in your PC or Mac and run a file system check on it.
-
It's fat32 and it seems to be the pc causing it, I copied 2 films to via sd card reader but had no permission to delete once back in jxd.. weird eh?
Sent from my SM-G900F using Tapatalk
-
It's fat32 and it seems to be the pc causing it, I copied 2 films to via sd card reader but had no permission to delete once back in jxd.. weird eh?
Sent from my SM-G900F using Tapatalk
The JXD is probably mounting the card funny. If you've rooted the device, open a terminal and see if you can remount the card re-writable.
-
What's the command to do that
Sent from my SM-G900F using Tapatalk
-
Oh I should add, once I changed permissions I was able to delete them.
Sent from my SM-G900F using Tapatalk
-
I have tried the sd card, in NTFS format, and it works, but there are also no write permissions, in NTFS. And you can not delete content from the jxd.
Is there any way to make that work?
-
LordDavon, I am wondering if I could ask you a favour. I have received my S192 back from repair for the yellow light of death. (although I suspect they did not repair my console but have simply sourced a second hand unit and given it to me as a replacement) although my s192 now turns on I have noticed a rather strange problem. it would appear that whilst using the console it randomly starts repeating d-pad pushes (mainly down and right directions) which results in an unusable console. I have to shutdown and turn it back on to use it again. ie) once it starts happening it wont stop. upon reboot the d-pad controls work properly but sooner or later it will start happening again. However if I double tap to show what apps are currently running there always seems to be the keymapping app running from startup. if I swipe up and close it the problem so far appears to disappear. I would like to try some more testing so I want to ask if you could compile a version of your firmware with the keymapping app removed? after waiting 6 months to get my console back I don't want to have to go through the whole problem of returning the console for repair if I can avoid it.
Thanks Pottzman
-
...
I would suspect that there is an issue with the mapping, rather than the app. Have you tried doing a factory reset on the unit? If that doesn't fix the issue, a reflash of the firmware may correct the issue.
As well, I think there is a way to disable the app in the settings, if I remember correctly. I am in the warehouse right now trying to get the holiday orders ready, but will look tonight when I have my unit.
-
Hi LordDavon,
Yes I have tried a reset. I have reflashed you firmware and the official firmware about 5 or 6 times. When I go to the settings to disable "keymapping" app the disable button is greyed out, thats why I'm asking if it would be possible for you to remove it from your firmware as I can not.
Thanks
pottzman
-
Hi LordDavon,
Yes I have tried a reset. I have reflashed you firmware and the official firmware about 5 or 6 times. When I go to the settings to disable "keymapping" app the disable button is greyed out, thats why I'm asking if it would be possible for you to remove it from your firmware as I can not.
Thanks
pottzman
The Keymapper option is grayed out? That's very strange. There is no reason for that. I am really thinking that you are having an issue with your NVRAM. That's telling me that something is really wrong in your system.
I have an earlier beta that doesn't have the mapper in it. I will see if I can find it.
-
Do you know if there would be an issue with removing kingroot from an already up and running system and installing the root you recommended to me above?
Sent from my SM-G900F using Tapatalk
-
The Keymapper option is grayed out? That's very strange. There is no reason for that. I am really thinking that you are having an issue with your NVRAM. That's telling me that something is really wrong in your system.
I have an earlier beta that doesn't have the mapper in it. I will see if I can find it.
I thought the reason it is greyed out is because it is installed as a system app and my device is not rooted so I can not uninstall system apps
-
I thought the reason it is greyed out is because it is installed as a system app and my device is not rooted so I can not uninstall system apps
Wait, I think we aren't on the same page. In Settings, there is a Gamepad section. One of the last options there allows you to disable the Game Mapper. When you said it was grayed out, I assumed that's the option you were referring to.
-
Do you know if there would be an issue with removing kingroot from an already up and running system and installing the root you recommended to me above?
Sent from my SM-G900F using Tapatalk
Not sure. It is worth giving it a try. Worst that can happen is needing to reinstall Kingroot.
-
Do you have a link to a trustworthy source for TowelRoot ?
Sent from my SM-G900F using Tapatalk
-
I found it but it didn't work, I clicked make it rain and it just sat there not doing anything so trying to re do kingroot now.
Sent from my SM-G900F using Tapatalk
-
Still looking for a viable root alternative,super su keeps saying I need to update but it keeps failing.
Sent from my SM-G900F using Tapatalk
-
there is an application pay one called SuperSumi pro to remove Kingroot and install Supersu
-
I have to pay for super sumi ?
Sent from my SM-G900F using Tapatalk
-
does anyone know which files need to be modified, in order to fix the percentage of the battery?
-
can someone help point me in the direction to fix a s192. a friend gave it to me cause he jacked it up. it goes to bootloader options. i can scroll the optionsd with vol down button. but i cant select anything.
-
Question: How does one get an updated Shield Hub?
I have LordDavons Beta 0.53 but my Shield Hub shows up as 4.11.20782483.
How do I update Shield hub to like 4.12 or 4.13?
-
a question of ignorant, to the jxd s192, you can install a rom of the tablet shield? even if it has flaws?
because if it is installable, you can not take a rom marshmallow of the tablet shield, and taking the 2 source codes, copy and paste, the code necessary to make everything work correctly?
-
Here you have managed to make a rom nougat for the xiaomi mipad 1, with tegra k1.
https://forum.xda-developers.com/mi-pad/development/rom-resurrection-remix-n-v5-8-2-xiaomi-t3564793
How could I make a rom nougat, for the xiaomi mipad 1, tegra k1, without bootloader? Could you do the same for the S192?
-
Please note that this is no longer and active project and the author no longer has a unit to develop with.
-
Please note that this is no longer and active project and the author no longer has a unit to develop with.
I know it's discontinued, but I'm sure there are people who would know how to answer my questions, like what would happen if I try to install a rom file of the nvidia shield, is there a brick risk?
-
Sure, you will break it. differemnt hardware
-
I have spoken with the developer of the rom of the xiaomi my pad, and he has answered me that it is not necessary to ortho bootloader, which uses the same as kitkat.
here your message:
That's not how it works. Bootloader has nothing to do with the Android version. The Mi Pad uses the stock 4.4 bootloader to boot all the OSes upto Oreo.
It is not enough that your device has a Tegra K1. There are many device specific changes in the kernel and userspace that would need accounting for. You could use our work and the Nvidia Shield Tablet's work as a reference, but a lot of work would need to be done from scratch. I recommend you do intense research if you plan on doing anything about it.
-
Thank you very much Lord Davon! My device stopped working properly so i flashed your rom and now it works better than ever so thanks so much!
-
friends this version provided by LordDavon, is for the S192k with RK3288 processor, 64GB / 4GB ram?
-
friends this version provided by LordDavon, is for the S192k with RK3288 processor, 64GB / 4GB ram?
no, it's for the tegra k1 version.
-
no, it's for the tegra k1 version.
Thank you for keeping an eye on this. I've not been very active as of late. Just too busy trying to keep my business afloat. My computer crashed pretty hard too.
It was sad watching an Intel i7-4790K and ASRock Extreme6/ac kill each other. I ended up replacing it with a Ryzen 2700X and Gigabyte Aorus, which worked out pretty well, but required new RAM also -- RAM is so friggin expensive right now.
Anyway, thank you for having my back.