Leaderboard

Oh, bloody hell. Forget it. Lol. I forgot to tell apply update I was sideloading. 🙄 😄

Indeed. Before you lock, make absolutely sure that you have "allow bootloader unlock" enabled in the security settings. If you lock with that disabled and anything goes wrong, you need EDL to fix it. And trust me, EDL is much more finicky about USB ports than fastboot, as many here can testify.

So just received my phone today. (I purchased in the later batches) I started it up, inserted the SIM from my Galaxy S9+, and actually followed the default set up. After the basic Google start-up, I waited for the 'sync-ed' apps to download, and updated the phone to the newest version of Android. (Did not have 4G at this time) In the settings, changed the Preferred Signal Type to 'LTE Only', restarted (acquired 4G at this point after restart) I was not getting any phone calling service/texting without being connected to WIFI, so I *#*#4636#*#*, and toggled 'VOLTE Provisioned', 'V

To do a full nandroid backup. I like to change some settings, icons, play with some apps and a backup will help me to do that, to be on the safety side. TWRP + Tasker are the main reasons why I use Android. Backup and modify/automate 🙂

Just received my phone this am. QWERTY SN 1996

Careful with that. Some in here had locked it and could not unlock without help. Only re-lock if you are sure that it is the official stuff that is running, and it might not be after the failed attempts.

https://twrpbuilder.github.io/downloads/twrp/#tab=inQueue No.30 ...good to know 🙂

I got an update from fedex. Now its delivery in tuesday. Its in cologne.

It is a known issue on stock ROM. I believe that random reboots on low signal network is also relared to this.

Disconnect and reconnect the USB, reboot the phone, reboot the PC, say some cuss words... This just looks like adb being tempramental.

For the record, I don't seem to have this problem on LOS either:

See for yourself: https://photos.app.goo.gl/bXsZoydGZnEyzUNK8 I did tap the screen to focus, as I was not patient enough to wait for auto-focus. It is unlikely the sensor is a different brand or model, as I removed support for most of the unused sensors. But perhaps there could be some differences, I guess. Kernel logs from boot may help identify the exact sensor.

QWERTY 2043 (just arrived today)

Great job! I installed the latest version successfully. First row shift is acting like a FN (except that shift + ß gives ẞ but that is probably like it should).

My only system is a i7-3667U in a ThinkPad with 8GB ram... I could as well build the ROM on the Pro¹ itself 😉

I did not find the App in F-Droid or as APK anywhere, but apparently when you build your own ROM it can be pulled in easily: Anyway, I won't build any ROM for myself, as at the moment my most powerful device is... lets see... possibly my Pro¹ 😉 ...sad but true.

Can confirm. I am in Cologne as well and it is scheduled to arrive before 12.

@DieBruine Thank you! Your suggestion seems to have worked on my Asus RT-AC86U router I was able to use WiFi MAC filtering to force 2.4GHZ and so far so good, no reboot. I do hope this gets fixed in the standard OS though, I should be able to use the phone on 5GHZ these days!

If it's a DHCP issue, you could try fixed IP. Under WIFI settings on the phone apply the IP, subnet mask, gateway and DNS you used for the reservation. If you don't know what that is and/or cannot find it. Just use the IP, subnet mask and use the router's IP address as default gateway. For DNS use 1.1.1.1. That's an easy way to rule out DHCP issues. You can change these settings when you modify a known/saved WiFi network on your phone. BTW, your basic logging on the router should at least show password incorrect/rejected and a DHCP request from your phone...

Doesn't Lineage have this issue fixed? Might want to give that a try.

If possible switch to 5GHz only. I had a similar issue on my provider-provided-router, but only on 2.4GHz. I have tested it on my Ubiquity routers, no problems there. But that whatever-brand-it-is-router, that one made my phone reboot. I alway make a distinction in SSID between 2.4GHz and 5GHz. Also, my 2.4GHz network is fixed on channel 1 and 20MHz. No reboots since (Ubiquity).

Correct, there are currently no restrictions on rejecting devices

I can try to investigate. Send me a logcat in PM. Also, if you have root access, a kernel dmesg would be good.

The tapping doesn't work on my device in this situation. Although it tries to focus to tapped point, it doesn't really get there at all or/and focuses back to close again, and continues sawing the focus back and forth for few seconds. But looks like it really can't focus to infinity, and that's why it never gets it to focus outdoors.

Yup, same for me. 18:17 moving again. Well I hadn't noticed the 5 hours delay on Saturday. So it doesn't seem all that strange the delivery will be delayed by at least a day. It was destined to arrive at the hub at 23:00, not 04:35. You can't expect a delivery as promised when it's that late. I'll be expecting it tomorrow. It's a 5 hour drive to my local hub. So fingers crossed for delivery tomorrow.

Its in transit now for me again. Maybe it will arrive tomorrow .. or wednesday. Timeframe still undecided.

Being able to do a Nandroid Backup (which is not so much a new reason as the result of having decrypt).

It was added as a character to official German rather recently (June 2017), for the case of writing an existing text in all caps (as an example the Corbusier WP theme I use for my blog has this odd behaviour for some headers). I guess It is not that likely to actually type it though. But that is now possible.

Try reinstalling the ADB device driver I had issues initially due to this.

I am from Finland. QWERTZ suits quite well for us since we have Ä and Ö letters also and instead of Ü we are using Å. Then Y and Z needs to be swapped. So, only minor remapping is needed from QWERTZ to Scandic.

Before you flash issue :"fastboot -aa" or "fastboot -ab". This should set your active slot to either a or b. I had a similar issue with my friends FairPhone 3 couple of weeks ago. You can issue "fastboot getvar all" to check the current active slot. The output somewhere in the beginning should state "bootloader current-slot = a/b". When I experienced similar issues on the FP3, the current active slot was "-". After I set it manually I could flash the phone again. And maybe, just maybe, LOS will flash now. Check if you have an active slot. Because that (not having an active slot) would exp

Yes that's how it was done in FinQwerty I'm not sure if it makes sense though, I can't think of any instance of upper case ß in german.

Installed smoothly with and without root. 🙂

Seems like my package is stuck at ROISSY CHARLES DE GAULLE CEDEX FR. 😞 And the tracking told me it arrives today! Don't want to wait anymore 😋

Known issues from above should be fixed now. hwkbd-v0.4.1-fxTecPro1-qwertz-release.apk

@FlyingAntero Here is a first draft for QWERTZ layout. The ALT layer is still missing, the Fx layer may need to be adapted for QWERTZ as it should currently be the same as on QWERTY. hwkbd-v0.4.0-fxTecPro1-qwertz-release.apk Known issues: First row shift not acting as fn. Fn characters on standard letter keys missing or wrong.

Hmm, when I look at https://download.lineage.microg.org/pro1/lineage-16.0-20200718-microG-pro1.zip there's no match for 't5' in the accompanying plain text files. Might be in payload.bin? How do I make the change (to the assert) you spoke of? EDIT: Oh, damn. I should change QX1000 info t5, not the other way round, got it.

https://eskerahn.dk/?p=3651

I have exactly the same issue on LOS. and it doesn't depend on camera app used. Also I have wiped my system several times, which doesn't help. Seems like not everyone has this issue on LOS though, because it isn't listed to 'official' bugs in Github..

That is very optimistic.

Well, in my case, I HAVE autofocus. But it only works for near objects. Far objects I cannot focus automatically nor manually. I tried 'Open Camera' app and MANY OTHERS and far objects (infinity focus) do not get sharp. If I change from CameraApi to CameraAPI2 I can focus manually, and the counter goes up to 1000 meter, but actually at like 20 centimeter it is done.. everything else is in the fog. With stock ROM: no such problem.

Hi, I use Camera FV-5 app on LineageOS (the last) and it seems to be the same. I found the original photo app was not very good, so I have installed Camera FV-5, and I confirm : no autofocus. Focus come when you push to take a picture. Not very practical yet. As I don't take much picture yet, I never think it could be a Lineage bug. But why not ? Also as we are here, I found stock picture app far better, is it possible implement stock picure-app in Lineage or is this idea stupid ?

Somewhat of a long shot but does this per chance happen when playing voice messages on whatsapp/telegram/simiar? That happened to me and I thought the device had gone mad, but after some investigation i found out when playing voice message the proximity sensor is active which turns off the screen when something comes near. The purpose being to turn off the screen if you put the phone to your ear, and normally it's not noticed because people hold their phone in portrait mode. I found that in landscape mode my thumb easily gets in front.

The angels descended before me. My sincere thanks to Fxtec staff.

I just now received from FedEx.. finally It is worth waiting. Products quality is very good. I am waiting for headphones. Thanks @Erik and Team Fx..👍

As a Scandinavian I want to make one point clear. We do not have "/" and "?" marks as independent buttons on standart ISO QWERTY keyboard. Typically they are used as below: "Shift" + "7" = "/" "Shift" + "+" = "?" (where "+" is located next to the "0") Pro1 QWERTZ is arranged like this on stock when you select German except that there is a catch. Now those keys are working like this: "Shift" + "7" = "7" so you have to type "Yellow arrow" + "7" = "/" However "Shift" + "ß" = "?" and "Yellow arrow" + "ß" = "ß" (where "ß" is located next to the "0") Developer of the

SailfishOS can be seen as a Linux distribution (Android uses Linux kernel too). Only thing where it relies on Android are Android drivers through libhybris. Certain Android Apps can be run in SailfishOS using an emulator and it is possible and officially supported only on certain Sony Xperia models - so no go on Pro1. The overall state of SailfishOS on Pro1 is a community port in alpha stage. Many thanks to those making it possible (the same goes to LineageOS porters)! Could SailfishOS on Pro1 be used as a daily phone? Well - it depends. Give it a try but don't hope you can fin

Maemo-Leste! with a functional Rockbox port please, and add osso-notes too while we're at it!

I summarized it on reddit, but the main things are keyboard working a lot more like it should and no more audio crackle.