R
revolverXD
Guest
Great idea.
using samsung galaxy s3
was able to generate touch only once,
and failed the calibration test but its to be expected in such early stage.
and another thing that i noticed is that the camera couldn't track my eyes when i
was wearing my glasses.
using samsung galaxy s3
was able to generate touch only once,
and failed the calibration test but its to be expected in such early stage.
and another thing that i noticed is that the camera couldn't track my eyes when i
was wearing my glasses.
It couldn't find my front facing camera on my tablet 
Maybe any chance for a configurator for the camera? I think my firmware sees my fron camera as a back camera so any chance of option to use back camera*?
*which is ofcourse my front camera, my firmware just thinks otherwise...
Also why don't use the integrated cursor of android itself and fake a mouse input?
Maybe any chance for a configurator for the camera? I think my firmware sees my fron camera as a back camera so any chance of option to use back camera*?
*which is ofcourse my front camera, my firmware just thinks otherwise...
Also why don't use the integrated cursor of android itself and fake a mouse input?
Last edited:
Inference!
Hi Donlk!
Intriguing concept!
Tested it on:
Samsung Galaxy Note (Intl) i.e. GT-N7000... running Paranoidandroid v1.3 ROM
Result:
Does detect head movement nicely and the icon/app selection works upon holding cursor onto it for a brief while
Issues:
1. Quite frequently the cursor jumps to random points hence the tracking isn't reliable
2. Tracking sensitivity is too fluid to control
Suggestions (based on your feasibility):
1. Incorporate a tracking sensitivity setter/adjuster, similar to mouse sensitivity setter on (windows) PC.
2. I understand a plan to append Menu and Back button functionality is in pipeline. In addition Long press functionality might be of help.
I will test the app on Paranoidandroid v1.7 (Staxx build) and report that too!
Cheers 'n beers!
Hi Donlk!
Intriguing concept!
Tested it on:
Samsung Galaxy Note (Intl) i.e. GT-N7000... running Paranoidandroid v1.3 ROM
Result:
Does detect head movement nicely and the icon/app selection works upon holding cursor onto it for a brief while
Issues:
1. Quite frequently the cursor jumps to random points hence the tracking isn't reliable
2. Tracking sensitivity is too fluid to control
Suggestions (based on your feasibility):
1. Incorporate a tracking sensitivity setter/adjuster, similar to mouse sensitivity setter on (windows) PC.
2. I understand a plan to append Menu and Back button functionality is in pipeline. In addition Long press functionality might be of help.
I will test the app on Paranoidandroid v1.7 (Staxx build) and report that too!
Cheers 'n beers!
Crashes on galaxy nexus with paranoid android cm10 jelly bean when I try to calibrate screen.
Sent from my Galaxy Nexus using xda app-developers app
Sent from my Galaxy Nexus using xda app-developers app
I'm on a US HTC One X. Installs fine, as others have said it fails to calibrate, crashing after I have to touch the screen twice.
The app fails to rotate when I rotate the homescreen on its side.
I still haven't figured out how to click things.
The cursor tends to drift upwards when I hold it perfectly still.
This has potential though, and it looks great!
The app fails to rotate when I rotate the homescreen on its side.
I still haven't figured out how to click things.
The cursor tends to drift upwards when I hold it perfectly still.
This has potential though, and it looks great!
Wow... very cool concept indeed! Thank you for your work and for sharing!!
Installed and runs on Motorola Atrix 2 on GB... still getting the hang of it... but I can't get the mouse click to open anything... and calibration also failed for me. Sent a couple of bug reports...
Thanks again! Keep up the good work!
EDIT: Another thing - it looks like the app also keeps the screen awake (does not allow auto screen timeout) until you Force Stop it..
Installed and runs on Motorola Atrix 2 on GB... still getting the hang of it... but I can't get the mouse click to open anything... and calibration also failed for me. Sent a couple of bug reports...
Thanks again! Keep up the good work!
EDIT: Another thing - it looks like the app also keeps the screen awake (does not allow auto screen timeout) until you Force Stop it..
Last edited:
I cant click!!!!!!
it detectes my head movements almost perfectly...but wasnt able to figure out how to click (tried concentrating on a point for few seconds)....this app really has great potientials...n calibration also failed.....
This app will b in no time a revolution...best of luck for the future buils....:fingers-crossed:
it detectes my head movements almost perfectly...but wasnt able to figure out how to click (tried concentrating on a point for few seconds)....this app really has great potientials...n calibration also failed.....
This app will b in no time a revolution...best of luck for the future buils....:fingers-crossed:
Keep working on it. I sent a few error reports. I can confirm that the calibration still crashes on GT-I9100. Even though the calibration crashes you can start the head tracking after restarting the app.
Sent from my GT-I9100 using xda app-developers app
Sent from my GT-I9100 using xda app-developers app
I made a video.
I have tried everything but you can not "press" anything!
http://www.youtube.com/watch?v=S5lP_pe-J-Y&feature=youtu.be
I have tried everything but you can not "press" anything!
http://www.youtube.com/watch?v=S5lP_pe-J-Y&feature=youtu.be
Thanks for the feedback guys, i'm getting hundreds of reports, it really helps a lot!
I'm working on the fix for calibration force close, though i'm not sure what could cause this as i thought i handled every possible exceptions that might occur through the process. However, if you get 'Calibration failed' message, i encourage you to try it a couple of times more (you dont have to send a report every time you try), and see if it succeeds. The important part is to only tap the screen lighty two times, not as you would do normally. This is important because the increasing screen PPI's makes it a lot harder to tap at on only one pixel of the screen, so every time the calibration fails, it means you swyped even if you didnt mean to. Just hit it a couple of times and if it failes repeatedly, send me the log.
As for the other questions and suggestions:
Thank you again very much for your cooperation and enthusiasm, i hope i cleared out some blind spots. I'm working on the fixes, so stay tuned!
cheers,
donlk
I'm working on the fix for calibration force close, though i'm not sure what could cause this as i thought i handled every possible exceptions that might occur through the process. However, if you get 'Calibration failed' message, i encourage you to try it a couple of times more (you dont have to send a report every time you try), and see if it succeeds. The important part is to only tap the screen lighty two times, not as you would do normally. This is important because the increasing screen PPI's makes it a lot harder to tap at on only one pixel of the screen, so every time the calibration fails, it means you swyped even if you didnt mean to. Just hit it a couple of times and if it failes repeatedly, send me the log.
As for the other questions and suggestions:
- Yes, you need root to calibrate and then click. It's in the usage and installation instructions on our website, which i posted a direct link to in the first post. I strongly recommend for everyone to read it through first.
- The mouse's fluidity is due to the 'Mouse smoothing' option turned on in the Settings menu. It can be turned off. I suggest to experiment with it a little, see what suits you. You can access Settings through the menu button on the main screen of the app (also present on the website).
- Mouse sensitivity adjuster is in the same place, in the Settings menu.
- Menu and Back button simulations are already implemented, though they're not present in the Alpha test. It's tested out, and the method is pretty much the same for every device, so we took it out. It will be present in the full Market app. Touch simulation is the one that needs lots of testing, hence it differs not just between touchscreen models, but sometimes between API versions too. This is why we need you guys to stress it out and experiment with it, maybe modify the FaceDetection, Mouse and other options, to see what works best on your device in different lighting conditions.
- If you can't simulate touch with the mouse while face tracking, then the calibration wasn't successful. You can test the calibration out in the Calibration menu, if it succeeds, then you will be able to click.
Thank you again very much for your cooperation and enthusiasm, i hope i cleared out some blind spots. I'm working on the fixes, so stay tuned!
cheers,
donlk
Last edited:
I got this working quite well on my T-mobile Galaxy S III. My only complaint is that once the touch registers, it continues to tap. It would be nice if it would tap only once, or tap and hold until you moved away quickly.
Uploaded build 0.1.7
If you do get unhandled force closes and you have the knowledge of how to look into the logcat, please reproduce the crash and send me the corresponding exception. If you dont know how to do this, that's fine. Just describe when exactly the crash happened.
As the first post states and as i said before, all the info according to installation and app usage can be found here: http://www.colleyeder.com/mousense/installation/
Please read the OP, i will not post this link again for such questions.
If you do get unhandled force closes and you have the knowledge of how to look into the logcat, please reproduce the crash and send me the corresponding exception. If you dont know how to do this, that's fine. Just describe when exactly the crash happened.
As the first post states and as i said before, all the info according to installation and app usage can be found here: http://www.colleyeder.com/mousense/installation/
Please read the OP, i will not post this link again for such questions.
Last edited:
Okay, thanks for the link.
When leaving the mouse sensitivity menu in settings the app crashes. So to change sensitivity I must edit the cfg file manually. I don't have any logcat lines right now, might grab some later when I'm on the pc.
I tried disabling mouse smoothing and the mouse is much easier to control. The downside is that the mouse movement looks laggier, atleast on Samsung Galaxy S2. Maybe the smoothing alg needs tuning?
Sent from my GT-I9100 using xda app-developers app
When leaving the mouse sensitivity menu in settings the app crashes. So to change sensitivity I must edit the cfg file manually. I don't have any logcat lines right now, might grab some later when I'm on the pc.
I tried disabling mouse smoothing and the mouse is much easier to control. The downside is that the mouse movement looks laggier, atleast on Samsung Galaxy S2. Maybe the smoothing alg needs tuning?
Sent from my GT-I9100 using xda app-developers app
Hello, I tried the latest version on my razr, problem is that when I try to calibrate, it gets a force close, same thing with my friend's galaxy s3
The
The
No problem on S3. But not easy to control :/
Thx for the work
Edit : Fc when want to disable mouse smoothing :/
Envoyé depuis mon GT-I9300
Thx for the work
Edit : Fc when want to disable mouse smoothing :/
Envoyé depuis mon GT-I9300
Last edited:
Those who experience force closes please try to reproduce the problem and look into the logcat. You can find such tools on the Play Store:
https://play.google.com/store/search?q=logcat&c=apps
I have absolutely no idea why modifying any Mouse setting would end up in force close, since they're pure API based Preferences.
https://play.google.com/store/search?q=logcat&c=apps
I have absolutely no idea why modifying any Mouse setting would end up in force close, since they're pure API based Preferences.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
33
The Neural Information Processing Group from
Eötvös Lóránd University proudly presents:
MouSense for Android based mobile devices
- MouSense headmouse (head tracker) is a hand-free application software for computers - one can control the cursor on the screen by head movements. Our latest product is MouSense for Android, a headmouse software for Android based smartphones, tablets and other info-communication devices.
- The software uses the latest opensource Computer Vision algorithms to determine the exact position of the head and to track it further. The stability, reliability and flexibility of these Computer Vision algorithms allow us to put them together in a way to create a robust and sufficiently optimized face-tracking software for mobile devices. The software tracks your face using the front-facing camera of the device, displays a small cursor on the screen as you move it along, and lets you simulate touch and API based key events to gain full control over the system.
- We considered making a slightly limited alpha version available to the public, so users with different variety of devices can help us improve our product before we release it to Google Play. Its a limited version hence the different action simulations (long click, drag, swype) are not present. We appreciate the help of testing from anybody who is curious enough to try the software and commited enough to send us the error reports the software prepares in case of a crash.
- Download link to the latest build will always be in post no. 2.
Please don't upload the file to any website or file server, because the software is still in early alpha version, and bug fixing becomes much harder when we start having all sorts of strange error reports from builds coming from unknown sources all across the world wide web. We provide one reliable source for the new builds, one issue/feature tracker site and one discussion topic (this one).
- If you have noticed a bug, had a crash, or have a feature request for the application, you can ceate a new Ticket on this tracker site: http://nipg.inf.elte.hu:8556. All the active tickets holding these informations are under the 'View tickets' tab. Please don't write posts about these matters in this topic.
If you feel you stressed the software well enough and didnt notice behaviour failures (or it has already been fixed), please feel free to post about that so we an add your device to the site under the 'tested devices' secion here: http://www.colleyeder.com/mousense/installation/
- For additional information such as installation, usage, background, contact address etc. please visit our website at: www.colleyeder.com/mousense
The software belongs to Eötvös Lóránd University and ELTE Neural Information Processing Group.
Thank you for your contribution!
6
Market stable release is very close. Until the software is published there won't be any more links here. You all helped a lot with your reports and comments, so i'd like to thank you very much!
- build 0.4:
- Speed optimizations for face preview bitmap redraws
- Instruction popup windows implemented in the main menu and in the swype demo - build 0.3.5:
- Force close fixed when Calibration starts on non rooted devices - build 0.3:
- Demo applications implemented, you can access them through the main menu. These apps can be tried out WITHOUT root access.
- Better mouse smoother algorithms integrated - build 0.2.1:
- menu and back button simulations are merged in (available through the right button panel while facetracking)
- further optimizations for touch calibration - build 0.2:
- massively improved touch calibration
- touch simulation is instant, zero delay
- mouse is not clicking continuosly while holded still
- Mouse sensitivity X, Mouse sensitivity Y and Circle radius step preference strange save behaviour fixed - build 0.1.7.5:
- fully handled possible force closes and failures through the calibration process (hopefully) - build 0.1.7:
- fixed possible runtime exceptions while face tracking
- improved touch calibration (shouldnt fail now if you're tapping it lightly)
- temporary fix for touchscreen device detection on some devices
- improved method for detecting front-facing camera (needs test) - build 0.1.6:
- fixed calibration FC on Samsung i9100 and possible other devices (thanks for the reports)
- fixed seekbar progress display at Circle radius step option in Settings menu - build 0.1.5:
- most logreporters fixed and expanded (please test) - build 0.1.4:
- more logreporters added with extended exception-handlers (tests needed as always) - build 0.1.3:
- added a few more in-app logreporters in case of calibration failure (therefore please send me the prepared log when it does happen!)
- fixed possible FC when 'Start tracking' was pressed - build 0.1.2:
- changed MouseSensitivityX, MouseSensitivityY and CircleRadiusStep option items to launch a seekbar instead of list
- most of logcat debug code removed
- About section in Main menu slightly reworked
- build 0.1.0: initial alpha release
- slight UI lag
4Thanks for the feedback guys, i'm getting hundreds of reports, it really helps a lot!
I'm working on the fix for calibration force close, though i'm not sure what could cause this as i thought i handled every possible exceptions that might occur through the process. However, if you get 'Calibration failed' message, i encourage you to try it a couple of times more (you dont have to send a report every time you try), and see if it succeeds. The important part is to only tap the screen lighty two times, not as you would do normally. This is important because the increasing screen PPI's makes it a lot harder to tap at on only one pixel of the screen, so every time the calibration fails, it means you swyped even if you didnt mean to. Just hit it a couple of times and if it failes repeatedly, send me the log.
As for the other questions and suggestions:
- Yes, you need root to calibrate and then click. It's in the usage and installation instructions on our website, which i posted a direct link to in the first post. I strongly recommend for everyone to read it through first.
- The mouse's fluidity is due to the 'Mouse smoothing' option turned on in the Settings menu. It can be turned off. I suggest to experiment with it a little, see what suits you. You can access Settings through the menu button on the main screen of the app (also present on the website).
- Mouse sensitivity adjuster is in the same place, in the Settings menu.
- Menu and Back button simulations are already implemented, though they're not present in the Alpha test. It's tested out, and the method is pretty much the same for every device, so we took it out. It will be present in the full Market app. Touch simulation is the one that needs lots of testing, hence it differs not just between touchscreen models, but sometimes between API versions too. This is why we need you guys to stress it out and experiment with it, maybe modify the FaceDetection, Mouse and other options, to see what works best on your device in different lighting conditions.
- If you can't simulate touch with the mouse while face tracking, then the calibration wasn't successful. You can test the calibration out in the Calibration menu, if it succeeds, then you will be able to click.
Thank you again very much for your cooperation and enthusiasm, i hope i cleared out some blind spots. I'm working on the fixes, so stay tuned!
cheers,
donlk2Sorry for the inconvenience, but the papers are going slow about publishing rights with the university. Once its done, i'll be pushing up the free version first, then the paid app later on.
No more builds will be released here, so next version would be 1.0 straight away.
netkillercat: yes, hand-tracking is in consideration, not much of a work is required for implementing this feature anyways.
