Jump to content

NFC Transfers...


elkaku
 Share

Recommended Posts

Please anyone can give me a bit of insight on the nfc transferring....but between a gs3 and an EVO LTE....

 

THNX

 

posted using J.A.R.V.I.S.

 

 

Link to comment
Share on other sites

Please anyone can give me a bit of insight on the nfc transferring....but between a gs3 and an EVO LTE....

 

THNX

 

posted using J.A.R.V.I.S.

What specifically? That is pretty vague.

 

Sent from a phone using an application. That's pretty cool.

 

 

Link to comment
Share on other sites

There's always dropbox on both devices. If the accounts are different just share a folder to the other account. Drop the APK in the share and done deal. Much easier than emailing.

 

This how I transfer stuff to my wife's phone all the time. I'm lazy and don't feel like hooking up my phone to a PC and just use the dropbox cloud. I know it's slower but oh well.

Link to comment
Share on other sites

You should not need to do more than enable nfc on both phones and then follow the directions. One oddity that i did notice when trying to send an app from the GS3 to the EVOLTE is it wont transfer the app. but rather it will take you to the google play store where the app is located.

Link to comment
Share on other sites

It should work no problem. I did this with a friend of mine who has the evo lte. I have the gs3. Yes it will just share a link to the app in the play store as it will only use the "android beam" standard nfc tech which is very slow and only meant for transferring small amounts of data. You will not be ablt to transfer the actuall app files . S beam, which is what samsung devices use to transfer larger files.(pictures, videos etc) only uses the nfc part of the technology to create a wifi direct connection between the devices to transfer the larger files. Obvioulsy connected the devices directly to one another via wifi gives you a much faster transfer rate as well as increased range. I would have to imagine that sooner than later there will be an app that will allow all phones with nfc and wifi direct capability to do s-beam like transfers

  • Like 2
Link to comment
Share on other sites

  • 4 weeks later...

In still havintlg issues ...... Why does my sister can transfer from her gs3 some files but if I were to send similar files from my LTEVO to her phone it sends her to the play store....??

 

:(:huh::wacko::unsure::blink:

 

posted using J.A.R.V.I.S.

 

 

Link to comment
Share on other sites

In still havintlg issues ...... Why does my sister can transfer from her gs3 some files but if I were to send similar files from my LTEVO to her phone it sends her to the play store....??

 

:(:huh: :wacko::unsure::blink:

 

posted using J.A.R.V.I.S.

you may have to bypass the s-beam functionality and set up the direct wifi on both devices.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Update just showed up for both of my phones. So far I don't notice any difference, LTE TA is still reporting as 0, I was hoping the new routine might fix that. I sent a diag report from both phones in case you need any of that info. I'll let you know in a day or so if its crashing as frequently or not. 
    • A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes: New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this. New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working. Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing. Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact. Feedback welcome as always!
    • Another converted keep site: Sprint eNB 9436 -> T-Mobile eNB 895067 (40.60777246698788,-74.16199692361377) Looks like they're using the FFVV-65A-R2-V1 here, as well!   Edit: Also, I know this technically isn't NYC, but here's a Jersey City conversion. Not 100% sure on either eNB. Sprint eNB 105863 -> T-Mobile eNB 876452 (40.72265196811989,-74.08804945021805)
    • More confirmations incoming! T-Mobile eNB 880561 (40.74176835140717, -73.88364207139453)   Sprint eNB 6191 / T-Mobile eNB 880065 (40.71339007010928, -73.85695387371624) Confirmed this site but was unable to get a photo because the antennas are set back from the edge of the building. I could see them from super far away but there wasn't a good area for me to pull over and snap a pic.   Sprint eNB 6189 / T-Mobile eNB 877995 (40.71183894845567, -73.83529788316665)   Sprint eNB 253741 / T-Mobile eNB 875537/875538 (40.70170960850086,-73.83302208208359)   Sprint eNB 79912 / T-Mobile eNB 875989 (40.86349197342981, -73.923456682535) — — — — — T-Mobile eNB 880536 in the Bronx isn't a Sprint conversion but rather, T-Mobile changed the eNB when they upgraded the site. The nearest Sprint site at 40.8150405321864, -73.93010756429787 still has all of its antennas up and is literally within spitting distance of two other T-Mobile sites in an area that's very industrial as opposed to residential or commercial so a keep site isn't particularly necessary. You can see on Cellmapper that the old eNB stopped broadcasting about two days after the new eNB went live.  — — — — — Also wanted to add that I spotted AT&T C-band antennas quite a bit in both Queens and the Bronx. I would expect a summer C-band launch announcement from them because they're moving FAST. At least in my area, it seem like they're upgrading at a faster pace than Verizon is. Some more pics: AT&T eNB 116408 / T-Mobile eNB 42887 in Woodhaven. This one is interesting because T-Mobile upgraded this site but in the process didn't put any Ericsson n41 antennas. There are just two of the RFS antennas that we normally get.   AT&T eNB 112047, bad pic but the arrows on the billboard are pointing right at the C-band antenna lol   — — — — — Last edit I promise: I noticed T-Mobile submit a permit to convert the keep site I found in Staten Island (Sprint eNB 75141). I 100% guessed it's location since I connected to it literally 4.5 miles across the water while inside a building. Glad to see I was right!
    • Support for the -1 TAC is good to go now, so I'm ready whenever you are!
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...