search

RikkaApps / WADB

A simple switch for adb (Android Debug Bridge) over network.
https://play.google.com/store/apps/details?id=moe.haruue.wadb
Apache License 2.0
578 stars 77 forks source link

Quick settings tile wrong behaviour #19

Closed mgood7123 closed 3 years ago

mgood7123 commented 3 years ago

In Samsung, tapping on the quick settings tile CAN, but not ALWAYS, invoke the next song media action

RikkaW commented 3 years ago

This is out of our control.

mgood7123 commented 3 years ago

This is out of our control.

How so?

RikkaW commented 3 years ago

SystemUI controls this :)

mgood7123 commented 3 years ago

System ui controls what happens when the tile is clicked?

On Thu, 5 Aug 2021, 9:27 pm Rikka, @.***> wrote:

SystemUI controls this :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RikkaApps/WADB/issues/19#issuecomment-893381903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLITH52NOSW5YIEYA4S25DT3JYSPANCNFSM5BTMSVAA .

RikkaW commented 3 years ago

SystemUI controls what app is used when clicking the tile

haruue commented 3 years ago

I saw you are maintaining lots of projects, so it should be OK to talk about this issue in detail.

Android, as a modern operating system, has many features that are not implemented by applications. Instead, the Android OS provides a series of methods, which is called the "API". Applications use these APIs to tell OS what they want to do, and the OS determines the detailed implementation.

In this example, the OS provides an API named TileService for applications that want to display a tile. This API has a series of callback methods, which will be called when users interact with the quick settings tiles. For example, when the user clicks the tile, the TileService#onClick() will be called. We just extended this class in the WADB, and implemented those callbacks, which you can find in the WadbTileService. However, what this API really does is implemented by the system. As you can see, the only thing we know is we did nothing about media action in this service. There is nothing we can do to fix this bug.

So what would be the reason for this problem? I think there are two possibilities.

  1. There is a bug in Samsung's customized system. You can update your system to the latest version. If this problem still persists, you can try to find other people who also use devices of the same model, if they also encountered a similar problem, please report this bug to Samsung.
  2. If you are using Xposed, please note that an Xposed module can modify the implementation of Android frameworks. So maybe there is a malfunction on your device which causes this problem. Please try to disable those Xposed modules one by one to check which module is the cause. And report this bug to the maintainer of that module.
mgood7123 commented 3 years ago

SystemUI controls what app is used when clicking the tile

Hmmm

mgood7123 commented 3 years ago

I saw you are maintaining lots of projects, so it should be OK to talk about this issue in detail.

Android, as a modern operating system, has many features that are not implemented by applications. Instead, the Android OS provides a series of methods, which is called the "API". Applications use these APIs to tell OS what they want to do, and the OS determines the detailed implementation.

In this example, the OS provides an API named TileService for applications that want to display a tile. This API has a series of callback methods, which will be called when users interact with the quick settings tiles. For example, when the user clicks the tile, the TileService#onClick() will be called. We just extended this class in the WADB, and implemented those callbacks, which you can find in the WadbTileService. However, what this API really does is implemented by the system. As you can see, the only thing we know is we did nothing about media action in this service. There is nothing we can do to fix this bug.

So what would be the reason for this problem? I think there are two possibilities.

  1. There is a bug in Samsung's customized system. You can update your system to the latest version. If this problem still persists, you can try to find other people who also use devices of the same model, if they also encountered a similar problem, please report this bug to Samsung.
  2. If you are using Xposed, please note that an Xposed module can modify the implementation of Android frameworks. So maybe there is a malfunction on your device which causes this problem. Please try to disable those Xposed modules one by one to check which module is the cause. And report this bug to the maintainer of that module.

hmm ok

mgood7123 commented 3 years ago

I saw you are maintaining lots of projects, so it should be OK to talk about this issue in detail.

Android, as a modern operating system, has many features that are not implemented by applications. Instead, the Android OS provides a series of methods, which is called the "API". Applications use these APIs to tell OS what they want to do, and the OS determines the detailed implementation.

In this example, the OS provides an API named TileService for applications that want to display a tile. This API has a series of callback methods, which will be called when users interact with the quick settings tiles. For example, when the user clicks the tile, the TileService#onClick() will be called. We just extended this class in the WADB, and implemented those callbacks, which you can find in the WadbTileService. However, what this API really does is implemented by the system. As you can see, the only thing we know is we did nothing about media action in this service. There is nothing we can do to fix this bug.

So what would be the reason for this problem? I think there are two possibilities.

  1. There is a bug in Samsung's customized system. You can update your system to the latest version. If this problem still persists, you can try to find other people who also use devices of the same model, if they also encountered a similar problem, please report this bug to Samsung.
  2. If you are using Xposed, please note that an Xposed module can modify the implementation of Android frameworks. So maybe there is a malfunction on your device which causes this problem. Please try to disable those Xposed modules one by one to check which module is the cause. And report this bug to the maintainer of that module.

This is probably a rare bug then