Leaderboard

Regarding the slider causing the device to sleep, this is a build time configuration that, as far as I know, has no run time setting. So I guess whichever people like the most is what should be done. Personally, I find it very frustrating when the device goes to sleep on closing the slider because I frequently open the slider to type some text and then close it to go back to portrait/touch mode. Regarding wake on keypress, I've got an idea for that and it is both pretty simple and should work for all systems (including sailfish). Just track the screen state in the keyboard drive

Thanks for all the info, its good to take a break from developing and explain things from time to time. It really helps to know the state of the project. It would be nice if FxTec took more of an interest in helping make the software work, after all they were advertising it as Linaege compatible. In any case keep up the good work and don't mind the complainers.

@tdm I agree with Polaris your post are quite insightful and the work you are doing is very much appreciated 👍

please don't !

Thank God it's just half a mind because your posts are super informative and I, for one, would sorely miss them. Thanks for all you are doing for us!

You really should be more open with sharing how you feel. 😉

A balanced, detailed comparison test (German): Link.

Great work!

Here a (collage) version with my descriptions (and colouring) added.

Isn't this a community project? Isn't this being worked on by unpaid volunteers?

So I didn't change anything on the phone (I didn't try squeezing it or anything) but it suddenly started working again. No idea why.

Whiskey helps. (is it spelled whisky? I spent a friggen half hour in wikipedia to learn it doesnt really matter, just depends if scotch/canadian/irish/american and even then, only if they want to, some american bottles are labeled the other way - the main point is to avoid anything labeled bourbon, that's evil if you enjoy a touch of rye or brandy in yer whisk(e)y)

No this update was mostly just keyboard. I'll be working on audio next.

No. Most sites will tell you that because these IMEIs are not in their data bases. There's a whole process F(X)Tec would have to go through to make that happen. It doesn't mean the phone can't operate on their network, You can try putting in the SIM. It may just work , or you may need to talk to customer service. I believe people have been successful with T-Mobile itself. Check the first post in this thread and then read through the thread for details.

NO it was not, you remember wrong, sorry... That is a MUCH OLDER screen dump, as can clearly be seen by the "Shipping globally is estimated to be July 2019" that was changed around mid June. I do not remember the exact day, but on June 17 it had been changed to "Summer 2019", see e.g. this. So you dump is older than that... We got a newsletter on July 2 saying "We anticipate that payment will be requested at the end of July, ahead of an expected shipment date in early September." Unfotunately the WayBackMachine has no points between April and August of this page. But your dump matche

test4 build is up. This has the shiny new keyboard driver and a kcm file that declares the keyboard type to be ALPHA. I am still working on persisting the keyboard layout, so qwertz users will need to "adb root" and then "echo qwertz > /sys/bus/i2c/drivers/aw9523b/6-0058/layout" after each boot. It also has the fingerprint reader fix and a few other things that I can't recall at the moment. I'll try to get new builds out more regularly now that the hard work on the keyboard has been done. Things you are likely to see in test5: persisted keyboard setting

Let us hope you get a replacement or a fixed unit quickly.

For the bug you see it sounds like it almost certainly is something with the Pro1 not handling some network changes correctly, perhaps changing bands? But the reboots others see we do not know if they are also network related, or something completely different. I guess when they fix the bug you got, we will see if it help others or not...

It remembers me the Windows method where initially they didn't even use permissions, then (by NT) they built up a proper permission system but practically nobody used it in a proper way so they started to restrict root (Administrator) permission and started using popups. Linux also has a proper permission system but it seems Android goes the wrong way by restricting user (giving no root) but the hacked root has no proper permissions. ...this is the worst possible scenario in the means of security I think...

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

It still can be network related, it's not that I was in bad reception area.. coverage is good there, but still got restarts.

yeah rebooting made it show up bit poor! 🙂

This looks more like it. Doesn't say which file system it is though, although it was formatted in the phone.

I'm insecure. I don't have any lock-screen passwords or thumbprints or fingerprints or patterns. I'm crazy like that. If someone gets my phone, they learn all about me. I just find it unlikely that will ever happen, and if it does, I'll be sad.

So, it was even worse then just hitting the power button... I was playing with keepassdx, I had extended the keyboard to type my very long password. After entry the screens did not work well on landscape so I closed and went to portrait... The screen blanked and when I hit power I had to go through the password entry all over again. I figured I had hit the power button or something when closing the first time so I very carefully closed again only to have the bloody thing lock again! I find portrait nicer to use without the keyboard extended so its not in the way, but you can always just l

I know I've said it before, but I'm amazed how well-trained Verizon customers seem to be. That you just accept these rules just because Verizon has made a political decision to impose artificial restrictions in their network is simply A-MA-ZING! Ok, sure, if it's the ONLY carrier in your area, but this can hardly be the case for everyone in this thread..? Sorry for the OT rant, just needed to get that off my chest. 🙂

If you're referring to my case, it certainly isn't network related. Because I have a friend that lives nearby, with the same subscription/operator, and his is rock solid. I did return my device for repair/replacement a week or so ago, but haven't heard anything since.

Yet another reason to use LineageOS! You'll have a slider (at least in v.16) that allows you to turn it on and off. There is also an option to select root access for ADB only, apps only, or both ADB and apps. It's a great setup.

Yes I've had this issue. Try using recovery from the other slot.

Most poeple using Sailfish with Alien Dalvik, besides f-droid, seem to like Aurora store. But I think some people have installed all google services and made play store work. I'd check together.jolla.com for more info if you're really intested. But either way, there's no official AD for Pro¹.

well if you play around a bit with magisk modules and the phone does not boot. You can flash back the original bootloader and the phone will boot again. But the problem is that you can not uninstall the problamatic magisk module as the magisk manager is not able to see the installed modules. The solution is the so called "core" magisk version. https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 I used the aproach that disables magisk modules after flashing the patched bootloader. When you boot the device remove the problematic module, de

Turn it face down?

Thanks for the response, I'll have to play with that and see if it helps.

One I spammed in the forum before, still happy with it 🙂 https://f-droid.org/en/packages/net.gsantner.markor/

We really should have two and a half foils!! One for the back, one for the under side of the display, and one for the top of the lower part behind the keyboard.... But I guess that would be slightly overkill....

Just voted

I just voted for the fxtec pro1 option. I have the skin on my Nintendo Switch already and it's really nice.

F(x)tec didn't think real hard about searching when they used parenthesis in the brand name and superscript in marketing name.

We really need stickies in this forum for info like this. I only really learned this here myself. Now, if I'm going to charge overnight, I use an older slow charger (or from a PC i leave on overnight). Quick charger is now reserved for when I'm getting ready to go out and see my phone isn't full enough, as it can add a lot of charge real quick.

Yes it is basically a rugged and modernised version of the monster wide BB passport, with Android.

I think they more generally are interested in seeing if they can resurrect some lost ideas, so I would not be surprised if they would be interested in portrait also, IF they feel there is a market large enough also considering that it will cannibalise on the Pro1, as many of us users might accept both types but prefer one, and not only new users insisting on portrait. So it is a matter of the additional number of total keyboard users that could be added to the user base.

Is there actually a concise list of bugs being kept somewhere or are we just using this enormous thread? I am experiencing the issue with all learned fingerprints being forgotten. On build QX1000_EEA_20200106110245 .

Well, I hope someone does. I'm not sure if it'd be Fxtec. When I went to the London meetup I got the impression that this is their one very specific niche that they want to work on and perfect. I might be wrong on that though. If a portrait Fxtec doesn't appear, I think it's more likely to be done by a company that specialises in filling in niches, like Unihertz.

I am wondering if this is a good thing for F(x)tec or not? In theory, old BlackBerry customers might consider buying new QWERTY slider from F(x)tec (potential customers). On the other hand, these kind of news can accelerate the death of QWERTY phones overall if people think that no one doesn't even manufacture them anymore. I have never owned BlackBerry phone (I like landscape sliders) but I am still sad that one option is gone now.

The Priv served me well for 4 years despite it's many shortcomings so it's a shame that we likely won't be seeing any more Blackberry devices but the Fxtec Pro1 is a more than reasonable replacement. The writing was on the wall for about a year though with the lack of a Key3.

Agreed. Blackberry isn't even really a competitor just like Gemini and Cosmo; there's some crososver but it's another niche. Not to mention that at least the Blackberry brand had the power to have keyboard devices shown in store. It's also another justification for people to go "I guess not enough people want keyboard phones!".

Competitor leaving the market is bad no matter what. You may not like the designs, lack of root, OS or whatever, but fact is it's one less option for people who want a keyboard. I was debating hard about getting a Priv when it came out a while back but the price was so high. I would've made soany compromises to get it too, but it was the only semi modern option for a keyboard phone

I'm repeating my self from many other threads, but do not do fast charging for a daily basis. It will shorten the lifespan of the battery. Sure the battery is replaceable but not easy user-replaceable. Fast charging is like junk food. Fast and convenient, and fine for occasional use, but very unhealthy for daily usage.

I always do that with phones for this very reason. Also those pesky emails in the middle of the night!!

Or put it face down while sleeping 😁