rokejulianlockhart

joined 2 years ago
[–] [email protected] 1 points 2 weeks ago

That's why it's considered good practice to act on the presumption of innocence until proven guilty.

[–] [email protected] 4 points 2 weeks ago
[–] [email protected] 1 points 1 month ago

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.

[–] [email protected] 1 points 1 month ago

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)?

[–] [email protected] 1 points 3 months ago

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.

 

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.

[–] [email protected] 2 points 3 months ago (1 children)

Is it FOSS? I'm having a difficult time locating its source.

[–] [email protected] 1 points 3 months ago

No, I had not. That's certainly novel.

[–] [email protected] 2 points 3 months ago

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.

5
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
 

A few weeks ago, VSCode began to constantly recreate tabs. Notably, they are always considered to have been modified, so I have to confirm their closure.

I initially thought that the undermentioned log might be the cause:

2024-07-10 13:50:43.340 [error] Unhandled method getIdAtPosition: Error: Unhandled method getIdAtPosition
    at /home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:398068
    at re (/home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:398362)
    at /home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:393146
    at Immediate.<anonymous> (/home/RokeJulianLockhart/.vscode-insiders/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.8/dist/extension.js:2:393166)
    at processImmediate (node:internal/timers:478:21)
    at process.topLevelDomainCallback (node:domain:160:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)

...because another entry appeared to always occur each time I closed one of these tabs. However, it stopped appearing today, so I'm a loss for the cause.

The attached URI is this video, which depicts the reappearance of the tabs. The attached image depicts multiple entries of the aforementioned log.

 

As https://github.com/orgs/PrismLauncher/discussions/2550#discussion-6847972 explains, I'm trying to debug https://discussion.fedoraproject.org/t/random-indefinite-system-hang-and-crash/110020/1#related-issues-3 using flatpak run --command=sh --devel org.prismlauncher.PrismLauncher and gdb /app/bin/prismrun. However, so that I can ensure that its environment matches mine, and so that I don't have to do an absurd amount of configuration each time I try to debug, I'd like to not have it create an entirely new userdata storage each time I debug.

 

As https://github.com/orgs/PrismLauncher/discussions/2550#discussion-6847972 explains, I'm trying to debug https://discussion.fedoraproject.org/t/random-indefinite-system-hang-and-crash/110020/1#related-issues-3 using flatpak run --command=sh --devel org.prismlauncher.PrismLauncher and gdb /app/bin/prismrun. However, so that I can ensure that its environment matches mine, and so that I don't have to do an absurd amount of configuration each time I try to debug, I'd like to not have it create an entirely new userdata storage each time I debug.

[–] [email protected] 1 points 5 months ago

Yeah, I just installed it from 23.12's repository. Works well for the basics. Many thanks.

[–] [email protected] 0 points 5 months ago* (last edited 5 months ago) (2 children)

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)?

1
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
 

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

  2. 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.

[–] [email protected] 0 points 5 months ago (2 children)

You shouldn't criticise someone because they were late to a discussion.

[–] [email protected] 2 points 6 months ago (1 children)

Can you elaborate?

view more: next ›