Database Users

How to get rid of upgrade nag messages

I am sure this is answered somewhere but it's hard to find. Apologies.
I am on JSS15Q, rooted, TWRP installed with no issues. I would like to permanently get rid of the upgrade nag message (I can temp get rid of it by accepting the upgrade and letting it fail).
I don't see any value in installing the upgrade.
Can you help ?
Thanks.

Get AutoRun Manager from the PlayStore.
Autorun manager - advanced mode, then in settings check 'show system entries' and then find Google services framework, and disable the one with 'system update receiver' in the name.

danvee said:
Get AutoRun Manager from the PlayStore.
Autorun manager - advanced mode, then in settings check 'show system entries' and then find Google services framework, and disable the one with 'system update receiver' in the name.
Click to expand...
Click to collapse
Thanks, installed, settings changed etc. but not understanding/seeing "the one with 'system update receiver' in the name"

Why don't you want to install the update?

homemadehitshow said:
Thanks, installed, settings changed etc. but not understanding/seeing "the one with 'system update receiver' in the name"
Click to expand...
Click to collapse
Do you have 'show system entries' enabled in settings?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

detonation said:
Why don't you want to install the update?
Click to expand...
Click to collapse
(a) It will not install because I am rooted and have TWRP (b) too many stories of people with no problems getting them after the update.
For a more major update I would do it but if it aint broke I aint fixing it.
danvee said:
Do you have 'show system entries' enabled in settings?
Click to expand...
Click to collapse
Yes, just didn't know which one to go after.

homemadehitshow said:
Yes, just didn't know which one to go after.
Click to expand...
Click to collapse
As show in the image. At the bottom- "system update service receiver".

Go to settings then apps then swipe left to all and click on Google services framework and untick show notifications
>^.^< Sent From Meow HTC One

DowntownJeffBrown said:
Go to settings then apps then swipe left to all and click on Google services framework and untick show notifications
Click to expand...
Click to collapse
Will that work on a stock N7, too? Or only rooted?

Looks like it to me... Running locked, unrooted Stock.

Vmurph said:
Will that work on a stock N7, too? Or only rooted?
Click to expand...
Click to collapse
It should work on stock I don't see why it wouldn't. But I root everything so I'm not sure lol
>^.^< Sent From Meow HTC One

Awesome, thanks! What other notifications is the 'Google Services Framework' responsible for? In other words, if I turn off its notifications, will I miss any other important notifications, besides the firmware update nag??

More easy way.
Long click on the notification - select information and then stop.
Sent from my Nexus 7 using Tapatalk

danvee said:
Get AutoRun Manager from the PlayStore.
Autorun manager - advanced mode, then in settings check 'show system entries' and then find Google services framework, and disable the one with 'system update receiver' in the name.
Click to expand...
Click to collapse
Cool, and thanks. Gonna give it a shot. I see two apps called "AutoRun Manager" though. This one and this one. Does it matter which one? Would either work?
EDIT TO ADD: I just tried the first one (as it matched your screenshot.) I went to Settings and enabled "Show system entries" as well as "Enable System app disable." Then when I went to the Google Services Framework and expanded it, I see that "com.google.android.gsf.update.SystemUpdateService&Receiver" was already disabled. I have never done this before and I'm on stock Android, KitKat 4.4.4, rooted via towelroot. So now I am wondering, does towelroot disable this by default, by any chance? Just wondering if I need to do anything further, and why this would be disabled for me already. Does it get enabled by some other mechanism, when an update is actually out?
Vmurph said:
DowntownJeffBrown said:
Go to settings then apps then swipe left to all and click on Google services framework and untick show notifications
Click to expand...
Click to collapse
Awesome, thanks! What other notifications is the 'Google Services Framework' responsible for? In other words, if I turn off its notifications, will I miss any other important notifications, besides the firmware update nag??
Click to expand...
Click to collapse
Good question, I am wondering about that too.
Sensamic said:
More easy way.
Long click on the notification - select information and then stop.
Click to expand...
Click to collapse
Seems to me that would just prevent the notification, but the update would still be downloaded and waiting to install. Am I wrong about that? I want to block any system update entirely (until I am good and ready for it, until Lollipop is properly rooted, etc.) I don't want it to download, I don't want to be nagged about it, I don't want my Nexus 7 to know about it at all. I'm thinking danvee's solution is more in line with that than simply "blocking the notification."

HealthService?

I was having problems with xposed and s health, so I turned it off. then HealthService started popping up errors, so I turned it off as well. I found the solution for this in another thread but now I can't turn HealthService back on... There's no button for me to click...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jideay said:
I was having problems with xposed and s health, so I turned it off. then HealthService started popping up errors, so I turned it off as well. I found the solution for this in another thread but now I can't turn HealthService back on... There's no button for me to click...
Click to expand...
Click to collapse
...edited
Sent from my VW S5 using your mom.

You need to remove Xposed, edit your build.prop and then reinstall Xposed in order to stop this from happening.

I did all that. I just can't turn HealthService back on.

EVOme said:
You need to remove Xposed, edit your build.prop and then reinstall Xposed in order to stop this from happening.
Click to expand...
Click to collapse
This is why I edited my comment. I did like you and not read it fully. He did all the pre-reqs, just turned it off rather than the original solution. I do know eventually they come back on, I believe. Give it 24 hours and check again.
Sent from my VW S5 using your mom.

How did you turn it off? Mine won't even let me disable it (unless I change the apk name to .bak).
Sent from my SM-G900V using Tapatalk

joshw0000 said:
How did you turn it off? Mine won't even let me disable it (unless I change the apk name to .bak).
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Force stop.
Sent from my VW S5 using your mom.

No dice.
Sent from my SM-G900V using Tapatalk
---------- Post added at 05:48 PM ---------- Previous post was at 05:48 PM ----------
Did you disable other apps (S Health)? Maybe it's dependent on them.
Sent from my SM-G900V using Tapatalk

No idea. But it's definitely in the "turned off" section of manage applications.

jideay said:
No idea. But it's definitely in the "turned off" section of manage applications.
Click to expand...
Click to collapse
Omg..go to the turned off section and click it to turn it back on..
Sent from my VW S5 using your mom.

Take a look at the image again. there is no way to turn it back on.

jideay said:
Take a look at the image again. there is no way to turn it back on.
Click to expand...
Click to collapse
There is if you go to system settings>applications>application manager> swipe all the way to the right to turned off. It will be there, select it and turn it back on.
And as I said if you just force stopped it it would probably turn back on in 24 hours. If after a couple days you can't do anything just save all your settings via Kies and Odin back to stock, re root and Kies back your settings
Sent from my VW S5 using your mom.

Take a look. First pic shows healthservice in the "Turned off" folder. Second pic shows there is no button to turn healthservice back on.

jideay said:
Take a look. First pic shows healthservice in the "Turned off" folder. Second pic shows there is no button to turn healthservice back on.
Click to expand...
Click to collapse
Just go to the Samsung App store and just look for HealthService or just reinstall S-health.. If you don't have the Samsung apps APK just download it from the site. Hopefully it works!

Try clearing app data on the service if you can

Could you fully delete the two apks (S Health and Health Services) from the system/priv-app folder, uninstall Xposed, restart the phone, then install shealth and health service with updated apks from the web (download, unzip, and install as normal apks).
I still can't post links to updated apks on the web as I'm a new poster, so either google for SHealth 3.2 or type mediafire, then ".com/" and then: download/w1bdd7665aiyogo/S-Health3_2.zip
Install, open, and let them update (if they will - probably won't be needed as both files are in the zip and both are current) and you should be good to go.
For what it's worth, I most recently installed Shealth AFTER having installed Xposed after also having started with a clean wipe (Oden) and having run the bloatware deletion .bat file from another thread (My order was wipe, root, SU, debloat, Xposed, then SHealth update manually as it wouldn't on its own).
I had removed the SHealth files from the .bat file, but I found I was stuck with an older version of SHealth that wouldn't update (I assume I also blew out some required Samsung updater with the bloatware bat). I used the above method to update my SHealth app to the latest version (I wanted the stress feature). In the end, I have Xposed running all sorts of things and current SHealth apps that work fine.

If you go into Titanium Backup, you should be able to turn it back on there. It's the same as "unfreezing" an app. In titanium, click on the app, and then click "defrost" .
If you also notice, any app that you turned off in the application manager, will show up as "frozen" in titanium backup.
Sent From The Darkside of My N3

OK thanks everyone for your help. I found the apk online, installed it, and then went through all the correct procedures. Xposed and S Health are now playing nice together.

jideay said:
OK thanks everyone for your help. I found the apk online, installed it, and then went through all the correct procedures. Xposed and S Health are now playing nice together.
Click to expand...
Click to collapse
Where did you find the apk? I can't seem to find it.
Sent from Big Blue Country

ukyfan said:
Where did you find the apk? I can't seem to find it.
Sent from Big Blue Country
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23329332407584514

[Fix]How to FIX XPOSED FRAMEWORK LAG on Note 4

Found and confirming a method on how to get the latest version of Xposed Framework working on Note 4 (T-Mobile SM-N910T). Also Wanam Xposed is working fine too inside Xposed Framework.
Step 1:
Insure that Xposed Framework is fully uninstalled from the device temporarily.
Step 2:
Go into Root Browser, or any browser of choice that has root privileges and go to /System/Build.Prop and open it as a text document.
Step 3:
Inside the Build.Prop file look for a line that says "ro.securestorage.support=true" [NOTE: IT IS THERE I PROMISE YOU, a bit hard to find]
Step 4:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change "ro.securestorage.support=true" to "ro.securestorage.support=false"
Step 5:
Go back into Xposed Framework, install and reboot and you MAY be fine. Most users will need to continue here. If you still have issues there are 2 methods to fully fix Xposed and S-Health
[Option 1: Download a fix module after Xposed re installed after the Build.Prop fix]
[Option 2: Disable S-Health completely]
Thanks to Compusmurf for mentioning about this module
Option1:
Step 1:
Go into Xposed Framework, download a module called "XSecureStorage"
Click Framework and hit Install/Update and you are good to go! If this module doesn't do the
trick, try Option 2. Option 2 is guaranteed to work since you will be disabling S-Health all together.
Option2:
Step 1:
In Settings App>>Application Manager find "SHealth" and select "Turn Off"
That will guarantee for Xposed to work fully fine with no lag. Leave a Thanks if this worked for you and post back if any questions or issues!

Or if u use shealth then don't disable that but install the fix module.

Thanks...I will add that in my post.

Or use the xposed module that wanam made that fixes thus issue plus private mode and shealth

What xspoded lag ?

I had to reflash through Odin to fix the lag and haven't tried xposed since. I'll give this a go

On the Note 4 when Xposed Framework is installed, on alot of peoples Note 4's including mine, in the phones performance it will have randum 3-4 second hiccups everyonce in awhile. It will just freeze anywhere for 3 seconds then resume. Some may not have that issue/notice it. I heard it happens on the GS5 also.

Yea odin doesnt really solve the problem, it just removes xposed framework obviously, but it works for me and my friends with Note 4's tried it and they are confirming it also.

Yes that is another worthing method, but if you dont want Wanam Xposed for some odd reason this works without dependencies on other modules excluding Option 1 in my post.

XxSilent.NightmarexX said:
Or use the xposed module that wanam made that fixes thus issue plus private mode and shealth
Click to expand...
Click to collapse
Which module is this?

Rinthe said:
Which module is this?
Click to expand...
Click to collapse
Xsecurestorage

Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.

XxSilent.NightmarexX said:
Xsecurestorage
Click to expand...
Click to collapse
chaunold said:
Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.
Click to expand...
Click to collapse
does this fix the lag?

Rinthe said:
does this fix the lag?
Click to expand...
Click to collapse
Yes sir

Rinthe said:
does this fix the lag?
Click to expand...
Click to collapse
fixed mines:good:

Has anyone else had issues with the Play store after installing xposed and Wanam? Actually just xposed caused the issue. When I installed it my play store downloads wouldnt finish. They would start and then hang in the middle and never finish. I had to uninstall all of it. Any ideas?

Gam3r 4 Life said:
Has anyone else had issues with the Play store after installing xposed and Wanam? Actually just xposed caused the issue. When I installed it my play store downloads wouldnt finish. They would start and then hang in the middle and never finish. I had to uninstall all of it. Any ideas?
Click to expand...
Click to collapse
Yeah the secure storage issue was the reason it lagged

demon28 said:
Yeah the secure storage issue was the reason it lagged
Click to expand...
Click to collapse
Thanks. I was able to get it to work again. But can anyone else confirm they were able to use the S5 add widgets to lock screen module to work on the Note 4? I read a couple other posts that said it worked. But I cant get it to. I added all the modules, enabled them. But still cant find anyway to get widgets to the lock screen. If anyone knows please let me (and others) know. Thanks

The fixes here in the OP did seem to eliminate the lag I was seeing after rooting and using Xposed. The Samsung keyboard still seems to lag some but I'm thinking that's just the keyboard, because the Google keyboard works great! Thanks OP!

Just disable secure storage in Wanam this fixes the lag as others mentioned
Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.

Is the Galaxy S7 Edge encrypted?

Hi, does anyone know if the phone is encrypted or is there an option to do so?

Marshmallow by default is encrypted, but I think with Samsung you have to do it in the Knox environment.

The sd ?

Yes there is an option for encryption. Also Knox adds an extra layer of security above it.

ekjl said:
Yes there is an option for encryption. Also Knox adds an extra layer of security above it.
Click to expand...
Click to collapse
Bump. I'd like to confirm if this device is already encrypted. From what I can see in Lock Screen and security, I can only encrypt my SD card (useful) and when I tap Protect encrypted data, it states it's already encrypted but offers to "require screen lock to decrypt data when device turns on".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It is encrypted, by default.

ingenious247 said:
It is encrypted, by default.
Click to expand...
Click to collapse
I have an S7 edge and was just trying to find how to do it. It just has the SD encryption options, so I thought it might be by default for the main storage. Good to have this confirmed. Thanks.

How to disable encryption......

gurpreet4u15 said:
How to disable encryption......
Click to expand...
Click to collapse
You can't.

spectrumfox said:
You can't.
Click to expand...
Click to collapse
You can if you do a clean wipe and flash dm-verity to disable it - which is required for a usable internal storage partition in TWRP and xposed

Inb4, necropost.
I and it would seem a lot of users are missing the option to set a password before the phone boots into Android. The ‘Protect Encrypted Data’ option in 'Lock screen and security' section doesn't show. Does any one know if this has been removed? Can anyone confirm that the S7 (edge) is still encrypted? Surely you can prevent the phone from booting into the OS until you've entered credentials? To prevent lock screen exploits.
Just curious for your input.

LoftysGame said:
Inb4, necropost.
I and it would seem a lot of users are missing the option to set a password before the phone boots into Android. The ‘Protect Encrypted Data’ option in 'Lock screen and security' section doesn't show. Does any one know if this has been removed? Can anyone confirm that the S7 (edge) is still encrypted? Surely you can prevent the phone from booting into the OS until you've entered credentials? To prevent lock screen exploits.
Click to expand...
Click to collapse
My AT&T S7e continues (under Android 7.0) to have the Settings->Lock Screen and Security->Secure Startup option "Require password when device turns on".

Gary02468 said:
My AT&T S7e continues (under Android 7.0) to have the Settings->Lock Screen and Security->Secure Startup option "Require password when device turns on".
Click to expand...
Click to collapse
Thanks for the reply.
Any one from the UK have this setting still?
I've been reading that there is a possibility that recent (end of Dec 2016) UK law change could have caused this to be removed from phones sold in the UK hence digging up this thread.
I'm still waiting for the 7.0 update OTA as I'm still on 6.0.1 but I may try and update myself to 7.0 to see if the option returns.

LoftysGame said:
Thanks for the reply.
Any one from the UK have this setting still?
I've been reading that there is a possibility that recent (end of Dec 2016) UK law change could have caused this to be removed from phones sold in the UK hence digging up this thread.
I'm still waiting for the 7.0 update OTA as I'm still on 6.0.1 but I may try and update myself to 7.0 to see if the option returns.
Click to expand...
Click to collapse
Hi there,
Had the same question today but I found the option is there and has been renamed to "Secure Startup" and is just above the "Decrypt SD card" option (Or Encrypt SD card if you haven't already enabled SD card encryption).
Samsung Galaxy S 7 SM-G930F
Android 7.0

Dialer codes not working any more, due to root?

Rooted my S7E, and just noticed that the common Samsung dialer codes (as *#0*# or even *#06#) do no longer work!
When I enter them into the dialer nothing happens! I used them successfully before!
Only change is that I installed TWRP, root and Viper!
Do dialer codes work on your phone after root?
Sent from my SM-G935F using XDA-Developers mobile app

Yes, it works for me.

That's very strange. Root shouldn't affect those codes as they are generic for all devices.

TML1504 said:
Rooted my S7E, and just noticed that the common Samsung dialer codes (as *#0*# or even *#06#) do no longer work!
When I enter them into the dialer nothing happens! I used them successfully before!
Only change is that I installed TWRP, root and Viper!
Do dialer codes work on your phone after root?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Depends on the rom I find. Echoerom working good for me.
Sent from my Pebble Time

Thx for the replies!
For me this is also strange, I can't remember that this was the case anytime before I rooted an android device!
Anyone else with this problem?
Sent from my SM-G935F using XDA-Developers mobile app

Did you perhaps install the Google Phone application? I installed it and can't use dialer codes with it. If I switch back to the stock Samsung Phone application it works again.

mcfly76 said:
Did you perhaps install the Google Phone application? I installed it and can't use dialer codes with it. If I switch back to the stock Samsung Phone application it works again.
Click to expand...
Click to collapse
phone is pure stock, only thing I did was rooting with TWRP and CF-root, and installing viper4android
0verdaflow said:
try another version and see if that fixes it
Click to expand...
Click to collapse
another version of what?
another rom? i think this would fix it, but it would be interessting for me WHAT caused this behaviour !

I had this problem once. Factory reset did the trick for me

Solution to failed dialler codes
Boot into recovery using vol up+home button + power button.Then wipe cache in the recovery and reboot.I hope that solves it.

S7 Edge G935V
Yes My husband replaced the stock Rom on my rooted S7 G935v and the codes didn't work afterwards

maybe the feature was turned off during the root process. use a file browser with root permissions and navigate to the lowest level and go to-- /efs/carrier --then long press hidden menu and open it with a text editor. Using capital letters just change the OFF to ON then save it, reboot and try your codes again. :highfive:

kanesglove said:
maybe the feature was turned off during the root process. use a file browser with root permissions and navigate to the lowest level and go to-- /efs/carrier --then long press hidden menu and open it with a text editor. Using capital letters just change the OFF to ON then save it, reboot and try your codes again. :highfive:
Click to expand...
Click to collapse
I can't find the folder /carrier

Same thing here

try using the search feature in file browser. make sure it has root access with permissions granted.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kanesglove said:
View attachment 5396149
Click to expand...
Click to collapse
Check this no folder named carrier at all

Umar Sabo said:
Check this no folder named carrier at all
Click to expand...
Click to collapse
I see that. Do you use the stock rom? See if you have the actual apk file in your system apps
if you don't have the apk file I think I can send mine. I'm pretty sure if you manually inset the apk in the system folder and change the permissions to match what the other apps in the folder have it should work. I mean you may have to create a couple other files though like the carrier folder and the document in it.