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 - gabs5807

Pages: [1]
i will sell my rarely used Cosmo with a german keyboard - all parts working fine.

Without a good working Salfish OS (or out of the box working linux) i had no usage for the Cosmo :(.

I prefer a face-to-face handover, so someone near munich (germany) would be fine.
On the planet store the cosmo price is 599,00£ - this is 679,00€ today.
So i think 450,00€ should be fair for the cosmo in good condition and a completely filled original box ;).

If anybody is interested please send me a privat message ...


After i few months and a few updates (to SailfishOS version i have to use the device as (phone) replacement for my failed main phone.
... and i run into a problem which make the usage as phone with SailfishOS impossible  ::).
There is no audio output on the phone speaker, on the stereo laudspeaker, on a wired and on a bluetooth headset  :o.

For more information take i look here

On my also installed debian linux audio woks, so it is no hardware problem.
If someone did not have this problem it would be fine to give some information here (e.g. installed rpms, ...)

Many thanks gabs5807

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?

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.

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 - Linux / [GUIDE] HowTo to install Gemian beside SailfishOS
« on: August 26, 2019, 10:32:26 am »
here a quick HowTo to install gemian beside a licensed SailfishOS on the PDA.

I use a Scatter file from planet partitioning tool with following settings:

First: SailfishOS
Second: recovery
Third: empty (it seems, that there also is the sailfishos_boot.img flushed like at First)
Fourth: TWRP

After downloading all files from Planet and Jolly i modified the content of the .../etc/sysconfig/init from the ramdisk on the sailfishos_boot.img:
Code: [Select]
# Common settings for normal and recovery init.

# Amount of space to keep unallocated for refilling root or home later on.

# Default size for root LV

Then i rebuild the ramdisk and the sailfishos_boot.img.
After installation there is 20G free space on the sailfish LVM.

On SailfishOS i create a new logical volume named gemian on the free space:
Code: [Select]
lvcreate -v -ay -Ay -l 100%FREE -n gemian sailfish
Next i extracted the latest linux-boot-lvm-stretch.img and gemian-stretch.img.xz from Adam Boardman (see the thread Final call for TP3) many thanks to Adam.
Code: [Select]
xzcat gemian-stretch.img.xz | dd of=/dev/sailfish/gemian bs=1024k
dd if linux-boot-lvm-gemian.img of=/dev/disk/by-partlabel/boot2 bs=1024k # 1)
And expand the filesystem on /dev/sailfish/gemian
Code: [Select]
e2fsck -f /dev/mapper/sailfish-gemian
fsadm resize /dev/sailfish/gemian

Then reboot the PDA using the silver Button to the installed system.

1) It should also be possible to change the filename at boot2 from sailfishos_boot.img to linux-boot-lvm-gemian.img at the Scatter file,
then it should be not necessary to write the stretch boot image on SailfishOS to /dev/disk/by-partlabel/boot2.

Many thanks to all who make this possible  


i updated my Debian 9 to Debian 10 (buster).
Now the Linux Flash Tool did not work anymore  .
I also tried it on a new installation.
The PDA is detected, but readback or flush did not work.
The error is:
Code: [Select]
Then i tried to compile it by myself, but compiling also did not work:
Code: [Select]
$ make HOST=linux BUILD_TYPE=release
make BUILD_TYPE=release HOST=linux LOG=off  2>&1 | tee build_log.txt
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_CAST_FROM_CAST -D_LINUX -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I../../../SP-Flash-Tool-src-master -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o AppCore.o ../../../SP-Flash-Tool-src-master/Public/AppCore.cpp
In file included from ../../../SP-Flash-Tool-src-master/Public/AppCore.h:16,
                 from ../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:8:
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h: In function ?€˜void Utils::SetTextCodec()?€™:
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h:114:17: error: ?€˜setCodecForTr?€™ is not a member of ?€˜QTextCodec?€™
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h:116:17: error: ?€˜setCodecForCStrings?€™ is not a member of ?€˜QTextCodec?€™
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::IsSecuLoaded(APKey)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:135:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e){
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::IsAuthLoaded(APKey)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:152:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e){
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜int AppCore::CheckSecUnlock(APKey, int)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:169:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e)
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::GetScatterVersion(APKey, char*)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:187:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e)
make[2]: *** [Makefile:2437: AppCore.o] Fehler 1
make[2]: Verzeichnis ?€ž/home/gabs/Software/Gemini/_Output/linux/release?€œ wird verlassen
make[1]: *** [Build/ all] Fehler 2
make[1]: Verzeichnis ?€ž/home/gabs/Software/Gemini/SP-Flash-Tool-src-master?€œ wird verlassen

The planet support give me the following answer:
Unfortunately, we do not provide support for the flash tool with Linux. Linux tends to fail 9/10 times when tried to flash our devices with it. This is due to Linux often lacking libraries or settings necessary for the flash tool work, combined with a general lack of understandable diagnostics and issue reports to the user.

The quickest fix here would be to use an available Windows (ideally windows 7) machine. You can also use a virtual machine running Windows 7 through Debian.

I did not have any Windows on my computers (and don't think to buy one ;-)).
So did anyone solved this problem?
Or did i miss some files/packages on my system?

Many thanks


Gemini PDA - Sailfish OS / SailfishOS released by Jolla
« on: January 12, 2019, 07:35:15 am »
today i read at that the SailfishOS Version is released by Jolla (older versions came from Community).

At the link above there is a detailed description howto install it.
Third party licensed Software is not included, but landscape mode should work out of the box  .
I installed it per ssh and after having a short look on it everything worked fine  .

Pages: [1]