Jump to content

claude0001

Members
  • Content Count

    206
  • Joined

  • Last visited

  • Days Won

    16

claude0001 last won the day on August 2

claude0001 had the most liked content!

Community Reputation

334 Excellent

Recent Profile Visitors

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

  1. Thanks for the suggestion, but no way. I did not install a Google-free LineageOS to then use a Google App that can theoretically record and evaluate everything I type on my phone ... I have given up on that problem for now as it is practically restricted to that one word in K9-Mail, and occurs only with the physical keyboard. Hopefully, K9 will switch to a more modern text input API at some point which should get me rid of this.
  2. Have uploaded my latest build (20210718), including the 5th July 2021 AOSP security patches, after flashing it to my own Pro1 without issues.
  3. The instructions in the LineageOS wiki are really good. Just follow them and make sure not to miss any steps: https://wiki.lineageos.org/devices/pro1/build It is really not that hard. I have been self-building LOS 16.0 without issues for some time now, although I understand next to nothing about the internals of the build system ... Even if you have some Linux running on your main PC already, I strongly suggest to set up a dedicated VM with the latest Ubuntu LTS to stay as close as possible to the recommended environment. Ubuntu Server is sufficient btw. (and much easier on y
  4. That's a known phenomenon. As far I know, there are several ways to fix it, depending on what operating system you run, and whether you are ready to do a full data wipe or not. It's all in this thread: I suggest to contact Dragonbox ( @EvilDragon ), they'll probably know best what to do ... Edit: Dragonbox.de even have note about this on their product page: https://www.dragonbox.de/en/spare-parts-tools/lcds/fx-tec-pro1-replacement-lcd
  5. I'm 100% with you. I remember I uttered that same criticism months ago (though I cannot find the thread anymore): The size of the keyboard feels wrong for me. It is too big for thumb-typing while holding the phone in hand, and too small for 10-finger-typing when putting it on a desk. I, too, could thumb-type much faster on my old N900. For sending the quick text message, I actually rarely use the hardware keyboard. That being said, I also never looked back. The big high-res screen is nice (though not very well suited to watching movies due to the green-tint problem), and there are so
  6. Yes, for me @agent008's entire picture seems blurry. To answer your question: No, I never had this "tilted" focus others have observed and which indeed looks like a misaligned lens to me. My problem seems more like an misbehaviour of the double-action button, where upon pushing the button all the way down, the system changes the focal length once more, instead of just taking the picture. Does not happen all the time, so maybe I'm just pressing the button "wrongly". But I never had that issue with any other camera, so it's annoying enough for me to avoid that button now.
  7. I got many shots like yours when trying to use the double-action (hardware) shutter button: I observed that the camera focuses fine at first (as visible in the viewer) but at the point of pushing the shutter button through, the lens defocussed again. For me, this late defocussing never happens when using the touchscreen ("soft-button") to take pictures (I'm using OpenCamera). So I have pretty much given up on the hardware shutter button for now. Quite sad, as the double-action shutter button was one of the things I liked most about my N900 ...
  8. Unwilling to let go my LineageOS 16.0 setup, I started to compile my own builds some time ago. For the case anyone else still has interest in LineageOS 16.0, I've made them available here: http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 As of writing this, the latest image contains the 2021-06-05 AOSP security fixes. I will probably continue to make new builds every month, as long as the sources keep getting patched by the good people at lineageos.org. Although based on the official sources, these builds are "unofficial" in that they are signed with the so-ca
  9. The 2021-06-05 patches have been fully merged into Lineage branches 16.0, 17.1 and 18.1 only today. That was too late for the build bot. It should come next week, I guess.
  10. I get best results when using a Raspberry Pi3 for flashing the Pro1. I had lots of trouble using my normal PCs as well, even though some of them are old pure-USB-2.0 systems. The RPi has a 100% success record up to now. The cable then does not seem to matter much: I have successfully used, both, the official one and some random spare I had lying around. If you have a Raspberry at hand anyway (), just give it a try. The needed Android tools are just an "apt install adb fastboot" away. Edit: Note that the fact that my RPi is version 3 may be important. The Pi3 is the latest versi
  11. In principle, yes. Note, however, that some hardware components are likely to never be supported by open-source drivers within the realistic lifetime of the Pro1. For orientation: The Nokia N900, a relatively popular hacker's phone from 2009 (!), still has only 80-90% of its hardware supported by the mainline Kernel (personal estimate). And that's despite the fact that it originally shipped with an OS that was quite "open" compared to today's Android ...
  12. Well, not quite (as we discussed above). With Lineage you get the Android framework fixes from the AOSP security bulletins, but no patches to the Linux kernel or the binary driver blobs, as these are supposed to be implemented and distributed by the SoC manufacturer. That's what LineageOS calls the "vendor security patch level". As you confirmed yourself, that one is stuck at 04/2020 in LineageOS, too. It must be, as the binary bits are taken directly from Stock.
  13. OK, thanks. I was unsure because, according to this thread, Stock received further updates at least until August last year ... So I get none of these actually included any fixes to the vendor bits. We'll probably have to accept that, I guess ... 😞 Sorry if I am asking obvious things. I was never on Stock, either, so I'm a little disconnected from its development.
  14. Could anyone running the latest Stock look up what its "vendor security patch level" is? I am wondering why my self-built LineageOS (with Android patches from May 2021) indicates a vendor security patch level of "5 April 2020", although I extracted the vendor blobs from a much more recent (Lineage) release. Of course, if even Stock was stuck at that date, this would explain things ... thanks in advance!
×
×
  • Create New...

Important Information

Terms