Skip to content
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

Non-stop notifications cycling after connecting to 2019 Rav4 #1267

Closed
MichaelCrimando opened this issue Feb 6, 2020 · 11 comments
Closed

Non-stop notifications cycling after connecting to 2019 Rav4 #1267

MichaelCrimando opened this issue Feb 6, 2020 · 11 comments

Comments

@MichaelCrimando
Copy link

MichaelCrimando commented Feb 6, 2020

Bug Report

Non-stop notifications cycling after connecting to 2019 Rav4

Preconditions

  1. Pair Android device via BT to the Rav4
  2. Make sure all apps are logged in and permissions enabled on the phone. You do not need to login to the apps in Entune 3.0
Reproduction Steps
  1. Restart the phone
  2. Launch Toyota Entune 3.0 App Suite Connect on the phone
  3. Turn on the car and press the Apps button. Ensure that apps show up and are connected.
  4. Turn off the car and ensure the device disconnects from BT
Expected Behavior

No SDL notifications would be seen

Observed Behavior

Constant notifications:
Toyota Entune (with Toyota logo) "Ready to connect to your vehicle, Tap to launch"
Toyota Entune (with SDL logo) "SmartDeviceLink Connected to" (This is not a typo, it just cuts off)
Toyota+Alexa (with Alexa logo) "Toyota+Alexa is running"
Ford+Alexa (with Alexa logo) "Ford+Alexa is running"

Notifications that keep coming back every ~10 seconds. Each one has a timer that starts at 00:00 and counts down to -00:05 then disappears:
Toyota+Alexa (with SDL Logo) "SmartDeviceLink Waiting for connection..."

OS & Version Information
  • Google Pixel 2 XL
  • Android 10
  • 2019 Rav4

SDL Apps:

  • Ford+Alexa 1.0.17
  • Pandora 2001.2
  • Toyota Entune 3.0 App Suite Connect 1.1.9
  • Toyota+Alexa 1.0.8

This has happened 3/3 times tried

@MichaelCrimando
Copy link
Author

Here's a video:
Non-stop Notifications.zip

@MichaelCrimando
Copy link
Author

MichaelCrimando commented Feb 6, 2020

@kshala-ford @mrapitis @ashwink11
I made a ticket for the issue that I saw in Toyota systems, since I know you're starting to look at Android notifications and this is one of the pieces of that puzzle

@joeygrover
Copy link
Member

joeygrover commented Feb 6, 2020

Is it possible you narrow down the apps a little bit? This list is very long and it would be good to understand if it's a bad actor or not. Also can you confirm all of these apps have been SDL certified?

EDIT: Also any logs from logcat would be very helpful.

@MichaelCrimando
Copy link
Author

@joeygrover working with @bilal-alsharifi now to simplify and get logs. All the apps I have are from the play store, how can we figure out if they're officially SDL certified?

@joeygrover
Copy link
Member

You can use your OEMs page to view app partners that are available. Looking through our records only Webex Meet and Ford+Alexa are currently certified.

@MichaelCrimando
Copy link
Author

Drastically cut down on apps required to do the test

@MichaelCrimando
Copy link
Author

Logcat logs,
logcat_02-06-2020_14-23-35.txt

@bilal-alsharifi
Copy link
Contributor

bilal-alsharifi commented Feb 6, 2020

Most of the apps that are used to reproduce the steps use very old versions of sdl that have some bugs related to the router service:
Pandora uses 4.6.3
Toyota Entune: 4.7.2
Toyota+Alexa: 4.7.2

These bugs were fixed in later versions of sdl.
For example, just removing Pandora that uses the oldest sdl version among the other apps solves the notifications issue.

@bilal-alsharifi
Copy link
Contributor

After testing with @MichaelCrimando, we couldn't reproduce the issue on our Pixel 2XL or Pixel 3XL. The issue is only reproducible currently on @MichaelCrimando Pixel 2XL phone. Is it possible that other apps installed on that phone are affecting the result?

@MichaelCrimando
Copy link
Author

@bilal-alsharifi possibly, but I have 110 apps on my phone. I think we just gotta go based on logs at this point

@bilal-alsharifi
Copy link
Contributor

It looks like the issue is happening on some Android devices because Android takes some extra time (~5 seconds) to dismiss the router service notification after calling this.stopForeground(true):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants