Messages

1

Cosmo Communicator - Android / Re: [Solved] Airmail crashing after update to V25

« on: April 01, 2021, 06:14:13 pm »

Looks like the Airmail problem has been cause by the Google WebView bug:
https://www.google.com/amp/s/www.theverge.com/platform/amp/2021/3/22/22345696/google-android-apps-crashing-fix-system-webview

Probably the update came automatically so Airmail just started do work normally again.

2

Cosmo Communicator - Android / Re: [Solved] Airmail crashing after update to V25

« on: March 23, 2021, 08:38:16 am »

Starnge, without doing anything the crash suddenly does not happen anymore...

3

Cosmo Communicator - Android / [Solved] Airmail crashing after update to V25

« on: March 23, 2021, 06:51:44 am »

Hi,
after the update airmail stopped working for me. Since I have updated yesterday and I have noticed the problem today, I cannot tell for sure if this is connected to the update. Airmail crashes when displaying a mail from IMAP. I have not tried yet to clear airmail date / reinstall airmail.

Does this happen for other airmail users?

Thanks.

Mith

------------------------------------

Parts of the logcat that seem to be interesting:

...

03-23 11:26:31.173  2222  3697 D OpenSSLLib: OpensslErr:Module:12(177:); file:external/boringssl/src/crypto/asn1/asn1_lib.c ;Line:168;Function:ASN1_get_object
03-23 11:26:31.173   963  1177 D serial_port: send(fd = 0) write
03-23 11:26:31.173   963  1177 I chatty  : uid=1000(system) Thread-3 identical 22 lines
03-23 11:26:31.173   963  1177 D serial_port: send(fd = 0) write
03-23 11:26:31.173  2222  3709 D OpenSSLLib: OpensslErr:Module:12(177:); file:external/boringssl/src/crypto/asn1/asn1_lib.c ;Line:168;Function:ASN1_get_object

...

03-23 11:08:03.670  9864  9864 F crashpad: -----END CRASHPAD MINIDUMP-----
03-23 11:08:03.705  3074  3074 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 3074 (.gemini.airmail), pid 3074 (.gemini.airmail)
03-23 11:08:03.786 10010 10010 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 11:08:03.786 10010 10010 F DEBUG   : Build fingerprint: 'Planet/Cosmo_Communicator/Cosmo_Communicator:9/PPR1.180610.011/1611025365:user/release-keys'
03-23 11:08:03.786 10010 10010 F DEBUG   : Revision: '0'
03-23 11:08:03.786 10010 10010 F DEBUG   : ABI: 'arm64'
03-23 11:08:03.786 10010 10010 F DEBUG   : pid: 3074, tid: 3074, name: .gemini.airmail  >>> com.gemini.airmail <<<
03-23 11:08:03.786 10010 10010 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
03-23 11:08:03.786 10010 10010 F DEBUG   : Cause: null pointer dereference
03-23 11:08:03.786 10010 10010 F DEBUG   :     x0  0000000000000000  x1  000000751e8061ec  x2  7265646f63654400  x3  726f7463656c6553
03-23 11:08:03.786 10010 10010 F DEBUG   :     x4  0000000000000000  x5  0000000000000000  x6  716e7362646b6452  x7  7f7f7f7f7f7f7f7f
03-23 11:08:03.786 10010 10010 F DEBUG   :     x8  0101010101010101  x9  000000751e563000  x10 0000007000027488  x11 0000000000000001
03-23 11:08:03.786 10010 10010 F DEBUG   :     x12 0000000000000000  x13 0000000000000000  x14 4b3d092f234ec266  x15 cae6c696f68e9634
03-23 11:08:03.786 10010 10010 F DEBUG   :     x16 00000075228ac0f0  x17 00000075ba8df2d0  x18 0000000012d53bc8  x19 0000000000000003
03-23 11:08:03.786 10010 10010 F DEBUG   :     x20 0000000000000000  x21 000000700001fe00  x22 0000007ff00acf38  x23 0000007000027488
03-23 11:08:03.786 10010 10010 F DEBUG   :     x24 0000007000027498  x25 0000000000000000  x26 0000007ff00ad1d0  x27 0000000000000000
03-23 11:08:03.786 10010 10010 F DEBUG   :     x28 00000070000b8270  x29 0000007ff00ace90
03-23 11:08:03.786 10010 10010 F DEBUG   :     sp  0000007ff00ace60  lr  00000075218379dc  pc  00000075218379dc
03-23 11:08:03.787 10010 10010 F DEBUG   :
03-23 11:08:03.787 10010 10010 F DEBUG   : backtrace:
03-23 11:08:03.787 10010 10010 F DEBUG   :     #00 pc 00000000034529dc  /data/app/com.android.chrome-xlQJt7_dlyyNeGDpiKwopg==/base.apk (offset 0xa0f000)
--------- beginning of system

4

Cosmo Communicator - Android / Re: New firmware How to set the default booting partition ?

« on: March 23, 2021, 06:41:41 am »

Hi,
in the boot menu navigate to the desired boot menu entry using Vol+/Vol-. Vol+/Vol- has to be pressed at least once. Then use Cursor left/right to select whether to retain or set the default entry. You can see the change in the Default line below the boot menu. Then use Enter or Esc to confirm the selection.

This howto should have been part of PCs update. Anyways, I am glad we can eventually set the default boot menu entry.

Mith

Posted by Planet Computers

Cosmo Communicator News - March '21
Dear Cosmo backers!
The long awaited Android firmware update for Cosmo is now available. This is the v25 version.
This version includes:

Bootloader improvements - you can now set the default booting partition

But how to do this ?
There is a menu with boot options, but I cannot navigate to the option to select and set the default boot partition. What keys I have to press  to select the default boot partition? Thanks.
Thanks .

5

Cosmo Communicator - Android / Airmail 1st/2nd class folder selection

« on: March 11, 2021, 08:59:33 am »

For enabling disabling notifications for imap folders I need to distinguish between 1st and 2nd class folders in airmail. I can enable/disable notifications for folder classes, but I have not found an option to set which folder is 1st class (in german: Hauptordner ) and which folder is 2nd class (in gerrman: Nebenordner) in Airmail.

Anybody knows?
Thanks.

6

Cosmo Communicator - Android / Re: Airmail Imap folder abonnement

« on: March 11, 2021, 08:55:28 am »

In the meanwhile I have found out that the folder list gets refreshed when I enter the incoming server settings and then selecting next. So, this problem is solved now.

7

Cosmo Communicator - Android / [Solved] Airmail Imap folder abonnement

« on: March 05, 2021, 04:19:00 pm »

I have just added some Imap folders with thunderbird. Does anybody know how to refresh the folder list with airmail? With K9 mail I remember a menu item refresh folders, but I cannot find this with airmail.
Tanks!

8

Cosmo Communicator - Linux / Potential Future Debian on Phones Distro?

« on: July 10, 2020, 02:20:35 pm »

Hey, maybe there's another potential option for Debian on our phones......

Work in progress....but it's designed to run on phones.....

https://liliputing.com/2020/07/mobian-is-a-...-on-debian.html

Really depends on getting all hardware features working in Debian with the MTK chipset. I don't know what the status of the Cosmo is, but I never managed to get GPS working on the Gemini. The fingerprint sensor might also be a problem.

Otherwise this looks really nice.

9

Cosmo Communicator - Android / Skype incoming calls/messages

« on: July 08, 2020, 03:12:53 pm »

My Cosmo does not ring or show incoming messages when Skype is not the active app running in the foreground. As soon as I return do desktop or have another app in foreground I do not catch incoming Skype calls.

I already have checked all notification settings I can find and also disabled battery optimization and gave overlay permission.

Does Skype work properly for anyone else on the Cosmo?
Anything else I can try?

Thx. Mith

10

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 04, 2020, 06:49:11 am »

Great idea! But I've never done that before. How do I do that?

Magisk Modules are installed in /data/adb/modules/[modulename]. Some modules have a service.sh script there which gets executed on startup. Just install a magisk module and add the two lines to the service.sh file afterwards. (requires root) Since I have installed my exfat module anyways (and it has a service.sh file) I just have added the lines there. (If you want to use the module for this,  it can be found on mygnu.de)

I also replaced the default boot image with a magisk image (@see: https://www.oesf.org/forum/index.php?showtopic=35879) so it boots into rooted android by default (so the script gets executed). Anyways it seems, with the newly rooted boot image, the cosmo is far more stable than with planets rooting method. I have not seen a spontaneous reboot since then. Maybe the official kernel image is outdated and does not contain the kernel modifications for V22.

11

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 03, 2020, 08:48:54 am »

Sadly, it didn't survive a reboot and I had to reboot about 8 times before it booted up again so that I could run the commands again. Planet better be fixing this with V23, 'cause this way, it's getting hard to use my Cosmo...

I have just added the two comands

settings put global device_provisioned 1
settings put secure user_setup_complete 1

to a service.sh file of a magisk module, so the commands should get run on every startup (when booting rooted). I am curious to see if the issue happens again with that. Maybe this also is an option for you.

12

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 01, 2020, 08:03:47 pm »

See? I knew I couldn't be the only one with this issue! I reported it a few days ago in the V22 is out thread.

But I can't use your solution  ADB won't recognize my phone as Developer Options are inaccessible due to this bug, meaning I can't enable USB Debugging for ADB. And I can't access a root shell either since the Play Store won't install apps anymore, APK's won't install anymore either and Planet's TWRP still isn't working. Do you have any suggestion as to how I can get a root shell?

Someone managed using adb by "brute force":
https://forum.xda-developers.com/showpost.p...;postcount=2706
Unfortunately he did not mention the Android version used. Maybe this is also possible on the Cosmo.

You could also try to install the rooted image from sd card as described by Planet Computers: http://support.planetcom.co.uk/index.php/Linux_for_Cosmo
Afterwards install termux from apk (since Play store does not work): https://f-droid.org/packages/com.termux/ and use the settings commands from above.

13

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 01, 2020, 10:50:20 am »

After one of the random reboots with V22,  today this happened again. Maybe switching between rooted/non rooted due to reboot is connected? Solution worked, as before.

14

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: June 25, 2020, 05:26:36 pm »

Two days after upgrading from V19 to V22 my Cosmo suddenly started to behave strange. Most functionality of the taskbar has been missing. The home screen suddenly only had one page. Taks switching became impossible.

The reason has been, that due to a bug in/after OTA update the device has been struck in initial setup mode, where most functions are locked.

This can be solved by running the following commands in a root shell or with adb:
settings put global device_provisioned 1
settings put secure user_setup_complete 1

Initially I thought I had to perform a factory reset, but  then I found the issue on: https://www.xda-developers.com/broken-navig...ota-update/amp/

Mith

15

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator

« on: June 22, 2020, 05:02:23 pm »

Anyone already has V22 stock and magisk boot images? Is there an easy way to extract the stock boot image on the unrooted device? I started with spflash tool, but I am unsure about the partition addresses since my scatter file does not match anymore because of reserving space for Linux.

Thanks!