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.

Topics - cam1965

Pages: [1] 2 3 4
Cosmo Communicator - Linux / gemian certificate expired
« on: November 14, 2021, 06:56:57 am »
cosmo@cosmocom:~$ sudo aptitude update
[sudo] password for cosmo:
Hit buster InRelease
Ign buster InRelease                                       
Err buster Release                                       
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 443]
Hit buster InRelease
E: The repository ' buster Release' no longer has a Release file.
E: Failed to download some files
W: Failed to fetch Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Please help !
Thank you.

Libreoffice is only  installed with ssh.
Please see :

After enabling ssh, I have installed the container with libertine and then libreoffice.
You need to restart ubuntu touch after all.
But libreoffice  is too small to read.
I will attach photos.
Good luck !


After a long time without using gemini, I decided to reinstall linux on it.
But dialer-app is not working. No sound on voice calls. It rings and I can answer a call with the silver button. But only this. No sound on conversations.
I remember in the past ( DEBIAN TP first version ) it was working.
I think the problem is /data/system.img.
I have downloaded the previous first version and extracted the system.img  to /data/
So as described in the old wiki ( not available now ).
But from memory:
sudo apt-get install xdelta3
xdelta3 -d -s /data/system.img system.img
sudo cp system.img /data/system.img

The problem is that the file from wget is wrong or it is not working correctly.
The system.img from first version seems to be correct
So I can't do this test.
Please if someone has this file , let me know.
When I did the command  xdelta3 -d -s /data/system.img system.img I got an error
xelta3: not a VCDIFF input : XD3_INVALID_INPUT

Thank you.


I saw this :

So I downloaded the firmware image  of KALI linux ( from  Planet site ) and discovered that the md5sum of the correct system.img is the same of the link above  ( New md5 output after update: 1b6f07d345cbb9fadca562e788375515 ).

So I have extracted  and mounted linux.img .
First  I made a backup of system.img . ( cp /data/system.img to somewhere )
Then I removed the system.img from /data.
I copied the system.img (from kali ) to /data.
I did a Reboot.
But the phone didn´t work and neither the camera-app.
So, I copied the backup of  system.img to /data ( overwriting the system.img from kali ).
I rebooted linux again.
And for my surprise the phone was working . The camera-app too ( of course ).
I really don´t know. Maybe when booting with  kali system.img in /data some configuration was changed in debian.
The most important is that now everything is working.

Gemini PDA - Linux / Ubuntu Touch on gemini
« on: June 14, 2021, 02:47:10 pm »
Just for curiosity. Has anyone installed Ubuntu Touch on gemini? And if so, Id like to know if it is better than   debian ( from Planet ). My gemini is not in use. It is left in my wardrobe with Android only for a long time. I am using Cosmo. Thanks.

Cosmo Communicator - Linux / USB charging problems
« on: June 14, 2021, 02:32:11 pm »
In linux and in android  when using a peripheral at the left usb port I  can´t charge at the right usb port . ( The peripheral  connected at left USB port disables the right USB port charging ).
And in linux  the right USB port only works for charging.
In linux , If you connect  a peripheral at the right USB port  it doesn't  work.
In android it works for peripherals in both USB ports. ( with codi enabled ).
And in android you can use the peripheral in the right usb port ( codi enabled )  and charge the cosmo in the left usb port at the same time.
This is confimed by me and by jakfish.
Any Ideas ?
Thank you.

Hi .
I have compiled 2 kernels.
Differences are below

When apparmor is the default security the kernel doesn't  boot correctly. It  hangs  at the debian logo image.
With  selinux as a default  security everything is OK.

Why ?
Any ideas ?
Thank you.

Sorry for posting here.
I tried to insert pictures here, but received this message below:

An Error Has Occurred!
The attachments upload directory is not writable. Your attachment or avatar cannot be saved.
Please help me.
Thank you.

Cosmo Communicator - Linux / How to pass a cmd line to kernel ?
« on: June 10, 2021, 08:52:44 pm »
How to pass a comand line to kernel ?
I would like to pass apparmor=1 security=apparmor to my kernel.
For example :

mkbootimg --kernel cosmo/arch/arm64/boot/Image.gz-dtb --ramdisk initramfs-4.4.146 --base 0x40078000 --second_offset 0x00e88000 --cmdline "bootopt=64S3,32N2,64N2 log_buf_len=4M" --kernel_offset 0x00008000 --ramdisk_offset 0x14f88000 --tags_offset 0x13f88000 --pagesize 2048 -o linux-boot.img.

I have tried to put something like this  --cmdline  "bootopt=64S3,32N2,64N2 log_buf_len=4M" apparmor=1 security=apparmor.
But the kernel didn´t boot correctly.
Any help ?

Is there a way to enable the USB port on the right side ?
In android it works if CODI is enabled.
Thank you.

Hi Shuntcap.
Thank you for post these instructions : Topic below

I followed your guide. Except that I didn't build an android image.

But when I did systemctl --global enable anbox-session-manager the error below occurs.
cosmo@cosmocom:~$ systemctl --global enable anbox-session-manager
/usr/lib/systemd/user/anbox-session-manager.service:1: Missing '='.
Failed to enable unit, file anbox-session-manager.service: Invalid argument.

So I did an script like below and it is working.

cosmo@cosmocom:~$ more
sudo systemctl start  anbox-container-manager
systemctl --user start anbox-session-manager
LD_LIBRARY_PATH=/opt/gl4es/lib anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

To test if the network was working I had to install a text browser and It works ( TJ text browser ).
With firefocus ( also firefox )  and other browsers the screen is black.
Also with the pre loaded email software it only loads the messages and I cannot open them. Also witth k-9 mail program. Same behaviour.

Only to know if these errors are happening with you.
Maybe the problem is with the android image. ( I don´t think it is the image, plaease see my note below )
I really would like to know if there is a possibility to install playstore inside the image you have provided.
This will help to install some apps that need google plays ervices and other dependencies.
Thank you so much.
 Note : tested with

Same behaviour with the android image above.

First I installed a fresh v4 firmware.
Then I mounted the v3 image file ( gemian-cosmocom-kde-plasma.img ).
And  copied  the folder droid-hybris from the the v3 image ( /usr/libexec/droid-hybris ) to the v4.( same place  /usr/libexec )
I did a reboot.
Please, do not upgrade the system for now.
You have to hold ( apt-mark hold )  codi-app and lxc-android.
Now you can upgrade.
Incoming calls and outgoing calls are working pretty well.

Unfortunately messaging-app is still with the same problem : only outgoing messages are working.

But I think it is a light to Adam Boardman to solve these problems.
Good Luck .

ALT key is not working in v4. ALT + TAB  and every shortut that uses ALT key are not working.
Any sugestions ?

When  repository will be available to V3 ?
I still have v3 in my cosmo.
I prefer incoming calls ( working in v3 and not in v4 ) than camera ( working in v4 and not in v3 ).
Bluetooth as I know doesn't work in v3 and has lotof problems in v4.
So, is there a possibility to camera and bluetooth work in v3 ?
Also again when does the repository will be available to V3 upgrade ?
Thank you all.

Could not update cosmo. Problem with repository.
Err:1 buster InRelease
  Could not resolve ''
Hit:2 buster InRelease                                                 
Hit:3 buster InRelease                                       
Reading package lists... Done
W: Failed to fetch  Could not resolve ''
W: Some index files failed to download. They have been ignored, or old ones used instead.

Thank you all.

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 .

Pages: [1] 2 3 4