Database Develop

[Q] Dialer screen loss

I'm running 4.4.4. Rooted and unlocked.
This problem occurred before I upgraded.
When I call someone, the dialer screen immediately disappears and when I'm done with the call I usually have to press the power button 3 or 4 times to get my lock screen back. I have blue tooth for my hearing aids. When I use that, it doesn't disappear although after the call I need to hit the power button twice for the lock screen. I might have changed some settings inadvertently due to the screen changing when it sould have turned off. I think the blue tooth on my hearing aids is what activates the screens. I'm using Apex launcher. I have had my phone completely apart because of a plugged mic opening. I don't think this anything to do with the problem at hand, At one time on my phone I saw a setting someplace where I could end a call with the power button. Anyone know where that's at? Any help would be greatly appreciated. I might flash it back completely stock.
Moto X DE

Do you have two dialer apps? I had a similar problem and the problem ended up being having the stock dialer as well as the google dialer installed.
I got rid of the stock dialer and then the problem went away.

Settings > Accessibility > Power button ends call (check that).
Do you have a screen protector? If misplaced, it may activate the sensor that turns off the screen when the phone is up to your face.

metaljr81 said:
Do you have two dialer apps? I had a similar problem and the problem ended up being having the stock dialer as well as the google dialer installed.
I got rid of the stock dialer and then the problem went away.
Click to expand...
Click to collapse
Only one

Groid said:
Settings > Accessibility > Power button ends call (check that).
Do you have a screen protector? If misplaced, it may activate the sensor that turns off the screen when the phone is up to your face.
Click to expand...
Click to collapse
No.. took it off

I am having this same problem . only one dialer app unlocked and rooted.
Sent from my XT1060 using Tapatalk

To anyone having this issue: I have seen this issue several times now with multiple members. I haven't seen a working solution yet except that a factory reset sometimes solves it, and flashing back to 100% stock as per the return to stock thread (in the General sub-forum) always solves it. I know it is often a pain to have to set everything up all over again, but it is the only solution I'm aware of.
Good luck

Yep factory reset was the only thing that fixed it for me
Sent from my XT1060 using Tapatalk

Unresponsive touchscreen with FXP331 (CM11)

Hi all there
I have been having problems with the touchscreen becoming unresponsive after any blackout - intentional lock, screentimeout, wake from phone call.
It's a fresh install and apparently this is a common problem: code.google.com /p/freexperia/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=&id=2410
I solved it by flashing the lightning kernel from the development forum.
Hope it helps somebody.
Daniel

stormsaber said:
Hi all there
I have been having problems with the touchscreen becoming unresponsive after any blackout - intentional lock, screentimeout, wake from phone call.
It's a fresh install and apparently this is a common problem: code.google.com /p/freexperia/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=&id=2410
I solved it by flashing the lightning kernel from the development forum.
Hope it helps somebody.
Daniel
Click to expand...
Click to collapse
It's because of double tap to wake which does not work on Xperia ZR disable it from display in options

harshal.rio91 said:
It's because of double tap to wake which does not work on Xperia ZR disable it from display in options
Click to expand...
Click to collapse
I think there might be a buck in FXP331 which prevents disabling of DTW? I couldnt disable it anyway but its disabled by default with lightning. Have had no problems or bugs at all with this setup, that I've found yet.

persistent dt2w has been in CM11 nightlies since a few weeks ago

chewdaniel said:
persistent dt2w has been in CM11 nightlies since a few weeks ago
Click to expand...
Click to collapse
Apparently I'm still having a problem with this, even though dt2w is disabled for me. It only happens after a call.
During a call, my screen goes black. Nothing I can do wakes it up.
If the other person hangs up first, the screen returns to normal.
If the other person does not hang up (e.g. answer phone, etc.) the screen remains black and I must remove the battery.
This is problematic for me. Is anyone else experiencing similar?
For now, perhaps there is a way to remap a key - for instance the shutter button - to hang up the call? Unfortunately the apk 'button remapper' (lifehacker.com /5705224/buttonremapper-reassigns-your-android-phones-buttons) did not seem to have any way to select that key. Does anyone have any other ideas or solutions?

stormsaber said:
For now, perhaps there is a way to remap a key - for instance the shutter button - to hang up the call? Unfortunately the apk 'button remapper' (lifehacker.com /5705224/buttonremapper-reassigns-your-android-phones-buttons) did not seem to have any way to select that key. Does anyone have any other ideas or solutions?
Click to expand...
Click to collapse
The relevant keys are 568 (soft press to focus) and 766 (long press to take picture). 766 is already set to WAKE the screen, and I just set 568 to do the same. I'm guessing it won't work though.
Hopefully someone else has had this problem and knows a solution...

[Q] Incoming call with screen on problem

Greetings everyone. Device - XT1056, GSM unlocked. After going from Cm12.1 to stock 5.1 then back to Cm12.1 a problem occurred. When I'm getting a call with screen on, the screen with caller and answer button does not appear only sound . When it's on home screen I can switch pages, but no answer options. The solution I use is to turn off the screen with power button and the the incoming call screen appears. When I'm using any app and getting a call - app freezes and navigation buttons stop working. Same solution - to turn off the screen and then answer the call. So maybe someone knows what's this about and some ways to resolve this?

I had a similar issue on previous nightlies. Check today's build, I think this commit solved it: http://review.cyanogenmod.org/#/c/102378/

Thank you for the info, can't flash it right away, at moment I'm using it with activated "Heads-Up notifications" which partially solves the problem, it became possible to enter call screen through on screen notification.

Weird vibrations while in call

I get random vibrations on the phone while talking on the phone. When I check the phone there is nothing there for notifications. Is there something in the background going on? Anyone else experiencing this?
Nexus 6

I had a mysterious vibration when scrolling back a youtube video but nothing else happened. Maybe, but maybe, it is because of those idiotic ads infecting chrome or browsers, which causes very alarming vibrations. Since I use adaway I never get those vibrative ads so maybe those ads are the culprit. But of course it is better to check background apps or maybe you dont see a notification because you block it ?

Got the same problem! thought it was just me with my 'monday morning nexus 6' having multiple problems no one else seems to have
I don't think it has anything to do with ads, cuz i'm running adfree since i bought the device and chrome has been deinstalled too.
When i check during or after the 'vibrating' call no notifications are there; i don't block any notifications.

When I was on phone today I had short vibrations, but because of buttons like keypad, pause, speaker selection. For some reason screen did not go off and my cheek was pushing those buttons and making vibrations. Can you check if that is your case?

Yes, that's what i thought at first too Scythe, but my screen does go out correct and stays out until i put the phone off my ear to look

Do you have double tap to wake enabled? When I did, I noticed small vibrations when on a call.

@mulhiny Yes i have double tap to wake enabled and it's something i haven't thought of yet! Gonna give it a try and get back here!

Serious practical problem lock screen

Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?

tomsag said:
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
Click to expand...
Click to collapse
Yep I have the same thing... Today my pocket took 9599295 pictures and movies.. also when I'm a bit sweat my pocket dial random numbers. I've noticed that when screen is touched and disnt recognize fingerprint then whole lockscreen shows up and its easy way to random open dial or camera... Its rly anoying, because I dont want to hide phone screen outside of the skin. (Its easier to break screen if I hit something with my leg.)
Dunno why it doesnt use proximity sensor to recognize that phone is in the pocket like every other brand... :/

Do you have the double tap to wake up activated?

I had this problem a while ago and it was the double tap that played all kinds of tricks calling emergency and taking pictures in my pocket! Disable double tap to wake up screen and the problem goes away.

Disable the fingerprint icon on when the screen if off.

Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.

tomsag said:
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
Click to expand...
Click to collapse
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!

gerhard_wa said:
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
Click to expand...
Click to collapse
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.

tomsag said:
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
Click to expand...
Click to collapse
My only solution was to buy a flip case. At first, I disabled the fingerprint reader by removing all fingerprints and setting up face recognition, but this didn’t fix the problem you are talking about. I don’t really like flip cases, but the Nillkin QIN Smartcase is rather good.
So now I ‘m eagerly awaiting a fix from Xiaomi so I can strip the Mi9 again!

Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Where can the fingerprint icon be disabled? Thank's.

j4dotcc said:
Where can the fingerprint icon be disabled? Thank's.
Click to expand...
Click to collapse
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.

gerhard_wa said:
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
Click to expand...
Click to collapse
Thanks for the prompt reply. I don't have the problem and just wanted to know where I can disable the fingerprint icon. Thanks again.

New uppdate out that include Pocket Mode. MIUI-V10.2.27.0PFAEUXM EEA version.