Messages

1

Cosmo Communicator - Linux / Re: How to pass a cmd line to kernel ?

« on: June 11, 2021, 04:09:24 am »

Just for curiousity: Does it help to put the quot to the end of the command line like below?

Code: [Select]

--cmdline  "bootopt=64S3,32N2,64N2 log_buf_len=4M apparmor=1 security=apparmor"

2

Cosmo Communicator - Linux / SIM-PIN-Entry in Linux v3 / v4

« on: May 17, 2021, 05:22:27 am »

Planet computer's Linux for Cosmo Article does not mention how to enter the PIN for Telefonie and Messaging. It used to be recommended for v2 to use ofono-scripts to enter the PIN (I don't remember where). Up to now this still for me.

Still I'm wondering, wether there exists a more "out of the box" way of entering the PIN, since there's hardly any mentioning of ofono-scripts here in the forum and the packages is still not installed by default under v4.Any hints?

3

Cosmo Communicator - Linux / Re: no network available error when I try to use the messaging or phone app

« on: February 28, 2021, 05:51:55 am »

I could installed 1.15 on top of 1.14 at least twice. So I can confirm, that this works, but as you already found out, it does not work reliably. It took me around 1 to 5 retries to get a new condi firmware installed, no matter what version it was. If I recall it correctly the installer app did not crash but just reported that the upgrade failed after some time. Then I could just restart.

4

Cosmo Communicator - Linux / Re: Prevent wearing internal flash storage?

« on: January 03, 2021, 08:14:57 am »

Thanks for the pointer, sven1999. I probably should subscribe to that repository

5

Cosmo Communicator - Linux / Prevent wearing internal flash storage?

« on: December 18, 2020, 04:52:00 am »

Running the Linux firmware (currently V3) for some days now and I observe the /var/log directory grow to impressive size of many GB as I already saw with V2. I can find a whole lot of "fuelgauged", "pmic_thread" and "battery_thread" related messages in syslog, messages and kern.log. I'm concerned that this - besides draining the battery - will wear the internal flash storage. Can anyone confirm that this is a problem or am I just a bit paranoid?

While /var/log/journal/ will grow to a max. of around 4GB (Thats what 'systemctl status systemd-journald' tells me), the text files seem to keep growing until they get log-rotated. All together the logging creates a continuos write-bandwith of 200 to 700 kB/s on mmcblk0p43 - around a GB per hour.

So I turned the text file output off by commenting out in /etc/rsyslog.conf. This did not reduce the bandwidth much, but at least it stopped growing the textfiles. Additionally I temporarily deactivated systemd-journald, which brought the storage bandwidth close to 0. So now I don't have to worry about wearing my internal storage anymore.

Still I would like to filter the above mentioned messages before systemd-journald produces write-bandwidth. This would allow me to turn back to normal (stock) logging.

Any ideas how to turn off that excesive kernel logging. Do I have to modify the boot commandline (which probably is not trivial) or can I switch it off in a runing system? What other strategies do you use to prevent wearing flash storage?

Thanks for any help in advance!

6

Cosmo Communicator - Linux / Re: Wrong keyboard mapping on login?

« on: December 17, 2020, 09:53:49 am »

I just left them as your post shows!

7

Cosmo Communicator - Linux / Re: Wrong keyboard mapping on login?

« on: December 16, 2020, 06:41:41 pm »

I just found, that specifying the keyboard layout permanently via
XKBMODEL="planetcosmo"
XKBLAYOUT="de"
in /etc/default/keyboard works fine for all users.

8

Cosmo Communicator - Linux / Re: Wrong keyboard mapping on login?

« on: December 14, 2020, 12:13:55 pm »

Here's some of the keys I found handy before having activated German layout:

/  Shift+,
-  Fn+ö
+  Fn+i
_  Fn+j
;  Fn+k
`  FN+2
"  FN+l

but once you managed to type
setxkbmap -model planetcosmo -layout de
you won't need them anymore 

9

Cosmo Communicator - CoDi / Re: CoDi firmware T1.1.1.15

« on: November 21, 2020, 07:11:34 pm »

Worked to me. Good luck

Thanks for the links to instructions and the official firmware. Good to know where to find them

After a reboot and selecting the T1.1.1.15 manually and another 5 or 6 retries of pressing the flash button (out of mere despair), I finally succeeded without downflashing to T1.1.1.14 first. Fortunatelly once the flashing had started, it finished without errors.

10

Cosmo Communicator - CoDi / Re: CoDi firmware T1.1.1.15

« on: November 21, 2020, 06:34:09 pm »

I'm receiving notifications from Cover Display Assistant once a day telling me that "New version of Cover Display is available" but when I follow the notification to the app it just says "Cover Dispay not responding" or "Codi up to date"

I observe similar sympthoms after manually flashing T1.1.1.15. Codi seems to be dead. Don't really know howto revive it. Fortunatelly Android does not seem to be affected. Can anybody give a pointer?
The "Codi up to date" I assume wants to tell us that the Cover Display Assistant does not know of a newer version than the last version it flashed - most probably T1.1.1.14. So this does not seem to help much.

11

Cosmo Communicator - Linux / Re: New Linux firmware for Cosmo Communicator is now available

« on: July 25, 2020, 07:34:18 pm »

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.

In my Post 11 I mention two ways that made my Fn-key combinations work with a german keyboard.

12

Cosmo Communicator - Android / V23: eSim (and mobile network) not available anymore

« on: July 09, 2020, 07:55:59 am »

You can select the preferred sim card in settings ,network and internet , sim card,  preferred sim for data, calls and messages .

Thanks for the hint! Just tried that, but for my eSIM-only setup SIM slot 2 is activated and all other controls are disabled due to a lack of alternatives.

Fortunately I have not encountered any of those spurious restarts, that I observed with V22. So I do not have to fiddle with the eSIM in Cosmo settings too often.

13

Cosmo Communicator - Android / V23: eSim (and mobile network) not available anymore

« on: July 08, 2020, 05:19:39 am »

In cosmo settings  just enable  use esim for sim slot 2.
And the esim will be available.

Thanks for pointing me in the right direction.
Actually the switch was already enabled to use eSIM for SIM slot 2. After disabling and enabling it again the eSim-wallet will start activating the eSIM and initiate the mobile connection. Unfortunately this has to be done after every reboot. Otherwise the eSIM wallet will show the error message "Preferred SIM for Calls should be switched to SIM slot 2" and has to be started manually. This behaviour is reproducible for non-rooted and rooted PC android.

14

Cosmo Communicator - Android / V23: eSim (and mobile network) not available anymore

« on: July 07, 2020, 12:14:32 pm »

After upgrading to V23 the eSim is not being detected and as result no mobile connection (phone, mobile data) can be established.
The eSIM wallet tells me to set SIM 2 as a default. All the SIM settings under Settings -> Network & Internet -> SIM cards : are disable, so no way to change.

Sofar the eSim survived upgrades to V20, V21 and V22 without problems. I assume it still there but not detected properly.

15

Cosmo Communicator - Android / V22 is out.

« on: June 30, 2020, 04:53:25 am »

Mine,  up to now is OK. I have updated from  V19 to V22. No password defined . Everything is fine.

I came to V22 the "official" way ;-) OTA V20 -> manual upgrade to V21 -> OTA V22. I'm not decided whether this can cause the reboots.