Leaderboard

The Pro¹ is just too powerful. Phone too loud at lowest volume. Screen too bright at lowest setting. Keyboard too awesome even when backlight off. Where does it end?

Tested with 512GB of card and it works fine. I think it should work up to 2TB.

That feature should be possible since OnePlus kinda had that feature by accident https://forums.oneplus.com/threads/oxygenos-9-0-0-ota-for-oneplus-5-and-oneplus-5t.970309/ "Q. Why my Fingerprint does not work, after my phone is in standby for long time?A: The Fingerprint service goes to sleep and thus doesn't allow unlocking the phone. To avoid this, the current work-around it to turn Off Standby Optimization in Advanced Optimization Battery Settings or wake up the phone using Power button after long standby." So the "Fingerprint service" should be hibernated when screen is of

Glad to hear it, BUT your still stuck with that darn portrait keyboard! 😁

Hello I have just received my pro 1 however due to the lack of instructions I have two bits I am struggling with was wondering if anyone could helo me 1. I cannot get my apps to go into landscape mode when the keyboard is out 2. How do I assign keys to open apps from the keyboard Thank you

Mine doesn't do that at all. You might check the screws. If any sticker is not flush, it has been suggested that it indicates a screw that is not fully tightened. Don't know if this helps.

Same boat. Just checked and mine is now in Oakland. Getting excited. Possibly have it earlier than Wednesday

Currently there isn't an option for that and I don't know about other solutions to do it without rooting. However, I have not tried it, but I think if you download FinQwerty's apk, and modify the appropriate .kcm file in this archive and install it directly instead of the original application, it should work. ...or if you make your own build like I did.

It is possible to lower the screen brightness with root access so that might help. If root it not an option you can try some "screen dim" app from Play Store also. https://play.google.com/store/apps/details?id=nu.lower.brightness

Unfortunately there is no way around. 😞 You could try to backup with adb backup after you enabled adb over usb. It may work for many apps but not all, because the apps can decide if their data gets backuped or not. I fear that's the only option you have without root. If you plan to re-lock your bootloader, beware that it will reset your device again.

You may find them here.

@Waxberry wrote it will be fixed in next OTA. It may come somewhere after the Chinese New Year celebration. As of Sailfish and Lineage OS, as far as I know, it is already fixed.

Indeed I am. Now we'll have a small sample size for how the Pro1 does in the bitter cold we've been getting as of late. As for you being the only one in the state, there's a good chance of that being true for a bit. Mine hasn't moved from the sorting facility, and I live in the suburbs. But hey, I'll know who it is if I happen to hear a random clack in the wild. 😄

I can't decide if I like it since it adds character or if it is mildly infuriating and will keep me up at night. I guess it would be an easy fix that I could do myself but then I have to take the stickers off the screws. It also does not effect the usage of the keyboard and everyone that I showed it found it hilarious 😄

If it was me, I would ask them to send you a corrected keyboard and then you'll have a spare in case the original one wears out or the letters wear off. That seems fair, since you do have a defect. However, I'd use it and think fondly of it, as others have said, by being unique and also a reminder of the special nature of the phone, in general. And each time you see the upside down 3, it will be a reminder for you to send negative karma to Steve Jobs, wherever he may be, for putting all of us keyboard lovers in this minority situation. 😉

Captains log: I can't remember what day it is. It's been so long since the last time I've used a QWERTY keyboard. The slabs have taken over every country, it's terrible, all those innocent people have been brainwashed. I had started to give up hope, but the Brits retaliated. We have got to help the resistance, my battery is almost out, long live THE CLACK!

There were prototypes which were given serial numbers. That accounts for a few. The remaining discrepancy may be a small failure rate and those defects having received serial numbers. There may have been other reasons for skipping serial numbers that I'm not aware of. I specifically said "as many as around 800" because we don't know the exact number of units shipped. We did see a picture of a pallet of boxes that could have had as many as 600 phones on it and we had between 100 and 200 units that we were pretty sure had been delivered before that pallet picture. If you want to assume th

So... it looked to be strange as I feeled there is a problem somewhere but not really found it. Battery usage was not seem to be radically high nor the system showed extreme usage of apps and I could also not find its cause in other apps. CPU usage was also not showed to be high by those application what@EskeRahn has linked and it seemed CPU frequencies are also changed frequently - so system looked to be relatively good, but I still had several characters while typing on Pro¹ keyboard and also had long-press effect time to time on touch interface. Moreover, scrolling was not really fluen

It sends KEYCODE_SYM. "Symbol modifier key. Used to enter alternate symbols." iirc this was meant to bring up the emoji selection too, but Alt already does that (they moved the label then). It's a modifier that can be used for bindings, but no default mapping seems to use it.

@Hook I guess I see your point, but I'm not even sure that it would be easier for F(x)tec personnel to take notice of a new bug in the pinned thread than it would be to notice a new thread. It's of course unfortunate that not even the features of the (commercial and thus being paid actual money for) forum software have been used, i.e. by creating several forums, one of which could be reserved for bug reports. This is something that still could be quite easily improved and implemented, by the way. [Correction: There actually *is* a category called "bug reports", but as this forum is

As of version 1.5.2, SYM in Finqwerty wakes the phone when the screen has timed out without having to reach in back. Google Play doesn't always have the latest version of Finqwerty. https://github.com/anssih/finqwerty/releases

Indeed, sad but true. It's currently not working in 17. I'm hoping they will figure that out. And if they don't, me or someone else likely will.

This one would be the perfect device for a lawyer. Legal sections are more important than numbers 😉

Right, but one big thread containing all bugs anyone might have found gets less and less practicable for someone to comb through, and it gets less and less sensible to suggest someone should before they may be allowed to mention something themselves – the more so as forum search always only finds so much... And it hasn't been officially "confirmed", either. As others already suggested, things would probably be different if F(x)tec would set up a real bugtracker...

I thought keyboard mat is in one piece but maybe it isn't. Hmm, if it is in one piece, F(x)tec may send a replacement part and maybe replacement stickers, but... ...in the world of money, I think these special differences make it worth even more. I am not sure about technical devices though.

In my opinion it adds rotates character. I had no idea the keycaps were individual separate things, that's quite nice actually.

The typical installation method as described on XDA won't work yet on Pro1, because we don't have a fully working version of TWRP yet. But never fear, it's still easy, five simple steps and you will have the privileges you so rightfully deserve on your own device. 1. Install Magisk Manager App on Phone Download from: https://magiskmanager.com/downloading-magisk-manager or github. After download, install the apk, which will require you to allow the install from "unknown source". 2. Install Android Platform Tools on PC (adb & fastboot) Ubuntu (and presumably de

I would try to find some tiny rubberised adhesives to replace the ones hiding the screws at the four corners of the back of the screen. FxTec could provide them and maybe upgrade their production line.

I think it shouldn't do that - not as extremely as in the video. A personal fix would be a soft black tape taped on the bottom of the screen side so it will never be visible, If it can be solved by tightening a screw, of course that would be perfect.

By the way, now that this thread has been revived – I withdraw my earlier statement; if I won't get my device before Dec 25 2020, I actually might ask for a refund.

FinQWERTY certainly looks like a util I'll be installing as soon as I get my Pro1. ...Is it possible to use custom KCM files? Being able to custom define our own layouts would be the only thing that could make it even better.

To be honest it seems to me that on my replaced screen the brightness on lowest setting seems still a bit brighter than say that of the Samsung Galaxy S8. But I think it became better than with the original screen. I hope someone will be able to compare side-by-side.

It's not that simple. Such behavior could cause collision with many other apps (i.e. keyboard handlers). It's not in FxTech's (or any dev's) power to handle all exceptions and key-combo fallback situations for all possible apps. I also think they went with current solution for time being. Let's hope some skilled devs will jump up and improve this.

Yes - I have just tried to remove then reinstall it and I had the same problem. Even a single keypress is slower to respond but also experienced multiple keystrokes of the same button when it was active.

How is this a launcher feature though? It has nothing to do with the launcher since you actually bypass it by using keyboard shortcuts. Lol why would any launcher implement that for a niche device like the pro1 that most people on this planet have never heard about? And again, a system setting or app would not overrule any launcher since it has nothing to do with the launcher. It is only specific to the keyboard of the pro1. You press some physical buttons on the keyboard, you don't open your launcher first to do that. If anything, it's more a driver thing than a launcher t

LOL :-)

[Jeopardy thinking music plays] 😉

I used keymapper to make it into a slash key.

I've not seen a thorough discussion on the subject, even on internal lineage slack. With several hundred people making up lineage, there are undoubtedly people who want it and people that don't. The major reason it's been dropped is that the security changes in Q make it even more difficult to support. Since it's not really a core feature it will get done last. And if it turns out to be really difficult or intrusive, it may just get dropped. At least until someone with the motivation and ability comes along.

Couldn't withstand it any more - Pro1 running SFOS! 😄😍 feels like. .

Never! Termux running vim - or nothing at all! *g*

Now who's got no. 1000 ?

Will give you mine for exchange, it´s a one-of-a-kind. I would not recommend to take it apart to peel of the button and reseat it. As far as I can tell, single Buttons are not meant to be replaced/torn off.

Lineage OS devs in general seem to hate Magisk, I think for valid reasons. I saw a dev on reddit make a good case for why it's bad once, but I can't find it now. Basically, the whole point of Magisk is that it allows you to change important things, while hiding itself from the rest of the system. This allows you to have root and pass safetynet so you can use banking apps, but if anything malicious gets access to that it can just hide itself as well and do some very nasty stuff. I'm not sure how likely it is something malicious will get access to Magisk, but it's definitely something to keep in

Have the same, looks awful. Is it software issue, or we just have bad AMOLED?

I had fedex 'delivery scheduled' for next Tuesday. Checked tracking yesterday, showed the unit arriving in Japan. Got an email this morning 8am saying 'your delivery is on the van' (in the UK). Arrived by 10am Flashed SFOS by 11am Late for work - luckily I work for myself, so will give myself a stern talking to later on when I get a quiet moment. This evening I may buy myself a beer by way of an apology (QWERTY, order 48xx)

In theory, after Jan 3rd update there should be no more issues with screen frozen and keyboard lost. We are working on the current issues and hopefully to deliver a build not too long after the Chinese New Year: - To fix the driver with keyboard that enables any two keys to press together (already fixed under Sailfish OS) - To fix the sound cracking issue with some music and whatsapp - To Re-map the esc key back to esc instead of back - reduce the sensitivity of double clicking power button so the camera short cut doesn't launch often And more fixes on the pipelin

Short cuts works, and are set up, from the home screen. Press the Logo F key, and do as described above. Just tested, works fine.

@netman is the community developer we need, but don't deserve!