Question Do you have the same Google Pay issue (Google Pay/Wallet fails to trigger if multiple payments are attempted per app sesion.) - Red Magic 8 pro

Google Pay/Wallet fails to trigger if multiple payments are attempted per app sesion.
Example scenario: Make a payment at a store. It works fine. Go to another store two minutes away and attempt to make a payment. It doesn't work. App must be force-closed and restarted for it to work again.
How to reproduce: Attempt to make multiple consecutive payments within a single app session. (Due to large amount of RAM on the phone it's unlikely that the wallet/payment app will ever close itself to save memory so a "single app session" can last a long time.)
Software Version: NX729J\_EUCommon\_V4.12

Related

[Q] amazon app store

is anyone else having issues with the amazon app store? i'm rooted and running jellybomb. i had this issue on a previous device, and it turned out to be that i had too many registered devices. i checked for that, and it isn't that this time around. every time i put in my email and password, it says "Please enter a valid email and password." it also happens on the kindle app. i can log into my account on the plain amazon store app just fine though. any ideas?
most likely you've got a lot of devices activated (happens each time you flash and register the device after installing). just to to your device management and start deactivating devices you no longer use. or deactivate them all and reactivate as needed.

"app" could not be downloaded due to an error (920)

I just booted my brand new 2014 note and when the home screen finally showed up the notification bar was full of warning sign/exclamation marks each mentioning a different app saying "<app name>" could not be downloaded due to an error (920)".
I've bought well over a dozen Android devices through the years and they've all downloaded my set of apps just fine. Some of the apps that get downloaded cannot be found on the app store any more as the developer packed up and left, but they still download when I get a new device.
But, this error essentially means that none of my initial download of apps (which is the only way I get some of my legacy apps) didn't happen.
Any thoughts on troubleshooting this? I didn't find any references to the problem in the Note2014 forums.
Also, if I can get the downloads to work, any thoughts on triggering it to do the "brand new device download" again?
FWIW, I did try a factory reset once the new system update downloaded to see if it would download the apps with the new OTA version of the play store, but the same thing happened all over again...
Note that the standard solutions you find on the web include removing your Google account and adding it back and force stopping the Google Play Store and then clearing its data and cache.
I recreated the account about 4 times and cleared the data and cache about 15 or so times and one of those times it managed to download just updates for the pre-installed apps, leaving me with none of the 100 or so apps I usually have. I then tried recreating the account and clearing the data again a few times, but it stubbornly refused to believe it had any more work to do.
Then I did another Factory Reset after all of that, hoping that the gremlins were asleep, but it came back up to the notification list full of hundreds of 920 errors. I also found a thread on the web about someone asking about retriggering the initial download of all of the apps and nobody could find a solution - they eventually gave up and just manually reinstalled all of the apps. That isn't really a good solution for the hundreds of apps that I typically carry and isn't even possible for the 5 or 6 that are no longer searchable on the Play Store (they must be downloaded in that initial download or they won't appear. I can get their 920 notification errors, but I can't use that to trigger another download of the original app...
I've had the same issue. Usually, I just turn the device off for a bit, turn it back on and it's fine. It seems to be an odd issue. If it lasts longer than a day I'd try the factory reset, not right away however.
The problem is you have more than 5 devices attached to your android play store account. Go into google play and remove some of your older devices.
skyline23 said:
The problem is you have more than 5 devices attached to your android play store account. Go into google play and remove some of your older devices.
Click to expand...
Click to collapse
That sounds like the most knowledgeable advice so far, but I'm not sure how to follow it. I found where my devices are listed in the play store (play.google.com => gear icon => settings) and I do have more than 5 devices (8 currently listed including the new 2014 Note) on the account, but...
- there is no way to remove them. All I can do is hide them (visibility).
- There were only 4 total that weren't hidden, including the new Note.
So, if this is an issue of more than 5 visible devices, I didn't even have 5 visible with the new tablet. If it's an issue of deleting them from the account, there is no option for that (only changing their name and a checkbox for visibility).
All of them have a "last used" date within the last couple of years. Perhaps there is a 2 year timeout?
I just did a factory reset after updating the visibilities in my Google Play account. Unfortunately, I think Google has shifted from "downloading the apps from your old devices" to "Oh, hey, we recognize that device - it was the one you didn't download any apps to, right?" and so now I'll never be able to get that factory fresh download unless someone knows the magic to make Google treat it like a brand new device.
Sorry I wasnt clear. If you make then not visible, thats the same as deleting it. If you make the note not visible, then google should see it as a new device. Are you sure you're checking the auto reload option when you are setting up the note?
flarbear said:
I just did a factory reset after updating the visibilities in my Google Play account. Unfortunately, I think Google has shifted from "downloading the apps from your old devices" to "Oh, hey, we recognize that device - it was the one you didn't download any apps to, right?" and so now I'll never be able to get that factory fresh download unless someone knows the magic to make Google treat it like a brand new device.
Click to expand...
Click to collapse
skyline23 said:
Sorry I wasnt clear. If you make then not visible, thats the same as deleting it. If you make the note not visible, then google should see it as a new device. Are you sure you're checking the auto reload option when you are setting up the note?
Click to expand...
Click to collapse
I had downloaded a bunch of apps last night (I was up to the F's by scanning the app list on my old tablet), but this was worth an experiment to try.
I had already unchecked all of the devices other than my Notes and my phone, so I unchecked the tick mark next to the new unnamed device and factory reset my 2014 Note. It came back up and managed to start installing apps without errors - woohoo!
But, it only reinstalled the apps that I had been busy downloading last night. Perhaps I mucked it up when I started downloading apps and so now it remembers my device even if it was unchecked?
I found a few apps that aren't "searchable" by going to the "All" tab in the list of "My Apps" in Google Play Store. One of them worked, but another (the Doodle Android app for the Doodle.com service) refuses to install. That may be due to the fact that they have modified the app to be "not compatible with any of your devices". The version installed on my old Note gets an error on startup, so they may have manually sabotaged it (and given that they now have a $3 pay app, I can imagine why). If I remember my device install history I seem to recall that the initial app install could install older versions of apps that aren't accessible from the Play Store (and I relied on that in the past to avoid updates that broke things when I got a new device) so it might have been able to install the version that I last installed on my old Note, but in this case it probably wouldn't have worked out of the box.
Still, at least some of the withdrawn apps are still visible in the "All apps" tab...
Probably just version conflicts. I have a lot of apps I paid for that wont show up and install on my note 10.1. Even some apps that work on my note3 wont be compatible with the 10.1. Your 'all apps' should always show you the apps you paid for and workable. As for pulled or discontinued apps, try finding the apk and side loading them.
skyline23 said:
Probably just version conflicts. I have a lot of apps I paid for that wont show up and install on my note 10.1. Even some apps that work on my note3 wont be compatible with the 10.1. Your 'all apps' should always show you the apps you paid for and workable. As for pulled or discontinued apps, try finding the apk and side loading them.
Click to expand...
Click to collapse
I assume you are referring to my example of the Doodle app that won't install?
The apps that failed to download when I did my most recent factory reset are the ones that I didn't manually install last night. It was 1:1 as far as downloading only those apps (A-F) that I had downloaded last night and none of the others. It looks like the system has permanently remembered the app set for my new device whether or not I uncheck it from my list of active Google Play devices...
I see.. I guess you'll just have to go to 'my apps' and install manually one by one. Have fun with your note. It's an amazing device!
skyline23 said:
I see.. I guess you'll just have to go to 'my apps' and install manually one by one. Have fun with your note. It's an amazing device!
Click to expand...
Click to collapse
grrr. many of my games, including crystal defenders and need for speed most wanted are telling me i have to buy the app or the device isn't authorized for this game. never had this problem before, just using my google play account as usual. advice?
Google playstore probably detected that you had too many devices using the same play account. Dont think theres a work around
I had this on my first one..
Then it filled up the memory with hardly any app installed and kept boot-looping. Same results after restoring so I returned it and bought a new one. No more issues! I didn't restore backups from Google though.
For me Method 1 worked
Here are couple of fixes for the infamous error 920 or “App could not be downloaded due to an error 920” :
Method 1:
Turn your wi-fi off
Turn your wi-fi on
Run Google Play Store and install or update the app
Method 2:
Go to settings>>Accounts>> Delete your Google account synced with Google Play.
Restart Phone and add your Google account back in the settings. Alternately, add a different Google account.
Run Google Play Store and download your app.
Method 3:
Go to settings >> Apps >> Open “All” tab
Find and click Google Play Store >>Clear Cache and Clear Data
Now from the same tab uninstall Google Play Store Updates
Restart your phone, open Google Play Store and install the app
What worked for me
1.First Remove your google account from the device
Settings -- Accounts -- Google -- (select your email account) -- Remove
2.Then clean cache and data of Google Play store
Settings -- Application Manager -- Google play store -- remove cache, remove data, force stop (in that order)
3.Then turn off for 15 seconds
4.Add your account again on Google accounts
Settings -- Accounts -- Google -- (sign in with your account)
It worked well after that!
And I tried many other options before without it working.
As quick commercial if anyone is having problems with the stupid google update that makes the tablet not access properly the SD Card, I just found an app that amazingly fixed it with one click. Only for rooted users:
NextApp SDfix
Works fast and after a reboot you can use your SD card again!

RPC:S-7:AEC-0

After having it for a day, my Pixel C is already getting replaced under warranty.
Whenever I try to make a purchase of a paid app on it, I just get an error message "Error retrieving information from server [RPC:S-7:AEC-0]". Purchases work fine on my Nexus6P so the issue seems specific to the tablet. Downloading updates, pre-purchased apps or new Free apps works fine, error only happens when trying to make a purchase.
Have tried all the troubleshooting steps I can find online, clearing data from Play Store and Google Framework Services, no effect. Have removed my Google account from the device, rebooted and then re-added the account, no effect. Done a complete factory reset but still the same issue when I go to the Play Store and try to make a purchase of any paid for app.
I had several payment methods on my account, one of which was expired, but I've removed that and still the same error. I've got over £11 of credit on my Google account anyway and was only trying to purchase something that costs less than £3, so payment cards shouldn't have come into it.
Contacted Google Support and they called me back, said they're going to send a link for me to order a brand new device and instructions on returning the old one.
On the one hand, it doesn't seem like something that would be caused by a hardware issue. But on the other hand, it doesn't seem like an account issue since it's specific to just this one device. Looking around it seems this is a relatively common error, but just removing and re-adding the Google Account should normally fix it.
I'm not running a custom ROM or anything, not even rooted, just running the tablet as it comes (with updates installed)
I've not had any issues like that on either of my Pixel Cs (replaced one under warranty due to the lockscreen pattern bug) so I'd imagine a replacement should sort your issue.
Very strange though... Fingers crossed it gets sorted for you.
Someone has mentioned to me that it could be an issue with the hardware storage of the root certificates that's the problem, which makes sense since the error occurs after the Permissions prompt, at the stage where the Play Store attempts to access the payment information on my account.
Received my replacement Pixel C and still got exactly the same issue.
Whenever I try to purchase an app that costs money, I get an error,
"Error while retrieving information from server.
[RPC:S-7:AEC-0 ELVS-P3QO-E625O]"
(Everything after the AEC-0 is different every time)
This is immediately after turning on the tablet for the very first time and going through the setup process.
Worried that something is wrong with my Google account and that I'm going to have exactly the same issue even if I return it and got a different tablet. But it still works fine on my 6P phone is the thing.
1. In our Android terminal, we go to the Settings
2. Then to Applications
3. Here locate the following FRAMEWORK OF GOOGLE SERVICES:
4. We select Google Services Framework, stop the service, and then delete the data.
5. Then, we locate the service also Google Play, and do the same operation, stop and delete data.
6. After doing this with the two services, reniciamos our Android terminal and will try to download an application from Google Play, we see that already operate normally. Disculpame by Google translation.
chinimen said:
1. In our Android terminal, we go to the Settings
2. Then to Applications
3. Here locate the following FRAMEWORK OF GOOGLE SERVICES:
4. We select Google Services Framework, stop the service, and then delete the data.
5. Then, we locate the service also Google Play, and do the same operation, stop and delete data.
6. After doing this with the two services, reniciamos our Android terminal and will try to download an application from Google Play, we see that already operate normally. Disculpame by Google translation.
Click to expand...
Click to collapse
Did all that on a call from a Google troubleshooter, but still the same error.
Definitely looking to be an issue with my account from some further testing though.
Just created a new account and added my card as a payment method. Tried to make a purchase and it goes through fine.
The only difference with my regular account and the new account is that my regular account has some Google Play Store credit on it from the Opinion Rewards app, and has a fair few devices registered against it.
I'm wondering if it's possible that my account just has 'too many' devices against it, but I can't see any way to actually remove an old device from my account (My old S3 phone seems to be on there 3 times and I now have two Pixel C tablets registered against it)
Removed the new account from the tablet and re-added my original account. If I go to the "My Account" section of the Play Store on the tablet, I get the same error message when it tries to retrieve/display my payment methods. But again, only with my primary account on a new device. My old devices that were already registered can do this no problem. So the issue seems to be that new devices aren't correctly registering against my account, or something along those lines.
https://security.google.com/settings/security/activity?pli=1
chinimen said:
https://security.google.com/settings/security/activity?pli=1
Click to expand...
Click to collapse
I can see my current devices on there, but not the older ones. But I can see the older ones on my Play Store devices list strangely enough.
The device I'm having trouble with is listed on there and doesn't state as having any problems.
I had another callback from Google and the issue is being escalated, so we'll see how it goes.
El goog don't advertise this, and might be reticent at first, but you can get them to delete all your devices (not the same as you account) from 'registered' and then you begin again. Usually you only have a number (4?) you may disconnect every year from the total of 10 (I think).
In your case, I've no doubt they'll do it.
Had this problem too on my Sony Android TV. In my case the problem was a voucher code (and trying to pay with it, paying normally worked fine), I've activated over the chromecast offers page. The google support wasn't able to delete it, but the unredeemable voucher disappeared after a few months.
Hm, will see if I can get Google to remove some devices from my account. There's 8 showing on there at the moment when I go to Settings on the Google Play Web store, 4 of which need to be removed (3 old phones and the first Pixel C tablet), though these don't appear in the Android Device Manager.
I'm also wondering if the issue lies with the Google Credit I have on my account, all of which was earned through the Opinion Rewards app. I'm tempted to try just spending all of it via another device to clear it from the account and see if that sorts things. Even if it doesn't it's only about £8 worth, and it's not like I paid anything for it.
Cracked it.
It was something weird with my account, but also something I could fix.
I downloaded the Firefox browser onto my Pixel C and accessed the Play Store webpage through there, going to the My Account section where my Payment Methods are listed. I noticed that there's a payment method for my mobile carrier that I set up on my old Sony Z2, but was also available on my Nexus 6P. I removed that payment method, then on the Pixel I cleared the Data/Cache for Google Play Framework and Google Play Store apps, then restarted. After that, my Pixel C Play Store app can now access my payment information and make purchases.
No idea if it was removing the carrier payment method that did it since that method was causing some kind of conflict on a non 3G tablet, or if it was accessing the Play Store via a third party browser app which kicked some kind of authentication into gear.
Either way, a very weird issue thankfully solved! I've responded to my Google Support ticket with the update as well, so hopefully they can become aware of a possible issue.

Multiple NFC payment apps

Does anyone use multiple NFC payment apps with any success?
I have Android Pay for my personal debit card and Barclaycard for my work expenses.
Unfortunately I can't get the two to cooperate. If Barclaycard app isn't set as the default tap and pay app it simply disables NFC payment unless you go into the app and click pay now.
My plan was to set Barclaycard as the default and use the tap and pay option "pay with default unless another payment app is open". This didn't work as even if I open Android Pay the Barclaycard app always wins and processes the payment.
I tried setting Android Pay as default and going into the Barclaycard app and hitting the pay now button. Although it sat there waiting to be held against the payment terminal, as soon as I did so Android Pay processed the payment.
So, it seems that the setting to use another tap and pay app if it's open doesn't work.

(Q) How can I disable Instant Apps for Android

Like the title says, I've noticed since updating to 7.1.2 at least 2-3 times a day I am thrown a notification for "updating Instant Apps" but it never tells me if it was updated or installed. I tried going to Settings -> Google -> Instant Apps and it is disabled yet these apps are auto-downloading and installing in the background. I have auto-updates off on the play store but this still occurs.
Is there anything I can do to disable or at least cripple the instant apps? I'm reading the purpose of instant apps is so you can try an application without installing it, I do not want to test drive apps like Buzzfeed so however I can disable it would be great
fatapia said:
Like the title says, I've noticed since updating to 7.1.2 at least 2-3 times a day I am thrown a notification for "updating Instant Apps" but it never tells me if it was updated or installed. I tried going to Settings -> Google -> Instant Apps and it is disabled yet these apps are auto-downloading and installing in the background. I have auto-updates off on the play store but this still occurs.
Is there anything I can do to disable or at least cripple the instant apps? I'm reading the purpose of instant apps is so you can try an application without installing it, I do not want to test drive apps like Buzzfeed so however I can disable it would be great
Click to expand...
Click to collapse
So, using Titanium Backup I couldn't find the package com.google.android.instantapps.supervisor but using a root explorer I found the application in /data/app/com.google.android.instantapps.supervisor-2
I also found saved data in /data/data/com.google.android.apps.instantapps.supervisor
I have no idea if this will prevent the service from auto-updating as it has been without permission but I know where it is now...
Update: Deleting both folders causing settings to crash when you go to Settings -> Google -> Instant apps, so it might be deleted off my phone entirely. I will update if I see the application re-install itself
Instant apps are temporary apps. So you can't uninstall them or disable it. It's a feature built into Android that is not going away. Your only option is to install a rom without Gapps. Otherwise deal with it.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Instant apps are temporary apps. So you can't uninstall them or disable it. It's a feature built into Android that is not going away. Your only option is to install a rom without Gapps. Otherwise deal with it.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
deleting those two files seemed to have broken that feature.
My issue was that I disabled that service through settings as suggested by one of the google support pages but it would still download and install "Instant Apps" the service throughout the day, not the actual temporary apps themselves. So it's been dealt with lol
oh man, when i saw this i thought i had a virus on my phone.
especially when i couldn't find anything named "instant apps" in the app drawer
I am hoping that this will work for me as well. The first time I saw the instant apps pop up I just connected to a free wifi in Mexico and freaked out. This seriously bothers me. I uninstalled it and it came back update after update. I also will not be using any instant apps, so this is something I want to break.
speedee12 said:
I am hoping that this will work for me as well. The first time I saw the instant apps pop up I just connected to a free wifi in Mexico and freaked out. This seriously bothers me. I uninstalled it and it came back update after update. I also will not be using any instant apps, so this is something I want to break.
Click to expand...
Click to collapse
some how it was pushed back on to my phone. this is not a permanent solution...
so I'm trying to disable this through other means now and I found something interesting? I need someone with more experience to chime in as far as what these* lines* do*.. and where I found it...
so in /data/data/com.google.android.apps.instantapps.supervisor/shared_prefs/phenotypeConfigurations.xml there are these three lines:
<boolean name="Supervisor__enable_instant_apps" value="true" />
<boolean name="Supervisor__disable_url_resolution" value="false" />
<boolean name="TestFeature__enable_test" value="true" />
I flipped the value of these three entries to see if this will disable it. I find it odd that for the first line it was set for "true" when the settings say it's off. I will update again if I see this come back. My coworker had suggested that this may be built in to the Google app itself? Let's see...
so I had to unroot my phone because I forgot to log into snapchat, then re-root after, and Instant Apps was back yet again. The changes I made to the XML file persisted but the app was back.
I think I found a way to remove it entirely. I used Root Explorer, idk what other applications would work for this. So I navigated back to /data/app/com.google.android.instantapps.supervisor-1 and I clicked the base.apk and I had an option to uninstall, I did this then rebooted my phone to see if reboots are why it fixes itself except the entry for Instant Apps has been removed from settings. This appears to permanently remove this feature.
every time I think I fix this it keeps coming back lol, I finally called Google Support and this is the first they are hearing of it. The application re-installed itself at 430-some Mountain Time on it's own, other times it re-installs upon reboot. I'm going to find a way to cripple it if google cant
I recommend calling support to let them know that Instant Apps is enabled even though the switch says it is disabled.
fatapia said:
every time I think I fix this it keeps coming back lol, I finally called Google Support and this is the first they are hearing of it. The application re-installed itself at 430-some Mountain Time on it's own, other times it re-installs upon reboot. I'm going to find a way to cripple it if google cant
I recommend calling support to let them know that Instant Apps is enabled even though the switch says it is disabled.
Click to expand...
Click to collapse
I have the same annoyances, "Installig Instant apps" notification appears randomly during the last month, and reading in the logcat they are updates/patches to the new feature, managed by finsky app (Play Store). The most scaring thing is that one time it appeared also during mobile data connection, which is not acceptable (and 800kb background data from Play Store). Google is being too aggressive with it. Why not simply integrate it and update it along with Play Services like the other 1000 google APIs ? !on WIFI!
Thank you for your tests, unfortunately the update process seems to be triggered by Google Play services itself or by Google play store.
I searched for related alarms/wakelocks in Amplify and could only found one wakelock coming from com.google.android.apps.instantapps.supervisor itself: .ExperimentUpdateService. I decided to keep it as this probably isn't the trigger.
ninestarkoko said:
I have the same annoyances, "Installig Instant apps" notification appears randomly during the last month, and reading in the logcat they are updates/patches to the new feature, managed by finsky app (Play Store). The most scaring thing is that one time it appeared also during mobile data connection, which is not acceptable (and 800kb background data from Play Store). Google is being too aggressive with it. Why not simply integrate it and update it along with Play Services like the other 1000 google APIs ? !on WIFI!
Thank you for your tests, unfortunately the update process seems to be triggered by Google Play services itself or by Google play store.
I searched for related alarms/wakelocks in Amplify and could only found one wakelock coming from com.google.android.apps.instantapps.supervisor itself: .ExperimentUpdateService. I decided to keep it as this probably isn't the trigger.
Click to expand...
Click to collapse
yeah that's now my only worrisome complaint is that it ignores the play store settings and will download over any network connection. You can try submitting feedback through settings and suggest they fix this part so that it updates as you said. Thanks for the additional info, I'll try disabling that and report back if it makes any difference. I doubt that's the source of the problem though so I uninstall the apk so something else must be initiating it.
Thank you guys for this thread! I have the regular Pixel and have been seeing this happen... "Instant Apps" was disabled but somehow still updating either itself or something else, and I wondered if there was an additional switch somewhere to disable it. Looks like the answer is no. ?
Sent from my Pixel using Tapatalk
So I noticed every time the play store found an update, magically Instant Apps was back. I began to notice that this may be a service built into Play Store and not the Google app itself. So I had an idea, I went into Settings for Android and turned off background data for Play services. Obviously this will affect quite a bit, but honestly I am at that point from fighting this feature that I'd gladly give that up. So far after 2 days I have not seen the application re-install itself. It has been more permanent that the other solutions I've had so far.
There's an article from XDA in Analysis and Opinion talking about Instant Apps and Play Store 7.8.15, apparently this issue is affecting people all the way down to the Samsung S5... although people are hesistant to believe this issue exists for whatever reason.
You can cripple it by restricting its access to internet via firewall. Unfortunately this method also drives up battery consumption as the firewall does jujitsu with "Google Play services for Instant Apps" - I am actively fantasizing about taking my baby sledge to this thing and going back to a "dumb"-phone that doesn't have all this drama constantly! I'm using an S5 right now. This is definitely a google thing. They have a similar self-install-without-asking "feature" on windows via their chrome browser. Just look up "SwReporter" in that program's directory. It self-populates with an executable as you use chrome normally and there is no option in the program for it to not do that. You can safely make a shortcut to that directory and empty it out regularly to restrict its functionality which is presumably for keeping an eye on you. I am also trying an alternate method of changing security to prevent write access to that directory. I have no idea how to do that on an unrooted android. Any ideas? And does anybody know how to cripple "instant apps" malware/spyware backdoor "feature" on an unrooted device without eating battery like crazy?
Today I noticed that Instant Apps was installing without my permission. When I clicked on that notification, it brought me to the Google Play Store. (In Google Play Store, I have auto updates disabled.) I have an unrooted Galaxy Note 4 and I can't even find the settings for Instant Apps under the Google settings. Why aren't the settings there? I found the app in the Apps settings called "Google Play services for Instant Apps" (thank you G1A). I cleared it's the cache and data and then uninstalled it. So I'm assuming it will not come back but you never know.
EDIT: Well the "Google Play services for Instant Apps" reinstalled itself AGAIN WITHOUT MY PERMISSION. Getting sick of tired of Google's POMPOUS business ethics.
If it reinstalled itself.... then his would require root privileges in order to disable.
yeah this issue is annoying, it seems to initiate the download upon every reboot and each time it checks the play store for updates for any of your apps.
I found a way to disable it but it required freezing the app through Titanium Backup. I have NO CLUE why I couldn't see Instant Apps before in this list but it is listed as "Google Play Services for Instant Apps." It does not re-install or try to even download, does not show in Settings under Google, but if you look at the app itself in settings you will see it does still run. I am not sure to what extent but yeeeaahhh at least it doesnt seem like it can run anything
No problem As an update, changing security permissions (specifically for writing) for chrome's target folder Definitely (in windows 10) serves as an effective measure to blockade its ability to regenerate itself. This same method also works for microsoft edge located in the C-Windows-SystemApps folder. I presume that the programming methods would be analogous with android on google's end. Anybody know how to restrict write access to a folder on android? So long as it checks for a folder existing and it does exist (multi-decade programming approach) then it attempts to write to that folder. However, because it's already running in stealth mode (aka background) then it will never show an error message when it fails to execute, and it won't report back either, as that functionality depends on the contents of the targeted folder it is denied access to. It should be effectively crippled without excessive CPU consumption if you can just restrict its ability to write to the default folder that it installs itself in. Any ideas how to execute this kind of blockade?
UPDATE: As a way to cripple not Instant Apps specifically, but an entire host of functionality on the android platform, something called "Power Saving Mode" seems to knock out a key background runtime required for this pest to run. Unfortunately it doesn't let you pick and choose what it shuts off, so other useful apps may lose their functionality too. Post if anybody finds a more app-specific method!
Does this crap have its own separate package? If so, you could uninstall it and make a dummy APK having the same package name. This could prevent "updates" due to signing key conflicts, but might also break things...

Categories

Resources