Leaderboard

I've just spent a whole day with the Pro1, and overall, I love the device. Here are some of my thoughts and issues. It's a thicc boi! But I'm ok with that because it feels really solid in hand. Keyboard opening clack is so satisfactory. Holding Shift + alphabet keys on the physical kb doesn't capitalise. I have to toggle Caps Lock on/off for capitalisation which is slower and inconvenient. Key modifiers really need to be sticky. I'm using the Swype + Dragon virtual keyboard which doesn't seem to play nice with the physical keyboard open. If I tap to focus in a text inp

...and in practice, it does exceptionally well photos using Google camera (so not the stock one).

If you want to unlock with fingerprint you need to use Screen Off - Unlock with fingerprint app. Screen Off and Lock does not support that. Also, you can't just select Screen Off - Unlock with fingerprint from Keyboard/Button Mapper. You need to install Nova Launcher and use Nova actions as an activity. Select Screen Off .MainActivity. You can still use stock launcher as a default launcher. I tested this and I am able to lock with magnet and unlock with fingerprint like normally.

Wow, this already is miles better than the awful Snapdragon Camera. Thanks @netman!

Her name is Juniper. I call her Juni. Ergo, she is the Junicat.

That's my Juni-cat.

You can find comparison shots between stock camera app and Gcam from my review. With Gcam you are able to take pretty good photos.

The camera hardware is the same as the Pixel 3 (Sony IMX363). That is a flagship level camera. Much of what makes photos better in modern cell phones is done through software. The default camera app that comes with the Pro1 doesn't have millions of dollars off research and development behind it. But you can run the same camera app that Google uses in their phones, so in theory, it should be able to produce photos as good as the Pixel 3.

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.

These completely different behaviours are interesting anyway.

I haven't experienced this at all.

I had a dilemma - I really like the 36 keyboard shortcuts that the stock launcher has (the stock launcher is the desktop with all the icons). I also like how well the stock launcher handles rotation. But... I really like Nova. It fits much more on the screen, widgets are much more adjustable, it has useful gestures, different actions on icons and folders depending if you tap or swipe etc etc etc... (But I don't like how it can't handle screen rotation.) So here's my fix/compromise to get Nova with the 36 shortcuts... You set Nova on fixed landscape (or portrait, whi

Hello, I am about to order the pro1. But I still have a few doubts about it... I have a blackberry priv for 3 years, changed the batterie, but it's dying again... batterie goes down to 50% to 0 % in a second. I also have a lot of overheating problems with it, and it restarts for no reasons almost everyday, sometime 3 times a day... So I am about to give up with that phone because it's getting worse. Before I buy the pro1 I need to be sure that I will not have the same problems that I have with my priv. For those who had both phones, can you tell me why the pro1 would be bette

I was filming my new washing machine today but the Pro1 camera app decided to do all sorts of random shit while recording, which pissed me off greatly. With that comes my question: is there a sane camera app for the Pro1?

It's mostly just a reminder for me to look at the code. The current lights code hasn't really been tested or anything, it was just brought along with the initial stuff from 1+5/5t.

I did a quick check. It also stops recording if I press F5 or F6 on Pro1's keyboard (own layout) and unfortunately Pro1 sends these keypresses on opening/closing event. I have also checked on my Motorola G6 using a bluetooth keyboard and it also stopped when I pressed F6 or F7 keys (yes, it seems to be shifted). So it seems OpenCamera has a function mapped to these keys and that is why it stops when you open or close Pro1's slider. It also reacts when I press yellow arrow anyway. So this behaviour will change if F(x)tec assigns a better keypress event for slider open/close f

I like opencamera, the shutter button doesn't yet work in it though (but should be a relatively easy fix in future OTA).

Ok, per your request I will file an issue on the tracker page, but please remember that it would stop working with the stock ROM, and I setup a poll to see if this was a known issue. Very few people responded to the poll, but it appeared as though it was working correctly for most. Thus, I'm not sure if my original problem got pushed into Lineage (with regard to the LED at least. The vibrate option always worked in the stock ROM, so that might be a Lineage thing?). Thanks again for everything!

It's not clear, but if you want an official answer, you need to email infor@fxtec.com. Before the phone came out they projected security updates would come within 90 days of being released. Since we currently have the September update, that clearly hasn't happened. I would expect the upcoming OTA from IdeaLTE (their software developer) to bring us more up to date, but it too has been delayed by the Coronavirus. I hope not much longer. This may all go much smoother once they are caught up and phones are in general availability. Again, none of this is official, just guesses.

My point of view as well, I'm afraid. 😉 I only have a "lockscreen" to keep from accidentally launching icons when pulling my phone from my pocket and it opens with just a swipe. I didn't keep a padlock on my old physical datebook with a lot of personal information. Why do I need to lock my phone? (I know how people would answer that question-- but I really don't like being inconvenienced 😀). Still, on principle, if there is a fingerprint reader on the phone, it should be made to work properly.

The Netherlands, Hillegom (near Amsterdam) Not having to use a touchscreen anymore, and the fact it resembles the nokia E7 (which has been my favorite phone ever, but after my third one died and Microsoft took over, I was done) I was sold.

I suspect the January OTA did some fixing of this. I used to get the greenish grey wash effect when I lowered my brightness past 50% when I first got my Pro 1 in December, but I don't get it anymore and the black rectangle in David's post above looks fine at all brightness levels.

Never thought I'd miss the touchpad on the keyboard that the priv/key[1/2] had but I do. I find myself trying to scroll through a page swiping across the keyboard on the pro1 frequently (of course, nothing happens). The fingerprint reader is better placed on the blackberry and you are going to miss the double tap to wake in the default setup of the pro1. Apart from that I can't see a down side to moving to the pro1.

Ah, cool (and of course!) I've already got KM installed. So I could use one (or two) of the modifiers to provide permanent shortcuts. Good call, thanks. I'll also check out your modded FinQwerty. Cheers!

It seems to be not an easy thing as if somebody would like to buy a new phone then it should be intact. If you use the device for days then send it back, there is high chance it will not be intact and the next buyer may receive a device which is not really new. So it is much better if you may meet with somebody around to see the device...

No such things on mine.

The work around for the fingerprint seems to be to register those parts of your palm that usually trigger the reader in error. I did the following, activate FP registration and do those task that trigger the reader. Like lay it on the table and pick it up and lay it down until this action is registered as FP1. Then move to FP2 and eg pull the pro¹ from your pocket multiple times until FP2 is registered. I did this with 5 actions and the result was the pro¹ unlocked as soon as i picked it up.

This is one of the "other issues" that I mentioned in my earlier post. The vendor data and framework data get out of sync under certain conditions, for example when you wipe data (aka. factory reset). This is a problem because the vendor data only seems able to hold 5 fingerprints and doesn't seem to ever delete its data. So once you have registered 5 fingerprints total, any further fingerprints registered will not be saved in the vendor data until the vendor data in /persist is deleted (this is why it works until you reboot). Deleting the vendor data in /persist requires root acce

KITTY! ❤️

Disable the fingerprint reader. Problem solved. :P

Finally got mine after waiting so long. I love it!

Finally got mine! QWERTY Serial #984.

Foxconn says cautiously resuming China output, warns coronavirus will hit revenue "KGI estimates Foxconn’s factories in China will be operating at 30% to 40% of normal production levels by the end of February"

Experimented with a slightly different approach that might be helpful for those that do not like any of the other techniques. Simply applyied a tiny strip of high friction tape at the back edge, with this it is so easy that you can even lift up using your nose(!) ...Yes I actually tried it...

Been hacking on the lights HAL this morning (shhh, don't tell my wife). I think I've got the logic figured out so that the keyboard backlight always keeps the proper state (which is, on only when both the screen is on and the slider is out).

Ugh. I just noticed there are no black stickers in what I ordered. Lol

I think I found a workaround for this issue. First you have to install this Magisk module: https://forum.xda-developers.com/apps/magisk/module-universal-deepbuffer-remover-t3577067 Then place script from Viper4Android (you don't have to install Viper) in your service.d folder. You can find mentioned script in attachment. v4afx.sh

Got the same problem. Fixed that issue by finding updater app in all applications list and clearing its cache.

I'm planning to refactor and expand to various Qwerty layout variants. As it was inherited from FinQwerty some characters can only be accessed using two modifiers which is very unpractical on a thumb keyboard. We will try to make sure all characters can be accessed using no more than a single modifier. In the spirit of WYSIWYG the printed layout will remain very much as intended by F(x)tec design. Fn keys will provide access to yellow prints. Shift will provide access the uppercase or hidden characters which are variant specific. Alt will provide access to hidden characters and som

Poland, Kraków, also occasionally Poland, Przemyśl

Just west of PHILADELPHIA, PA, USA Heck, if you like it I'm willing to sell!

Those could easily be integrated back in FinQwerty.

My serial number is "only" 606. Thank you. Best wishes. ~~~~~~~~~~~~~~~~~ Per aspera ad astra...

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.

@shani You will get used to the mechanism it in a short time and hopefully you will change your mind. If you have ever used Nokia N97 (Mini) E7 N950 you will probably this is a "feature" instead of a design flaw. I think the only this that can be mis-leading is calling it a "slider" with the fact that it uses a lift-turn hinge. "Slider" would mis-lead user to think it slides like Droid 4 and can push from middle of the screen. (Instead of lifting / pushing the edge) Maybe we could invent a new word calling this?

All the others would include n97, e7, n950... In my opinion they made the best possible choice.

We know "if", as they said so. But not "when". I think it is @netman that already did a port by himself, and it only had minor issues, so I expect it wont be long after the rush with the pre-orders . but just guessing.

Main issue with the camera seems to be that the lens they used is quite bad. Lots of distortion. Test taking a picture of a calibration pattern. Sharp in the middle but quite blurry and distorted at the edges. Sure this can be compensated for to some extent by software, but a good sensor isn't worth much if the optics in front of it are bad.