Messages

1

Cosmo Communicator - General Discussion / Cosmo for sale, DE QWERTZ with EU plug

« on: April 10, 2020, 03:44:30 am »

Here are some photos and screenshots to show the current state of the device and prove it's working fine:
https://photos.app.goo.gl/HborbJ3k2nAnJMGr9

2

Cosmo Communicator - General Discussion / Cosmo for sale, DE QWERTZ with EU plug

« on: April 10, 2020, 03:39:16 am »

I’m selling my used Cosmo with German QWERTZ keyboard in original packaging with all accessories (EU plug). As a backer of the IGG campaign I paid US$619 which corresponded to 564€. I’d like to add the fitting felt pouch from https://www.flat-design.eu/ for 20€.

Unfortunately, I do not find the keyboard as good as expected, mainly because of the missing dedicated umlaut keys. Also, to be frank, I'm very worried by PC's update strategy and current SW support of the device.

I received the device on 27th Dec, but couldn’t use it on the go before February when I finally received the missing SIM tray.

Device is in very good condition, only a minor scratch on the bottom due to salt. I have added rubber bumps to avoid since then. Both display protector foils are still on. Everything works hardware-wise, in particular battery life, both USB ports, and CODI communication with main system. Signal reception of mobile com and WiFi seems very good to me. Couldn’t test eSIM, though, due to SW errors. Device battery was never completely exhausted and mostly slow charged. Device is at latest hotfix FW and partitioned 50:50 for dual boot with Debian derivative.

I’m asking for 585€ plus shipping.

3

Cosmo Communicator - Android / eSIM wallet crashes after QR code scan

« on: January 08, 2020, 08:57:28 am »

Further information:
I've added the eSIM GSMA Root CI Certificate (from https://www.gsma.com/esim/certificate-issuer/) to the Trusted CA Certificates of the Cosmo by converting to CRT using openssl and install from SD-card:

Code: [Select]

openssl x509 -inform PEM -outform DER -in CA.pem -out CA.crtThis did not help at all, eSIM wallet still crashes.

4

Cosmo Communicator - Android / Odd Behavior Thread

« on: January 06, 2020, 02:48:52 pm »

Thanks all for this thread, I hope Planet Computers will take the time to read it.
Mostly, I agree with PJS' observations (https://www.oesf.org/forum/index.php?showtopic=35915&view=findpost&p=293794):

• Notes App (pre-installed): Ctrl+left/right changes font size instead of wordwise cursor movement
• Cosmo keyboard: longpress character map should be customizable for more fluid umlaut typing (i.e. characters should be rearrangeable, and a default should be set)
• CODI: opening notifcation and then opening the device clamshell should also open corresponding app
• keyboard backlight should turn off when main display turns off (has been reported already)

5

Cosmo Communicator - Android / eSIM wallet crashes after QR code scan

« on: January 06, 2020, 02:40:10 pm »

OK, I've now received two answers regarding eSIM support for the Cosmo Communicator, one from Sipgate regarding their simquadrat/esim service, and one from Congstar, the low budget subsidiary of Telekom in Germany. Not so good answers, actually, which questions the entire eSIM thing:
Congstar only offer the eSIM for a handful of high quantity devices (basically only iPhones, iPads and Google's Pixel 3 and 4).

Hallo,
wir können aktuell leider nur für folgende Geräte eine eSIM anbieten:
Apple Geräte-Generation:
• iPhone 11, iPhone 11 pro und 11 pro max
• iPhone XS, iPhone XS Max und iPhone XR
• iPad Pro 2018 (11 und 12,9 Zoll)
• generell ab iOS 13 noch einmal komfortabler als zuvor
Geräte-Generation mit Android:
• Google Pixel 3 und Pixel 3 XL
• Google Pixel 3a und 3a XL
• Google Pixel 4 und 4 XL
Ich bitte um Ihr Verständnis.
Freundliche Grüße
Renate von congstar

As expected, Sipgate respond on a higher technical and satisfactory level:

Hallo,
vielen Dank für Ihre Nachricht.
Das Gerät gehört nicht zu den von uns supporteten Geräten.
Wir hatten allerdings einen Kunden, der ein ähnliches Gerät hatte mit einem ähnlichen Fehlerbild.
Dieser Kunde hat eine für ihn funktionierende Lösung gefunden - wir übernehmen aber weder Garantie noch Support, dies ist nur ein Hinweis unsererseits: Dafür musste er unter https://www.gsma.com/esim/certificate-issuer/ die beiden Zertifikate runterladen und in .crt Dateien umbenennen. Dann installieren.
Wie der Kunde hier genau vorgegangen ist wurde uns leider nicht mitgeteilt.
Viele Grüße
Sven

So, it seems we also have to deal with missing certificates. They suggest to download the GSMA root certificates and convert them to CRT and "install" them.
In case anyone know what to do here and how, I'd be happy to read up on it!

6

Cosmo Communicator - Android / eSIM wallet crashes after QR code scan

« on: January 04, 2020, 02:40:31 am »

I had to disable TLS certificate checks.  It seems that the wallet is missing a number of root certificates in its trust store.

.
I've seen this, but unfortunately, this is no already default in the eSIM wallet settings. Enabling or disabling it has no effect. Also, disabling and re-enabling eSIM in Cosmo settings also does not improve things.

7

Cosmo Communicator - Android / eSIM wallet crashes after QR code scan

« on: December 31, 2019, 04:23:12 am »

Hello,
since my Cosmo (ROW version) has been delivered without SIM tray, I've been trying to install an eSIM profile, but without success.

My German everyday carrier Congstar has recently added eSIM support, but this is a one-way SIM>eSIM, because the physical SIM will be deactived immediately. So I'm reluctant to do the switch, and rather I've experimeted with simquadrat. They offer a basic prepaid plan with no initial cost for account setup and identity authentication: https://www.simquadrat.de/

I've setup an account there and tried to scan the QR code or enter the data manually in the Cosmo's eSIM wallet app, but it keeps crashing right after.

In another thread (https://www.oesf.org/forum/index.php?showtopic=35933) it has been indicated, that one must disable eSIM for slot 2 in Cosmo settings and re-enable it for the wallet to function properly, but this didn't help either.

I'm willing to provide more detailed errors, but I don't know where to start. Any help is appreciated.