EskeRahn

It is in the official Android Market too https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup

Someone posted that Shift, Alt and Meta gets sticky, So IF they change type to Alpha a fix could be to change so the yellow arrow keys to send right&left Meta rather than Fn, and obviously adjust the key-maps to reflect this. Still Ctrl would not be sticky though.

Indeed, very interesting. let me tag @Waxberry, to make sure he sees this....

Yes, I got that. My point was that it would require a hole for the earpiece, unless you slide it 1cm up during calls. On the last part I would consider to mount it in a £1 clear silicone shell, and then let that be attached to the case.

Yes the first looks like a good fit. Though aud$30 (about us$20) is a bit on the hefty side, as it is plastic and not leather. But in contrast to the other slide and flip cases mentioned earlier, this one uses adhesive, and this means no problems with the side buttons, so absolutely interesting, and at the most a hole for the secondary microphone when slid in. (and for the earpiece if mounted flipping to the right not left, unless you just slide it 1cm up during calls), The 160mm is also a good fit, as it leaves a little space for magnetic plugs for the USB (and 3.5mm if you can get

Personally I would be more interested in the opposite: Something turning Off the screen (including touch sensibility) when the proximity sensor is activated. E.g. closing a flip-case or simply putting it in a pocket.

Flip-case....

Oh! Thought it was the charging 'only' that did not work. Sorry. As @netman said, the port could be the issue. But also try to simply blow into the port. With a little luck it is merely pocket lint in the plug. Also try with good light and a magnifying glass (or a macro camera) to look into the port and see if you find anything that looks like it should not be there. But still make sure to select Aeroplane mode, so it drains slower while looking for a fix.

I accidentally had a Pro1 depleted beyond the point of turning it on in about 100h, but as the above flag was earlier set, it did start charging (charge icon only) After about a quarter of charging I booted it, and it is just now charging and powered on.

If you got swiftkey installed, it kills that feature, but it brings it as a touch button in its own bar.

First put in aeroplane mode, to prolong the stamina. Then put in in fastboot mode and from a pc execute fastboot oem off-mode-charge 1 Turn it off, and see if it charges correctly. Try different cables also, not just different adapters. (If this flag is not set, it turns the phone back on when power is applied) See also e.g. this

You need to have usb debugging enabled, and ADB installed. Then we can execute fastboot oem off-mode-charge 1 EDIT: from fastboot mode, see Craig's correction below.

...See the below examples, The Snapdragon camera can get a little confused on the icons though (see the last two). (Pressing power to take a screenshot often takes the focus away, hence the black images)

Odd. Could it but app dependent? I have no idea if an app can set signal something to the OS on minimum requirements? What Apps did you try? Even "Settings" and the "Snapdragon Camera" apps works here. ADD: The minimum size is about 30% though.

See other threads, easiest, install FinQwerty

Yes. Never used for anything than testing though, so could be app dependent. Took two stock apps Chrome and Android Market, and they can be adjusted just fine in portrait. Obviously it is also easier to change in portrait, as many programs got scrolling anyway. Changing in landscape would require much more of the UI design.

Erhmm.... Have you tried pulling the split-divider? A Sorry, just tried, only seem to work in portrait - how odd ADD: And it acts rather oddly if you press the home while in split, without dropping the split first. This CAN give us an asymmetric split in Landscape.....

Oh certainly doable, but the question is how much tampering with the stock android that would be needed. I think they now let Android do all the keyboard handling, only having made the mapping files to handle the key mapping, but no 'logic'

Nice. On the keyboard, I would extend the list a bit of other non-obvious things (in no particular order here) Alt+Tab and Alt+Sh+Tab : Task switching Logo-key : Home Alt+Sym : Reawakens keyboard-light like close&open (FinQwerty only) Ctrl-Space : Rotate between installed keyboard-layouts (e.g. US and a national one) Alt pressed and released : Launches Emoji (Does NOT work with SwiftKey installed 😖) Esc : Back (If FinQwerty installed ONLY Back if the app does not use the Esc key - e.g Termux does) Fn+Esc : Back (Even if app understands Esc, Fi

Oh, and still not allowed to do it. haven't got any good ideas there...

I guess the ones where it works are rooted. I have not played around with root on the Pro1 (yet), so others know much much more on that.

Same here, does not exist, and requires higher privileges to create. But could make sense that it had a default value, and if the fie is present it reacted on it.

The same I so on Pro1 as your Moto Z3, so must be stock android... Under notification I can select the noise but not the level.

Yes really odd. Only tried out the most basic of the launcher, not open&close. For some reason F(x)tec have chosen the 'keys' to be sent at close&open as F5 & F6, so at first I thought if total Launcher reacts to those, but that is NOT it. If I fake the keys by one of these adb shell input keyevent 135 adb shell input keyevent 136 The bug does not follow. So the slide open/close does more than just sending those - that was new to me.... Interesting... ADD: Please note that the above is not entirely correct, @Sean McCreary pointed out that it sends Fn-F5 &am

Yup. Try FinQwerty