oh, btw, theres an existing systemd service I use on Arch and Debian to manage this nowadays, might be worth examining if it already works for the most part and forking that if necessary.

@Keneda Btw, i have a fp4, and have found that installing over the Android 13 rom from fp works without issues, though it does seem that I need to disable ipv6 in the kernel tunables to get things like waydroid to work correctly, but I'm not sure if thats related.

After messing with it for a good while, I was actually able to get it working with 5G/4G on the T-Mobile network by flashing the Android 13 stock image, then using the UBports installer. Note: it did seem to have some issues entering the fastboot mode, so that took some finagling.

Also, it didn't seem to like it the first install, and I think I flashed Android 15 before Android 13, THEN installed Ubuntu Touch. But mileage may vary, obviously.

Now to run some documentation of all loaded kernel modules and firmware versions from dmesg, and potentially try to debug why sound doesn't work on PostMarketOS, enough eyes, every bug is shallow, etc, as I'd prefer Plasma Mobile over Loromi. (Lorimi?) [But any FOSS system over Android, so I'm happier than I'd be without Ubuntu Touch]

@gpatel-fr yeah, that site is absurd.

All I'm saying is that a mere 30W at 4.2V puts us far over the 6A point anyway, and since the battery is what puts a specific amperage load on the BMC, the only "lever" we can even have in the first place is actually the voltage being used to charge the battery.

While we may be able to control the battery charge rate and therefore amperage that its pulling, the BMC can only actually do so by changing its output voltage.

Basically, while we might be putting an amperage in somewhere in the sysfs, even if that is somehow being sent to the BMC, at some point that has to be getting calculated into a voltage to achieve the desired charge rate, and no matter what, when android is charging the battery, we already know its exceeding the 6A value in that code when the battery is low.

Something doesn't add (or rather multiply) up with the nunbers, that's all I'm saying.

@RandomUser probably important to include the specific version of UT you're using. I think Focal is no longer supported

@gpatel-fr Is that code specifically referring to input from the wall, or output to the battery amperage? My understanding is that at 30W charging, at a nominal voltage of 4.2 V, we're already looking at over 7A.

And 30W is just fully supported by FP natively. Also note that the input voltage at 30W is probably 9V or 12V, bringing the actual amperage down on the input side. Why, I have a 120V USB PD charger that doesn't go over 5A because it just ramps up the voltage.

I suspect that the "6A" unit in the kernel may be a pseudo unit that the BMC takes, pretending that the actual output voltage to the battery is always 5V, meaning it's actually describing wattage, specifically the natively supported 30W charging.

@Keneda Btw, i have a fp4, and have found that installing over the Android 13 rom from fp works without issues, though it does seem that I need to disable ipv6 in the kernel tunables to get things like waydroid to work correctly, but I'm not sure if thats related.

oh, btw, theres an existing systemd service I use on Arch and Debian to manage this nowadays, might be worth examining if it already works for the most part and forking that if necessary.

@ChromiumOS-Guy I'm pretty sure it is, I think that it might even vary more by kernel version than device, meaning that you may want to switch on kernel version before device information, if you even need to check different locations. I would expect devices like the PinePhone to possibly be quite different since they don't use Hallium, iirc, but even thats a guess based on my experiences with the sysfs on various laptops.

I believe the kernel docs specify where to look generally, so 4.19 kernels should be (somewhat) consistent. (however most of my knowledge is based on the 6.1, 6.6, and 6.12 LTS kernels, take my recollections with a grain of salt)

That said, this is if you're accessing this sort of stuff through the sysfs, instead of using direct system calls, that may be rather different for all I know.

Interesting, this general approach should work (at least extremely similar if not exactly the same) on most devices, as this is very close to how I manage charge level on Arch on my thinkpad laptop. The exact sysfs path is different, (it's got BAT0 in there somewhere, iirc), but the fact that it's THAT close between an AMD64 machine and the fairphone means it may be scriptable to search and locate the appropriate sysfs files on multiple devices.

This sounds like something that could be integrated into the Lorimi settings UI pretty easily as well, i'll have to see about trying to write a patch for that, get my hands dirty etc.

After messing with it for a good while, I was actually able to get it working with 5G/4G on the T-Mobile network by flashing the Android 13 stock image, then using the UBports installer. Note: it did seem to have some issues entering the fastboot mode, so that took some finagling.

Also, it didn't seem to like it the first install, and I think I flashed Android 15 before Android 13, THEN installed Ubuntu Touch. But mileage may vary, obviously.

Now to run some documentation of all loaded kernel modules and firmware versions from dmesg, and potentially try to debug why sound doesn't work on PostMarketOS, enough eyes, every bug is shallow, etc, as I'd prefer Plasma Mobile over Loromi. (Lorimi?) [But any FOSS system over Android, so I'm happier than I'd be without Ubuntu Touch]

@MrT10001 So, it's not fixable at all, and I need to give up and throw away the phone, or I can fix it and there's a way to do it?

I'm able to get 5G on the stock Android 13 and Android 15 from Fairphone without an issue, but if I install the stock Android 11 from Fairphone, I lose 5G and I'm stuck on Edge service (at best).

Installing Android 15 to check if this is a version issue, I'm guessing with the modem firmware, I find that 5G works just fine, and installing the Android 13 stock firmware works fine, as does LineageOS.

Is there any way to identify the exact cause, and resolve it, potentially by using the firmware .bin file from a newer Android OS version, (or however exactly it works)?