Leaderboard

I found some missing libs yesterday. I almost pushed a new build but decided to wait until I investigated a2dp a bit more. Should have a new build in a few hours either way.

Thanks to tdm, mccreary, and everyone who has contributed to aosp, cyanogenmod, and lineage OS, as of test6 we now have keyboard shortcuts, referred to as Bookmarks. Since the lineage thread is getting long and too many topics, thought it might be worth starting a thread to share this info. The Fxtec logo key (Fx, now assigned as Meta) in combination with various keys will perform certain functions and with letters open certain types of apps. The first time you use it, it'll let you choose which app to set as default. Here's the App Bookmarks I've found to work: Add (Calculat

test7 is up. This has some missing audio libs that should make audio behave better. Please test and let me know. a2dp is still broken but other bluetooth functions seem to be okay (tested file transfer). @EskeRahn this will hopefully make [email protected] behave better. @EskeRahn no I didn't do any screen calibration that I'm aware. @Kabbone yes double tap to sleep works.

I had asked the same message via Email and got the following response:

So I said other cool features. How bout wake on keypress? Now it works for every key. And backlight too. You can move the status bar time back to the right in settings. You can select which orientations are permitted during auto-rotate. If you think your phone works better in portrait upside down, disable 0degrees and enable 180. If you dont want it to accidentally upside-down landscape and confuse you when you try to open the keyboard, then disable 270. Also by default, it displays LTE to indicate 4G connections. Someone complained about this in stock, I assume th

I see these ghost touches when a certain charger is connected. On another phone, I had ghost touches in strong winds...

When I tapped the third one down in the list, nothing happened. Then 20 minutes later someone banged on my door. When I opened it there was a guy standing there with a take-away demanding £15. 😯

One more feature request - a way to lock from keyboard. I often leave my device sitting on my desk in landscape, and its awkward to reach around back to lock. If I could do from keyboard somehow, that'd be great. If its possible as a bookmark, meta/Fx+something would be great. Otherwise, left-slant-arrow plus something would be just as good.

I recently contacted support because I hadn't recieved the update mails and they wrote that part of the staff is already at the factory again. There might still be problems with recieving components from suppliers and obviously they cannot produce at full output, but at least it seems like something is going further a bit :)

Unfortunately, not speaking about F(x)tec, the same case applies to Chinese manufacturers... basically nobody knows what is going to happen.

As a longtime physical keyboard lover I waited with a lot of anticipation for the Pro1. And waited. And waited. And waited. Finally, January 2020, when the $650 I spent on the phone seemed the most ridiculous, the phone arrived. Nevertheless, I was excited and immediately unboxed. Right away I had such a miserable and frustrating time applying the screen protector. Never had such a pain with other phones but no matter what I did countless bubbles and dust particles made the final product look like total crap. The whole sheet ended up crumpled in a mess in the garbage can. This would set

Logged in hoping to catch @fxyo1 before it's too late: Please dig it out of the trash!!! There are LOTS of useful components, I would personally pay you cash for it. I'm sure others here or on Ebay would too. Like hundreds of dollars. - Battery - Keyboard - Shell - Main Board / CPU / RAM - Buttons / Sensors - etc It's just that these phones are so rare. Having one for parts is still super valuable!! I hope I caught you in time... otherwise what a waste 😭

@Craig I'll respond once here... In theory gapps should persist from install to install. If that is not working, someone may need to investigate. You do not need to re-install the recovery once you have it. I'll try to get the instructions updated. The slant arrows are fully dead keys in the current Lineage build. I would like to make them customizable but haven't gotten there yet, as there are higher priority issues. After they are customizable, however, you will still need to keep at least one key as KEY_FN (or whatever I decide to make it) for a fully dead modif

Ordered September 20, no tracking number, no stock assigned. Didn't think of canceling. Waiting for production to restart.

Ya now you mention it its possible with keymapper too. But I was thinking something built in, ideally I dont want to have to run keymapper or tasker, be able to do everything just by editing files or settings etc (even with adb root shell is fine).

Most humans do start with a tricycle before bicycle for that very reason, sometimes for years. And then some even switch up to four wheels for a while before going to 2....

@roland I love how 'stiff' the keys are. And after just a couple minutes typing on it I can almost type blind. Always interesting to see how different our silly human brains work 😉

Unlikely, but we shall see. The change that enables the accent chooser is the same one that enables sticky shift: setting the keyboard type to ALPHA in the kcm file (instead of FULL). I'm not sure if that can be overridden. Perhaps others could investigate.

This can easily be done by setting it to thumb keyboard instead of full keyboard, which I expect they'll fix in next OTA But, I dunno if this particular feature will play friendly with the longpress shortcuts they added to their launcher. Longpress accents would most likely still work other places outside launcher of course... (and the bookmarks I mentioned above are global, unrelated to launcher, can switch app to app that way) and you don't need them while using the launcher, just dunno if it could interfere.

It has come to my attention that the Edge Block profile didn't actually export with the scenes, so I've edited the post to add them as separate files.

My friend told me about this strange behaviour a few weeks ago. Before that I ran into this problem but as pressing an other key solved it, I didn't really care of it. A little bit after he said it I ran into this thing again and showed him if he is speaking about this behaviour. It was not after a reboot but I have opened the keyboard and started typing... so I showed him I pressed one of the buttons several times and nothing happened... then I have pressed a button nearby which appeared and then the previous button also worked. Anyway, I thought it is much better than the previou

After using my Pro1 for a little bit, I wanted to share my Tasker profiles here. Tasker is that one app I've had bought just in case but never really used before. But on the Pro1 it turned out to be very useful to create workarounds for some of the software issues. That also means I'm pretty much a beginner when it comes to Tasker. This stuff does work on my phone, though. Not going to explain how to import these, nor do I have actually tried to import them back myself, but the files look like they contain everything needed. If problems arise, just ask. Force Landscape on Keyboard Out

Well, yes, but if you register the part of your hand that causes inadvertent reads, the reads would be successful, and there'd be no lockouts, correct?

hello guys, I finally got my Pro1, the experience has been pretty good, the camera aspect is well, serviceable, but the most annoying thing is the fingerprint reader registering inputs when you just hold and grip the phone in your hand when it's locked, leading to the dreaded "too many attempts, try again later" prompt. I think the proper fix (apart from not enrolling into fingerprint unlock) is to only turn the fingerprint reader on when the phone screen is on. The big question is: is there a way to disable the fingerprint reader from reading whatever it's placed on it when the screen

I agree on that. People have different hand size, and more or less dry skin, so how much each is affected is quite different, so would be nice if we could compensate it. My personal favourite would be the most primitive approach. Present the API with a reduced 'physical' size of the display, So people can select as wide bezels as they need, that are displayed black, and independent for the two sides. This might require a boot after changing the bezel size, but that would be acceptable in my book. Having it happening in the HAL-layer, would mean that there are no programs that would ever k

And some switch back from two to three when they get old... 😂 Would it be pushing it (excuse the pun) seeing a plain keyboard slider as a handicap friendly version of a real keyboard device like the Pro1? 😇😇

I'm quite happy with how keyboard is functioning in LOS, it's certainly better than stock in some ways (ALPHA, meta, right-alt) but worse in others (stock has both slant arrows on same keycode, now LOS seems they have no keycodes at all). There are two things I want to customize to make it ideal for me, and I can't figure out how to do it. How do I assign the right slant arrow as key to behave as standard slash/questionmark key. I don't care if this requires root or an external app at this point, I just want it to work, this has been my number one complaint with Pro¹ since the

Is there a recommended procedure to go from one test build to another and keep gapps working? And is it necessary to flash the new recovery each time also? When I went test4-->test6 I tried to follow the step by step again, just skipped the new recovery and the factory reset, but did flash mindthegapps again. However still google apps crashed when ran, had to manually unininstall and reinstall everything I wanted to work (i.e. maps, gmail, hangouts, etc).... I assumed this is cuz I botched the upgrade somehow.... Perhaps @tdm you could update your webppage instructions to not

I thought I only got it at boot. In reality, I get it at boot and any other time the screen goes off.

This is for stock... https://github.com/tdm/android_kernel_idealte_msm8998/blob/oem-history/drivers/input/keyboard/aw9523b.c#L1901 https://github.com/tdm/android_kernel_idealte_msm8998/blob/oem-history/drivers/input/keyboard/aw9523b.c#L865 I changed those in Lineage.

I have the same issue with another phone after a screen change. One side isn't glued perfectly so the screen sticks up a millimeter (I didn't bother renewing all tapes since I expected the Pro1 soon after). In my case it happens in cold temperatures, often conneted to temperature changes (and therefore humidity changes). I think it's humidity in the screen/electronics so check for small gaps where water could enter. What you can also do is heat the thing up evenly (no more than 40°C) and then put it in the fridge for 15min. This removes water from the internals due to vaporization.

Will this device get on the AER list? My employer only allows for Android devices on AER.

I am mostly hoping for OTA soon so that people don't grow any weird habits by the time it comes :D.

Darn... Okay, so we just need a little robotic spider that sits under the screen and every time the screen is turned on, he runs out and taps the Sym key. 🙂 Or.....we can hypnotize every Pro1 owner so that they tap the Sym key every time when they first start using the keyboard.

There will be 8 keys to find. It happens because a register in the keyboard chip gets initialized incorrectly, I don't know exactly when android decides to re-initialize, but it does not care whether the keyboard is retracted or not. It'll depend on what apps are running, time of sleeping, and some mystery factors that I won't even try guessing at. I don't think the modifier keys can wake it, but not 100% confident, I solved the issue for myself so can't test xD. Sending keypresses artificially won't do the trick, the keyboard driver needs to receive an interrupt from the keybo

Ding ding ding!!! You just won the fake prize of the night! 🙂 My phone had been sitting a while, so I tested out your idea, and sure enough, the 7, Y, H were dead. N was not, but maybe I bumped something else before trying it. Oh, I just looked above, and maybe on the QWERTY, it is the B key on the bottom row that would be dead. I'll test that in in the morning, after my phone has been sleeping. But I think the mystery is solved. Things must need to be re-initialized after sleeping, so the register issue happens again, just like when the phone is powered on again. Maybe it

This looks like something that could perhaps be put into another APK? I fail to find any documentation regarding this and feel like it could quickly result in conflicts if just any APK could actually define those... btw. my clock is on the right side (in more than one way) in stock too... well via Substratum, but it's not impossible. Having it as a setting would be cool, but question is how close Fx wants to stay to that unmodified experience. That symbol keyboard looks like something that hasn't been touched for a couple of years. The design is a bit out of place, but I suppose

In The Neherlands one of the larger retailers has stopped advertising and increased prices. So, I think it's safe to say that if this continues any longer you won't even be able to get an Iphone 😅. Trust me, I feel your pain. My family members are also still awaiting their phones. A Priv with a cracked screen, an S6+ over 4 years old and an... my point being, shit happens. My family has seen and held/felt a Pro1 (mine) and are still anxiously awaiting theirs 😉. So, think before you act 🙄.

I also very often inadvertently trigger the fingerprint reader with my palm. The ideal positioning for me would be above the power button where the volume keys are now. Easy to press with my thumb when holding in my right hand, and easy to press with my index finger on my left hand. The volume keys could then move to the left side of the phone, similarly accessible easily in both hands. When in landscape mode, the fingerprint reader could easily be reached by my left index finger, and the volume adjusted with my left thumb. I personally also find that having the volume opposite from the power

It's a very simple bug, they initialize a register in the keyboard chip wrongly. Fix exists but I suspect we will get OTA only when the corona thing calms down a bit. If there is a desperate need for multi-key support and having all the keys work on boot here are fastboot images to fix it (but WARNING this requires erasing userdata - aka a factory reset - and then another one when you want to go back to normal images that can actually receive OTA update, and it comes with bonus bug of fully locking out the phone when the touchscreen bug happens) https://matland.be/pro1/kernel.zip Alternat

One of my advantages, I suspect, is that, other than work assigned Blackberries, this is the first physical keyboard phone I have ever used, so I am just training my motor skills to this keyboard. All other keyboard phones tempted me, but they were too small, making them very difficult to use when I tried them in stores. I only reluctantly used my BBs with their hopelessly cramped keyboards, and usually only to say "k, email later." I most often just phoned people if I wanted to reply. So I really find this phone the first phone really made for my hands. With the Pro 1 I will snap out the

I too am bummed about the keyboard, and for a device of which the main attraction is the keyboard, it's a serious bummer. I have stated before that I have been using physical landscape keyboard phones ever since they became available (pre-smart phones, early to mid 2000s I believe) and have never had trouble aclimating to a single one like I have with the Pro1. Serious disappointment! I too find myself using the virtual keyboard more than I ever have with any other phone (again, I always have used physical landscape keyboard phones). This really shouldn't be the case, as this phone

Well it is quite safe to say that NOTHING is going to happen before the factory starts operating, and (the same for any supplier of anything not already stocked). And it is anyone's guess when the virus-situation is going to allow for that. And with much much bigger players pushing, We should be lucky if the first thing they start on is the Pro1s or any need component.

Maybe they sent yours to mosen 🙂

I bricked my phone, so in fact I followed the directions Chen Posted to reflash both the A and B partitions via ADB, and then retook all OTAs. However, I suspect factory reset might be enough, if anything here is working and it isn't just some weird alignment of the planets for David and myself. Lol.

I can not see the logic in that. It is clearly much more a nice-to-have than need-to-have feature, so obviously it would not be at the top of the stack of issues for fixing. That some reports random reboots is one of the much more important things to handle. But that does not mean that we in anyway can conclude whether or not it will be handled once the more grave issues have been handled. I like @SchattengestaIt find it likely that it will be handled, but of course there are no guarantees here, unless officially stated.

So I "agree" with both of these just want to point out its not the curved screen, its the touch recognition parameters my Priv never had these issues. I am constantly activating the camera via the physical button, really not even sure how, bugs the hell out of me. The screen activating while on a call is also never an issue I have had with any other phone but happens every call with the Pro1. Also likely a software issue where they aren't interpreting data from the sensor correctly.

Below 45% the dragon starts to appear even brighter than at 55% as the black becomes green-grey instead. I would definitely expect this to be remedied by an update or screen replacement but will let them deal with the factory production and shipment first while it gets figured out.

I spent some time looking at the dragon picture at various light levels. I am not seeing the harsh transition from black to near black in the lower right that is shown in those camera photos. To me, it looks like jpg compression artifacts in the photos posted, but it is unclear if those were introduced in the photo process or are like that on the original screen/app being used to display the photo. I only see harsh transitions at under 40% brightness in that picture, and only in the far right side of the lower right of the photo, in 3 areas. I have to look hard to see it. It isn't as pron

It would be great if it allowed to disable on lockscreen ONLY when display is off. So pressing power would activate the scanner. As Open source, I hope someone can make this mod!