EskeRahn

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.

....it happened shortly after unplugging at 98%. Which in it self will give a drop in voltage. I then checked for new app updates at the Android Market. So in total it went from 98 to 94 in fairly short time, and the logic mathematically predicts that it will be depleted shortly.... Perhaps this could be prevented by adding a check for NOT doing these estimates within the first minutes after unplugging.

Minor bug. Just got this notification: I would say a bit early to suggest to turn on the battery saver at 94% *LOL*

(do with flash - after some troubles with win11)

(I can get my old driver installed and working temporarily disabling the driver check as described in Fix 6 here, but that only last to next boot)

Did you find a workaround? I just got a new PC with Win 11, that requires drivers to be signed (unless going through all kind of hoops to loosen the security at bios-level to disable that). With the default windows driver ADB works just fine. But fastboot does not.... The driver I used on the previous PC (that worked fine) are not signed. I tried downloading from Google, but they aren't signed either. The force method mentioned on XDA does not work on Win 11. (I do not get the question to install it anyway, it is just denied) I have not tried all the manufacturer on the list.

New to me too. 🙂 Let us tag @Elysia to see if she can find a way to make stuff like this more visible. If no smarter solution found, a pinned post with links to stuff like this might do the trick. Maybe the general header on https://www.fxtec.com/ could be added to the community too? Perhaps even with something smart like the 'Stars' in the community, to indicate if the other 'tabs' have content the logged in user have not (yet) seen?

I agree that it sounds like a software priority issue. But rather than lack of priority I would guess something else having too high priority thus interfering with the keyboard operation, as not everyone reports it. But could still be a system isssue, where some other system stuff gets activated by some actions or apps not all use or use the same way. Starting with the ones power consumption points at as posssible culprits, I would try to stop (or even deactive/uninstall) stuff and see if whatever triggers the phenomenon can be narrowed down. Ultimately trying a factory reset, and t

Hmm cable perhaps, or connector for some reason not working as it is supposed to?

If we look at the previous update dates, it has been slightly over a month every time (less May+June) since Janurary. Creeping from January 06 to September 20 - So hardly a surprise that it has gone over a month this time too. Just saying....

Update to October 20, with October 1 security patch using flash, and with OpenGapps-Pico went smoothly. Known keyboard bug still there (see lineage thread)

(lineage-18.1-20211018-nightly-pro1-signed.zip on October 1 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.