Whenever I try to install an APK I downloaded, I am not able to tap on the Install button of the prompt with the app permissions. I can tap on Cancel, but nowhere on the Install part. (phone is configured to allow untrusted sources, otherwise it wouldn't even launch the package manager).
I also am unable to hit OK when trying to connect to a VPN, but I can tap Cancel.
Is this some silly LG "safety feature". I posted on the Tmo forum but someone mentioned they have the similar APK issue on a Verizon model, so I pose the question to every one else here.
I am unrooted, and running the stock T-Mobile version. I have debloated my phone with the Debloat tool, but I can't think of what I could have disabled that would create this odd behavior.
Edit: I had MDM installed on my phone that had some administrator profiles enforced, but I have removed them and I am still unable to tap on Ok for VPN or Install for APKs.
havanahjoe said:
Whenever I try to install an APK I downloaded, I am not able to tap on the Install button of the prompt with the app permissions. I can tap on Cancel, but nowhere on the Install part. (phone is configured to allow untrusted sources, otherwise it wouldn't even launch the package manager).
I also am unable to hit OK when trying to connect to a VPN, but I can tap Cancel.
Is this some silly LG "safety feature". I posted on the Tmo forum but someone mentioned they have the similar APK issue on a Verizon model, so I pose the question to every one else here.
I am unrooted, and running the stock T-Mobile version. I have debloated my phone with the Debloat tool, but I can't think of what I could have disabled that would create this odd behavior.
Edit: I had MDM installed on my phone that had some administrator profiles enforced, but I have removed them and I am still unable to tap on Ok for VPN or Install for APKs.
Click to expand...
Click to collapse
What other Apps are have you installed? I read somewhere that certain Screen Filter Apps reproduce this issue just in case yo have one installed.
GUGUITOMTG4 said:
What other Apps are have you installed? I read somewhere that certain Screen Filter Apps reproduce this issue just in case yo have one installed.
Click to expand...
Click to collapse
I heard about that too. No screen filter apps.
It's strange that it is only that part of the screen that is not tappable, or rather, it does not create an action on the button. If I enable screen taps in the developer menu, I can see the taps, they are just not registering.
If you have something like Lux installed, disable it, continue w/ your install, then re-activate the culprit app(s). I had the same problem installing APKs where pressing INSTALL did nothing, but CANCEL was ok.
havanahjoe said:
I heard about that too. No screen filter apps.
It's strange that it is only that part of the screen that is not tappable, or rather, it does not create an action on the button. If I enable screen taps in the developer menu, I can see the taps, they are just not registering.
Click to expand...
Click to collapse
Would you post a list of apps you debloated? You may exclude all T-mobile ones as they are not the problem.
alamo76 said:
If you have something like Lux installed, disable it, continue w/ your install, then re-active the culprit app(s).
Click to expand...
Click to collapse
Well, well, well, that did it. The Lux service breaks this, even though I never see it on top of anything because it just runs in the background. Hopefully this will show up when people search for the issue and they can easily fix it.
Thank you!
No problem-o. I was stumped initially and also can't exactly wrap my head around why some buttons work and some don't. I read somewhere that in the context of INSTALL it was to prevent malicious software from being installed. Or something.
For those who may be having a similar problem, you can go to Setup->Advanced in Lux. Enable the "Use Alternative Overlay" option and it should allow you to get the tap to work and still have Lux enabled.
Fyi the OK/Install eventually works, just give it about 10 seconds
Related
I downloaded it from the internet, clicked on the programme in downloads and got the 'do you want to install this application' screen, but nothing happens when I click 'install'. I have the same issue with the Amazon Appstore. I have ticked the 'allow installation of non-market apps' box in security and would love to know where I'm going wrong! Ta!
I've tried downloading it directly to the phone and mounting it and dragging it across from the computer. I've also used a file manager to open the .apk, but although 'cancel' works, 'install' doesn't. My phone isn't rooted, but I'm assuming that doesn't make any difference...
Okay, in case anyone else is having issues, I have discovered that for some reason 'screen adjuster' or 'screen filter' somehow stop the manual loading of .apks and they have to be turned off for this to work. I hope this helps!
bigbamboo5 said:
Okay, in case anyone else is having issues, I have discovered that for some reason 'screen adjuster' or 'screen filter' somehow stop the manual loading of .apks and they have to be turned off for this to work. I hope this helps!
Click to expand...
Click to collapse
This worked for me, thanks!
I put ATT sim card in Verizon note 4, everything seems to be good (I got 3G, no LTE, but that's okay), except the annoying message "the sim card is not from verizon". I checked it, and it was from "activation agent". Does anyone know how to get rid of it? Thanks.
liyapunov said:
I put ATT sim card in Verizon note 4, everything seems to be good (I got 3G, no LTE, but that's okay), except the annoying message "the sim card is not from verizon". I checked it, and it was from "activation agent". Does anyone know how to get rid of it? Thanks.
Click to expand...
Click to collapse
give this a try - go into settings -> applications ->swipe to all tab, this will list all the apps and services, scroll down to 'setup wizard', tab on it and turn it off.(disable).
Thanks for the suggestion. Unfortunately, the "turn off" (of setup wizard) is grey. Same thing happened to "activation agent". Does this mean I need to root (which is not available right now) first?
buhohitr said:
give this a try - go into settings -> applications ->swipe to all tab, this will list all the apps and services, scroll down to 'setup wizard', tab on it and turn it off.(disable).
Click to expand...
Click to collapse
Just Force Stop the application. It'll stop showing the annoying message.
Update: just notice that there are two "setup wizard". One can be turned off, one can't. I turned the first one off, but it didn't help, i.e. message still pops up when the phone restarts.
liyapunov said:
Thanks for the suggestion. Unfortunately, the "turn off" (of setup wizard) is grey. Same thing happened to "activation agent". Does this mean I need to root (which is not available right now) first?
Click to expand...
Click to collapse
area5x1 said:
Just Force Stop the application. It'll stop showing the annoying message.
Click to expand...
Click to collapse
That works, but I hate to do that every time the phone is turned on. Want to find a more permanent solution.
liyapunov said:
That works, but I hate to do that every time the phone is turned on. Want to find a more permanent solution.
Click to expand...
Click to collapse
This should help:
http://forum.xda-developers.com/note-4-verizon/general/disable-knox-ota-root-t2972263
I was able to disable activation agent through this, and havn't noticed any adverse effects.
in adb shell use the following command:
adb shell
pm block NAME_OFTHE_SETUP_WIZARD_APP
then it should be blocked and you won't see it.
I can't find the exact name of setup wizard so you have to find how the app is called in android. something like com_XX_XX
VzwActivationAgent.apk = com.samsung.vzw.activationagent
The defroster works for it as well. I deactivate the little notification and it's app after I switched my phone to cricket wireless
Install Debloater by Gates Jr. and the Samsung USB drivers. Enable USB debugging on your phone. Launch Debloater and it will read all .apk packages. For the S4 you will need to check off the Samsung (and not the Google) setup wizard. Once complete, you will no longer see the Verizon icon in your system tray, as well as the annoying message.
tw426 said:
VzwActivationAgent.apk = com.samsung.vzw.activationagent
Click to expand...
Click to collapse
The package and command that worked for me on s8 plus:
pm uninstall -k --user 0 com.sec.android.app.setupwizard
Old thread, sorry, but my old Galaxy S8+ is actually still usable as a WiFi based browser and it has some games and Titanium Backup (phone was rooted). I'd like to use it to play some of those games and browse via WiFi at home with it to save wear & tear on the S20 Ultra. I would really like to know what I can use Titanium Backup to turn off so I don't see the "Activation Incomplete" message.
I have FoxFi and FoxFi must use a VPN/Credentials storage. This disables the pattern lock. I can re enable pattern lock by clearing credentials however than I have to go through the process of disabling it every time I use FoxFi. Is there a way to have both?
JeffATL said:
I have FoxFi and FoxFi must use a VPN/Credentials storage. This disables the pattern lock. I can re enable pattern lock by clearing credentials however than I have to go through the process of disabling it every time I use FoxFi. Is there a way to have both?
Click to expand...
Click to collapse
I'm sorry that I don't have an answer for you, but can I ask how you clear the credentials so that you can change the screen lock method? I'm using fingerprint and it works fine with Foxfi, but sometimes I like to just use swipe and I can't choose it (its greyed out). I have gone into "Trusted Credentials" and manually removed the FoxFi credential under the User setting (so that user setting is now blank), but when I try to change screen lock to swipe, its greyed out. What am I supposed to do so I can choose any of the screen unlock methods, not just the ones FoxFi allows?
I apologize for hijacking your post and you don't have to answer me if that upsets you. Thanks anyway.
FlattFoxJohnson said:
I'm sorry that I don't have an answer for you, but can I ask how you clear the credentials so that you can change the screen lock method? I'm using fingerprint and it works fine with Foxfi, but sometimes I like to just use swipe and I can't choose it (its greyed out). I have gone into "Trusted Credentials" and manually removed the FoxFi credential under the User setting (so that user setting is now blank), but when I try to change screen lock to swipe, its greyed out. What am I supposed to do so I can choose any of the screen unlock methods, not just the ones FoxFi allows?
I apologize for hijacking your post and you don't have to answer me if that upsets you. Thanks anyway.
Click to expand...
Click to collapse
Security - Clear Credentials (Removes all) works. But I have to add back credentials to use FoxFi
I was trying to work this out this morning myself. I came across a thread with "fixes" but none worked for me. Feel free to give them a try and let me know if anything works for you.
http://forum.xda-developers.com/showthread.php?t=2739469
vwpiper said:
I was trying to work this out this morning myself. I came across a thread with "fixes" but none worked for me. Feel free to give them a try and let me know if anything works for you.
http://forum.xda-developers.com/showthread.php?t=2739469
Click to expand...
Click to collapse
Thanks. This one worked for me.
e4c said:
found a fix for getting all lock screen options back.
log into google device manager: google.com/android/devicemanager
click on the lock button for your device.
enter a new pass and save.
now go to your phone and use the new pass to unlock the phone.
you should now be able to go to your lock screen settings and pick whichever lock option you need.
Click to expand...
Click to collapse
just to clarify. login to google device mgr from pc, not phone - I guess I now have to plop down $8 for the key, I thought I did already.
"log into google device manager: google.com/android/devicemanager
click on the lock button for your device.
enter a new pass and save.
now go to your phone and use the new pass to unlock the phone.
you should now be able to go to your lock screen settings and pick whichever lock option you need."
You can do this from chrome on your phone.
This worked for me!
Thanks for the help!
Running an sgs3 i747 and tried ththis to no avail. All other lock methods are still locked out.
I'm having issues with Kodi after rooting my Fire TV 2. It seems to be doing a first run every time I open it, if it actually opens. I've removed it 6 or 7 times and tried to reinstall it, but it constantly does it. Other apps seem to work okay. I've installed using ADBFIRE and I've been using the same Kodi .apk as I've used since I bought my FTV2. I've tried a new .apk to see if that helps. I'm stuck here. Any advice would be appreciated.
*UPDATE*
Installed via SD and it's working fine. Obviously an issue with ADBFIRE.
Apologies for a pointless post, feel free to remove.
liam080888 said:
I'm having issues with Kodi after rooting my Fire TV 2. It seems to be doing a first run every time I open it, if it actually opens. I've removed it 6 or 7 times and tried to reinstall it, but it constantly does it. Other apps seem to work okay. I've installed using ADBFIRE and I've been using the same Kodi .apk as I've used since I bought my FTV2. I've tried a new .apk to see if that helps. I'm stuck here. Any advice would be appreciated.
*UPDATE*
Installed via SD and it's working fine. Obviously an issue with ADBFIRE.
Apologies for a pointless post, feel free to remove.
Click to expand...
Click to collapse
adbFire does nothing more that adb install -r filename.apk, so I seriously doubt that this is an adbFire issue. At any rate, I can't duplicate this and have had no other reports of this issue after many thousands of downloads.
jocala said:
adbFire does nothing more that adb install -r filename.apk, so I seriously doubt that this is an adbFire issue. At any rate, I can't duplicate this and have had no other reports of this issue after many thousands of downloads.
Click to expand...
Click to collapse
I'm not suggesting it was an issue with adbFire, there could've been many other factors, in face I thought it could be an issue with my router or my MacBook. It could have also been a coincidence.
Any way, it's sorted now so I'm not worried. I'll continue to use adbFire, for everything else.
Do you have firestarter installed? There is an option in settings that you might need to unchecked.
smartymcfly said:
Do you have firestarter installed? There is an option in settings that you might need to unchecked.
Click to expand...
Click to collapse
I do, yeah. I've run in to the problem a few times since. Which option would that be?
liam08 said:
I do, yeah. I've run in to the problem a few times since. Which option would that be?
Click to expand...
Click to collapse
Under settings. There is the option to use home button to launch apps, and for each app it has the option under the app you select for single press and also for double press. I can't think of what it is says but if you go through the settings you will find it.
smartymcfly said:
Under settings. There is the option to use home button to launch apps, and for each app it has the option under the app you select for single press and also for double press. I can't think of what it is says but if you go through the settings you will find it.
Click to expand...
Click to collapse
Out of interest, which option would cause it to delete all of the addons etc? I'll close Kodi after setting it up and then start up again and it's doing its first run.
liam080888 said:
Out of interest, which option would cause it to delete all of the addons etc? I'll close Kodi after setting it up and then start up again and it's doing its first run.
Click to expand...
Click to collapse
I misunderstood what was happening to you. And I don't know the setting off the top of my head. Go through and double check them anyways.
I was thinking it was starting Kodi like at startup rather than bringing it up from the background. Because that would cause a delay as it takes Kodi a minute or so to have everything in order.
Are you sure the addons disappear? Do you know how to manually set shortcuts in skin settings?
It sounds like your skin is resetting, after you installed a preconfigured build.
smartymcfly said:
I misunderstood what was happening to you. And I don't know the setting off the top of my head. Go through and double check them anyways.
I was thinking it was starting Kodi like at startup rather than bringing it up from the background. Because that would cause a delay as it takes Kodi a minute or so to have everything in order.
Are you sure the addons disappear? Do you know how to manually set shortcuts in skin settings?
It sounds like your skin is resetting, after you installed a preconfigured build.
Click to expand...
Click to collapse
I've only ever used a preconfigured build once. There's only a few add ons I use. It literally deletes everything. I even have to re-enter the url for the repo to download the .zip. It's as if I run clean start.
My Google Assistant suddenly stopped working. Whenever I tried to issue a command, it returns "Cannot reach Google at the moment.".
Tried in my old phone, there are no problems.
Tried restarting but the problem still persists.
Anyone experienced this? Any solution?
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried, didn't work.
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Sea21 said:
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Click to expand...
Click to collapse
Did this one but didn't work. Also, I only have Chrome as browser so I guess this isn't the problem.
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried uninstalling, rebooting and re-updating the Google app. The Assistant is working again but Continued Conversations doesn't work. There were also times after I did this, the problem returned.
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Starzboy77 said:
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Click to expand...
Click to collapse
Not rooted and already set to Full, Continued Conversations still doesn't work.
danw_oz said:
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Click to expand...
Click to collapse
ok i forgot to off capital letteres
I have struggled with this recently. Here's what worked for me. I noticed that on cellular it worked, but on my WiFi it did not although it had in the past. The trick was to go into WiFi settings and tell it not to randomly change the Mac address (use Device MAC). I suppose that -- maybe only with some routers -- the changing MAC is upsetting the NAT translation and your phone is making an outbound connection but that's just a theory.
I had the same problem, had used adaway and blocked some dns requests, cleared these and Hey Google worked again. Cheers.
Usually, the only times I have trouble with the Assistant this way are when I get in my car, hook it up for Android Auto, and in my driveway, I'm kinda in range of my Wi-Fi but not very well. It doesn't usually take very long for my phone to switch to mobile data on its own in this situation (and it took my Samsung way longer), but once it establishes a reliable connection via mobile data, then it's fine.
Necro'd thread to post POSSIBLE FIX:
Go into Developer options and disable 'App Wi-Fi Multi/Broadcasting Filter'. I'd turned it on randomly and forgotten, and have been suffering ever since. Turning it back off allows the app to connect to the internet, despite your phone being locked until standby.
Going off to cross-post this elsewhere because I've searched SO many pages trying to find a fix, and nobody mentioned trying this.