Home Artists Posts Import Register

Downloads

Content

Turns out GeForce Now only accepts "external" gamepads (connected via USB or Bluetooth) which is why it actively refused our "internal" gpio-wired gamepad.

We now tell the OS that our gpio-wired gamepad is actually connected via USB, which seems to be enough to make GeForce Now play nice... go figure.

In other news, we now also have two new options in System -> Buttons -> Extras, allowing people to manually exclude the D-pad and / or triggers from the axis translator.

If you encounter an app or game that doesn't pick up on the D-pad or L2 / R2 triggers, there's a good chance that toggling these options will do the trick.

Known offenders are Drastic & AetherSX2 (at the time of writing).

How to install: Unpack the attached files using 7zip and follow the included instructions found inside README.txt. For those simply upgrading, please enter "NO" when asked whether you want to wipe userdata!

For those needing the Google Play Store: The PowKiddy X18S is a read-only partition device, which means flashing Google Play app packages (via a recovery) isn't possible. Magisk is shipped out-of-box though, allowing the install of system-less Google Play packages like MagiskGapps. The included README.txt contains a section explaining how to.

For those needing root: Magisk is included out of box and only needs to be activated on first boot. Due to the boot partition being signed, in-app updates of Magisk will render the device semi-bricked. Long story short: Don't update Magisk! When a new Magisk update gets released I will make sure to release a new build containing it!

Changelog

  • The internal gamepad now works with GeForce Now
  • The D-pad can now be excluded from axis translation (toggle this on or off as needed)
  • The L2 / R2 trigger buttons can now be excluded from axis translation (toggle this on or off as needed)

Unfixable known issues (including fixable things that aren't up to me to fix)

  • The screen turns off while using HDMI output (PowKiddy uses this to hide the fact that their LCM/LCD rotation values are off, but there's little I can do to fix this unless someone at PowKiddy decides to send me the kernel sourcecode)
  • Updating Magisk or trying to uninstall it via the app semi-bricks the device because the bootloader expects signed boot images (don't do it)
  • The kernel wakes the device up every so and so minutes for a split second (its annoying, but there's little I can do to fix this unless someone at PowKiddy decides to send me the kernel sourcecode)
  • Some Antivirus tools falsely report X18STool.exe as a trojan (because it interacts with adb, fastboot and uname to get the things it needs to do done)

Files

Comments

Anonymous

Hello Again, I think im stuck at the fastbootd screen it doesnt show that its loading anything. it jsut sits saying its waiting for device [INFO] userdata has been formatted! [INFO] Rebooting device into dynamic bootloader... [INFO] Waiting for device...

Anonymous

Yeah, just noticed it, its flashing now, thx for the support!! And sorry for bad english, im from Brazil

Anonymous

I want to say thanks for the update, I've never had an update go so smoothly. Appreciate it. Also, I noticed in the readme file that the windows instructions say to follow the onscreen prompts. On the X18S screen at one point it hilights a line that says "reboot now" or something like that, and I was tempted to actually press it per the instructions, but on my PC it looked like it was still writing the update, so I didn't. Glad I didn't. Just a little confusion that may inspire you to clarify the readme a bit. It was really smooth otherwise. 👍🍺👍

Anonymous

brilliant!!

Anonymous

I'm updating from beta 4 and get the following error [INFO] Signing identifier token... Unhandled Exception: Org.BouncyCastle.OpenSsl.PemException: problem creating RSA private key: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Any ideas?

blackseraph

That's a new one... Truth be told no, I don't know why this is happening on your end. Maybe your system clock is off. SSL tends to fail if the local system time isn't correctly set.

Anonymous

It seemed like Windows hiccuped. Reboot fixed it. Thanks

Anonymous

Its like and engineer mode, where you can test stuff on the phone, before the update it was clicking on the kernel 7 times(likethde dev mode), and just in case I forgot, thanks for the update and for the awesome work you've been doing for the community.

Anonymous

Are there any guides on installing from PC for a potentially bricked device?

blackseraph

Unpack the image with 7zip. You'll find a README file inside explaining all the steps.

Anonymous

Thanks for your hard work - was able to successfully get your LineageOS release on my new X18S. Any tips on how to enter safe mode? I'm not having success with the button combo (not sure if I'm hitting the vol button too soon after power or what but I either end up with the system doing nothing or booting normally)...trying to get the gapps on it for play access.

blackseraph

You don't need to enter any kind of safe mode to do so. Read the included readme on how to get the play store installed first.

Anonymous

Ah - ok, thanks! Mind went directly to the regular Lineage workflow.