Related
I recently rooted my Samsung Captivate using SuperOneClick 1.9.1. The only things I have done since rooting the device is allow sideloading (by editing settings.db with SQLite Editor), so I can install apps from Amazon Appstore and used Titanium Backup to delete bloatware.
I noticed that when I installed SwiftKey that I would click 'Enable Swiftkey' and then click on Swiftkey settings only to be told that I need to enable swiftkey in order to change the settings. I thought it was a problem with swiftkey.
However, I then noticed that the phone kept reverting to USB Debugging Mode and only after three attempts was I able to disable USB debugging and mount my drive. I finally figured out that it's a problem with changing settings; can anybody tell me how to fix this? Thanks.
Super one click 1.whatever has the option to enable side-loading ( 2nd tab! ) so you really waisted some time on that one!
if you are running a custom rom, they are made to keep debugging on, it doesnt stop you from doing anything.
to enable swift key:
menu button > settings > locale and text > check swiftkey to enable.
ive never used swiftkey but that is how all other keyboards go....
all else fails install a custom rom / pre-rooted, crap removed, extra options, side loading tethering ect...
More info
The problem isn't just SwiftKey or USB debugging. All settings on the phone are screwed up. I hold down the power button and bring up the options:
Data Network Mode: I restarted the phone and 3g was enabled. I clicked on the data network mode and disabled it. But now it's always off, yet it says it's activated (and I can't set it to deactivated)
Airplane Mode: I can't put the phone in airplane mode, nor can I do this from the settings menu
Sound: This works fine
On the Power Control Widget:
Brightness: I can change brightness, but the icon stays the same
Sync: This button works fine
GPS: This button is not responding
Bluetooth: n/a (the button lights up, but I don't have bluetooth)
Wifi: n/a (the button lights up, but I don't have wifi nearby)
The settings menu:
I know that Swiftkey and USB debugging are giving me problems
As for the custom ROM, I was having problems with the the signature error on 2.2 (http://forum.xda-developers.com/showthread.php?t=1051197)
I'm going to try out the advise from that thread and see if I can resolve this with a custom ROM. Normally I'd say this is "throwing out the baby with the bath water," but I'm excited about putting a custom ROM on my phone for performance reasons.
If there is another solution, I'd like to know about it because I want to be a little more adept before installing a ROM on my phone. Thanks.
I was going to install Serendipity 6.4. Do you have another MOD that you would recommend?
+1 for serendipity
I have Android 5.1.1 completely stock anyway I have no enable after touching the 3 dots for extra settings.. all I have is help .. is this a bug? am I missing something? I've enabled WiFi and tried as well same thing..
As most of you might know, OnePlus removed the proximity wake option from OOS lately, replacing it with the lift to wake feature. If you want to use the proximity wake feature, you either have to switch to a custom ROM or use an outdated version of OOS. Both options might be suited for most people, but in case you prefer to use latest OOS and still want to use proximity wake, I have some kind of workaround.
PLEASE NOTE: it seems that the given shell command does not work on Android Oreo (OOS Open Beta as of writing). Check the latest posts of this thread for any progress.
I came across this shell command, which will trigger the ambient display:
Code:
am broadcast -a com.android.systemui.doze.pulse com.android.systemui
A big shoutout to @Quinny899 for providing me the code to trigger ambient display by shell command.
You can use this command with Tasker to trigger it when the proximity sensor is covered for some seconds or even when you wave your hand over it. I haven't had the time to get such a profile working until now, but I know that it can be archived easily.
In case you use the above command, ensure you check the "use root" option in Tasker's context menu for the shell command!
EDIT: I managed to get this working :good: Below my implementation. I am sure there is room for optimization, but this is just a basic task and it works for me (OOS 4.5.13 with Tasker 5.0u6).
You need three profiles. Two of them will check the proximity sensor state while screen is off, the third one actually triggers the ambient display while screen is off and proximity sensor has been covered (by waving over it for example).
First of all, we need to ensure that Tasker will monitor the proximity sensor while screen is off. For this, open the three-dot menu, select Preferences and navigate to the Monitor tab. Set "Proximity Sensor" to "On". That's it.
Second, you have to enable the Ambient Display option via Settings -> Display, otherwise this won't work at all (thanks to @Devildire for confirmation)
Let's have a look at the needed profiles:
Code:
[B]PROFILE [I]Prox OFF[/I]
[/B]State -> Sensor -> Proximity Sensor -> invert
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity uncovered[/I]
[/B]Variable -> Set -> %Prox = false
[B]PROFILE [I]Prox ON[/I]
[/B]State -> Sensor -> Proximity Sensor
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity covered[/I]
[/B]Variable -> Set -> %Prox = true
[B]PROFILE [I]Wake Ambient Display[/I]
[/B]State -> Display -> Display State -> "Off"
State -> Variables -> Variable Value -> %Prox = true
[B]TASK [I]Wake Proximity Display[/I]
[/B]Task -> Wait -> 1s
Task -> IF -> %Prox = false
Code -> Run Shell -> am broadcast -a com.android.systemui.doze.pulse com.android.systemui (DON'T FORGET TO CHECK "USE ROOT")
That's it. Now turn off your screen and try to wake the ambient display by waving your hand over the proximity sensor.
EDIT: Tasker profiles can be found in post #7.
EDIT #2: @Arstoien provided us with an improved version of my basic tasks, check it out here.
Thanks for the guide on how to, great work from you for the community
OP updated with instructions. Feel free to comment and share your experience or any kind of optimization proposes. Please note that the implementation is only a rough imitation of the original proximity wake feature, most likely this implementation needs some polishing.
Hey there. Sounds intriguing... I'm not understanding the stacked profiles... It seems you've got it triggering with two conditions. How do you do that?
Or... Would it be possible to upload the profiles and tasks for importing?
@saccentekennedy
If you want to add another trigger to a profile, just long-press the first trigger condition and Tasker will prompt you with a popup window where you can select to add another trigger option.
If anyone else is interested, I might upload the profiles later.
Hi guys , any file so that we can import it on tasker (if it has such system) to get this. !!??!!
Please find attached the requested profiles.
EDIT: You might want to change the wait time within the wake ambient display task to 1s instead of 300ms, this one actually works way better.
Portgas D. Ace said:
Please find attached the requested profiles.
Click to expand...
Click to collapse
Works! Thanks for sharing this.
Is root required?
BloomerzUK said:
Is root required?
Click to expand...
Click to collapse
Yes look in the code last line
Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.
Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.
dre-z said:
Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.
Click to expand...
Click to collapse
As said before, this is just a rough workaround, it works for me (but not as perfect as the former in-built option). It works if you move your hand slowly over the sensor.
saccentekennedy said:
Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.
Click to expand...
Click to collapse
Hmm, I don't have this issue, but we might add another trigger option to the wake ambient profile: only trigger if display is face-up. This way it won't be triggered if the device is in your pocket.
After looking over what you steup in Tasker........The biggest question is "What does the phone do when it is in your pocket?" I think if you can figure out a solid Tasker-based solution to that question, this will be something worth using. Great work.
It works (more or less)
@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.
Portgas D. Ace said:
@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.
Click to expand...
Click to collapse
I think I am doing something wrong. Doesn't work at all. Thanks for your help anyways
Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?
Devildire said:
Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?
Click to expand...
Click to collapse
Did you check the "use root" option in the corresponding task?
I use the downloaded profles and yes, root is checked. Using OP5 up to date OOS.
Edit: maybe there is something wrong with shell execution. Can you give me information about what I have to enter using tasker's "send intent" action instead?
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
*gentle push*, because the problem still remains
katerlouis said:
*gentle push*, because the problem still remains
Click to expand...
Click to collapse
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
fehrcomp said:
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
Click to expand...
Click to collapse
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
katerlouis said:
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
Click to expand...
Click to collapse
Yes! On my device Mate 1o Pro, it was Talkback as well that ¨obscured a permission request¨.
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
help please
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
YEESSSS!!! Thank you for mentioning this, I never would've make that connection and that's exactly what it was for me! I guess those pics weren't all that smart after all ?
Panshu Mehra said:
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
Click to expand...
Click to collapse
I have an Honor 8 pro and I'm facing the same issue. I've disabled all apps which draw on the screen and restarted my phone too.
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Wow, good call. I was having this same issue. Thanks!
Fix #2 - if it works
i was messing with my Samsung Galaxy J7 Core J701F/DS and I was trying to figure out your problem also because i got the same problem as yours so the thing that worked for me is going to Settings (Nougat 7.0/1)> Apps> 3-dot menu/optionsl settings/other settings> Special Access> Apps that can be on top> Disable all apps like literally disable them all and try to debug your phone again...if it works, enable apps in that setting one by one and repeat debugging process. If it doesnt work, disable the last app you enabled, and if it works again...that is the app that is doing the dirty work...mine was not in the system apps it was one of my apps which is AZ Screen Recorder lol....(why the app that is being used everyday need to be disabled....)
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Omg thank you so much for this. It was driving me bat**** crazy. I tried everything didnt even think this would cause it.
katerlouis said:
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
Click to expand...
Click to collapse
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
kapil1100 said:
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
Click to expand...
Click to collapse
This put me on the right track.
I have an LG G6 running Android 8.0. My Keeper Security app needs permission to Draw over other apps and since around December 2018 it has started acting 'flaky'. The app would warn me that I need to turn on this permission, but when I clicked "OK" in the Keeper app to take me to the Android setting for the app, it was always turned on. I could turn it ON/OFF, along with the setting that needed this permission in the Keeper app (called Keeper Fill) and eventually get it to work again, but it would always break again very soon after.
As I am getting ready to go on a trip, I installed Google's Datally app. It, too, wants me to turn on Draw over other apps, but when I tap "next" to be taken to the Android settings page to enable Draw over other apps, nothing happens (I usually expect an app detects it has been enabled and gives "success" message).
So I started disabling the 3 possible suspects listed by kapil1100. I had LG's Comfort View and some Accessibility options enabled, so I turned them off and: no change.
I disabled all other apps that have permission to Draw over other apps via: Settings > Apps & notifications > Special access > Draw over other apps, and: no change.
I use Evie launcher, so I went back to the stock one: no change.
I got thinking about what else could be modifying/accessing the screen and realized that LG has custom Home touch buttons.
I went to: Settings > Display > Home touch buttons > Hide Home touch buttons and DISABLED Show lock/hide icon and then tried enabling Draw over other apps for Datally and IT WORKED!.
I was then able to turn Show lock/hide icon back ON and everything has been working as expected. I suspect that, because I had Show lock/hide icon turned on during an upgrade, something got messed up and my turning it OFF and back ON fixed the issue.
I hope this helps someone!
Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.
does this affect battery life
shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.
Tested now on my RN10-pro... works just fine! Thank you!
Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.
Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.
I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.
Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?
Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).
Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.
You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com