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

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

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 😄

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.

Is the Pro1 launcher open source by any chance?

Right lower corner is completely silent, there's a bit of clattering around the rest of the screen, but nothing I would have considered disturbing. shaking the whole device also gives the slightest noise from volume and power switches.

How to you go about it? Could anyone with a rooted version try it out?

Neither mobile network nor wifi strengths look like what I'd expect, considering your circumstances. Drastic changes in signal strength just by taking up the phone into your hands aren't normal, either, to the best of my knowledge and experience, at least not in such a close proximity to the signal sources. Not having my own Pro¹ yet, this looks to me like there's something wrong with your specific device anyway.

@alexmarzulli Phone signal and service is tricky to report as a bug because there are so many variables, as you can see from the following thread: I'm in the US and so am useless to give advice. There are a lot of US posts in this thread because US network operators are terrible at accommodating strange new phones they don't know, but there might still be things to look at. I know that by default on the Pro 1 VoLTE is not provisioned, so if your service is dependent on that you may need to flip those switches using *#*#4636#*#* With all the new phones getting ou

Michigan here and device has been at the sorting facility since yesterday, too. I called FedEx to see if there was a chance of being delivered before Wednesday and they said probably Tuesday, but low-key hoping for Monday lol.

Expediency could be behind that design decision. Keep in mind FxTec is a start-up. They surely had to make many time saving decisions to make sure they could deliver a product. I'm with you though. Ideally we should have had global shortcuts implemented as a background service.

On Pro1 it does look like the fingerprint reader is off once the phone has been idle for some time. You have to hit the power button to wake it up, then scan your finger.

Hardly, but in the event it would be necessary, maybe by removing flash chip and to read it elsewhere. However, it is a very complicated process potentially being a BGA component or at least it needs special equipment to do it. If TWRP will be able to decrypt data before backup, that makes everything far much better. I hope for a fully working TWRP soon.

The rest of the pre-orders is scheduled to be produced after the end of CNY, meaning a new batch should be ready mid to end of February.

I haven't really investigated keyboard things yet. I've been busy getting the vendor image working in order to fix a2dp. But I know that idealte put the keyboard config files in system instead of vendor, which is why its broken. I'll put them in my lineage vendor once it's working. As for other locales, I haven't tried at all yet.

This behavior is the same on the stock build, and was raised to the CEO when I had the chance to get a hand on a prototype last year. I will try to bring this to attention again, but it's not a lineageOS specific thing as of now.

But I thought it was officially not wanted anymore? The xda post and https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/257100 kinda sound like it is being dropped deliberately. Well, I'd be glad to be wrong :)

The device tree and kernel tree will be imported into Lineage github for official support. Any changes needed for this particular device in the other Lineage code will need submitted and approved by the Lineage team. I don't have any of these changes yet, and may or may not eventually need them. The device becomes official when I tell the Lineage team that it's ready and request that they import the code. I also need to add a Lineage wiki page and etc. The device will continue to receive builds add long as at least one person is maintaining it. (There are at least 3 peo

That or increase or remove the possible number of attempts.

Now THAT's a name I haven't heard in a long time. Used to be pretty big back in the Palm OS era.

I would like to also hear about this problem as detailed as possible. Also if it is a hardware failure and also if it is a software problem... and if a solution has been found, it would be good to also hear what helped. I hope you will solve it soon.

@tdm You're one of the good guys, and I'm convinced you would have helped devyl solve the problem too. 😄 I'm genuinely curious as to what's wrong with it also. So when the time comes, please enlighten all of us on the sidelines. ☺️

By its nature, it hijacks basic system functions and hides/overrides things. That's bad in my book. Same as xposed. After 7 years of working with Android ROM development, I've seen the trouble these types of things can cause. And since they usually work fine, the device maintainer (me) gets blamed when they break in odd ways. Lineage (and previously CyanogenMod) bug forums are littered with crashes caused by these things. So the first thing the alert developer does is look for evidence of these tools and reject the bug report if found. So basically, they cause much pain

It has been discussed earlier and is build into android. It is depending on whether the keyboard s defined as Full or Alpha. See this Would be nice if we could choose either,

I think it is an LG feature. It is not in the stock android, so would require you to install an app doing more advanced screen-shots.

That is the way how the "dark theme" is working on Android Pie. System wide dark theme comes with Android 10 so we need to wait for update. Or flash Lineage OS 😉.

On 2, that is in the launcher. Press and hold any blank space on the home screen, Select Home settings Select Keyboard Shortcuts

Quick demo of my modified driver, keep in mind i'm also limited by the my thumbs and trying somewhat randomly to press this and that to give an idea what is possible.