Leaderboard

While we all wait for a production quality case, 3D printed case or some other optimal protection, I had to figure out a case solution that would work for me in order to being using the Pro1 as my primary device. For me this currently means a flip / book style case until something for covering the screen / top half of the body exists to mate with a bumper that fits the bottom half. I purchased a lot of cases intended for a Huawei P20 Pro since early testing indicated that was a good fit for the bottom / keyboard half. The Huawei P20 Pro is overall a thinner device, so more then half of

F(x)tec Team: I remain hopeful that the Pro1 will make it. It is very important to me that it does, especially with the demise of the Blackberry QWERTY cellphone keyboards that will occur this coming October 2020. I have learned that if you are a visionary, it is often a lonely place. It is a curse when you are the only one in the room that sees what you envision. In my case, my friends and co-workers laughed at me in 1989 when I created an electronic health record database software system (today known as Ezpro - https://ezprosystem.com/?page_id=74, https://ezprosystem.com/?page_id=6

Certainly it would be nice if someone official created an issue tracker. But until that happens, I think github issue tracker is much nicer than a spreadsheet. If someone could import the spreadsheet into the issue tracker that would be really nice. Heck, I might even make a new stock build with some of the issues fixed... 😄

Don't you dare to buy a spare phone when I/we are still waiting for our device to come!

I believe my Pro1 reboots sometimes. I reported long time (like 2 months) ago, that the Pro1 queries pin code sometimes. I was thinking that it only loses network. I even replaced my sim card, to make sure that the problems aren't because of worn out/loose sim card. Replacement didn't help though; the device randomly reboots sometimes. There can be days to weeks without a reboot, but I think it has rebooted even three times in one day once. Looks like those reboots are more likely to happen when I am on weaker network area. For example in my friend's home the 4G signal is weak, and this makes

Yeah that is probably a good idea, I'll update that. When I have something that prints ok I will post all files. The entire thing did not fit in my printer, but I printed the top part for testing and the camera hole is correct (camera position is actually visible in scan), but other holes need some adjustment.

So I'm talking to the Lineage folks and discovered that there is a setting to only accept fingerprint touches when the screen is not off. But it is a build-time setting. That is, you cannot toggle it. So I'm not sure if it would be appropriate because one of the cool things I like about fingerprint sensors is the ability to unlock the device without touching any other keys. Aside from that, I did discover a way to control the fingerprint behavior without doing anything too hacky. It just involves copying the AOSP fingerprint service to the pro1 device tree and modifying it. So

... but keep in mind, the slant arrows will be configurable at some point. It's on my to-do list.

All parts test printed, I will do some adjustments tomorrow and post the design 😃 Then I will try and print it in one piece during the weekend. Th msla I am using is just so slow, to print it in one piece I need to print it standing and it takes about 1h/cm.

That you only get half, has the benefit that you can investigate the detail of the fit to the curvature towards the side edges, and how the 'lip' is grabbing the edge. For the same reason you could consider cutting the part you already made in two, to see how good it fits the end-profile.

That's not too bad for a first try! 👏

I'm trying to push a release out today, but it may slip to tomorrow morning (Seattle time, naturally). The current fixes include fixed notification lights, fixed wifi signal strength, and a delay for failed fingerprint authentication. COVID-19 affects development because I am in Seattle which is currently in full freak-out mode over the virus. Fortunately it hasn't hampered me that much (yet).

Well, sort of. I have the BSP minus GMS (aka. gapps), but it is missing the device signing key. It's not hard to add a minimal GMS. So I could make an "almost" stock that is signed with a different key. Obviously my version would not get OTA updates, I would have to provide updates myself.

I think that option 2 would be better. Then user could use application like WaveUp (pocket mode) to wake up the screen and then just place finger to the sensor. If user has to wait 2 seconds to unlock phone via fingerprint sensor it might be too slow. Pressing power button and then placing finger to the reader would be faster I think. Edit: One idea would be to allow greater number of wrong fingerprint attemps and disable vibration on false read. Then false reads would not disturb the user but user would still be able to use the sensor when screen is off.

@auvo.salmi the idea for the Lineage keyboard driver is to emulate a full PC keyboard. @Gigadoc2 had a long and detailed reply on the github issue page, which is very informative and I encourage others to read here. The idea is that you select your physical keyboard as QWERTY or QWERTZ and then let the standard Android keyboard layout stuff do its thing. I do not have a QWERTZ device. And even if I did, I am a sheltered mono-lingual American so I wouldn't know how it's supposed to behave. The current QWERTZ layout was done with a picture of a QWERTZ pro1 device and a picture of

Still not a single spontaneous reboot since I got my Pro1. Using it with 2 SIMs and even weak signal does not bother it. I did not travel much with it though, I wonder what it will be like on the train for instance.

https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_FUNCTION

I swear it wasn't me who stole the credit card numbers of all 5 users of Fx Service 🤣

In my book it always raises suspicion when a very simple thing comes in a large package I immediately think: Hey is this compiled on an infected PC and used as a mule by some malware? And I'm especially cautious/suspicious when it is an app that (for good reasons) needs high privileges. So would be nice if you could dig into the "Why". 🙂

It looks like that the feature is not available on Pro1. But I can use Keyboard/Button Mapper to make those shortcuts if I want. Here are the pics that Chen showed on Twitter. https://twitter.com/chenliangchen/status/1141016306801676290

They are electrically identical, the only difference is the print, so your app will work identical on both. So you can test if you would like to (though the print will obviously not match when tested on a qwertY device) You can see the two stock prints described at the top here

Nice. I too would like to find a good one in leather. On the glue half part, I think it should be mentioned that For those using the back camera and/or LED a lot, it is recommendable to cut a hole, and perhaps glue the whole part (like you did). For those using it less, keeping it un-cut gives a better camera protection, at the price of needing to fold it all the way open to use the camera/LED. I like you idea of using a better inner bumper case, though to me that would be overkill The best one I've found (so far) isn't real leather either. I have bought

You should really not use any of those as long as we don't have an official build with a properly signed image and SELinux enabled.

Yes that was tricky too but once you get it right it works flawlesly. I tried to make a little help-file, to show at 100%... ADD Sigh, the forum shrinks the image ... Here the full file: https://eskerahn.dk/wp-content/uploads/2020/03/Pro1_Hall_Sensor_Top.png It is roughly 300 pixel from the top and 200 from the Right (refferenced in portrait) Note that the orientation of the magnet matters, so you might need to turn it around back to front

Video *finally* finished uploading. Seems the same to me as that S8 video. Is it worse with stock? With stock you'll have to assign a (gas) to a modifier key so that you can still turn while driving....

That video does the pause when rotating before each level that I was trying to describe. first time is right at the 1 minute mark..... then again around 725-735... I'llsee if I can make my own video... but my behavior seems same on Pro¹ edit: made a video, but it probably wont be online for a couple hours, my upload b/w is slow

Similar to pretty much any other Android phone, you do a build by pulling binaries off the device. I don't know if FxTec has provided any "official" kernel sources but this repo has the full OEM history, which is a step above your typical "here's a tarball" that most every other OEM does: https://github.com/tdm/android_kernel_idealte_msm8998/commits/oem-history

Isn't that the norm? I mean... All this secrecy.... [/sarcasm] The same way other companies lie? Are you sure the factory didn't just do all of them in one go although the deliveries were slower? Are you sure the WHOLE factory is dedicated for the PRO¹? Do you even know how these contracts work? F(x)tec pays by the phone, not time. If F(x)tec suffers from the virus, it is and will be because the founders need money to live their lives. Other than that, I believe there won't be more losses. This being a niche produ

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

ISSUES: Static/crackling noise in many games Camera Selfie Mode is inverted Camera app closes when settings are selected Pictures are not that great Security updates are not being released quickly enough Keyboard repeats keys Keyboard will randomly start repeating the last pressed key endlessly until interrupted Fingerprint reader on the right is getting annoying because of how it is always getting hit due to position locking out its use Screen is sensitive on the sides causing errant selections when holding Cellular data stops someti

When I initially got my Pro1 device, when you pressed the power button the FxTec logo would appear and slightly animate while android booted. This gave you a clear signal that something was happening. But now I've totally lost that somehow. When the device is off and you press the power button in for a few seconds: - no vibration - no led light - screen appears totally off / nothing displayed - I either have to wait until I open the keyboard or receive a notification for the screen to light up - after the initial power button press to start the boot, pressing the power button agai

Because @tdm's time is so limited, my personal take is it's best to just stick with Lineage related coding, despite his overflowing generosity. There are still important LOS issues like the notification LED to be worked out! ...just saying 😇

Any news if enough workers went back to the factory so they can restart production?

I believe it is not limited to a weak/failing signal, but combined with the bands relevant for the carrier. As more of us would see it if it was just the lost signal.

If you are on stock ... well ... that is a bit tricky. Do you have a root solution? If so, you simply run "mount -o remount,rw /vendor". If not, perhaps find the copy of TWRP that someone built and use it?

I would think that using a DFS channel is the likely cause. Note that the 1+5/5t has the same WiFi chip but somewhat different configuration for the DFS features. So you can play around with the WiFi configuration file to see if that helps. The configuration file is at /vendor/etc/wifi/WCNSS_qcom_cfg.ini. You can find the 1+5/5t configuration file used in Lineage here.

I'm pretty sure that's what it is as it seems that the idea with JetPack is that it gets updated a lot more often than the android platform. It's basically a way for Google to make sure apps are running high quality code even on devices that are not getting updates anymore. The downside is that the app developer seems to be responsible for doing the update himself and the package is a lot larger obviously. My two cents.

Just curious. Does this include some library, or how does this end up at 1918KB ? Browsing through the source even the small images in various resolutions could not get it anyway near (the source adds up to 1/10th).

We really should have somewhere offical... We already got this unofficial one: https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y/edit#gid=0

I've found the most annoying with this, which is a personal problem, is when I put the phone back in my pocket, my thumb hits the reader and it unlocks! And thats getting really annoying for me...I know lineageos has a feature for screen margins but I don't like to fiddle with my phone and my primary computer just in case I break either! Now to find an Amazon UK link for that case...

Yes they are identical, that is why @Anssi Hannula starts his qwertZ-files (e.g.this) by mapping. For image, see e.g. here ...That they are identical is actually an issue when setting up a new device (WiFi and account credentials), so we need to use the fake keyboard, as the real keyboard acts as the shifted until you get a chance to tell the system that it is the qwertZ. See also this

You could use Key Mapper.

How can you add new shortcuts?

Can't find those settings options.

This actually works! Just unplug charger (or plug it in) and the crackle stops. Very weird. I wonder if that works on stock too and nobody noticed til now.

Make sure your APN is set correctly. Mine wasn't and that was the cause of my woes.

I yesterday got the old SCH-U750 aka Zeal aka Alias 2. Very interesting. There are little movement of each key, but to my surprise it looks like the e-ink move with the key, so it is not just a transparent mat on top of a common e-ink display, But it looks like it is 42 individual matrix e-ink displays! And a warning to @abielins: The below is AFTER a thorough cleaning attempt. You do NOT want to know how it looked before. I believe it might have been an entire eco-system....

OK STEP BY STEP COMING UP... 1. Ensure keyboard mapping is set to no keyboard mapping 2. Click Advanced keyboard settings 3. Click Key repeating 4. Currently I have selected Slight key delay (recommended) 5. Open your keyboard 6. Go to your web browser and select the address bar, so that the flashing text entry cursor is flashing. 7. A little keyboard icon will appear at the top right of your screen in landscape. (unfortunately unscreenshotable.) 8. Click on the icon and Select Keyboard helper rather than Gboard. 9. You will notice now when you clo

test8 is up, you know the drill by now. * a2dp should be working. * Added touchscreen margin/deadzone. * Added settings UI for keyboard and touchscreen (Settings -> System -> Advanced). NOTE: if you use a custom keymap (looking at you @Craig) note the keymap file has moved. The reason is that /persist should only be used for things specific to the device that are invariant, eg. physical properties. So it is now read from "/data/system/keyboard/keymap". The file contents are the same, just "mv" the file over to the new location (creating the directory first,

Holy crap, I finally got a2dp working. That took waaaaaaay too long, but it's working now. Next build will have it, probably tomorrow since I am a bit busy today and there's some other stuff I want to fix/add also.