So just hoping you guys could clear this up for me.
As far as I know, S-beam replaced android beam as the NFC app on the gs3. Form everything I've heard, s-beam can only communicate with another s-beam enabled device, which right now means only the gs3. However I have no proof of this, either way.
So, that said, here are my questions.
1) if you 'bump' a gnex and a gs3, will android beam and s-beam communicate?
2) if not, is there any way to get a-beam working on the gs3, for better compatibility?
3) would it be worth the effort (or even possible) to try to get s-beam onto other nfc enabled devices? It seems to have more features than A-beam, so if A-beam and s-beam are compatible, it would be seen as an upgrade, and if they're not compatible, it would still be useful, as a way to communicate with s-beam enabled devices.
Thanks in advance for your answers!
S Beam supplements Android Beam, it doesn't replace it. There are two separate options in the menu (see attachment).
As for porting, S Beam obviously implements certain authentication and security features. But it might still be possible to port. It might not even be worth it: the only other person I know with an S3 is my dad and he's thousands of kilometres away so I can't say how well S Beam works.
Your first two questions are obviously moot.
But I also got the impression before that S Beam replaced Android Beam, so don't feel bad anyway.
Thank you for clearing that up!
The reason I asked if it would be possible/worth it to port is twofold. One, because the US is soon going to get a huge amount of GS3s, and the other, because nfc-based wifi direct is a feature that I would use daily if I had it on both my phone and tablet.
i tried android beam 2.0 (jelly bean on my nexus) with the galaxy s3 s beam. I tried to sent a image and only get text on my display like ".../galleryshare" with an OK button but no file.
not very sucessfull
Related
ASUS has touted Wi-Fi Direct http://www.asus.com/News/k4PosV90YN1qdjZ3/ as one of the features present on the Transformer Prime. For those of you who are not familiar, Wi-Fi Direct is basically a means of establishing an ad-hoc Wi-Fi connection without the need for a router or one device acting as a hotspot and was just introduced into Android 4.0.
I've had the chance to use it on multiple occasions, transferring huge files between two Galaxy S II devices and all I can say is the speed is much, MUCH faster than Bluetooth, such that transferring 2GB can be done within a reasonable time frame like that of a meal. Also, it doesn't consume anywhere near as much battery as using one device as a hotspot and then transferring files between them.
So my question is, has anyone found a way to access the WiFi Direct functionality we all supposedly have on our Transformer Primes? Given the spottiness of MTP/PTP, having another reasonably fast way to get files on/off the device can only make things better!
Source: android.com
Support for Wi-Fi Direct lets you connect directly to nearby peer devices over Wi-Fi, for more reliable, higher-speed communication. No internet connection or tethering is needed. Through third-party apps, you can connect to compatible devices to take advantage of new features such as instant sharing of files, photos, or other media; streaming video or audio from another device; or connecting to compatible printers or other devices.
Click to expand...
Click to collapse
application is needed
Thanks! Did a search of the market, seems no apps implement that functionality yet...
ong.andrew said:
Thanks! Did a search of the market, seems no apps implement that functionality yet...
Click to expand...
Click to collapse
yea, i've been really excited about this, but google doesn't seem to have it finalized yet from what i understand. It will make printing about 50x easier in the workplace since chrome is not commonplace and chrome is required for cloudprint
So is this why we don't have an option in our settings as opposed to the Galaxy SII?
You don't need any App.
WiFi-Direct technology is implemented in ICS 4.0 and aboce.
whne the Prime will get ICS update it will support it. in any context menu.
it would be like sending via bluetooth.
I guess ASUS ment that te Prime's wifi chip DOES suppot that. but the software need too. and Gingerbread dosen't.
On the Galaxy S2 it's the same thing. only Samsunge made special apps for themselfs and that was build in the system (in the TouchWiz). No other 3-rd party project can access that thing and build other Apps. Only when the Galaxy wil have ICS update. exaclly like here....
Good luck...
Here are some resources regarding "wifi direct":
http://developer.android.com/resources/samples/WiFiDirectDemo/index.html
zaxy78 said:
You don't need any App.
WiFi-Direct technology is implemented in ICS 4.0 and aboce.
whne the Prime will get ICS update it will support it. in any context menu.
it would be like sending via bluetooth.
Click to expand...
Click to collapse
This is actually not true. I own the Galaxy Nexus and currently there is no way to actually use WiFi Direct without an app. Even the core Android apps don't make use of it. Pretty useless feature up until Google or the developers start releasing apps that make use of it.
The Android Beam function on the S3 is called "S Beam". Samsung says the S Beam can send photo's sized 10mb within 2 seconds. The Android Beam however can only send links because of the slow transfer rate. So now I was wondering wether this is a software or a hardware upgrade, anyone got some idea's?
The S Beam uses Wi-Fi Direct to transfer the files, NFC is just for pairing.
That explains a lot, thanks
Is there already a ROM that also includes this?
The question now is still the same, though.
The Galaxy Nexus supports Wifi direct, will it be able to pair up with a SGSIII the same way? Not too long 'till the 29th of May..
I just got a s3 and my wife has a nexus s. I know s-beam only works between 2 s3s but I was hoping plain android beam would work between the s3 and nexus s since both of them have NFC and android beam support. I have all the required settings turned on but no luck. I can't share a link or YouTube video or contact. What's the point of the open nature of android if 2 phones with the same OS can't use the same damn technology? Sorry ... has anyone made android beam work between s3 and any other phone.
koham said:
I just got a s3 and my wife has a nexus s. I know s-beam only works between 2 s3s but I was hoping plain android beam would work between the s3 and nexus s since both of them have NFC and android beam support. I have all the required settings turned on but no luck. I can't share a link or YouTube video or contact. What's the point of the open nature of android if 2 phones with the same OS can't use the same damn technology? Sorry ... has anyone made android beam work between s3 and any other phone.
Click to expand...
Click to collapse
It would be a shame if Samsung nerfed A-Beam with S-Beam. If OEMs are going to add features and skins - fine I guess although I wish they would give them back to Google as AOSP. If they are going to destroy features of the stock OS, this hurts the ecosystem as a whole and I'd like to see Google play hard-ball and not certify those devices for having the market or any Google apps.
Droosh said:
It would be a shame if Samsung nerfed A-Beam with S-Beam. If OEMs are going to add features and skins - fine I guess although I wish they would give them back to Google as AOSP. If they are going to destroy features of the stock OS, this hurts the ecosystem as a whole and I'd like to see Google play hard-ball and not certify those devices for having the market or any Google apps.
Click to expand...
Click to collapse
I agree that would be a good start but would go against the "open source" ecosystem that Google has created.
Sent from my Galaxy Nexus using Tapatalk 2
Open up your gallery and select a picture after turning on your a-beam then try tapping backs.
If that doesn't work, check if turning s-beam off allows it to, maybe s-bean takes over the event.
Sent from my GT-I9300 using xda premium
koham said:
I just got a s3 and my wife has a nexus s. I know s-beam only works between 2 s3s but I was hoping plain android beam would work between the s3 and nexus s since both of them have NFC and android beam support. I have all the required settings turned on but no luck. I can't share a link or YouTube video or contact. What's the point of the open nature of android if 2 phones with the same OS can't use the same damn technology? Sorry ... has anyone made android beam work between s3 and any other phone.
Click to expand...
Click to collapse
Contact, links : galaxy nexus <=> S3 with Android Beam, I tried and it worked.
Photo, files: S-Beam, therefore only between S3
link2caro said:
Contact, links : galaxy nexus <=> S3 with Android Beam, I tried and it worked.
Photo, files: S-Beam, therefore only between S3
Click to expand...
Click to collapse
May i know the settings you used to get this to work?
doomwithdon said:
May i know the settings you used to get this to work?
Click to expand...
Click to collapse
Turn on nfc and Android beam and touch the backs of the phones together.
doesn't android beam use nfc to pair phones just like s beam does?
s beam uses wifi direct, and I thought android beam uses bluetooth to transfer files?
am i wrong? it's pretty stupid that i'm limited to other galaxies for this feature to send a picture...
I agree with all of these statements. Android Beam should be able to open a Wi-Fi direct connection. Samsung's S-Beam is a gimmick unless everyone has a damn GSIII. i have a Gnex and my Girlfriend has a GSIII. This makes her badass GSIII S-Beam feature useless as we can only tap our phones to share links and contacts. unless we are sitting on each others lap; Texting her a link is quicker and more practical than tapping our phones together, me touching my screen to 'beam' a damn link to a youtube video to her. I was pretty stoked when she got the phone thinking that we would be able to share pics and video's via NFC and WiFi direct. For some reason I just assumed that this would work seeing how both phones have NFC and WiFi Direct.
This is atrocious! When I try to send a picture to my friend's GNexus with my android beam and nfc on but s beam off, my phone asks me to turn s-beam on. WHY? I am trying to use android beam!!!
I have a galaxy nexus on tmobile (yakju variant) my friend has a galaxy nexus on Sprint network. I open the gallery app on my phone, and go to a picture (its a 1.02MB photo) i tap my phone to the Sprint Galaxy Nexus, and touch to beam, and android beam can transfer this file over, easily, no other actions necessary.
I tap the same picture to somebody using an galaxy s2 or galaxy s3, and the android beam cannot send the picture, instead I receive a message saying "the receiving device cannot support large file transfers" ??? what ??? i dont understand??
so android beam supports large file transfers when its android beam nexus to nexus? but not when its nexus to Galaxy S2 or Galaxy S3 ?
does anyone have any insight on this?
If you want to transfer images to a non-sbeam device, make sure you have enabled android beam in you settings and DISABLED sbeam. If you do not disable sbeam, for example transferring a photo will give you google play on the target device, because it tries to find the samsung gallery. Disabling sbeam will pair the devices and send the data over bluetooth.
avdaga said:
If you want to transfer images to a non-sbeam device, make sure you have enabled android beam in you settings and DISABLED sbeam. If you do not disable sbeam, for example transferring a photo will give you google play on the target device, because it tries to find the samsung gallery. Disabling sbeam will pair the devices and send the data over bluetooth.
Click to expand...
Click to collapse
I'm not seeing android beam on my s3, just NFC and Sbeam... Ideas?
http://www.youtube.com/watch?v=Cytk-GvEdA8
I was wondering if any developers were working on porting s beam over to our devices? Android Beam lacks the feature of sending larger files so s beam kind of solves the problem. I hate having to go through settings to enable wifi direct and then manually connect to other devices and manually send files. I think it's actually pretty smart to have nfc establish this connection automatically.
dsmboost said:
I was wondering if any developers were working on porting s beam over to our devices? Android Beam lacks the feature of sending larger files so s beam kind of solves the problem. I hate having to go through settings to enable wifi direct and then manually connect to other devices and manually send files. I think it's actually pretty smart to have nfc establish this connection automatically.
Click to expand...
Click to collapse
I don't think its possible
Honestly it sounds more likely that someone would modify Android Beam to accommodate larger files and such, since its manufacturer agnostic.
This is not a solution but when jelly bwan comes out for the I1777 we will be able to send larger files.
Sent from my SGH-I777 using xda app-developers app
jthatch12 said:
I don't think its possible
Click to expand...
Click to collapse
I realize I'm necroing, but why isn't this possible? We have Wifi direct and NFC, and some ROMs retain Touchwiz if TW dependencies exist with S Beam, so why wouldn't it be possible to port S Beam over? I think it would be both cool and useful if we could mod our phones to work with GS3s, and besides, there aren't many other current uses for NFC right now anyway.
Side note, what is the current file size limit for Android beam transferring?
karate104 said:
I realize I'm necroing, but why isn't this possible? We have Wifi direct and NFC, and some ROMs retain Touchwiz if TW dependencies exist with S Beam, so why wouldn't it be possible to port S Beam over? I think it would be both cool and useful if we could mod our phones to work with GS3s, and besides, there aren't many other current uses for NFC right now anyway.
Side note, what is the current file size limit for Android beam transferring?
Click to expand...
Click to collapse
From what I understand, when transferring media files with android beam, all it does is enable bluetooth and transfers via that. So, I don't think there would be a file size limit.
Task 650 ROM has this enables and works well
Sent from my SGH-I777 using xda app-developers app
bocephus007 said:
Task 650 ROM has this enables and works well
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
An initial search of the AOKP thread doesn't mention anything specific about S Beam, it seems to be only Android Beam. I'm just wondering about a full S Beam port, that would work with stock S3s and any other Samsung devices that include S Beam, especially since I've heard people have problems using Android Beam with S3s, which get confused. Samsung's Android devices are so prevalent nowadays, so it would be nice to be able to interact with them easily without having to fuss around with extra apps or settings. I just want to know if it's possible or not.
EDIT: So a little more research done. Android beam isn't a separate app but is built into ICS (guess I forgot that lol). It uses Bluetooth to share data and is limited to links and contacts (maps and YouTube videos fall under links, you don't beam the whole thing, you just beam the specific urls). Please correct me on that point if I'm wrong. This is already possible with S3s, I didn't know they retained Android beam in addition to SBeam, which uses wifi direct and can transfer larger files like pictures (it's faster too).
As useful as Android beam is because it works with all nfc-capable ICS devices, I still think a full S Beam port would prove useful since it can transfer larger files faster and with newer Samsung devices (of which there are now several, and they're the most popular). So is it possible? And if not, why not?
karate104 said:
EDIT: So a little more research done. Android beam isn't a separate app but is built into ICS (guess I forgot that lol). It uses Bluetooth to share data and is limited to links and contacts (maps and YouTube videos fall under links, you don't beam the whole thing, you just beam the specific urls). Please correct me on that point if I'm wrong. This is already possible with S3s, I didn't know they retained Android beam in addition to SBeam, which uses wifi direct and can transfer larger files like pictures (it's faster too).
Click to expand...
Click to collapse
Fyi..this stuff is very old news. In Jellybean, you are now able to send larger files via android beam, such as audio and video. But files aren't actually transferred through android beam, all it does is activate bluetooth and automatically pair your device with the other phone to initiate transfer via bluetooth. S Beam is the same thing, except it activates wifi direct instead of bluetooth.
I'd give up on this whole s beam thing if I were you. I have not seen any devs ever mention implementing it on our phones.
Today i tried to play a bit around with the s3 of a co-worker and mine.
It seems that s beam overrides the with jb introduced feature to send images/videos with android beam.
It isn't that big deal, i used wifi direct directly instead and will go on that way, because s beam itself is a bit messy (wifi direct setting isn't connected to s beam setting, but s beam needs wifi direct to work, it often fails to send,...), but i really would have liked to use the native android beam feature instead.
It anyway isn't completely understandable to me why they did it that way, yes, for sure it took time to implement s beam, but they could have kept it for notes and such and still let media content be shared over android beam.
What do you guys think about it or has anyone maybe got android beam working at the latest touchwiz release with multimedia content?
It's really annoing, especially since it's where nfc is mainly going to be used for now.
Tectas said:
It anyway isn't completely understandable to me why they did it that way, yes, for sure it took time to implement s beam, but they could have kept it for notes and such and still let media content be shared over android beam.
Click to expand...
Click to collapse
Isn't the whole point with S Beam to transfer media content? Pure NFC is S-L-O-O-O-O-O-W, which is why they want to use WiFi Direct for "big" files.
It's a shame that it's not stable, but suggesting only using it for the thing where it doesn't make any sense (notes and such)... Well, makes no sense.
But anyway, can't you just disable S Beam? On mine (4.1 DLI3), NFC/Android Beam and S Beam are two different settings, and S Beam can be disabled seperately.
LosD said:
Isn't the whole point with S Beam to transfer media content? Pure NFC is S-L-O-O-O-O-O-W, which is why they want to use WiFi Direct for "big" files.
It's a shame that it's not stable, but suggesting only using it for the thing where it doesn't make any sense (notes and such)... Well, makes no sense.
But anyway, can't you just disable S Beam? On mine (4.1 DLI3), NFC/Android Beam and S Beam are two different settings, and S Beam can be disabled seperately.
Click to expand...
Click to collapse
Said it, because that's the only use left when android beam is used for media content.
Yes, it can be disabled, but while it's disabled and only nfc and android beam is enabled while i try to share a picture, it just tells me that s beam is disabled and let's me enable it to share the content.
Sent from my GT-I9300 using Tapatalk 2
Tectas said:
Yes, it can be disabled, but while it's disabled and only nfc and android beam is enabled while i try to share a picture, it just tells me that s beam is disabled and let's me enable it to share the content.
Click to expand...
Click to collapse
Yeah ok, it seems a bit silly not to use the new Android Beam capabilities when S Beam is disabled
I have a generic tablet which has Android 4.0.3 stock-installed. I can use the 3G feature without a problem; but when it comes to make voice calls; here's what happens:
1- eXdialer: When the calling button is pressed, nothing happens but the screen refreshes only.
2- DialOne: Prints out the warning on the thread subject: "Telephony feature is unavailable on this device"
The producer company claims that Xphone dialer works on this device; but it looks like some hardware-lock or similar?
Since the mentioned software is not free, I could not test if it works.
Hint: The devices are imported to our country as "it has no telephony feature" on the formal papers, just because of the higher taxes on telephony enabled devices. Previous products of the same company were similarly software-locked and they soon released a new rom that enabled the telephony feature. Now there is no any modified rom for this device.
Any ideas are welcome.
Waiting for somebody to say "xda-dev forum is not a right place for you, ugly duckling"; after all.
To put it in another way, Samsung Galaxy Camera also don't have the Telephony feature even if it does have 3G. So its pretty much they've removed the standard dialer app and the resources/lib associated with it. But by installing the missing things, it could be do-able though, I guess.
That is what I also think; but the damn thing I don't know is: HOW?