Related
I've just encrypted my Nexus 5 under Android 5.0 and I was hoping I could set a decryption PIN just for the startup boot process, and not every time I unlock my phone. I haven't managed to find a way to do this, though: it's possible to enable a startup PIN if you enable the lock screen PIN, but I don't see a way to simply enable a startup PIN.
My goal is simple: to secure my phone when it's powered off, while making it comfortable to use when it's powered on. Can this be done?
Thank you!
Not by standard. Not sure what affects using apps that turn the secure lock on and off will have. You can test them.
rootSU said:
Not by standard. Not sure what affects using apps that turn the secure lock on and off will have. You can test them.
Click to expand...
Click to collapse
OK, I will, thank you for your response.
jpabloae said:
My goal is simple: to secure my phone when it's powered off
Click to expand...
Click to collapse
When its off its already secure since no electrons flow through it...
jpabloae said:
I've just encrypted my Nexus 5 under Android 5.0 and I was hoping I could set a decryption PIN just for the startup boot process, and not every time I unlock my phone. I haven't managed to find a way to do this, though: it's possible to enable a startup PIN if you enable the lock screen PIN, but I don't see a way to simply enable a startup PIN.
My goal is simple: to secure my phone when it's powered off, while making it comfortable to use when it's powered on. Can this be done?
Thank you!
Click to expand...
Click to collapse
i'd say you want your phone to boot if you loose it (so you can track it), don't you think?
kenshin33 said:
i'd say you want your phone to boot if you loose it (so you can track it), don't you think?
Click to expand...
Click to collapse
That's reasonable in most cases. But there are situations and circumstances in which the data privacy has a higher priority than the ability to track the phone. Anyway the question can be considered independently from its motivations: can I separate the encryption key from the lock screen key? According to issue 29468 and this discussion, it seems it's still not possible.
jpabloae said:
That's reasonable in most cases. But there are situations and circumstances in which the data privacy has a higher priority than the ability to track the phone. Anyway the question can be considered independently from its motivations: can I separate the encryption key from the lock screen key? According to issue 29468 and this discussion, it seems it's still not possible.
Click to expand...
Click to collapse
according to this:
http://source.android.com/devices/tech/encryption/
out of the box, no because the lock screen password/PIN/ is used to encrypt the actual encryption key (randomly generated)
thank you very much b/c indirectly you answered the question I had (the reason I was browsing this thread), namely the boot password thinggy (as I said I'd like the phone to boot, baring an exploit, it's well protected: bootloader relocked, long password, impossible to flash anything without wiping - I sign my builds cm-12 with my own keys, and I crippled the recovery to allow only signed zips-, and no adb -even in recovery- connection outside my own computer, I installed cerberus in the system partition without a backup script, the only way to get rid of it is to explicitly format the system partition, and above all I don't trust the phone ).
that said, it should be possible may be to fiddle with vold's sources to make it so (separate passwords, it shouldn't be too hard ) the only problem in the absence of an "official" solution (be it in AOSP or the flavor du jour Android) the user is backed into a corner : build his own ROM from sources.
I bought this device knowing there would be potential notification issues, but I had seen mixed reports that the L29 model may not suffer from them. It took about a day, but they finally started showing up. My main issue is email. I have tried stock Gmail, Bluemail and Typemail (same app, basically). After the screen has been off for about 5 minutes, I stop getting notifications for email.
I have seen people blame this on doze, but my Nexus 6p isn't nearly this bad, at least not until it has been sitting for hours. I have tried everything to resolve this including:
Whitelist in battery manager
Whitelist in Doze settings
Notifications set to priority
Rooting and making Bluemail a system app (which I can't quite get to work for some reason)
Editing the doze settings with the doze setting editor app found on here
Running in Performance mode
Updating to B162
Disabling Phone Manager with Titanium Backup
Even all of these things in combination are not working. Nothing works. Since other Huawei devices have this issue, it doesn't seem like Huawei is planning to fix it. I know people want to blame Doze, but neither my Moto X Pure or Nexus 6P are this bad, both of which are running Marshmallow. Something else is going on with the ROM. Short of getting an actual Cyanogenmod port, I don't know that we'll ever see this resolved.
It's frustrating, too, because I like everything else about this phone, but this is a pretty big deal. A Smartphone that doesn't get notifications reliably is pretty useless.
I have the exact same issue as you, and have tried everything that you have tried as well.
Can't get it to work. It's like saying goodbye to a girl you really really love...
Please fix this somehow... anyone...?
Oh look, another thread about notification issues. This one should help. Has any of you made sure that mobile data stays on after screen goes off?
nighthawk626 said:
Oh look, another thread about notification issues. This one should help. Has any of you made sure that mobile data stays on after screen goes off?
Click to expand...
Click to collapse
All settings are on, mobiledata during screen off, wifi always enabled etc.
It is not about receiving notification, it's about receiving them instant the same second as they are received.
We don't want to receive delayed 5-10mins notifications.
This happen both on mobiledata and on wifi as well.
Oh I can assure you that is a feature belonging to Android 6 called doze function. The phones who are updated to MM mostly received a not fully functioning version of Android 6.0. So you can not compare them.
deaad said:
Oh I can assure you that is a feature belonging to Android 6 called doze function. The phones who are updated to MM mostly received a not fully functioning version of Android 6.0. So you can not compare them.
Click to expand...
Click to collapse
What? So you're saying that the Nexus 6p has a "not fully functioning version of Android 6.0"? Go home, you're drunk. That phone does not have this issue, not to this extent.
It's not doze. I have manually edited the doze settings and the issue persists.
try disabling gmail, install outlook and protect it in the battery settings. then go into notifications and make sure it pops up how you want it to.
When i changed my locckscreen I started getting notifications regularly. Try a third party lockscreen app.
deaad said:
Oh I can assure you that is a feature belonging to Android 6 called doze function. The phones who are updated to MM mostly received a not fully functioning version of Android 6.0. So you can not compare them.
Click to expand...
Click to collapse
TheNamelessMan said:
try disabling gmail, install outlook and protect it in the battery settings. then go into notifications and make sure it pops up how you want it to.
Click to expand...
Click to collapse
I wasn't even using gmail at first. I was using Bluemail (which is actually better than Outlook on Android) and I had the same issue. If it were that easy, I'd already be using a different email app.
sumer1 said:
When i changed my locckscreen I started getting notifications regularly. Try a third party lockscreen app.
Click to expand...
Click to collapse
How did you do that and what did you try? Please tell exactly.
greyhulk said:
What? So you're saying that the Nexus 6p has a "not fully functioning version of Android 6.0"? Go home, you're drunk. That phone does not have this issue, not to this extent.
It's not doze. I have manually edited the doze settings and the issue persists.
Click to expand...
Click to collapse
I'm not drunk, I know this for sure. My LG G4 is also updated to 6.0 and now I also own a Huawei mate 8 and therefore I can tell the difference, it's huge. And about your nexus 6p I'm not sure, in any case I was talking about the updated phones.
deaad said:
I'm not drunk, I know this for sure. My LG G4 is also updated to 6.0 and now I also own a Huawei mate 8 and therefore I can tell the difference, it's huge. And about your nexus 6p I'm not sure, in any case I was talking about the updated phones.
Click to expand...
Click to collapse
My Moto X Pure is updated to 6.0 and has absolutely no delay with notifications, nor does my 6P, so there's a flaw in your logic.
This goes far beyond doze. This is something specific to the Huawei ROM and since previous Huawei phones (Mate 7, P8) had this exact issue on older versions of Android, it's pretty obvious that the problem lies with them and not doze.
Before I bricked my device I tested the hell out of this and found the issue.
Doze implementation is broken in the Mate 8.
The phone is supposed to wake up and check for notifications and it doesn't.
Turning off doze fixes all the issues on the Mate 8, at the cost of whatever benefit Doze would have offered.
duraaraa said:
Before I bricked my device I tested the hell out of this and found the issue.
Doze implementation is broken in the Mate 8.
The phone is supposed to wake up and check for notifications and it doesn't.
Turning off doze fixes all the issues on the Mate 8, at the cost of whatever benefit Doze would have offered.
Click to expand...
Click to collapse
It's certainly possible that it's broken for this device specifically. Fine, I'll bite. How do you disable doze with tasker? I thought I saw a tutorial on here before, but haven't been able to find it.
greyhulk said:
It's certainly possible that it's broken for this device specifically. Fine, I'll bite. How do you disable doze with tasker? I thought I saw a tutorial on here before, but haven't been able to find it.
Click to expand...
Click to collapse
Run this command as root with Tasker.
dumpsys deviceidle disable
Or, even without root, use adb and run
adb shell dumpsys deviceidle disable
duraaraa said:
Run this command as root with Tasker.
dumpsys deviceidle disable
Or, even without root, use adb and run
adb shell dumpsys deviceidle disable
Click to expand...
Click to collapse
Thanks. I'll give it a try. Losing doze would suck, but this device is unusable for me without timely notifications.
Sent from my XT1575 using Tapatalk
greyhulk said:
Thanks. I'll give it a try. Losing doze would suck, but this device is unusable for me without timely notifications.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
It worked for me to get notifications, but yes, I really wish Huawei would have fixed it.
Maybe in an upcoming version it will be fixed.
I am interesting to see if S7 will also have this problem.
Can you tell us non rooted people how to do this? I have dev options available but don't know how to do the rest.
TheNamelessMan said:
Can you tell us non rooted people how to do this? I have dev options available but don't know how to do the rest.
Click to expand...
Click to collapse
If you are not rooted, you will need to plug into your computer and run the ADB command mentioned before EVERY TIME YOU BOOT UP THE DEVICE (sadly)
The command is:
adb shell dumpsys deviceidle disable
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages unique to Pixel devices when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Artim_96 said:
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Click to expand...
Click to collapse
Nothing as far as i know.
Unstroofy said:
Nothing as far as i know.
Click to expand...
Click to collapse
That sounds great. Wasn't sure if they might have done something through the Titan M or else
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
sic0048 said:
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
Click to expand...
Click to collapse
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Artim_96 said:
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Click to expand...
Click to collapse
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything and gives that person access to anything they want. That super secure lockscreen password or fingerprint won't help keep them out and does nothing but give users a false sense of security.
When the FBI paid a 1 million dollar bounty to someone to access an iPhone, they were paying someone to get around the bootloader. If you unlock your bootloader, you give this access right from the beginning - for free, and without any effort required.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I was simply trying to give a thorough answer. It's up to the individual user to decide if the the positives of unlocking the bootloader and rooting outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
sic0048 said:
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything they want. That super secure lockscreen password or fingerprint won't help keep them out.
Again, I'm not familiar with this lockscreen passport you mention, so perhaps there is a way to secure the phone that I am not aware of.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I am simply trying to give an thorough answer. It's up to the individual user to decide if the the positives or rooting and unlocking the bootloader outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
Click to expand...
Click to collapse
Was a typo,I meant lockscreen password. Android should ask you, if you set up a lock method other than Swipe to unlock, if you want to be asked for it on bootup.
So no matter what you are able to flash through an unlocked bootloader, /data and with it anything that could be relevant stays encrypted until you enter the lockscreen pin/pattern/password, no matter if you do this on the screen that will interrupt bootup after a few seconds or in TWRP. So it doesn't matter what you could come up flashing, as long as you don't find a way to extract the encryption key from the secure storage either in Titan M or any ARM processor, there is no way to get your hands on user data. The only thing you can do is simply wipe /data. Then you can start up new, but the users data will be gone.
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Artim_96 said:
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Click to expand...
Click to collapse
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
sic0048 said:
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
Click to expand...
Click to collapse
Fixed that. Hope the text is more clear now.
But could you reproduce what I explained? Because I would be very surprised if that was unique to Motorola and not AOSP
I have a stupid problem where it says battery temperature is too cold. I cannot prove ownerships so no warranty but there is no damage.
still very new. I heard some ROMS/Kernals can disable this sensor detection on Androids devices. Is there one available for this Note 10+?
Install adb on a pc.
Disable Samsung Battery Guardian.
I kinda like that app. You could maybe just disable its notifications.
But if you really want to disable it hear you go, I ain't here to judge, lol
Install adb on a Windows PC (search for it) plug your phone into the pc
Type in:
"adb shell pm disable-user --user 0 com.samsung.android.statsd"
Push Enter
If you decide you want it back do the same thing except change "disable" to "enable"
Gregbmil1 said:
Install adb on a pc.
Disable Samsung Battery Guardian.
I kinda like that app. You could maybe just disable its notifications.
But if you really want to disable it hear you go, I ain't here to judge, lol
Install adb on a Windows PC (search for it) plug your phone into the pc
Type in:
"adb shell pm disable --user 0 com.samsung.android.statsd"
Push Enter
If you decide you want it back do the same thing except change "disable" to "enable"
Click to expand...
Click to collapse
Hey, i tried to do the same on Samsung Galaxy A52 5g, but i didn't work. Do you know whats the reason for this or what i can do to disable the battery guard on my phone? Thanks in advance.
Kuehlrealg said:
Hey, i tried to do the same on Samsung Galaxy A52 5g, but i didn't work. Do you know whats the reason for this or what i can do to disable the battery guard on my phone? Thanks in advance.
Click to expand...
Click to collapse
Lol, this whole time it's been wrong? I wrote "disable" instead of "disable-user". Try it now
"adb shell pm disable-user --user 0 com.samsung.android.statsd"
Push Enter
Gregbmil1 said:
Lol, this whole time it's been wrong? I wrote "disable" instead of "disable-user". Try it now
"adb shell pm disable-user --user 0 com.samsung.android.statsd"
Push Enter
Click to expand...
Click to collapse
Thanks for your fast reply. I tried it, but got the following response "java.lang.IllegalArgumentException: Unknown package: com.samsung.android.statsd". Maybe it's named differently on my phone?
Kuehlrealg said:
Thanks for your fast reply. I tried it, but got the following response "java.lang.IllegalArgumentException: Unknown package: com.samsung.android.statsd". Maybe it's named differently on my phone?
Click to expand...
Click to collapse
Yeah, thats what I'm thinking. It might not be installed or its something different. What phone is it again?
Gregbmil1 said:
Yeah, thats what I'm thinking. It might not be installed or its something different. What phone is it again?
Click to expand...
Click to collapse
Samsung Galaxy A52 5G it is
I'm rooted with Android 10 on my pixel4a. I don't want to upgrade to 11 just yet, but I keep getting the annoying update notices. Is there an app or module I can freeze with titanium to turn off the notices?
Wrong forum, dude!
An app from Google Play called "Notification off" did the trick for me on my Sony xz2c.
old.splatterhand said:
Wrong forum, dude!
An app from Google Play called "Notification off" did the trick for me on my Sony xz2c.
Click to expand...
Click to collapse
It was moved to this forum by a forum moderator, dude! But thanks for your very helpful reply to the original question, dude!
nogods said:
It was moved to this forum by a forum moderator, dude!
Click to expand...
Click to collapse
Because i reported it
I posted a similar question in the correct forum with no replies. The Notification Off app in the Play Store hasn't been updated since 2015.
And anyway, not a normal notification...the full screen one that appears overnight every night. There should be a process that can be blocked or turned off on a rooted phone(?), but I can't find it.
Same question. I don't need a daily reminder that my OS is is out of date.
Testing the below on a Marlin with Android 9 & TRWP backup before I actually try on Sunfish with Android 10.
1. Usb debugging on
2. Computer with adb drivers
Open command window in pc and connect your device and run these commands one by one.
Commands are
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.android.backupconfirm
exit
Done. No more update notification.
crackerjack1957 said:
com.android.backupconfirm
Done. No more update notification.
Click to expand...
Click to collapse
Thanks for the tip on the process to look for. I froze it using Titanium Backup and I'll see if that solves it.
EDIT: Freezing that app process does nothing. I froze it and then got another full screen notification a few hours later.
After some trial and error, I think the correct process is Dynamic System Update. I froze that process but I'm still receiving notifications.
I then found that even though the process is disabled in TiBackup, it still has notifications turned on.
Go to Settings/Apps & Notifications
Select see all apps
Top right 3-dots/select show system
Scroll down to Dynamic System Update.
The notification can't be turned off.
I cleared storage and cache for it and restricted battery use.
digger16309 said:
After some trial and error, I think the correct process is Dynamic System Update. I froze that process but I'm still receiving notifications.
I then found that even though the process is disabled in TiBackup, it still has notifications turned on.
Go to Settings/Apps & Notifucations
Select see all apps
Top right 3-dots/select show system
Scroll down to Dynamic System Update.
The notification can't be turned off.
I cleared storage and cache for it and restricted battery use.
Click to expand...
Click to collapse
Could be a Titanium issue..........................no ill effects on the Pixel XL so I removed file with ADB command of pm uninstall -k --user 0 com.android.backupconfirm on the Pixel 4A..............no update notices overnight..............will report back in a few days to confirm.
Edit: 24 hours I get notice for update............
logcat-entry for that popup seems to be
Code:
START u0 {act=android.settings.SYSTEM_UPDATE_COMPLETE flg=0x10048000 pkg=com.google.android.gms cmp=com.google.android.gms/.update.phone.PopupDialog (has extras)} from uid 10147
on my pixel 4a. sounds a lot like the process described on that other post here, so ..
i’ve gone ahead and disabled that process. fingers crossed.
crackerjack1957 said:
Testing the below on a Marlin with Android 9 & TRWP backup before I actually try on Sunfish with Android 10.
1. Usb debugging on
2. Computer with adb drivers
Open command window in pc and connect your device and run these commands one by one.
Commands are
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.android.backupconfirm
exit
Done. No more update notification.
Click to expand...
Click to collapse
Thanks for posting this information.
But if it causes some other problems can that be reversed, and if so how?
I originally had hoped for a Tinatiaum freeze solution so that I could easily reverese it if there any problems, but it doesn't seem that anyone has yet found a program that can be frozen that will eliminate the popups.
I'm beginning to suspect that a lot of Apple OS programers have infiltrated Android and are turing Android into Apple little by little, until one day we'll wake up and find that every one has to ask Steve Job's estate for permission to use their phone.
nogods said:
Thanks for posting this information.
But if it causes some other problems can that be reversed, and if so how?
I originally had hoped for a Tinatiaum freeze solution so that I could easily reverese it if there any problems, but it doesn't seem that anyone has yet found a program that can be frozen that will eliminate the popups.
I'm beginning to suspect that a lot of Apple OS programers have infiltrated Android and are turing Android into Apple little by little, until one day we'll wake up and find that every one has to ask Steve Job's estate for permission to use their phone.
Click to expand...
Click to collapse
"pm uninstall -kb -user 0 ..." is not permanent (simply 'disables' the executable) and can be easily reversed. A bit of googling will surface procedures.
Enforcing updates and associated reminders is good security hygiene. No evil intent IMHO.
nogods said:
Thanks for posting this information.
But if it causes some other problems can that be reversed, and if so how?
I originally had hoped for a Tinatiaum freeze solution so that I could easily reverese it if there any problems, but it doesn't seem that anyone has yet found a program that can be frozen that will eliminate the popups.
I'm beginning to suspect that a lot of Apple OS programers have infiltrated Android and are turing Android into Apple little by little, until one day we'll wake up and find that every one has to ask Steve Job's estate for permission to use their phone.
Click to expand...
Click to collapse
Definitely not as easy in Android rooting like it once was............actually frank93 in post #11 found the working solution.
DB126 said:
Enforcing updates and associated reminders is good security hygiene. No evil intent IMHO.
Click to expand...
Click to collapse
I'm fine with security updates, but unfortunately, the updates always seem to break something that once worked, so I want to wait until the items that weren't supposed to be broken by new security are fixed, And the "evil" part comes from programmers making aesthetic changes for no reason other than someone thinks "this would be nicer if..."
crackerjack1957 said:
Definitely not as easy in Android rooting like it once was............actually frank93 in post #11 found the working solution.
Click to expand...
Click to collapse
There isn't any "com.google.android.gms" or anything similar in my Titanium list. A search in Titanium for "com.google.android.gms" returns two items: "Google Location History 1.0" and "Google Play...33172415" - is that second one the item I need to freeze? After freezing it I get popups saying "iHeart Radio won't work" and "google maps won't work" and "Pixel launcher won't work", etc, sure enough, they don't work after freezing "Google Play...33172415"
nogods said:
There isn't any "com.google.android.gms" or anything similar in my Titanium list. A search in Titanium for "com.google.android.gms" returns two items: "Google Location History 1.0" and "Google Play...33172415" - is that second one the item I need to freeze? After freezing it I get popups saying "iHeart Radio won't work" and "google maps won't work" and "Pixel launcher won't work", etc, sure enough, they don't work after freezing "Google Play...33172415"
Click to expand...
Click to collapse
Can't help you there in Titanium but the below works with no ill effects.
Adb devices (for checking device is connected)
Adb shell
su
pm disable com.google.android.gms/.update.phone.PopupDialog
exit
Besides Audio mods and other apps that don"t work with Android11........... another reason to stay on Android10 for now.
https://amp.hothardware.com/news/android-11-performance-degradation
Despite the block of the update module in TiBa, I got bitten by it anyway. It downloaded and installed (wrong setting in developer options) on a reboot. I never saw anything. It just happened and now I'm stuck on 11.
digger16309 said:
Despite the block of the update module in TiBa, I got bitten by it anyway. It downloaded and installed (wrong setting in developer options) on a reboot. I never saw anything. It just happened and now I'm stuck on 11.
Click to expand...
Click to collapse
I too wish to block auto-updates...and I have a few questions for you...
1) This thread seem to indicate that you need to disable the package " pm disable com.google.android.gms/.update.phone.PopupDialog " using ADB and that this package is not visible in TiBa, so did you use ADB, and if not, what did you freeze in TiBa?
2) You also said "(wrong setting in developer options)" - what did you mean by this? I'm asking because I turned that option off in developer settings and I was hoping that would stop the auto-updates.