*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!
While looking over some aosp code for the settings apk, I stumbled upon a much easier loophole that completely bypasses Verizon's and maybe other carrier's Tethering Entitlement Check app. By setting the net.tethering.noprovisioning property to true, Verizon and other carrier's entitlement check app won't even run, the native tethering will start now as soon as you turn it on. This has been tested on and works on my XT1060 but depending on how other carrier's run their entitlement check app, it could work on other phone models also. So if you test it and it works on the other carrier Moto X's or other phone models let me know!
So for Rom Developers all you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove the entitlement check app if you want to. Also if your phone model has any property that has dun_required like ro.mot.tether_dun_required then you will need to change that line from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
v1.1 http://www.androidfilehost.com/?fid=23329332407584928
Changelog
-v1.2 Update (7/4/2014)
-It can now bypass the read only property's like ro.mot.tether_dun_required and set it to 0 via setpropex for the models like Sprint, and RPW, Thanks to Poliva for setpropex, and jduck for getting it working on KitKat
-Cleaned up the code a lot it was extremely sloppy, still needs some work
-Also I ended up having to create another key to sign the app, thanks to the android L sdk update that screwed up my dev environment, and I ended up accidentally deleting my keystore
-v1.1 Update (5/8/2014)
-For v1.1 I added checks to grab the phones model number and then apply certain commands specific to those models
iKrYpToNiTe said:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!
The other day I stumbled upon a much easier loophole that completely bypasses Verizon's...
Click to expand...
Click to collapse
As mentioned in the OP, I can confirm this works. Thanks for posting this app!
Damn, I spent a few days trying to figure this out on my own a few weeks ago and couldn't get it to work. Needless to say I gave up. Good find!
The Tallest said:
Damn, I spent a few days trying to figure this out on my own a few weeks ago and couldn't get it to work. Needless to say I gave up. Good find!
Click to expand...
Click to collapse
Thanks, I just happened to stumble across it while looking over the dex2jar output of the Settings.apk.
for this to work on sprint, you would also need to change ro.mot.tether_dun_required=1 to ro.mot.tether_dun_required=0 in build prop
Very nice app you made here works perfect
hartv427 said:
Very nice app you made here works perfect
Click to expand...
Click to collapse
Awesome thanks for the feedback!
Kittiesoncrack said:
for this to work on sprint, you would also need to change ro.mot.tether_dun_required=1 to ro.mot.tether_dun_required=0 in build prop
Click to expand...
Click to collapse
Hmm so sprint doesn't run their entitlement check as a provisioning app nice to know, I will look into putting in a check to grab the model number and set the right props in the app. Thanks for the information!
iKrYpToNiTe said:
Awesome thanks for the feedback!
Hmm so sprint doesn't run their entitlement check as a provisioning app nice to know, I will look into putting in a check to grab the model number and set the right props in the app. Thanks for the information!
Click to expand...
Click to collapse
I believe sprint does use the entitlement check but the tethering won't allow data without the tether dun edit in build.prop
Sent from my XT1056 using Tapatalk
Kittiesoncrack said:
I believe sprint does use the entitlement check but the tethering won't allow data without the tether dun edit in build.prop
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Gotcha thanks for info!
The easiest way, that works on every carrier that I know of, is to just edit framework-res.apk and remove the provisioning app from the XML so that it defaults to native tethering setup.
imnuts said:
The easiest way, that works on every carrier that I know of, is to just edit framework-res.apk and remove the provisioning app from the XML so that it defaults to native tethering setup.
Click to expand...
Click to collapse
How is that easier than my way? By adding net.tethering.noprovisioning=true to the build.prop file it launches the native tethering instantly by bypassing the framework-res all together. At least for Verizon for which I made this for, I said it could possibly work on other carriers I never said it would. I made the app for people who don't want to modify their system at all, by either adding that line to the build.prop file or decompiling, editing, recompiling, and replacing the framework-res.apk. To me that seems to be a whole lot easier, a high percentage of users on this forum don't know how to properly replace a system apk much less edit it properly. So I was trying to help them out by simplifying it for them.
iKrYpToNiTe said:
How is that easier than my way? By adding net.tethering.noprovisioning=true to the build.prop file it launches the native tethering instantly by bypassing the framework-res all together. At least for Verizon for which I made this for, I said it could possibly work on other carriers I never said it would. I made the app for people who don't want to modify their system at all, by either adding that line to the build.prop file or decompiling, editing, recompiling, and replacing the framework-res.apk. To me that seems to be a whole lot easier, a high percentage of users on this forum don't know how to properly replace a system apk much less edit it properly. So I was trying to help them out by simplifying it for them.
Click to expand...
Click to collapse
I think the app is fantastic ... I have modded my own farmework.res.apk which works and also modded my own VzwEntitlementService.odex which works as well ... The bottom line is I'm using your app because it's simple and works perfectly without any system mods. :good:
iKrYpToNiTe said:
How is that easier than my way? By adding net.tethering.noprovisioning=true to the build.prop file it launches the native tethering instantly by bypassing the framework-res all together. At least for Verizon for which I made this for, I said it could possibly work on other carriers I never said it would. I made the app for people who don't want to modify their system at all, by either adding that line to the build.prop file or decompiling, editing, recompiling, and replacing the framework-res.apk. To me that seems to be a whole lot easier, a high percentage of users on this forum don't know how to properly replace a system apk much less edit it properly. So I was trying to help them out by simplifying it for them.
Click to expand...
Click to collapse
The method I suggested works on all carriers, not just VZW. Another user posted that you need something else for Sprint for this to work. Sure, your's is quite simple, but it isn't universal.
imnuts said:
The method I suggested works on all carriers, not just VZW. Another user posted that you need something else for Sprint for this to work. Sure, your's is quite simple, but it isn't universal.
Click to expand...
Click to collapse
I never said it was universal, I said it possibly could be I have no way of testing other carriers. That's why I said for other carrier users to try it if it works great let me know, if it doesn't oh well it was a shot.
If you don't think it's universal or don't think it's the easiest way for VZW Moto X owners. Then that's your opinion not mine, but this thread isn't the place to debate it out. Now if you don't mind can we drop it and get back on topic please?
Thank you to the developer, works on droid Maxx!
Sent from my XT1080 using xda app-developers app
Thanks for this, I completely failed trying to set it up myself. Great job!
Sent from my XT1060 using Tapatalk
pbaldw10 said:
Thank you to the developer, works on droid Maxx!
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
Sorry for not replying before now, I've been focusing on my rom thread and my new job and haven't had time to check this thread. I'm glad it worked thanks for the feedback!
MugZ91 said:
Thanks for this, I completely failed trying to set it up myself. Great job!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Your welcome, I'm glad it helped you out.
I added v1.1 to the OP that runs certain setprop commands depending on your phone model. Let me know if it works for everybody or doesn't!
Works great on unlocked, stock rooted DE edition Moto X.
Sent from my XT1060 using Tapatalk
Great app and idea any plans to add the sprint support for this?
Thanks for the great work bud
Thanks for this great app. Works great on DE Verizon moto x.
Sent from my XT1060 using Tapatalk
Related
Looking over in the HERO forum someone has found out away to modify the phone.apk to include a roam only option. Wondering if this was possible for the evo as well. I tried using the apktool but the files do not match.
Heres the link:
http://forum.xda-developers.com/showthread.php?t=745092
I'm sure it's possible. If I remember correctly when I was using CyanogenMod Nightlies, there was an option for this (it wasn't call roam only but im sure thats what it did).
Yeah this is where all of this started.... Now someone has ported it to the hero and I would really like to see if this is possible for the hero.
Why would you want to force Roam only?
tdusen said:
Why would you want to force Roam only?
Click to expand...
Click to collapse
I know I would. I used to do it on my Pre while I was at work.. I work in radio and in the lower level of our building in production studios all day and my signal is very weak. Forcing the phone into roam helped me have better battery life, and a more stable phone if I got a call or something.
Roam only on the Evo would be very nice!
fastamx79 said:
I know I would. I used to do it on my Pre while I was at work.. I work in radio and in the lower level of our building in production studios all day and my signal is very weak. Forcing the phone into roam helped me have better battery life, and a more stable phone if I got a call or something.
Roam only on the Evo would be very nice!
Click to expand...
Click to collapse
This is the same reason why I need it..... I used it on my pre all the time as well when at work and in other areas where coverage was very spotty
I have the phone.apk (from Fresh 3.1.01) decompiled and I have made the noted changes from the original Hero thread and I'm ready to test, but I'm having fits on compileing the apk to sign and test. Can someone else try, the modifications are simple to edit.
itsachirpthing said:
I have the phone.apk (from Fresh 3.1.01) decompiled and I have made the noted changes from the original Hero thread and I'm ready to test, but I'm having fits on compileing the apk to sign and test. Can someone else try, the modifications are simple to edit.
Click to expand...
Click to collapse
I am not running Fresh.... Wish I knew a little more about programing. I tried the apktool mentioned in the post but the rom I use has a different dialer setup than fresh's. I wonder if he would be willing to help.
I would love to have this option in a widget, shortcut, or some other method that makes it easy to toggle on and off. There were registry edits on my old HTC WinMo phones to enable this.
I have very good Sprint coverage most of the time but every once in a while I'm somewhere Verizon has better coverage. I've seen my phone hold onto Sprint with one or even no bars, and only switch to Verizon every once in a while and get full bars. This kills the battery and of course service.
Could someone post the original stock 2.2 phone.apk (unthemed). I think that the themeing on the dialer is what is causing my issues with rebuilding the .apk. This could cause issues with the htc framework used, just my .02. We should be able to port this over.
I modded the apk for Fresh 3.1.0.1, try it out and let me know if it works:
http://forum.xda-developers.com/showthread.php?t=745092
ssjgoku24 said:
I'm sure it's possible. If I remember correctly when I was using CyanogenMod Nightlies, there was an option for this (it wasn't call roam only but im sure thats what it did).
Click to expand...
Click to collapse
I think it was called "Affiliated Networks", but I'm stuck on "Roam only" from the winmo days
MrGreg said:
I modded the apk for Fresh 3.1.0.1, try it out and let me know if it works:
http://forum.xda-developers.com/showthread.php?t=745092
Click to expand...
Click to collapse
Unfortunately I keep getting FC's after moving this one over the old one. Rebooted the phone and still no luck. I feel like something is different with the framework or something. Could theme changes (Rosie) in this ROM be the issue? What did you do to rebuild the apk. I worked a few hrs after I moded it from your instructions trying to rebuild using APKmanger. I greatly appreciate your efforts. Trial and error, we'll get there with the EVO!!! Thanks!
I would love this app also
please
I understand the purpose of roam only but we get charged for roaming? Am I missing something here?
Sent from my PC36100 using XDA App
this would be a huge step forward to helping me get good reception in a couple really bad areas. Thanks for working on this!!!
leeh41 said:
I understand the purpose of roam only but we get charged for roaming? Am I missing something here?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
U dont get charged for roaming it just comes out of your anytime minutes if you do not have an unlimited plan. If u have unlimited then it costs nothing
Any one have any progress to report on this
One thing that may work: load CM6, set it to affiliated networks, then restore back to your previous ROM.
It may not work, but I know on my N1, if I would set it to WCDMA only to prevent the 3G dropping to EDGE, then that would stay sticky over flashes & wipes etc.
The settings are stored in the radio, so I think setting it to roam only should stick.
coojoe1000 said:
this would be a huge step forward to helping me get good reception in a couple really bad areas. Thanks for working on this!!!
Click to expand...
Click to collapse
Sprint doesn't charge for domestic voice or data roaming. They reserve the right to cancel your account if you roam for more than half your minutes or a specific amount of data (I can't remember how much), so it's not the kind of thing you'd leave on all the time. But there are situations where it would be beneficial to force roaming for a short period of time.
i'd def be interested in this. im using fresh.
Has anyone figured out how o change the sprint branding on the nexus yet? if so can you point me to the right files. I followed a (HOW-TO) from the epic but it wasn't there. So, i assume its is diffrent. anyones help is greatly needed. Thank you
Rant: The XDA search feature sucks!!!!! Searched for branding and i got some threads where the word wasnt even in the thread or the title.
Have you tried the eri.xml file found in framework-res/res/xml yet? I decompiled framework-res and the word 'sprint' is in there 3 times under roaming indicator stuff. Not sure if it will change anything but its something I remembered from past research.
edit: I also found 'sprint' in the system/etc/apns-conf.xml but I have no idea what will happen if you change it. I suppose its worth a try if your adventurous...
Code:
<apns version="6">
<apn carrier="Sprint"
mcc="310"
mnc="120"
apn="Sprint"
user="Sprint"
server="*"
password="*"
mmsc="http://mms.sprintpcs.com"
authtype="3"
/>
</apns>
thankyou.......
i will post my results as soon as i have a chance to mess with it.
again thank you.
spdwiz18 said:
thankyou.......
i will post my results as soon as i have a chance to mess with it.
again thank you.
Click to expand...
Click to collapse
No worries, just got mine and poking around a bit in the stock rom seeing where things are. Its a bit different than past devices I've had ;-)
Sent from my Nexus S 4G using XDA Premium App
alright...
I got it. framework-res.apk/res/xml/eri.xml
edit line 7 where it says sprint. this will change the lock screen and the pulldown notification branding.
again thank you for your help. thought i would let you know it worked.
spdwiz18 said:
alright...
I got it. framework-res.apk/res/xml/eri.xml
edit line 7 where it says sprint. this will change the lock screen and the pulldown notification branding.
again thank you for your help. thought i would let you know it worked.
Click to expand...
Click to collapse
Glad it worked. That was one that never worked on the moment or the epic but I had a feeling it might because the nexus is different enough.
Sent from my Nexus S 4G using XDA Premium App
WITH BOTH QPST AND CDMA WORKSHOP, I AM ABLE TO READ THE PHONES SETTINGS BUT I CANT WRITE TO IT. woops, sorry bout the caps.
anyway, when i click write, some things write and others dont. then when i click read, the banner is recognized as google even though it reads sprint on my phone still. often time when i click write in cdma workshop, it tells me phone is requesting spc, spc is required.
update: it seems that the sci and access overload class have stuck to the values that i chose. however, the main goal for me is to alter the banner to read 'Google'.
any input is much appreciated. thank you!
tailsthecat3 said:
WITH BOTH QPST AND CDMA WORKSHOP, I AM ABLE TO READ THE PHONES SETTINGS BUT I CANT WRITE TO IT. woops, sorry bout the caps.
anyway, when i click write, some things write and others dont. then when i click read, the banner is recognized as google even though it reads sprint on my phone still. often time when i click write in cdma workshop, it tells me phone is requesting spc, spc is required.
update: it seems that the sci and access overload class have stuck to the values that i chose. however, the main goal for me is to alter the banner to read 'Google'.
any input is much appreciated. thank you!
Click to expand...
Click to collapse
I personal dont know anything about qpst or cdma work shop. I did mine by decompileing the framework-res.apk in apkmanager4.9 . Go to res/xml/eri open w/ notepad++ and edit line 7 where it says sprint. This is how I did it.
Sent from my Nexus S 4G using XDA Premium App
I got it to work too! Thanks!
Thanks to snandlal, you can also now do this without windoze: http://forum.xda-developers.com/showthread.php?t=1093556 .
Method is not what matters. Its the result that counts....
Sent from my Nexus S 4G using XDA Premium App
spdwiz18 said:
Method is not what matters. Its the result that counts....
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Method matters when the only windows box still around has a slower processor and much less memory than my phone. :-o
Is this only for Sprint?
Can I do this for Rogers?
can I do this from rootexplorer or ADB? I can't figure out for the life of me how to use APKManager 4.9
Thanks
Heeter
Well it seems cheesecake is not working on scv6. Even on the production server, it fails every time to check updates!!! any ideas?
More importantly I am creating an auto cheesecake app, but I need some help. I have phydo's original source and that is what I have been building off of. His app just starts an event, or what ever you want to call it that is built in to the phone (the cloud switcher thing that pops up. My question is what does that even change. it does not seem to change the same xml that is used for the manual method, but to automate things I really need to figure out what that does so I can do it myself.
Thanks,
-lkrasner
lkrasner said:
Well it seems cheesecake is not working on scv6. Even on the production server, it fails every time to check updates!!! any ideas?
More importantly I am creating an auto cheesecake app, but I need some help. I have phydo's original source and that is what I have been building off of. His app just starts an event, or what ever you want to call it that is built in to the phone (the cloud switcher thing that pops up. My question is what does that even change. it does not seem to change the same xml that is used for the manual method, but to automate things I really need to figure out what that does so I can do it myself.
Thanks,
-lkrasner
Click to expand...
Click to collapse
I have mine all scripted... I will PM you what I have, then maybe we can come up with something more user friendly.... My script just replaces the XML with a new file with the next server in line to check, then runs the update check from the command line on the phone. not pretty, but it works in both cron and with tasker.
I would not write an app or apk for this, it could all be 100% behind the scenes to the user, and maybe an app that could change the frequency and/or turn the cron on or off.... just some thoughts, we can throw some more ideas around here too.
jimbridgman said:
I have mine all scripted... I will PM you what I have, then maybe we can come up with something more user friendly.... My script just replaces the XML with a new file with the next server in line to check, then runs the update check from the command line on the phone. not pretty, but it works in both cron and with tasker.
I would not write an app or apk for this, it could all be 100% behind the scenes to the user, and maybe an app that could change the frequency and/or turn the cron on or off.... just some thoughts, we can throw some more ideas around here too.
Click to expand...
Click to collapse
I thought about just doing a script but I went with an apk for a few reasons. first, many users here might have trouble figuring out how to use that right, and we want as many people as possible. I am also trying to get better with java, so this was a good simple starter project that is still useful to people.
I will try to include a way to set it to check at certain times.
I think we should set up a schedule as for who will check at what time so that we don't miss things. Maybe I should create an open google calendar and everyone can add the time they want to check to better our odds of getting an update. let me know what you all think
I mentioned in another thread, but this thread seems appropriate....
I haven't had any luck with any of the cheesecake servers for a couple weeks now--since the weekend of the searet ics leak. Before that I would get various servers all the time and plenty of "your device is up to date" messages.
I try several times a day at various times ( ~4am, ~11am, ~4pm PST ) and haven't gotten a server once since that weekend.
I've been wondering if Moto has changed something on their end...its quite an easy thing to change DNS entries ans/or server hostnames and/or IP addresses and/or usernames...
So I've been wondering...
Where does cheesecake get its servername info? How does it resolve the servernames? What user is it using?
FWIW, I'm on lithium v1.2 (and have been since back in April).
Sent from my MB865 using XDA
I've been checking Cheesecake servers just fine for the past couple of days, though I am on stock. I still believe that being on a stock build is crucial.
lkrasner said:
Well it seems cheesecake is not working on scv6. Even on the production server, it fails every time to check updates!!! any ideas?
Click to expand...
Click to collapse
Been seeing this more and the only explanation that I can come up with is that the ROM is de-odexed? Im running Romulus, which is odexed. I have no problems.
Although I doubt it.
Sent from my MB865 using xda premium
Fall of Enosis said:
Been seeing this more and the only explanation that I can come up with is that the ROM is de-odexed? Im running Romulus, which is odexed. I have no problems.
Although I doubt it.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I had no problem when I was on lithium, which is de-odexed, so I m confused
I had no problem when I was on lithium, which is de-odexed, so I m confused
Click to expand...
Click to collapse
Perplexing. Quite.
However I would love to be a part of the "cheesecake calendar" if I can!
Sent from my MB865 using xda premium
I've been using cheesecake on scv6. Works fine here.
Sent from my MB865 using xda premium
Is there a way to 1. Get google wallet to fully function on my Razr HD on verizon? Or 2 if that cant happen, trick isis to not seeing I have root.
Also if I get google wallet to get past the idea my phone is a verizon phone, is there anything in the app for root that could cause problems for me like with isis?
AndroidGreg said:
Is there a way to 1. Get google wallet to fully function on my Razr HD on verizon? Or 2 if that cant happen, trick isis to not seeing I have root.
Also if I get google wallet to get past the idea my phone is a verizon phone, is there anything in the app for root that could cause problems for me like with isis?
Click to expand...
Click to collapse
Google wallet will only work on 4.4 and once the app is updated to support our NFC chip.
Borderpatrol1987 said:
Google wallet will only work on 4.4 and once the app is updated to support our NFC chip.
Click to expand...
Click to collapse
I have the Secure Element NFC Sim so the update to 4.4 and NFC support are not needed.
Is there a way to just tell the app my phone is something like the nexus 4?
AndroidGreg said:
I have the Secure Element NFC Sim so the update to 4.4 and NFC support are not needed.
Is there a way to just tell the app my phone is something like the nexus 4?
Click to expand...
Click to collapse
Trust me I tried, the phone is missing the proper OS support with any os before 4.4. Plus the App will ONLY look at NCI. It aint happening untill google updates the chips that it supports and to be running 4.4 so the carrieries can be bypassed.
HCE support is missing from the AOSP stack for NXP NFC controllers. It only works on Broadcom (NCI) controllers. (Unless it was pushed as part of the android-4.4-r1.2 tag...)
So if you have a device with an NXP NFC controller - still no Wallet for you. If your device has the HCE permissions XML (this will only happen if someone made a mistake), Google Wallet will indicate that it's 100% ready for payment, but won't react at all to a payment terminal.
(Another option is if an OEM implements HCE for NXP chips even though it is missing from AOSP.)
Click to expand...
Click to collapse
Borderpatrol1987 said:
Trust me I tried, the phone is missing the proper OS support with any os before 4.4. Plus the App will ONLY look at NCI. It aint happening untill google updates the chips that it supports and to be running 4.4 so the carrieries can be bypassed.
Click to expand...
Click to collapse
I had it working way back before the wallet app was available to all phones, I updated on the assumption that the app would work without it hacked. I got the app from the s3 forum but it was taken down because the dev abandoned it and people had security concerns, all that was done was a mod that disabled the ID checker and told the app the phone was either the Galaxy nexus or the Nexus 4, not sure.
Im just looking for either a build prop edit script that also has the built in undo ability or a modified app by a reputable and trustworthy dev, maybe it was the wrong place to post in the Q&A and I should request a mod to either move to the dev area or FWD the thread link to a few developers to let them see it and have a discussion.
Im honestly NOT trying to start a argument here, I know it CAN be done and HAS before but I cant get instructions how to do it again.
AndroidGreg said:
Im honestly NOT trying to start a argument here, I know it CAN be done and HAS before but I cant get instructions how to do it again.
Click to expand...
Click to collapse
If it can be done on the Razr HD then you would be the first. Many have been trying...search the forum and you will see. The build.prop hacks just dont resolve the issue...with the build.prop modifications you can install the old GW and even start the process of initializing google wallet but then it just hangs there forever. New Google Wallet will install but no tap and pay.
When Android 4.4 comes to the Razr HD then you will have host card emulation and all will be working fine with Google Wallet as it wont need the secure element.
It doesn't even work on 4.4 yet. GW doesn't support our chipset. Once they fix that then we will be good to go.
Sent from my XT926 using xda app-developers app
People, this isnt rocket science, someone hacked the app for a verizon s3 back in the days of ICS. The hack was supposed to just be a simple change and the effect could have been done the same by a build prop edit according to the thread. Maybe a little more was done I didnt care I only have prepaid credit cards anyway.
Im thinking I need to go over to the s3 guys and kick and scream till I get my wallet candy.
The gs3 has a NCI chip....
Borderpatrol1987 said:
It doesn't even work on 4.4 yet. GW doesn't support our chipset. Once they fix that then we will be good to go.
Sent from my XT926 using xda app-developers app
Click to expand...
Click to collapse
App works on my M and HD, both running 4.4. As far as touch-n-pay, I don't know, but I can complete setup and get into all the other options.
AndroidGreg said:
People, this isnt rocket science, someone hacked the app for a verizon s3 back in the days of ICS. The hack was supposed to just be a simple change and the effect could have been done the same by a build prop edit according to the thread. Maybe a little more was done I didnt care I only have prepaid credit cards anyway.
Im thinking I need to go over to the s3 guys and kick and scream till I get my wallet candy.
Click to expand...
Click to collapse
If its not rocket science how come you do not know how to do it? If its simple you would think there is no need to ask the question. Look people who have been on this form much longer than you have been trying to help you understand its more than a build.prop edit to get this to work. The support is simply not there yet. Google Wallet has also changed a lot since the ICS days. When Android 4.4 comes out for the phone from Motorola then GW will work.
I am using my Moto X daily now so I am not sure about this next statement but CyanogenMod 11 might work for you on your Droid Razr HD if you have yours unlocked. If not wait on Moto to release the 4.4 update and give GW a try then.
https://plus.google.com/109468208780802399420/posts/fZTNWnWmxYC
Sent from my XT926 using Tapatalk
scoobaspeaz said:
If its not rocket science how come you do not know how to do it? If its simple you would think there is no need to ask the question. Look people who have been on this form much longer than you have been trying to help you understand its more than a build.prop edit to get this to work. The support is simply not there yet. Google Wallet has also changed a lot since the ICS days. When Android 4.4 comes out for the phone from Motorola then GW will work.
I am using my Moto X daily now so I am not sure about this next statement but CyanogenMod 11 might work for you on your Droid Razr HD if you have yours unlocked. If not wait on Moto to release the 4.4 update and give GW a try then.
Click to expand...
Click to collapse
I'm running OSE 4.4 on my M and HD and Wallet works on both.
RikRong said:
I'm running OSE 4.4 on my M and HD and Wallet works on both.
Click to expand...
Click to collapse
Tap and pay part or just wallet. They changed gw a few releases ago so you can install it and use it for everything but tap and pay.
Sent from my XT1060 using Tapatalk
scoobaspeaz said:
Tap and pay part or just wallet. They changed gw a few releases ago so you can install it and use it for everything but tap and pay.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There will be no Tap&Pay until someone gets the NXP Controller set up for HCE.
This will require some decompiling of files that are not easy to decompile. Of course, nobody that does this is going to get paid, so, we can't exactly hire a software reverse engineer. I am going to try to get in touch with Dan Rosenberg and see what he can cook up for us. He's the most known software engineer here and responsible for our unlocked bootloaders.
If you want Tap and Pay, the best thing to do is push that Googe+ link that I posted last night (a few posts up) to any social medium you can think of and maybe it'll grab the right person's attention.
ISIS and Google Wallet have nothing to do with each other. Android 4.4+ and HCE made it independent.
What we are looking at:
Decompile NFC.apk, NFCui.apk
Decompile the CPP files in that.
Find out what is missing from AOSP
Add it to CM or make a flashable zip.
If you have any friends, family or anyone that can help out. This is the time. Because it doesn't seem like it's going to get merged into AOSP.
scoobaspeaz said:
Tap and pay part or just wallet. They changed gw a few releases ago so you can install it and use it for everything but tap and pay.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Like I said in my previous post, I haven't tested TNP. However, the OP is talking about getting the app installed and was just stating that it was possible to install on 4.4. As for TNP, I don't really need it because I've seen very few places near me that even have POS capability for TNP.
If you want this, please go to my Google+ link and find the jira link in there and vote it up. Nothing is going to get done if we don't bring attention to it.
Sent from my Nexus 7 using Tapatalk
abuttino said:
If you want this, please go to my Google+ link and find the jira link in there and vote it up. Nothing is going to get done if we don't bring attention to it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Or just wait a month or so for Motorola to release the 4.4 update for the HD then someone pulls it from there.
Can't. Otherwise it would have been done with the HTC one, moto x, nexus 7 and a couple others that have support with stock
Besides. Is it really that much effort to vote on a fix? One click..
Sent from my XT926 using Tapatalk
Anyone know of any mods to show an "LTE" symbol instead of the "4G" sign?
it can be done but its not simple. it requires moddifying framework files.
Are their any xposed modules like gravity box that will work with the oneplus one?
Could also do it from modifying the SystemUI.apk
See,
http://imgur.com/hXAtBvi
http://i.imgur.com/E0DXdBH.png
Although I do have to warn that.... when you apply a CM theme, it resets it back to 4G and the "LTE" will only stick when using the stock theme because they have their own _4g and _lte pictures. Unless you modify the .apk to change images of _4g to _lte
The other way doing this is to modify how Android scans _4g and _lte and change it.
DISREGARD APP HASN'T BEEN UPDATED IN A FEW YEARS.
Looking around I ran into the video below but not sure if it'll work for OnePlus One though, if anybody is willing to attempt. App is called NinjaMorph FREE but there's also NinjaMorph Pro paid version which is $4.99.
https://www.youtube.com/watch?v=xlCfvFvsCEY
Free https://play.google.com/store/apps/details?id=stericson.ninjamorph.free&hl=en
Paid https://play.google.com/store/apps/details?id=stericson.paid.ninjamorph&hl=en
Knight-Rider said:
Looking around I ran into the video below but not sure if it'll work for OnePlus One though, if anybody is willing to attempt. App is called NinjaMorph FREE but there's also NinjaMorph Pro paid version which is $4.99.
https://www.youtube.com/watch?v=xlCfvFvsCEY
Free https://play.google.com/store/apps/details?id=stericson.ninjamorph.free&hl=en
Paid https://play.google.com/store/apps/details?id=stericson.paid.ninjamorph&hl=en
Click to expand...
Click to collapse
Considering the app Ninjamorph hasn't been updated since 2010,2011 I would strongly advise not doing this.
zephiK said:
Considering the app Ninjamorph hasn't been updated since 2010,2011 I would strongly advise not doing this.
Click to expand...
Click to collapse
Ya just noticed that lol.
Knight-Rider said:
Ya just noticed that lol.
Click to expand...
Click to collapse
Yeah it probably wouldn't be any good for Kit Kat. The workaround I listed above works, by modifying the SystemUI.apk with the 2 files, it'll work.
But if you apply a theme, you'll need to modify the apk to do the changes for _4g to _lte as well.
The only other way around it is to modify the rom on how it correlates our signal to "4g" instead of the "lte" status bar. I wish that CM stuck with "LTE" instead of "4G" but to me it really doesnt matter and is just cosmetics.
zephiK said:
Yeah it probably wouldn't be any good for Kit Kat. The workaround I listed above works, by modifying the SystemUI.apk with the 2 files, it'll work.
But if you apply a theme, you'll need to modify the apk to do the changes for _4g to _lte as well.
The only other way around it is to modify the rom on how it correlates our signal to "4g" instead of the "lte" status bar. I wish that CM stuck with "LTE" instead of "4G" but to me it really doesnt matter and is just cosmetics.
Click to expand...
Click to collapse
I definitely agree with you on that. Maybe if we send feedback next OTA update will include LTE =)
The Gravity box xposed module will swap from LTE/4G. I'm not sure if it works on cm11s though since I'm running cm nightlies which already have LTE. Maybe someone could try it out on the stock ROM.
Knight-Rider said:
I definitely agree with you on that. Maybe if we send feedback next OTA update will include LTE =)
Click to expand...
Click to collapse
Or at least a option to swap the two if the user wants to swap it. I get told "wah your phone doesn't get LTE?!" when in actuality it does but everybody is so used to seeing "LTE" instead of "4G" when in reality, LTE is 4G but marketed differently.
zephiK said:
Or at least a option to swap the two if the user wants to swap it. I get told "wah your phone doesn't get LTE?!" when in actuality it does but everybody is so used to seeing "LTE" instead of "4G" when in reality, LTE is 4G but marketed differently.
Click to expand...
Click to collapse
That would be a great suggestion to be able to swap between the two. I bet it's the iphone fanboys that tell you that lol HATERS.