Anyone else getting these notifications? It started for me after I updated the Boxer app in the play store. It seems to think the ph1 is rooted. This and the HSBC app keeps thinking ph1 is rooted.
Any possible fix I can try?
Thanks,
rtype0
got same issue in Honor v10 device. Starting today, with update of VMware/Airwatch Boxer app into Workspace ONE app.. Honor v10 is *not* OEM unlocked (neither rooted).
Related
Hi all,
I just updated my Nexus 4 to Lollipop and I sometimes get this notification:
An application requires an updat..
Requested by Google Play services
Whenever I tap it, it just brings me to the Play Store, in which I have no updates.
I updated to Lollipop via the OTA and have never flashed/unlocked/restored my phone; it's basically been on the same ROM since I bought it.
Any ideas how I can fix this notification?
Thanks.
Fred2028 said:
Hi all,
I just updated my Nexus 4 to Lollipop and I sometimes get this notification:
An application requires an updat..
Requested by Google Play services
Whenever I tap it, it just brings me to the Play Store, in which I have no updates.
I updated to Lollipop via the OTA and have never flashed/unlocked/restored my phone; it's basically been on the same ROM since I bought it.
Any ideas how I can fix this notification?
Thanks.
Click to expand...
Click to collapse
Ya, this seems to be a bit of a bug. Try to download the latest version of Google Play Services apk from apkmirror and install. It may or may not resolve the issue but it'll not harm.
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
pwnerman said:
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
Click to expand...
Click to collapse
an Android controlled toothbrush? is it april 1st? How does that work?
blue"tooth" LOL
You listen to music via vibration of your teeth.
railfan-eric said:
an Android controlled toothbrush? is it april 1st? How does that work?
Click to expand...
Click to collapse
it syncs with bluetooth and your phone camera to see what stops you are missing and over brushing. even without all that functionality and just as a dumb toothbrush it really is worth it
Same problem with LG G5 with 7.0. Did you find any solution?
Oral-B not starting on rooted devices
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
jbd7 said:
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
Click to expand...
Click to collapse
hi. did you find a solution? rootcloack didnt help me...
Ugo10 said:
hi. did you find a solution? rootcloack didnt help me...
Click to expand...
Click to collapse
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
jbd7 said:
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
Click to expand...
Click to collapse
it's perfect! thx!
Anyone else had this experience? While I was on Nougat I was getting "tag not supported" for each classic tag I was scanning. However, after updating to Oreo it started to successfully read mifare tags.
bomblader said:
Anyone else had this experience? While I was on Nougat I was getting "tag not supported" for each classic tag I was scanning. However, after updating to Oreo it started to successfully read mifare tags.
Click to expand...
Click to collapse
While I was on Android N I could not use my Barclays banking app. It kept saying rooted device even if I Odin flashed and went back to stock. Now on Oreo if I go back to stock I can use the Barclays app np, and if rooted with Magisk I simply tick it in Magisk hide and it works.
I think Oreo is a better base in a long time a lot of things that previously didn't work on N work on O.
bomblader said:
Anyone else had this experience? While I was on Nougat I was getting "tag not supported" for each classic tag I was scanning. However, after updating to Oreo it started to successfully read mifare tags.
Click to expand...
Click to collapse
Hi, are you using Snapdragon or Exynos variant? Thanks
So i recently updated to 338. Updated magisk to 18 and phone pe app itself got an update. Yesterday i tried paying through phone pe on flipkart and the transaction failed. It said the device is insecure. Now i don't know which among the 3 updates caused this. Can someone help? Thanks.
chaitanya.v said:
So i recently updated to 338. Updated magisk to 18 and phone pe app itself got an update. Yesterday i tried paying through phone pe on flipkart and the transaction failed. It said the device is insecure. Now i don't know which among the 3 updates caused this. Can someone help? Thanks.
Click to expand...
Click to collapse
Use Magisk Hide to hide root and also disable start on boot for Phone pe.
Try disabling telephone and sms permission from Google Play services
That might work.
Google pay and banking apps worked for me
I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
bigmikey307 said:
I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
Click to expand...
Click to collapse
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Yes, I was running the international software and had this same issue. Flashed back to stock T-Mobile software due to horror stories of the update to Android 10 bricking converted devices. Tried to turn these on again, and same story... Stock messaging app worked, Google's didn't.
I have converted to International and upgraded to 10.0 using Oxygen Updater then downloaded Google Messenger app and it works great. I do have a unlocked bootloader however.
qbanlinxx said:
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Click to expand...
Click to collapse
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
pyrorob said:
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
Click to expand...
Click to collapse
RCS on the stock TMobile firmware isn't the issue. Latest beta message installed, carrier services updated, still no RCS on my device.