EskeRahn

(lineage-18.1-20211115-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed.

let us hope they find some ingenious way with a top layer that is hard all over, except at the fold, so 'only' the fold-area requires extreme caution.

My guess would be something mechanical too. Since related to the pocket. Either a cable, or perhaps a superthin crack-line of a print plate. You could try some (gentle) flexing of the botom and top parts and see if you can trigger it. And perhaps revive when the issue is there.

I can definately see the benefits of samsungs folded variants versus a tablet or ordinary slab. And clearly using half for a fake keyboard is likely to work much better with android than a fake keyboard on a slab. But that said I see two drawbacks. Primarily that it isn't a keyboard with real keys, and secondary that the surface will be prone for scratches, as we can not have both hard and bendable with currently known materials. So I see it as the optimal device for those that do some typing and still also want a large screen for other stuff. But not ideal for those that do a lot of

I just tried on mine (AICP without Magisk), I get no fix at all so something is broken indeed. I'm a little unsure if it was on Lineage or AICP I had it working before (seldom have location on). But I THINK it has been working on AICP-R for me earlier....

Try this https://devices.ubuntu-touch.io/device/pro1/

Ah so you got a rather recent LOS (the earliest 18.1 release is from around May, if I remember correctly). Please click Settings ► About phone ► Android Version. The line LineageOS version would then have a stamp like 18.1.20211108-NIGHTLY.pro1, that should give the date. So they will know the bug is newer than your date. 🙂

Thanks. I'm unfortunately to lazy to start flashing old versions to see when it was introduced. *LOL* What are you running? 16.x , 17.x or just an older 18.x ?

Two (other) ways to force an sms to an mms: 1) Use e.g Textra, and select that sms, that would split in more than one SMS, is send as MMS, and make sure the text is more than 160 characters long (or about 80 including at the least one not simple unicode char) 2) add any email as a secondary recipient apart from the real number. (Please note that for some carriers MMS is sent at a higher costs than SMS)

PS A tiny tiny bug on the lock-screen in landscape (Both Lineage and AICP) BTW it might have been there 'always', since the lock icon was added, as the position of the clock in landscape/portrait is the same for stock android.

(lineage-18.1-20211108-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above. (the bug introduced last week maiming accessibility app's access to the keyboard has gone 🙂 )

As @Totalnoob is allowed to do calls, it can not be completely locked out of the network. so i would certainly check SMSC as the first thing. Though it is a bit odd if they just changed that. Verizon support should be able to tell their SMSC Maybe also try to borrow a SIM from a friend or two with different providers, and see if everything work on other networks (given that the provider has suitable reception where needed). And if so consider changing to that provider.

SMSC would be my guess too. (The smsc is not needed for recieving) I am not sure where it can be set/checked in the normal menues but if you dial 'info' *#*#4636#*#* And select "Phone1 information" You will find a line SMSC with a refresh and update button next to it, press refresh and verify that it is the correct number. On modern SIMs the number is usually already entered (decades ago we always had to enter it manually)

All these bbbbbbbbs, I thought you were bbbbbbbrrr freezing 🤣

Update to November 3, with October 1 security patch using OTA went slowly but smoothly. Known keyboard bug still there (see lineage thread) With a charger attached and display on during update, there was a slight decrease in the estimated remaining percentage (25 to 23%) during the install. It only seemed to pull about 0.2A at 5V, or roughly 1W from the charger. That was a bit odd. After boot it went to 1A (5W) - as I would expect (using a slow charger to be kind to the battery).

Just a thought. you could send the defective one the other way, as it certainly would fit the hole perfectly 😉

(lineage-18.1-20211101-nightly-pro1-signed.zip on October 1 security patch installed smoothly using OTA ) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above. Actually it has goten worse as accessibility keyboard not only interferes with Ctrl-Space, now these apps access to the keyboard aren't working any more. Try e.g. Android Assistant

Sad story, though at the least you got the camera fixed. I have no idea if any other phones fingerprint reader would match. I have not heard it mentioned. But would be great if a more widespread device uses the same cable, as the cable is definitely vulnerable opening. Others have reported tearing it, On the torn membrane, I would try with tiny pieces of (non conducting) duct tape and see if that would do the trick. My guess would be that they wont have the membrane as a spare, but would replace the 'entire' side print with all three contacts.

I have not heard it mentioned in here, so I do not think so.

AICP is certainly not bad either. 🙂

Ah so that is why it is called N-key-rollover. ... Sorry, could not help it. *LOL*

Well there is strictly nothing wrong, it is just an unwanted warning. When they have two points with 98 and 94 % with 2½ minutes distance, the matematical extrapolation is about 1hour remaining stamina.... The problem is if the estimate is just mathematical or sensible...

I had the same, but adding an ancient usb-hub at the least allowed me to do the flashing, though with the speed down at the least a factor of five... It takes a whole minute to flash the 64K boot-image, and sort of forever to flash the main image *LOL* So will see if I can find an old, but not THAT old hub, tucked away in a drawer somewhere...

When typing very fast, and perhaps having more than one key down at a time, there are N-key-rollover issues. Could that be the issue? And if I remember right, it was @TDM that made a new variant of the keyboard-driver that improved this for Lineage 16 (that I assume is still in use on 18 and AICP)

Indeed, using a charger with no ground-wire connected usually makes touch input almost impossible on mine. For some chargers rotating the power-plug helps. And charging through a (grounded) pc I never have the issue.