I recently acquired an S6A and I seem to have trouble reading NFC tags (ISO 15693), when I put it to the back of the phone no matter what position, it cannot read the tag. However, it does sometimes read the tag if I keep tapping the tag on the back of the phone or slide it around. Does anybody else have experience or possible answers to why this is an issue? It's not a faulty phone as it is brand new and it happens to another GS6A as well. Galaxy S5 with an Otterbox, reads it instantly. The only difference I've noticed is the Android version on the phones are different.
S5: 5.0
S6A: 5.0.2
Any help would be greatly appreciated.
Try updating the software to 5.1.1, it may help. I haven't had issues reading NFC tags with a supcase case, but I don't really use NFC much either.
Related
Hi all,
I'm having problems with NFC in my HTC One and perhaps you can help me in order to solve them.
I mean, I bought NFC tags (Myfare Classic 1K), and initially I worked with them very well using NFC Task Launcher and Tasker. My issue is that I can read these tags sometimes... but sometimes no. It's frustating. Of course I have activated NFC option in my mobile and I put it close to the NFC tag using the area of the rear camera (where is located the antenna).
I try to connect with my new bluetooh headphones by NFC (Sony MDR-1RBT) and sometimes connect... sometimes no.
My HTC One is not rooted and bought free.
Any idea? Help please.
Thanks a lot!!
You probably have the same issue as I do. We've got faulty NFC chips. I'm sending mine in for warranty soon
I looked for information about NFC problems with HTC One but I didn't found nothing. Bad NFC Chips? Oh my God! Is this usual and reported?
I thought that perhaps it would be something related to software (i.e. some process running in background)... but if we are talking about a hardware issue I'm going to worry a lot.
Could we expect news with new release of android? What do you think?
Thaks a lot for your answer!
Best regards
Did you unlock your screen before using the tag? U must unlock first or the tag wont work
Yes, I try it after unlocked screen. I am not able to say when NFC fails or woks, but I try to read tags with unlocked screen.
Thanks
cta1234 said:
Yes, I try it after unlocked screen. I am not able to say when NFC fails or woks, but I try to read tags with unlocked screen.
Thanks
Click to expand...
Click to collapse
For me, mine I think is a little loose. I cna read NFC tags if I put it near my camera and press it really hard against the phone. That seems to push the NFC chip back into place and I hear the "Boop" when it detects the chip. A fully working will beep instantly upon contact.
ArmedandDangerous said:
For me, mine I think is a little loose. I cna read NFC tags if I put it near my camera and press it really hard against the phone. That seems to push the NFC chip back into place and I hear the "Boop" when it detects the chip. A fully working will beep instantly upon contact.
Click to expand...
Click to collapse
Obviously that would mean a hardware issue. In my case, doing always the same I get different results. I don't press the tag against the phone, and trying with the same tag I don't get the same result (sometimes reads the tag and sometimes not). It's crazy.
I haven't been able to get nfc to work either. I don't have any proper tags but I tried my MasterCard paypass that worked fine in the past. Can somebody with working NFC try to scan their MasterCard with paypass and let me know if it works?
Sent from my HTC One using Tapatalk 4 Beta
Having serious troubles with the GPS (I think ever since I upgraded to KitKat). I've tried a couple of ROMs and went back to the stock rooted one found here. I will get a fix at times but it will be lost within a minute or so and makes things very frustrating.
What's the best way to troubleshoot this? I've tried Chartcross GPS test, but it doesn't fix anything. Any help would be really appreciated.
Anybody?
scopefield said:
Having serious troubles with the GPS (I think ever since I upgraded to KitKat). I've tried a couple of ROMs and went back to the stock rooted one found here. I will get a fix at times but it will be lost within a minute or so and makes things very frustrating.
What's the best way to troubleshoot this? I've tried Chartcross GPS test, but it doesn't fix anything. Any help would be really appreciated.
Click to expand...
Click to collapse
If you google your question you will find loads of the same exact issue. I am also having the same exact issue, it only kind of works on stock rom with no root. But even then not for very long. Samsung decided to put garbage gps radio's in our phones so gps is pretty much non existent on the Note 3. I'm on my 4th phone from ATT. Not only does the GPS suck, the connection losses are pretty unbearable at times and have actually costed me customers. And to think I traded my S5 for this POS....really frustrating.
TLDR: Someone at Samsung needs punched in the face, twice.
Djspinister said:
If you google your question you will find loads of the same exact issue. I am also having the same exact issue, it only kind of works on stock rom with no root. But even then not for very long. Samsung decided to put garbage gps radio's in our phones so gps is pretty much non existent on the Note 3. I'm on my 4th phone from ATT. Not only does the GPS suck, the connection losses are pretty unbearable at times and have actually costed me customers. And to think I traded my S5 for this POS....really frustrating.
TLDR: Someone at Samsung needs punched in the face, twice.
Click to expand...
Click to collapse
Interesting. Mine was working perfectly prior to this whole kitkat ordeal. If I Odin back to stick and reflash to 4.4.2, do you think it will remedy the issue?
That's what i did because I need gps daily, though it still has major issues, I'm literally trying to sell it, my s5 never lost lock, even in my pocket.
Djspinister said:
That's what i did because I need gps daily, though it still has major issues, I'm literally trying to sell it, my s5 never lost lock, even in my pocket.
Click to expand...
Click to collapse
Do you think there's any use in ODIN'ng back to stock and then trying the custom 4.4.2 ROMs or is it not going to work?
Got my hands - ( don't ask how ) - on what appears to be a fake S5 Mini. Everything about it says Samsung, however neither Kies nor Odin detect the phone and the specs are all wrong anyway. Attached are screenshots from Device Info and CPU-Z.
The phone actually works OK, though it's not nearly as good as a real S5 Mini. But there are several glitches in the system: some apps or options just don't work, multi-language support is deficient, etc.
Nothing surprising from a clone.
Question: is there a ROM I can try to load to that device to see if I can make it work better? I was reading up on MoKee (because of the serrano3g identifier in the model name displayed by CPU-Z), would one of those ROMs work? The phone/wifi/BT portions all work correctly, so I guess there's no need to flash a new radio. Then again, I haven't flashed an Android device in a couple years, I'm basically like a newbie at that stuff, so if anyone can provide me with information on what/how to flash, I'd be grateful.
Thanks!
neat
Any pictures of the phone itself?
SOC seems to be a MediaTek MT6572 if correct see this thread http://forum.xda-developers.com/showthread.php?t=2687487
@protogenxl: Visually, it's an exact replica of a Samsung S5 Mini, with the brandname and all. So if you check out the Samsung site, you'll find plenty of pictures there!
As for the thread you mentioned, I had already read it but I'm still not sure whether that particular ROM can be installed on my device, even though it's a MT6572 ROM. And keep in mind that I am a newbie on flashing devices, so I'm not even sure where to start, what tools to use and what I should be looking for.
Thanks for the suggestion, though!
s5
I have a S5 Mini G8800-F, so the most interesting part would be the layout of the inside of the battery compartment, is the dead space for a second sim there etc....
I would say first order of business is getting a custom recovery installed and getting full backups of original OS in a safe place, after that should be relatively hard to completely brick it as I seriously doubt the clone company put any effort in to boot security
@protogenxl: I'll try and upload a picture of the battery compartment later today. Don't recall seeing a second SIM slot in there, though.
And I agree with you that the clone company didn't put any effort on securing the device. It was rooted when I got it, it's got one of those chinese bootloader menus (I found a video on Youtube explaining what each option means).
As for the custom recovery, should I just pick any of them or are there any recommendations specific to this chipset (or do I even have to care about the chipset at that stage)?
@protogenxl it has been to long since I messed with sisters then boyfriend's phone to get it usable but if memory serves I got a custom made version of CWM from the ChinaPhoneArenea forum.
@protogenxl: here's a youtube video I found which describes the exact device I have: https://www.youtube.com/watch?v=k_-OoKhkD_0
It shows it with its back cover open around the 2:30 mark.
I've done some searching about and can't find what I'm after so new thread time!
Basically I've replaced my battered S4A with a OnePlus One (love it!) and was wondering what I could do with my S4A as its in no state to sell.
It's been sitting on the side all week and still got power!!! but I guess that's due to the fact its not connected to Wifi, has no sim and isn't being used but did make me think that I could prob get some use out of it when doing some of the long cycling events I do.
So I was wondering what would be the best way of doing this? I would generally only want to run Endomondo on it and keep it running for as long as possible with GPS on, prob have a PAYG mobile broadband sim in there for the data that it requires.
Is there a really stripped down rom anyone would recommend? Things I should remove/disable/turn off? Is this just a stupid idea?
Cheers
After flashing Marshmallow factory image, I'm unable to connect to any BLE devices. I have both a Coin and a Stratos card and neither will sync now. The phone just doesn't seem to see them. Since neither one will work, I figured it was bluetooth and not the cards themselves.
Tried rolling back to the 5.1.1 radio, but that didn't help, so I'm guessing it's in the kernel.
Went back to my Nexus 5, which is still on 5.1.1, and both BLE cards synced with no problem.
Was worried it was a hardware problem with my phone, but a friend who also has a Nexus 6 on stock Marshmallow and a Coin card is having the same issue, so I don't think it's anything specific to me.
Has anyone else experienced this? Aware of any fixes/workarounds?
Here's the debug info from my phone. Does this look right?
Thanks
Update
I was able to connect to my Tile, another BLE device, with no problem, so it doesn't seem to be all BLE devices. Might be that one or more specific BLE device types have issues (there are different profiles per the Bluetooth spec). That might help narrow down the problem. Tile works, two different credit card thingies don't.
Hi mlevin,
I'm a Technical Specialist with Tile's Customer Care. Our app is actually having some issues regarding Marshmallow as well and we are looking into why some of our users are able to connect while others cannot.
Do you mind if I could reach out to you over phone or email to inquire further regarding your device/Tile usage?
Please feel free to email me as well at: [email protected]
Thank you!