Database Info

[Q] Constant re-downloading of OTA updates, how to disable?

Hi,
I have two Nexus 5 phones in my possession, both currently on 4.4.2 (Cataclysm and AOKP). I've recently noticed that the N5 running 4.4.2 Cataclysm has been using an immense amount of background data for 'Google Services' and did some digging to find out what it was. Turns out the phone is constantly re-downloading an OTA update, failing to flash it, then re-downloading it again, and so on.
There's a few attached images that are related - the file it's downloading, and the data used so far.
I found a couple of supposed solutions on various XDA threads and disabled the update service at startup, as well as installing FOTAKill.apk to system, but somehow it's still downloading and it's wearing me down as I can't figure out how to stop it. I understand an update to 4.4.4 would fix it, but i'd rather not as the person currently using the phone isn't all that keen on me taking time to flash & restore backups etc.
Are there any fixes for this that can be done by removing/disabling system services or the like? If it comes to it, I may just be able to block access to that particular ZIP in pfSense/SquidGuard.
Cheers.

ItsEmber said:
Hi,
I have two Nexus 5 phones in my possession, both currently on 4.4.2 (Cataclysm and AOKP). I've recently noticed that the N5 running 4.4.2 Cataclysm has been using an immense amount of background data for 'Google Services' and did some digging to find out what it was. Turns out the phone is constantly re-downloading an OTA update, failing to flash it, then re-downloading it again, and so on.
There's a few attached images that are related - the file it's downloading, and the data used so far.
I found a couple of supposed solutions on various XDA threads and disabled the update service at startup, as well as installing FOTAKill.apk to system, but somehow it's still downloading and it's wearing me down as I can't figure out how to stop it. I understand an update to 4.4.4 would fix it, but i'd rather not as the person currently using the phone isn't all that keen on me taking time to flash & restore backups etc.
Are there any fixes for this that can be done by removing/disabling system services or the like? If it comes to it, I may just be able to block access to that particular ZIP in pfSense/SquidGuard.
Cheers.
Click to expand...
Click to collapse
Download this: https://play.google.com/store/apps/details?id=cn.wq.disableservice
Disable SystemUpdateService in Google Play Services + Google Services Framework.
The app itself doesn't store any data so you can uninstall it afterwards.
Or;
Open /system/build.prop, change
Code:
ro.build.fingerprint=google/hammerhead/hammerhead:4.4.2/KOT49H/937116:user/release-keys
to
Code:
ro.build.fingerprint=google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys

I believe you can long press on the notification and just untick show notification.

nitramus said:
I believe you can long press on the notification and just untick show notification.
Click to expand...
Click to collapse
Doesn't stop it from downloading the OTA again and again. That'll just hide all notifications from Android System, and you might miss something else.

If people don't want to be bothered by important security updates and other goodies, why should we care? I fully updated my manta last night (factory image, latest twrp, omni, restore stuff) in 30min. In my opinion, you're just being lazy with both devices.

beekay201 said:
If people don't want to be bothered by important security updates and other goodies, why should we care? I fully updated my manta last night (factory image, latest twrp, omni, restore stuff) in 30min. In my opinion, you're just being lazy with both devices.
Click to expand...
Click to collapse
The ROM used is an outdated rom, Cataclysm(4.4.2), which is based on stock.
It's their preference for what they want to use.

[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"

[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
Unfortunately, Hangouts has stopped.
Click to expand...
Click to collapse
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
Unfortunately, Google Apps has stopped.
Click to expand...
Click to collapse
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
===============================================
UPDATE -
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This is like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.

bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
What was your installation process for Play Services 7.0.93?

Aerowinder said:
What was your installation process for Play Services 7.0.93?
Click to expand...
Click to collapse
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.

bagarwa said:
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
Click to expand...
Click to collapse
That is strange. I have the same version of Hangouts, but my updated version of Play Services is 6.7.76 (1745988-438).

bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.

My issue is hangouts keeps getting killed by the Low memory killer even though I have 1gb free ram.
I did some monitoring, hangouts Noe has to run its own process that I've never seen before and after a minute it caches itself, and I guess the cache is dumped later since I haven't opened hangouts in 5 minutes, I have to restart the app every time I need to use it. I also don't receive any messages during that time because the app has been killed. Any ideas?

chabsie said:
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
Click to expand...
Click to collapse
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.

bagarwa said:
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
Click to expand...
Click to collapse
Actually I'm using LBE as well and I suspected that it could have been the cause, and as you experienced, I removed all restrictions from the hangouts app and the problem still persisted.
My theory now is that a restriction that we've set on another app (or apps) is indirectly causing this issue with hangouts.
Does anyone know specifically which system apps could be connected to the functionality of Hangouts?
UPDATE: I've disabled restrictions on Youtube, Calendar, and Drive. This appears to have solved the problem.
Hangouts is working normally thus far and I haven't seen any error messages. Will update if things change.
I have a feeling that it's Drive.

What s
Is LBE? I'm stock phone sideloafed 5.1 and I have actually disabled hangout prior to upgrade now getting this error
Lee

Google play services "keep awake" disabled could cause it

I let all my apps keep awake in app ops and so on, but still have an issue with hangouts. It gets killed by system 5-10 minutes of not using it even if I leave it in background

2nd Update:
The problem is persisting again... my hypothesis has been disproved.
Any other suggestions or discoveries would be appreciated. I'm trying to find a way to fix Hangouts while keeping privacy settings in place as much as possible...
If XPrivacy was working for Android 5.0+ this issue would disappear.

I re enabled hangouts and updated it and not had the issue since

Play Service 7.0.96 from http://www.apkmirror.com/apk/google-inc/
Hangouts (+LBE) works fine by 5.1
Nexus 5 32GB, Android 5.01

Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)

I had a similar issue, so I rolled back hangouts to 2.5x and it's working fine now, YMMV. of course this may not be a viable solution to you but a working older version is better than a non-usable latest version.
Cheers!

Well, the only thing I can think of, in my circumstances, is that I had hangouts disabled when I updated to 5.1 (I don't use it). So yesterday I enabled it, cleared data, and disabled it again, and so far no crash. Maybe something got changed in the update and it didn't like the fact hangouts was disabled. Again, your issue may vary.

spark001uk said:
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
Click to expand...
Click to collapse
The new play services pretty much renders your phone useless due to nonstop update wake lock, (read more on the cataclysm ROM thread, like last 30 pages). The only way to fix the wake lock so far is to flash the cataclysm ROM patch (idk if it will work with stock ROM but it should) and it blocks the wake lock.
See attached picture below, that's how bad the new google play services is.
As for hangouts I got UKM and lowered the low memory killer to a minimum and disabled laptop mode (I'm using elementalX) and hangouts works just fine for me now.

russian392 said:
The new play services pretty much renders your phone useless due to nonstop update wake lock.
Click to expand...
Click to collapse
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?

spark001uk said:
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
Click to expand...
Click to collapse
Yes, it would.

[Q] Ongoing issue with "Chrome is not responding"

Firstly I want to apologize if there's a thread on this. I tried searching and didn't find anything. Google fails me as well.
For a few months now, Chrome has been driving me insane on my stock nordic Z3 (5.0.2 with the .690 firmware). I also have the most recent version of Chrome installed.
Every single time I open the app, it works for about 2 seconds, then completely freezes for around 15 seconds after which a message pops up stating "Chrome is not responding. Would you like to close it?" If I press "OK", it obviously closes the app and the problem appears again when I restart it. If I choose "wait", Chrome works just fine until the next time I open it. EDIT: The freezing problem started happening three times in a row a few days ago.
This happens every single time I open the app, whether launching it or opening it from the recent apps menu.
I'm pretty certain the problem has been around since the v39 build of Chrome, as 38 worked just fine. I have tried everything I can think of to fix it. Uninstalled updates and re-updated it, updating to lollipo didn't help, I also did a completely fresh install today (repairing via Sony Bridge for Mac) and it didn't help either. And apparently I can't go back to v38 anymore since lollipop doesn't seem to support it.
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.

Try clearing the data in settings - apps - chrome

gregbradley said:
Try clearing the data in settings - apps - chrome
Click to expand...
Click to collapse
I have done this too. Also, the problem persists even with completely fresh installs of Chrome.

Remove your google account, restart the phone and restore your google account

gregbradley said:
Remove your google account, restart the phone and restore your google account
Click to expand...
Click to collapse
Tried it, sad to say it didn't work either. Interestingly it now does the same 15 second freeze, but without the error message in the end. Curious indeed.
EDIT: Got the error message again.

Does this happen on Wifi or on data?
If on wifi is always the same router?

gregbradley said:
Does this happen on Wifi or on data?
If on wifi is always the same router?
Click to expand...
Click to collapse
I Use data 90% of the time, and various routers when on wifi. The problem occurs in all circumstances.

Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.

gregbradley said:
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
Click to expand...
Click to collapse
I have a completely untouched device. So no root, locked bootloader and it's always been that way. Thus Nordic is the original region of my device.
I'd rather not flash back to kitkat, but I can tell you that I tried reverting back to v38 before updating to lollipop and it worked normally without the freezing issue.

This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this

gregbradley said:
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
Click to expand...
Click to collapse
I have the same version of chrome as you. The problem has persisted during every single update after v38.

ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?

gregbradley said:
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
Click to expand...
Click to collapse
How do I do that?

install a logCat app from the playstore

gregbradley said:
install a logCat app from the playstore
Click to expand...
Click to collapse
Does this require root? One of the apps I tried is requiring it and the other one isn't doing much either. Should I be doing something to make it work?

isshoni said:
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe try the beta version of chrome in case it's a bug which has been fixed but not yet rolled out to chrome. Perhaps try this first as it'll be quicker!
Perhaps it's some data associated with chrome that's getting pulled down after each restore. Perhaps you can try, on a desktop pc, backing up your bookmarks and then deleting them, and clearing chrome's data on your phone, then trying again? And if that doesn't work try getting rid of extensions (not that I think they should be pulling them down as chrome for android doesn't yet support them, although I'm sure I read years ago that one day they would). And anything else associated with your chrome account.
Another one, perhaps quicker (not sure) would be to see if you can associate your phone with a new google account with no previous chrome use and see if it goes wrong with that one. It would help to rule out account-related problems.
Another possibility is that it's not chrome causing the problem but something it relies on; google play services, for example. Perhaps clear data on any apps chrome could conceivably use.

I'm happy to report that my problem is now solved, though still a giant mystery.
My upper speaker broke and I had to get it replace under warranty. I got insanely lucky as they replaced both front and backside glass pieces, the frame, the screen module itself and of course the speakers. So I've now got a brand-new looking phone So happy.
Anyway, I complained about the software being a mess so they also did a complete reinstall and after that Chrome works absolutely perfectly. As magically does everything else too. Not yet a sign of lollipop's previous lagging and rebooting.
It still bugs me, however, that why would Chrome suddenly start having this unreasonable issue. I had tried everything suggested in this thread and nothing worked. My own clean install didn't work. I'm really quite bothered by this.

Overall Issues with S8+ i have.

First issue is app badges. When i read message or check missing calls whatever it is general issue, the notification badge on app icon does not reset it self. Badge keeps as it is for 1 hour and then reset. Tried clearing badge provider but no solutuon.
Cant install apps from google play normally, it downloads to %100 and stays as it is. When i kill the google play and restart it then it installs the app.
Randomly getting really laggy with device.
When i am on call with bluetooth headphone and using my device, the device gets laggy. Cant switch wifi or install apps. Its like device gets my actions but does not proceed. When i end calls it starts proceed my actions one by one.
Tried factory reset, reinstalling stock firmware, all same. My device is stock and never rooted.
Btw, I see touchwiz update on sammobile but neither samsung apps or google play does not update the launcher. I try to install the apk from sammobile manually but it gives error like i have an app as same name as it is. So cant update to last version of touchwiz i stuck at 6.1.02
Any help for these issues or explinations? Thanks.

Is your device snapdragon version?
Sent from my SM-G955F using Tapatalk

emremutlu said:
First issue is app badges. When i read message or check missing calls whatever it is general issue, the notification badge on app icon does not reset it self. Badge keeps as it is for 1 hour and then reset. Tried clearing badge provider but no solutuon.
Click to expand...
Click to collapse
I hate this, only choice is either install a new launcher or long press the icon and select "clear badge."
emremutlu said:
Cant install apps from google play normally, it downloads to %100 and stays as it is. When i kill the google play and restart it then it installs the app.
Click to expand...
Click to collapse
Not sure, it hasn't happened on my phone sorry.
emremutlu said:
Randomly getting really laggy with device.
Click to expand...
Click to collapse
Not sure, it's something that generally happens with Samsung devices.
emremutlu said:
When i am on call with bluetooth headphone and using my device, the device gets laggy. Cant switch wifi or install apps. Its like device gets my actions but does not proceed. When i end calls it starts proceed my actions one by one.
Click to expand...
Click to collapse
Odd, I haven't seen that before.
emremutlu said:
Tried factory reset, reinstalling stock firmware, all same. My device is stock and never rooted.
Btw, I see touchwiz update on sammobile but neither samsung apps or google play does not update the launcher. I try to install the apk from sammobile manually but it gives error like i have an app as same name as it is. So cant update to last version of touchwiz i stuck at 6.1.02
Any help for these issues or explinations? Thanks.
Click to expand...
Click to collapse
You tried everything, could be a hardware issue. As for the touchwiz update, it could be for a different version then yours. I wouldn't be worried if you don't see the update unless your seeing other people with the sane phone get the updates.
Sent from my SM-G955F using Tapatalk

None issue you mentioned I face it, by the way mine is Exynos edition.
Suggest Factory reset your phone, don't restore anything (this part is freaking important). Start as flash new phone setup.
As for Touchwiz, 6.1.02 is the latest version.

Snapdragon here, none of these issues are present on my device.

Exynos here. I did not facr these issues until last firmware update. After factory reset it was awsome for 1 week. Then again here my problems.

I highly suggest to return the phone to samsung and get a new one.. your phone seems to have a hardware issues.
I only have the common issues which is fingerprint sensor stops working sometimes. I never tried bluetooth so i can't confirm if i have any.
As many here also suggest that you should start fresh factory reset your phone and install your apps directly from the play store. If you had any problems with the playstore don't bather your self to fix the problem go directly to nearest samsung center and ask for an exchange unit.
Sent from my SM-G955F using Tapatalk

Snap dragon here and I have no clue what these problems are....thank goodness of course

Use Nova launcher. Problem solved.
Galaxy S8+ Black

clear cache from the boot menu. May help before you return it.

"Ok Google" not working on new 7 Pro

I tried uninstalling and reinstalling the Google app, clearing cache in app and on phone. Retrained the voice in Google app a dozen times. Nothing is working. Side note: my SIM card is still installed in my old 5T. the 7 Pro doesn't have a SIM card. Not sure if that is a factor. Assistant works fine. *UPDATE: "OK Google" will launch when prompted when display is locked but it won't answer or respond to whatever I ask it. "OK Google" will not launch or respond when phone is unlocked at all.

I'm having similar issues but mine stops responding once I connect to my car stereo... And doesn't respond even after disconnecting until I reboot.

7 pro?

Same issue OK Google will NOT work on the One Plus 7 pro for some reason on my end
Did all that was suggested , Clear Cache , Clear Data, Disable Google, Reboot, then Endable google, retrain my voice
But still on the home screen when I say OK Google nothing happens
Anyone have a FIX for the Oneplus 7 pro? Thanks
BTW Stock 9.5.7 GMA21AA Firmware
Model GM1917
STOCK Not Rooted

I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647

qwen3579 said:
I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647
Click to expand...
Click to collapse
Not rooted. Using Nova and I restored from a Nova backup if that matters.

robdam1001 said:
Not rooted. Using Nova and I restored from a Nova backup if that matters.
Click to expand...
Click to collapse
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?

rooted, with custom kernel and custom launcher. OK Google works like a charm.

qwen3579 said:
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?
Click to expand...
Click to collapse
Just did factory reset and ok Google is now working. It hasn't finished restoring, however. I'll report back once it has. What a pita.

UPDATE: OK Google is working fine after Factory Reset, (PITA), and full restore.

That is what I was afraid of ,doing a full factory reset
If anyone has another solution that avoids that please let me know
Thanks all

Mine seems to work when the phone is awake however I have noticed that for some reason the Google pill widget does not show the 'ok google' text that normally shows up on my other phones.
Using stock launcher so not a 3rd party problem.
Anyone else notice this?

Not entirely helpful here other than to tell you that I'm not experiencing the same thing. ?

Full factory reset as a solution, lol. C'mon guys

No better solutions? Are we the only unlucky ones here.

The similar issue I have also come across on my phone and believe me, it was very irritating situation as I am not getting any way to fix it. Even I was not able to understand why it was happening but after searching a lot, I have got some solutions given in one blog. So if you are also coming across the same issue like "OK Google Not Working" then try the below solutions:
Solution 1: Restart Your Android Phone
Solution 2: Force Stop Google App
Solution 3: Clear Cache of Google App
Solution 4: Turn Off Bixby [For Samsung Users]
Solution 5: Make Sure That OK Google Command Is Enabled
Solution 6: Check Microphone On Your Device
Solution 7: Turn Off Adaptive Battery And Battery Saver Option

An old one here but have you installed any third party notification app like notifybuddy or plus beat? Ok Google won't work with these installed. The only notification app that doesn't interfere is AOE.

I have noticed a similar issue with voice-to-text being terrible and when this is happening OK Google does not work although it could be problem that happens even after OK Google is working but the voice to text is terrible at recognizing words. After android 10