Dingoonity.org

Hi all,

Here is an Android 7.1 for GPD XD:
- v4 https://we.tl/QZVjd1QWe8 (see #3 for older versions)
- Play Store: https://we.tl/yzZZ2mKb27 run install.sh (linux-only script, sorry)
Kernel source: https://github.com/phhusson/linux/tree/gpdxd-rk3288-7

Please note that this is HIGHLY EXPERIMENTAL.
Many things are not working, and I don't expect this ROM to be usable for day-to-day.

Things that work:
- Vulkan
- Adoptable Storage on microSD
- Audio out
- ...

Things that don't work:
- No Gamepad mapping tool
- DDR scaling

Known quirks:
- Bootloader doesn't support the screen, so you'll most probably see weird images at boot.
- WiFi doesn't survive a suspend, you need to reboot after a suspend to get Wifi back
- Sometimes the screen doesn't power up, though the backlight does. Don't worry, unplug your GPD XD, power it off for 30s, and power it back on. It should be good now.

ChangeLog:
v4:
- Enable suspend

v3:
- Fixed power button
- Fixed audio output (speaker and headphones)
- Forced permanent wake lock. No suspend, but no suspend crash either
- Fixed battery gauge

v2:
- Works on legacy flash tool
- LCD fix
- 1GB /system instead of 2GB

Have fun! And if you find this useful, tell me, so I keep working on it
(Also I'm curious about the usage of Vulkan, I haven't seen much except demos, so if it's useful for you, please tell!)

Ok, this behaviour means you need a more recent rockchip flashtool. (like one which is able to flash an rk3399 should be good)
I can make an image which works with older versions of rockchip flashtool, but it makes the image bigger, takes more time to flash, ...

I used RockchipBatchTool 1.8 which I think is the latest. Maybe I can use RK3xxx to repack it and try again.

As soon as I'm done backing up my stuff I can try flashing it with the upgrade tool for linux maybe that works.

If you want to change to ext4 version let me know. (it's easy) You can basically reinstall Legacy as an update and it will just change it with no changes to user data. Then you can flash twrp. Flashing recoveries takes like 2 seconds.

Just cause I like twrp better hehe.

yup I too prefer TWRP and ext4 is also pretty good to have. (ext3 is pretty old and ext4 has been the standard in linux for a while)

I just unpacked that update.img and it contains uboot (rockchip open source bootloader found on tvboxes for instance) and I remembered this:

The bootloader in rk3288 tablets is different from rk3288 tvboxes. If you flash the wrong bootloader from a tvbox you will brick it. Unfortunately, bootloader is close source, so nothing you can do. You would also need to make a ramdisk for linux, the one included in the xd won't work. But you don't.miss anything, i have run ubuntu in a tvbox and runs very poorly, bad performance and bad GPU Support, so cannot be used to emulate anything better than Android.

The bootloader in the xd is the allminiloader versi?n 2.2.5

So... wrong bootloader? would explain why it won't boot at all. Allthough the image also contains the miniloader.
seems I'm on the wrong track.

Almost forgot, Commander flash this zip : http://www.sectioneight.net/s8files/gpd/tools/TWRP-theme.zip

It will fix the twrp resolution. It will make a folder on your sd card and save it there: /TWRP/Theme I think.

cool I'll remember that when flashing back to legacy

UPDATE: well strike that. repacked the firmware and flashed and now the XD seems completely FUBAR. won't boot up, won't get into recovery, cannot get into flashmode - completely hardbricked. something must've gone really wrong. Maybe I can find a way do get into maskrom mode and fix it, if not I got a nice paperweight.

As for the brick, the device can be in three states:
- powered on/suspend ==> long press on power button for 15 seconds to power off
- powered off ====> keep pressing volume+ button and plug USB cable
- battery drained ====> well same thing, though possibly it will need some time to raise above lower battery voltage limit

As for flashing, while you're unpacking, you can do simg2img system.img, this will make it compatible with your flashtool.

Quote from: CommanderKitler on September 26, 2017, 04:16:05 am

Quote from: PsyOps on September 26, 2017, 04:01:18 am

What exactly did you do?

Maybe the battery drain method could save it.

Well I unpacked the update.IMG and then repacked it using imgrepackerrk and then flashed it again with androidtool 2.3(seems i've messed something up there)  . flashed without problems and bam: green led of death. thought to myself "ok no biggie just power down, press vol+ and plug back in" and green light again. darn. kept it connected to the pc and pressed vol+ and power and got a green light again. vol- and power; green light. hooked up to the power adapter; green light. looks pretty bad, bricked a lot of android devices in my days and recovered all of them but this looks pretty bad. I doubt that draining the battery will do much in this case and that could take a while with nothing going on in the device except a green led glowing.

Also my pc doesn't recognize it at all. It's not even showing up in the device manager.

UPDATE: looks like some files got mixed up when I unpacked the legacy rom to compare it so it has probably has the wrong bootloader now. mea culpa. thats pretty much a hardbrick. the only thing that might fix it is maskrom mode but I don't even know if that works on the XD and even if it works I have to teardown the device to short the pins on the motherboard. biggest problem is finding out wich 2 pins to short to enter maskrom mode.

When you connect yout XD to BatchTool, do you see a blue light instead of green? If that's the case you are in mask rom mode, probably because of a bad bootloader. You would need to shortcircuit nand, generaly even if you don't know what pins, just using a paperclip through all pins should do the trick, and make the system go to loader mode to reflash stock, legacy or the firmware you use.

nah it's basically like a normal softbrick but it will not go into flashmode when connected to the PC or ligth up red when connected to the charger.


I disassembled the XD yesterday (don't try that at home kids) the biggest problem is gonna be getting to the NAND. couldn't take a look at the front of the motherboard because it is fixed in place with tiny little screws so I need to buy a small electronics screwdriver kit. also I have taken a couple of looks at photos of the motherboard and I can't see the NAND chip on there.

https://imgur.com/kfoe93Q

If it's under the the RF shielding covering most of the board, I'll have to get some acetone and desoldering braid to desolder and re-solder the whole thing. I'll see to that next week and probably post an update. I got a friend who does a lot of electronics tinkering maybe he's got the tools to do this. Gonna open a dedicated thread for this though as this is getting offtopic and if i succeed, some in-depth documentation could be useful for people running into the same problem.

About the kernel, there are things different from mine, joystick driver is different (no adc.js which I use in my kernel) so no ps3/xbox/null modes I guess.

Yup, I'd like to be able to push GPD XD support into Linux mainline, so no ps3/xbox emulation will be allowed.
Though, what I'm currently trying to do, is to make an Android application handle all gamepad => game stuff (either ps3/xbox emulation, or touchscreen emulation, ...)
This way it will work on all (rooted) Android devices/gamepad, not just GPD XD

My feeling is that this ROM is made using or porting firefly RK3399 SDK to RK3288. As far as I know, RK3288 SDK for nougat is beta and full of bugs, even the RK3399 is full of bugs. But that's just my guess. The maker of this rom is the one that can explain which one is using, because I only see kernel but not a device tree, so I suppose is firefly SDK and not aosp, but no idea because I don't have an XD to test or to help with the development

Well, that's not exactly firefly's rk3399 SDK, that's from another private SDK, but it looks really close.
I'll try to make something that works based on firefly rk3399's SDK, so that I can share all my changes.
So thanks for pointing me to this direction :-)

For the details of the work needed:
Rockchip dropped support for the PMIC, the WiFi chip, the audio chip, the touchscreen of the GPD XD.
For all of those, the code is actually there, but hasn't been updated for Linux 4.4

For the PMIC, I've actually sent mainline a basic support, so that's what I've integrated there.
It's still missing a lot. I'll keep working on the PMIC anyway to get a better mainline driver,
but I think it would be much faster to get a fully working device if someone just fixes Rockchip's code for it.

For the WiFi chip, I did some changes to make it build, changed a build init logic, and it seems to work, but I'm expecting bugs.

For audio, the good thing is that rockchip moved to a mainline method, and that our codec is supported in mainline!
So only minor configuration changes are required.

For the touchscreen, it has mainline support, I just had to enable it in kernel config \o/

For accelerometer, there is both a rockchip and mainline support. I need to switch to rockchip support, so that it works in Android.

For those who want to compare my kernel to rockchip's, do the delta with https://github.com/rockchip-linux/kernel branch release-4.4
You'll notice there are actually really little changes.

How about you CommanderKitler? any update on your situation?

As I said, I gonna open up a new thread if find I anything groundbreaking.

Only thing I can confirm right now is that draining the battery doesn't help in any way. Not a surprise though as I had it hooked up to the PC without the battery out of curiosity when I opened it up earlier and even then the only thing happening was the green led. The only thing interesting is that it does take a while for the green light to come up when the battery is drained (probably because it needs to have a certain charge to power up) but it comes up instantly without the battery installed. Maybe that's a quirk of the rk3288, usually most android devices don't respond at all when the battery is not installed.

The electronics guy I know is on holiday right now but he should be back next week so I gonna see to that then. Sucks that I messed up my XD but this could be an interesting opportunity to get some more information about the device. Anyways, don't worry, I gonna keep you guys in the loop .

Ok ok I'll make a non sparse-image...

Here it is:
http://dl.free.fr/mzOZDYNBB

Ok ok I'll make a non sparse-image...

Here it is:
http://dl.free.fr/mzOZDYNBB

We would love you to keep working on this and get it working perfect gpd xd needs a updated rom bad there are many users out there inc me.I am willing to donate if we can get this at least a usable state and i am sure many will follow keep up the great work great project.