yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] Synner12:
Sorry, I meant the Nexus. Confusing my threads...heh.

According to what I have read, a phone needs to have the Secure Element chip in it. This is what differentiates it from ISIS. ISIS will sit on the SIM.

http://www.google.com/wallet/how-it-works-security.html

http://www.nfcworld.com/2012/03/02/...s-with-carriers-to-take-google-wallet-global/

That second link (where the quote is from) implies that the Secure Element chip is present in all Google phones, but not turned on by US carrier demand on everything but the sprint Nexus S and the Verizon Galaxy Nexus (although that wasn't turned on until recently).

I haven't been able to figure out if other phones have the chip. It stands to reason that they should if they can be used for Wallet in other countries since it makes more sense to just turn off the chip for US use rather than change manufacturing (although that does happen as well). So the premise of my question is still stands. Is there a way to tell if the chip in in the i717 or not? I suspect it isn't, and we would need to be covered under 'option 2' in the quoted article. But I would be happy to be wrong.
[AT&T Samsung Galaxy Note I717] kimocal:
Are you using the sticker rfid tags? If so which type? There are a couple types to choose from.
[AT&T Samsung Galaxy Note I717] cmucooper:
We are now on the same page. If this phone doesn't have a secure element chip in it I will be pissed off. I don't want ISIS. I wonder how we can find out about a secure element chip. Anyone have any ideas
[AT&T Samsung Galaxy Note I717] Synner12:
I think the the best possible scenario is for option 2 to come to fruition. That would allow Secure Element enabled SIM's to be used by Google Wallet rather than restricting them to just ISIS, or whatever other sim-centric scheme comes along. That would, in theory, allow Google Wallet to run on any android phone with NFC. Plus, peeps uncomfortable with Google's privacy practices could opt to use ISIS instead. Two options are always better than one.
[AT&T Samsung Galaxy Note I717] powdered_donuts:
has anyone tried to simply change the phone name in build.prop?
[AT&T Samsung Galaxy Note I717] cmucooper:
Interesting thought. Is there a guide.to do that someplace. I will try that out. I would think that now that I have NFC enabled if the chip is present, it should be enabled also. It's just a matter of getting Google Wallet to use it

I agree that would be ideal. I just want it now.
[AT&T Samsung Galaxy Note I717] Synner12:
It won't work, if what I've read is accurate. Editing build.prop will not activate the secure element chip. It will only fool the market into letting you download the app, which we can do anyway.

---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------

It would be possible, however, to create a ROM that can access the chip, if it is present on the Note in the first place. But if you read the Nexus forums, they are having all kinds of problems with 'bricked' secure element chips. They can lock out if misused and apparently it is extremely difficult to unlock them. The primary cause of the bricks is believed to be custom roms and a customized version of the wallet apk that is available here on XDA.
[AT&T Samsung Galaxy Note I717] cmucooper:
While I agree, the problem now is that the app says it's not supported. There could be multiple reasons for that. One of which could be that the app only looks for phone names that it recognizes as compatible. It's worth a try at least. If it doesn't work what harm could it cause?
[AT&T Samsung Galaxy Note I717] Synner12:
Editing build.prop is pretty simple assuming you are rooted. Just make a copy of the file in root explorer, then open it up and change the references to i717 to whatever the model number is for the nexus, or any other phone on which wallet works.

However, you should ask in QA what lines are safe to edit and which aren't. I've only done it once, on the infuse, and only changed two specific lines. You'll find more than two references to i717 in there (ive already looked at it), and I'm not sure if it's safe to edit them all.
[AT&T Samsung Galaxy Note I717] cmucooper:
Okay I will look at this later this week on my day off so if something happens I can easily go exchange the phone. Unless someone else comes up with something sooner.
[AT&T Samsung Galaxy Note I717] blnypny:
Yes the sticker tags. I got mine on Amazon from Web Evolved. They have all sorts of data sizes. I can get the phone to work with changing settings but not with Smart URLs or text tags. Those are more novelties anyway. I think there's still a portion of the phone that doesn't have those abilities unlocked or maybe it has to do with Gingerbread.
[AT&T Samsung Galaxy Note I717] powdered_donuts:
ill edit mine later on tonight ive messed with it before on other samsung phones. i need to find out how the nexus' name is shown in its build.prop under name to make sure i enter it the same way
[AT&T Samsung Galaxy Note I717] spec2323:
That would be great! NFC is enabled and Google wallet installed without having to trick it... now just need it to work :)
[AT&T Samsung Galaxy Note I717] alexige:
If I remember correctly att allows I think the gnexus to use Google wallet on it's network, or is it the nexus s carrier locked? I remember some months back seeing a story by engadget detailing this development.

EDIT: Found a story on engadget who source droid-life, guess it was only last month I swear I heard something months ago.

http://www.droid-life.com/2012/02/0...still-nothing-for-the-lte-variant-on-verizon/

Moral of this post at&t allows google wallet on one phone there is hope for us yet!
[AT&T Samsung Galaxy Note I717] californiarailroader:
http://www.droid-life.com/2012/03/05/google-wallet-now-showing-as-unsupported-on-rooted-devices/

It looks like Google is working towards ending use of Wallet on Rooted devices.
[AT&T Samsung Galaxy Note I717] tylerdurdin:
Google wallet and NFC are a ways off yet....we went through this same thing with the S2....I realize they are not the same phone but the problem is the same. Read the two pages of this thread.....especially Entropy512s posts....

http://xdaforums.com/showthread.php?t=1477987

Sent from the baddest cellphone ever made.
[AT&T Samsung Galaxy Note I717] cmucooper:
No that's a way Google can cover their asses if you have a rooted device, run Google wallet and get you stuff hacked or stolen. It would be like them saying it's your fault we told you not to do it.
[AT&T Samsung Galaxy Note I717] lowlidx50:
So it appears that some of the apps that we can now download will scan or read nfc. Is it possable to just scan your nfc enabled credit card and store it then share it at a nfc or paypass card reader at the retailer.
[AT&T Samsung Galaxy Note I717] cmucooper:
Did you have any success?
[AT&T Samsung Galaxy Note I717] kimocal:
I tried reading my amex blue card but nothing was seen.

Sent magically through the air from the mighty Note!
[AT&T Samsung Galaxy Note I717] kimocal:
Which exact ones did you buy? Will all the ones for the Galaxy Nexus work? I sent an email asking the company but never received a response :-P

Sent magically through the air from the mighty Note!
[AT&T Samsung Galaxy Note I717] blnypny:
I ended up splitting a pack of 10 of the 48byte ones with a buddy that has a Galaxy Nexus and they work on both of or phones. I don't recall the exact ones so I'll have to check and reply back tomorrow.

I would suggest getting some bigger ones depending on what you plan on doing. With the 48byte ones you can't write much to them. You can fit a couple commands on them though.
[AT&T Samsung Galaxy Note I717] blnypny:
Here's the ones I purchased...

http://www.amazon.com/gp/product/B005UIQVB4/ref=oh_o03_s00_i00_details
[AT&T Samsung Galaxy Note I717] lowspeed:
So can you use this to put an nfc tag on your car cradle and enable the bluetooth everytime is near it?

That would be cool.
[AT&T Samsung Galaxy Note I717] kimocal:
Awesome thanks for responding. I'm just planning on using them for NFC Launcher & Tasker so probably can get away with the cheapers ones for now.

---------- Post added at 12:03 PM ---------- Previous post was at 11:58 AM ----------

That's the idea. Either you need to keep NFC enabled (drains battery a bit) or setup a shortcut to temp turn on NFC for X amount of time to allow you to tap and read the tag to activate something.

You can also use them for when you put your phone on your bed night stand to put your phone in "Night time mode" OR when you get to work to set specific volume levels OR even have it trigger something like send a WOL to your home computer.

One idea I want to implement is when I am taking a shower trigger a profile to route audio to a bluetooth receiver/speakers rather than have to play the audio from the phone speaker.

Lots of things you can do especially coupled with Tasker.
[AT&T Samsung Galaxy Note I717] lowspeed:
So how do i download any app? the market doesn't allow me to download any NFC app to the note...
[AT&T Samsung Galaxy Note I717] kimocal:
What phone do you have? Are you running stock or a custom ROM? If you have an AT&T Note you need to install Saurom (see my sig) to enable NFC in it as AT&T has it disabled in the stock ROM. It could also be tied to your prop ID as the Candian version is i717R and already has NFC enabled. If the market sees your phone is just the i717 then AT&T may have any NFC stuff not allowed much like tether apps.
[AT&T Samsung Galaxy Note I717] lowspeed:
Ah yeah running stock with dg kernel...

I didn't have good luck with Saurom, maybe i'll nandroid my current state and check out Saurom again.
[AT&T Samsung Galaxy Note I717] nm3th:
I'm stock and dag OC 0.2 kernel. I enabled nfc using the xml file and am able to dl nfc apps from the market. No custom ROM needed.
[AT&T Samsung Galaxy Note I717] kimocal:
I went re-read the OP and that is correct. My bad. Too many NFC threads to remember :D
[AT&T Samsung Galaxy Note I717] id_mew:
TC, I followed your method and now I have NFC in the wireless and networks menu.

Thanks a lot!
[AT&T Samsung Galaxy Note I717] lowspeed:
anything in normal stuff at home this should read ? tried credit cards with nfc but it doesnt do anything.
[AT&T Samsung Galaxy Note I717] blnypny:
As far as I know it can only read/write tags. That's not set in stone, just saying I haven't heard of anything else. I haven't tried transferring data from one phone to another using NFC yet but I'll be trying that next week.
[AT&T Samsung Galaxy Note I717] bykr_dude15:
I tried using android beam but it didnt work... I never did anything with changing the files because I am guessing hybrid rom has nfc enabled already and nothing happened.
[AT&T Samsung Galaxy Note I717] Froid:
Here's a flashable zip that adds the nfc tags app to your phone.

http://xdaforums.com/showthread.php?t=1545751

Sent from Galaxy Note
[AT&T Samsung Galaxy Note I717] r_avital:
Just to confirm

Just to confirm, folks: Rooted AT&T i717 (U.S.), created file on my desktop with the contents specified on opening post, named it as specified, copied to the correct folder, rebooted phone, I now have the NFC option in "Settings->Wireless and Networks, right below "VPN settings" and above "Mobile networks."

However, when I went to the Google Android Market, attempted to install NFC Task Launcher, it still insisted that my device was not compatible.

Removed the XML file, and used CWM to install g_note_nfc_on_fox689.zip, this brought back the NFC option above in settings, and allowed me to install the app from the market.

Off to buy some cheap tags to test this out. Schweet. :fingers-crossed:
[AT&T Samsung Galaxy Note I717] Atrix2destroyer:
NFC works stock with many JB ROM's out right now. For instance i have PA 2.54 and NFC already has a toggle within my setting and android bean is available as well. As far as getting google wallet to work, I've been unable to do so. There is a trick when you edit your build prop to make the market think your running a nexus device but it still doesn't work even if you od that. I believe we may not get it to work on our phones
[Android Software/Hacking General [Developers Only]] bgcngm:
I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.

Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:

export TERMINFO=/system/etc/terminfo
export TERM=linux

Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).

It works flawlessly over ssh, although. :D

EDIT: Fully working version is here.
[Android Software/Hacking General [Developers Only]] M66B:
You will need this patch to fix the enter key:

https://github.com/Evervolv/android...b568f0b417c1fe3fe8597c600bdbcda4837013f.patch
[Android Software/Hacking General [Developers Only]] bgcngm:
Great! Thanks for the information. :good:

As soon as I have time for that I will apply the patch and release a new binary.
[Android Software/Hacking General [Developers Only]] M66B:
You are welcome.

I guess you will like this patch too:

http://www.faircode.eu/freexperia/update/terminfo.patch

(I have composed it for CM9, but I guess you known how to modify it, when needed)

Edit: use git apply instead of patch
[Android Software/Hacking General [Developers Only]] chepe263:
how do i install this in my phone?
[Android Software/Hacking General [Developers Only]] bgcngm:
ARM cross-compiling how-to

Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:

Set the path to C compiler:

export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc

After you have unpacked the sources change to the source directory:

cd nano-2.2.6

Now configure the source:

./configure --host=arm-none-linux-gnueabi

To compile the sources (statically) type this:

make LDFLAGS=--static
[Android Software/Hacking General [Developers Only]] bgcngm:
Here is the fully working version of Nano 2.2.6 for Android (without the [enter]-key bug). Enjoy. :victory:
[Android Software/Hacking General [Developers Only]] osm0sis:
Great job!

I went ahead and packaged this in a flashable zip for people, it also adds a script to /sbin so you can (temporarily) use nano from the recovery console in AROMA Filemanager during that recovery session. :)

http://xdaforums.com/showpost.php?p=47402916&postcount=133
[Android Software/Hacking General [Developers Only]] bgcngm:
Good idea! Thank you. ;)
[Android Software/Hacking General [Developers Only]] osm0sis:
[MENTION=455439]bgcngm[/MENTION] Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things. :)

Mention me back when you get the chance.
[Android Software/Hacking General [Developers Only]] daboss5:
How do I exit Nano in the android Terminal emulator

Edit: I found out hacker's keyboard's ctrl key helps with this problem
[Android Software/Hacking General [Developers Only]] idoit:
If anyone has this issue, let me help out:

In Windows, running nano and vim through ADB returns weird characters on the terminal, and you need ansicon.

Or better use ConEmu.
[Android Software/Hacking General [Developers Only]] bgcngm:
That's right. It is documented on the internet, that Ansicon is a requirement for Windows if you use command prompt. As you say, better go with a good terminal emulator.
[Android Software/Hacking General [Developers Only]] killoid:
[MENTION=455439]bgcngm[/MENTION] will u update it to v2.4.2 plz?
[Android Software/Hacking General [Developers Only]] mc510:
Just tried to install through CWM on Cyanogenmod 10.1 Unofficial for Samsung Infuse, and got "installation aborted." Any idea what my problem might be?
[Android Software/Hacking General [Developers Only]] bgcngm:
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
[Android Software/Hacking General [Developers Only]] osm0sis:
Fixed both of these issues and compiled nano 2.5.0. :cowboy:

http://xdaforums.com/showthread.php?p=64247691#post64247691
[Android Software/Hacking General [Developers Only]] CipherSwami:
If you are a termux user and want to install a nano or vi or any other binaries of termux in Andriod su mode. Here is the link to Termux superuser.

Give it a star if it was helpful !!!
[Android Software/Hacking General [Developers Only]] rahaaatul:
How to do this on termux? @bgcngm I got the latest 6.4 tarball.
[Barnes & Noble Nook Tablet] RobWoodall:
I'm loving my newly-rooted Nook (Albert Wertz SD card method).

I'm not really into the Barnes and Nobel ecosystem, and have no need to maintain compatibility with it.

I know the NT is still fairly recent but, at the moment, what is the closest ROM to pure Android? ICS would be wonderful, of course, but I like Gingerbread and Honeycomb as well.

Thanks in advance!
[Barnes & Noble Nook Tablet] Cubanluke88:
CM7 (gingerbread) alpha is out, head on over to android development to find it. There is also a soft modded version of it and an MIUI (gingerbread based as well). CM9 will be ICS (android 4.0) but its still in development (no public release yet). There won't be any honeycomb rom as ICS is basically honeycomb without the **** and support for tablets/phones and a few added features.

tl;dr check out CM7
[Barnes & Noble Nook Tablet] RobWoodall:
Thanks! I had good luck with CM7 on my G-Tab, so I figured that's where I'd end up.
[Nexus S Q&A, Help & Troubleshooting] plaguethenet:
Has anyone been able to extract amss.bin from radio.img? Or the efs filesystem (Not the same as /efs btw.)?

Would anyone be interested in helping me rip apart a radio image?

I've googled around looking for any instances of extracting the radio firmware from radio.img and have come up with nothing.

More information for those who know less about the baseband:

What is it?

AMSS is the name Qualcomm gives the software that runs the phones modem. When the modem software is compiled, it is encrypted and stored in a file called amss.bin. There is a small entry point in amss.bin which decrypts the image into the phones memory during boot and then executes it.

What does it do?

Its job is to find, connect, and decode cell phone signals and convert them to usable data. In most older cell phones the phones operating system was a part of this as well, but with android the modem runs along side android (Question: Is it a separate processor for the baseband? or is it somehow multiplexed with android on the main CPU?)

This software reads settings that were set either by the phone itself (2G/3G or 4G data, PRL on cdma, APN settings, and other radio related things.) or by the carrier/manufacturer (NVRAM) and changes its behavior accordingly.

It then accepts commands and gives responses to another piece of software (In this case android) which does something useful with the phones modem. (Dials a phone number, connects to a data service, etc) and lets the software know when events happen (Text messages, incoming calls, etc)

The modem firmware (amss.bin) is inside radio.img for the nexus s 4g, This much should be blatantly obvious. However, the phones EFS filesystem (FAT12 IIRC) is also located here as well. radio.img may be encrypted or compressed, (Why it takes so long to flash a radio update to the nexus s 4g)

Why?

With access to amss.bin it can be decrypted and disassembled to show the phones true inner workings, and I may be able to develop a solution to the absolutely terrible data speeds for the nexus s 4g (No matter where I go, with 3 different D720's now, I get 56k dialup speeds and once in a great while it will go up to 3g, unless I'm sitting right next to my airave.) or at least have an insight as to why this phones data is so slow.

How do you know all of this?

I originally tried to get android running on a Samsung Eternity, I was able to decode the first part of AMSS.BIN but then realized that writing the radio interface layer for android was going to be a real challenge, not to mention that the phones hardware was barely capable of running 1.5 (And by barely I mean not really capable at all). But I learned an awful lot about the internals of Qualcomm phones along the way, and even wrote a small utility to edit the boot images and EFS filesystem (In this case, EFS also held the OS itself, not just the radio stuff)
[Nexus S Q&A, Help & Troubleshooting] Harbb:
Great read. I have no experience in this, nor any worthwhile software experience so I doubt i can help you, but if you think I can just let me know. I havn't experienced any particular issues on my GSM Nexus though. It's not like I get to use data very often anyway considering how little data i have and the state of Vodas current data network.

Question: Is it a separate processor for the baseband? or is it somehow multiplexed with android on the main CPU?

Answer: On phones like the Nexus S where the "Sleep" state (and even "Deep Idle" state) shuts off the CPU entirely, there must be a seperate low-power processor just for decoding and sorting through cell signals. This, in turn, will wake up the main CPU when something happens (call, text message, push notification, etc). That should clear a little up for you.
[Nexus S Q&A, Help & Troubleshooting] NS4G.John:
If I had skills required I would gladly help you, But I don't. It seems like you have done your homework, and done this before, so what exactly do you need help with? Re-writing it?

By the way that was a very interesting read!
[Nexus S Q&A, Help & Troubleshooting] mabry:
Very good read, and useful info. Have you tried mounting the radio.img in Linux, yet? I don't know exactly how to do it, but you should be able to. I run Linux dual booted with Windows, and have mounted the system.img no problem. I tried with the recovery.img, but no luck. I think you have to mount it as another filesystem.
[Nexus S Q&A, Help & Troubleshooting] plaguethenet:
I doubt that radio.img would mount, Android is based on linux and uses linux filesystems. The radio is different, its more the same class as a bootloader (or rather, somewhere between). It does have a filesystem in that radio.img, but its likely encrypted.

Mar 15 17:45:28 localhost kernel: EXT3-fs (loop0): error: can't find ext3 filesystem on dev loop0.
Mar 15 17:45:28 localhost kernel: EXT2-fs (loop0): error: can't find an ext2 filesystem on dev loop0.
Mar 15 17:45:28 localhost kernel: EXT4-fs (loop0): VFS: Can't find ext4 filesystem
Mar 15 17:45:28 localhost kernel: SQUASHFS error: Can't find a SQUASHFS superblock on loop0
Mar 15 17:45:28 localhost kernel: FAT-fs (loop0): bogus number of reserved sectors
Mar 15 17:45:28 localhost kernel: FAT-fs (loop0): Can't find a valid FAT filesystem
Mar 15 17:45:28 localhost kernel: FAT-fs (loop0): bogus number of reserved sectors
Mar 15 17:45:28 localhost kernel: FAT-fs (loop0): Can't find a valid FAT filesystem
Mar 15 17:45:28 localhost kernel: ISOFS: Unable to identify CD-ROM format.
Mar 15 17:45:28 localhost kernel: hfs: unable to find HFS+ superblock
Mar 15 17:45:28 localhost kernel: hfs: can't find a HFS filesystem on dev loop0.
Mar 15 17:45:28 localhost kernel: ufs was compiled with read-only support, can't be mounted as read-write
Mar 15 17:45:28 localhost kernel: UDF-fs: warning (device loop0): udf_load_vrs: No VRS found
Mar 15 17:45:28 localhost kernel: UDF-fs: Rescanning with blocksize 2048
Mar 15 17:45:28 localhost kernel: UDF-fs: warning (device loop0): udf_load_vrs: No VRS found
Mar 15 17:45:28 localhost kernel: UDF-fs: warning (device loop0): udf_fill_super: No partition found (1)