Slion

I wanted to try FireFox but discard it pretty quickly as I did not find a dark theme. If I recall well the top bar is bright white.

I've been using mostly Chrome but lately switched to Vivaldi Snapshot as it has an option to hide the status bar thus going full screen in landscape which is neat.

I've installed that Volume Control app but I'm not sure what I need to do with it to fix that issue.

I'm running the suspended update and I did not notice any improvement. Anything above minimal volume is unusable.

Indeed, just ran across that problem again and launching the camera app saved me a reboot.

How?

No such issue here. Then again I'm on the suspended update.

@EskeRahn Well, ideally we should use the sensors directly rather than relying on funny key input. Last we looked we could only find the keyboard sensor, the one for the case remained elusive. Surely @tdm could help us with that as somewhere in the system something generates those keys based on the raw sensor input.

Just released v0.6.1 that's mostly fixing the issue reported by @EskeRahn above, thanks mate for doing my QA 😉

Thought of that too but decided against it. Indeed.

It is unlikely I bother with that myself until I get myself a spare Pro1 for development purposes that I could flash with LineageOS.

Thanks, good catch. I can reproduce it too. I'll see what I can do to fix it.

My initial idea too but it turns out Android won't let you do that apparently. Even turning off the display without locking the screen and without the proximity sensor is apparently not possible. If you think about it does make sense too.

That's exactly what was implemented 😁

Just released v0.6.0 adding support for locking the screen upon closing your keyboard. Mostly for people not using flip case I guess.

Mine is x.132 funny enough.

I have that same issue in Gmail. In Chrome I believe the blank popup actually has those two same entries and if you tap on it they are functional. They just show blank. @tdm Does spellcheck work on Lineage?

Created a bug report to track that issue: https://github.com/Fxtec-Community/Pro1-Android/issues/2

Has anyone managed to get this working on Pro1? @Erik @Waxberry Are you guys looking into that issue? I mean a working spellchecker makes a lot of sense on a keyboard smartphone 😁

Try "massaging" your keyboard and see if that fixes it? If it is a mechanical issue rather than an electrical issue it could help. Maybe your keyboard is still too stiff and too new. I found mine got easier to use as it aged a bit.

That would make sense. I'm afraid you may have to contact support.

@Erik @Waxberry Can you guys or anyone else confirm that issue with current OTA? I'm running the one that was suspended and don't have any issue with it TBH.

Do I detect sarcasm?

Odd, did you try an extra reboot?