[Q] Control touch key backlight effectively? - Samsung Infuse 4G

Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!

AndyYan said:
Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!
Click to expand...
Click to collapse
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.

niral7 said:
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.
Click to expand...
Click to collapse
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.

niral7 said:
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.
Click to expand...
Click to collapse
Not even CM7? No dice then, I guess... Thanks for the tip anyway.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Related

Anyway to disable the capacitive button lights?

I read that CM7 will supposedly let you turn off the button lights (back, menu, search, and home), but is there a way to turn them off without it? Thanks.
Are you using a custom kernel with backlight notifications? Or do you just want the lights off all the time? If you are using a custom kernel with BLN you can use BLN Control from the market to disable backlight notifications.
I'm using it stock and want the 4 cap. button lights to turn off after a few seconds so I can watch videos in the dark (or have an app that I start that turns off the lights before I watch a movie).
Does BLN also disable capacitivte button lights (not just backlight notifications)? Are there other non custom rom solutions?
Backlight dimmer (BLD), one of Ezekeel's mods does this. It disables the capacitive buttons after x amount of time (variable you can set freely). But you need a custom kernel for this to work, not a custom rom. Check the developer section, most new kernel versions support BLD. Then, you can download NSTools from the market to set and configure the functionality.
BLN is only for notifications and blinking normally so it's not what you're looking for.
Greetz
edit: Check this: http://forum.xda-developers.com/showthread.php?t=1141233
frutelaken said:
Backlight dimmer (BLD), one of Ezekeel's mods does this. It disables the capacitive buttons after x amount of time (variable you can set freely). But you need a custom kernel for this to work, not a custom rom. Check the developer section, most new kernel versions support BLD. Then, you can download NSTools from the market to set and configure the functionality.
BLN is only for notifications and blinking normally so it's not what you're looking for.
Greetz
edit: Check this: http://forum.xda-developers.com/showthread.php?t=1141233
Click to expand...
Click to collapse
Awesome, that's actually even better. One question though, once the buttons/lights are disabled how are they re-enabled? Simply touching the screen? Thanks.
nope they'll stay off if you touch the screen. you have to touch the buttons themselves to get them to relight
v3rk said:
nope they'll stay off if you touch the screen. you have to touch the buttons themselves to get them to relight
Click to expand...
Click to collapse
Oh ok, perfect. thanks
Can someone point me to the correct file to download here for installing BLD:
https://github.com/Ezekeel/GLaDOS-nexus-s
Thanks
edit: the newest CM7 has the feature built in!! Thanks everyone
i've been looking for a way to disable the lights too! thanks!
drleospaceman said:
edit: the newest CM7 has the feature built in!! Thanks everyone
Click to expand...
Click to collapse
As a clarification, the feature is not available on 7.1.0.1 but only in the nightly later nightly builds. However, if you're running the stable mod, a workaround is to use Spark Mod Manager.

[i9020a] Problems with BLN

Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 8 on a I9020a.
I have a script set to enable blinking backlight notification by do this:
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
My problems are:
1) Sometimes after I've turned the screen off the soft keys are still sensitive to touch and when I touch one they all light up and stay lit up until i turn the screen on and off again. This seems to only happen sometimes. I haven't nailed down when exactly this happens.
2) Sometimes (more like rarely) the screen will be off and I will have a notification but the power button will not turn the screen on. It seems as if the OS is still running though because I can still hear when a text comes in. I don't know if this is the famed Sleep of Death because it seems like just the screen is off but it might be.
3) This is less critical but ties in to point 2). If I use the app SMS Popup, when I get a text the screen will turn on and then go off by itself, the lights will start blinking but then if I get another kind of notification (like an e-mail) I will hear the notification sound but will not be able to wake up the screen with the power button. Again it seems as if the OS is still running to some extent. This is consistent behavior and I've just uninstalled SMS Popup to avoid the problem.
It seems as if all the problems go away if I turn off BLN. I know the problem in 3) definitely went away because the behavior was consistent and I was able to test. I just love BLN so darn much that it's hard to live without.
So, has anyone experienced similar behavior to what is mentioned above? Does anyone know why this is happening? Is there some problem with my setup?
Thanks in advance.
I've had the same issues with some kernels like netarchy. Or matrix. I haven't figured out why it does that. Its weird.
Sent from my Google Nexus S 4G using xda premium
I run CM7.1 and I haven't installed the BLN kernel because for me the soft keys automatically light up and stay on until I turn the screen on. I do also have the problem with soft keys lighting up when screen locked if I bump them but it doesn't happen very often.
Esteway.619 said:
I've had the same issues with some kernels like netarchy. Or matrix. I haven't figured out why it does that. Its weird.
Sent from my Google Nexus S 4G using xda premium
Click to expand...
Click to collapse
Which ROM were you running with those kernels? I'm trying to nail it down to either the kernel or the ROM.
I had the same issue running Gummy with the matr1x kernel. Im trying a full wipe as I installed the kernel just wiping the cache. Might help, might not. Ill post results.
Does anyone know if there have been any solutions to this issue?
I am running the CM9 nightlies on my NS4G and I also find that the soft keys will light up after I turn off my screen. They don't go dark again until I turn the screen on an off again.

[Q] Make soft button lights stay on

Hi,
Is there anyway to make the soft keys stay on all the time when the screen is on? I searched all over for this answer and I found a bunch of apps and tweaks that work on other phones but none for ours.
My Light/Proximity sensor don't work , as I confirmed with androsensor. So my button lights never turn on. When I flash a new rom sometimes they work for a few hours or till I restart then never turn on again. They also work when im in recovery. I also just now tried a CM9 rom and found out if I adjust the brightness they lights turn on until I turn off the screen then they go off.
Only tweak I could find for our build.prop is
"ro.mot.buttonlight.timeout=0"
Which didnt help me.
Thanks in advanced
as i know you can control it with kernel file.but i dont know to edit it.ask it from a kernel developer (flaux, or sebestian)
Sent from my HTC Sensation Z710e using XDA
Thanks I'll shoot them a message
Guess I'll bump this thread with a little update.
Sent a PM to every kernel dev for the sensation.
1 is busy working on his first android app
1 is willing to research it and if he figures it out will compile something
1 is confident he could do it but is busy and its something he wouldn't want in his kernel.
Will update it if anyone succeeds and I know there are a few people looking for this feature.
I'm glad the community is responsive
HeXDeMoN said:
Hi,
Is there anyway to make the soft keys stay on all the time when the screen is on? I searched all over for this answer and I found a bunch of apps and tweaks that work on other phones but none for ours.
My Light/Proximity sensor don't work , as I confirmed with androsensor. So my button lights never turn on. When I flash a new rom sometimes they work for a few hours or till I restart then never turn on again. They also work when im in recovery. I also just now tried a CM9 rom and found out if I adjust the brightness they lights turn on until I turn off the screen then they go off.
Only tweak I could find for our build.prop is
"ro.mot.buttonlight.timeout=0"
Which didnt help me.
Thanks in advanced
Click to expand...
Click to collapse
@HexDemon:
Did you try this app? I've been running it and it fixes it perfectly (link below). My lights don't work at all otherwise. LeeDroid Tweaks will either turn them ON or OFF, not let them be controlled automatically. The newest versions of LD Tweaks (4.2/4.3) don't let them turn on AT ALL and the Devs are not interested in answering my questions there either. Other users have gotten involved though thank God, but no answers really.
https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5kZXNrYW5nZWwua2JsaWdodCJd
My Proximity and Light Sensors are also ****ed......and no fixes that work to date.
I'm willing to pay $$$ to whoever can find a fix that will STICK! (I am dead serious!)

Touch key brightness

Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/

[APP] Smartswitcher

The app is now on google play, get it there if you want it:
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5wZXJtby5zbWFydHN3aXRjaGVyIl0.
If you want to support the developer of this app you can get the prokey here:
https://play.google.com/store/apps/...EsImNvbS5wZXJtby5zbWFydHN3aXRjaGVycHJva2V5Il0.
Since this app is still very much in development you can see it as a donation, but a donation that gives you access to all the future development and features of this app. It will also give you start on boot and unlimited actions.
# What it does #
Basically what it does is it makes it possible to launch androids taskswitcher (recent apps) or call another action such as home, back, menu or turn screen off by waving your finger past the proximity sensor. You can also set an action to run when your proximity sensor is covered. With a little practice this really makes multitasking much faster. There is now also actions for media like volume, play pause and such, aswell as a flashlight (only tested on galaxy note, probably wont work on all devices) The media-actions are not properly implemented yet, so all actions may not work on all devices.
There is now some other features aswell.
Smart keep screen on will keep your screen on as long as you hold the phone in your hand. When you put it down, it will let the screen go off. I have only tested it on a galaxy note. Feedback on this would be welcomed.
You can now also run an action to keep the screen on permanently, or atleast until you run the action again.
Feel free to try it out.
# Instructions #
Configure actions for each number of waves up to six. The action you choose will then be executed when you wave.
You can also configure an action to launch when you cover your proximity sensor and for when the device is shaken.
If you have trouble with the gestures and smartswitcher recognizes the wrong gesture, you can adjust the gesture sensitivity. If you put this on low, the response and gesture recognition will be fast, but you will have to wave fast also. On high, the opposite is true. If you are not Lucky Luke like me, medium or high should work.
# Planned features #
Multiple actions for one event
Actions: toggle wifi, mobile data, bluetooth, launch apps, etc
Device facedown event
"Franticwave", action for when you wave past all six waves and then stop.
Suggestions, anyone?
# Known issues #
If the gestures stops working, particularly after using the screen off action, the gesturecounter probably consumed some magic mushrooms and forgot to count the waves and got all confused. You can either restart smartswitcher or wave until it starts picking them up again.
# Other #
The powerconsumption of the proximity sensor is extremely low so the impact on your battery should be fairly low. Did anyone using this notice a reduction of battery life, and I mean that in a more scientific way than just checking under battery in your system settings? Was it 5 minutes or 1 hour?
Zenblom made a video of smartswitcher:
He also compiled a list on working devices:
# Confirmed working devices #
- Samsung Galaxy Note GT-N7000
- Samsung galaxy s3 i9300 international version
- Samsung Galaxy Tab 7.7 P6800
- Sony Ericsson xperia neo v
- HTC One X
- Sony Ericsson Arc S
- Galaxy Nexus
- HTC evo 3d
- Samsung Galaxy s2
Thanks Zenblom!
# Changelog #
Version 1.1.7 2012-08-25
-Added cm10/JB compatible recent apps option.
Smartswitcher behaves really badly in cm10. Since everything worked great in cm9 that I just ran ten minutes ago I am not sure how to handle this. A use at your own risk warning for cm10 maybe?
Version 1.1.6 2012-08-23
- Added non root actions: Toggle airplane mode, launch browser, launch calculator, launch messages, send message, launch camera, launch contacts. Also end call, but it did not work properly so its set invisible for now.
Decided to freeze the features here, or this thing is never going on google play. If you cant find something seriously wrong with this version until tomorrow, its going on play. After that, I will continue developing the app but the updates will come via google play.
The smart keep feature... I may have to scrap that idea. I cant get it to work reliably. It can be made to keep the screen on on very small movements but then it wotn turn the scren off instead. Will fiddle a bit more before I give up. Its now set quite sensitive so it may not turn your screen off properly now, if so you can just press the powerbutton or disable the damn thing
If you have any ideas on how to make this work better, please let me know!
Version 1.1.5 2012-08-21
- Fixed the bug that caused to ui to crash or slow down when you were shaking the device. Should work fine now, so there should now be no need to close the ui when trying actions any more.
- The smartswitcher listening button will now completely (hopefully) unregister sensorlisteners so if you press this button there should be no batterydrainage at all.
- Made the handling of sensors a bit more effective. Now if you have no action on any event that need the accelerometer, it wont register and use battery power. If you set none on accelerometerevents the sensorlistener will unregister and stop using battery. The same goes for the proximity sensor.
I was hoping that the users with a glowing proximitysensor will tell me if I got this to work right
Version 1.1.4 2012-08-20
- Toggle wifi, bluetooth, rotation lock, ringer volume, audio volumeactions added. The do not need root and does things the right way. Audiovolume does not seem to work, will check why.
- Added something I called quick actions menu, but the first time its launched you may wonder why I did not name it slow actions menu After its loaded once it should work faster, it could slow down every once in a while, I will fix this. Note: if you cancel this menu strange things could happen, I forgot to implement oncancel. The plan is that you will be able to make these favouritemenus yourself and add the actions you want, and trigger your new menu on any event. I need a database handler som I have to fix this first. I never intended for this app to do all of this stuff, if I did I would have done things differently from the beginning. I noticed that this menu is counted as a pro action so you can only use it 20 times before it resets, sorry, did not mean for that to happen. For now there is only a few actions hardcoded in there.
Please close Smartswitcher settingsscreen before you start playing with the actions, strange things can happen if you dont. This is betastuff, so you cant expect things to be perfect even though I do my best for them to be as good as possible
Version 1.1.3 2012-08-18
- Added action keep device alive. If you run this, your device will not sleep until next time you run it, period. It wont activate if the device is already being kept awake by the smart keep screen on function, have not tested this very carefully. If you feel a burst of short vibrations, the device is being kept awake. If you use this, dont forget to turn it off, or it will drain your battery.
- Adjusted the shakedetection. It should now work much better and should notmake doubleactions. Try it and tell me if it is better or worse.
- Adjusted the smart keep screen on function to a little less sensitive. Sometimes it did not turn the screen of because i set the sensitivity too high so it detected movement event when it was fairly still. Try it and tell me if I made it better or worse.
- Added support for up to six waves by request. Tested it some, it seemed to work fine.
Version 1.1.2 2012-08-17
- Added action flashlight. Will probably not work on all devices, but it works on my note atleast. Will add more variants for other devices.
- Added EXPERIMENTAL Smart keep screen on function. There is no adjustable settings yet, just on and off. You can try it by setting your screen timeout at a low value like 15 seconds. As long as you hold your phone in your hand, the screen should keep on. If you put it down the screen should go off in 30 seconds or so. I adjusted it to work on my device, but that does not mean it will work good on yours. There is no settings for it yet. Try it, if you dont like it, disable it. Will also spend some time on next version with the shake detection, Its teally not what I wanted it to be. It works, but barely.
Version 1.1.1 2012-08-16
- Added shakedetection. You can now set an action for shake. Note: Will cause the ui to crash, press backbutton to close smartswitcher settings before using it and it should work fine.
Version 1.1.0 2012-08-15
- No visible changes, but lots of changes in the code. I hate spagetticode, so I spent some time removing and rewriting things. Sensorcovered will now really have zero delay if you set that.
- Made the number of proactions allowed to 20, as I said I had done. It seems it was only 10
Version 1.0.9 2012-08-13
- Fixed sensor covered, now it wont trigger any action if you remove your finger within the delay time.
- Added a BUNCH of actions. Some will work on your device, some will not. (Depending on rom, installed apps etc) The new features are for the pro version (Yes I will make a pro version.) I am a nice guy so everything you had before still works, plus you can use the profeatures for a total of 20 times, after that they will reset to no action. You are free to select pro features again for another 20 times. Sorry about this, but I have spent quite a few hours on this app now, and I would not mind getting a few bucks for my work. Please tell me what price you find fair for this app, if any price at all
- Made it so that gestures will work on active phonecall. This means actions like for instance hangup will actually hangup the call. Sensor covered should not interfere with anything now.
Version 1.0.8 2012-08-11
Note: Remaining bug, sensor covered works but the delaysetting does not do what it is supposed to do. That is, even if you remove your finger from the sensor within the delay time, the action will still trigger. Sorry about that, will fix. Too tired now
- Fixed the bug that caused settings to not save after a while. Should work fine now.
- Added configurable settings for sensor covered so you can now set any action for that event. If you have a device with slow sensor you should now be able to launch recent apps by setting sensor covered delay to 0 and action to recent apps. You can now also set screen off as action on any wave.
- Fixed vibration feedback for sensor covered event.
- Removed Screen off setting as it is no longer needed.
- fixed some other bits and pieces and cleaned up the code.
Version 1.0.7 2012-08-09
- Completely rewrote all of the code for taking care of actions. If I am lucky this will take care of the strange superuser permissions error. Unfortunately this way will mean an ever so slightly slower response, but if it turns out this way works better, I will see if I can speed it up some.
- Lots of bugfixes. Wavesettings and gestures off in landscape SHOULD work properly now. So SHOULD the screen off feature.
- Added button to stop Smartswitcher from doing anything at all. Now, please tell me what I have broken this time
Version 1.0.6 2012-08-08
- Added settings for all gestures. You can now disable/enable/configure individual gestures. I did test this, but not very carefully. I should stop doing this so late at night. Please tell me if you find problems.
Version 1.0.5 2012-08-07
- Added option to disable gestures when phone is in landscapemode. Now you dont have to kill smartswitcher if you find it unusable in landscape and then start it again when back in portrait. Let me know if it does not work as intended.
- Changed the vibrationfeedback on recognized gesture to a more gentle level.
- Find my sensor-mode is gone. Kind of useless feature anyway, good riddance to bad feature.
Version 1.0.4 2012-08-06
- Wave once for recent apps, twice for menu, three times for back, four for home. No customizable settings for this yet, I need to sleep now Oh, I broke find my sensor-mode.
Version 1.0.2 2012-08-05
- Configurable delay for the screenoff when sensor covered-feature added
Version 1.0.1: 2012-08-04
- Disableoption for screenoff "bug"
- Changed Get the feel-mode to Find my sensor-mode, hopefully this is not as confusing
More coming. If you have any ideas or suggestions, let me know.
ssspeq said:
Hello!
I made a little app that I am not sure if anyone but me will like. Basically what it does is it makes it possible to launch androids taskswitcher (recent apps) by waving your finger past the proximity sensor. With a little practice this really makes multitasking much faster. Atleast, thats what it did for me. I was hoping for some testers here on xda. I have only tested this on a galaxy note running paranoid, it seems to work fine on that rom on the note, but i would like to see some more testers.
Feel free to try it out. If anyone likes it i will put it on google play. By the way, you need root for it to work. I attached a full version except for autostart on boot that will not work in this version.
Click to expand...
Click to collapse
Well it vibrates but does not launched recent apps.
I like the ide Of it
CoopZor said:
Well it vibrates but does not launched recent apps.
I like the ide Of it
Click to expand...
Click to collapse
The fault may be mine, but just to be overly clear, you have to wave your finger past the sensor AND back again within a relatively small amount of time. Maybe you did that.
What is your phone running?
Hi,
I've been testing both an earlier version and current version and it works fine for me. Could be that I'm also running paranoid (v0.5) on a note.
I shot a video on an earlier version:
www youtube com/watch?v=gsIFtIxhD1g
(I'm not allowed to post links yet so you go figure)
Just tested it on stock LRG with CF-Root kernel. Works well.
AndroidGreenHorn said:
Just tested it on stock LRG with CF-Root kernel. Works well.
Click to expand...
Click to collapse
Cool! I hope it will be of some use to you. Thanks for testing!
Is this battery friendly? I love the idea and if it doesn't drain my battery quicker than usual I'll be using it instead of the long click of home button.
Please add an option to hide the notification icon. I don't think there is a need for it as this is a set it once and forget about it app. You don't go changing the settings every day.
Thank you and good luck with this awesome project!
EDIT: btw, I'm running stock rooted 4.0.4 and this works great!
Oh god that's a great idea ! Way faster than long-pressing home button. It works like a charm on jellybean cm10.
Sent from my GT-N7000 using xda app-developers app
moyajaya said:
Is this battery friendly? I love the idea and if it doesn't drain my battery quicker than usual I'll be using it instead of the long click of home button.
Please add an option to hide the notification icon. I don't think there is a need for it as this is a set it once and forget about it app. You don't go changing the settings every day.
Thank you and good luck with this awesome project!
EDIT: btw, I'm running stock rooted 4.0.4 and this works great!
Click to expand...
Click to collapse
I was expecting someone to tell me to remove the notification icon I know, It was really useful get to the settings quickly when I was developing it. I will see what I can do to remove it. As for the battery, I have not really noticed any change in drainage at all, but please tell me if you experience any bad impact on battery life.
Thanks for testing!
CreepyDroid said:
Oh god that's a great idea ! Way faster than long-pressing home button. It works like a charm on jellybean cm10.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Excellent! Wave on
One small notion i made: I recently installed WidgetLocker and it's possible to swipe your finger for recent apps while the lockscreen is active/visible. Not that it's disturbing but it's good to know! In ics lockscreen everything works as intended!
Doesn't work on mine unfortunately....I'm on LRG
Only vibrated
Sent from my GT-N7000 using xda premium
zenblom said:
One small notion i made: I recently installed WidgetLocker and it's possible to swipe your finger for recent apps while the lockscreen is active/visible. Not that it's disturbing but it's good to know! In ics lockscreen everything works as intended!
Click to expand...
Click to collapse
I am actually aware of this problem. I have sent an email to the developer of widgetlocker but no answer yet. I could not find a way to detect when widgetlocker was running so i could disable smartswitcher. I will keep trying to fix that issue. Thanks for letting me know!
DMax99 said:
Doesn't work on mine unfortunately....I'm on LRG
Only vibrated
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thats a bit strange. It worked for a previous poster on LRG if I am not mistaken. I don´t mean to offend you, but are you sure you are doing it right? Set the sensitivity to high and try a few more times. If you enable the somewhat strangely named Get the feel mode, the phone will vibrate a little when it "sees" your finger, thats just to help you find the sensor. The Vibrattion setting will make the phone vibrate a little longer when you waved correctly. If you cant get it to work, let me know and I will try to help you get it working.
ssspeq said:
Thats a bit strange. It worked for a previous poster on LRG if I am not mistaken. I don´t mean to offend you, but are you sure you are doing it right? Set the sensitivity to high and try a few more times. If you enable the somewhat strangely named Get the feel mode, the phone will vibrate a little when it "sees" your finger, thats just to help you find the sensor. The Vibrattion setting will make the phone vibrate a little longer when you waved correctly. If you cant get it to work, let me know and I will try to help you get it working.
Click to expand...
Click to collapse
No matter how I slavery finger over it (fast or slow), it just vibrates and nothing happens....I'm on the stock LRG kernel.
Sent from my GT-N7000 using xda premium
You must de-select "get the feel"mode in the app menu, otherwise out only vibrates
Carefully crafted on my Galaxy Note, for your eyes only
I installed it minutes ago,
and it works great.
Switched to high.
I'm on classic rom v3.
Only thing is, deactivate vibration and feel mode, but still feedback with vibration.
sent from my G-Note
Not working on cleanote rom really like the idea though!
Will be keeping up to date with this for sure!
Sent from my GT-N7000 using xda premium
What a great app. Works perfectly. Stock lrg with cf root kernel
Works perfectly on Asylum. CM9 after a bit of practice. Thanks :thumbup::thumbup:
Sent from my GT-N7000 using xda app-developers app

Categories

Resources