I only have 500 anytime minutes, this is usually enough for me, but I've been taking many interviews this month. I only have 15 anytime minutes left and I have 9 days left on my cycle.
This prompted me to try and get Sprint WiFi calling working. When I approve my access point, and the address for it, it keeps saying "network connection error. Please try again" and it never works.
So I gave up on that, and tried integrating my Google Voice services with my phone for free VoIP calling. For some reason the app is only letting me text with it. This guide tells you how to make calls with Google Voice from Android: https://support.google.com/voice/answer/168520?hl=en but I am not getting the dialog screen asking me if I want to make calls with my Google voice. Whenever I call a contact it just auto rings with the normal dialer without asking.
As you can see from this picture I screen capped, my sprint recognized I have both Google Voice and WiFi calling enabled as services. http://imgur.com/qIirVrG
Not sure if this matters. But I soft bricked my phone and had to use the factory reset guide. That worked great, I even did the RTN Sprint reset to get my Sprint Spark apps back. I do currently have my phone rooted with Xposed and Tweaksbox installed.
Any ideas?
this is just a copy/paste from another thread I posted in, this fixed my WiFi Calling issues
I had an issue getting WiFi calling to work out of the box, here's how I fixed it.
- Forgot WiFi network I was trying to connect to
- Log onto my Sprint account and remove WiFi calling from my plan (click "Change my Services" from the drop down menu associated with the G3 then select the "remove" text next to VWDOM0 - Domestic Voice Over Wi-Fi Unlimited)
- Wait a few minutes and keep an eye on your phone; you'll receive a pop up saying "Changes Saved" or "Profile Updated". Something like that
- After I got the pop-up I entered ##SCRTN# in the dialer (phone will reboot and update profile)<----- (I have seen where ##UPDATE# works as well so maybe try both)
-Once my phone booted up and settled in I entered the WiFi Calling menu through the dialer app; I signed into my home network and went through the activation process to add WiFi calling to my phone
It worked for me after that. However it recently stopped working for me (last night) and all I had to do was enter ##UPDATE# to fix it
fergie716 said:
I had an issue getting WiFi calling to work out of the box, here's how I fixed it.
Click to expand...
Click to collapse
Super cool thanks for showing me this.
On a side note, Google Voice is making me rage. Google Voice provisions your carrier to accept Voice Over IP (VoIP), and whenever it tried provisioning it always said "network error". I uninstalled it, logged into my Voice account and disabled it from my Sprint phone, but it's got like a zombie network process still trying to provision it. Once every hour or so a message pops up that says "network error" and it wakes the phone and it won't go back to sleep unless you press "cancel" on the error message. Pretty enraging. Rebooting the phone doesn't make it go away either.
Oh well, I might be RTN resetting my phone in the near future.
EDIT:
Here's a screenshot of the network error. Is there any way I can figure out what process is displaying this error?http://i.imgur.com/99idKL1.png
I was able to fix my "Network Error" dialog box waking up my phone with an RTN reset.
Although I tried all of "fergie716" steps to get WiFi Calling working multiple times, and it still doesn't work. Sigh....
may i ask where do you get the app for Sprint Wifi called i do not see it on my list of app
ruff97 said:
may i ask where do you get the app for Sprint Wifi called i do not see it on my list of app
Click to expand...
Click to collapse
Do you have the Sprint boot up screen? If not, read #25 of this post. http://forum.xda-developers.com/showthread.php?p=54912191
engine95 said:
Do you have the Sprint boot up screen? If not, read #25 of this post. http://forum.xda-developers.com/showthread.php?p=54912191
Click to expand...
Click to collapse
just check and i do not i have LG boot up screen. thank you
ruff97 said:
just check and i do not i have LG boot up screen. thank you
Click to expand...
Click to collapse
Also in that same thread I linked, you'll find out how to get your MSL. I think its in post #3.
comzee said:
I only have 500 anytime minutes, this is usually enough for me, but I've been taking many interviews this month. I only have 15 anytime minutes left and I have 9 days left on my cycle.
This prompted me to try and get Sprint WiFi calling working. When I approve my access point, and the address for it, it keeps saying "network connection error. Please try again" and it never works.
So I gave up on that, and tried integrating my Google Voice services with my phone for free VoIP calling. For some reason the app is only letting me text with it. This guide tells you how to make calls with Google Voice from Android: https://support.google.com/voice/answer/168520?hl=en but I am not getting the dialog screen asking me if I want to make calls with my Google voice. Whenever I call a contact it just auto rings with the normal dialer without asking.
As you can see from this picture I screen capped, my sprint recognized I have both Google Voice and WiFi calling enabled as services. http://imgur.com/qIirVrG
Not sure if this matters. But I soft bricked my phone and had to use the factory reset guide. That worked great, I even did the RTN Sprint reset to get my Sprint Spark apps back. I do currently have my phone rooted with Xposed and Tweaksbox installed.
Any ideas?
Click to expand...
Click to collapse
Just so you know, Google Voice is not a gateway for free voip calling in itself. It is simply a feature server that sits between you and Sprints core network that adds enhanced functionality.
I do believe that calls over Sprint's VoWifi app are unmeasured, so this is your best bet if you are trying to save minutes.
robber said:
Just so you know, Google Voice is not a gateway for free voip calling in itself. It is simply a feature server that sits between you and Sprints core network that adds enhanced functionality.
I do believe that calls over Sprint's VoWifi app are unmeasured, so this is your best bet if you are trying to save minutes.
Click to expand...
Click to collapse
Good to know. I feel like I've done literally everything trying to get WiFi calling working though. RTN resets with my MSL, multiple ##SCRTN# and ##UPDATE#. I'll chalk it up to my phone being rooted, I can't think of any other reason. I'll just wait for the bootloader to be unlocked for custom roms. My anytime minutes being out is only a minor inconvenience too, I almost never go over 150 anytime in a month, just so happens I've been out of work and been doing many phone interviews, which maxed my minutes. Luckily I landed a job, and my cycle resets in 6 days now.
comzee said:
Good to know. I feel like I've done literally everything trying to get WiFi calling working though. RTN resets with my MSL, multiple ##SCRTN# and ##UPDATE#. I'll chalk it up to my phone being rooted, I can't think of any other reason. I'll just wait for the bootloader to be unlocked for custom roms. My anytime minutes being out is only a minor inconvenience too, I almost never go over 150 anytime in a month, just so happens I've been out of work and been doing many phone interviews, which maxed my minutes. Luckily I landed a job, and my cycle resets in 6 days now.
Click to expand...
Click to collapse
I've had issues with Google Voice (And Wifi calling) and the only thing I was able to do to get it to work was call sprint and have them remove the services from my account from their end. I waited about 15 minutes and when I re-added them, I didn't have any more issues. For Wifi Calling, I did an RTN reset after the 15 minutes, and for Google Voice, I logged out, cleared app data and uninstalled, then reinstalled after waiting Maybe give that a try. I was rooted as well FWIW.
dakoellis said:
I've had issues with Google Voice (And Wifi calling) and the only thing I was able to do to get it to work was call sprint and have them remove the services from my account from their end. I waited about 15 minutes and when I re-added them, I didn't have any more issues. For Wifi Calling, I did an RTN reset after the 15 minutes, and for Google Voice, I logged out, cleared app data and uninstalled, then reinstalled after waiting Maybe give that a try. I was rooted as well FWIW.
Click to expand...
Click to collapse
What was your issue out of curiosity? I am having issues with inbound calls over WiFi, phone doest ring. Was this your problem by any chance.
robber said:
What was your issue out of curiosity? I am having issues with inbound calls over WiFi, phone doest ring. Was this your problem by any chance.
Click to expand...
Click to collapse
No, it just says "network connection error please try again" in the notifications bar. But it never connects to work.
Related
I know it's been a pretty common issue for rooted EVO 3D users to get an error 16 while roaming, which requires them to call Sprint and go through some rigmarole to get the phone working again.
I seem to be having a different (although similar) issue. I have no issues making calls, or with data while I'm on the Sprint network. But now that I'm roaming off of a nearby Verizon tower out here in the middle of no-where, I'm having issues. I try to place a call, and immediately the phone sounds a disconnection beep and that's it. I also do not have data.
About 45 days ago up here I received a message about not being authenticated (the error 16), but I was told that they couldn't fix this without me bringing my phone into the store. I just reset the phone and did hands free activation again, and avoided the store. I haven't noticed any issues after that, and I do go in and out of roaming areas sometimes while in the city.
I just tried to do a chat with Sprint. I specifically said I had an error 16 and needed an HRL refresh (I lied). The rep had me power off my phone while she attempted to send it a signal. After this she had me dial *2 and my phone process crashed while I tried this. I also still couldn't call out. She tried having me power off again. Same problem. Next she told me to power off my phone and keep it off for 30 mins. If it wasn't fixed by then, she gave me a support number to call.
Anyway, not sure if the support number will help. Figured I'd just see if anyone has had a similar issue or experience. I found another thread mention resetting through ##786# and using your MSL to get into it. My EPST process seems to crash when I try this. ##DATA# doesn't crash though...hm.
I'm running the Synergy 3Dvo Rom (Nightly 344 I think?). Stock kernel.
This maybe due to my "upgrading" SIM cards at T-mo earlier today, but my new Amaze is not allowing me to set up Google Voice or utilize the Visual Voicemail preinstalled features and keeps directing me to call 611. Google Voice sends back an error stating "Failed to retrieve and save current forwarding number settings." When I click on Voicemail Settings it looks bad. The page doesnt load up (ie appears greyed out, with a jumble of numbers at the top where my phone # should be. Anyone else having similar issues? My first guess is either an issue with Sense or T-Mo.
do you have wifi calling ?
vinterchaos said:
do you have wifi calling ?
Click to expand...
Click to collapse
No I dont see the app. At least like there was in myTouch4G, also no references to it in my settings menu.
my google voice works. it wasnt able to set up the forwarding numbers, but i always check my vm via the app anyway so. It downloaded all my vm and a test call was sent to my google mailbox
domin8 said:
my google voice works. it wasnt able to set up the forwarding numbers, but i always check my vm via the app anyway so. It downloaded all my vm and a test call was sent to my google mailbox
Click to expand...
Click to collapse
If you try to open VM Settings does it look normal, or is it all greyed out and the number all jumbled?
mines not greyed out. double check and run the setup a few times, maybe itll work through. mine said some error, but i dont have anything greyed out actually. i check mine with the google voice app itself, so i dont see it as an immediate issue (for me at least)
I went from the LG G2x to this device and I had GVoice on that. The voice app failed to set call forwarding options for me, too, when I first installed it on the Amaze4G but becuase they are subscriber specific with the carrier, and not the device it doesn't matter.
If you go through google voice web site and go through the settings you can get the call forwarding codes and dial it from the device and it will accomplish the same thing and work fine.
I was on the phone with TMO this morning about a network issue happening with my phone that's unrelated to voicemail. In investigating potential service issues they mentioned that Seattle and the surrounding area has a new visual voicemail system issue. It could be that. I'm not sure if that's specific to my location or if they rolled out something service wide.
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
mghtymse007 said:
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
Click to expand...
Click to collapse
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
pdqgp said:
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
Click to expand...
Click to collapse
Sorry to hear you have a&t. Connected remotely and call forwarding are two completely different things as you may know but regardless of the matter its not Samsungs fault. Your device showed that it was connected remotely therefore it was....the real issue is your wireless carriers crappy network not pushing your notifications plain and simple not your watch or your phone. Both are working just fine from what you've stated which leads to the fact that its your network connection. Only GSM networks are capable of auto call forwarding which as I stated is completely carrier network based. No offense but at&t sucks anymore and havent seen these issues with anyone but at&t customers. Its on at&ts end. Call and complain about your issue but unfortunately I doubt they will do crap which is why I left at&t 3 months ago. Hope you can get them to figure it out.
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
pdqgp said:
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
Click to expand...
Click to collapse
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
rickleasa said:
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
Click to expand...
Click to collapse
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
pdqgp said:
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
Click to expand...
Click to collapse
ok glad to hear but that didn't work for me as when i went to call setting on my phone i still received the sim network error until i did the restore but glad it worked for you
djc-wi said:
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
Click to expand...
Click to collapse
I finally figured out this only happens to me after I have Bluetooth paired to my car or a headset. Only happens every once in awhile. If I reenter my car and turn it on, as soon as Bluetooth reconnects it's back to working. The problem will come back if I don't reset my phone. Then all is fine for a few days. In my case obviously the bug is in gear S bluetooth not my phone or my car as the same thing at times will happen with a Bluetooth headset.
SaintCrispin said:
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Click to expand...
Click to collapse
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
foulmouthedruffian said:
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
Click to expand...
Click to collapse
Hah I'm glad it's working for you now.
Anybody have the T-Mobile (USA) Visual Voicemail working on the Mate 10? Mine just tries to set itself up for a few minutes, then says "We are experiencing some issues with activation. We will retry in a few minutes."
Sorry, I can't help you but I have a problem with MetroPCS visual voicemail and Mate 10 as well. Mine does activate but I loose my data connectivity. I unistall the app and connectivity is restored.
same problem mate 10 pro
snowkilts said:
Anybody have the T-Mobile (USA) Visual Voicemail working on the Mate 10? Mine just tries to set itself up for a few minutes, then says "We are experiencing some issues with activation. We will retry in a few minutes."
Click to expand...
Click to collapse
i also have this problem, try resetting app; deleting cashe; uninstalling; re-installing; even resetting/formatting phone when i 1st received the phone. But ive gave up on it.:crying::crying:
numernumer said:
i also have this problem, try resetting app; deleting cashe; uninstalling; re-installing; even resetting/formatting phone when i 1st received the phone. But ive gave up on it.:crying::crying:
Click to expand...
Click to collapse
I also called T-Mobile tech support and posted on the T-Mobile forums. I got feedback but never solved the problem. Very happy with Google Voice as a substitute though. Caller ID lookup and vmail-to-text transcription is included free.
snowkilts said:
I also called T-Mobile tech support and posted on the T-Mobile forums. I got feedback but never solved the problem. Very happy with Google Voice as a substitute though. Caller ID lookup and vmail-to-text transcription is included free.
Click to expand...
Click to collapse
WHAT!!!!! NICE....thanks alot:good::good::good:
I discovered how to activate T-Mobile visual voicemail on a Mate 10 (non-pro). I read it on a T-mobile forum so I cannot take credit. I will say this first - even though I can get it to install, and activate, it appears to be causing my phone to not have data/internet access, unless I toggle mobile-data. Then it will continue to work until I reboot the phone at which time my data access/internet access stops. I have all 4G/LTE/ APN's setup correctly so I am not sure why this happens. I have since uninstalled the T-Mobile version of visual voicemail and the problem is resolved. GO figure!
Now here is what you need to do to get it activated in the first place. If you have the app already installed I recommend that you uninstall it before we start. After you have it uninstalled go to settings > wireless & networks > call settings > (under SIM 1 which is the only one I use) tap on additional settings > voicemail > toggle OFF visual voicemail. Now you can install T-Mobile visual voicemail and follow the prompts to allow access to contacts, etc., etc, and it should activate without issue.
Now if anyone can get it to continue working after a reboot without having to toggle mobile data then please let me know.
Also...does anyone know what the default, built in visual voicemail even does on EMUI 8.0, or how to access some app for it to work? Seems useless to me other than to block the T-Mobile app from activating.
jaseman said:
I discovered how to activate T-Mobile visual voicemail on a Mate 10 (non-pro). I read it on a T-mobile forum so I cannot take credit. I will say this first - even though I can get it to install, and activate, it appears to be causing my phone to not have data/internet access, unless I toggle mobile-data. Then it will continue to work until I reboot the phone at which time my data access/internet access stops. I have all 4G/LTE/ APN's setup correctly so I am not sure why this happens. I have since uninstalled the T-Mobile version of visual voicemail and the problem is resolved. GO figure!
Click to expand...
Click to collapse
Sounds like you are having the same issue as the guy in post #2.
I am very happy with using Google Voice instead of visual voicemail. Wouldn't go back even if I could get it working. In addition to everything VVM does, you also get free voice-to-text on voicemail messages, as well as automatic caller ID lookup.
Hello,
I have a LG Stylo 4 (LML713DL), Android 8.1 stock, Straight Talk
been working fine since Nov. 2018 when I purchased, no issue. Time to refill service in Feb., it took four hours to get service back.
Now its's stuck on 3G. It will sometimes go crazy 1x, 3G, 4G, none, roaming (not in that order it's random).
No calls are made the first try, have to redial after immediate drop of connection error.
I don't receive calls, I get voice mail notifications.
Texting is always with a indicator that no sms service.
Called Straight Talk and Version. Took sim out, reboot, factory reset, network reset: x1000 times. Tried a new apn.
No dial codes work besides *#546368#*713#, tried all the towers, etc. Only one with auto prl works. Tried all the modem options under field test. Nothing besides the issues still at hand or no service.
Both carriers have said after two weeks of calling them, nothing on their end and not being throttled.
I can't cast, mirror, screenshare, (the Internet says my model number can) but no native options to turn it on. Used shortcuts to get to these said native options. My device says connected to the tv, but my tv says "F*ck Off, with that sh.!t". I can't figure it out??
I can't get Qslide to work, naturally it's in my setting under > home button options. But nothing on the notifications bar like it says it should. I launch a "q-app" it opens and closes. Besides calc.
Thanks to anyone that read this and is interested in helping me solve this..
At the moment I am lost. I am pretty mid level tech handy.
deleted
**More info
Screenshots of signal info
1 - 2 - 3
Screenshot of Qslide
1
Casting
I read your build.prop needs this:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.debug.wfd.enable=1
So I think I am screwed there. I don't have those lines in mine
same phone mine works fine .....
Casting
I read your build.prop needs this:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.debug.wfd.enable=1
So I think I am screwed there. I don't have those lines in mine[/QUOTE]
zombie8u2 said:
hello,
i have a lg stylo 4 (lml713dl), android 8.1 stock, straight talk
been working fine since nov. 2018 when i purchased, no issue. Time to refill service in feb., it took four hours to get service back.
Now its's stuck on 3g. It will sometimes go crazy 1x, 3g, 4g, none, roaming (not in that order it's random).
No calls are made the first try, have to redial after immediate drop of connection error.
I don't receive calls, i get voice mail notifications.
Texting is always with a indicator that no sms service.
Called straight talk and version. Took sim out, reboot, factory reset, network reset: X1000 times. Tried a new apn.
No dial codes work besides *#546368#*713#, tried all the towers, etc. Only one with auto prl works. Tried all the modem options under field test. Nothing besides the issues still at hand or no service.
Both carriers have said after two weeks of calling them, nothing on their end and not being throttled.
I can't cast, mirror, screenshare, (the internet says my model number can) but no native options to turn it on. Used shortcuts to get to these said native options. My device says connected to the tv, but my tv says "f*ck off, with that sh.!t". I can't figure it out??
I can't get qslide to work, naturally it's in my setting under > home button options. But nothing on the notifications bar like it says it should. I launch a "q-app" it opens and closes. Besides calc.
Thanks to anyone that read this and is interested in helping me solve this..
At the moment i am lost. I am pretty mid level tech handy.
Click to expand...
Click to collapse
277634#*# hidden menu
---------- Post added at 12:59 AM ---------- Previous post was at 12:55 AM ----------
Have any of you folks been able to get laf, fastboot, or edl to work on this phone?