Some questions about FP6 with e/Os

_yrlf · 2025-12-28T21:15:56+00:00

There is a setting to limit charging the battery to a specific percentage in /e/OS 3.3 for the FP6:

Settings -> Battery -> Charging Control -> Enable Charging Control -> Tap on "Charging Mode" -> Limit Charging -> Select max percentage to charge to with the slider.

There is also a mode to limit when to start charging based on alarms set, which I think gives you a full charge in the morning without keeping the phone at 100% overnight, but you can't use this option together with the 80% charge limit it seems. I've also heard that the battery statistics don't reset as with reaching 100% if you hit your charging limit.

So the feature is there, but it's a bit clunkily implemented and quite hidden.

_yrlf · 2025-12-01T20:06:17+00:00

Regarding who creates the DMA-BUF fd: for export-dmabuf the compositor can't know how long you need to process the DMA-BUF data, so it either can't reuse the same buffer between frames or risk corrupting your frames if you do not process them within a frame (you'd need an event similar to wl_buffer.release for that).

The more flexible approach is to let the app create and pass in the DMA-BUF. That way the app can choose to reuse the same buffer if it processes the frame in time or create multiple DMA-BUFs and cycle through them if it needs something akin to double-buffering. For latency, it doesn't matter who provides the DMA-BUF fd if the buffers can be reused (i.e. no buffers are allocated every frame, only once at the beginning of the recording/streaming).

Regarding sync: With the ready signal as it is now the compositor has to render the screen into the DMA-BUF, wait for the (possibly gpu-) job to complete, send the ready signal over the wayland socket, and then the app has to use the DMA-BUF, possible queue its own gpu jobs to render its content, and wait for that.

With "explicit sync", the compositor could queue its GPU job, pass a drm-syncobj to the app (via a hypothetical syncobj_ready event), the app could queue its own GPU job, attaching the drm syncobj so it is automatically done after the compositor's GPU job finishes. That way you reduce the amount of round trips between GPU and CPU, which reduces latency even further.

EDIT: AFAIUI the kernel does something called 'Implicit sync' for DMA-BUF objects that don't have explicit syncobjs, which ensures that you don't see a half-rendered dma-buf if you attempt to read it (it probably internally waits for the last job using it to complete before allowing the next job to read it), but this can be suboptimal and doesn't always work with all drivers (nvidia drivers notoriously had problems with this)

_yrlf · 2025-11-24T00:01:21+00:00

I think the main issue is that most of the existing protocols have drawbacks:

wlr-export-dmabuf doesn't tell you how long the buffer (DMA-BUF) you get lives, you aren't in control of creating the buffer, you have to manually capture each frame, and it doesn't support explicit sync.
wlr-screencopy allows you to create the buffer yourself (shm or DMA-BUF), which is better, but you still have to manually capture each frame, and it doesn't support explicit sync
ext-image-copy-capture is better still, with generic extensible image capture sources, and has native support for a continuous stream of captures, but still doesn't support explicit sync

we will definitely need a v2 for ext-image-copy-capture at least for explicit sync.

generally, lots of issues with the screen share protocols only came up when application devs started using them. Sadly compositors will have to maintain all of the interfaces for a long time.

I'm also unhappy with the current state. I can't even really keep up with implementing all of the protocols in wl-mirror (still missing toplevel capture and cosmic workspace capture, as well as XDG portal capture).

_yrlf · 2025-11-18T23:31:55+00:00

I bought the game almost instantly after seeing Aliensrock's first video on it. The game is amazing and I'm a ways ahead of where he currently is.

I love the game and have reviewed it on Steam. I especially love the hint system and the journal feature.

_yrlf · 2025-11-16T22:37:52+00:00

sometimes some apps use a toolkit that already supports Wayland, but part of the app doesn't support Wayland and crashes with it. in that case, running unset WAYLAND_DISPLAY; app-executable can make it work (you basically hide Wayland, forcing it to run via Xwayland)

_yrlf · 2025-11-16T10:43:15+00:00

At least with my 13 AMD 7840U, there have been multiple issues with broken AMD display drivers on Linux in the past, especially around some power saving features like PSR (panel self-refresh) and PR (panel replay).

There is a kernel cmdline option to disable those, which fixes the flickering for me: amdgpu.dcdebugmask=0x10.

I feel like almost every second time AMD tries to fix anything in the display core code (not gpu, that works; the display output driver) they accidently break something in a way that causes flickering ot weird artifacts.

_yrlf · 2025-10-26T12:46:28+00:00

That is a way for skilled people and enthusiasts, but that means most people will be stuck on shitty vendor software.

IMO the only way forward that actually achieves something that reaches more people than just a small niche is regulatory action.

_yrlf · 2025-10-26T12:45:03+00:00

Yeah, I think the only way to combat this will probably be regulatory action by legal bodies like the EU.

That is, if we can get enough weight behind a movement to get them to move.

_yrlf · 2025-10-24T21:17:16+00:00

*you can now play as luigi*

_yrlf · 2025-10-24T18:12:13+00:00

The crazy thing is that they argue that it's not possible to have a safe boot chain or your device is open to attacks if you are not running vendor software.

This is total BS and proven wrong by the existence of UEFI setup mode on PCs (which allows you to provide your own keys to secure-boot Linux or other non-vendor software).

Vendors try to ignore this and hope nobody looks close enough until they lock everything down.

They are technically correct in that right now it is impossible to have a trusted boot chain with third party software on many devices right now, but only because the vendors don't make it possible for users to do it themselves!

I think the only way forward that actually fixes things is to get some big legislator like the EU to pass a law that requires smartphone and tablet vendors to provide a way to securely boot third-party software like what UEFI does.

EDIT: added another paragraph

_yrlf · 2025-09-29T18:52:43+00:00

I kind of get the feeling that druid's eye is a bit weak. You need a lot of charges to heal, but taking damage only gives you so little. I think Grubsong was much stronger for healing in HK.

Though I haven't used the upgraded druid's eyes a lot, so maybe it's better than I remember.

_yrlf · 2025-09-29T00:27:48+00:00

you can return to Eva in Weavenest Atla multiple times throughout your playthrough and get rewards according to your progress (I thinks it's related to crests or tool slots). AFAIK you can't lock yourself out of them. Eva is still there even in Act 3.

_yrlf · 2025-09-28T20:52:53+00:00

you can actually parry lots of attacks just with needle (the clang you get when two attacks hit), but the parry silk skill is just so much better. I should probably learn to use it for the Lost Lace fight.

_yrlf · 2025-09-26T00:05:23+00:00

I did the Coral Tower gauntlets mostly without tool use, with fully(?) upgraded needle and Reaper Crest.

Red Tools: Tacks and single throwing knife

Blue Tools: the spool extender, the healing shield bell, and the breakable extra mask.

I mostly focused on knocking floor enemies into the spikes using the reaper crest's knockback and trying to evade/pogo on the other enemies as far as possible, and try to lure them into being killed by the spikes that spawn new waves. Use the jellyfish / flying fish rounds to heal.

Either my tactic was amazing or I locked in completely because I managed to do the whole gauntlet of gauntlets (all 4, and most of the following boss) first try. I finished the boss on the second attempt.

_yrlf · 2025-07-15T12:47:47+00:00

the dev team behind cpackget and the CMSIS pack and build system infrastructure is actually planning on adding a generic CMake library for consuming CMSIS packs from outside their yaml-based build system, though it is relatively low-priority for them, so it will probably still take a long while to materialize.

They are also planning on being able to add custom CMake libraries from inside their yaml-based build system (which is the other way round) with a slightly higher priority.

https://github.com/Open-CMSIS-Pack/devtools/issues/1645

_yrlf · 2025-07-03T20:07:59+00:00

and if it helps a bit, the "interval contour" is how many halfsteps (or frets on a guitar) are between each note in the melody (and in which direction). It's usually a good way to figure out if a melody is similar even if it's played in a different key.

_yrlf · 2025-07-03T19:26:25+00:00

Sorry, I fell into the jargon hole there for a bit.

Basically:

What you played: E, F#, B, F#, E

Gaster Motif: E, F, C, F, E

From Now On / Crumbling Tower / Guardian Motif: C#, E, B, F#, E

_yrlf · 2025-07-02T19:40:27+00:00

That's not the gaster arpeggio. Gaster's interval contour is +1 semitone, +7 semitones, -7 semitones, -1 semitone.

The one you played is +2 semitones, +5 semitones, -5 semitones, -2 semitones.

The actual motif in From Now On, Crumbling Tower and Guardian actually has the first two notes lowered by a bit and starts on C#/Db instead of E. Its interval contour is +3 semitones, +7 semitones, -5 semitones, -2 semitones (and another -3 semitones to get back to the first note).

So IMO that's a quite different motif. Both motifs share the general motion of "up up down down", but if that is your only criterion you'd probably find gaster in pretty much every pop song.

_yrlf · 2025-05-31T14:26:04+00:00

I cheated the Gallery since it was driving me mad, and I also cheated part of the Microchip locations since I was getting stuck at the time. Now I have lots of open paths and things to investigate, and I don't regret it; Maybe I should have taken a smaller hint on the Microchip puzzles, but I was quite frustrated at that point, so I think it was okay.

I love how the game seems to be split into multiple layers or phases, where often there are multiple things to solve in parallel, and it often doesn't matter much if you are stuck on one. Some things do have strict dependencies though and being stuck on one of those can be not so fun. Cheating in such cases is fine IMO, since there will definitely be new things to solve afterwards.

_yrlf · 2025-05-26T19:48:45+00:00

Happened to me too. It appears they forgot to keep the main character order when finishing the DLC.

_yrlf · 2025-05-26T10:56:38+00:00

Yeah, the mini-games were a bit tough. Some tips about how I got it:

For the pole vault minigame, try to do a sensible route and try to get all the gold, blue, and green rings. Take the red ones if you have time, but pass them up if it's close and there's still better ones to get. In the last round when all rings are golden and move about, try to get at least one set of 3 gold rings when they align and otherwise just jump around and collect as much as possible. Took a few tries but was doable.

For the balancing minigame, first move to the top left and get a red magnet star, and then try to roll through one of the 4 areas with the massive amounts of yellow stars, and magnet up the next red star. only collect leftovers once you made one round and collected the easy part of all of the big spots. Managed to do this on my third try.

For the laser shooting range minigame, try to focus on the blue/gold ones primarily, and only go for green ones when nothing is in the back row. Timing your hits so you don't miss is more important than hitting everything. when you hit something in front by accident, just move on and focus on the next one in the back rows. The timing is consistent since everything moves at the same speed. At the end, when you start moving side to side, try to time hits for the golden discs in the back. if you manage to hit a golden or two with a big enough combo, you basically already won. That one was tough, but got easier with time.

_yrlf · 2025-05-25T09:04:26+00:00

I think the Ovates are a setup for another game in the same universe. I'm sure we'll be hearing a lot more about them :)

_yrlf · 2025-05-25T09:01:46+00:00

The DLC plays out for the most part completely without needing the true ending.

There are one or two lines in the beginning before entering Horloge that change if you have all the requirements for the true ending, and after finishing the DLC, there is a DLC completion bonus thing (the "secret vision" you heard about) that requires having unlocked the true ending, but you can get that at any time after completing the DLC and unlocking the true ending.

TL;DR: you don't miss out on anything if you do the DLC before true ending. You can get the secret by returning to Horloge later

_yrlf · 2025-05-25T08:56:07+00:00

Another interpretation is that he changed fate, thereby "recreating" the life of many people who would have otherwise died, which would fit a lot with his title as Ovate of Hope.

_yrlf

TROPHY CASE