Database Develop

Screen not waking up after call ends or during call.

This started happening about two weeks ago. During a call when I pulled the phone away from my face in order to press the end call button, the screen did to wake up. I could not end the call. This has been happening quite regularly now. The screen simply does not turn on after or during a call. Even if the other person ends the call from his side, the screen on my phone does not start.
I was using the stable version of the official CM7 at that time so I flashed the rom again. Since that did not work, I did a clean installation of Mebitek's CM7 without restoring any backups. But I am still having the problem. I am now using the power button to end the call like a handicap person would.
I think something might be wrong with the proximity sensor or my battery. Since, I have absolutely no expertise of how the phone functions, I seek help from you guys. Please give me some suggestions.

try changing the proximity delay

Flash new rom.

dheeraj (dhlalit11) said:
try changing the proximity delay
Click to expand...
Click to collapse
Even i face the same issue, i have tried flashing many roms and even tried installing the Samsung official gingerbread firmware with the odin software.It is still the same, display does not wake up after the call. any solutions pls.....

AW: Screen not waking up after call ends or during call.
Do u use a screen protector? I heard some might cause problems with proximity sensor.

Screen protector and wakelock
Masrepus said:
Do u use a screen protector? I heard some might cause problems with proximity sensor.
Click to expand...
Click to collapse
I used to have this same problem. The problem seems to be a combination of the screen protector/case getting in the way of the ambient light sensor and therefore not allowing the phone to accurately measure ambient light, and the phone going into some sort of sleep mode. I usually wipe my ambient light sensor off, and adjust my silicone case to allow the light to come in, but the thing that solved the problem for me permenantly was running the small app called wakelock to keep the system from going into complete standby. I am sure that this solution affects battery life, but I still get 10-12 hours between charges which is enough for me.
This thread talks about a similar problem, and this is where I got the idea to try this fix for our problem: http://forum.xda-developers.com/showthread.php?t=1491223
rodjoo said:
No no no guys.. don't bother with reflashing and stuff, that's not the problem.. I had the same problem and I googled it for months until I've learned its a Samsung wifi hardware related problem and mostly Galaxy devices are affected. Something is wrong when phone goes in standby. It continues to work but you can't wake it and you have to reinsert battery to get it on again.
The solution is to install a tiny app called Wake Lock, it's there on market.. it keeps phone awake even when you lock screen. My phone doesn't shut off anymore and I can finally rely on it. I don't have to think anymore and check all the time if the phone is off and if I'm going to miss a call...
The alternative is to turn off wifi before you lock screen but I think that most of us need wifi on all the time to get mails and messages on time
Click to expand...
Click to collapse

Galaxy mini doesn't have ambient light sensor.

My mistake
yackovsky said:
Galaxy mini doesn't have ambient light sensor.
Click to expand...
Click to collapse
I am of course mistaken. It is the proximity sensor that is malfunctioning due to the screen protector and case.

dheeraj (dhlalit11) said:
try changing the proximity delay
Click to expand...
Click to collapse
Where to locate that setting?

[Q] Best way to wake the device?

I wonder what is your prefered way to wake the device. For me the most comfortable is using an app like Simple Cover Lock, but it causes a bir battery drain and sometimes is very sensitive, so the phone can wake while it's still on your pocket.
Also, I read the s2w , tap to wake and so also causes battery drain, so I don't know what method is more battery friendly (I personally don¡'t like using the power button, it's not comfortable at all for left handed people)
Opinions from devs and skilled people are more than welcome!
Thanks

On m7, half-screen dt2w is my favorite, with l2s. I don't think there is any significant drain from this, and combined with pocket detection, there are almost no accidental wakes for me. The ones I do have, tend to be from the power button being pressed when I sit or bend.

For me it's dt2w then s2s, also vol2w is very helpful when I'm driving to change songs. I've read before flar2 has said these wake/sleep options have such minimal affect on battery you will never notice.

Bottom half DT2W, then sweep2sleep if available.

Bottom dt2w (kernel) and dt2s (secure settings alias).
[size=-2]Send with much love & Android. ( HTC One M7 )[/size]

I use wake gestures(dt2w). It's an options in Sense 6 toolbox. It requires a kernel by flar (bulletproof or elementalX)
Verstuurd van mijn HTC One

No one uses proximity sensor? It is like: i take my phone and it turns itself on... magic!

blackhawk_LA said:
No one uses proximity sensor? It is like: i take my phone and it turns itself on... magic!
Click to expand...
Click to collapse
Yeah and it will also turn on by itself many times in your pocket too.

It depends, on my old Xiaomi Mi2s it didn't ever turn on while being in my pocket, but it seems like m7 proximity sensor is more sensitive...

[Q] Adaptive display doesn't work

Is anyone having trouble getting adaptive display to work consistently? It kind of just does it when it wants. Cannot get notifications to display constantly and when picking up phone almost never works.

joshtb86 said:
Is anyone having trouble getting adaptive display to work consistently? It kind of just does it when it wants. Cannot get notifications to display constantly and when picking up phone almost never works.
Click to expand...
Click to collapse
Yes. I turned that crap off a long time ago. It improved my batterly life a lot. I'd rather have knock to wake enabled than stupid adaptive display. Or an LED. And to think, Motorola disabled the LED and knock to wake because of Adaptive display and it doesn't even work right!!!!!!!!!!!

blazinazn said:
Yes. I turned that crap off a long time ago. It improved my batterly life a lot. I'd rather have knock to wake enabled than stupid adaptive display. Or an LED. And to think, Motorola disabled the LED and knock to wake because of Adaptive display and it doesn't even work right!!!!!!!!!!!
Click to expand...
Click to collapse
i wonder if thats whats causing my battery problems. i turned it off also. does anyone have any ideas for a solution??

joshtb86 said:
i wonder if thats whats causing my battery problems. i turned it off also. does anyone have any ideas for a solution??
Click to expand...
Click to collapse
I'm hoping they fix it in the next update? The workaround to get the LED working doesn't seem to be fruitful at this point. Just gotta make due I suppose?

Adaptive display?
Is that some weird hybrid between Adaptive brightness and Active display?
:cyclops:

joshtb86 said:
Is anyone having trouble getting adaptive display to work consistently? It kind of just does it when it wants. Cannot get notifications to display constantly and when picking up phone almost never works.
Click to expand...
Click to collapse
i have been able to duplicate this behavior by selecting no lock screen. then ambient display seems not to work even if selected to. but when i enable any lock screen it works "almost all" of the time.
do you have a lock screen set? do you use trusted devices etc?

blazinazn said:
I'm hoping they fix it in the next update? The workaround to get the LED working doesn't seem to be fruitful at this point. Just gotta make due I suppose?
Click to expand...
Click to collapse
I am rooted, using light flow and my LEDs work just fine. Albeit, but colors do not seem to mix well. More like three separate LEDs plus a charging led as I understand it.
This is what I followed... Works the bahlzzzz
Can't seem to paste the link. Notification light confirmed byJMUT. In the general section.

lock screen is set on mine.
also use trusted devices.

I use a pattern unlock and my bluetooth headphones are a trusted device. I have no issues with the notification

Can't turn off double tap to wake?

I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?

Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it

WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
FWIW, Exodus and I'm sure some other ROMs, have a setting to prevent pocket wake ups by using the proximity sensor.

WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
Are you sure it's not ambient display waking your phone?

Eh... "ambient display" doesn't wake your phone. Ambient display just shows WHEN your phone is awoken by... tap to wake, shake to wake, incoming notification.
OP: Some people confuse tap to wake and shake to wake. Nexus 6 implements shake to wake by default. Problem is that tapping on the screen can.... shake the phone.
This generally should NOT be going off in your pocket. Either, that is. Reason is that it is *supposed* to use the state of the proximity sensor as a CONDITION on whether or not it should start up ambient display. The proximity sensor will read as "near" when the phone is in your pocket, thus prevent tap or shake to wake from triggering ambient display.
So sounds like you probably tried a couple of different sysimages that both contain a bug that stops it from taking the proximity sensor into account. My guess would be something that is based on cyanogenmod (aka "the buggiest android ever conceived"). Try stock and see if the problem goes away.

Personally, I prefer to use a custom ROM with native LED control and disable ambient display.

danarama said:
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
Click to expand...
Click to collapse
what do you even mean?

slamsal said:
what do you even mean?
Click to expand...
Click to collapse
What part don't you understand?
If you haven't got a modified Nexus 6 with this problem, then this isn't relevant to you.

Double tap to wake on Stock rom (s228) doesn't work well!

As title, i'm using stock s228. But the Double tap to wake doesn't work well. Sometime it's perfect, but sometime it doesn't work!
Why?

hgiang0808 said:
As title, i'm using stock s228. But the Double tap to wake doesn't work well. Sometime it's perfect, but sometime it doesn't work!
Why?
Click to expand...
Click to collapse
Because stock ROM and all other company roms we have use software method to control dt2w. There is a system app in vibe called blackscreengestures which controls dt2w.
But sometimes, when you leave your phone idle for some time, the phone goes into deep sleep and the screen input is shut down to save battery. That's why when you double tap again, it doesn't work.
When you use custom roms, the dt2w part is not in ROM, but it is present in the kernel. Kernel is linked to hardware so indirectly the bonding between screen input and dt2w is much better and remains always on. But since the screen input remains always on, it costs battery.
If you use custom kernel with dt2w on stock, dt2w will ALWAYS work.

tanish2k09 said:
Because stock ROM and all other company roms we have use software method to control dt2w. There is a system app in vibe called blackscreengestures which controls dt2w.
But sometimes, when you leave your phone idle for some time, the phone goes into deep sleep and the screen input is shut down to save battery. That's why when you double tap again, it doesn't work.
When you use custom roms, the dt2w part is not in ROM, but it is present in the kernel. Kernel is linked to hardware so indirectly the bonding between screen input and dt2w is much better and remains always on. But since the screen input remains always on, it costs battery.
If you use custom kernel with dt2w on stock, dt2w will ALWAYS work.
Click to expand...
Click to collapse
Thank you! I understood