tdm

No I've been off doing other things. Maybe one day...

Maybe you can try this... I just uploaded it and will merge to 18.1 in a few days after I clean it up a bit. https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/316402

You should be able to use pretty much any recovery to install it.

This is now official. Builds are weekly, currently scheduled for Wednesdays. Install instructions are exactly as LineageOS 18.1. Download site: https://dwnld.aicp-rom.com/ Enjoy!

This is most likely a kernel issue. I am using the Lineage 17.1 kernel as-is. I'll investigate.

Oh my fault, I was thinking lineage. Did any previous aicp versions ever work properly with HDMI out?

Sorry, the Lineage admins don't allow exFat unless the device shipped with it.

What is the date of the last working build?

I still have the AOSPX 9.0 tree. They were working on rebasing 10.0 at the time I was building it, so I never did an AOSPX 10.0 build. Which do you guys want, 9 or 10? There are pretty much no changes in 9 since the initial build.

Yeah split screen seems a bit buggy. I think R is far enough along that any bug reports should probably wait.

I've not seen the OTA updater crash. But then again, I don't use it much and never with official builds. What crashes and when? Can you get a logcat of it crashing?

There have been rumblings of starting official release builds, so I'm guessing in the next couple weeks.

It builds off Lineage, so I will just wait for Nolen and Bruno to do the hard work... 😄

Indeed, all your data is still present. Do not believe any messages that tell you otherwise. The Pro1 is an A/B device. If an update fails, you should be able to go back to the other slot using fastboot. There are myriad pages on the internet about where to find the fastboot binary for your PC and how to enter fastboot on your phone. Once you are ready, simply run "fastboot --set-active=a" and reboot. If that does not work, try "fastboot --set-active=b" and reboot. Alternatively, @claude0001 is correct. You should be able to manually install the latest nightly. I

Yes the link in the op is always up to date. It is a symlink on the server. I'll add the link to the actual file and the md5 hash for clarity.

New build is up. Build date is today, 2021/02/06. It is available via OTA (settings -> aicp -> updates) or direct download. Changes are virtually all security/bugfix updates, updates to the adblock hosts file, and language translation updates.

Settings -> AICP Extras -> Update Center. You will get a notification when a new build is available. This is for the kernel keymap, by the way. I posted some instructions a long time ago in the Lineage 16.0 thread. Perhaps someone can find them. Here is the exact file location: https://github.com/LineageOS/android_device_fxtec_pro1/blob/lineage-18.1/devicesettings/src/org/lineageos/settings/device/Constants.java#L27 By removing it, I meant the toggle in the UI. The system should still read and apply a custom keymap, but providing an option to disable

Here is a good place. Or if you prefer discord, perhaps we can make an AICP channel in the Pro1 discord. Or we could make a Pro1 channel in the AICP discord. I doubt this is AICP specific. It is more likely an issue with hardware or kernel. Again, this is most likely a hardware or kernel issue. There is an OTA function. This is an unofficial build, so there are only updates when I choose. And I have been busy with other things for a while. All the developers are working on R now, so Q is pretty stable. There have been a few security updates since the last build,

First, keep in mind that EDL is a "one shot" protocol. You must reset the phone between each attempt. You can tell the phone resets in Windows by watching the notifications and listening for the plug-in sound. In Linux, run something like "watch -d lsusb" and you should see the device disappear and then reappear with a new device number. Things to try: Use a different cable. Use a different port on the PC. Try with/without a hub. Try a different PC. Note these issues are not specific to Pro1, this is common with EDL. I recently used EDL

I don't know exactly what blobs you are talking about. Can you be more specific? But generally AICP is pretty lenient with their policies.

Setting aside that /e/ is basically a rip-off of LineageOS, the TWRP referenced in the Sailfish thread should work for this purpose. If not, perhaps @Sean McCreary or another developer can help. I simply don't have the time or desire to build TWRP right now.

Not currently. If I could decrypt data, I'd have a decrypting TWRP released by now. 🙂 I am hoping that backing up an FBE encrypted data partition (eg. while in recovery) and then restoring it in the same environment will work. But I have to test that out.

Well, the standard Unix-y part of it will be a CLI tool with arguments more or less like tar. But the backup and restore arguments will likely be limited to block devices and directories, though that is not certain yet. Block devices will be backed up as a single unit of data (as you would get with "dd") and directories will be backed up recursively (as you would get with "tar"). It will also have a client/server mode similar to rsync, which will communicate over sockets (meaning remote backups are possible without using tools like stdio pipes or sshfs etc.) Android will surely

Yes, backup and restore is far and away the biggest thing people want out of TWRP over and above the "standard" recovery. The main thing I'm working on now is an archiver. It will be able to backup and restore directly from Android, no recovery required. Among other things, it will feature compression, encryption, incremental backups, and both local / remote storage. And it will work on any Linux system, not just Android. I plan to use on my own systems once it's working well.

You would be amazed at all the things that need to align for two revisions of the same model device to get the same updates. Not saying it won't happen, just warning you that it is not as straightforward as it seems on the surface.