sorry if my english isn't perfect but my first language is french.
My problem is I have a cross-compiler on my window for raspbian and i finally did it, but when i execute the program on my pi the widget on window has no text and i don't have a close button. Someone gave me a code that works perfectly on his raspberry pi and i have the same result. With both codes it's the same result: just the basic window with a push button "test" written over it. So I know that my issue isn't my cross compiler but is on my pi. I tried to uninstall qt5-default package,reinstall it and upgrade all packages, but isn't effective. i tried to run linuxfb plugin with this command -./myprogram -platform linuxfb but i have the graphical bug... take a look at this picture.
my program it's on the left corner
I have also posted on Qt forum, but the reply time is very slow. it'll have been three weeks that i tried to find the issue. if anyone can provide a solution or an idea for this problem i will take any suggestions.
Thanks for reading this message.
Kuba Ober gave me a solution to solved it take a another microsd reinstall a raspbian img with qt5 and it's work!!! but what is exactly the issue i don't know but this solution work.
I know that my issue isn't my cross compiler but is on my pi
That's unlikely - it's easy to check: download a fresh Raspbian image to an SD card, boot it up, and try your code out.
You forgot the more likely reason: you probably have built a non-fully-functional copy of Qt. I bet it won't work on anyone's Raspberry Pi, including your friend's.
Your issue is actually the --platform plugin you are using, linuxfb won't have any Windows borders because it's writing directly to the frame buffer, not to the X server. You need to use xcb.
And don't run it as root or you are likely to loose your DISPLAY environment.
Related
I just downloaded and tried to install the 'Rosetta' rough sets tool on my laptop with OS Windows 10, but I can't. And after I search, it seems only compatible for Windows 98 / XP. But the problem I saw in the video tutorial is that anyone can run it on an OS that looks like that. Does anyone know of a solution to being able to use Rosetta on Windows 10?
Error message when I install Rosetta
I have just solved this problem after many days of googling and trying various ways. I use the "Run programs made for previous versions of Windows" feature in the control panel, then troubleshoot. I have also written down the step I did on that, and I uploaded in my medium story, but in "Bahasa Indonesia". So if you want to read it, you can translate it into English first to understand.
The medium link below:
https://medium.com/#andini.pratiwi/tidak-bisa-install-software-old-version-karena-tidak-compatible-dengan-os-windows-10-solusinya-1d8820c71572
While learning buildroot i write this document
https://github.com/EliArad/MyDocuments/blob/master/Linux/Buildroot/Buildroot_image_with_Qt5_OPEGN_GLS_2.0_mesa_VC4_driver_in_32_bit.odt
That list the steps i make to get QT5 run with the VC4 driver.
The status for now is that i managed to get the device loaded.
I built image with buildroot with examples for qt5.
But not all the examples are working fine.
some works and the majority not.
for example, the marron game
and animation are not showing ( just gray screen)
many of the help out there are referring to vc4 + raspbian jessie
but i want to make it work using build root.
Can you please tell me what should be done to make it work perfectly
using buildroot?
*This is not final answer but some issue solved.
I found several things , not yet complete my mission here but 1. I need the x.org fbdev , because QT uses this plugin to determine the screen size. 2. Need to install libxkbcommon for the keyboard 3. Need to add export QT_QPA_EGLFS_NO_LIBINPUT=1 found it here:
4. Need to link between /usr/share/fonts to /usr/lib/fonts
because buildroot install it in usr/share/fonts
and qt wants it in usr/lib/fonts ( howto use fontconfig?)
https://github.com/carlonluca/pot/issues/54
5. QT complains that it cannot decode png files. there is also some issue with fake kms or kms. I checked raspbian and there only fake kms works but without mouse left click. if some one use buildroot with QT and can share with us it will be great.
EDIT:
You have to select the PNG support on Qt5 package menu
is better to remove the output/built/qt5-(...) folder to recompile the Qt package
Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.
I've faced a problem getting my libusb-w32 based program to detect devices.
The program has to detect digital cameras, and I need to automatically install driver filter for any new camera to be detected without any manual work.
I've used install-filter i --class={6BDD1FC6-810F-11D0-BEC7-08002BE2092F} , i. e. installing filter for MTP devices, and it seemed to work. But today I tried it on a clean machine and found out it actually only seemed that way. Tried install-filter with different parameters - no luck.
The only way I was able to detect devices at all was to use the inf-wizard.exe. It installed the driver, enabling my program to detect devices, but also disrupting the original Windows functionality for digital cameras. Then, I've uninstalled the libusb driver, installed the original windows driver back, executed install-filter i --class={6BDD1FC6-810F-11D0-BEC7-08002BE2092F} - and the program is still able to detect devices.
The question is: how to automate the process so that any new camera is detected without any work required from a user?
Update:
I'll shorten the question. It seems that when I install a driver with inf-wizard.exe, it does something besides installing the driver itself. I need to know what, exactly.
Thanks in advance.
In case someone has similar problem - the answer is here:
https://sourceforge.net/mailarchive/forum.php?thread_name=749401313049992%40web78.yandex.ru&forum_name=libusb-win32-devel