SteffenWi

Primary order factor is date of payment, not date of placing the order. *edit* erh, nvm. You posted somewhere else you paid in early august. Weird that you didn't get a phone yet. Sorry.

yeah just checked mine, too. No pivoting here. I have the 'rattling' noise others report when you tap a bit harder on the screen but that is from the keyboard and not disturbing.

I like that that list doesn't contain the info about the fingerprint sensor, but thanks. The missing Microsoft Exchange thing would be problematic, too.

Soo, since the Sailfish version will take some time, I took a look at SFOS and stumbled over this article: https://sailfishmods.de/2019/04/fxtec-pro1-mit-sailfish-os/ In there it says "Der Fingerprint wird allerdings nicht mit der CV funktionieren, da dieses Feature nur für Sailfish X Geräte freigegeben wird." which translates to "The fingerprint functionality will not be available in the community version, as this feature is exclusive to the Sailfish X devices". Is that true? Why does SFOS have these weird limitations on the community version? It can't run Android programs, it can't o

I had wondered why I didn't see anything from you, but figured you were busy with reallife...guess I wasn't too far off. Hope you and your family are feeling better and that nobody starts a 'second wave'! Nice to hear that you now have a proper FxTec device 🙂 .

Germany, D2 network (Vodafone) LTE is working fine with stock Android.

I'm guessing that it has something to do with the test build environment...if this persists when the official build comes around I'll dive deeper into it.

Done. I'm assuming the "This build was signed by a public key" message will go away when we have a non-test LineageOS build?

Fun fact: It isn't forgetting the data for me? When I initially set up the device after flashing it, I registered my thumb and three shutdowns and one reboot later it is still being recognized.

Nope, it does not work. So what happens - and that is the same as with stock android - you press "d" on the keyboard and "s" appears. The numeric row is fine. I didn't try any special characters like äöü. For stock Android the solution was to go to System, then "Language and Settings", then "Physical keyboard", then click "Fxtec Pro1 (Default)" and in the pop-up select "German" (Or Deutsch if your system is set to German). For stock android that allowed the keyboard to work. On Lineage that doesn't do anything as far as I can tell. Another issue: The WIFi symbol looks like it only

Flash successful. No issues this time. Just remember kids: use a USB 3 cable connected to a USB 3 slot on your computer. It might just be my machine being weird though. But if the process gets stuck, just give it a try. I'm going to update this post as stuff happens or bugs appear. First bug: I'm using German keyboard layout, during the initialization Android asks you if you want to connect to a WIFI network. When trying to enter a password, the virtual keyboard does not pop up. When I open the physical keyboard, the screen does not change orientation and the keys I press do not ma

correct, but that would still mean that there is an address. That is different from nothing at all being returned. Maybe that is what tdm meant though. ANd at least in my case the MAC address that was visible in stock Androids settings looked made up, but wasn't something like 11:11:11:11:11:11. Unless stock Android generated a MAC.

Wait what? How does that even work? From my limited understanding a network device has to provide a MAC address - even if it isn't a 'real' one. Is that again one of those 'ARM is a broken platform' things? So, if Qualcomm decides to put a keylogger somewhere in their version of the kernel it would take ages before anyone found that due to all their changes? Wow...that seems really bad. As for closed-source userspace binaries: That shouldn't prevent a kernel upgrade as the ABI towards the userspace is rarely changed and even if, it never breaks any prior stuff. That

I'm from EU, IGG backer. I was part of the first batch and my phone has - as requested - a QWERTZ layout. Maybe it calms you a bit to know that I have not yet used my phone. I'm waiting for LineageOS to be ready or basically any non-stock Android system (that allows Android apps to be installed) to become ready enough to use or at least test.

Why not just use the addresses provided by the hardware? Even if they aren't part of an assigned block, they should still be unique amongst all the Pro1 devices? @Polaris I would have totally understood (and apologized) if you would have been offended by the way I wrote the first version of that post - that is my point. Yes some people have a thicker skin, others don't. If one aims to word their thoughts so that non-thick-skinned-people are comfortable reading it, everyone benefits. That is my point. As for FBS vs. FDE here are some interesting reads on the topic:

Yes and that part, the blowing off steam part, is what I don't deem acceptable on a forum, especially when it is directed at specific people just because they have a different view on things. As for thin skinned and people should be more relaxed: While I generally agree with that, I do strongly believe that people should be more respectful towards eachother and more mindful about the things they say. We as humans strive to constantly improve everything and part of that is improving ourselves and the societies we live in, as such people have always yearned to get back to the "good ol' days" eve

Just for reference, what I wrote is not acceptable, I wouldn't find it acceptable if someone talked to me that way. The first sentence alone should have been written in a lot more respectful manner and the rest is just full of hyperbolic statements and black/white thinking. That could be okay in a longer discussion to make a point, however that isn't what I had in mind when I wrote that. I was just irritated.

@Polaris I edited my post before you posted, because I realized I didn't handle that well. Sorry, about that.

okay, I rebooted disconnected my USB Hub and any other USB devices except my keyboard. Then connected the Pro1 first with a USB 2 cable to a USB 2 slot, which didn't work. Then tried a USB 3 cable to a USB 3 slot and that worked. Finally. Anyway, when trying to sideload the zip file I got an error. Full output. Opening update package... Installing update... E: Package is for product FxTecPro1 but expected QX1000 Restarting adbd... E:Failed to open driver control: No such file or directory Installation aborted. Stopping adbd... E:Failed to open driver control: No such file or d

@tdm as for flashing, I'm stuck at fastboot flash boot_a ~/Downloads/lineage-16.0-pro1-test1-boot.img it gets stuck there with Sending 'boot_a' (65536 KB) and just hangs there. I repeated two times by restarting the bootloader without success. I waited for ~10 minutes for it to do anything but no success. fastboot devices does output the Pro1. I made sure to be connected via USB2 and I tried differen USB cables.

Why would you even want to do that? I for one don't want that. I love the idea of having a 'safe space' on the device that allows me to start over, especially when flashing stuff where things can easily go wrong.

Uhm, so I really would feel uncomfortable with fiddling around with a copper wire on a device that cost >600€. Could we maybe not do that? Also I like the idea of A/B partitioning. And @Polaris And if you are aware on how Google is spying on you, maybe use SailfishOS? I want LineageOS because I can install GApps and use the Playstore while at the same time not having to worry about the vendor being responsible for security updates and similiar things and being able to use the pico version of Gapps, just because I don't need or want the majority of Google applications, not because

Just FYI because it took me > 2 minutest to find anything on this: The A/B issue with gapps is described here -> https://lineageos.org/Changelog-19/

Just to be transparent here, that info came from me / my device which is from the first batch.

Much obliged