[Bug] Flashlight control broken on Android 17 (Pixel 10 Pro) - CameraManager Empty Camera ID

[LacazeThomas]

Describe the bug

The application opens and stays responsive, but it is impossible to toggle or adjust the flashlight. The controls have no effect. The underlying logs show that CameraManager receives illegal arguments, specifically an empty camera ID, preventing the app from binding to the device's hardware.

To Reproduce

Steps to reproduce the behavior:

1. Open the FlashDim app on Android 17 (Pixel 10 Pro).
2. Attempt to toggle the flashlight or move the brightness slider.
3. Observe that nothing happens (no light turns on, but the app does not crash).

Logcat / Stacktrace

Exception occured
CameraManager received illegal arguments, probably empty camera id

[pcislocked]

Hello, I was going to open a separate issue but it seems like they're similar/related so I'll add here.

Accessibility shortcut via smashing both volume buttons is dorked on today's newest Android update. google is doing some weird api stuff probably because my home assistant is also acting up about... local network access???? idk

FlashDim:

• Version: 2.4.3 (31)
• Installer: com.android.vending
• Build: release (main-10d22b0)
  Phone:
• Manufacturer: Google
• Brand: google
• Model: Pixel 9 Pro
• Product: caiman
• Device: caiman
• Board: caiman
• ABIs: arm64-v8a
• Light levels: 21
  OS:
• Version: Android 17 (37)

[cyb3rko]

Thanks guys @LacazeThomas @pcislocked for the report. Unfortunately I can only test that when I have access to Android 17, which will take some time.

[OldManJenkins12]

Android 17 also makes each option bigger, there also used to be 22 options

FlashDim:

• Version: 2.4.3 (31)
• Installer: com.android.vending
• Build: release (main-10d22b0)
  Phone:
• Manufacturer: Google
• Brand: google
• Model: Pixel 9 Pro XL
• Product: komodo
• Device: komodo
• Board: komodo
• ABIs: arm64-v8a
• Light levels: 21
  OS:
• Version: Android 17 (37)

[OldManJenkins12]

Also, I can't prove it, but minimum brightness (which is what I always use, rarely ever go higher) feels slightly brighter

[cyb3rko]

@LacazeThomas @pcislocked @OldManJenkins12
So I installed A17 on my second device (P7), on which FlashDim fully works as expected including the number of levels shown (45) and the volume buttons shortcut.

Maybe the issue is only appearing on >P9 or something. I can try to fix it when I can test it on my P10 Pro. But because I'm running GrapheneOS, that can take some time (weeks, maybe months).

Is anybody of you willing to capture and share a stack trace of the error that is thrown?
That would help me tracing the problem without having it on my phone.

[pcislocked]

@LacazeThomas @pcislocked @OldManJenkins12
So I installed A17 on my second device (P7), on which FlashDim fully works as expected including the number of levels shown (45) and the volume buttons shortcut.

Maybe the issue is only appearing on >P9 or something. I can try to fix it when I can test it on my P10 Pro. But because I'm running GrapheneOS, that can take some time (weeks, maybe months).

Is anybody of you willing to capture and share a stack trace of the error that is thrown?
That would help me tracing the problem without having it on my phone.

don't know exactly how but can look into it tonight

also my main app also works fine for me, it's the shortcut that's broken on me

[cyb3rko]

Do you all use stock Google Android or some custom ROM?

[OldManJenkins12]

Stock, I have used adb before, so you can send the exact adb cmd that's needed

[BroJac5246]

I'm having trouble with the volume button toggle option on my Pixel 9 Pro after updating to Android 17. My guess is that the app tried setting the brightness to level 45, the old maximum, but can no longer do so and just receives an error because the new max is 21.

A couple observations:

1. Clicking on the "Preferred level" setting, which was set to 45, caused the app to crash.
2. Once I reset the app's data and set it up new, it worked perfectly as expected.

I think this error could probably be fixed by changing the logic to ensure the app never requests a greater brightness level than the device supports.

It is worth noting that if someone previously on Android 16 had the brightness set to something lower (say, 10), they will probably wind up getting a brighter result on Android 17 because 10 is ~50% of 21 but was only ~20% of 45. I can't verify this, however, because I did not have my settings set like this. It would be consistent with my other observations, though.

[carlosaya]

I'm having trouble with the volume button toggle option on my Pixel 9 Pro after updating to Android 17. My guess is that the app tried setting the brightness to level 45, the old maximum, but can no longer do so and just receives an error because the new max is 21.

A couple observations:

1. Clicking on the "Preferred level" setting, which was set to 45, caused the app to crash.
2. Once I reset the app's data and set it up new, it worked perfectly as expected.

I think this error could probably be fixed by changing the logic to ensure the app never requests a greater brightness level than the device supports.

It is worth noting that if someone previously on Android 16 had the brightness set to something lower (say, 10), they will probably wind up getting a brighter result on Android 17 because 10 is ~50% of 21 but was only ~20% of 45. I can't verify this, however, because I did not have my settings set like this. It would be consistent with my other observations, though.

So does the volume key shortcut work for you now on A17 or not? Kinda confused by your message. I've been avoiding the update until this app gets fixed since I use the vol keys all the time.

[pcislocked]

Do you all use stock Google Android or some custom ROM?

Hi, stock pixel rom, bl lock and everything

Also I'm sorry for promising it earlier but i have exams and stuff so won't be able to sit by my computer to do the debugging stuff. Still lmk if theres something i can try out.

to recap: i currently have 21 levels on my app showing up and working as the usual dimmer, only part that i notice as "broken" is the shortcut

[Gabri1495]

Hi, I am using a stock Pixel 8.
I have just received a notifications about "Advanced Protection disables accessibility apps that are not trusted".
I have checked on accessibility menù and founda that FlashDim and Automate are both disabled/off.
I think thant is the reason why teh volume key shortcut doesn't work anymore.

[pcislocked]

Hi, I am using a stock Pixel 8.
I have just received a notifications about "Advanced Protection disables accessibility apps that are not trusted".
I have checked on accessibility menù and founda that FlashDim and Automate are both disabled/off.
I think thant is the reason why teh volume key shortcut doesn't work anymore.

Hi. No. Accessibility service was still open for me when I had issues. With bit more tackling just now, I think I've found the issue.

Turning off "Volume buttons link" restores the volume button shortcut.

Another thing I've found: clicking this option crashes the app.

[carlosaya]

thanks @pcislocked ! just confirmed on my wife's Pixel 9 on A17 that disabling the toggle DOES work. Weird, but she is happy to have her volume key flashlight shortcut back!