Jump to content

Leaderboard

  1. tdm

    tdm

    Members


    • Points

      184

    • Content Count

      434


  2. Slion

    Slion

    Members


    • Points

      98

    • Content Count

      634


  3. EskeRahn

    EskeRahn

    Keymaster


    • Points

      78

    • Content Count

      3,000


  4. Hook

    Hook

    Members


    • Points

      70

    • Content Count

      605



Popular Content

Showing content with the highest reputation since 06/06/2020 in all areas

  1. 15 points
    FYI... Made huge progress on selinux today. I should have an enforcing build by end of week. And I think it can go official after that.
  2. 12 points
    Quick update... Got lineage to boot in enforcing mode today. Still need to tweak a few rules to get the fingerprint reader and lights hal to work. I'll probably have that done in a couple days. Then I'll start preparing for official lineage support. And of course, after that it's on to Q. Which should be pretty fast and easy. I'll be trying to get VoLTE working next week. @Hook has sent me a Verizon SIM to use for testing. Thanks!
  3. 10 points
    This is a good idea. I will look into some Wiki platforms, and allow trusted community members to post :). I've just removed the time limit on post edits.
  4. 10 points
    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 [email protected] 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##*/}" "[email protected]" 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.
  5. 10 points
    I'll probably be the one to do that. I got close to a functional decrypt before covid hit, but haven't been able to work on it since. I'm focused on getting Lineage finished and official and TWRP should come after that.
  6. 9 points
    https://github.com/ubports-on-fxtec-pro1 is correct. Rootfs currently has manual tweaks for configs, as I didn't plan for the image to be released publicly and it more served as demonstration, but if there are enough interested parties, we could properly integrate the device on UBPorts CI for OTA updates and support in installer.
  7. 8 points
    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 OS for Fxtec Pro1 from the following link: https://drive.google.com/file/d/1qQtVgbmRezbGWovfxulUvhiOkhtehfTP/view?usp=sharing ubports-fxtec-pro1-v0.5.zip (811M) Preparation: TWRP for Pro1: Download here https://drive.google.com/open?id=1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh (Credit to Mccreary) Universal ADB Driver A MicroSD Card, preferably no more than 32GB Backup your data (if needed) and turn off the phone completely Transfer the TWRP image into the adb folder of your PC, and Sailfish OS package zip-file to MicroSD card. Insert the MicroSD card to your phone's SIM card tray. Procedures: For units shipped after November 19, you need to unlock Bootloader first, by enabling developer mode in Android, and enable OEM unlocking and USB debugging. Then following the steps. When phone is switched off hold Vol Down while pressing the power key, then release both fingers together and the phone should boot into bootloader Connect the phone to PC and run fastboot devices If the phone is successfully connected, the phone should be listed in command line. Then type: fastboot flashing unlock then using vol +/- navigate to "Unlock Booloader", and select with the power key Warning: All your data will be wiped after Bootloader is unlocked! Please back up! After unlocking bootloader, boot into BL again using vol- + power key, and perform: fastboot set_active a fastboot flash boot [|path|to|file]twrp-3.3.1-qx1000.img Use volume up/down to scroll, to Recovery mode and power key to select, from bootloader. And wait for TWRP to boot. In TWRP go to Wipe -- Format Data (Warning: All your data will lost.) --- type yes, and click blue tick When format is completed, go back three times and go to reboot and choose to reboot into recovery (swipe to confirm) Choose to install and select storage SD, In lower right click Install Zip (not image) navigate to where you put the Ubuntu Touch OS zip package click it. Make sure signature verification check is off. Swipe to install Wait until the installation is finished and choose reboot. The device will now boot into Ubuntu Touch OS. ====================================================================================== Preinstalled user account is phablet phablet So If you get asked for PIN or password, type in phablet My first impressions: I could do phone calls in and out going. Wifi and Bluetooth seem to work. Could not get GPS location. My Pro1 has qwertz keyboard. Did choose German keyboard during first setup. Weird: Most keys on hardware keyboard are shifted one key rightward: w is q , e is w ... u is z and so on. In terminal /etc/os-release says its based on "Ubuntu 16.04.6 LTS" I did not try other OSs with my Pro1 yet. As I don't see an OS without disadvantages I personally find Ubuntu Touch OS the most promising. Hope to see progress soon. Does anyone know of a developers repository for Ubuntu Touch OS on Fxtec Pro1? Maybe https://github.com/ubports-on-fxtec-pro1 ? Cheers, #10248
  8. 8 points
    Hi. Since installing the 20200620 update, I've noticed a Wireless Update notification (a plain circle) often popping up for a few seconds then disappearing. It seems to appear pretty much each time the Pro1 gets internet access - i.e. turning off and turning on Wi-Fi can trigger it. I've never had this behaviour in all previous updates. Wireless Update is set to check Daily. Has anyone else seen this too? Is it likely to be draining my battery unnecessarily? Any ideas how to stop this? EDIT: Not just Wireless Update.
  9. 8 points
    I've had my Pro 1 for 6 months now. I use it without a case or screen protector, just a black matte skin on the back to give the back a little texture. It has been dropped a few times. It shows no wear and is still as solid as the day I got it. The hinge has loosened a little over time, as I would expect, but everything still feels properly aligned. I think this phone has a long life ahead of it. πŸ‘
  10. 8 points
  11. 8 points
    Seems an awful waste since a) I have no idea why you think you are entitled to a refund for a smashed phone and b) unsmashed, you probably could have sold it. But if the therapy was worth $700+, glad it was cathartic. By the way, very little of the above has been my experience.
  12. 7 points
    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?
  13. 7 points
    Just installed it and it looks like the certification issue is fixed cause I can now download disney+ 😁 It did not fix my touch screen issues, unsurprisingly...
  14. 7 points
    This is a complicated case. 1. It appears that you confirmed the refund request 1 day after the stock assignment notice (not prior to it). Typically that would be fine, but when we ship devices, it is the busiest time for us, and we aren't always able to react by the time the courier collects your device from our warehouse. 2. To further complicate, the delivery of the Pro1 was accepted despite the "Order completion - device on it's way" confirmation emails that we send. In those cases, we typically expect the customer to immediately notify us to revert the shipment, but it looks like the ticket request remained quiet, and the delivery was accepted according to the Fedex tracking and signature. We've replied to your message on how to arrange a return to our UK location. As soon as we have any indication that the device is on it's way to us, we will issue a refund.
  15. 6 points
    Test17 is up. The only changes are selinux rules and enabling selinux. This is getting dangerously close to submitting for official builds. Please test and let me know if anything is broken. I've verified it boots and the lights hal and FP reader work, but not much else.
  16. 6 points
    I have now processed the refund request for you. We're just a little overwhelmed at the moment, but we should get back to everyone by the end of this week. Workload piling from months of lockdowns has to be done in a few weeks.
  17. 6 points
    As stated earlier, Secure Boot is disabled. So no, security can never be "proper" on the Pro1. But stock software and a locked bootloader should be able to pass corp checks since Android cannot "see" the Secure Boot setting. Android does see the bootloader lock state and pretty much any security type software will flag that as unacceptable. So no, you most likely cannot run Lineage with your corp stuff. And then there's selinux which is not fully working in Lineage yet, so that's another issue for corp use. There are workarounds (such as magisk and xposed), but I would never run them myself nor recommend them. As for using a personal device on a corp net in general, I refuse to do it myself and I recommend against anyone else doing it. Keep in mind that most any corp software is going to require admin access to the device. This means that your corporate IT department can remotely wipe your device. That includes not only all your apps, but all your local media storage (pictures, etc.) All it takes is one guy clicking the wrong thing to ruin your day (or more likely your week). I refuse to give that power to anyone.
  18. 6 points
    Yes, great idea, but please LineageOS first πŸ˜‰
  19. 6 points
    FYI... Apparently my last few builds have included GMS (Google Play Store, etc.) I've removed that and rebuilt. test16 is exactly test15 without GMS.
  20. 6 points
    Yes. I actually wrote the kernel patch to do that, about ... 3 or 4 years ago. I'll apply that for next build. The patch works by watching for the su daemon process. When it is running, everything is normal. When it is not running, the kernel hides the existence of the su binary -- it cannot be detected with "ls" or "stat" etc. except by root. So you just disable root before running one of those (annoying and broken) apps.
  21. 6 points
    test14 is up. Changes: * Fix QWERTZ apostrophe. * Disable double tap to wake. Also updated github repos.
  22. 6 points
    No there's is a difference ... Normal orders are delivered before than pre-orders... Courtesy ...FX Tec
  23. 6 points
    Doesn't look like right. Maybe have been damaged in transit. We'll send another one. Will discuss with you over email.
  24. 6 points
    I don't think it is reputation the manufacturers are concerned about. They care about money before anything else. Yes, reputation can affect sales (ever so slightly), but that is a secondary effect. A primary effect is customer support. And, it is sooooo easy to refuse support for a rooted device. Yes, there are half-wits who have no clue what they are doing and who break their devices ... but these will find a way to root and screw up anyways. On the other side, if the manufacturers and Google would not constantly screw up and give their users more choices/freedom, there would be fewer reasons to root. Android is crippled by greed. Google and phone manufacturers cripple the user experience because it is cheaper not to consider our wishes. After all, "we stupid bunch of idi***" buy their phones anyway. On Lineage, I don't need GravityBox. On stock, GravityBox improves the UI a lot. Google cripples SD-card access more and more with each new version of Android. I do not believe their claim to protect our privacy. I believe they want to sell their phones without SD-card slot and get higher margins from overpriced internal memory. Simple as that. One of the biggest drawbacks of rooting and modifying your system is the update problem due to a modified system partition. Google has a choice in this matter. They could package updates on a file basis for binaries and parse text files (as they did in earlier Android versions?). But they decided to go for partition images ... and took things further by refusing to update when the checksum of the system partition is wrong. Mix in the ability to destroy your encrypted data partition in the blink of an eye, and you have perfection. Another thing that Android does really badly is user control over apps. Even the most simple fart-app is regarded as the most important app by their developer. Hence, most apps start on boot and listen to events like USB-power or WiFi availability to auto-start themselves. Yes, one could say this is the app's fault. But I blame Android for giving apps all these crazy possibilities that no one would accept on a desktop OS. Only root with certain apps can help us users. Again, Google cares only about money from app sales and advertising, and caters to app developers instead of end-users. Talking about advertisement and user control... Google and manufacturers don't like root because they can lose out on precious user data. Some people argue that advertisement is a way to finance app development. I disagree. Advertisements and the collection of user data are the only way to keep a saturated market going. If all apps would be either advertisement free or paid, most apps would cease to exist. No one needs 1000 fart apps. This is the reason why Google does not give us the choice to filter for apps without advertisements in their Play Store. The only choices are paid or free (most often with ads or in-app purchases). In essence, root is not a security issue but a loss of revenue. It is not just apps with root detection. Android itself was made to make root either impossible (by the manufacturer's choice) or as inconvenient as possible.
  25. 6 points
    Catching up on a couple days here... Yes, I'm working with @Digital_Toxin to resolve the locked boot loader. @acrux @schmittlauch I've never installed SailfishOS, so I'm not sure how that would affect the phone. But I can tell you that Lineage uses a different format for userdata (FBE instead of FDE) and modifies boot, vendor, and system partitions. I also suspect that AVB may have something to do with this. Are either of you currently stuck in a place where you are not able to use your preferred OS? @SchattengestaIt the kernel keymap location has been mentioned here many times, eg. here .. use the line from @acrux a few posts up: "47:0026:802b". I will put this change in test14. @schmittlauch nwwn.com is my domain. I don't bother with a http->https redirect because there is nothing that could be considered private there. But https does work and you can certainly use it. Lastly, is anyone unable to boot test12 or test13 who has not installed SailfishOS? I want to try to figure out what's going on, but SailfishOS is an unknown variable to me. The big difference (really, the only difference) between test11 and test12 is integrating the latest security patches. That would have changed the security patch date, which in turn may make AVB unhappy...? After I get that sorted out, I can start looking into why SailfishOS and LineageOS are not compatible (with the exception of userdata, which must always be wiped when changing to a different OS anyway).
  26. 6 points
    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.
  27. 6 points
    test13 is up. Changes: * Updated QWERTZ keymap. * Addressed some SELinux denials. If you have a QWERTY device, there is pretty much no reason to upgrade from test12. If you have a QWERTZ device, please test and provide feedback. Please remember to remove any custom keymap before testing.
  28. 5 points
    5mm hole punch does the job just fine then you can try any material you want.
  29. 5 points
    Just a heads up, according to the support, I will get it shipped in 1.5 weeks. I'll keep you informed if that's really the case. πŸ™‚ 313XX / QWERTZ Paid in August
  30. 5 points
    Here are my tips and tricks for F(x)tec Pro1 Configuring the keyboard layout Right after the initial setup the phone will ask you to set the keyboard layout. QWERTY users should remain unselected and QWERTZ users should select German so that layout will match the physical keyboard prints. However, if you want to modify some keys with pre-designed layouts you can try Fx Qwerty (for QWERTY) and FinQwerty (both QWERTY and QWERTZ) Adjusting the screen size Screen size is not optimal with default settings for landscape use so you might want to adjust it. Go to Settings > Accessibility and select Display size to Small and and Font size to Large. This will prevent cut-offs in the quick settings drop down menu. Preventing unintentional touches Due to the curved display, you might face a relatively large number of unintentional touches. To work around this issue, download Edge Null, which disables touch from the long edges of the screen. The app also has an experimental β€œDetect Edge Swipes” feature that doesn’t completely disable the touch but allows edge swipes. Defining key combinations and shortcuts Keyboard/Button Mapper is a versatile application for defining various shortcuts. The application can remap individual buttons or key combinations to perform desired tasks. Below are a few examples: Function + Esc = Back Function + Tab = Latest applications Ctrl + tab = Divide the screen into two parts Function + up = Volume up Function + down = Volume down Long press on camera button = Open Google Camera (does not work when screen is closed) NOTE! Long press disables a short press on the selected button. However, this is not a problem with the camera button because Google Camera does not support the camera button anyway. Android's standard key combinations are listed in the article below: https://www.pcworld.com/article/184656/android_keyboard_shortcuts.html Forcing applications to landscape Not all applications, such as Instagram, support landscape mode, even if "Landscape Orientation lock" is selected in the Slider settings. However, applications can be forced horizontally with Ultimate Rotation Control (URC, paid) and Lock Screen Rotation (LSR, free). URC in Forced Auto mode and CSR in Lock Landscape mode places screen to landscape with the keyboard in the open position and portrait in the closed position. If you want to rotate the screen while the keyboard is closed, you must do it manually or turn off the application. Camera app For a better picture quality, you can try Gcam ports. Personally I prefer PocoPhone F1 port but the viewfinder is upside down if you select Night Sight. However, the picture is right way in the gallery afterwards. There is also BSG port (with fixed viewfinder) but it does not provide as great picture quality in very dark situations (noise level is bad). PocoPhone F1 port vs. stock camera app
  31. 5 points
    I think people are just surprised to get it at all.
  32. 5 points
    I wound up being shipped the phone anyways a month after requesting the refund... Using it since I couldn't resist opening the box but really wish they could update the software which should have been finalized first.
  33. 5 points
    The release in Japan has also been changed to mid-July.
  34. 5 points
    Secure Boot is a Qualcomm-specific mechanism that enforces the phone must run signed (trusted) code from power-on to the bootloader. This setting cannot be changed by the user, it is a very low level setting that can only be enabled at the factory (and, once enabled, can never be disabled -- it's a hardware fuse). The "device state" (locked or unlocked) is a bootloader setting that may be toggled by the user with the fastboot tool. As far as I know, the Secure Boot flag is not visible to Android in any way at all. I don't do corporate stuff on my personal device, so I can't say why your device can't play on your corpnet. But it's almost surely not due to Secure Boot.
  35. 5 points
    I'd recommend just peeling it off first thing anyway, IMEI isn't really something you should flaunt about. Just stick it in the box or something in case it is needed, but apparently it's not.
  36. 5 points
    Would be nice if they can formally open up a semi-public beta program for end-users to test updates, maybe provide OTA packages there. Just don't do it like BlackBerry who pretty much allows anyone who can fill a form in, at least vet the participants for technical background who can actually help with bugs and quality feedback. I'd gladly help, with my former full-time background as Software QA.
  37. 5 points
    test15 is up. Changes: * Fix QWERTZ apostrophe (really!) * Back out noise rejection bits from DT2W patch * Add su-hide patch Please test. Particularly those that have had issues with the screen failing to turn on after sleep. I would like to know if this fixes the issue or not. If it does not, I'll need to play with the noise rejection stuff and see if I can fix the issue without the visual artifacts on my device.
  38. 5 points
    I just got my Pro1 today (after a really long period of waiting) :-) I am struggling to root it now
  39. 5 points
    Of course :D I need a phone with a keyboard. Got a multiple-times-cracked screen (as it fell down multiple times on the ground without a protection... now I've got a nice leather cover :), but it's still working. And I've ordered a new screen already (and will also offer a replacement service later on). Just waiting for the team to catch-up with the orders so they can deliver more units to distributors. I'll try to find that out... I think I was on test12 before, as I always try out the latest version, but if it just had fixes I wasn't interested in, I might've skipped. It was at least a version after the audio has been fixed :)
  40. 5 points
    I have finally received a (used) Pro 1 too, so I was able to try and play with it a bit today. The ideas in this thread sounded very interesting but I looked for a completely silent method that also reduces the risk of dropping the phone because of the spring mechanism. What I do is I lift up the back slightly and then push the top forwards. That way I can open the phone completely silent as you probably (can't) hear in this video. Also you do need less force to open it. Don't forget to rate my camera setup...
  41. 5 points
    Looking at how your update is named "userdebug 9", I think you got a unit with a pre-production flag enabled of some sort, so yours came shipped with an unreleased firmware. Maybe you can help test to see if the extensive list of bugs are fixed...
  42. 5 points
    Sidekick. What phone don't YOU miss anymore?
  43. 5 points
    Just to update everyone - I have received a new screen through the post this morning. When I get a chance I will attempt to replace it and video it for reference.
  44. 4 points
    I started looking into fixing the keyboard layout boot code and noticed several other things are broken. Basically all the custom device stuff, from the keyboard to the display margin to livedisplay and so on. I'll get that all cleaned up for the next build. Probably tomorrow.
  45. 4 points
    Yes I'm aware of that. I'll be trying to fix su once I move to lineage 17. I'm still running 16 on both my devices (pro1 and 1+6t).
  46. 4 points
    I wonder who was surprised by getting it earlier than expected. I'm surprised that happened πŸ˜‰
  47. 4 points
    Skriv venligst pΓ₯ engelsk, tak!
  48. 4 points
    Regarding root detection and the su-hide patch... The kernel su hide patch was intended for a specific purpose: someone claimed that Lineage su was insecure but refused to provide any details except that it could be exploited even when root access was disabled in settings. The su-hide patch was my response. It is impossible to exploit something that does not exist. πŸ™‚ The patch was never intended to prevent apps from detecting the device has been rooted. That is a cat-and-mouse game and I don't play. If an app insists that it run on an un-rooted device or does anything else that is hostile to the user (such as SafetyNet checks), I don't install it. The way to determine if the su-hide patch is working is as follows: disable root access in settings and then try to access su from a non-root shell (either adb or a terminal app). If the su binary is accessible, the patch is broken. If not, the patch is working. If you want to run an app that does checks which are hostile to the user, please do feel free -- it's your device. You can run xposed and magisk and whatever else you like. But this is not my concern and I will not support either the hostile apps nor the apps which try to hide from them.
  49. 4 points
    @EskeRahn is correct, the A/B system is for updates. Android (either stock, or Lineage when it's official) will install OTA updates to the non-active slot, then tell the boot loader to switch active slots, and then prompt you to reboot. So no, by default, you cannot use A/B for a dual-boot system. Additionally, there is only one data partition. So any dual boot scheme would require some way to separate data A from data B. And lastly, you would probably want some sort of a boot manager to select the slot at boot time. So in theory, it would be possible to make the phone dual boot. But it would take quite a lot of work and each OS would need to be customized to make it compatible with the scheme. I'm not sure that would be the best use of time right now. Maybe later, after everything else is working reasonably well.
  50. 4 points
    My second order #32*** is on the way. (paid late August 2019) YES YES YES
×
×
  • Create New...

Important Information

Terms