My drip maker shuts off. This is very frustrating, since no human should attempt the consumption of six cups of coffee within thirty minutes.

I'd like to get rid of this timer, but I can't see anything obvious on the board. Is it most likely to be in that little processor at the top left of the coated side?

lmao some of these replies are exactly the sort of thing you'd expect from reddit in like, 2011. For reference, even mildly scalded coffee tastes better than that instant shite, and I'm not drinking ut for taste.

As much as I want to support the idea of a well supported, modernised graphical protocol system, wayland simply isn't ready yet. There's so much shit that simply doesn't work, and they're all made up of little niche cases that will take substantially longer than a few months to resolve, and I still haven't seen anything that suggests Wayland has a practical equivalent to xorg.conf.

Is Alma Linux rolling their own version of Plasma with x11? Or are they just sticking with an older version of Plasma? Is anyone else planning on hacking x11 back into the DE?

edit: To the people leaping down my throat, the last time I tried wayland was around five months ago. I have a substantial list of thi gs noted down somewhere that I was considering trting to work around or fix. off the top of my head:

• remote desktop is a fucking pain. remmina would not allow a multiple monitor remote session at all, and a single monitor session was frequently unstable. What I really wanted was something simple that I could start from a bash script, like XFreeRDP.

• nvidia drivers were spotty at best. I'm not too fussed about them being proprietary, but they never seemed to quite function properly. I have a 1660ti.

• applications in general felt sluggish

• it was hit/miss when attempting to disable desktop composition. sometimes it would cease, sometimes it would not. for skme full-screen applications, I require this as desktop composition can make input responses fairly latent. Trying to type out a class is unpleasant and somewhat halting when it takes 200ms for a character to appear after it is typed.

• lack of a pre-init config option. I currently use a xorgconf to set screen position, layout, and resolution (including a virtual resolution) before any graphical environment starts. this stops my vertical monjtor being displayed sideways before I log in. I have yet to see something similar for wayland, but this feels like it should exist - please prove me wrong.

• screen tearing. although the environment claims to be running my monitors at 60hz, a 60fps test sample revealed they were actually being driven at 50hz. thjs is not a hardware limitation, as all my monitors currently drive at 60hz.

• application and desktop sharing. this flat out didn't work. I'm told it should work, but it doesn't.

here's the thing. I'm not arguing against the inclusion of wayland. I'm very pleased that we have new options. I'm arguing that we should have the choice to choose the most suitable option for some time yet. I like Plasma a lot h despite it being horribly bloated, unnecessarily complex, and somehow oddly lacking in some basic features whilst simultaneously having some fantastic built-ins such as window rules.

so no, this isn't a "self report" as one profoundly inciteful respondent put it. this is me looking for any possible solution that will allow me to run a modern DE whilst retaining features that I require.

I originally signed up to mastodonapp.uk. Now that I'm attempting to get m.dollha.us running, I'm looking to pull my account from the former and move it to the latter. Easier said than done, though, because I cannot, for the life of me, seem to get my instance to federate with that instance. I have tried leaving it for a week or three, I have tried starting it in limited federation mode and whitelisting the instance in question, and I have tried a dedicated relay provided by fedi.buzz.

Today I noticed something interesting in my sidekiq logs: My instance is actively rejecting mastodonapp.uk - despite it not being in any blocklists. This is, of course, via the dedicated relay, so it could be a relay issue, but I can see no obvious reason why that would occur.

What could be the problem here?

Given the endless problems with attempting to properly initialise ALSA with the qualcomm chipset in my device, I've resorted to the idea that I'll be designing a larger case, with a larger screen (and hopefully no shitty curvy corners) and an integrated DAC with probably a small headphone amplifier.

Ideally, I would like this to be addressable, and have the facility to run an equaliser on-board that can be configured via the USB connection, although I'll settle for bluetooth if the former is too complicated. It will also need to fit inside the phone housing (which will likely be around 9-10mm). I plan on an aluminium frame, so heatsink facilities should be easily manageable. The USB connection will, of course, need to be a passthrough connection to facilitate charging the phone - having a separate USB-C socket on the board is fine, I can probably adjust for this.

Am I setting my aspirations too high, or are there components available that meet these specifications?

With the new changes to reddit's UI, and their insistence on age verification, I have elected to leave that platform. This includes my moderation of the /r/NewcastleUponTyne subreddit, for which I have recruited a couple of other moderators to replace me.

This sub...lemmy(?) doesn't get much traffic, but what little traffic it may get in the future will be treated with the same deference as mine and $otherMod's approach to the content over on the subreddit. I'm still in contact with that moderation team should there be any cross-platform high jinks.

At a later date, I may bring over the automoderator implementation I was building for the subreddit. The changes need not be overly complex, although in fairness it was never really finished. At present, there's little to no need for it - the vast majority of posts here have been mine, although I hope that might change in the near future.

I'm attempting to alter the XNext walkman Magisk module for the Xperia 1 IV. I've gotten to the stage of modifying the existing asound.conf, but I'm struggling to find the right controls on the device to play media through.

In this case, I have a config that defines audio in/out devices (resourcemanagr_waipio_qrd.xml), and from this I have extracted the following out-device: https://paste.debian.net/1394516/

From this, I have noted the corresponding hw device from aplay -l: CODEC_DMA-LPAIF_RXTX-RX-0 multicodec-0

I'm lost, however, as to how I might determine how to address this in asound.conf - which contains the module as follows: https://paste.debian.net/1394517/

where the first and last name elements appear to be the name of the device. I have attempted the following values:

CODEC_DMA-LPAIF_RXTX-RX-0 multicodec-0
CODEC_DMA-LPAIF_RXTX-RX-0
CODEC_DMA-LPAIF_RXTX-RX-0 Audio Mixer Multimedia1

The last being a vague hope that there are somehow some additional configuration flags necessary. However, each time I attempt aplay -v -D headset test.wav, aplay responds that the device cannot be found. headset is slaved indirectly to pcm.headphone, and aplay does contain the correct device name according to asound.conf, so instead I must have the wrong device - except it's configured as such in all the resource config files. So what am I doing wrong, and how might I find the correct combination of bits and pieces?

Here is the full resourcemanager_waipio_qrd.xml: https://paste.debian.net/1394821/

Output of aplay -l on the device: https://paste.debian.net/1394822/

asound.conf as it currently stands: https://paste.debian.net/1394823/

Update! I have discovered that the DMA control is now obfuscated on this generation of audio card. Instead, I am supposed to turn on and off the dac switch. As a result, I have come up with the following:

{
					name 'HPHL_RDAC Switch'
					preserve false
					lock false
					value [ 0 ]
				}
				{
					name 'HPHR_RDAC Switch'
					preserve false
					lock false
					value [ 0 ]
				}
				{ name 'RX_MACRO RX0 MUX' value AIF1_PB }
			    { name 'RX_MACRO RX1 MUX' value AIF1_PB }
			    { name 'RX INT0_1 MIX1 INP0' value RX0 }
			    { name 'RX INT1_1 MIX1 INP0' value RX1 }
			    { name 'RX INT0 DEM MUX' value CLSH_DSM_OUT }
			    { name 'RX INT1 DEM MUX' value CLSH_DSM_OUT }
			    { name 'RX_COMP1 Switch' value 1 }
			    { name 'RX_COMP2 Switch' value 1 }
			    { name 'HPHL_RDAC Switch' value 1 }
			    { name 'HPHR_RDAC Switch' value 1 }
			    { name 'RX_RX0 Digital Volume' value 84 }
			    { name 'RX_RX1 Digital Volume' value 84 }
				{
					name 'HPHL_RDAC Switch'
					preserve true
					lock true
					value [ 1 ]
				}
				{
					name 'HPHR_RDAC Switch'
					preserve true
					lock true
					value [ 1 ]
				}

Now aplay -v -D headset test.wav returns the following:

ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
ALSA lib confmisc.c:136:(snd_config_get_bool) Invalid type for value
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1436: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (10666 10667)
PERIOD_SIZE: (470 471)
PERIOD_BYTES: (1880 1884)
PERIODS: (15 17)
BUFFER_TIME: (170657 170658)
BUFFER_SIZE: 7526
BUFFER_BYTES: 30104
TICK_TIME: 0

I'm not quite sure if this is because I actually have the incorrect values, or if I just have the wrong components. They certainly match the contents of my mixer paths...

I've just bought a new-to-me Xperia 10 V. It took me a while, but I managed to root the device, forcibly remove the bloat I didn't want, and apply some system tweaks.

There are two things that persist in frustrating me. First, I cannot shift the clock back over to the right. Shizuku & System UI Tuner appear to have no effect on this, and until I can compile a copy of LineageOS, I appear to be stuck with it in the wrong place.

The second is a little more egregious, and that's this new lockscreen/notification media control. It's horrendous. In fact, it's a step back in functionality, because the FF/RW buttons are too small to press (and sometimes don't work at all!). Yet, somehow, the notification manages to be larger than it used to be.

I'd really like to get rid of this new media notification UI, and return to the old style of media control where it was indistinguishable to other notifications bar the media controls. Short of compiling Android... 10?11? for a phone released last year, what can I do to accomplish this?

WEY AYE NEWCASTLE, I have updated the print with some of the fabulous comments from last night and today, I really appreciate your time and help with this.I feel so many of you have contributed towards this. But this is the final print now. Cheers Paul.

I'm currently using a VM to run Visual Studio on Fedora. Because I want easy access to both systems at once, without having to minimise a VM or use hotkeys to access the host system, I require a VM solution that has "seamless" integration - I.E hiding the virtual desktop, and running applications in the VM as though they were running natively.

Virtualbox has this solution, but it is somewhat unreliable and doesn't maintain seamless mode (or multi-monitor mode) between boots. VMWare has a feature called "Unity mode", which seems to be a little more reliable - however, unity mode has not been a VMware Linux feature since v7 - we are now somewhere around v17.

I'm using v7 at the moment, but I'd like to find something that won't fall over at some point in the future. RemoteApp isn't a solution, because VS needs to be able to launch a browser and communicate with it during debugging. What other VM solutions have this "seamless" functionality?