Is there a NFC reader app that works on the SGS II? Are there any NFC settings?
Best,
-- Thomas
My Nexus S had NFC built into the battery door, though it appears that my SGS II has no NFC chip visible...unless it's hidden in the main body of the phone some where.
The engadget review said its in the battery itself.
bencozzy said:
To be honest I'm waiting on my tech bud to get phone to take it apart and see if it has NFC harware in it.
Its not there that I know of so no app will work.
Click to expand...
Click to collapse
Look at the battery itself and it is listed on there. Like the other poster said it is in the battery.
So there is no official word on NFC yet?
I hear it does based upon some articles I read dated in late September. 2.3.7 is supposed to have Google wallet. I am curious if anyone can verify it on this variant.
Someone try installing this on top of the cm7 beta http://forum.xda-developers.com/showthread.php?t=1286315
jivy26 said:
Look at the battery itself and it is listed on there. Like the other poster said it is in the battery.
Click to expand...
Click to collapse
Further evidence of it being in the battery - four contacts in ours instead of three for the Infuse. (How many does the I9100 have?)
AT&T is probably waiting for its ISIS deal to go through before enabling NFC on the GSII.
I wonder if the FM tuner is built into the battery too...
Stock kernel has NFC support compiled in but no FM tuner support. Trying to enable FM in the kernel results in the driver failing to initialize.
Don't know the state of NFC in userland. I wish I could get an APK for some app to test with. Market right now considers our device as lacking NFC.
The official AT&T I777 user manual states that the NFC hardware is present but currently disabled.
AT&T manual?
Deleted xxx
Sorry if this has been asked, but I have not been able to find a solid answer yet. Can I install " [ROM]UCLC2 Official ICS "Leak" I777 (3-27-12)" on my S2 with the baseband version UCKK6 and be alright? I had an incident where I put a kernel that wiped my wifi capabilities a while back and wasn't sure if it was because it contained a different baseband. I'm not sure on which modems/basebands I should stay away from?
Thanks.
ck2323 said:
Sorry if this has been asked, but I have not been able to find a solid answer yet. Can I install " [ROM]UCLC2 Official ICS "Leak" I777 (3-27-12)" on my S2 with the baseband version UCKK6 and be alright? I had an incident where I put a kernel that wiped my wifi capabilities a while back and wasn't sure if it was because it contained a different baseband. I'm not sure on which modems/basebands I should stay away from?
Thanks.
Click to expand...
Click to collapse
Any UC baseband will work on our phone. Baseband ONLY affects cell data and voice.
Entropy512 said:
Any UC baseband will work on our phone. Baseband ONLY affects cell data and voice.
Click to expand...
Click to collapse
Oh I see, Thank you for clarifying!!!
Entropy512 said:
Any UC baseband will work on our phone. Baseband ONLY affects cell data and voice.
Click to expand...
Click to collapse
That would seem to be true, since the modem.bin "image" is really just a mini-kernel and real-time OS (ThreadX I believe) loaded by the modem and only talks to Android via the RIL abstraction layer.
But on the Captivate, when using an i9000 ROM (similar to the use of i9100 ROMs here) you actually had to use an i9000 modem too. In fact the rule generally was, the modem had to match the kernel, as we had separate kernels for i9000 and i897 ROMs. This of course opened up many more options since the international variants inevitably have many more modems available. Point is, on the Hummingbird platform, the modem/kernel (and usually ROM) were somehow interdependent on each other. Maybe due to quirks specific to the RIL in each? Or maybe something else? No idea, and not sure that anyone ever bothered to figure it out. (Why people aren't more intrigued about trying to "hack" the modem binary is beyond me. I don't care if my phone violates the law or gives me cancer as long as I get better reception and data speeds... )
Any ideas as to why this wasn't the case with the i777?
In particular on the Captivate, running a mismatched modem would result in voice calls not working properly, though data would usually work, which isn't all that dissimilar from what happens on the i777 with a mismatched modem/kernel/ROM combo.
Just looking for any solution that would let us run i9100 modems on the i777 in particular since there is no proper way to adjust the bands selected by the modem. Aka, that whole stupid RAT restricted bull**** business that AT&T seem to enforce on the UCXXX modems.
Thanks in advance!
And PS, I'm not kernel developer (though I am studied in C/C++), but if you pointed me in the right direction as to where I might be able to find some useful RIL debug output, I'd be willing to pour through some logs looking for anything interesting.
*bump*
Sent from my SGH-I777 using Tapatalk 2
I think that in the case of the I9000 vs. I897, the modem/CPU audio interface may have been entirely controllable by software.
On I9100 vs. I777, there appears to be some hardware in between we don't have control over. As a result:
An I9100 modem on I777 results in no audio regardless of kernel.
An I9100 kernel on I777 results in no audio regardless of modem. I know this end of things - one of the digital I/O channels is set up very differently on I777. Master instead of slave I2S (or was it the other way around?), 16 kHz sample rate instead of 8, and a few other settings are different.
There might be something about that "in between" block we don't know about and can control with the right knowledge, but right now - there's an unknown black box somewhere and it prevents I9100 modem firmwares from providing call audio.
So i have the Galaxy Tab 10.1 LTE from verizon..
I got CWM installed, and tried AKOP... No LTE support
Tried CM9, no LTE support...
so basically there is no LTE support or camera support for the tab? or did I miss something? (totally possible)
Thanks for your help.
BTW both booted fine, and looked good, but without LTE this tab is worthless to me.
evilz51 said:
So i have the Galaxy Tab 10.1 LTE from verizon..
I got CWM installed, and tried AKOP... No LTE support
Tried CM9, no LTE support...
so basically there is no LTE support or camera support for the tab? or did I miss something? (totally possible)
Thanks for your help.
BTW both booted fine, and looked good, but without LTE this tab is worthless to me.
Click to expand...
Click to collapse
No camera because no one has written a camera driver for ICS and Samsung hasn't released the official ICS for our tab. LTE isn't on any ICS ROMs, either, just Honeycomb.
GazaIan said:
No camera because no one has written a camera driver for ICS and Samsung hasn't released the official ICS for our tab. LTE isn't on any ICS ROMs, either, just Honeycomb.
Click to expand...
Click to collapse
thanks
now that is quite disappointing honestly.. I knew about the camera, and was ok with it, but without LTE... I might as well not have the thing
guess I have to wait till Samsung releases ICS, and Verizon checks it out..
I do Kind of wish that the ROM publishers would make that clear... you download a VZW version of a rom you assume that that would work unless otherwise specified.
So LTE doesn't work, but does 3g?
Don't get confused here . .for the SCH-i905 you will NOT get mobile data to work PERIOD. Flashing ICS based ROMs (CM9 or AOKP) that are marked compatible with the SCH-i905 (VZW) version of the GT 10.1 will result in that tablet becoming a WIFI ONLY device.
Until an official release is made there are no drivers available for the camera or the modem built into the LTE version which is why EVERYONE is waiting on camera drivers and all verizon tab users on contract are waiting on modem ones. Before anyone asks, NO the 3g modem driver for 3g models is not compatible with LTE.
muzzy996 said:
Don't get confused here . .for the SCH-i905 you will NOT get mobile data to work PERIOD. Flashing ICS based ROMs (CM9 or AOKP) that are marked compatible with the SCH-i905 (VZW) version of the GT 10.1 will result in that tablet becoming a WIFI ONLY device.
Until an official release is made there are no drivers available for the camera or the modem built into the LTE version which is why EVERYONE is waiting on camera drivers and all verizon tab users on contract are waiting on modem ones. Before anyone asks, NO the 3g modem driver for 3g models is not compatible with LTE.
Click to expand...
Click to collapse
Right I understand, but when you read what is and isnt working on the roms, and the only thing listed over and over and over again is the camera, you are likely to make a bad assumption that the LTE radio would work. I am not upset that it doesnt work, just wish the devs would do a slightly more comprehensive job detailing that the radio doesnt work.
I mean honestly if the rom is written with your tablet in mind, and besides and caveats you are already aware of, you would assume that the primary thing that sets your tablet asside from the rest.. would work.
I am just more disappointed that I have to wait for samsung to get off their lazy asses to make ICS a reality, I have a GNEX and am now spoiled by both ICS, and now JB, and really just cant wait to get my hands on them on this tablet.
Questions go in the Q&A section
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...