Custom D.E.O.T. V2.0+/Clockwork OS v0.5 image - With customised DEOT interface, Kernel 5.7, Optional 1400MHz OC, Debian 10 Buster, Retroarch 1.9.0, Mupen64+ plus more! (Current build: 200903)

[javelinface]

Here we go! Another update, but one to test out before making it prime time. Please let me know how you go with it!

DEOT v2+ Build 200307
7th of March 2020

Current changes:

1. Updated Kernel to 5.4.20
2. Updated to Debian 10, Buster, maintaining Lima drivers functionality. Ie, Buster hasn’t broken everything like it normally does.
3. Installed and configured ScummVM

Future Changes:

1. Incorporate the DEOT boot splash screens
2. Include Drastic emulator, action.config files, and icon
3. Godot

It’s currently uploading to the Google drive from the first post.
I’ll provide a mega link once it’s uploaded.

Custom D.E.O.T. V2.0+/Clockwork OS v0.5 image - With customised DEOT interface, Kernel 5.7, Optional 1400MHz OC, Debian 10 Buster, Retroarch 1.9.0, Mupen64+ plus more! (Current build: 200903)

Similar to my previous DEOT custom build based on 0.4, I have put together a new image, based on the ClockWork OS 0.5. This is the same as the official 0.5 image, just with a lot of updates, and quality of experience optimisations. You don’t need the DEOT edition Gameshell to use this. The official DEOT image is much older, and behind the official 0.5 image. This custom image is the bridge to get the best of both worlds. [b7d679edaee7a55ad42147c9085b5e919824296a_2_462x500] Here is a google dr…

In my rush to upload and compress the image, I forgot to a) empty the mail and b) delete clockwork-pi3-kernel-5.4.20 directory I copied over to muck around with incorporating the custom boot splash screen.
Use the empty mail script in utils to remove the mail dialogue, and just delete the clockwork-pi3-kernel-5.4.20 directory to save about 800MB or so.

As a side, I’m also experimenting with this overclocked 5.5 kernel:

1.2GHz and beyond

First, I’m not responsible for anything if you want to try what I did. Everything is at your own risk. Clockworkpi is advertised as “Allwinner R16-J Quad-core Cortex-A7 CPU @1.2GHz” although if you check your cpufreq-info info with the kernel that came with OS v.0.5 you will see that the maximum frequency is, in fact, 1.008GHz witch is ~20% less. So I thought that maybe something was wrong with it and tried to look more information. The Allwinner R16 datasheet/User manual doesn’t specify what…

I only haven’t provided it, since the overclock may give a beginner user an inaccurate perception of the Gameshell’s battery life due to the overclock, and thus attribute this image with a lower battery life.