Hook

To be fair, that's Android 11 that messed that up. Lineage just seems to be using the same setup rather than modifying it. At least you can still get the full reset menu (system, Recovery, Bootloader).

I jettisoned Microsoft Office and started using Softmaker Office years ago on Windows, Linux and Android. I have the full up paid version of the office suites for Windows and Linux. The old Android version was good but stopped being updated around 2017 and the cloud sync broke. The new beta for Android ia wonderful—I was involved in the beta test from the beginning. This allows me to keep my work in Dropbox and pick it up where I left off on any platform. They have done a masterful job. Upside: All but a few features will be free (IIRC, printing from Android, covert to epub and conver

Also, be aware it's the device that is under warranty, not the specific user. If you or anyone else sells the device to another user, that user is still covered by the warranty.

No, just an HTML formatted email right after I paid.

Back on August 1st, 2019, I received an email invoice for my payment of my pre-order, but as someone who has used their warranty repair service, I never needed to use it. In general, they can access all your info using your email (presuming it's the same one you used when you purchased).

Not long enough to be a firm answer, but it's been two months since my screen replacement (by them in London) and it solved my problem.

There must be some way to get the security updates into older releases of Lineage. My old old Samsung Galaxy Tab S is still on unofficial Lineage 14.1, maintained my Dark Existence on XDA and continues to get current security patches. This is obviously not Lineage doing this, but it suggests the patches can be obtained and compiled into the OS. So the question (the answer to which is way beyond my pay grade) is can this be done for Lineage 16? Is there a source for the security patches or is the XDA dev extracting them from later versions of Lineage or... For reference:

I suspect the parts are delayed because it is cheaper to order the parts when they are also ordering them for assembly of the Pro1xs at the factory... volume discount and all that.

Not sure what you mean by "special care," Updating via sideload is: 1. Boot to recovery 2. Adb sideload (name of nightly update zip) 3. Reboot to recovery (this changes the slot to the slot where the new update was installed) 4. adb sideload current Magisk zip (no need to reboot to recovery after this step) 5. adb sideload Gapps package zip. 6. System reboot. I have no idea if steps 4 and 5 are necessary if you are just updating, but they take little time and they can;t hurt, so I do them. None of this disturbs your user data pr anything you already h

Again, I've only ever adb sideloaded the updates, as well as reflashing Magisk and Gapps. It has always gone smoothly for me with both Lineage and AICP.

I don't have experience with Magisk and OTAs although my impression has been that OTAs don't bother it. I sideload the weekly nightlies (I know, that sounds wierd) and after rebooting to recovery to change slots, I flash the Magisk zip. I don't think I have to, but I tend to be thorough, and it is so little trouble. I do the same with Gapps even though I don't think I have to.

It seems to be pretty basic. Just the service framework, store stuff, google search. No calendar, contacts, maps, gmail, Chrome, etc. Anything you want to add you are left to download from store, but they aren't installed as system apps. It may even be equivalent to pico, Very few Google apps, which is what I want too. I don't use many Google apps.

That must be a tiny hand holding the phone in the first image because if I put my hand around my Pro1 with the same hold, the Pro1 doesn't look any bigger in relation to my hand. 😉 Which is why I love the size of the Pro1 and have never been able to use portrait keyboards. But I'm really glad to see so many keyboard phones being attempted.

Did you wipe userdata? And did you flash both the a and b partitions. I did hit that wanting a password problem once but it has been so long I don't remember the solution, but i think either erasing userdata or flashing both partitions (or both) saved the day.

I agree completely. But this, in my experience, is how most ROM developers work. Once they move on to the next version, they drop all support for the previous versions. However, some ROM dev teams are much more careful about where to draw that line. The Dirty Unicorns team, probably the best ROM I ever used, would take ever so long before they would declare a new version official and they would maintain the previous version for all that time with security updates even though they weren't doing anymore work on the previous version.

Really, aside from the car BT thing (which also existed in 16, I never got around to trying 17), 18.1 seems to be working fine for me Then again, I don't have the keyboard issues because I don't do international stuff. But really, it seems fast, smooth and stable on my Pro1. It is true that I am here largely for the security patches and if @tdm ever returns to updating AICP I will probably go back to that, but Lineage 18.1 makes a great daily driver for me so far.

Actually, I've gone ahead and deconverged. I didn't realize Android Auto depended on the BT for phone stuff and it will not send the phone to speakers and microphone in the car no matter what somersaults I do with the Pro1, Lineage, or the car's dashboard software. It's just a deal breaker. So I will use my Moto G8 Power as a phone and in my car and use the Pro1 for everything else. It's an arrangement I had already been doing when I couldn't get Verizon working in Lineage on the Pro1, so I'm already used to it and the functional split is very clear and useful. I am planning to get the Pro

That's the way it was on mine. I even got fooled by the coincidence of installing AICP and the demons, as I called them, went away, I think it was for a couple of weeks, but then they came back full force, like they had gone off to training camp and my Pro1 was unusable again.

Updated to lineage-18.1-20210405-nightly-pro1-signed.zip via adb sideload. Everything went smoothly. Still March 2021 security patch.

Never mind. I found it with help on Discord. Vol- + Power, quick click on both. Kind of awkward in landscape. 😏

Okay, I know this is a little trivial, but has anyone figured out how to do screenshots in Lineage 18.1? There is a srceen shot button that appears in recents, but that only takes a shot of whatever recent is over it (so, for instance, you can't screenshot launcher since that never appears there). It doesn't appear on the power menu and I can't find any way to add it. There is also no quick tile for it. Am I missing something (I assume yes)? 😉

Make sure you are looking at the display only option for those Elephone screens. The frame won't work on the Pro1 because those are different (The more expensive screens sold by FxTex include the frame with the display already mounted). With the cheap replacement display, you have to remove the old display on the pro1, which is glued, from the frame and then glue (it comes with adhesive strips) the new display into the frame.

Me either, but since Android Auto works perfectly, I can get everything I need that way. But, yes, the BT in the car thing is frustrating. It might make me switch back to deconvergence (using my Moto G8 as phone and Pro1 as PDA) if I ever take a long trip again.

I did a clean flash. Flashed the new 18.1 recovery to bootloader, rebooted to recovery, did a factory reset/data wipe, then flashed 18.1, Magisk and MindTheGapps, reboot. All smooth as silk (takes me only a few hours to rebuild). Verizon works right out of the box, as does Android Auto. I tend to do clean flashes when moving between major versions. You can get away with a dirty flash sometimes, but I believe it's risky. That's why Lineage doesn't let you move via OTA. Oh, and yes, each nightly updates the recovery, I believe.

Sorry it took me so long to get back. I only just got back to setting up, but so far everything is going smoothly. I expect the rest to go well/ One big surprise is that Verizon works, right out of the box. I had meant to try 17.1 when 18.1 hit, so I decided to try it on a lark. No muss, no fuss, no hoops, just followed windraver's instructions in this post: I'll continue to monitor, as I had it working on stock for 3 months long ago, but this just worked and before I had to do a complicated dance. I think it may be right this time. Everything so far is working great. Next t