Jump to content

claude0001

Members
  • Content Count

    463
  • Joined

  • Last visited

  • Days Won

    53

Posts posted by claude0001

  1. Interesting discussion. What I have observed with some WiFi's run by shopping malls is that they block price-comparison websites. <conspiracy> So maybe the have an interest in locking your out of your mobile network ...  🕵️‍♂️ </conspiracy>

    On a more serious note, in my daily life, I lack mobile network just too often. I travel by train a lot, and there are still too many uncovered areas in the open countryside. At my working place there is practically no chance of having mobile data at all (radiation protection walls). So I rely on local WiFi's even for phone calls much of the time. To be honest, I never worried much about it ...

    4 hours ago, Rob. S. said:

    But I guess that's what VPNs are for...

    Hmm ... not so sure about that. It is true that an (encrypted) VPN would protect you from a malicious WiFi admin overhearing your communications. But that can be achieved with any kind of end-to-end encryption, as is standard on the Internet nowadays. Protocols like https can safely be used even on a fully unencrypted WiFi from that point of view.

    What I thought we were discussing here is the (theoretical) possibility of the WiFi access point exploiting some vulnerability in your unpatched phone OS to get access to your device. I do not think that can be excluded via the use of VPN. After all, a VPN is just a virtual (tunnel) interface that relies on an existing physical network connection underneath. So, obviously, the latter has to be established normally before the TUN interface can be installed. In order to be accepted on the typical (semi-)public WiFi, you have to register by accessing a web interface controlling the AP. In theory, that would probably be enough to exploit some vulnerability e.g. in your web browser (apparently my LineageOS always uses the built-in browser for that, even though Firefox is set as default).  

  2. 2 hours ago, EskeRahn said:

    my 'Paranoia' never would let me connect my device to a net where I do not feel they are suitable secured behind firewalls. And thus never in any circumstances to a public WiFi.

    No offense, but that does not seem very practical to me. The only network you can trust on that level is one you configured yourself. For most users, that would mean to connect their Pro1 to the Internet only at home. At that point it is not really a mobile device anymore ...

    We do agree that banking is best done at home anyway. I use only my PCs and separate hardware tokens for that. In fact, by relying on security of a single system (the phone), most banking apps undermine the very principle of two-factor authentication which lies in using two independent devices that are air-gapped from one another.  

    • Like 1
  3. 47 minutes ago, savvy said:

    Not sure if you ever tried but have you successfully run docker inside your Chroot distro ?

    I am not sure if "recycling" an old Android device to run any Linux home servers is worth the trouble, considering how cheap and powerful RaspberryPis (or similar single board computers) have become. They provide a full-featured and well-supported GNU/Linux environment, with Docker just an "apt install" away. With Android chroots, you'll always be on your own to solve any issues emerging (trust me on that 😉 ).

    I do not know about Docker on Android. Yes, it seems like a lot depends on what your kernel provides. I would guess that installing everything manually in a chroot should always be possible somehow. But I have no experience with those servers you want to set up. 

     

  4. 1 hour ago, raymo said:

    having a pro1 with a linux container ...

    I probably shouldn't have hijacked this thread for advertising Debian-on-Android containers/chroots. While I love to have that possibility with my Pro1, and use it every day, this is technically not comparable to running a foreign OS on the device. 

    What we actually do, is just run a second userland on the existing Android Linux kernel, which is rather trivial and probably considered "cheating" by the authors of Project Renegade. 🙂  

    The cool thing about Project Renegade is that it can run Windows ARM (or an upstream Linux kernel and OS!) natively on the mobile device. Technically, that's very impressive. The practical usefulness is probably limited, though, as you'll hardly be able to use the device as a phone while running Windows or a desktop Linux distribution. I do not know, if dual-booting with Android would be feasible.

    • Like 1
  5. 8 hours ago, sequestris said:

    These people are my friends.

    I see and fully support your point that aggressive ranting about F(x)tec, as is popular on the IGG forum, does not help anyone and certainly will not lead to better communication.

    However, what you are insinuating is also wrong: customers should not need to be "friends" with companies they do business with in order to get support queries answered.

    Anyway, your "system" is not scalable: if we all had personal ties with the guys at F(x)tec, their mailboxes would be flooded with cat pictures in addition to our user requests. I do not see how that would improve responsiveness ... 😉     

    • Like 1
    • Haha 2
  6. 6 hours ago, ToniCipriani said:

    They also have the advantage of having x86 emulation

    On Linux, there are tons of solutions for running x86(-64) code on aarch64 efficiently. Besides traditional qemu, there are new projects like FEX and Box86/64 that, reportedly, can do amazing things.

    However, most of the time, emulation is just not necessary. Linux has supported ARM for so long that every major distribution has an aarch64 branch containing (almost 😉 ) all the software you will ever need ... 

     

  7. On 4/3/2022 at 8:17 PM, ToniCipriani said:

    Anyone heard of this?

    I had heard of it. Technically, it looks like an awesome project.

    The only reason I did not dig deeper is that I am no Windows person, full stop. I achieved my (Linux) laptop experience with the Pro1 quite some time ago and and have been a happy camper since. The big advantage of a Linux desktop is that it can run in parallel with Android (using the same Kernel) so that you do not sacrifice any "smartphone" use cases in favour of running the desktop OS.

    I do envy them for their accelerated 3D graphics though, which is not at all possible with my solution as of today. 😞

    • Like 2
  8. 2 hours ago, fxtec-preorder-47xx said:

    It's OBVIOUSLY not meant for you.

    Sorry, but this is not true. You quoted a post of @VaZso, and then responded with the opening sentence "Don't you think ...".

    I am ready to believe you did not mean to address your rant at @VaZso, and that the impression of you doing so just resulted from a careless writing style of yours. However, this interpretation is all but "obvious" and, even if true, would still call for an apology.

    In other news, all-caps are usually considered equivalent to shouting, for which there is also no need here. Even if we all frustrated about manufacturing delays and F(x)tec's communication skills ... 😉

    Everyone try to relax. Keyboard phones are important. But not that important, are they?

    • Like 5
    • Thanks 1
  9. @daniel.schaaaf and @VaZso: I think we already discussed that elsewhere, right? I have not found any switch to enable or disable sticky shift. Interestingly, I found that the feature does not work in all apps: On my setup, "typical" smartphone apps like messengers and firefox tend to have it enabled, while more advanced things like terminal emulators and text editors usually don't. Seems like apps can choose to support that accessibility feature or not.

    • Like 1
    • Thanks 1
  10. As @Jacob_S point out, all editions of LineageOS for the original Pro1 have the sticky-shift feature enabled. We do not know about the successor Pro1-X yet (Pro1 is no longer available).

    I might add that, because of the large size of the Pro1, I find it is not practically possible to use the keyboard while holding the phone single-handedly -- with or without sticky shift. You'll still have to put it on a table when typing with one hand.  

    • Like 1
  11. On 3/8/2022 at 2:55 PM, archseraphim said:

    [...] the device did experience a drop several months beforehand which was severe enough to break the screen, and that I replaced the screen myself. [...]

    I'm not downplaying the known bad communication skills of F(x)tec, but this fact alone would have led other manufacturers to say: "Well you broke it, and, after that, you probably made things worse by exchanging parts yourself. Our <shiny-new-successor-product> is superior to your broken phone anyway, consider buying that as a replacement. Otherwise, please don't bother us anymore."

    • Like 3
  12. 4 hours ago, daniel.schaaaf said:

    And, this build got rid of the Bluetooth file transfer MIME type restriction.

    Interesting. I wasn't aware there were file types one could not send via bluetooth. But you are right: shell scripts are not accepted for me either. Not that I use BT file transfer much (ssh rules!), but I might still include this in my next ROM, too. Thanks for sharing.

    • Like 1
  13. 6 hours ago, Rob. S. said:

    I can finally clear this up!

    Thanks for sharing. Few would think about the SD card being the reason for the long boot time.

    Good luck with your next card. I've had a Sandisk Extreme 256 GB almost since day one. I run my GNU/Linux chroot on it (which certainly causes above-average disk-I/O) and it still hasn't failed me.

    • Like 2
  14. 22 minutes ago, steff said:

    I wonder if  the ubports development will be affected in a positive way by the added support to the 5.16 linux kernel.

    No, I think it won't.

    UbuntuTouch for the Pro1 (and for the Pro1-X, as far as I know) is a hybris port, meaning it does not actually use it own Linux kernel. It re-uses the kernel of the original AndroidOS that came with the device (together with other core parts of Android).

    That basic support for the Pro1 is in mainline now, is certainly a good thing in itself. But right now it allows not much more than booting to a terminal. There is no support for any advanced hardware that one needs for the device to fulifil its purpose as a phone. It may be an interesting starting point for new applications of the Pro1, but using this as a new basis for UbuntuTouch would be a serious set-back for that project.

    • Like 1
  15. In LineageOS 16.0 this works: long-pressing any accentable character on the hardware keyboard (e.g. 'a') brings up a selector box allowing you to pick any accented variant ('à', 'á', 'â', 'ä', ...) using the touchscreen. The box looks a bit rustic, like using a design from previous Android versions, but it works. Not sure about the later Lineage versions 17.1 and 18.1.

    Note that this is for the original Pro1 only. We still know nothing about software for the new Pro1-X. The LineageOS ports for the Pro1 will no longer work because of the different SoC. A new port will be necessary and probably be based on some other, already existing snapdragon-662 device. But the keyboard driver of the Pro1 is open-source, and, I guess, the keyboard hardware has not changed. So maybe those bits can be re-used.

    • Thanks 1
  16. 1 hour ago, VaZso said:

    However, I don't know why there are a plenty of capture / playback devices there

    Indeed. I cannot use any of the standard ALSA tools like aplay for doing anything with these devices. I am testing from a rooted GNU/Linux chroot.

    In contrast, if I connect a standard USB sound device, I can control it normally via ALSA. So I assume that proprietary driver is just behaving differently.

    Edit: Better be careful when messing with the sound interfaces directly. I remember that, on the N900, one could break the internal speakers that way (as one was able  to bypass some software filters in the driver, I think).

  17. On 6/22/2021 at 8:15 PM, claude0001 said:

    I uploaded my latest Lineage 16.0 build, dated 20220225.

    • It includes the February 2022 fixes from the 2022-02-05 Android Security Bulletin. These fixes are now backported to Lineage 16.0 by the good people at lineageos.org, as AOSP does not officially support Pie anymore. I bumped the Android security string to reflect this.
    • New local mods since the last release: Backported some CPU and GPU (surfaceflinger) optimizations that, while initially proposed against 16.0, were merged only in 17.1.
    • My full local patchset with respect to the upstream lineage-16.0-branch can be downloaded at the link above. 

    Have fun.

    • Like 3
    • Thanks 3
  18. 4 hours ago, adam.c.r.roman said:

    Can we get this driver in the stock OS from f(x)tec?

    I guess, the simple answer to this is (and has been for a while): No.

    The official Android 9 for the Pro1 is dead. I do not expect that there will be any more fixes from F(x)tec.

    Although the stock keyboard driver is open-sourced, producing a fixed driver and installing it in the stock ROM in binary form is probably not possible because of code signing. I am no expert on this though.

    The pragmatic way of getting better keyboard support would be to simply install a recent LineageOS release, which improved on the duplicate-stroke issue (besides many more enhancements). The relevant patches are here and here. Note that the keyboard driver (the qx1000.c source against which the patches are applied) was completely rewritten by @tdm as part of the initial port to Lineage OS 16.0, so these patches would probably not apply directly to the Stock sources.

    • Like 2
  19. We do not know anything about the status of OS development for the (future) Pro1-X.

    What we do ḱnow is that UbuntuTouch on the original (835)  Pro1 is falling behind LineageOS by many orders of magnitude. LineageOS outclasses even the official Android 9 OS that came with the device, while UbuntuTouch -- unfortunately -- lacks some of the most basic functionality even two years into development

    The reason for this is that F(x)tec officially support neither of those OSes for the original Pro1, but, because of the much larger community, LineageOS has much more traction. Hopefully the situation will be different for the Pro1-X.

    The way you ask your question however makes me suspicious about whether you truly understand what UbuntuTouch is. UbuntuTouch is not comparable to the Ubuntu Linux distribution for PCs. It is a smartphone system quite similar to Android. In fact, it even does not use a Linux kernel from Ubuntu, but rather that of the Android OS that initially shipped with the device! With UbuntuTouch, you shouldn't expect to to use standard Unix software out-of-the-box, nor should you believe you can use apt for managing your software, or be able to use traditional Unix paradigms in your daily workflow. Are you aware of that? In what sense do you expect UbuntuTouch to be more "Linux" than LineageOS?   

    • Like 1
  20. 10 hours ago, Doktor Oswaldo said:

    But it is stupid, I would say LOS is at least on pair with a Android FxTec patched together.

    I'm using Lineage myself and completely agree on that point.

    However, also @EskeRahn is right in that "certification" of a software does not necessarily mean that the software in question is technically superior to any other. It just guarantees that it fulfills the requirements of a certain defined standard in terms of configuration and behaviour. 

    Technically, my self-built LineageOS 16.0 is, both, more capable and more secure than Stock Android 9: unlike the latter, it contains the latest security patches and the many feature enhancements implemented by the LOS community and myself. However, without code-review, no-one can guarantee that I did not modifiy critical parts of the base AOSP system in a way they simply do not qualify as "Android" anymore, or that I did not include backdoors, malware, or other evil-cracker stuff at compile time. Hence my ROM cannot (and should not) be considered a certified Android 9. 

    • Like 3
×
×
  • Create New...

Important Information

Terms