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.

Messages - gabs5807

Pages: 1 [2] 3
Cosmo Communicator - Linux / Wrong keyboard mapping on login?
« on: November 07, 2020, 05:19:05 pm »
i changed my keyboard mapping as described on the planet cosmo linux page to german.
Then i changed the password of the new user using some special charactes as '-' and '_'.

Login did not work :(. It seems, that the keyboard uses standard (english) keymapping :-\.
Any one else have the same experience?

I used a .sh script in the Planet recovery/bootloader thing to flash the hybris-boot.img (modified from the Debian one), and have tried both the zip and the newer 3.4 one on the CI, both fail to go any further than the Planet logo boot splash! Curious to know if anyone's gotten either image working, I'd really love to try Sailfish on the Cosmo :)

EDIT: Attached my here as requested in the Telegram channel
I copy your script to my planet 'cosmo custom installer' sdcard and added it to the './cosmo-customos-installer/'.
Now i can flash the hybris-boot.img to the last 'empty' boot slot via the 'cosmo custom installer' sdcard (similar as described at planets debian installer instruction)  ;D.

But this is only for flashing the boot img, so the system from the tar archiv must be extracted on the running debian system  ::).

The contains an 'extract' script which shows that the content of the tar file should go to '/data/stowaways/sailfishos/' directory (FS_DST="/data/.stowaways/sailfishos" and tar use the option '--numeric-owner').

But this also did not work on my cosmo. Selecting SAILFISH_OS the system shows the planet logo and the blue led is on, but did not continue booting  :-\.

So sorry - no :( no tests are possible so far ...

I was corresponding with Davide Guidi, Planet Computers' CTO, about Sailfish. He has sent me the following link to download a preview of Sailfish for Cosmo, and encouraged me to make it available to interested parties. Note he mentions that screen rotation is broken %u2014 but I hope maybe people more technical than me might be able to fix this relatively easily?

Along with the recent announcement about making the CoDi work with Linux, I hope this might be welcome positive news for other enthusiasts for a google-free Cosmo!
All the best,

You can find the sailfish image for cosmo here:

Installation is a bit tricky, You need first to install Debian Linux as for

After that you have to:

- untar sailfishos-cosmocom-release- into the Debian file system itself, in a folder called ".stowaways/sailfishos%u201D in the root folder. Basically it should be in /.stowaways

- flash hybris-boot.img in an empty boot partition, such as EMPTY_NORMAL_BOOT_4, for example dd if=hybris-boot.img of=/dev/disk/by-partlabel/EMPTY_NORMAL_BOOT_4 bs=1M

That should be it, you should now be able to boot to Sailfish by selecting EMPTY_NORMAL_BOOT_4 at boot time.
This should be all, but let me know if you run into troubles.

As far as I remember, it might take a couple of reboot to finally boot Sailfish correctly. Also, keep in mind that it%u2019s an early release, in particular screen rotation is broken.

The project is open source, feel free to forward the link to anybody that might be interested!

Kind regards,

Hello, it did not work for me on my cosmo :(.
This is what i have done as root on my installed debian:

Code: [Select]
root@cc:~ # mkdir -p /.stowaways/sailfishos
root@cc:~ # cd /.stowaways
root@cc:/.stowaways # wget
root@cc:/.stowaways # unzip
root@cc:/.stowaways # cd sailfishos
root@cc:/.stowaways/sailfishos # tar xvjf ../sailfishos-cosmocom-release-
root@cc:/.stowaways/sailfishos # ..
root@cc:/.stowaways # dd if=hybris-boot.img of=/dev/disk/by-partlabel/EMPTY_NORMAL_BOOT_4 bs=1M
root@cc:/.stowaways #

On the next boot i select the EMPTY_NORMAL_BOOT_4 entry.
The Planet logo is shown a few seconds then the cosom did a reboot.
The blue LED  above Tab did not light during this phase.
The screen did flash a short time but always stay black, also after startup ???.
Only on Codi i see the bootup (and i can do a reboot on Codi).
So i think Android is up and running(?)  :-\.

I tried booting from EMPTY_NORMAL_BOOT_4 several (ten or more) times, but the result is always the same.
Booting debian and Andriod works as expected .

many thanks for any hint  ;D.


What is the command to install  the phone app?

 When I ran the latest fireware update neither the messaging app or phone app installed. I  have install the messaging app from the command above.

Anyone know the phone app install command?

During installing messaging-app again apparmor is removed.
So it seems there is an other dependency problem  ???.

But may be we don't need apparmor(?).

installing libreoffice will remove messaging-app  ???.
I cannot find what dependency the conflict raise.
Is this a problem of different library versions?

It would be nice if both could be installed :-* thanks.

Quote from: ehasbrouck
(This relates to both Linux and Android, so I am posting it here in  the general forum)

I receoived the following message today from Planetcom support:

Linux on the Gemini still remains as a Developer Preview release, which is by no means recommended to be used as the main OS on the device. We advise using Linux for experimental and development reasons only. The main OS on the Gemini will remain Android, as the ARM/Mediatek chipset is best designed for use with Android.

There is no way to enable cellular data on Linux, and this will likely remain the case due to the "openness of Linux". Linux with an unlocked cellular modem could allow some potentially illegal actions to be easily executed. Hence, standard Linux (not talking about modified Linux for smartphones such as Ubuntu, Sailfish) does not, to this minute, have workable cellular modems in any device with such a vanilla form of Linux.

While this is unconfirmed, we know our developers are focusing some of their resources onto LineageOS for both the Cosmo and the Gemini. It is, however, important for us to focus primarily on Android, as no mobile phone manufacturer, regardless of scale, can risk their entire business by getting unlicensed by Google.

The refereences in this message to "Android" appear to refer not to Android but to a bundle of Android with proprietary Google-ware.

The statements about Google licensing are disingenuous, since Google itself says that proprietary Google apps are independent of Android and that "Android will remain free and open source..... Going forward, Android partners wishing to distribute Google apps may also build non-compatible, or forked, smartphones and tablets for the European Economic Area (EEA)."

So distributing LineageOS or any other Android distribution not bundled with Google-ware, even if it were the primary Gemini OS rather than one of several options, would not (and, under EU law and Google licensing terms, could not) provide grounds for termination of licensing of Google-ware for those Gemini users who want it, or for other Planetcom devices.

The Gemini was advertised to Indiegogo backers, and is still being advertised to prospective purchasers, as a dual-boot Android/Linux device, with no mention of limited functionality in Linux or of basic Android functionality (such as calling, SMS, and mobile data) available only if proprietary Google-ware is also installed.

Strange information  . Why did SailfishOS (community port and 'official' Jolla version run on gemini PDA?
Both are linux and have access to cellular data   . Or what means '... no way to enable cellular data ...'?

At the moment i did not have a SIM Card at my Gemini PDA, so i cannot verify that 'enable mobile data transfer' did work on the latest version.
But i remember that on earlier SailfishX versions it did work ...

On Cosmo forum i read, linux have access to phone and SMS (no mobile data transfer until now).

Gemini PDA - Sailfish OS / New Sailfish OS
« on: June 19, 2020, 02:13:56 pm »
Quote from: tpp
Does it support device encryption on Gemini? Did they fix inability to answer call with side button?

How secure is Sailfish on Gemini PDA, compared to ancient Android? Does it actually bring any improvement to security in terms of addressing vulnerabilities, or is it pretty much the same as Android due to ancient kernel?

@tpp: Take a look to TJC
As i know only on the 'official' Jolla SailfishX /home partition encryption (no full device encryption) is possible   .

The community port did not have a own partition for /home, so encryption is not possible on the port.

I don't know who is responsible for this part on SailfishX   .

It seems that Jolla pay less attention to the Gemini PDA.

Cosmo Communicator - Linux / GSM-calls?
« on: June 13, 2020, 10:54:03 am »
Quote from: cam1965
Quote from: suhrm
Quote from: LinuxGuy
Hi to all

Quote from: mibry
From the telegram group, Cosmo is missing a ofono plugin. So Wont work for now. Hopefully soon.
Well, installed Dialer app, but right, " no network" error. Setting up a broadband-connection in the networkmanager application didnt help either ... any new idea?
Thanks for your advice!

After reading up on android cellular stuff (apparently not the same as interfacing with standalone modems) as well as the reply from milbry I managed to find and configure the modem using good old fashioned AT command through  /dev/radio interfaces and even sending and SMS. Now I am trying to see if I can get it working through ofono, however my experience with ofono, Android RIL  etc. is limited.

Are you using v20 or v21 firmware,  right ?
In v19, I can't see my sim card.
Is it possible to update firmware on 'debian only' cosmo?
I installed a 'debian only' with the first released sdcard image and i think the firmware was v19 at this time.
So i need to update the firmware from debian (if possible).
Otherwise i have to repartition the device an this delete the debian as well    .
Btw.: is there a newer image with a updated debian and firmware?

Hello oida,
my cosmo is broken  . Now i read here that it is possible to reflash it   .
Can you please tell me where i can get these SP flash tool?
And can i use the bin files from planets latest firmware page?

Many thanks


Quote from: oida
Why not just extracting the boot image with SP flash tool, modify it with magisk and reflash it with flash tool? That usually works like a charm on Mediatek devices, no unlocking bootloader, no recovery required. I have not tried it with the cosmo yet though.

Cosmo Communicator - General Discussion / Firmware update
« on: January 27, 2020, 05:51:01 pm »
after trying a manually firmware update (described at Planet WebSide my cosmo is dead   .
I search for a new Firmware via cosmo update process but the 'searching ..' window did not end.
So i try to download the two bin files via the cosmo browser, but when the first bin file was downloaded the cosmo tries to install it immediately.

The cosmo then starts a reboot with out success and now it is not possible to start the cosmo.
After poweron there is a short vibration and nothing else.

Is it possible to flush the bin files via computer to the cosmo?
And how can i do this?

Many thanks


Cosmo Communicator - Linux / Linux community?
« on: January 27, 2020, 12:50:17 pm »
Quote from: g.husson
Personally I don't care about a phone like UI. I bought the cosmo in order to have a laptop UI :-)
What would be great for me to work with cosmo under Debian :
- LXDE/Cinnamon or equivalent
- 4G/3G modem
- bluetooth
- all the other things would be here with Debian distro
- and as an exception : an app with a phone UI for calling (in order to use my fingers on the screen) and eventually using external speakers and make call fusion + call management via CODI
I am a network and system engineer. I would be happy to help :-)
PS : I was a N900 user and I loved this phone with debian chroot. But if I had to choose, I would prefer laptop UI rather than phone UI on a phone with a physical keyboard that you have to deploy anyway :-)

It should be possible to switch between the phone UI and the laptop UI with a hotkey (same as switching between ttys).
So the phone UI could be similar to e.g. Sailfish UI (using wayland) and an native X11 UI   .

Best regards

Quote from: ArchiMark
Think this just means that Jolla does not want to be the messenger now for Planet Computers.

Given the relationship that Planet Computers established with Jolla regarding the Gemini, I would think they have had conversations about the Cosmo.

It may be that they don't want to discuss it publicly until they have a more definite date for releasing Sailfish for Cosmo.

I would not read more into the statement than this.


I hope you are right.
At this mer-meeting the answer from Jolla - James Noori (Jaymzz) was:

08:18:15 <Jaymzz> #topic Planet Cosmo Communicator (5 min – asked by  VWrestle)#info How are Developments going for the new Cosmo?
08:18:31 <ExTechOp> #info Otto Mäkelä, community
08:18:32 <Jaymzz> #info How are Developments going for the new Cosmo?
08:18:47 <Jaymzz> The answer simply is
08:18:58 <Jaymzz> #info We have not announced official Sailfish support for Cosmo
08:19:56 <Jaymzz> I guess we can move on from this one as well

So i'm not shure  

Best regards Gabriel

Gemini PDA - Linux / Final call for TP3
« on: December 27, 2019, 07:03:51 am »
Quote from: mithrandir
I think there has been no kernel upgrade with Android 8. Still having the Android version before here (using Linux only with the Gemini).
Can anyone confirm that with Android 8 there still is the 3.18 kernel. (from settings or running 'uname -a' in termux root shell)?
You are right. At the git there is only a 3.18 kernel ..

At the Jolla Blog i read the following conversation:

ghling   on November 20, 2019 at 8:29 am

Any news on the Cosmo Communicator support? With the device finally being in construction and the first batch already shipped to backers (me included), I wonder when we’ll see the first SFOS build for it. The fact that it is mentioned at no point in this post really concerns me.
Does the license offer for existing users apply to the Cosmo as well?
Log in to Reply   

    James Noori   on November 21, 2019 at 2:31 pm

    The special offer applies to the supported Xperia devices, as you may see in the table featured in this blog. We cannot speak on behalf of another company, therefore we encourage you to get directly in touch with Planet Computers.

This means, that Planaet should do the first step to get Sailfish on the Cosmo   .

It seems that we have a hen-egg problem here - who do the first step   ?
So what is the way to trigger the Jolla - Planet communication?

On the PDA the first step was do setup a community Port.
But i did not see any actions for the Cosmo, or did i miss something?

Best regards gabs5807

Gemini PDA - Sailfish OS / Dosbox
« on: December 23, 2019, 02:51:20 pm »
Quote from: FrankS
Quote from: idc
Assertion failure at SDL_SetWindowIconREAL (/home/abuild/rpmbuild/BUILD/SDL2-2.0.9+git3/SDL2/src/video/SDL_video.c:1772), triggered 1 time: 'window && window->magic == &_this->window_magic'

Yup, I have the same issue with SFOS and the dosbox. Looks like something in SDL lib changed.
@vader, where can I find your source code, may be a compile on my Gemini with can fix it.

Edit: May I ask again for the source code, I want to try to recomlile dosbox. Same issue with SFOS v3.2.1.19.

Yes same here.
I think recompiling is necessary on the latest Version.
V3.2.1.20 requires a new Sailfish development environment    ...

Pages: 1 [2] 3