[Q] write nfc tags? - Galaxy S II Q&A, Help & Troubleshooting

i've not been able to find any details as to whether you'll be able to write nfc tags with this phone. i'm guessing it's gingerbread 2.3 which was read-only. it'll be a real bummer for me if it isn't write able
any one know anything about it?

MarkusPO said:
i've not been able to find any details as to whether you'll be able to write nfc tags with this phone. i'm guessing it's gingerbread 2.3 which was read-only. it'll be a real bummer for me if it isn't write able
any one know anything about it?
Click to expand...
Click to collapse
I think the SII doesn't come with NFC functions at all. I heard you can add an additional antenna to enable NFC but I don´t know how or if it works.

Related

Hacked Framework.jar

Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.

NFC on AT&T Version

I just picked up this phone... for the NFC capability........ but HOW DO I CONFIGURE AND USE this feature?
The battery has NFC written on it...
Can anyone help?
Thanx
It has the "capability" but it's not functional yet since there are no "official" apps to use it with. I assume Google will eventually release their app or someone will post an early beta or a hacked APK from some foreign device.
It's no in our phone's firmware yet.. It's built in, but we can't use it..
phoneman108 said:
I just picked up this phone... for the NFC capability........ but HOW DO I CONFIGURE AND USE this feature?
The battery has NFC written on it...
Can anyone help?
Thanx
Click to expand...
Click to collapse
Wait. AT&T removed a lot of the stuff required for usable NFC support from the firmware.
There's a thread with more info at http://forum.xda-developers.com/showthread.php?t=1289344

[Q] Faking Galaxy Nexus through Build.prop mod

Is it possible to edit the build.prop so that the market believes our device to be a Galaxy Nexus instead of the GS2?
I'm asking because I can't find any way to get Google Wallet to work on my device, and I'd really like to get it working. NFC is functioning fine on my Korean SGS2 but I can't really use it if Wallet isn't working...
Any help is much appreciated!
Do a search theres a mod in xda that got it working...
Nyssa1104 said:
Do a search theres a mod in xda that got it working...
Click to expand...
Click to collapse
I have nfc working, but no idea how to get google wallet / pay with phone functioning There is nothing in the sgs2 forum when i search for google wallet that actually gives a solution. Can you link it? I can't find it...
gs2 has NFC chip ?and how to enable NFC ?
the I9100p only has an nfc chip
TRY THIS
http://forum.xda-developers.com/showthread.php?t=1365360
http://forum.xda-developers.com/showthread.php?t=1286315
Nyssa1104 said:
TRY THIS
http://forum.xda-developers.com/showthread.php?t=1365360
http://forum.xda-developers.com/showthread.php?t=1286315
Click to expand...
Click to collapse
No dice, the first thread installed but it FCs right away and I can't get it run after that. I'm thinking this has to do with the device being the wrong name (nexus instead of gs2). I know they have a ton in common so I doubt there's a whole lot that I'd have to change to get this to work... any ideas how to take that APK and modify it to work, or maybe a build.prop mod that lies to the app?
se7en_boi said:
gs2 has NFC chip ?and how to enable NFC ?
Click to expand...
Click to collapse
Yeah, just the i9100p and the Korean variant (m250s/k)...

[Help]Any way to change the function of hard key?

My phone after installed the android rom..all things run well...
but...only the power button works but not others...it may be due to different model of a Hong Kong Phone from Europe/ US phone...anyway to give the keys back functions that they should have? thanks
Go to Spare Parts, and change the power key to home.
You should search first... Thx. Also, post in the ROM/Build thread!! That way we know what you're using, instead of having to guess...
Yes, I searched, peoples using spare part as well... but I just seen End button behaviour only in Spare Parts...no other keys...so I wonder whether there is any other methods.?
sorry for making such thread
waiwai567 said:
Yes, I searched, peoples using spare part as well... but I just seen End button behaviour only in Spare Parts...no other keys...so I wonder whether there is any other methods.?
sorry for making such thread
Click to expand...
Click to collapse
Oh, I thought you only wanted to change the end call key.
If you want to change around other buttons, you'll have to hack at the source. Depends on what you're running - on HaRET, you'd need to modify the keymaps in the rootfs. On NAND, I'm guessing the keymaps in /system/etc. Either way, this isn't something that's easily done nor recommended.
Maybe an app like this.
http://www.addictivetips.com/mobile/remap-reassign-your-android-devices-keys-with-buttonremapper/
wizardknight said:
Maybe an app like this.
Click to expand...
Click to collapse
Thanks, is that one support NAND?:good:
waiwai567 said:
Thanks, is that one support NAND?:good:
Click to expand...
Click to collapse
Well it does say, "As can be expected, the application requires complete root access, with a NAND unlocked device and complete, permanent write access to the system directory."
This is where you have to start to do a little research on your own.
wizardknight said:
Well it does say, "As can be expected, the application requires complete root access, with a NAND unlocked device and complete, permanent write access to the system directory."
This is where you have to start to do a little research on your own.
Click to expand...
Click to collapse
yes, thanks! it's my fault by only focusing the samsung galaxy stuffssorry

[Q] Using the setPreferredNetworkType method through reflection

I've been going over the android sdk for the past year to find out if there is a way to change the network type(2g/3g/4g), in phones with root access.However I couldn't find any way to do this.Asking around,someone told me that I could do this using reflection,by calling a method on a phone instance.Looking through the source code,I did find a setPrefferedNetworkType(); method in the Phone Interface,inside the internal telephony package.Is there anyway I can use this to solve my problem.I can't seem to find a way to get an instance of a class that implements the interface.Or is there any other way to do it entirely?Please help :crying::crying:
If u are rooted why not use Xposed?
Sent from my GT-I9300
Not clear on exactly what you are trying to do... The settings to switch to different network types should be built-in. They are on MOST phones. This is a useful app for other situations where you can't access those settings:
https://dl.dropboxusercontent.com/u/9903887/Apps/tellinfo.apk
I don't think you guys got what I was talking about.I know that there are built in settings to change it.But I want to build a widget that makes it easier to switch between networks.So I need to know how to do this with the api.
es0tericcha0s said:
Not clear on exactly what you are trying to do... The settings to switch to different network types should be built-in. They are on MOST phones. This is a useful app for other situations where you can't access those settings:
https://dl.dropboxusercontent.com/u/9903887/Apps/tellinfo.apk
Click to expand...
Click to collapse
I have been wondering the same exact thing. Did you maybe find correct answer yet ?

Categories

Resources