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 - bolderz

Pages: [1] 2
1
Cosmo Communicator - Linux / Re: Boot menu is missing
« on: January 31, 2022, 08:55:46 am »
The best method is probably to use the officail multi-boot installation including both normal and rooted android provided by Planet Computers.  You can find information on the Planet website and there is lots of information on other threads on this forum as well.

2
Thanks again, Onkel, I have successfully updated Magisk in the rooted boot to V23 using the procedure detailed in the first post.  The updated version is now shown in both panels of the app and both normal and rooted Android boot run normally without failing verification.

3
Planet Update #48 shows Astro assembly production actually starting on Christmas Day 25 Dec.

4
I charged my Cosmo overnight running rooted Android to 100% and then turned it off this morning around 09:00.  I have just turned it on again at 20:30 and it still came up at 100% charged.  So it looks as though there is negligible discharge of the battery when it is turned off. As far as I know I haven't done anything special to make sure that the device is fully turned off. 

5
Cosmo Communicator - Linux / Re: New Gebian Linux user questions
« on: May 22, 2021, 10:02:32 am »
But I have to say that messaging-app  is only working for outgoing messages. Not for  incoming messages. I don't know if it is working as expected for you. Good luck .

Same for me.  Outgoing calls work in phone and messaging, but nothing incoming.  I think you have followed this up elsewhere on the forum.  I haven't tried to fix the phone for incoming calls myself.

6
Cosmo Communicator - Linux / Re: New Gebian Linux user questions
« on: May 21, 2021, 01:59:46 pm »
Thanks cam1965.  That worked.  aptitude identifies apparmor as breaking media-hub and messaging-app and gives the option not to install apparmor.  LibreOffice was then installed with messaging app still available.

7
Cosmo Communicator - Linux / Re: New Gebian Linux user questions
« on: May 01, 2021, 09:55:13 am »
There seems to be a conflict in gemian v4 with LibreOffice.  Attempting to install LibreOffice gives a warning that it will remove packages camera-app. media-hub, messaging-app.  I recall that the message app disappeared on installing LibreOffice in gemian V3, which could be fixed by re-installing the message app.  I aborted the installation of LibreOffice this time, but presumably the next thing to try is re-installing these packages after LibreOffice.
 

8
Cosmo Communicator - Android / Re: need to reflash stock android image
« on: April 24, 2021, 04:40:39 pm »
There is this https://support.planetcom.co.uk/index.php/Cosmo_Android_Firmware_Manual_Installation on the Planet website which supports the manual installation of Cosmo Android V19, V22 and V23 complete with download files.

9
Have you updated or installed the non-rooted android V25 first?  Rooted android is a layer on top of the non-rooted android and is not a complete system in itself.

10
I have found the answer to getting the key mappings to work with the Cosmo keyboard.  After following the Planet advice to set up the keyboard layout, you must delete any other layout so that the GB layout is the only one available.

Many thanks to Piece_Maker for the suggestion and lokomoko for showing me where to look. https://www.oesf.org/forum/index.php?topic=36158.msg295099#msg295099

11
I have loaded up the new V2 Linux firmware and gone through the installation instructions from Planet.  Most of it runs OK but there are some things I can't get working
 
Despite setting the keyboard layout to
Code: [Select]
Keyboard model: Planet | Planet Computers Cosmo Communicator
Layout: English(UK)
I cannot find a key combination to give "-" for example.  Also the some of the keys don't map crrectly, "/" gives "<" for example.

Using sudo bash to get root, I have run apt update and apt upgrade, but I am getting a certificate warning.  From re-running apt update, it looks as if the update worked.

Code: [Select]
root@cosmopda:/home/cosmo# apt update
Hit:2 https://deb.debian.org/debian buster InRelease                         
Hit:3 http://gemian-buster.thinkglobally.org/buster buster InRelease         
Get:1 https://gemian.thinkglobally.org/buster buster InRelease [4104 B]
Ign:1 https://gemian.thinkglobally.org/buster buster InRelease
Fetched 4104 B in 1s (5084 B/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: GPG error: https://gemian.thinkglobally.org/buster buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6669378035F4918C
Also I cannot get the Device Notifier popup to scroll despite having a scroll bar which activates.

Is there something obvious I am missing or is there a fault?  Is everyone else using a different keyboard?

12
From IndieGoGo Daniel Mader reports this response from Planet Support:

Customer Support 1 (Planet Computers) Jun 26, 2020, 4:39 PM GMT+1 Dear Daniel, I'm actually not sure what happened here exactly, but I would like to rule out a possible hardware failure by asking you to perform a manual installation of the v22 firmware. You can install the latest v22 firmware by using this manual installation (http://support.planetcom.co.uk/index.php/Cosmo_Android_Firmware_Manual_Installation).

Link gives V19 and V22 downloads for manual installation.

The downloads verify successfully against the MD5 checksums given, but I haven't tried installing from them yet.

Edited to correct link (thanks @ehem)

13
Cosmo Communicator - Hardware / Wierd Cosmo after partitioning
« on: April 03, 2020, 02:54:37 pm »
Copy/paste text with links appears to damage the links.

Here are the links again, hopefully intact:

https://www.oesf.org/forum/index.php?showto...35879&st=90
Topic   Cosmo Communicator - Hardware > Rooting the Cosmo Communicator Post #97

https://www.oesf.org/forum/index.php?showto...35879&st=60
Topic   Cosmo Communicator - Hardware > Rooting the Cosmo Communicator Post #69

14
Cosmo Communicator - Android / Boot error after setting up rooted android
« on: February 28, 2020, 06:48:23 am »
I see what you mean, but the rooted Android option does not work with the SIM card, and so is not suitable for everyday use.

However since I installed Magisk, the 'non-rooted' Amdroid appears in fact to be rooted (see previous post) and so there is no need to use the rooted Android option at all.

Still not sure what's going on here...

15
Cosmo Communicator - Android / Boot error after setting up rooted android
« on: February 27, 2020, 11:35:20 am »
As far as I can tell, both normal android and rooted android boot options are giving me a rooted android.  After a normal android boot Magisk shows two green ticks and Solid Explorer reports that it has been granted Superuser rights.  Also Magiisk does not fail on startup.

This is also the case for the rooted android boot option, the main difference being that the SIM works for the normal android boot option. So even though normal boot is the default, I don't really have a way of running android without root.

Iniitally, mobile data refused to work for the normal android option, but this turned out to be because the SIM slot for mobile data had not been selected (see Settings | Network & Internet | SIM cards).

Although the Cosmo is quite usable, I suspect I might have problems with the next update, unless Planet provide a full image install.

I am hoping root will allow me to use Titanium Backup and possibly import bookmarks into Firefox.

Pages: [1] 2