Database Users

[APP] Smartswitcher

Check out main thread here:
http://forum.xda-developers.com/showthread.php?t=1803902
# 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. If media controls is what you really want, I think wave control is your app. They have media controls implemented properly.
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 #
Suggestions, anyone?
# Known issues #
FIXED?
Sometimes Smartswitcher does not get superuser permissions at first try, if you are rooted and you are sure it should work on your device, this may be the problem. I am not sure why this is as it has never happened to me, but a few users have reported that installing it again or using supersu fixes the problem. Will try to get this fixed.
# 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?
If you dont have root or smartswitcher wont work, please buy the excellent app wave control. (Or if you simply like it better)
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
Thanks Zenblom!
# Changelog #
Version 1.1.3
- 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
- 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 really not what I wanted it to be. It works, but barely.
Version 1.1.1
- 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
- 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
- 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
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
- 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
- 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
- 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
- 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
- Configurable delay for the screenoff when sensor covered-feature added
Version 1.0.1:
- 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.

Nice idea...but on my HOX screen goes off waving past proximity sensor...BUT really nice idea!!

Work with me fine , but I must wave to lunch it
Thank you
Sent from my GT-I9300 using xda app-developers app

HISOON said:
Work with me fine , but I must wave to lunch it
Thank you
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Cool, what phone do you use?

Samsung galaxy s 3 international version
Sent from my GT-I9300 using xda app-developers app

didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note

oaz63 said:
didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note
Click to expand...
Click to collapse
If it is rooted, it really should work. There is a bit of a trick to it, you have to wave your finger past the sensor and back within a fairly short amount of time. I did this because if I launched recent apps when you just come close to the sensor once, it launched when I did not want it to and was more of a pain than it was useful. Try setting the sensitivity to high and try a few more times. If it does not work then, we will have to figure out why. Plenty of people has tested it successfully on the note, thats why I am fairly sure that it should work but I could be wrong.

ssspeq said:
If it is rooted, it really should work. There is a bit of a trick to it, you have to wave your finger past the sensor and back within a fairly short amount of time. I did this because if I launched recent apps when you just come close to the sensor once, it launched when I did not want it to and was more of a pain than it was useful. Try setting the sensitivity to high and try a few more times. If it does not work then, we will have to figure out why. Plenty of people has tested it successfully on the note, thats why I am fairly sure that it should work but I could be wrong.
Click to expand...
Click to collapse
Stock NEE 4.0.4 on galaxy note,
Doesn't work :/ (rooted)
Sent from my GT-N7000 using Tapatalk 2

Racle90 said:
Stock NEE 4.0.4 on galaxy note,
Doesn't work :/ (rooted)
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Would you mind doing a logcat for me while you try to wave at the sensor? It has worked for the majority of testers, I need to figure out why it does not for a few. No hurry, I wont have the time to look at this for a few days anyway. Thanks for testing!

ssspeq said:
Would you mind doing a logcat for me while you try to wave at the sensor? It has worked for the majority of testers, I need to figure out why it does not for a few. No hurry, I wont have the time to look at this for a few days anyway. Thanks for testing!
Click to expand...
Click to collapse
Here's your logcat, (looks like spamming the same message, probably triggers the event (?) but doesn't execute that)

Tried on xperia ray. Doesn't work. Just vibrate that's all. Will attach logcat if possible.
Edit : not sure if I'm doing it right, but this is all I get.
l/Smartswitcherservice(27913): Räknare:1
I/Smartswitcherservice(27913): Räknare:2
I/Smartswitcherservice(27913): Timer done

Absolutely amazing idea. Sometimes it does shut the screen off, though. Other than that, it works perfectly on the S3.
Thanks for this.

Nice idea
But On HTC desire and Sony Live with Walkman
It just vibrates and turns the screen off

frenzyboi said:
Tried on xperia ray. Doesn't work. Just vibrate that's all. Will attach logcat if possible.
Edit : not sure if I'm doing it right, but this is all I get.
l/Smartswitcherservice(27913): Räknare:1
I/Smartswitcherservice(27913): Räknare:2
I/Smartswitcherservice(27913): Timer done
Click to expand...
Click to collapse
You are probably doing it right, its not that hard, most likely the sensor on your xperia ray is not updating its values fast enough. Räknare is swedish for counter You will need to get it up to 4 counts to trigger recent apps.If there are enough people with slow sensors Ill see if I can fix some other way of triggering it, maybe just covering the sensor but I am not sure if thats going to be useful. I dont have access to my computer right now.

fire_kid2003 said:
Nice idea
But On HTC desire and Sony Live with Walkman
It just vibrates and turns the screen off
Click to expand...
Click to collapse
The screen off thing is something that should not be there. I forgot to remove it after a failed experiment with a screen off feature, will be removing that. If you could check logcat while you try waving I would be happy. If you see something like the poster with a xperia ray, its probably the same problem.

This is working nicely for me. Sgs3 internationsl i 9300. Wanamlite rom.
I switched sensitivity to low and i think is better.
What i want ask. How is this for the battery and the sensor itself?
I think that this will fry it after some time.
Anyhow great thinking.
Sent from my GT-I9300 using xda premium

oaz63 said:
didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note
Click to expand...
Click to collapse
same here but with Motorola Defy

mariosraptor said:
This is working nicely for me. Sgs3 internationsl i 9300. Wanamlite rom.
I switched sensitivity to low and i think is better.
What i want ask. How is this for the battery and the sensor itself?
I think that this will fry it after some time.
Anyhow great thinking.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I have not noticed any negative impact on battery life, maybe someone else has, nobody has had any complaints about it so far. As for burning out the sensor, I dont think thats much to worry about. I used the sensor on my n900 for this for a very long time and its still working, although other parts of my beloved n900 has broken but not the sensor. If it makes you worried it might be best to not use this.

Downloaded the apk from galaxy note forum and it's working
Sent from my GT-N7000 using Tapatalk 2

Racle90 said:
Downloaded the apk from galaxy note forum and it's working
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Cool! Its the same apk, but whatever makes it work is good

Wake Lag?

I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.

One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk

Ibkevin said:
One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Nice tip. In all my years of Android tweaking, I've never come across that one. I don't need fancy screen on/off animations. I prefer quicker response time. Thanks.

This phone is fast enough to where you should be able to do screen on animation with no lag. I'd try wiping cache before disabling anything
Sent from my SM-N900V using xda app-developers app

noticed too
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I have noticed this too... bugs the hell out of me. i tried putting animations to .5 cause i think it makes the phone look like crap when set to 0, helped a little bit but it is still there.

I noticed this last night. I was missing the swipe to unlock because it was taking so long. Seems ok now, though.

I found a slightly faster response with the three animation options set to 0.

I think its a touchwiz thing my s4 did it stock and it went away with Hyperdrive rom but it came back when I was on cynanogen mod. I feel like my I wore out my power button lol it is a little loose.
Sent from my SCH-I545 using xda app-developers app

Its a Samsung thing with the processor. The Note 2 was the same way. The easiest way explained to me awhile back....once your screen goes off...and all stuff running finishes up...you essentially enter Deep Sleep. It's a battery saving feature...if you will.
Manually turn off your screen, then like..2 seconds later, turn it back on. Should be virtually instant. Now do the same thing but wait 2 minutes....lag.
It is 'kind of' annoying, but I'll deal with it for the sake of battery life.
Now that we have root, you can always try to adjust governors and kernel settings to help it, but until we're able to use other kernels, it's gonna pretty much always be there, the lag, that is.
Hope that helps explain a bit.

The only way around it on the Note 2 was to force a wake lock, basically it never enters deep sleep. You may be able to use an app to do it as well, such as: https://play.google.com/store/apps/details?id=eu.thedarken.wl
MikeyXDA was an advocate of the method and explained it really well on his MeanBean ROM for the Verizon Note 2. You just take a slight hit to battery, but at least there's no wake lag.
Here's the thread: http://forum.xda-developers.com/showthread.php?p=543135
Sent from my SCH-I605 using XDA Premium 4 mobile app

I have absolutely no wake lag on mine at all. I was expecting it like my Note 2 but I hit the button now and it's just on instantly.

Wake lag with sd card
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I'm having a problem with wake lag bad sometimes - several seconds. Mine seems to be connected to the sd card. I have a 32 gb card I used in my note 2 with no problem, it's and sdhc i think. I cleaned it down to 8g of stuff on it and put it in. It kept causing note 3 to dis mount the card each time I turned it on; had a little message at the top left. Much of the time the card would stay dismounted. When I finished a call the screen would not come back on for a long time, couldn't end the call. Took the sd card out, problem resolved. Backed up the sd card, put it in the N3 and formatted. Got better results although still doing it some. I'm wondering if I'm going to have to get a new sd card or trade in for a new note 3.
Any thoughts. I would check the sd card if you still see long lags.

Try to freeze/remove S Voice if you rooted because S Voice is mapped to double tapping the home button. This helped me out a lot on the Note 2 and I removed it already on the Note 3 without comparing lag difference already

Touchscreen sensitivity

Been using the 2nd gen Moto G for a week and I've noticed the touch screen isn't as sensitive/accurate as my previous phone (NEXUS 4). For example, when I scroll (in Facebook, Chrome etc.), the app opens links and images if my thumb is over either one. It's the same with gallery. If I were to scroll then halt, it'll open the image under my thumb. It's doesn't happen often, but enough to take notice. I have to press slightly harder (compared the NEXUS 4) for the Moto's touch screen to register accurately. Can't use light touches reliably at all. Has anyone experienced similar/same issue?

Not an issue with me like this
Works fine

It is by no means bad, but it takes a little bit of getting used to. I'm guessing they'll fix it via OTA if it needs fixing.

I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.

anshumandash said:
I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.
Click to expand...
Click to collapse
Glad I ain't the only one. Hopefully it is software related and can be addressed via update

I have this only when I charge my phone with a specific wall adapter, everything else is fine

Gabboplano said:
I have this only when I charge my phone with a specific wall adapter, everything else is fine
Click to expand...
Click to collapse
Strange, I didn't notice this issue before yesterday's OTA.
Will try other another wall adapter.
I'm currently using the Sony/Ericsson LwW adapter (5V/800mA).

My Moto G 2nd Gen had this issue too, but it also had problems where occasionally the touch screen would interpret scrolling as tapping and vice versa, in the end, I had to RMA it.

I had mentioned earlier that sometime scrolling would consider as tapping and would open apps/links etc. Some time tapping needed multiple taps. I just removed the screen guard and this problem is mostly not noticeable any more. Just thought this information might help some one.
My phone came with the official charger of 550 MA and I don't get any screen freezing while the phone is charging with it.

Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5

sahil kaul said:
Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5
Click to expand...
Click to collapse
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.

anshumandash said:
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.
Click to expand...
Click to collapse
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5

sahil kaul said:
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5
Click to expand...
Click to collapse
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.

delete please

anshumandash said:
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.
Click to expand...
Click to collapse
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.

touch sensitivity
this problem appeared once, after an update from motorola.
Factory resetting it solved the problem xd

Nielo TM said:
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.
Click to expand...
Click to collapse
I completely agree with you. This phone has got two coatings. One called splash resistant and the the other is finger print resistant coating. I think those are another cause the finger doesn't glide well on the screen. I am also coming from Nexus 4 and I can feel this problem every time as I still carry the N4 with me. I too ran touch screen tests and everything looks fine. I am not sure if I RMA how will the 2nd device behave. It might be same. I can actually replace it from Flipkart.com from where I bought, but I am not sure if that will help.
I read some review comparison between the new moto g and new moto x and the reviewer has commented that Moto x 2014 screen is far more responsive than the moto g 2014. I know the problem was real bad with the stock screen guard on the screen. If I need to manage with the phone, I know I will have to use the phone without a screen guard.
I tried using ART as I have been using that on my N4 since Jan 2014. But in Moto g the app optimization starts at every boot with ART taking more than 10 mins for every boot. I wrote a mail to Moto support and they said there is a technical problem with the builds and they suggested me to use Dalvik. I think they won't fix it till Android L drops in.

DoubleTap to Lock/Wake while using Apex Launcher

My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.

Double tap to wake works for me with Google Now launcher and Nova (free version). Double tap to sleep (lock) doesn't work with either. Works fine both ways with the stock Idol launcher. Looks like you may have discovered a work around.

stl1859 said:
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Click to expand...
Click to collapse
Nova Launcher has an identical gesture/setup. [ which I'm using in same way with the "Screen Off" app since the phone auto locks when the screen goes blank. ]

I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.

JJ2525 said:
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
Click to expand...
Click to collapse
Same here, NOVA launcher premium

My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.

maddog497 said:
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
Click to expand...
Click to collapse
Exactly the same situation here.

Borghi said:
Exactly the same situation here.
Click to expand...
Click to collapse
I'm spoiled with the G3 and the Zenfone 2. They both work flawlessly.
Hopefully this gets fixed in an update.
Sent from my LG-D852 using Tapatalk

Thank you very much dude, I'm hoping to root ASAP still haven't found a reliable way to. I wish this device had a bit more ram but pretty good so far. I hate not being rooted just because I can erase anything on the external SD and hopefully with a custom Tom the screen Issues with the phone not waking gets fixed

You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk

Shodan5150 said:
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Click to expand...
Click to collapse
Sorry it took so long fopr me to get back here to post the link. I had PC issues and had to install Windows and then the hardware drivers for the AMD card gave me a fight. But you prolly already found the thread but the thread is below.
http://forum.xda-developers.com/idol-3/help/install-to-sd-card-root-access-t3119374

New discovery
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.

stl1859 said:
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
Click to expand...
Click to collapse
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.

maddog497 said:
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
Click to expand...
Click to collapse
Since the time I arrived at this theory, I have tested it again and again - and I can confirm that it is always doing it. You just have to be really really patient to see this in action. Forget what I said about 10 seconds ; sometimes you have to wait for more than a minute. It is weird - you double tap - then just stare at the phone for ages and suddenly out of nowhere the screen lights up.
If D2W is important for you , then my discovery does nothing for you - It is still broken. So you did the right thing in returning it. As far as updates go, again if that is important for you, then you did the right thing. Honestly I do not expect many ( if at all ) updates from TCL. From what I understand, they do not have the kind of software development infrastructure that Asus does . And that is evident from the extent of skinning that Asus did on top of Lollipop whereas the Idol3 was mostly a stock experience. IMHO - right now - more than updates from TCL, we need root , so that developers can do their own thing with the phone.

I have since installed a proximity sensor based wave-to-unlock app. Not only does it work very well, it also allows me to lock the screen back, from the lock-screen itself, something that is missing in the default D2W setup. The only downside is the additional power consumption by the proximity sensor. Since it is supposed to use only 3 mA , I am hoping it is not going to be too bad, but I will watch out for it. If the battery performance does not degrade too much, then I think I can kiss D2W goodbye.

I sent an email to Altatel Tech Support about a week ago and asked them if they are aware of the DTTW issues and working on a fix. I received a reply stating that they are aware and are working on an update. My guess is that they will try to combine multiple fixes into a single update. It may take a little longer and it is too bad that Alcatel is not better at communicating with its customers. It would make no sense for Alcatel to ignore all of the customer complaints here, on Amazon, and in various reviews and do nothing. They are spending cash marketing this phone and they must be smart enough to know that their sales will tank if they ignore the issues.

Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en

japhule said:
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
Click to expand...
Click to collapse
I tried this app and it seems to improve lag time when you open an app too! Great find!

OTA
An official OTA update has just been announced to fix the DTTW
Borghi said:
I tried this app and it seems to improve lag time when you open an app too! Great find!
Click to expand...
Click to collapse

Second Screen Lag

Hi everyone,
Has anyone noticed a second screen lag when swiping it around while the main screen is off? I only have the quick toggles and music player on my second screen when the main screen is off. But regardless of any direction you swipe it, there is a VERY considerable lag as it navigates to the next item. For those who previously had the LG v10 and are currently using the V20, I'm pretty sure you've noticed that the swipe on the V10 was very swift. I'm asking out of curiosity if anyone else has had this issue. It's possible that due to first batches of V20s available to the public, these units are suffering from it? Idk, I just want to hear your thoughts if possible. Thank you!

I'm experiencing the same thing.

Not mine, I have also the music player active and actually is pretty snappy.

no problems here. I'm not saying there's never been a lag, but generally not a lag on my Tmo version.
Sent from my LG-H918 using Tapatalk

When Pandora is playing the 2nd screen is noticeably laggy for sure. It doesn't impact how quick I can scroll around but it doesn't look great. Doesn't really bother me since the 2nd screen is too locked down to be that useful. I just leave it on Pandora controls or date/time

Yeah I'm seeing it too. Most of the time I need to double swipe it then it would jitter to the left when playing music. When not playing anything, it still has basic lag when screen is off.

Im noticing the same lag on mine as well when the main screen is off. Maybe something to do with battery saving.

Try this
Settings/Developer Options/ Tick on "Force GPU Rendering" this should make your beast smoother/snappier!
If root available try L Speed/Entropy/fstrim apps found on Play Store! LG V20 & LG G5 are both snappy beasts and most anticipated of 2016! They are well optimised with Snapdragon 820 and is better than Samsung.

I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk

beast330001 said:
I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?

saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk

Pick_A_Name said:
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?

saqc2010 said:
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?
Click to expand...
Click to collapse
Honestly I didn't notice the lag until this thread pointed it out. Probably because I've had Samsung devices for so long that lag is just part of life. Since factory resetting it, I've noticed it just runs better in general and not just the second screen lag.
Sent from my LG-H918 using Tapatalk

saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
The second screen lag hasn't returned for me after the factory reset. It swipes left or right very quickly.
I do get a random lag from several hours/days uptime on the regular screen though. A restart fixes that lag for me.
Sent from my LG-H918 using Tapatalk

My screen was lagging so I reset all the defaults that go with the second screen and it now runs smoothly so long as my battery percentage is above 25%.

Almost 3 weeks and I've experienced no lag at all on second screen, always fast and fluid however it's been set up.
@Olivia1234
I'm curious why you think battery % would make any difference. Have you actually confirmed it does?
And welcome to XDA.

Same here. I am having lag on stock and now running mega rom on my 918. I have to swipe a couple of times and then it will skip the toggles I want ? maybe it's meant to be laggy so toggles aren't pressed by accident? Or so it's not swiping back and forth in your pocket??...either way it's very annoying

Nah mate, you not read my post above yours?
It should behave the same as main screen, be dumb to purposely make it behave like yours is.

Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on

KUSOsan said:
Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on
Click to expand...
Click to collapse
I've experienced that exact same thing. Sometimes I try to unlock it to fast and it just locks again no big deal for me though. I just ran across an issue running MegaRom.
Not sure if it has anything to do with the room though anyway the quick tools on the second screen are gone. If you scroll from the signature to the quick tools menu it's just black if you tap where the icons should be they work it's just like they are invisible or black I'm thinking it might have something to do with Nova launcher but I'm not sure I've played with the settings in Nova for about a day and it hasn't changed.