Interesting, what are the benefits of this firmware versus the stock firmware?If he did base the kernel on the RG-350 kernel, then it should have BGR colorspace support. (mostly useful for PCSX4ALL and can also be compiled for support in ReGBA)
And if necessary, could the stock firmware be flashed back to the device? Since the Pocket Go 2 uses a removable TF1 card for the firmware.
My Pocket Go 2 hasn't arrived yet.
It supports the same as the RG350, file systems, it is screen scaling in Hardware mode, combinations with the power button for functions (such as brightness adjustment). Of course, this console has no rumble and something else, the pscx4all emu of the RG350 works in this one, but you cannot map the R2 and L2 because they have different definitions, for that you have to use one of GCW0 or the one in the SD_IMAGEN.binThat sounds good. so it does support BGR colorspace support. I thought it had rumble, oh well.
ROGUE OFICIAL FIRMWARE FOR POCKET GO 2(https://raw.githubusercontent.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/master/logos/logo_gcwzero_clut224.png)Same features that RG350 "ROGUE" CFW https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/ (http://CFW https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/)RELEASE 1.0.0https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/releases/tag/v1.0.0 (https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/releases/tag/v1.0.0)
I'm new to this, how to flash OFW?You need the sd_card.bin for first time because the image make for Jutleys has the system partition corrupts (Again)
just copy all opks and sdcard_image.bin to /apps folder?
Finally! Yes the Combos work now <3
Thank you very much =]
It is possible to add BGR-Support?
No I mean this RGB to BGR thing what some of the newer versions of emulators using.
Like ReGBA or pcsx4all. Without this support the colors are off.
Try the pcsx4all version from sauce and you will see what I mean.
https://gameblabla.nl/files/ipk/gcw0/pcsx4all_rg350.opk
In the future there will be support for PocketGo 1?
Enviado de meu moto g(7) play usando o Tapatalk
And this shit console, soes it support custom firmware?In the future there will be support for PocketGo 1?
Enviado de meu moto g(7) play usando o Tapatalk
hmmmm I have that console too, but I don't know if I want to go through the hell I had to go through in order to adapt the kernel hahahaha. If it weren't because they sent me the console to do it, I would have given up days ago hahahahaha.
For this use the same drivers that RG350 in win10
Enviado desde mi Redmi 4 mediante Tapatalk
For this use the same drivers that RG350 in win10
Enviado desde mi Redmi 4 mediante TapatalkI will give it a try, I did try that when running the Stock FW but it did not work :(
UPDATE - I have tested with the RG-350 driver, it gives an error "No Driver for Specified Device" even when selecting manually :(
To install the CFW I flashed the "Bin file" then run the kernel OPK file.... Is that correct ?
I would like to know, does Rogue firmware (or even the stock firmware for Pocket Go 2, RG 350 etc) support a 50 HZ display mode?That could require tweaking the LCD timings. I'm fairly certain that it could be in theory possible for 50 hz (though it depends on the display and i'm not sure if that would work, i haven't tried it yet) but how to expose this to the software, i'm not sure. (probably a kernel dev interface of some kind like for the IPU)
One of the issues with the GCW Zero was that it could only output at 60 HZ, so some games that run at 50 FPS like PAL region games or Cave Story did not play smoothly.
This is not about the analog stick.
This is about the dpad.
This is not about the analog stick.
This is about the dpad.
you try the release
I'm on Rogue 1.0, sometimes after power on or reboot TF2 in not detected and the GUI become laggy
So I must hold the power button to turn off the device because both reboot and power off menu not working.
Did a fresh install to SD with v1.0.1
I can say the clock does not work anymore. I gets reset after a reboot.
Is there a way to just remove or hide the clock in Gmenu2x?
Or maybe that can be build in?
Ok, cool. Good work mate! ;D
Ok, cool. Good work mate! ;D
Mario bros 3, release!!
You can update directly.Ok, cool. Good work mate! ;D
Mario bros 3, release!!
AWESOME! 8)
You're my hero.
I can just "flash" the new OPK over my v1.0.1 install right?
Also, would it be possible to hide the clock in Gmenu2x?
Is that something that can be accomplished?
What do you mean with:
Gmenu2x now can show two type of previews (put in /(romsdir)/.previews/).
Heads up:
Your title "RELEASE 1.0.2" in the first post redirects to the v1.0.1 release url instead of v1.0.2
https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/releases/tag/v1.0.2
Hi, I just updated to 1.0.2 (OPK update from 1.0.1).
I can't set the date and time with the clock app. If I press select it closes... How come? Is there a settings folder in home (I copied over my home form RG350).
-EDIT-
I will try a clean flash of 1.0.2, and report.
-EDIT 2 -
Still happening after a clean flash. You need a very short press on select otherwise it exits. Very finicky. I was able to set time though. A minor issue but it should probably be adressed.
Another question, where should my external sd card be mounted? Can't see it in /media nor /mnt...
How do the new GMenu2x previews work? What are the types and the corresponding directory and file naming convention under . previews?
I installed Rogue 1.2 on my pocketgo 2, and I seemed to hit a bug. My R2 button does not respond. it works with the stock firmware, along with the 1,0 build of Rogue, so I can rule out my hardware being the problem.
I love what I see other wise, thank you!
Would it be possible to add one or more extra overclock step(s) in to the firmware?
1080MHz is already great for most games but maybe we can squeeze a little more out of the device?
Maybe great 3 steps: 1000 - 1080 - 1150 (ish)?
People that don't want an overclock can go back to 1000MHz.
Just my 2 cents. 8)
just got my playgo powering on i can't get to the menu it just goes from the logo to wall of text sometimes in loops. what are the steps/programs recommended for windows 10 users? does the smaller partition need to be extended up to a certain amount in order to boot correctly?Same with me when trying this firmare.
However,with the stock firmware what happened to me was launching many roms from any of the emu's would cause the unit to reboot.so far i've only tried on the latest 1.0.2 firmware release with the stock 16gb. i'll see if i have any luck with different cards and maybe older release
And some apps,like changing wallpaper,launching clock for eg would cause the unit to freeze.
So first I tried flash of the clean disk image available,same thing.
So then I thought Id this Rogue firmare,but it just loops for me.
(Stiil have original 32GB card it came with ofcourse so Ive been doing this with spare 16GB card)
No,I didnt see the menu with the Rogue FM,Im having exact same issue as your pics,
so far i've only tried on the latest 1.0.2 firmware release with the stock 16gb. i'll see if i have any luck with different cards and maybe older release
well you got to see the menu thats at least something :)
Nothing has been touched on buttons since I created the first functional kernel, as it is manufactured, I was not surprised that the button starts to fail.
Nothing has been touched on buttons since I created the first functional kernel, as it is manufactured, I was not surprised that the button starts to fail.
That's weird. I do not think its a hardware failure. When I downgrade back to rogue 1.0, ithe R2 button responds fine in the HW tester, but then reupgrading back up to 1.0.2 it stops responding again. It also responds normal on the stock firmware still (which is on another sd card).
@Ninoh-FOX I also would like to say thanks for your work on bringing this to the PocketGo. The few issues I had with my device on the stock FW seem to have gone away once I installed yours!
One thing I would like to ask about is the overall system volume. Is there any way you can set the default system volume to something like 25-50%? The device is so loud by default that I usually just have it set 1 "click" above being off and it's still very loud. This can be mitigated a little by if the emulator has a master volume control, but some like PocketSNES have no built in audio control.
Thanks again for the work you've put into this!
@Ninoh-FOX - Just wanted to take a moment and thank you for moving your Rogue FW to the new PocketGo - I hope they gave you a little more than just the handheld for your efforts!
Also, let me know if you have any donation/payment links - I?m not made of money, but I?ll gladly buy you a beer... ;)
This weekend I go to test the code again.
there was a user from another forum who posted recommending diskgenius to extend partition...... looks to be some clash with the os/software also maybe something with ext4I did try that.
thanks for the info. heard the partition-type must be logical and not primary. i tried this it looked to get rid of the "re-reading the partition table failed...." red text warning but the looping is still therethere was a user from another forum who posted recommending diskgenius to extend partition...... looks to be some clash with the os/software also maybe something with ext4I did try that.
I used diskgenious to extend the ext4 parition part on the SD card after flashing the img with etcher.
Didnt help either.
Still bootloops for me.
Just tried pressing R2 once on my PocketGo with Rogue v1.0.2 and I do not have this problem.
It registers on the first try, no double or triple pressing.
I just tested stock and can confirm that there is some kind of bug going on with the 1.0.2 rogue OFW. The issue can be replicated with the button testing app. Basically what happens is that R2 does not register when I give it a single press, but if I do a double/triple press really quickly, it registers once. I've notice this issue is not apparent in the PG2 stock firmware.
Edit: Just wanted to say thank you for your work on the rogue ofw, it is much appreciated.
NOT RESIZE WITH THE PC!! The console has autoresize.
If you resize with the pc you broken the partition tablet and then bootloop
I just tested stock and can confirm that there is some kind of bug going on with the 1.0.2 rogue OFW. The issue can be replicated with the button testing app. Basically what happens is that R2 does not register when I give it a single press, but if I do a double/triple press really quickly, it registers once. I've notice this issue is not apparent in the PG2 stock firmware.
Edit: Just wanted to say thank you for your work on the rogue ofw, it is much appreciated.
I can confirm that I have this same exact bug in 1.0.2. My R2 button never registers on the first press, but if I hit it two times in a row it will then register on the second press. Can also confirm this behavior carries over to emulators as well.
Could it be a board revision? My units are the ones with the extra two screws in the back (2 in the battery compartment, and 4 on the outer back). One is the white PocketGo, and the other is the black PlayGo. Do you have the earlier version?
Could it be a board revision? My units are the ones with the extra two screws in the back (2 in the battery compartment, and 4 on the outer back). One is the white PocketGo, and the other is the black PlayGo. Do you have the earlier version?
Mine is the white Pocketgo with the 4 outer screws and 2 inner battery screws, and it is affected by the R2 bug
@Ninoh-FOX I also would like to say thanks for your work on bringing this to the PocketGo. The few issues I had with my device on the stock FW seem to have gone away once I installed yours!
One thing I would like to ask about is the overall system volume. Is there any way you can set the default system volume to something like 25-50%? The device is so loud by default that I usually just have it set 1 "click" above being off and it's still very loud. This can be mitigated a little by if the emulator has a master volume control, but some like PocketSNES have no built in audio control.
Thanks again for the work you've put into this!
Unfortunately, the volume seems to be a hardware thing, at the end of the month I will look at how you can lower the sound of the speaker by hardmod and post it.@Ninoh-FOX - Just wanted to take a moment and thank you for moving your Rogue FW to the new PocketGo - I hope they gave you a little more than just the handheld for your efforts!
Also, let me know if you have any donation/payment links - I?m not made of money, but I?ll gladly buy you a beer... ;)
I go to post my paypal.me in the first page
NOT RESIZE WITH THE PC!! The console has autoresize.still rebooting
If you resize with the pc you broken the partition tablet and then bootloop
Gmenu2x now can show two type of previews (put in /(romsdir)/.previews/).
I'm doing a brand new install of firmware 1.0.2 on a new sd card. I format sd card twice with sd card formatter and then write the sd_image.bin file with win32diskimager? Do I need the kernel update opk file? Do I need to do anything else?No. Just put the micro-SD card in the device and turn it on and *wait* for it to completely finish and boot to the desktop.
Does anyone have a step by step noob explanation of how to update the firmware? Everyone keeps not going into enough detail of what specifically needs to be done. Messing with the main SD card can brick the device so I don't want to mess it up. It can't be too complicated. Is anyone on here good at being clear and going into detail?
Does anyone have a step by step noob explanation of how to update the firmware? Everyone keeps not going into enough detail of what specifically needs to be done. Messing with the main SD card can brick the device so I don't want to mess it up. It can't be too complicated. Is anyone on here good at being clear and going into detail?
This is what I'd like as well. A simple guide for first installation and then updates.
Some questions I'd like answered:
- Do you need to install Release 1.0.0 first and upgrade from there? Or can you install release 1.0.2 directly?
- Does this require completely removing the stock firmware from the provided microSD card?
- What files are used to install Rogue Firmware, and in what method?
- What Windows software is used to install the firmware to a microSD?
- What should someone expect after preparing the microSD on a Windows machine, inserting it into the Pocket Go 2, and powering it on?
- What should someone avoid doing to prevent damaging or bricking the system?
For preparing a microSD on Windows, I saw that Win32 Disk Imager was recommended, but would something like Balena Etcher also work?
You can just use the bin file for 1.0.2. I would suggest using a new micro sd card for the firmware in case you want to put the stock one back in (should anything go wrong.) BalenaEtcher is an easy to use software, you basically select the image file, then the drive for the sd card, and it'll do the rest. Aftwards you put the card into the system and it should expand the drive's space. Also note that the rogue firmware does not come with emulators other than psx and snes. You can find the opks and copy them back in yourself, I would suggest looking up how to do that if you aren't sure.
I installed Rogue 1.02 and the analog stick offset is now -0.33 on the Y axis now... Does this mean it is a hardware issue? This is really annoying since it makes any game that uses the analog stick (psx, some arcade ones) unplayable. The funny thing is that it doesn't affect GmenuX either in stock FW or Rogue.
Any ideas?
I installed Rogue 1.02 and the analog stick offset is now -0.33 on the Y axis now... Does this mean it is a hardware issue? This is really annoying since it makes any game that uses the analog stick (psx, some arcade ones) unplayable. The funny thing is that it doesn't affect GmenuX either in stock FW or Rogue.They should be able to just send you out a replacement stick. If you look at the mainboard itself you can see where they just screw into the board and are attached via a ribbon cable. I'd check that cable and make sure it's properly inserted/secured to both the stick and the mainboard.
Any ideas?
I installed Rogue 1.02 and the analog stick offset is now -0.33 on the Y axis now... Does this mean it is a hardware issue? This is really annoying since it makes any game that uses the analog stick (psx, some arcade ones) unplayable. The funny thing is that it doesn't affect GmenuX either in stock FW or Rogue.
Any ideas?
Is the analog stick working in psx4all for everybody else? It isn't for me unless I use mouse mode in which case it drifts to the left (which it does in the button test app).
The stick itself works normally in the button test app and can also be switched to dpad mode, just doesn't work in psx4all.
Power+B not work in pcsx, for analog stick you can chosse the option Map L-stick to Dpad, or analog mode how "dualshock /a"
Thank you for the updates!
I didn't realize that, in the ROM menus, that "preview 1" lets the rom images take up the whole screen. I had them set to "preview 2" which was the solid image, as opposed to 1, which is translucent. Preview 2 keeps the image smaller in the top right corner.
(https://boards.dingoonity.org/index.php?action=dlattach;topic=15052.0;attach=8150;image)
It looks great!
I figured I might try and make a Raspberry Style set of screenshots based on the "Full Screen previews:
I have done a full set for Sega 32x, and a bunch of templates ready to use, however will only do "Best of Each System" to start :)
Any thoughts
(https://i.imgur.com/VpfdNHx.png)
I'm having trouble getting previews to work on all directories. In my arcade folder the .previews directory works ok for all roms but on other directories e.g. neogeo, even though the preview files are under a ".previews" folder with the "(rom name).png" convention however they don't get displayed... what am I doing wrong? All images have been resized to 128x96 (from initial 800x600) to fit the screen placement
I've gotten the v1.0.3 Rogue firmware installed and had a little time to try it out, haven't noticed any problems so far.
One thing I did notice was that the device will now power on immediately after pressing the power button, unlike the stock firmware which required a long press to prevent accidental power-ons.
My main worry is the device accidentally switching itself on whilst in my pocket or in a soft carry sleeve, can there be an option in firmware somewhere to control the power on method?
Options like hold duration (0 second, 1 second, 2 second etc) or even button combination (Power button alone, Power + Start, Power + R1, etc)
I've gotten the v1.0.3 Rogue firmware installed and had a little time to try it out, haven't noticed any problems so far.
One thing I did notice was that the device will now power on immediately after pressing the power button, unlike the stock firmware which required a long press to prevent accidental power-ons.
My main worry is the device accidentally switching itself on whilst in my pocket or in a soft carry sleeve, can there be an option in firmware somewhere to control the power on method?
Options like hold duration (0 second, 1 second, 2 second etc) or even button combination (Power button alone, Power + Start, Power + R1, etc)
I second all of this. 1.0.3 is great but the device does indeed seem to power on quite easily. I ran down my battery once because of this.
@Ninoh-FOX I flashed back to update 1.0.2 and kernel 1.0.0 because the performance on 1.0.3 was bad.
On the older version i can play SNES games like Secret of Mana, Earthbound and Ganbare Goemon 2 at a steady framerate, but on 1.0.3 it keeps dipping below 60, even with a clock of 1080mhz.
What happened here? Why is 1.0.3 performing so badly?
@RGB_Gamer For comparisons sake make sure that the 1.0.2 unit does not use the new kernel, but the 1.0.0 kernel.
Both 1.0.3 update and 1.0.3 kernel might be to blame here.
I use PocketSNES to play SNES games and the performance has taken a serious hit.
Where before i got rockstable 60 (well, actually 61) fps in Secret Of Mana it now keeps dipping below that framerate constantly. THe same thing happens with other SNES games, too.
@lemmywinks returned to the village after the first intro-bossfight against the mantis thing where they teach you how to fight. After that you can leave the village to the left and encounter some of those bunny-enemies.
Frames drop below max in the village and especially when encountering those enemies on 1.0.3.
No issues with kernel 1.0.0 and update 1.0.3
Using the 2019 11 11 build of pocketsnes from the repository, not the ninoh one.
Video mode set to original, frameskip set to 0, prefer smooth both, audio at 32khz
Tried the ninoh one, too yesterday tho. Same behavior.
@lemmywinks https://github.com/soarqin/PocketSNES/releases
found on this repository: https://github.com/retrogamehandheld/OpenDingux (Dont click anything, just scroll down)
I seem to be having a problem with version 1.03. After loading it in I keep getting random slow downs. This happens in any Emulator and any game. It will run fine for a bit but then slow to a crawl for a second then continue at full screen. Is there maybe a fix for this?
@lemmywinks yeah, tried all versions of PocketSNES on 1.0.3.
All behaved the same.
Which revision do you have of the pg2?
pre-release or 1.2? (All black ones, for example are 1.2)
new release 1.0.4, fixed R2 finally 8)
R2 works in the internal hardware test and the Ninoh specifically complied build of PCSX. It does not work otherwise. /sigh.
It doesn't even work in any other PSX emulators other than yours. The effort is appreciated, but breaking things that work on stock and narrowing my software options further on a device that already struggles to run what the RG-350 does is just not practical. I realize R2 is used in very little, but if it may or may not work with your build, and will work on stock, I'll stick with stock. And this isn't limited to just me, or the PG2. I have had a friend testing on his Playgo just to cover me here. In addition this release locks up and crashes a lot compared to stock.
...
Never had a single crash on the Rogue firmware over three updates and a ton of play time. Stock firmware locked up on me within the first 15 minutes and I had to remove the battery.
YMMV.
...
I didn't say your work is bad. I am saying things that work on stock, don't work on yours. I am saying that stock runs for hours without crashing, and yours crashes the console and locks up at random. I have no idea how the programming end works. I told you that "I appreciate the effort." I am also telling you as a user, your effort has flaws compared to stock. Being a jerk about it doesn't change that.
# /etc/asound.conf
defaults.ctl.card 1;
defaults.pcm.card 1;
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "dmix"
}
min_dB -50.0
max_dB 0
resolution 6
}
@Ninoh-FOX
re: volume loudness
I'm currently building the toolchain to try this myself, but I was wondering if it's possible to use ALSA's softvol plugin to set volume boundaries? I wanted to try a file like this but the FS is read-only when I ssh in:Code: [Select]# /etc/asound.conf
defaults.ctl.card 1;
defaults.pcm.card 1;
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "dmix"
}
min_dB -50.0
max_dB 0
resolution 6
}
@lemmywinks not a fan of that version. Doesnt have a 1:1 Pixel Scaling mode.Hi Vanguard.
Try a different version of PocketSNES and under video scaling set it to "Original".
Thats the pixel perfect mode. You will see what i mean.
Can someone tell me how to set the date in rogue? I can set the clock without problems, but when i want to set the date it says ?y to begin?, but nothing happens?
Gracias ninoh-fox for the software
I'd like to know if you have any plans for the UI in terms of rom preview/cover, in the same looks of the rs97 ui, with rom names and pic by side
This looks so good ^^ cheers
(https://i.ytimg.com/vi/D8XlVy8AcSo/maxresdefault.jpg)
What's missing then for images to be previewed?
? Can yu guys compare with what you have?
hi, i tried to use all the firmware versions, but it seems that it does everything right and when it restarts it shows the home screen and the screen goes black. any sugestions?
Tks.
What's missing then for images to be previewed?
? Can yu guys compare with what you have?
OK I suggest a CLEAN install of the CFW 1.0.4... Format the SD Card before you start and clear all partitions.
My GMenu Settings
(https://i.imgur.com/jdLqof8.png)
My Emulator Settings - Obviously file types vary for each emulator
I Reccommend it greatly along with the folderr structure for your games etc
The suggestion of formatting the sd again moved me in to take this option seriously.
I'm also trying to move the fba explorer in to the settings or apps section, but after every reboot, it goes back to emulators again. Any thoughts?Can you confirm which version of FBA you are using and which rom set it supports ?
Also I'm not able to launch openbor with world heroes perfect, that previously I could play in this handheld.Sounds silly but "Delete or Rename" the .OpenBOR from the home folder and reboot, then lauch OpenBOR to create a new .OpenBOR home folder. Then only add the World Heroes pak file.
hi, i tried to use all the firmware versions, but it seems that it does everything right and when it restarts it shows the home screen and the screen goes black. any sugestions?
Tks.
Try the following:
1) Test another Memory Card
2) Try a clean install using the BIN file
3) Try another CFW (Not rogue) and see if the issue still happens
OR Try this....
Download "HP Format Tool" also known as "3-HPUSBDisk.exe" and format the SD Card (Run as Admin)
Then Download and install "Win32 Image Writer" click browse and navigate to the folder with the Rogue CFW "BIN" file (Select "All Files" to show the BIN file, then click "Write"
Once done pur the SD Card in the "Left" slot on Pocket Go 2, power it on and let it do its thing.
Let me know how you get on ;)
I had no issues installing 1.0.2 with image on a new SD card.
Then I had no issues with update opk to 1.0.3
But now update opk 1.0.4 is not installing. The initial percentage goes about 40% maybe and then the device shuts down and it's still on 1.0.3.
what's wrong?
https://youtu.be/dsmzhGxxJzY
New PocketGo version??
Enviado de meu moto g(7) play usando o Tapatalk
https://youtu.be/dsmzhGxxJzY
New PocketGo version??
Enviado de meu moto g(7) play usando o Tapatalk
Any easy way to edit the boot splash? I'd like to create a few of my own.
Very cool!https://youtu.be/dsmzhGxxJzY
New PocketGo version??
Enviado de meu moto g(7) play usando o Tapatalk
Great video share Thanks...
Maybe start a seperate thread about this device, its not really a Rogue CFW topic so people not on Rogue CFW wont see it.
Hi! Can we hope to see the recent changes from Rogue CFW RG-350 ported over to the PG2?
I'd especially love to have the previews transparency level option in GMenu2x on PG2 too!
It cannot show non-English filename correctly, e.g. Chinese, Japanese.... Any way to fix it?
IMPORTAN!!! THE CFW NOT WORKS IN POCKETGO2 V2!!!
I don't have that model, so I don't know where the failure may be or what has changed
Is it ok to jump from v1.0.4 to v1.0.7 ?
I just got a PocketGo2 Rev 2 (Has reset button + colored buttons). I'm confused about the available Firmware for this device. I installed the RG-350 BASE v1.5 231019 firmware which worked fine, but when I install any of the updates, it always fails. Anybody has any suggestions????
Thanks for your response......I used the rg350-flasher-1.7.9.9R-2020-05-10.opk to do the update and it worked fine on my PocketGo2 (Rev2). It took a long time (30+ minutes) but it worked great. When I used the rg350-update-1.7.9.9-2020-04-25.opk update file it would install OK, but crash after the 1st reboot, then all subsequent reboots would crash.I just got a PocketGo2 Rev 2 (Has reset button + colored buttons). I'm confused about the available Firmware for this device. I installed the RG-350 BASE v1.5 231019 firmware which worked fine, but when I install any of the updates, it always fails. Anybody has any suggestions????
Did you try the Rogue firmware developed for RG 350?
https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/
It seems like PocketGo2 v2 might need its own firmware that's forked from RG 350, or moded or something because PocketGo2 v2 doesn't have a second analogue or a wifi module.
Thanks for your response......I used the rg350-flasher-1.7.9.9R-2020-05-10.opk to do the update and it worked fine on my PocketGo2 (Rev2). It took a long time (30+ minutes) but it worked great. When I used the rg350-update-1.7.9.9-2020-04-25.opk update file it would install OK, but crash after the 1st reboot, then all subsequent reboots would crash.I just got a PocketGo2 Rev 2 (Has reset button + colored buttons). I'm confused about the available Firmware for this device. I installed the RG-350 BASE v1.5 231019 firmware which worked fine, but when I install any of the updates, it always fails. Anybody has any suggestions????
Did you try the Rogue firmware developed for RG 350?
https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/
It seems like PocketGo2 v2 might need its own firmware that's forked from RG 350, or moded or something because PocketGo2 v2 doesn't have a second analogue or a wifi module.
Sorry but I pasted the wrong patch in my comment.....it really was rg350-update-1.7.9.9R-2020-05-10.opk which wouldn't install without crashing. rg350-flasher-1.7.9.9R-2020-05-10.opk worked for me. Sorry but I didn't try to uninstall with the method you mentioned (was not aware of it. So now I'm running RG350 firmware "Rogue" edition ----- Update firmware 1.7.9.9R on my PocketGo 2 (Ver2) and so far it is working without any issues.Thanks for your response......I used the rg350-flasher-1.7.9.9R-2020-05-10.opk to do the update and it worked fine on my PocketGo2 (Rev2). It took a long time (30+ minutes) but it worked great. When I used the rg350-update-1.7.9.9-2020-04-25.opk update file it would install OK, but crash after the 1st reboot, then all subsequent reboots would crash.I just got a PocketGo2 Rev 2 (Has reset button + colored buttons). I'm confused about the available Firmware for this device. I installed the RG-350 BASE v1.5 231019 firmware which worked fine, but when I install any of the updates, it always fails. Anybody has any suggestions????
Did you try the Rogue firmware developed for RG 350?
https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/
It seems like PocketGo2 v2 might need its own firmware that's forked from RG 350, or moded or something because PocketGo2 v2 doesn't have a second analogue or a wifi module.
That sounds like you actually tried to update from a newer version (2020-05-10) to an older version (2020-04-25), which might explain why it did not work correctly after rebooting.
Were you able to return to the previous working version by holding X or Y, or a combination of them when booting the device? I forget which button combinations boot what exactly, if it's kernal, firmware, etc, but it's something to that effect.
Is there plans to put on Rogue Connect and Rogue Store like on the RG-350?
Does the PG2 have any wireless capabilities like the RG-350?
Sorry but I pasted the wrong patch in my comment.....it really was rg350-update-1.7.9.9R-2020-05-10.opk which wouldn't install without crashing. rg350-flasher-1.7.9.9R-2020-05-10.opk worked for me. Sorry but I didn't try to uninstall with the method you mentioned (was not aware of it. So now I'm running RG350 firmware "Rogue" edition ----- Update firmware 1.7.9.9R on my PocketGo 2 (Ver2) and so far it is working without any issues.Thanks for your response......I used the rg350-flasher-1.7.9.9R-2020-05-10.opk to do the update and it worked fine on my PocketGo2 (Rev2). It took a long time (30+ minutes) but it worked great. When I used the rg350-update-1.7.9.9-2020-04-25.opk update file it would install OK, but crash after the 1st reboot, then all subsequent reboots would crash.I just got a PocketGo2 Rev 2 (Has reset button + colored buttons). I'm confused about the available Firmware for this device. I installed the RG-350 BASE v1.5 231019 firmware which worked fine, but when I install any of the updates, it always fails. Anybody has any suggestions????
Did you try the Rogue firmware developed for RG 350?
https://boards.dingoonity.org/retro-game-350rg-350/rg350-'rogue'-cfw/
It seems like PocketGo2 v2 might need its own firmware that's forked from RG 350, or moded or something because PocketGo2 v2 doesn't have a second analogue or a wifi module.
That sounds like you actually tried to update from a newer version (2020-05-10) to an older version (2020-04-25), which might explain why it did not work correctly after rebooting.
Were you able to return to the previous working version by holding X or Y, or a combination of them when booting the device? I forget which button combinations boot what exactly, if it's kernal, firmware, etc, but it's something to that effect.
Hi OP / @Ninoh-FOX !
I just wanted to say that I really appreciate your hard work on these devices and firmwares!
I just got my PlayGo last week and, well maybe I just have good timing haha, but you've already addressed every "issue" that I had with the device. (The sound/volume control being the latest)
Thank you so much!
I'm loving this little device!
My aluminium PocketGo2 V2 arrived today, and I got Rogue v1.0.8 installed on it, as well as on my older PocketGo2.
The volume fix is fantastic and controlling the master volume with the volume -/+ is great, thank you for the hard work!
My aluminium PocketGo2 V2 arrived today, and I got Rogue v1.0.8 installed on it, as well as on my older PocketGo2.
The volume fix is fantastic and controlling the master volume with the volume -/+ is great, thank you for the hard work!
How of better is the aluminium version?
Hey Rupee, where are you located? I put my order in day one and can't wait to get the new unit.
$ make ARCH=mips pocketgo2_defconfigUpdate: SOLVED! Turns out I needed to download the V2.1's kernel source separately and work from there.
Here's the custom boot logo if anyone's curious:
Here's the original post for the sake of context:
Thanks for your work on this CFW!
I tried to make my own custom boot screen by compiling a kernel update from the source based on the instructions from the github page, while the custom kernel installed fine and my custom boot screen now works, I noticed that some of the keys are mapped differently or don't work.
I am currently using a PocketGo V2.1 but the instructions only seem to mention:Code: [Select]$ make ARCH=mips pocketgo2_defconfig
Is this the universal config for both the V2 and V2.1? Or have I used the wrong config? Currently L2 and R2 no longer work properly, pressing L2 registers as L1 whereas pressing L1 and R2 are no longer detected in the PocketGo button test app. The volume buttons are also no longer detected and the analog stick is rotated 90 degrees anti-clockwise (pushing up is registered as left on the tester).
Can someone please let me know what I've done wrong here? For now, I have reverted back to the original kernel.
I don't have the expertise to help but thank you for your work, hope you're able to get it working properly. Really not a fan of the rogue boot and I wish it was easier to change or we could switch it for something more neutral.I got it to work in the end, it's now possible to change the boot logo by running a .opk file from the apps folder. Would you like a copy of the one I made? Or alternatively, if you have a custom image you'd like to have as the boot logo I can try to build an update file that will install it for you.
version 1.0.8 Why did it disappear? ;D ;D ;D ;D
version 1.0.8 Why did it disappear? ;D ;D ;D ;D
It didn't.... That was what I though at first, however when I deleted part of the URL back highlighted in red then it clicked POCKETGO2 it was there.... https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/releases/tag/1.0.8
Below is the link, click that then choose 1.0.8 and it will download :)
https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW (https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW)
I don't have the expertise to help but thank you for your work, hope you're able to get it working properly. Really not a fan of the rogue boot and I wish it was easier to change or we could switch it for something more neutral.I got it to work in the end, it's now possible to change the boot logo by running a .opk file from the apps folder. Would you like a copy of the one I made? Or alternatively, if you have a custom image you'd like to have as the boot logo I can try to build an update file that will install it for you.
Can you build me the update file with your Gameboy style boot screen please, I have a PG2 V2.1 on rogue 1.0.8.
Thanks
Can you build me the update file with your Gameboy style boot screen please, I have a PG2 V2.1 on rogue 1.0.8.
Thanks
Hi nekomichi,
I know this is s a huge ask, but is there anyway you could please build a Playstion style Boot screen for the RG350 and the MiYoo MAX ? (I believe the MiYoo MAX is rebranded v1 Pocket Go 2 / Play Go 2)
Or may be would you create a video tutorial on how to do it on a Windows 10 PC ?
It would very be much appreciated :)
Thanks
ace
Here's a sample of what I had in mind:
(https://i.imgur.com/opvi8aj.png)
Here's a sample of what I had in mind:
(https://i.imgur.com/opvi8aj.png)
I think This one below... What do you think ?
(https://i.ibb.co/h9q2QYy/Pocket-Final.png)
I think This one below... What do you think ?
(https://i.ibb.co/h9q2QYy/Pocket-Final.png)
Here's what it would look like on the device:
(https://i.imgur.com/QIBIbsf.jpg)
I've built an updater that installs this as the boot logo, it can be found here (https://www.dropbox.com/s/hu3wffvnfx1fmjm/POCKETGO2-Kernel-update-1.0.8p-2020-06-20.opk?dl=0). It was built with the PocketGo V2 original model as the target device, I can't guarantee it has the exact same button mappings as the Miyoo Max. After installing this update, please run the button checker app and confirm that all buttons are properly mapped. If you want to be extra-safe, flash a spare micro SD card with your CFW and test this on that one first before installing it on your main card.
How do the new GMenu2x previews work? What are the types and the corresponding directory and file naming convention under . previews?
Place a folder titled: .previews in each rom folder. Dot-files will not appear in your rom directory when you are playing/choosing roms to play (but you WILL be able to see them when using DinguxComdr). Place the .png files in the .previews folder, matching the names of the .png with the names of the rom files. The pics will appear when you move through the list. The anchor seems to be the upper right corner, so smaller pics will be up in the upper right of the screen.
it looks like the text of the rom title will appear over the pics, so I'm going to try some 320x240 images, and see what they look like taking up the whole screen, with the list over them.
In the settings of gmenu2x (accessed by pressing 'start' when on any screen), the last setting is 'Preview type' - 2 is solid, 1 is transparent, if you wish to see the background bleed through the images.
EDIT: Whoops! I initially stated the folder name should be '.preview' - it should be plural: .previews - I've corrected that in my text above.
can you please show how 320x240 images looked like?
can you please show how 320x240 images looked like?
These are examples of my final version. The latest firmware allows you to choose how opaque you want the images, and I went for fully solid, no background showing. I then created a pic for each game that included the background I am using for the main menus. The lists appear over them. Yes, longer titles appear over part of the game pictures, but it works pretty well for me.
release 1.0.9
-gmenu2x-
Several changes have been added, including:
NOTE: you will have to delete the file /media/data/.linker so that you can reconfigure gmenu2x, and calm, it has been modified so that it saves the personal changes of the opks
- option to change brightness
- new theme in pixel mode (this does not support all fonts)
- New way to monitor the battery.
- the titles can now be read in two lines
there are more changes, but I don't remember them all XD
-kernel-
- boot mode has been changed, now read mininit-syspart file from boot partition. This way you can update without having to recompile the kernel.
- cleaned unnecessary drivers.
- gpu frequency corrected according to the cpu.
- Battery capacity has been corrected.
-General-
- Added ROGUE Manual
- Added news combo keys (see the manual)
- Updated some libraries.
release 1.0.9
-gmenu2x-
Several changes have been added, including:
NOTE: you will have to delete the file /media/data/.linker so that you can reconfigure gmenu2x, and calm, it has been modified so that it saves the personal changes of the opks
- option to change brightness
- new theme in pixel mode (this does not support all fonts)
- New way to monitor the battery.
- the titles can now be read in two lines
there are more changes, but I don't remember them all XD
-kernel-
- boot mode has been changed, now read mininit-syspart file from boot partition. This way you can update without having to recompile the kernel.
- cleaned unnecessary drivers.
- gpu frequency corrected according to the cpu.
- Battery capacity has been corrected.
-General-
- Added ROGUE Manual
- Added news combo keys (see the manual)
- Updated some libraries.
Thanks for the update!
I tested the update .opk on both PocketGo 2V1 and 2V2 (I downloaded both versions and made sure to use the correct version on each hardware model), the 1.0.9 update works on PocketGo 2V2 but on the 2V1 it would detect the installed rootfs as corrupted. I then took the rootfs.squashfs and re-built an updater from the source and it works. I think the rootfs.squashfs.sha1 inside pocketgo2-update-1.0.9-2020-07-02.opk might be corrupted.
can you please show how 320x240 images looked like?
These are examples of my final version. The latest firmware allows you to choose how opaque you want the images, and I went for fully solid, no background showing. I then created a pic for each game that included the background I am using for the main menus. The lists appear over them. Yes, longer titles appear over part of the game pictures, but it works pretty well for me.
sd_image_PLAYGO.bin, is this compatible with PG v2.1 with reset button ?
What's the difference between sd_image_POCKETGO2.bin and sd_image_PLAYGO.bin? I've got PLAYGO without RESET button, so which one have I to use?
Thanks Ninoh, great work!
Would you add in next releases the new version of reGBA by jdgleaver?
I am interested if you can remap the menu button for the pocket go v2.
yes, I maped the pcsx4all of jd, so I can remaped the regba I think.
try this https://mega.nz/file/7hxV0KDQ#7Olif0hBiYI1e2MTFQ8bZLEej_ms5y832MnJ6-z4cJ0 (https://mega.nz/file/7hxV0KDQ#7Olif0hBiYI1e2MTFQ8bZLEej_ms5y832MnJ6-z4cJ0) regba pg version
NEW UPDATE
https://github.com/Ninoh-FOX/POCKETGO2_ROGUE_CFW/releases/tag/v1.0.9u2
updated alsalib to version 1.2.4
updated alsamixer to version 1.1.7
add libpng 16 from OD
fixed sound mute level in pcm
fixed sound crashes in some emulators (you have to delete the old temper settings from the folder /usr/local/home/.temper/config/)
updated Picodrive emulator to 1.97 https://github.com/irixxxx/picodrive
recompiled Temper 1.24.2 https://github.com/gameblabla/temper/tree/f3328369d5e00e70b9c2ea095e09b1dec6452de5
updated pr-boom+ to OD-pr-boom+
note: V2 versions are those with the reset button in the lower right corner