Messages

1

Cosmo Communicator - Android / Re: Signature spoofing

« on: May 31, 2022, 04:31:02 am »

I was not aware of a LineageOS port for Cosmo. Is this the fork you are referring to? https://github.com/PCLineageOS-Ports/cosmo-lk

2

Cosmo Communicator - Android / Signature spoofing

« on: May 28, 2022, 11:58:00 am »

Thanks to Shiunbird1's guide (https://www.oesf.org/forum/index.php?topic=36736.0), I almost managed to get an google-less Android system on my Cosmo. However, as I described in my answer to that thread, my setup created through the guide still lacks Signature Spoofing. I found out by the help of the "Signature Spoofing Checker App" (https://f-droid.org/packages/lanchon.sigspoof.checker).
As long as the Signature Spoofing feature is disabled, some apps like WhatsApp won't function properly.
I tried various solutions to enable signature spoofing, such as Needle (https://github.com/souramoo/Needle) and the EdXposed module (https://github.com/thermatk/FakeGApps), none worked.
Does someone have an idea how to approach this problem?

 

3

Cosmo Communicator - General Discussion / Almost successfully did it, but perhaps still a problem with signature spoofing

« on: March 05, 2022, 05:01:51 am »

With the help of your instructions I almost managed to degoogle my cosmo.
I just needed to figure out that in order to update magisk you need to manually patch the root-boot.img as described here: https://www.oesf.org/forum/index.php?topic=36528.
I installed microG-Revived inside Magisk (https://github.com/nift4/microg_installer_revived), but I didn't find any F-Droid extensions for Magisk. Moreover, I could not do steps 17 and 18, as I couldn't locate the MicroG settings. Nonetheless, almost everything works, only some apps complain about missing Google Play Services (WhatsApp and MILES). I ran the Signature Spoofing Checker app, which says signature spoofing is not enabled. I guess this is the reason. Is it because of the skipped steps 12, 17 and 18?

4

Cosmo Communicator - Hardware / Re: Rooting the Cosmo Communicator

« on: January 31, 2022, 03:59:00 am »

I've just stopped following this topic since I've been using the official planet procedure for rooting and I suggest everybody to do the same.

Does this mean that the problem with the version of Rooted Android provided by Planet that does not recognise the SIM card has been fixed? As I understand it, the status quo is still that you have to manually root the system for SIM card recognition to work.             

5

Cosmo Communicator - Linux / Successfully created a script to control battery charging behaviour

« on: January 31, 2022, 03:54:47 am »

In case that someone wants to limit the charging threshold in Linux (to reduce battery wear), I'd like to post my solution how I did it. In Android, I use the AccA app (https://f-droid.org/en/packages/mattecarra.accapp/) to control the charging behaviour.

To do this with Gemian on cosmo, I wrote this simple script:

Code: [Select]

#!/bin/sh

threshold=70 # stop charging at this percentage threshold

p="$(upower -d|grep -m1 percentage|cut -d: -f2 | tr -d "%")"

if [ "$p" -gt "$threshold" ] ; then
  echo "0 1" > /proc/mtk_battery_cmd/current_cmd
else
  echo "0 0" > /proc/mtk_battery_cmd/current_cmd
fi

When called by cron (root user), the script periodically checks (via upower) whether the battery percentage is higher or lower than the specified threshold, stops charging in the first case and starts charging in the latter. When the charger is plugged off, the device goes into discharging mode as usual and returns into the custom charge mode when the charger is plugged in again.

There is one uncertainty though, I do not know if the cosmo is truly energized directly by the charging cable if charging is paused. In AccA, you can manually enable this option, otherwise the current still takes the detour through the battery. But on the cosmo the app says that the Android kernel is not compiled for this direct power supplying.

6

Cosmo Communicator - Linux / Disabling the password prompt when a call is received and the cosmo is in fold

« on: December 07, 2021, 03:13:47 pm »

Dear community,

I got my cosmo today and I'm very pleased to see that Gemian is amazingly good working. Thanks to the users contributing to the thread https://www.oesf.org/forum/index.php?topic=36554 I can now receive calls, even if the cosmo's lid is closed and the OS is in standby. But when I receive a call in standby, I have to enter my password first to answer the call, which is quite annoying. I ran the command `kcmshell5 screenlocker` and unchecked the box "lock screen after suspend". But this doesn't have any effect, even if the command is run as root and doing a reboot after. Does someone have an idea for a solution to either
  A) disable the lock screen prompt when a phone call is received, or
  B) make the lock screen prompt easier (a 3 digit code for instance which is not the Linux user password), or
  C) disable the lock screen completely if nothing else is possible?

Thank you

Fabio