Quick RP6 privacy review:
>Android / Google bullshit seems pretty obvious from the getgo. Chrome can be disabled to prevent it taking resources, but requires root to fully gut out as usual.
>Surprisingly pleasant that Google Play Services are completely optional, and have no hidden remnants if you tell them to fuck off early.
>FOSS alternatives are, as usual, exponentially more lightweight, GBoard hogged ~320MB memory by default, Simple Keyboard is ~35MB in comparison
>Most other tracking seems via QualComm / manufacturer, regarding silicon. Some unnecessary phoning home, can be disabled.
>Nothing egregiously intrinsic or additional shit dumped on top from Retroid - no hidden adware or 3rd party pre-installs or the like. There is a Retroid Game Assistant (77KB size file, ~90MB memory usage) that dictates a quickmenu overlay for device specs (temperature, utilisation etc) (that you can hide / turn off, even if it still runs) and their own Retroid Launcher frontend (141KB, 0 memory usage, but appears responsible for the ~50MB FOTA service). The former's functionality can be done in-emulator for all emulators via settings -> UI, while the latter can just be replaced by a better frontend (I'm just using ES-DE). That said, I'm not going to delete them, on the offchance either control something like the button inputs or fan functionality - they don't appear to be phoning home, just reasonable device analytics. Can't say I'm ever happy with shit I don't want (and I still might test getting rid of them later, once I've got everything I want to try sorted), but it's not worth getting caught up over, since my actual communication devices are locked down like fucking Alcatraz anyways and this is just a emulation chinkheld.
>You could rip out Quickstep / Default sliding-App-Menu-interface typical of smartphones if you set ES-DE as your default device frontend, which does appear to work just fine, albeit significantly less convenient
tl;dr it's the standard of what you'd expect from an Android-based device.
- Don't debloat it, and Google's gonna smell your ass constantly (but you're at least not required to use Google play)
- Debloat it, keep it offline and it's never going to do shit, take it online and Qualcomm's going to get 2kb of telemetry about the silicon. I can tolerate them getting that (since it's going to be emulation-only anyways), as long as it's not got tracking or other spooky shit that has more intrinsic analytics.
As for memory gains (or more accurately, less-losses) before loading the emulators / ROMS :
<2.5GB passive usage average before
>2.1GB passive usage average after
<6.9GB/12GB available before
>7.1-7.5GB/12GB available after
I'll take my 400MB and call it a day. Linux dual-boot exists if I want the other 2GB if I run into any memory throttles later on.
If anyone wants my .txt file notes on all the visible + hidden processes running by default pre-debloat, just ask.
>>305054
Man, I've been fucking around a ton (including needing to getting back from a near-brick state after I half-assed thought about rooting it half-asleep) so sorry I left it this late.
Running on NetherSX2-Patch; initially running at x3 Native OpenGL
>Shadow of the Colossus
NTSC option within the PAL version. Online says an early on worst-case-scenario is the top of the spiral staircase at the back of the initial shrine, seemed a bit choppy when looking at the steps with the no-fucks-given x3 OpenGl settings (but emulation speed did maintain 100% throughout). Pushing it down to some leddit-recommended settings for the chip /r/OdinHandheld/comments/18pocur/finally_found_smooth_shadow_of_the_colossus/ but on 2.5x instead of 2x and with a 1px crop to account for Widescreen Hacks. It's maintaining a stable 100% speed and much more stable than the default n-f-g settings, but it's clearly not running flawlessly when panning the camera around as fast as possible, even with VSync on. Smoother out in the field, and definitely playable on this staircase.
Thing is, it's not using the entire CPU / GPU load (average 45-55%, peaking at 65% when moving the camera all around) and High Performance / Fan mode isn't changing the situation so I have a feeling it's software-side, not hardware-side. Got as far as meeting the first Colossus, the story is the same, absolute peak number utilization I saw was 68%.
I say all this, but now I look at a YT longplay, it doesn't seem the original was a stand-out in terms of performance either. Yeah, actually the emulated version is much better, both fidelity and performance, assuming it wasn't caught on a shit capture card. Not sure what the input delay was on the original, but that would be my only hesitation. Otherwise I'd say this scenario is 100% playable + better on the RP6 compared to original hardware.
>Soul Calibur 3
I'll cut the shit, the stage is locked and I'm too much of a shitter to reach Abyss's stage. I actually assumed you were talking about Yoshimitsu's stage when I looked it up online (Fuji Volcano), and bruteforced my way to unlocking him the shortest part possible (Raphael's story, A-Path, and a lot of spamming a heavy move that seemed good, a chunk of retrys, quitting out afterwards when the dude with the glass sword rekt me), but when I got there, I realised the lack of meteors and my mistake. If there's some unlock code for the stage, a dogshitter AI-breaking character who has an easy path to Abyss or another tougher stage with slowdowns, I'll be happy to re-do it more in-depth, but as of now the game felt like it ran fine on all the stages leading up to it.
Romanian Castle seemed (?) like it might have been intensive, so I took screenshots there, same settings as SotC, ran fine.
>Tekken Tag Tournament
Trying to figure out how to get onto Ogre, it seemed alright (maintained 100% emulation speed throughout, barely hitting 40% GPU load tops), but yeah, after the L2+(R2x6) trick from the menu, Ogre's a problem. Zoomed in, it was hovering 100% speed, with common drops to 96% emulation speed (honestly unnoticeable), but backing out as far back as possible / straining the game as much as possible and it chokes down to unplayable 60% emulation speed and 100% utilisation. While hugging up to the enemy seems like it's still mostly stable, the pushback from a knockdown puts you in that "slowdown" range, of about 80% emulation speed / playable but noticeable.
Switching it over to High Performance mode + full fan + x2 resolution, and that "80% range" is as good as eliminated (so CQC combat and usual knockdown is completely fine, 100% emulation speed maintained), but that maximum-zoom-out 60% range still exists. Fiddling with shit like the Hardware Download mode at best only delayed the slowdown curve to 60% (so if I was being kind, you could back out a bit, then run back in and only experience a little bit, but still noticeable amount), but it only delays it a few seconds with absolute optimal settings.
Apparently the MAME / Arcade emulation method runs better (maybe a solution for your RP5), but brass tacks is that this one situational situation has issues that are even apparently present on PC (https://wiki.pcsx2.net/Tekken_Tag_Tournament).
And yeah, I'm rolling with the 12GB version. I plan on getting Windows emulation up and running, hence why I've been debloating to strip every extra MB of RAM I can get before really doing some hackjobs.
Is this worth a full hardware upgrade? Depends. All three were definitely playable; Shadow of the Colossus had no issues I couldn't see on original hardware, SoulCal 3 was 100% fine trying to reach Abyss (even if I couldn't test Abyss for you), and Tekken Tag seemed fine (100% by default, 100% on Ogre with optimal settings in CQC, significant slowdown in situational). Any more questions, hit me up, I'll be happy to test the night away for you (or anyone else reading). With the absolute state of the tech hardware markets right now, I'd cautiously say waiting for the next generational might be a plan; especially if Retroid follows the trend of lagging one chip grade behind AYN (or letting AYN beta test compatibility for it, depending on your perspective) and putting the 8Elite in the RP7 (which just recently / as a benchmark can now play Tears of the Kingdom Switch with no graphical errors).
>>305281
Graphene is Pixel-only because of development platform / "security reasons", but knowing the state of Jewgle trying to lock down into a walled garden, I don't know how long the head dev is going to maintain that position. Retroid can dual-boot into Linux if I wanted near-100% access to the hardware, and there are alternate handheld OS's like Lineage; but debloating gets the job done for me. I'm very much an 80/20-rule respecter and self-moderated convenience appreciator; 20% of the time taken solves 80% of your problems: is it worth the other 80% of the time to do a full job to gut the other 20%.