Originally Posted by c_86

How is it not useable? I have been using it from day one and haven't seen an increase in battery drain at all. Not a single bit.


Sent from my Galaxy Nexus using Tapatalk 2

It WAS not really useable because of some slowdowns and the way it was working (independant countdown before detection restarting by itself and not taking care of how the mobile was working) but now with screen on/off detection (with new version) it's a little bit better!

Now the app has to synchronise its countdown with the screen's countdown (instead of detecting screen-touches which is apparently not possible) which would mean that everytime somebody touches the screen and that the screen countdown starts, the app countdown restarts and then if there is no touches it restarts by itself also.

This would avoid an issue that makes the screen turn-off anyway because if the apps countdown restarts every 20 seconds and that screens countdown is set to 30 seconds after some cycles the app doesn't detect our face before screen countdown reaches zero :-/

I'm not sure if I'm clear but I'm talking about real integration here

Originally Posted by Tableuraz

It WAS not really useable because of some slowdowns and the way it was working (independant countdown before detection restarting by itself and not taking care of how the mobile was working) but now with screen on/off detection (with new version) it's a little bit better!

Now the app has to synchronise its countdown with the screen's countdown (instead of detecting screen-touches which is apparently not possible) which would mean that everytime somebody touches the screen and that the screen countdown starts, the app countdown restarts and then if there is no touches it restarts by itself also.

This would avoid an issue that makes the screen turn-off anyway because if the apps countdown restarts every 20 seconds and that screens countdown is set to 30 seconds after some cycles the app doesn't detect our face before screen countdown reaches zero :-/

I'm not sure if I'm clear but I'm talking about real integration here

I'm working on this, and i can announce that the next version will have an option that can disable the polling mode. I found a way to intercept the touch events so i can synchronize with the set screen timeout. In this way the camera scanning should work only few moments before the screen goes off.
This update should resolve also the camera access issue.
Cheers!

Would like to see an option to remove the notification

Originally Posted by fifarunnerr

Would like to see an option to remove the notification

Unfortunately this can't be done due to android system. The app is set to run in foreground mode so that android should not be kill the ISeeYou process. This mode needs a persistent notification icon that tells the user that there is a persistent process running in his system.

How Samsung did it than? Did they build that function in to android or something?

Could you also explain how this app works in free version? What I want to know is how not activates itself and for how long etc.... And what does the blinking mean... If it means that it's scanning for my face while I'm typing this msg its a definite un install of the app as it just eats the hell of the battery

Sent from my Galaxy Nexus using xda premium

Originally Posted by Mirarchi

Unfortunately this can't be done due to android system. The app is set to run in foreground mode so that android should not be kill the ISeeYou process. This mode needs a persistent notification icon that tells the user that there is a persistent process running in his system.

We just asking for option. Other "foreground must" apps have it. Some of us will not mind if it was sometimes killed, in favor of not seeing notification.
:)

Sorry for my English.

Any idea as to when that will come! The update?

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by Mirarchi

I'm working on this, and i can announce that the next version will have an option that can disable the polling mode. I found a way to intercept the touch events so i can synchronize with the set screen timeout. In this way the camera scanning should work only few moments before the screen goes off.
This update should resolve also the camera access issue.
Cheers!

Man, I love you!

For this notification thing, wouldn't changing the process priority fix the Android killing issue? This would require Root access I guess but when the first versions of ICS on the Sensation came out, Android kept killing Sense, then some guys found a fix by changing the process priority

I can't wait for the next version, keep up the good work!

---------- Post added at 07:57 PM ---------- Previous post was at 07:39 PM ----------

Here, I found this quite instructive Process | Android Developers

Originally Posted by Tableuraz

Man, I love you!

For this notification thing, wouldn't changing the process priority fix the Android killing issue? This would require Root access I guess but when the first versions of ICS on the Sensation came out, Android kept killing Sense, then some guys found a fix by changing the process priority

I can't wait for the next version, keep up the good work!

---------- Post added at 07:57 PM ---------- Previous post was at 07:39 PM ----------

Here, I found this quite instructive Process | Android Developers

Maybe i've found also a solution for this. There is much work to do and the time is very low but maybe in the week i can release the new version. Stay tuned!

New version released (1.3)

v1.3: New user interface. Added the Intelligent Timeout system. This will disable the polling mode and detects the user inactivity and will enable the camera T seconds before the screen off event where T is a custom parameter. To enable it, press the settings icon and activate the proper accessibility service. If the service is disabled, the app will use the old polling system with the defined settings. Added finally the possibility to switch off the Notifications.
Added also backwards compatibility. Now the app should be compatible with the latest gingerbread devices (API level 9).
Let me know the results.
Cheers!