Quote from Guido on 29.10.2021, 20:36

Hi Gunter,

 

I have honestly not have any other feedback on this since your previous post. It on the Scenic 2 issues and not on the Scenic 3 additional issues. I have now asked a couple of WunderLINQ users to give this a try. I don’t own a BMW anymore and am testing with a test device which might give different results so that’s why I want others to check to.

Will keep you posted.

Quote from Gunter on 31.10.2021, 04:26

Hi Guido,

I did a little test yesterday, at home, indoors. Started a trip and then waited for the "pauze" message to appear... the button had the glow around it and WunderLINQ worked.

I'm not exactly sure what happened the first time since I was lane-splitting and needed my concentration for something else. I suspect it was an issue with Bluetooth disconnecting and reconnecting, in which case you lose the glow/focus around the button and you can no longer control it (as mentioned in my previous post). At that time I was also navigating a little test-route which added some extra confusing.

I will do some extra testing in the coming days and keep you posted.

Kind regards,

Gunter

Quote from Gunter on 03.11.2021, 05:03

Hi Guido,

Using Ver 3.0.1.

What I noticed so far is:

• that after some time, the glow is missing around the focused button. The external buttons (WunderLINQ) still work.
• when zooming in, there is no longer a message indicating max-zoom level.

Will continue testing...

Kind regards,

Gunter 

Quote from Gunter on 16.12.2021, 15:03

Hi Guido,

Thank you for the frequent updates of the app. I was going to say something about the "Overview" function not working, but it seems you already fixed it! Nice. 

As you know I am using a homemade WunderLINQ, or a GunterLINQ as my colleague likes to call it. 

I am still having connectivity problems with WunderLINQ. Before I can start my trip, I have to make sure I launch Scenic in the correct order. (see sequence below) When bluetooth disconnects during the ride, it reconnects, but it doesn't activate the UI-buttons (no glow around it). 

A little frustrated about these connectivity problems, I started to look for other apps who support WunderLINQ. 

I found OsmAnd. This app supports WunderLINQ and also a generic keyboard. Both options work stable. When I disconnect and reconnect Bluetooth, the external buttons just work. 

I also tried it with the official WunderLINQ-app and experienced no problems. Disconnecting and reconnecting bluetooth works flawlessly.

This makes me believe that the problem exists in the Scenic-app.

To replicate the connection issue, execute the following steps exactly:

1. Make sure Scenic is not running by killing it with task-switcher. 
2. Power down WunderLINQ device. 
3. Start Scenic. 
4. Power on WunderLINQ device. 
5. Wait for "WunderLINQ connected" message. Notice that there is no glow around the "Start" UI-button. Also notice that external buttons don't work. 
6. Goto homescreen. 
7. Go back to Scenic.

At this point, the glow appears around the default UI-button and the external buttons work normally. 

A related problem, which I mentioned before is this: when WunderLINQ is powered on before Scenic is started, there is no "WunderLINQ connected" message, no glow around the focused button and the external buttons do not work.

To replicate this:

1. Make sure Scenic is not running by killing it with task-switcher. 
2. Power on WunderLINQ device (make sure it is connected). 
3. Start Scenic. 

I suspect that the test done by "idebide" was missing the first step. It was not clearly stated by me. If Scenic was already running in the background, and connected to WunderLINQ, then there is no problem. 

Maybe the official WunderLINQ behaves differently than my GunterLINQ (which is basically a stripped down BT-keyboard), but I have no connection issues with either OsmAnd-app nor WunderLINQ-app. For the rest, Scenic works fine with my GunterLINQ, it's just not stable in (re)connecting.

I am using Scenic version 3.05

Kind regards,

Gunter

Quote from Guido on 16.12.2021, 15:36

Hi Gunter,

I had a beta tester with a WunderLINQ look at the specific issues you mentioned before and he had no problems. And still no one else reporting these issues. For his detailed report see below. Maybe his sequence is a bit different than yours, but still, I would expect others to have reported this in the over 2 years that Scenic supports the WunderLINQ.

So, it might be Scenic specific in how it reconnects, but the regular WunderLINQ does not seem to have any problems with this.  At least not noticeable for anyone else to report it so far.

When I rewrite this code (probably with CarPlay addition) I’ll have another look at this, but for now other matters have a bit higher priority since this only seems to affect you.

 

Should other come forward with similar problems, of course I’d be happy to take an earlier look.

Sorry, I hope you understand. I just don’t feel comfortable changing something that ‘works’ at this point in time when there are so many other things to do.

 

Nothing critical to say about the use of Scenic in general, and not much to say about it’s use in combination with Wunderlinq and BMW command wheel.

I took the habit to always use the same procedure when starting the day and never encountered any communication problem:

- Launch the Wunderlinq app

- Launch the Scenic app from the Wunderlinq app (and not from the Scenic icon)

- Start the motorbike (and so switch on the Wunderlinq bluetooth communication)

 

 

Quote from Gunter on 17.12.2021, 06:29

Hi Guido,

I understand your decision.

[Removed some negative remarks. I still use your app.]

Kind regards,

Gunter

Quote from Guido on 17.12.2021, 06:49

I understand Gunter. I’ll report back here once this code has been rewritten. All the best.