Related
Hi Guys.
My friend was trying to tell me how awesome NFC is, but no matter what we tried we cannot get it to work.
Its fine between his Nexus and S3, but neither will connect with my HOX.
I am running Leedroid, though im not sure that will matter.
I will try with my wifes HOX later, but has anyone else encountered trouble and how did you get it working?
lets get the stupid questions out of the way first...
You turned it on in settings >more >NFC?
you got android beam turned on just underneath that?
Yep, all of these things ticked.
And you are right, stupid questions out of the way first!
I tried with out my phone case and his phone case just to be sure. I tried all combinations of holding together (front to front, back to back, front to back etc) but still nothing.
Any other ideas would be great
I did succesfull with two HOX. And it worked fine to "beam" a contact (back on back) wich is opened. I'm also using NFC tags since weeks.
I think the problem are the two different vendors of the phones. Probably S Beam is not comptabile to Android Beam of HTC
S Beam is just for Galaxy S III. It should still support Android Beam. Yay for more proprietary standards.
Try it with another phone to see if its the HOX or SIII
My NFC worked fine for sharing a web link...
Thanks for the advice.
Tried with the wifes HOX, worked first time.
Guess it is a bit of a hiccup between vendors, might be something that gets patched in the future
ME TOO - But different issue?
I'm seeing similar...
Having now found out that Android Beam cannot be used for transfer of photos and video files, I discovered "Blue NFC"
The principle behind this app is simple...
When tapping your two devices together, the NFC chip, which is not suited for heavy file transfer, INSTEAD does the back-end work at automating a BLUETOOTH pairing between both devices, without any security questions, user action etc. It then uses BLUETOOTH to send the file, and then closes the connection.
But it seems there is some strange issue with the HTC One X...
As trying this method, bumping the devices (A Galaxy S3 and an HTC One X both with Blue NFC installed), causes the Galaxy S3 (as the host device) to allow me to tap to send the file to the One X...
Blue NFC sets up the Bluetooth connection automatically, and the file starts sending.
BUT... when it reaches 99%, on the HTC one X, I receive a "File Transfer/Could not be received" error, EVERY TIME.
Alas, I think this must have something to do with the new BT 4.0 spec on the Galaxy S3, and the HTC One X not supporting this, and I think this for the following reason...
Setting aside any fancy NFC wizardry, when trying a normal, traditional, Bluetooth image transfer the "old fashioned normal" way from a SGS3 to an HOX, the file transfers up to 99%, and fails every time then too.
Yet file sending FROM the HTC One X, back TO the SGS3, works fine.
The SGS3 can receive files fine. The HOX however cannot.
Has anyone else been able to send files either via:
1. ANDROID/S-Beam from SGS3 to HTC One X
2. Blue NFC from SGS3 to HOX
3. Traditional standard BT File Transfer from SGS3 to HOX
-
It's totally doing my head in!
Perhaps you can try File Expert. I don't know how it is establishing the transfer.
Early I read that the concepts planned to use WiFi direct to transfer data
Shadamehr said:
I'm seeing similar...
Alas, I think this must have something to do with the new BT 4.0 spec on the Galaxy S3, and the HTC One X not supporting this, and I think this for the following reason...
Click to expand...
Click to collapse
The HTC One X is Bluetooth 4.0 so id doubt its that.
My NFC is not working at all. Can anybody help. It has just stopped, it worked on stock 1.28, since ive ran slim, arhd, + leedroid, now im on stock 1.29.401.11 and it is not working at all. can anybody please help
thanks
drew071
Another bit of info is that in alogcat, the software is switching NFC on and off with the screen state.
Is there a way the NFC hardware could have been damaged?
drew071
drew071 said:
My NFC is not working at all. Can anybody help. It has just stopped, it worked on stock 1.28, since ive ran slim, arhd, + leedroid, now im on stock 1.29.401.11 and it is not working at all. can anybody please help
thanks
drew071
Click to expand...
Click to collapse
I figured mine out. The NFC chip is in the stock battery, so my non-OEM extended "2850 mAh" (they're pretty close to stock time-wise, though) effectively removes the NFC hardware from the phone.
So, I'm going to try putting some packing foam around the stock S3 battery in my Note and see if I can rig up or find the software to support it.
My wife got anS3 the other day, and every time we'e tried it with my HOX, I can't beam a picture. I've been able to transfer an app (link to the play store)
When I try to transfer a picture from the S3 to my HOX, I get the message,
text/DirectShareGallery
rushwal said:
My wife got anS3 the other day, and every time we'e tried it with my HOX, I can't beam a picture. I've been able to transfer an app (link to the play store)
When I try to transfer a picture from the S3 to my HOX, I get the message,
text/DirectShareGallery
Click to expand...
Click to collapse
As mentioned before the phones are not compatible. Perhaps it works if you use Roms like AOSP
ive just tried this with a galaxy s3 user and my CM10 HOX. worked well with youtube vids, pictures and contacts. The bumping phones process is a bit weird, to be honest
Glad to hear that this works with CM10, really disappointed that it doesn't work with Sense. Hopefully they fixed it in the Jellybean update?
Sent from my HTC One X using Tapatalk 2
Not working
Just tested with a s3 and a htc one x, both jelly bean and it doesn't work
Has anyone tried the S beam on this? I may be handing down my S III to someone where using this might be worthwhile.
I did the settings on both phone to enable it, but have not been able to get them linked to transfer files. I have tried going both ways and get a popup of touch to transfer but it disappears fast and nothing is transferred. i had read that it is supposed to first ask permission to connect, but this does not pop up on either device.
I am wondering if in typical Samsung fashion, have they made the two devices S beams incompatible (like they did with Android beam)?
gaww said:
Has anyone tried the S beam on this? I may be handing down my S III to someone where using this might be worthwhile.
I did the settings on both phone to enable it, but have not been able to get them linked to transfer files. I have tried going both ways and get a popup of touch to transfer but it disappears fast and nothing is transferred. i had read that it is supposed to first ask permission to connect, but this does not pop up on either device.
I am wondering if in typical Samsung fashion, have they made the two devices S beams incompatible (like they did with Android beam)?
Click to expand...
Click to collapse
to use S-beam, both devices must have S-beam and wifi enabled, which means they both must be samsung devices (S3, note II for example). you then have to go to an app that supports sharing via NFC such as a picture from your gallery. after you touch phones you have to hold it there then tap and wait until it prompts you to separate the phone; i'm guessing this is the step that's being done wrong. if you separate too early the connection will never be established.
Jinra321 said:
to use S-beam, both devices must have S-beam and wifi enabled, which means they both must be samsung devices (S3, note II for example). you then have to go to an app that supports sharing via NFC such as a picture from your gallery. after you touch phones you have to hold it there then tap and wait until it prompts you to separate the phone; i'm guessing this is the step that's being done wrong. if you separate too early the connection will never be established.
Click to expand...
Click to collapse
I have encountered the prompt to separate a few times, and I do so slowly (also been using stock gallery pictures) and still no transfer.
This took me a few rries with my new Note2's. Touch the backs, touch the image to transfer, and separate when it says to. Works pretty decent. Even cooler is photoshare. The wife and I went on a safari today and took about a hundred photos between the two of us and we both have all of them on both our devices. Badass Samsung!
Sent from my SGH-T889 using Tapatalk 2
farfromovin said:
This took me a few rries with my new Note2's. Touch the backs, touch the image to transfer, and separate when it says to. Works pretty decent. Even cooler is photoshare. The wife and I went on a safari today and took about a hundred photos between the two of us and we both have all of them on both our devices. Badass Samsung!
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
What I am asking is does it work with other devices and not just two of the same? I would like to be able to do what you did with a Note 2 and Galaxy S III
gaww said:
What I am asking is does it work with other devices and not just two of the same? I would like to be able to do what you did with a Note 2 and Galaxy S III
Click to expand...
Click to collapse
My roommate has an S III and I have a note II. We are able to use S beam, but like I said, we needed to hold the phones there, tap, and wait for a prompt to say it's okay to separate the phones. Initially, we failed to beam because we were separating too early. Maybe you should also make sure you both have nfc/sbeam turned on as well as wifi?
Tried the Nfc with a Motorola razor maxx hd and it opens the play store on his phone every time I try to send a file... Why??
Sent from my T-mobile Galaxy Note II
ezsoulja said:
Tried the Nfc with a Motorola razor maxx hd and it opens the play store on his phone every time I try to send a file... Why??
Sent from my T-mobile Galaxy Note II
Click to expand...
Click to collapse
sounds like you're trying to send something from an app that he doesn't have. if i try to send my roommate a note from s-note, it will open the play store for him as it doesn't know how to negotiate the file. also note that i dont think you can send large files via nfc, i couldn't even send a picture.
Nfc transfer works with Nexus 7, fyi
Tmobile SGH-T889 using xda premium.
I do not have a SIM in my S III (It is in my note 2 now), but NFC and wifi transfer should not be affected.
I have carefully done all the settings on both devices and the few times I have gotten the "touch the image to transfer", I separated slowly when it said to and have yet to get a transfer. I was only trying to transfer one photo from the gallery. Tried it both ways.
Update. I realized I had the Perseus kernel installed so I flashed over it and now S beam works.
Update 2 - working fine with S 3 on a leaked LI8 ROM. Official JB S 3 update came out, and it is broken at S 3 end now - WTF.
Question - there is no S beam apk, so which apk is it included in?
Hello NFC experts.
I received my Nexus 10 yesterday and I love it. I also have a Galaxy S3 running Stock Jellybean and would like to be able to beam photos or music from it to the Nexus 10. Although I can send webpages and YouTube links via NFC, I cannot send pictures.
Whenever I try, the connection is made but the Nexus opens the Play Store instead of receiving the file.
I have tried it with S-Beam off but the S3 insists on it being on.
The Nexus will however send photos to the S3.
I have a similar question in the Nexus 10 forum at the moment but thought that this may be the best place to ask.
Any ideas?
Sent from my GT-I9300 using xda app-developers app
That's because S Beam and AOSP use different methods of transferring the data. AOSP uses Bluetooth, S Beam uses Wi-Fi Direct. Small files work because they use NFC to transfer. (NFC is slow, that's why it's not used for larger files.)
Sent from my Galaxy Nexus using xda premium
I had the same issue as him. I just want to know if it is possible to get an app for the s3 or note 2 that will send it to the nexus using the AOSP standard?
same problem... no ideas!?
Question
what is NFC and what is its role in Mobile Phones? anyone help!
kingayazkhan said:
what is NFC and what is its role in Mobile Phones? anyone help!
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Near_field_communication
It allows for very easy handshakes for transferring files. (Just tap two compatible devices together and the download will start)
Sent from my Galaxy Nexus using xda premium
Android Beam is one of the standard features of Android platform and implemented within Android Application Framework.
On the other hand, S-Beam is Samsung's proprietary and that works only between two Galaxy S3s.
When you try to send pictures from the Galaxy S3 to the Nexus 10, Galaxy S3 sends a handover request message for
establishing a Wi-Fi Direct link to the Nexus 10, as in S-Beam manner. However the Nexus 10 doesn't support S-Beam
and that attempt fails.
When you try to send pictures from the Nexus 10 to the Galaxy S3, Nexus 10 sends a handover request message for
establishing a Bluetooth link to the Galaxy S3, as in Android Beam manner. Because Android Beam is a standard
feature of Jelly Bean, Galaxy S3 accepts the request and return a handover select message to the Nexus 10. Then a
Bluetooth OPP link is established between those two devices and the pictures are transferred.
Hope this could help you.
chugglet said:
Hello NFC experts.
I received my Nexus 10 yesterday and I love it. I also have a Galaxy S3 running Stock Jellybean and would like to be able to beam photos or music from it to the Nexus 10. Although I can send webpages and YouTube links via NFC, I cannot send pictures.
Whenever I try, the connection is made but the Nexus opens the Play Store instead of receiving the file.
I have tried it with S-Beam off but the S3 insists on it being on.
The Nexus will however send photos to the S3.
I have a similar question in the Nexus 10 forum at the moment but thought that this may be the best place to ask.
Any ideas?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
k.h. said:
Android Beam is one of the standard features of Android platform and implemented within Android Application Framework. On the other hand, S-Beam is Samsung's proprietary and that works only between two Galaxy S3s. .....
Click to expand...
Click to collapse
Yep, good description!
From my point of view, this is a good example why NFC is struggling for years (believe it, or not, the first nfc phone , Nokia 6131 NFC ; was introduced 2007 ...) ...Let me explain my point of view:
- First, some kudos to Samsung for implementing the WiFi transfer via S-Beam ! Not sure, why this is not implemented within the android standard, but i think it´s only a matter of time...
- Second, some BOO to Samsung for messing with the standard and introducing a not compatible function (btw.. There is a connection handover specification defined by the NFC Forum... and Samsung implemented two major flaws):
1.) Why not let the devices handle out the alternate carriers (WiFi/ Bluetooth), e.g. if WiFi is available ,use Wifi (S-Beam), else use Bluetooth (Android-Beam) ...No, S-Beam insists on WiFi ....
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Bottom line: Hello samsung, fixing one of the mistakes above, will do the trick
Edit: Samsung fixed 2.) with new GS3 firmware (4.1.2) ...
ascsa said:
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Click to expand...
Click to collapse
That's because pure NFC file transfert is very slow, as mentionned earlier in the thread. You can send/receive small files of few bites but not more. And I agree with you, S-Beam system with direct wifi transfert for all compatible smartphones should be the next feature of android
Okay, so my question is this. I have the Nexus 10 and the Galaxy Nexus, but they will not transfer or connect correctly. Definitely get an acknowledgement sound, but nothing further. What else is required on my part? Also, what are some of the ways people are using NFC tags?
Sent from my Nexus 10 using Tapatalk 2
frankynov said:
That's because pure NFC file transfert is very slow, as mentionned earlier in the thread. You can send/receive small files of few bites but not more. And I agree with you, S-Beam system with direct wifi transfert for all compatible smartphones should be the next feature of android
Click to expand...
Click to collapse
Sorry, not correct!
(standard) Android -Beam uses Bluetooth to transfer pictures ... works without any problems between a nexus 7 and a nexus 10 ...
Speed_419 said:
Okay, so my question is this. I have the Nexus 10 and the Galaxy Nexus, but they will not transfer or connect correctly. Definitely get an acknowledgement sound, but nothing further. What else is required on my part? Also, what are some of the ways people are using NFC tags?
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, my experience is, that most users (including myself ) struggling with the handling of the beam feature, especially if you try it alone....I would love to have a third hand for this ....
Let´s try to beam a picture step by step:
- First enable android beam (-->settings) on both devices ...
- Be aware, that standard nfc will only work when device is not locked and screen is on(--> e.g. homescreen on both devices!)
- open the galerie app on the sending device --> then open the picture ...
- tap the devices together with their "nfc sweet spot" ...--> you should hear the nfc sound AND the picture should shrink and a message "touch to beam" should appear
- Touch the shrinked picture without losing the nfc connection (thats where the third hand would be nice ) and voila the beam should start ....
Earlier tonight a friend had a nexus 7 and I had my nexus 10, we tried to get NFC working for like a half hour, with no success. We both had NFC and Beam on, we were both connected to WiFi, and we eve tried with Bluetooth being turned on (but not paired).
Is there something we were doing wrong?
Is this the incompatibility that Samsung has?
I'm not on CM10, but I am rooted and on the latest update (ends with D).
Is your nexus 7 running the latest version 4.2? I have both devices as well and they are both up to date, nexus 7 is on a custom rom, but nfc works fine between both devices when say loading YouTube video on nexus 7, then holding holding both devices until connection is made then holding down the shrunken video then it opens youtube on nexus 10 and goes to the video. The issue with Samsung is for who knows what reason, when i first got it stock with ics it only had sbeam. As opposed to when I upgraded to JB, they added android beam as well. That way you could connect to non Samsung devices over nfc. Since as someone else said sbeam uses wifi direct to make the connection resulting in a much faster connection. While beam is over bluetooth. I ve heard rumors of the upcoming updates will more than likely contain the wifi direct version of NFC as its much faster and transferring files, etc is too slow as is. I dont know why its not in there already since 4.2 waa supposed to be the Android version that supports miracast, which relies on wifi direct as well. Although Samsung augmented there JB 4.1 with the update for allshare fw update that allows miracast transfer using there dongle.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
ascsa said:
Yep, good description!
From my point of view, this is a good example why NFC is struggling for years (believe it, or not, the first nfc phone , Nokia 6131 NFC ; was introduced 2007 ...) ...Let me explain my point of view:
- First, some kudos to Samsung for implementing the WiFi transfer via S-Beam ! Not sure, why this is not implemented within the android standard, but i think it´s only a matter of time...
- Second, some BOO to Samsung for messing with the standard and introducing a not compatible function (btw.. There is a connection handover specification defined by the NFC Forum... and Samsung implemented two major flaws):
1.) Why not let the devices handle out the alternate carriers (WiFi/ Bluetooth), e.g. if WiFi is available ,use Wifi (S-Beam), else use Bluetooth (Android-Beam) ...No, S-Beam insists on WiFi ....
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Bottom line: Hello samsung, fixing one of the mistakes above, will do the trick
Click to expand...
Click to collapse
Received the 4.1.2 Update for my Samsung GS3 yesterday ... and guess what... Samsung fixed it )) ....They fixed number 2 (above), so S-Beam is not longer mandatory for sending pictures from the galery (just disable S-Beam) ....and android beam works as expected ... beaming pictures from the galery between a GS3 and a nexus 10 over bluetooth works now without problems
there is an app on the app store called wifi direct, from the description and the install it appears to be able to handle nfc initiated wifi direct transfers? i only have my nexus phone so i dont really have another thing to test it against just yet, but it might be the missing link with the beam stuff....
Hi Everyone.
Keen to get a cellular version of the galaxy watch (keener for a cellular version of the watch active but apparently its not coming our with a cellular version) but I have a huawei mate 9,
Can anyone tell me...
Will it work with a mate 9?
If not what functions are not active?
Does it matter if the watch is a cellular version? does it being cellular mean it can connect directly to apps and access required information.
Apologies if this has been asked before, I have gone looking but cant find any reference ..
Thanks Tony
I have a Samsung phone so I'm not certain that this is 100% the truth, just what I have read from people in here or over the galaxy watch subreddit.
It should not matter what android phone is most things will work fine just like with a Samsung phone, I've only seen people talking about some compatibility issues with iPhone.
Now about the esim..
What I've read about it is that it works as if you have the phone with Bluetooth with you, you will get all the notifications but you don't have apps on the watch.
All of the notifications will be just mirrored from the phone notifications and the apps you can get on the watch right now are really limited.
Well you have Spotify and Samsung mail but for the others you can only do the same as on the phone notifications, read most of them, answer some things but it's going to be limited, on messaging apps you can see the last 10 but once you close the notification you have to wait until you get another etc.
If you often go out to do things like some kind of sport that doesn't allow you to bring the phone or you think you could use it while doing other things, it can be worth it but it's not going to work fully as a secondary smartphone, just as a app notification center + phone.
I'm using a cellular Galaxy Watch with a Huawei P20 Pro and it works perfectly.
Cheers,
Tom.
In all honesty, since they now allow you to download/install the Galaxy Weable app on pretty much any device now, you can use it with whatever device the app will work with.
I mean, there are always limitations and whatnot, but rule of thumb, yeah, it's not locked to Samsung phones only. Hell, they even let i(cough)Phone users use it! (unlike that fruity company with their watches).
Thanks!
Does the Samsung Galaxy Cellular smart watch work with huawei pro20?
Um said:
Does the Samsung Galaxy Cellular smart watch work with huawei pro20?
Click to expand...
Click to collapse
You may have to activate LTE on a samsung phone. S7 or newer.
I'm on a p30 pro. Panicked when I tried to activate LTE through the wearable app and it wouldn't work. Borrowed an S10, put in sim card and activated. All good now.
Works a treat with my OnePlus 8 Pro! Cheers
I'm using Galaxy Watch Active 1 and Honor 9 lite, all function on watch work well ( pairing, get whatsapp,email, SMS notification, purchasing app). And I can access galaxy store without phone (using Wifi network).
tomc99 said:
I'm using a cellular Galaxy Watch with a Huawei P20 Pro and it works perfectly.
Cheers,
Tom.
Click to expand...
Click to collapse
I have Galaxy Watch R800 (BT, WiFi only) and Huawei P20 PRO and I cannot make a Galaxy Store on the watch to work. Any idea?
Everyone I try to run Galaxy Store on my GW i get error. I can run galaxy store on my phone and it works. I have the same problem with Bixby. Any other app works great.
I get this error even on WiFi connection.
My advice for those who want to perfectly match the smartphone with the watch: If you own a huawei smartphone then buy a huawei watch and if you own a samsung smartphone then buy a samsung watch! Otherwise, after few updates of one or another nobody guarrantee if pair samsung/huawei/xiaomi or whatever will still work without bugs...
Hi I currently have the note 9 but I'm looking to upgrade to the xperia 1 will my galaxy watch fully work on the xperia 1 like it does on my note 9 or will I loose some functions
Thanks
Compatibility on non samsung android smartphones is 90%.
Some apps are samsung restricted (like Komoot) and you will lose the ability to use email and sms app on watch. You can still reply to email and sms but only as a notification. Apart from this is perfect.
Tested firsthand
You will lose many features if you do not have a Samsung phone connected to the watch. I'm currently using the Galaxy watch with an lgv30 and my experience is terrible. You're way better off grabbing a watch with wear OS if you don't have a Samsung phone. I would trade my $400 Galaxy watch for $100 wear OS watch in a second. You will be unable to view your conversations in the messaging app, many of the Samsung Health features do not work correctly, your battery will not last as long as it does with Samsung phone users. I've also had issues with things syncing up correctly. . If you look here https://www.samsung.com/global/galaxy/galaxy-watch/device-compatibility/ at the bottom of their page it says all the limitations for iOS. They don't clearly state on this page but many of those limitations will apply to you as well if you're using the Galaxy without a Samsung phone
Sent from my LG-H932 using Tapatalk
Thanks guys think I'm going to return the xperia 1 and stick with my note 9 then until note 10 come out
Galaxy wearable doesnt work with me any other app can connect my watch and manage it ?
Galaxy watch (6350)
Any custom wearable manager ?