Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

78 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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?
  3. 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.
  4. 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 barely has a signal (completely greyed out) even though I'm right next to my router. Starting youtube in the default browser and putting a video in fullscreen mode causes the screen to flicker. The status bars (top and right) are being displayed and disappear immediately again. Video playback itself isn't affected. It is quite irritating though. Playback in embedded mode/normal mode is fine. My banking app crashes when trying to start without giving any information as to why. From my previous phone I do know that an unlocked bootloader isn't an issue. On a more upbeat note: The camera is working perfectly and the physical button is working as expected :). Disclaimer: As the SIM card is a bit difficult to get out of my current phone, I didn't test anything regarding that yet. Question: Is there a way to get rid of the google asisstent stuff? Meaning the voice recog thingi? I had hoped that it wouldn't be included in the GApps package.
  5. 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 match the input appearing on the screen. (I believe the original stock Android had the same issue and you have to go into settings and change the layout.) If I then click on the small keyboard icon in the lower right corner a popup appears and I can enable the virtual keyboard regardless of the state of the physical keyboard, which works. It seems like the open/close action is not being recognized at this time. Is that what is meant with "virtual keyboard should default to enabled. "?
  6. 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.
  7. 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 is a base rule of the kernel: Never break userspace. So the only issue is all those changes Qualcomm made. Is it possible for a non-Android developer to get a hand of the Qualcomm kernel source? That thing still falls under the GPLv3, right?
  8. 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.
  9. 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: From 2016: What are the diffs of FBE and FDE and why do both suck on Android, just in different ways when compared to iOS/iPhone encryption? https://blog.cryptographyengineering.com/2016/11/24/android-n-encryption/ From 2018: Ways to break into an encrypted device depending on vendor and encryption method. https://blog.elcomsoft.com/2018/05/demystifying-android-physical-acquisition/ In that article there is a linked PDF that describes FDE and FBE and how susceptible FBE is to some FDE attack vectors. Also towards the end there are some recommendations regarding security of smartphones (re-locking the bootloader once you are done with changing your system, using a restrictive bootloader to make it harder on attacker to get into the system etc.). If someone knows of a more recent study on this please post it. https://www.delaat.net/rp/2016-2017/p45/report.pdf From reading through all of this, I'm gathering that FBE is more secure in terms of preventing someone from copying data from the device, if it is properly implemented. In the PDF it is mentioned that ext4 (a linux filesystem) is used in case of FBE and that ext4's own encryption method is used but that there are a bunch of TODOs in the source code. Since the study was done several kernel versions ago, I would imagine that most if not all of those are done by now. What kernel version does LineageOS use?
  10. 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" even though they mostly weren't 'good' in realistic comparison. As for the Google apps stuff: I completely understand why people don't want it (I don't want it either), however I have certain requirements (banking app, chatting apps...) that can only be fulfilled via the Google store (at least to my knowledge). For me the interesting part about LineageOS is a) a more fine grained control about security b) a device that is easier to 'root' and c) being less reliant on the vendor of the phone for updates
  11. 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.
  12. @Polaris I edited my post before you posted, because I realized I didn't handle that well. Sorry, about that.
  13. 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 directory E:Failed to open driver control: No such file or directory Seems like they use a different name for the model compared to the pre-production thing you have.
  14. @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.
  15. 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.
  • Create New...

Important Information