I've installed program "motion" on Raspbian OS in my Raspberry Pi to work with camera
The only thing that I couldn't understand is why it gives maximum zoomed image from my Creative PD1110 webcam. In motion.conf config file nothing about that directly. Maybe problem with v4l? I'm total newbee in linux. In windows on Skype all is perfect
I think I fixed that. I set resolution of image on 352x288 as by default in motion.conf (was 320x240). Still don't understand why it worked
Related
I have recently discovered the Mac OS X application GeekTool where one can use a html file as your wallpaper. However that isnt the most interesting thing, what I find interesting about it is that it keeps the html file alive even allowing http requests. I wanted to create that using Node.js and some other web technology that allows to run a browser on the desktop with full access to nodejs' APIs.
So I wondered if there is any way to create an alive browser in the background (as a wallpaper), which is interactive (e.g. I can press buttons and type in inputs). If so, where can read about that?
I prefer either one of the packages mentioned above, but others are accepted as well. What I need it to do is just being under the desktop-icons but as well over the default wallpaper, so it can be interactive.
Thanks 😀
I'm trying to create a responsive custom theme for Wordpress. I'm hosting it locally with WAMP and using a variety of tools to make sure it's mobile friendly. Problem is, I'm not getting consistent results and I can't test on an actual mobile phone until the theme has been uploaded to the actual site (kind of defeats the purpose of hosting and coding locally!).
Results from using the Chrome "Inspect" function:
So far so good, even when the viewport width is less than 320px. Right?
Results from manually resizing the Chrome browser window:
Just kidding, the design breaks at 363px.
So which is going to show up on mobile devices? Any advice is appreciated.
You're likely going to see that the manual resizing of chrome is more accurate to what you would see on a mobile device, but the best way to find out is to test it on a mobile device.
You can test the site WITHOUT deploying it to a server fairly easily as long as you're running a local server (localhost, or 127.0.0.1). Here's how:
Make sure your mobile device and the computer running the local server are connected to the same wifi network.
Find out your local network IP address. Here's a handy link: http://lifehacker.com/5833108/how-to-find-your-local-and-external-ip-address
Type your local network IP address into your mobile device's browser, followed by the port you are running the local server on.
Example: If your local network IP address is 192.168.1.11, and you have been accessing the site at localhost:5000, you can access the site on your mobile device at 192.168.1.11:5000.
After creating a number of landscape-oriented Tizen Web Applications, and building and installing on the box with the Feb 1 Tizen release image using Crosswalk and other boxes with previous images of Tizen, I've discovered that web-applications on the February image will not launch successfully unless the weston.ini files are set to a transform of 90, or 'portrait orientation'.
I've been unable to get web apps to launch in landscape and I'm looking for clues. I have compared packages from the october image and a great many of them have changed. I get a timeout when launching with "xwalk-launcher". I have also attempted to launch with app_launcher.
Service 'org.crosswalkproject.Runtime1' could not be reached: Timeout was reached
I am able to launch these apps successfully in portrait orientation but not in landscape. If you have any ideas about where this problem could be, please let me know. I am looking to find which packages are responsible for the problem.
If you've gotten web-apps running in landscape orientation on HDMI on a VTC1010, how did you do it? Which packages did you change, add, or uninstall? What did you add to, or remove from your configuration files? How did you change your web-apps to counter this specific problem?
It is not possible to run Landscape oriented Web-Apps on the Tizen 3.0 Feb milestone under Crosswalk at this time.
The Crosswalk team at Intel have verified this as being a Tizen bug. The appropriate JIRA issue numbers are TC-2501 and XWALK-4115.
For more details: "I've been using the VTC1010 for testing. My primary choice for display output is HDMI. I have noticed that crosswalk isn't developed for multi-screen yet and I wonder if this could be part of the problem. I have been able to get the Landscape to work on VGA and this can help us move forward but our target is HDMI.
I have also been able to get Landscape to work on HDMI but only under the right conditions. When the VGA is connected the apps will launch on the VGA screen from the start. Once the VGA is disconnected apps will fail with the same error message. After reconnecting the VGA screen the apps will launch on the HDMI port.
It appears the VGA must remain connected. If you boot the box without VGA and just HDMI the apps won't start on boot. You cannot launch the apps by hand. You then connect the VGA display and the apps will launch on the HDMI display. I have found if you disconnect the VGA display the app will shutdown. This is some kind of hard dependancy on the VGA display for the VTC1010."
I believe the problem is in the fullscreen-shell.so.
I have a working fix going forward. Two changes are required for this to work.
remove the line in /etc/xdg/weston/weston-genivi.ini
shell=fullscreen-shell.so
Your apps will launch now but not in fullscreen. To correct this add --fullscreen to weston call.
Add a parameter --fullscreen to line in /etc/session.d/user-session.
weston -i0 --log=$XDG_RUNTIME_DIR/weston.log --backend=wayland-backend.so --fullscreen
I would like to know if there are any reasons for fullscreen-shell that I am not thinking of.
I want develop a simple program for an Android smartphone that give the possibility to the user to transfer an image from the device to the pc. I want create a direct connection using the WiFi Direct technology. I saw the official documentation on the developer android site, and i found it very helpful. My question now, is how can i find the pc and established a connection with it? I saw that establish a connection from two smartphone is really easy, but how can i proceed in this case? The pc need to be in a wireless network (i don't think) ?
Thanks for any suggestion.
The PC does not need to be on a wireless network (that is the whole point of using Wifi-Direct) but to enable Wifi-Direct on a PC, you need to install the Intel MyWifi Dashboard software (full version) and also need to make sure that your drivers are updated.
(http://www.intel.com/support/notebook/sb/CS-033660.htm)
Any ideas on how to get memory usage, Javascript errors, etc. from Chrome running on Google TV?
I have a page that is getting the "Aw, snap!" error when viewed in the Chrome browser on Google TV (Logitech). The page is fairly simple, but it does load a bunch of photos, though only up to 7 at a time (the photos are loaded using JavaScript). The photos are 640x480 and ~500KB each. They are stacked and the top one fades out (using jQuery) until all are gone then a new batch is loaded.
It only crashes on Google TV (it runs fine on Windows 7) and it takes a while before it crashes (I can get it down to about 10-20 minutes before it crashes by turning on a "fast mode" on our page).
Unfortunately I can't figure out how to get any information that might help me debug it. It would be cool to be able to get Chrome's developer tools on the Google TV device.
Currently there is no way to pull debug information from Chrome on Google TV. The Logitech Review is rather limited in it's RAM and you may be encountering an issue there (I don't know how big these images are). It is also possible that you have a memory leak in your javascript code. This might be hidden on other systems running a browser as there would be more memory to buffer you from seeing the error.
My advice would be to create a virtual machine (VirtualBox is free and runs on Windows) - create a VM with limited memory (256Mb Ram for instance) and install Ubuntu or some other flavor of linux that can run Chrome. Then run your app in the VM and see what happens.
Failing that you could always try loading the imaged with static image tags and see if it is the images that are causing the crash. If it's not the images then I would say look at your JS code closely and perhaps run it through JSLint (http://www.jslint.com/)