Really sorry to say that Google Wear OS & Mobvoi intentionally are not addressing the problem, I am simply saying that eSIM installation option must be provided in Google Wear OS and its Mobvoi responsibility rather than saying that Cellular function is not available for Pakistan or other countries except for UK, Germany & Spain? Only Google Wear OS supporting the Mobvoi & Vodafone monopoly rather than addressing the problem. Hope you will understand the problem that cellular services is the secondary issue, only need option to install the eSIM in Google Wear OS, pethatic and non justified policy rather than option of network unlock like most of the other smartwatches.
Related
Sorry if this was asked before...
I am about to buy an imported Nexus One, I will use it on a GSM carrier in another country (google doesn't sell it here).
In the future, when there will be an official firmware update available, who be will providing it to consumers ? Is it Google, HTC, or only the official carriers like T-Mobile ? Will I be able to download it somewhere, or will I unable to upgrade without voiding the warranty ?
Thanks
you will most likely be able to manualy update by downloading and installing it your self.
htc will look at the official site
It will be FOTA...
How does OTA updates work, technically ? Does it need a special cooperation of my service provider or is it via any internet connection ?
I remember the OTA updates for the G1 needed to be pushed by the service provider, and if your carrier doesn't want you to have the update, you'd never have it. I hope it's not like that for an unlocked phone but I haven't found any info anywhere about that.
This is what I know + my personal logic: an ota is data so its going to be over your internet. And your provider will have to allow it. For those with tmo obviously otas come no problem, tmo expects to push them for google. I've never gotten one I'm always too impatient and I do it manually. So you'll receive it through your data connection but the always available alternative is to manually update it. The point is, even if a carrier prevents it from transmitting, it'll end up online and you will be able to get and install it. And it doesn't require rooting or any special level of knowledge in my opinion.
What about for those who TMO has no idea that we are currently running this phone? Will the OTA still be available?
Thanks
Yes every firmware update so far has turned up on the web to be installed manually. I don't anticipate the next update to be any different in that regard. It isn't google or a carrier but smart consumers who have received the ota and are nice enough to put it on the internet for public consumption
DMaverick50 said:
Yes every firmware update so far has turned up on the web to be installed manually. I don't anticipate the next update to be any different in that regard. It isn't google or a carrier but smart consumers who have received the ota and are nice enough to put it on the internet for public consumption
Click to expand...
Click to collapse
I was prompted by by N1 to check for updates and did so OTA via the phone.
On the google forum, one of the google employees said that the phone can check a google server for updates, and then you can choose to download over wifi or 3G, and install.
unfortunately the forum won't let me post an external link... so I can't show you the thread
post the link please
you can just add some space in the URL , or just remove the ht from h t t p . we can understand it .
the information is important.
h t tp ://www.google.com/support/forum/p/android/thread?tid=24211ae486d5b412&hl=en
note that this response was chosen as best response by a google employee
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.
I live in Singapore but recently I came to Iran, for some reasons I had to factory reset my phone, and when I try to turn on google now it says not available in your country, when I came from Singapore it was working fine. With kitkat, it is possible by disabling Play Services like THIS but I use Lollipop and it does not work and What ever I do it finds out I'm in Iran. I used Fake Location, US VPN, a foreign sim card but it does not work. The problem is that Play Services it more involved in Lollipop and controls most of google futures. I'm getting a Moto 360 next week so I really want google now. Is there Any Solution?!?!?!?
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
I would defer to my boss or VZ corporate lest I get fired for doing the "wrong thing", which I learned on an internet forum!
UNBELIEVABLE
Sent from my SM-G900V using XDA Free mobile app
YamiYaiba said:
Okay, I'll start with a little background. I'm a Verizon Wireless employee, and the store's resident Android nerd. That said, I'm stumped on something.
With the recent government ruling about sim-unlocking phones, we've seen an influx of devices from other carriers. Honestly, we've not been trained on how to handle these. Popping active sims into the phone typically activates them just fine, but we've been running into issues with SMS pretty frequently. Also, having AT&T firmware on a Verizon device is weird too, and can result in some odd behavior with baked in features.
With regard to the SMS issues, my immediate first thought was to edit the APN settings. Those are greyed out on a lot of devices I've seen though. So now I'm thinking something needs to change in the firmware. We do not have the ability to flash firmware* though.
We recently had a customer come in and activate 12 sim-unlocked US Cellular GS5s.They report that everything is working except SMS. What do I do?
*We do have an unapproved laptop laying around, and I do have Kies installed on it. I've never used it though, and nobody in the store wants to be liable for bricking a phone. With the right customer, I'd be willing to try it through Kies if that's something it is capable of. But as a large store, that's not a viable solution for most customers.
Click to expand...
Click to collapse
No offense, I'm actually trying to do the opposite and move my Verizon S5 and S3 to T-Mobile. (Verizon phone reps, through six separate phone calls, gave me six different stories of how to unlock my phone. I'm experiencing hiccups as I go - T-Mobile gave me some misinformation as well.)
They were able to change a lot of settings for their network, there are still SMS issues and other random odd issues. Maybe that's the nature of it?
I haven't looked into this in over a year, but I was under the impression that Verizon operates on an IMEI white list, i.e. ONLY Verizon branded phones are allowed on the network. When a user attempts to activate a phone on the network, it's IMEI is checked against the list of IMEIs for every phone Verizon has sold. If it's IMEI is not on that list because it's a non-carrier branded phone or it's another carrier's version of the phone it will not be allowed on the network regardless of hardware compatibility.
From what I recall, this was also the reason that Nexus 7 LTE buyers were screwed by Verizon. Verizon was advertised as supporting the tablet because legally they had to due to the open access provision they agreed to when they purchased their LTE spectrum. Up to that point Verizon had operated with a white list as I described above. They were able to get away with this despite the open access provision because they run voice and text over the older 2G and 3G networks on which they have not agreed to open access. When the tablet came out, for months Verizon had no system in place to activate it because the IMEIs were not on the white list. Users were able to successfully connect to the network with a SIM activated in another tablet proving that it was not a hardware issue.
Has this changed in the last year? If so that great news!
---------- Post added at 12:25 PM ---------- Previous post was at 11:58 AM ----------
I just Googled it, and based on information from November when the Nexus 6 came out, Verizon still operates on a white list, but it's only for activating NEW LINES. Verizon will not allow you to activate a new line with a non-Verizon branded phone, however, once the SIM has been activated, if it is placed in a non-white listed phone, that phone will be allowed on the network.
Some people suggest that you can take the IMEI of a floor model at the Verizon store and enter that when you order a SIM CARD, and that will allow for activation. I cannot personally verify this as I'm not a Verizon customer, and I'm not sure if the SIM activation process requires an actual phone with a white listed IMEI.
---------- Post added at 12:51 PM ---------- Previous post was at 12:25 PM ----------
Also OP, have you verified that the handsets with SMS problems support all of Verizon's 2G and 3G network frequencies? From what I recall, Verizon still runs voice and SMS over its legacy 2G/3G networks. I'm not sure if they've implemented Volte yet, but it's likely that older handsets and even some newer ones don't support it, especially if they don't have a Verizon ROM. It's possible that a handset could support only Verizon's LTE frequencies or support everything except it's 3G frequencies for example. If it supports only the LTE frequencies, data could work while voice and SMS don't. If voice and SMS are run over different frequencies it's possible that only one of the two will work.
Information on supported frequencies can be tough to find for phones sold in the US. The information is readily available for the same phones sold anywhere else in the world. The most plausible explanation is that this is because the US carriers insist upon it. They've been forced to start unlocking phones that in the past they've been able to permanently lock to their own networks for domestic use. To combat the emergence of a free marketplace where customers are free to move to a carrier offering a better deal, the carriers have started specifying that their carrier branded versions of the phone be shipped with firmware (possibly also hardware variations) that does not support the frequencies of other US carriers. That way, the phone is "unlocked," but it still won't work on other US networks, so they've managed to sidestep the legislation and continue screwing over consumers.
If the supported frequencies aren't listed on the manufacturer website, you can find them in FCC testing documents.
If customers do have a problem where voice or SMS doesn't work because the frequency isn't supported, they could use a Google voice number for calls and SMS over the data network using the Hangouts app. It works great for me. Your employer definitely would not approve of this suggestion though, since it compromises the way they've artificially limited their technology to force consumers to pay more. All calls and texts to/from a Google voice number are totally free when you're on a Wifi network, and the number is device agnostic, so there's no barrier at all to switching phones or carriers. Verizon wants to use your phone number to make switching as inconvenient as possible, so they don't want you using a cloud based phone number.
Samsung holds your phone hostage!
1. Blocks you from factory resetting your phone even when you provide your identity (You really have to go above and beyond to prove that you are who you say you are even with an unlocked phone)
2. Samsung stores your information and continuously uploads your information from your phone photos texts and all even when you disable items it reenables and blocks you from making changes in system settings
3. Tech support is not in the US in fact it isn't even in Asian perse it's in Indonesia or Pakistan and the customer service is in my experience not so friendly
4. The fact that you have to provide your full address, full name and date of birth for security reasons and it still doesn't count unless you provided every number you ever used with the device this is TRACKING You
5. Why is Samsung like Google so hell bent or survielence of it's users... You spend money for your device and they continue to act like youre an renter of the device instead of the owner.
5. My device is an unlocked South American device although I am in North America. Once I get this matter sorted out with Samsung I am selling off all of their devices Will never purchase anything from Samsung again. Also stay clear of Google, Microsoft and Amazon devices. So many things that I could say that are a security risk and a true risk to national security... The countires taht are at war with each other are also in cohoots together if you look at the security certificates on your phone. You attempt to delete, remove or disable those items Google and Samsung will diable your phone... block you from browsing the net, can block your camera, block you from doing basic things with your phone that you own. This is telecommunications/technological terrorism and warfare.