Hello. I know this is a problem that many have had and many have posted about but there are so many different varieties of the error and so many different solutions I cannot figure out what solution applied to what problem. Also, I find it difficult to track what solutions work on what versions of things.
I am getting this "Access Denied" message on my phone within the Samsung Wear app when I click on the Samsung Pay app.
I do NOT have the Samsung Pay app on my phone, nor to I need it. Just want it working on my watch.
The watch is a Watch3, Tizen 5.5.
The phone is LineageOS 16 with root and Developer Options and USB Debugging disabled.
Everything else works, including ECG and BP, thought I did have to use a Samsung Health Monitor app where the system root check was disabled.
Is it possible to disable the check in the Samsung Pay, app, too?
I think probably no one will be able to give me solution to my particular problem because I probably have not given enough details and I would know what else I might need to give.
Maybe my most important question is:
When I do get the "Access Denied" error, is there any log I where I could see what check it failed that cause it to give that error?
I don't care about using "Samsung Pay" on my phone (I can use Google Pay instead which works fine), BUT is the "Samsung Pay" apk not installing on my phone the exact same problem as the "Samsung Pay Watch 3 Plug-In" not opening? If I go though all the "fixes" for "Samsung Pay" on the internet would those work for the "Samsung Pay Watch 3 Plug-In", too?
1) Was it that it thinks my phone it rooted? If not, then I could stop fiddling with Magisk Hide. I was using LineageOS before just fine without it.
2) Is it Knox failure? If so, then I would have to figure out how that is possible on LineageOS.
3) Is it some SafetyNet thing? Because Magisk tells me that passes.
4) If none of the above, then what? (this is what I was hoping some error log would tell me)
I do have a another phone, a Moto Z4, on which everything, including Samsumg Pay on my Watch, works just fine.
Thanks.
Related
So I got a new toy. A Samsung Gear Live. I've had it for a week and so far really like it. The biggest issue I seem to be having is the companion apps. I don't know why, but they refuse to work. Everytime I try to use one I get an error message to the tune of, " not connected to a device with this application" or "lost connection to phone". This is clearly untrue. I can see that I'm still connected and even the device itself acknowledges it. I just can't figure it out.
I have attempted a power cycle, using the restart function, a hard reboot, even reseting it back to factory. I rebooted my phone, Uninstalled and reinstalled the apps on the phone, and still no luck. I'm at a loss. Anyone who knows what to do on this front would be very welcome.
What are companion apps?
Sent from my SM-N910T3 using XDA-Developers mobile app
Companion apps, are the apps that are activated on your smart watch. Like the dominoes easy order app, or a bank app that let's you check your balances without pulling out your phone.
I did find my problem however. It seems that my gear live was shipped with a dev kit. I had to completely reflash it to stock software to get it to run correctly.
How did you figure out it was a dev kit? Im having similar problems. Thanks.
Fixed the problem resetting the watch and reinstalling the Android wear app. However now in the storange manager its showing three of several apps. How to fix please?
You can find if it has a Dev kit under the settings. Under build I believe. It should be a set of numbers with "dev" somewhere in it. If that's there, it's gonna hold up your regular use of the watch. It caused the apps not to work right or not to show up, etc. I'll see if I can find the link I used before for how I reset the watch to stock firmware.
I have been going through and optimizing my T813 by disabling stuff that doesn't need to be running, firewalling off anything that does need network access, etc. However, I've run into a couple odd issues.
The first is DRParser.apk (DRparser Mode). It is marked as safe to disable on the Galaxy S6/S7, and I have. Or at least I tried. Even when it is frozen, it is somehow getting started because it is banging at the firewall like nuts. I have AFWall+ setup to show toasts from the logger, and it is constantly showing DRparser Mode has been denied access to a half dozen IP addresses. I double checked, and yes, it really is disabled in Titanium Backup. There is some serious WTH going on here, as it persists after a reboot. I have used TiBu to successfully freeze other services, so I'm not sure what is so special about this one.
The other weird one is mDNS, which I believe is part of the "find stuff nearby" functionality. I don't actually have a problem with it, but I can't find a specific service to enable in the firewall. I'm guessing it's bundled with something else, but I'm not sure what. It's also getting flag by AFWall, but not nearly as often.
The last one is the game optimizer service. I'm not sure why it is trying to access the network, but it is. I'm tempted to freeze it, but I'm not sure what it actually does.
Anyone have any ideas on these?
jshamlet said:
I have been going through and optimizing my T813 by disabling stuff that doesn't need to be running, firewalling off anything that does need network access, etc. However, I've run into a couple odd issues.
The first is DRParser.apk (DRparser Mode). It is marked as safe to disable on the Galaxy S6/S7, and I have. Or at least I tried. Even when it is frozen, it is somehow getting started because it is banging at the firewall like nuts. I have AFWall+ setup to show toasts from the logger, and it is constantly showing DRparser Mode has been denied access to a half dozen IP addresses. I double checked, and yes, it really is disabled in Titanium Backup. There is some serious WTH going on here, as it persists after a reboot. I have used TiBu to successfully freeze other services, so I'm not sure what is so special about this one.
The other weird one is mDNS, which I believe is part of the "find stuff nearby" functionality. I don't actually have a problem with it, but I can't find a specific service to enable in the firewall. I'm guessing it's bundled with something else, but I'm not sure what. It's also getting flag by AFWall, but not nearly as often.
The last one is the game optimizer service. I'm not sure why it is trying to access the network, but it is. I'm tempted to freeze it, but I'm not sure what it actually does.
Anyone have any ideas on these?
Click to expand...
Click to collapse
I can't even find anything via google that even explains what this apk does. But I did find that the app associated with it is com.sec.android.app.parser. You might want to look for that in /Setup/apps. Once you open apps, you might have to click the settings and choose "show system" for it to appear in the list. I'm running the RR ROM on my T810 and that app isn't installed with the Pico gapps, so I can't test it.
edit: After a little more research, it appears that the apps function is to decode "special codes" that you dial on your phone. Without it, you won't be able to dial those codes. But I have no idea why that would require access through your firewall. But it would explain why it isn't found on my T810, which doesn't have a cellphone function.
This is on a T813, which also has no LTE functionality. I'm guessing Samsung puts a largely "standard" image on these devices, as it also has the Phone services as well. (from poking around, this thing feels a bit like a gigantic Galaxy S6). However, it's a moot issue, as it is lumped under a bunch of other stuff, at least a couple of which do require network access. So, whatever it is, I have to let it through. :|
I did, however, come across some info on the mDNS issue:
https://forum.xda-developers.com/showpost.php?p=63977673&postcount=2742
Apparently that is a strange AFWall+ issue, and there is a custom script to resolve the issue.
jshamlet said:
This is on a T813, which also has no LTE functionality. I'm guessing Samsung puts a largely "standard" image on these devices, as it also has the Phone services as well. (from poking around, this thing feels a bit like a gigantic Galaxy S6). However, it's a moot issue, as it is lumped under a bunch of other stuff, at least a couple of which do require network access. So, whatever it is, I have to let it through. :|
I did, however, come across some info on the mDNS issue:
https://forum.xda-developers.com/showpost.php?p=63977673&postcount=2742
Apparently that is a strange AFWall+ issue, and there is a custom script to resolve the issue.
Click to expand...
Click to collapse
It may be "lumped with other stuff" but I would think that "the stuff" would all be phone related and therefore removable. It isn't there in the custom ROMS. Did you look for the app I listed in your app settings?
Yes, it's there. DRParser.apk in /system/app. I can, if I need to, delete it now that I have a full system backup on the SD card - which I suppose is the next step. I usually disable services rather than deleting them, though.
jshamlet said:
Yes, it's there. DRParser.apk in /system/app. I can, if I need to, delete it now that I have a full system backup on the SD card - which I suppose is the next step. I usually disable services rather than deleting them, though.
Click to expand...
Click to collapse
Renaming or deleting the apk is an option, but I was talking about disabling com.sec.android.app.parser in the app settings.
Recently did a factory reset of my phone to free up some system memory. As I was trying to get my phone setup back the way I had it ( first ever reset) I decided to do something different and ran BK manager to block some bloatware for hogging all the functional memory instead of disabling them in app manager like I did before. Well I got a little trigger happy and disabled Samsung kies. I didn't know what it was. It looked like a lot of other BS Samsung apps. Later I tried to download Netflix and I kept getting an error message stating that the app did not support rooted phones. Not sure what I did but some other apps that used to work no longer work either. I went back into BK and App manager and Samsung kies is nowhere to be found. How do I get it back? Is this even the problem or did I accidentally root my phone somehow? Please help. Thank you.
Hi all I'm still in 2 minds whether i root my note 9, I'm not sure I wanna lose sasung pay, I'm trying to get google pay to work on my rooted S7 to make comparisons but it's not working I get errors that it's been rooted. I thought google pay works with rooted devices? I've followed the instructions such as hiding it magdisk but it fails safety net...any advice?
Thanks
Some mods will screw Safety Net and there's nothing you can do about it. For example, Xposed. You should disable all Magisk modules, and try them one at a time until you find the culprit, and see if you can live without it.
Hey all!
I'll do the long story short: I am stuck on a Korean Note 9 in Europe, which means no Samsung pay for me.
Now, since I can't get Samsung Pay, and I saw I can't instal Google pay either(not sure why the Play store wouldn't let me), I have been contemplating before setting up my Note, to maybe root it, and going stock european ROM.
I have rooted multiple phones in the past, but I am not sure if it's worth it in the present, as the UIs are pretty good and complete.
Now my question is, do I lose anything else by rooting? Could someone Eli~10 what that knox fuse tripping means for future limitations/possibilities? Also, besides my reason to set custom dpi for an app, why else would one root its Note 9 nowadays?
Thanks!
I'm pretty sure you lose Private Folder and maybe Samsung Health if you root. I'd consider rooting only for Viper4Android & the YouTube Background Playback xposed module. But I saw there is xposed for non-rooted phones & Note9 has Dolby Atmos so I think this will be my first android phone that I won't root (don't even need root anymore).
It is personal preference, but all apps that require Knox will cease to work, so almost all payment apps will be of no use. While the first comment said S Health would no longer work, months ago a workaround was found to get it to work. Many apps I like require root, but there are nonroot workarounds for most of them.
Snowby123 said:
It is personal preference, but all apps that require Knox will cease to work, so almost all payment apps will be of no use. While the first comment said S Health would no longer work, months ago a workaround was found to get it to work. Many apps I like require root, but there are nonroot workarounds for most of them.
Click to expand...
Click to collapse
And which are specifically the apps that require Knox to work?
I don't know all of them. The only ones I know are Samsung Pay, Samsung Pass, Secure Folder, and Adhell, but development of Adhell ceased months ago. There are definitely more.
I had the same dilemma when I first bought my Note 9. For a couple of seconds. Then, I rooted it as I do with every Android phone I get since 2009.
Any app, website, or service that demands a non-rooted device goes automatically to my black list.