This post was apparently posted at 11:08 GMT+2, which is almost two hours in the future from now.

This is obviously a bug, but is it a frontend or a backend issue?

Two years ago, a feature was added to Android 12 where the previous audio source would fade out when a different source starts playing (e.g. you start a YouTube video while music is playing).

A post was made on XDA on 18 May, 2021:

Audio focus is determined by the app in question that's playing media. Google explained that when an app requests audio focus while another app has the focus and is playing, the framework forces the playing app to fade out. This will be a nice change because instead of another app abruptly ending its audio stream whenever the user starts another session, Android 12 will nicely fade out the old stream that's lost focus.

I remember being very impressed with this feature and found it satisfying every time. However, after buying a Samsung Galaxy A24 running Android 13, I was disappointed to discover that this feature is missing.

This is yet another reason why I can't wait to install a custom ROM on this phone. For now, though, I guess I'll just have to wait.

Some research I've done suggests that a small idling engine should consume about 0.2 - 0.3 gal/h, which is about 0.8 - 1.1 L/h. However, the following calculations I've done are off by a mile.

At idle, engines typically operate in a rich-running condition, which implies a best-case air-fuel ratio of roughly 14.7:1 (i.e. 1 L~fuel~ / 14.7 L~air~).

According to this article, engines typically have a volumetric efficiency of 15% at idle. This means the volume of fresh air drawn into each cylinder is about 15% of the cylinder's volume.

A 4-stroke engine sucks air into all cylinders in two revolutions.

Using this information, I've calculated the idle fuel consumption for a 1.1L engine at 800 RPM as follows:

rate = (800 rev / min) * (15% * 1.1 L~air~ / 2 rev) * (1 L~fuel~ / 14.7 L~air~)

This comes out to roughly 4.5 L~fuel~ / min, or 269 L~fuel~ / h. What gives?

User jAm-0 has issues getting into and out of his phone's bootloader. He attributes this to the bootloader being corrupt and wants to replace it.

User return.of.octobot provides instructions to allow reflashing the bootloader. One of the steps is to run fastboot flashing unlock_critical, which allows the bootloader to be overwritten.

Overwriting the bootloader is the only way to hard brick most devices, and fastboot flashing unlock_critical tells Android you don't care and are willing to take the risk. Hard bricking makes a device unfixable on the software level.

jAm-0 has another question and receives responses from return.of.octobot and another user, nrage23. Again, no disclaimers are given and the word "brick" isn't even brought up.

jAm-0 hard bricks their phone.

Sensor 1	Sensor 2
Oscillates between 0.1 V and 0.75 V	Stays at 0.45 V

1.1L I4 petrol engine
Measurements taken about six minutes after starting

There was a fault code for sensor 2 that I cleared about 3 000 km ago, but it hasn't come back since. There was never a CEL

Think about it: Lemmy provides you with a ready-made frontend and backend

all you have to do is host your own instance of it. The following could all have been implemented as Lemmy instances, had it existed at the time:

• Reddit (www.reddit.com)
• Quora (www.quora.com)
• Stack Exchange (stackexchange.com)
• 4chan (www.4chan.org)
• Disqus (disqus.com)
• Hacker News (news.ycombinator.com)
• Something Awful (forums.somethingawful.com)
• GameFAQs (www.gamefaqs.com)
• Bodybuilding.com Forum (forum.bodybuilding.com)
• Gaia Online (www.gaiaonline.com)
• IGN Boards (www.ign.com/boards)
• NeoGAF (www.neogaf.com)
• MacRumors Forums (forums.macrumors.com)
• Digital Spy Forums (forums.digitalspy.com)
• WebmasterWorld (www.webmasterworld.com)
• AVForums (www.avforums.com)
• DeviantArt Forum (forum.deviantart.com)
• XDA Developers Forum (forum.xda-developers.com)
• WordPress Support Forums (wordpress.org/support)
• The Student Room (www.thestudentroom.co.uk)

Of course, these all have very different rules and frontends, but those can still be changed.

In addition, members of other instances can visit these forums without having to create new accounts, thanks to everything being federated.

Isn't that cool?

TL;DR How can I equalize my car speakers using an equalizer app like ViPER4Android on my phone?

I just equalized my headphones on my phone using ViPER4Android's convolver feature and a headphone-specific .wav file I got from AutoEq, and it sounds great. Unfortunately, AutoEQ only seems to support a limited range of sound devices, which does not include car sound systems.

I'm not an audiophile, but even I can tell that my car's system's frequency response is terrible, specifically in the low end, where there are specific frequencies that resonate through the car (especially noticeable when the bass frequency changes in a song).

As far as I know, AutoEq's files are made by playing something over the speakers, recording it with a high quality microphone and correcting it to match some pre-determined frequency response curve called an equalizer target. I was wondering if there's a way to replicate this process using my phone's microphone (I'm not after near-perfect sound quality here, just something that sounds reasonable), and if that would be the best way of going about this.