Related
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
I pretty much love this phone. It would be my ideal device if it had double-tap-to-wake. As it is, I could almost learn to live with using the fingerprint scanner (which I avoid using on all of my other phones) to unlock, but I finally encountered a deal breaker.
I have had all kinds of bluetooth issues. I have a lot of connected devices and I've been encountering the following:
Gear S3 constantly disconnects (even when it's really close to the phone)
Fitbit will not sync
Car Stereo Bluetooth profile deleted itself
AirPods break up, have static, or completely cut out
Here's the thing. I went back to my V20 and I don't have any of these issues. The Fitbit always syncs, the AirPods work flawlessly, the Gear S3 NEVER disconnects, and my car stereo has never disconnected. I have to believe it's a bluetooth stack issue. Perhaps the proprietary processor is to blame. But with all of the bluetooth devices I use on a daily basis, I can't live with this.
I really want to keep the phone, but I think I'm going to have to return it. That sucks because there's nothing else really like it on the market for me. But after all of the testing I've done, I can't draw any other conclusion. Maybe a software update might fix it in the future, but I can't take that chance.
I'm sure some of you will chime in and say "I'm not having any of these issues". That's great. I'm fairly certain you don't have the exact same devices/combination I've listed here. The fact is, my currently daily setup does not mesh with this phone. I still have my Mate 8, but I haven't tested this combination of devices with it yet.
I also have a big issue with this phone's Bluetooth. I can't pair it with a 2014 Pajero. Any other phone works perfect when paired with the car but this one cannot even pair. I always get "pairing failed".
I tried every oprtion and pairing application and still no success.
I know mate 9 has bluetooth 4.2 but it should be backward compatible.
Anyone has a solution or similar issue?
I wonder what firmware version your mate is on.
I'm running MHA-L29C432B138 and I have no problems with my Gear S3, nor with my Mazda bluetooth hookup.
Yeap, latest B138 version.
Gear S3 is fine. Only issue is the car connection
B138 here.
Won't connect to my 451 Bosch Highline car radio (they can't even see each other).
Connects fine to my laptops (Win & MacOS), BT speakers and Xiaomi Roidmi.
Sent from my MHA-L29 using XDA Labs
duraaraa said:
I wonder what firmware version your mate is on.
I'm running MHA-L29C432B138 and I have no problems with my Gear S3, nor with my Mazda bluetooth hookup.
Click to expand...
Click to collapse
I am on MHA-L29C567B138
I have the U.S. unlocked model. So, unless there's something specific about the firmware on that model, I don't know what to tell you. I have tested this repeatedly with all of my Bluetooth devices. Nothing works as it should, especially compared to my other phones. It would be interesting to see if I have the same issues on the Europe firmware, but I'm not flashing it to find out.
This bluetooth seems to be issue with this phone, does anyone know if this is something huewei is working on to fix or its an android issue ?
I hate to be the guy that says "mine works blah blah blah" but I've got multiple devices connected through Bluetooth and have yet to have an issue on any of them. 2 Ford vehicles running Android auto, 3 Bluetooth speakers and a set of Bluetooth headphones.
With that said, I wonder if your actual device is faulty. Has anyone with the issues done a factory reset? If so I'd be contacting Huawei support.
Sent from my MHA-L29 using Tapatalk
I have same issue as describe. My tought is mate 9 do not accept Bluetooth multipoint connection... 2 devices with same profil cannot be connected in same time
Envoyé de mon MHA-L29 en utilisant Tapatalk
I am wondering if the manufacturer is aware of the issue or not but to me it seems more of a Android nogut issue than anything else
I have the same issue. The Mate 9 takes about 3 minutes to pair with my car where my LGV10 automatically did it within seconds. It also does not seem capable of handling being paired with multiple Bluetooth devices at the same time. It has to be disconnected from one and wait to pair with the next one. For cars, I have tried it with both a Tesla and a Jeep GC and the I have the same problem.
greyhulk said:
I pretty much love this phone. It would be my ideal device if it had double-tap-to-wake. As it is, I could almost learn to live with using the fingerprint scanner (which I avoid using on all of my other phones) to unlock, but I finally encountered a deal breaker.
I have had all kinds of bluetooth issues. I have a lot of connected devices and I've been encountering the following:
Gear S3 constantly disconnects (even when it's really close to the phone)
Fitbit will not sync
Car Stereo Bluetooth profile deleted itself
AirPods break up, have static, or completely cut out
Here's the thing. I went back to my V20 and I don't have any of these issues. The Fitbit always syncs, the AirPods work flawlessly, the Gear S3 NEVER disconnects, and my car stereo has never disconnected. I have to believe it's a bluetooth stack issue. Perhaps the proprietary processor is to blame. But with all of the bluetooth devices I use on a daily basis, I can't live with this.
I really want to keep the phone, but I think I'm going to have to return it. That sucks because there's nothing else really like it on the market for me. But after all of the testing I've done, I can't draw any other conclusion. Maybe a software update might fix it in the future, but I can't take that chance.
I'm sure some of you will chime in and say "I'm not having any of these issues". That's great. I'm fairly certain you don't have the exact same devices/combination I've listed here. The fact is, my currently daily setup does not mesh with this phone. I still have my Mate 8, but I haven't tested this combination of devices with it yet.
Click to expand...
Click to collapse
It's interesting and frustrating how different people have different experiences.
As you'll see from my sig area, I am on US version, with 183 firmware. Interesting too, I had first tried a V20, and left it because of BT issues. As you are probably expecting to hear given my intro statement, I am not having BT issues. But, I am on different phone and firmware from most posts here.
I've only had my phone a couple weeks. When I received it it was on 138, and the GPS didn't work at all. Was about to box it back up and send back, but then checked, and had the update. After update, it's been great for me so far.
I'm not sure how different the 138 is from my US phone and yours...but a common thread for problems seems to be (based on this thread) is 138.
As the title states I can't get my fitbit charge 2 to come up on Bluetooth and the fitbit app won't recognize it either. The fitbit is performing perfectly and synced with my tablet due to the honor 6x not pairing with. Anyone else having this issue? Thanks in advance for your help!
This makes no sense to me, but my wife says her fitbit charge 2 didn't want to pair (BLN-L24) until she turned location on.
Thanks for the quick reply, I definitely had location on. I requested a replacement from Amazon before I give up on it.
johnzenobia said:
Thanks for the quick reply, I definitely had location on. I requested a replacement from Amazon before I give up on it.
Click to expand...
Click to collapse
My fitbit alta pairs normally with honor 6x, its true you need location on, also on my older galaxy s6 the location had to be on
That's good to read. Hoping I just have a bad 6x. Otherwise I think the phone is fantastic for the money spent.
I've been having the same issues. Syncs perfectly with my old one plus one, macbook air. But ever since I got my 6x even when I turn everything on (wifi data Bluetooth location) it simply can't find my charge 2.
Called huawei and there response was they knew it won't work and couldn't give any idea when and if it would work. I returned the phone for a refund. I find it very hard to believe that it's just a software issue. It's a shame because the phone was nice.
That's odd...my wife's been using hers for almost 2 weeks now with no problems with
Honor 6X BLN-L24C567B110
Fitbit Charge 2 FB407SBKS
Too bad they didn't say what the exact issue is...kind of curious.
johnzenobia said:
Called huawei and there response was they knew it won't work and couldn't give any idea when and if it would work. I returned the phone for a refund. I find it very hard to believe that it's just a software issue. It's a shame because the phone was nice.
Click to expand...
Click to collapse
Sad you had to return even though you liked the phone and more important, no solution was given... thats sad
Hi everyone, thanks in advance for your help. I've searched and searched on this site and all over the internet to no avail. If you can help me, I'd be most appreciative!
First off, I have basic knowledge of this stuff with the help of tutorials, but am not even close to being fluent in it. That said, I had my gear s2 paired with my old Note 4 a few years ago. Last year, I bought a Pixel on Black Friday and found a way to root the watch and put Android Wear on it so that it would work with the Pixel. It worked fine for over a year. Recently, it was giving me problems, every few seconds crashing saying Google Services were not working. I factory reset the watch and it is now fresh with Android Wear on it. However, it will not find my phone and vice versa to connect them.
I told it to "forget" my phone and repair, even uninstalled Android Wear on my phone and reinstalled it, and nothing. The BT function of both my phone and watch work fine, as they are able to find other BT devices near them, just not each other.
Anybody have any ideas? It's driving me crazy. Thanks!
m0ssman said:
Hi everyone, thanks in advance for your help. I've searched and searched on this site and all over the internet to no avail. If you can help me, I'd be most appreciative!
First off, I have basic knowledge of this stuff with the help of tutorials, but am not even close to being fluent in it. That said, I had my gear s2 paired with my old Note 4 a few years ago. Last year, I bought a Pixel on Black Friday and found a way to root the watch and put Android Wear on it so that it would work with the Pixel. It worked fine for over a year. Recently, it was giving me problems, every few seconds crashing saying Google Services were not working. I factory reset the watch and it is now fresh with Android Wear on it. However, it will not find my phone and vice versa to connect them.
I told it to "forget" my phone and repair, even uninstalled Android Wear on my phone and reinstalled it, and nothing. The BT function of both my phone and watch work fine, as they are able to find other BT devices near them, just not each other.
Anybody have any ideas? It's driving me crazy. Thanks!
Click to expand...
Click to collapse
How did you manage to get Android Wear on this watch? Are we talking about the regular gear S2 or the classic?
I have a HW2 Sport, all of a sudden yesterday morning the device decided to stop tracking anything - i noticed after going for a 10k run and it told me i had not taken a single step! I have tried clearing the cache and then re-installing the firmware with no joy. It really does look like the device is dead as far as fitness goes... anyone else had this issue??? Its over a year old but think i may struggle to find the receipt... :crying::crying:
Have even tried the wrist gestures too - they dont do anything anymore...