Android Dolphin defaults to GL which is kind of bad on Switchroot, you need to switch to Vulkan and separately enable threading. The special maysomeone build seems to run kind of close to Lakka, which is to say, Sonic Adventure 2 can't quite get through its opening intro without lagging horribly.
Homebrew Discussion SwitchRoot - Android
- Thread starter ganons
- Start date
- Views 96,141
- Replies 402
- Likes 6
Android Dolphin defaults to GL which is kind of bad on Switchroot, you need to switch to Vulkan and separately enable threading. The special maysomeone build seems to run kind of close to Lakka, which is to say, Sonic Adventure 2 can't quite get through its opening intro without lagging horribly.
I haven't installed the reboot2payload update yet (haven't been back in android since I finished Portal 2, Switch games have been keeping me busy), but I saw discussion about mounting the vendor partition in TWRP before flashing the update zip, because the payload is stored there or something - try that.
Thanks! Info is all over the place with this lol
The official switchroot discord is a good place to hang out and soak up info, or ask questions when you're stuck.
Just weird that the instructions in the XDA thread were just literally flash the zip with twrp, nothing about going into developer options and enabling rebooting to payload or mounting vendor before you flash it, never would have thought to do either of those things!
Thanks man, mounting vendor worked. Pretty cool goiong from atmosphere to nyx then swapping sd cards and booting to android and vice versa
Now we just need to install android to emmc, mount the Fat32 partition of the SD card as external, and all will be well.
R2P update overwrote the 720p boot image someone made, so I seem to be running in 1080p now. Reflashing the 720p boot image seems to break R2P. The thread mentioned a root app easy DPI changer but that keeps seeing the resolution as 720p and won't let you change anything. Not sure how to get back to 720p now.
Edit: retroarch looks like its running in 720p between the integer scaling and Ozone UI. The home screen reminds me more of 1080p now though with how small and soft everything is. Not sure what is going on.
Edit2: after some more use my best guess is that it is running 720p, but it reset the DPI scale so that normal size = how it used to look on 1080p. Crank it up to Larger and you get more of the old 720p look. Not sure if this outcome only applies to people like me who flashed 720p boot image at some point.
Edit: retroarch looks like its running in 720p between the integer scaling and Ozone UI. The home screen reminds me more of 1080p now though with how small and soft everything is. Not sure what is going on.
Edit2: after some more use my best guess is that it is running 720p, but it reset the DPI scale so that normal size = how it used to look on 1080p. Crank it up to Larger and you get more of the old 720p look. Not sure if this outcome only applies to people like me who flashed 720p boot image at some point.
Last edited by Rahkeesh,
Yeah I figured since the Android version only had GL as an option it wouldn't run too well but it wasn't bad as I expected. I'll likely try it out more later though, imo it has the better advantage of being dockable
I'm using version 9494 v16 of Android dolphin, I read it's the best one for the switch. Just googling.
No. The fixes to bluetooth are being made to Android Q (by google), hopefully someone will backport them to Pie for Switch.
No there's some kind of bluetooth bug that breaks the kernel driver for joy-cons, IDK how far reaching the effects would have been for other stuff but generally bluetooth controllers had analogue working fine.
I used a 32GB card for LineageOS.
However, I encounter various problems:
- I cannot use the 32 GB image. Balena Etcher says that I only have 35MB too little on a fully formatted Micro SD card to flash this image.
- I finally opted for the 16GB image. After that was flashed, it turned out that only 1.85 GB on my 32 GB card could be used afterwards. I find that very strange.
- I could boot LineageOS, but I cannot complete the installation. When searching for updates (after setting up an internet connection), I always get the comment that Google Play is (still) not responding (anymore).
- If I try to complete the installation without connecting to the internet, I get the message that the entire OS is no longer working.
I have correctly followed the step-by-step plan of the installation. What could be the problem and what are possible solutions?
However, I encounter various problems:
- I cannot use the 32 GB image. Balena Etcher says that I only have 35MB too little on a fully formatted Micro SD card to flash this image.
- I finally opted for the 16GB image. After that was flashed, it turned out that only 1.85 GB on my 32 GB card could be used afterwards. I find that very strange.
- I could boot LineageOS, but I cannot complete the installation. When searching for updates (after setting up an internet connection), I always get the comment that Google Play is (still) not responding (anymore).
- If I try to complete the installation without connecting to the internet, I get the message that the entire OS is no longer working.
I have correctly followed the step-by-step plan of the installation. What could be the problem and what are possible solutions?
Your sd card might be counterfeit or damaged. Check it with h2testw and try another one.
I couldn't get it to work until I switched SD cards, originally I was using a 128gb SanDisk and the boot time was 10 minutes and would lag after any button press, switching to a 32gb Samsung reduced the boot time to 30 seconds and no lag whatsoever
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Veho:
Illinois is working to ban toxic food additives that have been banned for decades in other countries; additives that can be replaced and all those countries still have Skittles and Mountain Dew. Title of the piece: GUBMINT WANTS TO TAKE AWAY YOUR CANDY -
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
-
-
-
-
-
-
