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

Hi all, Today I tried to connect my Pro1 on my Pioneer AVH-4100NEX head unit, but failed with the message in the included image. Tried to reconnect a few times giving the same message, but after few times the message no longer came up. I restarted the head unit and reconnected the Pro1, the error message came up again the two time I tried to connect it. The Pro1 was freshly started a few minutes before. Pro1 is on the current firmware. The radio unit is on its latest firmware v1.11 built on December 8, 2018. Message is in french: Android Auto is not responding. To

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...

Android auto works just fine here but my car setup is much simplier than yours. Mostly just connecting to car audio output over bluetooth.

Making a normal phone call, holding the phone to my ear, I hear no audio. If I turn on speakerphone, I hear audio just fine. If I plug in a headset into the jack, I hear audio just fine. All my ringtones and notifications also work fine and I have no problems playing multimedia. I hadn't actually run into this until just now because I usually use a headset for calls, so it's possible it's been this way since I first received the phone.

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

The channel was advertised the first time yesterday and there will be more adverts for it. Also, the way that YouTube works, I expect a lot of publicity for it sooner or later. I'll be alright.

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.

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

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.

Another module causing trouble: Wifi QR Code Creator This module wouldn't work with Pie anyways, as I found out later ...

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?

Canada, Québec, Montréal

This happened to me too and I reported it in the Known Bugs thread. For me, it mysteriously started working again after firmly squeezing the phone shut, and it has worked since. I don't know if it was a hardware or a software problem because it hasn't happened since....

The rattle in my case is noticable when just typing, it kind of bugs me but I'm going to live with it for this iteration. A Pro² should have that fixed though...

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

Just voted

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

Put in my vote! 🙂

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.

Yeah with up to date specs TBH I'm tempted to get one, mainly as a phone to use when going out drinking beer 😄

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

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'm getting a Pro1 mostly because the Priv2 was never created. I love the design of the Priv, had a Q10 before it. Unfortunately I didn't take care of the battery nearly as well as @EskeRahn (I've only just done my homework on what I was *supposed* to be doing..) so the thing's failing on me pretty badly now. A full charge will hit 50% by evening, and then (based on some criteria I can't determine) has a chance to shut itself off, reboot, get stuck in the adroid optimizing apps screen for ~10 minutes, and then come back up with 12% somehow. Here's hoping my Pro1 gets he

Thats the problem these days no real differences between devices.

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!".

Use a slow charger. Either an old one, a charger with both a slow and quick charge ports, or usb port on a PC, or any other equipment with a low power output. I would suggest to stay at 5W and under (Many old chargers offers 5V 1A, and thus 5W). The problem is that the worst condition for a battery is charging heated. See e.g. this (This is a practical solution, though the print on the slow ports say 2.1A, it actually only provides 5W to the devices I tested, just as wanted) See also this thread

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.

(If you do not want to be disturbed, use aeroplane mode. Quick to turn on/off and saves battery)

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 😁