EskeRahn

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

It seems to work, but has the same silly stretch and squeeze as most launchers. Quite silly to assume that an icon layout suited for 1:2 also is suitable for 2:1 A few launchers offers different grids for the two orientations, The stock browser has a quite clever the block approach with two halves next to each other or on top of each other. Simple to use/setup, but does prevent widgets from crossing the line dividing the screen in two halves, so not ideal either.

(lineage-17.1-20201123-nightly-pro1-signed.zip on November security patch installed smoothly using sideload) There are a LOT of changes this week according to this.....

Guessing here, but would not at all be surprised if FxTec themselves was unaware of the the short refund limit Indiegogo has in their policy. And thus has to fiddle with the refunds themselves. And @flx they said in a comment in indiegogo that you can change the requested layout withou having to cancel and select a new perk. Though they seem to have a rather long queue of handling mails, sending a mail at the last minutes might be a bit risky. So would be great if the actual azerty was published soon. Or at the least the limit for changing layouts will be well after the publication.

Too bad Marethe did not manage to leave the legacy with the three united kingdoms. It certainly is silly with the tiny differences in orthography. My guess is that it was a silly attempt from the danes to distance themselves from German orthography ...

Different users, different usage patterns. When i tried out SFOS I do not recall if I even opened the browser.

With Swedish selected you do get @ on Sym+2 on AICP-Q 🙂 (Goes for both qwertZ and qwertY layout)

By far an expert here like e.g. @tdm but i would try a fastboot getvar all and almost at the bottom see if one (or both) slots are marked as "slot-unbootable", and also check the "current-slot". The below is from AICP-Q so does not have to look exactly the same.... (bootloader) has-slot:modem:yes (bootloader) has-slot:system:yes (bootloader) current-slot:b (bootloader) has-slot:boot:yes (bootloader) slot-retry-count:b:5 (bootloader) slot-unbootable:b:no (bootloader) slot-successful:b:yes (bootloader) slot-retry-count:a:6 (bootloader) slot-unbootable:a:no (bootloader) slot-successful:a:ye

Well it was an attempt in a more polite way to question your accusation: