Leaderboard

PSA Updating to Sailfish 3.4 The update to Sailfish 3.4 on the Pro1 is much anticipated. Not only will it bring the great features in 3.4, but it also bring encrypted home partition for added security of your data. While this is a great feature, it is also not straight forward to implement, requiring a completely different style of installation to previous releases. Because of this, it is not possible to upgrade an existing 3.3 release to 3.4. The 3.4 release must be flashed onto the phone, after which it will be possible to restore any backups taken. Trying to force an upgr

Anyway, the 8/256GB upgrade could be solved regardless of the other parts like the black colour. The question is if they have the PCBs already manufactured or they are still pending as if they were manufactured then this upgrade will not be possible.

Thanks for the tip. Could well be related. It works fine on AICP-Q though, restoring Google's own extremely limited backup (from Stock Pie). The difference is that I upgraded 16.0 to 17.1 without a wipe, but I did do a wipe from 16.0 to AICP-Q, before the restore through the wizard. So could be some settings from 16.0 that survived. For now it seems stable after the AutoNotification uninstall, will report back after some time if it is merely luck that it has not booted (yet), or I found the culprit...

In the past, I usually ran in to the issues if I recovered a backup from older Android version to newer (9 -> 10). Android does not handle backups very well so every time I install new Android version I start from scratch. I don't know if that was the reason on your case.

If I actively try to put it to sleep with the power button, and not just wait for it to time out, it most often boots... I had a suspicion to Greenify, that acts in this scenario, but stopping it before, does not change the behaviour. ADD: Tried to disable the Accessibility of any apps granted that (3C battery monitor, Greenify, Android Assistant) - no difference. Any logs that could benefit anyone before I wipe it clean? Went one step further and stopped every user app running, and found the culprit AutoNotification, that came in with my backup from Stock, after uninstall, and re

I agree. I'm just going to be patient and wait for my screen (Hook screams into bucket and goes back to his slab phone) 😄

I know this type of threads got heated - anyway, I got response from fxtec support today concerning my 2nd piece order on Aug/31/2020, find as below. i.e. ETA next spring. FTN00b22, if you place order now and you are lucky, you will get it next summer. The most realistic estimate we have at the moment for another batch, which will include your order is between January 2021 and March 2021. We're very much aware your device should have arrived by now, and we're sorry we haven't met the previously suggested estimates. We want you to try the Pro1 for yourself more than a

It depends on how you update. Recovery and OTA are completely separate. Which did you use? Either way, the data partition should not be touched by the upgrade. Can you spot any pattern with the missing apps? eg. are they all Google apps, or are they all large apps that have auxiliary data, or some other thing?

To me it looks like that there will be only two production runs left and next batch is going to be shipped in December. I think that "Pre-Christmas Pro1 X" backers (10 units) will be included in this run since they are also 6/128GB models. Then there will be probably the last batch in Q1 2021. It should include all the rest Pro1 orders and Pro1-X orders from Indiegogo. I am just wondering if they still want to manufacture so many different versions? Pro1 6/128GB Black (2 layouts) Pro1-X 6/128GB Blue (4 layouts) Pro1-X 8/256GB Blue (4 layouts) Note: QWERTY is d

New build is up, the link in the OP is updated. Changes: * Fixed keyboard backlight. * Fixed incremental file update. New MD5: 8d557ea563667d1332dd99729fa5e4ca This is a full update because the existing incremental updater is broken. Future updates should be incremental and automatic, if all goes well.

In my opinion LineageOS 16 was a very important OS for the Pro1 that brought the best out of the device at a moment when stock couldn't (yet) . Although not a developer, I can well imagine it also broke the ground for all future releases of Lineage on the Pro1. So, I guess this is an appropriate moment to thank @tdm for all the hard work!

In the above I think you forget a very important commercial aspect: Many (most?) apps are sold as 'free' by being infested with ads, and for some by stealing data. That model would not work if people had complete control and could easily remove/block the ads. E.g. by blocking or restricting network access. In that sentence you quote the app developers are the "content providers", so I don't think I forgot them in that part of the post? This is precisely why they have that veto right in the Android security model, so that they can retain control over their content, be it the App i

I'd like to add a bit unto the things @daniel.schaaaf and @tdm already said, with regards to how Google interprets "security". There is a paper by Google employees where they explain the Android security model, it might even be an official Google position (though I am not 100% sure of that): https://arxiv.org/pdf/1904.05572.pdf#section.3 That paper is quite interesting, they include a detailed threat model (which finally explained to me why Google considers a locked bootloader as a critical security feature for regular end-users) and it is not even that old, it refers to Android 9.0.

I agree with most of what you said. Except perhaps the part about comparing app permissions to a desktop OS. Every desktop OS allows apps (we used to call them programs or executables, remember?) to do pretty much whatever they want whenever they want. Please note that there are two distinct meanings for "secure" / "security" in terms of a device. There is security from the corporate perspective, which includes things like DRM and evidence of tampering. And then there is security from the user perspective, which includes exploiting vulnerabilities, hacking, malware, etc. Whene

@tdm Do you know if LineageOS creates a log file when updating? I updated to 10.0-20201026 (OTA), and now a lot of my apps are missing. The corresponding directories in \data\app are gone, even though the app data in \data\data is still there.

Well, they did not complete all January 2020 orders, I have payed for pro1 (qwerty) at 20-th January 2020 - it is still in "Processing" status (order number 48416).