Related
My corporate WiFi uses a personal certificate for 802.1x authentication.
It works if the setting "Location and security > Use secure credentials" is checked.
The problem is, after rebooting, that option is always unchecked. When I re-enable it, it prompts for the security store password and all is good.
So, is there anyway to make the "Use secure credentials" setting permanent even after a reboot?
radeon_x said:
My corporate WiFi uses a personal certificate for 802.1x authentication.
It works if the setting "Location and security > Use secure credentials" is checked.
The problem is, after rebooting, that option is always unchecked. When I re-enable it, it prompts for the security store password and all is good.
So, is there anyway to make the "Use secure credentials" setting permanent even after a reboot?
Click to expand...
Click to collapse
I’m experiencing the same problem. Have you found a resolution?
I also have this problem, only on a Desire. Is there a solution yet?
Howdy!
I know I am late to the party.
I also have this problem.
Using an HTC Sensation, with cyanogenmod 7.1 alpha10, if that matters.
Where in the filesystem should these kind of options be stored?
radeon_x said:
The problem is, after rebooting, that option is always unchecked. When I re-enable it, it prompts for the security store password and all is good.
So, is there anyway to make the "Use secure credentials" setting permanent even after a reboot?
Click to expand...
Click to collapse
Apologies if I misunderstood you, but, are you asking for access to secure store without the password?
Simply, alternative (not predicted by Samsung I presume) is that each boot you'd be asked for a password... and this is not a bug, that when your phone will be stolen, someone directly after reboot will have access to your company's WiFi, I think.
same problem
pre-rooted shipped stock ROM.
everytime rebooted, the "use secure credentials" unchecked automatically.
And i must check it again so i can use the power button to poweroff the phone.
spamtrash said:
Apologies if I misunderstood you, but, are you asking for access to secure store without the password?
Simply, alternative (not predicted by Samsung I presume) is that each boot you'd be asked for a password... and this is not a bug, that when your phone will be stolen, someone directly after reboot will have access to your company's WiFi, I think.
Click to expand...
Click to collapse
I'm having this headache too, and for the reasons spamtrash listed above - you don't want it to automatically use the secure credentials.
What would be nice though (and what I could use a hand trying to figure out): Is getting the phone to prompt you for the secure login on boot, or prompt you for the login the first time it attempts to connect to the secure network. I turn my WiFi on from a homescreen widget - so I'm not in the WiFi screens to see the credential login box.
same problem here, using ICS (CM9) and CM7 latest nightly build.
I have been successfully using the Verizon FIOS remote control app to control my TV FIOS STB and it is much nicer to use than the standard IR remote.
To get it to work originally using a nightly (circa 128), I had to persuade the Nook that it had a phone number as this is registered against one set in the STB. I did this by going into Settings/Call Settings/Additional Settings. This gives a network or SIM card error but when OK'd allow me to manually enter a phone number which then worked fine and continued to work through many nightly updates.
Something has now changed (I am currently on nightly 200) as I find that I have to re-register the FIOS app almost daily to get it to work.
On checking I find that the Phone Number setting gets lost periodically and set back to Unknown and I have to manually enter it again.
Does anybody know whether CM7 behaviour has changed with respect to the storage of the Phone Number? I realise it would normally be on a SIM, but it does seem to stick around for quite a while on the Nook before getting lost.
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
dgibb2000 said:
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
Click to expand...
Click to collapse
I have made some progress investigating this but have not got a final solution yet.
First, I can set my phone number up even though it is not a phone. I go into Settings, Call Settings, Additional Settings. The screen blurs and brings up a dialog box saying Call settings Error - Network or SIM card error. If I OK that then I see 3 menu items. The first 2 are grayed out but the 3rd "My Phone Number" is enabled. I select that and can enter a Phone Number. Are you saying you get the error and then all 3 options are grayed out?
Once entered I can view the Phone number via Settings, About Tablet, Status.
So far so good. The phone number setting does not normally survive a reboot, and also typically reverts to Unknown after a couple of days even without a reboot.
I have traced the Phone number setting to be stored in com.android.phone_preferences.xml which is in /data/data/com.android.phone/shared_prefs
But when the Phone number disappears it doesn't disappear from this file so there is some more complex interaction with trying to read a non-existent SIM first. So far I have traced the code involved to MyPhoneNumber.java and MSISDNEditPreference.java which are in the CyanogenMod-android_packages_apps_Phone-5d2764c.
I am still working on understanding this to see if there is some work-around to make the setting stick better. Currently I just have to check the phone number manually and set it again when it disappears.
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
dgibb2000 said:
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
Click to expand...
Click to collapse
Yes. That is strange. All my settings in Call Settings are enabled even though most are inapplicable. I don't think I have done anything to explicitly enable them and I'm on a standard Nightly 240 with the updated SystemUI.apk which turns off the phone signal bars. But I've never had these greyed out with any nightly build before.
Anybody else comment on whether their whole Call settings are enabled / disabled?
There is also a setting in build.properties in the system folder with a key called
keyguard.no_require_sim
I think this may have effect on how the OS treats calls which access the SIM. On my system this is currently set to 1. I might try playing with other values like true, 0 to see what effect that has.
Another theory as to why your call settings may be greyed out is that it they may get disabled in airplane mode.
Now this could be an issue even if you have set and subsequently cleared airplane mode as I believe the airplane mode setting doesn't go away entirely and can cause problems.
There is a command line way of clearing this setting completely which I did once when I set airplane mode on. Search for something like airplane sqlite to find the instructions.
That was it. I was stuck in airplane mode, and must have been for a long time. I used Android Assistant to clear the setting and it worked. I'm able to set my number and use fios mobile remote now! Thanks for your help.
Where did you get that updated systemui.apk to clear the cell signal bars? Now that I got the airplane mode off I have the signal strength there for no reason.
I got the SystemUI.apk from here
http://forum.xda-developers.com/show...60542&page=547
I just replaced the one in system/app. If you overwrite then you might get status bar forced close but a system reboot will sort that out and I haven't had signal bars since.
I've now put this in a zip that I can use to install after any nightly update I do as I've now found there is a wifi patch to deal with any remaining SOD issues although I haven't had one of those for a long time now.
Hopefully this stuff will get put into the main build before too long.
Looks like your link got clipped. Getting a page not found error.
Also, do you have any instructions on how to put the .apk into a zip for re-install after you do an upgrade? I'm assuming its not as easy as just ziping the file up?
Updated link
http://forum.xda-developers.com/showthread.php?t=960542&page=547
Yes. It is as easy as zipping the file up, but you have to create a matching folder structure to determine where the file goes. So in the case of the SystemUI file you create a folder called system containing a folder called app, put the file in the app folder and zip it so that system is in the root of the zip.
Correction: I thought that zip method was working but it wasn't. I had manually put the files in anyway and that worked OK. Then I was testing the zip, but it was actually failing.You need to put the files in a zip with the meta-inf etc. I think this link gives instructions
http://alldroid.org/default.aspx?g=posts&t=855
No. That doesn't work either as it uses an older method of scripting no longer supported. Apparently it needs to use Edify scripting now. It looks like some people add files to the gapps package, but I'm not clear yet whether it has to be re-signed, and I don't particularly want to redo gapps just to do this minimal patch.
I think I now understand how to produce an update zip that works.
I first took a gapp zip and stripped out all the existing files under system leaving the meta-inf alone. I put in the patch files in the appropriate folders under system. I then modified the updater-script in the meta-inf tree to just mount system, run package_extract_dir("system", "/system"); and unmount system with changes to the ui_print
I then signed the zip using the win-sign utility available here
http://forum.xda-developers.com/showthread.php?t=629151&highlight=sign+zip+files
I tried this out by first updating to nightly 246 and then applying my patch containing the SystemUI and the wifi driver that fixes SOD and that seemed to work OK.
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
You can probably unpair (from both the phone and sync) and then repair and when you repair just deny the MAP access request.
Also, you should be able to turn off new message download in Sync
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
boosting1bar said:
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
Click to expand...
Click to collapse
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Yeah that's exactly what I'm getting in my 14 Raptor. Terrible, I guess I have to disable it every time I get in the car now.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
dtg7 said:
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
Click to expand...
Click to collapse
Great idea, however I just tried it with no avail.
I just thought of something as well... my fiance has a '13 Focus SE with the base stereo, and she has the same model phone as me (VZW X Dev). Her SYNC doesn't alert her to new messages, but my truck with the same SYNC setup did, but I figured my truck had a more recent version of SYNC. I dunno, all I know is it's annoying as hell and I'd like to find a more permanent solution. Especially since I'm contemplating on buying the Droid Turbo in the future and I'm sure it will do the same thing.
triton302 said:
Great idea, however I just tried it with no avail.
Click to expand...
Click to collapse
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
dtg7 said:
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
Click to expand...
Click to collapse
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
boosting1bar said:
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
Click to expand...
Click to collapse
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
https://play.google.com/store/apps/details?id=cn.wq.disableservice
good luck.
dtg7 said:
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
good luck.
Click to expand...
Click to collapse
Thanks so much! Option 2 is exactly what I've been looking for! Option 1 doesn't work for me because I use Trigger and have conditional BT on/off and that would just recreate the same problem lol.
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
triton302 said:
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
Click to expand...
Click to collapse
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
boosting1bar said:
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
Click to expand...
Click to collapse
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of profile).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Roger, I'm off work today so I'll try these out here shortly.
EDIT: From what I recall, if you have a recent version of MFT, there are no options whatsoever for MAP, in phone or system settings. I'll double check.
EDITING EDIT: #2 doesn't work.
dtg7 said:
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of protocol).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Click to expand...
Click to collapse
I think we have a winner! #3 works perfectly.
I tested it with the phone unlocked and locked, rebooting the phone, toggling bluetooth on and off, turning the car on and off... seems to work every time. As long as you turn off just the SMS/MMS options, you can still have it send and receive calls and allow the device to remain unlocked while connected.
Ahhhh...... Success feels good...
Xposed is pretty amazing... It gives us a fighting chance lol.
if only they'd installed Xposed on Skynet things might have turned out differently...
dtg7 said:
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
Click to expand...
Click to collapse
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
You're welcome!
boosting1bar said:
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
Click to expand...
Click to collapse
How did you get this yo work? I am on a cm12 Rom also with the same issue.
Did all the above, but anytime I start the Bluetooth afterwards, it just reactivates the "Read / Write sms messages permission all over again nd im back to square 1.
Sorry to bump an old thread. But its still yhe same issue I am dealing with.
Seems totally random, but when attempting to activate an accessibility service (settings > accessibility), after toggling the switch to on, a pop-up displays asking if you would like to activate the selected service and you have options of 'cancel' and 'ok' - none of them will allow me to hit 'ok' but 'cancel' works just fine! I'm clueless on this, but fear that it's probably something silly that i've overlooked. I'm on stock rooted 5.1 (LMY47D) with Franco r21 kernel. I initially had a similar issue with SuperSU and root requests - it wouldn't let me grant OR deny access to anything, but a bit of digging lead me to the 'tapjacking protection' feature in the settings - i'm wondering if this issue is something similar?! i searched around a bit but wasn't turning up anything useful - anyone have any good ideas?! all i want is LastPass to be allowed to form fill my passwords!!
Hi,
I tried to find root cause, but unfortunately without success. Is there anybody, who using Tasker or another application for automatization of your phone without any issues?
My issue is, Tasker is still "delayed" - but same rules I used before on LG G3 (Android 6.0) - but now on P9 (DualSIM) didn't work.
I have task for Calendar Entry, where if I have appointment in my work calendar, during this time Sound mode is deactivated (only Vibrate).
Some suggestion? I tried white lists, etc. or another app with same bad behavior.
Thank you!
Well, I tried to deactivate power management app from Huawei over ADB and looks good now finally! Its workaround, but tasker now working very well as expected.
adb shell pm hide com.huawei.powergenie
Did you have "Run in Foreground" selected in Tasker's preferences?
My Tasker works fine with that selected, although I also have trusted the app in permissions manager, allowed it to auto launch & activated it as a device administrator in advanced settings/security.
Yeah, I tried every tip over Tasker or phone (EMUI settings) and only deactivate power management helps me.
I had the same problem with IFTTT. It worked perfectly with my LG G3, but was hopeless on the P9. No amount of white-listing or settings would work.
I even had the app in memory, with Google maps running, on GPS, screen on, and it still wouldn't trigger a location based profile.
I've had to revert to manually arming and dis-arming my home security system. Annoying.
I translate from spanish so I'm sorry if your phone shows menus with other name.
You must go to adjust > advanced adjusts > memory and store and at bottom of page "space clean". On new screen push on upper-right wheel, and now on last option "white list of memory clean". Finally look for your app and activate it.
If you don't include app here, clean system will close it on background and timers won't work. It solved my problems.
aidrabmol said:
I translate from spanish so I'm sorry if your phone shows menus with other name.
You must go to adjust > advanced adjusts > memory and store and at bottom of page "space clean". On new screen push on upper-right wheel, and now on last option "white list of memory clean". Finally look for your app and activate it.
If you don't include app here, clean system will close it on background and timers won't work. It solved my problems.
Click to expand...
Click to collapse
"Settings>Advanced settings>Memory & storage>Storage cleaner" and "Memory cleanup whitelist".
Using Agama, I can get an app to start following a reboot. However, I would like to start the App at every Startup. Does Automate or any other app let you do that?
carroamer said:
Using Agama, I can get an app to start following a reboot. However, I would like to start the App at every Startup. Does Automate or any other app let you do that?
Click to expand...
Click to collapse
Why would you need Tasker for that simple.
Settings, type in the Search Autostart and add your app to the list of apps to be started on every reboot.
You may also need to disable Battery Optimization for your app (to make sure it would still work in background when the phone sleeps with dark screen)
That should generally work for all Androids. I don't have Huawei P9 now for years, I remember that EMUI might have had specific Settings organization but there was also Autostart (or Auto start)...
zgfg said:
Why would you need Tasker for that simple.
Settings, type in the Search Autostart and add your app to the list of apps to be started on every reboot.
You may also need to disable Battery Optimization for your app (to make sure it would still work in background when the phone sleeps with dark screen)
That should generally work for all Androids. I don't have Huawei P9 now for years, I remember that EMUI might have had specific Settings organization but there was also Autostart (or Auto start)...
Click to expand...
Click to collapse
When I search 'Autostart' it produces 'No results'
carroamer said:
When I search 'Autostart' it produces 'No results'
Click to expand...
Click to collapse
I had P9 for three years (if you don't believe, you can find tons of my posts here back from 2017-2018)
Now, you have that phone, not me (I got rid of my last Huawei almost three years ago) - I cannot show you and I cannot look into the EMUI settings because I don't have the EMUI phone anymore
But I KNOW that there was a way in EMUI how to control which apps will be automatically started on boot - I know because I played with all that back in those years, II did need for many apps like AdAway, Find My Device and similar that required to be auto-started to operate correctly
Take your time and google and you'll find. Sorry, I tried to help you but I will no more waste my time on that. Huaweis are past time for me
And take your time, use your imagination, If not Autostart, google for EMUI startup manager or something similar to find the answer for your question on the Net