Jump to content

Raksura

Members
  • Content Count

    156
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Raksura

  1. 20 minutes ago, claude0001 said:

    Thanks @Raksura, for answering your own question and posting you experience here.

    I am also very interested in UbuntuTouch. But as I rely on my Pro1 as my only phone, I cannot afford to experiment too much with it.

    I would well be ready to give UT a chance for a few weeks, if I could be sure that basic stuff like telephony and GPS are working at least. Apparently this is not the case yet, so thanks for the warning.

    Is there any place where one can follow UT development for the Pro1, specifically (a list of open issues/bugs related to precisely that device)? What is the presently recommended way of installing it anyway? How do you get to the latest patchlevel? Does one still follow the flashing procedure form the OP, followed by in-OS-updating? 

    I've updated my report following a full firmware restore + clean install that was intended to let met clearly define how to reproduce the telephony issue but ended up removing it altogether.

    Haven't gotten GPS to work yet (and cellular internet doesn't appear to be working either).

    I don't know where to get details about UT development specific to the Pro1. There's UBports's repository collection, but it's not Pro1 specific.

    Installation is very easy: https://ubuntu-touch.io/get-ubuntu-touch

    • Thanks 2
  2. On 11/28/2020 at 8:19 PM, Raksura said:

    Is there a list of what works and what doesn't with Ubuntu Touch on the Pro1?

    I've been using Ubuntu Touch for about a week:

    Here's a report of what works and what doesn't:
    - OS Install process: almost perfect, a slight documentation issue for first time ADB users on Windows 10. ✔️
    - OS Welcome thingy: Impeccable. ✔️
    - Wi-Fi connection: Impeccable. ✔️
    - Lorimi (the window manager): impeccable. ✔️
    - The default terminal app: works well. ✔️
    - GPS: does not work. That's an immediate deal breaker for me, but since I don't need to travel during our current quarantine, I'll test things out more.
    - Media player (for music): impeccable.  ✔️
    - Default web browser: impeccable. ✔️
    - Mail application: there is none by default. The recommended one works just fine. ✔️
    - Synchronization with Google account: impeccable (contacts + calendar). ✔️
    - Calendar: works as intended, which isn't great (there's no event hub, so I can't easily tell what's about to happen). ✔️
    - Camera: front and back camera seem to work. The flash also works. ✔️
    - Charging: it charges, but the icon doesn't change to indicate it's plugged in. I don't know if that's intended. ✔️
    - Flashlight: does not work.
    - HDMI output: crashes the phone.
    - Screen orientation stuff: almost perfect. ✔️
    - Physical keyboard inputs: impeccable. ✔️
    - Physical keyboard backlight: does not work.
    - Cellular Internet: does not work. That is also a big issue.
    - MMS: does not work. Yet another big issue.
    - Telephony: I had a very problematic issue on my first install. After doing a full firmware restore and a clean Ubuntu Touch install (didn't transfer previous home directory), things seem to be working.

    All in all: great OS, not ready for daily use on the Pro1 yet.

    I wouldn't consider Ubuntu Touch as being ready for use as a daily driver until it has GPS, cellular internet, and MMS working.

    • Thanks 2
  3. I thought libhybris was a replacement for (or at least part of) Mesa 3D so it would be compatible with the Android kernel. I am failing to find a clear picture of what the figure I showed before looks like in the Pro1's version of UT or SFOS. 🤔

    Edit:
    I'm too tired to read it tonight, but I assume I'm not the only one getting a rather brutal introduction to all of this for the first time, so here's a website that looks like it explains it all: https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=53608808

    • Thanks 1
  4. Alright, that's not quite the point where I think I'm mistaken. I do see quite clearly that there is a difference between the Wayland interfaces and EGL.

    What I don't understand is (and that was my question in the quoted discussion, hence my confusion if this is indeed not what the reply is about): the link between client and the user mode graphics drivers, is there a defined EGL API that allows replacing one user mode graphics drivers with another in a way that is transparent for the client, or does the client have to be compiled with an API that is only valid for a specific user mode graphics drivers? I took the reply to mean that there is a standard API, but that part of it (concerning the framebuffers) is currently missing and that's why it isn't working. Now I see the answer might not be addressing my question.

    The_Linux_Graphics_Stack_and_glamor.svg

  5. I am also far from being expert on this, so it is entirely possible that I misinterpreted the following conversation:

    Quote

    Me:
    I'm playing around with a prefixed install so that I can compile stuff and have up-to-date software. Learning about how things works as I go. I'm sad to see that even with its latest version, Weston does not have hardware acceleration (I haven't compiled other Wayland applications yet, but I assume they will have similar limitations). From the Wiki page for Wayland, I gather Weston properly interfaces with Wayland, but there is an issue with the EGL interface. I assume (I don't see any error message, so it's kind of a blind guess) the root of the issue is that this interface relies on a library that should provide/use the drivers for the graphics and in my case (a Pro1 phone), these drivers are actually provided by libhybris and Weston doesn't interface with it. Is this correct? Would this require special bindings, or can libhybris be selected as user mode graphics drivers in some way that is transparent to Weston?

    TheKit:
    currently Mir is missing Wayland EGL buffers integration on Android platform. You can look through the logs here around November 19th
    it's not impossible to fix and the code is mostly there, but not integrated and there are some bits that need to be debugged

    I took it to mean that once EGL buffers are properly integrated on the Android platform, hardware acceleration will become available to standard Wayland applications.

  6. 11 hours ago, claude0001 said:

    * As long as all alternative OS'es (Lineage, Sailfish, UbuntuTouch, ...) use the same original Linux kernel from stock Android 9 and its (closed-source) drivers, we will never get things like hardware-accelerated graphics in a "desktop" Linux install.

    Are you sure about that? Hardware acceleration seems to be working on both SailfishOS and Ubuntu Touch. From what I gather, the main issue is the Wayland protocol interfaces not being up to date (SailfishOS, but also sometimes with Ubuntu Touch), not proposing the standard interfaces (SailfishOS), or not quite yet featuring all the stuff they need for hardware acceleration but this lack is being worked on (Ubuntu Touch). Applications ported to these systems are modified to match such restrictions (use Mir on UT until Wayland support is fully there; use the peculiar Wayland interfaces on SFOS) and thus benefit from hardware acceleration. Once the Wayland interfaces get updated, I assume porting applications so that they support hardware acceleration will require little to no work at all.

    • Thanks 2
  7. There are people working on a Mobian (Mobile Debian) port: https://github.com/hybris-mobian-images

    I've attached a screenshot of the progress as reported on a Google drive link that was given by a porter on the Discord (with an understanding that it is not up-to-date, and that was on the 2020-10-23). I am not sharing the link, as it allows editing so I don't think it should be made that public.

    mobian-port.png

    From what I understand, the main barrier for other OSes being supported is that the drivers for the Pro1 are not available in the mainline Linux kernel. The current solutions rely on libhybris, which in effect makes it possible to use the Android drivers (and kernel maybe? I'm not sure). I believe PostmarketOS declined to consider the Pro1 as a viable target because of that (no interest of supporting devices through libhybris).

    • Like 2
    • Thanks 2
  8. 1 hour ago, PokeParadox said:

    I'm also toying with the idea of moving over to Ubuntu Touch or SailFish but I don't know if that would make my life easier or not.

    Getting a standard Linux install running on SailfishOS is pretty easy, thanks to containers. Hardware acceleration isn't available for those containers, as far as I know, so it might not be the best solution to play games.

    • Thanks 2
  9. I have this issue with mine, but it's most likely due to something different (I am using SailfishOS).

    In my case, plugging the phone to a computer doesn't provide enough energy to charge (~500mW being consumed, versus ~1500mW when unplugged), but if I use an USB-C hub in between, it starts charging (around -1500mW consumed). However, the phone has a tendency to disconnect from the telephony network while charging that way.

    Using the adapter provided with the phone works fine though. I've only used once or twice, so I don't have much data for it. Using a car adapter also charges fine, but generates parasitic noise on the jack output.

    So yeah, you might want to try with a USB-C hub in between, if you have one.

  10. 1 hour ago, gogasan said:

    Hello.

    I've send ETA clarify request 2 days ago to fxtec support. I'm doing it each month, but this time they did not responded. Do we know new shipping eta for preorders?

    Not really. The last update indicated that they were trying to get the factory to output one (unknown size) batch every two or three weeks. That's basically 21 days in-between batches. According to the usual thread for informing people they are received, the last "stock assigned" messages were sent June 3 (23 days ago), so they might not have succeeded in getting that deal (or have a small delay in sending new stock assigned messages, in which case we'll know soon enough).

    • Like 1
    • Thanks 1
  11. The removal of the time limit does help a lot. The main issue with only using the forum would now be indexing. for example, if I were to look for the currently available OSes for the Pro1.

  12. Hey,

    Do any of you know of a good (and free) platform to host a community wiki for the Pro1?

    The issue being that the forums are good for discussions, but not for providing information and guides (especially considering there is a time limit for editing posts). For example, if you were to discover this phone today, you'd have a hard time finding out which OSes are available for it and where the guide for each of them is. Basically, if you know to search for it, the forums will provide you the info you need, but there is no index, nor much separation between conversation and guides (not to mention user suggested solutions which spawn many, many pages in a single thread without such distinctions).

    The best solution would be for F(x)tec to be hosting it themselves, since that avoid all the caveats a free solution would imply. @Erik, would this be possible?

     

    • Like 7
  13. 26 minutes ago, marmistrz said:

    Could we have some community wiki about the protective cases? I know about the blogpost by @EskeRahn, but I saw that others recommended some other cases... and I don't think I have the time to get through 34 pages of the thread 🙂

    Great idea. We could definitely use a community wiki, in general.

    • Like 2
  14. 2 minutes ago, ohkami_b said:

    oh wow, i just checked your previous posts and found this from february 2020: "#12xxx IGG EU QWERTY". my order # is 34xxx, not even close. if they are shipping 12xxx now i guess i better cancel. and hope they have money to refund.

    There's not much correlation between order number and delivery time. Look up what we assume to be the sorting algorithm for order delivery.

    • Like 2
  15. I think there is a time limit on edits on this forum, so I'll post updates on this page instead.

    Here's a guide on how to get Gentoo Prefix running under SailfishOS. I've made it for the Pro1, but you might be able to use it for another device.

    If you know what Gentoo Prefix is, do not expect it to be the smooth ride I'm sure it usually is.

    If you know what Gentoo is, but not what Gentoo Prefix is: the short of it is that this basically lets you install Gentoo as a normal user in the directory of your choice, minus the kernel (since one is already running). You cannot mess up your SailfishOS install with this, so it's pretty safe to play around with.

    If you don't know what Gentoo is, it's a distribution aimed at power-users that lets you customize quite a lot of stuff. Basically, a dedicated group of maintainers ensure that the configuration of your usual programs can be done through simple keywords in a standardized fashion (e.g. "ssl" to indicate you want your package to have the ssl options enabled). In practice, you basically have a set of text files in /etc/portage/ that describe the system you want, and a package manager (Portage) which will tell you if that's doable, or why not, and make it happen if it is. The downsides being that you are expected to have a coherent set of files in /etc/portage/, so you'll often face a "nope, you need to allow this in /etc/portage/ before I can do that" kind of issue if you're not careful. Also, since you really can personalize stuff, packages have to be compiled, which can be annoying when installing new software (not so much when updating, since you can just let it compile in the background). This also means you can tailor your programs to your hardware to get better performance. There is somewhat of an expectation for users to read documentation, so if you don't want to take the time to learn what things are and how they work, you shouldn't be trying to customize them, and thus probably shouldn't be using Gentoo. Oh, and the TL;DR of compiling on a phone: it wasn't a good plan 20 years ago, but you have a gaming PC in your hands nowadays, so the only issue is the rewrite limits of flash memory. Just use tmux or Screen when merging huge packages (e.g. llvm, xorg, firefox, webkit-gtk, icedtea, ...) so that you don't lose progress if the Sailfish terminal application stops for some reason (I've noticed it did that sometimes, and that was even before I installed the Prefix).

    SailfishOS runs a 64bit kernel (aarch64) with a strictly 32bit userland (armhf). I'd ask, but I don't know who to.
    Whatever. The point is: you're not easily getting a 64bit toolchain set up on that, so this guide goes for a 32bit Gentoo Prefix (armhf). Now, the interesting thing is: Gentoo is very good at setting up cross-toolchains, so it might be possible to use the 32bit Gentoo Prefix to create a 64bit toolchain that you could use to install a 64bit Gentoo Prefix (this... is to go... even further beyond!). You can see what your toolchain is by running "gcc -v".

    Note that ${EPREFIX} refers to the folder you want your Gentoo Prefix installed in. Mine is /gentoo, so if you see that in this guide, assume that this means you have to actually write the name of the folder and not use the environment variable (and only in this case, otherwise, prefer using the env variable). You should export this environment variable (which you'll need to do anyway):

    $ export EPREFIX="/gentoo"

    For reference, commands starting with "#" (e.g. "# mkdir ${EPREFIX}") are commands ran as root, whereas commands starting with "$" (e.g. "$ mkdir ${EPREFIX}") are commands run as nemo (or any normal user). You shouldn't be using root for anything past "Getting Started".

    Getting Started

    Setting up an SD Card

    I strongly recommend using an SD card (and one targeted at dashcams, so that it withstands a lot of rewrites) to store your prefix. If you don't want to, feel free to skip this step and create the EPREFIX folder.

    This assumes you've just put a dedicated SD card in your phone. If this is not the case, make sure the SD card is formatted in something that can support a Linux system (e.g. ext4).

    Formatting the SD card:

    # cfdisk /dev/mmcblk0

    Choose Linux as partition type. Write the new partition table.

    # mkfs.ext4 /dev/mmcblk0p1

    This makes your partition use ext4.

    Preparing the Prefix folder:

    # mkdir ${EPREFIX}

    This creates the folder (if you didn't know that, it's a strong sign that you should probably not be trying Gentoo yet).

    As root, edit /etc/fstab to add the line:

    /dev/mmcblk0p1  /gentoo ext4    defaults 0      0

    This will make it be mounted automatically at boot.

    # mount ${EPREFIX}

    This mounts it right now.

    # chown -R nemo:nemo ${EPREFIX}

    This makes it owned by nemo, meaning that you don't need root privileges to read or write in there.

    Installing the required packages:

    SailfishOS has a package manager called pkcon. I'm very new to that OS, so there may be a better one, but this one will do.

    You will need to install "make", "gcc", "gcc++", and "python" (that last dependency is not standard for a Gentoo Prefix install, but you'll need it for a workaround).

    # pkcon install make gcc gcc++ python                                                              

    I've actually done that with one command per program installed, but I assume you can use a single call.

    Tinkering some stuff in the install script:

     Download the Gentoo Prefix bootstrap script from https://wiki.gentoo.org/wiki/Project:Prefix and put it in ${EPREFIX}.

    Make the script executable:

    $ chmod +x ./bootstrap-prefix.sh

    Open it in your favorite text editor (i.e. vim).

    Find:

    	if [[ ${PN} == "m4" ]] ; then
    		# drop _GL_WARN_ON_USE which gets turned into an error with
    		# recent GCC 1.4.17 and below only, on 1.4.18 this expression
    		# doesn't match
    		sed -i -e '/_GL_WARN_ON_USE (gets/d' lib/stdio.in.h lib/stdio.h

    Add before:

    	if [[ ${PN} == "tar" ]] ; then
    		# drop _GL_WARN_ON_USE which gets turned into an error with
    		# recent GCC 1.4.17 and below only, on 1.4.18 this expression
    		# doesn't match
    		sed -i -e '/_GL_WARN_ON_USE (gets/d' gnu/stdio.in.h gnu/stdio.h
    	fi

    tar won't compile if you don't do that.

     

    Find and comment out:

    	[[ ${PN} == "bash" && ${CHOST} != *-cygwin* ]] \
    		&& myconf="${myconf} --disable-readline"

    bash won't compile if you don't do that.

     

    Find:

    	einfo "running emerge -u system"
    	CPPFLAGS="-DGNUSTEP_BASE_VERSION" \
    	CFLAGS= CXXFLAGS= emerge -u system || return 1

    Add before:

    	einfo "fixing virtual/libc"
    	CPPFLAGS="-DGNUSTEP_BASE_VERSION" \
    	CFLAGS= CXXFLAGS= emerge -1 --nodeps -n --ask virtual/libc glibc || return 1

    The script won't be able to do the "emerge -u" you just saw without that.

     

    Find:

    	[[ ${OFFLINE_MODE} ]] || type -P wget > /dev/null \
    		|| (bootstrap_wget) || return 1

    Add before:

    	[[ ${OFFLINE_MODE} ]] || type -P wget > /dev/null \
    		|| (bootstrap_libpsl) || return 1

    wget needs libpsl to compile.

     

    Find:

    bootstrap_wget() {
    	bootstrap_gnu wget 1.20.1 || \
    	bootstrap_gnu wget 1.17.1 || bootstrap_gnu wget 1.13.4
    }

    Replace with (yes the extra function should be added):

    bootstrap_wget() {
    	bootstrap_gnu wget 1.20.1 #|| \
    #	bootstrap_gnu wget 1.17.1 || bootstrap_gnu wget 1.13.4
    }
    
    bootstrap_libpsl() {
    	bootstrap_gnu libpsl 0.21.0
    }

    wget will crash anyway, so let's not lose too much time trying the other versions. We also need to add something to install libpsl, hence the added function.

    You're done with pre-installation stuff.

    Stage 1

    I'll repeat it again, just in case: from now on, no root, only nemo.

    Go to ${EPREFIX}

    $ cd ${EPREFIX}

    Create a file called prefix_env_stage1_2.sh, with the following:

    export EPREFIX="/gentoo"
    export CHOST="armv7hl-hardfloat-linux-gnueabi"
    
    export CFLAGS="-march=armv8-a -mtune=cortex-a73.cortex-a53"
    
    export PRESTAGE_1_PATH="${PATH}"
    export PATH="${EPREFIX}/usr/bin:${EPREFIX}/bin:${EPREFIX}/tmp/usr/bin:${EPREFIX}/tmp/bin:${PATH}"
    export LDFLAGS=""
    export LD_LIBRARY_PATH=""
    export CFFLAGS=""
    export PKG_CONFIG_PATH=""
    export PATH="${EPREFIX}/usr/sbin:${EPREFIX}/sbin:${EPREFIX}/tmp/usr/sbin:${EPREFIX}/tmp/sbin:${PATH}"

    If you are indeed using the Pro1, you should only modify the EPREFIX line to match your own. Otherwise, I believe the CHOST is mostly linked to the toolchain provided by SailfishOS and should thus stay unchanged. the CLFAGS must match something that fits your CPU. Do not simply remove them, this will not work here and will force you to restart the whole thing way down the line (can you tell I'm speaking from experience? 😅).

    Source prefix_env_stage1_2.sh. You'll need to do that again every time you close the terminal during the stage 1 and stage 2 process (which you have no reason to, but just in case, it's nice to have it available):

    $ source prefix_env_stage1_2.sh

     

    Stage 1 is now about to start for real...

    $ ./bootstrap-prefix.sh "${EPREFIX}" stage1

    If you see a nice logo in ASCII art, you failed to source prefix_env_stage1_2.sh.

     

    Bootstrapping WGET fails:

    Yeah, it will do that in this install. I did warn about this not being a smooth ride, didn't I?

    $ mv ${EPREFIX}/tmp/bin/wget{,_back}

    This renames wget into wget_back. We'll create a shim. Using your favorite text editor, create the file ${EPREFIX}/tmp/bin/wget with the following content:

    #!/bin/bash
    LD_LIBRARY_PATH="/gentoo/tmp/lib" /gentoo/tmp/bin/wget_back $@

    It is important that you do not use the ${EPREFIX} environment variable here. Hardcode the location.

    Make it executable:

    $ chmod +x ${EPREFIX}/tmp/bin/wget

    Resume stage 1:

    ./bootstrap-prefix.sh "${EPREFIX}" stage1

    Bison will try multiple versions before succeeding.

     

    Missing Profile:

    Near the end of stage 1, you'll get a message about the profile for your setup not being automatically found.

    $ ln -s ${EPREFIX}/var/db/repos/gentoo/profiles/prefix/linux/arm/ ${EPREFIX}/etc/portage/make.profile

    Let's  do everything we need to do in ${EPREFIX}/etc/portage right now, so we don't have to later.

     

    Modifications in ${EPREFIX}/etc/portage:

    Here's my ${EPREFIX}/etc/portage/make.conf. Make yours match so that the compilation succeeds. Note that some of these fields might not be doing anything. Also, don't worry if one of the values do not match the environment variables you sourced before, we don't want them to until stage 3 (hence the name of the sourced file):

    # Added by bootstrap-prefix.sh for armv7hl-hardfloat-linux-gnueabi
    CHOST="armv7hl-hardfloat-linux-gnueabi"
    USE="-X wayland pulseaudio dbus ssl unicode nls"
    CFLAGS="-march=armv8-a -mtune=cortex-a73.cortex-a53"
    #LDFLAGS="-Wl,--dynamic-linker=/gentoo/lib/ld-linux-armhf.so.3"
    LDFLAGS="-Wl,--dynamic-linker=/gentoo/lib/ld-linux-armhf.so.3 -Wl,-rpath=/gentoo/lib"
    CFLAGS="${CFLAGS} -O2 -pipe"
    CXXFLAGS="${CFLAGS}"
    MAKEOPTS=""
    CONFIG_SHELL="/gentoo/bin/bash"
    DISTDIR="/gentoo/var/cache/distfiles"
    # sandbox does not work well on Prefix, bug 490246
    FEATURES="${FEATURES} -usersandbox -sandbox"
    LIBRARY_PATH="/gentoo/lib/:/gentoo/usr/lib"
    RPATH="/gentoo/lib/:/gentoo/usr/lib"

    ${EPREFIX}/etc/portage/package.accept_keywords:

    =sys-apps/baselayout-prefix-2.6-r2::gentoo ~arm

    Not having that will interrupt the install script when it comes time to install that package: they're all marked as unstable and thus, masked.

    ${EPREFIX}/etc/portage/package.env:

    dev-lang/perl perl

    Perl... has some issues getting installed.

    ${EPREFIX}/etc/portage/env/perl: (You will need to create the directory first)

    EXTRA_ECONF="-Dosname='linux' -Dhintfile='linux' -Duserelocatableinc='false'"

    Perl considers that any OS with a Linux kernel in which /system/lib/libandroid.so exists must be Android. We need to really insist on being Linux. Also, it'll try and fail to install with incompatible options, so we disable the one that isn't hardcoded in the Gentoo package file.

    ${EPREFIX}/etc/portage/package.unmask:

    =sys-kernel/linux-headers-4.4

    Not too sure about this being a good idea, but we need one and that matches the numbers I get when I use "uname -a".

    Stage 2

    We've got one last thing to do before starting Stage 2: fixing some stuff the script did incorrectly.

    Print $PRESTAGE_1_PATH:

    $ echo $PRESTAGE_1_PATH

    Does it contain anything related to Gentoo Prefix? The goal here is to get the $PATH you were using before adding the Gentoo Prefix directories to it.

    You'll need to edit two files, but their content are the same. Make it so ${EPREFIX}/tmp/usr/local/bin/{gcc,g++} contain only one copy of the three lines (you'll be able to see it clearly if the content has been duplicated). Make it so that their content is similar to:

    #! /bin/sh
    PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/nemo/bin" export PATH
    exec "${0##*/}" "$@"

    Replacing the value I've put there with the one you have in $PRESTAGE_1_PATH (which is the same if you haven't modified your PATH outside of this guide).

    You can now run Stage 2:

    ./bootstrap-prefix.sh "${EPREFIX}" stage2

     

    Stage 3

    $ mv prefix_env_stage1_2.sh prefix_env_stage3.sh
    $ echo 'export LDFLAGS="-Wl,--dynamic-linker=/gentoo/lib/ld-linux-armhf.so.3 -Wl,-rpath=/gentoo/lib"' >> prefix_env_stage3.sh
    $ source prefix_env_stage3.sh

    The binaries we compile from now on have a little problem with finding the right libraries. So we're going to use a dynamic linker that works for them.

    You can now run Stage 3:

    $ ./bootstrap-prefix.sh "${EPREFIX}" stage3

    emerge --depclean failed:
    Yeah, and you know what? Let's not bother fixing that. Look at the very last line there. It should tell you have successfully passed stage 3.

     

    After the Install

    $ mv prefix_env_stage3.sh prefix_env.sh
    $ echo 'export PORTDIR="${EPREFIX}/var/db/repos/gentoo"' >> prefix_env.sh
    $ source prefix_env.sh

    If you don't do that last part, Portage won't find the packages.

    Just source ${EPREFIX}/prefix_env.sh whenever you want to use Gentoo Prefix.

    Hopefully, you now have a Gentoo Prefix install on your phone. Happy hacking.

    PS: If you're not used to Gentoo on ARM/AARCH64, but use it on some other architecture, you might be surprised by some packages being masked due to missing keyword (e.g. mednafen). Check the webpage for the package, since it might not be available even in unstable for this architecture, meaning that you will need to add a keyword to allow its installation using the package of another architecture.

    You'll most likely want to follow the advice of Portage and set your locale in ${EPREFIX}/etc/locale.gen. I'm not going to include much in terms of guides for general Gentoo use, since there are many other better written resources for that. Just know of the "--autounmask" parameter for emerge, which really helps getting quickly over blocked/masked packages: if it tells you that you need to add a keyword looking like "your/package **", this means there's no ARM package available and it's trying to get the package from another architecture. It's not something you usually see when using Gentoo on a PC.

     

    I'll post guides for these once I've reached them, but the next objectives are:

    • Getting Gentoo Prefix applications linked up with the existing Wayland display. I don't know much about Wayland, so don't expect too much, but as far as I know, this is totally doable.
    • Getting XWayland running. This should let you get standard X11 applications running on SailfishOS.
    • Getting Firefox running. Web browsers aren't exactly the easiest of packages to successfully merge.
    • Getting Mednafen running. I want that keyboard driven console emulator on the Pro1, dammit! 😄

    If you've beaten me to these, please share how you did it.

    The two first steps are somewhat there (this is weston running XWayland and displaying glxgears, all of which are from the Prefix), but without hardware acceleration (don't believe the FPS indicated by glxgear, there's still some stutter), which I really hope can be fixed.

    • Like 2
    • Thanks 8
  16. I bought a nice magnetic case that seemed very sturdy, but it ended up not being usable, since the phone holder is rigid (and it would need like 1 or 2 extra millimeters). I also had a rather rubbery phone holder for a flip case that was not sturdy enough for my tastes. I tinkered a "best of both worlds" version:IMG_20200610_190713.jpg

     

    I used some strong glue to get the magnet attached, so that it's not just held by tape.


    IMG_20200610_193049.jpg

    Some laundry clips straight out of the garden.

     

    IMG_20200610_194551.jpg

    IMG_20200610_194557.jpg

    IMG_20200610_194702.jpg

    By pure coincidence, my mom actually brought prawns for dinner while I was working on the cover, so I knew I had to take a picture. Also had to explain and translate the inside joke.

    IMG_20200610_195243.jpgIMG_20200610_195325.jpgIMG_20200610_195341.jpgIMG_20200610_195354.jpg

    There's not enough feedback on that button, I don't like it. The fingerprint reader is hidden, but that is on purpose.

    IMG_20200610_195401.jpg

    It ends up working as well as I hoped. I still need to make a hole for the notification led.

    • Like 3
  17. Finally got the phone. 😀
    From what I understand, the delivery guy actually just flags packages meant to come here as having been attempted and a delivery notice having been given even though he kept the package, and he simply does that part of the delivery on the next day (the website doesn't help, implying that said notice is indicating if and where the package might have been left, and will tell you if further deliveries will be attempted if it wasn't). Might be making his life easier, but getting blatantly incorrect info is not exactly what I'd call a good experience for the recipients who are not aware.
    • Like 4
    • Thanks 1
    • Haha 1
    • Confused 1
    • Sad 1
  18. 17 hours ago, kontakt said:

    Maybe ring your neighbors?

    Yeah, that was indeed what I thought might have happened. The house is lost in the countryside, with only two neighbors. I actually checked the slightly distant neighbor's mailbox (they're away and we've agreed to take their mail in the meantime), the other's can't have been reached without me noticing, since the delivery man would have had to park right in front of ours to access it.

    • Haha 1
  19. FedEx is lying to me and saying they attempted delivery and I wasn't there.
    I am, not figuratively, camping in front of the house all day and night (working remotely during the pandemic). I'd be impressed if anyone managed to actually go to the mailbox without me noticing.
    While I do not tend to take being lied to lightly, having yet another "you're about to get the phone" followed by a "oh, never mind, new delay" has me ever so slightly upset.
    My phone is currently at the location indicated on the delivery attempt notification that was left in my mailbox. You know, the one that was never left in my mailbox.
    Can't talk to any human at FedEx either, their contact number is not attended to because of the pandemic. Can't phone their depot directly either, they only have the non-attended national number. The depot is rather far and I don't have the free hours needed to go there during work time either (since I also have deadlines, and, as weird as it seems, mine can't be ignored without consequences).
    So yeah, I don't know where the phone has gone to. I'm hoping they'll bother informing me at some point.

    • Haha 1
    • Sad 1
  20. I just received a SMS from FedEx about a delivery on the 8th of June for a package from Expansys (Hong Kong). 😀

    Still slightly worried about being the only QWERTY in a QWERTZ batch, but I guess I'll know soon enough if something went wrong.

    Edit:
    Got the tacking number from FedEx to go with it by email a few minutes later. They just picked up the package, apparently. That's very fast.

    • Like 3
  21. I am part of the batch and in France, so it's not just for Germans (it is however possible that they send it to France through Germany, that's not uncommon).

    I am however getting slightly worried that I have the only QWERTY in that batch. I'll trust them not to have sent the wrong layout, but I can't help wondering. 😄

    • Like 1
    • Confused 1
  22. Can confirm, I received one. Thanks! 😀

    Quote

    Dear valued customer,

     

    Good news! We have now assigned the stock for your Pro1 order. The product is on its way from the factory to the regional fulfilment warehouse with customs clearance to follow. 

     

    We expect to notify you with the courier tracking details by Monday, the 8th of May if not earlier.

     

    Thanks for your support and continuous patience.

     

    Kind regards,

    F(x)tec Logistics

    For those trying to make a guess at delivery times:

    Date of Pre-Order: Fri, 22 Mar 2019 10:20:07 (GMT)
    Order Number: 103xx
    IGG Coupon: No
    Model: QWERTY
    Location: EU (France)
    Date of Payment: Thu, 1 Aug 2019 06:06:37 (GMT)
    Stock Assigned Email: Wed, 3 Jun 2020 12:19:35 (GMT)
    Tracking Number: No
    Phone Received: No

    • Like 5
    • Thanks 1
×
×
  • Create New...

Important Information

Terms