Database Info

Wallet - Won't actually pay.

I've got Google Wallet installed, and cards activated, but I can't seem to make it actually pay...
A couple of trips to the local McDonalds - waking up my phone and waving it over the red sensor part of their card reader does nothing... unlocking or having wallet open at the time doesn't help either.
What am I doing wrong?
Sent from my SCH-I535 using xda app-developers app

Does your phone beep to let you know the nfc receiver has picked up an rfid signal?
Sent from my SCH-I535 using xda app-developers app

Did you have the NFC box check under settings more settings. It allows information to be sent between NFC device which is necessary.
Sent from my SPH-L710 using Tapatalk 2

No response at all from my phone or the terminal. Might as well have been waving my hand over it.
Does the phone need a physical "bump" instead of a wave to do its thing? I would expect this to work much the same as my proximity company ID badge.
NFC is turned on. SBeam is off (does that matter?)
Sent from my SCH-I535 using xda app-developers app

I always touch my phone back to the spot on the card reader. Do you have a case on your phone? There is only like a half inch of play before the phone is too far away. Try it again by tapping the phone.
Sent from my SCH-I535 using xda app-developers app

yeah. i get embarrass too if wallet doesnt work. how embarrassing!
but they have nfc soda vending machines in Atlantis hotel casino in reno! i tried it there with wallet on my nexus without the embarrassment and it works!
https://www.youtube.com/watch?v=OEwHMk4qFTs

"waving it over the red sensor part"
You dont know what your doing if you "waved" it. You must hold it up to the scanner for it to recognize. Also, if you have a case, it takes longer to pick up because the case adds thickness which reduces the bandwidth NFC can utilize due to a weaker signal.
Experiences: 8 successful payments. 1 failed (Walgreens isnt there yet)

There is no red sensor where I used it. 7-11 and cumbys. It's the grey part above the debit/credit card scanner that has the nfc symbol....Walgreen's failed for me also the manager said they just recently installed.
Sent from my SCH-I535 using xda premium

I've had the same exact problem as the OP. I tried mine at a local gas station where a friend works so I didn't look like a complete dunderhead and I tried it on 6 separate occasions and tried installing it several different times/ways and could never get it to work. They have the EZ Pay NFC reader above the credit card machine and every time I tried it it would not work no matter if I tapped it, took it out of the TPU case, got the cashier to hit credit, opened and unlocked the app. Nothing. It just simply refused to work. Maybe I'm just an idiot though, I just assume the EZ Pay NFC card reader would read my NFC chip in my phone. Maybe it won't. I am just at a loss. I just reset the app and went to my backup nandroid and left it along after all the attempts because I was so embarrassed.

i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol

Try without a case.I had no comm using NFC due to my case blocking the signal somehow. took it off and now it works every time.
Sent from my galaxy nexus using xda app-developers app

digitalsynner85 said:
i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol
Click to expand...
Click to collapse
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....

shangrila500 said:
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....
Click to expand...
Click to collapse
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.

digitalsynner85 said:
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.
Click to expand...
Click to collapse
Sorry about the misunderstanding. When I said off o meant my screen was locked. My phone just edited that part out. I have tried it like you did also, by opening the app right before touching it to the reader. Still doesn't work. It may just be an issue with my phone. No matter how I try to use it to pay it won't work...

i've had no issues having my nfc chip being scanned but i have yet to complete a purchase successfully. i'm going to chalk it up to the terminals not being configured correctly... my other nfc functions work fine.

Some dont work for some odd reasons because the storemanager/higher ups dont know what it is so they might have disabled it for what ever reason.
I know Walgreens has scanners but does not work JUST yet, they are partners of the whole NFC movement thing.
Stores that have worked for me are.
Chevron, 7-11 ( had to tilt there scanner up), McDonalds, BJ's (like walmart), Vending Machines.
Doesnt work: Walgreens, Some Random gas station out of town
I find that if you see a LED blinking or on thats connected to the scanner, the scanner works, but if it doesnt scan right away its the case's fault or not placing it.
Source: I like to consider myself a Wallet expert haha, my thread is over in Developer Section to get wallet as well. Also all my purchases have been used using a Otterbox Defender, and take about 3-5 seconds to complete the transaction.

mine failed as well at a jack in the box drive thru. looked like a fool. haha
i took my case off, opened the app, clicked the lock in the corner, entered my pin, and held it up against the reader for a good few seconds but nothing happened. nfc was on. their reader had like 4 spots for lights and the first one was on with a solid green light so not sure, hopefully it was their reader. will try again at a 7-11 if I can get over the embarassment

LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem

NeoMagus said:
LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem
Click to expand...
Click to collapse
Well said and 100% accurate. I bet the problems people are facing are user error or the terminal just doesnt work.

I've used mine on about three different occasions and it worked perfectly. But what's funny, I was in a local vzw store buying something. They have what looks like the press pass set up, tried to use it and it wouldn't go through. The girl checking me out was surprised and had no idea that you could even do that. Anyway, my point is that even though the card reader looks like it will work, if they don't have it set up it won't. Vzw's looks just like the ones at McDonald's.

Tap+Send

was trying this out for the first time and it's not working at all. We have a 920 and a 820 in the house tried a few different ways to use it and not working at all. I have tried it with the Bluetooth on and a separate time the Bluetooth connected and paired and still nothing works. I am trying to send a small picture turned on the tap+send and everything it asked me to on the phone still cant do it no accept notification or anything. Wondering what to do?

Covers and restart
proneto911 said:
was trying this out for the first time and it's not working at all. We have a 920 and a 820 in the house tried a few different ways to use it and not working at all. I have tried it with the Bluetooth on and a separate time the Bluetooth connected and paired and still nothing works. I am trying to send a small picture turned on the tap+send and everything it asked me to on the phone still cant do it no accept notification or anything. Wondering what to do?
Click to expand...
Click to collapse
If you removed the cover while the phone is powered on and put it back on, the tap to send will stop functioning. Only way to fix is to restart the phone.
If you received an update recently, you may need to factory reset the phone.
When you tap the phones together you may need to remove any cases you may have on them. Make sure you are touching the areas of the phone with the nfc antenna and not some other part.

Found the NFC area
figured out that not all phones have it on the same spot. The Lumina 920 has it in the middle near the black bar for the camera and mine Lumina 820 is at the top near the camera. My friend at work has a S3 going to find out where that is tomorrow.

No phone audio after rooting and new ROM

So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!

Edit, sounds like a hardware problem.
Have you tried to odin back to stock?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.

dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.

dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4

And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.

I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.

NFC?

Has anyone got NFC to work?
You have an option of choosing NFC secuity chip by choosing kne of the sim slots
But it does not read any nfc tags
M

I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.

dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
First i read "clothes" then "cases" ... :laugh:

lol, it just needed a little LUV baby!

have you found the solution? mine also not working and been trying to reset as well... this is a nightmare!

I had my NFC work as mobile payment. It works smoothly.

AL10 reflashed to L29
NFC doesnt work, i try to read card, on oher phone works
kangvip b170

On my AL10 NFC works. I transferred a video I had taken to a friends Samsung phone through NFC and it worked fine. I was running KangVIP B168 at the time but NFC should work on stock as well.

jbmc83 said:
it just needed a little LUV baby!
Click to expand...
Click to collapse
what you mean ? or just laughing ?
i dont try took case off yet (it is not metal) and very hard do it

Its a very strange but after i took of case ... it works. I put phone back in case and ... work again... In other apps works too... In same app that dont work earlier... Nothing other changes - only on off NFC button, try to send photo via NFC ... May be first launch was hard ? I start thinking thats needed to receive next level in Hogwarts
AL10 KangVIP 170 4/64

dpagoh said:
I'll admit I had a time trying to get nfc to work. Just sending a picture to my wife (who also has the Mate 8), was a task. I finally got it to work when we took our cases off.
Click to expand...
Click to collapse
I tried this with another Mate 8, made the 2 Mate 8 "kiss" close to where the camera is. The other phone recognized a tag which it could not read (My Mate 8). That was L29C185B560. I just updated mine to L29C636B563... I tried to NFC with a Windows Phone. No luck.
Pretty pissed now!

I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....

Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
childoftheworld said:
I also have a problem with NFC on my Mate 8.
Current firmware L29C636B563, previous firmware tested on L29C636B321 (and maybe L29C636B330)
First off, I was testing this with an LG Washer / Dryer with the "Tag On" logo. The LG Application could not detect the NFC so I will assume the problem is with the phone? Where exactly is this NFC strip they are talking about? No, even after updating to L29C636B563 Nougat OTA Push Update, my Mate 8 will still not work with LG Tag On.
So, I got curious as to whether or not NFC was working to begin with. I live in Canada. It is a very *backwards* country and NFC applications are few and not mainstream. Apple Pay just got introduced... and Android Pay is not even available for download... so... I never really had any use of NFC at all.
Anyway, I have another Mate 8 (not mine). It recently got an OTA push, L29C185B560. At that time, my Mate 8 was still at L29C636B321.
We tried Android Beam... I guess the instruction was to bring the phone close together (in this case - back to back) and both phones will detect each other... then you can tap content to the other phone...
Well... the L29C185B560 (let's call this C185 for short) made a sound and it picked up a tag, but that tag was empty... ?? My phone, the L29C636B321 (let's call this C636 for short) did not do anything at all... it just stared and stared in outerspace....
I also tried to "Share" and then pick "Huawei Beam" and of course, nothing happened between the 2 phones....
I was suddenly discouraged... eeeks! No NFC? I thought this phone was the *super* phone... time to shop for another phone.
Just last week, my C636 got its first OTA update... uhm... only after downloading Firmware Finder... maybe it did something to the settings to correct it...
So, it got updated to C636B330 first, then 2 days later, C636B563 arrived. Yay... Nougat! What bugs are there?
Just 2 days ago, I tried to Beam with a Samsung Galaxy S4. No luck there...
So just this weekend, I tried Beam again... first, just putting the phone together... no luck.
Then, I thought... uhm... so this time, I put the phones together, back to back and then picked a photo on my phone, "Share" and "Huawei Beam".... surprise, surprise... I heard a tone.... I angled my head and saw that my phone recognized a device and I tapped and I guess the other phone, the C185 didn't need to accept the beam, it was already downloading the photo...
So I tried the LG Tag On again... no luck...
Then. I got home and downloaded apps to read my chip enabled Canadian passport (inside and outside the covers) and my Paypass enabled credit card... No... none of the apps detected anything.
To my understanding NFC will "communicate" once detected. No further action. In the experience with Huawei Beam... it seems that an "action" has to be triggered for NFC to activate? Maybe I am wrong and have been wrong all this time?
So, does "reading" an NFC tag also require an action?
What else is broken?
I found some documentation on Huawei Mate 8 NFC. Maybe someone with more experience will be able to explain this occurrence way better? Give us more insight and get it working?
I just bought 10 NFC Tag stickers on eBay, let's see late on if the phone actually reads it....
Click to expand...
Click to collapse

Actually, never mind. It's dead again. I have no idea what I did to make it work for a short while,
but now it won't read my cards anymore. (sigh)
r0bgar said:
Thank you for this. I had sworn my NFC was dead, then I took the extra step you mentioned of trying to send a picture using Beam, and that appears to have woken the NFC chip up. I can't believe it's working fine now.
Cheers!
Click to expand...
Click to collapse

Repair
Same case but i have found the reason.
The nfc antenna is embedded in to top side of back cover.
It's connected not with flex cable, but with spring contacts
2 screws on bottom
open carefully (fingerprint scanner on cover is connected with flexible cable)
adjust spring contacts
clean contacts and contact pads on cover with alcohol or ...
that's all
now it works

Question Sim recognition issue

Owned the phone for about a month now. Phone was working perfectly fine for the majority of this time. I use 2 different sims and they were both working smoothly until recently.
A few days ago, I woke up and the phone wouldn't recognize the Sim cards anymore. I took out the Sim tray, cleaned the Sim cards and the tray as thoroughly as I could and they both started working again. A few days later, I restarted my phone and both of the Sims stopped working again.
This time nothing I would do would solve the matter, so for the next few days the phone wouldn't recognize either Sim. I have unlocked the bootloader and rooted, factory reset it and updated it none of which seems to solve the issue.
I use this phone for gaming so last night to my surprise one of the Sims started working (sim was in for a couple of days) and all connectivity was perfectly fine - I tried putting in my other Sim as well but again the phone wouldn't recognize them anymore. Tried putting in only one card on the Sim 1 slot but it made no difference. I don't understand what the issue could be.

Do you have a converted CN version or did you buy a global version? (just curious, as far as I know only CN -> WW versions faced this issue and I would like to know if this is a coincidence or an issue with these versions. But I could be wrong as well)
Nevertheless I would make use of warranty and send it back to Asus to get it repaired.

Yeah it's CN version > WW ROM. It's absurd how randomly it was hit with this issue. Again, the phone was reading a sim card perfectly fine out of the blue last night, then when I took out the Sim tray to insert another card, went back to square one and wouldn't recognize either.

I know.. If you had searched this forum or the rog reddit you would have noticed there are multiple topics like yours and all people explained the very same. Seems totally random.. sometimes it works, sometimes not. Unfortunately no one was ever able to post an accurate answer of why this is the case or how to fix it. At least there is none here, on reddit or the zentalk forums.
Since all device so far were CN -> WW version I don't know any successful case. Asus mostly rejects the support and redirects people to their sellers but those mostly refuse to do something. (they probably know that issue and it's cheaper to do nothing)
I wish you best of luck. Maybe you could try to contact Asus and report the outcome so we finally have a documented successful repair.
Edit: as said, that's only my knowledge, maybe there is a fix and someone found a way but they either didn't publish it or they posted it in a not so well known forum.

I wonder if the connections that touch the SIM are poorly designed. If it is such a widespread issue that randomly seems to come and go, it could be similar to the issue I had with the Kunai 3.
The pins on the side are designed to give a little when sliding the controller off and on the mount or charger. After moving them between the mount and charger twice, some pins fell off and others never popped back into place so they could make a connection. It turns out they never secured the pins well enough to handle it.

Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.

r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Good tip and glad it worked - this could help a few out there. Perhaps ASUS should have included some instructions explaining how to press/bend the device back in order when it happens ...

I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.

nickdagriff said:
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
Click to expand...
Click to collapse
Paying over $2,000 for a OnePlus 9 Pro seems like an expensive solution, but I am glad it worked out for you. Best of luck over there.

r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Works like a charm here! Congratz!

Omg worked here too, now I have a Poco F3 AND a revived ROG Phone 5...

.

You are the mvp. I love this phone and using it for almost a year. Suddenly sim no longer detected. I tried everything, unlocked bootloader, update firmware. Hour and hours of trying to revive it. I even called Asus and they said to call the Chinese warranty support. Then finally came across this thread. Pressed down hard on the lower end of the logo of the phone on its back. Restarted and now it's detecting the sim again. Thank you so much