tdm

Hmm, interesting. Is anyone else seeing this? I certainly don't notice it. Also FYI... the first build missed a kernel configuration to enable EAS (the Energy Aware Scheduler, a key part of the new power stuff). So that may be causing some performance issues. It's been fixed and the next build will have it enabled.

Perhaps it is the animation speed? Go into developer settings and set the animation scales to 0.5x. That should feel faster.

The phone works perfectly fine on reasonable GSM carriers. Verizon is neither reasonable nor GSM. Your fix is to switch to another carrier. T-Mobile, AT&T, or any of their MVNOs work perfectly fine. I'm on PureTalk which is an AT&T MVNO. Paying $80/mo for four lines. Or, if you insist on being abused by Verizon, I'm sure someone would be happy to buy the phone from you.

Perhaps your PC is having issues with USB? Lineage supports ADB over network. I frequently use this instead of USB because it is super convenient. Enable developer settings (tap on build number 7 times), then go into developer settings and enable ADB over network. The adb address will be shown. On your PC, run "adb connect <address>".

It is because A/B. See this link: https://source.android.com/devices/tech/ota/ab/ab_faqs#if-youre-installing-an-update-while-the-system-is-running,-isnt-that-slow Incremental OTAs are much faster, but don't work with addons. I would like to fix that at some point.

If I were you, I would install test22 first, before the nightly. It is what others have done, so it is known to be working.

Yes it is the complete factory package with the modem and everything else, just as you would get from the OTA.

Just redo the test22 install, following the instructions as if it were the first time. That is, flash the boot image, boot into recovery, flash test22, reboot recovery, flash gapps, reboot. If you booted into Android without gapps, various Google apps get unhappy and may need to be removed and reinstalled (like hangouts, etc.) But your data should still be there.

To be clear, fastboot talks to the bootloader and that is never changed by Lineage (or any custom OS). I merely specified the suffix _a/_b to make the user aware of exactly what is happening. You have always been able to fastboot flash any partition without the suffix. It just writes to the active one. But you may not know which one is active, so I considered this a bit dangerous.

The former. Basically update just like you always have with my test builds, but using the official zip. When you reboot into recovery to install gapps/su, you will be in the official recovery. You can tell because should see the version string show nightly instead of unofficial and adb shell will be unauthorized. And when you flash gapps, it will complain about the signature (but it will let you proceed anyway). After gapps installation, reboot and you should be running the official build without issues. This is all theory .. I haven't actually done it, as I typically don't ru

I have created an official LineageOS discussion topic: https://community.fxtec.com/topic/3037-lineageos-160-official-builds-discussion/ This thread should die down and the new one should take over.

Oh, I see. I honestly never really look a the Lineage wiki. I just assume that it is clear and correct because it is used by so many people. Again, if you or anyone else finds issues that need to be addressed, both myself and @npjohnson can assist in getting the text fixed and/or updated.

I am pleased to announce that the Pro1 has received official support in LineageOS 16.0. You can find the builds and installation instructions on the official LineageOS Downloads page. Please note that LineageOS does not include the proprietary Google apps (aka. "gapps", Play Store, etc.), nor a "su" binary. These are "extras" or "add-ons". You may use any appropriate gapps package for Android Pie. I personally recommend MindTheGapps which can be found here. LineageOS maintains an official su add-on and a couple other extras here. Note the Pro1 is arm64 and be sure

Guys, I appreciate the critique of the wiki. But please do note that virtually everything except the device specifications are templates that are linked -- I did not write it. Here is the actual code for the Pro1 device page: https://github.com/LineageOS/lineage_wiki/blob/master/_data/devices/pro1.yml Notice it says "install_method: fastboot_nexus". That means the recovery install instructions come from here: https://github.com/LineageOS/lineage_wiki/blob/master/_includes/templates/recovery_install_fastboot_nexus.md Also note it says "is_ab_device

The LineageOS nighly builds on lineageos.org are the "official" Lineage builds. I have imported the code for test22 to the Lineage github, so they will be functionally equivalent to that (at least to start, we will continue development there). There are only a couple differences for official Lineage builds: They are signed with a "real" key, not a "test" key. This is more secure and will make the Trust warning go away. I have a couple changes to my code locally. Nothing you should really notice except for a small anti-spam hosts file. Signature checking and adb auth is di

Yes. Just be prepared for the OTA install to take nearly an hour.

Just ignore the warning.

This is expected. The official lineage recovery has stricter security. I have a patch in my build that disables adb auth in recovery.

The OEM/stock kernel sources are here: https://github.com/tdm/android_kernel_fxtec_msm8998/tree/oem-history This also exists as history in the Lineage tree, but it is not a separate branch. You would need to go find that commit manually. As for fn+alt, I don't think I ever considered that combination.

Better is subjective. But there are many fixes and features. Not sure what your issue is with the camera. EdgeNull is not needed, I added my own solution. Don't know what Audipo is. If you are interested, give it a try. You should not expect people here to give you a sales pitch.

Probably Nolen's. I'm taking a break for a bit to do other stuff and he is still fresh and energized.

Precisely. Google makes Android and publishes the sources. The LineageOS team takes those sources and fixes bugs, adds features, etc. Of course it is more complicated in practice and I left out all of the history. But that is the takeaway.

The intent is always for updates to keep you addon packages. But when the A/B system arrived, the lineage folks only got this working with OTA. They haven't yet figured out how to make it work with sideload on A/B devices. So yes, if you switch to OTA updates, your addons will stay. And no, you don't need any particular version except the correct one for your Android version. You will need to install the first official build via sideload. After that, OTA works and keeps your addons.

Oh. Interesting. I did exactly that and it was fine. Try rebooting into recovery and install gapps again?

This is kind of off topic, but something to think about for future testing of 17.1, perhaps. I got my OTA server running and tested it with a full (not incremental) update. Took roughly 45 minutes from the time the download completed. Google intentionally makes this process low priority because you are expected to be able to continue using your phone normally while the update installs. But there is an updater option to increase performance which helps some. It would be much faster, both for download and install, to do incremental updates. But incremental updates req