EskeRahn

I do not see this. (Also using K9) Perhaps clear the cache of swiftkey, or even uninstall and reinstall swiftkey if it really has messed it self up.

(I split the posts on Lineage 18 into a separate thread here)

I think we better tag @Waxberry here, I just naïvely added the link to the August package in the OP. Other things in the guide might need to be adjusted too. e.g. I guess it should have one (and not both) of these (I do not know which) fastboot set_active a fastboot set_active b and/or fastboot --set-active=a fastboot --set-active=b ...But I'm a noob here, others have to help here

Note the @tdm reply in another thread:

No, that is the way I deliberately can put it in this mode. 😉 My wild guess was if your volume keys (seen from the phone) appeared as being constantly pressed, that might prevent it from ever trying to boot. Pocket lint that crept in could be an issue, so that is why I asked if they felt moving 'normally'. (And positive sign that it charges with 1A 5V too, that is totally normal, and reduces when above something like 90% charged)

(merged the two threads)

Just curious. Any particular reason for not upgrading to 17.1 ?

As it can be seen from a computer as in loader mode, I would say that it is very unlikely that it is the USB-port. And as you reported it as 75% shortly before becoming unavailable, I do not think that it is (or at the least not was) depleted. Why you are not allowed to flash it once it is connected in loader-mode is really beyond me. My best suggestion would be to follow the advices from others and try from different computers. (And/or with different cables) Especially slightly older computers with a USB-2 and not USB-3 port, as I repeatedly seen this reported as helping others. (gene

Sure you are allowed to in this forum 🙂 That it is not official does not make it illegal, but perhaps it is not the optimal thread for it. IS it the XDA build mentioned here, or is there another one?

Oh was not aware they got that working in finiate time. Maybe I will try that next week. 😁 EDIT 20201207: Still only total, not incremental 😒

Not quite. If you buy the screen assembly I assume it is, but the BOE spare screens we can get from AliExpress just got a hole, so the actual LED is behind the display with the speaker and the narcissistic camera, ADD: Roughly here on the long PCB next to the camera (Crop from the picture 73 of the disassembly manual)

(lineage-17.1-20201130-nightly-pro1-signed.zip on November security patch installed smoothly using sideload)

I have tried to take some images, but none are good.... in showing neither Pros nor cons. The light is made from individual R+G+B LEDs, with no diffuser. Clean R, G, B colours work just fine and bright, and that is the ones used in stock. If you try to use base colour combinations to get more colours, these will not keep the combined colour when viewed from a shallow angle shadowing one of the base colour-LEDs If/when I need to take a Pro1(X) apart, I will try to add some kind of diffuser above the LEDs.

I know absolutely nothing on the Ubuntu port, but would try a forced restart (long press on power) first, in a vague hope that it fixes itself.

CTIA (Also known as AHJ). I do not know if any new phones/phablet still uses the once very common OMTP? I remember that Nokia and SonyEricsson was using OMTP a decade ago, but it is rare to find new devices using it, except those that keeps backwards compatability with earlier products in a line like playstations. See e.g. https://help.longtailproducts.com/hc/en-us/articles/207970396 The CTIA headphone plug is one of the few standards aPple followed (well almost...) with their Iphones, and after a mess with converters as aPple grew, most have changed away fra OMTP since. It

Uh, this certainly sounds extreme. Try contacting them from another mailadress, if any mail from them (for what ever reason) do not reach you.

Yup

Are you on stock Anroid, or? If you do not need apps that requires it pass the safteynet test, then Lineage or AICP gives you a less buggy environment. I too are a bit tired that calls only work stable with a headset on stock. I seldom use calls, and have not even tried video calls, so not as bad for my usage pattern. The camera works fine for snaps for me.

I would try a usb-Volt-meter, and see if any current are drawn. If I recall right someone had a device where the connector between the small usb-pcb and the main pcb had gotten loose, with a little luck it is similar. But all is rather strange if it was as high as (roughly) 75%, as this should last very long with the device/display off.

Nope. As I said it is not the app, as HDR works fine on other devices. And as their own app can do it too, it must be a matter of not using the camera2 interface correctly

I have noticed what I thought was my error: Occasionally Ignoring touching the fingerprint reader (no haptic feed back indicating an unaccepted scan), BUT after clicking the power button to show the lock screen, re-touching the fingerprint reader unlocks just fine....

I use Firefox on stock too, and do see the autorotation bug from time to time, but not correlated with FireFox usage. If I open any app that use the sensor (e.g. "AndroidSensor" or a camera app), the problem disappears for me)

Newest afaik.....

I was not aware of that ebay limit 😰, but thanks for sharing, and hopefully you will find an alternative, so the Pro1 can get a new owner.

Yes it is the same in that aspect, We do have a thread somewhere with different launchers and pros&cons, Though that is made for Stock, it might well have relevant input for Lineage users also. Will try to see if I can dig it up.... Edit; Merged it into an older Launcher-thread