Tried using NFC for first time ever between my GNex and Nexus 7 and nothing would transmit. I originally had the VZW Extended battery in, but put in the original to see if that was the cause. Nothing, still no transmission. Is is possible the NFC is defective? Seems odd since it's in the battery.
I am running franco kernel 220 384mhz and Vicious Jelly Bean v1.1 for what it's worth. I really wanna see NFC in action, is it the kernel?
Is NFC enabled on both devices?
Yeah, Android Beam as well
Sent from my Galaxy Nexus using xda app-developers app
For me beaming Images from Galaxy Nexus to Nexus S works, but not the other way round.
And beaming videos didn't work at all, i believe.
This is with stock Jelly Bean 4.1.1 on each device. I don't think this is a hardware problem.
Yeah it's hard for me to tell if it's possibly always been defective since I've literally never tried using NFC until I tried messing with it with my Nexus 7 out of boredom, so not sure if it was cool on 4.0 and 4.1 is the problem or what. :\
Beaming "big" files (other than YT links or so) requires Bluetooth to be enabled on both devices. NFC makes the pairing process easy but the transfer itself is handled by Bluetooth...
It's quite unlikely that it is broken in both batteries. Have you tried a different ROM or wiping? If it's still happening, it's more likely that it is broken on the Nexus 7 than the Gnex
Is there a way to test the Nexus 7 nfc?
Sent from my Galaxy Nexus using xda app-developers app
Looks like device placement was the problem, it's working now.
http://forum.xda-developers.com/showthread.php?t=1779674&highlight=nfc
Lol
EvoRocker said:
Seems odd since it's in the battery.
Click to expand...
Click to collapse
The NFC isn't in the battery, only the antenna... the chip is internal
Google screwed android beam, i was super excited to learn android beam had been updated to share pictures and even videos on jellybean, but guess what? android beam just activates bluetooth! and you send pictures and videos using bluetooth they take ages to transfer , how come the galaxy s iii use wifidirect ( with their marketing name "s-beam" ) ? so silly
Isnt there a way to force android beam to use wifi direct instead of bluetooth?
WiFi direct is in there along with Android beam
Samsungs S3 brings all three
WiFi direct
Android beam
S Beam
-Google
My friend has a galaxy s3 and i have the gnex and we shared pics no problem, especially speed..
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
DerAmi said:
My friend has a galaxy s3 and i have the gnex and we shared pics no problem, especially speed..
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is your friend's S3 running jelly bean?? I thought picture sharing was only available with Jelly Bean if you're using GNex's beam feature. I understand the S3 has S Beam but that won't work if you try to pair with a GNex, right?
Yep he is. You guys really should do research before creating forum topics.. Android beam uses NFC not Bluetooth. S-beam while yes using WiFi direct, the s3 also has the ability to share content through NFC.
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Where is the Wifi Direct setting in JB? I don't see it.
Nvm...found it in the Wifi settings.
I have to agree Android Beam is stupid slow. It took almost a full minute to transfer a 2mb image from one GNex to another.
Sent from my Galaxy Nexus using Tapatalk 2
Chad_Petree said:
Google screwed android beam, i was super excited to learn android beam had been updated to share pictures and even videos on jellybean, but guess what? android beam just activates bluetooth! and you send pictures and videos using bluetooth they take ages to transfer , how come the galaxy s iii use wifidirect ( with their marketing name "s-beam" ) ? so silly
Isnt there a way to force android beam to use wifi direct instead of bluetooth?
Click to expand...
Click to collapse
is your NFC even turned on? How about try going to settings>more>(check) NFC and you can see Andriod Bean via NFC
It is a chip stored in a battery do you expect it to take 2 seconds to transfer?
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Maybe not 2... but less than 10. 1 MB/s isn't unreasonable though so yeah, he probably does expect that.
Sent from my Xoom using xda premium
DerAmi said:
It is a chip stored in a battery do you expect it to take 2 seconds to transfer?
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's just the antenna isn't it?
Sent from my Galaxy Nexus using Tapatalk 2
DerAmi said:
Yep he is. You guys really should do research before creating forum topics.. Android beam uses NFC not Bluetooth. S-beam while yes using WiFi direct, the s3 also has the ability to share content through NFC.
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Maybe you should do some research as well.
In Jellybean:
Android Beam uses NFC as a matchmaker and transfer for basic things like URLs. For images, it is a matchmaker for BT.
NFC initiates connection and BT transfers.
NFC is too slow to transfer images. Are you really going to hold your devices together while you transfer a ~3+mb image for that long?
Max speed for NFC (standardized) 424Kbps. Slowest is 106. I have no idea which speed the Gnex uses, but its probably NOT the top end speed.
DerAmi said:
It is a chip stored in a battery do you expect it to take 2 seconds to transfer?
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
NFC antenna is in the battery. Not the NFC hardware itself.
3devious said:
Maybe not 2... but less than 10. 1 MB/s isn't unreasonable though so yeah, he probably does expect that.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I've transferred several mb images in a few seconds from my Gnex to N7. However it is wonky. The matchmaking process has issues. It took me 4 tries to get it to work to my N7, and Gnex to Gnex, it hasn't worked at all.
And your point? A radio needs an antenna does it not? It's supposed to be used to share light files not megabits of files. It may not be much, but again were talking about something slower than Bluetooth.
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
DerAmi said:
And your point? A radio needs an antenna does it not? It's supposed to be used to share light files not megabits of files. It may not be much, but again were talking about something slower than Bluetooth.
SwiftKey'd with my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Maybe you missed the features of Jellybean.
http://mashable.com/2012/06/29/jelly-bean-android-beam/
My point is, IT IS for transferring pictures but the transmission medium is not NFC like you said.
It uses Bluetooth.
Also, my point about the antenna being in the battery, not the NFC chip, is to correct your mostly wrong information in this thread. You can't be going and telling people to research while you post incorrect information yourself.
The SGSIII uses Android Beam with Wifi Direct and calls it S-Beam....so there has to be a way to do the same with the GNEX!
Btw when I tried transferring an image to a SGSIII, it popped up with an error about not supporting such a big file or something. But it transferred fine GNEX to GNEX.
Sent from my Galaxy Nexus using Tapatalk 2
Elisha said:
The SGSIII uses Android Beam with Wifi Direct and calls it S-Beam....so there has to be a way to do the same with the GNEX!
Btw when I tried transferring an image to a SGSIII, it popped up with an error about not supporting such a big file or something. But it transferred fine GNEX to GNEX.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not without surgery. S-Beam uses wifi-direct as the matchmaker, Android Beam uses BT. It would likely take changes to the source code to fix it, and I don't believe Android Beam is completely open source.
Dear OP
You don' t say something sucks unless that item/services trully really sucks. In this case your GN since it's you that seems to have issues with it.
As far as Android Beam is concern everthing works fine. Perhaps it's time to get yours check?
Would like to take a sec to thank adrynalyne for clearing up misinformation all over these forums posted by people who have no clue what there talking about.
That is all.
Sent from my Galaxy Nexus using xda premium
xxprodigyxx11 said:
Would like to take a sec to thank adrynalyne for clearing up misinformation all over these forums posted by people who have no clue what there talking about.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes! thank you adrylyne, perhaps people should make their own research before they say my nexus is broken lol , or that android beam doesnt use bluetooth to transfer files
I'll probably end up upgrading around December but, I've been curious as to what the current state of dev support is for the s3.
I've heard there are a number of problems with getting the NFC to work and I was wondering if this is local to the S3 or if it applied to all phones with NFC.
It doesn't apply to the galaxy nexus.
Sent from my Galaxy Nexus using xda premium
Snow_fox said:
I've heard there are a number of problems with getting the NFC to work and I was wondering if this is local to the S3 or if it applied to all phones with NFC.
Click to expand...
Click to collapse
Can't speak for anyone else, but NFC works fine here (running CM10). Maybe it's another model of S3 that's having issues?
smelenchuk said:
Can't speak for anyone else, but NFC works fine here (running CM10). Maybe it's another model of S3 that's having issues?
Click to expand...
Click to collapse
I'm not entirely sure which is actually why I felt the need to ask.
The S3 is a pretty nice piece of kit that I may pick up in Decemberish.. but, I'd like to make sure it can mirror my captivates longevity in terms of dev support.
Its a flagship Samsung phone. Of course there will be prolonged dev support.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hey guys,
I just placed an order for the following item which is Miricast pre-certified: http://www.netgear.com/home/products/hometheater/media-players/PTV3000.aspx#
As per several articles online such as this one http://www.theverge.com/2012/9/19/3356512/miracast-certification-wifi-direct-video-streaming , the Galaxy 3 is already Miricast enabled (I assume the technology is similar to its allshare cast).
My question therefore is how will I be able to enable/use that feature once I get my new Wireless Display Adapter? I assume it's an app to use, but as far as I'm aware there is not one yet on the market. Is this something we have to wait for Samsung to release as an update?
Thank you in advance for any help.
I belive you would use wifi direct to connect to the unit
Sent from my SGH-T999 using xda premium
vopezy said:
I belive you would use wifi direct to connect to the unit
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Makes sense, I'll try it out as soon as I can and report back. Thanks!
Sent from my Samsung Galaxy 3
Tried it out but it did connection failed, although it did identify the adapter and try to connect. I thought it was a WiFi direct problem with my Rom on my phone but I just tested it with my co worker and we can send stuff to each other no problem.
Any ideas?
Sent from my Samsung Galaxy 3
Okay just got off the phone with Samsung and they're saying only the International Galaxy 3 is miracast certified? Can anyone else confirm? I really only got the PTV3000 for this feature =/
Any ideas?
Sent from my Samsung Galaxy 3
I'm understanding no Bluetooth LE for galaxy nexus but can anyone confirm that the broken features in 4.2.2 are fixed in 4.3 like bad in call quality, bad audio streaming and no id tags that worked in 4.1.2. I have awhile to wait since I'm on toro but wondering if I should even be excited as I need these to work.
Sent from my Galaxy Nexus using xda app-developers app
Tags work but quality still sucks like on 4.2.2. Epic fail if you ask me. And no more audio controls were added.
Sent from my AOSP on Toro using Tapatalk 2
Guess I can move on with life and not worry about upgrading to 4.3.
Sent from my Galaxy Nexus using xda app-developers app
Howdy
I just got 4.3 on my Nexus - and the first thing I did was run out to the car and try pair it. Sadly it behaves just like 4.2 did - it pairs - connects for about 2 seconds and then disconnects - and that is the end of that.... I know it might be blasphemous - but I am wondering if an iPhone would at least work with my car .. I really don't want to go all the way back to 4.1 to get Bluetooth working! Sadly in my country you get a huge fine if found talking on your phone in the car - so bluetooth is kinda essential (and one of the reasons I bought the car in the first place)