Slion

You know you can do shortcuts using the following app: https://play.google.com/store/apps/details?id=io.github.sds100.keymapper Also worth noting the following keyboard layout mods provides you a bunch of shortcuts to default apps:

No such things on mine.

I just released version 0.1.0 See: https://slions.net/resources/fx-qwerty.7/update?update=12 I still need to update the description but basically all US layouts should provide you with stock behaviour plus extras. Shift alias layouts lets you access most Fn characters using Shift too. Alt typically gives you access to some international characters and dead key. Much like on stock plus extras. It also does navigation Back and Forward. Fx key is not the Home key anymore but a modifier giving you access to default apps, F1-F12 and media functionalities. Just do Fx+H to go to Home/L

I didn't need to do that. Works just fine without Nova it seems. Thanks to you @FlyingAntero I have a functional smart case for my Pro1 🙂 Now I just need to sort out the wake up part.

Looks like this app has the same problem as Key Mapper built-in lock action. It prevents you to unlock with fingerprints.

Works flawlessly so far. Thanks for the tip. It also made me realise it should be able to properly lock the phone programmatically leading to this:

Actually there is an easy way to get the phone to lock and wake upon closing and opening your case. Just use Key Mapper. Unfortunately, it can only lock as admin thus preventing you to use the fingerprint reader. However, the source code is available therefore we should be able to implement normal lock using accessibility service. I'm not sure if wake up could be implemented in the same way. I guess it could: https://stackoverflow.com/questions/2891337/turning-on-screen-programmatically So there you go, someone needs to jump into Key Mapper code and implement those two actions.

I was not a big fan of gesture navigation either until I got myself that awesome Huawei P30 Pro last year. I'm now a gesture convert. You don't have a navigation bar anymore so more screen real estate. Swipe from the edge to go back has the advantage to be accessible from anywhere along either of the screen's edge enabling one handed operations of larger devices.

Do an online search for 'verizon apn settings' and check if yours are OK.

@EskeRahn I wonder if we could get a KCM file working by naming it using the VendorID and ProductID that's associated with that sensor, or maybe even simply the name of the device. Do you have a way to work out VID, PID and device name of that sensor?

Could you be more specific about your problem? Which software are you using, phone of facebook messenger? Is it when using it hands-free or handheld?

My understanding is that all preorder should get them.

I'm planning to refactor and expand to various Qwerty layout variants. As it was inherited from FinQwerty some characters can only be accessed using two modifiers which is very unpractical on a thumb keyboard. We will try to make sure all characters can be accessed using no more than a single modifier. In the spirit of WYSIWYG the printed layout will remain very much as intended by F(x)tec design. Fn keys will provide access to yellow prints. Shift will provide access the uppercase or hidden characters which are variant specific. Alt will provide access to hidden characters and som

You may want to open a dedicated thread to discuss audio quality under Sailfish OS. That thread was more about stock audio experience.

I would have first tried using double sided sticky tape with the original TPU housing before going this way. That should work nicely unless you are taking your phone out of the case too often. Do let us know how it goes as I might be considering a similar mod at some point. I was thinking of taking a Snakehive P30 Pro case, as the camera cutout works better with Pro1 and replacing the TPU housing. How did you separate the TPU housing from the leather? Is it glued on ?

Odd, mine is such a perfect fit on all 4 colour variants I own. Make sure you secure it to the bottom of the TPU housing especially if you are a pusher rather than a lifter. Pusher: people who think reading the docs is for noobs and keep insisting on opening their Pro1 by pushing the lower edge of the screen. Lifter: pretentious know-it-all people gifted with the ability to safely open a Pro1 by lifting the top edge of the screen. Usually equipped with just enough finger nail to operate.

Wow, so that's really happening I thought that whole project was a scam 🤣 Good to know they are shipping our headsets 😁

My favorites from those new shortcuts are the media controls. Being able to turn music on and off at anytime, skip tracks and adjust volume is just very cool 😎 That's some descent audio rendering on Pro1 with those stereo speakers.

That's the one I tried. No joy there. To be honest I'm not impressed with those default shortcuts anyway. The ones offered in v0.0.3 make just as much sense.

@wilhelmfitzpatrick I'm not sure what's that search key. I tried it as SEARCH but the advertised shortcuts are not working.

Interresting, I'll have to give it a try.

Just published v0.0.3 See what changed.

Actually I'm guessing the KCM file only applies to the keyboard device and thus does not to that sensor. Maybe there is a way to install another KCM and have it apply to that sensor somehow. However I can't find docs about it. Even a lot of the stuff I got from FinQwerty does not seem to be documented or just partially.

Sure looks like that. The events sent by the sensor are actually Fn+F3 and Fn+F4 but trying to replace those did not work either.

What are those? Sleep and wake up? Sleep and wake up are working when mapped to other keys. However the kcm file appears to have no effect on the events coming from that Hall sensor.