Related
I'm seeing many users notice different little bugs with the phone (me included) and instead of having multiple threads about it, maybe we can all post it in one place where later the devs can see it and work on them once the phone is rooted etc.. Good idea/bad idea? I come from an Evo 4g with Sense rom so I wonder how many of these might not really be "bugs" but just a different user experience.
I'll start..
Accu weather app not updating location automatically
apk files downloaded from the computer and then transferred to phone are not showing up (unknown sources, usb debugging checked)
No function when touching the clock widget. It does not launch me to alarm, world clock, time etc menu. Maybe this is just a touchwiz thing as I mentioned above, I come from a sense rom.
So far those are the ones on top of my head. As I use the phone more, I'm sure I'll spot more (hope not!).
Anyone else?
Phone dialer issues
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Mentioned above plus the following so far (except reboot for calling issue):
No landscape mode using TW (auto-rotate enabled)
Red LED only available notification color (REALLY?!)
Skype video calling is upside down when using in portrait mode.
Also, phone call is automatically in Speaker mode when calling after making a Skype video call.
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Journeyjeans said:
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Click to expand...
Click to collapse
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Erislover said:
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Click to expand...
Click to collapse
Actually, other's have experienced auto-closing apps and freezing. It's in a thread around here or at sprintusers.com, I forget which.
For the first three days I couldn't get data while roaming though the proper settings were checked. Sprint customer care reset my phone and after an hour of waiting it works.
All else its great (except for the above oddities with Touch Wiz) though I haven't checked GPS after encrypting the device.
Sent from my SPH-D710 using XDA App
humdrum2009 said:
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Click to expand...
Click to collapse
Can you elaborate on this issue?
Also, anyone else having similar issues, please chime in.
Are you seeing a circle with a slash through it (no service) when this happens?
Can you receive calls when this happens?
Do you lose 4G or WiFi? Or is it just Voice/3G?
Does it seem to happen sometime after making a call/text (~30min), or any other pattern you've noticed?
Are you rooted?
If yes, what kernel (zedomax or tanimn/shabbypenguin - trying to narrow down an issue with one of the current root kernels)?
Exchange Appt. Notification Bug
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Journeyjeans said:
*SWYPE does not work properly, no matter the settings. Have to type normally.
Click to expand...
Click to collapse
I know this may sound silly, and you may have already checked this, but check your language settings. I've read about some owners that were having problems with Swype discovered that their language was set to Spanish.
Also, on the LED notifications only being Red, I've been playing with an App called Light Flow. I've at least been able to change the notification colors to Blue using this App. Also, the App lets you use "White" as a color, which still shows a Red light, but blinks very fast if some of you prefer a faster blinking light.
I have had the roaming data issue as well. It does eventually work for me though, but on once occasion it took 10 minutes before data turned on after the roaming started. I will try calling Sprint as well.
Wifi signal is bad.. but speedtest says otherwise. I think the issue is with the amount of bars displayed and not the actual signal. I was standing 5 fee fromt he router and still didn't have full bars.
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
MadFlava said:
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
Click to expand...
Click to collapse
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Just got this phone friday. So far the only bugs I am experiencing are roaming in places my evo got coverage and the security draw pattern having a mind of its own making it very hard to unlock the screen. Also the wifi reception is noticeably weaker than my evo
nate420 said:
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Ive done that already and it didnt help. Thanks, tho.
Luckily, no freezes or crashes here (knock on wood).
what i HAVE noticed is the rotate bug, for instance
when rotating the phone for texting or browsing, you have to kind of
bring it up to your chest @ about a 90 degree angle in order for it to rotate.
calibrated it all correctly & i still have to do that.
this is my first phone from the Epic/Galaxy company so im not sure if that was a problem in the original Epic 4g (non-touch) but it sure is kind of annoying :/
hopefully the dev's can tweak the gyro or SOMETHING.
Poor Wifi/3g Signal
Noticed lower bars on both wifi and 3g...when in same spot on my Evo 4g I had more...might be just how many bars its displaying and not the actual signal...but not for sure...actually went into roaming a few times when with my Evo 4g I never did (even with roaming was set to automatic...now I have it set to sprint only)
Hello. Has anyone tried updating through Kies? I tried and it says that this version of software cannot be updated. I just got my phone today. I did have problems installing the drivers. After I let it install say one or two drivers, one would error out. Once I unplugged it a few times and then plugged it back it, all of the drivers installed.
I hope this doesn't mean that Samsung is not going to upgrade to ICS or else I am taking this back. I have a Samsung Galaxy Tab 7" and it won't allow updating with rooting. Thanks for any input and have a great day/night!
analyst28 said:
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Click to expand...
Click to collapse
I noticed this too.
you have to check the check boxes next to the calender item. This is deceptive because the boxes have checks in them. But they should be green and not grey.
hope that helps
This is really weird.
I know people have been having problems with Loss of Service, but so far, I've only had it happen once or twice. What's really bothering me, is that I've noticed an invisible service dropping problem that's actually way worse.
Twice now, my phone has full signal bars, and isn't roaming, but my wife will come home and say she sent me some texts. Sure enough, no texts. So I reboot, and suddenly I get a flood of text and voicemail alerts. So, not only was I not getting texts, but all calls were going straight to voicemail, as if the phone was powered off.
Has anyone noticed this?
I'm not rooted, no alternative kernel, nothing. I'm completely stock. If this keeps up, I have no alternative but to return the phone. I have a job where I have to be available for emergency alerts, and this is definitely a major problem.
I mean... why would the phone say it has a connection if it clearly doesn't?
Yeah can confirm the same. Its like the phone has los but doesnt realize it.
Sent from my SPH-D710 using XDA App
This is definitely a problem. It's usually referred to as "Stealth LOS". (or "POOS" but I have no idea what that stands for.)
If you decide to keep the phone, a workaround is to set Tasker to automatically reboot if it senses no signal. It should work even for the stealth cases. Obviously not everyone will feel that they should have to workaround the issue though.
Well I updated last week and now I notice I lose the keyboard while texting a lot now. This gets very frustrating. Also when I had bluetooth running I couldnt send a pic in a text message, seemed weird to me, anybody else getting these problems or is it just me.
Don't know about the bluetooth, but the disappearing keyboard issue is common and Microsoft is looking into it. People are saying it might have something to do with the background agents running and that it goes away if you disable them all.
937dytboi said:
Well I updated last week and now I notice I lose the keyboard while texting a lot now. This gets very frustrating. Also when I had bluetooth running I couldnt send a pic in a text message, seemed weird to me, anybody else getting these problems or is it just me.
Click to expand...
Click to collapse
The keyboard disapearing bug is not related to 7740, its a bug that popped up with Mango, still to be fixed.
My BT is always on, and I have no issues with sending pics in messages.
I noticed after the update that it happened a lot more than before the update. IDK it might have been something wrong with my phone at the time restarting it helped. I actually had to do a battery pull last night because my phone would power back on after it was just on. I havent had to do a battery pull since upgrading to Mango.
Happens to me frequently enough. Sometimes like 4 times in a row very quickly.
Yes, my keyboard is disappearing ever more than 7720, It's very annoying...
Thank god i didnt upgrade.. i think i will skip this upgrade at all..
I think I'm going to go back to the previous update. My keyboard has disappeared 3 times while typing this. Come on windows
Sent from my Venue Pro using XDA Windows Phone 7 App
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!
I'm getting tired of it, wifi disconnects and reconnects or flat out doesn't work, mobile data flat out doesn't work most times unless I reboot the phone for either of them to work. I'm rebooting about 4-5 times a day just to get either working. I'm at my wit's end and about to get rid of this thing as soon as I can.
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
chris.arney said:
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
Click to expand...
Click to collapse
I'm getting the same problems and it's annoying the hell out of me I'm paying this phone off but I'm about to just ditch it buy a pocofone and just pay im this off separately or try to trade it in for a one plus 6T