Related
Now that we have s-off and root, is a solution yet to get the phone and dialer to work on the View?
I'll look into it. Have you tried clubtech's patch?
Sent from my SPH-D700 using XDA App
No I haven't tried it. I will try it tomorrow before I flash my rom.
ElAguila said:
No I haven't tried it. I will try it tomorrow before I flash my rom.
Click to expand...
Click to collapse
Let us know if you get it running. I'm interested in this too. Thanks.
It may turn out that you will not be able to use your present SIM card as with some dongles, the carrier may only allow data (no voice calls) through it. Test the SIM in a standard phone for calls.
It'll be interesting to see if another carrier's SIM works in it also.
Farsquidge said:
It may turn out that you will not be able to use your present SIM card as with some dongles, the carrier may only allow data (no voice calls) through it. Test the SIM in a standard phone for calls.
It'll be interesting to see if another carrier's SIM works in it also.
Click to expand...
Click to collapse
There is no sim in the view. I'm not aware of any sprint device with a sim card.
Yes the sprint phones do not use a sim card. I added the lines to my build.prop file that are listed in the clubtech hack. Although the line
ro.phone.function=1
Was already there. I was able to place a call. The person could hear me and I could hear them although the volume was kind of low. I have not tested it with a bluetooth headset yet. Also keep in mind that I don't know but I believe any calls you make will count as data on your tablet data plan.
My concern was with upsetting sprint... you have your view on a regular view plan and not a phone plan right?
Sent from my SPH-D700 using XDA App
T120ted said:
There is no sim in the view. I'm not aware of any sprint device with a sim card.
Click to expand...
Click to collapse
Ah, OK, not actually seen one physically.
It must be a surface mount pre-programmed version locked to Sprint.. I can foresee difficulty in getting the phone to work then if it is set to data only on the network.
Edit: Just seen his success...
I'll be following this thread closely as I am on the fence for picking up a Sprint View. If phone calls are somehow enabled on this device then I will most likely pick one up.
As far as upsetting Sprint, that is the question mark. As far as I know they do not offer phone plans for the view, only data plans.
ElAguila said:
As far as upsetting Sprint, that is the question mark. As far as I know they do not offer phone plans for the view, only data plans.
Click to expand...
Click to collapse
You will probably find calls suddenly being blocked at the network then once they find out users are able to make them. They will not give anything for free!
If you want to use the view to regularly make calls, I would advice looking for the thread that tells you how to do this using a market app groove ip and gtalk and gvoice. That is your best bet. While using the view as a phone is possible, DO SO AT YOUR OWN RISK. This means if you use it and sprint blocks your account don't blame xda nor the members here.
I'm just interested in getting rid of groove ip. I would rather have a phone function than another app running in the background. I actually went from a phone plan to straight tablet plan with groove ip. I only need phone functionality incase the school needs to call me about my kids.
With all of the files on the the tablet but hidden and the fact that the only thing needed to enable the phone was a couple of lines in the build.prop makes me wonder if maybe sprint had looked at possible phone plans. Then either decided against or possible a future offering.
ElAguila said:
With all of the files on the the tablet but hidden and the fact that the only thing needed to enable the phone was a couple of lines in the build.prop makes me wonder if maybe sprint had looked at possible phone plans. Then either decided against or possible a future offering.
Click to expand...
Click to collapse
This is what I thought, too. I think they left it out until they could come up with a good game plan for it. It's inevitable that tablets will be phones as well. The asus memo is going to help usher it in. I'm just not an att fan and that's more than likely where that one is going to hit.
T120ted said:
This is what I thought, too. I think they left it out until they could come up with a good game plan for it. It's inevitable that tablets will be phones as well. The asus memo is going to help usher it in. I'm just not an att fan and that's more than likely where that one is going to hit.
Click to expand...
Click to collapse
I don't know, I think there is more to it than that, or HTC would have enabled phone calls on the WWE Flyer for all others to use.
I still think HTC had some problem gaining approval with this design from Google for GB and had to leave out the phone function.
Why else disable fitted hardware when it would be a bigger selling point if working? It makes no sense!
For the time being I'm using nettalk. I had to install it on my evo first then copy and send the apk to my view via dropbox. Once it was installed I was able to make "data" calls with my view with no bt headset...mic and speakers worked just fine. This was done before clubtech posted his patch.
So has anyone been able to get the phone function working with clubtech's work around?
I've done exactly what he advised, added those lines to my build.prop and even added unlimited mobile to mobile minutes to my tablet plan (yes it exists, I work at a Sprint store and added it myself) but I'm not able to dial out or receive incoming. The phone service doesn't run, ever, even when trying dial out a call.
I know the GVoice method works but I'd really like to be able to open this up without having to use extra apps.
yes theres a way. I did that on my HTC FLYER 3G. I created a full detailed document on how to do that on HTC FLYER but I used some sources on xda developer forum in order to do that. Here is the document I created, the sources with links are available at the very end of the pdf file. (one of the sources is for evo view)
http://bit.ly/r6x82t
Hey guys,
So I have a bit of a tricky question that I can't seem to find an answer for. My wife and I just move to Europe for work for 2 years. We had AT&T in the states, so my wife has an AT&T HTC One X+. We got our phones SIM unlocked before we left, and purchased French SIM cards that run on the Bouygues Telecom network. My phone (Lumia 925) can do wifi tethering no problem... My wife's on the other hand has issues. I keep getting the following error:
" There is a temporary network problem that prevents the enablement of the Mobile Hotspot function. Please retry later."
I have tried the following steps:
1. Rooting the phone.
2. Installing other hotspot apps (Both root and non-root)
3. Installed custom ROMs with hotfixes to remove AT&T data requirements.
I don't know if it's relevant, but when I do a reset on the phone, it doesn't automatically connect to Bouygues network for data. I have to manually add the APN every time. Once I do that, her mobile data works just fine, so I don't THINK that the APN is causing the problem...
Anyways, if anyone has an suggestions on how to fix this issue, I would be indebted to you... I've just never encountered this problem on any of my other Android devices and I have to believe that there is a simple solution to fix the problem that I've just not encountered. Thanks!!
I loved my international HOX, so when got dropped in water i said lets go for the ATT HOX+ that has LTE.
Big mistake! I have OP's same issue, im in spain and my provider is Movistar.
I bought it on e-Bay, configured all the APNs, I used settings from their webpage and also tried telephony.db values from an international rom, stock rom didn't tether.
Rooted stock (4.1.2 i think it was) still nothing.
Elegancia (4.2.2) ROM, still nothing.
Changed some stuff on the telephony.db, still nothing
Swapped the wifirouter.apk with the international wifirouter.apk, still nothing.
Nuked TetherGuard.apk, still nothing.
Installed Moto-X tether Xposed module, still nothing (probably cause it's for android 4.4).
I read that AOSP or Cyanogen ROMs don’t have this issue.
I also read that if you swap telephone.db from international version to USA version the phone goes into a reboot loop, [More Info].
I guess the solution lays in something similar to the Moto-X tether patch, but i don't really have the time to fork the project, and try to get my tethering working.
Hope someone can give us a hand, im sure there are at least 5 more people in this same situation.
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
Hi all, sim unlocked s-off sprint m9 used to work well on android 6 with official rom. But until the phone was upgraded to Android 7. Data connection stopped working for one operator (NOS in Portugal). However Vodafone works well.
Tried different roms and apn settings, same at all. Data connection does not work on NOS operator.
Does anyone have similar issue and of course any advices?
Thank you all.
redoano said:
Hi all, sim unlocked s-off sprint m9 used to work well on android 6 with official rom. But until the phone was upgraded to Android 7. Data connection stopped working for one operator (NOS in Portugal). However Vodafone works well.
Tried different roms and apn settings, same at all. Data connection does not work on NOS operator.
Does anyone have similar issue and of course any advices?
Thank you all.
Click to expand...
Click to collapse
Why sim unlock a Sprint variant and not an AT&T or T-Mobile which already support GSM?
did you find a solution?
i have exact same issue.
bought one m9 from ebay with sprint (651) firmware on.
lte was working fine in israel (1800 2100).
after nougat im only getting 3g.
it makes sense that i cant use those bands (1 and 3 i think) on a sprint device.. but it did work with marshmallow
Same problem in the USA
I have (nearly) the same problem in the United States with a Sprint CDMA version of the One M9. The main difference is that my data speed is even worse than 3G, around 10-20 Kbps. Occasionally, I get faster speeds, but I haven't been able to figure out if it is location-specific (but always away from home and work) or due to some other characteristic.
The phone came brand new in a retail box from an eBay seller. It worked as expected for 1.7 years. The OTA update which installed Android 7 (aka Nougat) in early 2017 resulted in the very slow data speeds. WiFi is unaffected, but data is so slow that I cannot reliably send or receive MMS; Google Maps says that I do not even have a data connection for traffic info.
EcoMobile (my MVNO provider; I still have a sprint email address, so I know who is actually providing service) could only suggest resetting my phone; did this twice with no change in operation (but several of the programs which automatically re-installed themselves operated differently, including GMail no longer providing auto-complete for addresses).
After literally 2 hours in chat with htc, they told me that my MEID indicates my phone was "made in Taiwan". I took this to mean that: 1) the person I was chatting with had poor English skills (because aren't they all made in Taiwan?), and 2) my phone is gray market (meaning it was not imported into the country via official channels, even though the manual was in the American version of English).
I came to XDA looking for an answer, too. I was mildly surprised to see that this topic was at the top of the list for the One M9.
The best solution for my situation would be the proper ROM for my phone, but I don't know how to figure that out from the MEID. htc USA says they cannot help me with this.
I could even go back to Android 6, but I do rather like the new features in Nougat.
Alternatively, I could root the phone and install a 3rd party ROM, but I still need to know how to choose the proper one for my phone.
I hope this info finds its way to a helpful expert.
Regards,
Jeff
Hi all...
I recently, and mistakenly, bought the AT&T version of the G Pad 8.0 X.....it was a mistake because I didn't realize I wouldn't be able to use simple dialer and sms apps.
Can anyone PLEASE educate me on one or both of the questions below?
1) What has AT&T done to prevent dialers and sms apps from interacting directly with the LTE interface
2) Is it a certainty that the v521 ROM will not work on the v520? Based on LTE bands supported by each I assume it's different radio hardware but wanted to see if I could get more details from anyone here.
At this point I've thrown away $75 on this tablet because not being able to send and receive sms is a deal breaker for me and I don't know if I feel like going through the hassle of trying to resell it. I'm willing to be a guinea pig in trying to install the v521 ROM on the v520.... IF there's a chance it could work.
Is there any way to receive sms messages from my carrier via data only? I'm told that Hangouts used to have this functionality but no longer does?
Appreciate anyone who will take a moment to share their knowledge....thank you very much folks
Kevin
These devices don't have voice capability. The modem is not configured to do so.
Now for SMS, they do have that ability. If you don't have an SMS app, get one. Googles SMS app, messaging. Blue icon. The tmo ROM has SMS baked in.
I have both the T-Mobile V-521 and AT&T V-520. Actually, I have a working V-521, a broken V-521, and two working V-520s.
I use T-Mobile, and I have been frustrated with the AT&T version's lack of SMS and hotspot. Though I can live without the hotspot, I use SMS a lot, and I'd really like to have it on the AT&T version.
I've tried installing a number of SMS apps on the V-520, and no luck at all. They all act as if there's no hardware available to use for SMS, and give a variety of errors (or no error at all) and do not work for me.
I took apart the broken V-521, and I saw a series of jumpers labeled "V521", "V520" and a few others, though I don't recall which. (I'll take it apart again and see.)
I've wondered if these jumpers turn on/off hardware features, or access different ROMs or other model-specific features.
Would changing the jumper from V520 to V521 give it the "personality" of the T-Mobile version, and activate SMS and hotspot?
I'd be willing to "sacrifice" one of the AT&T tablets, because I don't use it at all, due to the lack of SMS.
I'm also available to analyze either model, at someone's direction, to see what is going on with them.
I'm happy to cooperate in almost any way, to help those of us with the AT&T version get more functionality from it!