-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assistant Button Override doesn't work on Android 13 #66
Comments
Here's what happens:
This is on a 5 III running the latest 13 OTA with both the "Assistant" and "Google" apps manually disabled. This setup worked on 11 and 12. Fingers crossed! |
I looked through the source and the trigger "GAKeyEventHandler: launchAssistGuideActivity" seems to be there, but I don't get your logcat message that it got detected. Maybe something about 13 broke reading the logs? Sorry, not an android dev :( |
Can you send this logcat unfiltered? |
Hey, thanks for your interest,
|
Hi, I have an Xperia 5 III with android 13. Using the app to remap the key to flashlight worked before reboot, now it no longer functions even if I turn the assistant button off and on again, or change the action the key should make. I'm unfamiliar with adb at all, let me know what I should type to get a good log for you if you need it. |
Yesterday I found a behavior with Xperi+ that migt give a clue why it isn't working on 13. I can't make the lockscreen shortcuts work again watever I try though, but that is not a big deal for me anyhow. Having an Xperia 1 iii I basically grow addicted to having my assistant button as a flashlight control. Ever since updating to A13 I have felt somewhat handicaped, to express myself a bit dramatic. (Adding this info just to show that I realy appreciate Xperi+ and the ability to remap the assistant button and that I really hope you will find a way to make it work again) EDIT |
Thank you for this! It seems like the logs haven't changed, but A13 now requires a "one time only" logs permission granted via a dialog. You can re-trigger this dialog when you reset the custom assistant action button to default via the top-right overflow menu from action selection, then set it to your custom action again. When battery optimization is unrestricted, this will probably work as long as you don't reboot your device. You'll need to reset it again afterwards. If there's a way to trigger that dialog after each device reboot, that would be a fairly alright workaround. |
Ah, didn't think about that. Makes it a bit easier, thanks. |
Actually... I could only get it to trigger some of the time, not always.
Sorry :/
…On Fri, Dec 30, 2022, 14:42 Holton181 ***@***.***> wrote:
... You can re-trigger this dialog when you reset the custom assistant
action button to default via the top-right overflow menu from action
selection, then set it to your custom action again...
Ah, didn't think about that. Makes it a bit easier, thanks.
—
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA7IORXOGHK6T2JIREGTHTWP3REXANCNFSM6AAAAAATA2THJA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Can this be fixed and updated for A13 ? |
Same thing here, but when using the remapped button it still opens the "you need to set your default assistant to google assistant" page as well |
fixes mentioned earlier do not work. it also shows "null" for a lot of apps now when you set the action. the maintainer had 2 screens fail on his xperia in a few months so has most likely written them off. i wouldn't hold your breath for a fix to this but it would be nice. i'll never buy another xperia after my experience with this phone. |
mine works now for some things, but a lot of apps are still "null" and don't work at all on XQ-BC62. some of them are even native apps. if you could please take a look at this @ivaniskandar it would be greatly appreciated. lockscreen shortcuts don't work at all either. latest 0.8.0. it worked great on android 12. |
Just upgraded my 10 III to A13 and have the same issue. |
This is most likely broken because of the undocumented change of Android 13 reported here and even the dialog to grant the access request is broken. The only solid workaround I can think of is using Shizuku to run the logcat reader as shell (which still need a one-time activation on every boot) or just use root altogether. |
time to switch to iphone |
Is it possible to get a build of this which has this enabled? I'd take the trade-off for Shizuku as I already use it to force enable VoWifi with Pixel IMS. |
any update on this? |
Is this abandoned? |
Pretty much, yeah. |
For me it works mostly fine. I have an Xperia 5iii with Android 13. The activation is a bit tricky. I need to reset the Button Trigger to Default and lock my Phone. After ten Seconds im unlocking it, i can set it to flashlight, than i get the prompt where it asks for permission. This works every time for me. It sometimes stopps working for no reason (every 3-4 weeks). Just the same Process is needet to get it working again. Also the same is sometimes needet after every reboot. Also i recommend to disable Energy saving for this app. It helps a lot. I hope this helps someone... |
I don't have a Sony device running stock Android 13 so I will not be able to deal with it by myself.
At least a full logcat when pressing the assistant button is needed to do a debug.
The text was updated successfully, but these errors were encountered: