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?

first of all, thanks for all your effort you put in this, great work @tdm! I'm not sure if this is still an standard option in the vanilla LOS, but it was available some time ago that you can lock your device by double tapping the notification bar, is this still a thing or is there any other way to lock it without the power button? I'm using mine as a daily driver, that's why I'm still waiting a bit before changing, otherwise I would just have tested this myself.

Before I looked at your picture, I was imagining you meant something more like this.

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 beginning to get a little better with mine, with regards to accidental touches. Not happening as much, but I'd still like a stock setting where you can lock out different edges of the screen.

Possible from Tasker, but I am guessing you mean with a system setting?

The keyboard character map file determines the type, FULL or ALPHA. It is loaded at boot and cannot be changed after. Perhaps I could implement an option in settings to switch. The documentation is here. I am currently placing the default kcm file in "/vendor/usr/keychars/DEVICE_NAME.kcm". The setting could place a modified keymap in, say, "/data/system/devices/keychars/Vendor_XXXX_Product_XXXX.kcm".

Missing keypresses might be due to a bug, where you can't press the next key before the last key is released. That should be fixed in one of the new firmware updates. For the / and ? problem, clear your keyboard language selection so that it reads "Default". Then the button next to the left control key will get you / and ? The other 2 are known issues. Hopefully they will be fixed in a newer firmware.

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.

Is this a layout given by LineageOS, or something within your control? If within your control, it would be awesome to extend it to mimic the four top rows of physical keys, and then let the corresponding key pressed when displayed give the symbol. e.g. Press and release of Sym displays the map, a press on the 1-key, then gives the top left symbol displayed. etc. (preferable with the printed letters faintly printed on the image to ease orientation) Make it even more awesome: allow Sym used as a modifier to give the same, e.g. Sym+1 .... And this could be extended to more com

I cracked the screen 2 weeks after I got it - and got it replaced a bit over a month later. It slipped because I was careless (had nothing to do with opening the keyboard).

Thanks. Around 20 MB/s sequential read/write is consistent with what I and others have gotten. Something is making it perform well under the UHS-1 speeds.

Let's put it this way. I *thought* that mine was behaving differently than other people's phones. That's because I was not seeing the problem when I was opening and closing my keyboard. But what I was missing is that my screen wasn't shutting off in the middle of testing. When my screen shuts off (whether by itself or with me tapping the power button), then the problem happens. I'm postulating that other people have their screen go off when they are in closed keyboard mode at some point. They then open their phones and wake up the screen and go to type something and it doesn't work a

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.

I would not hold my breath on this. Just off the top of my head I can name several show stoppers that any "decent" "enterprise" (*) IT policy would require: - Secure Boot is disabled. - Security patch level is out of date. - WiFi and BT MAC addresses are bogus. (*) definitions of decent and enterprise may vary, and frequently do.

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

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.

Time to get out the ouija board app!

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.

This is what a black to white gradient looks like on mine with the brightness set as low as possible, though the cut-off already starts being clearly visible about 50% or something. I have the latest update installed, unless I really managed to flash the wrong boot image when rooting. If so, I guess it'll be taken care of with the next OTA instead. This unit is from the latest batch, #344.

I made that one thinking on many romance languages. ES-ES, ES-* (all the latin-America), FR-FR, IT-IT, PT-PT, PT-BR, PT-* (All portuguese variants). I also throught about having it compatible (dunno how viable) with all romance languages in South Europe. Maybe for ES-* I'd swap the "ñ" with "ç" on the dedicated key on the right side. That URL is not working. I think this BB breaks those URLs

@Slion, can I get you also interested in this layout? https://github.com/anssih/finqwerty/issues/12 Or maybe you can work directly with the owner of FinQWERTY and make a better product overall. This one looks good!

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.

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!

Yes there is! Problem solved (for me at least). I had the very same problem (continuous "too many attempts" warnings even caused hiccups for my banking app...) and I stumbled onto an excellent fix. Go to the Play Store and install the app Admin Control by Dave Hewitt. Very simple small app, totally free, no ads, doesn't use internet, open-source (Github). This app has just one on-off switch and what it does is very simple: it disables the fingerprint sensor JUST for the lock screen. Meaning that on a locked phone the fingerprint sensor is inactive, but once the phone is unlocked, the