Unlocking phone (possibly even receiving notifications) stops whatever Kodi is playing

Support Solved
1

Be sure to read How to get debug information and open a proper issue to provide necessary logs and information.
Any issue without the logs can be automatically closed without further notice.

Issue description:

Unlocking the phone sends a stop signal to the Kodi player. I think it has happened when receiving notifications as well (possibly related to the screen turning on) but this log extract is from when I unlocked my phone and tapped a Whatsapp notification to reply. A music album was playing on Kodi when all this happened.
Please note that this does not happen every time I unlock my phone or get a notification, but it happens consistently since I installed (clean install) Android 13 (LineageOS 19).

I have a similar, long-standing issue where any interaction with the phone triggers a CEC call to switch my TV/Receiver to Kodi from whatever other input is in use, but I guess I’ll open a separate thread about it later on.

I know your guidelines say not to paste logs here, but I hope it’s ok in this case since it’s a small extract and there’s no private information in it.

Thank you very much in advance!

Logs: (Join files do not paste the content of the files here !)

2023-07-20 12:47:49.927 Verbose/StatusObserver: Screen off
2023-07-20 13:06:19.055 Verbose/YatseReceiver: OnReceive: android.intent.action.SCREEN_ON
2023-07-20 13:06:19.056 Verbose/NetworkManager: Network status: Screen On
2023-07-20 13:06:19.061 Verbose/NetworkManager: Wifi Only: Not connected! UNKNOWN/No active network
2023-07-20 13:06:19.062 Verbose/StatusObserver: Network status changed to false from true
2023-07-20 13:06:19.073 Verbose/FirebaseManager: Result: T999
2023-07-20 13:06:19.075 Verbose/MediaRefreshManager: Refreshing queued media
2023-07-20 13:06:19.076 Verbose/NetworkManager: Network status: Fast refresh
2023-07-20 13:06:19.076 Verbose/NetworkManager: Wifi Only: Not connected! UNKNOWN/No active network
2023-07-20 13:06:19.079 Verbose/MediaRefreshManager: Not connected 1
2023-07-20 13:06:19.080 Verbose/NetworkManager: Network status: NetworkCallback onCapabilitiesChanged: [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=1454Kbps LinkDnBandwidth>=89852Kbps TransportInfo: <SSID: <unknown ssid>, BSSID: 02:00:00:00:00:00, MAC: 02:00:00:00:00:00, IP: /172.16.1.73, Security type: 4, Supplicant state: COMPLETED, Wi-Fi standard: 5, RSSI: -54, Link speed: 650Mbps, Tx Link speed: 650Mbps, Max Supported Tx Link speed: 866Mbps, Rx Link speed: -1Mbps, Max Supported Rx Link speed: 866Mbps, Frequency: 5200MHz, Net ID: -1, Metered hint: false, score: 60, isUsable: true, CarrierMerged: false, SubscriptionId: -1, IsPrimary: -1, Trusted: true, Restricted: false, Ephemeral: false, OEM paid: false, OEM private: false, OSU AP: false, FQDN: <none>, Provider friendly name: <none>, Requesting package name: <none><none>MLO Information: , AP MLD Address: <none>, AP MLO Link Id: <none>, AP MLO Affiliated links: <none>> SignalStrength: -54 UnderlyingNetworks: Null]
2023-07-20 13:06:19.081 Verbose/NetworkManager: Wifi Only: Not connected! UNKNOWN/No active network
2023-07-20 13:06:19.435 Verbose/ApiReceiver: API call: tv.yatse.api.MEDIA_COMMAND - SOURCE : ntf_dismiss
- COMMAND : stop
2023-07-20 13:06:19.442 Verbose/KodiNexus: --> [447] POST http://172.16.1.9:808/jsonrpc (73-byte body)
2023-07-20 13:06:19.442 Verbose/KodiNexus: --> [447] {"id":385,"jsonrpc":"2.0","method":"Player.Stop","params":{"playerid":0}}
2023-07-20 13:06:19.509 Verbose/KodiNexus: <-- [447] 200 OK http://172.16.1.9:808/jsonrpc (67ms, 50-byte body)
2023-07-20 13:06:19.510 Verbose/KodiNexus: <-- [447] {
	"id": 385,
	"jsonrpc": "2.0",
	"result": "OK"
}

Screenshots:
None

Additional information:
Android 13 (LineageOS 19)
Yatse Pro, version 11.5.0/21108270-arm64-v8a

2

Funny how even if there’s clearly written do A, people do B and say you wrote A but I think B is fine :wink:

Anyway this is a bug on your OS, it dismiss the notification while something is playing and it send the intent that should only be sent when dismissed by the user.

3

Thanks for your reply. I know you said A and I did B :slight_smile:
Do you mean that my OS dismisses the Yatse notification and this action (which should not happen without my interaction) makes Yatse send the stop signal?

4

Well I don’t know if it actually dismiss the notification but it does run the pending action tied to that action.

  1. that should only be sent when done by the user.
  2. the notification can’t be dismissed when something is playing.
5

Thanks, I think I understand.
Considering that it’s unlikely that I can change my OS’s behaviour, is there anything else I can do apart from disabling the “Now Playing” notification type?

6

Not really no.

If you had uploaded the logs as asked I could have added a workaround for your phone but we’ll ;):wink:

7

Ok… remind me how to upload my logs? :slight_smile:

I get the standard Android Share option but nothing specifically about an upload procedure.

8

If you read them to copy paste you have them so you can upload them here :slight_smile:

Anyway I just need the full untouched lines that contains Information:

9

I thought it was an upload tool built into the app. It says the file is too large so I got you a generous extract, untouched.
yatse_debug_log05.txt (6.4 MB)
The ntf_dismiss line is at 245481.

Thanks again!

10

There’s not the necessary lines that are near the top :wink:

Enable logs again then do something then stop logs to have those 2/3 lines.

BTW by default when you disable log it propose to zip and send them by mail :wink:

11

Ah, I haven’t disabled it yet! :slight_smile: I’ll do that right now.

12

So much time lost :wink:

Anyway I’ll disable the feature for device who expose lineage in the product code as your device do.

13

Come on, just a few hours! :slight_smile:

But thank you, really, I appreciate your support.

I’ll open a new thread about the CEC issue in the next few days.

14

Imagine that for the millions users who downloaded the app :wink:

For CEC there’s no call to CEC inside Yatse unless you press the custom commands.

15

Fair enough! :smiley:

It may be not CEC then, but interacting with my phone (without interacting with Yatse at all) sometimes switches my AVR to Kodi (this has always been happening, long before Android 13). But I’ll try to produce a useful debug log before I go further.