Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by order#10248

  1. Hello again, I can confirm that dual boot with Ubuntu Touch and current LineageOS 19.1 is working. Some small things have changed over the year: Magisk (needed to get root access in LineageOS) can not be used as version 21.4 (last version available as zip) in Android12 (it does not turn up as installed app), so sideloading that doesn't make sense. Instead the way with patching boot.img is needed. But it turns out to be quite easy: The file "boot.img" has not to be extracted from full nightly build img, the file is exactly the same as the recovery-pro1.img . Just download linea
  2. I wonder what would be the best place to ask for help with the other issues. I couldn't find any angoing recent development or issue tracking for UT with Fxtec Pro1. Did I miss something over at XDA-dev? UBorts have claimed they cant give support, as "development is mostly done by manufacturer Fxtec" ... I would be happier with seeing them work together more closely ... Do @tdm or @TheKit still stop by here every now and then? Cheers, order#10248
  3. I had a look into this "DNS" issue. It's not based on setting up DNS wrongly for cellular data. Instead an IP route is blocking access to those DNS servers. After every boot of my Pro1 I had an IP route for an usb0 device: phablet@ubuntu-phablet:~$ ip route ... dev usb0 proto kernel scope link src linkdown ... phablet@ubuntu-phablet:~$ I could not find where it is generated. Obviously it is for accessing the device (without usable UI) and with connected USB ethernet cable. For example: It is possible to do a ssh [email protected] then. My (and surel
  4. Okay, I managed to solve this finally. I found this driver source: https://gitlab.com/ubports/community-ports/android9/fxtec-pro1/kernel-fxtec-pro1/-/blob/halium-9.0/drivers/input/keyboard/qx1000.c where @tdm describes that there are different modes of the keyboard driver: qwerty and qwertz. In qwertz mode the generated keycodes by the internal micro controller are like printed on the QWERTZ version of Pro1 . The default mode with Ubuntu Touch is qwerty . No matter what is actually printed on the keyboard pads. So how to switch the driver to qwertz mode? One way ist to execute
  5. @Zahkc, a very big thank you for sharing your findings here! I am using code snippets for keyboard backlight and bluetooth and find them extremely useful. Bluetooth: The script did not work for me, dont remember the error (and did not look after). I just added the line with "sleep 5" in /etc/init/bluebinder.conf manually. For that a rw (re)mount of / is needed. I had this set permanently before already with sudo touch /userdata/.writeable_image From next reboot / is mounted writeable. To have it mounted ro again, just delete/rm /userdata/.writeable_image and reboot. Note tha
  6. Today I found over at Twitter twitter.com/lukapanio/status/1385479765445025792 : "Nice thing, but soon (some 3 month) ABM for pro 1/x will be avalible 🙂 you will have nicy boot menu, and unlimited number if OSes" ABM seemingly stands for Android Boot Manager and it is posted by the one who has started the thread at xda forum I linked here in last December. The suggested release time comes together with the time the new Pro1 X should become available. I love the idea to boot into Maemo Leste on the Pro1 (X) every now and then (additionally to UT and LOS like now). We will hop
  7. Thanks for the hint! But that rises again the question for a wiki or something alike to keep this kind of info easy accessable. Cheers, order#10148
  8. With my understanding the "recovery image" for Pro1 comes together with "boot image". The "boot" is only missing in the naming of the recovery-file offered for LineageOS. The fastboot command flashes the "recovery" into "boot(_a)". That means, as long the LineageOS-recovery.img is flashed into slot A, the boot-img-part is not the right one for Ubuntu Touch (that also resides in slot A) and Ubutnu Touch wont boot up fully. It needs to have its boot.img (re)flashed into slot A. So instead of "keeping" I suggest temporarely flashing the LineageOS-recovery-image to slot A, boot into that slo
  9. Congratulations Zahkc for getting it done and a very big Thank You for writing this up! Excellent work, I was about to share the notes I have made while dressing up my Pro1 to get famous, but that were already some meters to scroll (thats how it felt 😉 ) ... and you nailed it down. My way to get to dual booting was slightly different in details. But all in all the same. Still I want to paste some additional notes here. ****************************************************************************************************************** Basic things I learned, that might enlight the gu
  10. I am not sure if it already had come to notice here in this forum: There is a funding campaign to have a professionally skilled developer working on Anbox container for Ubuntu Touch: https://gofund.me/acb31504 I think it is worth to be supported. Anbox is kind of a container running an android environment so that native android apps could be run. Of course this could be more convenient than dual boot 😉 Cheers, Ulle
  11. YES!!! See attached video file (sorry for the ridiculous video quality ... had to shrink 2min to 2MB ...) I now have Ubuntu Touch via "Slot A" and LineageOS 18.1 via "Slot B". Dual boot procedure takes to get used to: It's not choosing OS during boot, instead it works from fully booted OS and then "OK, reboot into the other OS". The app used for that is "Switch My Slot" , with existing versions for UBports (Ubuntu Touch), Android and Sailfish. Feels like ages ago having such a satisfying moment like seeing this on my Pro1 \o/ Cheers, order#10248 Edit: Video is
  12. There seems to be some TWRP ... see https://community.fxtec.com/topic/3005-ubuntu-touch-os-for-fxtec-pro1/ ... Preparation: TWRP for Pro1: Download here https://drive.google.com/open?id=1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh (Credit to Mccreary) ... Thanks for for the steps/listing! I was on LineageOS 16 (Android9) and had to activate USB debugging via --> Settings --> About Phone (scroll down to last option) --> Build number (scroll down to last option) and tap on "Build number" multiple times --> until notifcation for "developer options are enabled" -->
  13. After almost half year there is some glimps of hope: https://forum.xda-developers.com/t/dualboot-android-boot-manager.4195929/ Will my dream come true to have Ubuntu Touch on my Pro1 AND being able to boot into LineageOS for apps that dont exist for Linux , like bike and car sharing etc? Lets keep fingers crossed!
  14. Today I took the time to flash Lineage OS , following the instructions at https://wiki.lineageos.org/devices/pro1/install . My Pro1 has physical qwertz keyboard layout and I prefer German as system language. So i did the following steps (sorry for writing german setting names here): "Einstellungen" --> "System" --> "Sprachen & Eingabe" --> "Physische Tastatur" -> "Builtin Keyboard" -> "Tastaturlayout wählen" + "einrichten": Checked Deutsch (Android Tastatur). Still no change: Most keys seem to be "shifted" , i.e. pressing "f" then a "d" is printed . Af
  15. Don't know how to put this into a code-box ... phablet@ubuntu-phablet:~$ uname -a && lsb_release -a && cat /etc/os-release Linux ubuntu-phablet 4.4.153-perf+ #4 SMP PREEMPT Wed Jun 10 00:15:28 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial NAME="Ubuntu" VERSION="16.04.6 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.6 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http:
  16. Thank you _DW_ for sharing these issues. TheKit, how much effort would that mean? Anyway, as you seem to be the one behind ubports-fxtec-pro1-v0.5.zip : Any plans to improve it newer versions?
  17. Well key "u" results into "z" , not "y" .
  18. Thank you both for excellent comments! My first try will be Ubuntu Touch OS as sngle boot OS ... Cheers, #10248
  19. Last week Liangchen Chen posted a video of a Fxtec Pro1 running Ubuntu Touch on Twitter https://twitter.com/chenliangchen/status/1272903474393604100 containing a link to an installable zip-file. I managed to install it and wanted to share the procedure, which is pretty equal to installing Sailfish OS: https://community.fxtec.com/topic/2467-community-build32120updated-jan-20-sailfish-os-for-fxtec-pro1/ . Text below is mostly copypaste from over there ... Most important info first: Installation process requires that you wipe your current OS and user data! Download Ubuntu Touch
  20. The Pro1 is announced with an unlocked or unlockable bootloader. And since I ordered my Pro1 ages ago I had the idea to have one Android system for some apps important to me AND one system which I could use for geek stuff, preferrably something like N900 Maemo . I am pretty new to current Android versions and how it handles "disk" space. I read something like "slot a" and "slot b" . Any chance to have two (or more) operating systems which could be choosen during boot process? Cheers, #10248
  21. Hello, I would like to ask if other pro1 (qwertz) users have the same uneven backlight behind their keyboards. See attached picture *. Some keys are hardly to be recognized, i.e. L, . (dot) , P , Ü , ß . Should this be considered as a hardware issue? Does anyone know how to push backlight to more brightness? And is it known today by someone how to keep backlight on as long as keyboard is slided out? Cheers, #10248 * Picture is changed a bit to some thresholds for brightness and contrast to emphasize the issue.
  • Create New...

Important Information