elvissteinjr

It has come to my attention that the Edge Block profile didn't actually export with the scenes, so I've edited the post to add them as separate files.

Gotta say, I can't reproduce this on my unit at all. Did not bother to reboot to check that part, but otherwise it's just working. The touch screen does not count as a "button" for this, right? I don't have a password on the lockscreen so I have to touch my way into some input field first. QWERTZ (this part should make zero difference except for the key label), rooted, running FinQwerty and Tasker (but turning it off didn't change a thing). I did technically factory reset from the current OTA when unlocking my boot loader.

I've had this issue, but no idea why it defaulted to that. Well, it defaulted to a silent notification here. The solution is to go to the notifcation settings for the phone app and change the behavior for the incoming call notification back to allow screen notification (or whatever it is in the English UI).

After using my Pro1 for a little bit, I wanted to share my Tasker profiles here. Tasker is that one app I've had bought just in case but never really used before. But on the Pro1 it turned out to be very useful to create workarounds for some of the software issues. That also means I'm pretty much a beginner when it comes to Tasker. This stuff does work on my phone, though. Not going to explain how to import these, nor do I have actually tried to import them back myself, but the files look like they contain everything needed. If problems arise, just ask. Force Landscape on Keyboard Out

Mine is fine apart from the typical rattle (though that's honestly not something I notice when handling the phone normally). Not flush with the case and both sides of the rocker have the same clicky feedback. Does a fine job and can be pressed down anywhere except the exact middle of it.

This is what a black to white gradient looks like on mine with the brightness set as low as possible, though the cut-off already starts being clearly visible about 50% or something. I have the latest update installed, unless I really managed to flash the wrong boot image when rooting. If so, I guess it'll be taken care of with the next OTA instead. This unit is from the latest batch, #344.

While it should be noted that it shouldn't be abused as a free trial, especially as all the credit card transactions won't be free for Fx, let alone them getting a not-new device back, you do have a 14-day return window. Just handle it with care and you can return it close to original condition if you are unhappy with it.

When disabling the "landscape orientation lock" option in the Slider settings, the phone does not report the hardKeyboardHidden state correctly anymore (stays true). I want to use Tasker to handle the orientation changes as it does work more reliably with apps that otherwise stay portrait. That works fine and until I disable Fx's orientation changer. The keyboard out state is not detected anymore then. Now, having both Tasker and the OS do the orientation change is no problem and it works. Except that one game app I have crashes when Fx's method switches to something different than w

Only had normal a Xperia Pro and a E-Ten Glofiish M800 (that's some WinMobile thingy) before as far as keyboard phones go. However, I almost religiously watched slow-motion Pro1 clacking videos more often than a normal person would. I went in fully aware what to do to say the least.

I did take some, but nothing that would proof anything per say. Almost one complete print visible on one of the photos though! Device is on by now. Everything seems fine so far! And that's with me being invested and pretty much looking for all kinds of known typical defects. I don't know what issue people have with opening the clacker either. I had no issue doing it one-handed before even turning that thing on for the first time. Sure, you need to make sure to do it right, but it's not like "damn, I can't open that darn shitty thing".

Serial Number #344 QWERTZ Ship Date: January 21st Delivery Date: February 18th Customs had their great time with it. Unsealed, taken out of the plastic bag and not put back in and full of fingerprints. However, it's totally fine apart from that. Well, physically. Haven't turned it on yet. Edit: Of course I did turn it by now but further posts were moved elsewhere. Nothing atypical. Everything is running as fine as it can in the current software state!

I'd say this really depends on how good the batteries are... and luck? I have a lot devices with now crap batteries, but also quite the counter example. My OpenPandora is 9 years old now. The original battery (4240 mAh Li-Po) it came with is still at 87% of design capacity. It's not a phone and wasn't charged that frequently in comparison, but a well kept spare could survive in a similar fashion. Though maintaining a certain level of charge could turn out being tedious since the Pro1 battery isn't easily swapable without tools, but yeah.

Which one of these two theories is more likely to explain that one unit with the upside-down 3-key, I wonder.

How? I'm very curious what suddenly happened to convince them... or did you find out you made a typo in your EORI number the whole time or something? I'm very confused. @Waxberry @Erik , pinging you again here. You very likely did something to have this happen, but for the small off-chance that you didn't, please hold off sending that other device. I'll also shoot a proper support reply here, but not sure if that'd get read in time. I'd also like to apologize to the community a bit here. Quadruple post it is now. Would break quite the forum rules if we had any. Edit: I can still

So yesterday after communication over the support system, Fxtec agreed to send me another unit straight from the UK as soon as possible (well, Monday is the earliest they can check if they have one to do so). Okay, nice. But... After 23 days, the tracking status suddenly changed. Talking to FedEx and Fxtec it seemed rather grim. What happened? If this is just the shipment going back, then it is a very confusing status. The FedEx support agent who was supposed to keep me updated asap and called me a few times when nothing happened did not notify me yet... probably since they're off

This is offtopic, but I feel like this is something I can get give my personal input on. I'm running Windows 10 Home with all UWP apps removed except Settings, automatic updates disabled, Classic Shell (maybe I should update, but ain't broken yet), OldNewExplorer to restore old Explorer UI, Glass8 to restore Aero looks, Windows 7 custom theme, 7+ Taskbar Tweaker for big icons in taskbar (and other neat things), as well as QTTabBar for tabs in Explorer (this one is slowly falling apart on newer Windows 10 builds, but still works). I like this setup, but some of the stuff is prone to brea

KEYCODE_FUNCTION?

@Waxberry Any updates on the situation already? Excuse me for being a bit pushy now, but I'd hate if this went off your mind over the weekend or something and I only noticed I should've brought it up again later. As I'm expecting multiple days of turn-around on FedEx' end, I'd love quickness where I can perhaps still influence it a bit. Having the package find it's way to me this week would be cool. I'm calm about it, but also kept seeing that some parties have to be asked again to actually get responses for some reason (lost like a week of time from that)... well that's for FedEx, but

Looks like there's one upside to my package being stuck in customs.

I'll leave handling this to you guys now, but I'm not exactly sure how Expansys would solve my situation. FedEx said they're contacting F(x)tec, the importer, for a valid EORI number. I'm not sure how and why Expansys would be the one to provide that... well they might know it, but it's your company's number, isn't it? Expansys might've been contacted in the very beginning regarding the shipment value, but I'm past that stage now, fortunately. I hope getting Expansys involved too doesn't make this playing the long game...

I usually would really avoid doing double posts, but today I got a call from FedEx on voice mail repeating my situation, but adding that the importer thing can't be reverted now. So it's up to F(x)tec to somehow provide an EORI number the German customs like... not sure if you can, but yeah. In desperation and looking at the third upcoming weekend I could've had my device for I'm gonna ping @Erik and @Waxberry here, hoping you could somehow manage to sort that out quickly. Maybe customs can muck around with the package during the weekend already then. Sorry if it comes across the wron

The UK is still part of the EU single market and customs union during the transition phase. I'd expect the Swedish Post to know that to be honest.

Still waiting for customs to do their thing... or so I thought. Just had a live chat session with FedEx and had someone who actually looked into the case properly now. Customs does not accept the EORI number provided by FxTec. Cool. To not re-tell the entire conversation there, bottom line is that FedEx may try to contact you regarding this... or maybe they won't. I've had concluded with the support agent that it doesn't really matter who is listed as importer at the end (fees are paid by sender, so Expansys) so they may as well revert that back to me. I at least allowed them to do so if t

So if I got that right, the fn key state doesn't have to be hidden for this to work, correct? If no fn mapping is set in the active kcm file, there should be no drawback from having fn be down during the synthesized key press. In theory, at least. I do have some doubts about switching between standard layouts to be practical at all even with this (physical layout just doesn't match up), but behaving closer to a PC QWERTY keyboard will probably be beneficial indeed. QWERTZ does have yellow characters on other keys, including letter keys. Having proper fn key state will probably be require

Here's mine: