tdm

Maybe. Stock imposes some restrictions: you cannot modify /system or /vendor. This makes things more challenging.

Firefox does indeed lock rotation occasionally. I see it on my 1+7pro sometimes. You just need to kill and restart it. Also, I generally like to keep some diagnostic tools on all my devices which can help figure out issues like these. Sensor Box (for all sensors including rotation), GPS Test, and NFC Tools frequently come in handy.

It's still on my TODO list. But I am writing an Android based backup/restore solution first. This will be much more flexible than TWRP. Check the AICP-Q thread.

Your phone is already booting to EDL mode. This is what you are seeing in the USB dialog. Specifically, "Qualcomm HS-USB QDLoader 9008" is exactly what the flash tool requires. Now, why did it all of the sudden decide to do that? I don't know, but there is likely some underlying issue. Perhaps a dead or dying flash chip or worse. But using the factory restore tool is a good first start, along with starting an email thread with support.

Yes, it should work just as well as gapps and su for any LineageOS version. This includes "stock" on the Pro1-X... which, as far as I know, is just going to be a normal LineageOS weekly build installed at the factory.

"Stock LineageOS" is a bit of an oxymoron. It will install on LineageOS via the add-on mechanism, just like gapps and su. I will provide that add-on, you will not need to compile it yourself. But it will be open source, of course, so you can compile it yourself if you want. If you are asking if Lineage will incorporate this into their builds ... I cannot answer that. They are currently planning to use SeedVault. But SeedVault uses the built-in Android backup API which allows apps to opt-out of backup and restore. This is a fatal flaw for me and many others. So perhaps they

It will work on any custom Android version including Lineage. I plan to package it as an add-on, like the su package.

A brief update... I've been working on a backup/restore solution for Linux (plus an Android app to drive it) that will be able to do full backup/restore, similar to TWRP. This is a bit of an involved project, but it will be well worth it in the end. It will be cosmetically similar to tar on the command line to make it familiar to use, but it is an entirely new code base. Some of the features include: A client/server mode for use in Android and other privilege sensitive environments. Built-in compression and encryption support. The Android app will mo

I could check into it. Shouldn't be hard.

Try switching active slots? I've heard rumor that slot B may not work.

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?

My guess is that the wlan kernel driver is causing this. I'm sure it got updated.

You can try and let me know.

Both run just fine without gapps.

AICP is not Lineage based. It does incorporate a lot of the QCOM hardware support and a few other things. But it specifically does not use the Lineage SDK. And I think the telephony stack is more similar to AOSP than Lineage. So it is quite possible that VoLTE/IMS is working on AICP. Though I haven't tested it myself, as my carrier still won't work with this device. 😕

Oh reeeeeally. That's very pleasantly surprising. Especially when it's broken on Lineage. Thanks for letting us know. 🙂

VoLTE is currently not working on 17.1. The developers are looking into it.

I don't know, but my guess would be probably not.

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.

Figured out the issue with the keyboard backlight. Lineage decided they wanted to add the keyboard backlight logic into the Android core (frameworks/base) and delete the keyboard backlight logic from the lights HAL. This is Lineage specific -- neither AOSP nor AICP have it. I made a brief attempt to add the Lineage code into AICP's frameworks/base but it didn't go smoothly. So I'm just going to revert the change and move on. I hope to have a new build within a few hours.

I found the issue with the incremental updater. We will try that again with the next build.

Okay I'll look into that next.

Okay I've uploaded the file and pointed the link in the OP to the new one. New MD5: e6d57186599ab0177a48fc3984c6ae5b

It must be broken. I'll check into it and upload the full zip later. Thanks for testing.

Settings, aicp extras, update center.