Hi,
I've got the latest FW and am running on DooMLoRD's kernel #8 (now on #9), min/max 256/1209MHz and everything was fine until a couple of days ago when some random Force closes started appearing, and today I experienced SIM lock skips. By that I mean that when my phone boots, it shows SIM lock screen, but after a few seconds it continues to main screen without me entering the code. This second thing started happening after I've installed WidgetLock Lockscreen.
The phone also didn't allow me to connect to my operator. It showed me a toast message Your SIM card can't connect to this operator, or something along that line.
Also, some system apps started FCing, and when I was receiving a call, I saw only the notification bar and black screen, thus could not answer. My phone usually vibrates for a few seconds, then starts ringing, and a bit after that shows the screen with who's calling and the answer/reject slide bar (this whole action is way too slow :/ ).
I went into recovery mode and restored one of the backups, then turned on my phone and everything was alright. After that I restored the newest backup from today and now everything seems to be in its place.
Any ideas what might have been the problem? The call screen delay is still there (it show up after 10 seconds of ringing + a second or two to be able to answer). Is that normal? I also noticed that with WL Locksreen enabled I have to wait SEVENTEEN seconds to be able to see the call screen and answer the call.
Related
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
seraphic8x said:
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
Click to expand...
Click to collapse
Did you try a hard reset?
Am currently running WWE ROM 2.07.401.1 and what happens is, when the screen is locked and I receive a call, and then end the call either with the hardware button or screed button, the lock screen comes back instantly, but for the part over the bottom menu where it says all people and menu.
If you ignore the call, there is no issue...
There is a good 5-10 second lag before this disappears. Does anyone else have this issue or knows of a fix? (apart from reverting back to an earlier ROM, 1.86.xxx definitely doesn't do this )
Any help would be much appreciated!
Screenshot added
Are you using Co0kies Home tab? I noticed with the latest version there were a lot of options for how the screen locked, one of them was to lock when ending a call.
Nope, totally standard
yup I'm having the same issue but i'm running the energy sense 2.5 rom. I was never running sense before this so didnt know if it was a issue with it or what. I disabled all the locking stuff and installed the new pocket sheild that does all the locking by proximity. I pull the phone out of my pocket and it unlocks after a few seconds
It'ss definitely a strange one as it only does it when you press the end call key(s) everything else is fine and refreshes instantly.
I am currently using Go SMS for my txt application. I have it setup to show a popup of a received txt message over the lock screen so I can quickly reply. If I look at the txt, and reply or close it out right away, everything is fine, but if I let it sit for a few seconds, and the screen turns off, when unlocking the screen, the camera doesn't kick on for face detection. The workaround that I have found to get past the lock screen is to press the Emergency Call button, then the back button, then it allows me to use the pattern lock screen to unlock my phone. Has anyone else experienced this?
Just a little more background, I'm running the stock ROM, and the phone is rooted.
Hey gang,
This has been going on a few months for me now, and can be pretty frustrating. Compounded by the fact that wi-fi in my own apt is occasionally shoddy with any device, (frequent disconnect/reconnect issue) sometimes it can be downright maddening. Thank god I have a dope case, because I have launched this ****er multiple times now as a result of the issue. Two factory resets have not solved the problem.
Every time my phone connects to or disconnects from any wi-fi source the phone freezes up completely and is unresponsive for anywhere from 5-20 seconds, pretty much immediately after the wi-fi toast message pops up (although occasionally the phone will freeze b4 toast message pops up). After it regains consciousness, the device will "catch up" with whatever inputs were made while it was frozen.
For example: Keyboard open, typing comment on reddit. Wi-fi toast message appears, phone becomes unresponsive. While unresponsive, if I tap 5, g, h, q, back button (touch key), home button (touch key); after becoming responsive again phone will swiftly type "5ghq," close keyboard (go back), then go home (home button) along with the associated haptic feedback responses occurring.
This also seems to be occuring occasionally when I receive text messages. Sometimes but not always. Though, if it happens with one txt received, I can safely assume it will continue to occur until after I restart or (maybe) put phone down for a while.
Restarting or not using phone for a while, however, has no effect on wifi issue. Wifi issue is occuring every single time, no matter what.
Its a minor inconvenience but can be quite irritating
Anyone else experiencing this or able to help? Thx.
Blob Blobbed said:
Hey gang,
This has been going on a few months for me now, and can be pretty frustrating. Compounded by the fact that wi-fi in my own apt is occasionally shoddy with any device, (frequent disconnect/reconnect issue) sometimes it can be downright maddening. Thank god I have a dope case, because I have launched this ****er multiple times now as a result of the issue. Two factory resets have not solved the problem.
Every time my phone connects to or disconnects from any wi-fi source the phone freezes up completely and is unresponsive for anywhere from 5-20 seconds, pretty much immediately after the wi-fi toast message pops up (although occasionally the phone will freeze b4 toast message pops up). After it regains consciousness, the device will "catch up" with whatever inputs were made while it was frozen.
For example: Keyboard open, typing comment on reddit. Wi-fi toast message appears, phone becomes unresponsive. While unresponsive, if I tap 5, g, h, q, back button (touch key), home button (touch key); after becoming responsive again phone will swiftly type "5ghq," close keyboard (go back), then go home (home button) along with the associated haptic feedback responses occurring.
This also seems to be occuring occasionally when I receive text messages. Sometimes but not always. Though, if it happens with one txt received, I can safely assume it will continue to occur until after I restart or (maybe) put phone down for a while.
Restarting or not using phone for a while, however, has no effect on wifi issue. Wifi issue is occuring every single time, no matter what.
Its a minor inconvenience but can be quite irritating
Anyone else experiencing this or able to help? Thx.
Click to expand...
Click to collapse
I just updated to the DO17 and I am having the same issues... I come from a long line of rooting and rom flashing. This is the first phone I have had that is so locked down that I can literally do nothing.
After this last update I am experiencing the freezes and app crashes like you. It is very frustrating. This will be the last ATT phone I ever own
i have the same problem. not sure what causes this.
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
I dont have this problem.
pogano_celjade said:
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
Click to expand...
Click to collapse
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
lbsilva said:
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
Click to expand...
Click to collapse
Yes, it is very weird and annoying. Not happens every time, but sometimes... ?
This happened to me yesterday for the first time, but I thought that was a problem of the person that was calling me.
It was a number I didn't have in my contacts, and after the bug I immediately called back that number, but it was not available.
I thought the person that was calling me had a very low battery charge and while calling me his phone turned off, causing the bug (because immediately after the bug it was unavailable).
To this date I still did not have this problem.
Me too, i cant answer and reject calls when i upgrade to android pie
Solved: Screen not turning on with incoming calls
Step 1: Go to Dialer or Phone app settings. To do so, you can either go to main settings, then open ‘Apps’, and then scroll down to Dialer or Phone App.
You can also access App Info page by long pressing the app icon, and then tapping the App info option or the small ‘i’ icon in the corner.
Step 2: Now select “App notifications” option and turn it "on"
Step 3: Now if App notifications are turned off, your display won’t wake up when someone calls you. Also if only the “Incoming calls” permission is off, your screen will not light up with incoming calls. Make sure required permissions are turned on and your issue will be fixed.
Xiaomi Mi 2 Lite. I cannot get incoming calls to show on my screen, so I can't answer. Tried switching notifications off and on again, tried forcing stop. Two days ago I did a factory reset and was OK for 2 days. I think this is since latest Android update about a 10 days ago.
Call answer bug
I have similar issue on Mi A1, been going for a while. Sometimes, call comes in, the answer key cannot pick and cannot reject the call. This happened after a certain update I just dont know which. I have noticed that this mostly happens at some particular GSM antennas, sometimes, just by moving away from that antenna (that's when in a car) solves the problem. But as long as I remained in that location at that time, i cannot pick or reject calls, I also can't make calls, I get the promt, network problem, even though the service bars r showing. And in some cases the people calling will tell me, that calls to me are not going through.
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
PeterSharpe said:
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
Click to expand...
Click to collapse
Clear data and cache of the "phone" App and if necessary reinstall the application