It almost certainly is designed to run indefinitely, this exact same coffee maker has been in production since the nineties or so. the only addition is the timer circuit, which is very clearly a much later addition, as the supporting structure is markedly different tk the rest of the device.

Anyway, a 240v switch is in order, I think. Fortunately we still have Farnell here in the UK, I shouldn’t like to pay international shipping fees for a single switch from china.

ah, I should have cottoned on in my first reply. the reason it switches off is EU regulation, not for any safety reasons. The machine otherwise looks exactly the same as any kther coffee maker in the world.

The fire hazard is no greater for removing the timer, there’s a bimetallic strip in there that will detach from circuit if the thing gets over 90ish degrees. It’ll just keep cycling like that. Microwaving coffee tastes, in my opinion, worse.

I habitually use a clean install whenever I move OS - so much so that I’ve been buying new storage drives for the sake thereof. I actually have one ready to go for Trixie, once I finish a current project.

Hmm. Git is far too organised for my play style. I may take photographs at some point, assuming I can actually find components (and learn how to do… well, any of this).

After a night’s thought, this might be an interesting idea. Although I’d need to figure out how to add a programmable interface to it.

Neither. This is a purely personal project, and I’m using as much off-the-shelf as possible. The dac itself doesn’t have to be top of the line, just decent. The PCB itself I’ll probably just have printed, rather than trying to breadboard it or make some ungodly wire mess.

Some stuff I can get for almost pennies, like a USB-C controller and the actual sockets and plugs, so this is a non-concern. The actual dac chip though, I’m expecting (or at least hoping) to find something around the £30-£40 mark, although this may well be aspirational. That said, this is something I can theoretically transplant to my next device, and the next after that, assuming I create custom housings for them.

I’ve put some thought into it, but realistically I lack the experience to flesh out the idea.

I’ve seen a few small DAC concepts out there, like https://www.elektroda.com/rtvforum/topic4091483.html or that iPhone modification that Strange Parts did a few years ago, but none of these really 100% match my needs. As for the sizing, the only real answer I have for you is “small” - whilst it is intended for integration into a phone, I’m going to be building a housing for that phone from scratch, so the size requirements are somewhat led by the dac itself. I had a few ideas about using a flexi-strip in place of a solid PCB too, but I think that’s aiming too high for my non-existent skillset. Instead, I have no problem redesigning the board to be long and thin if necessary, or squat and fat in the alternate. Realistically, it’s probably going to be somewhat L-shaped, but there’s a good two inches or more of width and something like six inches of height to work with - minus the PCB of the phone, that is.

The actual handset it will be accompanying is a Sony Xperia 1 IV, but that’s largely meaningless as we can add pretty much any additional size to it up to a reasonably large handset within the last ten years (preferably with an OLED display, but I’ll be somewhat limited in terms of compatibility anyway and might have to end up running the screen in an alternate fashion somehow, I haven’t thought too hard about that side of things because the project is useless if I can’t design a DAC inthe first place).

The heatsink stuff was really just a suggestion, I’m not actually sure if it will be necessary, but it’s good to have the option.

Specifications wise, it essentially needs to do four things:

• Pass any connected headset microphone through to the handset
• Run an EQ that is addressable and configurable from the handset
• Have a volume ceiling at least comparable to a fifth-gen iPod video (i.e. a wolfson chip)
• Take power from, and pass data and power through to, the existing USB-C socket on the handset.

The bit that I’m stuck on, really, is the addressable EQ. I could possibly go with some sort of Arduino-esque solution, but that’s a lot of lifting for a single-purpose device. I have no idea where else to start looking - I know there are RISC chips out there that run on nothing but a button cell, but again I’m clueless as to whether or not this is a good idea.

I’ve looked at these, but they lack the integrated amplifier (afaik) and the configurable equaliser. Those are two super important features that pretty much break the idea for me.

Can we get that udev rule? Or at least a rough idea how to put it together? I had to put a windows box up just to get this phone talking to a pc

I get the feeling that it would be more feasible to build a separate kernel at this point. Its a lot of work, but adding another option to the comparatively small array of kernel options that we have might actually be a good idea -and in doing so, it word demonstrate r4l’s willingness to maintain the project long-term. There’s no need for this pissy behaviour, and there’s no need to take the drama to social media.

I have an SFF PC currently running Mint, with Bello and steam as well as xemu and a few other goodies. The flexibility is great, if something is a bit borked I can usually just play it in VLC, and the compute allows me to run pretty much any emulator besides Xenia or that PS3 one. Once I plug a GPU into it, those should be fine too. Not bad for a cheap i5 system.

Holy shit this looks practically perfect. Thanks!