That's why it's considered good practice to act on the presumption of innocence until proven guilty.
Indeed - https://xdaforums.com/t/does-twrp-function-with-non-aosp-oses.4692346/post-89709288 seems to elaborate quite well, if you agree with it. Thanks for the response.
If interesting, I've also posted at the XDA Developers forum about whether this is more broadly applicable.
I'd like to install PMOS onto my Fairphone 5, because TWRP recently became available for it. However, the comments and post above this Reddit comment appear to demonstrate that the PMOS installer might overwrite all partitions (A and B, but also Recovery), if I've understood it correctly.
Has anyone used both together? If so, can you confirm whether it functions (as expected)?
You couldn’t even comprehend that I wasn’t criticising a person (consider this as criticism).
I evidently am able to comprehend it. If I were as incapable as you purport, you informing me would be worthless. You doing so, with this response, demonstrate consequently that your assumption is incorrect. It's a strange one to make.
It really isn’t that great that instead of active discussion you stumble upon months-old threads.
You responding renders it active. Any alternative designation is fundamentally nonsensical.
If you're to discuss semantics, be more pedantic, else this conversation is uninformative for us.
I made a point illustrating that switching off from reddit didn’t do any good for the community.
I'm aware. It's quite easily comprehensible. However, it's unsubstantiated, hence the downvotes.
Q&A for users of Linux, FreeBSD and other Un*x-like operating systems
After researching why current consumer and embedded ARM (and, to a lesser extent, embedded RISC-V) devices are difficult to port to, the primary reason appears to be device discovery and driver support.
Obviously, extracting proprietary drivers from a potentially outdated AOSP-based OS version with a probably quite outdated kernel and getting that to run in mainline is a lot of work.
However, getting device trees shouldn't be, and really shouldn't be necessary, since they're not something that a manufacturer would hope close to their chest, unlike complex driver software.
Consequently, I would like to request to Fairphone – considering their mission statement – that they provide device trees and enumerable busses (if they don't) but would like to verify here that I wouldn't look like a moron asking for the wrong thing.
I hope this makes sense.
No, I had not. That's certainly novel.
Really impressive work. SystemD was the sole thing missing from PMOS for me – I'm ecstatic that I'll finally be able to say, when it's done, that – excluding 3rd-party GUIs’ support – it's better than AOSP.
Yeah, I just installed it from 23.12's repository. Works well for the basics. Many thanks.
Thank you. I'll use that information about the USB ID for my report to KDE. However, could you elaborate somewhat? That is, would it be correct to ask for Plasma to not merely utilize the USB ID to identify whether a device is accessible, but test whether it can be accessed by MTP first, before presenting that option to the user? Regardless, per what you've said, I've consolidated my previously disparate reports under https://bugs.kde.org/show_bug.cgi?id=486931.
Additionally, I'll definitely mention on Bugzilla that incorporating some of the patches in that package would be a feasible implementation method. Relevantly, I'd like to use that package, but because I'm not using Edge, would adding that repository do any harm (for instance, would it be added with higher priority by default than existent repositories)?
Those criticisms seem reasonable. Regarding package signing, are you referring to https://github.com/NixOS/nix/issues/613#issuecomment-134361033? Additionally, that default for pip seems veritably insane. I understand using system packages, but modifying packages outside the virtual environment is definitely weird.
> Having ascertained https://discuss.kde.org/t/how-to-capture-a-screenshot-in-plasma-mobile/15070/2?u=rokejulianlockhart, I'd like to be able to transfer screenshots off my Plasma Mobile device. > > 1. I try to access it via KDE Plasma 6's Disks & Devices plasmoid (widget): > > > !Screenshot_20240505_041647|460x450 > > 1. However, all I see is: > > > !Screenshot_20240505_041605|689x170 > > Weirdly, it's acting like https://bugs.kde.org/show_bug.cgi?id=486594#c0.
I ask because I'd like to upload screenshots to https://bugzilla.mozilla.org/show_bug.cgi?id=1895116#c1, and ascertain whether it affects https://gitlab.com/postmarketOS/webflash/-/issues/2#note_1892953259.
You shouldn't criticise someone because they were late to a discussion.
It worked for me. I came here instead of Reddit, which would have alternatively been my primary choice.
I'd like it opened for new users to be able to participate there without a Lemmy account, but there's a cost-benefit ratio to everything, and the additional moderation burden and potential fragmentation of the small community appears to outweigh the benefits. Additionally, a lack of choice paralysis can be quite a significant advantage.
I used it yesterday, via Pidgin. I'm rokejulianlockhart@xmpp.jp. Why else would I have referenced it? Don't tell me what I've done. That's not a way to have productive conversations.
Regardless, I can't provide any more technical insight than that - I know solely that the clients provide so much more functionality that irrespective of the protocol, it's better in practice. Fedora, openSUSE, the Bundeswehr, NATO, and Beeper - all chose Matrix over XMPP, not least partially because of Element (which they also all chose).
I don't believe that its existence causes more fragmentation than it remediates. https://news.ycombinator.com/item?id=36939482 explains why I consider Matrix fundamentally superior most (if not all) uses, although in practice it's because the clients (Element and FluffyChat primarily) are cross-platform and support a generally uniform set of features, in comparison to the aged (but glorious) Pidgin, and its counterparts.
Its bridges are FOSS, but its client (an Element fork) doesn't appear to be.
Mr. Beedell, Roke JL @lemmy.ml My GitLab profile's readMe.MD states:
> Hello. My first name is Roke, and I always shall, and have been since I gained my first computer, a software developer. I specialize in OS architectures and GUI consistency, accessibility, and ease of use.