Database Develop

How to disable OTA lollipop without wakelock

If you decided to stick a bit longer with KK and lollipop OTA notification is bothering you - this is how you can disable it without wakelocking your phone.
Get something which disable service receivers/listeners (not just service like Disable Service app does). If you disable SystemUpdate service - this will wakelock your phone - thanks to Google wonderful design, which become "better and better".
But instead you disable 3 receivers for that service:
com.google.android.gms.update.SystemUpdateService$Receiver - this will run on boot completed.
com.google.android.gms.update.SystemUpdateService$ActiveReceiver - this will check for OTA on connectivity change.
com.google.android.gms.update.SystemUpdateService$SecretCodeReceiver - this will check for OTA when your phone "handles" the secret code.
So, by doing this, SystemUpdateService will never have a chance to get OTA and you phone will still sleep like a baby.
Now, what apps will allow to disable receivers? Well, I compiled my own Autostarts. It's old but still job can be done.
You can find something in play store or I can upload my autostarts if you want me to.
Anyway, in summary do not disable GooglePlayServices.SystemUpdate service just its 3 receivers.
EDIT: Here, this is autostarts I've compiled long time ago but still can be run on KK and of cause ads free. Well, you have to "hunt down" those 3 receivers. Just open up one by one and read if this is one of those 3 and then disable it.

Vlad_z said:
If you decided to stick a bit longer with KK and lollipop OTA notification is bothering you - this is how you can disable it without wakelocking your phone.
Get something which disable service receivers/listeners (not just service like Disable Service app does). If you disable SystemUpdate service - this will wakelock your phone - thanks to Google wonderful design, which become "better and better".
But instead you disable 3 receivers for that service:
com.google.android.gms.update.SystemUpdateService$Receiver - this will run on boot competed.
com.google.android.gms.update.SystemUpdateService$ActiveReceiver - this will check for OTA on connectivity change.
com.google.android.gms.update.SystemUpdateService$SecretCodeReceiver - this will check for OTA when your phone "handles" the secret code.
So, by doing this, SystemUpdateService will never have a chance to get OTA and you phone will still sleep like a baby.
Now, what apps will allow to disable receivers? Well, I compiled my own Autostarts. It's old but still job can be done.
You can find something in play store or I can upload my autostarts if you want me to.
Anyway, in summary do not disable GooglePlayServices.SystemUpdate service just its 3 receivers.
Click to expand...
Click to collapse
I'd be interested in you uploading your compiled copy.

Thanks OP! I just used Autostarts and hunted for those 3 receivers. Now we wait and see if it worked.

It looks like it worked! I've rebooted 3 times since doing it and still no notification. Thanks again OP.

Vlad_z said:
If you decided to stick a bit longer with KK and lollipop OTA notification is bothering you - this is how you can disable it without wakelocking your phone.
Get something which disable service receivers/listeners (not just service like Disable Service app does). If you disable SystemUpdate service - this will wakelock your phone - thanks to Google wonderful design, which become "better and better".
But instead you disable 3 receivers for that service:
You can find something in play store or I can upload my autostarts if you want me to.
Anyway, in summary do not disable GooglePlayServices.SystemUpdate service just its 3 receivers.
Click to expand...
Click to collapse
I would like to receive your Autostarts.
I found several autostart apps on Play. Which is the one to install and use?

Anderson2 said:
I would like to receive your Autostarts.
I found several autostart apps on Play. Which is the one to install and use?
Click to expand...
Click to collapse
This is the one that I used, been using it for years. https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts

Any free ones? I'm just planning to use it for one thing: the ota notification.

Anderson2 said:
Any free ones? I'm just planning to use it for one thing: the ota notification.
Click to expand...
Click to collapse
ROM Toolbox Lite

Thank you very much. Worked perfectly.
Hope ota notice doesn't return.

Anderson2 said:
Any free ones? I'm just planning to use it for one thing: the ota notification.
Click to expand...
Click to collapse
Autostarts is free in F-Droid. And the method works perfect.

Thanks. I used RomToolbox lite which I already had. As you say, it's been perfect.

For those who need my autostarts.apk, I just added it to the first post.

Vlad_z said:
com.google.android.gms.update.SystemUpdateService$Receiver - this will run on boot completed.
com.google.android.gms.update.SystemUpdateService$ActiveReceiver - this will check for OTA on connectivity change.
com.google.android.gms.update.SystemUpdateService$SecretCodeReceiver - this will check for OTA when your phone "handles" the secret code.
Click to expand...
Click to collapse
Hi, if it can help, I've "hunted" these receivers in:
After startup
Connectivity changed
Secret code entered

spaniard said:
Hi, if it can help, I've "hunted" these receivers in:
After startup
Connectivity changed
Secret code entered
Click to expand...
Click to collapse
Disabling these 3 receivers in all those sections you mention, solves the wakelock issue?
Have you tested this throughout a full day?
Last time I tried this, I didn't disable all of them in all of those section.
My phone was awake 100% of the day...

Thanks Vlad_z and spaniard. These have to be disabled in both Play Services and Framework when they appear in each?

I found an easy method
I had already downloaded the one from the Play store, so I dont know about the APK in the OP..
But there is a... Yes... Search button, lol.
If you look for "SystemUpdate", it'll automatically look up all those receivers, and you're good to go.
Its working like a charm for me.
My 4.4.4 stock image is no longer checking for OTA or being kept awake.
Finally got my KitKat ART flying Nexus5 back.

ritchea said:
Thanks Vlad_z and spaniard. These have to be disabled in both Play Services and Framework when they appear in each?
Click to expand...
Click to collapse
Just in Play Services.

Deleted. Sorry.

Just used the root/autostarts method today and can confirm that it works! Thanks for the help.

Thanks Vlad_z... working so far. Damn that notification was annoying. Nice work and thanks for the .apk

Touchless Control stuck behind PIN lock

I have a XT1053 with stock 4.4.4 and have been having this problem for the last few months.
Somehow, the touchless control is now stuck behind my PIN lock. I have encrypted my phone, so the PIN lock is required. I used to be able to do things like "OK Google Now, what's the weather?" and Google Now would open and show me the weather, or send text messages. Basically the usual use, but recently the touchless control screen doesn't show when I say "OK Google Now", just the PIN screen. I can tell that the voice recognition is happening because Google Now will read me part of the weather, but usually gets cut off as the device goes to sleep before it finishes.
I'm not prompted to say or enter my PIN, I can enter it and get into the Google Now screen but not without using my fingers.
I haven't been able to find anyone else having this particular problem so I don't really know what to try. I've tried disabling Touchless Control, retraining, uninstalling updates (Moto Voice) all to no avail.
Anyone else seeing this? Any ideas?

Oh thank you. I was going nuts because I thought I was the only one. I posted on here as well and no one responded. I have been having this issue for the last few months ever since a Google search app update.
I have an exchange work account set up that forces me to have security on the lock screen. I have the pattern lock set up.
At this point I'm waiting for the lollipop update and hoping that it will fix that problem

Don't know why I didn't think of this before, I uninstalled updates to the Google App and everything is as it was before. If I can find a repository of various versions I will experiment to try and find which version broke.

Just FYI, I got the 5.1 update over the weekend. The updated Moto Voice app, and the latest Google search app are once again working together. I'm able to use the voice control without entering my PIN again.

Same here waiting paid off this time

Google Now can't unlock??

Hi all,
I'm running into an odd issue on the N6, although other devices seem to have this as well. . .
I used to be able to use google now to set alarm, send message, etc while its locked.
Now, doing the same things, google now replies that it can't complete the task until device is unlocked.
Is anyone else running into this and is there any way around it?
Thanks!

Bump ... help please?

rom you are using? and android version?

it only happens when the device is locked with a password or something similar. If you disable that you're good to go.
Sent from my Nexus 6 using XDA Free mobile app

I have this issue. I can't set alarms or reminders unless I unlock the phone. The voice prompt tells me so. Quite annoying. Hopefully they remedy it with smart voice unlock soon
Sent from my Nexus 6 using Tapatalk

This updated feature now affects texts via voice now. I can no longer wake my phone from sleep and send a text unless the phone is unlocked. More of a reason to move to a moto x pure now. what a huge step back.

arts711 said:
Hi all,
I'm running into an odd issue on the N6, although other devices seem to have this as well. . .
I used to be able to use google now to set alarm, send message, etc while its locked.
Now, doing the same things, google now replies that it can't complete the task until device is unlocked.
Is anyone else running into this and is there any way around it?
Thanks!
Click to expand...
Click to collapse
Hi, I just saw your post and I was having the exact same issue. The only way I can get around it currently is by rolling back to an old version of the "Google App" which seems to encompass Google Now, Voice Search, Google Now Launcher, and most importantly the OK Google "always on" functionality.
I went back through previous versions testing the "OK Google call _____" (screen off & device locked) feature until I found where it stopped working correctly and the "4.9.22.16.arm" version is the last one that does work the way it is supposed to. You can find older versions of the Google App on Apkmirror. Hopefully they track down the root cause of the issue and fix it soon.

OK Google - PROBLEMS

I use ok google all the time to send texts especially when driving. frequently i am getting an error where she says
"actually, i can't do that while the device is locked" after unlocking with fingerprint it isn't recognized that the device is unlocked for some reason
it seems to be a MIUI problem as there is a huge thread http://en.miui.com/thread-274084-1-1.html
anyone know a solution?
also, one suggestion from Google is to just turn on Trusted Voice so that you can use the OK Google command when the device is locked. when i turn this on the OK Google command does not work and is not recognized no matter what screen i'm on let alone with the device locked
anyone ran into similar problems with the Mix?

I have a similar issue...If I disable lock pattern and then re-enable it it will work. A bit of hit and miss really. Would love a proper solution if there is one.

bbourizk said:
I have a similar issue...If I disable lock pattern and then re-enable it it will work. A bit of hit and miss really. Would love a proper solution if there is one.
Click to expand...
Click to collapse
Same. I can't get it working from a black screen. My other devices will wake up and "listen". On the Mix, I have to activate the screen and then say ok google for it to listen. I did the resetting the lock screen and it did help get ok google to listen on the lock screen. So thanks for that.

I also have the same problem with the latest Google app but it works with version 4.92.16 except that I'm not able to use ok Google from screen off. I hope there's a solution to this

Not sure if i just haven't used OK Google enough yet, or if it has legit fixed the problem...but after converting google to a system app i have not run into this error yet with over 20 times using OK Google. we will see if it holds up.

did you have this problem before making it system app and went away after?

I figured this out.
Browse to Google App > Settings > Voice > "OK Google Detection" and enable "Personal results"
Kind of a workaround, since this allows actions when your device is locked, but works well for me.

I don't have that option for enable Personal results.
I only have
From the Google App
From Any Screen
Trusted Voice
While Driving
All four are enabled.

personal ressults has always been enable and still no joy.

I don't even have while driving.
Only three options.

I don't think it's a MIUI thing. It happens on my Google Pixel XL with the latest Nougat. Same message.

Google assistant not working when screen is off and locked

Hi
I cannot access google assistant when screen is off its working fine when phone is locked but screen is on but not working when screen is off
I have tried all option found on google and my all settings of lock screen are on but still when i say hey google when phone is locked and sceeen is off nothing happend

komalsaeed said:
Hi
I cannot access google assistant when screen is off its working fine when phone is locked but screen is on but not working when screen is off
I have tried all option found on google and my all settings of lock screen are on but still when i say hey google when phone is locked and sceeen is off nothing happend
Click to expand...
Click to collapse
sounds like a permisson issue. if you can't fix it yourself, your best bet is to contact support and raise the concern with them.

Akira_Kitsune said:
sounds like a permisson issue. if you can't fix it yourself, your best bet is to contact support and raise the concern with them.
Click to expand...
Click to collapse
All permission are on
All options are on