yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] volfan22:
I normally wouldn't care but I've already bricked once. Probably shouldn't test my luck for a 2nd time Haha.

CM10.1 Droid DNA
[HTC Droid DNA] bb12489:
I don't mind testing whatever anyone comes up with. I'm no dev by any means sadly :/
[HTC Droid DNA] bb12489:
Has anyone tried modifying files on CM10.1 yet?

I may be flashing it soon to play with. What's the signature that needs to be put into nfcee_access.xml?
[HTC Droid DNA] ThatFool:
I replaced the nfcee_access.XML on CM 10.1 and it just continuously said creating wallet. The I just borrowed a SIG from a another phone was maybe need to pull it from the jbutterfly?
[HTC Droid DNA] bb12489:
Where is the nfcee_access file located? I'll see if I can find it in a J butterfly dump.
[HTC Droid DNA] ThatFool:
/system/ect
[HTC Droid DNA] bb12489:
So I pulled the nfcee_access from the Sprint HTC One. Now wallet doesn't complain about secure element, but now it's stuck on "Setting up Wallet, this may take up to 5 minutes".

I checked to make sure that the HTC DNA, Butterfly, & One all use the same NXP np544 chip. Do you think changing Libs from the Sprint One would work? I'm kinda at a stall now.....

Also what library files should I look to change?
[HTC Droid DNA] ThatFool:
That's where I ended up. Haven't had time to switch libs. Couldn't hurt to try.
[HTC Droid DNA] bb12489:
I tried changing some nfc libs to ones I pulled from a sprint Rom, but they still had no effect. In log cat it still says that it can't detect the secure element. I'm really thinking these libs are the answer though.
[HTC Droid DNA] djh816:
It is but we need to have them already compiled with secure element access. The S3 for example was able to use the nfc libraries from another unlocked S3. I haven't seen the HTC One or DNA libraries unlocked anywhere though and HTCDev has said they don't care to release any further source than they have.. So unless maybe someone gets secure element working on One, DNA, or Find 5, I don't see this changing anytime soon. Even CM10.1 currently uses the same sense nfc libraries. (CM10.1 DOES have header support for the libraries but without a kernel module with secure element there, we can't do anything. It still hangs if you get headers working)
[HTC Droid DNA] formula84:
Thanks for this info I was wondering why cm10.1 was also not working this explains it.

BTW the sprint one does work with Wallet without any modifications maybe the needed kernel modules can be grabbed from there?

Sent from my HTC One using Xparent Skyblue Tapatalk 2
[HTC Droid DNA] ThatFool:
Wish I knew kernel stuff..
[HTC Droid DNA] djh816:
So we need the kernel modules for our specific nfc chipset (pn544 i think?). If the posted file has that, you could try. I will definitely take a look shortly when I have the time but you would need more than just the xml file. That just tells the libraries which app signatures can access the element but it needs to be enabled at a kernel/system level first.

You'd probably some combo of these:

/system/vendor/firmware/libpn544_fw.so and maybe that mfg.bin

/system/lib/hw/nfc.*

/system/lib/libnfc*.so

Then the typical modified nfcee_access.xml (/etc) and maybe the Nfc.apk and NfcTest.apk from CM10? (I'd try using cm10 with replaced files)
[HTC Droid DNA] bb12489:
The only things I replaced were files from /system/lib & system/etc.
[HTC Droid DNA] djh816:
so it's probably in the pn544 firmware or .bin maybe? someone with more time is welcome to try. looking at logcat I remember getting stuck after having it enabled in the libraries and it would just sit because the SE was still not there (I assume its in one of the mentioned above)
[HTC Droid DNA] bb12489:
I'll try pulling files out of the Sprint HTC One rom from the directories you mentioned and report back. The most I can do is just replace files and send in logcats if it helps anyone else.
[HTC Droid DNA] djh816:
should be all thats needed assuming they are the right files. if nfc breaks (as in you can't toggle it on or it doesn't show a toggle), something didn't work right but assuming they are the same hardware, its very likely that they would work.
[HTC Droid DNA] bb12489:
Here's the Sprint files from those directories. The only difference seems to be the /System/Lib/Hw/nfc.m7wls.so. On DNA based Roms the file is nfc.dlx.so.
[HTC Droid DNA] formula84:
I feel like this issue is going to lie in kernel not ROM I did a binary compare on those libs and they are the same between stock Sprint and T-Mobile versions. Works out of the box for sprint but not for T-Mobile so it must be the kernel.

Sent from my HTC One using Xparent Skyblue Tapatalk 2
[HTC Droid DNA] bb12489:
I hope someone who knows Kernels can help us out eventually!
[HTC Droid DNA] plh233391:
I haven't tried it nor do I use Google wallet but have y'all tried using modaco toolkit witch uses xposed framework to to disable wallet checks like I said I have not tried it and for all I know y'all might have already tried
[HTC Droid DNA] bb12489:
Yea I've tried it before. It only disables root checks and local checks I guess. The issue we have currently is the secure element not being enabled in our phone.
[HTC Droid DNA] jasoraso:
The secure element is the issue. The phone either doesn't have one, or else it is disabled. The HTC software on the phone is programmed for Isis, which looks for a secure element on a sim card. Google wallet is programmed to look for a secure element on the phone itself.

There are some reports that the DNA does not have a secure element. If it does have a secure element, we need a kernel, or hardware libraries to activate the secure element.

Or else we need to get a version of Wallet that looks for the secure element on a SIM card.
[HTC Droid DNA] Argumentation:
Don't know if it'll help, but Google announced at I/O that the One will get official Wallet support. :good:
[HTC Droid DNA] ThatFool:
I read that. I am going to begin digging through the kernels comparing the DNA and the One.
[HTC Droid DNA] volfan22:
[MENTION=3962821]ThatFool[/MENTION] did you ever find anything that would benefit us?

CM10.1 Droid DNA
[HTC Droid DNA] bb12489:
Find anything?
[HTC Droid DNA] ThatFool:
Sorry guys I have been busy with school finishing up. I found the NFC files match and still haven't found anything to do with SE. I will have more time soon but if anything does come up I don't know how to recompile a kernel or anything. :p

EDIT: Just saw formula's post, looks like he was a step ahead. Hrmm maybe someone will get luckyb
[HTC Droid DNA] bb12489:
Just a quick update! I installed the 5/30 build of CM10.1, then for the hell of it i followed the instructions from the GS4 wallet thread here. After doing so I started Google wallet up and looked at a log cat and this is what I saw ( see attached image)

The part the sticks out the most is "Number of Secure Elements : 1". As far as I remember, we have never gotten our devices to even detect a secure element before. Now I could be reading this wrong, and I'm still stuck at the setting up screen for wallet, but I have not seen anywhere in my log cat a line for "No SMX". What could this mean?
[HTC Droid DNA] bb12489:
Here is a better view of the log. Just looking at the nfc entries specifically
[HTC Droid DNA] mracrawford:
Any way I can help, I've got the SE sim and am willing to try just about anything.

Just throwing it out there. I would really like this capability, otherwise NFC is pretty pointless for me.
[HTC Droid DNA] bb12489:
I don't think we will need the nfc sim if what I posted above is correct.

Also I've noticed on the most recent CM 10.1 build, that when i launch wallet to attempt to get it to work, it will cause the NFC menu under Settings > More to become not responsive and force a reboot just to toggle NFC back off an on.
[HTC Droid DNA] djh816:
This xposed framework seems to emulate some nfc thing and provide some sort of bridge to wallet. It appears that the secure element portion is working at least (including SecureMX headers) but somehow we still are not communicating with the element itself. I would try combinations of a known Google Wallet supported pn544 firmware bin and maybe nfc libs (though I don't think those are the issue now)
[HTC Droid DNA] bb12489:
I'll try some different bins out, but I think i've done that already...can't remember now :P

I only switched bins on sense based roms by pulling from other sense roms from different carriers. Idk if I can take a firmware bin from say a Sprint rom and put it into CM 10.1 for our DNA. I think it breaks NFC completely. I'll try it later tonight.
[HTC Droid DNA] bb12489:
Ok, so I tried the firmware from the sprint HTC one and it breaks nfc just like I thought. However, we do not need xposed framework installed in order to see a secure element. It is still detected without, except the same problem persists with wallet....

How the hell do the Sprint ONE users get wallet working?!? lol. The international ONE can't get it working, and as far as I know the AT&T variant isn't working either. Could this be kernel related?

EDIT: I tried all of this on Carbon Rom just now.
[HTC Droid DNA] mracrawford:
Man.. I wish I could help with this... Happen to have a logcat from when your NFC is broken?
[HTC Droid DNA] bb12489:
I didn't save the logcat, but all it said was "firmware download failed" while trying to initialize nfc.. The rest is the same as in my previous logcat above.
[HTC Droid DNA] mracrawford:
Seems like we may just be out of luck.. =/
[HTC Droid DNA] bb12489:
I just really want to know what makes it possible on the Sprint HTC One but not the AT&T, T-Mobile, or international One. No one has gotten it to work on dev editions either. Yet all the hardware should be identical aside from radios. Also the exposed does not seem to be emulating a secure element. I tired xposed on a sense ROM, and it didn't make a difference. Then tried straight stock CM with no xposed and it detected the SE just fine. Xposed is only helping us get past carrier, root, and version checks. Nothing to do with SE.

I can only hope that with the recent s-off release and impending release of the Google HTC One, that we might find a way yet. I know the DNA and One are different models, but both carry the same pn544 NFC
[HTC Droid DNA] mracrawford:
I'm really losing hope, I just don't see it happening.

Although I'm not much help either, I've pretty much just messed around with xposed as well as build prop changes...
[HTC Droid DNA] bb12489:
As much as I love the DNA compared to other phones, I may end up ditching it come this September. It seems that Galaxy phones are the easiest to mod to get wallet working.
[HTC Droid DNA] mracrawford:
I just hate their form factor.. They are ugly friggin phones! Damn..
[HTC Droid DNA] bb12489:
I felt it was my duty to revive this thread from the dead since I notice HTC dropped the kernel source for the HTC One Google Edition! I still believe this is all at the kernel level to be honest. I'm hoping someone might be able to take another look soon!
[HTC Droid DNA] mracrawford:
I've got my fingers crossed!
[HTC Droid DNA] jasoraso:
Unfortunately, it appears Google Wallet STILL isn't supported on the "Google Experience" HTC One. :( FYI, it appears the S4 Google experience DOES have Google Wallet.
[HTC Droid DNA] bb12489:
This is just unfortunate....I read the same thing as well. Google even stated it was because of not having an embedded secure element. So I don't understand what the logcats are showing me then when I'm on CM 10.1 and it shows a secure element (1). Do we have it or not? Plus I'm not sure why HTC would want to cripple their Google Experience device when the GS4 can clearly do it.

rage....
[HTC Droid DNA] fr4nk1yn:
Has any one actually tried the NFC equipped SIM card?

I tried to get one and was told even though " i often travel to San Antonio and Salt Lake City" it wasn't available in my home ,arket so I couldn't have it.
[HTC Droid DNA] demitrix:
Hey, dropping in the from the AT&T One forum. I have been trying to look into this as well. They only possibility I have left is that the sprint HTC One is actually different hardware. It seems that there is a PN544 chip that does not include a SE.
[HTC Droid DNA] mracrawford:
I have one, it hasn't helped at all.
[HTC Droid DNA] imbonez9:
You guys are hopeless... You want GW to work here you go... However, for 5 on, put back to DNA info...

http://xdaforums.com/showpost.php?p=32187579&postcount=1
[HTC Droid DNA] bb12489:
If you bothered to read the thread from beginning to end, you would see that our issue is more complicated then a build.prop change.
[HTC Droid DNA] mracrawford:
Damn for a second I WAS hoping he had something we'd over looked. Our problem Ohh bigger than build.prop changes, GW looks for a secure element that our phone does not have. Even with a secure element SIM card, it searches for an on board secure element. That's just the beginning of our problem.
[HTC Droid DNA] bb12489:
I think this is going to be our only hope in the future...

http://www.simplytapp.com/

I've read about it before, and there is a video of a guy using it at a coke machine. Works a bit different then Google Wallet since it doesn't require and embedded secure element. They have different cards you can purchase, but they seem to be out of the reloadables at the moment. From the looks of the website I'd say they are getting ready to maybe update the Tapp app they have in the play store. I'm going to try and get in touch with them and see!

Edit: Well that was fast! I just got an email back from one of the guys at Tapp. They said to inform the community that the project is still on track! Hopefully it won't be too awful long before we can just simply ditch Google Wallet on the DNA and the One in favor of Simply Tapp!

If I get any further updates on this, I will make a thread for SimplyTapp. To me, Google Wallet is dead on the DNA. Unless Google ever decide to rewrite Wallet to not use the embedded secure element, then I don't think we will ever see it on our device.
[HTC Droid DNA] maxjivi05:
Sounds awesome!
[HTC Droid DNA] bb12489:
Straight from the horses mouth....

No ETA was given. So it could be next month, next week, or tomorrow for all I know lol.
[HTC Droid DNA] demitrix:
Who is the horse? Where did you see this?
[HTC Droid DNA] mracrawford:
"Edit: Well that was fast! I just got an email back from one of the guys at Tapp. They said to inform the community that the project is still on track! Hopefully it won't be too awful long before we can just simply ditch Google Wallet on the DNA and the One in favor of Simply Tapp!

If I get any further updates on this, I will make a thread for SimplyTapp. To me, Google Wallet is dead on the DNA. Unless Google ever decide to rewrite Wallet to not use the embedded secure element, then I don't think we will ever see it on our device."
[HTC Droid DNA] bb12489:
I emailed simply tapp myself and got a reply from two of the guys involved. I can post the emails as proof if no one believes I talked to someone lol. I just figured it wasn't that important right now. In my reply I did say that many of us here in the DNA xda thread would probably be more then willing to test their app if they're looking. I just haven't heard back since then, or have any other info yet. So as I said I'll make a thread dedicated to simplytapp since I'm following it quite closely, but only when more info is available.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Valtrex11:
Hey guys, i want to move on from ICS to JB, I have seen that the flykernel is a pretty good one... Which rom is the best in terms of:

1. Battery life

2. Performance

3. Stable

Thanks a lot for your future tips or recommendations.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] fuser1337:
Try CyanogenMod 10. Its stable, fast and almost everything working except front camera (It will work in future update)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] TheDynamiteGuy:
you can also try p.a.c.

http://xdaforums.com/showthread.php?t=1803076
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Kafka Datura:
First hint : pac is the only one that has everything working, just sayin.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] xzeiP:
Pac does not have front camera working, as far as I know..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Kafka Datura:
Completely does, at least on my phone.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Valtrex11:
Ill try Pac, I hope everything is working there fine :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Parkside:
My phone too. PAC is great but I can't get great battery life from it. Not disastrous life just a lot faster drain than the best ICS builds. Don't think it copes with the widgets i use.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] immerblind:
cam not working with face unlock and tango application for me. skype working,normal camera working too.

i use the rom in daily use,still the best for me. and i have no special fast battery drain.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Deleted member 3493119:
Pac is the best
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ChongWiz:
Not a commercial(or maybe it is), but try my Nyandroid AOSP Jally Bean, it's the only fully AOSP rom out there and it has fixed front camera (in release 3 wich is uploading ATM), and it is clean and pure AOSP.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Valtrex11:
flykernel for JB roms is the best?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] frenzyboi:
How can you compare when one is a kernel and another is a rom?

IMO, PAC rom is the best. You get the best support on the thread, with every two weeks (more or less) updates and currently dev is building 4.2 roms. Have a go at it ^^
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] TheDynamiteGuy:
p.a.c. and cm10 is rom that i suggest to use with flykernel v0.5a(jb)..for flykernel v.8 it support most ics rom..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] demolatorul:
first of all wrong section to post, there is a general or a q&a section but there is no such thing of best rom, best rom for me will prbably not suit you, and will be worse for you, and saying one is better than other is not ok for developers, try them all and choose the one you like more
[Verizon Samsung Galaxy S III] TokedUp:
Imoseyon gave me permission to link his kernel here on XDA. Please thank Imo on here or RootzWiki, and please donate to him if u can.

ICS and JB kernels are available.

v 4.0 is the newest version for

TW JB 4.3 ML1

only.

Older versions are available (4.1.2)

Experimental builds are also posted on RW. I personally dont want to link them here since I cannot help if something goes wrong. So keep an eye on the RW thread if you can help in testing.

Link to OP/ICS kernel

http://rootzwiki.com/topic/31329-ke...el-minimalistic-kernel-ics-v13-jb-v03-112512/

Link to JB kernel changelog

https://github.com/imoseyon/leanKernel-d2vzw/wiki/TW-ChangeLog

Link to source

https://github.com/imoseyon/leanKernel-d2vzw

All credit goes to Imoseyon

Please feel free to post results from Roms.
[Verizon Samsung Galaxy S III] jdub251:
OK so running this on jelly beans b 4 and it is super fast. Works like a champ! Great work imoseyon. I tried ktoonsez and this way smoother on touchwiz. Like butter baby!

Sent telepathically
[Verizon Samsung Galaxy S III] countryfolk07:
Are there any custom governors with this kernel?
[Verizon Samsung Galaxy S III] jdub251:
No just three. Not as many options but already set out of the box so to speak. Changed my io scheduler to deadline and let her rip.

Sent telepathically
[Verizon Samsung Galaxy S III] Imoseyon:
I hope to have interactiveX running on it before the 1.0 release.

Also, you can find the change logs here: http://revision.io/embeds/leanKernel-galaxys3-tw
[Verizon Samsung Galaxy S III] Pete7ate:
Thanks for sharing.
[Verizon Samsung Galaxy S III] omair2005:
Running fine on clean Rom 5
[Verizon Samsung Galaxy S III] SoCalSpecialist:
does not work with Taste of Beans 3.5k at all..

color flux

removed boot animation

reboots

battery gets SUPER HOT!

had to do a batt pull, boot into recovery, and go from there.
[Verizon Samsung Galaxy S III] Metfanant:
Ran fine when it first booted...benmark scores were very high...running very smooth...

Then after a reboot things got kinda wonky...

Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...

I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...

...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...

Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...

Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...

The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...

Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...

sent from my VZW Galaxy S3 running Synergy Jelly Bean
[Verizon Samsung Galaxy S III] Imoseyon:
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
[Verizon Samsung Galaxy S III] Metfanant:
So it would be "stress" related sorta...but more heat related specifically?...its a bummer because my phone does not like 1900mhz at all...and really starts to heat up/lag at that clock speed...

So if the kernel is going to "reset" all the time I'm gonna have to stick with 747 because its the only one (except stock vzw jb) that sticks no matter what I throw at it

Edit: I will however say...the kernel is completely compatible with Synergy 118...and like I said before...when it initially booted the phone was screaming...and performing better than ever...

So keep up the good work and I'll keep my eye on things...

I didn't run your kernel on ICS...wishing I had tried it out now lol

sent from my VZW Galaxy S3 running Synergy Jelly Bean
[Verizon Samsung Galaxy S III] zakth:
Despite what a previous user said I'm running this on tasteofbeans 3.5 with no issues. I've ran both 0.2 and now 0.3
[Verizon Samsung Galaxy S III] TheGman125:
Has anyone ran this kernel over CM10 nigthlies?
[Verizon Samsung Galaxy S III] juancaperez2000:
This is for TW roms not for aosp roms, imos has his aosp kernel in rootz
[Verizon Samsung Galaxy S III] TokedUp:
Sorry to hear Met. My phone has never run so well. I'm not experiencing any heat ups or problems set at 1700mzh. When I I run Vellamo it lists the kernel max at 1900mhz but when I check setCPU its locked at 1700mzh. I ran LK on ICS and it was simply amazing. It was the only thing I missed moving to JB. Plz remember that this kernel is just days old and it will continue to get better with updates from Imo. Keep the reports coming guys, it's the best thing to do to help.
[Verizon Samsung Galaxy S III] jdub251:
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.

Sent telepathically
[Verizon Samsung Galaxy S III] Morkai Almandragon:
Any chance of Call Recorder kernel support Imo? I only ask becaues several of your kernels for other phones I have owned did support it.