clockworkpi

GameShell OS image files (v0.5)

@guu @yong attached a video of the issues I’m seeing on my GS after updating to v0.5.

In addition to the Wi-Fi not working, now whenever I power on GS, its screen goes dim and remains as such, even when I’ve set the brightness to max. Also, the UI seems to freeze (can be noticed once or twice in the video) every now and then.

https://filebin.net/1bulvo7i4d8ozeqr/gameshell-screen-dim-wifi-broken-v0.5.mp4?t=o3bbtn5z

By updating, was that an update from 0.4 to 0.5 using the update? Or a complete update and flash of a fresh 0.5 image?
I’m guessing it was the former, but if it was the latter, that is a lot of things to go wrong on in a fresh image, an shouldn’t have.
It might just be worth restoring your backup you made before updating, retrieving all of your Roms and changes, then flashing a new card from scratch. (Assuming your backed up your card before updating as per the instructions)

This was an update of basically the stock image on the sd card that I had received with the GS. Basically, the day before was the first time I did a re-flash of the sd card.

I’m not sure what version was originally on the sd card :disappointed:

I’m guessing it came with 0.4. In which case, you don’t have much to lose. I wasn’t sure if you updated because you had a lot of established files.
In fact, it will be faster to flash a new 0.5 image from scratch. :slight_smile:
I couldn’t view your video for some reason, but your description basically sums up a bad time.

Yeah, not sure what happened with the video. Please refresh, I added the link to the video file as well.

Hang on… when you say update, do you mean updating via the settings menu, or the larger more involved update script mentioned in the earlier posts of this thread?
If it’s the former, that probably wasn’t an update to 0.5, and instead an update to the launcher that was expecting your system to already be at 0.5.
Another user made a thread with this same problem. Sounds like it’s something that needs to be addressed and made more fool proof.

I took out the sd card from the GS, and flashed v0.5 on it via etcher on my mac. I’ve had this GS for several months (I hadn’t used it much), so whatever version was on it was pretty old.

@javelinface are you able to access the video via the link https://filebin.net/1bulvo7i4d8ozeqr/gameshell-screen-dim-wifi-broken-v0.5.mp4?t=o3bbtn5z?

I’ve had this situation before, but it’s rare

I just unpluged the mainboard , unpack and repack it, if that does not help,try to refresh the os v0.4 for testing, if os 0.4 not working, then it must be a hardware issue

1 Like

That seemed to be a valid link to download, although it needed to be clicked as an external link. :slight_smile:

I occasionally had the wifi not work. I just restarted it, and then it fixed itself. Then on times it didn’t activate, again, I just kept restarting it till it did work. This was for an earlier version that I fiddled with a lot.

Just having a think, re: the slow downs. Perhaps it’s taking up extraneous memory, trying to get the wifi started with some kind of cyclic loop.

Another thought. Dimming of the screen could be happening after initially starting, and then applying the setting you have in your system. It boots up at 100% brightness, which quite frankly is way too bright, and drains the battery like mad. As for why it can’t be changed, maybe it’s the wifi loop taking up too much memory, not allowing the hook for brightness adjustment to activate.

Have you tried flashing to a different card? Sounds like there’s a lot wrong, that could almost warrant starting a new thread. :slight_smile:

1 Like

Tried to update and upgrade before running the update script, but the GameShell crashed. Now when I try to start it up it gets stuck on “Loading…”.

Decided to flash instead, downloaded the image but balenaEtcher complains that “Something went wrong. If it is a compressed image, please check that the archive is not corrupted.”

md5 ~/Downloads/clockworkos_v0.5.img.bz2
MD5 (/Users/bjornkri/Downloads/clockworkos_v0.5.img.bz2) = 27f85542d0278f898bfca060c264dc6f

Seems to check out… Any ideas?

EDIT: Leaving this here if anyone else has the problem. Updating balenaEtcher did the trick. 1.5.5 -> 1.5.7

2 Likes

@guu @javelinface thanks for the inputs. I’ll definitely try flashing to a brand new SD card and using that to see if things improve.

Also, I noticed yesterday when I had the GS ON for 30-45 minutes–its back (the area somewhere below the micro HDMI port, I think) was getting extremely hot :fire: (so much so that I wasn’t able to hold it from there)! Is this also expected, or a potential h/w issue as well?

I also had trouble flashing to 0.5 with balenaetcher, even though I’d used it months ago to flash 0.4. I ended up using win32diskimager instead and that worked. Sounds like balenaetcher may have been buggy. :frowning:

The app I actually use for most of my image writing is apple pi baker. It’s meant to be for preparing raspberry pi images, but basically does the job for CPI with a few extra tricks up its sleeve. I hadn’t had to update it in years.


And don’t worry. I’m not like advertising for them. Just saying what I use.

@chalchitra What were you doing for those 30 minutes. For diagnostic purposes, I’ve had my gameshell on for about 12 hours on the homescreeen, plugged in via USB power. It’s no hotter than my cat’s stomach. That’s to say 38 degrees celcius.
When doing something more intensive, eg playing mupen64plus or Quake 2, it gets about as hot as a cup of green tea, or about 80 degrees celcius.
This is actually cooler than what it used to be. I guess it comes down to what people individually perceive as hot.

Also consider there are no heat sinks on the unit. I’ve considered cutting a large portion of the CPI casing, and installing an exposed heat sink plate. So far, I haven’t had any stability, slow downs or error inducing problems due to heat. It’s all within operating specs, which I think was twice as hot. I’ll have to dig up the data sheets but it was around there. Here’s the heat sink type I was thinking of. I needed it for my raspberry pi, otherwise it would constantly crash.

In summary, it gets hot. It’s just something I’ve gotten used to.

1 Like

It appears that my issue with the 0.4 to 0.5 upgrade was caused by the missing theme icons that were added in v0.5.
Missing files prevented the themed OS from loading and resulted in being stuck on “Loading” screen.
Anyway, copying the files below over from /home/cpi/launcher/skin/default to your favourite theme folder should solve the problem:

sys.py/gameshell/icons/add.png
sys.py/gameshell/icons/app.png
sys.py/gameshell/icons/appdling.png
sys.py/gameshell/icons/ware.png
sys.py/gameshell/titlebar_icons/dlstatus18.png

I have updated my dark theme (and styled new icons) accordingly, so it now works with clockwork OS v0.5

1 Like

To disable “You have new mail.” message:

sudo nano /etc/pam.d/login

comment this line:

session    optional   pam_mail.so standard

so it looks like this:

# session    optional   pam_mail.so standard

If you want to disable it for ssh too, edit /etc/pam.d/sshd in the same way.

To get rid of tidal, qobuz and id3v1_encoding warnings:

nano /home/cpi/.mpd.conf

add this:

input {
        plugin     "qobuz"
        enabled    "no"
}

input {
        plugin       "tidal"
        enabled      "no"
}

decoder {
        plugin       "hybrid_dsd"
        enabled      "no"
}

and comment this line:

id3v1_encoding         "UTF-8"

so it looks like this:

#id3v1_encoding         "UTF-8"

save and reboot.

3 Likes

Hey folks, a little help on this one would be appreciated. I’m super new to all this, (got the gameshell as a learning/fun gadget) and am having some issues following the instructions above, and I’ve tried to use the comments but I feel I’m missing something basic.

Steps I’ve taken:

  1. Installed Putty and learned how to ssh into the gameshell
  2. Used sudo apt-get update + sudo apt upgrade - this seemed to update a bunch of files
  3. Used wget command to download the patch file
  4. Got stuck on how to ‘run’ the file, as run isn’t a command?
  5. Installed FileZilla (gui, yay!), confirmed that the patch file is in the root directory of the pi

So I know I’ve got the patch file, but I can’t for the life of me figure out how to ‘run’ it, like the instructions say to. I’ve tried a ‘run’ command, and have rebooted the pi to see if it shows up on the pi’s gui, but no dice.

Like I said, I’m sure it’s something super simple. I appreciate the help!

As in windows, linux has file permissions.
You can find a nice starting point on linux systems here UNIX Tutorial for Beginners

So lets start from the basics.

You can check if the patch script has executable permission with (More info here http://www.ee.surrey.ac.uk/Teaching/Unix/unix5.html)

ls -l

Probably as you downloaded it from the internet, the patch doesn´t have execution rights for security reasons.

You would have to do

chmod +x patch_for_clockworkos_v0.4.sh

and then to run any script you just need to put ./ in front

./patch_for_clockworkos_v0.4.sh

2 Likes

Thank you, this was exactly what I needed!

Hello! Welcome to the forums. :slight_smile:
An interesting thing I saw in your initial commands. You did a sudo apt-get update, then a sudo apt upgrade.

It comes down to the apt vs apt-get debate. I prefer to use the former, “newer” version. Very minor differences in the way they handle things.

I’d probably stick to using the same one you used to update your sources for the upgrade, ie,

sudo apt update
sudo apt upgrade 

#OR

sudo apt-get update
sudo apt-get upgrade 

It was always my assumption that updating one, then using the other to upgrade wouldn’t ensure having the updated lists.

Hello! I just got done patching O.4 and had to reinstall the Lima drivers and delete the OS 1 theme to get my Launcher booted. Games are running now! Yay! However for some reason my Light Keys aren’t being recognized now. Has anyone else had this issue? They still light up so I believe they’re functioning.

1 Like