I’m experiencing several issues using iodeos on my Pixel 9.
1. Conditions: my earplugs are connected to the phone via Bluetooth (listening to music), and I receive an incoming call. When I accept the sound comes via the phone speaker (not via connected earplugs). However, the phone app (the default one, as well as Fossify, which I mainly use) shows that the audio route is Bluetooth. Switching the audio route doesn’t change anything. After the call ends, it seems like the Bluetooth service is stuck. I think so because when I adjust the volume, there’s a delay of about 2 seconds between pressing the button and the phone reacting. Also, changing the volume level doesn’t change the actual volume (the slider position changes, but the volume doesn’t change). Furthermore, if I go to the Bluetooth settings, it says the settings are not responding. After a reboot, the problem goes away. It then happens again with next incoming call. If I make an outgoing call, the problem doesn’t occur.
2. If “Allow USB connections when unlocked” is selected in the “USB Restrictions” settings, I’m having trouble connecting my phone to PC. After restarting the phone, I can connect it via USB and select "Use USB for” (file transfer, USB tethering, etc.). However, if I disconnect the phone from the PC and reconnect it, I only have a few seconds to select the connection type (file transfer, USB tethering, etc.); otherwise, the list (file transfer, USB tethering, etc.) becomes grayed out, making it impossible to select. When I manage to select the desired connection option (file transfer, USB tethering, etc.) within a few seconds, the phone prompts me to verify my identity, and as long as the device is connected to the computer, I can change this selection. But when I reconnect, the same thing happens again.
Re bluetooth issues: what bluetooth device, and is it the same with others?
I have Huawei freebuds pro 3 as earplugs. Also I have Huawei watch GH4 connected via bluetooth at the same time. The watch can receive incoming calls (a call notification appears, and audio can be routed via it)
I’ve just got an idea there might be a conflict between two Bluetooth devices which should be used to rout the sound.
I tested the phone without the watch. Simply disconnecting the watch also stuck Bluetooth. But after reboot (if prevent the watch from connecting to the device) audio root works normal. I can hear through the earplugs and select another audio root option without any problems.
So it seems that there’s a conflict between the two Bluetooth devices. But the stock firmware didn’t have this issue.
Re “allow USB connections when unlocked” issues, is all working as expected when the standard “Always allow USB connections” is used instead?
If use standard option “Always allow USB connections” usb connection works fine. Issue only with “allow USB connections when unlocked“ option.
There’s another minor software bug. If enable “charging control” and set up charging mode to “limit charging to a certain percentage”, the text “Charging on hold to protect battery” appears on the lock screen while charging. This text appears even though the battery doesn’t reach the set limit. However, the charging process itself continues, and it is just a text error.
Is there any Huawei app needed for the devices that you don’t have installed? Also some broader searching on “LineageOS” or “microG” plus your device names may find some discussions on the issue, but it is a bit of a challenge for us to debug without the devices in hand as you may guess.
I didn’t check the LineageOS issue tracker if this is a known problem, but do note that even if you have the “Always allow” option you still need to manually switch it from “charging only” to “file transfer” for example, and this can only be done unlocked. So it is isn’t a security risk to have it at this default at least as I understand.
I’ll let you do a bit more digging (maybe better search terms on their issues or instead check their subreddit), but if you don’t find something I can then make an issue on our gitlab but I do assume this problem is at the LineageOS issue and is probably beyond our normal scope, meaning it may be some time before they could look at it.