Develop Bugs

Some strange AT&T One X oddities

Just got my One X from AT&T the other day.. Cancelled my Verizon contract to come over to this phone, came from an iPhone 4s.
This isn't my first rodeo when it comes to Android devices, I sampled just about every VZW device they offered.
After playing with the One X for a few days, I have noticed a couple things; one of which I think is a software bug.
1. Sometimes the WiFi doesn't disconnect, or realize that it is no longer in range of a connected access point. This morning for example, when I got to work it thought I was still connected to my home access point and as such wouldn't connect to the work access point, until I manually went into the WiFi settings. It's almost like a background process stopped and didn't start up again until I did something.
2. The HTC Sense integration with Facebook is really cool, however, even though I told it *not* to show any contacts on my contact list, when I sync my phone with my car's bluetooth system, it downloads not only the contacts I want to see, but all of my Facebook contacts also. Any way to use the FB integration but truly not download/present the contacts to a bluetooth device?
So far, I am really liking the phone. The screen is absolutely amazing and I really, really like what Sense 4 has added. I had a Rezound with the ICS rom on it, but you can definitely tell that HTC took a lot of feedback coming from the older versions of Sense and incorporated it into Sense 4.

This isn't the forum for the AT&T One X. It's over here...
http://forum.xda-developers.com/forumdisplay.php?f=1539

Scumbag AT&T naming strikes again

wrong forum pal

Crap, sorry guys.

Another CM10 question...AFT? I can't connect...

Okay, one other curious question...On CM10 7/29 build...is anyone getting Android File Transfer to work? Yes, I'm on a Mac, but it was working fine before, granted I had to call it a camera instead of MTP, but it worked just fine. Now that I got a 32GB SD, I'm wanting to transfer everything over, but now when I plug it in, I get nothing. Any ideas?

So, I've flashed all the roms on my SD card...CM9, CM10, Ultimatum, AOKP, now I'm on Paranoid Android(liking this one best because it's a mix of CM10 with more stuff working so far..) but anyway. I noticed on all of the JB-based roms, Android File Transfer no longer works. This wouldn't be an issue because I could flash Ultimatum, which is ICS-based, right? Still doesn't work. I've read around and some people say Samsung updated something that broke AFT for mac...but I'm just not sure. I just got a new 32GB SD, so I want to move the stuff from my 8GB to this one...but using wireless solutions will take hours on end...and I'm not even sure which one of these works the best. Any ideas?

I believe the file transfer on android does not like to work with cm10 on this phone and its not an issue that seems too high on the devs list because of the few amount of mac users. Really sucks but meh, honestly if i want to transfer stuff i boot up windows through bootcamp and do my thing
My suggestion is, flash a stock based rom and just move the majority of the stuff using mac and then for smaller/more periodic stuff after that you could just use a wireless transfer thing. Because for me, after my initial sync of all my music i usually only sync photos or a few songs at a time so wireless syncing wouldn't be too big of an issue.

Indeed, I found a workaround to use CyberDuck to transfer stuff...of course, my first big transfer is going to take hours, which sucks---I wish they would look at this issue...even if Mac users are the minority, that's a pretty big issue-Normally I wouldn't have issue with either dual boot or Parallels, but I'm broke at the moment so I'm running a G5 iMac. While it runs, you can imagine how slow it can get, since this is pre-aluminum models... I tried flashing a stock-based rom (Ultimatum) and it still didn't work. I've heard that a Samsung minor update might have broken it, but I didn't get any OTA updates. I'm just glad CyberDuck/SSHDroid let it work just like my jailbroken iPhone works with CyberDuck the same way, so I'm familiar with it. I guess I'll need to go back around the forums I was searching for answers on and post a tutorial on using CyberDuck with the S3.

S Beam

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?

NFC S Beam

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....

does NFC really works in HOX?

I have tested about 3 HOXs that, after turning on NFC and android beam and bringing closer the two devices (back to back) the HOXs vibrate but NFC symbol doesn't show up and 'tap to beam' option won't appear. I have tested a gs3 and xperia ion as well, they work correctly (NFC symbols shows up and tap to beam options appear on files to be transferred)
Is this a serious bug or is there any other way to make it work on HOX?

Mine definitely works. I have a bunch of nfc tags and used nfc task launcher to set the tags. Also sent a link from my HOX to my wife's LG escape using nfc.
Are you saying that it doesn't work for you in both directions? Do have any tags to test with?

I am not sure whether it works or not in all the three HOXs I've tested. But NFC symbol won't shows up, though the devices vibrate when I bring them closer, back to back.. touch to beam option never apppeared on the files to be transferred. So, I doubt it for the same two reasons.
No, I haven't tested with tags, but tested among many combinations of HOX, GS3 and Xperia ION.

RAHIM233 said:
I have tested about 3 HOXs that, after turning on NFC and android beam and bringing closer the two devices (back to back) the HOXs vibrate but NFC symbol doesn't show up and 'tap to beam' option won't appear. I have tested a gs3 and xperia ion as well, they work correctly (NFC symbols shows up and tap to beam options appear on files to be transferred)
Is this a serious bug or is there any other way to make it work on HOX?
Click to expand...
Click to collapse
if it works, I've already used to transfer contacts from a galaxy s3. The icon never appears, or is it that I've never seen xD

Nah it doesn't, its just a switch made specifically to brag about with your iPhone using mates.
Seriously, mine works.
Sent from my HTC One X using xda app-developers app

Are you doing file transfer using NFC?
Nah~ NFC file transfer doesn't support natively on ICS, Google implemented it since JB. FYI, file transfer on GS3 was Samsung's own feature that using NFC to hook up Wifi-Direct for tranfering files. NFC had really tiny bandwidth that not feasible for transfering large quantity of data.

It works fine, but as HebeGuess stated, in ICS transfering pictures or files does not work.
Open a contact or a webpage on one device and then put them back to back. Make sure the devices have the screens on & the screen unlocked.

Hmm.. my NFC is working well. But NFC icon isn't displaying in HOX. successfully transferred webpages and contacts.
Waiting for JB update for file transferring via NFC