EskeRahn

A tiny thing that cause some reboots: When in inverse landscape, the Power-menu is in the same order as in landscape. So when you press the one close to power as usual to do a screen shot - you get a shut down!?!? The icons should be at fixed positions at the fixed bar rotating the icons only, like they already do correctly between portrait and landscape. In Inverse portrait, it fails completely, placing the bar identical to portrait, and thus at the wrong side and in the wrong order... 🙃 This goes for both Lineage and Stock, so tag @Waxberry hoping he sees it

Well we can only guess. Maybe the fix they tried had some unwanted side-effects they want to iron out?

I have also had cases where it did not pull power from a PC-port, I thought it was the magnetic cable that had not been attached properly. When attached to a port offering 5W (or more) I have seen no issues.

AH I think that is how the "too many retries" seems to be handled, just inactive, a warning text would be nice though. Logging on with my password and locking, it works again.

Worked fine for me too, used it directly from the downloads folder.

Well the principle is the same. Handle the physical print first, and then let default android language-layouts (or our own) act upon that. As I read it, they were debating on how close they want to be to the print or the standard. Both has it advantages, and thus followers. I personally think that what is printed should be what we get BUT not as a limit, but as a base. I want say Shift+1 as well as YelAr+1 to give an exclamation point. I expect YelAr and Shift to work as doublets on ALL the yellow prints, except the letter keys (and that is two on qwertY and fifteen on qw

UPDATED: Hi everyone, there is a new OTA update stamped 2020-03-06, offered. This REPLACES the OTA stamped 2020-03-04, that proved to have an error with Safetynet. IF you already updated to the 2020-03-04, you will NOT be offered the 2020-03-06. But both groups will be offered a common OTA, hopefully in the coming week. The two updates contains the same fixes, but the 04 had slightly newer security patches, and that broke Safetynet OLD message on the 2020-03-04 : Hi everyone, @Waxberry has shared a little sneak view of some expected to be in t

I think the idea @tdm is using is to handle which physical keyboard-print we got first, mapping either to be usable by the standard android language files on top. This should mean that there will be no hard need for additional mapping for normal text and the most ordinary symbols. We MIGHT want some additional mapping for extra symbols etc, but that same mapping would then also work on any other qwerty-phone, and not be Pro1 specific (nor specific to qwertY or qwertZ) That is, if you want a special symbol pressing say Shift+Ctrl+Alt+Sym+Q you would get that no matter where the Q key

Odd, works for fingerprints here ???

Thanks! It works perfect! 😁 Especially the last one I bet will help those not using a case. Would it be possible to not count the 2secs from last registered attempt but from last sensor-touch? That is if I repeatedly press (or even hold) a wrong finger/hand-part at the sensor, it should be ignored, until I leave it free for at least 2s, and then activate it again.

You should include the var= part of an ebay-link ved multiple items, so we can see the right one, e.g. https://www.ebay.com/itm/233460908295?var=533070924751 The easiest way to get it is to put the right variant in the basket, copy the link, and remove it from the basket again. Or if bought from the order list. Are you sure about the first link BTW? I see no "P20 Pro"...

Well of course guessing, but seems rather likely that they work at an office, and not all with the option to work from home. Of course we could be lucky that this is in an area of China not yet affected. But not that likely.

Kind of you to offer, but it seems a bit odd to make a parallel build. If you got the applicable fixes it would make more sense to have F(x)tec implement them. Though I obviously do not know how close/far we are from a new OTA update, with the current COVID19 situation.

Suggestions 1) on the first one. I would suggest to immediately turn screen and touch sensing off BUT do not LOCK the device until the specified time-out Similar to Settings, Security&Location, Screen lock, Automatically Lock PERHAPS doing some pulsing with the notification LED to warn that it is not yet locked. 2) Why not offer an option to lock on keyboard close. Some of us are used to that from ancient devices. (I doubt I would use it though, but others in the forum have been asking for it) I do not quite get the four filters. Especially the

I believe it is not limited to a weak/failing signal, but combined with the bands relevant for the carrier. As more of us would see it if it was just the lost signal.

I would expand that to Option to disallow screen on as well as unlocking with fingerprint if the hall sensor detects closed.

When I use Finqwerty for qwertY Danish, I see the same on "2" BUT it works fine on "P" (giving P resp /) and "L" but not en neighbouring "Å" and "Æ" with YelArr. Also both Sh+YelArr+3 and Ctrl+YelArr+3 gives nothing rather than £ on lineage ... So I guess we would need a special variant of the FinQwerty maps for the approach this lineage implementation uses... Note that if you check with e.g. "Keyevent display", Pressing Fn does not return a code in it self on this Lineage.

https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_FUNCTION

In my book it always raises suspicion when a very simple thing comes in a large package I immediately think: Hey is this compiled on an infected PC and used as a mule by some malware? And I'm especially cautious/suspicious when it is an app that (for good reasons) needs high privileges. So would be nice if you could dig into the "Why". 🙂

Just curious. Does this include some library, or how does this end up at 1918KB ? Browsing through the source even the small images in various resolutions could not get it anyway near (the source adds up to 1/10th).

He he, well I would rather have @Waxberry or @Erik do that.... AND it should have a 'secret' part we as users could not see. E.g. the priority of each bug/wish. And any known bugs no users have stumbled into yet, that they hope to fix before the public even know it existed. It is common practise on security bugs to not tell about them before they are fixed.

We really should have somewhere offical... We already got this unofficial one: https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y/edit#gid=0

Yes they are identical, that is why @Anssi Hannula starts his qwertZ-files (e.g.this) by mapping. For image, see e.g. here ...That they are identical is actually an issue when setting up a new device (WiFi and account credentials), so we need to use the fake keyboard, as the real keyboard acts as the shifted until you get a chance to tell the system that it is the qwertZ. See also this

They are electrically identical, the only difference is the print, so your app will work identical on both. So you can test if you would like to (though the print will obviously not match when tested on a qwertY device) You can see the two stock prints described at the top here

Nice. I too would like to find a good one in leather. On the glue half part, I think it should be mentioned that For those using the back camera and/or LED a lot, it is recommendable to cut a hole, and perhaps glue the whole part (like you did). For those using it less, keeping it un-cut gives a better camera protection, at the price of needing to fold it all the way open to use the camera/LED. I like you idea of using a better inner bumper case, though to me that would be overkill The best one I've found (so far) isn't real leather either. I have bought