User Profile
magenta8240075
Newbie Caller
Joined 6 years ago
User Widgets
Contribuciones
Re: Norton Password Manager UNUSABLE on T-Mobile Branded OnePlus 6T
Thanks for trying, but with all due respect, "end of life" is no more than a trite expression in my opinion. This phone isn't "dead," it has merely been "poisoned." It's far from dead, its heartbeat is STRONG. Rather, my feeling is that someone who wants me to buy a NEW deviceis slowly pushing out "OnePlus 6T arsenic smoothies"...and I think thatstinks. So, not that I'll get a straight answer from a T-Mobile Developer; but I will wait (hope?) for a straightanswer from someone with intimate knowledge concerning those two files I mentioned. By the way, I should add that this issue doesn't impact only Norton Password Manager on my device. It also impacted LG ThinQ and ResMed's MyAir--FREE apps (not ones I have to pay for, so there's no incentive to "break" them)--and possibly others I don't yet know about. Both of thoseapps also "broke" with a similar "This app doesn't work on a rooted device" message. But why? My device has never beenrooted! Certainly not with my knowledge. No, this is just like dominoes falling or the proverbial straw on a camel's back...every new "push" makes previous devices less and less reliable. And while this might not actually be "planned obsolescence," to me, something is rotten in the City of Bellevue.8Visto0likes0ComentariosNorton Password Manager UNUSABLE on T-Mobile Branded OnePlus 6T
I can no longer use Norton Password Manager on my T-Mobile Branded OnePlus 6T. The Norton Password Manager app (also the LG ThinQ app, possibly others as well) tell me my phone is rooted. However, I do not believe that, I have never rooted it. In addition, Norton 360 for Android tells me my phone is not rooted. However, I do get a "ROOTED" message for "Dangerous props" showing on the app, RootBeer Sample. I would like to tell you why I think that is, based on info I've been given. There are apparently two badly-written, or incorrectly-setvariables (0 or 1) on two files on the phone. Those files being, "ro.debuggable" and "ro.secure". At some point in time, possibly a recent security update to the device, the 0's and/or 1's in those two files were not "switched back" after the phone got its update. I believe it is POSSIBLE that it was an update T-Mobile "pushed." I have tried to coordinate this "flaw"--that's MY characterization--between OnePlus and Norton. But from what I have gathered, I believe T-Mobile now needs to take action to get this fixed. Can T-Mobile please help me out with this? (It is SO DIFFICULTwhen OnePlus makes the device, Norton makes the app, and T-Mobile provides the updates--what a nightmare!!!) One company is a bit impatient, so I need T-Mobile to check out the problem as quickly as possible. (For your info, the Norton app has already reached the point it is UNUSABLE, so please, help if you can. And I do not believe a "factory reset" will be helpful in this case--because remember, updated software is unaffected by "factory reset!")159Visto0likes2Comentarios