I have installed PDP as I do with every new phone although it doesn't seem to be working on my new S8+. It worked fine on my S7E. Any idea why it's not now or anyone having the same issues?
Related
Hi
This is really a warning to anyone who has an Android wear (or probably any other kind of smartwatch)
My Gear LIve and LG Watch R worked perfectly with KK and Lollipop but with MM 522 it just would not work properly at all
i worked with a dev of one of the apps and it was only the Huawei with MM that caused any problems and notifications were just not getting to the watch
MM on a samsung worked no trouble and going back to 5.1.1 on the M7 again worked perfect
I liked MM but i didnt see that much difference to being worth keeping without the watch
So if you are planning on Upgrading and have a smartwatch then you will have issues
I am now back on 5.1.1 and rooted and all works fine
I have Asus ZenWatch 2 and it works with B522 properly. Only issue I have noticed is infrequent unconnecting, about twice a week. But I just run Android Wear app and watch is connected again.
I must admit I'm surprised that's is working OK for you add the tests we got when trying to resolve the issues were all down to huawei and the non standard calls they make and the permissions issues that were occurring
The doze feature in mm seemed to be conflicting with huawei's own features and stopping a lot of the notifications getting through even though those apps were set to protected.
It also seemed to be an issue with 1 app calling another appointment and again even though that permission was granted it still gave us issues.
But I suppose in the end every setup is different and in all honesty I don't think mm was a great step up grim lollipop anyway or at least not on the huawei
Sent from my SM-N920C using XDA-Developers mobile app
I have a Samsung Gear S2 Classic and since I installed MM on my MT7-L09, Samsung Gear app will not not load, it just opens and closes in a flash.
The only way to make it work is to switch off the Bluetooth on the phone, then open the Samsung Gear App, and press connect from the app. This will switch the Bluetooth back on, connects to the watch and the app works.
Weird and very frustrating until I figured out a workaround!
Sent using Tapatalk
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
sthentic said:
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
Click to expand...
Click to collapse
I've got the first gen Moto 360. when I updated to MM my watch at didn't receive any notifications (even the test ones). I did a factory reset and everything works fine now. The only issue I have is that sometimes the Gmail app pushes a ton of notifications for the same email.
Good morning everybody,
I flashed the UK version of Nougat on my S7 Edge last wednesday (I'm from the Netherlands, so the update is not yet available on my device).
It worked perfectly and Nougat has been great so far (except for the headsup preview, wich I have since disabled using ADB).
But ever since the install I keep getting a pop-up saying that Authservice has stopped. I'll get a few of these in a row and then I'll get one saying Authservice keeps stopping. I can close the notification and tell it to close the app, and it will be gone for a while.
Does anyone has any idea what this is and how I can stop it?
I think it has something to do with Samsung Pay and the fact that Pay isn't available in the Netherlands yet...
But I've tried force stopping and disabling Pay, to no avail.
Thanks!
Install package disabler (or Titanium if you're rooted) and search for com.samsung.android.authservice then disable/freeze it. This should stop it.
just optimize your phone in device maintenance. its what i did..
:good: This worked for me. Thank you.
No it didn't at least. It only worked for a while.
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Not sure about editing the build.prop but I have the Gear Fit 2 Pro and the Gear S3 Frontier both connected to my 6T. I found that sometimes the app is kind of finicky to get connected and I will have to turn Bluetooth off and on again, sometimes a couple of times to get connected the first time. Also keep the screen on your phone on to see if there is a popup to connect. Maybe even cycle the watch off and back on also along with the phone if all else fails. I was ready to give up at one point and it all the sudden connected. If none of that works I'm not sure what else to try but maybe someone else will have some ideas.
tnap1979 said:
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Click to expand...
Click to collapse
Along with the Galaxy Wearable app there is also a Gear S Plugin that needs to be installed. The first time I set up my Gear S3 Frontier the plugin was automatically installed but when I had to set my watch up a second time I had to manually install the plugin.
alryder said:
Along with the Galaxy Wearable app there is also a Gear S Plugin that needs to be installed. The first time I set up my Gear S3 Frontier the plugin was automatically installed but when I had to set my watch up a second time I had to manually install the plugin.
Click to expand...
Click to collapse
This is good to know...Been a good while since I set mine up so wasn't aware of that. Thanks for the info!
tnap1979 said:
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Click to expand...
Click to collapse
I have the gear S3 frontier and fit2 pro. I paired them with minimal issues. Did you reset your watch before trying to pair it?
I have an S3 Frontier, and every clean install ROM switch I have to reset the watch. I think they do it for security purposes? Unless someone knows something I don't, I've never found a way to reconnect the watch to a different device without resetting the watch. The backup of the watch puts everything right back once connected, but still kind of annoying (as it adds back in "removed" programs and such).
I have to use the MagiskHide Props Module to get all the correct things installed for my watch to work. However on a stock 6T it should just work. That module should only come into play on a rooted / unlocked device.
I attempted to use AR but every app I have installed keeps telling me the OnePlus 8 Pro it is not supported. I have uninstalled arcore, I have also updated arcore to the latest version. I keep being told arcore is not functioning and in other apps I keep getting told the device is not supported.
I've also been experiencing issues with ARCore on my OnePlus 8 Pro, but not exactly the same as you describe it. On my OnePlus 8 Pro, ARCore apps launch fine and they detect my device is ARCore compatible, then it asks me to move my hand around to scan the surroundings. I do this, but my device just stays in this state forever. I have tried it in a really big room, moved my hand, even walked around a bit, but nothing. The device just keeps telling me to move my hand around. This happens on every ARCore app I've tried. I have not been able to successfully see an AR object on my OnePlus 8 Pro
marceltex said:
I've also been experiencing issues with ARCore on my OnePlus 8 Pro, but not exactly the same as you describe it. On my OnePlus 8 Pro, ARCore apps launch fine and they detect my device is ARCore compatible, then it asks me to move my hand around to scan the surroundings. I do this, but my device just stays in this state forever. I have tried it in a really big room, moved my hand, even walked around a bit, but nothing. The device just keeps telling me to move my hand around. This happens on every ARCore app I've tried. I have not been able to successfully see an AR object on my OnePlus 8 Pro
Click to expand...
Click to collapse
What you describe is exactly what would happen when I tried this on the OP7P. Haven't even bothered with this phone. Just figured it would be something I never have.
Flapjack said:
What you describe is exactly what would happen when I tried this on the OP7P. Haven't even bothered with this phone. Just figured it would be something I never have.
Click to expand...
Click to collapse
This is really disappointing to hear! I was really hoping this ARCore issue was just a software bug that they would fix soon. But since you say it's been an issue since the OnePlus 7 Pro, I don't really have much hope for a fix now
marceltex said:
This is really disappointing to hear! I was really hoping this ARCore issue was just a software bug that they would fix soon. But since you say it's been an issue since the OnePlus 7 Pro, I don't really have much hope for a fix now
Click to expand...
Click to collapse
We have to notify this problem to oneplus because i dont understand why everytime the op phones have these strangers bug
I just upgraded my OnePlus 8 Pro to OxygenOS 10.5.9 European version (IN11BA) and ARCore is now working perfectly on my phone! It starts up almost instantly like it asks me to move my hand around for like 1 or 2 seconds max and then goes into AR mode and displays AR objects
marceltex said:
I just upgraded my OnePlus 8 Pro to OxygenOS 10.5.9 European version (IN11BA) and ARCore is now working perfectly on my phone! It starts up almost instantly like it asks me to move my hand around for like 1 or 2 seconds max and then goes into AR mode and displays AR objects
Click to expand...
Click to collapse
What AR app works for you? I'm on the same firmware ( also EU model ) and no AR app will work for me. Maybe you can point me in the right direction?
Yesterday after 10.5.9 update AR worked for me but today It doesn't work. I noticed AR is working only soon after reboot.
minek124 said:
Yesterday after 10.5.9 update AR worked for me but today It doesn't work. I noticed AR is working only soon after reboot.
Click to expand...
Click to collapse
Yep, works just after reboot but later it doesn't. Then needs a new reboot. Must be something related to battery saving or something.
Same thing happened to me...
Take a look at my issue here and how I 'solved' it.. https://forum.xda-developers.com/oneplus-8-pro/help/augmented-reality-problem-bug-t4109129
i have a Samsung Galaxy S10 Plus Exynos and i rooted my device with magisk and this process goes perfect, i pass the the safetynet and works fine, i'm getting issues with some apps that detects that my device is rooted sccreen mirroring isnt working so i research and found that adding this line “wlan.wfd.hdcp=disable” in build.prop it'll fix the problem and it works but i dont know why adding this my dex mode stops working so i delete this line and my samsung dex works now but screen mirroring stops working someone has and idea on how to really fix this ?