Hook

I sideload Magisk 23.0, but I only use it for SU, I don't use any modules. I don't even open the manager. To do this, I use the depreciated method of renaming the apk to zip and doing adb sideload. That's it. I don't have to do anything else and Lineage boots fine. The SU function also survives OTA updates.

In Lineage 18.1, just pressing the left Alt key seems to work, unless (this is just a theory) the app takes over the keyboard assignments. So, for example, Google Messages (sms), Aquamail, Facebork Messenger (don't judge me, Mrs. Hook insists on using it) and a text editor,Markor, will all give me an emoji pallatte when I press left Alt. However, Softmaker Textmaker, which hasit's own key assignment shortcuts, does not. It may depend on what soft keyboard you are using. I use the AOSP keyboard and it has an actual setting to have emoji appear when using the physical keyboard.

One other possibility-- I've seen people here talking about charging from being fairly low battery. I never drop below 40% and am usually above 50% (what can I say-- I'm retired and I don't go anywhere 😄 ). It could be the struggle is recovering from very low battery.

I am updating weekly and not seeing this problem. I just updated to the 16 August nightly, although there isn't much in this latest update.

Just to note, I never shut down my Pro1. It just gets a weekly reboot with the update.

I'm also am curious if they are doing this with pre-pay, which has always tended to be more open to strange and international phones, or if it's just post-pay.

I'm having no charging issues with 18.1 (I update weekly). I tend not to let it drop lower than 40% and I use slow charging from a USB 2 powered hub.

If you are talking about Android Auto (maybe it is called Carplay outside the US?), yes, it requires Google Play services. Google maps too. However, music and phone should work fine over BT alone, but you'll need an alternative method of navigation than google maps, like a GPS unit (or in-dash navigation).

I seem to recall, but don't remember from where, that the update doesn't work with Android 11.

See my reply above from March 29th, It still pretty much applies. They have kept their backers informed with monthly updates. If you are not ordering an already manufactured phone that is already sitting in a warehouse, there are no promises, only projections. And those projections are based on not much going wrong. You may regret the investment because of the time it is taking, and that is understandable, but they are being transparent about the sources of those delays.

"Post-Paid" and "Contract" are the same thing to me. They tend to have more restrictions than Pre-Paid. I have never done contract or post-paid since I always pay for my phones up front.

How very odd. Is this contract AT&T or Pay as you go? I used AT&T pay as you go (under various names going back to Cingular Wireless) and they never cared what phone you wanted to use. I had mt Pro1 on it for a year with no problems, but I finally switched to T-Mobile because they have a very good low price Pay As You Go plan. Here's a thread here about Verizon. The recommended instructions worked fine for me once Lineage fixed a few things. The trouble is you need a "mule" phone that you can activate woth Volte before you can insert the SIM in the Pro1. You can't u

I hope he's okay. Seems strange that @tdm would just completely stop communicating. 😕

I'm sure I'm about to hex myself by posting this but, no case, no screen protector, no broken screen (though it was replaced by FxTec in January for Ghost Touches). In use since December 2019. For me, the true lifesaver is the textured Dbrand matte black skin on the back. Best shatter protection is having enough grain on the back to prevent it from sliding easily either out of your hand or off a surface. That, and not being in a blazing hurry when handling it. 😉 I do have 2 AlieExpress replacements waiting in the closet for the day when you all get to point your fingers and laugh

The July 19th update with the July 2021 security patch installed smoothly via OTA. Root retained.

True, but I believe the security update was April 2020, which was the yardstick I was using. 😉

Sorry, I did say that with a bit too much certainty. I have no official source for that, but now that they are focused on developing for the 662 SOC and, given that they have not provided any updates for over a year, I find it unlikely that they can spread their limited resources to providing updates for the 835 SOC. Would love to be wrong. As @EskeRahnpointed out, Lineage is currently required to keep the Pro1 up to date and I have happily gone there.

I no longer have an active AT&T sim to test, but my sim always worked fine with LTE. I think I had the preferred network set to Global. Also, try checking the Access Point names. I forget which one I used, unfortunately. Unless LTE where you are uses a band not included on the Pro1 (like band 71), I have no idea why you would have a problem with LTE.

Interesting. So AT&T on the contract side is getting fussy about this. I still recommend you take it in to the techs in person and see if they can work it out. PAYG is not a bad idea. Also check T-Mobile coverage as they are a good alternative (I would look at PAYG there too). I am currently using T-Mobile on Lineage right now myself, just FYI.

All I can address is that on mine , the dialer app is fine. I don't have any Microsoft apps.

Yeah, I'm not sure what that means. The message is IMEI is not recognized. But we have both had the Pro1 working on AT&T, so I really don't think that's the issue. I don't realy know much about how IMEIs work, but I think that message amounts to "your phone is not in some database we use so we don't know if it works on our network or not." I used AT&T PAYG under various names for years and never had the impression that they ever did phone model limitations like Verizon did. If it's got the bands their network uses, they'll take your money and go. I admit I have no experience

I assume you have Post-pay AT&T servivce right now. If so, that is why the BYOD check is complaining about the IMEI-- it is already locked to an account. I don't know if you have other phones on this account and therefore what options you do or don't have. One possibility would be to take them the spec sheet with the bands listed. If you don't have other phones tied to your account (like a family plan), one option is to switch to Pre-pay, either AT&T or T-Mobile (porting the number). But if you get a good in-person tech at AT&T, given the specs, they should be able to

The Pro1 certainly won't be updated, but I'm still pretty sure the contractor is working on the Pro1x, whether the same contractor or a different one. They most likely had to initiate a new contract. The contractor does the initial development job but is pretty bad at any maintenance follow-through. I assume that will probably be true for the Pro1x as well-- it will get an initial not well refined version of Android (probably 11) and will fall behind over time. I suspect they don't have a lot of choices of contractor and that they have no clout at all being a very small company. They get w

I think, as before, Android is being done "in-house" by their contractor. This update is talking about getting reference devices to external developers and that those devs have made progress. At least, that's my interpretation. 😉

I did OTA for the first time rather than ADB and it works great. And, yes, root is preserved.