Leaderboard

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.

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 anyt

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.

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

That did the trick - test16 booted OK! So that was the reason for non-booting system for those without gapps... Thanks a lot! Now to test qwertz keyboard 🙂

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 🙂

Beautiful, so far. Manually sideloaded Test 15, MindTheGapps and the su addon, changed theroot setting to apps and adb and gave permission to Root Explorer and Titanium Backup and away I go. I'll let you know if I get any more phone turning off, but tbh, that hasn't happened in a few days anyway. Lol. I think it's time to buy @tdm another 6-pack. 🍻

No, it is not opt-in/opt-out. But it does not break anything either. It works like this: If root access is enabled for apps in settings, the patch does nothing -- su works normally. If root access is disabled for apps in settings, the su binary (/system/xbin/su) disappears. You cannot see it with "ls" or "stat", it cannot be run, etc. It simply does not exist. Note that root access for adb still works in both cases, as it does not use the su binary.

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.

@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

Order No. 18151 (June 21, 2019) - QWERTY Received phone on: June 10, 2020

Mount /system r/w with "adb remount". Then edit the file /system/etc/prop.default. Change the following properties: ro.adb.secure=0 persist.sys.usb.config=adb Reboot and hopefully logcat will work from early in the boot process.

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

Had pretty much the same happening with the app from the insurance "Signal Iduna" with all unrooted Lineage test versions I used so far. The app just said my device was rooted and wouldn't start for security reasons. So either their check is wrong or their message is lazy.

I think the error message is inaccurate. I get the same on a LineageOS 16.0 Test15 that has NOT got the root addon installed. Maybe it is trying to say that the device is not certified or that it does not pass the SafetyNet test. ADD: Checked that It opens without this on Certified Stock even with an OTA not passing SafetyNet. (So the important part of the message is the next that it expects an "official Android")

Thanks, I never knew that existed. I'll have to give it a try. I'm not a big fan of Magisk, but the only instructions on this forum were for Magisk. Is the right one Arm64 or Arm?

No, I am talking about the Official(tm) LineageOS superuser add-on from here. I do not use or endorse any other su package, and I absolutely don't touch magisk at all.

Thanks for the recovery log, but unfortunately that is not really helpful -- it only says that the Lineage install succeeded. I need a logcat of Lineage (trying to) boot in order to figure out what's going on. This will require some tweaks to enable logcat at startup. If you are comfortable hacking on your phone with adb, we can try to do that. Alternatively, perhaps you can tell me exactly which version of stock you were running and maybe I can reproduce that here.

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.

No there's is a difference ... Normal orders are delivered before than pre-orders... Courtesy ...FX Tec

COVID has really screwed with things regarding shipping, I've done a lot of orders in the last few days (Including a Pro1, Order #55xxx) and yeah, some places you simply can't ship to/from at the moment for a reasonable cost. (eg. I've got some used PC parts coming, PhysX PPU from Texas? No problem. Radeon x1950Pro from England? Not an issue. A second x1950Pro from Germany? Fifty Euros to ship to Australia because we have to pay for premium shipping to get DHL to ship here.) I wouldn't be surprised if some of the skipped over orders had something along those lines going on. It really s

orders and preorders = same = waiting and waiting 😄

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

Well in theory they could offer the uncertified software, but I bet a lot of users would be quite angry if Fxtec deliberately prevented people from using their banking app and the like requiring the certification.

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, bu

Yes it is really close to fitting, so if someone wanted to let the adhesive go directly on the Pro1 that extra 1mm might be enough for it to close. 🙂 Had it been me, I would venture the bend. Say over the edge of a table using some books or small blocks of wood, like this sketch

The Dux Ducis Universal case arrived (this is the 5.5-6" version of course). Overall not great, not terrible. The Pro 1 is just way too thick of a phone lol. In size it's almost identical to my Priv case which is very good because the previous Puro case was considerably bigger to the point it was almost very pocket unfriendly, just like that pre-order pouch. I put the Huawei P20 Pro silicone on the glue, it holds alright. (sorry about my horrible cutouts..sadly I don't have precision tools and this was done with small scissors) Sadly the case can't close na

Hello, I just got my pro1 and I noticed that with the screen brightness pretty low, the darker colors look terrible. Mostly the dark greys look green or kind of crunchy. Is there any display setting that I'm missing that can help with that?

This morning it went mad again. Turned it off for one hour did not help. It's unusable ATM. I have to contact support.