I have been thumbing through just about every file in the system/vendor images and I think I found the file that needs to be fixed for Verizon WiFi Calling.
https://www.tinozplace.com/vendor.zip (decompiled vendor.img)
In vendor\mbn\mcfg\configs\mcfg_sw\generic\NA\Verizon\hVoLTE
The mbn file on line 398 seems to have the defaults to "Mobile Preferred".
-------
<Node>
<APN>vzwinternet</APN>
<RoutingRule>
<Node>
<AccessTechnology>1</AccessTechnology>
<AccessNetworkPriority>1</AccessNetworkPriority>
</Node>
</RoutingRule>
<RulePriority>1</RulePriority>
</Node>
--------
Access Network Priority 1. Which is Mobile Preferred. 2 is WiFi Preferred.
I don't know how to edit these files but if someone could help me find the way and recompile this vendor.img, it would really be a lot of help.
I could try to change it on my own but, I am guessing that it's not just as easy as editing text in this type of file.
Tony
Sent from my Pixel 2 XL using Tapatalk
Did you compare this to the Oreo version to see if it is different?
Google search found this...
https://sourceforge.net/projects/axbase/
abuttino said:
I have been thumbing through just about every file in the system/vendor images and I think I found the file that needs to be fixed for Verizon WiFi Calling.
Click to expand...
Click to collapse
Hi Tony... I've been researching the heck out of this issue as well and might can add a bit. From what I can tell browsing the source, the carrier-specific settings that you are seeing are being set from an XML asset in the CarrierConfig application. I registered to post this (after having been a lurker for a long time), so can't post a link. But search for this file, such as at android.googlesource.com (311480 is the Verizon code in the US):
carrier_config_311480.xml
The two settings that stand out to me:
<int name="carrier_default_wfc_ims_mode_int" value="1"/>
<boolean name="editable_wfc_mode_bool" value="false"/>
I completely admit I could be reading this wrong... I do Android development but not an expert in the setup/modding/etc. scene by any means.
Adam
nomisunrider said:
Did you compare this to the Oreo version to see if it is different?
Click to expand...
Click to collapse
I didn't. But I have not flashed my phone to RTM. I have been testing pie to find the hack. If I plan on going to Orlando Florida any time soon, I will have to put Oreo back on.
I had a heated discussion with Verizon Tier 2 and they just want to place a network extender in my home.. I don't live in Orlando, so it was kind of stupid that they offered me that.
Onwards.....
I did replace that file with Magisk. It didn't help. The next thing I'll try is QPST/QXDM
To the carrier_config.xml, I believe this is placed in the vendor partition. Is that correct?
Sent from my Pixel 2 XL using Tapatalk
abuttino said:
To the carrier_config.xml, I believe this is placed in the vendor partition. Is that correct?
Click to expand...
Click to collapse
Looks to be an asset in the CarrierConfig.apk, which is on AOSP... I am not certain if we could change that and re-compile, replacing it on the device with those properties changed. I assume this is in /vendor though I am not yet positive. I need to find time to dig through the phone and see.
RogueProeliator said:
Looks to be an asset in the CarrierConfig.apk, which is on AOSP... I am not certain if we could change that and re-compile, replacing it on the device with those properties changed. I assume this is in /vendor though I am not yet positive. I need to find time to dig through the phone and see.
Click to expand...
Click to collapse
I edited the mdn file that I mentioned in the OP and replaced it with Magisk. I'm not sure that it's being placed in time. Because it should work. I replaced all of the 1's with 3
Gleaning from the file where LTE isn't available, it showed 3.
Verizon also coded "no WiFi calling if LTE is between -115 and 29"
I went through this file with notepad++ and edited with HxD.
Sent from my Pixel 2 XL using Tapatalk
abuttino said:
I edited the mdn file that I mentioned in the OP and replaced it with Magisk. I'm not sure that it's being placed in time. Because it should work. I replaced all of the 1's with 3
Gleaning from the file where LTE isn't available, it showed 3.
Verizon also coded "no WiFi calling if LTE is between -115 and 29"
I went through this file with notepad++ and edited with HxD.
Click to expand...
Click to collapse
I hope you are successful with this... I ended up going back to stock because I needed the wifi calling soo bad. I haven't ran a stock phone ever!! Even my first smartphone... The AT&T Tilt was modded.
I am taking the weekend off but if anyone wants to look at the vendor partition in the driver's section of the images site, that's where I believe the uncompiled carrier_config xml is.
It's supposed to give you info of how to compile it on a Linux machine.
That's the next place I'm looking. Because, in order for QPST/QXDM to work, you need the user-debug key.
The only thing I've been unable to decompile is the radio partition.
I want to say this is probably borderline illegal for to Verizon for making us do all these things. It doesn't make sense for us to not be able to use wifi calling just because of the phone we buy. This is how Microsoft got into an anti-trust. I may file a complaint with the FCC/FTA for this.
Sent from my Pixel 2 XL using Tapatalk
abuttino said:
I am taking the weekend off but if anyone wants to look at the vendor partition in the driver's section of the images site, that's where I believe the uncompiled carrier_config xml is.
It's supposed to give you info of how to compile it on a Linux machine.
That's the next place I'm looking. Because, in order for QPST/QXDM to work, you need the user-debug key.
The only thing I've been unable to decompile is the radio partition.
I want to say this is probably borderline illegal for to Verizon for making us do all these things. It doesn't make sense for us to not be able to use wifi calling just because of the phone we buy. This is how Microsoft got into an anti-trust. I may file a complaint with the FCC/FTA for this.
Click to expand...
Click to collapse
At&t does the same thing....and to add to that illegal-ness... You can add discrimination because they only do it because it is not a carrier branded device so they withhold some carrier specific features but when you buy an iPhone directly from Apple and not from At&t or Verizon they allow those phones to utilize all the carrier's features but not the pixel purchased from Google. That is clear blatent discrimination!!!
I checked on the driver binary file for vendor. It was just a linux script to extract it, it has nothing new. It's just a way to get QPST working. The problem is, I can't seem to find one for DP5 to flash.
I would LOVE to know where this carrier_cofig xml file is.. Every post on it seems to show it the content of it but doesn't have the location of it.
I filed a complaint with the FCC.
It would be great if we still can get some work on this because Ajit Pai was an employee of Verizon (I am not sure if it was Verizon Communications or Verizon Wireless [two different companies]) and he's probably stacked the deck against us.
So, Calling All Devs!! Please Help!!!
nomisunrider said:
Did you compare this to the Oreo version to see if it is different?
Click to expand...
Click to collapse
Just looked.. It doesn't look like there are any differences.
The problem here is that when we were on Oreo, we still had the ability to do Wifi Preferred. Now, we can't because global settings (settings list global) doesn't respect that setting anymore.
As mentioned several times in the this thread, it is looking like "carrier_config" is now in charge of that setting with Verizon and I have been trying to find that file for the last week without any luck. It might be in QPST but there is no vendor partition for Developer Preview 5 that allows the userdebug/test-keys.
Thanks for the reply, sorry that it took me so long to get back to you.
Also... I looked at the file WfcActivation APK (/system/priv-app/WfcActivation) after decompiling it with APK Tool. This looks really promising as well. I thought I compiled the file properly but Wifi Preferred was still not an option..
It would be nice to know how we can apply settings in global before the phone boots and post-boot-fs. That way we could try stuff like wfc_ims_enabled and wfc_ims_mode.
I'll ask in the Magisk forums.
EDIT:
It appears that the Pixel does not use the common file structure for CarrierConfig. I downloaded a LGg7 ThinQ rom and it has it right there as plain as day. That's why I've been unable to find it. Google made it really hard for us to do this.
The FCC did decide to elevate this to Verizon Wireless. Couldn't believe it and how fast Verizon got back in touch with me.
Waiting on a Sr. Tech to tell me what's next. This is pretty much BS, so I would hope that I can get them to do something!
abuttino said:
The FCC did decide to elevate this to Verizon Wireless. Couldn't believe it and how fast Verizon got back in touch with me.
Waiting on a Sr. Tech to tell me what's next. This is pretty much BS, so I would hope that I can get them to do something!
Click to expand...
Click to collapse
Great job; thanks for pursuing this.
abuttino said:
Waiting on a Sr. Tech to tell me what's next. This is pretty much BS, so I would hope that I can get them to do something!
Click to expand...
Click to collapse
Wow, though I wouldn't hold my breath on them being able to do anything without changing that in the phone itself, huh? Still, keep us updated!
I haven't been able to find any more on my Pixel either - I concur that something seems different on the Pixels... or else I am missing something obvious. Kind of stuck at this point...
New update:
Verizon told me that 'it's just the way it is'
I complained back to the FCC regarding this and now they just let me know that Verizon must give a supplement for their horrible response in 14 days from today.
Just got this from the FCC about 5 minutes ago.
Thank you for your submission. Based on our review of the provider’s response to your Ticket No. ######, we are asking your provider for a supplemental response to your issue.*
Here's what you can expect from the FCC's informal complaint process:
-Your provider may contact you directly to resolve your issue.*
- The FCC's role in this process is to facilitate a conversation between you and your provider.
-Your provider is required to submit to the FCC a written supplemental response regarding your issue no later than 14 days from today.
- The FCC will not contact you until we receive a supplemental response from your provider.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
With all hope, the FCC will solve this issue. It's a built in function of the phone that they have no right to be blocking, just so you'll buy one if their other bloated phones.
Sent from my Pixel 2 XL using Tapatalk
My rebuttal to the FCC about Verizon's response in which they lied and spun.
Unfortunately, this case needs to remain open. Verizon's supplemental letter stated less than accurate facts about the Pixel and WiFi Calling Preferred.
Currently, Verizon is the only carrier that is authorized to sell the Pixel (1, 2, 3) and they've blocked WiFi Calling Preferred on all Pixel devices; Verizon purchased or Google purchased.
In my case, it was Google purchased.
Verizon has also stated that there are fundamental software differences between the Verizon Pixel and the one sold from Google. This is extremely untrue. Verizon locks the bootloader but as soon as a Verizon Sim card is inserted, the phone downloads roles and rules for the APN and their software (apps). So, blocking WiFi Preferred is a Pixel wide issue, no matter where it was purchased.
A WiFi call takes loads off the towers and, in areas with very low service, it gives people ways to conduct their business without hassle. Essentially, Verizon is enacting a very draconian rule to block this from our Pixel phones but no others that are issued by Verizon.
Essentially this is punishment for not buying a phone from Verizon Wireless.
Most recently, they have locked down Pixel 3 phones purchased from the Verizon store to the Verizon Network which was a clear violation of their agreement with the FCC.
It's apparent that Verizon is getting away with locking features out of phones and intrinsically devaluing the Pixel with no oversight from the FCC.*
With hope from thousands of members of the XDA forum and, myself, the FCC will investigate these nefarious practices by Verizon Wireless and put an end to them.
Click to expand...
Click to collapse
This is in response to Verizon's Supplemental letter to the FCC:
Dear FCC,
This letter is in response to the above-referenced complaint. Thank you for referring it to our office for
review. Customer expressed concerns regarding Verizon blocking Wi-Fi Calling on Google Pixel,
Pixe XL, Pixel 2, and Pixel 2 XL devices. Mr. Buttino stated Verizon blocks the Wi-Fi Calling Preferred
mode for phones that are either not locked to Verizon’s network or purchased from Google.
Our records indicate customer is an Account Manager on Account Number #####,
which has one line of service on The New Verizon Plan Single Smartphone 5GB. customer has a Google
Pixel 2 XL Non-Verizon Wireless device on his mobile number #########. Wi-Fi Calling allows you to
make and receive calls and send messages even when there is no cellular coverage. Customers with Wi-Fi
capable devices turn on HD Voice, enable Wi-Fi Calling, and need a Wi-Fi connection to make calls.
Verizon Wireless’ Technical Support thoroughly investigated customer's WiFi Calling complaint and
determined the device has used Wi-Fi Calling to place and receive calls. Verizon Wireless does allow non-
branded VZW devices that meet hardware requirements to operate on the Network. However, due to
software differences, certain functionality that Verizon brand devices offer may not function the same or be
available on non-branded VZW devices.
On October 10, 2018, I spoke with 'customer' to address his concerns and the findings. Customer has not
provided any new information that would warrant a change to our findings. As a result, Verizon Wireless'
position remains the same. Customer confirmed he had no additional account concerns. Customer
is aware regarding Verizon Wireless’ position in this matter.
Should the Federal Communications Commission have any questions, please contact S. Kashif using the
contact information you have on file. Should 'customer' have any questions or concerns, I may be
reached at 800-779-2067 ext. 2220935 between 8:00 AM - 5:00 PM (PST), Monday - Friday.
Click to expand...
Click to collapse
(Letter edited for private content)
Sent from my Pixel 3 XL using Tapatalk
Sent from my Pixel 3 XL using Tapatalk
The FCC ended the case with no action. Time for some hacks.
Sent from my Pixel 3 XL using Tapatalk
Related
The reason I ask is because I went to both verizon and sprint and i asked:
--at verizon--
Me: If I buy an Evo from sprint, full price and bring it here to run on your network will it work? being that both of you run CDMA I dont see it being a problem? am I wrong?
Verizon: No, it will not work. You should get our "incredible."
--at sprint--
Me: If I buy an "incredible" from Verizon, full price and bring it here to run on your network will it work? being that both of you run CDMA I dont see it being a problem? am I wrong?
Sprint: No, it will not work.
So I asked them both why not...?
Verizon: different hardware. And settings.
Sprint: Legality.
(they also said they have not had their training yet at that location for the evo... and they are only a few weeks away of a release. )
Can someone explain whats going on here? They made me doubt my understanding as to how cdma worked. It is to my understanding it should work on both networks. Question is, getting verizon to accept me as a customer with the evo. Someone correct me if im wrong.
Im set on the Evo, but I dont want Sprint. I want verizon. Not planning on getting the "incredible." For that I stick with the iphone 4g and att.
There are ways to do it, but they are quite illegal (as in rape you in the ass prison felony). Look it up online, but don't expect to find that info here.
kyleblakepeters said:
There are ways to do it, but they are quite illegal (as in rape you in the ass prison felony). Look it up online, but don't expect to find that info here.
Click to expand...
Click to collapse
Any chance for a little more clarification? A keyword at least to find my answer. I just want to know actually why they would reject a potential customer. I'm a little tired of smoke and mirrors.
I wouldn't want to do anything illegal like cloning. I just want facts. No big deal.
tried it twice...no go
only way would be to hack the phone and change a whole lotta stuff...then change the esn to another verizon phone you own (which is illegal, i believe). then it is possible. however, i have two phones (one alltel, one sprint) and have requested verizon to add my esn's to their database (after i changed the 'whole lotta stuff' myself) ...eventhough the phones work on verizon, i could never get them to add them to their database enabling me to legally use the phone on their network. i griped and griped, they 'caved' in on more than one occasion, and said it would be done, but never did it. 15-20 total calls? and still nothing. i can't wait to tell them i am leaving...and for that reason i am not on contract. they tried to tell me numerous times it "wouldn't work, different hardware" but i have even tested it and made calls successfully, so it all seems to be a game. the one department that was designed to allow this, apparently closed. bottom line, don't waste your time. by the time someone posts instructions on how to do it, their will be 2-3 verizon phones more powerful -it is still a long way off.
It's ESN switching. Sprint and Verzion never put each others ESNs on to the other's network. I don't think even Jesus could manage that feat.
adeyo said:
only way would be to hack the phone and change a whole lotta stuff...then change the esn to another verizon phone you own (which is illegal, i believe). then it is possible. however, i have two phones (one alltel, one sprint) and have requested verizon to add my esn's to their database (after i changed the 'whole lotta stuff' myself) ...eventhough the phones work on verizon, i could never get them to add them to their database enabling me to legally use the phone on their network. i griped and griped, they 'caved' in on more than one occasion, and said it would be done, but never did it. 15-20 total calls? and still nothing. i can't wait to tell them i am leaving...and for that reason i am not on contract. they tried to tell me numerous times it "wouldn't work, different hardware" but i have even tested it and made calls successfully, so it all seems to be a game. the one department that was designed to allow this, apparently closed. bottom line, don't waste your time. by the time someone posts instructions on how to do it, their will be 2-3 verizon phones more powerful -it is still a long way off.
Click to expand...
Click to collapse
Thank you! thats the answer I was looking for. Much grateful!
What about the users that pay full price? Why would they do that if they cant take it elsewhere? Does it mean Even if they pay full price, the ESN belongs to sprint? It sounds wrong to do that. Im not complaining. Im just trying to make sense of this.
0okami said:
It sounds wrong to do that.
Click to expand...
Click to collapse
Welcome to the world. Don't let the door kick you in the ass on the way out.
theres a form you can fill out to take a cdma phone from another carrier and activate it on verizon, you need to ship your phone to vzw HQ though, and they say it can take 3 weeks to determine if they will allow it on the network or not.
its an official verizon form just gotta find it.
tricknasty said:
theres a form you can fill out to take a cdma phone from another carrier and activate it on verizon, you need to ship your phone to vzw HQ though, and they say it can take 3 weeks to determine if they will allow it on the network or not.
its an official verizon form just gotta find it.
Click to expand...
Click to collapse
I'll check with the verizon rep. She was really friendly and what ever she didnt know she dug for papers. Maybe we can work something out.
I'll keep everyone posted if something results.
Thanks for the information!
will not work on verizon, they have a policy of not taking sprint branded phones, the esn's are registered to sprint and they know it's an evo.
sprint doesn't take anything other than what they've registered... it's a sticky thicket I know.
esn cloneing would work, but we don't talk about that kinda stuff here apparently, gotten scolded on more than one occasion for doing so =P
Too much chatter across multiple threads...
I found a temporary solution. I ported my number to AT&T. Thus far, coverage is fine, data speeds are disappointing only in the sense that where I am right now, I am getting less than the 8 Mbps Cricket would cap me at.* Cricket is apparently now owned by AT&T and now offers unlimited talk, text, and 20 GBs of LTE for $60.
My data worked upon activation.* It seemed my AT&T rep had to alter the IMEI associated with my prepaid account to get phone calls working.* Don't know if there will be any implications, but in the hour I have been with AT&T, some root apps (including Ultimate Dynamic Navbar, without which I have no Navbar) have force closed for the first time. Seems like coincidence but I guess not? This is happening regularly now, X many minutes after boot, and bluetooth is being disabled as well.
I hope that T-Mo gets this straightened out, unless AT&T really impresses me, I look forward to hopefully switching back to the $30 Wal-Mart 5 GB plan.
(I'm too lazy to delete all the pasted asterisks)
Possible Solution?
thref23 said:
Too much chatter across multiple threads...
I found a temporary solution. I ported my number to AT&T. Thus far, coverage is fine, data speeds are disappointing only in the sense that where I am right now, I am getting less than the 8 Mbps Cricket would cap me at.* Cricket is apparently now owned by AT&T and now offers unlimited talk, text, and 20 GBs of LTE for $60.
My data worked upon activation.* It seemed my AT&T rep had to alter the IMEI associated with my prepaid account to get phone calls working.* Don't know if there will be any implications, but in the hour I have been with AT&T, some root apps (including Ultimate Dynamic Navbar, without which I have no Navbar) have force closed for the first time. Seems like coincidence but I guess not? This is happening regularly now, X many minutes after boot, and bluetooth is being disabled as well.
I hope that T-Mo gets this straightened out, unless AT&T really impresses me, I look forward to hopefully switching back to the $30 Wal-Mart 5 GB plan.
(I'm too lazy to delete all the pasted asterisks)
Click to expand...
Click to collapse
I work for T-Mobile and have also have the same issues with my Z3tc I, being a store manager, have limited resources available to me but i plan to submit a ticket in hopes of resolving this issue, it would help if i had multiple issues to report however. If you folks are willing to help me out with this (power in numbers as they say) i think we may have a chance of getting a fix, what i need from each of you is your T-mobile telephone number that you've been using your Z3TC on and i can submit this ticket. Email your name and phone# to [email protected] and I'll do my best
Some more info on this can be found here
ipetitions.com/petition/let-us-call-because-our-tablets-are-made-to-call
Ive been using xda for a while now but didn't really have a good enough reason to creat an account but......since im new and can't post links hopefully you can addbthe http stuff
I really hope this can get cleared up soon a 500$ phone with practically the same features as a flip phone........ Smh
Any update?
tysontthompson said:
I work for T-Mobile and have also have the same issues with my Z3tc I, being a store manager, have limited resources available to me but i plan to submit a ticket in hopes of resolving this issue, it would help if i had multiple issues to report however. If you folks are willing to help me out with this (power in numbers as they say) i think we may have a chance of getting a fix, what i need from each of you is your T-mobile telephone number that you've been using your Z3TC on and i can submit this ticket. Email your name and phone# to [email protected] and I'll do my best
Click to expand...
Click to collapse
Any luck with the ticket you opened? You might consider posting the ticket number both here and in the t-mobile support forum so that anyone with the same issue can easily contact t-mobile and reference that ticket. As you said there is power in numbers!
montp said:
Any luck with the ticket you opened? You might consider posting the ticket number both here and in the t-mobile support forum so that anyone with the same issue can easily contact t-mobile and reference that ticket. As you said there is power in numbers!
Click to expand...
Click to collapse
Any update on this? My billing cycle started today and I think I got my internet pulled too. Called tech support and they said they don't know what the problem is. They said they elevated my ticket to a engineer and should hear back from them in 3 days. :crying:
just port the number to Metro its' the same network and just $10 more for unlimited you can always port the number back if t-mobile fix this issue.
Tweeted at Legere and Tmobile help and now I'm sitting on the phone with a tech rep. Let's see what happens. Seems like such an easy thing to switch and the irony is the paying customers and getting screwed and are jumping ship to pacify the freeloaders. I'm in love with huge phones and this is the First tablet with phone capabilities that plays nice with us carriers. I'm prepared to jump ship over this.
SO far she keeps insisting that it will work fine its it has the phone capabilities and i have the proper rate plan. She keeps putting me on hold....
There's someone who clocks into work 9-5 at t-mobile who can fix this issue with very little trouble, just have to locate that person.
---------- Post added at 11:41 PM ---------- Previous post was at 11:32 PM ----------
tysontthompson said:
I work for T-Mobile and have also have the same issues with my Z3tc I, being a store manager, have limited resources available to me but i plan to submit a ticket in hopes of resolving this issue, it would help if i had multiple issues to report however. If you folks are willing to help me out with this (power in numbers as they say) i think we may have a chance of getting a fix, what i need from each of you is your T-mobile telephone number that you've been using your Z3TC on and i can submit this ticket. Email your name and phone# to [email protected] and I'll do my best
Click to expand...
Click to collapse
So, The tech rep I just spoke to says that she can't open a ticket for me to send to the engineers until there's physically a problem. SO, I'm going to pick it up tomorrow and start the process. Anything happen with your ticket? Am I wasting my time?
I'm still waiting on a call back. Day 2 with no Internet. I told them to call me 24/7. I didn't bother calling today, but you can bet I will again tomorrow. Please, also get it elevated so that they realize this is not an isolated incident. I stopped by at&t today to ask about porting over my number. They said it would take 15 mins. About to jump ship and take my 5 lines on the account with me if I can't get the Internet to work again.
Please keep me updated, I'll keep you updated too.
Sent from my SGP621 using XDA Free mobile app
AirBruce said:
I'm still waiting on a call back. Day 2 with no Internet. I told them to call me 24/7. I didn't bother calling today, but you can bet I will again tomorrow. Please, also get it elevated so that they realize this is not an isolated incident. I stopped by at&t today to ask about porting over my number. They said it would take 15 mins. About to jump ship and take my 5 lines on the account with me if I can't get the Internet to work again.
Please keep me updated, I'll keep you updated too.
Sent from my SGP621 using XDA Free mobile app
Click to expand...
Click to collapse
The question is, you can't buy this device from a good reputable store with a 14 day no questions asked return policy. Expansys, or Amazon (not fulfilled by amazon) and the place where I'm going to go to in Manhattan are all "you buy it you keep it".
So, should I even go buy this tomorrow... The only way they will submit a ticket is if I actually have the device with the issue but if it turns out no one will fix the problem... I dont want to be stuck with it..
I guess I could always switch carriers but I'm in a family plan where we split the bill each month and the payments on my note 4 are going to come due... Big mess... But maybe that's what I'll do.
Why not just switch to metro though? Why at&t? Metro the exact same coverage. Or so I've heard.
Maybe I'll take the time to check out metros coverage while I wait for the issue to be fixed. Although.. I wonder, people were already working on this 2 months ago,why should I have any impact at all.
Whatever, yeah, let's keep each other updated!
Sent from my SM-N910T using XDA Free mobile app
AirBruce said:
I'm still waiting on a call back. Day 2 with no Internet. I told them to call me 24/7. I didn't bother calling today, but you can bet I will again tomorrow. Please, also get it elevated so that they realize this is not an isolated incident. I stopped by at&t today to ask about porting over my number. They said it would take 15 mins. About to jump ship and take my 5 lines on the account with me if I can't get the Internet to work again.
Please keep me updated, I'll keep you updated too.
Sent from my SGP621 using XDA Free mobile app
Click to expand...
Click to collapse
They responded on twitter, let's see if they can do anything... Day 2 with no internet you said, did you just get it or have you had it for a while and it just stopped giving you data?
I wonder if walking into a tmobile store would help too...
---------- Post added at 03:53 AM ---------- Previous post was at 03:22 AM ----------
mottyengel said:
They responded on twitter, let's see if they can do anything... Day 2 with no internet you said, did you just get it or have you had it for a while and it just stopped giving you data?
I wonder if walking into a tmobile store would help too...
Click to expand...
Click to collapse
I just read through a pretty depressing thread. I'm posting the OP's final depressing post after finally getting through to a tmo vp. You can read through the whole thread too if you like. Seems like the battle is lost at this point, it's over, i just have to decide in a few hours when the store opens if I want to leave tmo over this and go to metro... I've been really happy with tmo up until now...
https://support.t-mobile.com/thread/86423?start=0&tstart=0
After doing some research I got a hold of a couple of T-Mobile's executive e-mail addresses and typed in detail about what is happening here hoping someone would respond. Today I received a phone call from the office of the Vice president of T-Mobile. I had a detailed conversation about the problem. They said that our device, the Sony Xperia Z3 Compact Tablet LTE SGP621 should have never worked as phone with a data plan and T-Mobiles network should have recognized the device as a tablet and not allowed it to work as a phone with a data plan for the few months that it did right away. He also stated that T-Mobile up until I told him was unaware our device existed. He actually had to look up the device. He then went on to explain how the network didn't register the IMEI of the device right away that's why it worked on their network for those few months until the IMEI of the device was registered and classified on their network as a tablet. He didn't actually admit it was the free data for life program but if you understand how network protocols work I don't have to state the obvious. So the bottom line is that T-Mobile doesn't offer the service we are asking for on our devices. The way the network is structured it uses the IMEI number to determine the devices classification and then only allows approved services to be used on that particular device. So the rules on T-Mobiles network work says "Smart phones" are allowed to make phone calls, surf the web, send multimedia text messaging ect. and "Tablets" are only allowed to have a mobile data plan and are incapable of making phone calls. Our device is a phablet but there isn't a phablet classification on T-Mobiles network. Even though our devices will work, have worked, and can work the way we want, it is irrelevant due to the way the network protocols have been written. The industry is somewhat at fault here by not having a specific classification for a device like ours. It really should just be classified as a phone. The world I live in, if a device is capable of making phone calls its a phone end of story. Phones make phone calls, this is kid stuff. So there is no solution to our problem and there never will be one as of right now. So the device is useless in the US for what we bought it for. I would have never bought the LTE version if I knew this was the situation. The service I'm willing to pay for is not offered by any US carrier according to T-Mobile. I find the whole situation funny at this point. Look at it in this perspective, the hardware of our device is identical to the Sony Xperia Z3 that T-Mobile currently offers, the only difference is the size of the screen. and the IMEI number that says its a tablet. You can actually flash the Sony Xperia Z3 operating system onto our devices thats how Identical the hardware is. It's just the IMEI number that defines the devices classification. Overseas this isn't an issue. I'm hoping soon there will be a US carrier offering this service, the first company that does I'm switching to. I think I'm just going to cancel the line and use WiFi for now. I can't believe I spent close to $700 for this device and it's now basically the $400 WiFi version. I'm keeping my T-Mobile account because I'm grandfathered into a very good rate and I'm hoping they will eventually offer the service. but I know for a fact our devices will never work the way they did because of our devices classification. They would only be able to work if T-Mobile changed the networks protocols that classifies the device as either a phone or a tablet, as long as they have that protocol in place we are out of luck. I really don't see them ever getting rid of this classification/rule system on their network. So if they ever do offer a "Phablet" device with the service it will be on T-Mobile branded devices only because those devices will have an IMEI that classifies it as a "Smart phone" or by that time they will have added the new classification of "Phablet".. Good luck to everyone that was having the same issue, I really thought we had a chance at solving the problem because our devices "WORK" on T-Mobiles network perfectly. If anyone knows a carrier willing to provide the service to our devices please let us know.
mottyengel said:
They responded on twitter, let's see if they can do anything... Day 2 with no internet you said, did you just get it or have you had it for a while and it just stopped giving you data?
I wonder if walking into a tmobile store would help too...
---------- Post added at 03:53 AM ---------- Previous post was at 03:22 AM ----------
I just read through a pretty depressing thread. I'm posting the OP's final depressing post after finally getting through to a tmo vp. You can read through the whole thread too if you like. Seems like the battle is lost at this point, it's over, i just have to decide in a few hours when the store opens if I want to leave tmo over this and go to metro... I've been really happy with tmo up until now...
https://support.t-mobile.com/thread/86423?start=0&tstart=0
After doing some research I got a hold of a couple of T-Mobile's executive e-mail addresses and typed in detail about what is happening here hoping someone would respond. Today I received a phone call from the office of the Vice president of T-Mobile. I had a detailed conversation about the problem. They said that our device, the Sony Xperia Z3 Compact Tablet LTE SGP621 should have never worked as phone with a data plan and T-Mobiles network should have recognized the device as a tablet and not allowed it to work as a phone with a data plan for the few months that it did right away. He also stated that T-Mobile up until I told him was unaware our device existed. He actually had to look up the device. He then went on to explain how the network didn't register the IMEI of the device right away that's why it worked on their network for those few months until the IMEI of the device was registered and classified on their network as a tablet. He didn't actually admit it was the free data for life program but if you understand how network protocols work I don't have to state the obvious. So the bottom line is that T-Mobile doesn't offer the service we are asking for on our devices. The way the network is structured it uses the IMEI number to determine the devices classification and then only allows approved services to be used on that particular device. So the rules on T-Mobiles network work says "Smart phones" are allowed to make phone calls, surf the web, send multimedia text messaging ect. and "Tablets" are only allowed to have a mobile data plan and are incapable of making phone calls. Our device is a phablet but there isn't a phablet classification on T-Mobiles network. Even though our devices will work, have worked, and can work the way we want, it is irrelevant due to the way the network protocols have been written. The industry is somewhat at fault here by not having a specific classification for a device like ours. It really should just be classified as a phone. The world I live in, if a device is capable of making phone calls its a phone end of story. Phones make phone calls, this is kid stuff. So there is no solution to our problem and there never will be one as of right now. So the device is useless in the US for what we bought it for. I would have never bought the LTE version if I knew this was the situation. The service I'm willing to pay for is not offered by any US carrier according to T-Mobile. I find the whole situation funny at this point. Look at it in this perspective, the hardware of our device is identical to the Sony Xperia Z3 that T-Mobile currently offers, the only difference is the size of the screen. and the IMEI number that says its a tablet. You can actually flash the Sony Xperia Z3 operating system onto our devices thats how Identical the hardware is. It's just the IMEI number that defines the devices classification. Overseas this isn't an issue. I'm hoping soon there will be a US carrier offering this service, the first company that does I'm switching to. I think I'm just going to cancel the line and use WiFi for now. I can't believe I spent close to $700 for this device and it's now basically the $400 WiFi version. I'm keeping my T-Mobile account because I'm grandfathered into a very good rate and I'm hoping they will eventually offer the service. but I know for a fact our devices will never work the way they did because of our devices classification. They would only be able to work if T-Mobile changed the networks protocols that classifies the device as either a phone or a tablet, as long as they have that protocol in place we are out of luck. I really don't see them ever getting rid of this classification/rule system on their network. So if they ever do offer a "Phablet" device with the service it will be on T-Mobile branded devices only because those devices will have an IMEI that classifies it as a "Smart phone" or by that time they will have added the new classification of "Phablet".. Good luck to everyone that was having the same issue, I really thought we had a chance at solving the problem because our devices "WORK" on T-Mobiles network perfectly. If anyone knows a carrier willing to provide the service to our devices please let us know.
Click to expand...
Click to collapse
That is some F#* King BULL SH!T!!!!!
I'm going to port my number out.
I just called back tech support and they didn't even know what was happening. No one ever seems to know. I'm going to Metro PCS. EFF these s0n's of b!tch3s.
Yup... Yup... I just had a very long conversation with a tech support guy (i gave him all a bunch of different forum thread links to read through) he read everything I showed him and he understood fully. He transferred me w8th details to someone else who again took plenty of time to read through everything including internal T-mobile discussion. He's gonna call me back on Sunday. I left off with him that everyone is jumping ship because of this, including me, all to pacify some freeloaders.
Of course, I'm not delusional. after reading the above thread I realize he's probably gonna get back to me with a sorry, nothing we can do. That's why I'm going to a metro pcs store today to sign up. I'm not porting my number just yet, first I want to test metro and give tmo a little more time. Plus, I have a new note 4 (warranty issue replacing my current note 4) coming which I will then have to pay off when I port my number out so I'm gonna sell. And actually, I'm going to finally port my number to Google voice so I can always jump around and back to our tmo family plan if they ever fix this.
So, to recap, joining metro today with the tablet and if/when he comes back Sunday with nothing, I'm porting out to Google voice.
I'm so disappointed with tmo. I joined them in 2012 right before everything started getting exciting in 2013 and on and I have been increasingly more happy with them ever since...
What a shame
Sent from my SM-N910T using XDA Free mobile app
mottyengel said:
Yup... Yup... I just had a very long conversation with a tech support guy (i gave him all a bunch of different forum thread links to read through) he read everything I showed him and he understood fully. He transferred me w8th details to someone else who again took plenty of time to read through everything including internal T-mobile discussion. He's gonna call me back on Sunday. I left off with him that everyone is jumping ship because of this, including me, all to pacify some freeloaders.
Of course, I'm not delusional. after reading the above thread I realize he's probably gonna get back to me with a sorry, nothing we can do. That's why I'm going to a metro pcs store today to sign up. I'm not porting my number just yet, first I want to test metro and give tmo a little more time. Plus, I have a new note 4 (warranty issue replacing my current note 4) coming which I will then have to pay off when I port my number out so I'm gonna sell. And actually, I'm going to finally port my number to Google voice so I can always jump around and back to our tmo family plan if they ever fix this.
So, to recap, joining metro today with the tablet and if/when he comes back Sunday with nothing, I'm porting out to Google voice.
I'm so disappointed with tmo. I joined them in 2012 right before everything started getting exciting in 2013 and on and I have been increasingly more happy with them ever since...
What a shame
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I just came back from the cricket store. After writing my last post, I put my jacket on, and walked out, walked 6 blocks down, and had them port my number. So far so good. LTE speed is decent, and now I'm actually paying less! $35 a month. 2.5GB (which is enough for me, they had $45 for 5GB, maybe I'll upgrade next month) and unlimited talk and text. Not too shabby.
Dear T-Mobile. See how easy it was to "Un-carrier" you? I did it in less time, than it takes to do one load of laundry.
Nice hope it works for you. I need the unlimited data because I use North of 30gb a month... With I could go to cricket, but metros probably where I'll end up
Sent from my SM-N910T using XDA Free mobile app
AirBruce said:
I just came back from the cricket store. After writing my last post, I put my jacket on, and walked out, walked 6 blocks down, and had them port my number. So far so good. LTE speed is decent, and now I'm actually paying less! $35 a month. 2.5GB (which is enough for me, they had $45 for 5GB, maybe I'll upgrade next month) and unlimited talk and text. Not too shabby.
Dear T-Mobile. See how easy it was to "Un-carrier" you? I did it in less time, than it takes to do one load of laundry.
Click to expand...
Click to collapse
Well, I'm now a happy metro pcs customer. Just started porting my tmo number to google voice and it'll work through the new metro number. Turns out, my eip on my note 4 doesnt come due at all. As long as there are still more lines on the account, i can just keep paying it off month by month. Of course I'm gonna sell it soon but still.
BTW, to anyone who had this issue with tmo, you can get through to the engineering department for technical support, forward them to the following link so they can read up on the problem and then you can get them to credit your bill for the data portion since february. The credited my account 60 bucks.. Not bad. I wish I could have stayed with t-mobile but what can ya do.
Again, to all you people holding out for this to change. Not gonna happen. Not a chance in hell. really. It's a tablet now and it's final. you're gonna all have to move on
Metro is working fine for me is $10 more for the unlimited data but I am happy at least to have this working don't hesitate guys
Once I got the phone setup and on the Sprint network I tried a test SMS to someone. They replied and the message came in. Then it repeated itself over and over indefinitely. I had someone else send me a SMS message but that message never came through. I received the last message that was sent once again.
Countless hours on the phone with Sprint escalated through tech support. Took it back to the store. They tried to "flash" it but could not. Swapped out for another Essential Ph-1 and it did the same thing.
I told them to keep it. It has caused enough stress in my life for years at this point.
Curious, there have been a few random issues (not just on Sprint) that have turned out to be APN related. Do you know if they checked the APN settings and verified they were correct for their network? I changed a couple settings on TMobile to match what their recommendation is on their website and I know a couple AT&T people have had to change a thing or two as well.
ack154 said:
Curious, there have been a few random issues (not just on Sprint) that have turned out to be APN related. Do you know if they checked the APN settings and verified they were correct for their network? I changed a couple settings on TMobile to match what their recommendation is on their website and I know a couple AT&T people have had to change a thing or two as well.
Click to expand...
Click to collapse
To be honest I do not know if they checked that and I did not know to check it.
So you only had the phone for a few hours? Your call but I think you may have jumped the gun.
spotmark said:
So you only had the phone for a few hours? Your call but I think you may have jumped the gun.
Click to expand...
Click to collapse
I did not know what else to do. Guess I should have asked you guys first.
chasdw said:
I did not know what else to do. Guess I should have asked you guys first.
Click to expand...
Click to collapse
No use crying over spilled milk. Enjoy whatever you went with.
This is entirely speculation, but it could be on either Sprint's side or the Messenger app itself. What you describe mirrors my experience with my unlocked Galaxy S8 and using the Messenger app. I switched that line over to the Essential phone it started working fine with text messages. If you try again in the future, try disabling the advanced SMS features (called RDS I think?).
CollinFX45 said:
This is entirely speculation, but it could be on either Sprint's side or the Messenger app itself. What you describe mirrors my experience with my unlocked Galaxy S8 and using the Messenger app. I switched that line over to the Essential phone it started working fine with text messages. If you try again in the future, try disabling the advanced SMS features (called RDS I think?).
Click to expand...
Click to collapse
Thank you, appreciate the advice.
I work for sprint and this is an uncommon issue that has plagued the network for years. If your phone is not rooted, a simple profile update can fix this. One common issue we have seen with the essential phones bought through sprint is it not activating fully the first time. After the phone says it's activated still go through the settings, tap about, tap "OMADM updates" and click profile update. It was reprovision the phone correctly and reboot again. Sometimes it gets stuck on the last step. As long as the reception goes blank and then comes back with a LTE logo then you are done and can reboot the phone.
I know you already went with another phone but you could just as easily have the same issues on another phone. This comment is more for those who are looking for answers to your issue.
hellot1M said:
I work for sprint and this is an uncommon issue that has plagued the network for years. If your phone is not rooted, a simple profile update can fix this. One common issue we have seen with the essential phones bought through sprint is it not activating fully the first time. After the phone says it's activated still go through the settings, tap about, tap "OMADM updates" and click profile update. It was reprovision the phone correctly and reboot again. Sometimes it gets stuck on the last step. As long as the reception goes blank and then comes back with a LTE logo then you are done and can reboot the phone.
I know you already went with another phone but you could just as easily have the same issues on another phone. This comment is more for those who are looking for answers to your issue.
Click to expand...
Click to collapse
Very much appreciate the reply. I have not gone with a different phone because I am not really interested in any others at this time.
I did try what you suggested on both of the essential phones. It did not work on either.
I will probably go back by the Sprint store tomorrow to see if they figured anything out.
I cannot be without a phone and I do not currently have time to troubleshoot one that is not working.
I will keep chugging along with my old phone for the time being.
Sent from my Nexus 6 using Tapatalk
To be clear, Sprint Technical Support is so close to useless you might as well ask your dog how to fix your phone. You'd get the same quality of information and save yourself some time to boot. This is not necessarily Sprint's fault. It's very likely that Essential isn't giving them enough information. For example, I was trying to get files transfered from my PC to my Essential Phone earlier today. All I got was an big empty nothing telling me "This Folder is Empty." Figured it was something very simple but I couldn't figure out what. Sprint's second level support told me to call HP (computer OEM). Came onto this forum and somebody mentioned "just change the setting in notifications from charging to file transfer." Yep! It really was that easy! And Sprint should have easy fixes like that extremely well documented.
It makes me more that a little nervous to realize that Sprint is completely clueless about this phone and that Essential is next to impossible to get in touch with. Makes me wish I could have held out for the other Sprint exclusive coming soon: The LG V30+. Same 128GB internal, better screen, waterproof certification, drop proof certification, OLED screen instead of the PH-1's disappointing LCD panel, bigger screen, has an SD card slot, better camera, and above all else, well supported. Unfortunately, my old phone was broken and I needed to replace it immediately and as cheaply as possible. $15 per month made the PH-1 the best option available for me. Even the LG G6 with it's inferior specs, processor, etc. would have cost me more -- $20 per month.
We'll see how I'm feeling about my PH-1 in a week. Right now there's a lot of good and a lot of bad, so it's hard to say. At least by shear dumb luck I got the PH-1 at a budget phone price.
I had the same issue and took it to a Sprint store today. After a lot of trial and error, turning off Google voice did the trick for me. Even though they already switched me to a new phone.
I wanted to keep it but Pixel 2 coming out in October and camera subpar.
Sent from my Pixel XL using XDA-Developers Legacy app
I am on sprint and I have had zero issues, in fact I have a better signal with this phone because it utilizes the LTE + network. This is very interesting to me.
I purchased an unlocked Moto G5 Plus (XT1687). It was supposed to support sprint. I took it to a sprint store and they told me the phone was not supported. They wouldn't pop in a sim card to verify (just typed the IMEI into their system and reported the results).
Anyone have any advice?
artician said:
I purchased an unlocked Moto G5 Plus (XT1687). It was supposed to support sprint. I took it to a sprint store and they told me the phone was not supported. They wouldn't pop in a sim card to verify (just typed the IMEI into their system and reported the results).
Anyone have any advice?
Click to expand...
Click to collapse
I have same problem ,then I went to Best buy get new sim let them act all done
They should support it. They just need to get right SIM. Try the product numbers below.
The proper Sprint SIM as of this date for a Moto G5 Plus is SIMGLW446C. That part has a Sprint UPC of 019962040146.
I had no problems getting mine done, they just had to setup the computer to say it is a generic device, whatever that means. On Sprint.com it says I have a ZTE Optik, but all works great, so I don't really care.
Sprint Employees are mostly dumb to unlocked phones. They know what's on their shelves. It works, I've activated one online and one in store
Thank you all for the replies. I'm trying again today. I hope this goes okay if I have an existing number/account that I'm trying to activate this phone for; I'm pretty ignorant of how SIM's work.
artician said:
Thank you all for the replies. I'm trying again today. I hope this goes okay if I have an existing number/account that I'm trying to activate this phone for; I'm pretty ignorant of how SIM's work.
Click to expand...
Click to collapse
Just tell them that you want a nano SIM. They might not be familiar with the phone which is why they say it won't work. You can also tell them that it's the same SIM used in the Nexus 6P, which they probably have activated.
You can also refer them to this link.
https://www.sprint.com/en/landings/bring-your-own-phone.html
If you click on the first question in the FAQ (How do I know my device is eligble?), it lists the BYOD phones, which included the phone. Good luck.
I went to a third Sprint store today, where the employees hemmed and hawed for about 30 minute before finally telling me they just didn't have any of that kind of sim card in stock. They tried to sell me another phone twice. I got the impression (again), that something else was going on.
I went to Best Buy, where they had the sim in stock, but were prevented from accessing my account by the system. I imagine this is because I have a SERO account, so things are starting to fall into place now.
I may try to buy the sim and have them connect it through Sprint support, but this entire adventure has encompassed more than 200 hours of my time, multiple phones, and over $300 to date. Some of that is my fault because I didn't properly research the phones that they would support, and I would be able to root. I didn't pick up the sim today due to fear of investing even more money in this.
esoh said:
They should support it. They just need to get right SIM. Try the product numbers below.
The proper Sprint SIM as of this date for a Moto G5 Plus is SIMGLW446C. That part has a Sprint UPC of 019962040146.
Click to expand...
Click to collapse
This was immensely helpful in particular. Thank you!
I'm all hooked up. I ultimately purchased the SIM and had their online support connect the device. Easy-peasy. Thanks to everyone for sharing their experiences. I wouldn't have had the nerve to follow through unless people had shared their success with the same device/carrier.
Just tried getting my second Moto G5 Plus on sprint (the first was a 2gb/32gb version easy peasy with right card online by myself). This one for my wife, 4gb/64 not so easy. It doesn't go in their system and out of 7 sprint employees they were all clueless . There is a bunch of posts on the actual sprint support website about how some phones (even if the models are on their accepted byod list) need to be added to the system and it takes 2-3 days. As i mentioned this they looked at me like i was crazy telling me that it should be added to their system instantaneously when they try. Told him to try google search so he can be better at his job and walked out. He did give me the store manager's card, who was not in but......... ill just try with the sprint help support page people before i contact amazon / motorola. Havent had too many issues with amazon and we order alot. Cant believe though that out of 7 people, in a SPRINT store (not one of those that sells sprint services and others) .. and a big one too...... nobody has any ideea that to add a phone (specific phone) to the sprint system (system that lets them activate/ deactivate phone) takes 2-3 days and requires more than just the IMEI number and a "ticket" needs to be created........
https://community.sprint.com/t5/Acc...LUTION-Bring-Your-Own-Device-FAQs/ta-p/962647
more info about esn/ ticket etc..
Does anyone know how I can install the camera on my Moto G5 Plus XT1687? Since I install Pixel Experience 10 Plus Edition and it does not come with the camera application. Help
I was able to get VOLTE working by "manipulating" ATT. I dont know if this has been discussed or anything, all I can say is it's verified.
You need the IMEI of a device that has been "greenlighted" by ATT to have VOLTE. Leave your OP 5t setup alone. Sim card in and everything.
Chat with att or call them and tell them to assign the IMEI number to your phone number. It took about a day for it to go through. I went in and used the Magisk Module to enable VOLTE. Sure enough VOLTE works fine. Its just fooling their system into thinking the device is "greenlighted".
Edit: I guess when I sat down to write this, it may not be totally clear.
1) You have to have a device with a good IMEI, you arent changing the IMEI.
2) You want ATT to Apply that IMEI that came with the phone you are going to use for the IMEI.
It triggers their system to think the device is greenlighted for volte, even if you use your OP 5t (or other phone).
Theres nothing illegal, its just a loop hole Ive found in their system since they dont want to play nice with VOLTE and phones they dont sell. That S6 was mine and had a good IMEI. Its sitting next to me.
Just wanted to go on record and in a little more depth of what I was doing and how it was working, Sorry for any inconvenience I may have caused. I do go on record stating, I told the ATT tech what I was doing and all he said was "thats clever". He still did it for me. So I dont even think you would have to lie to be honest,
apophis9283 said:
I was able to get VOLTE working by "manipulating" ATT. I dont know if this has been discussed or anything, all I can say is it's verified.
You need the IMEI of a device that has been "greenlighted" by ATT to have VOLTE. Leave your OP 5t setup alone. Sim card in and everything.
Chat with att or call them and tell them to assign the IMEI number to your phone number. It took about a day for it to go through. I went in and used the Magisk Module to enable VOLTE. Sure enough VOLTE works fine. Its just fooling their system into thinking the device is "greenlighted".
Edit: I guess when I sat down to write this, it may not be totally clear.
1) You have to have a device with a good IMEI, you arent changing the IMEI.
2) You want ATT to Apply that IMEI that came with the phone you are going to use for the IMEI.
It triggers their system to think the device is greenlighted for volte, even if you use your OP 5t (or other phone).
Theres nothing illegal, its just a loop hole Ive found in their system since they dont want to play nice with VOLTE and phones they dont sell. That S6 was mine and had a good IMEI. Its sitting next to me.
Just wanted to go on record and in a little more depth of what I was doing and how it was working, Sorry for any inconvenience I may have caused. I do go on record stating, I told the ATT tech what I was doing and all he said was "thats clever". He still did it for me. So I dont even think you would have to lie to be honest,
Click to expand...
Click to collapse
Well there are 2 things about that.
1. Xda doesnt condone committing fraud which is what you are doing. It doesnt matter if you own the other phone or not.
2. ATT also does random scans where they pull the imei from active devices to update the accounts.
I have an LG G6 on my account as my OP5t and it still doesn't work for me. I tried that on the OP5, having them add an imei of a known ATT phone. They guy scanned a store version of a G6, but no change.
zelendel said:
Well there are 2 things about that.
1. Xda does condone committing fraud which is what you are doing. It doesnt matter if you own the other phone or not.
2. ATT also does random scans where they pull the imei from active devices to update the accounts.
Click to expand...
Click to collapse
Says who? I'm sure you meant to say that we DON'T condone the committing of fraud, which would then be an accurate statement.
As to the subject matter however, I have to respectfully disagree here Zel. There is no theft taking place, no exchanging of IMEI information. All this is saying is that you apply a valid IMEI to your account for VoLTE access in a device that typically wouldn't have it. This is simply circumventing the system. Just like allowing threads that talk about circumventing Googles startup security measures for pre-owned phones that were reset while a password encrypted device was in use. Or slipping your working sim card from a device you own and into a new device you purchased from the carrier in an effort to keep from getting charged the upgrade fee once the new provisioned sim becomes active and registers that it is an upgrade.
Yes, XDA does not condone illegal practice and in my strong opinion, this isn't such. I will now take this to the others for clarification and input as I'm sure it will go there without me after making this post
Neo said:
Says who? I'm sure you meant to say that we DON'T condone the committing of fraud, which would then be an accurate statement.
As to the subject matter however, I have to respectfully disagree here Zel. There is no theft taking place, no exchanging of IMEI information. All this is saying is that you apply a valid IMEI to your account for VoLTE access in a device that typically wouldn't have it. This is simply circumventing the system. Just like allowing threads that talk about circumventing Googles startup security measures for pre-owned phones that were reset while a password encrypted device was in use. Or slipping your working sim card from a device you own and into a new device you purchased from the carrier in an effort to keep from getting charged the upgrade fee once the new provisioned sim becomes active and registers that it is an upgrade.
Yes, XDA does not condone illegal practice and in my strong opinion, this isn't such. I will now take this to the others for clarification and input as I'm sure it will go there without me after making this post
Click to expand...
Click to collapse
But it is not a valid one that is connected to that account. As those features are meant to only work with ATT devices which ATT sales. Meaning that you are taking money from them in a sense that is stealing. You are purposly giving incorrect info (imie that will be used with the sim number) to get things you normally wouldnt unless you bought one of their devices. So i see no difference.
Our threads are a lot of grey with a bunch of double standards really.
You are right. I did mean doesnt.
zelendel said:
But it is not a valid one that is connected to that account. As those features are meant to only work with ATT devices which ATT sales. Meaning that you are taking money from them in a sense that is stealing. You are purposly giving incorrect info (imie that will be used with the sim number) to get things you normally wouldnt unless you bought one of their devices. So i see no difference.
Our threads are a lot of grey with a bunch of double standards really.
You are right. I did mean doesnt.
Click to expand...
Click to collapse
Ah yes, the gray. ATT would obviously check the IMEI before using it. If it has been flagged as stolen, clearly they won't use it. The same if it happens after this has been applied. If it hasn't been reported as being from a stolen device though, it is assumed that the device is owned by that person and I don't see a problem with it.
Sent from my Nexus 6 using Tapatalk
zelendel said:
Well there are 2 things about that.
1. Xda does condone committing fraud which is what you are doing. It doesnt matter if you own the other phone or not.
2. ATT also does random scans where they pull the imei from active devices to update the accounts.
Click to expand...
Click to collapse
I would have to agree with Neo's thoughts. XDA absolutely does not condone fraud.
Like Neo said, there is no exchanging of imei information whatsoever. All this does is unlock a service you already pay for. It reminds me of the old school tethering apps. Therefore, nothing that is being done is illegal. It might trip something in ATTs system but there is a lot of stuff done on XDA that carriers don't like.
Neo said:
Ah yes, the gray. ATT would obviously check the IMEI before using it. If it has been flagged as stolen, clearly they won't use it. The same if it happens after this has been applied. If it hasn't been reported as being from a stolen device though, it is assumed that the device is owned by that person and I don't see a problem with it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It doesnt matter if you own the device. Its the devicve that is being used. Which you are flat out lying about so in the text of it you are committing fraud. ATT could very well be in their rights to sue if they found out (not that they really would)
This came up recently in our core stores and 2 ideas are being batted around to fix it.
1. lock sims to imeis
2. Require imei changes on the account to be done in person with the person presenting the device to be verified.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mark manning said:
I would have to agree with Neo's thoughts. XDA absolutely does not condone fraud.
Like Neo said, there is no exchanging of imei information whatsoever. All this does is unlock a service you already pay for. It reminds me of the old school tethering apps. Therefore, nothing that is being done is illegal. It might trip something in ATTs system but there is a lot of stuff done on XDA that carriers don't like.
Click to expand...
Click to collapse
You are right I did know that fact. But as of late I am not sure about anything to do with XDA.
Thread Closed.
EDIT: As an update to this discussion, it has been found that this procedure is not illegal, and is simply either a limitation of the carrier's current system, or circumventing a carrier placed restriction (such as getting tether to work on your device without paying for a tether package). We've allowed these kinds of workarounds for years on XDA, and if ever the carrier or entitled body officially requests/demands removal of the content, we have and will oblige. XDA has always been a site for development, workarounds, exploits, mods, etc. There is an ethics element to this however, depending upon how the IMEI is obtained or by lying to the carriers.
That is all.
[Neo]