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.
Related
Hi all,
have had my Desire for a couple of months now, well pleased with it. I have not in any way modified it other than installed some apps from market. This afternoon after lunch while it was in my Brodit car holder I suddenly noticed it was asking for PIN code. Entered it, fine. But then a couple of minutes later, same thing again. And again.
Just now I was typing an SMS to somebody and just before finishing screen blanks out, then the screen asking for PIN comes up.
What the heck?
Anybody who has had similar problems and knows what causes/caused them?
I haven't had the battery or sim card out or anything, it just suddenly started doing this.
Cheers
//Joris
*edit*
I have tested switching off the phone, removing battery for a couple of mins then reinserting and rebooting, but same problem persists.
Wonderful, we're going on holidays in 2 days.... :'(
Well I couldn't for the life of me figure out what the problem was, tested with another SIM but same. Completely random, sometimes it would last half an hour sometimes not even a minute.
Did a clear storage/hard reset and after that all seems fine. Except for that my conversations were still there, but somehow if I get an sms from somebody now it's added to the wrong conversation. Then if I reply to it, it goes to the person in the conversation, not the person who sent the msg
Deleted all msgs now so should be sorted. Think a problem with all contacts syncing to and from Microsoft Outlook, it messed up all phone numbers like this:
46 2342423423
so no + and a space between country code and phone number. ANnoying as heck but haven't figured out if there's a setting in outlook or htc sync to solve this.
//J
What ROM/Radio is it running?? is it unbranded??
I have no idea. Bought from Komplett here in Sweden, i.e. unbranded and unlocked. It's running what it came with since there haven't been any updates and I haven't the balls to start experimenting about with it
Strange, I just picked up my Desire today. I rooted it this evening and only noticed it happening after rooting it. I didn't run it for very long unrooted though, so I don't know if it's related. I wonder what's causing it.
maybe this helps:
http://www.xda-developers.com/android/lockpicker-now-updated-to-v0-94/
Flaggie said:
maybe this helps:
Thanks but it goes to SIM lock rather than phone lock... like when you first switch on your phone. The phone doesn't reboot though, it just asks for the SIM pin all of a sudden, even when you're doing something on it.
Click to expand...
Click to collapse
i also had this problem (well more or less) for me it happened when my cellphone signal dropped to limited service (or no services at all) after the phone picks up a signal again its asks for a pin. you mind want to check this out aswell. i fixed this by going into the settings and fiddling around with network/mobile operator settings and such, soz i cant remember exactly, but this did the trick for me.
hope it helps.
I was going to take it back to the shop when I thought I'd try a different ROM first. I installed the OpenDesire 3.0.1 Froyo ROM last night and so far it hasn't done it yet. Maybe the official Froyo ROM won't have that problem either.
Tester app
Hi
I've been having the same problem on my X10 Mini Pro for the last couple of days. To try and figure out what's causing this I've made a small app that checks the sim-status periodically. If it's not available or a pin-code is required for unlocking it the phone starts vibrating plus default notification-sound.
If you're fast you can check your device's LogCat with aLogCat (available from market). At least you'll get notified that you're unreachable
Since I have no Market-account yet you have to upload it to your phone manually with adb. Search google for a howto.
See attached file.
Hi!
Do you have Exchange 2010 sync?
Hi have the same porblem with LG Optimus 2x.
Tom.
Hello! I don't know why but my phone started having this problem. It was out of nowhere. Well, maybe not, I've flashed my phone with the official mango update like two weeks ago, and it was working fine.
And today I saw that that I messages doesn't send out. I tried to call/text myself from other phone, and I couldn't. Phone displays gsm network name in phone hub, and also it shows full gsm connection bars(five of them), so you couldn't tell that something is wrong until you try to text or call. When you call the phone says "dialing..." but this shows forever and there's no sound from the speaker. It's worth mentioning that I've received few messages I've send to myself, but just about 2hours from sending, and then I tried to send a few more and haven't received those. Also, I've suceeded to call for a few times but after a long long wait(like at least 30sec) with the "dialing..." message shown. However, I cannot reach the phone when calling from my other phone.
I've tried to turn my phone on/off, to take the battery/sim card off, reseting the device, but none of these things helped. Then I've decided to flash my device. I've flashed my phone with DeepShining Mango custom ROM, and it seems to be working fine, but the problem still exists.
I don't know what else to do. And that's a major problem, because noone can call or text me. As I've said in the beginning, it was out of the sudden, I haven't done anything to my phone. Just yesterday I was using my phone normally, texted and called with no problem.
So I'm asking yours, guys, help. Could you please suggest what I could do? Thank you very much!
P.S. I've bought this phone from second hand and it was unlocked, but it has an orange logo on the battery cover, so I suppose it was locked to orange.
Did you pay your bill?
I have a prepaid card.
Ok, do you have a another SIM to test
I really have tried to avoid posting but I'm really not sure what to attempt next. I've been through a few threads on the XDA as well as trawled Google but I've not really come up to much.
Basically my One X has been fine since I got it up until the last couple of weeks, I'm not entirely sure if that coincided with a software update or any other changes I could have made but I never seemed to have a problem initially.
I've been using GO SMS since I got the phone, but having just re-installed the app to no avail and having just tried the exact message within a 60 second window through the standard messager it still did not send. This has happened in alternative locations too, so it doesn't appear to be signal based on where I am. After the 4th attempt and the message would not send I put my phone into Airplane mode to reactivate the sim, after doing so and turning it off the message sent.. So it might even be network related.. I've no idea! I've removed the sim card and left it for a few minutes to see whether when it's reinserted if there is still a problem, failing that though I am out of ideas!
Just for your reference I am with Vodafone, totally stock phone as it comes out of the box running the updated 1.29.401.11 software
Any help greatly appreciated.
Ashalak said:
I really have tried to avoid posting but I'm really not sure what to attempt next. I've been through a few threads on the XDA as well as trawled Google but I've not really come up to much.
Basically my One X has been fine since I got it up until the last couple of weeks, I'm not entirely sure if that coincided with a software update or any other changes I could have made but I never seemed to have a problem initially.
I've been using GO SMS since I got the phone, but having just re-installed the app to no avail and having just tried the exact message within a 60 second window through the standard messager it still did not send. This has happened in alternative locations too, so it doesn't appear to be signal based on where I am. After the 4th attempt and the message would not send I put my phone into Airplane mode to reactivate the sim, after doing so and turning it off the message sent.. So it might even be network related.. I've no idea! I've removed the sim card and left it for a few minutes to see whether when it's reinserted if there is still a problem, failing that though I am out of ideas!
Just for your reference I am with Vodafone, totally stock phone as it comes out of the box running the updated 1.29.401.11 software
Any help greatly appreciated.
Click to expand...
Click to collapse
I have the same problem, AT&T HOX, stock 1.73.502 rom, completely un-modded.
You are not alone my friend.
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.