Related
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
sammy.sung.me.a.song said:
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
Click to expand...
Click to collapse
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Flash cm10 or Sammy jb
Sent from my GT-I9300 using xda app-developers app
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
5aq1b said:
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Click to expand...
Click to collapse
How is that very different from a restore?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Unfortunatlly mate, i think ur having problem with this stock rom did you try to factory reset your device to eliminate those bugs. or flash another Rom because this is definitly a Rom problem.
sammy.sung.me.a.song said:
How is that very different from a restore?
Click to expand...
Click to collapse
it's not lol but at least this way i'll gain as well by upgrading to jelly bean - 2 birds with 1 stone etc etc
kachrukamble said:
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
Click to expand...
Click to collapse
i'll try this as well mate - thanks!
Same issues that I'm facing
I'm also facing the same issue.... Long black screen pause when exiting or moving from one app to other. Very very frustrating ....
Tried all the trick in world including those that mentioned below.... Will be returning the device and going for a iPhone 5 !
Same exact issue, any results?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
bvz2000 said:
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
Click to expand...
Click to collapse
have you tried a different modem( also use getril to match modem and ril)
slaphead20 said:
have you tried a different modem( also use getril to match modem and ril)
Click to expand...
Click to collapse
Thanks for the quick reply. I didn't know what a ril was and did a little research. Fascinating.
As far as I can tell, and please bear with me since I am a complete noob here (though I am resonably facile with Linux), since I am running the original ROM, I don't have any influence over the RIL. Is that correct? I downloaded getril, but it says that my device (Verizon GS3) is not supported.
What is the text that would show up in a log if I made a call? I'm going to try and search the logs again, maybe that will tell me something,
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.
Hey guys.
I recently upgraded to JB. I have an Xperia P.
Most of the things work, but there is a BIG issue with the phone app.
It lags and crashes to the point that I literally struggle to receive and make any call. It is by far the worst bug you can get in a phone. Coz then it ceases to be a PHONE.
Anyone else got this issue? Maybe there is a way to fix it? I have tried to repair the phone via PC companion, but nothing.
Hi
I also experienced this problem, while receiving calls it's sometimes impossible to answer (slider locks on the right side of the screen and application freezes) and make calls - short lag appears after touching the contact, then the screen blinks, then it calls or freezes. It's becoming more and more annoying. I've tried wiping data and cache of Phone application, neither helped.
That being said, I'm currently on a Jellybean 6.2.A.0.400 build, unbranded (changed from branded build, my contract provider is still keeping the OTA). I'm always in battery stamina mode and I'm using Apex launcher instead of stock.
Maybe something is interfering with the app, I don't know. Other thread about ICS being laggy suggested limiting background process limit - I didn't do it just yet, I need to check if any of background apps are not responding (turned Show all ANRs on, I wonder what will happen).
I hope somebody will find an answer to this problem.
Cheers.
I used to roll with nova launcher too, and i have the impression that when i changed back to stock, things were better.
But still not good enough. There are times that when there is an incoming call, the phone just vibrates, without any ringing.
It seems that the issue was solved in A.1.100 update, as it does not occur anymore. However, sometimes there's some trouble reaching me on the mobile, as if I had no coverage, the calls go to voicemail. Anyone has a solution?
Sent from my LT22i using xda app-developers app
I have (obviously) an HTC One AT&T Model, running CyanogenMod 11 M2? Whatever the current milestone is. I'm pretty sure it's 2. Anyways
EDIT: The CM version is 11-20140104-SNAPSHOT-M2-m7att
I'm not sure if this is a ROM error or not, but I've got a really strange bug. CM 11 was running mostly fine, aside from the occasional reboot, which was a deal breaker fr me, as I really enjoyed it otherwise.
However, yesterday, right before class, I was on a phone call, and when I hung up, I locked my screen as usual. Well I went to unlock it a few minutes later, and the screen was black, but the backlight was on, and the control keys on the bottom were on. I could not get the phone to respond to anything, so I hard shut it down(held the power button for about 10 seconds). When I booted it back up, it had made 2 changes I noticed immediately.
1.) My background was reset from the one I had to a random CM wallpaper, and not even the one that comes with CM11.
2.) (and the more annoying one) I now have a constant notification from my default messaging app that tells me i have XX amount of new notifications, with the number growing every time I get a new message.
Now, I use EvolveSMS as my default, having just recently switched from GoSMSPro to Hangouts with CM11, and now this one. I have never used the default messaging app, as it just plain lacks some features I want. I've gone through the default app, however, and "read" every text,and the number in the notification did not decrease. When I clear my notification, it returns within 3 seconds. I think 3 seconds is longest I've gone without it.
Yesterday, I went through and, regretably, deleted ALL of my texts. At that time, I had 35 "new"messages. That got rid of the notification. So I went back to using my EvolveSMS, and now today, I got the notification again, and have 37 "new" messages as of now.
Any ideas what the heck could cause this? Obviously that random freeze had something to do with it, I just can't find anything out.
ryno9100 said:
I have (obviously) an HTC One AT&T Model, running CyanogenMod 11 M2? Whatever the current milestone is. I'm pretty sure it's 2. Anyways
EDIT: The CM version is 11-20140104-SNAPSHOT-M2-m7att
I'm not sure if this is a ROM error or not, but I've got a really strange bug. CM 11 was running mostly fine, aside from the occasional reboot, which was a deal breaker fr me, as I really enjoyed it otherwise.
However, yesterday, right before class, I was on a phone call, and when I hung up, I locked my screen as usual. Well I went to unlock it a few minutes later, and the screen was black, but the backlight was on, and the control keys on the bottom were on. I could not get the phone to respond to anything, so I hard shut it down(held the power button for about 10 seconds). When I booted it back up, it had made 2 changes I noticed immediately.
1.) My background was reset from the one I had to a random CM wallpaper, and not even the one that comes with CM11.
2.) (and the more annoying one) I now have a constant notification from my default messaging app that tells me i have XX amount of new notifications, with the number growing every time I get a new message.
Now, I use EvolveSMS as my default, having just recently switched from GoSMSPro to Hangouts with CM11, and now this one. I have never used the default messaging app, as it just plain lacks some features I want. I've gone through the default app, however, and "read" every text,and the number in the notification did not decrease. When I clear my notification, it returns within 3 seconds. I think 3 seconds is longest I've gone without it.
Yesterday, I went through and, regretably, deleted ALL of my texts. At that time, I had 35 "new"messages. That got rid of the notification. So I went back to using my EvolveSMS, and now today, I got the notification again, and have 37 "new" messages as of now.
Any ideas what the heck could cause this? Obviously that random freeze had something to do with it, I just can't find anything out.
Click to expand...
Click to collapse
sorry but you won't get much support for CM11 here
try posting in the Rom's thread
clsA said:
sorry but you won't get much support for CM11 here
try posting in the Rom's thread
Click to expand...
Click to collapse
Change your messaging app from hangouts to messaging, the notification will go away, and stays away after you switch back to hangouts. Done and done.