testing scenicv3 and wunderlinq with bluetooth keyboard
Quote from Deleted user on 26.07.2022, 15:54Hi Guido,
As a very enthousiastic scenic user, I would like to test scenic with wunderlinq as I do not have a BMW with a wonderwheel yet.
My problem:
with two different bluetooth keyboards and two different iphones (7 and 13) I found that Scenic does not recognize my "wunderlinq" keyboard as it should.
There's no message "connected".
But:
a. in all cases the bluetooth keyboard respond in Scenic as I can use the bluetooth start/stop music keys in scenic; also I can type a search phrase on the bluetooth keyboard in scenic.
b. also the left & right arrows on the keyboard work, so keyboard mapping seems ok (I can move the cursor back and forth while editing a text field)
c. but there's no 'orange glue' around the buttons
So my guess is that Scenic does not recognize the bluetooth keyboard as a simulated wunderlinq...
Is the real wunderlinq sending an identification-code or even a keep-alife-code or something like that?Thanks in advance for your reply.
Best regards,
Hi Guido,
As a very enthousiastic scenic user, I would like to test scenic with wunderlinq as I do not have a BMW with a wonderwheel yet.
My problem:
with two different bluetooth keyboards and two different iphones (7 and 13) I found that Scenic does not recognize my "wunderlinq" keyboard as it should.
There's no message "connected".
But:
a. in all cases the bluetooth keyboard respond in Scenic as I can use the bluetooth start/stop music keys in scenic; also I can type a search phrase on the bluetooth keyboard in scenic.
b. also the left & right arrows on the keyboard work, so keyboard mapping seems ok (I can move the cursor back and forth while editing a text field)
c. but there's no 'orange glue' around the buttons
So my guess is that Scenic does not recognize the bluetooth keyboard as a simulated wunderlinq...
Is the real wunderlinq sending an identification-code or even a keep-alife-code or something like that?
Thanks in advance for your reply.
Best regards,
Quote from Guido on 27.07.2022, 16:17Perhaps obvious but still I have to ask… Did you enable “I have a WunderLINQ” is settings?
Perhaps obvious but still I have to ask… Did you enable “I have a WunderLINQ” is settings?
Quote from Deleted user on 28.07.2022, 01:28Sorry Guido,
I should have said that: yes I enabled Wunderlinq in the Scenic settings and I allowed Scenic to use bluetooth.
Oh and I also renamed the name of the bluetooth keyboard to "WunderLINQ" in IOS bluetooth settings. I use the latest version of Scenic 3.12 and IOS 15.5
Thanks,
Sorry Guido,
I should have said that: yes I enabled Wunderlinq in the Scenic settings and I allowed Scenic to use bluetooth.
Oh and I also renamed the name of the bluetooth keyboard to "WunderLINQ" in IOS bluetooth settings. I use the latest version of Scenic 3.12 and IOS 15.5
Thanks,
Quote from Guido on 28.07.2022, 02:14Ok. Let me check the code on this. It’s been a while since I programmed this bit. Will probably be next week before I have time for this. Will keep you posted.
Ok. Let me check the code on this. It’s been a while since I programmed this bit. Will probably be next week before I have time for this. Will keep you posted.
Quote from Deleted user on 28.07.2022, 04:52Ok, thanks a lot in advance.
Ok, thanks a lot in advance.
Quote from Guido on 28.07.2022, 20:02Is the real wunderlinq sending an identification-code
Checked the code and, your above remark is true. Next to the name (which you changed correctly), Scenic also checks for a specific service UUID and characteristics UUID that must be available on the connected device. And only a real WunderLINQ emits these specific UUIDs.
Because a bluetooth keyboard does not offer these UUIDs the keyboard connects like a regular Bluetooth Keyboard, letting you enter text and move the cursor if in a text field.
Is the real wunderlinq sending an identification-code
Checked the code and, your above remark is true. Next to the name (which you changed correctly), Scenic also checks for a specific service UUID and characteristics UUID that must be available on the connected device. And only a real WunderLINQ emits these specific UUIDs.
Because a bluetooth keyboard does not offer these UUIDs the keyboard connects like a regular Bluetooth Keyboard, letting you enter text and move the cursor if in a text field.
Quote from Deleted user on 31.07.2022, 09:27Hi Guido,
Thanks for your reply!
In the meantime I have made a prototype "wunderwheel", basically consisting of 4 buttons connected to a small bluetooth capable cpu chip. Even with a IOS toggle function for bringing up the virtual iphone keyboard when connected.
Would it be possible to support a generic bluetooth keyboard in Scenic next to the WunderLINQ option? I think more users might appriciate this.
By the way I found out that the Wunderlinq APP on IOS does work with a generic bluetooth keyboard as well. It is possible to navigate with the normal up, down, left, right keys in this app. So I guess they do not check the Wunderlinq hardware UUID info themselves. This might be something to consider as well.
Best regards,
Hi Guido,
Thanks for your reply!
In the meantime I have made a prototype "wunderwheel", basically consisting of 4 buttons connected to a small bluetooth capable cpu chip. Even with a IOS toggle function for bringing up the virtual iphone keyboard when connected.
Would it be possible to support a generic bluetooth keyboard in Scenic next to the WunderLINQ option? I think more users might appriciate this.
By the way I found out that the Wunderlinq APP on IOS does work with a generic bluetooth keyboard as well. It is possible to navigate with the normal up, down, left, right keys in this app. So I guess they do not check the Wunderlinq hardware UUID info themselves. This might be something to consider as well.
Best regards,
Quote from Guido on 31.07.2022, 09:39That's interesting about the WunderLINQ app themselves not checking this. Let me see if I can remove these checks without side effects. If so, I'll do that for the next update.
That's interesting about the WunderLINQ app themselves not checking this. Let me see if I can remove these checks without side effects. If so, I'll do that for the next update.
Quote from Deleted user on 01.08.2022, 15:54Thanks! That would be great!
Thanks! That would be great!
Quote from Guido on 11.08.2022, 13:18So... I have disabled the UUID checks in the upcoming version. Releasing a beta with that soon. Are you already a beta tester? If not, and you would like to test, could you send me a direct email (use 'email me' button at bottom of help page)?
There is one caviat with this. The bluetooth keyboard needs to 'advertise' it's name "WunderLINQ". If it does not advertise this, it won't be recognized. So, this won't work with all keyboards. For example... I have a random Chinese bluetooth keyboard here. I can change it's name in iOS bluetooth settings, but the keyboard (firmware I'm guessing) is configured to not advertise its name. So, with my keyboard it doesn't work.
Having said that, by disabling the UUID checks I now have a check that's equal to or very similar to what the WunderLINQ guys are doing in their app, so with your 'keyboard' it should work. Curious though.
So... I have disabled the UUID checks in the upcoming version. Releasing a beta with that soon. Are you already a beta tester? If not, and you would like to test, could you send me a direct email (use 'email me' button at bottom of help page)?
There is one caviat with this. The bluetooth keyboard needs to 'advertise' it's name "WunderLINQ". If it does not advertise this, it won't be recognized. So, this won't work with all keyboards. For example... I have a random Chinese bluetooth keyboard here. I can change it's name in iOS bluetooth settings, but the keyboard (firmware I'm guessing) is configured to not advertise its name. So, with my keyboard it doesn't work.
Having said that, by disabling the UUID checks I now have a check that's equal to or very similar to what the WunderLINQ guys are doing in their app, so with your 'keyboard' it should work. Curious though.
Quote from bartelsman on 13.08.2022, 07:56Hi Guido,
Would certainly be happy to test. Have sent you an email!
Thanks.
Hi Guido,
Would certainly be happy to test. Have sent you an email!
Thanks.
