I am facing issues with unreliable bluetooth on STK1AW32SC with 8330 CPU. I tested with multiple bluetooth devices and issue remains same
1) Both Logitech V470 bluetooth mouse and K480 keyboard works unreliably. Both of them works fine with my macbook
2) Samsung HS3000 bluetooth headset, the audio is choppy and breaking. This headset works fine with macbook, elitebook, iPhone and samsung note 5, so no issues with headphone.
3) Sony bluetooth headset, same issue as above.
1) compute stick is having latest bios, latest WiFI and bluetooth drivers
2) I tried WiFi in both 2.4Ghz and 5Ghz band and issue remains the same.
The similar issue was reported here and intel support responded pointing at WiFi activity in the area. Please note that my macbook and phones also in the same wifi activity region and not having issues with those bluetooth devices so that response from Intel support is unacceptable.
I've had the same problems with audio dropouts on the original (STCK1A32WFC) compute stick. I identified the problem after looking at the task manager processes and saw that the "system interrupts" process eats 100% from one core. After reboot the problem was gone so in order to avoid the problem, I disabled fast startup. The audio is much better now (however there are some very small pitch changes). I am not using the included WLAN adapter (because it shares the antenna with the BT device) but a USB dongle.
Maybe the same could apply to the new Compute Stick.
Thank you for contacting the Intel community.
Just checking – Do you have the latest Bluetooth driver installed? You can download it here:
Is your BIOS up to date? If not, you can download it here:
https://downloadcenter.intel.com/download/26540/BIOS-Update-FCBYT10H-86A-?product=86612 BIOS Update [FCBYT10H.86A]
Please check http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000006039.html F7 BIOS Update Instructions for Intel® Compute Stick
Please let me know.
Did you even read, i categorically mentioned having latest bios and drivers in my first post itself.
is this the kind of ridiculous support team does intel have who don't even care to read and answer in robotic fashion, extremely disappointing
oh, so is this a modus operandi of intel support that you wann when you do not know the answer? Not going to work, I have screenshots of stupid response above and going to escalate best I can.
and aren't you the same person who gave brainless answer to adjust my tv when rest of the devices are working fine with tv. And now I meet another of your type who asked useless questions about if I have latest driver which I already mentioned in my post that I am using latest driver and BIOS. How do you defend that stupidness. Don't waste our time just because you don't know the answer.
And this is not a free support, I paid my hard earn money for the stick and intel is bound to reply without beating around the bushes. Else there are consumer court.
I'm sorry if the information provided above is not what you expected but for any technician in the world is hard to have an answer of the root cause of the issue at the first time before doing some troubleshooting and sometimes it is necessary to do some investigation depending on the issue and it is not about not knowing an answer.
I posted the BIOS and driver above because I did not see the BIOS and driver versions on your post and I just wanted to make sure. Also your post has been read and understood.
I understand that you want to expect a straight forward answer but depending on the issue no technician can diagnose an issue at the first glance.
To be more straight forward at this moment, we have tested this Intel® Compute stick plenty of times and we have not experience unreliable problems. At this point I suggest you to get replacement for the unit and you can submit a warranty request at the link Al Hill posted above.
Although the thread is 3 years old, the problem is still persistent on the same device with all latest driver and bios updates. I've bought this device 1 day back and I am facing the same issue even though tried every thing mentioned in this thread. I just overcome this issue by adding a usb bluetooth dongle and disabling the builtin bluetooth as a work around. It is very disappointing that even in 3 years, the newly produced devices still have the same issue. So, it means that the issue was not taken serious even though was reported by customers.