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

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.

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.

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

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.

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

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

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

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

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

My phone tried to brick itself when the SD card I set up as adoptable storage failed. I ended up having to flash back to stock, reapply the OTAs, and re-root as well. I had to take it back to Verizon along with my old Samsung so they could deactivate and reactivate my SIM. Until they did that, the Pro 1 would get stuck trying to register in the switch. That was per the Verizon tech watching what was going on from their end. Steps were: 1) put SIM back in Samsung and establish everything works; 2) deactivate and reactivate SIM, establish everything works; 3) put SIM back in Pro 1 and verif

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/

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

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! 🙂

We could easily get too many stickies, so people drown in them. But you are right this is important. Maybe we should have a thread over in the new "How Tos" group, on how to take best care of the Pro1. One could copy the main stuff and then link to the existing threads perhaps? It could be on the battery, on the screen protector (I think there is a rather recent thread advising how to apply without bubbles), perhaps cases, for those into that stuff. The thread could also be expanded to a "How to get the most out of your Pro1" or similar, that also pointed to (IMHO vital) stuff lake F

Yeah, it is so big you can use the back as a plate eating 😇😜 It is nice that it is rugged though 👍, To me the Passport design offers the worst of two worlds: A cramped always out keyboard and yet too big to possibly operate even partly one handed. The Key½ design I can understand, as you get a keyboard (though cramped), and a screen that at the least to some extend can be one hand operated. I mean the Titan is really Titan-sized, it is humongous. Liiterally like three SonyEricsson txt pro landscape-keyboard-sliders side by side--- (including the weight)

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

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 .

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

If I was F(x)tec I would get a portrait device in development to cover that section of the market.

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.

Thats the problem these days no real differences between devices.

Guess I didn't add enough smiley faces, or probably should have added a couple of wink ones as my comment was strictly in jest. While true I owned a Priv, never acclimated to it, and dumped it quickly, I would never want a company to stop making something just because I don't like it. To each their own, and in that regard, the more choices available to the consumer the better.

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

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

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