Related
I find this behavior of my touch pro irritating and stupid. The screen goes off during coversation. We all know that. And we know that we can tweak it via the registry not to go off at all.
But WHY can't it just act like my wife's iPhone does? The iPhone turns the screen off during conversation by using the LIGHT DETECTOR. So when you put it near your ear screen goes off and immediately returns when you move the phone away from your ear. I am using my wife's iphone a lot and I can say this behavior works excellent, flawless and so much better than the Touch Pro, where it's either goes off and I have to click on a button each time to turn it on again. Or just leave the LCD on even I talk for half an hour. Did anyone fix that ?
Look for Touch InCall Screen Tweak.
Check the options for:
"Ignore Light Sensor"
"Ignore First Screen Off"
and I believe it'll work how you want it to.
unless one talk for a long time turning on and off the lcd backlight would most likely use more power then having it on during the call these devices don't have led backlight or use oled
so there is still a neon backlight type of thing I believe
and they use most power when turning on
mindfrost82 said:
Look for Touch InCall Screen Tweak.
Check the options for:
"Ignore Light Sensor"
"Ignore First Screen Off"
and I believe it'll work how you want it to.
Click to expand...
Click to collapse
I just want to second this. The behavior you describe really annoyed my about my fuze as well, when I had been using a Samsung Eternity that operated similar to the iPhone (detected when it was at your ear to turn off screen).
Get the program mindfrost said, it works like a charm! You can even make the phone automatically turn to speakerphone when you sit it face down mid-call, and go back to normal when you pick it back up! It's an excellent add-on.
I don' understand one thing. Why do we check Ignore Light Sensor? I have the program, my phone now works like an iphone with the settings you described but that option is throwing me for aloop
I went to the thread for the app and found that the app is working a bit different than I thought. I do enjoy this app. Nuts that this isn't an out of the box type behaviour.
the iphone doesnt use the ambient light sensor, it uses the proximity sensor which the touch pro doesnt have. if you tilt it up to the sunlight you can see 3 black spots on the iphone. one that is the light sensor, a proximity beam and sensor. it can tell if an object like your face is too close to use the screen and turns it off during a call.
The Jack of Clubs said:
the iphone doesnt use the ambient light sensor, it uses the proximity sensor which the touch pro doesnt have. if you tilt it up to the sunlight you can see 3 black spots on the iphone. one that is the light sensor, a proximity beam and sensor. it can tell if an object like your face is too close to use the screen and turns it off during a call.
Click to expand...
Click to collapse
Thanks for all replies. I will try Touch InCall that you guys suggested.
Jack : I didn't know that. That seems like a smart thing to do, better than using the light sensor I wonder why the HTC guys didn't think about that being that the HTC devices are more expensive, newer and should have better tech. Oh well
I'm a bit curious why everybody wants their screen to remain on while they are talking on the phone. Do you like to press the screen with your cheek while you're talking? What do you need to look at the screen for? I've always had the option of turning the screen off while talking enabled.
pennywisdom said:
I'm a bit curious why everybody wants their screen to remain on while they are talking on the phone. Do you like to press the screen with your cheek while you're talking? What do you need to look at the screen for? I've always had the option of turning the screen off while talking enabled.
Click to expand...
Click to collapse
I don't think anyone is saying that - they want the screen to turn off when the phone is against their face, and turn on if the phone is moved, to type in numbers, take notes, etc.
DaveLinger said:
I don't think anyone is saying that - they want the screen to turn off when the phone is against their face, and turn on if the phone is moved, to type in numbers, take notes, etc.
Click to expand...
Click to collapse
Yep. That's correct
DaveLinger said:
I don't think anyone is saying that - they want the screen to turn off when the phone is against their face, and turn on if the phone is moved, to type in numbers, take notes, etc.
Click to expand...
Click to collapse
I guess the impression I got from the Tilt (which doesn't have a light sensor) and the users of the Tilt, they didn't like the screen to blank during a call. I always turn my screen off with the power button if I have to while I'm on the phone so I never understood why they wanted it to stay on.
I think the problem with using the photo sensor reading is that if it is dark, you'll never get the screen to turn back on, even if you pull the phone away from your ear.
On the Raphael/Touch Pro perhaps the improved screen sensitivity and the non-bezelled screen makes for ear shenanigans while ear mashing.
I could get away with ear mashing on the Tilt and the Wizard.
What if you are using bluetooth in the car?
May be this tool will be usefull.
It switch off screen using proximity sensor detection.
Like alternative power button.
After proximity detected - screen switched off and proximity sensor don't used until screen will be switched on again manualy.
No screenshots
Second time running will unload program from memory, it can be used for switching on/off proximity lock feature.
All settings in registry, settings reloaded on each program run.
HKEY_CURRENT_USER\Software\Exidler\Hd2ProximityScreenOff
AfterCallReactivateSensor = dword:150 - time in ms when activate proximity sensor after call ended
SensorOffWhenProximity = dword:0 - time in ms when disabling proximity sensor on proximity detected. May be useful for disabling accident detection. This time proximity sensor is still active and if no porximity detected with this time - screen will be switched on automatically
ActiveOnlyIfLocked = dword:0 - Activate Proximity sensor only if Phone locked.
HKEY_CURRENT_USER\Software\Exidler\Hd2ProximityScreenOff\Exceptions
Create any named sub keys with values:
ClassName = string - name of windows class
WndTitle = string - title of window
ProcName = string - name of process
For exception windows proximity sensor will be disabled if this one window is active.
All criterias are optional. For example create only one value ProcName="Explorer.exe" for disabling proximity lock when Resco Explorer is active.
Proximity sensor activated only in portrait mode.
Change log
2010-01-29: v0.2
- full uninstallable cab
- add options: After Call Reactivate Sensor, Sensor Off When Proximity, Active Only If Phone Locked, Exception windows
- disbaling Proximity lock when landscape mode
2010-01-28: v0.1 Test version. Bugs possible.
Great something to get us started, did you make this yourself? Are you willing to put some time in to perfect it & create some options etc. if we bug test it?
exidler said:
May be this tool will be usefull.
It switch off screen using proximity sensor detection.
Like alternative power button.
After proximity detected - screen switched off and proximity sensor don't used until screen will be switched on again manualy.
No screenshots, not settings, just install and reboot phone (or run tool manual from Install directory)
Second time running will unload program from memory.
Test version. Bugs possible.
Click to expand...
Click to collapse
How will this effect the screen turning on after a phonecall, i wan't the screen automatically turned on after a call without having to press a button.
Will this tweak allow default function in that case?
richardirv said:
Are you willing to put some time in to perfect it & create some options etc. if we bug test it?
Click to expand...
Click to collapse
I don't know which options may be added.
I'm can't full control proximity sensor. It's only possible to enable proximity sensor, and htc drivers switching off screen by itself. The i'm disable proximity sensor again
But if it's will be possible to implement some features - i can try to do this.
Ok this is a good start, for me the following things need to be worked out for this to work good.
1. Only works when phone is upright, ie. Portrait. Reason being is if the screen goes off via Proximity in when holding the phone in landscape there will be allot of accidental activations, especially while playing games etc. It is much less likely that proximity will be detected when holding the phone upright.
2. Screen needs to come back on when proximity not detected, as to not cancel out the in call screen off feature.
Will keep thinking! Really hope you can work some magic here exidler!! Thanks
ET said:
How will this effect the screen turning on after a phonecall, i wan't the screen automatically turned on after a call without having to press a button.
Click to expand...
Click to collapse
it will handle proximity sensor to default behavior after call. so i think (and shure) - screen will blink for short time (~200ms) and will be switched off by tool.
exidler said:
it will handle proximity sensor to default behavior after call. so i think (and shure) - screen will blink for short time (~200ms) and will be switched off by tool.
Click to expand...
Click to collapse
Let me test, I assume the cab can be de-installed and everything is back to default behaviour?
richardirv said:
1. Only works when phone is upright, ie. Portrait. Reason being is if the screen goes off via Proximity in when holding the phone in landscape there will be allot of accidental activations, especially while playing games etc. It is much less likely that proximity will be detected when holding the phone upright.
2. Screen needs to come back on when proximity not detected, as to not cancel out the in call screen off feature.
Click to expand...
Click to collapse
in call screen back on when no proximity
when not in call - it switch off. or you talking about switching on screen when not in call?
about landscape and portrait. it's make easy if screen orientation really changed (if not - polling g-sensor - is not a good idea for battery i'm think)
ET said:
Let me test, I assume the cab can be de-installed and everything is back to default behaviour?
Click to expand...
Click to collapse
Cab is Uninstallable, but you must close program manually before uninstalling: run program second time, it will show message about closing
exidler said:
in call screen back on when no proximity
when not in call - it switch off. or you talking about switching on screen when not in call?
about landscape and portrait. it's make easy if screen orientation really changed (if not - polling g-sensor - is not a good idea for battery i'm think)
Click to expand...
Click to collapse
I just ment you don't want it to interfere with the in call actions the HD2 already has.
As you say g-sensor polling etc. no good for battery. I have a feeling this maybe flawed before we get started.
richardirv said:
I just ment you don't want it to interfere with the in call actions the HD2 already has.
Click to expand...
Click to collapse
program know about call and not be interferace with HD2 proximity call actions.
Landscape alternative - Programs (windows) exceptions - when it's active - promity sensor may be disabled. (but this feature need more time for apply)
Just tested the app and maid an incomming call with an other phone, the screen will automaticly turn on after moving from my ear as should be.
Great app I must say!
My fear is when using apps like fpsece etc, the screen will keep going off. Need to put our heads together and brainstorm some ideas to prevent acidental proximity.
The landscape idea with g-sensor was the first thing that came to me but hopefully there will be a better idea. Maybe only when the phone is perfectly horizontal (i.e as it goes into a pocket) The problem is keeping the g-sensor active will drain battery....
Idea's peeps!!
Hmm no way of de-installing it. If I use the app and then push the on button and then try to remove the app via start/settings, after about 10 seconds the device freezes.
Even after trying to install the app again (wich usually workes to remove apps witch can't be completely removed via start/settings) the device freezes.
Taking battery out is only way to restart. App remaines on device though.
Noticed also that the app is flawed, trying to go with my right finger to the left top of the screen to push start makes the screen turn of and that simply sucks.
HOW TO REMOVE THIS APP?
ET said:
HOW TO REMOVE THIS APP?
Click to expand...
Click to collapse
Before uninstalling go to install folder (defaul is \Program Files\Hd2ProxmityScreenOff) and run exe file inside Hd2ProxmityScreenOff.exe
You will see message about that programe closed. Tap Ok and then uninstall.
All be fine.
about freezing when uninstalling without stopping in memory process i'm know.
exidler said:
Before uninstalling go to install folder (defaul is \Program Files\Hd2ProxmityScreenOff) and run exe file inside Hd2ProxmityScreenOff.exe
You will see message about that programe closed. Tap Ok and then uninstall.
All be fine.
about freezing when uninstalling without stopping in memory process i'm know.
Click to expand...
Click to collapse
OK thanks, it's de-installed correctly. Maybe will use it in the future when it has matured a bit.
The programm should look on proximity-sensor, when i turn on my phone with the power-button.
--> if proximity detectet, screen should be staying off
--> if no proximity, phone should be wake up
Is this possible with your app? This would be a very great feature off our hd2! Perfect locking solution!
Bib_x said:
The programm should look on proximity-sensor, when i turn on my phone with the power-button.
--> if proximity detectet, screen should be staying off
--> if no proximity, phone should be wake up
Is this possible with your app? This would be a very great feature off our hd2! Perfect locking solution!
Click to expand...
Click to collapse
it's not possible until full hack of promitiy sensor.
i'm not have a fule of knowlendge fo arm assembler interpereting.
it' not difficlt for poples, how have knowledge of arm programs research.
but for me, i'm only can handle simple events
We are waiting for full promitiy API
so all of yours requests is impossimle.
Its a good start. Keep the project on.
perhaps a little bit easier to develop and to get various possibilities:
could you add 2 parameters to your app:
-activate
-deactivate
or so.
then it could be called also from other apps depend on its needs and states.
And also one scenario: It should only work if screen is locked(using notification).Then it's sure,that it should switch off because sensor detection
Keep up your great work.A really good idea,which can be very useful, if adaptable and a little configurable.
Thanx
Micha
RootDim (formerly known as ScreenDim) lets you set the screen brightness on backlit screens below what the OS normally allows, which is handy for amateur astronomy where the lowest normal OS backlight setting (even with a red nightmode) leaks enough through the black pixels to damage night vision. Moreover, SuperDim lets have several brightness profiles, and to include nightmode settings (enabled by ChainFire3D or Cyanogenmod's render fx) as part of the brightness profile.
Needs root.
Public domain, source code available. In Market (search for RootDim).
Now in Market (free, no ads).
I just uploaded version 1.10, which restores low brightness settings after the screen is turned off and back on (the OS normally was restoring its brighter screen).
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
bobtentpeg said:
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
Click to expand...
Click to collapse
I assume this is when you use the other lights option to toggle these lights, or when you restore a profile, right?
In version 1.11 (just uploaded), I no longer restore other lights when a profile is loaded--this should help with your problem, as long as you don't touch the other lights. Eventually, I may add an option to choose which lights get restored from a profile.
I originally made SuperDim for setting very low backlight settings on LCDs, and so I made it not work on non-LCD screens (e.g., OLED). But I've since realized that the profile feature might be useful for non-LCD users as well, so I've released version 1.20 that supports non-LCD screens. It's in Market. While I was at it, I cleaned up the code a little, made it more javaish (I'm new to java).
My MyTouch 4G just seems to turn the screen off totally if i go below 20 brightness, it dims but then shuts off.
Doesn't work at all with Dell Streak 5
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Awesome, thanks for the Advise!
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Screen filter merely adds a black semi-transparent overlay across the screen, making it look dimmer.
This app adjusts the backlight, which means darker black levels on the screen.
Frosty666 said:
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
Click to expand...
Click to collapse
My eyes don't care. +1 Screen Filter
lownox said:
My eyes don't care. +1 Screen Filter
Click to expand...
Click to collapse
Your eyes would probably care if you were doing amateur astronomy under a dark sky (which is the primary purpose for SuperDim). Screen Filter doesn't turn down the backlight, and on a lot of devices there is enough backlight leaking through even completely black pixels to damage night vision. You can try this experiment. Turn a backlit device to a completely black screen (maybe view a black jpg) and take it to a completely dark room. Let your eyes dark adapt. The "black" screen will in fact probably be quite grey. (If it's really black, that's probably because you have an OLED device.)
When I do amateur astronomy, I am not infrequently looking to see objects way dimmer than backlit black pixels.
I'd like to do something about the screen turning completely off issue.
To that end, I need people to do some experiments for me, and I will be very grateful (I'll also give a free full version of Force2SD as compensation for the first couple of experimenters, if you want it--just email me). The first experiment is this. Download SuperDim 1.22, now up in the Market. Press the menu key, and choose "Turn on safe mode" (you can tell safe mode is on, because next time you pull up the menu, it says "Turn off safe mode"). Now, turn brightness down to 10. Does your screen turn off?
I should warn that very low brightness levels can be very low indeed. For instance, if I am outdoors on a sunny day, I have trouble telling the difference between brightness 4 and off. So you need to be in a dark area--I recommend a room without windows and with the lights off.
If the screen does not turn off at 10, turn it down to 5, and then 1. Let me know if it ever turns off.
I am guessing that in safe mode, it doesn't turn off at all.
What safe mode does is it makes very low brightness settings not persist. So if you are in safe mode and leave SuperDim, you lose your low brightness setting.
I'd also appreciate it if people who can normally turn their brightness down to 1 could do some experiments with safe mode. Specifically, I'd like to know if moving the slider to 1 in safe mode has the same effect on screen brightness as moving the slider to 1 in non-safe mode has. (Again, if you're one of the first few experimenters and want a free copy of Force2SD, email me.)
On my Archos 43, brightness 1 is very, very dim, but the screen is still on. And I can't tell the difference between safe mode and non-safe mode, except that in safe mode, the settings don't persist after I leave SuperDim.
Tried this app on my desire HD.
Great idea, but when I reach 10 and below, the backlight doesn't get lower.
If I use the adb method (don't remember the command), I can set the backlight manually all the way down to 0.
There is no difference with or without safe mode on.
inspire 4g with coredroid V7.0 doesnt work
elmanortega said:
inspire 4g with coredroid V7.0 doesnt work
Click to expand...
Click to collapse
What happens? And does safe mode work?
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
kamranh3 said:
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
Click to expand...
Click to collapse
I found a bug. In fact, the bug is such that I have no idea how it was managing to work on my device at all! In any case, I think I fixed it. Try 1.23 (should be in Market or here) and see if it does the job. If not, I have some more ideas.
Finally got my app up and running on the Market and being a die hard xda user, I thought it would only be appropriate to post it here for fellow users to enjoy. =)
IntelliCover is a utility which uses your device’s proximity sensor to control its display and allow fast and efficient access to your phone or tablet.
It turns the screen turns off automatically when you put your device in your pockets, close its flip cover, store the device in a bag, or even just leave the device facing down on a table. As soon as the device is back in your hand the proximity sensor is triggered again, the screen turns back on and your phone is instantly ready for use.
IntelliCover is more feature-filled than any other similar application on the market. And the best part? It's FREE!
Click here to visit the market page and download the app for free
P.S. If you find a bug, I'd appreciate if you could report it to me before giving a bad rating because it usually only takes me less than a day to fix.
*** Features ***
Calibration:-
Proximity Sensor Delay – Add a delay to the time takes to trigger the sensor and turn the screen off.
Application Settings:-
Automatic Unlock – Automatically dismiss the Unlock Screen, provided there is no password. *Experimental*
Disable in Landscape Mode – Disable the proximity sensor when an application is in landscape mode.
Go to Home Screen – Show the home screen when the screen turns on.
Screen Off Only – The screen will turn off but not on when the proximity sensor is triggered.
Screen On Only – The screen will turn on but not off when the proximity sensor is triggered.
Start on Boot – Automatically start the IntelliCover service when the device turns on.
Notifications:-
Proximity Warning – Vibrate every time the proximity sensor is triggered.
Status Bar Notification – Show an ongoing notification in the status bar.
Screen On and Off Actions:-
Airplane Mode – Enable or disable airplane mode.
Auto Rotate (will be removed) – Activate or deactivate.
Auto Sync – Activate or deactivate auto-sync.
Bluetooth – Enable or disable Bluetooth.
Haptic Feedback (will be removed) – Activate or deactivate haptic feedback.
Ringer Mode – Switch ringer mode to Normal (Sound with Vibration), Vibrate or Silent.
Wi-fi – Enable or disable wi-fi.
*** Frequently Asked Questions ***
Q) Is it really free? Where are the ads?
Ans) IntelliCover is completely free and has no ads whatsoever!
Q) Do I require a rooted device to use IntelliCover?
Ans) Nope. IntelliCover works on all supported phones and tablets, rooted or unrooted.
Q) Doesn’t using the proximity sensor consume a lot of battery?
Ans) Actually, the proximity sensor consumes minimal power, almost little enough to be insignificant.
Q) What are the ‘Screen On’ and ‘Screen Off’ actions?
Ans) IntelliCover allows you to set events to be triggered when the screen turn on or off. For example, by setting wi-fi to turn on when your screen turns on and setting it to turn off when the screen turns off, you could save a huge amount of battery power.
Q) Can I request a feature?
Ans) Of course! Head over to the Contact section to drop me an e-mail.
Q) Why does IntelliCover keep running in the background?
Ans) It has to run in the background to know when the proximity sensor is triggered.
Q) Can I donate to the developer?
Ans) Not yet but hopefully I’ll have something set up soon.
*** Permissions Required ***
INTERNET - Required for error logging (to send crash reports)
WAKE_LOCK - Required to unlock screen
WRITE_SETTINGS - Required to toggle ringer mode
VIBRATE - Required to vibrate phone
RECEIVE_BOOT_COMPLETED - Required to detect phone boot
WRITE_SYNC_SETTINGS - Required to toggle autosync
READ_SYNC_SETTINGS - Required to toggle autosync
BLUETOOTH - Required to toggle bluetooth
BLUETOOTH_ADMIN - Required to toggle bluetooth
ACCESS_WIFI_STATE - Required to toggle WiFi
UPDATE_DEVICE_STATS - Required to toggle WiFi
CHANGE_WIFI_STATE - Required to toggle WiFi
*** Contact ***
Feel free to contact me at [email protected] with any issues, bug reports, feature requests, suggestions or queries. Please read the FAQ above before sending an e-mail to avoid redundancy.
Click here to visit the market page and download the app for free
Hello! I love the app! I just installed it, and it works great so far keep up your good work!
Sent from my HTC Sensation Z710e using xda premium
Seems good, some questions though.
1. Is it supposed to be able to turn the screen on? Take phone out of pocket, proximity sensor detects values that indicate there's nothing near (Sorry, dunno how / what values are calculated / used) and viola, screen on?
2. Dunno if I've set it up incorrectly. But, currently, if I turn on my screen, via the power button (Sony Xperia S), the stock lockscreen will show, and either one of two things will happen. Either I unlock it successfully, and the split second I'm completing the unlock, the phone will screen off, and engage the lockscreen - after unlocking this, can I get into my phone. OR it'll do what I've previously mentioned, without input.
timmy-kidd said:
Hello! I love the app! I just installed it, and it works great so far keep up your good work!
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thanks! Glad you liked it! =)
Profool said:
Seems good, some questions though.
1. Is it supposed to be able to turn the screen on? Take phone out of pocket, proximity sensor detects values that indicate there's nothing near (Sorry, dunno how / what values are calculated / used) and viola, screen on?
2. Dunno if I've set it up incorrectly. But, currently, if I turn on my screen, via the power button (Sony Xperia S), the stock lockscreen will show, and either one of two things will happen. Either I unlock it successfully, and the split second I'm completing the unlock, the phone will screen off, and engage the lockscreen - after unlocking this, can I get into my phone. OR it'll do what I've previously mentioned, without input.
Click to expand...
Click to collapse
Yup, it turns the screen on as well. The values are pretty much just FAR and NEAR for most proximity sensors, so once it detects that there's no object close to it, it should turn the screen on. If it's not turning on at all, that might be the root of the problem i.e. it might be causing the unlock issue as well...Hmmm...I checked out your phone specs and since you said "stock lockscreen", I think it's safe to assume you're on the stock ROM but are you still on Gingerbread? If so, that partially explains the issue. Some Gingerbread ROMs have compatibility issues with the app that are very similar to what you've described, I have no idea why but I'm still looking into it. I had to fix ALOT of Gingerbread issues to get it working this far lol. If you're not on GB though, I guess I need to hunt for an Xperia and begin testing/debuggin. :fingers-crossed:
HUGE update released! V2.0 Hope you all like it. =)
Thanks a lot for sharing your app, it looks grate but unfortunately it is not working with my Galaxy note 10.1
Sent from my GT-N8000 using XDA Premium HD app
I like it! Works fine in my SII stock rom. It will be perfect if i could enable a sound notification when turns off the screen. Not really necessary but cool 4 me (car unlock beep-beep)
Thanks mate!
Frank
thanks for the update
working good.
I'm working on adding a widget and changing the design, but if anyone has any better suggestions, I'd love to hear them because design is not as important as functionality.
Love it. great app, and working fine on both my LG Optimus 3D and Samsung Galaxy Note II.
could we have a choice on the notification icon, would be nice to have a small black dot or something. i just like a empty notification bar but understand the need for it to actually be in the notification bar
thanks
other than that this is my fav ap on my phone
won't this drain battery
mikeschevelle said:
could we have a choice on the notification icon, would be nice to have a small black dot or something. i just like a empty notification bar but understand the need for it to actually be in the notification bar
thanks
other than that this is my fav ap on my phone
Click to expand...
Click to collapse
Yea, it's unfortunate that foregrounding requires the notification icon. You could try using the app without foregrounding, it works for some people. Adding more notification icons should be easy, won't take much time. =) Which ones do you think I should add? A small black dot would disappear on most black status bars (but it'll look like there's an empty space in the status bar so it'll look a little weird)...
skyrocketeer said:
won't this drain battery
Click to expand...
Click to collapse
The proximity sensor uses very little battery and the app itself is pretty light (4-5MB RAM). So far I've only gotten one deep sleep complaint out of 3500+ downloads but no battery issues.
im fine with the black dot, it will keep my bar looking empty
mikeschevelle said:
im fine with the black dot, it will keep my bar looking empty
Click to expand...
Click to collapse
Finally! Found a way to completely remove the icon and the notification from the status bar when the app is foregrounded. It'll be in the next update (today or tomorrow). It can still be enabled manually from the Notifications section but yea, enjoy the emptiness of your status bar. xP
Pretty Huge Update. Hope you like it!
Version 3.0
-Added Screen On Fix for some phones (Enable in settings)
-Status Bar Notification/Icon will no longer automatically show up when app is foregrounded.
-Added Pocket Mode
-Added Table Mode
-Added Widget
-Fixed Screen On/Off Actions bug
One thing I notice (which is NO WHERE CLOSE to a big deal)
The launcher I use (Nova) I hide the status bar and use a gesture to bring it down. When ever Intellicover turns the screen on, the status quickly shows itself and then goes back hidden, not more than a half second of this, but I cannot select anything on the screen until after that status bar thing happens
I like the concept of the app, and it works fine with my sensors. I have one complaint though, I don't like how when the phone screen turns on, it opens to the Intellicover App. Sure I can set it to go to the home screen, but I don't always want that. Once Intellicover is running, I don't want to ever see it again unless I manually launch it from the app drawer. If I have Chrome open and I have to suddenly put my phone down or in my pocket, I'd like to pull my phone back out and have Chrome still be on the screen, just like happens now using the sleep button.
Turns my dumb flip cover on my note 2 into a smart cover. Thanks
Sent from my SPH-L900 using xda premium
garfnodie said:
I like the concept of the app, and it works fine with my sensors. I have one complaint though, I don't like how when the phone screen turns on, it opens to the Intellicover App. Sure I can set it to go to the home screen, but I don't always want that. Once Intellicover is running, I don't want to ever see it again unless I manually launch it from the app drawer. If I have Chrome open and I have to suddenly put my phone down or in my pocket, I'd like to pull my phone back out and have Chrome still be on the screen, just like happens now using the sleep button.
Click to expand...
Click to collapse
Actually, that shouldn't be happening. Once set you never have to see it again. I'm not quite sure what could be triggering this but if you could provide a little information about the OS/phone model/etc. I could try to get a hold on the device and try to replicate the error...
Hi,
I would like to use Tasker to control screen on/off times based on following conditions:
1) Keep screen on when reading/using mobile:
a)IF SCREEN IS ON: If handset is in vertical position (reading position), either in portrait or landscape depending on orientation set in android then screen should stay on. This would presume mobile is being used.
b) When handset is laid down on table then screen should turn off after 7 secs automatically or when screen is manually turned off.
note: It would be nice to have a window period of 10 secs after screen off wherein if the handset is picked up within that period, (after the initial 7 secs and before another 10 secs) then screen automatically turns on.
2) NOTIFICATIONS
If notifications are received, have a window period of 15-30 secs where if position of android is changed from desk horizontal to vertical then screen automatically comes on without the need to press power button.This presumes we picked up mobile to view the notification event.
Again first rule applies and screen stays on when reading and turns off auto or manually as per first rule
I have tried but not able to configure rules.
One conflict in mind:-
What if mobile is kept in trouser pocket and notifications are received? Here the gyro won't change as it will go from vertical to vertical position....how to deal with that? Also rule 2 should not auto trigger upon receiving notifications, sensing orientation is vertical when in trouser pocket.
Any help?
Thanks in advance
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
okty2k said:
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
Click to expand...
Click to collapse
Hi,
The problem with using the front camera is that it will cause battery drain. The camera would constantly have to keep checking for movement and this would definitely drain battery. I am more inclined to use the gyro for this.
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
okty2k said:
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
Click to expand...
Click to collapse
I could not get it to work thats why asking for help.