Jump to content

claude0001

Members
  • Content Count

    713
  • Joined

  • Last visited

  • Days Won

    96

Everything posted by claude0001

  1. Why not? No OTA update of LineageOS 16 (and I did apply all of them) ever broke that set-up. Why should it? After all, what I do there is not black magic. I make use of system interfaces that are, explicitly or implicitly, defined to behave in a certain way. As long as the Kernel, Android features, or root management did not change, I could be fairly certain no upstream security fix would break anything. I had simply expected LOS 16 to continue to receive security patches as long as upstream Android 9 does. That it didn't is disappointing and, yes, unprofessional. As you confirm
  2. I could not agree more. What you describe is the reason I am staying on LOS 16. I have plenty of hacks in place, where I cannot predict whether they would still work on LOS 18.1 (or 17.1, for what matters). I use several autostart scripts in /data/local/userinit.d/ for setting up stuff on boot automatically. Those scripts are officially unsupported already in LOS 16, but can be made to work using some third-party apps. Will those still work with LOS 18.1? Obviously, all of those autorun scripts require root access. Will those early-executed shell scripts work with (third-party) Mag
  3. So I get the setting improved things on your phone too? I now somehow regret not to have stressed the follwing from the beginning: Fully enabling AGPS (which I believe these settings do) enhances the functionality of GPS at the cost of privacy! There are valid arguments for having AGPS disabled by default in LineageOS and leaving it to the individual user to opt-in. See e.g. https://forum.xda-developers.com/t/keep-a-gps-supl-disabled-upon-rom-install.3612024/ However, I am not in charge. Go ahead with submitting a patch if you feel you must. 🙂
  4. I think some things regarding AGPS are left blank on purpose in LineageOS, as using such services potentially reveals your location to the server operators, which may be seen as a privacy issue. Even disregarding this, from what I read on the internet, the optimum settings depend on what region of the world you are in. So maybe there is no one-size-fits-all config anyway. I found this config on some German Android user-forum and did not really check if it is truly optimal. The new settings certainly helped (a lot) in my case, but you may find even better ones for Poland by experiment
  5. In LineageOS 16 I could vastly improve the locking speed by the following edits in /system/vendor/etc/gps.conf: [...] XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin [...] XTRA_VERSION_CHECK=1 [...] NTP_SERVER=europe.pool.ntp.org [...] INTERMEDIATE_POS=1 [..] SUPL_HOST=supl.vodafone.com SUPL_PORT=7275 [...] I am also in Europe (Germany) and at times could not get a fix at all (even after waiting for hours) with the default settings of LineageOS 16. Since I made that edit, GPS fixes a
  6. Yes, I believe you. Let's not go over this again. 🙂 GCam is not compatible with a Google-free LineageOS, and certainly even less with SailfishOS and UbuntuTouch. It is simply not an option for many people, plus, it does not support the shutter button which was supposed to be one of the outstanding features of the Pro1. The camera should make good pictures reliably, irrespective of the backend software used. But, sadly, it doesn't.
  7. Well, honestly, the crappiness ... ahem ... loveable peculiarities of the Pro1's camera got me back to carrying my DSLR along more often, too ... 🤔
  8. I agree that the Pro1 is bulky compared to other modern phones. But to be fair one must also say that the big size helps in all kinds of business use-cases (which are a main selling point of the phone): When coding, emailing or word processing, the huge screen allows to display a lot of content at acceptable font sizes, which certainly increases productivity. Also, as @lawliett already mentioned, running desktop Linux apps in a chroot is much more pleasant with a big display. As much as I loved my N900, I certainly do not miss its tiny screen. 🙂
  9. I did not think that was the problem here. If LineageOS 16 and 17.1 still had the Pro1 as build target in their config, the build system would continue to spit out new builds every week. In that process, upstream patches like AOSP security fixes (which are not device-specific) would be included automatically and not require any manual intervention by a device maintainer. At least this is how I understood things work. Someone with more knowledge about the LineageOS build process may correct me. I thought the problem here was simply to save resources on the build farm by allowing
  10. Let me try to rephrase that in a more optimistic way: They are very enthusiastic about porting the latest-and-greatest release to the Pro1. 🙂 The real problem is that, as soon as a new release (here 18.1) is declared "official", the previous one (17.1) stops receiving upstream patches. De-facto, releases are dropped from support at the very moment they have matured ... Effectively, users have only this choice: Either stay on an older, stable, and nicely de-bugged LOS port that does however no longer receive upstream AOSP fixes. Or change horses every few months b
  11. If you just want to run a few Linux programs, something like Termux and AnLinux is definitely the easiest way to start. I have never used those Apps, though, so I cannot help with specific questions about them. For advanced stuff, like the above, a "hand-made" chroot (with root access to Android/Lineage) will probably always be superior to (non-root) in-App solutions. Setting up your own Linux chroot on Android is actually not that hard provided you have some experience with Linux. The real problem is that the required information is scattered all over the internet. Also, some things
  12. As I wrote above, 17.1 no longer has the Pro1 as build target, so there will be no more (official) updates for it. See https://www.lineageoslog.com/17.1/pro1 ... and that is exactly why the older, stable versions should keep building, at least on monthly basis so they keep receiving the upstream security fixes in AOSP. Every upgrade that changes APIs or other major parts of an OS is potentially disruptive for the already-installed base. That is why professional distributions keep their "stable" branches alive as long as upstream fixes can be picked-up with reasonable effort.
  13. Looking at your picture, I notice that the lower right corner is actually sharp: that wall socket seems to be quite nicely in focus. The rest of the picture obviously isn't -- even though there are many objects at roughly the same distance from the lens than the wall socket. Also the upper half of the shelf exhibits some very strange ("wavy") perspective distortion. This looks like an optical problem. Like a misalignment between lens and sensor or so. Sadly, I do not think this can be corrected for in software. @Jacob_S posted similarly distorted pictures earlier in this thread. Mayb
  14. That is, unfortunately, precisely my situation andd the reason why I am still using the last LOS 16 build ...
  15. As much as I enjoy the fact that LineageOS on the Pro1 seems to be alive and well, I am puzzled by the practice of removing previous major releases from the build systems as soon as a new version is made. In November, LOS 16 stopped receiving upstream updates (in favour of 17.1) just a few months after I had installed and -- quite heavily -- configured it. Now, 5 months (!) later, 17.1 disappeared from the build targets for the Pro1 at the very moment 18.1 came around the corner. I understand that a community project may need to save computing ressources on the build farms. Stil
  16. Setting up the ssh server seems a bit tricky in UBports indeed. The official docs -- which your certainly know already -- list several ways of transferring the key. I am no UbuntuTouch user, but basically, one encounters the same problems when setting up the SSH server in LineageOS. There, the easiest way (for me) was to grab the required public keys from the PC to the phone using Lineage's built-in SSH client (as opposed to pushing the files to the phone, which requires a working SSH server in the first place). Not sure if Ubuntu includes an SSH client out-of-the box, but if not, I would
  17. Update: I can now run the X.org X11 server inside my Devuan chroot. Yes, the real thing, not TigerVNC or TightVNC. The nice thing with X.org is that I can use it with xorgxrdp in the chroot and connect to my Linux distro via a much better-performing (native) RDP connection as compared to using VNC as backend for XRDP. I still use the Microsoft Remote Desktop 8 App combined with the default xrdp-0.9.9 shipping with Devuan 3/Debian 10. As far as I can see, one can find no information on how to do this on the internet. Either it is really tricky and I am a genius, or no one cares about
  18. Of course, an unlucky hit can get through the unprotected side of a flap case. My main point is that the case (any case for what matters) reduces the chance the Pro1 will slip out of your hand in the first place. As a bonus, a flap case also removes the need for a screen protector sticker. As much as I enjoy enthusiast projects, the 3D-printed cases I have seen so far (from pictures only, of course) look a bit awkward. They are certainly perfectly functional, but aesthetically not very appealing (to me at least). No hard feelings, but for now I will stick with my flap case ...
  19. Agree. I do not have a screen protector, but I decided for a flip case on day one. The Pro1's surface finish is nice but it enables the phone to slip out of your hand far too easily ...
  20. Ouch. I feel your pain. Maybe I should invest in a spare too as long as they are easily available. Is the Elephone U spare part on AliExpress the known-good screen for the Pro1?
  21. I remember you got your device only a month ago or so. What's wrong with your screen? Just asking ... About that APK for installing the required firmware: Is it (legally?) impossible to put that up somewhere for public download? It will certainly be of interest to many sooner or later. People replacing their screens will typically want to avoid reflashing their phones to stock and back just to get the replacement screen working.
  22. Wow, what a mess, indeed. From the other thread, I get that those who do not see the "Enhanced 4G LTE Mode" switch have VoLTE disabled anyway (because their OS, or their carrier, or both do not support it). So, according to @Rob. S.'s hypothesis, they should not encounter the loudness bug in the first place. However, @pistikem seems to have the bug despite not having VoLTE. Are we on the wrong track after all?
  23. In my LineageOS 16 it is called "Enhanced 4G LTE Mode" and is only visible in the "Advanced" settings under "Mobile Network". I do not think it is specific to LineageOS. As far as I know, the option used to be called "VoLTE" or "HD voice" in previous Android versions. But seemingly the switch controls more than just Voice-over-LTE nowadays: If I switch it off, also "Carrier video calls" get disabled. Potentially, you might loose other useful things like conference calls -- not sure about that, though (and too lazy to test). VoLTE is also said to use less power compared to 2G/3G calling, s
  24. Well, me too, and that is exactly how I use my Pro1. Not with Ubuntu, though. My point is that, for a phone to work as a miniature "laptop", all the functionality must be there in principle without carrying external devices along. For that is what a laptop is: a standalone all-in-one machine that has all required peripherals built-in. That you can extend functionality by plugging even more stuff into the device is a bonus, not a requirement. This does however not seem to be what the OP have in mind: they seem to refer to the so-called "convergence" mode of operation, where the phone
  25. Am I the only one who came here directly from an N900? I learned about the Pro1 on the maemo.org forum, where it was discussed as the spiritual successor of the N900 (and N950 for those who were lucky enough to have one of those). I (like others) used the N900 well beyond its time, as it was the only true Unix(-like) phone for years. I invested quite some time into setting up my Pro1 in a way that it can compete with the N900 in terms of usefulness as a Unix workstation. And while I have come quite far in that project, it is clear that I still do not have control of the system on a l
×
×
  • Create New...

Important Information

Terms