I completed the definition of an ISO keyboard with accented characters for Romance languages.
I have not prepared a script or an installation package.
OPTIMIZED LAYOUT, FILE CHANGED
If there is interest, installation can be made easier.
In the meantime, mark here how you can remap the keyboard.
This is the file named "iso" which should be placed in the directory (for Debian-like distributions)
"/usr/share/X11/xkb/symbols"
These are the lines to add to the "gb" file of this directory:
Code:
partial alphanumeric_keys
xkb_symbols "iso" {
include "iso"
};
these lines must be inserted between two descriptions of variants
example:
...
include "level3(ralt_switch)"
};
<-- enter HERE -------------------------------------------------------------------
// Describe the differences between the US Colemak layout
// and a UK variant. By Andy Buckley (andy@insectnation.org)
partial alphanumeric_keys
xkb_symbols "colemak" {
include "us(colemak)"
...
edit the file "/usr/share/X11/xkb/rules/base.lst"
adding the line:
Code:
iso gb: ISO (with latin letters)
(near line 721)
for example
...
mac_intl gb: English (UK, intl., Macintosh)
<-- enter HERE -------------------------------------------------------------------
colemak gb: English (UK, Colemak)
...
edit the file "/usr/share/X11/xkb/rules/base.xml"
adding the lines:
Code:
<variant>
<configItem>
<name>iso</name>
<description>ISO (with latin letters)</description>
</configItem>
</variant>
(near line 5618)
for example
...
<variant>
<configItem>
<name>mac_intl</name>
<description>English (UK, intl., Macintosh)</description>
</configItem>
</variant>
<-- enter HERE -------------------------------------------------------------------
<variant>
<configItem>
<name>colemak</name>
<description>English (UK, Colemak)</description>
</configItem>
</variant>
...
copy the two files "base.lst" and "base.xml" replacing respectively "evdev.lst" and "evdev.xml"
For safety, better rename the initial files so you can easily restore them.
To make the changes effective, use mate control center / keybord / add keybord ("mate-keyboard-properties") and select UK (GB) language and "ISO (with latin letters)" variant.
I don't know if everybody here is aware of these SailfishOS collaboration meetings so I thought I post this here. The following is from a meeting that took place on 19.03.2020:
09:06:53 <Jaymzz> #topic Official support for PinePhone and Xperia 10 || (5 min – asked by cquence)
09:07:05 <Jaymzz> #info Is there any information you can share with regards to these 2 devices and getting official Sailfish OS images for them?
09:07:12 <Jaymzz> And here comes the answer
09:07:25 <Jaymzz> #info We are currently looking the next possibilities for Sailfish X devices. Requirements for a new device in general is availability for the community and enough openness by the vendor to allow providing an image to the device, similar to what we have done with Sony devices in the past. The mentioned devices are both potential candidates, but currently we can not confirm any plans.
09:07:37 <Jaymzz> #info If you have alternative in mind in addition to the mentioned two devices feedback welcome.
09:08:15 <pasik> #info pasik, community
09:08:31 <Jaymzz> I don't see cquence online. Does anyone have anything to add? Otherwise we shall move on in a minute
09:08:47 <Nico[m]> Well, my favourites are the 2 mentioned devices
09:08:48 <leszek> Xperia 1 flagship device with SailfishX would be cool
09:09:00 <Jaymzz> for sure
09:09:31 <leszek> also could mean some effort will be put into the camera app which is very weak
09:10:00 <flypig> #info David Llewellyn-Jones - late sailor @ Jolla
09:10:02 <M4rtinK> yeah, I don't think is is possible to ingore that anymore
09:10:18 <bionade24> Jaymzz: So it's officially that Pine64 sent you some devices and Jolla evaluates to support them?
09:10:24 <pm-guest> some news on upcomming devices from OMP/Russian providers?
09:10:27 <vknecht> official support for Tama devices ? (XZ2 etc.)
09:10:48 <ApBBB> vknecht if you have bugs report them on github
09:11:05 <Jaymzz> bionade24: Where did you get that info from?
09:11:12 <bionade24> Jaymzz: https://forum.pine64.org/showthread.php?...2#pid62012
09:11:36 <veskuh_web> pm-guest We can't comment on customer device plans.
09:11:51 <Jaymzz> bionade24: can't really comment on that yet actually But stay tuned!
I have a rockpro64 board and I was booting up till now with micro SD card.
Today I was not able to push the microSD card in slot by the usual spring.
What I see that after applying power no white/red leds are on.
I updated the armbian image from the one on armbian website but no luck.
my first name is Steve. I come from Belgium but i live in the Reunion island, a very beautifull and tropical island in the indian ocean (between Maurice island and Madagascar).
So, actually, i'm infographist who use free and open source softwares (The Gimp, Inskcape, Scribus,...) since 2008. So, i think my working with that is a reason to do professional design with FLOSS software are possible.
I have PMOS installed on my device, and can play sound (with mpv, for example) thru speakers, earpiece, and headphone jack, and make a voice call by sending "ATD". However, i can't figure out how to connect the modem audio. I have been following this guide, including using the included audio routing setup utility, but when i call a test number (for example: 1-800-437-7950) hear no sound — neither ringback nor sound from the other party.
I look at alsamixer and am daunted at the number of knobs. I've been viewing the diagram in aforesaid guide, but it's not helping me figure out which switch values in alsamixer mean which paths in the schematic.
As an existing owner of Pine64s and a Rock64, I have finally decided to take the plunge with a RockPro64. It is on its way, and I am pondering OSes. As I recall, original Pine64 and Rock64 builds were a bit mixed and so I wanted to reach out to ask the experts about the build that I should consider. (I have the most experience with Ubuntu/Armbian, and my use case is a headless Linux server using a minimal distribution.) My current ideas are:
What do you folks think of these? Is one better than the others from a reliability on the RPro standpoint? Is there anything else that I should consider?
