I am having trouble to change the name of my Apple's Magic Mouse (older model) on MBP.
I did my research and looked in to all the options of debugging to reset the BT module but nothing worked. I am using macOS Catalina 10.15.3 and I am wondering is it the Catalina?
Does anyone know how to change the name of a connected bluetooth device on macOS?
Related
I want to use latest Mendel OS for coral dev board mini. I checked the coral website but they didn't provide any way for windows (Just Linux and Macs). Do someone know how can I do this on windows? I tried with wls but it does not (Couldn't find device)
I tried first method for linux (Windows Linux System) but it does not work. I want to flash my board to new Mendel OS
I've Installed the newest version of Android studio, including the newest version of HAXM, ndk, sdk and whatever other related dependencies it installs. Intel Virtualization bios setting thingy I can't remember the name of is enabled and I have no trouble in virtual box and such.
I created an empty activity and tried testing it on the phone, works perfectly. Then I tried it on the emulator and there is a problem when it is hardware accelerated. It just opens a white window. The android studio displays 0 errors and thinks it ran the app properly. The graphics card I have is a gtx 1060 6gb. When it is software accelerated it works but is so slow I would rather use a chisel on a rock to draw the application usage.
So if someone knows a fix it would be nice.
Thanks
Well I have discovered that in order to solve the issue you have to go to the sidebar menu click More>Settings>OpenGL ES Renderer and(in my case) set it to Angle(D3D11) or Angle(D3D9) or Swiftshader. After that you simply restart the emulator and the issue should be gone.
For me Desktop native OpenGL and Autodetect based on host(which probably sets it to the first thing) don't work and leave you with a white screen.
In case someone finds this useful, you can set software acceleration as below and this solved the issue for me on Mac OS. (OP also mentions it works with software acceleration)
Tools > AVD Manager
Select virtual device
Click on Edit (pencil icon for me)
Click "Show Advanced Settings"
Look for Emulated Performance - Graphics
Select "Software" option
Current version of the emulator (27.1.3) doesn't work for me. The emulator just shows a white screen. Even playing with the gpu in the .ini configuration didn't work.
Once I downgraded to 26.1.4 (https://dl.google.com/android/repository/emulator-darwin-4266726.zip) the emulator started working again.
It seems that the Android Emulator is somehow conflicting with the NVidia Web driver on Mac OS. I had the latest NVidia Web driver (378.05.05.25f04) installed and I was having this same problem - the white screen whenever I used Desktop Native rendering (or left it at the automatic default which selects that as well).
I tried the Swift Shader as well, it works but the performance is abysmal!
On a hunch, I switched back to the OS X Default Graphic Driver from the Nvidia Pref Pane in Apple menu settings, and the Desktop Native driver is now working great after the computer restart!
The same problem can happen to the lightning fast Microsoft Android Emulators utilizing Hyper-V that work on both Intel and AMD CPU based PCs. The solution is in the same line as the accepted answer. For those who use Microsoft Android Emulators and land here by searching "android emulator white screen", here is the screenshot showing how to solve the problem by changing the default hw.gpu.mode from the default "auto" to "mesa":
So sorry
Check your onCreate method in your MainActivity.java, it should have setContextView(R.layout.activity_main)
I've got a new Dell Inspiron 17 (7779) laptop with Windows 10 x64 (1703) which was working fine right up until the point where HyperV was installed. Now the host screen flickers like mad even with no Guest VM's created.
Dell are being particularly unhelpful, so I was wondering is anyone else was having the same issue.
Basically is anyone running Hyper V on a dell Inspiron successfully.
I guess it could also be a clash with the display drivers (Intel HD Graphics 620, driver ver 21.20.16.4627)
OK, I think I've resolved this with the latest Intel graphics drivers 21.20.16.4678, however there were a few issues...
So the Intel drivers (21.20.16.4627) installed on the machine were the ones installed via the Dell Driver Detect tool, if you just download the latest drivers from intel and install them, it wont update them....I think there is some versioning issue with the dell drivers, as it seems to think the existing drivers are newer than the ones your trying to install....
In order to make it accept the new drivers you need to uninstall the existing display driver AND delete the install files. Then after a re-boot the display drivers used should be the default Microsoft ones, you can then upgrade the driver (again via computer manager) selecting the location of the downloaded and unzipped intel drivers.
I'd like to be able to thank Dell for there help, but they failed miserably to provide any.
One last thing...
For some reason windows automatically 'upgrade' the display drivers and re-installed a old version (21.20.16.4627) replacing the latest drivers I installed. I then had to rollback the automatic update, which fixed the issue again. Hopefully I won't have to keep doing this...
It looks like someone has made a mess of versioning some of these updates, its difficult to tell whether its an issue with the Intel drivers or the Dell wrapping of them as part of the driver detect tool, but there's definitely an issue.
I have a POS terminal (APEXA G from POSBank) that comes with multi-touch screen made by Silicon Works. The touch works perfectly on Windows there are official drivers for it. But for Linux the touch does not work at all. After inspecting the device on Linux Ubuntu distribution using [lsusb -v] command I get the follow information:
Silicon Works Multi-touch Device, VID:PID 29bd:4101
The touchscreen is connected through usb not serial connection.
I tried several generic drivers online but none of them worked for me.
After emailing POSBank technical support I received their quick response which solves my problem.
Following their instructions here is what I did:
1. Uninstall the old touch drivers:
- Lanuch Device Manager
- Human Interface Device -> Usb Input Device
- Remove a USB input device with a value of VID_29BD in the attribute (PID is 3711 or 4101)
2. install latest drivers chipset, LAN, touch, etc... (These drivers downloaded from POSBank official website)
-------------------------------------------------
Please note:
-You need Windows only to run the software that applies the touch firmware upgrade.
-Touch firmware v1.8 is still not available from POSBank official website yet
you have to contact technical support or email me.
-You Must Install SiW Daemon Control Panel to upgrade the firmware (it is included in the touch driver zip file from POSBank official website)
-------------------------------------------------
upgrade the touch firmware to V1.8 using instructions below:
Open SiW Daemon Control Panel
On device tab press F6
Select Multi-touch device 0
Click File open then select the firmware update file
Click FW update
After Ubuntu boots the touch should start working out of the box no special configuration is needed.
Note: After the upgrade the touch may not work on Windows. Don't Panic. You will hear a beeping sound every time you click on the screen which is a good sign. To fix do the following:
Open SiW Daemon Control Panel on the Device tap
select Multi-touch Device_0 then click Open Device
select Mouse table(2nd tap) and check Emulation Mode
select About tab and click Preserve Settings which preserves the settings through Windows restarts.
If you have any questions please let me know.
I am happy with their solution now touch works for me on Windows and Ubuntu.
Thank you POSBank and special thanks to Peter Kim from the technical support.
I'm using a Mac Yosemite virtual machine on VMware, and I get this screen that says it's looking for a wireless keyboard (Bluetooth) because it didn't recognise a wired one. However, my normal keyboard input is working fine, as I am able to login. For some reason, I can't get this window to close on the login screen. Is this a problem others have faced?
I was able to resolve similar issue by changing the USB compatibility setting to USB 2.0