EskeRahn

on 1) I've been quite fond of VLC, and it works on the Pro1 too. on 2) You most likely have selected "US qwerty", the odd thing is that you shouldn't! De-select ALL tick-boxes to use stock F(x)tex qwerty. YES it is odd, but if you do it acts as Erik writes above, and the symbol over the numbers then needs the arrow and not Shift. You might want to have a look at the free open source project FinQWERTY that offers an extended keyboard experience over the stock one, not installing any fancy stuff, 'just' offering improved key-mappings. E.g. both the yellow arrow and shifts give access

The second part swiftkey can do. Surprisingly (to me) it supports a physical keyboard quite well 🙂 On the first, Have you noticed if it happens anywhere or in Chrome? I understand others see keyboard issues inside chrome.

It is an odd bug in google sheets. Try with usb debugging on and ADB adb shell input keyevent 62 it matches a press on the spacebar by sending a KEYCODE_SPACEBAR

That is VERY interesting as others have reported some keyboard issues in Chome, with it accidentally repeats keys. See this

Let us straighten things out. the dimension you are giving is the OUTER dimensions. Is the case you bought listed as intended for a "P20" that is 149.1 x 70.8 x 7.7 mm (5.87 x 2.79 x 0.30 in) or a "P20 PRO" that is 155 x 73.9 x 7.8 mm (6.10 x 2.91 x 0.31 in) see this

I merged the threads... See about 6-7 hours back where we were looking at these double-cases, what is important for us is whether the display part goes over or under the bottom part.

Ditto 🤣

Or if one is ordered for a "P20" without the "pro", that has no chance of a fit....

Remember it is P20 PRO. (A P20 is 6mm shorter and 3mm narrower than the P20 Pro, so no chance that something with a fit for P20 will fit a Pro1) But apart from that, with over experiments we are applying something intended for another device. So it COULD be that the extra tolerance/slack in one case over another can make them both sit perfect (though more or less tight) on the intended device. Yet they could be too tight or too loose for he Pro1. Though the dimensions are similar, they are not identical, nor are the profile of the sides. So if you do not have access to the intended d

Well it depends on how people use it. If they use it for unlocking the phone only, and not for authorising any sort of payments or the like, it could make sense to let the hand unlock. On the other hand I would certainly not use it either if used for authorising say payments.

That is interesting. Would be interesting to know if it for others too are limited to Chrome. This might help debugging if it is Chrome that is somehow interfering with the keyboard.

Oh I meant duplicate in the .kcm no fancy software (FinQWERTY is not 'active', it is just an easy way to present the system for prepared .kcm files on a non rooted device)

Oh I'm on the 3.dk network, and have no networks issues either.

I tried, and can confirm my deduction from what people told me they heard. Held to the ear I hear zero problems. But hands free there indeed ARE issues. To my experiments it seems like a matter of a minimum LEVEL of the incoming sound to the microphone. If I speak clearly like I would naturally do outdoors or to a meeting it gets through just fine, but if I lower my voice (including mumbling), it is cut away, though not immediately, but sort of faded out. A guess could be that it is the algorithm that is meant to filter out background noise that needs to have its bottom level r

Vil du ikke nok være sød at lade være med at skrive på dit eget sprog, det gør det uforholdsmæssigt svært for andre, tak. ...Or in short: English only.

You might consider the trick we 'invented' for the FinQwerty to let Ctrl+Arrow mappings duplicate those for Sh+Arrow, as you at both sides can easily press Ctrl+Arrow with one finger. (So when swapping Fn and Alt in your mapping it would be Ctrl+Alt)

I think that the 3mm difference is way too much to have it fit. I think looking for the Samsung Note 7 on other sources than ebay may be more fruitful. Until now I only found bottom-first type.

Odd, then there is a bug in the android doc quoted above 😥 : Though it does not say if the same goes for Fn and Ctrl too. Could there be other settings overruling the type? I mean something only available in Full, that when used makes it ignore if you select Alpha? Are you sure you actually get "Alpha"? Does it do auto capitalisation (without swiftkey) ?

Hmm, I guess I better do some experiments... I think calling another phone with a headset and muted mic, should make it possible to see erhm hear if there is a clear pattern in what is going on. E.g weakening the signal by putting the phone in a partly closed microwave should force it to increase sending power, and that could make it worse if caused by interference.

Not besides Galaxy Note 7. This is my brutto-list

Just to be sure. We do agree that it is the inner SIM-slot that is SIM1, and the dual-slot SIM2, right? If I set pin-request on, it on boot ask me on pin for slot 1/2 matching that. I do not see the message you mention on boot though.

I do not expect to here anything on the subject before general availability of the device. If a Scandic mat was available and easily user replaceable I would also buy some of them. But as I understand it, the keyboard is the only thing glued on, needing a heat gun. So not super user-replaceable, and I assume swapping it our selves would void the warranty... (Though I bought a heat gun for the purpose already....)

I have similar issues HANDS FREE only, but recording a video is just fine, so not a mic issue as such. So I HOPE it is something they can fix with a software fix. My guess is that it is the noise reduction using the signal from the second mic that is teasing, but have not tried to do explicit testing. If I plug in my earphones with a microphone everything is fine. And the other end is also happy if I hold the phone to the ear...

It certainly would not be a first with wrong images on bay... We will have to wait and see. Usually there are many almost identical designs copying another, but could also be principally different. There could be a problem with those that goes screen first, as it might have an 'edge-notch' the bottom part is supposed to grab (the renderings sort of indicates that), and if so that could be bad for edge operation of the display.... ADD: I tried to see if I could find similar for a Samsung Note 7, but here it is back-first only, so that strengthens my suspicion that the scre

It would also be elegant if you could choose based on country code. If you are inserting a local secondary SIM abroad, it might well be the cheapest to use your standard SIM to call home, but the local SIM to call locally and data. A bit spinning off from your topic: It is odd that more things are not per contact. E.g. when you text with a contact you are quite likely to do that in the same language each time! So assigning an active spelling/typing language to a contact seems bleeding obvious - they could even offer to set the default by the country code unless you override.