Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - MonkeyControl

Pages: [1] 2 3 ... 6
Gemini PDA - Linux / Re: Ubuntu Touch on gemini
« on: June 16, 2021, 03:35:40 am »
unfortunately it looks like there was no real progress on getting UT to run on Gemini or Cosmo afaict.
I can't speak for the Gemini, but as far as the Cosmo goes it seems to be coming along.

Cool. It does sound like it might meet my use case. Let me know how you get on if you manage this weekend.
My weekend didn't go to plan, but I did get a little trial run. 
I managed to get to a stage where all the options: 
    [1] NORMAL
    [2] RECOVERY
    [4] DEBIAN_KDE
    [5] UBPORTS
    [6] FASTBOOT
appear on bootup, but rooted android doesn't boot.  Also note the recovery option is still there after I tried to put rooted android into 'EMPTY_RECOVERY_BOOT_2'. 
I'll have another go this weekend, maybe changing the sequence I load stuff up, or putting stuff in different slots. 
The order I tried (following the instructions from the Planet website ( using firmware V3) was: 
1.  Debian into EMPTY_NORMAL_BOOT_3, (worked okay)
2.  Tried Rooted Android into EMPTY_RECOVERY_BOOT_2, (appeared below recovery on boot options, but didn't boot)
3.  Rooted Android into EMPTY_NORMAL_BOOT_4, (seems okay, but android is still ugly) :)
4.  Ran out of time and needed Ubuntu Touch back, so installed as per instructions here ( 
I wrote the procedure down as I went along, it's a bit long winded for a post, but I'll pm it to you if you are interested. 
I'll have another crack this weekend if I get time. 
Sorry, can't be more help than that at the moment, I'm short of time and really don't know what I'm doing :)

Thanks for that. When I've some time, I shall give it a go. If you do get there before me, I'd be interested to hear your experience.
I didn't have time last weekend, definitely this weekend though, full backup then a deep breath. 
Are you using Ubuntu as a phone or just as a mobile computer?
Full time phone, part time computer, I suppose.  Maybe you don't quite get the full desktop package experience that you do with Debian, but for me UT fits my use case, and it's very stable and has a really nice interface. 
How do you find the battery life?
From an overnight charge I get a day's work out of it, maybe a little topup in the evening if I'm caning the browser.  UT seems a lot lighter on battery than Debian, and also better signal coverage, not sure if the two things are related. 

I couldn't find much to help you other than this post warning about no modem access:, and you suggested you didn't need wireless, but other than that I don't know.  Maybe do a backup and give it a go, or contact PC and see what they have to say about it.  I have Android, Recovery, Debian, UBPorts, FastBoot options on my Cosmo.  UBPorts is my default and I have no use for Android, but I may have a go this weekend out of curiosity, if I'm feeling brave. 

I also cannot Import vcf contacts, Screen stays white in the Phone App. Any ideas? Tia
Apologies for the late response on this one, I spend most of my time in UBPorts these days. 
This link has a solution:
I've just tried it, it works for me. 

Dear users
I usually type
echo 42 > /proc/aw9524_led_proc
in the terminal to switch on keyboard backlight in gemian. After I close the lid and reopen it, the keyboard backlight is off again and I have to type that again. Does anyone of you maybe know of a way to keep this permanent or a way to execute that command after opening the device automatically? Like "If open lid, then echo 42 > /proc/aw9524_led_proc"
I thought about this myself, but more in a UBPorts than Gemian way, I even asked the question on the UBPorts forum (, more around creating keyboard shortcuts generating the effect required than opening the keyboard, sort of 'If (shift + fn + n), then echo 45 > /proc/aw9524_led_proc' , 'If (shift + fn + b), then echo 40 > /proc/aw9524_led_proc' rather than 'If open lid, then echo 42 > /proc/aw9524_led_proc', but my question was just a little post as a point of interest in an existing thread rather than an explicit question, I wouldn't even know how to generate a 'feature request'. 
You got me thinking though.  If you want the keyboard backlight to turn on when you open it, (specifically because the keyboard backlight turned off when you closed it), is there already a bit of code with a line that states 'If close lid, then echo 40 > /proc/aw9524_led_proc', that we just need to add your line of code below that states, 'If open lid, then echo 42 > /proc/aw9524_led_proc' below. 
This is all in principle of course, there's probably a lot more to it than that, but if the keyboard backlight turns off when the Cosmo is closed, there is already some form of integration there, just what it is, and how to expand on it. 
I wouldn't have a clue how to even begin to investigate or implement this, for now as a workaround I just open the terminal and use the up cursor to get to the good old 'echo 45 > /proc/aw9524_led_proc' command. 

Cosmo Communicator - Linux / Re: Ubports for Cosmo
« on: February 02, 2021, 02:11:11 am »
Has anybody shared such good news on ? Maybe this will help the adoption of this device. It is not even listed on the device list
I've made a couple of noises over there, and posted a photo of UBPorts running on my Cosmo.  I'm still having a spot of bother with sms receiving, but apart from that it works very well for me.  It's stable, pretty much does everything I need, and the UI is so nice. 

Cosmo Communicator - Linux / Re: Ubports for Cosmo
« on: December 23, 2020, 02:36:19 pm »

I cannot get my simcard running. Any1 can? or it could be my provider.

I got mine running on 2degrees and vodafonenz in NZ, it may be your provider. 
Try looking up your APN settings and having a tinker. 


I'm new to the group so please bear with me if this is widely known/understood.

I was keenly interested in getting he keyboard backlight to work in Cosmo Linux Firmware V3, I asked the support at Planet Computers if there was any way to turn the Keyboard Backlight on, turns out there is (the response from the Planet Computers support folks follows:

In Linux you can adjust the keyboard backlight from the command line.

The following command will work:

“echo X > /proc/aw9524_led_proc”

Where X range from 40 (no light) to 45 (light intensity max).

Again if this is old news my sincere apologies, I hadn't come across the above info before and wanted to share it.


A few more for both the Gemini and the Cosmo on this webpage below:

Cosmo Communicator - Linux / Re: Ubports for Cosmo
« on: November 24, 2020, 05:04:36 pm »
Wow, thanks for this, much appreciated.  This is great for the Cosmo. 
I been using UBPorts as a daily driver (on PinePhone), it's such a nice OS, and the UI is so slick. 
Now my Cosmo (which got parked after I damaged the CoDi, and repair looked unlikely under lockdown), will get its repair and may well get the sim card back. 
I got it installed and working last night, see photo of PinePhone and Cosmo both running UBPorts. 
Well impressed. 

Cosmo Communicator - Android / New v21 Problem
« on: April 22, 2020, 06:57:01 am »
Quote from: TomJ
Anyone experienced anything similar?
I had a problem with the vibrate, not random just couldn't turn it off, tried;  settings/sound/advanced/, then scroll down and turn off 'touch vibration', but still had the vibration, from memory only on some but not all input, maybe just some keyboard or touchscreen input, sorry I can't fully recall.  

After searching I found another option;  settings/system/languages & input/virtual keyboard/planet keyboard/preferences/, then turn off 'vibrate on keypress', which fixed it for me.  I now only get vibration on notifications when I want them.  

I'm on V21 now, but I found this on an earlier version of firmware.  I've routinely performed the same two checks after updates and a couple of flashes, but I haven't seen any difference in behaviour across firmware versions.  

I can't recall any more specifics than that, but yours definitely sounds a bit odd, mine was consistently annoying rather than randomly annoying, and I never saw the thing with the key combinations you describe.  

Try the two settings above if you haven't already found both of them, but failing that you may need to flick an email at Planet for support.

Cosmo Communicator - General Discussion / Latest updates on Indiegogo
« on: April 15, 2020, 07:56:40 pm »
Quote from: Zarhan
Another backer update promised "before end of the day tomorrow".
New update No 52 is out now on the other side

Cosmo Communicator - Android / V21 firmware
« on: April 13, 2020, 08:33:32 pm »
Quote from: Vistaus
Quote from: cge
Are these firmware updates coming from the OTA update system, or are people installing them manually from somewhere?  I haven't seen any available OTA updates on my device since V19.

V20 was pushed via OTA, but was retracted because some people reported issues. They then issued V21, but you have to install that one manually, which will wipe your device.
Link to manual update procedure on Planet website:
Taken from indiegogo update No51:

Cosmo Communicator - Android / V21 firmware
« on: April 01, 2020, 02:00:10 am »
Quote from: Rosie
Sorted now.  Switch the phone off, pop the SIM out, switch the phone on, switch the phone off, pop the SIM back in, switch the phone on.  Let your Cosmo pick up the settings from the 'new' SIM.

I think I saw this problem myself, and I think I managed to fix it by randomly crashing around in 'settings/network-&-internet/mobile-network' and 'settings/network-&-internet/SIM-cards' and 'something/something/something' turning things off and on while occasionally cycling the power, and then moving onto something else entirely before I made a note of what I did.  
I think I prefer your method.

Pages: [1] 2 3 ... 6