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
Related
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
So there i was cleaning my room -.-' and as i was cleaning i found my old nexus one. It was dead, so I plugged it in.
When i turned the device on, a lot of memories came to mind, as the progress google has made.
But then as i was looking trough it i noticed that it felt kind of fast for it to be a 3 years old. So I put my Gnex running jellybean next to it.
To my surprise every action was faster on the Nexus One? Odd but yeah. Openning Applications like the clock, calendar, browser, settings.
How come a three year old device is faster than the galaxy nexus, i know the gnex has a lot more things to process as well as the size of the screen, but common really? I guess im going to use it as an mp3 player now.
Screen resolution I would guess, gnex is pushing out android in HD 720p and nexus one is what 800x600 perhaps roughly. Also older versions of android I expect are much less complex than jelly bean. The only fair way to test is do a test of stock JB on each device and see which fares better then, but still you have to take into concideration just how many more pixels gnex is pushing out. Cool story though :thumbup:
Sent from my Galaxy Nexus
Probably differences of OS.
Sent from my Galaxy Nexus using Tapatalk 2
sergioosvaldo1 said:
So there i was cleaning my room -.-' and as i was cleaning i found my old nexus one. It was dead, so I plugged it in.
When i turned the device on, a lot of memories came to mind, as the progress google has made.
But then as i was looking trough it i noticed that it felt kind of fast for it to be a 3 years old. So I put my Gnex running jellybean next to it.
To my surprise every action was faster on the Nexus One? Odd but yeah. Openning Applications like the clock, calendar, browser, settings.
How come a three year old device is faster than the galaxy nexus, i know the gnex has a lot more things to process as well as the size of the screen, but common really? I guess im going to use it as an mp3 player now.
Click to expand...
Click to collapse
You must've been high
Sent from my Galaxy Nexus using xda app-developers app
malikadnanm said:
You must've been high
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Off of the dust from that dusty room.
Nexus One had an 480x800 display.
Sent from my Galaxy Nexus using xda app-developers app
Yeah! Because I love damaging my brain and self doing that. But its true. Maybe because they're both nexus. And Google had to come out with a really good phone. I still love my nexus one
Sent from my Galaxy Nexus using xda app-developers app
Run a game and see what happens :>
CPU in N1 is fine, so is ram, its the GPU/ amount of built in app/system storage that's the problem
Sent from my Galaxy Nexus using Tapatalk 2
What would happen if someone successfully port Android 2.x to gnex..
Bringing back it's legacy lol
Sent from my Galaxy Nexus using Tapatalk 2
sergioosvaldo1 said:
Yeah! Because I love damaging my brain and self doing that. But its true. Maybe because they're both nexus. And Google had to come out with a really good phone. I still love my nexus one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You could never damage your brain from THC. Just sayin.
I have both too. If you run stock on both (gingerbread vs jelly bean), there is certainly no way the gnex is slower...
For one, the touch response on n1 was pretty bad... its not slow, but to say its faster than gnex is a bit odd.
Sent from my cm_tenderloin using xda app-developers app
FC1032 said:
I have both too. If you run stock on both (gingerbread vs jelly bean), there is certainly no way the gnex is slower...
For one, the touch response on n1 was pretty bad... its not slow, but to say its faster than gnex is a bit odd.
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I have both too, n1 is a quite good phone, but the touch problem is historically odd.
I just switched from 2.5 years of using the N1. The GN is better in every aspect.
AmericanCon said:
You could never damage your brain from THC. Just sayin.
Click to expand...
Click to collapse
I think you meant HTC
Sent from my Galaxy Nexus using xda premium
My N1 is sitting in it's cradle on my kitchen bar and has become an e-mail alert system--I can see the flashing track ball from most points in my main living area when an e-mail comes in.
One place the Galaxy Nexus really excels over the Nexus One is as a music player. I was never impressed with the sound quality of the N1. And with low impedance headphones, there is a periodic thumping sound/artifact, about one thump per second. The Galaxy Nexus, on the other hand, has some of the best sound quality I've heard on a portable music player--at least as good or better than my iPod Classic 120GB.
That brings up one thing the N1 had that I really miss--a microSD card slot. I wish the GN had a modern microSD slot--I'd love to have a 64GB SDXC microSD card in it. I get around this by mounting a flash drive via USB OTG that contains my music collection, but it's definitely not ideal.
sergioosvaldo1 said:
...As i was cleaning i found my old nexus one...I put my Gnex running jellybean next to it. To my surprise every action was faster on the Nexus One? Odd but yeah. Opening Applications like the clock, calendar, browser, settings. How come a three year old device is faster than the galaxy nexus, I know the gnex has a lot more things to process as well as the size of the screen, but common really?
Click to expand...
Click to collapse
Put cm9 on both phones and see which one runs better.
you MUST have done something wrong..
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
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)
I have a T-Mobile S3 and a Nexus 7 but they aren't interacting with one another via NFC/Android Beam. GS3 is running root box and the N7 is running Paranoid Android. Anyway to test which one isn't working? I've thought of buying tags but want to avoid buying other items unless necessary.
EDIT: I recently had my S3 LCD Replaced but I always assumed the battery is what allowed NFC to be used and the battery (as far as I know) is original.
Sent from my SGH-T999 using xda premium
Nfc is built into the stock battery.
Get nfc tag info from the store and test on any rfid tag, such as security tags.
Sent from my SGH-T999 using xda premium