Kabouik

#!/usr/bin/env bash

# This script will install Cutie or Phosh on a device
# already running Droidian. This is an alternative to
# using one of the Cutie Droidian images that need to
# be flashed.
# Use at your own risk, odds are it will break things.
# Authors: Kabouik (@bouic), Erik (@eriki73)
# https://t.me/CutieShellProject

Kabouik

Dual-booting Droidian and SailfishOS on the F(x)tec Pro1

Author: kabouik but all credits to g7

---

Known issues related to dual-booting, as of 2023-09-10:

• Switching from Droidian to SailfishOS can be done directly on the phone, but from SailfishOS to Droidian requires a computer.
• Nothing else so far, yay.

---

Foreword

Kabouik

    wl(){
      local ssid
      local conn

      nmcli device wifi rescan > /dev/null
      ssid=$(nmcli device wifi list | tail -n +2 | grep -v '^  *\B--\B' | fzf -m | sed 's/^ *\*//' | awk '{print $1}')

      if [ "x$ssid" != "x" ]; then
        # check if the SSID has already a connection setup
        conn=$(nmcli con | grep "$ssid" | awk '{print $1}' | uniq)

Kabouik

postmarketOS and mainline kernel on F(x)tec Pro¹

Below are the steps required to flash postmarketOS (port made by Danct12 based on earlier work by Notkit) and mainline kernel (work done by Kholk and the github.com/somainline group) on the Pro1 msm8998:

2022-03-10. As of today, Danct12's port has not been merged yet, hence there are a couple extra steps to manually apply patches to pmaports. Beware that this is all work in progress and there will be bugs and missing functionality. 2022-03-12. device-fxtec-qx1000-nonfree-firmware added to the port, meaning support for model, WLAN and GPU.

1. pip3 install --user pmbootstrap
2. pmbootstrap init and choose edge and whatever device (I chose qemu and aarch64, but it should not matter, we'll redo it later).
3. cd /path/to/work/directory/you/chose/above/cache_git/pmaports

Kabouik

Kabouik

Kabouik

F(x)tec is using the Pro1x as a way to introduce new keyboard layouts, but we noticed the latest proposal on IGG doesn't seem to address the biggest issue with the original Pro¹ shifted qwerty layout: missing slash/question-mark key, creating problems in all OS's and necessity for OS-specific workarounds. Therefore we hope F(x)tec uses this opportunity to not only un-shift but to also improve functionality, especially as alternate OS's like Linux are now clearly targeted.

Fig. 1. Unshifted qwerty layout shown in the Pro1x campaign.

The community quickly showed interest in this topic, with more than 150 posts by users from multiple OS's and about 3k views in just a few days. After one week of vivid discussions to weigh the costs and benefits of each suggestion users came up with, we think we've finally agreed on layout proposals we believe would significantly improve the user

Kabouik

! model
  pc101           Generic 101-key PC
  pc102           Generic 102-key (Intl) PC
  pc104           Generic 104-key PC
  pc105           Generic 105-key (Intl) PC
  dell101         Dell 101-key PC
  latitude        Dell Latitude series laptop
  dellm65         Dell Precision M65
  everex          Everex STEPnote
  flexpro         Keytronic FlexPro

Kabouik

Warning

This guide is meant to be used with the Pro1 (QX1000 model, SOC SD835 or also called msm8998). If you have a Pro1x (QX1050 model, SOC SD662), head over here.

TWRP on F(x)tec Pro¹, an SFOS perspective

Table of Contents

• TWRP on F(x)tec Pro¹, an SFOS perspective

Inspired from this guide and proofread by @kabouik, @pcfe and @enigma9o7.

Kabouik

default  partial alphanumeric_keys
xkb_symbols "us" {
    include "us(basic)"

    name[Group1]="Fxtec Pro1 English (US, intl., with AltGr dead keys)";

# Extra symbols on levels 3 (YellowArrow modifier) and 4 (Shift+YellowArrow), no dead keys on levels 1 and 2

    key <TLDE> { [       grave,        asciitilde,           dead_grave,            dead_tilde] };
    key <AE01> { [           1,            exclam,          onesuperior,           exclamdown ] };