Author Topic: [ROM] LegacyROM 1.0 GPD Q9 (Also compatible with new Q9PSV batch) (Read 29167 times)

skelton · « **on:** July 09, 2015, 09:43:50 am »

Deleted

fetarius · « **Reply #1 on:** July 09, 2015, 12:37:50 pm »

Awesome, thanks for this. It looks a lot like what I'm running on my Q9 now, except for your custom kernel. I noticed after bumping to 2.1.0 my Q9 is running at 1.6GHz (via CPUZ for Android). I'm starting to think that the drop to 1.4GHz may have been a bug or to temporarily work around one.

skelton · « **Reply #2 on:** July 09, 2015, 12:53:18 pm »

Quote from: fetarius on July 09, 2015, 12:37:50 pm

Awesome, thanks for this. It looks a lot like what I'm running on my Q9 now, except for your custom kernel. I noticed after bumping to 2.1.0 my Q9 is running at 1.6GHz (via CPUZ for Android). I'm starting to think that the drop to 1.4GHz may have been a bug or to temporarily work around one.

CPU-Z report 1,6 ghz because is set in kernel, but max speed should be 1,4 ghz in 2.1.0 too. Or at least my device didn't allow me to go over 1,4 ghz using setcpu in 2.1.0. In fact I didn't notice difference between 2.1.0 or 1.1.3 for example.
GPD hardcoded DVFS values so that device won't go far from 1,4 ghz even though kernel report a higher value. No big difference between running at 1,4 or 1,6 ghz though. My kernel reports 1,8 ghz, but I am using a limitation to 1.6 ghz, because more than that my device was not stable even with highest voltages.

HobbsWon · « **Reply #3 on:** July 10, 2015, 04:21:24 am »

Do you think the ragingmolasses governor is sufficient enough for regular emu use? For example, the most intensive game I'd be playing is possibly Gran Turismo for epsxe. (Even though Gran Turismo juiced every last drop of processing power from the PSX)..

skelton · « **Reply #4 on:** July 10, 2015, 08:32:19 am »

Quote from: HobbsWon on July 10, 2015, 04:21:24 am

Do you think the ragingmolasses governor is sufficient enough for regular emu use? For example, the most intensive game I'd be playing is possibly Gran Turismo for epsxe. (Even though Gran Turismo juiced every last drop of processing power from the PSX)..

I use it just for 8 and 16 bit. With epsxe seemed good enough in the games I played, but I have never tried Gran Turismo.

Anyhow, ragingmolasses is just another governor, if it's not fast enough, you can select interactive or ondemand. The other governors are also present. Interactive is the defaukt one like in stock firmware.

lobski · « **Reply #5 on:** July 14, 2015, 08:07:11 am »

Is this based on the Q9 Official Firmware v2.1.0? Should I stick with this or the official? I am a power user.

skelton · « **Reply #6 on:** July 14, 2015, 08:13:01 am »

No, it's built from source. About which one to use, both firmware are ok. It depends on your needs.

sirp0p0 · « **Reply #7 on:** July 17, 2015, 08:05:17 pm »

I CLICKED RESTORE AND THE FLASH FAILED WITH "LOWERFORMAT FAILED" AND I DIED A LITTLE.

Clicking restore again did actually work. I was heartbroken thinking I'd bricked my new toy. Any idea why this happened?

DON'T PANIC is a very important mantra to have.

Here's the log if its of any use:

Code: [Select]

14:43:17 637 Rockchip Batch Tool v1.7.1.1 start run
14:53:55 771 **********Restore Start Total<1>**********
14:53:55 774 <Layer 2-7> Test Device Start
14:53:55 778 <Layer 2-7> Test Device Success
14:53:55 780 <Layer 2-7> Lowerformat Device Start
14:54:04 783 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=13,read=0
14:54:09 983 Error:RKU_ClearBuffer-->totalRead=0
14:54:14 984 Error:RKU_Write-->WriteFile failed,bRet=1,err=0,size=31,write=0
14:54:20 185 Error:RKU_ClearBuffer-->totalRead=0
14:54:20 185 <LAYER 2-7> ERROR:LowerFormatDevice-->RKU_TestDeviceReady failed,subCode(0x0),RetCode(-3)
14:54:20 189 <Layer 2-7> Lowerformat Device Fail
14:54:20 191 **********Restore Done Success<0> Fail<1> Time<24414>ms**********
14:56:31 771 **********Restore Start Total<1>**********
14:56:31 775 <Layer 2-7> Test Device Start
14:56:31 778 <Layer 2-7> Test Device Success
14:56:31 781 <Layer 2-7> Lowerformat Device Start
14:56:45 787 <Layer 2-7> Lowerformat Device Success
14:56:45 790 <Layer 2-7> Test Device Start
14:56:45 793 <Layer 2-7> Test Device Success
14:56:45 796 <Layer 2-7> Check Chip Start
14:56:45 799 <Layer 2-7> Check Chip Success
14:56:45 803 <Layer 2-7> Get FlashInfo Start
14:56:45 805 <LAYER 2-7> INFO:FlashInfo: 0 0 9 1 0 20 20 28 20 2 3
14:56:45 808 <Layer 2-7> Get FlashInfo Success
14:56:45 813 <Layer 2-7> Prepare IDB Start
14:56:45 814 <LAYER 2-7> INFO:CS(1)  (8480MB)  (HYNIX)
14:56:45 815 <LAYER 2-7> INFO:CS(2)  (8480MB)  (HYNIX)
14:56:45 826 <Layer 2-7> Prepare IDB Success
14:56:45 831 <Layer 2-7> Download IDB Start
14:56:47 996 <Layer 2-7> Download IDB Success
14:56:48 001 <Layer 2-7> Reset Device Start
14:56:49 006 <Layer 2-7> Reset Device Success
14:56:49 010 <Layer 2-7> Wait For Loader Start
14:56:50 299 <Layer 2-7> Wait For Loader Success
14:56:50 306 <Layer 2-7> Test Device Start
14:56:50 311 <Layer 2-7> Test Device Success
14:56:50 317 <Layer 2-7> Download Firmware Start
14:58:39 066 <Layer 2-7> Download Firmware Success
14:58:39 103 <Layer 2-7> Reset Device Start
14:58:40 108 <Layer 2-7> Reset Device Success
14:58:40 112 **********Restore Done Success<1> Fail<0> Time<128342>ms**********

skelton · « **Reply #8 on:** July 17, 2015, 09:04:10 pm »

Probably a bad connection with the cable. Sometimes the cable that comes with the device is not of very good quality.

procyon · « **Reply #9 on:** July 27, 2015, 03:39:02 pm »

I just wanted to write to thank you very much for this work Skelton. I went from 1.07 stock firmware to this, and I'm very happy with it.

Just a note to others who may install this so that you don't repeat my mistake; I backed up everything with Titanium Backup, but I saved those backups to internal. So when I installed the firmware, I wiped my backups

It's my own fault, I should have known better, I just didn't think it through. Make sure you back up to external SD before you attempt to install this firmware. It's definitely worth it.

skelton · « **Reply #10 on:** July 28, 2015, 08:49:23 am »

I have been playing a little bit with kernel, and after adjusting voltage and playing with dvfs I got 1,8 ghz stable. At least is stable on my unit.

However, in my opinion it's not worth to overclock like that. Difference in performance is quite minimal (Rk3288 cpu is not very powerful) and battery drains a bit faster. Also, have in mind that RK3288 has a cpu temp flag that reduce speed to 1,4 ghz if device gets over 80 Celsius to avoid overheating.

Anyhow, if someone wants a version of the rom with 1,8 ghz unlocked let me know and I can upload them,
I hope I can get the same thing with GPD XD, if GPD wants to collaborate with me of course.....

Mokura · « **Reply #11 on:** August 27, 2015, 07:19:36 pm »

Having some strange issues with the analog sticks. On a brand new install of LegacyROM, Game Controller Test (https://play.google.com/store/apps/details?id=com.catalyst06.gamecontrollerverifier) as well as other emulation apps are reporting the following:

PlayStation 3 controller:
Left stick up -> left
Left stick down -> right
Left stick left -> up
Left stick right -> down

Right stick up -> down
Right stick down -> up
Right stick left and right function normally. All other buttons function normally.

It might have something to do with the key mapping files in /system/usr directory, I can give it a look and see if there's anything I can do about the PS3 controller entry.

skelton · « **Reply #12 on:** August 27, 2015, 07:29:49 pm »

Most probably is a hardware issue in your device. I tested that app just on mine and it's ok. Analog works ok in mine.

Also, all emus and android games are fine with analogs in my device.

Try it with stock firmware, but it shouldn't make any difference, because joystick driver is the same in all firmwares.

My guess is that the analogs of your device don't work as they should, because as I say, testing it in my device it works ok in all directions.

Mokura · « **Reply #13 on:** August 27, 2015, 07:35:30 pm »

I tried installing the official firmware 2.1.0 and had the same issue, actually.

skelton · « **Reply #14 on:** August 27, 2015, 07:37:34 pm »

Quote from: Mokura on August 27, 2015, 07:35:30 pm

I tried installing the official firmware 2.1.0 and had the same issue, actually.

Then it's defintely a hardware issue. Try to contact your seller for an exchange, because it's clearly defective.

Mokura · « **Reply #15 on:** August 27, 2015, 09:33:11 pm »

Actually, I've got this almost solved. There's some weirdness in /system/usr/keylayout/Generic.kl, and with some twiddling of axis settings, I've got the left analogue stick functioning properly again. Up and down are semi-functioning properly, but AXIS_RZ seems to be centering at 1.0 instead of 0. Here's my settings (at the end of Generic.kl):

Code: [Select]

axis 0x00 Y
axis 0x01 X
axis 0x02 Z
axis 0x03 LTRIGGER
axis 0x04 RTRIGGER
axis 0x05 invert RZ
axis 0x06 THROTTLE
axis 0x07 RUDDER
axis 0x08 WHEEL
axis 0x09 GAS
axis 0x0a BRAKE
axis 0x10 HAT_X
axis 0x11 HAT_Y

If you could share your Generic.kl file for study, that would be helpful. Thank you for your work!

skelton · « **Reply #16 on:** August 27, 2015, 09:48:51 pm »

My generic.kl file is the same as yours before you modified, because all values for joystick are directly in kernel. Anyhow this is the file, but it's the same one of the stock firmware.

https://mega.nz/#!5wZnUZLZ!SyvJI7v_i1pVtD0zgjENFqdscXMnlQEBgZXAh2eJ8HA

Another option is using Tincore in gamepad mode and maybe you can set right analog in a different way.

But if you have a defective device, I think it's better just to talk to your seller and change the device rather than modifying this way, because probably some games won't recognize well at all even changing kl, because some games don't read kl files at all.

Mokura · « **Reply #17 on:** August 27, 2015, 09:53:50 pm »

Yeah, you're probably right, but I wanted to do pretty much anything I can before I shell out the money for return shipping. Just waiting on the word from the seller. Thank you anyway.

EDIT:
It's strange, but out of sheer stubbornness I was testing various firmwares from the Q9 review thread, and got linked to this Baidu directory (http://pan.baidu.com/share/home?uk=389368662#category/type=0), where the Q9PSV-EN 5.0.0 firmware seems to have my analog sticks functioning correctly. Maybe that one had the proper kernel?

skelton · « **Reply #18 on:** August 28, 2015, 08:16:07 am »

The joystick driver should be the same. The only thing that comes to my mnd is that there is a different batch that requires a different firmware. Not the first time that GPD do something like that.

skelton · « **Reply #19 on:** August 30, 2015, 04:01:10 pm »

GPD has confirmed me that there is a new batch that use different analog with different values, so my ROM is not compatible with it, because they have made an update to kernel. It's basically the problem Mokura had in the previous post.

So anyone with issues wirh analogs after flashing my firmware will have to install this stock firmware:

http://pan.baidu.com/s/1pJn9nAj

If you want to know if your device is a new batch, check settings/about device. If the build number says Q9PSV instead oj just Q9, then it's the new batch.

I don't know what GPD changed in kernel (I can imagine but I cannot test new batch), so users with this batch won't be able to use my firmware, because most probably I won't update it anymore. Sorry about that, but this way of acting by GPD with new batches etc.... is a pain in the ass for a dev with no time xD.

Author Topic: [ROM] LegacyROM 1.0 GPD Q9 (Also compatible with new Q9PSV batch) (Read 29167 times)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)

skelton (OP)