yashsingh1/xdaforums huggingface dataset:
[AT&T HTC One (M7)] bdorr1105:
I have seen instances where it has worked on viper with screen shots....

The Sprint One has the secure element it's not blocked by the carrier and my boy has it. You can try trial 1 and flash the zip it has the libs from sprint off a 4.1.2 based Rom. I would do a nand back up incase it puts you in a boot loop. Give trial 1 a try.
[AT&T HTC One (M7)] ElBeaner:
Trial one, stuck at the HTC screen with th red text. Won't boot further. Restoring NAND flash and will try the second file.

EDIT I held power + volume down to do a hard reboot and it booted up normally then. Trying wallet now - will take a sec

---------- Post added at 02:57 PM ---------- Previous post was at 02:53 PM ----------

Ok file 1, same results - sits there and then says wallet has stopped.

Going back to recovery, will flash the nand, then flash file 2 and try again.
[AT&T HTC One (M7)] bdorr1105:
So you are getting all the way to the end where you set up wallet and the app force closes? What Rom are you on?
[AT&T HTC One (M7)] ElBeaner:
I'm on ARHD 12.1 4.2.2

Yes tried without libs, app force closed, tried first file - phone hung on reboot, hard reboot allowed it in, app force closed.

File 2 you posted I am trying now. I'll know more in approx 5 min

---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------

Second file, same issue - App opens, sits there on the Setting up Wallet, this may take up to 5 minutes and then force closes (ie Wallet has stopped)

---------- Post added at 03:22 PM ---------- Previous post was at 03:09 PM ----------

I'm available for testing most weekdays during work hours. I'll keep an eye on the thread to see if you post any other methods for a 4.2.2 based rom.
[AT&T HTC One (M7)] bdorr1105:
Before you do a nand restore, I have a different nfc access xml
[AT&T HTC One (M7)] bdorr1105:
With the zip already flashed, I want you to push this http://db.tt/TGsDomgq

Place it in system/etc and change permission to rw-r-r..... Do a reboot and double check nfc is on and see if it will let you set up. Just let it force close out..

I had my boy wit a sprint HTC one send this with a working wallet already set up
[AT&T HTC One (M7)] ElBeaner:
Already did a restore, but I will try again. 1 sec need to redo my build prop back to Galaxy Nexus.

Ok, redid the build prop back to Galaxy Nexus.

Flashed the 4.2.2 zip(method 2), and pushed the file to system/etc and updated the permissions and then rebooted. NFC was on(when I check system)

Tried to setup Wallet and same issue, just sits there until it force closes but it did not have the little pop up that said Google Wallet had stopped.

I'll be able to do more testing tomorrow since I'm leaving the office now. Thank you for trying, and I hope that you(we) are successful

Also one thing to note, my battery % was 50 before pushing the file and rebooting and after pushing the file and reboot it went to 36%. Not sure what happened there, it was a quick reboot.
[AT&T HTC One (M7)] bdorr1105:
That is weird thanks for trying, the last thing I would suggest is when you restore is do not flash any libs just do the root explorer and push that same xml file I gave you the link to and do the whole build prop like you were doing. Thanks for all the testing
[AT&T HTC One (M7)] ElBeaner:
Ok tried that as well and no go. Forced close
[AT&T HTC One (M7)] bdorr1105:
Sorry Bro I am def trying for some answers...Getting help from the smart dudes who figure out the s4, sent them framework and the nfc from Sprint to try and cover for all for 4.1.2, 4.2.2 and 4.3
[AT&T HTC One (M7)] bdorr1105:
Updated OP

Updated OP​

- Moved Original Trial 1 to Trial 3

- Added new Trial 1

Hoping that this patched version will not force close and maybe something isnt working 100% properly with Xposed and Modaco....Hope there is a success somewhere. Best chace is with a 4.1.2 ROM but who knows this def possible to work on 4.2.2 as well
[AT&T HTC One (M7)] greenrocks:
Gave it a try. Did method #2. Open Wallet, got 'Setting up Wallet, this might take up to 5 minutes' for a while and nothing happened. Manually closed app and reopened few times. Same result.

This was done on Elgancia v8.0 ROM.
[AT&T HTC One (M7)] ElBeaner:
Tried new method 1 - still same results on a 4.2.2 rom - force close with no popup message. We need someone with a 4.1.2 rom to get in here and try.
[AT&T HTC One (M7)] greenrocks:
Tried method #1. Same. But from FC, that Wallet closed by itself.
[AT&T HTC One (M7)] bdorr1105:
This is all weird to me because If the libs werent correct you would an isufficient keys (RSA) are missing, like when you get to the Set up Portion or Wallet Won't even open...I wonder if trying the Sprint build.prop would work versus the Galaxy Nexus
[AT&T HTC One (M7)] ElBeaner:
No I seriously think it is because the GSM models lack a secure element.

http://www.nfcbrief.com/2013/06/htc-one-google-edition-lacks-google.html

The GE of the HTC is internally identical to the Developer, International, AT&T and T-Mobile varients. The only model that is different is the Sprint HTC One which has led many people to believe that the GSM models lack the secure element.

http://xdaforums.com/showthread.php?t=2272402&page=12

Here is another article on the matter

http://androidandme.com/2013/07/app...-nfc-secure-element-no-google-wallet-support/

Another article referring to no secure element.

http://blogs.computerworld.com/android/22397/galaxy-s4-htc-one-google-play-editions
[AT&T HTC One (M7)] bdorr1105:
Thanks for the info bro, I guess I was mis informed, if Google switches to API then that will be the only hope, fu*k HTC for doing that, all variants of the s4 have the secure element, that will be the slow death of HTC yet again being retarded
[AT&T HTC One (M7)] ElBeaner:
I'm always here for testing just in case(in the hopes of I guess) that they are lying to us.
[AT&T HTC One (M7)] bdorr1105:
I don't think the NFC chip would come without the secure element, maybe it has I just dont see how they reacted so fast because these phones were in production before Sprint even allowed Wallet, its the same exact NFC chip in all the HTC One's, however, I do believe that it can be disabled, I am doing research but I still feel there is a glimmer of somewhere...It would make no sense, The NFC Chip is the hardware, the secure element can be turned on or off....More to follow, am doing a lot of research and seeking help
[AT&T HTC One (M7)] Trinition:
Actually, some other threads have said it's NOT the exact same chip. Same family, but slightly different model number with the biggest difference being the secure element.

And after reading about what a secure element is, I can see why. A secure element isn't just an isolated bit of flash memory, but almost a mini-computer in and of itself.

That said, I doubt Google Wallet is growing wires to this chip. It's calling through an API or driver, and those are themselves code. So surely someone can gut the API implementation to fake it, or provide a fake driver, or something to trick Google Wallet into thinking it Does have a secure element.
[AT&T HTC One (M7)] bdorr1105:
That all makes sense unless Sprint knew they were going to allow Google wallet before the production of this phone and they planned it before they allowed Wallet, I find it weird but it probably is the case that the other phones don't have it, however isis also requires a secure element so what's different. If it's built in the SIM why would you not be able to force wallet to use the secure element, if the phone lacks the secure element than isis also can't work..... Thanks for the info sure is helpful and eye opening
[AT&T HTC One (M7)] Trinition:
SIM Secure vs. NFC Secure

There are actually three types of secure elements, so far as I've learned:

Embedded (internal chip, e.g. NFC, such as Spring HTC One)

SIM

SD Card

But these aren't just transparently interchangeable options. The Secure Element specification includes distinguishing between these. So an application developer can make their application look for a specific type of secure element, not just *any* secure element.

So Google Wallet specifically looks for an embedded secure element, while Isis applications will look specifically for a SIM secure element (they wouldn't dare trust a secure element that they, themselves, don't control!).

So it's not just whether a phone has/doesn't-have a secure element, but does it have the *type* of secure element that the application in question needs.

DISCLAIMER: I'm *not* an expert... just a computer geek who read a couple of lofty PDFs about secure elements when I was asking the same questions you are now.
[AT&T HTC One (M7)] bdorr1105:
Yea I happen to read that as well... It's all making sense except for sprints reaction to the phone, how could they have all that time to recall all manufacturered phones already pre wallet being allowed.... They managed to just out of no where get it to work?
[AT&T HTC One (M7)] tjsooley:
Sprint HTC one Uses CDMA sim cards like Nextel used to. Thoes Sim cards have the secure element not the one itself.
[AT&T HTC One (M7)] Trinition:
Same phone, different NFC chips

That information is different from information provided in other threads/forums. I read elsewhere that the NFC chips in the Sprint model and AT&T model differ. It said the NFC chips come from the same manufacturer, but are two different models in that family.

Here's another XDA Thread which talks about it. And another. And another. The latter says,

"There is a crucial difference between the GSM (T-mobile / AT&T) and CDMA (Sprint) versions of the HTC One. The CDMA version has the NXP PN65 NFC Chip this version supports SmartMX which is the secure element that is necessary for Google Wallet to work. The GSM version has the NXP PN544 which does not support SmartMX so there is no secure element and no Google Wallet support. It appears we are crippled at the hardware level and it is doubtful any development will be able to remedy that, short of somehow emulating SmartMX or actually replacing the NFC Chip"

Here's NXP's leaflet on the NXP PN544 NFC Controller. And here, NXP seems to support the above:

"NXP technology is available in a variety of form factors including standalone NFC radio controllers such as the market leading PN544, a stacked NFC radio and embedded secure element solution such as the Google Wallet enabling PN65 - See more at: http://www.nxp.com/campaigns/nfc/nxp-solution#sthash.cmvzC7FO.dpuf"

So do we have a PN544 in the AT&T HTC One? See the iFixIt Tear Down, page 2, step 10. Here's the 'huge' image. Note the chip labeled with the NXP logo and number 65012.

Is that a PN544?
[AT&T HTC One (M7)] ElBeaner:
Very good information. I can see HTC from the get go designing the GSM models with no Secure Element. Since AT&T and T-Mobile both block Google Wallet on all devices(aside from Nexus devices) and Google Wallet really is US only right now. There is no point in sourcing a more expensive NFC chip when it's not going to be used.

Sprint has always been generous to GW support(they have 9 out of 14 eligible phones that work on GW without any mods)

Now the kicker here, will the Verizon HTC One have GW supporting NFC chip(VZW alos likes to block GW)
[AT&T HTC One (M7)] anit77:
If Att/Tmo has the PN544, which appears to be the case, then there is no way to get it working short of emulating SE to the apk. Which would open the door to security concerns down the line.

Here is the break down of the Nexus S, Step 7 shows the NXP NP65 chip. It is definitely different than the one in our handset.

Lastly here is more info on the 2 chips. BTW these are BGA chips...

Sadly, it looks like we are SOL. :crying:

*Edit* Does this offer a ray of hope???

"From an integration point of view it does not make any difference if the handset manufacture uses the PN544 or the PN65 as both chips have the same interfaces and use the same PIN. The only difference is the SmartMX with is included in the PN65 which can not be contact from outside the chip."
[AT&T HTC One (M7)] tjsooley:
Looks like it doesn't matter anyway.

http://www.androidpolice.com/2013/0...rt-for-gift-and-loyalty-cards-on-august-21st/
[AT&T HTC One (M7)] K.AuthoR:
If it does indeed have a secure element, and someone can get this working, we would still have the ability to use the mobile payments stuff.
[AT&T HTC One (M7)] gunnyman:
There's no secure element and Sprint is Google's partner for wallet in the US so of course they made sure it would work on the sprint htc one.

There's no amount of hackery we can do to make it happen.

Want wallet? Buy a nexus. It is just that simple
[AT&T HTC One (M7)] Trinition:
I've heard about other chip manufacturers who produce one chip but multiple products by "cutting" the connection to sub parts of the chip. Probably through some sort of intentional weak point that they can overload with a shot of current or something like that.

They do this because, in the end, it's cheaper to have one assembly line where you cripple a portion of the products to make a second, lesser product. Then alternative is to build 2 assembly plants which is very expensive.
[AT&T HTC One (M7)] tagno25:
I have a T-mobile HTC One with 4.1.2. Neither method 1 or 3 worked for me. Wallet just force closes after a few minutes.
[AT&T HTC One (M7)] bdorr1105:
Thanks for trying but I guess from a lot of what we are reading is that the secure element that Wallet needs was not included with any of the HTC One phones except Sprint...Obviously we are still looking for workarounds, but it may never happen
[AT&T HTC One (M7)] ElBeaner:
Well CM found a way to do an NFC payment

https://play.google.com/store/apps/details?id=com.tapp&hl=en

But it force closes on anyhting but a CM rom :crying:

http://www.xda-developers.com/android/simplytapp-nfc-payment-system-debuts-with-cyanogenmod-9-1/

http://www.simplytapp.com/

http://www.cyanogenmod.org/blog/cyanogenmod9-1-and-simplytapp

Now if you could pull the NFC info we need from CM roms and allow to integrate into Sense based roms so we could use that app - that would be awesome.
[AT&T HTC One (M7)] bdorr1105:
Has this simply app been used on a HTC One with CM Mod other than on a Sprint Variant?
[AT&T HTC One (M7)] erandhawa:
Very dissapointing that HTC did this with GSM models. I do know AT&T is partnering with ISIS and the secure element is on the actual sim card, so if you live in Austin or Salt Lake you can actually go get the chip. Now what I don't know is if we get a sim with a Secure Element on it can we maybe get Google Wallet working by using the Secure Element on the sim card as the ISIS app does.
[AT&T HTC One (M7)] David111jr:
This is a possibility but why not just try isis.

Everyone is all over Google wallet. Maybe isis will put some pressure on Google since it did just sign up chase and American express lol
[AT&T HTC One (M7)] ac3kill:
Well we don't have either and that is just unacceptable
[AT&T HTC One (M7)] erandhawa:
I have no problem trying ISIS but AT&T and ISIS need to make it available to the general public first. They have been in test markets for a very long time.
[AT&T HTC One (M7)] orb3000:
On topic

Please keep on topic and with respect
[AT&T HTC One (M7)] ElBeaner:
Isis won't work if you're rooted(until somoeone can modify the apk to bypass the root check).
[AT&T HTC One (M7)] erandhawa:
I remember there is an app that makes other apps think your phone isn't rooted. I'd have to search for it but I remember using it with google wallet to get rid of the unsupported device message (the app wasn't xposed mod), it actually made your phone act as though it wasn't rooted until you re-enabled it, and no reboot was necessary.
[AT&T HTC One (M7)] TabascoJoe:
I live in Salt Lake...

I picked up a Secure Element SIM. Due to me being on Premier and my company not wanted to test Isis I can't use the SIM

My question is... who wants it. If this is the missing key to porting Google Wallet to the att HTC One, I am willing to give it to a dev who can take full advantage of it.
[AT&T HTC One (M7)] homeslice976:
So now that we have KitKat available (unofficially, in it's infancy), I was looking forward to being able to use (or at least play with) tap and pay via the HCE available in 4.4 on my ATT One. I was upset to find that the Tap and Pay setting still wasn't available, so I started digging a little. I found, in source, this wasn't simply something that was displayed or not displayed. Settings looks first for whether or not there is NFC available, if so, it adds the NFC settings options. Then, it checks to see if the DEVICE supports HCE (which confuses me as I thought this was built in to 4.4 for any NFC enabled device, not dependent on the NFC enabled device), if it does, it will display the Tap and Pay settings, if not, it will simply not display it. I modified the source so that it skips the second check, and would display the Tap and Pay settings no matter what, which it did. Trying to open Tap and Pay would crash settings. In a logcat of the crash, I found this beauty:

E/CardEmulation( 5325): This device does not support card emulation

Do we suppose card emulation is something that hasn't yet been merged to CM source, or yet another limitation of the PN544 chip? Or, with the national rollout of ATT's ISIS mobile wallet a few days ago (http://www.hispanicbusiness.com/2013/11/15/at_t_smartphones_stores_ready_for.htm) I wonder if the new SIM would allow for card

Edit: A few hours after I posted this, this change was committed:

https://github.com/CyanogenMod/andr...mmit/66f728d13fabd899e2828c6559fd10d115db88ab

Building now, will report results.

Tap and Pay options are there, Google Wallet is telling me tap and pay is ready!!!
[AT&T HTC One (M7)] Simba501:
In case anyone missed this.

Google Wallet app update brings support for all Android phones on version 2.3 and up
[AT&T HTC One (M7)] homeslice976:
What they're not telling you:

This according to entropy512... and according to all tests done on our 4.4 builds, and others who have 4.4 with NXP controllers :

This confuses me though - doesn't the Sprint version have an NXP controller as well? I know it's a different revision of the PN544 the rest of us have (with a secure element), but I thought it was still a NXP controller. If that's the case, did Google break Wallet for them in 4.4? Or will it just default to using the SE?

Edit: Just found this (http://xdaforums.com/showthread.php?t=2534238) thread where vzw motox users have confirmed it working. This gives me hope as they use a pn544 nxp nfc controller.
[AT&T HTC One (M7)] @moe:
Option 1 worked like a charm for me thanks
[AT&T HTC One (M7)] bdorr1105:
For real, what Rom are you running, I have not updated this in forever and it worked for you?
[AT&T HTC One (M7)] @moe:
im on stock (rooted) 4.1.2 sense 5.0 1.26.502.10 .. .. after i edited the build to nexus i put the wallet.apk in system/apps changed the permissions then i flashed the zip booted up and then used es file explorer to open the .apk because i couldnt get it to install for some reason when es file explorer opened it up it also installed it or something then i opened wallet setup the tap to pay then it said failed to setup tap to pay so i edit the build back to m7 then rebooted and bingo bango it worked
[AT&T HTC One (M7)] bdorr1105:
Is tap and pay there? It should not be there because there is no hardware secure element
[AT&T HTC One (M7)] @moe:
yah its there .. but i havent actually tested it yet.. could be a fluke
[AT&T HTC One (M7)] compta5:
So i'm running InsertCoin 7.0-2 firmware 4.4.....i got a update notification from play store saying there was an update to google wallet. i updated and now it gives me the option to do tap to pay. i set it up but now i have to go to a store to see if it really does work. i'll update if successful or not.
[AT&T HTC One (M7)] compta5:
Can confirm it is working on my end. I have a tmobile Isis SIM card as well.
[AT&T HTC One (M7)] bdorr1105:
OK so you are on version 4.4, makes sense, you don't need anything special... Wallet works right out of the box... All you have to do is download directly from the market
[AT&T HTC One (M7)] Entropy512:
If it's AOSP-derived and all they did was enable the HCE perms - you'll most likely find the device nonresponsive at the payment terminal as AOSP lacks HCE support for devices with NXP NFC controllers.
[AT&T HTC One (M7)] shogunmark:
I am running a different rom from a different dev.. but its a 4.4 sense 5.5 rom and wallet with tap and pay works right out of the box, no mod was needed. I verified it today when i paid for lunch.
[AT&T HTC One (M7)] homeslice976:
Has also been verified working at the terminal on official gpe 4.4 (and those Roms based on it)
[AT&T HTC One (M7)] enchanter100:
Tap and pay working for me on GPE 4.4 and updated wallet.. Loving it!
[AT&T HTC One (M7)] ElBeaner:
Working on ARHD 40.3 with no mods
[AT&T HTC One (M7)] bdorr1105:
If you have android 4.4 it works out of the box with host card emulation built in Stock not requiring a hardware secure element
[AT&T HTC One (M7)] pacDiesel:
I got a notification

saying that 'Tap and Pay' is now available but the UI hasn't changed.. Also when I go to settings it says that 'Tap and Pay' isn't started.

Any thoughts on how to set it up? Currently driving on ARHD 4.4 and 5.5
[AT&T HTC One (M7)] bdorr1105:
Different you make sure nfc was turned on, there is also an nfc hce xml floating out there that you need to possibly copy into system/etc. Look in the S4 threads for loser skaters thread
[AT&T HTC One (M7)] 2010ngojo:
You used the same method as the AT&T HTC One I assuming? I also have a T-Mobile HTC One and want to try this out.

Update: Method 1 does not work for me. Wallet just crashes while setting up in the beginning. Using stock T-Mobile HTC One 4.1.2

Update 2: Same problem as above with method 2.
[AT&T HTC One (M7)] Laughing Danny Elfman:
I'm using CM11 Nightly 14/2/13 on my AT&T HTC One, but while I can install Google Wallet straight from the store, with NFC on Tap and Pay is grayed out and says "Not available" in the Google Wallet settings menu.
[AT&T HTC One (M7)] KennyG123:
Thread closed at OP's request
[General Topics] fychan:
Hi Anyone currently using Intellisync Mobile Suite?

Please kindly advise any shortcomings if any?

Cheers
[LG Optimus 3D] reckoner13:
Hello, I just bought the LG Optimus 3D Max (P720h) thinking that it had already been updated to ICS. I like the phone, but I can't find any official announcement of ICS coming for this phone? Does anyone know if LG has announced plans for this phone to receive ICS, I've searched Google and the Forums and it's hard to find any information on this phone. Thanks.
[LG Optimus 3D] bagwithshi7:
Welcome in the club... prepare with huge amount of patient :)

The update was set for Q3-4 of 2012... well 1 year later you can see the situation.
[LG Optimus 3D] Eklovya:
There is no official update yet and i doubt it will ever come.

But you can use my unofficial ics for p720h.

Working 3D
[Samsung Infuse 4G] Pok3rr:
I'm about to try the soldering technique on my Infuse's power button but I have some questions before I give it a go.

My infuse has had this problem before but I temporarily fixed it by dropping the phone. Then it happened again so I tapped the power button against the corner of my desk which also fixed the problem. Now the stuck power button is back again, but this time I actually opened the phone up entirely to see what the problem was. There seems to be none..turning on my phone without the plastic casing containing the power button and volume rocker did NOT work. So my phone boot loops even without anything "jamming" the power button down. So is the issue with the stuck power button really resolvable? In MrKickstand's guide here http://xdaforums.com/showthread.php?t=1996709 I've tried everything except for the soldering technique. He notes there are four spots of solder that need to be melted. I see three. What do I do? This is my last ditch effort before I call up the local cell phone repair shop.

Edit: Pulling the power button with tweezers didn't do anything.
[Samsung Infuse 4G] alexischino:
Here try this it works for me....

https://www.youtube.com/watch?v=ifw2_yYP8e0&feature=youtube_gdata_player