EskeRahn

I closed this thread. Some newer can be found here https://community.fxtec.com/topic/2484-independent-reviews/

Well then @_DW_ most likely have given the answer: a mistake.

I think they from the beginning said that IGG backers we would get priority. But that is not the same as a few could not have even higher priority. Guessing here it could be some that have helped a lot e.g. by developing SailFish or LineageOS.

Nah, you just buy ten Pro1s, and modify the nine with various DIY keyboard-replacements. I'm sure F(x)Tec would be very happy if a lot did that.... 😜

Under developer options, a setting MIGHT need to be changed from default:

Moved all the stuff on the CPU-Z over here. A more precise variant can be found in a similar app, see this

Only tried the radio. And it works better than I dared hope for. I would like to find a better app though. You should remember to set the bands, and I recommend to turn OFF the alternate frequency scan - as it temporarily mutes the sound, which is really annoying.

Ah sorry, read your labels wrong, they are above, not below the images.... Silly me What I was talking about as a calibration issue, was the HDR when using the API, as e.g. with OpenCamera.

Nice review! On the vignetting thing. It seems to be limited to the Google app in your examples. So I guess that means the Qualcomm app are compensating by boosting the brightness of the corners? Just did a quick test here with "OpenCamera" versus Qualcomm's and I see the same. Edit: I confused the labels as below not above the images, DOH There is also what i assume is a 'calibration' issues in the Camera2 API. If you do HDR in OpenCamera the stitching gets the brightness levels wrong, leaving a dark 'halo' around a bright subject. It is hardly a bug in OpenCamera as the

(Just for comparison, this is how it looks with the default launcher) Edit: Added a few extra icons making the two blocks clearer

So you meant something like still haven't shipped any non-IGG-coupon pre-orders yet. That is correct (AFAIK), but there is quite a difference between that and a general "any". Our pre-orders were like any others, except the promised priority and the coupon. (If I remember right it was March 2017 I backed the IGG project, so it has been a much longer waiting for us...)

you mean: they still haven't shipped all pre-orders yet. The earliest to get it seems to have been some in Japan on Nov 15. Those in Europe seems to have had it this week

You are asking for exact info on stuff there are only estimates for... It is a bit like asking today how many cm snow Stockholm will get for Christmas... There are so many things involved that is out of their control, or unexpected. Take the US customers for the first batch, where something with the custom paperworks delayed stuff so they did not get them as quickly as the Asian and European customers (I'm not even sure if they got them by now). I mean even after I got the tracking info from UPS on the Parcel from UK to Denmark (and that is not a long travel), UPS after having g

And Waxberry already told that the certification is at the final stage and will be coming above, Would anyone have preferred an additional delay until the certification is completely finished? Just asking... 😇

Slightly uneven yes. It matters less on the (unshifted) qwertZ though as the second column is letters as standard, but on the shifted qwertY it is physically lesser symbols, But I think it will only matter in the beginning, as any user will quickly learn where things are relative to each other. I mean when you know the accent on the qwertY is between the Tab and the Q, that are both clearly visible, it is less important whether the actual accent is clearly visible. Similar you (with or without backlight) have to have good eyes/look closely to see the difference between the dot and th

....Who let that bee in here ? 😜

Well they HAVE made project Treble that should ease upgrades. If I do not remember wrong, any phone launching with Pie HAS to provide Treble, so that should ease the upgrade to 10 significantly.

In Nova yes, (but it is placed at the bottom left on the default Launcher)

Thanks. Technically independent, but so much a fan boy of keyboard-sliders, that some would say that it inflicts on being impartial, as there are zero modern alternatives. I'm not the one to go to, to ask if a physical keyboard is worth the extra price, as well economical as size and weight. To me it is a clear YES, to others it might not be so. It much depends on the individual's usage pattern. My primary usage of a phone/phablet is sms/mms/mail and secondary calls and web-browsing. Others with other priority might feel otherwise. If people use texting even more, the Cosmo might be

Just tried, and Autorotate, well the function is there, but as they seem to assume the same icon grid, rotating the icons in the grid, and stretching the grid, When it looks OK in Portrait, in landscape extremely spaced in one direction, and cramped together in the other (Or vice versa) - but not unusable. All the functionality is there, and with Ctrl+Arrow you can jump around the screens. An oddity with keyboard navigation is that you have to leave one of the the left most column spaces free as arrow-navigating there in landscape BOTH marks that empty space and the icon in the launch-bar

Well to me it is the sides that are interesting. But just tried, and that means it is only messed up in the otherndirection in that particular app...

Yup, see e.g. this thread, and this post linking to some paypal policies, that says

Yeah, any takers? But more seriously, it ought to be added to the launcher app. Ether as a widget, or as a shortcut, we can place on the homescreen

adb shell wm overscan 16,20,16,20 Matches the curves AND reduces the risk of accidental edge-touches. Note that "wallpaper" or "background" might be displayed beyond these boundaries. BUT not all programs handle it correctly. Various odd issues. e.g. the Danish National Broadcast DR.DK TV-app, gets confused, and adds additional borders when attempting full screen.... Problems like that typically occur if people coding are not consistent in working with the size of the physical or the logical display. Fiddling with the density also, can fix some, but can make it worse f

I can launch the activity, but when attempting to crate a shortcut it does not appear on the homescreen (nor app list). (it is launched disregarding the selected dark theme though) Output from similar app