Anybody working on Android for the Odroid-Go A?

[zztfoxdev]

So it is good, or do I need to upload a separate one for OGA Originals?

[macromorgan]

Is anyone else having trouble getting theirs to boot? I have an original Odroid Go Advance (not the newer model) with the latest U-Boot, and when I boot it shows some funky colors and then keeps rebooting. I checked the serial logs and it goes through U-Boot and gets to "booting Kernel" then reboots.

Hey, Can you take off the .txt and replace the dtb file in your BOOT folder with this one?

Thank you, I did that (and reflashed my U-Boot back to the February version) and now things seem to be working.

[notime2d8]

So it is good, or do I need to upload a separate one for OGA Originals?

Can you do a new upload when you get a chance? Or they can just update the files after they flash your image. But in the boot.ini you need to edit:

rk3326-odroid-go2.dtb
to
rk3326-odroidgo2-linux.dtb

And copy the DTB file that I posted.

[Shoesy]

Great news! Thanks for the update

[macromorgan]

Do you by chance have the most recent sources (or at least the most recent kernel sources so I can add some modules to mine)? Thank you very much for all your hard work.

[notime2d8]

Do you by chance have the most recent sources (or at least the most recent kernel sources so I can add some modules to mine)? Thank you very much for all your hard work.

https://drive.google.com/file/d/1Q5GXKJ ... sp=sharing

Let me know if there's something specific you want added or it doesn't work for you, I did add support for the Aircrack-NG driver but it only supports RTL8812AU/21AU and RTL8814AU sticks.

[Shoesy]

Redream works real nice. Anybody know what the problem with Mupen is?

[notime2d8]

Redream works real nice. Anybody know what the problem with Mupen is?

No, I haven't tried it. If someone can send me a log at some point.

You can enable logging in developer options. And the files will be located in data/misc/logd

or

You can enable Wifi ADB in developer options and just copy the log from terminal when it crashes.

or

I'll just test and check it this weekend. I'll also post instructions on how to enable WiFi ADB since we don't have USB OTG.

[zztfoxdev]

Updated version with the OGA patched boot.ini

https://drive.google.com/file/d/1yc4_9b ... sp=sharing

Can confirm OGA:BE still works, anyone with an original OGA wanna test to make sure it works on their end?

[jutleys]

Hi any chance to make a .img file so the user can just burn the .img file to sd card and boot it should be possible.

[Shoesy]

That’s what the gdrive links are @jutleys - 8gb img for etcher etc

[Tremont]

Updated version with the OGA patched boot.ini

https://drive.google.com/file/d/1yc4_9b ... sp=sharing

Can confirm OGA:BE still works, anyone with an original OGA wanna test to make sure it works on their end?

I tried it. It still complains about there being no dtb. The part in my boot.ini looks like this:

Code: Select all

if test ${hwrev} = 'v11'; then
load mmc 1:1 ${dtb_loadaddr} rk3326-odroidgo2-linux-v11.dtb
else
load mmc 1:1 ${dtb_loadaddr} rk3326-odroidgo2-linux.dtb
fi

I'm not sure if that will work for the black edition, but it does for the original.

[zztfoxdev]

Will double check my boot.ini when I get a chance.

[macromorgan]

Do you by chance have the most recent sources (or at least the most recent kernel sources so I can add some modules to mine)? Thank you very much for all your hard work.

https://drive.google.com/file/d/1Q5GXKJ ... sp=sharing

Let me know if there's something specific you want added or it doesn't work for you, I did add support for the Aircrack-NG driver but it only supports RTL8812AU/21AU and RTL8814AU sticks.

I was going to say the RTL8812AU is a DKMS driver from what I can tell, but if you already added support for it that's great!

Logically speaking, I think adding support for the Wifi 0 and Wifi 3 modules supported by the official build at least would make sense. Wifi0 uses the rt2800usb module and Wifi3 uses the rtl8192cu module, both in the mainline kernel (under Device Drivers/Network Device Support/Wireless LAN: Ralink Driver Support/Ralink rt27xx/rt28xx/rt30xx (USB) Support/rt2800 - Include Support for rt53xx devices & Realtek rtlwifi family of devices /Realtek RTL8192CU/ RTL8188CU USB Wireless Network Adapter). I suspect these also need firmware but I'm not sure where that would go in the image; I can help you troubleshoot where and build it if need be.

Thank you.

[Shoesy]

Little video of jet set radio on redream: https://www.youtube.com/watch?v=xudIVEUtiuc

[notime2d8]

I really wanted this to work...but the graphics drivers won't let me be great. I spent a good bit adding Miracast code back in, adding wifi drivers, getting wifi concurrent and wifi direct working... but think I'm over this until I circle back around to updating the graphics drivers

20200811_185608_HDR.jpg (348.99 KiB) Viewed 3626 times

[Shoesy]

Would be cool! High latency though I guess

[retrovortex]

Some instructions I wrote for someone to be able to expand the data partition for larger microSD cards.

Right so first you need Linux and gparted or another disc manager (the default one in the Linux image I use should work fine its called "disks"), and then what you do is bring up a terminal and then type: sudo apt-get install f2fs-tools
Once thats installed, you then put in your micro SD thats been flashed with the image into the pc with a card reader, load up the partition manager, and find your microSD. It will have four partitions and a large gap.
The final partition which is f2fs and labeled "/data" is the one you want to modify. Now. I'm not sure if you can expand the partition, but I deleted my /data partition just to be sure. Then you simply make a new partition. Select "other" and a list of types should show up. The f2fs option was greyed out before, but its selectable now, so I selected that, and then labeled the partition "/data" like it was before and let it build. Double checking i did it right I looked at the newly made partition to check it was f2fs.
Then I simply got Linux to boot and it eventually did and went to the setup page like it would on a first boot. Followed that, and hey presto its all working good.

[Shoesy]

I just used the gparted live stick, and made the data partition fill the rest of the space. Seems to work fine, although I don’t think I had any data on there to mess up

[zztfoxdev]

But did expanding /data give you more usable space?

BOOT should give you more actual space as it is what the system sees as a usable memory card.

So technically you would move /data to the far end of the card followed be /vendor, then /system. Then you could expand BOOT to the remaining size.

What would be ideal would be to script this as a one time function at boot, but neither me nor notime2d8 have been able to crack how to do that yet.

[notime2d8]

But did expanding /data give you more usable space?

BOOT should give you more actual space as it is what the system sees as a usable memory card.

So technically you would move /data to the far end of the card followed be /vendor, then /system. Then you could expand BOOT to the remaining size.

What would be ideal would be to script this as a one time function at boot, but neither me nor notime2d8 have been able to crack how to do that yet.

I actually haven't tried ....I'm putting all my money on me getting TWRP working. I should be able to to use existing code then. A lot of examples on how to do it with an update.zip. And i got carried away fixing that SD card partition mounting issue... I got rid of the emulated storage as well. Next time I sync and rebuild it'll be added back. The emulated storage would use the data partition giving us two storage locations.

Also i was able to get Mupen64 FZ working and it runs amazing. I didn't get any error message? I wasn't able to scan for roms though until I made a change in the emulator settings.

[kiebitz]

Just out of curiosity.
I don't know if it even make any sense.
But I'm wondering if Pokemon Go could be getting running?

I even have an old GPS Bluetooth receiver here lying around.

[zztfoxdev]

But did expanding /data give you more usable space?

BOOT should give you more actual space as it is what the system sees as a usable memory card.

So technically you would move /data to the far end of the card followed be /vendor, then /system. Then you could expand BOOT to the remaining size.

What would be ideal would be to script this as a one time function at boot, but neither me nor notime2d8 have been able to crack how to do that yet.

I actually haven't tried ....I'm putting all my money on me getting TWRP working. I should be able to to use existing code then. A lot of examples on how to do it with an update.zip. And i got carried away fixing that SD card partition mounting issue... I got rid of the emulated storage as well. Next time I sync and rebuild it'll be added back. The emulated storage would use the data partition giving us two storage locations.

Also i was able to get Mupen64 FZ working and it runs amazing. I didn't get any error message? I wasn't able to scan for roms though until I made a change in the emulator settings.

Sorry, thats what I meant to say :p

You have been REALLY busy making sure things work and I do not know enough to make it expand the partition.

You have been really amazing getting this image this far!

Also, about FZ, is that on a new version of the image or the current one I have and what version of FZ?

[zztfoxdev]

Just out of curiosity.
I don't know if it even make any sense.
But I'm wondering if Pokemon Go could be getting running?

I even have an old GPS Bluetooth receiver here lying around.

I have seen where people run it without GAPPS on Lineage OS, but even if you did all that you would still need a mouse to click stuff since there is no touch screen. And a seperate account so Niantic does not ban your main one :p

[Shoesy]

Any chance of adding a hotkey to turn the analog controller to a mouse? I hear that’s what happens on the retroid pocket 2 android build

[zztfoxdev]

Any chance of adding a hotkey to turn the analog controller to a mouse? I hear that’s what happens on the retroid pocket 2 android build

I think that would be what we need TWRP for, flashing custom modules/kernels for.

So TWRP needs to come first before any low level functions like that could happen.

I could be completely off the mark, however.

[notime2d8]

Any chance of adding a hotkey to turn the analog controller to a mouse? I hear that’s what happens on the retroid pocket 2 android build

I think that would be what we need TWRP for, flashing custom modules/kernels for.

So TWRP needs to come first before any low level functions like that could happen.

I could be completely off the mark, however.

Right, the direction I'm going going is TWRP -> Root -> Mouse toggle app that gives that functionality.

I don't know how they implemented it on the retroid pocket. But they did say they were sticking with Android 6 because they put a lot of work into it...I'm assuming that "lot of work" is that mouse mode and I doubt they'll release source code for it.

If that option doesn't work I'll try to do it on the kernel side but i don't know if that is possible.

[rooted]

While I've never tried it someone may want to give this a go:

https://www.easeapps.xyz/en/apps/ease-joypad

[notime2d8]

I know at @zztfoxdev mentioned gforce Now before... I tried steam link and it was pretty decent. I made it through a few levels of Bastion. I need to upgrade my GPU so I can try moonlight.

20200813_211722_HDR.jpg (184.33 KiB) Viewed 3422 times

20200813_212331_HDR.jpg (303.59 KiB) Viewed 3422 times

[notime2d8]

While I've never tried it someone may want to give this a go:

https://www.easeapps.xyz/en/apps/ease-joypad

Thanks, I did try this as it doesn't require root but it doesn't work as desired. And it doesn't give a mouse pointer, but a weird grid pointer.

[macromorgan]

Thanks for the kernel, I'm going to try building myself and see if I can help improve some QoL stuff like more WiFi adapters and the like. Quick question, do you have the config you used for the latest version against Lineage OS? I assume the version posted on sourceforge.net are for the AOSP builds you did earlier?

Thank you again for all your hard work!

[notime2d8]

Thanks for the kernel, I'm going to try building myself and see if I can help improve some QoL stuff like more WiFi adapters and the like. Quick question, do you have the config you used for the latest version against Lineage OS? I assume the version posted on sourceforge.net are for the AOSP builds you did earlier?

Thank you again for all your hard work!

The .config that i'm using was included in the kernel that i posted. It may be hidden.

[macromorgan]

Thanks for the kernel, I'm going to try building myself and see if I can help improve some QoL stuff like more WiFi adapters and the like. Quick question, do you have the config you used for the latest version against Lineage OS? I assume the version posted on sourceforge.net are for the AOSP builds you did earlier?

Thank you again for all your hard work!

The .config that i'm using was included in the kernel that i posted. It may be hidden.

My apologies, I meant the latest Android build config. I’m curious about what it takes to get TWRP and stuff integrated and want to help.

[notime2d8]

Thanks for the kernel, I'm going to try building myself and see if I can help improve some QoL stuff like more WiFi adapters and the like. Quick question, do you have the config you used for the latest version against Lineage OS? I assume the version posted on sourceforge.net are for the AOSP builds you did earlier?

Thank you again for all your hard work!

The .config that i'm using was included in the kernel that i posted. It may be hidden.

My apologies, I meant the latest Android build config. I’m curious about what it takes to get TWRP and stuff integrated and want to help.

So TWRP doesn't build against LineageOS, a lot of errors and changes from lineage doing their own recovery. Which, I've gotten lineage recovery working, but it can't find partitions and doesn't have some other features we need.

So I downloaded, but haven't looked at yet, twrp-minimal. I need to make a device folder and config for it, build it, and it should give me a ramdisk.cpio file that I can build into the kernel.

So you can try to build TWRP and either include it in the Kernel (then remove the skip_initramfs command from boot.ini to load it) or convert it into an initrd and edit the boot.ini to load it like the stock boot.ini. Nothing special/extra is needed to bring up TWRP, just need to configure it right.

Now if you want the LineageOS build files, I can compres and send you the device folder, and links to the additional folders for the gpu, etc.... I need to create a manifest.xml for it... ... But my patches to LineageOS might take me a little bit. I did quite a few patches to get Rockchips parts to play nice without using their heavily patched SDK. Also why you don't see different builds for Rockchip devices . But I can get that for you if you want it. It'll just be awhile.

[macromorgan]

Thanks for the kernel, I'm going to try building myself and see if I can help improve some QoL stuff like more WiFi adapters and the like. Quick question, do you have the config you used for the latest version against Lineage OS? I assume the version posted on sourceforge.net are for the AOSP builds you did earlier?

Thank you again for all your hard work!

The .config that i'm using was included in the kernel that i posted. It may be hidden.

My apologies, I meant the latest Android build config. I’m curious about what it takes to get TWRP and stuff integrated and want to help.

So TWRP doesn't build against LineageOS, a lot of errors and changes from lineage doing their own recovery. Which, I've gotten lineage recovery working, but it can't find partitions and doesn't have some other features we need.

So I downloaded, but haven't looked at yet, twrp-minimal. I need to make a device folder and config for it, build it, and it should give me a ramdisk.cpio file that I can build into the kernel.

So you can try to build TWRP and either include it in the Kernel (then remove the skip_initramfs command from boot.ini to load it) or convert it into an initrd and edit the boot.ini to load it like the stock boot.ini. Nothing special/extra is needed to bring up TWRP, just need to configure it right.

Now if you want the LineageOS build files, I can compres and send you the device folder, and links to the additional folders for the gpu, etc.... I need to create a manifest.xml for it... ... But my patches to LineageOS might take me a little bit. I did quite a few patches to get Rockchips parts to play nice without using their heavily patched SDK. Also why you don't see different builds for Rockchip devices . But I can get that for you if you want it. It'll just be awhile.

No worries, don't want to take time away from your hard work. Just let me know where I can be of assistance and I'll do my best. For now I can recompile the kernel with support for more WiFi adapters at least.

Also, am I misremembering or did I read somewhere you compiled with -O3? Does -Os negatively impact performance that much (I'm thinking given the 1GB of RAM reducing memory pressure might be a bigger win than increasing performance from Os to O3).

edit: got my WiFi to work by building in the module and firmware into the kernel (along with a bunch of other ralink and Realtek adapters). Is there a reason why everything is built-in versus as modules? Just curious. Thanks.

[notime2d8]

yes, i did compile the kernel and Android with the -O3 flag because of two sources i read:

Android by default is compiled with O2 flag for target ARM (about 10% of Android, mostly low-level parts) and Os flag for target THUMB (about 90% of Android, nearly everything apart from low-level parfs). Some guys think that Os is better than O2 or O3 because smaller code size is faster due to better fitting in CPU cache. Unfortunately, I proven that it is a myth. Os was good back in 2006, as only with this flag Google was able to compile Dalvik and it's virtual machine while keeping good amount of free memory and space on eMMC cards. As or now, we have plenty of space, plenty of ram, plenty of CPU power and still good old Os flag for 90% of Android.

-Link

Remove the kernel config for CONFIG_CC_OPTIMIZE_FOR_SIZE. This flag was originally introduced when the assumption was that smaller code size would yield hot cache hit (and thus be faster). However, this assumption is no longer valid as modern mobile SoCs have become more powerful.

-Link

But i also did a few test and i didn't notice an increase in ram usage from 32bit/64bit and Os/O3. I also disabled the low ram config in android and it still used the same ~400mb of ram and ~800mb used with apps/processes cached but the ram would be reclaimed if needed. So we usually have 600mb+ plus Zram to play with and i haven't seen or heard of low ram issues.

So for the WIFI...I only added two drivers to test 3 USB sticks that i had while trying to get WIFI display working... I couldn't get it working in the time i allotted for it and haven't thought about the WIFI since. But i did make the line that loads the WIFI module generic so you could swap out the wlan.ko with another module of that name and Android would load that module.

And i had the drivers built in because it was easy for me to just comment out the line that loads the built-in WIFI module, and plug in whatever USB WiFi i wanted without changing or adding modules? At the time it was easier to change the kernel than pushing a file to the vendor partition.

[macromorgan]

Cool. I’ve got a kernel with a shitload of WiFi (along with the firmware) built in now. Let me know if it would be useful to you.

I also got the (non-Android) mainline 5.8 kernel booting on Debian. Any benefit to getting the AOSP 5.9 running?

[Tagruato_Corporation]

@notime2d8, PrydaBoy on Reddit is working on Android for the RG351P (an OGA clone)

https://www.reddit.com/r/SBCGaming/comm ... of_rg351p/
https://www.reddit.com/r/SBCGaming/comm ... ndroid_10/

[notime2d8]

Cool. I’ve got a kernel with a shitload of WiFi (along with the firmware) built in now. Let me know if it would be useful to you.

I also got the (non-Android) mainline 5.8 kernel booting on Debian. Any benefit to getting the AOSP 5.9 running?

So when I tested those kernels, they didn't have the screen initialization issue that the rockchip 4.19.111 kernel has using the same display driver. Also got the GPU and controls working, but I could not get sound working. If sound worked I would switch to that kernel as I could test Rockchip and panfrost graphic drivers and switch between the two easily.

[notime2d8]

@notime2d8, PrydaBoy on Reddit is working on Android for the RG351P (an OGA clone)

https://www.reddit.com/r/SBCGaming/comm ... of_rg351p/
https://www.reddit.com/r/SBCGaming/comm ... ndroid_10/

Yeah I saw, wish they posted up details. It seems weird they're using LineageOS like me and not the Rockchip SDK . Also wondering if they got the GPU working or have newer Mali blobs than me.

[macromorgan]

@notime2d8, PrydaBoy on Reddit is working on Android for the RG351P (an OGA clone)

https://www.reddit.com/r/SBCGaming/comm ... of_rg351p/
https://www.reddit.com/r/SBCGaming/comm ... ndroid_10/

Yeah I saw, wish they posted up details. It seems weird they're using LineageOS like me and not the Rockchip SDK . Also wondering if they got the GPU working or have newer Mali blobs than me.

Do the blobs need to be version matched to the kernel shim, or does it matter (much).

edit: also how far did you get with the audio? I got the driver to compile on the upstream kernel (after redoing some structs that changed) but I think I’m having trouble getting it defined correctly in the device tree.

[zpy3]

I think oga needs to be configured to not allow background processes
This needs to enter the developer options
Otherwise, the background space will be insufficient. You know the space occupied by the Android background process is very exaggerated.

[rooted]

I think oga needs to be configured to not allow background processes
This needs to enter the developer options
Otherwise, the background space will be insufficient. You know the space occupied by the Android background process is very exaggerated.

Setting maximum background processes to 1 doesn't seem like a bad idea to try.

[zztfoxdev]

So obviously this whole setup is reasonably flakey at the moment, but here's some of my feedback on the Dreamcast bits I could get working!

Redream v 1.18 works nice and easy, but I couldn't get great performance out of it. Maybe the pay version would work better? Doesn't seem to be any options to tinker with in the free version. Scaling etc looks great though.

Flycast standalone is a bit flakey and hard to see (ui scaling is off - too large for a change!). BUT once you get it working it has great performance. Like fractionally better than any of the Linux setups Ive tried on OGA. I tried Jet Set Radio - frame rate reported hovered around the 20fps mark (like it does on RRVL and Emuelec) but the motion on screen was smooth. I switched to 2x scaling without any drop in performance, and turned off some of the extras (fog, clipping etc) for best performance. Sadly though experienced a lot of crashes back to the launcher screen with JSR.
I also tried Quake 3 arena, with similar results, but no crashes which was great. Some slowdown and certainly not a fully smooth experience, but certainly the most playable I've had it running on the OGA.
Flycast core also seems to work ok in Retroarch64 btw, but feels a bit more like it's struggling - fps counter is around the same with JSR, but audio sounds jittery.

Been meaning to ask where you got flycast standalone and what version you used.

[zztfoxdev]

I think oga needs to be configured to not allow background processes
This needs to enter the developer options
Otherwise, the background space will be insufficient. You know the space occupied by the Android background process is very exaggerated.

If you use a mouse to get to the search bar in settings you can type "about" and it will pull up about tablet. Click this to get to the About screen, click build number x amount of times (with mouse) and it should say you are developer.

Go back out to settings search tab, type developer options, click when they pop up and scroll down to keep no activities and kill all background processes. Disabling these will accomplish what you are asking. Seems to keep things tidy, but not so sure about the system running faster.

[Shoesy]

Been meaning to ask where you got flycast standalone and what version you used.

I just used the latest build that had test images on Flyingheads builds page: https://flyinghead.github.io/flycast-builds/

[zztfoxdev]

Been meaning to ask where you got flycast standalone and what version you used.

I just used the latest build that had test images on Flyingheads builds page: https://flyinghead.github.io/flycast-builds/

Did the menus work with the oga controls? Or did you use a usb controller?

Also, you mentioned resizing the screen to get eveything up and running?

[Shoesy]

Just used the mouse to nav. I don’t think you need to resize the screen, but it could do with a smaller ui.

[zpy3]

I think oga needs to be configured to not allow background processes
This needs to enter the developer options
Otherwise, the background space will be insufficient. You know the space occupied by the Android background process is very exaggerated.

Setting maximum background processes to 1 doesn't seem like a bad idea to try.

thank you very mach, and now I don’t know how to get root privileges
I tried super su, but it didn't work
google play also failed to install

[zpy3]

I can’t specify a default app，I install ATV launcher，But every time I need to return to the home screen, the system prompts me to select the launcher