My phone is on the latest btu software but now has a permanent notification telling up to update to nougat beta. I don't want to. How can I remove it
I've deregistered from the beta program but it's still there. I tried nougat bit right now I still prefer nougat so went back. Can nobody help. Surely I'm not the only one
Nougat is great your missing out
I already used the beta for 2 days. So no I'm Not missing out. Don't be so ignorant and patronising.
I tried it, I liked it, I gave my feedback and right now the beta for nougat is not as good as the full released marshmallow version so I went back until they've improved it.
I'll take that as a no lol
Install a package disabler from Play Store and disable the update apks
Sent from my SM-G935F using XDA-Developers mobile app
Related
Hi guys, I downgraded my note 4 to kit kat yesterday, because on this version of os note 4 used to work almost perfect. The main problem is that an update to lolipop has been downloaded automaticly and the notification which ask me to update cellphone appeared on the notification bar. Is IT possible to hide this notification? I do not have a root. Do i have a possibility to delete os update files from memory?
I am in exactly the same situation. I am happy with 4.4.4 and i will wait for 5.1 update. How do i get rid of the notificarion? It managed to trick me and download the update.
Sent from my SM-N910F using XDA Free mobile app
If you go into Settings -> About Device -> Software Updates there are check boxes there that you can uncheck to disable the firmware update notification. However I don't understand why you would want to do that as you will make your Note 4 more susceptible to hackers.
Well, a lot of people have experienced that Lollipop is a lot worse than KitKat. Therefore, some (like me) want to keep using KitKat until Samsung comes with a better upgrade. Frankly, I find the OTA functionality annoying in the EXTREME. So if anyone can help shutting it up (until we want to upgrade) without root, it would be much appreciated!!!
Well, if that's what you want just follow the instructions that I posed earlier that will disable the Auto OTA update and Firmware Update Notification.
The box is unchecked but my phone already downloaded the update and it keeps nagging me about installing it. Even if i said i'll install later, every few hours it pops on my screen or find it there when i unlock it.
Sent from my SM-N910F using XDA Free mobile app
In that case you will need to find where the update file is and delete it from you Note 4's internal memory.
^Which is not possible without root.
Can any of you tell me where exactly i can find those update files ? I have already done a root, but i dont see them i system files.
ALERT: Patch for critical security vulnerability ('Stagefright')
- Device stability improvements, bug fixes.
- New and/ or enhanced features.
- Further improvements to performance.
To get the best from your device, please keep your phone up to date and regularly check for software updates
* After updating. you will not be able to downgrade to the old software because of updates to the security policy.
Just updated the wife's Note 4 and it is NOT N910T3UVU1DOFC (5.1.1) like the Internet says. < http://www.ibtimes.com/android-511-...ng-galaxy-note-4-t-mobile-how-install-2039649 > Just a patch for N910TUVU1COG2 (5.0.1).
Just fyi
Downloading now. Wonder what the new/enhanced features are?
thegreatone3 said:
Downloading now. Wonder what the new/enhanced features are?
Click to expand...
Click to collapse
Probably Stagefright fix
Yep, just the patch. Also you can go back to an older version of Android. I thought this patch messed up my SD card and Odin'd back without a problem. Turns out my SD card was just bad.
Sent from my SM-N910T using XDA Free mobile app
Updated to new patch, battery life gotten really bad since update this morning.
Sent from my iPad using Tapatalk
Can I upgrade this security patch running a non touchwiz ROM on my note 4?
I posted this test after I updated to this build, I hope another update is on the way soon if this is what we're getting after their latest update.
Haven't gotten anything yet.. I will let it OTA itself
note4 guy said:
Updated to new patch, battery life gotten really bad since update this morning.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
You will usually get less than normal battery life after an update. This is normal for Android.
What is the best course of updating if I'm rooted and on a custom TW rom?
Unconfirmed, not exactly why or how but my gf's N4 has been suffering from poor signal and loss. This update has seemingly corrected those issues. I haven't done it on mine but I'm optimistic because I've been having similar issues. They just say "bug fixes" so not sure exactly what that is. Obviously the Stagefright is one of those but there may also be tweaks and corrections here and there. I'd be curious to know if anyone else has been having those issues and whether or not this update fixes them.
Also confirming its not 5.1.1
I used a different app to test and it said I was not vulnerable.
Sent from my SM-N910T using XDA Free mobile app
dkb218 said:
You will usually get less than normal battery life after an update. This is normal for Android.
Click to expand...
Click to collapse
You can also boot up into recovery and wipe cash partition which will sometimes help, this is what I did when updating from 4.4 to 5.0 it helped.
I did try a few other apps to test stagefright and one said no and two said it was vulnerable, the best process to update which has never failed me is Odin to full stock, root it flash recovery and flash what you want from there, I've tried every way there is to sneak an update but that's the sure fire way to make sure everything is in order and gives the best outcome.
I have a converted to dev retail Note 4. Still running the stock rom and on oscar_kernel_v0.2. This evening I got notice of a security update from verizon. My feeling is not to take the update, but that's because I'm not sure. Is it safe to take the update or not?
Sent from my N910V converted to dev.
I would stay away. Verizon is evil and you will regret taking that update. If you have custom kernel then you must have custom recovery. With both those things being custom the update won't work anyway. Will probably get you in bootloop.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Google issues a monthly security update for Android. For Nexus devices, it's OK to take these updates.
For devices like ours that took a year and a half to root, I'd stay away no matter how much it nags.
Many custom ROMs disable such warnings.
Use Titanium to freeze sdm.apk and you will not get the OTA notification any longer
Sorry for my ignorance but I can't find information any where am currently on Android beta N when they official os is dropped does that mean I will get it and unroll from beta or do I need to unroll and when am rolled back then manually flash the update.
Sent from my Nexus 6P using XDA-Developers mobile app
Got ota & update installed fine & now longer on beta.
Tons of informations to your question here http://forum.xda-developers.com/nexus-6p/general/android-7-0-nougat-official-thread-t3445373
Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.
isaac970 said:
Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.
Click to expand...
Click to collapse
Nothing sure what kind of answer you're looking for that you wouldn't already know.
We only have root due to an engineering kernel.
Android 7 requires a different kernel. So we can't use it.
So unless we get a leaked engineering kernel for Android 7 then we will have to see if we can unlock the bootloader or discover some other kind of exploit. But I'm sure you already knew all of that.
The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.
AceDaMack said:
The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.
Click to expand...
Click to collapse
I just got CM14 (Nougat) on my Note 4, it made it into a whole new device way better than the laggy S7Edge. Here's hope that Nougat has some exploit and we can root it. CM14 is so smooth.
Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app
gaww said:
Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.
black96ss said:
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.
Click to expand...
Click to collapse
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app
gaww said:
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)
black96ss said:
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)
Click to expand...
Click to collapse
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app
gaww said:
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?
black96ss said:
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?
Click to expand...
Click to collapse
Would not loose WiFi calling - it is working in Chen's 935f ROM. I think we loose band 12 and possibly another, bit not sure.
The best way would be to ask him - but am going to search his threads before I ask.