Post by: 02k0 on December 26, 2019, 03:55:29 am
Apparently, it's Runs Nes, Snes, MD, GBA and Mame.
Possible Firmware update for it's?
Link: https://a.aliexpress.com/OtcGD9zW
Worth??(https://uploads.tapatalk-cdn.com/20191226/5f2427725f9a0e062dd860584181c1cb.jpg)(https://uploads.tapatalk-cdn.com/20191226/3530b400be8a9eb31289498ab73824d1.jpg)(https://uploads.tapatalk-cdn.com/20191226/97c62963f11f2382045842edc7b1b441.jpg)
Post by: Qinti on December 29, 2019, 01:18:57 am
Post by: 02k0 on December 29, 2019, 03:10:42 am
This is an RS-69 clone, with two added buttons. SNES would be a quasi no go, some Genesis might play at bearable frame rates, NES will be almost perfect, GBA will be a lot more playable now that (hopefully) it has L and R mapped, and Arcade games compatible will be pretty much the same (but Street Fighter will be more playable albeit with frameskip). Issues with SNES and Genesis are frameskip that can range from bearable to slideshow, layer priority issues with SNES that made games unplayable (no transparency, and some layers are hidden behind others, so some Mario enemies are behind backgrounds but can still kill you, and Zelda is unplayable). Very low arcade compatibility, it pretty much is only compatible those arcade roms it comes with. Button mapping is all over the place, with no remapping options available. Only way to save is via the save states, but the save states are compatible with other emulators (I can share save states between my RS-69 and my Retromini, for example). I got one because I want to see how the extra two buttons are wired, so that maybe I can add them to my RS-69. Buy it mainly as a NES and GBA machine if you will, but for 8-10 USD more you have the Pocket Go.Dude you're great! I thought the console was good, it's pretty cute, too bad it doesn't work well. You could do a Reviews, what do you think?
Enviado de meu moto g(7) play usando o Tapatalk
Post by: 02k0 on December 29, 2019, 04:23:47 am
Enviado de meu moto g(7) play usando o Tapatalk
Post by: Qinti on December 29, 2019, 06:14:33 pm
Post by: 02k0 on January 03, 2020, 06:15:35 am
This is an RS-69 clone, with two added buttons. SNES would be a quasi no go, some Genesis might play at bearable frame rates, NES will be almost perfect, GBA will be a lot more playable now that (hopefully) it has L and R mapped, and Arcade games compatible will be pretty much the same (but Street Fighter will be more playable albeit with frameskip). Issues with SNES and Genesis are frameskip that can range from bearable to slideshow, layer priority issues with SNES that made games unplayable (no transparency, and some layers are hidden behind others, so some Mario enemies are behind backgrounds but can still kill you, and Zelda is unplayable). Very low arcade compatibility, it pretty much is only compatible those arcade roms it comes with. Button mapping is all over the place, with no remapping options available. Only way to save is via the save states, but the save states are compatible with other emulators (I can share save states between my RS-69 and my Retromini, for example). I got one because I want to see how the extra two buttons are wired, so that maybe I can add them to my RS-69. Buy it mainly as a NES and GBA machine if you will, but for 8-10 USD more you have the Pocket Go.Have you tried to install custom RS-90 firmware on it? It may work.
Enviado de meu moto g(7) play usando o Tapatalk
Post by: 02k0 on January 18, 2020, 03:49:18 pm
https://youtu.be/zB-7_1FVd1U
Enviado de meu moto g(7) play usando o Tapatalk
Post by: Qinti on February 06, 2020, 04:31:50 am
Ok, so I got mine, and it is not a simple rebrand of the RS-69. Yes, it uses the same OS and emulators, so it has the same base compatibility issues (same ROMs not loading, and the same layer priority issues for SNES), HOWEVER, it does not use the same chip (FC100s), it uses a different chip which I have been unable to identify yet. As a result, it has better performance on GBA ROMs (it used to have random frame skips), very playable performance for the most part on Genesis ROMs (it used to have nasty frame skip, now it seems to run between 80-90% speed, which while noticeable, does not bother much), much less frameskip in Arcade ROMs (goes from somewhat playable to quite playable), and less screen tear in NES ROMs (goes from looking like the screen is made of sloshing water to almost unnoticeable screen tear (and I am quite sensitive to it). Add to that the fact it has 6 action buttons makes for better gameplay.
As no device is perfect, especially Chinese devices, here come the cons:
- The D-Pad is absolute crap. It registered 2 of 5 diagonal presses. I modified it by opening the console, and cutting the 4 tabs it had on the diagonal axis (no idea why it had those), then using moldable compound to add approximately 2-3mm to the ball pivot it has. The result is that now all diagonals now work, and the increased height of the ball pivot prevents pressing all 4 directions at once.
- The screen has a "bad" viewing angle. I say "bad" because it will only bother you at the beginning, and will be noticeable if you keep putting it to the side just to remind yourself how much you hate those angles. The thing is, it looks ok at the angle you are supposed to play. Not the best screen, but I have seen worse and much worse.
- The menu button is gone, and now you have to press the select button for a few seconds to active the menu to exit or save and load states. Add to this the fact that using this menu is the only way to save (it doesn't create save files for those games that save), and the fact that some games use the select button for some functions and it can be a bit of a hassle.
- There is no volume rocker, only a volume button that goes up. So you have to press it to go louder and louder until it goes mute, then gets louder again. And it resets every time you turn off the machine. I saw some circuitry that could allow for the installation of a volume rocker, but then you would need to change the ON/OFF switch. Ugh...
- It does have an indicator LED, but it is hidden inside the machine. So you cannot tell if it is charging, if it has finished charging, if it managed to turn on, etc. Now, this might not be a problem for some people, but I would have preferred the LED be visible.
All in all, it's not bad. But... at 18-20 USD, it is in Bittboy V3.5 territory, and for 9-12 USD more you can get a Pocket Go, which is a much better machine. As I have got it already, I am going to use it as a cheap handheld on the go. If it breaks, it won't hurt as much as it would if my Bittboy or Pocket Go died. The ideal price point for a machine such as this is 15 USD maximum. If you can get it for that price, I recommend it if you need something to use on trips where you fear a more expensive machine might not return from. Hopefully the advent of machines such as this will push back those NES clone handhelds back to their original 5-9 USD price points.
If you want to know about ROM compatibility, think it similar to those of the early emulators of the DOS days, aka Nesticle, Genecyst, and whatever it's contemporary for the SNES was. This includes not just ROM compatibility, but sprite and layers issues it may have had as well.
Also, never buy something hoping there is custom firmware. Chances machine will get custom firmware are almost nil. Only reason those machines that did get custom firmware, was that they had a derivative of Open Dingux to begin with. So if you can't understand the difference between that and how machines work, my advice is to stick to WELL KNOWN MACHINES THAT ALREADY HAVE CUSTOM FIRMWARE. As such, I won't test games of any sort, not check if any CFW will work on it, as I believe I have provided sufficient information in this and my previous posts for people to know whether they still want this or not, and am sufficiently satisfied with how it works.
Post by: kevin_yamagata on May 01, 2020, 10:45:07 pm
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Post by: Qinti on May 04, 2020, 01:24:23 am
Edit: I did mod the d-pad though, necessary to have proper control. So if it fixes SNES and has a better d-pad, then it might be ok. The Pocketgo is a better buy for a bit more though. Heck the Bittboy is better and not difficult to mod and add L and R buttons IF you have the tools, but for the money spent modding might as well just get the Pocketgo.
Post by: kevin_yamagata on May 07, 2020, 12:53:56 am
Post by: 02k0 on May 07, 2020, 12:59:19 am
Thanks, man! I bought him and i still waiting for the sending, maybe not are a bad thing, you know? I paid 17 USD in the end, very cheap. But i wish try install some firmware on him, maybe the RS-07 CFW, just for test, who knows? The name "Open Source Arcade" on the box will have to make sense hahahaI intend to buy one of these, but I'm afraid it won't do much. These days I ordered an X6 Game console and two PAP KIII Plus (in case one doesn't work). I intend to buy an Odroid Go Advanced 2, more ahead.
Enviado de meu moto g(7) play usando o Tapatalk
Post by: kevin_yamagata on May 07, 2020, 12:11:20 pm
Post by: 02k0 on May 11, 2020, 08:16:32 pm
https://mega.nz/file/l8sBnBYI#ZjDx-lNzlNqa9d_qEmhn1TWEyKRfjZduliTGxJIkxrE
Password: DjvanbeatYT
Credit's: Djvanbeat
The firmware for this device is stored inside the MicroSD card. It would not be very difficult (for those who understand modifications) to modify it to add new emulators.
Post by: kevin_yamagata on May 12, 2020, 03:22:56 pm
Post by: Qinti on May 20, 2020, 04:05:56 pm
Post by: Djvanbeat on June 04, 2020, 05:33:53 pm
Here the Backup Firmware:
https://mega.nz/file/l8sBnBYI#ZjDx-lNzlNqa9d_qEmhn1TWEyKRfjZduliTGxJIkxrE
Password: DjvanbeatYT
Credit's: Djvanbeat
The firmware for this device is stored inside the MicroSD card. It would not be very difficult (for those who understand modifications) to modify it to add new emulators.
Hello! ,i'm Djvanbeat , the creator of this backup file (with any other games i tested aroud 3k games but only 120 works), this is not a firmware ,the firmware is only inside of this console eprom memory.
i open this and see a possible backdoor for see this in ttl mode betwen a usb ttl cable.
im now in working of this investigation.
regards.
Post by: kndcds on June 04, 2020, 06:06:24 pm
Cool, good luck. Would you have the list of games that worked on it?Here the Backup Firmware:
https://mega.nz/file/l8sBnBYI#ZjDx-lNzlNqa9d_qEmhn1TWEyKRfjZduliTGxJIkxrE
Password: DjvanbeatYT
Credit's: Djvanbeat
The firmware for this device is stored inside the MicroSD card. It would not be very difficult (for those who understand modifications) to modify it to add new emulators.
Hello! ,i'm Djvanbeat , the creator of this backup file (with any other games i tested aroud 3k games but only 120 works), this is not a firmware ,the firmware is only inside of this console eprom memory.
i open this and see a possible backdoor for see this in ttl mode betwen a usb ttl cable.
im now in working of this investigation.
regards.
Post by: kevin_yamagata on June 04, 2020, 10:06:08 pm
Here the Backup Firmware:
https://mega.nz/file/l8sBnBYI#ZjDx-lNzlNqa9d_qEmhn1TWEyKRfjZduliTGxJIkxrE
Password: DjvanbeatYT
Credit's: Djvanbeat
The firmware for this device is stored inside the MicroSD card. It would not be very difficult (for those who understand modifications) to modify it to add new emulators.
Hello! ,i'm Djvanbeat , the creator of this backup file (with any other games i tested aroud 3k games but only 120 works), this is not a firmware ,the firmware is only inside of this console eprom memory.
i open this and see a possible backdoor for see this in ttl mode betwen a usb ttl cable.
im now in working of this investigation.
regards.
Thanks for this!
Post by: kndcds on June 07, 2020, 09:11:28 pm
https://a.aliexpress.com/_dUNGGeu
Post by: kevin_yamagata on June 08, 2020, 12:23:15 pm
Better Clone?
https://a.aliexpress.com/_d7YOYnk
**Edit it has a volume controller and usb type c input, now it looks like a new model same.
I found this ugly, I prefer the first model, looks like more a game boy, but its ugly too lmao
Post by: kndcds on June 09, 2020, 01:06:18 am
Indeed, but is it that the emulation quality has improved? The way is to wait for the Review on YouTube.Better Clone?
https://a.aliexpress.com/_d7YOYnk
**Edit it has a volume controller and usb type c input, now it looks like a new model same.
I found this ugly, I prefer the first model, looks like more a game boy, but its ugly too lmao
Post by: kevin_yamagata on June 20, 2020, 11:39:20 pm
Snes emulator:
He have some improves on the layer issues, for example, in super mario World the layers dont stay behind the others. The frame drop is the same. Zelda a link to the past still unplayable.
Mega drive/Genesis: The same of the first version.
Nes: I realy dont understand this emulator, super mario bros runs like a turtle, castlevania the same, but contra, double dragon, ninja gaiden, TMNT 3 runs perfectly.
Mame: The same of the first version.
Gba: I tryed a lot of 3d games and they have a good performance.
The Dpad stills crap, but i will try improve him.
I replaced the screen with a RetroFc 8 bits screen, works very well and dont have bad angles of view. Lucky!
In The box i made a translation of the chinese for english and i found "Supports multiplayer", but my usb joysticks doesnt worked, Maybe the joysticks of RS 07 can work.
The speaker volume dont reset when you turn off The console, interesting change.
For today, its just this.
Post by: kevin_yamagata on June 23, 2020, 03:05:38 pm
Indeed, but is it that the emulation quality has improved? The way is to wait for the Review on YouTube.Better Clone?
https://a.aliexpress.com/_d7YOYnk
**Edit it has a volume controller and usb type c input, now it looks like a new model same.
I found this ugly, I prefer the first model, looks like more a game boy, but its ugly too lmao
Your Review https://www.youtube.com/watch?v=6-m1uTMNzQw
Post by: kndcds on June 23, 2020, 03:31:25 pm
Unfortunately it's the same crap.Indeed, but is it that the emulation quality has improved? The way is to wait for the Review on YouTube.Better Clone?
https://a.aliexpress.com/_d7YOYnk
**Edit it has a volume controller and usb type c input, now it looks like a new model same.
I found this ugly, I prefer the first model, looks like more a game boy, but its ugly too lmao
Your Review https://www.youtube.com/watch?v=6-m1uTMNzQw
Post by: kevin_yamagata on June 23, 2020, 06:49:54 pm
Post by: kevin_yamagata on June 29, 2020, 10:11:46 pm
**UPDATE**: It has an zh1901mp02c chip, which is the same one the RS-07 has. As this is new info, I will check if this machine does have any custom fimware and test if it works.
Ok, so I got mine, and it is not a simple rebrand of the RS-69. Yes, it uses the same OS and emulators, so it has the same base compatibility issues (same ROMs not loading, and the same layer priority issues for SNES), HOWEVER, it does not use the same chip (FC100s), it uses a different chip which I have been unable to identify yet. As a result, it has better performance on GBA ROMs (it used to have random frame skips), very playable performance for the most part on Genesis ROMs (it used to have nasty frame skip, now it seems to run between 80-90% speed, which while noticeable, does not bother much), much less frameskip in Arcade ROMs (goes from somewhat playable to quite playable), and less screen tear in NES ROMs (goes from looking like the screen is made of sloshing water to almost unnoticeable screen tear (and I am quite sensitive to it). Add to that the fact it has 6 action buttons makes for better gameplay.
As no device is perfect, especially Chinese devices, here come the cons:
- The D-Pad is absolute crap. It registered 2 of 5 diagonal presses. I modified it by opening the console, and cutting the 4 tabs it had on the diagonal axis (no idea why it had those), then using moldable compound to add approximately 2-3mm to the ball pivot it has. The result is that now all diagonals now work, and the increased height of the ball pivot prevents pressing all 4 directions at once.
- The screen has a "bad" viewing angle. I say "bad" because it will only bother you at the beginning, and will be noticeable if you keep putting it to the side just to remind yourself how much you hate those angles. The thing is, it looks ok at the angle you are supposed to play. Not the best screen, but I have seen worse and much worse.
- The menu button is gone, and now you have to press the select button for a few seconds to active the menu to exit or save and load states. Add to this the fact that using this menu is the only way to save (it doesn't create save files for those games that save), and the fact that some games use the select button for some functions and it can be a bit of a hassle.
- There is no volume rocker, only a volume button that goes up. So you have to press it to go louder and louder until it goes mute, then gets louder again. And it resets every time you turn off the machine. I saw some circuitry that could allow for the installation of a volume rocker, but then you would need to change the ON/OFF switch. Ugh...
- It does have an indicator LED, but it is hidden inside the machine. So you cannot tell if it is charging, if it has finished charging, if it managed to turn on, etc. Now, this might not be a problem for some people, but I would have preferred the LED be visible.
All in all, it's not bad. But... at 18-20 USD, it is in Bittboy V3.5 territory, and for 9-12 USD more you can get a Pocket Go, which is a much better machine. As I have got it already, I am going to use it as a cheap handheld on the go. If it breaks, it won't hurt as much as it would if my Bittboy or Pocket Go died. The ideal price point for a machine such as this is 15 USD maximum. If you can get it for that price, I recommend it if you need something to use on trips where you fear a more expensive machine might not return from. Hopefully the advent of machines such as this will push back those NES clone handhelds back to their original 5-9 USD price points.
If you want to know about ROM compatibility, think it similar to those of the early emulators of the DOS days, aka Nesticle, Genecyst, and whatever it's contemporary for the SNES was. This includes not just ROM compatibility, but sprite and layers issues it may have had as well.
Also, never buy something hoping there is custom firmware. Chances machine will get custom firmware are almost nil. Only reason those machines that did get custom firmware, was that they had a derivative of Open Dingux to begin with. So if you can't understand the difference between that and how machines work, my advice is to stick to WELL KNOWN MACHINES THAT ALREADY HAVE CUSTOM FIRMWARE. As such, I won't test games of any sort, not check if any CFW will work on it, as I believe I have provided sufficient information in this and my previous posts for people to know whether they still want this or not, and am sufficiently satisfied with how it works.
Hello, i have a funny storie
I wrote the Bittboy V2 system on a 32GB SD card and put it on the XYC Q8 and it worked! Yes, just wrote an image to work.
But there are some problems, the screen is upside down and the buttons don't work, just the X button that takes a screenshot. But I can see the menus!
This was a great sign! Then I tried the PocketGo img, because of the L and R buttons, and the screen stayed white, no results.
Conclusion, this handheld can now receive a OpenDingux port hahaha
Post by: kndcds on June 29, 2020, 11:08:04 pm
Post by: kevin_yamagata on June 30, 2020, 12:21:12 am
I tryed a lot of systens on him (Like the V3.5 CFW and LDK Game) and just the bittboy V2 img as worked. The pocketgo just present the gameboy boot sound in a full white screen.
The bittboy v2 have a start then turn of the screen automaticaly.
So i made a crazy mix with the BittBoy V2 System and the Pocket Go Sytem. Replace some folders and boot files, like a CRAZY BOY.
Results:
Now the console dont turn of automaticaly, and three buttons work, the Dpad Down (Its like A) and Right (Its like B), the Button X (its like Up), the button A (its like Down) and the Button Y open some options. I will continue making this bizarre test and see what it happen.
(The stock system of XYC Q8 works normaly, its just change the Sd card files)
Post by: kndcds on June 30, 2020, 12:31:37 am
Post by: kevin_yamagata on June 30, 2020, 12:48:12 am
Well, there are several members here on the forum who are able to resolve these details. But congratulations on the experiment. I believe that it would be enough to just reconfigure the buttons and rectify some things.
Thanks for the patience!
Post by: Infernus on July 01, 2020, 10:05:02 pm
**UPDATE**: It has an zh1901mp02c chip, which is the same one the RS-07 has. As this is new info, I will check if this machine does have any custom fimware and test if it works.Bittboy is 29$. Not in 18-20$ category. Its almost 50% more than the price. Its been like that for 8 months now.
Ok, so I got mine, and it is not a simple rebrand of the RS-69. Yes, it uses the same OS and emulators, so it has the same base compatibility issues (same ROMs not loading, and the same layer priority issues for SNES), HOWEVER, it does not use the same chip (FC100s), it uses a different chip which I have been unable to identify yet. As a result, it has better performance on GBA ROMs (it used to have random frame skips), very playable performance for the most part on Genesis ROMs (it used to have nasty frame skip, now it seems to run between 80-90% speed, which while noticeable, does not bother much), much less frameskip in Arcade ROMs (goes from somewhat playable to quite playable), and less screen tear in NES ROMs (goes from looking like the screen is made of sloshing water to almost unnoticeable screen tear (and I am quite sensitive to it). Add to that the fact it has 6 action buttons makes for better gameplay.
As no device is perfect, especially Chinese devices, here come the cons:
- The D-Pad is absolute crap. It registered 2 of 5 diagonal presses. I modified it by opening the console, and cutting the 4 tabs it had on the diagonal axis (no idea why it had those), then using moldable compound to add approximately 2-3mm to the ball pivot it has. The result is that now all diagonals now work, and the increased height of the ball pivot prevents pressing all 4 directions at once.
- The screen has a "bad" viewing angle. I say "bad" because it will only bother you at the beginning, and will be noticeable if you keep putting it to the side just to remind yourself how much you hate those angles. The thing is, it looks ok at the angle you are supposed to play. Not the best screen, but I have seen worse and much worse.
- The menu button is gone, and now you have to press the select button for a few seconds to active the menu to exit or save and load states. Add to this the fact that using this menu is the only way to save (it doesn't create save files for those games that save), and the fact that some games use the select button for some functions and it can be a bit of a hassle.
- There is no volume rocker, only a volume button that goes up. So you have to press it to go louder and louder until it goes mute, then gets louder again. And it resets every time you turn off the machine. I saw some circuitry that could allow for the installation of a volume rocker, but then you would need to change the ON/OFF switch. Ugh...
- It does have an indicator LED, but it is hidden inside the machine. So you cannot tell if it is charging, if it has finished charging, if it managed to turn on, etc. Now, this might not be a problem for some people, but I would have preferred the LED be visible.
All in all, it's not bad. But... at 18-20 USD, it is in Bittboy V3.5 territory, and for 9-12 USD more you can get a Pocket Go, which is a much better machine. As I have got it already, I am going to use it as a cheap handheld on the go. If it breaks, it won't hurt as much as it would if my Bittboy or Pocket Go died. The ideal price point for a machine such as this is 15 USD maximum. If you can get it for that price, I recommend it if you need something to use on trips where you fear a more expensive machine might not return from. Hopefully the advent of machines such as this will push back those NES clone handhelds back to their original 5-9 USD price points.
If you want to know about ROM compatibility, think it similar to those of the early emulators of the DOS days, aka Nesticle, Genecyst, and whatever it's contemporary for the SNES was. This includes not just ROM compatibility, but sprite and layers issues it may have had as well.
Also, never buy something hoping there is custom firmware. Chances machine will get custom firmware are almost nil. Only reason those machines that did get custom firmware, was that they had a derivative of Open Dingux to begin with. So if you can't understand the difference between that and how machines work, my advice is to stick to WELL KNOWN MACHINES THAT ALREADY HAVE CUSTOM FIRMWARE. As such, I won't test games of any sort, not check if any CFW will work on it, as I believe I have provided sufficient information in this and my previous posts for people to know whether they still want this or not, and am sufficiently satisfied with how it works.
Post by: kevin_yamagata on July 01, 2020, 10:48:05 pm
The screen is still upside down, I don't know what to do. The colors are very inverted, everything is so blue and strange which the megaman stayed orange hahaha
This handheld device is very powerful! It can run Resident Evil 1 and 3 at 60fps. Tekken 3 is very slow at 30fps. Crash Bandcoot at 50fps and 30fps.
I tryed Snes and it worked very well, 60fps in most games, only the yoshis island has a lot of slowness.
Doom 1 and 2 works perfectly at 60fps.
Quake 1 is so smooth! Quake 2 worked with good fps, but it has some slow downs due to the explosions.
I think the specs are like LDK Vertical. And for the price (20-24 USD) that is a good buy if the developers work on this firmware. The screen is a GARBAGE, but it's still worth it.
Post by: kndcds on July 01, 2020, 10:52:46 pm
Hey! I managed to remap some buttons to browse in gmenu2x and start all emulators and games. But when I enter an application, remapping does not work and games are still impossible to play, only a few buttons work like, Up, Down, R, A and B without Left and Right.This is incredible!
The screen is still upside down, I don't know what to do. The colors are very inverted, everything is so blue and strange which the megaman stayed orange hahaha
This handheld device is very powerful! It can run Resident Evil 1 and 3 at 60fps. Tekken 3 is very slow at 30fps. Crash Bandcoot at 50fps and 30fps.
I tryed Snes and it worked very well, 60fps in most games, only the yoshis island has a lot of slowness.
Doom 1 and 2 works perfectly at 60fps.
Quake 1 is so smooth! Quake 2 worked with good fps, but it has some slow downs due to the explosions.
I think the specs are like LDK Vertical. And for the price (20-24 USD) that is a good buy if the developers work on this firmware. The screen is a GARBAGE, but it's still worth it.
I'm almost buying one of these!
I think OpenDingux would be perfect in this other version:
https://a.aliexpress.com/_dYaXqq6
Post by: kevin_yamagata on July 01, 2020, 11:10:43 pm
Hey! I managed to remap some buttons to browse in gmenu2x and start all emulators and games. But when I enter an application, remapping does not work and games are still impossible to play, only a few buttons work like, Up, Down, R, A and B without Left and Right.This is incredible!
The screen is still upside down, I don't know what to do. The colors are very inverted, everything is so blue and strange which the megaman stayed orange hahaha
This handheld device is very powerful! It can run Resident Evil 1 and 3 at 60fps. Tekken 3 is very slow at 30fps. Crash Bandcoot at 50fps and 30fps.
I tryed Snes and it worked very well, 60fps in most games, only the yoshis island has a lot of slowness.
Doom 1 and 2 works perfectly at 60fps.
Quake 1 is so smooth! Quake 2 worked with good fps, but it has some slow downs due to the explosions.
I think the specs are like LDK Vertical. And for the price (20-24 USD) that is a good buy if the developers work on this firmware. The screen is a GARBAGE, but it's still worth it.
I'm almost buying one of these!
I think OpenDingux would be perfect in this other version:
https://a.aliexpress.com/_dYaXqq6
Yaz! I think so.
Post by: kevin_yamagata on July 03, 2020, 01:22:10 am
Ps: I recomend you make a backup of the sd card first. The Stock Firmware will continue working normaly after the CFW install, just copy the correct folders and files for a formated Sd Card again.
Step 1:
You can download the Bittboy V2 firmware right here
https://rs97.bitgala.xyz/Bittboy/Bittboy%20cfw/Bittboy_V2_V2.5_CFW_V1.3.1_23-09-19.img.7z
Step 2: Write the img on a Sd Card using the Wind32diskImager or some equal program. After this, plug the sd card on the console.
"When i will test it with this version 2.5 of V2, the screen is upside down, the arrow keys do not move, and when I press another button, the screen turn off automaticaly." That is normal in the first time.
So, i made a fix for this issue on that link.
https://drive.google.com/drive/folders/15F4P9uKCGn5lPhkMSBVke8pjMkTMdbTm?usp=sharing
Step 3: You will unzip the folder and replace the respective files. Plug the sdcard adapter again and on the Boot partition you replace all them with the files in the folder "boot". In the "main" particion you will replace for the folder "kernel" and "gmenu2x".
(Note: The screen stills upside down and all the colors are strange, i really dont know what do here)
Now, you can open the emulators and games. You can make a test with psone games! (Note: When you open a emulator or app the button mapping enter on default config, so, just some buttons work, like Up, Down and A)
And this is it, this not are a official firmware, i made this test and he worked, i am not a system developer. We need of developers to make a decent port of the OpenDingux for the XYC Q8.
Post by: Djvanbeat on July 03, 2020, 12:54:12 pm
Post by: kndcds on July 08, 2020, 02:15:41 am
Eu ainda n?o tenho dispositivo. Mas tomara que algum desenvolvedor se comprometa a investigar tamb?m.
Enviado de meu moto g(7) play usando o Tapatalk
Post by: kevin_yamagata on July 08, 2020, 01:30:53 pm
Ei Mano, eu ? BR tamb?m, em?
Eu ainda n?o tenho dispositivo. Mas tomara que algum desenvolvedor se comprometa a investigar tamb?m.
Enviado de meu moto g(7) play usando o Tapatalk
Eu estou aguardando os desenvolvedores do OpenDingux se interessarem em trabalhar no porte para o XYC. N?o sou programador e entendo pouco sobre os sistemas.
Post by: kndcds on July 09, 2020, 07:00:51 pm
Enviado de meu moto g(7) play usando o Tapatalk
Post by: PhenomX on July 12, 2020, 10:22:57 pm
It would be great to have such a cheap and accessible console for everyone with Opendingux.
I offer to test any compilation or contribute what I can ;)
Post by: kevin_yamagata on July 13, 2020, 01:37:46 am
Great contribution, we are going to make this very cheap console have opendingux, it seems that its soc zh1901mp02c is 100% compatible with the f1c100s of the bittboy. We have to solve problems with the screen, keypad and the very important sound, which for now does not have, the buttons must be remapped.
It would be great to have such a cheap and accessible console for everyone with Opendingux.
I offer to test any compilation or contribute what I can ;)
Thank you for your support.
Yes, as you just said, this console is very cheap and accessible for everyone.
Ps: the sound works if you connect a headset or some audio device, and if you want to press start to open the settings of an emulator, just connect an Otg cable to the micro USB port and unplug it again, Yes, the usb port work like a start button....WEIRD.
Post by: 02k0 on July 13, 2020, 01:45:54 pm
Post by: Fishfan on July 13, 2020, 02:30:48 pm
Better Clone?hi, anyone tested this?
https://a.aliexpress.com/_dUNGGeu
Post by: PhenomX on July 13, 2020, 02:38:45 pm
If all goes well, the Q8 will win the title of the world's cheapest emulation console ;D
Come on, let's support this project! ;)
Post by: PhenomX on July 13, 2020, 03:05:56 pm
Better Clone?hi, anyone tested this?
https://a.aliexpress.com/_dUNGGeu
As indicated by kevin_yamagata in the video link, it is the same dog with a different collar, in this case it seems that it has improvements such as analog volume, front mono speaker and analog remote. As for emulation with original firmware, just as bad. That model is more difficult to obtain at the moment, there are countries where they do not send it, the Q8 does not present distribution problems.
Another problem that I see with these consoles is the battery life, it lasts very little and charges in 1 hour or so, and it works little more, at least in my case, I changed the battery for another and the same thing happens. The RetroFC with the same BL-5C battery charges in just under 3 hours and lasts up to 4 hours.
Post by: kevin_yamagata on July 13, 2020, 03:52:43 pm
Post by: PhenomX on July 13, 2020, 05:24:38 pm
i use a motorola turbo power, it takes about 40 minutes to complete the full charge. Pretty quick I would say.
Using a generic samsung 5V / 1A charger connected directly to the console, the charging light turns off in about 1 hour or less. Curiously, with the original firmware it has an approximate autonomy of 1.5 hours. Then the automatic shutdown message appears. If I use the modified firmware of the bittboy when it goes out with the stock firmware, it still works much more, incredible.
If I charge the battery with an external charger or another console, the duration is very similar, the same if I use another new battery, I understand that it is a problem of the console and its consumption, or simply that it does not correctly detect the percentage of charge of the battery.
What autonomy does the console battery have with the stock firm?
To give an example the RetroMini (RS-90) with the same battery and OpenDingux holds me 4-5 hours with 3 hours of charge. The retromini has a 2 "screen and a 384MHz Injenic JZ4725B cpu.
Post by: kevin_yamagata on July 13, 2020, 05:57:29 pm
There is a file in the Kernel folder called "r61520fb", which is responsible for the bittboy screen. The Q8 screen is a model similar to RetroFc, I replaced it and it worked the same way. In my case, i used the "WL-283105-A1 PLUS" screen from my RetroFc. Perhaps, if the file "r61520fb" is reprogrammed for this screen, things can improve significantly.
Finally, the system sound, I rewrote the Bittboy 3.5 img and it shows the gameboy boot sound, but the screen is completely white. I tried to replace the files in the "kernel" folder with the bittboy 2.5 files and nothing has changed.
Post by: PhenomX on July 13, 2020, 06:57:40 pm
This is a problem, I did not notice this issue in the stock firmware. But there is one thing that greatly influences battery consumption, the brightness of the screen that is always at maximum. In OpenDingux, I tried to decrease the brightness using the Y + R keys, but it doesn't work, it just shows the brightness control and if I use the minimum brightness, the screen turns off.
There is a file in the Kernel folder called "r61520fb", which is responsible for the bittboy screen. The Q8 screen is a model similar to RetroFc, I replaced it and it worked the same way. In my case, i used the "WL-283105-A1 PLUS" screen from my RetroFc. Perhaps, if the file "r61520fb" is reprogrammed for this screen, things can improve significantly.
Finally, the system sound, I rewrote the Bittboy 3.5 img and it shows the gameboy boot sound, but the screen is completely white. I tried to replace the files in the "kernel" folder with the bittboy 2.5 files and nothing has changed.
I see that the battery problem is common, I thought at first that my unit was broken but I see that it is the usual duration and charge, when compared to your data, being very similar.
Indeed, the screen is the same as the retrofc, in this case with worse viewing angles and enough light leaks, I have fixed the leak with sponge stops for lcd, just like in the retrofc, at the same time I took the opportunity to seal dust inlets to keep the lcd clean.
My model has the PCB dated December 2019 and the firmware is 1.2
The problem of the crosshead diagonals can be solved by putting a support in the center of the circular crosshead, for example with thermal silicone. In my case I do not care, because I am not a big fan of fighting games, but that is a possible solution.
The first problem to solve will be the screen, colors, orientation, gamma ...
I will try to find information so that I can help as much as possible.
Moving forward using trial / error is tricky, I hope someone will help out with display settings.
Post by: kevin_yamagata on July 13, 2020, 08:22:10 pm
This is a problem, I did not notice this issue in the stock firmware. But there is one thing that greatly influences battery consumption, the brightness of the screen that is always at maximum. In OpenDingux, I tried to decrease the brightness using the Y + R keys, but it doesn't work, it just shows the brightness control and if I use the minimum brightness, the screen turns off.
There is a file in the Kernel folder called "r61520fb", which is responsible for the bittboy screen. The Q8 screen is a model similar to RetroFc, I replaced it and it worked the same way. In my case, i used the "WL-283105-A1 PLUS" screen from my RetroFc. Perhaps, if the file "r61520fb" is reprogrammed for this screen, things can improve significantly.
Finally, the system sound, I rewrote the Bittboy 3.5 img and it shows the gameboy boot sound, but the screen is completely white. I tried to replace the files in the "kernel" folder with the bittboy 2.5 files and nothing has changed.
I see that the battery problem is common, I thought at first that my unit was broken but I see that it is the usual duration and charge, when compared to your data, being very similar.
Indeed, the screen is the same as the retrofc, in this case with worse viewing angles and enough light leaks, I have fixed the leak with sponge stops for lcd, just like in the retrofc, at the same time I took the opportunity to seal dust inlets to keep the lcd clean.
My model has the PCB dated December 2019 and the firmware is 1.2
The problem of the crosshead diagonals can be solved by putting a support in the center of the circular crosshead, for example with thermal silicone. In my case I do not care, because I am not a big fan of fighting games, but that is a possible solution.
The first problem to solve will be the screen, colors, orientation, gamma ...
I will try to find information so that I can help as much as possible.
Moving forward using trial / error is tricky, I hope someone will help out with display settings.
I appreciate your dedication, good luck with yours tests!
Post by: Fishfan on July 14, 2020, 04:59:51 am
**UPDATE**: It has an zh1901mp02c chip, which is the same one the RS-07 has. As this is new info, I will check if this machine does have any custom fimware and test if it works.Very useful review for those looking at this handheld. Do keep this post active, if got more thing to add.
Ok, so I got mine, and it is not a simple rebrand of the RS-69. Yes, it uses the same OS and emulators, so it has the same base compatibility issues (same ROMs not loading, and the same layer priority issues for SNES), HOWEVER, it does not use the same chip (FC100s), it uses a different chip which I have been unable to identify yet. As a result, it has better performance on GBA ROMs (it used to have random frame skips), very playable performance for the most part on Genesis ROMs (it used to have nasty frame skip, now it seems to run between 80-90% speed, which while noticeable, does not bother much), much less frameskip in Arcade ROMs (goes from somewhat playable to quite playable), and less screen tear in NES ROMs (goes from looking like the screen is made of sloshing water to almost unnoticeable screen tear (and I am quite sensitive to it). Add to that the fact it has 6 action buttons makes for better gameplay.
As no device is perfect, especially Chinese devices, here come the cons:
- The D-Pad is absolute crap. It registered 2 of 5 diagonal presses. I modified it by opening the console, and cutting the 4 tabs it had on the diagonal axis (no idea why it had those), then using moldable compound to add approximately 2-3mm to the ball pivot it has. The result is that now all diagonals now work, and the increased height of the ball pivot prevents pressing all 4 directions at once.
- The screen has a "bad" viewing angle. I say "bad" because it will only bother you at the beginning, and will be noticeable if you keep putting it to the side just to remind yourself how much you hate those angles. The thing is, it looks ok at the angle you are supposed to play. Not the best screen, but I have seen worse and much worse.
- The menu button is gone, and now you have to press the select button for a few seconds to active the menu to exit or save and load states. Add to this the fact that using this menu is the only way to save (it doesn't create save files for those games that save), and the fact that some games use the select button for some functions and it can be a bit of a hassle.
- There is no volume rocker, only a volume button that goes up. So you have to press it to go louder and louder until it goes mute, then gets louder again. And it resets every time you turn off the machine. I saw some circuitry that could allow for the installation of a volume rocker, but then you would need to change the ON/OFF switch. Ugh...
- It does have an indicator LED, but it is hidden inside the machine. So you cannot tell if it is charging, if it has finished charging, if it managed to turn on, etc. Now, this might not be a problem for some people, but I would have preferred the LED be visible.
All in all, it's not bad. But... at 18-20 USD, it is in Bittboy V3.5 territory, and for 9-12 USD more you can get a Pocket Go, which is a much better machine. As I have got it already, I am going to use it as a cheap handheld on the go. If it breaks, it won't hurt as much as it would if my Bittboy or Pocket Go died. The ideal price point for a machine such as this is 15 USD maximum. If you can get it for that price, I recommend it if you need something to use on trips where you fear a more expensive machine might not return from. Hopefully the advent of machines such as this will push back those NES clone handhelds back to their original 5-9 USD price points.
If you want to know about ROM compatibility, think it similar to those of the early emulators of the DOS days, aka Nesticle, Genecyst, and whatever it's contemporary for the SNES was. This includes not just ROM compatibility, but sprite and layers issues it may have had as well.
Also, never buy something hoping there is custom firmware. Chances machine will get custom firmware are almost nil. Only reason those machines that did get custom firmware, was that they had a derivative of Open Dingux to begin with. So if you can't understand the difference between that and how machines work, my advice is to stick to WELL KNOWN MACHINES THAT ALREADY HAVE CUSTOM FIRMWARE. As such, I won't test games of any sort, not check if any CFW will work on it, as I believe I have provided sufficient information in this and my previous posts for people to know whether they still want this or not, and am sufficiently satisfied with how it works.
Post by: 02k0 on July 21, 2020, 06:16:42 am
https://a.aliexpress.com/_dSzWxpP
Post by: PhenomX on July 21, 2020, 11:11:27 am
Newest version!
https://a.aliexpress.com/_dSzWxpP
Very interesting, this M3 looks like another variant of the Q8, although modern the design is a bit rustic, to say something nice xD, the screen seems to have more brightness but I have seen a rare reflection to the right of the screen. The source video is quite out of focus. But the fact of having analog volume and analog stick, can make the rom of the original not be worth for the last one. I think the front left speaker is a good idea.
The important parts and the button panel seem to be the same as the Q8.
Post by: kevin_yamagata on July 21, 2020, 01:00:15 pm
I think the LDK landscape input file (from the gmenu2x folder) can work on this little device as long as you use the bittboy V2 firmware. So, maybe the analong stick can work normally.
Post by: Fishfan on July 21, 2020, 01:09:01 pm
Newest version!
https://a.aliexpress.com/_dSzWxpP
Post by: Fishfan on July 23, 2020, 08:03:35 am
Is this the retrofc u used for screen replace?](http://)https://images.app.goo.gl/bUNHjRpqAkvfbXu46
Hey, my XYC Q8 has arrived and i make a lot of tests with him. The firmware version is the 1.2, the most new i can ever seen. Now, lets go to the results.
Snes emulator:
He have some improves on the layer issues, for example, in super mario World the layers dont stay behind the others. The frame drop is the same. Zelda a link to the past still unplayable.
Mega drive/Genesis: The same of the first version.
Nes: I realy dont understand this emulator, super mario bros runs like a turtle, castlevania the same, but contra, double dragon, ninja gaiden, TMNT 3 runs perfectly.
Mame: The same of the first version.
Gba: I tryed a lot of 3d games and they have a good performance.
The Dpad stills crap, but i will try improve him.
I replaced the screen with a RetroFc 8 bits screen, works very well and dont have bad angles of view. Lucky!
In The box i made a translation of the chinese for english and i found "Supports multiplayer", but my usb joysticks doesnt worked, Maybe the joysticks of RS 07 can work.
The speaker volume dont reset when you turn off The console, interesting change.
For today, its just this.
Post by: peppemas on July 23, 2020, 08:48:47 am
This is a little resume about what i did for that one who want try the Firmware on your XYC Q8 by himself.
Ps: I recomend you make a backup of the sd card first. The Stock Firmware will continue working normaly after the CFW install, just copy the correct folders and files for a formated Sd Card again.
Step 1:
You can download the Bittboy V2 firmware right here
https://rs97.bitgala.xyz/Bittboy/Bittboy%20cfw/Bittboy_V2_V2.5_CFW_V1.3.1_23-09-19.img.7z
Step 2: Write the img on a Sd Card using the Wind32diskImager or some equal program. After this, plug the sd card on the console.
"When i will test it with this version 2.5 of V2, the screen is upside down, the arrow keys do not move, and when I press another button, the screen turn off automaticaly." That is normal in the first time.
So, i made a fix for this issue on that link.
https://drive.google.com/drive/folders/15F4P9uKCGn5lPhkMSBVke8pjMkTMdbTm?usp=sharing
Step 3: You will unzip the folder and replace the respective files. Plug the sdcard adapter again and on the Boot partition you replace all them with the files in the folder "boot". In the "main" particion you will replace for the folder "kernel" and "gmenu2x".
(Note: The screen stills upside down and all the colors are strange, i really dont know what do here)
Now, you can open the emulators and games. You can make a test with psone games! (Note: When you open a emulator or app the button mapping enter on default config, so, just some buttons work, like Up, Down and A)
And this is it, this not are a official firmware, i made this test and he worked, i am not a system developer. We need of developers to make a decent port of the OpenDingux for the XYC Q8.
Hi Kevin i have try to put this bittboy firmware , and then the fix for screen , but the screen is always upside down, you have try other firmware? many thx
also i have wrote to the admin of https://www.rghandhelds.com/ for help with this console
Post by: kevin_yamagata on July 23, 2020, 03:17:06 pm
Hi, glad to see the retrofc sreen fit Q8. Need any modifications? Or just plug in?
Is this the retrofc u used for screen replace?](http://)https://images.app.goo.gl/bUNHjRpqAkvfbXu46Hey, my XYC Q8 has arrived and i make a lot of tests with him. The firmware version is the 1.2, the most new i can ever seen. Now, lets go to the results.
Snes emulator:
He have some improves on the layer issues, for example, in super mario World the layers dont stay behind the others. The frame drop is the same. Zelda a link to the past still unplayable.
Mega drive/Genesis: The same of the first version.
Nes: I realy dont understand this emulator, super mario bros runs like a turtle, castlevania the same, but contra, double dragon, ninja gaiden, TMNT 3 runs perfectly.
Mame: The same of the first version.
Gba: I tryed a lot of 3d games and they have a good performance.
The Dpad stills crap, but i will try improve him.
I replaced the screen with a RetroFc 8 bits screen, works very well and dont have bad angles of view. Lucky!
In The box i made a translation of the chinese for english and i found "Supports multiplayer", but my usb joysticks doesnt worked, Maybe the joysticks of RS 07 can work.
The speaker volume dont reset when you turn off The console, interesting change.
For today, its just this.
Yes, i used this screen https://pasteboard.co/JinPfSa.png
Just plug it on the socket
Post by: kevin_yamagata on July 23, 2020, 03:19:24 pm
This is a little resume about what i did for that one who want try the Firmware on your XYC Q8 by himself.
Ps: I recomend you make a backup of the sd card first. The Stock Firmware will continue working normaly after the CFW install, just copy the correct folders and files for a formated Sd Card again.
Step 1:
You can download the Bittboy V2 firmware right here
https://rs97.bitgala.xyz/Bittboy/Bittboy%20cfw/Bittboy_V2_V2.5_CFW_V1.3.1_23-09-19.img.7z
Step 2: Write the img on a Sd Card using the Wind32diskImager or some equal program. After this, plug the sd card on the console.
"When i will test it with this version 2.5 of V2, the screen is upside down, the arrow keys do not move, and when I press another button, the screen turn off automaticaly." That is normal in the first time.
So, i made a fix for this issue on that link.
https://drive.google.com/drive/folders/15F4P9uKCGn5lPhkMSBVke8pjMkTMdbTm?usp=sharing
Step 3: You will unzip the folder and replace the respective files. Plug the sdcard adapter again and on the Boot partition you replace all them with the files in the folder "boot". In the "main" particion you will replace for the folder "kernel" and "gmenu2x".
(Note: The screen stills upside down and all the colors are strange, i really dont know what do here)
Now, you can open the emulators and games. You can make a test with psone games! (Note: When you open a emulator or app the button mapping enter on default config, so, just some buttons work, like Up, Down and A)
And this is it, this not are a official firmware, i made this test and he worked, i am not a system developer. We need of developers to make a decent port of the OpenDingux for the XYC Q8.
Hi Kevin i have try to put this bittboy firmware , and then the fix for screen , but the screen is always upside down, you have try other firmware? many thx
also i have wrote to the admin of https://www.rghandhelds.com/ for help with this console
Sorry man, it was the most I could do. thanks for contacting RgHandhelds, maybe they can help us!
Post by: 02k0 on July 23, 2020, 03:23:20 pm
Hello, how many pins does this screen have?Hi, glad to see the retrofc sreen fit Q8. Need any modifications? Or just plug in?
Is this the retrofc u used for screen replace?](http://)https://images.app.goo.gl/bUNHjRpqAkvfbXu46Hey, my XYC Q8 has arrived and i make a lot of tests with him. The firmware version is the 1.2, the most new i can ever seen. Now, lets go to the results.
Snes emulator:
He have some improves on the layer issues, for example, in super mario World the layers dont stay behind the others. The frame drop is the same. Zelda a link to the past still unplayable.
Mega drive/Genesis: The same of the first version.
Nes: I realy dont understand this emulator, super mario bros runs like a turtle, castlevania the same, but contra, double dragon, ninja gaiden, TMNT 3 runs perfectly.
Mame: The same of the first version.
Gba: I tryed a lot of 3d games and they have a good performance.
The Dpad stills crap, but i will try improve him.
I replaced the screen with a RetroFc 8 bits screen, works very well and dont have bad angles of view. Lucky!
In The box i made a translation of the chinese for english and i found "Supports multiplayer", but my usb joysticks doesnt worked, Maybe the joysticks of RS 07 can work.
The speaker volume dont reset when you turn off The console, interesting change.
For today, its just this.
Yes, i used this screen https://pasteboard.co/JinPfSa.png
Just plug it on the socket
Post by: Fishfan on July 23, 2020, 04:05:20 pm
[/quote]
[/quote]
Yes, i used this screen https://pasteboard.co/JinPfSa.png
Just plug it on the socket
[/quote]
Thks Kevin. Never know the Retro Fc 8 bits console contribute a great part for project. Shd keep more for future.
Post by: kevin_yamagata on July 24, 2020, 12:05:13 am
Hello, how many pins does this screen have?Hi, glad to see the retrofc sreen fit Q8. Need any modifications? Or just plug in?
Is this the retrofc u used for screen replace?](http://)https://images.app.goo.gl/bUNHjRpqAkvfbXu46Hey, my XYC Q8 has arrived and i make a lot of tests with him. The firmware version is the 1.2, the most new i can ever seen. Now, lets go to the results.
Snes emulator:
He have some improves on the layer issues, for example, in super mario World the layers dont stay behind the others. The frame drop is the same. Zelda a link to the past still unplayable.
Mega drive/Genesis: The same of the first version.
Nes: I realy dont understand this emulator, super mario bros runs like a turtle, castlevania the same, but contra, double dragon, ninja gaiden, TMNT 3 runs perfectly.
Mame: The same of the first version.
Gba: I tryed a lot of 3d games and they have a good performance.
The Dpad stills crap, but i will try improve him.
I replaced the screen with a RetroFc 8 bits screen, works very well and dont have bad angles of view. Lucky!
In The box i made a translation of the chinese for english and i found "Supports multiplayer", but my usb joysticks doesnt worked, Maybe the joysticks of RS 07 can work.
The speaker volume dont reset when you turn off The console, interesting change.
For today, its just this.
Yes, i used this screen https://pasteboard.co/JinPfSa.png
Just plug it on the socket
24 pins for both.
Post by: peppemas on July 24, 2020, 08:03:16 am
https://boards.dingoonity.org/ingenic-jz4760-devices/custom-firmware-for-the-retro-arcade-mini/
i write the firmware with etcher , but console q8 not starting , screen blue and if i press buttons i hear the beep sound
Post by: kevin_yamagata on July 24, 2020, 02:00:49 pm
hi, i have try the firmware for retro arcade rs-07I had done this test with RS-07 CFW before. It does not work. If you add an SD card to the Q8 without content, it will display the same blue screen with the beep, it always happen. Only the Bittboy V2 firmware worked.
https://boards.dingoonity.org/ingenic-jz4760-devices/custom-firmware-for-the-retro-arcade-mini/
i write the firmware with etcher , but console q8 not starting , screen blue and if i press buttons i hear the beep sound
Post by: peppemas on July 24, 2020, 02:48:26 pm
hi, i have try the firmware for retro arcade rs-07I had done this test with RS-07 CFW before. It does not work. If you add an SD card to the Q8 without content, it will display the same blue screen with the beep, it always happen. Only the Bittboy V2 firmware worked.
https://boards.dingoonity.org/ingenic-jz4760-devices/custom-firmware-for-the-retro-arcade-mini/
i write the firmware with etcher , but console q8 not starting , screen blue and if i press buttons i hear the beep sound
you have try the firmware of LDK retro?
https://ldkgame.com/pages/guide
Post by: Soup42 on July 24, 2020, 04:47:11 pm
Post by: kevin_yamagata on July 24, 2020, 05:28:30 pm
Post by: Soup42 on July 25, 2020, 07:08:02 am
Bittboy v2 & v2.5 models v3.9 firmware - https://mega.nz/#!Y1JDzKSS!ulxaNaPxAuYn_Um6ywNN4RQ1dlhE-uGLvukQD577oxI
lol, it seems you can update the emulators by yourself. Just like other cfw's. You could rename an .elf file so it starts instead of f.i. gameboy. Then you could make your own advanced firmware. If you install the wrong cfw, you might brick the q8 though.
And, what's this: https://github.com/TriForceX/MiyooCFW/blob/master/README.md#console-revisions-differences
Post by: kevin_yamagata on July 25, 2020, 11:42:12 am
Post by: Soup42 on July 25, 2020, 12:12:14 pm
and here a snes emulator for dingux: https://github.com/dmitrysmagin/snes9x4d-rzx50
a collection of emulators for the dingux: https://wiki.dingoonity.org/index.php?title=OpenDingux:Emulators
seems dingux is a kind of version on linux based.
Post by: kevin_yamagata on July 25, 2020, 12:38:19 pm
the executables for the emulators are .elf right? So you could replace an existing emulator with another one? Maybe even scummvm. There is a scummvm emulator for 'dingux', is that the same as opendingux? https://www.scummvm.org/frs/scummvm/1.6.0/scummvm-1.6.0-dingux.zip
and here a snes emulator for dingux: https://github.com/dmitrysmagin/snes9x4d-rzx50
a collection of emulators for the dingux: https://wiki.dingoonity.org/index.php?title=OpenDingux:Emulators
seems dingux is a kind of version on linux based.
Yes, Opendingux is a linux distribution based on Dingux initially launched for the Dingoo A320.
See this site for more information https://wiki.dingoonity.org/index.php?title=OpenDingux:About
Post by: Soup42 on July 25, 2020, 12:43:24 pm
Here's something about the bittboy, it seems it's running 'melis' os. So not dingux.
Overall it?s a good handheld which is limited to emulating older systems by the current system firmware. I?m sure that if Useless or OpenDingux is ported to the device we?ll see improvements made and other emulators added, but the lack of shoulder buttons and the limited CPU power means we?re not going to be seeing SNES or GBA on this thing.
So just copying the elf over the old file isn't gonna work.
Post by: kevin_yamagata on July 25, 2020, 01:26:59 pm
I had already tried to install Muphen64 +, but I was not successful. Why install an emulator in this version of Opendingux, it is necessary to move the "opk" file to root / media using the "Commander" application and when I use the Commander program in Q8, I cannot use the Dpad to move left or right therefore, there is no way to install any application or emulator yet. We need to map the buttons correctly to start other tests on the system.
Post by: kevin_yamagata on July 25, 2020, 01:31:44 pm
Post by: Soup42 on July 25, 2020, 01:35:16 pm
+Save location updated from '.snes96_snapshots' to '.snes9x4d'. If upgrading move old save files."
This means that bittboy is running snes9x4d, and that is the same as the dingux i mentioned a couple of posts earlier. So maybe it does run scummvm for dingux.
Does this work: https://jutleys.wixsite.com/retrogamers97-90/post/how-to-add-a-emulator
There are 2 ways of accessing the q8. One is turning on the q8 first, then connect to pc. The other is turn q8 off, connect the usb cable, then turn on the q8. The last should bring the root of the q8 to the pc.
Post by: kevin_yamagata on July 25, 2020, 01:48:50 pm
Post by: Soup42 on July 25, 2020, 02:08:19 pm
Post by: kevin_yamagata on July 25, 2020, 02:13:37 pm
Thanks.
Post by: Soup42 on July 25, 2020, 02:55:40 pm
Post by: blackz1982 on July 25, 2020, 03:04:15 pm
Sorry guys, I tested all Opendingux console systems and none of them worked, only Bittboy CFW. We will wait for the developers to improve this port from Opendingux to Q8.On Bittboy firmware this is Nxhope and not Opendingux. Do not confuse them and do not try to run software designed for another firmware, it will not work.
Отправлено с моего HRY-LX1 через Tapatalk
Post by: kevin_yamagata on July 25, 2020, 03:21:32 pm
you can edit the buttons of the GUI\menu. I:\gmenu2x\input.conf . The emulators are all under the \emus\ folder. The executables don't have a file extension.Yes I understand! I already made this modification, it is included in the "Screen Fix" file that I made available previously, however, the Keymap works only for Gmenu2x, the emulators do not recognize it.
Post by: kevin_yamagata on July 25, 2020, 03:23:34 pm
Sorry for my mistake, I don't quite understand these systems. Thank you for the explanation.Sorry guys, I tested all Opendingux console systems and none of them worked, only Bittboy CFW. We will wait for the developers to improve this port from Opendingux to Q8.On Bittboy firmware this is Nxhope and not Opendingux. Do not confuse them and do not try to run software designed for another firmware, it will not work.
Отправлено с моего HRY-LX1 через Tapatalk
Post by: Qinti on July 25, 2020, 10:10:14 pm
Post by: Soup42 on July 26, 2020, 07:46:34 am
btw. does the bittboy 2.5 rom also work on an xyz q8 handheld?
Ow, it seems there's no way to get to the original rom of the xyz q8, cause of no drivers for usb connection.
@kevin_yamagata : how did you make the patch? And does it work besides some emulators not having the right buttons? Do you have the original rom for the xyz q8?
Post by: kevin_yamagata on July 26, 2020, 01:57:02 pm
the nes emulator has an key.conf in the map, so that should be easy to change. The snes emulator, maybe we can copy from the original rom. The others i don't know. Sometimes last changes to an emulator were back in 2010, so then the original rom must also have an equal version to the one of the bittboy. Then, doesn't the bittboy firmware have 2 snes emulators? What's with the second one?
btw. does the bittboy 2.5 rom also work on an xyz q8 handheld?
Ow, it seems there's no way to get to the original rom of the xyz q8, cause of no drivers for usb connection.
@kevin_yamagata : how did you make the patch? And does it work besides some emulators not having the right buttons? Do you have the original rom for the xyz q8?
Check my tutorial in the pag 2 for himself:
This is a little resume about what i did for that one who want try the Firmware on your XYC Q8 by himself.
Ps: I recomend you make a backup of the sd card first. The Stock Firmware will continue working normaly after the CFW install, just copy the correct folders and files for a formated Sd Card again.
Step 1:
You can download the Bittboy V2 firmware right here
https://rs97.bitgala.xyz/Bittboy/Bittboy%20cfw/Bittboy_V2_V2.5_CFW_V1.3.1_23-09-19.img.7z
Step 2: Write the img on a Sd Card using the Wind32diskImager or some equal program. After this, plug the sd card on the console.
"When i will test it with this version 2.5 of V2, the screen is upside down, the arrow keys do not move, and when I press another button, the screen turn off automaticaly." That is normal in the first time.
So, i made a fix for this issue on that link.
https://drive.google.com/drive/folders/15F4P9uKCGn5lPhkMSBVke8pjMkTMdbTm?usp=sharing
Step 3: You will unzip the folder and replace the respective files. Plug the sdcard adapter again and on the Boot partition you replace all them with the files in the folder "boot". In the "main" particion you will replace for the folder "kernel" and "gmenu2x".
(Note: The screen stills upside down and all the colors are strange, i really dont know what do here)
Now, you can open the emulators and games. You can make a test with psone games! (Note: When you open a emulator or app the button mapping enter on default config, so, just some buttons work, like Up, Down and A)
And this is it, this not are a official firmware, i made this test and he worked, i am not a system developer. We need of developers to make a decent port of the OpenDingux for the XYC Q8.
Post by: Soup42 on July 27, 2020, 07:57:26 am
**UPDATE**: It has an zh1901mp02c chip, which is the same one the RS-07 has. As this is new info, I will check if this machine does have any custom fimware and test if it works.
Ok, so I got mine, and it is not a simple rebrand of the RS-69. Yes, it uses the same OS and emulators, so it has the same base compatibility issues (same ROMs not loading, and the same layer priority issues for SNES), HOWEVER, it does not use the same chip (FC100s), it uses a different chip which I have been unable to identify yet. As a result, it has better performance on GBA ROMs (it used to have random frame skips), very playable performance for the most part on Genesis ROMs (it used to have nasty frame skip, now it seems to run between 80-90% speed, which while noticeable, does not bother much), much less frameskip in Arcade ROMs (goes from somewhat playable to quite playable), and less screen tear in NES ROMs (goes from looking like the screen is made of sloshing water to almost unnoticeable screen tear (and I am quite sensitive to it). Add to that the fact it has 6 action buttons makes for better gameplay.
As no device is perfect, especially Chinese devices, here come the cons:
- The D-Pad is absolute crap. It registered 2 of 5 diagonal presses. I modified it by opening the console, and cutting the 4 tabs it had on the diagonal axis (no idea why it had those), then using moldable compound to add approximately 2-3mm to the ball pivot it has. The result is that now all diagonals now work, and the increased height of the ball pivot prevents pressing all 4 directions at once.
- The screen has a "bad" viewing angle. I say "bad" because it will only bother you at the beginning, and will be noticeable if you keep putting it to the side just to remind yourself how much you hate those angles. The thing is, it looks ok at the angle you are supposed to play. Not the best screen, but I have seen worse and much worse.
- The menu button is gone, and now you have to press the select button for a few seconds to active the menu to exit or save and load states. Add to this the fact that using this menu is the only way to save (it doesn't create save files for those games that save), and the fact that some games use the select button for some functions and it can be a bit of a hassle.
- There is no volume rocker, only a volume button that goes up. So you have to press it to go louder and louder until it goes mute, then gets louder again. And it resets every time you turn off the machine. I saw some circuitry that could allow for the installation of a volume rocker, but then you would need to change the ON/OFF switch. Ugh...
- It does have an indicator LED, but it is hidden inside the machine. So you cannot tell if it is charging, if it has finished charging, if it managed to turn on, etc. Now, this might not be a problem for some people, but I would have preferred the LED be visible.
All in all, it's not bad. But... at 18-20 USD, it is in Bittboy V3.5 territory, and for 9-12 USD more you can get a Pocket Go, which is a much better machine. As I have got it already, I am going to use it as a cheap handheld on the go. If it breaks, it won't hurt as much as it would if my Bittboy or Pocket Go died. The ideal price point for a machine such as this is 15 USD maximum. If you can get it for that price, I recommend it if you need something to use on trips where you fear a more expensive machine might not return from. Hopefully the advent of machines such as this will push back those NES clone handhelds back to their original 5-9 USD price points.
If you want to know about ROM compatibility, think it similar to those of the early emulators of the DOS days, aka Nesticle, Genecyst, and whatever it's contemporary for the SNES was. This includes not just ROM compatibility, but sprite and layers issues it may have had as well.
Also, never buy something hoping there is custom firmware. Chances machine will get custom firmware are almost nil. Only reason those machines that did get custom firmware, was that they had a derivative of Open Dingux to begin with. So if you can't understand the difference between that and how machines work, my advice is to stick to WELL KNOWN MACHINES THAT ALREADY HAVE CUSTOM FIRMWARE. As such, I won't test games of any sort, not check if any CFW will work on it, as I believe I have provided sufficient information in this and my previous posts for people to know whether they still want this or not, and am sufficiently satisfied with how it works.
You mean the xyc q8 is a clone of this one: https://droidbox.co.uk/droidbox-rs-07-pro-arcade-retro-gaming-mini-handheld-emulators.html
if so, then these cwm should work too: https://boards.dingoonity.org/ingenic-jz4760-devices/custom-firmware-for-the-retro-arcade-mini/msg193890/#msg193890
The little logo of the gameboy clone(rs07), it looks like it's the wide version and it only has 4 buttons.
This rom lets you execute variable emulators you can download here: https://boards.dingoonity.org/dingoo-technology-a380/dingoo-a380-emulators-games-list-and-support/
even amiga 500,that runs titus the fox, sort of blues brothers kind of game, and maybe streetrod.
.dge is dingoo, and the scummvm for that is here: https://dl.openhandhelds.org/cgi-bin/dingoo.cgi?0,0,0,0,20,276
Btw those are often from back in 2009, so quite a while back.
Post by: Fishfan on July 27, 2020, 09:10:48 am
Post by: Soup42 on July 27, 2020, 09:15:16 am
Rs-07 cost about 5x more than Q8. But seem like Q8 need a lot more work. Anyone know whether latest variant , M3 has address Dpad diagonal press and screen , hardware problem
Yes, but does the rom from the first post work? Same chipset.
Post by: kevin_yamagata on July 27, 2020, 11:46:25 am
Rs-07 cost about 5x more than Q8. But seem like Q8 need a lot more work. Anyone know whether latest variant , M3 has address Dpad diagonal press and screen , hardware problem
Yes, but does the rom from the first post work? Same chipset.
No man, it doesn't work. I've done tests with many systems, including RS-07 CFW and only Bittboy V2 worked, with many problems.
Post by: kevin_yamagata on July 27, 2020, 11:49:02 am
From my understanding, the emulators would have to be recompiled to include the button mappings of this machine. The RS-90, for example, received ports of it larger sibling, which were recompiled to take into account the smaller screen and less buttons. I do not have much knowledge on how to do this, but I figure we could ask the person who ported a bunch of emulators to the RS-90 on how he did it.
Who made this port for the rs-90? Can you talk to that person and ask about Q8?
Post by: Soup42 on July 27, 2020, 11:52:31 am
Ow apparently not, cause it only has a settings icon in the main menu.
Post by: Fishfan on July 27, 2020, 12:51:15 pm
I understand q8 and M3 are of same chipset, so emulation, or firmware problem still the same. So u r saying M3 being newer, has hardware more superior than the older Q8? Which parts of hardware is better?Rs-07 cost about 5x more than Q8. But seem like Q8 need a lot more work. Anyone know whether latest variant , M3 has address Dpad diagonal press and screen , hardware problem
Yes, but does the rom from the first post work? Same chipset.
Post by: Soup42 on July 27, 2020, 01:05:41 pm
I understand q8 and M3 are of same chipset, so emulation, or firmware problem still the same. So u r saying M3 being newer, has hardware more superior than the older Q8? Which parts of hardware is better?Rs-07 cost about 5x more than Q8. But seem like Q8 need a lot more work. Anyone know whether latest variant , M3 has address Dpad diagonal press and screen , hardware problem
Yes, but does the rom from the first post work? Same chipset.
kevin_yamagata says they aren't compatible with eachother. Only bittboy v2 v2.5 is. So maybe it's more obvious that the bittboy v2 2.5 has the same hardware as the xyc q8. So that means the chipset is "Taking a look at the internals, we can see the chip is an AllWinner F1C500S." It says here https://obscurehandhelds.com/2018/12/the-new-bittboy/
Here are the developers of the cfw for the bittboy v2 2.5: https://github.com/TriForceX/MiyooCFW
we should ask them if they can adapt the cfm for the q8.
Post by: kevin_yamagata on July 27, 2020, 03:29:28 pm
Post by: Soup42 on July 27, 2020, 03:34:16 pm
Curious that the Q8 really has the CPU zh1901mp02c and RS-07. However, it is not compatible with the same CFW. I believe that, if the RS-07 system was adapted to Q8, it can work very well, but i see the bittboy's CFW as the best solution for Q8, the emulators work well, all applications are ok, but features like "Overclock" doesn't work on Q8, I tried to overclock the PCSX4ALL and the emulator crashes and won't start, possibly because the CFW is not 100% compatible with the zh1901mp02c CPU, but from the tests I did, the Q8 is more powerful than Bittboy, even without use the overclocking function. Games like Crash Bandicoot, Tekken 3 and Dino Crisis runned up to 30 fps. Gran Turismo (40fps) runned better than bittboy himself, i made a comparision using one youtube video. All the config set in default.
you probably already knew this, but here (https://github.com/TriForceX/MiyooCFW/wiki) is a way to access the boot partition of the q8 with windows. There's also a link to join a chatsession for suggestions for the firmware for the bittboy(so maybe also for the q8).
Post by: kevin_yamagata on July 27, 2020, 03:59:41 pm
Curious that the Q8 really has the CPU zh1901mp02c and RS-07. However, it is not compatible with the same CFW. I believe that, if the RS-07 system was adapted to Q8, it can work very well, but i see the bittboy's CFW as the best solution for Q8, the emulators work well, all applications are ok, but features like "Overclock" doesn't work on Q8, I tried to overclock the PCSX4ALL and the emulator crashes and won't start, possibly because the CFW is not 100% compatible with the zh1901mp02c CPU, but from the tests I did, the Q8 is more powerful than Bittboy, even without use the overclocking function. Games like Crash Bandicoot, Tekken 3 and Dino Crisis runned up to 30 fps. Gran Turismo (40fps) runned better than bittboy himself, i made a comparision using one youtube video. All the config set in default.
you probably already knew this, but here (https://github.com/TriForceX/MiyooCFW/wiki) is a way to access the boot partition of the q8 with windows. There's also a link to join a chatsession for suggestions for the firmware for the bittboy(so maybe also for the q8).
Thanks for that, i will talk to them.
Post by: Qinti on July 27, 2020, 05:15:19 pm
Also, regardless of what the chip said, which by the way is NOT the same one as the RS-07 (it seemed so at the time, but it is not the same, so it seems like a rebadge of the FC100s, otherwise it would not work with Bittboy firmware, I thought that was obvious), please do read and inform yourselves on how the CFW is stored before you start speculating on how to do things. Of what is posted, half the stuff is just speculation without even an effort to research on how some things are done. Just because someone got it to work partially it (awesome work, btw) doesn't mean its a better alternative to a Bittboy. The Bittboy has MUCH better construction and durability, the Pocketgo even more so. The Q8 doesn't look like the D-Pad and buttons will last very long unless you are willing to modify it with moldable compound. And by the time you make these modifications, you have spent at least 5-7 USD, which puts it in Bittboy/Pocketgo territory. The d-pad is not an easy mod; you have to re-model the ball joint support just right, then remodel the buttons to add tabs to them and then create some mini sockets (the game buttons are connected by a single piece of plastic, which will eventually break).
Even if they manage to fix these problems, and add CFW, there is no guarantee that you will get the menu button to work (which is non existent in this machine). Is the Menu button activation, which activates when you press the select button for a few seconds, software-based or hardware-based? If it is software based, can that be implemented via software? If hardware based, how do you ensure it is correctly triggered?
You have already seen they have made two more "versions" of this machine. If any of you remembers the RS-97, when it was 25 USD, then someone made CFW, and now the thing costs 50 USD? Plus they made about 4-5 different versions? If you have this machine, and manage to get it working, fine. If you don't and are waiting for CFW, keep in mind, the Chinese stop making machines if they think they won't sell, and will increase prices if one machine is popular. So, if you are interested, buy it now, and read up on how CFW works. There is no guarantee it will still be made by the time any workable CFW is made.
I am willing to help once this pandemic eases up and reduces my workload. Until then I have provided all the guidance I can give, and wish you luck. And please stop quoting my post, it had a lot of old info which is no longer applicable, I only made it to help people only choose buying it if they knew their limitations, when a Bittboy and Pocketgo (which I also have) are much better choices. Heck the RS-90 (which I also have) is still a better choice with its CFW. I only keep this machine when I play on the road as if it breaks it is not that much an issue.
Post by: Soup42 on July 27, 2020, 05:33:45 pm
I'm sorry, I do not have the time to get involved, I work a lot during this pandemic. But, f you go to the RS-90 subforum, you should be able to reach someone.
Also, regardless of what the chip said, which by the way is NOT the same one as the RS-07 (it seemed so at the time, but it is not the same, so it seems like a rebadge of the FC100s, otherwise it would not work with Bittboy firmware, I thought that was obvious), please do read and inform yourselves on how the CFW is stored before you start speculating on how to do things. Of what is posted, half the stuff is just speculation without even an effort to research on how some things are done. Just because someone got it to work partially it (awesome work, btw) doesn't mean its a better alternative to a Bittboy. The Bittboy has MUCH better construction and durability, the Pocketgo even more so. The Q8 doesn't look like the D-Pad and buttons will last very long unless you are willing to modify it with moldable compound. And by the time you make these modifications, you have spent at least 5-7 USD, which puts it in Bittboy/Pocketgo territory. The d-pad is not an easy mod; you have to re-model the ball joint support just right, then remodel the buttons to add tabs to them and then create some mini sockets (the game buttons are connected by a single piece of plastic, which will eventually break).
Even if they manage to fix these problems, and add CFW, there is no guarantee that you will get the menu button to work (which is non existent in this machine). Is the Menu button activation, which activates when you press the select button for a few seconds, software-based or hardware-based? If it is software based, can that be implemented via software? If hardware based, how do you ensure it is correctly triggered?
You have already seen they have made two more "versions" of this machine. If any of you remembers the RS-97, when it was 25 USD, then someone made CFW, and now the thing costs 50 USD? Plus they made about 4-5 different versions? If you have this machine, and manage to get it working, fine. If you don't and are waiting for CFW, keep in mind, the Chinese stop making machines if they think they won't sell, and will increase prices if one machine is popular. So, if you are interested, buy it now, and read up on how CFW works. There is no guarantee it will still be made by the time any workable CFW is made.
I am willing to help once this pandemic eases up and reduces my workload. Until then I have provided all the guidance I can give, and wish you luck. And please stop quoting my post, it had a lot of old info which is no longer applicable, I only made it to help people only choose buying it if they knew their limitations, when a Bittboy and Pocketgo (which I also have) are much better choices. Heck the RS-90 (which I also have) is still a better choice with its CFW. I only keep this machine when I play on the road as if it breaks it is not that much an issue.
what you also can do, is buy a bluetooth gamepad and use some old android phone for gaming. All of the emulators used with the q8 and more, also work on android. For me, i'm just curious for new things to work.
Post by: Qinti on July 27, 2020, 09:33:31 pm
up=keyboard,273
down=keyboard,274
left=keyboard,276
right=keyboard,275
modifier=keyboard,32
confirm=keyboard,306
cancel=keyboard,32
manual=keyboard,304
section_prev=keyboard,304
section_next=keyboard,308
pageup=keyboard,304
pagedown=keyboard,308
settings=keyboard,13
menu=keyboard,27
backlight=keyboard,51
power=keyboard,305
inc=keyboard,32
dec=keyboard,304
Now, which ones did you say worked or did what? With those known ones perhaps we can find the mappings of some to activate an opk which tells us the values when we press a key, once we have all the values, remapping emulators is a matter of recompiling while including said values. Or maybe it requires more info, I don't know really, we'd have to ask the guys who recompiled for the RS-90 and New Pocketgo
Post by: kevin_yamagata on July 27, 2020, 10:41:48 pm
up=keyboard,13
down=keyboard,308
left=keyboard,306
right=keyboard,32
modifier=keyboard,
confirm=keyboard,273
cancel=keyboard,
manual=keyboard,
section_prev=keyboard,51
section_next=keyboard,304
pagedown=keyboard,
pageup=keyboard,304
settings=keyboard,274
menu=keyboard,27
power=keyboard,305
dec=keyboard,306
inc=keyboard,
Post by: kevin_yamagata on July 27, 2020, 10:50:46 pm
those are the only buttons that I managed to map (very difficult work by the way lol)
up=keyboard,13
down=keyboard,308
left=keyboard,306
right=keyboard,32
modifier=keyboard,
confirm=keyboard,273
cancel=keyboard,
manual=keyboard,
section_prev=keyboard,51
section_next=keyboard,304
pagedown=keyboard,
pageup=keyboard,304
settings=keyboard,274
menu=keyboard,27
power=keyboard,305
dec=keyboard,306
inc=keyboard,
but this mapping doesn't work on emulators, only on gmenu2x. The only emulator that I managed to change the buttons on was the PCSX4ALL, I did it by plugging an Otg cable into the micro usb port. When plugging and unplugging the cable, the start button is pressed and I can access the emulator settings (Very Weird). But with that it is possible to play racing games and even Resident Evil. However, when I try to install an opk, it is not possible to finalize the operation because the mapping is reset when starting any system application. The Commander app, for example, does not work the left and right buttons for changing directories, because of that there is no way to install opks.
Post by: Soup42 on July 27, 2020, 10:54:59 pm
those are the only buttons that I managed to map (very difficult work by the way lol)
up=keyboard,13
down=keyboard,308
left=keyboard,306
right=keyboard,32
modifier=keyboard,
confirm=keyboard,273
cancel=keyboard,
manual=keyboard,
section_prev=keyboard,51
section_next=keyboard,304
pagedown=keyboard,
pageup=keyboard,304
settings=keyboard,274
menu=keyboard,27
power=keyboard,305
dec=keyboard,306
inc=keyboard,
but this mapping doesn't work on emulators, only on gmenu2x. The only emulator that I managed to change the buttons on was the PCSX4ALL, I did it by plugging an Otg cable into the micro usb port. When plugging and unplugging the cable, the start button is pressed and I can access the emulator settings (Very Weird). But with that it is possible to play racing games and even Resident Evil. However, when I try to install an opk, it is not possible to finalize the operation because the mapping is reset when starting any system application. The Commander app, for example, does not work the left and right buttons for changing directories, because of that there is no way to install opks.
Think, fceux also has a key.conf file, so that should work too with the bittboy firmware.
Post by: Qinti on July 28, 2020, 01:01:55 am
So therefore it would be like this:
D-pad (ON THE MACHINE)
Up: (what mapping ID it has)
Down: (what mapping ID it has)
Left: (what mapping ID it has)
Right: (what mapping ID it has)
Action buttons (again, ON THE MACHINE)
Select: (what mapping ID it has)
Start: (what mapping ID it has)
A: (what mapping ID it has)
B: (what mapping ID it has)
R: (what mapping ID it has)
Y: (what mapping ID it has)
X: (what mapping ID it has)
L: (what mapping ID it has)
This is what I was asking from you, since you said you had managed to figure out what some of the keys did what.
To check if the remaining button can be remapped, or if the menu button trigger is done via hardware or software:
Volume: (does it launch a trigger, or is it linked to the volume switch in a circle loop)
Select: (long press to see if it triggers a different ID) - more than likely, the menu button is software based.
Once we know what physical mapping ID each physical button (including d-pad) has, then we can establish what is needed to call the different functions in the Menu, and in-game. We can also decide if we want button combinations to replace any missing buttons (no menu button = replaced by select + start keys together, for example). In case the Volume button is software based, we need to either reassign it, or add volume up and down combinations as well.
All of this requires either changing the *.CONF file in some cases, or recompiling the source OPKs. Perhaps even some changes at the OS level to have these settings be used globally. As for how, I have no idea, but I do know it can be done.
Edit: If we can figure out the keys, it might be easier to ask someone (very nicely) who has more experience in these things to give us a hand in compiling the CFW, as they would have done it before. Or at least direct us to the proper documentation. That would be nice.
Post by: Soup42 on July 28, 2020, 06:26:43 am
# Auto-generated
SDL.Arkanoid.0.DeviceNum = 0
SDL.AutoScale = 1
SDL.BitsPerPixel = 8
SDL.ClipSides = 0
SDL.DisableSpriteLimit = 1
SDL.DoubleBuffering = 0
SDL.FPSThrottle = 0
SDL.FourScore = 0
SDL.Frameskip = 0
SDL.Fullscreen = 0
SDL.GameGenie = 0
SDL.Hotkeys.BindState = -1
SDL.Hotkeys.CheatMenu = -1
SDL.Hotkeys.DecreaseSpeed = -1
SDL.Hotkeys.FDSEject = -1
SDL.Hotkeys.FDSFlip = 2
SDL.Hotkeys.FDSSelect = -1
SDL.Hotkeys.FrameAdvance = 18
SDL.Hotkeys.FrameAdvanceLagSkip = -1
SDL.Hotkeys.IncreaseSpeed = -1
SDL.Hotkeys.LagCounterDisplay = -1
SDL.Hotkeys.LoadLua = -1
SDL.Hotkeys.LoadState = 1
SDL.Hotkeys.MovieToggleFrameDisplay = 6
SDL.Hotkeys.MuteCapture = -1
SDL.Hotkeys.Pause = 51
SDL.Hotkeys.Quit = 304
SDL.Hotkeys.Reset = -1
SDL.Hotkeys.SaveState = 0
SDL.Hotkeys.Screenshot = 17
SDL.Hotkeys.SelectState0 = -1
SDL.Hotkeys.SelectState1 = -1
SDL.Hotkeys.SelectState2 = -1
SDL.Hotkeys.SelectState3 = -1
SDL.Hotkeys.SelectState4 = -1
SDL.Hotkeys.SelectState5 = -1
SDL.Hotkeys.SelectState6 = -1
SDL.Hotkeys.SelectState7 = -1
SDL.Hotkeys.SelectState8 = -1
SDL.Hotkeys.SelectState9 = -1
SDL.Hotkeys.SubtitleDisplay = 27
SDL.Hotkeys.ToggleBG = -1
SDL.Hotkeys.ToggleInputDisplay = -1
SDL.Hotkeys.ToggleMovieRW = -1
SDL.Hotkeys.Turbo = -1
SDL.Hotkeys.VSInsertCoin = 5
SDL.Hotkeys.VSToggleDip = -1
SDL.Hue = 72
SDL.Input.GamePad.0A = 306
SDL.Input.GamePad.0B = 32
SDL.Input.GamePad.0DeviceNum = 0
SDL.Input.GamePad.0Down = 308
SDL.Input.GamePad.0Left = 306
SDL.Input.GamePad.0Right = 32
SDL.Input.GamePad.0Select = 273
SDL.Input.GamePad.0Start = 27
SDL.Input.GamePad.0TurboA = 308
SDL.Input.GamePad.0TurboB = 304
SDL.Input.GamePad.0Up = 13
SDL.Input.GamePad.1A = 0
SDL.Input.GamePad.1B = 0
SDL.Input.GamePad.1DeviceNum = 0
SDL.Input.GamePad.1Down = 0
SDL.Input.GamePad.1Left = 0
SDL.Input.GamePad.1Right = 0
SDL.Input.GamePad.1Select = 0
SDL.Input.GamePad.1Start = 0
SDL.Input.GamePad.1TurboA = 0
SDL.Input.GamePad.1TurboB = 0
SDL.Input.GamePad.1Up = 0
SDL.Input.GamePad.2A = 0
SDL.Input.GamePad.2B = 0
SDL.Input.GamePad.2DeviceNum = 0
SDL.Input.GamePad.2Down = 0
SDL.Input.GamePad.2Left = 0
SDL.Input.GamePad.2Right = 0
SDL.Input.GamePad.2Select = 0
SDL.Input.GamePad.2Start = 0
SDL.Input.GamePad.2TurboA = 0
SDL.Input.GamePad.2TurboB = 0
SDL.Input.GamePad.2Up = 0
SDL.Input.GamePad.3A = 0
SDL.Input.GamePad.3B = 0
SDL.Input.GamePad.3DeviceNum = 0
SDL.Input.GamePad.3Down = 0
SDL.Input.GamePad.3Left = 0
SDL.Input.GamePad.3Right = 0
SDL.Input.GamePad.3Select = 0
SDL.Input.GamePad.3Start = 0
SDL.Input.GamePad.3TurboA = 0
SDL.Input.GamePad.3TurboB = 0
SDL.Input.GamePad.3Up = 0
SDL.Input.HyperShot.0 = 0
SDL.Input.HyperShot.1 = 1
SDL.Input.HyperShot.2 = 19
SDL.Input.HyperShot.3 = 2
SDL.Input.HyperShot.DeviceNum = 0
SDL.Input.QuizKing.0 = 0
SDL.Input.QuizKing.1 = 1
SDL.Input.QuizKing.2 = 19
SDL.Input.QuizKing.3 = 2
SDL.Input.QuizKing.4 = 17
SDL.Input.QuizKing.5 = 16
SDL.Input.QuizKing.DeviceNum = 0
SDL.Input.TopRider.0 = 6
SDL.Input.TopRider.1 = 27
SDL.Input.TopRider.2 = 5
SDL.Input.TopRider.3 = 18
SDL.Input.TopRider.4 = 0
SDL.Input.TopRider.5 = 1
SDL.Input.TopRider.6 = 19
SDL.Input.TopRider.7 = 2
SDL.Input.TopRider.DeviceNum = 0
SDL.InputDisplay = 0
SDL.KeepRatio = 1
SDL.MergeControls = 0
SDL.MouseSpeed = 3
SDL.MovieMsg = 1
SDL.NTSCpalette = 0
SDL.NewPPU = 0
SDL.NoConfig = 0
SDL.NoFrame = 0
SDL.OekaKids.0.DeviceNum = 0
SDL.PAL = 0
SDL.PauseFrame = 0
SDL.ScanLineEnd = 239
SDL.ScanLineStart = 0
SDL.Shadow.0.DeviceNum = 0
SDL.ShowFPS = 0
SDL.ShowMouseCursor = 0
SDL.Sound = 1
SDL.Sound.BufSize = 30
SDL.Sound.LowPass = 0
SDL.Sound.NoiseVolume = 256
SDL.Sound.PCMVolume = 256
SDL.Sound.Quality = 0
SDL.Sound.Rate = 32000
SDL.Sound.Square1Volume = 256
SDL.Sound.Square2Volume = 256
SDL.Sound.TriangleVolume = 256
SDL.Sound.Volume = 256
SDL.SpecialFilter = 0
SDL.SubtitleDisplay = 1
SDL.Tint = 56
SDL.XResolution = 320
SDL.XStretch = 0
SDL.YResolution = 240
SDL.YStretch = 0
SDL.Zapper.0.DeviceNum = 0
SDL.XScale = 1.000000
SDL.YScale = 1.000000
SDL.Arkanoid.0.DeviceType = Mouse
SDL.FCMConvert =
SDL.Input.0 = GamePad.0
SDL.Input.1 = GamePad.1
SDL.Input.2 = Gamepad.2
SDL.Input.3 = Gamepad.3
SDL.Input.GamePad.0DeviceType = Keyboard
SDL.Input.GamePad.1DeviceType = None
SDL.Input.GamePad.2DeviceType = None
SDL.Input.GamePad.3DeviceType = None
SDL.Input.HyperShot.DeviceType = Keyboard
SDL.Input.QuizKing.DeviceType = Keyboard
SDL.Input.TopRider.DeviceType = Keyboard
SDL.Movie =
SDL.OekaKids.0.DeviceType = Mouse
SDL.Palette =
SDL.RipSubs =
SDL.Shadow.0.DeviceType = Mouse
SDL.Sound.RecordFile =
SDL.Zapper.0.DeviceType = Mouse
Post by: Soup42 on July 28, 2020, 06:31:58 am
snex9x4d: so snes emu should be this version (for the bittboy made):
https://github.com/m45t3r/snes9x4d-miyoo/releases/tag/v2020.06.06
there's a sourcecode holding the keys values(keydef.h):
and there's a .makefile, so with linux we could rebuild the emulator. It's easy to adapt the square buttons, but the round i don't know. They aren't in the g-menu either.
#ifndef __KEYDEF_h_
#define __KEYDEF_h_
#define A_1 0
#define B_1 1
#define X_1 2
#define Y_1 3
#define L_1 4
#define R_1 5
#define START_1 12
#define SELECT_1 13
#define UP_1 16
#define DOWN_1 17
#define LEFT_1 18
#define RIGHT_1 19
#define A_2 6
#define B_2 7
#define X_2 8
#define Y_2 9
#define L_2 10
#define R_2 11
#define START_2 14
#define SELECT_2 15
#define UP_2 20
#define DOWN_2 21
#define LEFT_2 22
#define RIGHT_2 23
#define LU_2 24
#define LD_2 25
#define RU_2 26
#define RD_2 27
#define ACCEL 50
#define QUIT 51
#define HELP 52
#define SHIFTL 30
#define SHIFTR 31
#define CTRLL 32
#define CTRLR 33
#endif // __KEYDEF_h_
Post by: Soup42 on July 28, 2020, 07:09:55 am
can't find where the keys are stored.
It does indeed say something about .opk extension as executable.
keys can be adapted here: https://github.com/m45t3r/NGPCemu-miyoo/blob/master/shell/input/sdl/input.c
Found the opk file for scummvm: https://github.com/craigsc/scummvm-rg350/releases/download/v0.2/scummvm-rg350-01132020.opk
keys scummvm: https://github.com/craigsc/scummvm-rg350/blob/master/common/keyboard.h
source code scummvm: https://github.com/craigsc/scummvm-rg350
and opk for amiga emulator: https://redirect.viglink.com/?format=go&jsonp=vglnk_159592122619011&key=5150cb74f98acee214af0b53b6829d41&libId=kd5m9qn60102ljt2000DAbz519jrx&loc=https%3A%2F%2Fboards.dingoonity.org%2Fgcw-releases%2Fuae4all-release-1%2F&v=1&opt=true&out=http%3A%2F%2Fwww.gcw-zero.com%2Ffile.php%3Ffile%3Duae4all.opk&ref=https%3A%2F%2Fwww.google.com%2F&title=UAE4ALL%20Release%201%20%7C%20Dingoonity.org%20-%20The%20Dingoo%20Community&txt=http%3A%2F%2Fwww.gcw-zero.com%2Ffile.php%3Ffile%3Duae4all.opk
source code amiga emu: https://github.com/zear/uae4all
keys emu: https://github.com/zear/uae4all/blob/master/src/include/keyboard.h
source code for the commander: https://github.com/retrogamehandheld/OpenDingux#applications
keys for commander: https://github.com/glebm/od-commander/blob/master/CMake/rg350_defs.cmake
found an .opk file for inputtester, so i guess the keys input: https://github.com/retrogamehandheld/OpenDingux/blob/master/Applications/Input%20tester.opk
Post by: kevin_yamagata on July 28, 2020, 01:28:42 pm
OPKs are installed by just placing them inside the SD card folder structure, you dont use the commander. Also, please read what I posted before. Once we know what keys are what, they can be mapped. When you map, you don't go by what you mapped it by. You go by physical button mapping, then decide where to allocate them on an app basis.
So therefore it would be like this:
D-pad (ON THE MACHINE)
Up: (what mapping ID it has)
Down: (what mapping ID it has)
Left: (what mapping ID it has)
Right: (what mapping ID it has)
Action buttons (again, ON THE MACHINE)
Select: (what mapping ID it has)
Start: (what mapping ID it has)
A: (what mapping ID it has)
B: (what mapping ID it has)
R: (what mapping ID it has)
Y: (what mapping ID it has)
X: (what mapping ID it has)
L: (what mapping ID it has)
This is what I was asking from you, since you said you had managed to figure out what some of the keys did what.
To check if the remaining button can be remapped, or if the menu button trigger is done via hardware or software:
Volume: (does it launch a trigger, or is it linked to the volume switch in a circle loop)
Select: (long press to see if it triggers a different ID) - more than likely, the menu button is software based.
Once we know what physical mapping ID each physical button (including d-pad) has, then we can establish what is needed to call the different functions in the Menu, and in-game. We can also decide if we want button combinations to replace any missing buttons (no menu button = replaced by select + start keys together, for example). In case the Volume button is software based, we need to either reassign it, or add volume up and down combinations as well.
All of this requires either changing the *.CONF file in some cases, or recompiling the source OPKs. Perhaps even some changes at the OS level to have these settings be used globally. As for how, I have no idea, but I do know it can be done.
Edit: If we can figure out the keys, it might be easier to ask someone (very nicely) who has more experience in these things to give us a hand in compiling the CFW, as they would have done it before. Or at least direct us to the proper documentation. That would be nice.
I tried to install some emulators (opk) like Muphen64plus, Desmume, and even reinstall pocketsnes. I moved and unzipped the opk file in the "emus" folder at the root of the card. When I accessed the Q8 menu, the emulators do not appear, or they do not work here or I was unable to install them correctly.
About the mapping of buttons, this list I posted earlier is the one I use on my Q8, you can copy the text and replace it in the "input.txt" file located in the gmenu2x folder, if you still have your q8 of course.
The Start, Select, B, L, Dpad Up and Volume buttons are not mapped in the software, I don't know what to do about it, how can I find out these buttons and maps in the software?
Post by: Soup42 on July 28, 2020, 01:36:42 pm
OPKs are installed by just placing them inside the SD card folder structure, you dont use the commander. Also, please read what I posted before. Once we know what keys are what, they can be mapped. When you map, you don't go by what you mapped it by. You go by physical button mapping, then decide where to allocate them on an app basis.
So therefore it would be like this:
D-pad (ON THE MACHINE)
Up: (what mapping ID it has)
Down: (what mapping ID it has)
Left: (what mapping ID it has)
Right: (what mapping ID it has)
Action buttons (again, ON THE MACHINE)
Select: (what mapping ID it has)
Start: (what mapping ID it has)
A: (what mapping ID it has)
B: (what mapping ID it has)
R: (what mapping ID it has)
Y: (what mapping ID it has)
X: (what mapping ID it has)
L: (what mapping ID it has)
This is what I was asking from you, since you said you had managed to figure out what some of the keys did what.
To check if the remaining button can be remapped, or if the menu button trigger is done via hardware or software:
Volume: (does it launch a trigger, or is it linked to the volume switch in a circle loop)
Select: (long press to see if it triggers a different ID) - more than likely, the menu button is software based.
Once we know what physical mapping ID each physical button (including d-pad) has, then we can establish what is needed to call the different functions in the Menu, and in-game. We can also decide if we want button combinations to replace any missing buttons (no menu button = replaced by select + start keys together, for example). In case the Volume button is software based, we need to either reassign it, or add volume up and down combinations as well.
All of this requires either changing the *.CONF file in some cases, or recompiling the source OPKs. Perhaps even some changes at the OS level to have these settings be used globally. As for how, I have no idea, but I do know it can be done.
Edit: If we can figure out the keys, it might be easier to ask someone (very nicely) who has more experience in these things to give us a hand in compiling the CFW, as they would have done it before. Or at least direct us to the proper documentation. That would be nice.
the keys we already know(arrow buttons):
273 == 13 settings should be up
274 == 308 next should be down
276 == 306 confirm should be left
275 == 32 modifier should be right
there buttons we don't know (round buttons, start, select):
306 == 273 up should be confirm
304 == 51 backlight should be previous
308 == 304 manual should be next ???
304 == 304 pageup ???
13 == 274 down should be settings
menu 27 is the same
power 305 is the same
confirm 306 should be decrease 304 ???
could someone try an emulator to figure out what the buttons A,B,L,R,X,Y and the three red ones just beneath the screen, are used for in the emulator?
Post by: Soup42 on July 28, 2020, 01:41:20 pm
OPKs are installed by just placing them inside the SD card folder structure, you dont use the commander. Also, please read what I posted before. Once we know what keys are what, they can be mapped. When you map, you don't go by what you mapped it by. You go by physical button mapping, then decide where to allocate them on an app basis.
So therefore it would be like this:
D-pad (ON THE MACHINE)
Up: (what mapping ID it has)
Down: (what mapping ID it has)
Left: (what mapping ID it has)
Right: (what mapping ID it has)
Action buttons (again, ON THE MACHINE)
Select: (what mapping ID it has)
Start: (what mapping ID it has)
A: (what mapping ID it has)
B: (what mapping ID it has)
R: (what mapping ID it has)
Y: (what mapping ID it has)
X: (what mapping ID it has)
L: (what mapping ID it has)
This is what I was asking from you, since you said you had managed to figure out what some of the keys did what.
To check if the remaining button can be remapped, or if the menu button trigger is done via hardware or software:
Volume: (does it launch a trigger, or is it linked to the volume switch in a circle loop)
Select: (long press to see if it triggers a different ID) - more than likely, the menu button is software based.
Once we know what physical mapping ID each physical button (including d-pad) has, then we can establish what is needed to call the different functions in the Menu, and in-game. We can also decide if we want button combinations to replace any missing buttons (no menu button = replaced by select + start keys together, for example). In case the Volume button is software based, we need to either reassign it, or add volume up and down combinations as well.
All of this requires either changing the *.CONF file in some cases, or recompiling the source OPKs. Perhaps even some changes at the OS level to have these settings be used globally. As for how, I have no idea, but I do know it can be done.
Edit: If we can figure out the keys, it might be easier to ask someone (very nicely) who has more experience in these things to give us a hand in compiling the CFW, as they would have done it before. Or at least direct us to the proper documentation. That would be nice.
I tried to install some emulators (opk) like Muphen64plus, Desmume, and even reinstall pocketsnes. I moved and unzipped the opk file in the "emus" folder at the root of the card. When I accessed the Q8 menu, the emulators do not appear, or they do not work here or I was unable to install them correctly.
About the mapping of buttons, this list I posted earlier is the one I use on my Q8, you can copy the text and replace it in the "input.txt" file located in the gmenu2x folder, if you still have your q8 of course.
The Start, Select, B, L, Dpad Up and Volume buttons are not mapped in the software, I don't know what to do about it, how can I find out these buttons and maps in the software?
You could use the commander to start one of the emu's opk files. But the sh*t is difficult. Now i read it again, snes it says it's for the miyoo made. That's another portable gamestation. This is what the title says: [Bittboy/Pocket Go v1] Snes9x4d for MiyooCFW v2020.06.06. After that someone could make it work on his pocket go by just copying it over the old file.
*so you can replace the old snes9x4d file with the one from the download. But there are different bittboys, maybe it's from a bittboy that isn't compatible with the q8. Maybe also the screen resolution in the opk file should be altered.
Post by: Soup42 on July 28, 2020, 02:49:28 pm
Post by: blackz1982 on July 28, 2020, 03:45:57 pm
Отправлено с моего HRY-LX1 через Tapatalk
Post by: Soup42 on July 28, 2020, 04:01:08 pm
Bittboy CFW dont support opk. Dont use emulators from opendingux or retrofw. You must use emulators or games only compiled to Bittboy.
Отправлено с моего HRY-LX1 через Tapatalk
what is the file extension or language of the files in the bittboy then?
* I read something about arduboy (another portable gaming console). It's possible to make an emu by making it first for the arduboy, then convert it to bittboy. Further they say, there isn't much stuff to find about the bittboy executables, except https://discord.gznetwork.com/ (https://discord.gznetwork.com/)the discord channel.
Post by: blackz1982 on July 28, 2020, 04:44:51 pm
Отправлено с моего HRY-LX1 через Tapatalk
Post by: Qinti on July 28, 2020, 04:52:57 pm
Edit: Or do they need to be compiled? Let me fire up my Linux VM and see the SD card image I have.
Some of the emulators do have a *.cfg file. So could it be so simple as to just editing those? Did you guys find out the mapping of all the hardware keys?
Post by: Soup42 on July 28, 2020, 04:57:20 pm
Without extension, since it is not necessary. Its just elf file.
Отправлено с моего HRY-LX1 через Tapatalk
It surely isn't compatible with the ps2 elf files?
How do you make an .elf file from something like this: https://github.com/m45t3r/snes9x4d-miyoo/releases/tag/v2020.06.06 ?
The bittboy rom is in elf language, but it already has an snes9x4d.elf.
Post by: Qinti on July 28, 2020, 04:59:50 pm
Without extension, since it is not necessary. Its just elf file.
Отправлено с моего HRY-LX1 через Tapatalk
It surely isn't compatible with the ps2 elf files?
Dude, its an F1C500S cpu, I think everyone knows its limitations. Get real. ::)
Post by: Soup42 on July 28, 2020, 05:03:30 pm
Without extension, since it is not necessary. Its just elf file.
Отправлено с моего HRY-LX1 через Tapatalk
It surely isn't compatible with the ps2 elf files?
Dude, its an F1C500S cpu, I think everyone knows its limitations. Get real. ::)
Source code for retrofw isn't something.
Took a closer look at the size of the elf file, and it's way bigger then 800KB, so not going to work either.
Post by: kevin_yamagata on July 28, 2020, 05:54:05 pm
Right, the CPU is different. I have no idea how to compile them then.
Edit: Or do they need to be compiled? Let me fire up my Linux VM and see the SD card image I have.
Some of the emulators do have a *.cfg file. So could it be so simple as to just editing those? Did you guys find out the mapping of all the hardware keys?
up=keyboard,13
down=keyboard,308
left=keyboard,306
right=keyboard,32
modifier=keyboard,
confirm=keyboard,273
cancel=keyboard,
manual=keyboard,
section_prev=keyboard,51
section_next=keyboard,304
pagedown=keyboard,
pageup=keyboard,304
settings=keyboard,274
menu=keyboard,27
power=keyboard,305
dec=keyboard,306
inc=keyboard,
These are the only ones that I was able to map, however, when I try to remap any emulator or game, the buttons are not represented by numbers, but as pc keys, as "space" and "shift", so it is very difficult to find out which ones keys work.
I was only able to modify the PCSX4ALL keys because the mapping is done inside the emulator and not in a .config file
Post by: Soup42 on July 28, 2020, 07:49:50 pm
I spoke on the chatsite with someone who a year ago was busy making a gmenu2x that's compatible with the bittboy. https://github.com/retrostone-dev/gmenu2x/blob/master/src/inputmanager.cpp
Then my question was whether scummvm.opk would run. He said that a newer Dingoo version would work. So it has to re recompiled from the source code of scummvm(the Dingoo version still being inside the source code).
Then to make gmenu2x read opk files, next thing:
For OPK support to work, you need to make sure...
- that the kernel is built with Squashfs support + cramfs.
If unsure about it, try to mount it with the mount and see if it works.
- The rootfs needs to be mounted as read-write, not read-only.
Buildroot mounts it as read only by default.
The following line in /etc/inittab usually fixes this :
::sysinit:/bin/mount -o remount,rw /
- You need to have the opkrun utility in /usr/bin.
opkrun is used for mounting OPK files to run them.
This is seperate from Gmenu2x's own handling of OPKs.
- You need to have a supported version of Gmenu2x.
My fork of Gmenu2x supports this.
Note that the -D_CARD_ROOT=\"/media\" define at compile time does matter.
If your opk files are in /mnt/apps then you need to tell the compiler to use the folder before /mnt.
So in that case, it will just be -D_CARD_ROOT=\"/\".
Then the key of making all buttons work on the q8 isn't in recompiling the emulators one by one, but in changing the kernel. So the custom firmware thinks the q8 is in fact a bittboy.
Post by: blackz1982 on July 28, 2020, 09:17:26 pm
good news!Why do you need opk support?
I spoke on the chatsite with someone who a year ago was busy making a gmenu2x that's compatible with the bittboy. https://github.com/retrostone-dev/gmenu2x/blob/master/src/inputmanager.cpp
Then my question was whether scummvm.opk would run. He said that a newer Dingoo version would work. So it has to re recompiled from the source code of scummvm(the Dingoo version still being inside the source code).
Then to make gmenu2x read opk files, next thing:
For OPK support to work, you need to make sure...
- that the kernel is built with Squashfs support + cramfs.
If unsure about it, try to mount it with the mount and see if it works.
- The rootfs needs to be mounted as read-write, not read-only.
Buildroot mounts it as read only by default.
The following line in /etc/inittab usually fixes this :
::sysinit:/bin/mount -o remount,rw /
- You need to have the opkrun utility in /usr/bin.
opkrun is used for mounting OPK files to run them.
This is seperate from Gmenu2x's own handling of OPKs.
- You need to have a supported version of Gmenu2x.
My fork of Gmenu2x supports this.
Note that the -D_CARD_ROOT=\"/media\" define at compile time does matter.
If your opk files are in /mnt/apps then you need to tell the compiler to use the folder before /mnt.
So in that case, it will just be -D_CARD_ROOT=\"/\".
Then the key of making all buttons work on the q8 isn't in recompiling the emulators one by one, but in changing the kernel. So the custom firmware thinks the q8 is in fact a bittboy.
Fix the buttons first.
Отправлено с моего HRY-LX1 через Tapatalk
Post by: kevin_yamagata on July 28, 2020, 10:23:57 pm
But let's focus on the main problems, that are:
1 - Discover and map the "Dpad Up" "B" "L" "Start" "Select" buttons and find some way to use the "Volume" button. (if you plug and unplug an otg cable into the micro usb port when in game or emulator, the cable works like a start button, i really can't understand how it happens.)
2 - Adjust the rotation and colors of the screen.
In the "Kernel" folder of Bittboy V2 CFW there is a file called "r61520fb" that corresponds to the Bittboy screen, I believe that the changes should start here.
3 - Make the speaker work.
The console plays sound if you use a headset, but the speaker does not normally play sound. (using the Bittboy V3 CFW, the speaker works and shows the sound of the Game Boy startup screen, however, the screen is completely white).
4 - CPU compatibility.
Apparently, the cpu does not use all its capacity, it is not possible to overclock, the emulators crashed when I tried. However, some ps1 games worked very well using only the default settings, without overclocking, performing similarly to that seen in LDK Vertical (I have one by the way) and even better than bittboy himself, but I'm not so sure why I haven't bought a bittboy yet.
Post by: Qinti on July 28, 2020, 11:01:51 pm
The only reason I copied and pasted the contents of the *.conf file was because it was relevant to finding the hardware mappings of the machine. Please don't copy and paste an ENTIRE file content if it is not relevant to the immediate things to be done. Just getting one or two emulators to work is a haphazard solution, which is not a solution at all.
Also, just because some information has been found does not mean this machine automatically becomes a cheaper Bittboy. Take for example the RS-69, the first generation Bittboy clone. The Chinese for it out hoping it was similar enough to make people adapt NXHope to it. But they cut so many corners that developers just saw it and did not see it as worth it when the Bittboy was ready and just needed app porting.
The only reason I have some mild interest in this is because I have one, and have some coding knowledge which might be helpful. But that's it. Adapting firmware of any sort is not as easy as it sounds. And I have not only a job but other machines that can do this. Now, if we get it working, nice, but in the meantime, please refrain from just putting stuff just because you want, say, Scumm to work.
I'll look into the mappings later on, but if any of you wants to pitch in, those codes are keyboard number codes, so they should correspond to something.
When you mapped it in the PS1 emulator, you say you can remap the keys when you plug in the USB cable. But that could not be the start key, that doesn't bring the menu, that would be the menu key. At any rate, what values did it show when you mapped. Yes I know it said it was not numbers, but what values did it give for each key?
Post by: kevin_yamagata on July 29, 2020, 12:15:57 am
This is the mapping I did for PCSX4ALL, exclusively for Crash Bandicoot (I found that I can save specific mappings for each game, it helped me a lot)
Here I will tell you which Q8 keys correspond to the ps1 layout:
Up = Dpad Down
Down = X Button
Left = Right Dpad
Right = Left Dpad
Square = Y Button
Circle = R Button
Cross = A Button
Start button in game / Menu Button on system = Usb Otg Plug
I hope you can understand better by seeing the image I made.
Post by: Soup42 on July 29, 2020, 07:27:41 am
"you could also try to modify /etc/main to rotate the screen, but you need linux to explore the rootfs parition on the sdcard.
add this line just below "modprobe r61520fb.ko":
echo 2 > /sys/class/graphics/fbcon
this is the same as the following:
You can rotate the screen setting a flag on the boot cmd line like "fbcon=rotate:1"
0 - Normal rotation
1 - Rotate clockwise
2 - Rotate upside down
3 - Rotate counter-clockwise
Most commonly you?ll have a txt file with a string of commands, usually setting the uart bound.
This should be the fix for the upside down screen.
Post by: Soup42 on July 29, 2020, 11:14:34 am
use linux to enter the squashfs partition:
you could either add a line on your /etc/inittab
add a line like this after the swapon
::sysinit:/bin/loadkeys /etc/q8.map
download loadkeys.txt (remove the .txt), copy it in the bin folder on the squashfs partition.
Am not 100% sure it's the right loadkeys version.
(((( you can also load the keymap with 'loadkeys /path/new-keymap, or create a bash script with that same command and name it like S01loadkeys.sh save at /etc/init.d/ and make sure is executable))))
now we need the keys config file, a keymap that is a text file without extension with the following in it(example):
keycode 1 = Caps_Lock
keycode 58 = Escape
Download keymap.txt, rename it to q8.map and put it in /etc/.
they keycodes can be decimal or hexadecimal, it's trial and error to find out.
just make sure you set as one of your first startup scripts something like S01loadkeys
And on the script you load the keymap you generated remaping the keys from the q8 to match
keymaps you can dump the keys dumpkeys > original-keymap on the current hardware,
modify to match the keycodes you need and load the new keymap with loadkeys.
So, the bittboy has a startup script, we need to load a keys.ini file in at booting of the device.
Thanks go out to Boogaer!
Post by: Soup42 on July 29, 2020, 09:56:23 pm
Post by: kevin_yamagata on July 30, 2020, 03:52:48 pm
I managed to add Mupen64Plus and Desmume to Gmenu2x and made it run, however, as expected, it didn't work.
It shows this message that appears in the image, the same goes for Desmume.
I am currently downloading the previous CFWs from Bittboy V2. I did a test with V4.2 and it worked, the sound works normally, however, no button responds. Even adding the new input file, the buttons do not respond.
I will continue testing previous versions of the system, maybe some will work with the sound and buttons at the same time.
Ps: I'm just doing this to find new possibilities.
Post by: kevin_yamagata on July 30, 2020, 04:38:34 pm
This CFW:
https://www.dropbox.com/sh/04vuy4vwbz7tdn1/AABpeMqAmLP8_d6tnpEbIMyza/Custom%20Firmware?dl=0&lst=&preview=Bittboy_v2_v2.5_Only_CFW_v3.8_beta_18-05-19.img.7z&subfolder_nav_tracking=1
Worked very well, the sound works perfectly, however, the button mapping is completely different from the other versions. (The screen continues with the same problems).
I will take the time to find out what is the correct mapping because I am working on some Design projects.
In short, I believe that we can use this version to do the tests. Now I can install Opks on the bittboy, but I don't guarantee they will work, just like with Mupen64Plus.
For that, I unzip the Opk using 7zip, move it to the Sd of Q8, in the Emu / App folder, go to the gmenu2x / section / folder, and create a new file for the emulator / app I want to add. Basically I create an emulator Link for Gmenu2x.
If someone has an opk that finds the mapping of the buttons, just send it here on the thread and I'll do the test on my Q8.
Post by: Soup42 on July 30, 2020, 05:16:29 pm
you can download emu's here: https://github.com/steward-fu/miyoo/releases
like openbor for double dragon kind of games.
@kevin_yamagata so sound/volume is working? Screen upside down, did you install ubuntu/linux for the patching? Buttons again different, did you try the keyloader at systemstartup?
For opk's to work, we need another version of gmenu2x and kernel.
Post by: kevin_yamagata on July 30, 2020, 05:47:03 pm
Post by: Soup42 on July 30, 2020, 08:56:47 pm
** UPDATE
This CFW:
https://www.dropbox.com/sh/04vuy4vwbz7tdn1/AABpeMqAmLP8_d6tnpEbIMyza/Custom%20Firmware?dl=0&lst=&preview=Bittboy_v2_v2.5_Only_CFW_v3.8_beta_18-05-19.img.7z&subfolder_nav_tracking=1
Worked very well, the sound works perfectly, however, the button mapping is completely different from the other versions. (The screen continues with the same problems).
I will take the time to find out what is the correct mapping because I am working on some Design projects.
In short, I believe that we can use this version to do the tests. Now I can install Opks on the bittboy, but I don't guarantee they will work, just like with Mupen64Plus.
For that, I unzip the Opk using 7zip, move it to the Sd of Q8, in the Emu / App folder, go to the gmenu2x / section / folder, and create a new file for the emulator / app I want to add. Basically I create an emulator Link for Gmenu2x.
If someone has an opk that finds the mapping of the buttons, just send it here on the thread and I'll do the test on my Q8.
Could you figure out the mapping of the buttons, like you did with the latest custom firmware?
The reason the files are in iso format is that there is a hidden partition only readable with a linux system. So when i tried to fix the os, i made some changes in the hidden partition. So the iso files should fix the upside down screen, and some buttons should be at their right location.
Post by: Soup42 on July 31, 2020, 07:24:22 am
** UPDATE
This CFW:
https://www.dropbox.com/sh/04vuy4vwbz7tdn1/AABpeMqAmLP8_d6tnpEbIMyza/Custom%20Firmware?dl=0&lst=&preview=Bittboy_v2_v2.5_Only_CFW_v3.8_beta_18-05-19.img.7z&subfolder_nav_tracking=1
Worked very well, the sound works perfectly, however, the button mapping is completely different from the other versions. (The screen continues with the same problems).
I will take the time to find out what is the correct mapping because I am working on some Design projects.
In short, I believe that we can use this version to do the tests. Now I can install Opks on the bittboy, but I don't guarantee they will work, just like with Mupen64Plus.
For that, I unzip the Opk using 7zip, move it to the Sd of Q8, in the Emu / App folder, go to the gmenu2x / section / folder, and create a new file for the emulator / app I want to add. Basically I create an emulator Link for Gmenu2x.
If someone has an opk that finds the mapping of the buttons, just send it here on the thread and I'll do the test on my Q8.
I read that opk files made for the dingoo have best compatibility.
Post by: kevin_yamagata on August 01, 2020, 01:44:15 am
** UPDATE
This CFW:
https://www.dropbox.com/sh/04vuy4vwbz7tdn1/AABpeMqAmLP8_d6tnpEbIMyza/Custom%20Firmware?dl=0&lst=&preview=Bittboy_v2_v2.5_Only_CFW_v3.8_beta_18-05-19.img.7z&subfolder_nav_tracking=1
Worked very well, the sound works perfectly, however, the button mapping is completely different from the other versions. (The screen continues with the same problems).
I will take the time to find out what is the correct mapping because I am working on some Design projects.
In short, I believe that we can use this version to do the tests. Now I can install Opks on the bittboy, but I don't guarantee they will work, just like with Mupen64Plus.
For that, I unzip the Opk using 7zip, move it to the Sd of Q8, in the Emu / App folder, go to the gmenu2x / section / folder, and create a new file for the emulator / app I want to add. Basically I create an emulator Link for Gmenu2x.
If someone has an opk that finds the mapping of the buttons, just send it here on the thread and I'll do the test on my Q8.
Could you figure out the mapping of the buttons, like you did with the latest custom firmware?
Maybe this is something(screenfix&buttonfixtrial): https://drive.google.com/drive/folders/1sHdBiyfWhgUOLh0SCPZ73H3el6t1NCuJ?usp=sharing
The reason the files are in iso format is that there is a hidden partition only readable with a linux system. So when i tried to fix the os, i made some changes in the hidden partition. So the iso files should fix the upside down screen, and some buttons should be at their right location.
I will try it. Soon i will send you the results.
Post by: kevin_yamagata on August 01, 2020, 02:21:11 am
I tried to change the mapping, but it had no effect.
Post by: Soup42 on August 01, 2020, 05:18:01 am
I write this version "XYCQ8bittboy1.31.ISO", the sound works perfectly, the screen remains the same, but this time I had problems with the buttons. Any button I press activates the option to turn off the console.The ISO's aren't working, a pity.
I tried to change the mapping, but it had no effect.
*We could make a 'dumpkeys > keymap' and put it in the bootscript of the q8. Then we can make a new keymap and maybe the buttons would work.
For the upside screen, i uploaded the R61520.c, it's for making the gpu file for the bittboy v2 v2.5 and v3. The command to rotate the screen at boottime doesn't seem to work. More people on the net try to figure that out.
Post by: Soup42 on August 03, 2020, 06:24:42 am
https://github.com/MiyooCFW/kernel/blob/e450f31cbdc7cb019354ebeb4e1c6598cac66371/arch/arm/configs/miyoo_defconfig#L1124
Post by: Soup42 on August 03, 2020, 04:44:41 pm
It's a compiled kernel the same way as the txt file in the last post, but it's from the kernel.7z from this link: https://github.com/steward-fu/miyoo/releases/download/v1.2/kernel.7z
Downloadable here: https://drive.google.com/drive/folders/1sHdBiyfWhgUOLh0SCPZ73H3el6t1NCuJ?usp=sharing
Now we can compile the kernel, we can change what the buttons do somehow. Maybe we need to play games upside down with it.
Post by: Soup42 on August 04, 2020, 03:03:00 pm
I write this version "XYCQ8bittboy1.31.ISO", the sound works perfectly, the screen remains the same, but this time I had problems with the buttons. Any button I press activates the option to turn off the console.
sounds fixed to me! rofl
*seems when you put the brightness all the way up, it stops the static noise.
**added a txt file. It looks a bit like the ini file for the gpu driver.
And then something with this:
if(flip){
gpio_wr_dat(0xB0); //screen direction //0x70 for 3.5, 0xB0 for pg
} else {
gpio_wr_dat(0x70); //screen direction //0x70 for 3.5, 0xB0 for pg
}
So 3.5 stands for bittboy 3.5 and pg stands for pocketgo. It seems they have screens in opposite directions, one updown the other downup. Should be something to look at.
** with this line:
suniv_setbits(iomm.debe + DEBE_REGBUFF_CTRL_REG, (1 << 0));
it is working upside down, without it it is garbled screen.
**not making much progress. Maybe the rom of the bittboy v1 is something: https://mega.nz/folder/TYBREKgI#TDZnZrUd2PWKgwkq3_RJ5g
***the pocketgo has a f1c100s cpu/gpu, the q8/bittboy2 have f1c500s cpu. So can't just use the rom for pocketgo.
Post by: Fishfan on August 09, 2020, 02:29:16 pm
Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Post by: Soup42 on August 10, 2020, 05:20:41 pm
Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Does it play castlevania on the snes well? And what about zelda for the snes, cause it's unplayable with version 1.2.
Post by: kevin_yamagata on August 10, 2020, 11:40:49 pm
Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Yes, just copy the folder "game" and all content for the new sdcard. The usb port doesnt work on windows 10, but when you connect the usb cable, plug on the pc and turn on the Q8, you will hear a alert message telling something about "the windows could not find the drivers for this device". Maybe, if you connect the Q8 on a Linux OS he should display another result.
Post by: Soup42 on August 11, 2020, 06:54:08 am
Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Yes, just copy the folder "game" and all content for the new sdcard. The usb port doesnt work on windows 10, but when you connect the usb cable, plug on the pc and turn on the Q8, you will hear a alert message telling something about "the windows could not find the drivers for this device". Maybe, if you connect the Q8 on a Linux OS he should display another result.
I tried linux, not working. Asked ali if i could have the rom, they said no. Now i ask if there's a way to update the q8.
Post by: Fishfan on August 11, 2020, 11:49:44 am
Thks. Copy to 4gb micro SD. Not sure 32GB card workHello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Yes, just copy the folder "game" and all content for the new sdcard. The usb port doesnt work on windows 10, but when you connect the usb cable, plug on the pc and turn on the Q8, you will hear a alert message telling something about "the windows could not find the drivers for this device". Maybe, if you connect the Q8 on a Linux OS he should display another result.
Post by: Fishfan on August 11, 2020, 11:51:54 am
Will try. Btw, the provided games file name all in Chinese. What about yours?Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Does it play castlevania on the snes well? And what about zelda for the snes, cause it's unplayable with version 1.2.
Post by: Soup42 on August 11, 2020, 12:02:39 pm
Will try. Btw, the provided games file name all in Chinese. What about yours?Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Does it play castlevania on the snes well? And what about zelda for the snes, cause it's unplayable with version 1.2.
No, not in chinese. Can you try zelda on the snes? When you walk out of the house in zelda, all the environment is black, so you can't see where you walk. So it's unplayable.
Post by: Fishfan on August 11, 2020, 12:41:53 pm
Will try. Too bad, mine all names in Chinese.Will try. Btw, the provided games file name all in Chinese. What about yours?Hello everyone, how are you?Hi, I HV v1.6.
I was watching some reviews on this console and noticed that its current models are coming with a firmware update. The first versions have V1.1.1 and the most recent that I found on this link https://www.youtube.com/watch?v=M7dPWxNeYNk it uses version V1.2 Any news about CFW for him?
Btw, the SD card is full. To add game, we need transfer all file to new bigger card? Usb port does not allow access to SD storage!
Does it play castlevania on the snes well? And what about zelda for the snes, cause it's unplayable with version 1.2.
No, not in chinese. Can you try zelda on the snes? When you walk out of the house in zelda, all the environment is black, so you can't see where you walk. So it's unplayable.
Post by: Fishfan on August 11, 2020, 03:52:53 pm
Post by: Soup42 on August 11, 2020, 04:14:45 pm
Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
Ok, then version 1.6 seems to have fixed that. The noise, you mean the static sound? There must be some way to put the screenbrightness at maximum, then the static noise should go away.
*the only way to update the firmware, is using an image on an sdcard put it in and turn the q8 on. So it will flash the new firmware. If that is possible that is. So, how do we get the new firmware, so we can play zelda again?
Post by: Soup42 on August 13, 2020, 09:59:11 am
Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
About that donate screen, you may be right. If you would have a display that's upside down version of the q8, you could install bittboy v2 rom. Question is how expensive such a display would be.
Post by: Fishfan on August 13, 2020, 11:49:00 am
Donate screen may come fr an older unused device or cheaper device. Not sure whether q8 screen is same as those 8 bit console screen with 24pins. Those r USD4+ when on sale, some r brighter n more comfort to look at too.Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
About that donate screen, you may be right. If you would have a display that's upside down version of the q8, you could install bittboy v2 rom. Question is how expensive such a display would be.
Post by: Soup42 on August 13, 2020, 12:12:08 pm
Donate screen may come fr an older unused device or cheaper device. Not sure whether q8 screen is same as those 8 bit console screen with 24pins. Those r USD4+ when on sale, some r brighter n more comfort to look at too.Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
About that donate screen, you may be right. If you would have a display that's upside down version of the q8, you could install bittboy v2 rom. Question is how expensive such a display would be.
Yeah, let's buy a new bittboy v2 and put the screen from it in the q8 :)
Post by: PhenomX on August 15, 2020, 04:32:22 pm
Donate screen may come fr an older unused device or cheaper device. Not sure whether q8 screen is same as those 8 bit console screen with 24pins. Those r USD4+ when on sale, some r brighter n more comfort to look at too.Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
About that donate screen, you may be right. If you would have a display that's upside down version of the q8, you could install bittboy v2 rom. Question is how expensive such a display would be.
Yeah, let's buy a new bittboy v2 and put the screen from it in the q8 :)
The screen of the Q8 is the same as any RetroFC console or any of its copies, here you can see a video where it is exchanged without any problem https://youtu.be/mBHT8aBNk1I the issue of screen inversion is for the software.
Is there a way to put firmware 1.6 to versions like 1.2? the SD memory only contains the games and special folders, right? so the original firmware is on the soc itself if I'm not mistaken.
When we load the firmware of the bittboy v2 it is like loading the operating system from an external device.
Is there any progress with the modified rom or will you need to access the console by cable to move forward?
It would be great to use it even as a music or video player, we already know that it is a limited machine, but it would be surprising to give it more functionalities :)
Post by: Soup42 on August 15, 2020, 05:43:46 pm
Donate screen may come fr an older unused device or cheaper device. Not sure whether q8 screen is same as those 8 bit console screen with 24pins. Those r USD4+ when on sale, some r brighter n more comfort to look at too.Snes castlevania fairly playable, same goes to SNES Zelda. Did not experience any black out like what u said. Zelda sound noisy, can't stand in longer play. Also, cheap screen too , can't play long run. Need find a donate screen for this console.
About that donate screen, you may be right. If you would have a display that's upside down version of the q8, you could install bittboy v2 rom. Question is how expensive such a display would be.
Yeah, let's buy a new bittboy v2 and put the screen from it in the q8 :)
The screen of the Q8 is the same as any RetroFC console or any of its copies, here you can see a video where it is exchanged without any problem https://youtu.be/mBHT8aBNk1I the issue of screen inversion is for the software.
Is there a way to put firmware 1.6 to versions like 1.2? the SD memory only contains the games and special folders, right? so the original firmware is on the soc itself if I'm not mistaken.
When we load the firmware of the bittboy v2 it is like loading the operating system from an external device.
Is there any progress with the modified rom or will you need to access the console by cable to move forward?
It would be great to use it even as a music or video player, we already know that it is a limited machine, but it would be surprising to give it more functionalities :)
the chinaman says it's not possible to update the internal flash through sd card. uart cable, should give terminal connection. On the discore they say there's more possible then.
Post by: jamespoo1 on August 17, 2020, 12:44:38 pm
Post by: Soup42 on August 18, 2020, 06:07:59 am
Post by: Qinti on August 22, 2020, 04:06:15 am
Post by: kevin_yamagata on August 22, 2020, 12:49:48 pm
Would it be possible to build a drive for the Q8 screen and implement it in the Bittboy Kernel?
Does anyone have a Usb TTL cable and can try to rip the stock firmware? When I tear down the Q8, I saw that it had an area for the TTL cable.
I will ask again on Discord channels to find out if more people can help with Q8.
Post by: Soup42 on August 22, 2020, 01:47:43 pm
Hello I have some doubts:
Would it be possible to build a drive for the Q8 screen and implement it in the Bittboy Kernel?
Does anyone have a Usb TTL cable and can try to rip the stock firmware? When I tear down the Q8, I saw that it had an area for the TTL cable.
I will ask again on Discord channels to find out if more people can help with Q8.
I thought it was something with a uart cable, so you can connect it uart-cable/usbcable to the pc and you can use putty to get to the terminal of the q8.
Then this, i quote:"Yes, i am aware for the UART port but that only works one way as far as i know, not two-away and it is mostly used for getting debug logs.
And well, a mini USB to USB adapter could in theory allow for a small wifi adapter to be plugged in but from what i gather, the current kernel does not support that yet."
so it's for extracting logs from the device. Like buttoncodes.
Post by: Djvanbeat on August 25, 2020, 10:13:53 pm
Hello I have some doubts:Hi , sorry for a long time disconnected ,but my mother is old and she's fall and broke is pelvis ,and now im with her in full time.
Would it be possible to build a drive for the Q8 screen and implement it in the Bittboy Kernel?
Does anyone have a Usb TTL cable and can try to rip the stock firmware? When I tear down the Q8, I saw that it had an area for the TTL cable.
I will ask again on Discord channels to find out if more people can help with Q8.
you can buy this adapter ,from aliexpress ,this is too cheap,and can make test with this , caution the board of xyc q8 got two ports i think the correct is in left side of this board.
regards and
see you again ;)
Post by: kevin_yamagata on August 27, 2020, 03:52:27 pm
Post by: Soup42 on August 28, 2020, 03:50:38 pm
Post by: kevin_yamagata on August 30, 2020, 06:59:38 pm
Well, well, if the screen driver is ported to these systems, we will have the cheapest bittboy clones on the market.
Post by: PhenomX on August 30, 2020, 10:09:50 pm
https://www.youtube.com/watch?v=ICiv1-oTzDUIt would be great, it seems that the firmware of these systems is somewhat improved compared to the original Q8, at least I notice that there is no longer the horrible lag in the sound. Personally I prefer the digital cross control, compared to the analog control of these versions. Being able to do more with these inexpensive consoles would be extraordinary, game ports, media player, etc. Something important is to solve as you say the configuration of the screen ::)
Well, well, if the screen driver is ported to these systems, we will have the cheapest bittboy clones on the market.
Post by: Soup42 on September 01, 2020, 05:23:13 pm
Post by: kevin_yamagata on September 01, 2020, 06:34:43 pm
what's with these roms: https://github.com/retrofw/retrofw.github.io/releases ?
Dont work, these systems are completely different. I Have a RetroFw device, the LDK Vertical. It has 128mb of Ram, and a ingenic JZ4060B cpu, a lot different than bittboy.
Post by: Soup42 on September 05, 2020, 06:51:30 pm
It says it supports the ability to flip the screen. So if we compile it, we can use the main flip command to flip the screen right. But when i git clone the device tree, the flip text isn't found in the miyoo-defconfig file anymore.
I added a .c file for the gpu driver module. It's in c++ and i don't know what to change to get the screen flipped. Tried some things, but always white screen as a result. So we need a programmer now to alter the file so it makes an normal screen again when compiled.
Post by: Soup42 on September 08, 2020, 11:17:52 am
what's with these roms: https://github.com/retrofw/retrofw.github.io/releases ?
Dont work, these systems are completely different. I Have a RetroFw device, the LDK Vertical. It has 128mb of Ram, and a ingenic JZ4060B cpu, a lot different than bittboy.
Kevin, can you do something with this key logger app?
It is an SDL application. Put the files in a folder and create a link to it.
Post by: kevin_yamagata on September 08, 2020, 12:01:38 pm
Post by: jamespoo1 on September 11, 2020, 01:11:29 am
Post by: PhenomX on September 11, 2020, 01:12:51 pm
for like around 8usd more or so you could get a pocket go that will be much better then this
It is possible, but I do not see the problem in trying it, it does not seem very complicated and there would be a multitude of models that could be improved, it is more than anything a personal challenge, I understand it, I am enthusiastic about the project and I encourage it to continue and If I can help with something I will :)
Post by: Soup42 on September 11, 2020, 08:42:37 pm
for like around 8usd more or so you could get a pocket go that will be much better then this
It is possible, but I do not see the problem in trying it, it does not seem very complicated and there would be a multitude of models that could be improved, it is more than anything a personal challenge, I understand it, I am enthusiastic about the project and I encourage it to continue and If I can help with something I will :)
Then, go find a programmer to adapt the .c file i uploaded :) .
Post by: PhenomX on September 12, 2020, 06:33:52 am
for like around 8usd more or so you could get a pocket go that will be much better then this
It is possible, but I do not see the problem in trying it, it does not seem very complicated and there would be a multitude of models that could be improved, it is more than anything a personal challenge, I understand it, I am enthusiastic about the project and I encourage it to continue and If I can help with something I will :)
Then, go find a programmer to adapt the .c file i uploaded :) .
Maybe it doesn't help much, and sorry for my bad English xD.
What do you think of the following assessment? If I'm wrong, I'm sorry, I do what I can :P
I have downloaded the configuration file and reviewed the screen rotation part, the configuration part writes some information on some gpio pins of the chip to configure the orientation of the screen, changing that configuration without knowledge, it seems complicated. But the creator of the configuration must know what values to change since he knows how the soc f1c500s / f1c100s works.
https://www.thirtythreeforty.net/media/F1C100s_Datasheet_V1.0.pdf
It seems to be the same person who started the creation of the custom official firmware and it appears in the file, perhaps it would be possible to contact him , your contact information is as attached:
MODULE_AUTHOR ("Steward Fu <[email protected]>");
https://github.com/steward-fu/miyoo
Possibly I could solve all the doubts easily, I could even guide in the problem of adjusting the wrong colors on the screen, that is a typical problem when changing a tv lcd panel and changing a value in the tv firmware is solved, I hope kindly help us :)
If that's okay with you, could you tell him the details better?
Post by: Soup42 on September 12, 2020, 09:34:30 am
for like around 8usd more or so you could get a pocket go that will be much better then this
It is possible, but I do not see the problem in trying it, it does not seem very complicated and there would be a multitude of models that could be improved, it is more than anything a personal challenge, I understand it, I am enthusiastic about the project and I encourage it to continue and If I can help with something I will :)
Then, go find a programmer to adapt the .c file i uploaded :) .
Maybe it doesn't help much, and sorry for my bad English xD.
What do you think of the following assessment? If I'm wrong, I'm sorry, I do what I can :P
I have downloaded the configuration file and reviewed the screen rotation part, the configuration part writes some information on some gpio pins of the chip to configure the orientation of the screen, changing that configuration without knowledge, it seems complicated. But the creator of the configuration must know what values to change since he knows how the soc f1c500s / f1c100s works.
https://www.thirtythreeforty.net/media/F1C100s_Datasheet_V1.0.pdf
It seems to be the same person who started the creation of the custom official firmware and it appears in the file, perhaps it would be possible to contact him , your contact information is as attached:
MODULE_AUTHOR ("Steward Fu <[email protected]>");
https://github.com/steward-fu/miyoo
Possibly I could solve all the doubts easily, I could even guide in the problem of adjusting the wrong colors on the screen, that is a typical problem when changing a tv lcd panel and changing a value in the tv firmware is solved, I hope kindly help us :)
If that's okay with you, could you tell him the details better?
Isn't the direction maked out here:
if(flip){
gpio_wr_dat(0xB0); //screen direction //0x70 for 3.5, 0xB0 for pg
} else {
gpio_wr_dat(0x70); //screen direction //0x70 for 3.5, 0xB0 for pg
}
it stands twice in the .c file. So maybe we just have to twice change the direction to pg?
Post by: PhenomX on September 12, 2020, 06:42:25 pm
#endif
case MIYOO_FB0_SET_FLIP:
flip = (bool)arg;
writel(0x11111110, iomm.gpio + PD_CFG0);
writel(0x11111101, iomm.gpio + PD_CFG1);
writel(0x00111111, iomm.gpio + PD_CFG2);
writel(0xffffffff, iomm.gpio + PD_DATA);
mdelay(50);
gpio_wr_cmd(0x28);
mdelay(250);
gpio_wr_cmd(0x36);
if(flip){
gpio_wr_dat(0xB0); //screen direction //0x70 for 3.5, 0xB0 for pg
} else {
gpio_wr_dat(0x70); //screen direction //0x70 for 3.5, 0xB0 for pg
}
As I read to you before, you have only been able to rotate text but not the menus, and in some cases you have not been able to obtain an output image, it is clear that there are some parameters that we do not change correctly.
Although a little information is missing, there is a lot of work done, and it takes less to see the light :o
Come on! who is encouraged to give a little help! :)
Post by: Soup42 on September 14, 2020, 06:38:02 am
Ok, so i uploaded the .c file for the bittboy 2. Tried flipping the screen, i either got first garbled then upside down screen, or just garbled completely.
Seems like something is overriding the flip command.
OK, so i wrote an email to Steward Fu. He answered quick. Can't make much out of it though:
Hi,
thanks for your email :)
in panel_init(), switch miyoo_ver, case 2:
gpio_wr_cmd(0x36);
gpio_wr_dat(0x70); // 0xb0 rotate screen
you can also check st7789v datasheet for this command :)
thanks
Best regards
Steward
Post by: PhenomX on September 15, 2020, 03:26:40 pm
I guess the .c file before this post, is the wrong one. It's for bittboy 3 not for bittboy 2.
Ok, so i uploaded the .c file for the bittboy 2. Tried flipping the screen, i either got first garbled then upside down screen, or just garbled completely.
Seems like something is overriding the flip command.
OK, so i wrote an email to Steward Fu. He answered quick. Can't make much out of it though:
Hi,
thanks for your email :)
in panel_init(), switch miyoo_ver, case 2:
gpio_wr_cmd(0x36);
gpio_wr_dat(0x70); // 0xb0 rotate screen
you can also check st7789v datasheet for this command :)
thanks
Best regards
Steward
I hope you have luck with the file 61520fb.c.txt that you comment, I have found the latest revision of the datasheet that Steward refers to, at least the most current I have found.
https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf
On sheet 125 there is some information regarding orientation, however the information in this manual should be taken with care, since the two consoles are not exactly the same panel and they may not be completely compatible.
It is unbelievable that little effort on the part of the manufacturer to help develop for their "open source" console.
Thank you very much for all the work you are doing.
Post by: Soup42 on September 15, 2020, 05:29:27 pm
I guess the .c file before this post, is the wrong one. It's for bittboy 3 not for bittboy 2.
Ok, so i uploaded the .c file for the bittboy 2. Tried flipping the screen, i either got first garbled then upside down screen, or just garbled completely.
Seems like something is overriding the flip command.
OK, so i wrote an email to Steward Fu. He answered quick. Can't make much out of it though:
Hi,
thanks for your email :)
in panel_init(), switch miyoo_ver, case 2:
gpio_wr_cmd(0x36);
gpio_wr_dat(0x70); // 0xb0 rotate screen
you can also check st7789v datasheet for this command :)
thanks
Best regards
Steward
I hope you have luck with the file 61520fb.c.txt that you comment, I have found the latest revision of the datasheet that Steward refers to, at least the most current I have found.
https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf
On sheet 125 there is some information regarding orientation, however the information in this manual should be taken with care, since the two consoles are not exactly the same panel and they may not be completely compatible.
It is unbelievable that little effort on the part of the manufacturer to help develop for their "open source" console.
Thank you very much for all the work you are doing.
Thanks! We are looking for the MADCTR ML=0: command. So in case 2 of the .c file, there should be either a 0 or a 3 written somewhere. In the pdf you linked to, it says binary 00 or 11, so that means hexadecimal 0 or 3 value. In the .c file in case 2 (bittboy v2), it says a gpio_wr_cmd(0x??); followed by a gpio_wr_dat(0x??); command, the wr_cmd is probaby the director to a register, the wr_dat is probably what is written to that register as a value. One register should be for the placing/rotating of the screen.
Post by: Soup42 on September 17, 2020, 12:00:51 pm
I tested the program on my q8, the keys are still not recognized by the system.
@kevin_yamagata can you do this on the q8? dmesg > /mnt/log.txt ? And upload the log.txt here?
*ok, so i created the log.txt. I also tried to get the keycode of the 'Y' button. It doesn't get detected though.
Post by: Soup42 on September 19, 2020, 03:02:27 pm
#define IN_L1 ((32 * 2) + 1)
#define IN_R1 ((32 * 2) + 2)
#define IN_L2 ((32 * 4) + 0)
#define IN_R2 ((32 * 2) + 3)
#define OUT_1 ((32 * 4) + 7)
#define OUT_2 ((32 * 4) + 8)
#define OUT_3 ((32 * 4) + 9)
#define IN_1 ((32 * 4) + 2)
#define IN_2 ((32 * 4) + 3)
#define IN_3 ((32 * 4) + 4)
#define IN_4 ((32 * 4) + 5)
#define IN_A ((32 * 3) + 0)
#define IN_TA ((32 * 3) + 9)
#define IN_B ((32 * 0) + 3)
#define IN_TB ((32 * 2) + 0)
#define IN_MENU ((32 * 4) + 1)
as:
#define IN_A ((32 * PORT) + PIN)
So the port and pinnumbers are per button.
https://github.com/MiyooCFW/kernel/blob/master/drivers/input/keyboard/miyoo_kbd.c
port and pinnumber: gpio
https://docplayer.net/145603969-Allwinner-f1c500-datasheet.html
@kevin_yamagata how did you manage to use the buttons on the q8? Cause no button is responding on my device.
Post by: kevin_yamagata on September 21, 2020, 10:43:33 pm
Post by: Soup42 on September 22, 2020, 01:19:08 pm
Continues the same thing, the buttons doesnt work. I think that just the TTL cabe can find the log of key buttons.
eh, the buttons are read out by port and pin numbers. The kernel needs to have that information to respond to it. But the f1c500s datasheet talks about gpioC D E and F, so those are letters not numbers. Those should be numbers to add them in the kernel.
Post by: PhenomX on October 17, 2020, 02:22:54 pm
Post by: kevin_yamagata on October 17, 2020, 11:48:18 pm
Hello! I have great news for this little console, one awesome dev (from GZnetwork discord server) talked with me about the q8 issues and he already are working on the system port and making your own tests! He maneged dump the original firmware and will share with me as soon he can, then i will share with you guys.
I will keep this board updated.
Thanks for the patience!
Post by: PhenomX on October 19, 2020, 11:51:20 am
Post by: LuckyKiller69 on October 20, 2020, 06:41:46 pm
I Buy This Handheld Yesterday Ago, And I Research This Handheld And Do Full Review
For NES Its Running Perfect Like SUP 400 Handheld .. :)
GBA, SNES And Mega Drive Can Running Good But Not All Downloaded Can Playing ..
And Very Bad To MAME, I Don't Know Why ..
I Tries Metal Slug 1 But Cannot Running, I Try And Always Fast Force Close
Only Can Played From Originally Factory Home Screen MAME Games :'(
And For MAME, I Try Arkanoid, But When Opening Process, Showing Text "Bad Hardware" And Frezee / Crash :'(
So All Downloaded MAME Cant Playing :'(
I Research Other Handheld But Like This, I Found It ..
Its Named "M3 Sup Gamebox" And "Retro X12 Plus"
Theres On MAME Games On HomeScreen, Already Have "Metal Slug X"
And Can Playing And Running Good Too For NeoGeo ..
I Think This 3 Handheld Its Same Chipset And Other Component, But What Different This XYC Q8 To 2 Other ??
Oh Yes, My Version Firmware Is 1.4 on This XYC Q8, Maybe Very Latest Version ?
I Waiting Your All Comment And Tips & Trick, Thanks :')
Ohh I Almost Forgot, Im So Simple Review Video And Uploaded To YouTube, I Want You Help To Comment In There Too ..
My YT Channel "Lucky Anggora"
Or .. You Search Key "XYC Q8 Retro Handheld" But Setting To Latest Video ..
Thanks :')
Post by: LuckyKiller69 on October 20, 2020, 06:47:48 pm
Different Only To Direction Button Change To "Analog" ::)
But Still Same From Graphic, Sound, And System Like XYC Q8, There Home Screen Ready "Metal Slug X" Can Playing And Running Good, Do You All Have This Handheld Too ??
Are You Already Test All MAME From Downloaded ?? ::)
Im Waiting Your Comment Answer, Thanks ~ ;D
Post by: didingo on October 22, 2020, 07:14:33 pm
just bought q8 because of its design. i like it a lot more then the m3 and others...
cant wait for you guys to make a new firmware for it!! thank you so much!!!
and..what is the latest version of STOCK firmware on q8 \ m3 ??? can u please dump it and share here? i wonder if M3 has a new firmware better than q8... can i put it on q8??
sorry for my bad english. greetings from russia!
Post by: LuckyKiller69 on October 25, 2020, 04:06:06 pm
I Hope You Can Test And Always Trial And Error Because Not All Games Can Played On This Handheld
For NES, All Games Can Run Normally Not Problem
But The Problem Showing To SFC, Sega Drive, GBA, And Very Fatal To MAME
Not All Games Can Run Normally In 3 Emu : GBA, SFC, SEGA DRIVE
If The Game Heavy So Much Will Broken With Error, Crash, And Many Bug & Glitch
The Fatal Problem In MAME, Just I Don't Know Why This Failed Handheld (Maybe)
Can Success Go To Market ( Not Through Test In Factory )
You Can Only Played MAME With Original MAME China Folder Inside, For Downloaded Other MAME Games You Cannot Playing
Okay, For You Answer Request ..
Im Very Sure If M3 Is The Same Chipset With Q8
Because If You Watching All Review Video M3 SupBox In Youtube ..
The FPS Its Run Same Like Q8, Not Different So Much ..
Average 30 FPS
But The Core Different Is You Can Running Metal Slug On HomeScreen M3 SupBox
You Know Metal Slug Is Heavy Game Because SFX, Battle Effect Is So Fun ..
And For Firmware And Copying To Q8 From M3, Hmm I Dont Know Or Very Sure Can Make Q8 Can Run More Better ..
We Wait For Better Firmware Ok ?
Because Is Under Processs Now ..
Post by: LuckyKiller69 on October 25, 2020, 04:09:45 pm
I Test And Try Open ..
Will Always Crash, Frezee, And Showing Error & Glitch Bug
So You Can Look Down Here, Thanks ..
Post by: LuckyKiller69 on October 25, 2020, 04:12:23 pm
The List Upper Is From SNES Games List, Is Cant Running ..
And Down Here Is GBA Games List, Cannot Running Too
Post by: PhenomX on November 02, 2020, 01:21:50 pm
The issue of incompatibilities with games, we will also have them with the CFW emulators, less, but there are -\ _ (ツ) _ /-
Post by: 02k0 on November 15, 2020, 08:24:16 am
https://a.aliexpress.com/_ms0S5Xf
And
https://a.aliexpress.com/_mtYM2BF
(This is a great upgrade, support 10 emulator!)
Post by: Qinti on November 15, 2020, 06:43:42 pm
At that price I would just buy any other machine that is known to work with CFW, such as the Q90, RS-99, Bittboy or Pocket go. They have better build quality, better support, and will last longer.
Post by: 02k0 on November 16, 2020, 07:50:15 am
This is no upgrade, all they did was just separate the games a little, probably by using a different firmware. If they changed the board you can forget about CFW, the Q8 is only partially compatible and there is not enough interest to warrant creating a fork for it (so far).Thank you friend! Would you know if this process is good and powerful?(https://uploads.tapatalk-cdn.com/20201116/b340abf60c19afbcee85950308c1de55.jpg)
At that price I would just buy any other machine that is known to work with CFW, such as the Q90, RS-99, Bittboy or Pocket go. They have better build quality, better support, and will last longer.
Post by: 02k0 on November 17, 2020, 08:56:26 am
New versions:This looks like an update to the FC3000. But there is no video to confirm.
https://a.aliexpress.com/_ms0S5Xf
And
https://a.aliexpress.com/_mtYM2BF
(This is a great upgrade, support 10 emulator!)
Post by: PhenomX on December 06, 2020, 06:20:12 pm
Advance us any news or advance please ;)
Post by: v47 on December 24, 2020, 08:06:41 pm
Better than RS69, but not by a huge margin.
Post by: whisky on December 26, 2020, 03:57:15 pm
Hello! I have great news for this little console, one awesome dev (from GZnetwork discord server) talked with me about the q8 issues and he already are working on the system port and making your own tests! He maneged dump the original firmware and will share with me as soon he can, then i will share with you guys.
I will keep this board updated.
Thanks for the patience!
Hi Kevin, any news?
i bought one and i'm IT Guy. If you guys need help i'm available.
Post by: whisky on December 26, 2020, 05:05:03 pm
Ei Mano, eu ? BR tamb?m, em?
Eu ainda n?o tenho dispositivo. Mas tomara que algum desenvolvedor se comprometa a investigar tamb?m.
Enviado de meu moto g(7) play usando o Tapatalk
Eu estou aguardando os desenvolvedores do OpenDingux se interessarem em trabalhar no porte para o XYC. N?o sou programador e entendo pouco sobre os sistemas.
Oi Kevin, agora que eu vi que tu tb ? Brasileiro.
Eu sou de infraestrutura e manjo de linux bastante. Se precisarem de ajuda.
O meu chegou hoje, vou frazer uns testes. Se eu conseguir alguma coisa vou informando.
Post by: kevin_yamagata on December 29, 2020, 11:00:17 am
Whisky, yes i am brazilian too, you can share here your discoveries about the Q8, also let us know about any issues too.
There are a lot of "Q8 Clones" on the market right now, some of you guys have tried these ones? They can boot the Bittboy firmare? I Would like to know :)
Thanks, hope you guys have a great holiday. Stay safe.
Post by: SpacedAce77 on January 03, 2021, 01:43:10 am
There are a lot of "Q8 Clones" on the market right now, some of you guys have tried these ones? They can boot the Bittboy firmare? I Would like to know :)
As far as porting Q90/V90 style Miyoo CFW, i think not... Read this, and from curiosity tried it on my little Sup 5 emulator bit... No dice. Screen went white, was maybe reading input, I just couldn't see anything save for banding and small flickers toward midscreen... It'd be a vast improvement if we can run Bittboy CFW though!! Let's see if anyone else has luck... You mean the original/pre-V.3.5 Bittboys??
Also like the "Five Games Simulators" GB Pocket looking clone... $15, but wonder if it can do more! Cheap and replaceable, I still appreciate these cheap options, I get nervous dropping my RG350 or anything like that.
Post by: kevin_yamagata on January 03, 2021, 11:55:03 am
About the Q8, it can run specifically the Bittboy 2.0/2.5 CFW, the others just appears a white screen.
Post by: KdashX on January 26, 2021, 06:35:06 am
Post by: PhenomX on February 05, 2021, 07:07:57 pm
We are all waiting for news about the advances, greetings to all of us who frequent this thread :)
Post by: PhenomX on March 25, 2021, 11:02:31 pm
Post by: salvacam on March 29, 2021, 05:41:20 pm
(https://cdn.discordapp.com/attachments/579895917273022464/826086976620068864/photo_2021-03-29_15-34-27.jpg)
I've seen it on a discord server
https://discord.gg/T6UBp7JT
Post by: kevin_yamagata on March 30, 2021, 11:22:56 pm
Post by: PhenomX on March 31, 2021, 12:53:20 pm
has gotten it to look right
(https://cdn.discordapp.com/attachments/579895917273022464/826086976620068864/photo_2021-03-29_15-34-27.jpg)
I've seen it on a discord server
https://discord.gg/T6UBp7JT
Thank you very much Salvacam, it is incredible to see the advances that are taking place in this console. The result of the work can be enjoyed by thousands of people with this console and its variants.
I am looking forward to testing the new system on my XYC :)
I see that very good people are working on it who enjoy taking advantage of the power of these systems.
At least we know that some other port will be available thanks to porters like you! ;)
Post by: salvacam on March 31, 2021, 05:41:48 pm
Post by: TriForce on April 02, 2021, 02:54:22 am
has gotten it to look right
(https://cdn.discordapp.com/attachments/579895917273022464/826086976620068864/photo_2021-03-29_15-34-27.jpg)
I've seen it on a discord server
https://discord.gg/T6UBp7JT
Yes, the screen is working now thanks to some great research done by user Nyom on our Discord, he ended up getting information from the display driver similar to one of the Steward messages posted here in one of the previous posts so after a lot of testing we got it working.
So we have to fix the next things now: 1. The sound, 2. The key mapping (the system one, not the gmenu keys), 3. Continue checking stuff
;D
Post by: kevin_yamagata on April 02, 2021, 05:18:01 pm
Post by: PhenomX on April 04, 2021, 07:22:20 pm
Post by: KdashX on April 27, 2021, 08:35:29 pm
has gotten it to look righti am very happy to see this
(https://cdn.discordapp.com/attachments/579895917273022464/826086976620068864/photo_2021-03-29_15-34-27.jpg)
I've seen it on a discord server
https://discord.gg/T6UBp7JT
please, update the discord link, it expired
thank you.
Post by: TriForce on May 04, 2021, 01:12:09 am
i am very happy to see this
please, update the discord link, it expired
thank you.
the direct link is https://discord.gznetwork.com
FYI ive been busy the last weeks, so this has been slow, but some people is still helping on the keyboard mapping (thats the main thing now), also im trying to figure out whats the problem with the current uboot/kernel that makes the latest cfw not loading properly on this, an old source code we have launch correctly, so we are still working on that...
Post by: PhenomX on June 03, 2021, 08:25:50 pm
The little that I have been able to test with it (with the screen inverted, with the colors in negative and without having the operating system adapted yet) I have been able to see that this console has a lot of potential.
Once the button issue and the latest firmware are saved, the project should move very quickly.
The emulation compared to the Chinese firmware is amazing.
If you know more information, we will be waiting for any new news ;)
Post by: TriForce on June 29, 2021, 01:37:33 am
Once the button issue and the latest firmware are saved, the project should move very quickly.
Someone already helped us with the button stuff on a Sup M3, due that one is very similar to XYC Q8 we are near to have both consoles ready to include them on the next miyoo release
Post by: kevin_yamagata on June 29, 2021, 02:19:02 pm
There is a heck of M3/XYC variations on the market, when the new miyoo firmware version was released the other users could try it and see if the system is compatible with your current console variation :)
Post by: PhenomX on July 06, 2021, 11:59:00 pm
Post by: LuckyKiller69 on July 26, 2021, 05:36:51 pm
And This Custom Rom Project Can Running New Emulator Like GB, GBC, PS1, N64 ???
And What New update News About This Project ?? Sorry, If My English Bad, I Waiting this .. thanks
Please Reply Me Everyone Here If Know Something About This project .. thanks