I have Nokia 5800 xpressMusic and after install SmartTouch application (PC Bluetooth remote control) it tells me that it is connected but not working. There a log file generated after running the server in PC contains the following error:
Traceback (most recent call last):
File "client.pyw", line 24, in run
File "bluetooth\msbt.pyo", line 24, in init
IOError: An address incompatible with the requested protocol was used.
Can anyone help me to make it working?
I have found the solution for this problems and it is as follows:
1- The problem appear when trying to open SmartTouch from my phone (TypeError("fall_max")) vanished after installing the latest version of python 1.9.7.
2- The second problem (takes a more time from me to figure it out and make it working) was a problem in Bluetooth stack. I have Toshiba satellite A200 with Toshiba Bluetooth stack, and SmartTouch works only with Microsoft Bluetooth stack. You can downlaod it from Toshiba web site and install it instead of Toshiba Bluetooth stack.
Related
I downloaded RetroPie for my RaspberryPi 3 from this link and have been trying to get my 3.5" LCD to work. I downloaded the driver from here as described, but whenever I try and extract it with the "tar xzvf LCD_show_v6_1_3.tar.gz", the file for the Osoyoo LCD I have, around 50 lines are executed and then the Pi crashes. When I restart it, it goes into a kernel panic every time. I've reinstalled my OS multiple times. I cannot download the raspbian distro with the driver because I have been unable to install RetroPie on top of it and have been unable to display it on the LCD.
Install instructions and product:
Please respond if you know how to solve this problem or what you recommend.
Turns out I was not using enough power. The usb cable I used was a spare rather than official cable for the Pi. Not enough voltage to complete the tasks.
My Qt application which plays video shows just a blank VideoWidget window.
When I remove my Xorg.conf file from /etc/X11/ directory on my Debian Jessie 8.2 and restart system, video starts to play, but there is a lack of colors on whole display.
- Kernel version is: 4.1.15-ti-rt-r40
- Platform: BeagleBone Black
I found this error reported as a bug on this link, but it is very old thread. Is problem in graphic card drivers built for this BB under Debian Jessie 8.2?
I'm following the tutorial to install linux on SoCkit by Terasic.
This is my first time building a linux, so I am still learning. I was able to complete all the steps shown in the tutorial but when I try to boot it gives me error saying:
Did not find a cmdline Flattened Device TreeCould not find a valid device tree
Now, I know the .dtb file is on the SD card and I can load it using the fatload command of u-boot. After I load the .dtb file and run bootm command I get the error saying:
FDT and ATAGS support not compiled in - hanging ### ERROR ### Please RESET the board ###
I don't know where/how to enable this support. Could someone please help me with this.
It looks like this particular SD card I am using wasn't getting formatted (partitions file system) properly on a virtual machine. I was running Ubuntu 14 on VirtualBox. I then formatted on a laptop running ubuntu and re-wrote the SD card. It booted up just fine!
I use an Kinect, Model 1517, and cloned the master branch from the OpenKinect/libfreenect repo to my Ubuntu 14.04 LTS x64.
My target is to do some fancy stuff with the build in mic-array.
But if I want to test the sources and execute a sample program, I get following output :
$ ./freenect-glview
Kinect camera test
Number of devices found: 1
Could not open audio: -1
Failed to open motor subddevice or it is not disabled.Failed to open audio subdevice or it is not disabled.Could not open device
During compilation no error or warning is pointed out. With debugging I isolated the failure to the initialization of FREENECT_DEVICE_MOTOR.
I also tried to download the stable package version, using
$ sudo apt-get install freenect
but (not in freenect-glview but in other samples) this error occurs too.
What differs from all the tutorials and guides I read, is that after the command $lsusb the output just shows three devices named 'Microsoft Corp.', instead of a longer description like Bus 001 Device 006: ID 045e:02ad Microsoft Corp. Xbox NUI Audio.
Do you have any plans, how I can fix this Problem? I assume, if it doesn't work in these samples, that it also wont work in an selfmade one.
Try running with administrator privileges. I had the same problem and that worked for me.
$ sudo ./freenect-glview
my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.