netman

😱🤞 Good luck and be careful!

You could try this if not already factory reset https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438 edit: also delete the files password.key and pattern.key if they exist edit2:

Did someone say general availability before christmas?

The sensors hypothesis holds water! This actually may help the devs :).

The part I felt most relevant: 11-20 17:48:02.715 6164 6164 E SensorManager: Trigger Sensors should use the requestTriggerSensor. 11-20 17:48:02.736 6164 6164 I chatty : uid=10159(com.cpuid.cpu_z) identical 1 line 11-20 17:48:02.736 6164 6164 E SensorManager: Trigger Sensors should use the requestTriggerSensor. 11-20 17:48:02.835 6164 6164 I Choreographer: Skipped 1881 frames! The application may be doing too much work on its main thread. But no idea how to get dmesg at the time of the crash to maybe find out more. I guess the developers know better though, and seems easy enou

Is sticky shift getting misinterpreted as caps-lock?

I would tell these things but I've become oblivious to what is obvious or not to others :D.

Any of these steps is under the condition you didn't already do it of course, but here hopefully complete instructions if i didn't forget something: On the phone: - Turn on developer options - Go to "Settings -> Developer Options" and enable USB debugging - [edit] Now when you connect the phone to the pc it will ask if the PC is allowed to debug the device, tell it yes. On the PC - Install ADB (on windows you may need some driver also, do not know how) - Now you should be able to get a command line where you can run adb commands, to check if the phone is connected and

If it does not happen for others may be worth further investigating, with some luck running adb logcat on a PC connected to the device via USB, and then reproducing the issue could provide some more insight to what happens.

OH haha I had no idea... So the subforums are a bit sneaky but fair enough, I could live with that.

There is no way they'll be THAT slow.

I also have been puzzled by this. But today i am damn well excited to see them, for the first time :D.

Hm when i first read i was opposed to the idea, but thinking twice, it'd work if there was a dedicated subforum for it. I still vote for bugzilla or equivalent software.

That kinda defines this as a bug. Could it be because the bootloader comes unlocked by default? Is it safe to tell in developer options to lock the bootloader? Maybe @Waxberry can chime in here :).

Since deliveries have started, I think it's worth to look back what long way they have come since the early prototypes :).

To make transfer via IBAN you also need the beneficiary name (or company name) I believe.

(still needs work, twrp can be found in sailfish howto thread here, roms in flashing thread) https://forum.xda-developers.com/pro1

Just an idea, but has it been considered to set up a bug tracking system such as bugzilla or alike for these kind of things?

It should be sorta straightforward, once you follwed the steps to where TWRP starts from the Sailfish instructions, stop and do NOT do the step where it tells to wipe, but instead move over to here: https://www.xda-developers.com/how-to-install-magisk/ [disclaimer: I don't have the Pro1 yet so this is not verified, just works the same way on pretty much all phones when bootloader is unlocked]

The bootloader should come already unlocked, so it would be a matter of installing TWRP as on the Sailfish install instructions (which has download link for it): And after that installing Magisk or SuperSU or some other tool to aquire root, via the TWRP. If you are unsure how to proceed I'd wait a short while until someone writes a guide (I would expect this comes within a few days from now). In any case, good luck! 🙂

F(x)tec has set up a special collection point for pre-order customers in London that prefer not to wait for Royal Mail.

Pre-order any other phone and ask for a delivery date weeks ahead of time... They will either tell a vague estimate such as "before christmas", or they are very much making a gamble. It's quite normal not to have an exact idea of the yields the first production runs will have (it's simply fact of life not all phones produced will pass QA tests) so the exact size of batches may not be known, or the exact time when they are ready (depending on whether they aim for a date or a number of phones). And logistics companies are not the most dependable things in the world either. Would you rather be gi

🤔 I have been shopping the wrong way all my life.

It looks that way yes, and google translating that forum also renders: The protective sheet on the screen was affixed like a PET material.