Related
Hello,
I've had a very annoying issue with my Touch Pro.
Once before I found out that the clock was behind about 10-15 minutes. Today morning the clock was about 30 minutes behind. It sucks if you use the phone for alarm, too.
After soft reset it's ok again.
Any ideas what's causing it? It's definately not a time zone or DST problem.
Fixes?
Thanks
just realized my own Fuze is doing this when daylight savings occured last week.
First thing i can think of (since i dont have data on at the moment) is its my wifi connection ?
I dont know how or why, but that is the only "extra" Ive been using lately.
Make sure you post if you figure it out. I also use apptodate. ??
Have you tried checking the computer you sync to?
Is that off also?
Joe_PDA said:
Have you tried checking the computer you sync to?
Is that off also?
Click to expand...
Click to collapse
Time on comp is right.
Alright,
So I got the One X yesterday and the first thing I did was root it. After that, I followed the guides for removing the ATT branding, reactivating the FM radio, and removing the att wifi default network, and then theming and skinning it. I turned off wifi last night to test out the LTE network, and then tried to reactivate it this morning. When I say try, I click the wifi toggle and it replies "Error". Has anyone encountered this/knows how to fix it? Thanks in advance!
Happened to me once or twice...also happened to me a few times on my Captivate (running CM9).
A reboot should bring things back to normal. I'm not sure if this has anything to do with the wifi issues half the people here are complaining about since I haven't been paying too much attention to that issue.
Move up to 1.82 to fix the error. I had the same.
Tried reboots. No joy. Ill try to upgrade to 1.82, but it will have to wait until after class. What would be the best way to preserve application arrangement/theming, or am I SOL on that one?
ZombieLinux said:
Alright,
So I got the One X yesterday and the first thing I did was root it. After that, I followed the guides for removing the ATT branding, reactivating the FM radio, and removing the att wifi default network, and then theming and skinning it. I turned off wifi last night to test out the LTE network, and then tried to reactivate it this morning. When I say try, I click the wifi toggle and it replies "Error". Has anyone encountered this/knows how to fix it? Thanks in advance!
Click to expand...
Click to collapse
Have a similar problem. Happened when I edited the wpa_supplicant.conf file in /data/misc/wifi. It was meant to prevent auto connect to AT&T hotspots but ended up giving me an error after a reboot.
To fix it, open the file in text editor and make a change, either add a blank line or remove one and save it. Also, delete the wpa_supplicant.conf.bak file in the same folder..
I have no clue why this is happening and one of the above steps may not be doing anything but when I do that, my wifi works again until next reboot.
Good luck
Thanks the update to 1.82 solved the problem.
wpa_supplicant.conf
ZombieLinux said:
Thanks the update to 1.82 solved the problem.
Click to expand...
Click to collapse
In case anyone else is having this problem and is already on the 1.82 update, or if that didn't fix it...
You can delete /data/misc/wifi/wpa_supplicant.conf.
That may fix the problem. Somehow my wpa_supplicant became corrupt I guess and deleting that solved my problem.
I have a one S, but that shouldn't change much.
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Whisk_33 said:
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Click to expand...
Click to collapse
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
amber12129 said:
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
Click to expand...
Click to collapse
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
mtemlm satisfy
Whisk_33 said:
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
Click to expand...
Click to collapse
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
amber12129 said:
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
Click to expand...
Click to collapse
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Whisk_33 said:
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Click to expand...
Click to collapse
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
amber12129 said:
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
Click to expand...
Click to collapse
So, I have the option to force stop it. (no change in results).
I've even downloaded the "Google Voice" app, which added the "Voice+" app, opened it, confirmed that it was on disable and still no change.
I have no idea why this problem started this morning since I don't believe I am any changes to my phone the past couple days... I really don't know what information I can provide to help troubleshoot it...
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
thezam said:
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
Click to expand...
Click to collapse
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Whisk_33 said:
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Click to expand...
Click to collapse
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
thezam said:
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
Click to expand...
Click to collapse
A bunch of us on S4s seem to be having the same problem! The timing of this issue all happening at once is weird... http://forum.xda-developers.com/showthread.php?p=50552025
OK this really does seem to work for me as a temp workaround...it sticks through reboots and all. Go to the dialer and enter the trusty old *#*#4636#*#* then go to phone settings and change preferred network type to CDMA only then back out and reboot.
It kinda sucks cause it's slow on the go, but at least I can send texts reliably. I have WiFi most places I am anyway.
If anyone figures out a real long term fix please post!!!
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
gagnier27 said:
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
Click to expand...
Click to collapse
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
amber12129 said:
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
Click to expand...
Click to collapse
Some people don't have voice+ and the solution you used isn't an option for them.
For those of us less fortunate than you, It seems you can fix the problem by loading a TW ROM and flashing the MB1 firmware. Then you can return to CM
I had XVoice+ for Exposed on my SGS4, it stopped me from sending texts. It was ok when i uninstalled it. I hope that might help.
Hi All,
I have a fairly old Nexus S (Android 4.1.2). For some reason or other it switches itself off if not used for a few hours. I then have to go through a re-boot and PIN No. routine to use it again. While it is off I frequently miss calls.
I can't find anything in "Settings" which will enable me to adjust the period which it remains active.
Has anyone else experienced this?
Any help greatly appreciated
Regards
Art
artpayne said:
Hi All,
I have a fairly old Nexus S (Android 4.1.2). For some reason or other it switches itself off if not used for a few hours. I then have to go through a re-boot and PIN No. routine to use it again. While it is off I frequently miss calls.
I can't find anything in "Settings" which will enable me to adjust the period which it remains active.
Has anyone else experienced this?
Any help greatly appreciated
Regards
Art
Click to expand...
Click to collapse
Hi There,
Well i am sorry to say that either you didnt explain your problem correctly or i didnt get it properly well all i can say that there is some kind of a Bug in your device which switches it off by it self.
You can try This:
*Factory Reset your device.
OR
*Reinstall the Rom.
This happens on every Lollipop ROM I have flashed, no problems on 4.4 ROMS. I do clean installs, do not restore anything from Tibackup. So basically what happens is I will randomly but very frequently lose all data and cell service. Like once every three minutes frequently. It only lasts about 5 seconds at a time. The signal bar triangle will have an exclamation mark in it (see attached example). I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option. I have read some threads about this exact same thing happening on Nexus 5 after Lollipop update but they are old and it seems to have been fixed with an update. Does anyone have any ideas about what is going on? I'm on TMO in the US and like I said, it ONLY happens on Lollipop ROMs it does not happen of Kitkat.
I read this as sort of an explanation as to why but nothing as to how to fix it. It is driving me insane.
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
budm said:
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
Click to expand...
Click to collapse
Only discussion about this I have seen is in the Nexus 5 forums, nothing in OPO
Any insight to this would be greatly appreciated.
Come on guys, am I really the only one with this issue?
TigerDNA said:
Come on guys, am I really the only one with this issue?
Click to expand...
Click to collapse
You're not alone, I have this as well but I don't get the exclamation mark but instead the triangle appears completely empty, as if I have no signal at all.
anyone know a way to fix this awell? i flashed the new lolipop alpha modem and still same thing if not worse
The only time this has happened to me is when I toggle Wi-Fi. It for this every time, but have no data issues otherwise. Seems to be when switching between ip addresses. Are you possibly between towers or roaming on another network? May be the issue, but I can't say for sure. Running the lollipop rom exodus, no issues at all.
EDIT: also what baseband are you guys on? I thought I saw something similar and someone flashed a test baseband and it fixed whatever issue they were having. Link coming shortly.
EDIT 2: just now noticed the list above mine about the alpha modem and it not working for them. If anyone else needs to try however, link is http://forum.xda-developers.com/sho... work for some and not others.
from the one+
Does anyone know if we can flash the CM11S modem on CM12?
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
alleykat2561 said:
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
Click to expand...
Click to collapse
In OP "I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option."
Same issue here. Running SlimSaber using alpha radio.
Same problem on two OPOs here, both running Temasek CM12
Anyone found a solution yet?
I have the same issue on CM12, BlissPop and Validus ROMS.
Strangely I do NOT have the issue on Euphoria.
Think it happened after I flashed the Alpha L modem.
Tried flashing an older CM11S modem, but no luck...
Hi,
Sorry for the noob answer but anybody tried settings>mobile networks>preferred network type and set it to 3G? I flashed a new rom from stock CM and noticed that I was experiencing signal trouble, I checked my status and the signal detected is LTE so I changed my network to 3G and network signal improved. Downside is that you cant use LTE (but thats ok for me since here in our country, LTE signal is still kind of limited)
Zino same for me. Ever find a fix or a rom that doesn't do this?
OP here, it's strange that all of us have this issue, the same issue that came up on the Nexus 5 thread when L was first released but know one else seems to have any knowledge of it. I am almost certain it doesn't have to do with our carriers but rather something software related.
I'm also suffering from this issue, until now the only way I knew how to fix it was to wipe the cache in recovery which takes ages!
got the same problem :<
I have a similar issue. I use t mobile in the USA and LTE works, H+ works, but 3g shows signal and won't load anything. No idea how to fix it.