Do you guys also have this issue with the screen taking 2-3sec to wake up after the phone stats ringing on incoming calls? Or is it only me? Do you guys have a fix? Or is it because I have exdialer installed?
I find there is a delay with it sadly
Sent from my LG-D802 using xda app-developers app
DialerEx was probably the cause. Uninstalled relieved partially the issue
I had this problem but i think having Go power manager lower my cpu caused it. I turned that off and it seems like i don't have the delay anymore
It depends greatly on your governor and CPU hotplug - I am using Ondemandplus with a 1 Ghz screen off frequency and Intelli hotplug. I get about 2-3 seconds of delay from when my phone vibrates to when the screen comes on (I use a QuickWindow case), but I was surprised today to find the screen instantly on when receiving a call.
Anyone find a fix for this yet?
*WARNING: Do not manually set your screen off frequency lower than 1Ghz. This will cause screen wake on call issues*
I get near instant screen wake on call with this and anyone is welcome to test it out.
Added the xml as an attachment that you can just extract and import directly into tasker!
Requirements are:
-Must be rooted
-Tasker app
-Secure settings app
Profile: Force Screen On Call (46)
State: Display State [ Isff ]
State: Call [ Type:Incoming Number:* ]
Enter: Anon (47)
A1: Secure Settings [ Configuration:Screen & Keyboard Lights On
1 Second Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
Nice work
This does the trick,but it has a slight bug. My lockscreen wallpaper appears before the contact who is calling. Is this normal ?
demoncamber said:
*WARNING: Do not manually set your screen off frequency lower than 1Ghz. This will cause screen wake on call issues*
I get near instant screen wake on call with this and anyone is welcome to test it out.
Added the xml as an attachment that you can just extract and import directly into tasker!
Requirements are:
-Must be rooted
-Tasker app
-Secure settings app
Profile: Force Screen On Call (46)
State: Display State [ Isff ]
State: Call [ Type:Incoming Number:* ]
Enter: Anon (47)
A1: Secure Settings [ Configuration:Screen & Keyboard Lights On
1 Second Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
Click to expand...
Click to collapse
I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801
demoncamber said:
I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801
Click to expand...
Click to collapse
That would be really cool thanks
demoncamber said:
I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801
Click to expand...
Click to collapse
Did you manage to solve something with the wallpaper appearing before caller? Really annoying, and it's almost perfect [emoji12]
metalboy94 said:
It depends greatly on your governor and CPU hotplug - I am using Ondemandplus with a 1 Ghz screen off frequency and Intelli hotplug. I get about 2-3 seconds of delay from when my phone vibrates to when the screen comes on (I use a QuickWindow case), but I was surprised today to find the screen instantly on when receiving a call.
Click to expand...
Click to collapse
Awesome
I actually have a bit of a better more optimized profile now. Attachment XML incoming. What this actually does is allows you to set as low as you want screen off cpu frequency in the first part, and then when the phone rings it will boost the cpu to max set frequency, or anything you want to set it to manually above 1GHz will work.
First things first, download the attachment, then first import the 3 files ending in tsk.xml into tasker, they should show up in your tasks section, then import the one ending in prf.xml
Then you can set whatever frequencies you want for your screen off max freq in "display off cpu" task in tasker, this can be basically anything. Then you can open the "Wake_On_Ring" task and set that max freq to anything ABOVE 1000mhz. I have it default set at 1.9GHz and it works almost instantly for me on call. But it's up to you. After that, everything is good to go.
Here's what it looks like:
Profile: Display Off Wake On Ring (27)
State: Display State [ Is off ]
Enter: Display Off Ring Manager (52)
A1: Perform Task [ Name display Off Cpu Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq OFF ]
A2: Perform Task [ Name:Wake On Ring Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq ON ]
Can't wait to give it a try, I will give you feedback regarding this soon
demoncamber said:
I actually have a bit of a better more optimized profile now. Attachment XML incoming. What this actually does is allows you to set as low as you want screen off cpu frequency in the first part, and then when the phone rings it will boost the cpu to max set frequency, or anything you want to set it to manually above 1GHz will work.
First things first, download the attachment, then first import the 3 files ending in tsk.xml into tasker, they should show up in your tasks section, then import the one ending in prf.xml
Then you can set whatever frequencies you want for your screen off max freq in "display off cpu" task in tasker, this can be basically anything. Then you can open the "Wake_On_Ring" task and set that max freq to anything ABOVE 1000mhz. I have it default set at 1.9GHz and it works almost instantly for me on call. But it's up to you. After that, everything is good to go.
Here's what it looks like:
Profile: Display Off Wake On Ring (27)
State: Display State [ Is off ]
Enter: Display Off Ring Manager (52)
A1: Perform Task [ Name display Off Cpu Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq OFF ]
A2: Perform Task [ Name:Wake On Ring Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq ON ]
Click to expand...
Click to collapse
I tried it and it does work better. The wallpaper doesn't show any more before call. Great job, thanks
Unfortunately, there is no difference for me. I still get a 2-3 seconds delay each incoming call
nfl mobile app not working on cloudy rom g3/verizion lg g2
My nfl mobile app is not working on cloudy rom g3. I have the lg g2 verizon. Please help fix it
Try a different rom... I've had great success with the G3 ported roms... No wake up lag on either one of these
Alright guys, we have so many clock faces to pick from and I have a few favorite ones. The problem is is do not want to keep swapping them, and I alwasy favor one more then the other. We really need a randomizer, which will give the user an ability to set the change interval, from either 1.) every set amount of time, 2.) every time the screen turns on(for ambilent off users).
An advanced feature could be to pick which clock faces to put into the randomizer. Anyways, I am not a developer capable of such a feat, but I would pay more money then most app faces cost right now. I would help fund the development of it, ofcouse giving me the option to beta it
Thanks
smugyou said:
Alright guys, we have so many clock faces to pick from and I have a few favorite ones. The problem is is do not want to keep swapping them, and I alwasy favor one more then the other. We really need a randomizer, which will give the user an ability to set the change interval, from either 1.) every set amount of time, 2.) every time the screen turns on(for ambilent off users).
An advanced feature could be to pick which clock faces to put into the randomizer. Anyways, I am not a developer capable of such a feat, but I would pay more money then most app faces cost right now. I would help fund the development of it, ofcouse giving me the option to beta it
Thanks
Click to expand...
Click to collapse
I have been using Wear Facelift from the Playstore, it lets you choose which faces you want to have randomised and how often. Worked very well under Kitkat, not optimized for Lollipop yet, but hopefully will be soon.
Hope that helps
Dont know how to get rid of smiles that are in the task below, apologises.
Created using tasker and Watchmaker, using a profile that runs the task every morning, also using autowear to swipe to also run the task. Sets a random face every morning.
All that is needed is setup a couple of variables and a If statement each watch face. If you need help let me know
Watchran (78)
Run Both Together
A1: Bluetooth [ Setn ]
A2: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A3: Variable Set [ Name:%Lastwatchface2 To:%Lastwatchface Do Mathsff Appendff ]
A4: Variable Set [ Name:%Lastwatchface To:%Watchface Do Mathsff Appendff ]
A5: Variable Randomize [ Name:%Watchface Min:1 Max:19 ]
A6: If [ %Watchface eq %Lastwatchface | %Watchface ~ %Lastwatchface2 ]
A7: Goto [ Type:Action Number Number:4 Label: ]
A8: Else
A9: If [ %Watchface ~ 1 ]
A10: WM Change Watch [ Configuration:breitling custom Orange Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A11: End If
A12: If [ %Watchface ~ 2 ]
A13: WM Change Watch [ Configuration:BUNK3R WATCH red Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A14: End If
A15: If [ %Watchface ~ 3 ]
A16: WM Change Watch [ Configuration:fav1 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A17: End If
A18: If [ %Watchface ~ 4 ]
A19: WM Change Watch [ Configuration:Tron Identity Disc5 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A20: End If
A21: If [ %Watchface ~ 5 ]
A22: WM Change Watch [ Configuration:Joker 1 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A23: End If
A24: If [ %Watchface ~ 6 ]
A25: WM Change Watch [ Configuration:Untitled watch Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A26: End If
A27: If [ %Watchface ~ 7 ]
A28: WM Change Watch [ Configurationpulence Damien Hirst Tribute Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A29: End If
A30: If [ %Watchface ~ 8 ]
A31: WM Change Watch [ Configuration:Ferrari Scuderia V.yos Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A32: End If
A33: If [ %Watchface ~ 9 ]
A34: WM Change Watch [ Configuration:CAT 2 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A35: End If
A36: If [ %Watchface ~ 10 ]
A37: WM Change Watch [ Configuration:slipknot Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A38: End If
A39: If [ %Watchface ~ 11 ]
A40: WM Change Watch [ Configuration:Hamilton V3 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A41: End If
A42: If [ %Watchface ~ 12 ]
A43: WM Change Watch [ Configuration:Aviary Racer LG Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A44: End If
A45: If [ %Watchface ~ 13 ]
A46: WM Change Watch [ Configurationmega x-33 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A47: End If
A48: If [ %Watchface ~ 14 ]
A49: WM Change Watch [ Configuration:Black Shield Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A50: End If
A51: If [ %Watchface ~ 15 ]
A52: WM Change Watch [ Configuration:Black Hole Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A53: End If
A54: If [ %Watchface ~ 16 ]
A55: WM Change Watch [ Configuration:Sun Flare Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A56: End If
A57: If [ %Watchface ~ 17 ]
A58: WM Change Watch [ Configurationmega 3 Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A59: End If
A60: If [ %Watchface ~ 18 ]
A61: WM Change Watch [ Configurationpulence Rotor Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A62: End If
A63: If [ %Watchface ~ 19 ]
A64: WM Change Watch [ ConfigurationERRELET Turbine Racing alternative Package:slide.watchFrenzy Name:WM Change Watch Timeout (Seconds):0 ]
A65: End If
Thanks for the app. Works well so far!
Thanks for this app :3
Hey, I'm trying to automate fullscreen immersive mode for some apps. And can't find a way to set this up using either tasker or automate. Any tips are appreciated.
domsch1988 said:
Hey, I'm trying to automate fullscreen immersive mode for some apps. And can't find a way to set this up using either tasker or automate. Any tips are appreciated.
Click to expand...
Click to collapse
Pretty simple with Tasker. Here's the profile description if you want too did it yourself, or import the attached profile and modify for the aod you want.
Profile: Immersive (601)
Application: Maps, Disney Junior, Netflix...
Enter: Full Immersive (602)
A1: Run Shell [ Command:su
settings put global policy_control immersive.full=* Timeout (Seconds):0 Use Rootff Store Output In: Store Errors In: Store Result In: ]
Exit: End Immersive (603)
A1: Run Shell [ Command:su
settings put global policy_control null* Timeout (Seconds):0 Use Rootff Store Output In: Store Errors In: Store Result In: ]
https://www.dropbox.com/s/x6yq7h3k4seucdo/Immersive.prf.xml?dl=0
Sent from my SM-G955F using Tapatalk
This is not working for me.
The command runs but nothing happens - any idea as to why?
Below is a list of the Minimum width (dp) settings I have tested and documented and their corresponding Display size values (dpi). The UI mode has been noted and an asterisk notes a maximum or minimum for a display mode (phone, phablet, or tablet). (Please correct me if I am using the incorrect terms anywhere here.)
Enable Developer Options - Find "Minimum width"
[ ] Minimum width (portrait) / Display size (custom)
[ ] 550 / 418 Phone
[ ] 575 / 400 Phone
[ ] 595 / 387 Phone
[ ] 598 / 385 Phone*
[ ] 600 / 384 Phablet* (Chrome tabs)
[ ] 625 / 368 Phablet
[ ] 650 / 354 Phablet
[ ] 675 / 341 / Phablet
[ ] 700 / 329 Phablet
[ ] 717 / 321 Phablet*
[ ] 720 / 320 Tablet* (Chrome tabs)
[ ] 725 / 317 Tablet
Click to expand...
Click to collapse
Note About Google Assistant, Texting, and these display settings:
I always change my screen density as I prefer the tablet display mode and hate the oversized screen elements. This time I ran into an issue that drove me nuts. Changing from phone to phablet or tablet UI mode changes Google Assistant mode from phone to tablet. This can cause Google Assistant to go from sending texts on command to saying, "I don't know how to text yet."
Google Assistant Settings - Note: "Phone" changes to "Tablet"
Retraining the Voice model after increasing Minimum width past phone modes does not seem to fix the issue. Rebooting doesn't seem to help. Changing the Minimum width then retraining (possibly after a requisite reboot) DOES reenable Google Assistant texting. It also seems that if Google Assistant is trained while in Phone mode, increasing the Minimum width to any of the above settings without rebooting afterwards will allow Google Assistant to text until the phone is next rebooted.
(I'll clean this text up later.)
I have submitted a Feedback Request about this. Do the same if this annoys you too.
What smallest DPI u recommend for this device? Mine defaults to 411... Curious since I'm having some touch issues.
galaxys said:
What smallest DPI u recommend for this device? Mine defaults to 411... Curious since I'm having some touch issues.
Click to expand...
Click to collapse
I'm currently set at 720/320. I tried keeping it at the highest phone UI dp but it drove me nuts within an hour. I have touch issues too (near the edges, making folders/groups), but benefits versus costs for me still come down to tablet mode.
Looks like the touch issues should be resolved in a future update.
Is there any way to keep it in phone mode with the lower DPI settings?
Best I found for retaining phone UI is:
433 DPI / 532 dp Smallest Width
..
Device needs to be rooted!
This does not work with apps from the supplier as radio, phone, player, video etc. These are nearly all included in the com.car.ui and I did not yet find a way to get them "catched".... may be there is another way... Would be nice if someone could point it to me.
Target of this script with Tasker:
I just wanted to reduce touch screen using while driving.
To start may be a player with a click on a button is one thing, but I may don´t want to stay in this app.
In this case I need to click the Home button and choose another app. On a head unit without hardware buttons sometimes hard to get the home button clicked.
But If I need to play around with the settings of the app, I don´t want to get rejected to the home screen during changing the app settings....
So the target was to create a task which:
Moves the app to background after a short time
To not move the app to background while touching the screen
To move the app to background if there is no touch within a predefined time.
I found a way to get back to the home screen if I opened a player (in this case DAB-Z from realzoulou) by using shell commands.
Example:
Code:
DAB_RETURN (3)
A1: Variable Clear [ Name:%Touch Pattern Matching:eek:ff Local Variables Only:eek:ff ]
A2: Wait [ MS:100 Seconds:0 Minutes:0 Hours:0 Days:0 ]
A3: Variable Clear [ Name:%Dab Pattern Matching:eek:ff Local Variables Only:eek:ff ]
A4: Wait [ MS:0 Seconds:5 Minutes:0 Hours:0 Days:0 ]
A5: Run Shell [ Command:cat /proc/$(pidof -s com.zoulou.dab)/oom_adj Timeout (Seconds):0 Use Root:eek:n Store Output In:%Dab Store Errors In:%Dab_false Store Result In: Continue Task After Error:eek:n ]
A6: Wait [ MS:100 Seconds:0 Minutes:0 Hours:0 Days:0 ]
A7: Run Shell [ Command:getevent -c 1 /dev/input/event1 Timeout (Seconds):5 Use Root:eek:n Store Output In:%Touch Store Errors In:%Touch_false Store Result In: Continue Task After Error:eek:n ]
A8: If [ %Touch Set ]
A9: Goto [ Type:Action Number Number:1 Label: ]
A10: Else
A11: Run Shell [ Command:cat /proc/$(pidof -s com.zoulou.dab)/oom_adj Timeout (Seconds):0 Use Root:eek:n Store Output In:%Dab Store Errors In:%Dab_false Store Result In: Continue Task After Error:eek:n ]
A12: Wait [ MS:100 Seconds:0 Minutes:0 Hours:0 Days:0 ]
A13: If [ %Dab !~ 3 ]
A14: Go Home [ Page:1 ]
A15: Else
A16: End If
A17: End If
To use it for other apps you need to find the package name by using the shell:
Open ADB on your PC, connect to your Android in the same WiFi by:
adb connect [IP-Addresse]
adb shell
top (this command does not stop. You need to press "q" on your keyboard to stop it)
The output shows all running apps on your device. You need to search for the app name you want to use with this script.
Code:
cat /proc/$(pidof -s [app-name])/oom_adj
For DAB-Z it is:
Code:
cat /proc/$(pidof -s com.zoulou.dab)/oom_adj
This command returns the status of DAB-Z:
1 = App in foreground
0= App not running, or in background
Other apps can show different states. You need to find the status by using your PC for each app you want to get managed by this task.
The shell command:
Code:
getevent -c 1 /dev/input/event1
fetches touch events on the screen....
and waits in my script 5 sec, stores a touch in %Dab and keeps it empty if there was no touch on the screen.
If you touch it, the variable will be filled with a "0" (zero), otherwise the shell throws an exception which is the trigger to go back to the home screen.
Have fun with it.