Leaderboard

Thank you for noting your github name. 🙂 The aim is to get the keyboard working in the most obvious way possible. In other words, start by: 1. Select QWERTZ under settings -> system -> keyboard -> layout. 2. Select German (or similar) under settings -> system -> languages/input -> physical keyboard -> builtin keyboard. With that done, the keys should generate the symbols as marked, eg: 1. Pressing a key with no shift should generate the white marking. 2. Pressing a key with yellow-arrow should generate the yellow markin

This is what I figured, most...probably all...custom roms I've previously used have typically used closed source blobs for the camera (and plenty of other hw). Tried getting the dmesg but doesn't work on unrooted stock😅. So'll have a go tonight at flashing test12 and getting the dmesg. Also curious to see if the flashlight is going to work or not. But first...dinner (pancakes🥳)

Android Viruses? On Earth? Really? Yeah these are rampant....

I've been using my Priv for 2 different companies for BYOD already. One with BlackBerry Work, another with straight up Exchange EWS.

Absolutely. Reading the issue report, there is a modified keymap in comment by rehejuhan on March 10: 11:0033:8033 (, and ; ) 26:002c:0026 (y and |) <- update, not correct, 0026 is just l, not | 30:0011:0029 (w and ^) 38:0013:8029 (r and °) 39:0028:002b (ä and #) 42:0056:8056 (< and >) 47:0026:802b (l and ') Shall I use this?

Please, if possible, give some "love" to german qwertz layout 🙂 https://github.com/tdm/android_device_fxtec_pro1/issues/35

I am pleased to announce test builds for LineageOS 16.0. Please note this thread is for test builds. These builds are not necessarily stable or suitable for daily use. You can find the build(s) and detailed installation instructions here: Lineage on FxTec Pro1 Test Builds Please report any issues here and I will do my best to fix them. Thanks!

No problems here, but I also didn't use the Test 12 Boot image as it didn't seem like anything was being changed there. I just flashed the Test 12 ROM and Gapps and the Magisk.

I didnˋt flash the new boot.img when I updated from test11 to test12. I did flash the boot-qwertz-test1.imgtoday though. Had no issues with booting.

(Test12 works fine here, both. Only used slightly though)

@tdm I ran the commands you asked me to, (on test11, bc test12 would'nt boot but that's for the other thread). If I understood the output from dumpsys media.camera correctly it's basically only reporting on the front facing camera - finding only 1 camera device. Then had a look at the dmesg output. not quite sure what's going on here but simply doing a search for 'camera' gives a bunch of related fails and errors....and a naming collision for the flash (could this be why the flashlight doesn't work in LOS, but does work in stock?). Fun detail - flash doesn't work again in LOS. I h

Yes, Lineage only writes to a couple of partitions. Mainly boot, vendor, and system. You can return to stock by writing these three partitions from the stock firmware and doing a factory reset. EDL can be very picky about both hardware and timing. I'd stick with the fastboot method to restore. No, this is not the fault of Lineage. The camera stack is completely closed source blobs from stock except for the kernel driver, and I have not touched the kernel driver at all. You can start by getting a dmesg from a fresh boot ("adb

@Tsunero This is a known issue. It is resolved in Lineage. Its one line of code. Fxtec just needs to apply it to stock... Pretty sure I first reported it in November or December last year.....

acrux=rehejuhan 😄 If the aim is to get the keyboard act as printed on the keys (that is my strong preference) then it is a step towards it. However - these were the only keys I was able to adjust. About the others I wrote in that issue...

My camera also stopped working. I had problems from the get-go. After I installed multiple camera apps y problems got worse. I was unable to take pictures from within a Hangouts conversation. A couple of months later my camera stopped working at all. I started the camera app and it closed right away. In another camera app, don't remember which one, the camera would no t start and there was no video/picture. Just a blank/grey screen if I recall correctly. So, I uninstalled all camera apps, to no avail. After that I performed a hard reset. Which did not help the first time. The second t

Every. Single. One. We have just accepted it as one of the things we have to live with. High pitch buzzing sound. It's godawful.

Haha, I do that too. Unfortunately this triggers another bug: The proximity sensor is not sensitive enough (probably just a too low threshold value in some config file). During a call, the screen switches on "randomly", and my ear or cheek change the brightness to max or launch apps ...

Is this in-call volume thing really a general issue in all shipped devices? I ask because I saw only a few complaints so far. And because it would totally prohibit me from using the phone as a daily driver, perhaps make me carry a second device just for phone calls, requiring a monthly payment for a second SIM card if I want to keep my phone number...

This is even more of a reason to fix these huge annoyances that need so little work to be done. Software is, in my opinion, the number one reason not to buy a Pro1. This is in stark contrast to the hardware. F(x)tek made some really good choices there, with plenty of RAM and internal memory...

I wish I had an answer. I'm a bit frustrated too, and would even be willing to PAY to get a few of the most annoying software bugs fixed. But it IS a small company with few people. And even if they wished to do so I doubt the various licensing would allow them to put things out open source without breaking various certifications and/or licensing. But would be awesome if they let people help them - starting with some of the things the Lineage guys already have tracked down and fixed....

he will be delighted to sort and tidy up his apps to be able to keep up with the performance of the low end smartphones after delivery. He can revel in thinking how nice it would have been if he had got his smartphone back when it was still up-to-date.

One idea is for people to install an app like Wifi Analyzer (https://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer&hl=en_US) and report what it shows for the Pro1 vs other phones, at the same distance from the wireless access point. This is a screenshot from the Play Store, not from my Pro1, but it shows how the app shows the signal strength in dBm. The values will always be negative values. Values closer to 0 (zero) are stronger than values further away from 0. dBm values are logarithmic scale. Every 10 dBm lower in value (closer to zero) represents TEN TIMES th