Related
I know there are several other threads that deal with the titular separate topics...I even started one myself before the phone was released. However, I wanted to make this thread to pool all the relevant questions about the general topic of NFC on this phone under one roof, as it were, since almost none of the following questions have been answered very thoroughly.
1) What is the status of ISIS compatibility on this phone? Version 1.09, I can personally confirm, works fine with the Verizon variant, but the app has recently been marked as incompatible on Google Play. The ISIS webpage only lists the AT&T variant of the Note 3 as compatible with the service, which seems inconsistent. Verizon also doesn't seem to have updated their branded version of ISIS to 1.9 alongside T-Mobile and AT&T, so it's extremely confusing, and I want to know whether the app will continue to be supported on the Verizon Note 3 or not?
2) What is the status of Google Wallet tap-to-pay? It's fairly obvious that the normal, non-NFC version of Google Wallet works properly, but I haven't heard anything definitive on the status of bringing the tap-to-pay version to the Verizon variant. One thread suggested that it may be more difficult to do than simply changing the build.prop to the Sprint version and adding the required SE authorization keys, so what's the status?
3) Related to question 2: Does the Verizon variant of the Note 3 even include an embedded secure element? It's fairly easy to acquire an SE-enabled SIM card from Verizon, but one thread awhile back suggested that the phone may not even include an embedded SE, and also suggested that that was what was holding up (or, rather, making impossible) this phone's Google Wallet port. Can anyone with authority on this phone's hardware answer this question?
Again, sorry if this seems redundant--these are just loose ends, and I thought it would be useful to bring them into one thread for coherence.
Reading up on some of the other threads the non Sprint variants do not (by default) have the required libraries flashed (Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc), although since the hardware is the same, flashing the required libraries (properly) should not bork the phone. From this question 3 could be answered as "There should be a hardware based secure element in the phone".
For question 1) it is quite possible that ISIS may be on the downslope. From September 20, 2013, PC Mag was reporting that Capital One was dropping supporting for ISIS Capital One Drops Support for Isis Mobile Wallet with a zdnet report on a CTIA panel discussion Mobile payments: Are we there yet? CTIA panel talks up Isis.
For question 2) it's hard to tell at the current moment. The reason being is obviously about the physical secure element required. With the latest version of android (4.4 'KitKat'), Google collaborated with Doug Yeager and Ted Fifelski (of SimplyTapp) to bring Host Card Emulation to the official builds of Android (Google gets around the carriers with Host Card Emulation for NFC payments).
Back in 2012 SimplyTapp proposes secure elements in the cloud/ both of these gentlemen approached the problem of the inaccessible secure element by 'using the cloud' (or more technically accurate, an active data connection) to emulate the secure element. The only caveat was because the official builds of android didn't include the libraries required for HCE (ie ISOPcdA, ISOPcdB, etc) that was built from starch via Doug Yeager (GitHub Repo for the NFC libaries) could only be included in forked, unofficial builds of Android, most notably the CyanogenMod Roms (Emulating a PKI smart card with CyanogenMod 9.1).
With Google taking the cloud approach it is possible that Wallet may eventually work on all NFC phones running 4.4 (and hopefully on unofficial builds including the CyanogenMod Roms.
Hope this helps
Joe
Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?
deputydog95 said:
Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?
Click to expand...
Click to collapse
No, unfortunately. If you have a Sprint Note 3 then it already works, and if you have an AT&T/Verizon/T-Mobile model then Host Card Emulation isn't supported at all by the NFC chip. Kind of seriously aggravating that they went with a different NFC chip in those models, if you ask me. I really love the Note 3, but I absolutely will not be getting a Note 4 unless HCE is supported by the hardware AND the software; if it's available on some carriers, but not on the AT&T models, then I'll almost certainly change carriers.
Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).
PGHammer said:
Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).
Click to expand...
Click to collapse
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.
gunz.jones said:
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.
Click to expand...
Click to collapse
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.
PGHammer said:
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Thanx for this
gunz.jones said:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Click to expand...
Click to collapse
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)
PGHammer said:
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)
Click to expand...
Click to collapse
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums
gunz.jones said:
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums
Click to expand...
Click to collapse
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.
PGHammer said:
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.
Click to expand...
Click to collapse
I use it for pogo and that's about it.
Advanced Calling Features on MVNOs
gunz.jones said:
I use it for pogo and that's about it.
Click to expand...
Click to collapse
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)
PGHammer said:
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)
Click to expand...
Click to collapse
Pokemon go. WiFi calling doesn't work on vzw mvno.
gunz.jones said:
Pokemon go. WiFi calling doesn't work on vzw mvno.
Click to expand...
Click to collapse
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.
PGHammer said:
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.
Click to expand...
Click to collapse
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.
gunz.jones said:
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.
Click to expand...
Click to collapse
Advanced feature, remember? I get that. Somehow, I got SIMless operations straightened out (V firmware). I'm right now waiting on two things - the latest security update (have any of you on a VZW MVNO but VZW firmware gotten it yet?) and to grab a Tracfone SIM (I'm going local retail for that - likely Dollar General, as they are the closest retailer that carries them).
Just sharing this, just incase anyone wasn't aware.
My son got Andriod Pay working on his P9000 - credit goes to the Universal SafetyNet Fix by Deic here:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Simply instructions if already rooted with Magisk here:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=13626#lastpost
Andriod Pay works fine for him with no issues at all on my old P9000 (which I gave him) :good:
It works. Well done and thanks for posting.
jbs4 said:
It works. Well done and thanks for posting.
Click to expand...
Click to collapse
No probs, glad it helped
It does not work for me.
Maybe because I had superSU installed.
I unistalled superSU and reinstalled magisk v12 with magiskSU but still does not work (neither stable nor beta version of the module).
Any suggestion other than reinstalling the ROM again?
Thanks.
Edit
malomehi said:
It does not work for me.
Maybe because I had superSU installed.
I unistalled superSU and reinstalled magisk v12 with magiskSU but still does not work (neither stable nor beta version of the module).
Any suggestion other than reinstalling the ROM again?
Thanks.
Click to expand...
Click to collapse
As far as I know my son did do a fresh install of Nougat 7, (as he had issues initially with this fix) then installed TWRP recovery and rooted with Magisk 12 (just using Magisk - no SuperSU installed), just make sure in Magisk Manager app that Busybox, Magisk Hide and Systemless Hosts. are enabled in the settings. Not sure if that helps, but my sons is rock solid, SafetyNet Passed Green all the tie and app runs with no issues.
Btw remember to not have any other modules active in Magisk (obviously apart fromUniversal SafetyNet Fix v1.10.1) while setting up, even after successful setup "some" modules may affect this fix, check the thread at https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431 for more about that
It does work, great job just unfortunately for me it doesn't work in my Country. Thanks any way
I finally made it work.
My problem was the Magisk Manager version I was using, 5.0.2.
I downgraded to Magisk Manager 4.3.3 where the settings are totally different and applied the settings from the screen shots of the first post and that did the magic.
Thanks for all the information provided.
Has anyone successfully completed an android pay transaction? I have successfully registered 2 cards but I am not getting any action at Costa's terminal in UK.
fillippe said:
Has anyone successfully completed an android pay transaction? I have successfully registered 2 cards but I am not getting any action at Costa's terminal in UK.
Click to expand...
Click to collapse
I tried at an M&S shop but nothing happened, or so I thought. However, awhile later I got a message from the Android Pay app asking did I have a problem as it knew an attempt had been made. One of the suggestions was that I needed the screen on at the time for it to work, which I didn't do. I thought I had read that the screen didn't need to be on but obviously it does. I haven't a a chance to try it again yet.
Does this still work if I update Magisk to 13.1?
techtalkonline said:
I tried at an M&S shop but nothing happened, or so I thought. However, awhile later I got a message from the Android Pay app asking did I have a problem as it knew an attempt had been made. One of the suggestions was that I needed the screen on at the time for it to work, which I didn't do. I thought I had read that the screen didn't need to be on but obviously it does. I haven't a a chance to try it again yet.
Does this still work if I update Magisk to 13.1?
Click to expand...
Click to collapse
I've updated to 13.1 and it's still passing safetynet.
Does anyone know where the NFC contact area is on the phone?
I've tried 4 times, twice with visa debit and twice with amex. Last 2 times I got the green tick but the payment machine did not react. Very last time I got a message saying something to the effect "we can tell your device is not untouched!", so they could not go forward with the payment, because it couldn't be secure.
So, for me, android pay is still not working.
Haven't tried a payment on the phone yet, however, i did have to modify the build.prop to fully emulate a Nexus 6 and allow me to download android pay from the play store.
Original build prop:
ro.build.flavor=full_c239v55_dx-user
ro.product.model=P9000
ro.GYRO_CALIBRATION=AGOLD_GYRO_CALIBRATION_SUPPORT
ro.product.brand=Elephone
ro.product.name=Elephone
ro.build.tags=release-keys
ro.product.device=Elephone
ro.product.board=Elephone
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Elephone
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6755
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Elephone
# Do not try to parse description, fingerprint, or thumbprint
CURRENT BUILD.PROP
ro.build.flavor=full_c239v55_dx-user
ro.GYRO_CALIBRATION=AGOLD_GYRO_CALIBRATION_SUPPORT
ro.product.model=Nexus 6
ro.product.brand=google
ro.product.name=shamu
ro.product.device=shamu
ro.product.board=shamu
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Motorola
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6755
# ro.build.product is obsolete; use ro.product.device
ro.build.product=google
# Do not try to parse description, fingerprint, or thumbprint
You will notice, some of the lines have been changed, *ro.build.tags=release-keys* - deleted from between ro.product.name and ro.product.device, as there are two of these in the file. I also moved the ro.product.model to below the GYRO line, I don't know if that will make any difference.
These changes were made, after I found that android pay was "compatible" with my Zopo speed7+ in playstore, that phone doesn't even have NFC.
These lines also open up google dialer v10 and other google only apps which may or may not work. I also have the latest pixel experience working too. this may even sort out the spam caller issue.
N.B. You will still need Magisk running to pass the safetynet.
Update:
For those of you who are reporting that android pay does not register with the card reader on your P9000, it is most likely due to the type of NFC chip that the phone has. The main standard that supports contactless payment, is Mifare which, is an NXP brand name. Obviously Elephone weren't going to shell out on an NFC chip that is going to cost them megabucks, not when they can fit one that costs pennies. By the time anyone has realised that android pay will never work, the phone will no longer be supported, hey presto, you've sold every unit you needed to make to be in profit, and hoodwinked everyone into thinking that the phone is android pay compatible.
Anyone noticed that Elephone have made no more phones since, with NFC, they have returned to hotknot, which doesn't do much at all.
As I am usually browsing the S8 threads these days in XDA, I just noticed the comments on this thread & thought I would update on this. I spoke to my son and asked him if he was finding using the Andriod Pay app ok on the phone (he works over in Germany so I dont speak that often to him) He has said that he only managed to use the app on one occasion in Sainsbury's while here in the UK, however hasn't used again as he was constantly getting issues at paypoints and couldn't work out why ?? He would then receive an email from Andriod Pay saying something like "We see you had issues using andriod pay" etc & to "ensure the handset is actually on when using the app" He tried all that but to no avail & kinda gave up. He thought maybe it was just his card that he had registered.
So maybe the NFC chip (as stated above & doesn't surprise me one bit when it comes to Elephone) is a cheapy and simply not fit for purpose. My sons now using his mates Sammy S7 now, so no longer uses the P9000.
Unfortunately, it seems as much as you can install the Andriod App . add cards and bypass the security with SafetyNet Fix etc.. when it comes to actually working fully at the paypoint seems to be a mystery / hit n miss, it may work sometimes and other times it wont ;-( I guess the fact Google themselves stated the handset isn't compatible with Andriod Pay (as read HERE) is an indication that maybe its just not possible to use it with the P9000 after all
Ah well ;-( .. I thought I would initially share this as I though "finally" you would be able to use Andriod Pay, but seems this just isn't the case, well without issues that is
jotei66 said:
As I am usually browsing the S8 threads these days in XDA, I just noticed the comments on this thread & thought I would update on this. I spoke to my son and asked him if he was finding using the Andriod Pay app ok on the phone (he works over in Germany so I dont speak that often to him) He has said that he only managed to use the app on one occasion in Sainsbury's while here in the UK, however hasn't used again as he was constantly getting issues at paypoints and couldn't work out why ?? He would then receive an email from Andriod Pay saying something like "We see you had issues using andriod pay" etc & to "ensure the handset is actually on when using the app" He tried all that but to no avail & kinda gave up. He thought maybe it was just his card that he had registered.
So maybe the NFC chip (as stated above & doesn't surprise me one bit when it comes to Elephone) is a cheapy and simply not fit for purpose. My sons now using his mates Sammy S7 now, so no longer uses the P9000.
Unfortunately, it seems as much as you can install the Andriod App . add cards and bypass the security with SafetyNet Fix etc.. when it comes to actually working fully at the paypoint seems to be a mystery / hit n miss, it may work sometimes and other times it wont ;-( I guess the fact Google themselves stated the handset isn't compatible with Andriod Pay (as read HERE) is an indication that maybe its just not possible to use it with the P9000 after all
Ah well ;-( .. I thought I would initially share this as I though "finally" you would be able to use Andriod Pay, but seems this just isn't the case, well without issues that is
Click to expand...
Click to collapse
Strange thing is, I tried mine in a Sainsbury's tonight, and it worked there. I will try this in a few other places and report back, it obviously does depend to the NFC chip installed in the reader, I also have a company Blackberry DTEK50, which does support Mifare NXP, that never seems to have any issues with Android pay.
However, after the mods I've made to the build.prop file, i may not get so many issues, as I was able to install android pay through Play store, when I tried to install it through an unofficial source, my bank wouldn't authourise the card.
so, we're now able to install Android Pay with these tricks, but we're not able to make payments with it? hahaha, that's so elephone
farsiray said:
so, we're now able to install Android Pay with these tricks, but we're not able to make payments with it? hahaha, that's so elephone
Click to expand...
Click to collapse
It ain't working for me...
This guide no longer seems to work.
Whenever I try to install the safety fix it says "installation failed", no error messages.
I've been using Android Pay for a while now on my P9000 - I'm on Deepflex's LineageOS ROM (14.1) with Magisk and the Universal Safetynet Fix. When I first added my card it was blocked by the bank, but after a brief phone call they authorised it and I've been using it at my local Co-op supermarket without issue.
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked. I was sure it would work with project fi and even project fi said it would work. Well, it really does mostly work. I was able to activate it and do just about everything, but I noticed 2 things:
1. No option to enable wifi calling
2. No access to visual voicemail.
I figured I could just install the regular google phone app to gain access to those things, but the google phone app doesn't enable that stuff. And when you make a call, it appears to switch over the LG phone app.
I don't see why this shouldn't work with Project Fi, but I have no clue how to enable those things. Calling on Tmobile and sprint work, texts etc work, it's just those two things that don't work
Would really love to use this version since it's quite a bit cheaper than buying the Fi version.
bytemare said:
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked......
Click to expand...
Click to collapse
I don't have this device but, the following thread looks like the same/similar discussion than your question for the same device. It may be helpful for you.
https://forum.xda-developers.com/showthread.php?t=3813572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Same exact situation here...times three. I bought three of them for family members hoping there would be some way to make the Amazon V35 fully-functional on Project Fi. No visual voicemail would be acceptable, but lack of wi-fi calling is a deal-breaker for me. Any idea if it's even possible to get that working on this phone?
Ironically, wi-fi calling IS installed on the phone (visible by viewing installed system apps), and when I am in an area *with* wi-fi but *without* cellular service, it is trying to connect to wi-fi calling but can't with an "ER081 - Unable to Connect" error.
Any options here?
Thanks much!
Thanks ! It looks like it's just a matter of removing a couple of the lg apps and replace them with Google apps, like the dialer. I don't know if this is even possible or not so I may just return the phone. It would seem like just replacing the dialer would make a big difference though....
bytemare said:
Thanks ! It looks like it's just a matter of removing a couple of the lg apps and replace them with Google apps, like the dialer. I don't know if this is even possible or not so I may just return the phone. It would seem like just replacing the dialer would make a big difference though....
Click to expand...
Click to collapse
I have the At&t V35 and I was able to install the Google Dialer directly from the Play Store. This is the first non Google device I've ever used that let me install the official Google Dialer from the Play Store. It really does make a big difference.
Can you remove the Amazon stuff?
Ok, so I made some project on this -- I got visual voicemail working. All I did was download the phone app, made it default for phone , gave it some permissions and I got all of my visual voicemail.
As for wifi calling, I can't get it to work. I downloaded google connectivity services (strangely, you can't search for it in the play store, but if you do a web search, you'll get a link to it in the play store), I gave it all permissions, etc, and actually I got ONE wifi call to work, but after that I just keep getting "ER081, Unable to connect." So wifi calling doesn't work and I'm not sure what the trick is to make it work. Everything else SEEMS to work, but since wifi calling doesn't work, I wonder if there is anything else that is broken that I'm not seeing.
I don't think you can remove the Amazon apps but they aren't intrusive at all. I got this on prime day and I'd keep it if I could get that wifi calling to work :/
How do I test Wi-Fi calling. Have the same V350ULM on verizon.
I have been playing with hidden settings but really don't know what I am not I am doing and seems like a lot of damage can be done in there using the "Nova Launcher" using the activities widget.
Warning: can really mess up the phone. Be careful and let me know what you find. I am also looking to enable video calling on Verizon.
Thank you
So I got this device from Amazon, and I've had nothing but issues with it.
Originally got it for Verizon, as it says on the Amazon page that it supports the Verizon network, which is partially true. I can make calls and texts and use data on the Verizon network, but literally don't get ANY of the advanced calling features, such as Premium voicemail, or WiFi calling, which is what I needed.
After looking into it, I determined that it was becuase it was an unlocked phone, and I am just not going to get those services to work on the Verizon network.
So my thinking was to switch carriers to Google Fi, since all they do is service unlocked phones. I got the SIM card yesterday, downloaded the Project Fi app, activated and ported over my number from Verizon. All seemed good, except as soon as I finished activation, I kept getting hit with this WiFi Calling Error: ER081 "Unable to Connect".
I first attempted to use only WiFi to do stuff on the phone. I turned on airplane mode, then turned on WiFi, and started testing. I first sent and received SMS and MMS using the standard Android Messages app, and that worked fine.
I then attempted to make a call, and it failed. The phone app wont even attempt to dial out, as it states that 'Airplane Mode' is enabled. That Error: ER081 keeps popping up.
I've been dealing with Project Fi support for the past 12+ hours now trying to figure this out, going through all the BS, they wanted me to install the Hangouts App and Hangouts Dialer, and that works over WiFi, so they were trying to say problem fixed (only if I use that app). That is not a solution.
Has anyone had any better luck with this device on any other carrier, with ALL advanced services and calling features functioning 100%?
I feel like this is a carrier service issue, and not a device hardware issue.
robdarftw said:
So I got this device from Amazon, and I've had nothing but issues with it.
Originally got it for Verizon, as it says on the Amazon page that it supports the Verizon network, which is partially true. I can make calls and texts and use data on the Verizon network, but literally don't get ANY of the advanced calling features, such as Premium voicemail, or WiFi calling, which is what I needed.
After looking into it, I determined that it was becuase it was an unlocked phone, and I am just not going to get those services to work on the Verizon network.
So my thinking was to switch carriers to Google Fi, since all they do is service unlocked phones. I got the SIM card yesterday, downloaded the Project Fi app, activated and ported over my number from Verizon. All seemed good, except as soon as I finished activation, I kept getting hit with this WiFi Calling Error: ER081 "Unable to Connect".
I first attempted to use only WiFi to do stuff on the phone. I turned on airplane mode, then turned on WiFi, and started testing. I first sent and received SMS and MMS using the standard Android Messages app, and that worked fine.
I then attempted to make a call, and it failed. The phone app wont even attempt to dial out, as it states that 'Airplane Mode' is enabled. That Error: ER081 keeps popping up.
I've been dealing with Project Fi support for the past 12+ hours now trying to figure this out, going through all the BS, they wanted me to install the Hangouts App and Hangouts Dialer, and that works over WiFi, so they were trying to say problem fixed (only if I use that app). That is not a solution.
Has anyone had any better luck with this device on any other carrier, with ALL advanced services and calling features functioning 100%?
I feel like this is a carrier service issue, and not a device hardware issue.
Click to expand...
Click to collapse
For me it worked if I reset the phone back to stock, and turned it off. Put the Fi SIM in, went through setup, installed the Fi APP, let it do it's config thing, THEN tried to make a call. For me it then worked on WiFi.
bytemare said:
Hi, I just picked up on those Amazon Prime phones, LG V35 unlocked. I was sure it would work with project fi and even project fi said it would work. Well, it really does mostly work. I was able to activate it and do just about everything, but I noticed 2 things:
1. No option to enable wifi calling
2. No access to visual voicemail.
I figured I could just install the regular google phone app to gain access to those things, but the google phone app doesn't enable that stuff. And when you make a call, it appears to switch over the LG phone app.
I don't see why this shouldn't work with Project Fi, but I have no clue how to enable those things. Calling on Tmobile and sprint work, texts etc work, it's just those two things that don't work
Would really love to use this version since it's quite a bit cheaper than buying the Fi version.
Click to expand...
Click to collapse
Man, I just bricked mine last night trying to flash Google Fi variant to my new phone ATT and I htink it has wifi calling on it sighhh...
Any one know how to unbrick it ? I've searched but so far it's only for the V20 or V30 but havn't seen one for V35 yet.
KennynGGG said:
Man, I just bricked mine last night trying to flash Google Fi variant to my new phone ATT and I htink it has wifi calling on it sighhh...
Any one know how to unbrick it ? I've searched but so far it's only for the V20 or V30 but havn't seen one for V35 yet.
Click to expand...
Click to collapse
KennynGGG, just want to confirm something. You flashed a ROM onto your LG V35 ThinQ? How did you unlock the bootloader - has some kind of exploit been discovered?
Toxeia said:
KennynGGG, just want to confirm something. You flashed a ROM onto your LG V35 ThinQ? How did you unlock the bootloader - has some kind of exploit been discovered?
Click to expand...
Click to collapse
I never got to that partt...using this tool I was able to dump then it bricked.
https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23
KennynGGG said:
I never got to that partt...using this tool I was able to dump then it bricked.
https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23
Click to expand...
Click to collapse
Well, being a noob and all I wasn't sure but are you saying that the bootloader has to be unlocked in order to flash any rom in cluding the same Rom Albeit different carrier ?
I just got me a V40 ThinQ thanks to Sprint. It's full of bloated stuffs though, I've never had a branded phone before or may be other company aren't as bad.
Anyway, I want to take a rom dump from the V40 and see if I can give my V35 a run before I send it in to LG for warranty repair. But when I tried uppercut to launch LGUP it still says the dll is out dated. I've tried it with my dll from V35 extraction. still not taking it. Any suggestion ?
KennynGGG said:
Well, being a noob and all I wasn't sure but are you saying that the bootloader.........
Click to expand...
Click to collapse
I don't have either devices but, Regarding the LG V40, the following area of the forum is specific to that device.
https://forum.xda-developers.com/forumdisplay.php?f=7911
The following thread is regarding the Debloating of the V40 as well.
https://forum.xda-developers.com/showthread.php?t=3857801
Regarding the V35, the following is the Enhanced Tag link that's specific to that device.
https://forum.xda-developers.com/t/lg-v35
I'm not sure which thread within the V35 ET would possibly fit what you're looking for but, you can always take a look and see if there's anything there that's helpful to you.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
I just finished flashing the Project Fi firmware to my Amazon V35 and it all went fine. Going to assume it's a simpler flash since the 2 are practically the same, even the firmware share the same version number. Before doing a factory wipe I tested WiFi calling by turning airplane mode on, wifi back on and made a call. Worked perfect. Did a factory reset on the phone to clear all the Amazon bloat and noticed that when the Project Fi app was activating service, it auto downloaded a sprint file/profile which I had never seen before.
I pulled the LGUP dll from the firmware and also modded it and LGUP for developer options. I only had to pick upgrade for it to work and was surprised how quick the flash actually was. I won't ramble anymore, but if anyone wants I can upload the modded dll and lgup exe that I used to flash.
metal409 said:
I just finished flashing the Project Fi firmware to my Amazon V35 and it all went fine. Going to assume it's a simpler flash since the 2 are practically the same, even the firmware share the same version number. Before doing a factory wipe I tested WiFi calling by turning airplane mode on, wifi back on and made a call. Worked perfect. Did a factory reset on the phone to clear all the Amazon bloat and noticed that when the Project Fi app was activating service, it auto downloaded a sprint file/profile which I had never seen before.
I pulled the LGUP dll from the firmware and also modded it and LGUP for developer options. I only had to pick upgrade for it to work and was surprised how quick the flash actually was. I won't ramble anymore, but if anyone wants I can upload the modded dll and lgup exe that I used to flash.[/QUOTE
I'd appreciate it if you could upload the moded LGUP Dev version....btw what version did you upgrade to ? and where did you download it from ?
Click to expand...
Click to collapse
KennynGGG said:
I'd appreciate it if you could upload the moded LGUP Dev version....btw what version did you upgrade to ? and where did you download it from ?
Click to expand...
Click to collapse
No problem, hopefully the zip file with the modded files is attached correctly to this reply. It's for LGUP 1.14
My phone was listed as V350ULM10f after the latest OTA update last month (I think it was just a security update). But that's the same version I used for the KDZ. I grabbed the firmware from here:
Firmware
Hopefully it works for you too.
Edit: Also forgot to mention, I had to put the phone into download mode for it to work correctly. Power the phone off, plug the cable into the PC, while holding volume up plug the usb cable into the phone and once you see download mode, release volume up. Then launch LGUP and it should find the phone and be good to go.
Ibuprophen said:
I don't have either devices but, Regarding the LG V40, the following area of the forum is specific to that device.
https://forum.xda-developers.com/forumdisplay.php?f=7911
The following thread is regarding the Debloating of the V40 as well.
https://forum.xda-developers.com/showthread.php?t=3857801
Regarding the V35, the following is the Enhanced Tag link that's specific to that device.
https://forum.xda-developers.com/t/lg-v35
I'm not sure which thread within the V35 ET would possibly fit what you're looking for but, you can always take a look and see if there's anything there that's helpful to you.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks Ibuprofen...I'll definitely check those out this weekend....I noticed the V40 Dev mode has "OEM Unlock" an option to turn on or off but that's probably isn't going to do any good without fastboot.
Bloatcrap
I currently have the Amazon 35.... Are you telling me I can get rid of all this bloatware just by flashing the original firmware?
If this is true I could kiss you on the mouth.
So I was rooting my Google store bought pixel 4 and missed a step. Needless to say I had to sideload a full ota to recover it. But I'm pretty sure I accidentally loaded the verzion version. I got all the verizon apps that showed up when I rebooted the phone. I went back and wiped everything in recovery mode and tried sideloading QD1A.190821.007.A3 and it keeps erroring out. This is the firmware that Im 90% sure what was on my phone. Is there a way to get back to factory google store firmware or am I screwed now? I am on a verizon sim but phone was bought on launch day from the google store. Its also noted that I am currently on QD1A.190821.014 firmware. This doesn't appear to be the verizon firmware.
The Verizon apps appear not based on which ROM version you load, but instead based on whether you have a Verizon SIM in the phone during setup.
If you loaded the wrong ROM onto the phone, you may not be able to recover by sideloading an OTA. You should be able to recover by doing a complete reflash of the image you want (the image version, not the OTA version).
What error is it giving you?
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
BubbaGumprc said:
I cant remember the exact error but it would error out about 45% through the flashing. I am currently running QD1A.190821.014 which appears to the google FI, T'Mobile firmware. I still have the ability to turn OEM Unlock on in my settings, so it appears I am ok. I just wish they had better wording on which firmwares for the unlocked ones form the google store and others.
Click to expand...
Click to collapse
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Jon8RFC said:
Regarding loading the wrong one, I did the same thing because the December update had a discrepancy between the announcement and the download page about which rom applies to which phones. I switched back and forth between QQ1B.191205.011 and QQ1B.191205.012.A1 before they finally corrected it, but everything worked fine on both versions as far as I could tell.
About the Verizon apps, if you're on Verizon or one of its MVNOs, if it installs other stuff, you'll want to leave it. Don't confuse My Verizon and My Verizon Services. My Verizon can be uninstalled, but if you mess with My Verizon Services, you'll end up losing things like wifi calling.
Click to expand...
Click to collapse
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
bobby janow said:
That's not true. You can go to all apps and show system. MVS can't be deleted without root but you can disable it with no adverse effects. They can't get into your device to see what you have installed and when you installed it, but who wants to give them that info anyway?
Click to expand...
Click to collapse
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Jon8RFC said:
As of Android 8, disabling My Verizon Services doesn't permit wifi calling because it depended on that application for that functionality. It's hard to remember what else was troublesome, but I thought there was something else which didn't function once it was disabled.
I don't have wifi calling anymore on Visible, and I never used Android 9 because of the wifi scan throttling mess anyway.
Would you mind checking that your wifi calling works on your pixel 4, disabling My Verizon Services, rebooting, switching on airplane mode, then enabling wifi only, and then try making a phone call? I'm interested to know if that behavior has changed. Thanks!
Here's some more information. It certainly seems true for others as well:
https://community.verizonwireless.c...ng-since-Android-8-update/td-p/1042025/page/2
And many other XDA threads correlating the two:
https://www.google.com/search?q=sit...69i57j69i58.6651j1j7&sourceid=chrome&ie=UTF-8
Maybe things have changed in Android 9 or 10, but please test it out if you haven't already!
EDIT:
It looks like you tested it out in another XDA thread already where others lost wifi calling when it was disabled, but you said you were still able to make wifi calls. It's strange that you're the only one who can disable My Verizon Services and make wifi calls, but others can't. Very strange.
Click to expand...
Click to collapse
My wife has a Verizon device Pixel 3 locked bl and I have a Pixel 4 and they both have MVS disabled and both can call on wifi. I just tested again to make sure. Really, I'm the only one? Gotta love that. I hate that they can get into my device without my knowing and see what and when I installed stuff.