claude0001
-
Content Count
790 -
Joined
-
Last visited
-
Days Won
120
Posts posted by claude0001
-
-
-
12 hours ago, VaZso said:
Anyway, I just checked there are mkfs.exfat and mkfs.ext4 available... what do you think, if I format my SDCard to ext4, will it handle it as SDCard?
...just because I may like to install a Linux environment later and ext4 would be much better than FAT32 which it currently has.I have an ext4 partition on my SD card and it is recognised by Android. I did partition and format the card using my Linux PC, not from the Pro1, though.
Beware that many Android Apps will have problems accessing the ext4 partition. A file manager with root access will work, but many "normal" Apps won't. After some months, I found that disabling SELinux at boot time and re-mounting one of the many cryptic mountpoints of the SD partition allows one to use it almost normally from Android. I described that in this post. Of course one may want to think twice before nuking SELinux as that disables large parts of the Android security mechanisms. Also note that, even with that hack in place, you will always have file ownership mess as every App runs under another UID.
Concerning installing a Linux environment: I have my Debian installation on another partition of that same SD-card. For that partition I found that it must not be formatted as ext4, otherwise I cannot mount it to a custom location (e.g. /data/DEBIAN) at boot time. The reason is probably that Android recognises and "takes over" ext4 file systems into its awkward access management system. What worked for me is using ext3 for the Debian system partition. While the kernel has ext3 support, Android seems to leave that partition alone and allows me to use it to my own liking.
All this is experience from LineageOS 16, i.e. Android 9. Later releases introduced significant changes in the Android security mechanisms, so the behaviour may well have changed. That is actually the main reason I do not upgrade from LOS 16, as I can not be sure these workarounds would still work ...
-
2
-
-
4 minutes ago, Slion said:
I do not know. I'm new to this. Some people where saying they need to re-sideload Magisk. Maybe either Gapps or Magisk does the trick somehow.
I never had Gapps installed, but I am pretty sure that at the time LOS 16 was in testing phase, @tdm always reminded people not to forget to reinstall them after flashing a new version via sideload.
-
1
-
1
-
-
10 minutes ago, Slion said:
Looks like I always have to sideload gapps after ROM update otherwise it won't start.
Isn't that to be expected?
I also have to re-sideload AddonSU each time I flash a new ROM.
-
10 minutes ago, VaZso said:
So official LineageOS 18.1's recovery is currently installed on that device and it can be used to sideload my own build but I could not get it to boot without a factory reset after every new builds I made.
For me (on LOS 16) sideloading my custom ROM from the official recovery would just fail (without anything getting flashed), so I am not sure if this is the same phenomenon.
-
1
-
-
3 minutes ago, VaZso said:
I have found after sideloading LineageOS, I have to reboot back into recovery, it switches slots, then I can sideload Magisk and MindTheGapps.
Yes, that's the correct procedure, which worked for me since I got my Pro1. Upon flashing the ROM it switches the active slot. A reboot is then needed to make sure any additional software is actually sideloaded into the right OS.
-
2
-
-
14 minutes ago, VaZso said:
However, somehow I could not even sideload LineageOS of my own build without doing a factory reset.
Do you nhave any ideas what may I have done wrong?You mean sideload your own build over an official one?
That will only work without wiping data if you migrate your setup from 'official' to 'testing' keys.
Also, at least for LOS 16.0, the official recovery would not allow me to sideload my own build. I had to first flash my self-built boot.img using fastboot (to both slots, just to be sure 😉).
-
2
-
-
43 minutes ago, Slion said:
@claude0001 I'm in the process of setting up a VirtualBox for my custom build.
Will I need to reset my phone if I sideload the resulting ROM on top of my WSL ROM?
No, I do not think so. As far as I know, the "testing" keys are not unique to a certain building environment, so you should be able to flash the new build over the previous one without migrating.
Did you actually solve that issue you had with installing Gapps and other Apps on your custom build?
-
1
-
-
46 minutes ago, EskeRahn said:
Look at it another way. Why should a bank care if they did not see a reduction in their risk of loosing money somehow?
Sounds a bit like "Trust the authorities, they will know what is good for us." 👮♀️
I am not saying they have no reasons for doing what they do. I am saying that those reasons have nothing to do with technology and are thus not valid.
I believe they check against rooting as that breaks the App for only few technically-skilled customers, while giving all others the warm feeling that they care about security.
Technically, checking the Android patch level (and refusing to run on outdated systems) would make much more sense. However they will never do that as it would affect way to many clueless users who happily run their 3-years-outdated phones, because, you know, it still "works" and -- after-all -- it's not rooted, so what could possibly go wrong?! 🙃
-
2
-
-
4 hours ago, EskeRahn said:
And as security on phone banks apps are often down to simple four digits pins, and phones are stolen more than laptops, it all adds up to higher risk for the banks
Well, authentication at an ATM is done using that same 4-digit pin. And banking cards get stolen all the time. So I am not sure about that argument. 🤔
We are wandering off-topic here, but I think it is an interesting discussion, so let's go.
First, even looking at things in the most positive way, I fail to see how preventing root access from user space adds any security to the latter. After all, even with root access enabled, Apps do not gain that access right any more "easily" than any other permission. User interaction is required all the same.
But then, there are more fundamental aspects: Imho, hiding root access to users in an open-source operating system does not make sense by first principles: After all, anyone, including the user and the oh-so-trusted 3rd-party SoC vendors can implement any backdoor or other security breach they want prior to compiling the code. Once an App runs on Lineage, why should it care about "su" being present or not?
That may seem too theoretical, so let's restrict the discussion to "official" Android distributions: Then, as @Rob. S. correctly points out, the most practically relevant security issue is still that device support relies on those hardware vendors, which abandon devices at a much higher rate than customers replace them. The Pro1 is a typical example (though by far not the worst): Stock Android 9 has dozens of published and unfixed vulnerabilities to privilege escalation. Also in that situation, hiding root access from the user does not really add any layer of security anymore.
Of course everyone, including Google, hardware vendors, and App publishers, know these things. So, I think all that noise around rooting is there mainly to cloak the fact that Android security, as implemented today, is broken by Android's very publishing model.
-
1
-
-
1 hour ago, Rob. S. said:1 hour ago, claude0001 said:
Wtf is wrong with this world?!
Don't get me started on this 😉
After thinking about it, I see now that that rhetoric question was not very compassionate.
That millions of children suffer from hunger is indeed unbelievable.
That Apple and Google feist on user rights may be deplorable too, but it is also not that inevitable, after all ...
-
2
-
-
2 hours ago, Hook said:
Gives you root, doesn't require Magisk Manager (although it does install it—I ignore it), doesn't require any bootloader dance. It just gives root to the apps you grant root access to.
That sounds good. I wonder why there is no "light" version of Magisk as spritual successor of AddonSU. I really do not need all of that advanced stuff related to "hiding" the fact that I am rooted. Know what: I am proud of running a rooted device!
I hate all that FUD spread by Apple and Google around rooted phones (despite them knowing better, of course). Guess what: I have root access to my desktop PC, my laptops and my (Internet exposed) home server. Of course that does not mean that *all* software on them runs with root privileges! And, yes, of course, my bank allows me to make transactions from my "rooted" Thinkpad! Why should we look at smartphones any differently? Wtf is wrong with this world?! 🙂
-
3
-
1
-
-
4 hours ago, Sean McCreary said:
I'm curious about how you use 'su' or root access, if you're willing to describe it. For my part I haven't needed anything more than 'adb root; adb shell' for occasional administrative (mostly development) work in many years.
Well, even within Android there are use cases that require root management. E.g. file managers. However, the main reason is that I run a GNU/Linux chroot in parallel to Lineage that requires root access for all kinds of things.
Last, I simply like the idea that I have full control of the system from userland if I want or need it. I consider my Pro1 to be more of a computer than an appliance. So I expect to have the same possibilities as admin than on my PCs. 🙂
Of course, Magisk could do all of that. I like AddonSU because it is low-profile, nicely integrated in LOS, and an "official" solution.
-
4
-
-
1 hour ago, Sean McCreary said:
The 'su' extra package was discontinued after LineageOS 16.0
Sadly yes. As far as I know, that happened because changes in Android security mechanisms made porting AddonSU to LOS 17 non-trivial at best. One of the reasons I am camping on LOS 16 ...
-
2
-
-
12 hours ago, marmistrz said:
I switched to the AOSP keyboard, turned off the autocapitalization. the software keyboard doesn't autocapitalize, the hardware one does (tested by writing an e-mail in k9 mail)
While my hardware (qwertz) in principle works well with AOSP keyboard (can disable autocapitalization in the settings, sticky shift works), I also observe some quirks in K9-Mail only. So maybe test also in other apps.
Most annoying for me is that whenever I type "im" (german for "in"), that gets auto-replaced by "I'm", although AOSP keybaord is set to german input language and all auto-replacements are disabled in the settings. K9 is my only app that does that. Still hoping that misbehaviour will disappear with some update of the app as it seems to be the only (open-source) one to support arbitray IMAP folder configurations ... 😐
-
1
-
-
3 hours ago, Slion said:
I think I fixed it in the last patch. Did a build and testing it again.
It built alright in the LOS 16 tree. Flashed it some minutes ago.
Fn-Tab and Fn-Shift-Tab work as expected. I could not spot any regressions up to now. I will keep this build for the weekend and report.
-
1
-
-
10 hours ago, Slion said:
I'm having a hard time installing APKs on my custom Lineage OS build. First for some reasons I could not setup gapps probably because of signing issues. Then the Files app won't open some apks. Some work like the one from my Fulguris Web Browser, some do not work like the one from F-Droid or my Fx Service. It has not much to do with the APKs themselves it's just that the Files app won't install them for some reason. When I had gapps I could use another File Manager to install them but as it is I can't cause I can't even install F-Droid…
This seems really awkward. I fear I cannot help here.
I have been using my self-built (testing-key-signed) Lineage for months. And while I do not use Gapps (on purpose 😎), I can sideload LOS-16's official AddonSU, and I can install any App via F-Droid, Aurora, or by opening the *.APK from the file browser.
I did migrate a previous official Lineage install using the procedure explained in the Lineage wiki in order to not loose my data upon installing my own build. But that was it.
I understand you wiped data before flashing your build ("Nuke the entire site from orbit!"), so I would expect signing-keys not to be an issue for you.
-
1
-
-
3 minutes ago, Slion said:
I don't think we want most of the functionality. We want the actual Alt+Tab functionality.
I agree. The point is to comfortably switch apps while keeping your thumbs on both sides of the keyboard and not having to use the touch screen.
3 minutes ago, Slion said:I think fixed it in the last patch. Did a build and testing it again.
Yes. I had added back the "+" manually and it is building now ... 60% and going strong. I expect a flashable LOS 16.0 with Fn-Tab functionality in 2 hours or so ... 🙂
-
2
-
-
@Slion, I think you introduced a typo in the latest revision of the patch. Build fails with
../../../../../../kernel/fxtec/msm8998/drivers/input/keyboard/qx1000.c:1709:41: error: expected ';' after expression size = sizeof(struct gpio_keys_drvdata) ^I think that line should stay like in the original code:
size = sizeof(struct gpio_keys_drvdata) + pdata->nbuttons * sizeof(struct gpio_button_data);You probably deleted the "+" by accident in the latest edit.
-
1
-
1
-
-
3 minutes ago, EskeRahn said:
This mode can not be triggered as described with the default AOSP keyboard
Works for me with AOSP keyboard on LOS 16.0. Others report it also works on LOS 18.1.
So maybe the feature can be switched on/off somewhere. Do not know where, though ...
-
1
-
1
-
-
The patch (patchset 6) applied cleanly against my LOS 16.0 tree. Just started the build ...
-
1
-
1
-
-
1 minute ago, Slion said:
No, I've only submitted to 18.1 not sure what's the process is to propagate it to 16.0. As it is if my change is merged it only goes to 18.1 branch.
That would be great. If the driver code is still the same then you can just copy the file.
We'll see. I think the proposed behaviour is definitely useful.
If the patch does not apply cleanly, I'll try to backport it. If all goes well, I'll start a LOS 16 build with your new driver code in the evening and will report tomorrow.
-
1
-
-
29 minutes ago, Slion said:
I've implemented a new feature in Lineage OS Pro¹'s keyboard driver to be able to use Fn+Tab as Alt+Tab as this is most convenient for multitasking with two thumbs.
That would make a lot of sense, indeed.
If the patch gets accepted in the kernel branch, would it be in effect for all LOS branches (16.0, 17.1, and 18.1), or just for 18.1?
I could test against 16.0 by applying the patch to my local copy of 16.0. Should I?
-
1
-
-
21 minutes ago, Slion said:
Can't enter that mode. Is that a driver feature or virtual keyboard feature?
I should add that this does not work in all apps. E.g. sticky shift works in Firefox, K9-Mail and 1+Term, but e.g. not in ConnectBot or CollaboraOffice.
So probably Apps can opt-in and out of that feature.
-
1
-
Recent changes in LOS 18.1 regarding apps and battery optimisation?
in General Discussion
Posted · Edited by claude0001
I can confirm that the category "optimisation not available" exists on Lineage 16, too. Though I have only a handful of system Apps, mostly related to telephony, that fall into it.
Specifically, my GPS App (OsmAnd) is listed as "optimised".