Related
I successfuly updated my Stock, non-rooted Spring Epic Touch 4G last week to the newest build.
Battery life got better... signal got better. I lost the ability to use automated touch tone phone menu systems.
Does anyone else have this issue, if so please let me know if there's a fix or a way to revert back to a previous firmware update, etc.
Thanks in advance, I eagerly await your help. For now, I can't even get ahold of Sprint Customer service's phone system. I'm locked out!
-Tim
I to am having this issue. i am a phone tech at a local repair shop in south florida and 2 of my customers are having this issue (as well as my phone).
both of my customers phone are stock / non rooted
my phone is rooted using CALKUKINS E4GT Rom.
ive tried using a diffrent dialer but no help. anyone got a salution for this?
ON TOP OF THAT I HAVE 2 DEMO EPIC TOUCH'S AND THEY HAVE THE SAME ISSUE
Long time problem with dial tones in call
I have been searching for a month now to find a solution to this problem. I feel like I'm not explaining it right, but I'll try again.
For the last 2 years I have been dialing into a conference call line each morning. I dial the number then enter my access code (299542#). Upon recieving my new Samsung E4GT, the phone dialer does not register some or most of the digits entered, but it's not consistent. 95% of the time the 2 does not work, 25% of the time the 9 doesn't work...and so on. I have gone back to Gingerbread EL29, tried ICS FF18....FH13, I've used custom ROMs and those made no difference. There seems to be a few people who have had this problem as well, but there have not been any responses to help that I have seen.
paulsperli said:
I have been searching for a month now to find a solution to this problem. I feel like I'm not explaining it right, but I'll try again.
For the last 2 years I have been dialing into a conference call line each morning. I dial the number then enter my access code (299542#). Upon receiving my new Samsung E4GT, the phone dialer does not register some or most of the digits entered, but it's not consistent. 95% of the time the 2 does not work, 25% of the time the 9 doesn't work...and so on. I have gone back to Gingerbread EL29, tried ICS FF18....FH13, I've used custom ROMs and those made no difference. There seems to be a few people who have had this problem as well, but there have not been any responses to help that I have seen.
Click to expand...
Click to collapse
Your problem sounds like it might be different since you say you can't hear specific digits when you press the keypad, and this makes it so you can't log in.
I couldn't log in to my debit card today. I called my healthcare HSA debit card, and when I tried entering my 16 digit card number, their system kept stopping me after about 13-14 digits and would say it doesn't recognize the account number, then ask me to re-enter the 16 digit number. I tried about four times with the same results. I was using my speakerphone every time.
All I had to do was call back and NOT use the speakerphone. It worked first time and every time I tried! Another thing that works if I want to use my speakerphone is go into audio settings and un-check "Audible touch tones".
I think the loud speaker phone was causing their system to hear double presses sometimes.
My new VZW Galaxy Nexus has been occasionally entering a mode where it will not receive any phone calls.
The problem is corrected once I initiate an outgoing phone call.
The outgoing call connects immediately, is clear, and has no issues at all. If I then hang up and try calling the device it will ring immediately and work perfectly.
The problem tends to occur a couple of times per day. I've not found a direct trigger for it.
When the problem occurs, IP network connectivity still works perfectly. I can ping from the device, browse FTP sites, and run a speed test. Using the speedtest.net app (while the phone is unable to receive calls), I'm seeing 26mpbs down and 18mbps up (just like I would if the phone was working).
Powering down and then powering up the device does not correct the issue. Adding a battery pull while the device is powered down doesn't help. Once booted, the device will still not receive calls until you make an outgoing call from the device.
Phone is bone stock. Is not and has never been rooted or modified. Purchased on launch day. Indicated signal strength is great, and service in my area is very good on both 3G and 4G.
There's no indication whatsoever of an issue other than friends later notifying me that I was unreachable.
I believe text messaging may be halted as well, but have not verified this.
Verizon has no idea, indicates everything is provisioned correctly. Device was activated by a VZW store.
Any suggestions or reports of similar issues would be greatly appreciated. I can still take it back to Verizon and replace it with a new item (and I probably will).
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Maybe your phone can automatically detect when someone you don't like is calling
Has anyone seen John Connor?
xxprodigyxx11 said:
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thought this was the case as well after a Verizon tech suggested it. In a rare event, I actually picked this phone up at a VZW store and they activated it for me (while my previous phone was remained on).
Since then I've turned off the old phone (and left it off) and rebooted the Nexus immediately thereafter. The problem still occurs at roughly the same interval.
I actually do a lot of switching between phones for development work, but have never seen this before. Then again I always *228 it myself where the "old" phone has to be turned off.
I just experienced this problem today for the first time. I didn't realize my phone was unable to receive calls until my Gmail account notified me that I had a bunch of voicemails waiting. Then as soon as I made an outgoing call, I had about 12 text messages deliver to me. The weird part is that I was still receiving Facebook and Twitter notifications during this time. I haven't been able to replicate the problem again, but it has happened to me as well. Very weird.
My only hunch is that earlier in the day I was out in the middle of nowhere where my signal was dropping in & out and perhaps when I came back to the city, the network didn't connect properly? I don't know if that's even possible? Also, could my home wifi network be interfering somehow?
I have tested it since I made an outgoing call and now people are able to text me and call me, so it all seems back to normal. It's a very odd problem indeed.
I had the same issue this morning and its funny because I just turned my old phone on last night and that could be the problem
Sent from my Galaxy Nexus using xda premium
I've had a Galaxy Nexus on Verizon for a couple of weeks now and noriced this problem early on, but only in the evenings and night. I stumbled upon this thread looking for a solution. Thanks tliebeck for mentioning it.
I was using my old OG Droid as a bedside clock. In the evenings, after getting home from work, I place the Galxy Nexus on the same bedside table as my old cell phone.
Then I saw xxprodigyxx11's response (thanks, btw!) and tried turning off the old phone. Sure enough, my Galaxy Nexus hasn't missed a call since. It seems to be proximity related, since I was receiving calls just fine on my gnex at work even with my old phone on at home; I'll have to do more testing on that to see just how far apart they need to be.
Sorry that did not work for you, tliebeck.
There is very little information on this situation out there, so I am grateful for the help here. Hopefully someone can come up with a more permanent and universal solution.
Good to know I'm not alone, thanks all for posting!
Still a major issue here.
Took the device to a VZW store and had them replace it with a new one. Problem still happens in exactly the same fashion. They did reuse my SIM card.
Phone seems to do it about every day lately. I've had two calls to VZW level 2 tech support. First guy tried changing a bunch of account settings around, to no avail. Second guy thinks it's a bad SIM card, I'll be heading to a VZW to get a new one of those today, but am doubtful that it will be effective.
The fact that this works across battery pulls and on two different phones just plain screams network or firmware problem.
I had the same issue. First swapped out my 4g sim card...worked OK in store, after being home for 45 minutes it did the same thing again...wouldn't accept calls until an outgoing call was placed. Drove back to Verizon and was able to reproduce the issue in the store. They replaced it with a brand new GNex and haven't had the issue since (a couple weeks). Good luck!!
Sent from my Galaxy Nexus using XDA App
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
tliebeck said:
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
Click to expand...
Click to collapse
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
unremarked said:
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
Click to expand...
Click to collapse
The reason I think it's not an isolated issue is because very few people are going to notice and correctly identify the issue. It's a new device (small userbase), and the more frequently you're placing calls the less likely you are to notice it. It's intermittent with what appears to be an interval of at least a few hours up to a day or more.
The calling party will either go straight to voicemail or experience between two and four rings before being routed to voicemail.
I suppose I should chime in and saying I'm having this issue also. I've found that toggling airplane mode on and then off restores ability for me to receive calls. This is a particularly bad problem for me as my wife is pregnant. She was PISSED the other day because she thought I was ignoring the 6 back-to-back calls she made. I first thought it was a google voice issue but it wasn't. I verified by calling my actual cell number once I caught it in this "mode" again today. Until we figure this out, I have the luxury of being able to add my work cell to the list of phones that GV rings so that I don't miss another call from her. That's actually how I discovered the GNex was in that "mode" again.
The comment about the previous phone is an interesting one. I also use my old phone as a nightstand deskclock and alarm clock. I will try throwing that one in airplane mode for awhile and see if that fixes anything. I don't believe it to be a proximity issue though because my GNex has entered this mode while I was at work and the old phone was at home. It's a half hour drive and there's a mountain in between.
-Josh
I also think that more people could be having this issue without knowing at all which would lead to less complaining. The caller just thinks the receiver is just too busy to answer and leaves a message. Unless you don't get a really important call that a wife/friend complains heavily about, one would never know.
I had purchased a new GNEX a few days ago and I had a really strange problem where the phone would work (receive / make calls) for about 10 minutes, then the radio would just stop working.
Wait a few minutes, and it would come back to life.
Since it was new, I took it back to the Verizon store and they tried to claim it was due to some software issue that was being fixed in the next two weeks, but I disagreed.
Ultimately got a new GNEX and haven't had the problem since. Seems like maybe there is a bad batch out there with faulty radios?
I don't have anything to add except to say that my father's HTC Raider/Vivid did the same thing last night, and it was spooky. I phoned him a few times, and it went straight to VM every time. As soon as he placed a call, all the VM notifications came flooding in, and his phone could receive calls again.
My guess is that it is a quirk with the way 4g is authenticated. Since it's a new type of connection (requires sim card instead of esn) there's some kind of glitch where the old esn isn't fully un-registered with the network. Does your dad also use an old 3g phone as a deskclock or anything?
Me Too! Galaxy nexus stops receiving calls until I place an outgoing cal
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
pcnerdman said:
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
Click to expand...
Click to collapse
Do u have a phone that used to be on that line turned on?
Sent from my Galaxy Nexus using XDA App
Update: have not had this issue come up again since i put my old phone in airplane mode. I always wait for both of my gv phones to ring to ensure this problem is resolved.
Sent from my GalIaxy Nexus using XDA App
This issue is not exclusive to the Verizon Nexus. I have the GSM version through TMobile and quite often (several times a week, maybe more) my phone just stops receiving text messages. I can't even make outgoing calls.
So now, periodically throughout the day I call Google Voice to see if it works. If I get my own voicemail I know that I'm still receiving text messages. If it doesn't connect, then I have to turn on airplane mode, then turn it off again, and the network comes back.
During the outage I still show full bars over 3G.
It's so freaking annoying. I thought the latest update to Android would fix it, but it didn't. There's a Google thread on this too:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=34ad876196cb21c4&hl=en&start=40
Hi guys,
I am experiencing a bug on my Swift where the phone reboots itself during almost all calls after a minute or so. When the phone comes back on, there is no record of the call in the call log! The phone does not reboot during any other activities. Phone details below:
Wileyfox Swift
Cyanogen OS 12.1.1-YOG7DAS2FI
Kernel version 3.10.49
Build Number LMY48Y
I have checked for another similar thread without any luck. Thanks!
I have a similar,though not identical issue. Phone keeps rebooting,seemingly at random,every other day or so. During a call, listening to spotify,idle on the desk...i have an untampered with original Os on the phone.
Cheers,
Me too.
Hi, I just registered to say I'm having the same problem. If you check the Amazon UK reviews too there are several people with this rebooting problem.
So far I have:
- uninstalled all additional apps I installed
- tried it with wifi and data off
- tried the other SIM slot
- done a factory reset
and it still reboots during calls. After the factory reset things appeared to work better in general (alarms now worked properly, and there were more options available, eg in the power button menu), but it rebooted 5 seconds into a phone call, which is a record. It's usually a few minutes into it.
The factory reset didn't actually delete my data (photos, files, etc), so I am going to do a reinstall via Fastboot now; firstly because I'll have to do that I guess if I want to send it back, and secondly to see if it finally fixes it.
I personally think the update process has screwed something up. It did an update as soon as it was powered on for the first time (it to 12.1), then a couple of weeks ago did another update to 12.1.1. It was rebooting before 12.1.1, so it is either 12.1 or earlier where the problem exists.
If it still reboots after a Fastboot reinstall then it's getting send back, and I probably won't ask for another. It's a nice phone, and a nice idea but I can't have a phone that reboots during >50% of calls. That's useless.
Pretty sure you can discount the update process too! I have also had this issue on cyanogenmod nightlies, I honestly thought I had inadvertently pushed the power button..but, NO
*edit* CM13 nightlies
That's strange as I have had no such problem with mine (bought in October) and mine is rooted with the unofficial builds of CM13... Maybe it is a manufacturing error and only on some devices...
Have you tried contacting Wileyfox?
I have not experienced this yet on the Swift when making or taking calls on it.
i'm on the latest cm13 nightly for crackling. each and every time the phone is called, whichever sim, the phone reboots. what a waste...
I have the same issue of spontaneous reboots, mostly during calls but also at other times. Spoke to Wileyfox who weren't very helpful. Has anyone found a solution for this?
Hi, I'm having the very same issue (appears a few are on other forums). Has anyone found a solution? I'm about to factory reset if it continues
Update
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
enzoparker said:
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
Click to expand...
Click to collapse
Hi thanks for the update, I've just factory reset, if problem persists I'll try to get a replacement too! Was it quite a quick replacement process?
R
I'm in South Africa and have the same problem. Whenever sound is involved, I get random reboots. Calls, and music/audio books.
Not with videos though.
It doesn't reset any other time except when I've been listening to music, or on a call.
Been doing this from the beginning.
I thought it was Google Play Music, so downloaded different player.. That made it much less frequent, but then it started affecting my calls as well.
Not happy.
Hi, UK user here. I got this phone less than a week ago and have already had this issue a few times. Two spontaneous reboots on resuming from sleep, being connected to a large WiFi network was the only change from normal use here; then twice regarding calls, once when answering then immediately after reboot it rebooted again while the missed call notification was present, although still on the aforementioned large WiFi network. Unmodified, unrooted, Cyanogen OS 6.0.1 with two sims in use.
Same issue on my a1g2.
It reboots on wf swift Roms. It stucks in call screen on a1g2 stock rom. Strange...
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
DevilMind007 said:
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
Click to expand...
Click to collapse
Maybe it's the Dialer in Cyanogen OS, i installed the Google Dialer and made it default Dialer on my Swift, i don't have any problems with reboots during calls and i make long phonecalls. You don't need root access for this.
Although Wileyfox accept that there is a grounds for returns, I believe it is a software bug in Cyanogen OS 13. This fits in with using another dialler. You could also downgrade, or switch to Cyanogenmod.
Also, I only have found the issue when receiving calls, rather than making them, although I don't use a lot of minutes.
Sent bug reports to Wileyfox.. They're saying that what they see is a battery-pull reboot..
I tell them it's happening while I'm using the phone (music or calls)..
They say they can't see what the issue is.
Cos I'm in South Africa, sending the phone overseas is pointless.
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
Hello,
My brother is having a very weird problem with his HTC One M8. He is using a Verizon phone on a T-Mobile network, and I believe he has Android Marshmallow. Things have worked fine for some time, but for the past two weeks his cell signal usually flickers on and off every 1-3 seconds. Occasionally it will work as normal, usually after he makes a call, but generally speaking he cannot receive text messages or phone calls/voice mail until it stabilizes, which causes him to have to wait sometimes 5 or more hours before getting his messages. Location seems to have no effect on the quality of his signal. He's taken it in to T-Mobile and they gave him a new SIM card, but that didn't help. I helped him use HTC Sync Manager's software repair tool to see if that would fix anything, it didn't. We are trying to avoid a factory reset, but will probably be doing that soon. Has anyone heard of this problem or have any ideas on how to fix it? Buying a new phone is last resort.
Thanks!
Hi there.
My M9 has a strange problem where it rejects phone calls on a seemingly random basis. When I try to call the phone from a landline or another mobile it shows no sign that there's an incoming call. The phone making the call hears a ringing tone twice, and then only a beeping (like an engaged tone but with one beep longer than the other). The odd part is that it doesn't always happen. I get the occasional cold call come through, and sometimes people phoning me can get through, but at other times they can't. It seems consistent that when I'm at home in the evenings it rejects all calls. I'm sitting at home now and if I try to phone from a landline or mobile it won't get through yet the phone is showing full signal and can make calls. I've tried with WiFi and mobile data on and off and rebooting the phone to no avail. SMS messages come through fine all the time.
I've contacted my network (Virgin mobile UK) and they've issued a replacement SIM - same problem. I've tried the SIM in a Nokia and it seems to work perfectly, so I've come to the conclusion it must be the M9 causing this.
To start with I was on the stock HTC Android, and I've not got any auto-reject settings turned on (that I can see). To try and solve this I've done a factory reset via the phone, and when that didn't work I tried doing a complete wipe and installing TWRP recovery and ViperOneM9. It still rejects calls!
Anyone got any ideas? I've tried searching for this but all the posts seem to be about setting up auto rejects, or not receiving any calls at all. Are there any logs I could look at to see if the M9 is getting the call but then rejecting it without my knowledge? Any hints here would be appreciated!
TIA
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
shivadow said:
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
Click to expand...
Click to collapse
Thank you. I started doing that but had some problems, so in the end I bought a new phone, and lo and behold I had the same problem as I had with the HTC, and that was when the phone was fresh out of the box before I'd installed any apps.
After a LOT of playing around with settings, I've now figured out that if I have 4G turned on when I'm at home then all calls are rejected, even if WiFi is also turned on. Forcing the phone to use 3G when I'm at home means I get calls, and if I have 4G turned on when I'm at work I get calls OK. I guess the test with the Nokia worked OK as it wasn't a 4G phone.
After repeated calls to Virgin they've finally admitted that there's a fault on the phone mast close to my house, and by the sounds of it they have a lot of open tickets for that mast. As they use EE's network they say they can't do anything until EE pull their finger out, but as I've had the issue for months I bet it won't be anytime soon. For now I'll have to switch to 4G manually whenever I'm away from home and try to remember to put it back to 3G when I get back. Not ideal but at least I know what the problem is now!
Thanks for your suggestion, even though it wouldn't have worked in this case.