I can't get Google pay to work on my OnePlus 6t that has oxgen software how can I fix this problem
mt465 said:
I can't get Google pay to work on my OnePlus 6t that has oxgen software how can I fix this problem
Click to expand...
Click to collapse
A bit more info .. are you stock or rooted.. latest firmware, latest goay? As it does work...
mt465 said:
I can't get Google pay to work on my OnePlus 6t that has oxgen software how can I fix this problem
Click to expand...
Click to collapse
It's a Profile problem. You need the MagiskHide Props Module.
mt465 said:
I can't get Google pay to work on my OnePlus 6t that has oxgen software
Click to expand...
Click to collapse
How do I do that
mt465 said:
I can't get Google pay to work on my OnePlus 6t that has oxgen software how can I fix this problem
Click to expand...
Click to collapse
I'm on oxygen os version 10.3.2
Huskied said:
It's a Profile problem. You need the MagiskHide Props Module.
Click to expand...
Click to collapse
How do I do that
And I think I'm on stock
mt465 said:
And I think I'm on stock
Click to expand...
Click to collapse
ah... Yeah you'll need to root it to fix it. Don't know any fix for non-root since this is a error in the FP.
Huskied said:
ah... Yeah you'll need to root it to fix it. Don't know any fix for non-root since this is a error in the FP.
Click to expand...
Click to collapse
I take it..that fp for is finger print.. if that is the case it isn't needed as a pin works just fine... But as the OP doesn't appear what's on his/her phone... They haven't said whether it's stock or rooted so till we know that we can guess all day..
lilbrat said:
I take it..that fp for is finger print.. if that is the case it isn't needed as a pin works just fine...
Click to expand...
Click to collapse
I mean as in Device Fingerprint. The one that is in the file Build.Prop
It's a error in that, resulting in fixing it by root. It has nothing to do with Security nor PINs.
EDIT: THIS is what I mean. I word in the FP results in failure. This is a fault on 1+ side.
Huskied said:
I mean as in Device Fingerprint. The one that is in the file Build.Prop
It's a error in that, resulting in fixing it by root. It has nothing to do with Security nor PINs.
Click to expand...
Click to collapse
But he hasn't said what the issue is... except that he can't get it to work... Not one word of what's on his phone , as I said before stock rooted...did he update to the latest GPay as the version on the 6 is really old...hell we could guess all day without the basic information...
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
Huskied said:
I mean as in Device Fingerprint. The one that is in the file Build.Prop
It's a error in that, resulting in fixing it by root. It has nothing to do with Security nor PINs.
EDIT: THIS is what I mean. I word in the FP results in failure. This is a fault on 1+ side.
Click to expand...
Click to collapse
Hell you can't suggest that till you know if he's rooted or stock which he hasn't said..
lilbrat said:
But he hasn't said what the issue is... except that he can't get it to work... Not one word of what's on his phone , as I said before stock rooted...did he update to the latest GPay as the version on the 6 is really old...hell we could guess all day without the basic information...
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
Hell you can't suggest that till you know if he's rooted or stock which he hasn't said..
Click to expand...
Click to collapse
True and eh. I highly doubt Google could pull a Pokemon GO and look into files just to give it a red flag. Recently had to fix two others because of the same issue. This is indeed a issue that hasn't been fixed by 1+. If it isn't, and people are passing with the Fingerprint that is installed I will shut up. But I have yet to see that happen, Unfortunately.
Huskied said:
True and eh. I highly doubt Google could pull a Pokemon GO and look into files just to give it a red flag. Recently had to fix two others because of the same issue. This is indeed a issue that hasn't been fixed by 1+. If it isn't, and people are passing with the Fingerprint that is installed I will shut up. But I have yet to see that happen, Unfortunately.
Click to expand...
Click to collapse
I running Google Pay on my rooted 6t, without any Magisk mod except the core hide... I pass safetynet with ease...and my device is playstore certified.. and I had ran it unrooted without issues ..
But the OP seem a bit lost...
Related
i found on miui cn forum....
but not release yet...but hope's this will contiunes and finally realese
Post link so we can also see. Any news about it?
Xristomania said:
Post link so we can also see. Any news about it?
Click to expand...
Click to collapse
here : http://www.miui.com/thread-4826394-1-1.html
Fake.
This is just Android N-ify Xposed module + some build.prop edits.
banmeifyouwant said:
Fake.
This is just Android N-ify Xposed module + some build.prop edits.
Click to expand...
Click to collapse
see whos the one make it thread...he is administrator that's forum...
but maybe yes maybe no...only god know
Mayoz said:
see whos the one make it thread...he is administrator that's forum...
but maybe yes maybe no...only god know
Click to expand...
Click to collapse
It is. There is no CM14.
banmeifyouwant said:
It is. There is no CM14.
Click to expand...
Click to collapse
Also the cm api is 6 so i think that @banmeifyouwant is right.
Fake
LOL, really a fake. Noticed it without even opening the screenshot, just a CM13 with edited build.prop, an icon pack and N-Ify module. My phone looks exactly like that. Just watch the wallpaper and compare it with the CM we already have. XD
https://sourceforge.net/projects/abhi/files/?source=navbar here's a link you can try. CM14, looks legit, but some say it doesnt boot. Im testing now.
ryanchua0202 said:
https://sourceforge.net/projects/abhi/files/?source=navbar here's a link you can try. CM14, looks legit, but some say it doesnt boot. Im testing now.
Click to expand...
Click to collapse
I'm waiting dude. Since I'm using my kenzo as my primary device, I can't take that risk. Appreciate you for talking that risk
AravindhStanley said:
I'm waiting dude. Since I'm using my kenzo as my primary device, I can't take that risk. Appreciate you for talking that risk
Click to expand...
Click to collapse
No problems. At XDA, we should help each other . By the way, it didn't boot. It gave a bootloop. Hope the dev fixes it!
---------- Post added at 04:26 AM ---------- Previous post was at 03:43 AM ----------
https://plus.google.com/+ParthBhatia98/posts/5kiAgcapD1d Found this. TheStrix has started work on CM14, so we have to wait.
Anyone tried this ?
https://androidfilehost.com/?fid=24713784966775139
Fake af.
Sent from my Redmi Note 3 using Tapatalk
Android O DP4
Build number is OPP4.170623.014.
Factory images
Full OTA images
Release notes
Developers blog
Can someone running the build report back on whether the dark system them is back? I still can't stand that lighter notification tray...
dshoe said:
Can someone running the build report back on whether the dark system them is back? I still can't stand that lighter notification tray...
Click to expand...
Click to collapse
I just received the notification to update. Will let you know. Unless someone beats me to it.
---------- Post added at 07:56 PM ---------- Previous post was at 07:22 PM ----------
dshoe said:
Can someone running the build report back on whether the dark system them is back? I still can't stand that lighter notification tray...
Click to expand...
Click to collapse
I don't see a dark theme. Sorry man.
Mr Patchy Patch said:
I just received the notification to update. Will let you know. Unless someone beats me to it.
---------- Post added at 07:56 PM ---------- Previous post was at 07:22 PM ----------
I don't see a dark theme. Sorry man.
Click to expand...
Click to collapse
Any change with the bluetooth stuttering?
Jerreth said:
Any change with the bluetooth stuttering?
Click to expand...
Click to collapse
Can't help ya there man. I don't use Bluetooth often enough. Sorry
Mr Patchy Patch said:
I don't see a dark theme. Sorry man.
Click to expand...
Click to collapse
Well that's devastating. Between this and the emoji, it seems like the one big feature of Android O is to make it uglier.
Slusho said:
Well that's devastating. Between this and the emoji, it seems like the one big feature of Android O is to make it uglier.
Click to expand...
Click to collapse
It doesn't mean the final release won't have a dark theme. But it's probably unlikely after what I've read from the Reddit ama last week with Google engineers answering questions.
Mr Patchy Patch said:
Can't help ya there man. I don't use Bluetooth often enough. Sorry
Click to expand...
Click to collapse
I had no issue with ODP3, may be a YMMV situation? I set my codec to AptX as well.
Has anyone tried TWRP yet with this? Mine just seems to flicker and not work when i try to boot it from the bootloader.
Anyone know if DP4 is rootable?
chevycam94 said:
Anyone know if DP4 is rootable?
Click to expand...
Click to collapse
Seems to be...check here: https://forum.xda-developers.com/pi...android-o-dev-preview-1-pixel-t3591548/page14
Anyone seen the Android squid when you tap on the Android version? Not sure if that was in DP3. Boot animation is a little different.
Sent from my Pixel XL using Tapatalk
is there a way to install magisk on android O DP4?
Please upload system dump from Pixel XL DP4 :3
emplox said:
Has anyone tried TWRP yet with this? Mine just seems to flicker and not work when i try to boot it from the bootloader.
Click to expand...
Click to collapse
TWRP doesn't work consistently, but Chainfire has a fix if you have a computer with adb handy, I'll try and find a link.
EDIT: Here you go, it's under the "manual TWRP instructions" in this post.
In other news, I have SuperSU v2.82-SR1 from Chainfire working just fine on DP4.
SonarMonkey said:
TWRP doesn't work consistently, but Chainfire has a fix if you have a computer with adb handy, I'll try and find a link.
EDIT: Here you go, it's under the "manual TWRP instructions" in this post.
In other news, I have SuperSU v2.82-SR1 from Chainfire working just fine on DP4.
Click to expand...
Click to collapse
ty, sir!
Anyone notice anything new?
emplox said:
is there a way to install magisk on android O DP4?
Click to expand...
Click to collapse
No boot-to-root images for Magisk, so no way to install it without first having a working TWRP.
I still get the yellow O target thing... Anything special I have to do to unlock the Octopus? Or is Verizon suppressing my fun again?
Legobricke said:
Anyone notice anything new?
Click to expand...
Click to collapse
I haven't noticed anything to be honest.
I need to know how can I install the developer 3 on my phone. I tried it and it gave me a yellow error message that said something like hardware and software version don't match and it never loads after reboot.
PS I have the t-mobile veriant tieht international installed.
juancastro86 said:
I need to know how can I install the developer 3 on my phone. I tried it and it gave me a yellow error message that said something like hardware and software version don't match and it never loads after reboot.
PS I have the t-mobile veriant tieht international installed.
Click to expand...
Click to collapse
Answers to your case are already discussed and addressed in the DP3 threads
Striatum_bdr said:
Answers to your case are already discussed and addressed in the DP3 threads
Click to expand...
Click to collapse
I checked and I did not see the answer. Cuase they don't have an answer to how to fix it.
juancastro86 said:
I checked and I did not see the answer. Cuase they don't have an answer to how to fix it.
Click to expand...
Click to collapse
Well, the answer already there
https://forum.xda-developers.com/showpost.php?p=79928232&postcount=24
To recover from HW missmach use MSM Download tool
jsergan said:
Well, the answer already there
https://forum.xda-developers.com/showpost.php?p=79928232&postcount=24
To recover from HW missmach use MSM Download tool
Click to expand...
Click to collapse
I had seen that before but I just don't want to mess with any files or mod anything.
juancastro86 said:
I had seen that before but I just don't want to mess with any files or mod anything.
Click to expand...
Click to collapse
So don't install DP3 and wait for a stable release in a few weeks
juancastro86 said:
I need to know how can I install the developer 3 on my phone. I tried it and it gave me a yellow error message that said something like hardware and software version don't match and it never loads after reboot.
PS I have the t-mobile veriant tieht international installed.
Click to expand...
Click to collapse
This us up to date instructions
https://forum.xda-developers.com/showpost.php?p=79954792&postcount=49
Just uploaded a guide
---------- Post added at 06:21 PM ---------- Previous post was at 06:20 PM ----------
https://forum.xda-developers.com/oneplus-6t/how-to/dp3-q-beta-t-mobile-guide-t3951701
ayjays said:
Just uploaded a guide
---------- Post added at 06:21 PM ---------- Previous post was at 06:20 PM ----------
https://forum.xda-developers.com/oneplus-6t/how-to/dp3-q-beta-t-mobile-guide-t3951701
Click to expand...
Click to collapse
Nice
Some people are just special.
Has anyone else had this issue? I got into a boot loop and had to restore my phone and now my fingerprint scanner will not let me register my fingerprint.
ruthlessnature said:
Has anyone else had this issue? I got into a boot loop and had to restore my phone and now my fingerprint scanner will not let me register my fingerprint.
Click to expand...
Click to collapse
It may be because of the screen protector I'm not sure but when I took mines off it worked perfectly
Exathi said:
It may be because of the screen protector I'm not sure but when I took mines off it worked perfectly
Click to expand...
Click to collapse
That message pops up as soon as I click to try to register my fingerprint, it doesn't even let me try to add it.
ruthlessnature said:
That message pops up as soon as I click to try to register my fingerprint, it doesn't even let me try to add it.
Click to expand...
Click to collapse
Did you restore via MSM?
champ784 said:
Did you restore via MSM?
Click to expand...
Click to collapse
Yes about 10 times now.
ruthlessnature said:
Yes about 10 times now.
Click to expand...
Click to collapse
What version are you restoring it to? Have you tried different versions? It sounds like it could be a hardware failure honestly
champ784 said:
What version are you restoring it to? Have you tried different versions? It sounds like it could be a hardware failure honestly
Click to expand...
Click to collapse
I've tried on 10.0.16 and 10.0.19 they are the only ones available 10.0.13 doesn't have any links to download it.
ruthlessnature said:
I've tried on 10.0.16 and 10.0.19 they are the only ones available 10.0.13 doesn't have any links to download it.
Click to expand...
Click to collapse
Hmm... I still think it sounds like it could be a hardware failure... I'd look at doing a warranty exchange through OnePlus
ruthlessnature said:
Has anyone else had this issue? I got into a boot loop and had to restore my phone and now my fingerprint scanner will not let me register my fingerprint.
Click to expand...
Click to collapse
Were you on a custom rom before you tried to restore?
---------- Post added at 09:50 PM ---------- Previous post was at 09:44 PM ----------
lendawg said:
Were you on a custom rom before you tried to restore?
Click to expand...
Click to collapse
I'm getting the same thing after coming back to stock from Omni rom. It was a known issue that there was supposedly a fix for by flashing a persist.img but it hasn't worked for me. I've tried everything and just ended up turning on face unlock.
lendawg said:
Were you on a custom rom before you tried to restore?
---------- Post added at 09:50 PM ---------- Previous post was at 09:44 PM ----------
I'm getting the same thing after coming back to stock from Omni rom. It was a known issue that there was supposedly a fix for by flashing a persist.img but it hasn't worked for me. I've tried everything and just ended up turning on face unlock.
Click to expand...
Click to collapse
I was not on a custom rom. I was rooted on the newest stock firmware. Where did you find the persist.img? I would like to try it to see if it works for me.
ruthlessnature said:
I was not on a custom rom. I was rooted on the newest stock firmware. Where did you find the persist.img? I would like to try it to see if it works for me.
Click to expand...
Click to collapse
Found it in a telegram group called hottdog dev although if it stopped working for you on stock firmware that leads me to believe it's a hardware issue for us.....weird
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
Are you on the t mobile variant?
lendawg said:
Found it in a telegram group called hottdog dev although if it stopped working for you on stock firmware that leads me to believe it's a hardware issue for us.....weird
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
Are you on the t mobile variant?
Click to expand...
Click to collapse
Yes T-Mobile variant.
ruthlessnature said:
Yes T-Mobile variant.
Click to expand...
Click to collapse
Hmm....this is really weird. Couldn't have anything to do with root otherwise I think more people would be having this problem.
lendawg said:
Hmm....this is really weird. Couldn't have anything to do with root otherwise I think more people would be having this problem.
Click to expand...
Click to collapse
I contacted TMobile via Twitter and they're sending me a replacement device. They said that there are multiple reports online of this happening so if I was you I'd just get a warranty exchange.
lendawg said:
I contacted TMobile via Twitter and they're sending me a replacement device. They said that there are multiple reports online of this happening so if I was you I'd just get a warranty exchange.
Click to expand...
Click to collapse
I've been trying to get ahold of TMobile for almost a week now. Maybe I need to try Twitter.
ruthlessnature said:
I've been trying to get ahold of TMobile for almost a week now. Maybe I need to try Twitter.
Click to expand...
Click to collapse
Try Twitter I was all set in about an hour. It's TMobile help on Twitter.
lendawg said:
Try Twitter I was all set in about an hour. It's TMobile help on Twitter.
Click to expand...
Click to collapse
Thanks for the info. I messaged them and they are sending me a new phone . Tracking says I should have it tom. Already.
ruthlessnature said:
Thanks for the info. I messaged them and they are sending me a new phone . Tracking says I should have it tom. Already.
Click to expand...
Click to collapse
Good to hear and glad I could help!
Exathi said:
It may be because of the screen protector I'm not sure but when I took mines off it worked perfectly
Click to expand...
Click to collapse
Yep had to remove any and all screen protectors...
Skippy38 said:
Yep had to remove any and all screen protectors...
Click to expand...
Click to collapse
No this issue wasn't letting us even start to register our fingerprints.
As I was surfing on my computer, my phone was next to the screen on a stand charging. The phone made a sudden reboot, a crash, then took awhile to boot up.
The phone is rooted and bootloader unlocked.
I have taken a bug report from within the developer section. Something for which I have not done before, ever.
How can I find out what caused this sudden crash/reboot ?
rooted devices are unstable, It could just be a random occurrence. Sometimes, my apps crash and take a few minutes before I can use em again.
Arealhooman said:
rooted devices are unstable, It could just be a random occurrence. Sometimes, my apps crash and take a few minutes before I can use em again.
Click to expand...
Click to collapse
Yeah I understand that. But this is the first time I've ever seen any of my rooted phones reboot like that. I'm going on a trip soon to a concert and I don't want this to become an issue for me.
If it happens often then you can investigat. ATM not worth it.
Arealhooman said:
If it happens often then you can investigat. ATM not worth it.
Click to expand...
Click to collapse
Okay thanks. That is good advice.
rogerrulez said:
Okay thanks. That is good advice.
Click to expand...
Click to collapse
On what version of Nothing OS did it happen?
TheNewHEROBRINE said:
On what version of Nothing OS did it happen?
Click to expand...
Click to collapse
1.5.3 wit the hotfix update.
Been noticing other weird things lately as well like, when using bluetooth earbuds the wifi would sometimes cut out especially on the 2.4ghz band.
rogerrulez said:
1.5.3 wit the hotfix update.
Been noticing other weird things lately as well like, when using bluetooth earbuds the wifi would sometimes cut out especially on the 2.4ghz band.
Click to expand...
Click to collapse
There is a known incompatibility between Magisk and that version of NothingOS. You can read more about it here and here. Several Magisk modules have been created to try mitigating the issue such as this one: https://github.com/LukeSkyD/NP1-MGLRU-FIX
TheNewHEROBRINE said:
There is a known incompatibility between Magisk and that version of NothingOS. You can read more about it here and here. Several Magisk modules have been created to try mitigating the issue such as this one: https://github.com/LukeSkyD/NP1-MGLRU-FIX
Click to expand...
Click to collapse
Thanks. I appreciate that.
TheNewHEROBRINE said:
There is a known incompatibility between Magisk and that version of NothingOS. You can read more about it here and here. Several Magisk modules have been created to try mitigating the issue such as this one: https://github.com/LukeSkyD/NP1-MGLRU-FIX
Click to expand...
Click to collapse
The first link you mentioned, the picture of the crash is exactly what mine looked like. And from reading the stuff from the second link that confirmed my suspicion in that Nothing does not want anyone messing with their phones.
That's a shame.
rogerrulez said:
The first link you mentioned, the picture of the crash is exactly what mine looked like. And from reading the stuff from the second link that confirmed my suspicion in that Nothing does not want anyone messing with their phones.
That's a shame.
Click to expand...
Click to collapse
It may just be an unintentional mistake. We need to wait and see what will happen with the next update.
TheNewHEROBRINE said:
It may just be an unintentional mistake. We need to wait and see what will happen with the next update.
Click to expand...
Click to collapse
Do you suggest unrooting for the time being ?
rogerrulez said:
Do you suggest unrooting for the time being ?
Click to expand...
Click to collapse
Try the Magisk module and see if it solves the issue for you
TheNewHEROBRINE said:
Try the Magisk module and see if it solves the issue for you
Click to expand...
Click to collapse
I checked my modules. I have version ver 4 installed since I rooted. The link you sent brought me to V3.
rogerrulez said:
I checked my modules. I have version ver 4 installed since I rooted. The link you sent brought me to V3.
Click to expand...
Click to collapse
It's probably from a different author then
TheNewHEROBRINE said:
It's probably from a different author then
Click to expand...
Click to collapse
Yeah, not sure where I got it from at the moment. V3 was only released 2 weeks ago. I should probably try this version and remove the V4 I have installed now.
TheNewHEROBRINE said:
There is a known incompatibility between Magisk and that version of NothingOS. You can read more about it here and here. Several Magisk modules have been created to try mitigating the issue such as this one: https://github.com/LukeSkyD/NP1-MGLRU-FIX
Click to expand...
Click to collapse
Thanks! Man, my phone has been crashing like crazy, this seemed to of fixed it so far thanks!