Related
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Strange bug indeed and i have no idea why. The vibration on boot is always there to tell that bootloader boots. Its easier to troubleshoot a black phone that way, according to the service manual.
Sent through time and space from my s3mini/CM11
Jucarez said:
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Click to expand...
Click to collapse
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Meticulus said:
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Click to expand...
Click to collapse
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
i have the i8190 and have the same problems
So I'm using Carbon and Slimkat, works perfectly fine
Jucarez said:
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Click to expand...
Click to collapse
Did you try it ?
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Hi guys,
I tried it. It's working perfectly. Hallelujah!
Now I'm discovering the Xposed to do a lot of other things (autohide the navbar, disable the "3-dot" button on apps, etc)
Thank you very much!
down
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Click to expand...
Click to collapse
LMH1998 said:
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Click to expand...
Click to collapse
Jucarez said:
I tried it. It's working perfectly. Hallelujah!
Click to expand...
Click to collapse
Unfortunately, the workaround "patch" is not available anymore :crying:
would it be possible to upload it again anywhere, maybe here?
or is there another possibility to fix that problem yet?
Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected. Seems like the double tap is not always detected right away and I have to do it several times in order to wake the device.
Some times it will work at first try and some others it won't work at all.
Is there any definitive fix for this behaviour ?
Aanze said:
Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected. Seems like the double tap is not always detected right away and I have to do it several times in order to wake the device.
Some times it will work at first try and some others it won't work at all.
Is there any definitive fix for this behaviour ?
Click to expand...
Click to collapse
Known problem with tap to wake. I use swipe to wake and it works fine.
Thanks for the hint, I'm afraid swep to wake will wake the device in my pocket more easily
But I'll give a shot anyway !
Aanze said:
Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected.
Click to expand...
Click to collapse
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58
NLBeev said:
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58
Click to expand...
Click to collapse
If read the full thread it is still hit and miss and that file may not even be the same .so file for 5.1.1. That zip was made in December for 5.0.2.
prdog1 said:
If read the full thread it is still hit and miss and that file may not even be the same .so file for 5.1.1. That zip was made in December for 5.0.2.
Click to expand...
Click to collapse
I had the same problem and downloaded the attachted zip file shamu_doubletap2wake-s.zip.
After flashing this zip, dt2w works with stock 5.1.1. on my N6 (LMY47Z)
Edit:
and franco's kernel r30
NLBeev said:
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58
Click to expand...
Click to collapse
This is the cause of the issue and I suspect why google didn't release it. Kernel implementation is much better but actually sweep to wake is much safer in the pocket than double tap.
danarama said:
This is the cause of the issue and I suspect why google didn't release it. Kernel implementation is much better but actually sweep to wake is much safer in the pocket than double tap.
Click to expand...
Click to collapse
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.
NLBeev said:
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.
Click to expand...
Click to collapse
I use stock rom but custom kernel. Have options for both double tap and sweep to wake.
NLBeev said:
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.
Click to expand...
Click to collapse
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it
danarama said:
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it
Click to expand...
Click to collapse
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.
simms22 said:
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.
Click to expand...
Click to collapse
Yeah between that and ambient display, pocket wake is a huge problem. But for double tapping when you want to wake it up is not as reliable. 50% for some..or 3rd tap not 2nd.
danarama said:
Yeah between that and ambient display, pocket wake is a huge problem. But for double tapping when you want to wake it up is not as reliable. 50% for some..or 3rd tap not 2nd.
Click to expand...
Click to collapse
id say it was about 90-95% reliable here. it might even be a more location where you tap issue (maybe?)
danarama said:
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it
Click to expand...
Click to collapse
I've seen several posts about dt2w, and there are issues and solutions, and indeed not always successful.
My dt2w actions were as follows.
I started using an app untill I flashed a custom-kernel. Franco's kernel.
In the kernel settings there is an option to enable dt2w. But enabling had no effect.
Therefore I decided to flash the mentioned power.shamu.so.
Now it works for more than a week.
When there are issues I will post it here.
Works on stock with LeanKernel. Has option for stock dt2w, haptic dt2w, sw2w or both haptic dt2w and sw2w at same time.
simms22 said:
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.
Click to expand...
Click to collapse
This is understandable because the screen is touched when you put the N6 in the back pocket. But you have an option to switch it off.
It is different with the magnet sensor.
I was using a belt case (vertical) with a magnetic closure. Every move activates the sensor. Screen is turned on/off frequently.
Solution: another belt case,
EDIT
. . . I hope that in an new Android it will be possible to switch this sensor permanently off.
Because my magnetic car mount is not usable.
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?
Hello, I'm having issues with double tap to wake screen on custom ROMs.
I tried different ROMs(rr pie, dotos extended..) and sometimes double tap won't work, this happens randomly sometimes it's working sometimes don't. I tried with custom kernel available in xda and still the same issue occurs .
Anyone facing the same problem or is it just me, is there any way to solve this?
Edit: just perform a full wipe (system,data, cache...) and a fresh installation and now double tap don't work at all. Am I missing something ?
Solved!!!! Miui camera port was the culprit as soon as I uninstalled it dt2w worked again
I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
el4nimal said:
I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
Click to expand...
Click to collapse
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
xxBrun0xx said:
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
Click to expand...
Click to collapse
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
el4nimal said:
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
Click to expand...
Click to collapse
This also happened to me when I converted to WW ROM, and to many others as well. It affected my gaming experience so much so I converted back to CN ROM. I will be using the CN ROM until this problem is fixed.
Guys can u tell me where to set the double tap to wake the phone? Thanks
Found it. Dang all this time I didn't know this exist
Nb I tried using it and my phone is working great and fast. I'm using ten cent version.
It has nothing to do with what I mentioned. I think I'll reset my phone or convert it to the CN Rom
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Enigmatic331 said:
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Click to expand...
Click to collapse
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
el4nimal said:
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
Click to expand...
Click to collapse
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Enigmatic331 said:
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Click to expand...
Click to collapse
Im not sure about going to Android 10, is it still a beta right? The issue disappeared for me the first days when I changed to CN rom, but it came back a couple of days later :/
To update - Am on Beta 6 - So far so good. The problem hasn't come back yet. Only catch is double tapping is a slight bit less sensitive than before.
Once the official Android 10 release is out, hopefully that would sort you out for good!