EskeRahn

OH! Sorry, I thought you got your Pro1 and had it running there... If I explicitly select the Reverse-portrait, that works fine. And it also respects the slider setting forcing landscape. But If I to get its auto-rotate to work, it does not. It stays in reverse portrait when I select that first, and then autorotate, and rotates fine from reverse portrait, but will not go back to reverse portrait no matter what I try,.. I would want the tool to respect all four directions when rotating the device (and respect the slider setting for landscape when open) (And I do not li

That was the point, I did and it does NOT work here.... See above

It sounds to me that he just choose to ignore that they clearly stated that future pre orders from a certain date would NOT get the extras.

I don't know, I just assumed that it was because mine were cheap ones that they had issues.

Odd, though I have seen some cheap ones from ebay not working well either. (Other cheap ones works fine both slow and quick chargers) The two Quick-charge 2.0 chargers I tried did not work optimal, so could be a pattern?

Quite a number of launchers do support landscape mode, but most often just be stretching and squeezing the grid from portrait... Until now the only one I have seen with the two block approach (one over the other or side by side) is the one that comes with the Pro1.

Yes, but can you get it to do reverse portrait with autorotate? That is interesting for people preferring holding the device in the right hand portrait, as this would get the buttons and fingerprint reader on the finger side... (Either for one hand operation by right-handed people or two handed operation for left-handed people)

@tdm I took the liberty to renaming the thread, and merged in the new thread. Please let me know when there is a status change, or you want a different title, and and I will edit. Maybe it would also be nice if we kept your original post up to date with any new important info. Just PM me with what you want it to contain. 🙂

Yes we need to know their limit to see if it is realistically reachable. If say €2M forget it, if €50K not unlikely. As suggested an option could be some crowd-funding to get the needed money. l imagine a model with a minimal of the €50 paid giving a licence, and then we can see if we can reach the needed goal or not.

(...and to wake and turn keyboard-light on Alt+Sym)

Try entering fastboot oem device-info to see if it looks like the above, or something different.

Frankly I see the supplied launcher as a 'minimum build' that works decent in both landscape and portrait, compared to stock. I doubt they will spend much time on it, as so many alternative launchers exists out there. I guess it is more likely that some creative guy make a few fixes/additions to an existing open source launcher. And as other have asked, since the base of the launcher is clearly the AOSP sample, if F(x)tec are allowed to, they could consider putting the source for their modifications out as open source too.

If I remember right I locked them to get the google certification, but could remember wrong.

I'm yet to find one that works.... Some (like this) can do fore reverse portrait, but none of the many I tried can do real autorotate only 3/4 autorotate excluding reverse portrait

I agree that they went a little bit TOO "stock android" there. As the keyboard is THE main feature of a Pro1, I did expect a more polished Keyboard software. But this is all software, so it is just my lack of patience, and at the least we got workarounds for most of the keyboard issues with FinQwerty and Swiftkey until OTA gives a better experience stock.

If they need a specific amount that is not secret then crowd funding could perhaps be an option?

I did neither, so no.

Just ordered this as a (too long) candidate for the top.

I would not at all be surprised to see F(x)tec introduce a soft shell that can be used either as is or adhered into a flip case. Sort of similar to what we do when we take out the inner shell of a P20 Pro flip case, and then (optionally) glue it back in. This could be an adhesive strip, Let us see if we can not tempt @Waxberry to do that. I think we will have a hard time doing a two part case, but we will see. The first I got today for Honor 9 lite as expected is too small, but cutting off one end the front part sort of works, but not good. so hopefully something can be done with a l

I guess that could be the big question. What is the critical number before they will bother to support it. If that is say 50000 we are unlikely to reach that,

First of a user would not be able to copy files in without root. Secondly I'm not even sure the files are actually copied, but are merely presented to the system somehow (I do not know the specifics, but can not find the .kcm files copied in anywhere) and I guess that is also why FinQWERTY does not ask for privileges. As I understand it, the .kcm files has to be baked into the apk, and that is why there are no import/export in FinQWERTY. But I might have misunderstood. Hopefully @Anssi Hannula can chip in with the correct info? ADD: See this related simpler example &l

According to this it is "space w. acute accent" that in some older fonts are used for one of the curly quotes (that are generally available in unicode)

(The Tilde is NOT affected by the FinQwerty solution)

Please note that this is NOT the straight apostrophe, it is the backwards slanted one (apostrophe not accent!), printed left of Q, My English isn't good enough to even know where I could (or should?) use a slanted apostrophe over a straight one. Please tell me where it is used. (see also this) And the Alt functions are Stock Android afaik...

I think the FinQwerty solution for this is quite good, You only move the slanted apostrophe, and that frees the key for / and ?, So almost everything is left unchanged. That is what I would suggest as a default for the Qwerty in Lineage, really close to the print, and yet useful: