Rob. S.

Confirming for OTA, too.

I just needed to make sure all three options under "Auto-fill Services" were enabled ("Auto-fill Service", "Use Accessibility", "Use Draw-Over"). Could be that I also needed to force-stop and restart the browser once, but I'm not sure. Is there a list of WebView-based browsers somewhere? I would need to re-test; I've tested so many browsers that for the most of them I wouldn't remember which one worked and which didn't...

You don't mean that, do you? That's not how business works. Nobody would have ordered anything anymore, and other business players would have stopped doing business with them. My guess: because they might not have had enough money left for a coder for a few months, after so many months of COVID-19 and other factors having stopped production again and again, reducing sold quantities to a fraction of what they hoped to produce. If they would have been fluent enough for that, they probably wouldn't have needed to resort to IndieGogo to fund new batches of devices in the first place.

Yes, I can confirm it for the current versions of Brave, Chrome, Firefox, Opera, Vivaldi, Yandex on LineageOS 17.1. I don't know whether any of these are actually using the Android Autofill Framework to make it work, or whether Bitwarden recognises them as browsers and manages to extract the website URL through the accessibility services, which I found I have to enable for making it work at least on Opera. (The default browser on LineageOS 17.1, org.lineageos.jelly, by the way, doesn't work with Bitwarden, either.)

This site perhaps wasn't the best example because it has a usable mobile mode, but for the most sites I visit on my phone I usually like the desktop mode better. Also, when using my preferred (so far) browser which is Opera, it doesn't feel like I need a special tool 😉... Some sites' mobile modes, like ebay's (ok, there would be a dedicated app for that, which I don't like much though, either), even hide some of the information they're showing in desktop mode. No, I'm no friend of most websites' mobile modes and I don't suppose I'm going to become one any time soon...

Here's one other thing that, for the time being, stops me from using Fulguris: the Bitwarden password manager app doesn't recognise the page which I have opened, like 'community.fxtec.com', to look up the related login. It always only sees Fulguris' package name, 'net.slions.fulguris.full.playstore' in my case, for which it obviously doesn't find a login. I saw this happen with some other no-so-well-known browsers, too. I'm not sure whether this is something that could be changed from within Fulguris at all. It might be that the Bitwarden app would rather need to be informed that the app

You could use a random slashdot.org article, desktop mode. Enlarging the view far enough that the text width doesn't fit anymore (some pages don't need to be enlarged, but I didn't find one from memory), it's cut off from the view. Opera would then start wrapping the text so that it fits again. The "Text reflow" option doesn't do it, I'm afraid.

I'm still not sure what kind of problem this actually is, as my device, just like the ones of a few others, doesn't seem to exhibit this problem at all. No problem auto-focusing to infinity, whether with the Lineage 17.1 default camera app or something like the 'Manual Cam' app I'm normally using (despite the word 'manual', everything's automatic there, too, until I switch it off).

Any chance, perhaps, to get the "text wrap" option into Fulguris that I love so much in Opera (and only one other browser of the huge number I tried, I think it was Yandex)? I.e. forcing text blocks to wrap at the screen's edge instead of flowing outside the screen, having us scroll horizontally for each line.

That would be great! I guess I'm going to install magisk sooner or later anyway.

Interesting, are you on stock? I have seen others with the same complaints as me. It could be that it is a matter of usage pattern. When I got the first call on my new used phone recently, I was surprised after all I had read that call-in audio was perfectly normal and ok for a smartphone (and the caller, while I didn't ask him about it, at least didn't complain about what he got from me, either). Several days later I got a phone call that was so loud I had to hold the phone away from my ear (on the lowest volume setting). Ah! I thought, so that's what everyone was complaining

Excellent, thank you! Perhaps then I might even be able to add it to my device without changing the running system... Must have a deeper look into it some day.

Ok, if you're already on LineageOS, that makes it worse. Then the "action" your anger eventually needs to turn into will indeed probably be to move to another phone... My impression is that Fxtec has knowledge about most of the problems; there's even an unofficial github repo for issue reports which they should be aware of. And as with every other of the many issues we had with the company so far (including my waiting for a phone since October 2019 and their bad communication practices), I still think it's not because of malevolence or even just neglect that they didn't do something about

I would have tried to use stock, too, if I had bought a phone that would have come with stock. But as it was, it came with Lineage, and I'm glad it did... At least in case of the Pro1 X, I guess Lineage is going to be the new stock, anyway. No need to modify your phone, you'll get it preinstalled. And no matter how much better the Pro1 X stock Android might turn out compared to the Pro1, Lineage will probably be better, and it will probably support the specifics of the phone better, because that's where the developers are said to be working now. I guess they just wouldn't have the same op

Oh, no need to be sorry. I'm feeling with you. I went the Motorola way, too – after having had my share of fun with BlackBerry, when they stopped issuing security updates for the PRIV I had bought only a couple of weeks before. That was when the keyboard mod seemed to be just around the corner, so I bought a Moto Z... Which was a catastrophe, with an undersized battery that I had to have replaced twice during the time I had that phone, and then got a Moto Z3 Play which was ok. But didn't have a keyboard. And the Moto Z had been my first smartphone without a keyboard, so I continued to feel amp

It could be that they're simply not able to improve the software that much. As far as I know, the mainboard manufacturer is the one providing the stock Android for the device, and Fxtec might be mostly limited to what they can make them do, which doesn't seem to be all too much. Which might just have been why they've contacted the XDA developers community with the plan to get an official LineageOS and an official Ubuntu Touch OS for the phone. My first few weeks with the Pro1 under LineageOS 17.1 (it was a used device with LineageOS already installed) are nothing like your experience. A

I thought it might make sense to start a new thread after the Pro¹ X practically having become a new device, with several months ahead of us before we can hope to get one. Here's F(x)tec's latest info which came in via IndieGogo right now: Reason to stay optimistic after all, I'd say, despite the additional waiting time... Cheers, Robert

Same here from the settings menu.

I am noticing an issue with fingerprints: If I remember correctly, there's the one thing that the system stops accepting fingerprints for some time after too many unrecognized attempts, which can easily and unwillingly happen with our device because of the scanner's position. Whenever this happens, my banking app reports changes in my fingerprint configuration and stops allowing me to authenticate via fingerprint, until I authenticate via PIN and re-enable fingerprints in the app's settings. This doesn't bother me too buch, though, as it doesn't happen too often anymore after I

Ordered the last package that was available from a marketplace seller through amazon.de (8.88 €) on Friday – I'll report back when I get them...

Not for long, by the way – the card stopped being accessible in the midst of some large amounts of copying with the whole phone slowed down to a crawl, which made me go back to FAT32, and finally I have access to my music library with it...

No problem. I used to think similarly when I had my first rooted phone, but then I got a BlackBerry PRIV and that was that – currently, I just want a phone that works, and one of the traits of LineageOS (an unrooted installation of which is what my second-hand Pro1 came with) is that it works better than stock with our device😉 Looks like I finally could get back to being rooted when I switch to AICP at some point, though.

Sounds good, with the caveats you mentioned, of course – but I guess it's not an option on a non-rooted device 😉 Will be interesting to see how AICP behaves in that regard.

I'm struggling a bit getting my SD card to work the way I wish. As I expect to change from LineageOS to AICP in the foreseeable future, I decided to not mount the card as internal memory (which I usually did with my earlier phones). At first, it seemed like the SD card would work after being formatted to ext4 on my laptop. But at some point it stopped being writeable for apps even after explicitly giving them write access. Apps didn't report not being allowed to write, they reported being unable to. Some tried forever until I killed them. I thought I might have done something w