Hello!
I just got an email from my very large company's IT department saying that I will no longer be able to use my google workplace apps because I my S9 has Android 10 and they no longer compare security patches.
The problem is that I've been waiting until the S23 comes out in January or February. I'm not experienced with flashing rooms etc., but can follow most instructions. Is there a way to put Android 11 (or later) on my phone without losing all my data/settings/apps or somehow fake that I have the update until the new phone comes out? Many thanks in advance.
Related
I turned on my tablet the other night and on the screen was a system dialog box that said a new security profile (or something like that) was applied. It gave a number of the build but I can't remember what it was. I thought by clicking OK I would get some more info, but that was it. I checked for updates and there was nothing. I got no other information.
Anyone else see anything like this? I guess it's possible it was linked to some app I have installed. But the popup window definitely looked like a system framework box.
Edit: I guess I did find on the Security tab in the settings that it is set to Automatically install new security policies. So that would make sense, just wondering what might be included in this update?
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
dpersuhn said:
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
Click to expand...
Click to collapse
This message?
What's the harm? It's updating something already in place that you can't evaluate so why be up in arms about an update that you can't see to evaluate either? Samsung updates a bunch of stuff passively so it's kind of a trust exercise. Since passively doing bad things to people's s/w and h/w without their consent is a sure way for a publically held company to make the front pages of the news (in a financially damaging way) I'm trusting them until given a reason I shouldn't. Do you know what Google's changed security policy enforcement wise when they roll out updates to Android?
BT keyboard usage isn't broken. You need to disable the on-screen keyboard the first time you pair it. From then on the on-screen keyboard's automatically disabled when the BT keyboard is connected.
KNOX is benign when not in use with the exception of the warranty flag that detects the use of unknown ROMs being loaded on the device. I use KNOX on my N3 and N10.1-14 and like it. I also haven't had a single issue related to it.
And it's here to stay.
http://www.infoworld.com/d/mobile-t...-move-blackberry-users-android-and-ios-230343
Go do a little homework on android 4.3 and bluetooth keyboard issues, then I'll be glad to talk about constant disconnects, key repeats, etc. The note 2014 is even worse than other 4.3 tabs in the bluetooth dept. I have gone through 4 BT keyboards so far and each has disconnect and/or key repeat issues in a major way. This is in no way related to disabling the soft keyboard.
Like I said, it starts with google and some will lay the blame there and hold samsung harmless. I guess I have a higher expectation of quality control and since I bought a samsung product and have no direct relationship with google. Samsung selected this version of android for installation, so I think it is very reasonable to hold them accountable for the functional state of the resulting device.
As for Knox, I'd love it for managing enterprise devices as an MDM platform, but there is a reason MDM software has to be INSTALLED on other platforms. It's intrusive by its very nature. I'm not using this device in a corporate environment, it's my personal tablet. As such, knowing that Samsung has the reigns on a corporate MDM tool that wasn't advertised, I had no say in adding or removing, and also provides no visibility into what they consider an appropriate security policy, isn't exactly inspiring trust. You can trust them all you want, I don't see them as being any better than Apple at this point.
My ultimate point is simple. Samsung is wasting resources reinventing the MDM wheel and forcing it on everyone (whether they want it or not) while there are numerous functional issues with this tablet that aren't being addressed. I see that as a questionable ranking of priorities. If they're worried about device security, how about starting by keeping up with updates to The base android install.
---------- Post added at 02:53 PM ---------- Previous post was at 02:46 PM ----------
Also worth mentioning is the complete lack of release notes that go along with the system updates. Think about that for a minute. How do I, as a user, ever know from one update to the next what issues have been addressed, what functional changes have been made, or what areas might have been modified so I can make an educated decision regarding if/when to update?
Samsung has proven that they can and will remove things from one version to the next as they see fit. Why can't they actually tell people what to expect by putting out proper release notes like any respectable software developer would be expected to do? Samsung lacks the skill or capability to do what developers of $2 apps in the play store are capable of? Surely you jest...
So, I've decided that right now there isn't any hardware out there that is enough of an improvement over the Note3 to get me to upgrade (will wait for SD820-based phones).
Unfortunately since T-Mobile has neglected this phone we are running a year-old version of Android, and thus are vulnerable to all of the fun widely-reported security holes uncovered since then.
From what I've been reading all AOSP-based ROMs seem to be dealing with NFC/sensor fusion issues (CM has open bugs for both issues).
My question right now is: is there anything available for the Note 3 that would allow it to have the latest security fixes without having to deal with other major issues like the ones I mentioned above?
I don't really even care about having 5.1, I just want my phone to be more secure.
I'm with you about new phones and actually dislike Note 5 (no SD, non removable battery etc. WTF Samsung, if I wanted iphone I would get one). As far as I know the stagefright is the only major issue on the system level, otherwise chrome bug for example should be fixed with chrome update and other stuff should be easy to avoid as long as normal precautions are followed (installing apps from Play store only for example). But I think even stagefright bug was little overblown. My understanding is Android has ASLR (random address space allocation) so buffer overflow bug is difficult to take advantage off, since the hackers don't know where in memory needed functions are located, so even with the bug, Note 3 should be relatively safe. I updated my wife's GS5 to latest Lollipop: she hates it, I don't like it much either , so not having latest operating software is not a problem for me. Bottom line I don't worry about it too much, I just scan my phone with antivirus and all it can find is that my phone is rooted, like I didn't know that already. I'm running stock, since I can't find custom ROM that has all functions enabled, like WIFI calling, NFC etc. There was some talk of monthly security updates for Android, like Windows have, but with Google, phone makers and carriers all involved, I doubt it will happen soon.
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
andy o said:
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
Click to expand...
Click to collapse
I have 7.1.1 on my 5X. Can't get the initial setup/transfer to work whether I try to use the cable or cloud. "Google Play Services has stopped working" comes up just after I hit "copy" on the old phone, or when I select the 5X backup in the WiFi version, and basically brings me back to the beginning of the process. Not sure why it's happening, spent hours on the phone with Google support last night and didn't get anywhere, other than them offering me a replacement phone. That said, the support person couldn't even send me an RMA link that didn't give a "Internal Server Error" no matter what device or network I used... Anyway I doubt my particular issue is a 7.1.1 issue?
A few days ago Xfinity Mobile (or Samsung? I'm unsure) started pushing OTA update G965USQU7DTA5 (One UI 2 upgrade with Android 10).
I successfully updated mine SGS-9 but got stuck on wife's SGS-9 Probably, first attempt of download on this phone was interrupted (my wife went to store, and download was paused 'cause of no WiFi). But after that it's always stopped on 25% and saying "Couldn't download update: Unable to update the software. A network or server error occurred. Try later again". It's a bug in buggy Samsung software updater, I'm 100% positive, but how to fix that stuff without resetting the phone?
Phone is NOT rooted or unlocked; I googled for "offline update" instructions for stock, locked phones but can't find good, clear instructions.
Any suggestions, guys?
P.S. I've never done phone reset on SGS-9, how it works? Is it quick and safe enough? My wife's phone don't have sideloaded and/or pirated apps, everything by original, Google- & Samsung way.
Update: I resolved my issue by updating phone from PC, using Samsung's "Smart Switch" application - everything went smooth and easy.
P.S. Big thanks to this guide: https://thedroidguy.com/how-to-fix-...not-update-to-latest-software-version-1097987
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
sensboston said:
Update 2: My question received no answers, even no attention but I still believe in people (generally)
So, after update to Android 10 on SGS9, my wife found what the new camera app is kinda downgrade: she doesn't likes new video mode full screen chooser (instead of "scroller") and some other small things. By the way, I clearly understood her: for example, on her SGS9 (updated via PC) video has, by default, bigger zoom than mine SGS9! It's kinda ridiculous but I understand, some parts of the software was written by Korean guys
My question is: could you provide some tips how to install stock camera app from the previous firmware (Android 9), without flashing back old firmware (I suspect what Sam-damn-sung and X****&nity will not support Android 9 anymore)?
Thank you!
P.S. I know how the google search works; I know even more - how xda-dev search works too but I can't find exact answer to my question, sorry!
Click to expand...
Click to collapse
I think it's more no one has xfinity. I was one of the few and first to have xfinity when I got my s8. xfinity is a weird setup compared to most phones. I had to ditch em when they charged me like 3 or 4 times in one month, it took me almost 4 months to get a refund.
With root you might be able to get the old camera working possibly. Or gcam I'm no developer so I wouldnt know the exacts. And I still run my xfinity s8 ???
Hi All, it might be a stupid question but A13 upgrade in Pixel 6 Pro is mandatory as system update configuration like monthly security patch? I'm not big fan of A13 and preferring to stay at A12.
I *think* I understand what you're asking, but not positive.
If you're not rooted, you will definitely be eventually receiving the update no matter what. This is true of all OTAs on most every phone. You can disable automatic updates in Developer options, however even then some updates come through anyway. Others have seen it before, and I've seen it again just recently.
If you're rooted, then you might get an annoying message to update, but the update will always fail to install.
I hope that answers your question.
So, you plan on never updating your Pixel 6 Pro again...ever? (unless you like Android 14 or beyond much better)