Hello all,
First of all, let me say that I have not used the previous ROM versions, just the latest one (053116)
I'm currently using the Aerom V3
At first, the finger print scanner seems to work perfectly (once you find the knack on how to properly add your fingerprint).
Then I start fiddling with the OS (Root, LSpeed, and Rom Toolbox) to change the processor settings (I prefer full clock + Userspace, less UI jitter) the scanner gets worse and worse with every day.
After a few days, it barely recognises the fingers (unless you deliberately place it on the scanner, while looking at it) and even worse - the phone thinks I'm scanning the finger when I'm not even touching it and locks me out. Other times it fails to register my finger at all (no vibrate, screen off), then, when I press the lock button it suddenly unlocks.
The main question is - is it a deep sleep problem? Is it an oversensitive scanner? Is it my finger residue? (I try to clean the scanner once in a while)
I also tried installing Xposed, which means I have to set the SELinux to Permissive (removing the sleep 60/70/80 line).
Anyway, I can't seem to find where the problems come from. It seems, when the phone is bone stock, the fingerprint scanner works OK most of the time.
Any help is apreciated! Thanks
I've also made a short video to display the problem.
Sorry about the mumbly voice - big room, crappy mic.
https://www.youtube.com/watch?v=2Y48-taDE88
empy16 said:
Hello all,
First of all, let me say that I have not used the previous ROM versions, just the latest one (053116)
I'm currently using the Aerom V3
At first, the finger print scanner seems to work perfectly (once you find the knack on how to properly add your fingerprint).
Then I start fiddling with the OS (Root, LSpeed, and Rom Toolbox) to change the processor settings (I prefer full clock + Userspace, less UI jitter) the scanner gets worse and worse with every day.
After a few days, it barely recognises the fingers (unless you deliberately place it on the scanner, while looking at it) and even worse - the phone thinks I'm scanning the finger when I'm not even touching it and locks me out. Other times it fails to register my finger at all (no vibrate, screen off), then, when I press the lock button it suddenly unlocks.
The main question is - is it a deep sleep problem? Is it an oversensitive scanner? Is it my finger residue? (I try to clean the scanner once in a while)
I also tried installing Xposed, which means I have to set the SELinux to Permissive (removing the sleep 60/70/80 line).
Anyway, I can't seem to find where the problems come from. It seems, when the phone is bone stock, the fingerprint scanner works OK most of the time.
Any help is apreciated! Thanks
Click to expand...
Click to collapse
I've this error too, mainly the part of "the phone thinks I'm scanning the finger when I'm not even touching it and locks me out."
This is so annoying that i disable the FP, and this was one of the motives that i bought this phone :/
As you, this start after I root my phone with TWRP 3.0.2.1, but I just add the multiple window in the build.prop, I'm thinking on remove the root and see if this error stops.
gullatorre said:
I've this error too, mainly the part of "the phone thinks I'm scanning the finger when I'm not even touching it and locks me out."
This is so annoying that i disable the FP, and this was one of the motives that i bought this phone :/
As you, this start after I root my phone with TWRP 3.0.2.1, but I just add the multiple window in the build.prop, I'm thinking on remove the root and see if this error stops.
Click to expand...
Click to collapse
I've recently dirty-flashed Aerom on top. Didn't lose any settings, but the fingerprint scanner has improved greatly.
Also, Lux Lite was definitely interfering with the scanner and wake-scan. So I got rid of that.
empy16 said:
I've recently dirty-flashed Aerom on top. Didn't lose any settings, but the fingerprint scanner has improved greatly.
Also, Lux Lite was definitely interfering with the scanner and wake-scan. So I got rid of that.
Click to expand...
Click to collapse
I dirty-flash the Eragon v2.8, and the FP already increased, and it's rooted. So I think the problem is related with the stock ROM
FP sensor on the unrooted Aerom V5
gullatorre said:
I've this error too, mainly the part of "the phone thinks I'm scanning the finger when I'm not even touching it and locks me out."
This is so annoying that i disable the FP, and this was one of the motives that i bought this phone :/
As you, this start after I root my phone with TWRP 3.0.2.1, but I just add the multiple window in the build.prop, I'm thinking on remove the root and see if this error stops.
Click to expand...
Click to collapse
I have Aerom V5 on my phone, I am not rooted and I have the same problem. For now I have disabled the FP sensor and my battery life increased by 5 hours! I will try Eragon Mod as I prefer my phone rooted and xposed installed. I hope the new ROM won't have this FP issue.
I had several ROMs tested and conclusion is: Activated FP sensor takes about 1,5-2,5% battery per h (normally 0,2-0,5% in a good ROM without FP) in newer ROMs (Kernel > 31.05). For older Kernels it is even worse.
Unfortunately this takes us to the point that using the FP sensor will drain about 20-25% battery over night and nearly 60% in 24h :/ (to be fair: this seems to be a common problem with other devices having an always-on FP too, or to compare: even a Samsung S7 Edge needs two steps to unlock via FP) as i am a fan of using the FP sensor this really is sth. i struggle with. Best way would be to have option to disable "always-on" feature for FP-sensor, so it can be used "old" way: hit button to wake and then unlock via FP. At least it would be also sth. that i would appreciate to have quick widget to enable / disable FP or have it disabled with airplane mode to avoid the battery drain overnight.
Let me know your thoughts...
Regards A
Arangato said:
I had several ROMs tested and conclusion is: Activated FP sensor takes about 1,5-2,5% battery per h (normally 0,2-0,5% in a good ROM without FP) in newer ROMs (Kernel > 31.05). For older Kernels it is even worse.
Unfortunately this takes us to the point that using the FP sensor will drain about 20-25% battery over night and nearly 60% in 24h :/ (to be fair: this seems to be a common problem with other devices having an always-on FP too, or to compare: even a Samsung S7 Edge needs two steps to unlock via FP) as i am a fan of using the FP sensor this really is sth. i struggle with. Best way would be to have option to disable "always-on" feature for FP-sensor, so it can be used "old" way: hit button to wake and then unlock via FP. At least it would be also sth. that i would appreciate to have quick widget to enable / disable FP or have it disabled with airplane mode to avoid the battery drain overnight.
Let me know your thoughts...
Regards A
Click to expand...
Click to collapse
Everything would be better than disabling the FP completely. The FP scanner was one of the reasons i purchased this phone in first place....
I hope that the newly released kernel can be modified by ROM developers so that the FP scanner is usable.
Kooperativ said:
Everything would be better than disabling the FP completely. The FP scanner was one of the reasons i purchased this phone in first place....
I hope that the newly released kernel can be modified by ROM developers so that the FP scanner is usable.
Click to expand...
Click to collapse
I totally agree to that and same for me... if this sensor is there, i would really like to use it. In special as it is really good working (besides battery drain). I now ordered another (cheap) always-on FP sensor phone from redmi to compare the behaviour. For me a phone that is completely not used should not have battery drain >0,5% per hour.
I am also looking forward if the kernel source release will help for that issue... but if its hardware related i see no chance at all
Arangato said:
I totally agree to that and same for me... if this sensor is there, i would really like to use it. In special as it is really good working (besides battery drain). I now ordered another (cheap) always-on FP sensor phone from redmi to compare the behaviour. For me a phone that is completely not used should not have battery drain >0,5% per hour.
I am also looking forward if the kernel source release will help for that issue... but if its hardware related i see no chance at all
Click to expand...
Click to collapse
Please share your experiences as soon as compared the two phones. I'm curious about it.
So I have flashed my phone with Eragon V3 a few days ago and I have to say I am really happy
Fingerprint reader works very good now (no scans if no finger is on the sensor and very good scan-unlock ratio)
Batterylife is even better as in Aerom V5 (10 hours over night just 4% battery needed with wifi enabled)
with regular use I get one and a half days (music, web browsing, streaming, fp enabled)
Overall performance is very smooth
Xposed and root work very well
Related
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I already use this while my phone is on the desk. Way quicker to double tap screen and input key then grab phone and pick it up
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Jbluna said:
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Click to expand...
Click to collapse
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Do we need root for this to work?
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
DT2W is an AWESOME feature - even if it was disabled by Google after careful thought. Yes, the fingerprint scanner is quick and very convenient. However, because it bypasses the lock screen it also bypasses lock screen notifications. Sometimes I just want to read a quick text/push notification without picking up my phone or locating the power button. A quick double tap on the screen is a lot better than picking up the phone, using my fingerprint to unlock, and then swiping down the notification shade to read my updates.
deeproot said:
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
Click to expand...
Click to collapse
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
hutzdani said:
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
Click to expand...
Click to collapse
Agree to disagree. Double tapping for a quick check of the time or a notification is a handy feature. Not every notification requires you to act on it. A lot of times (Gmail Spam) I will DT2W and then swipe to dismiss the notification. That does not require using a pin and or fingerprint.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
Your argument is pointless, just because google turned it off doesn't mean it doesn't serve a purpose. Example, google heavily pushed ambient display over LED notifications and we all know LED notifications work ten times better....
Yep, my phone sits most of the day next to me in a trusted space and it is mucho nice to be able to double tap in and check messsages, time, etc. without having to specifically hit the power button to light the phone up. Further I have owned a phone where the power button eventually died and DT2W removes the majority of cycles on the power button. It can be done when the phone is on either side. It can be done while the phone is in a dock and more without taking your eyes off the road if docked in the car. Just because someone in particular doesn't use it doesn't mean it isn't a useful feature.
I think the reason DT2W was disabled is because someone on the android team secretly is taking money on the sly from Apple in exchange for removing useful and nice features from android. Anyone who says anything else clearly needs more tequila in their life.
i couldn't get this to work. anyone else successful?
I'd like to have this enabled on mine when it gets here Monday. Why not? When it's on table I can just tap to check it. More is more
Sent from my XT1096 using Tapatalk
double tap to LOCK?
Is it possible to modify your code so double (or maybe triple?) trap would lock the device? Thanks!
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
.
There is no need for this anymore, by installing a custom Kernel you can get this highly needed feature.
im currently running ElementalX Kernel which enables DT2W.
http://elementalx.org/devices/nexus-6p/
Working like a champ. I hope Francisco Franko kernel gets realeased soon.
Yeah, this is redundant now.
Sent from my Nexus 6P using Tapatalk
Excellent, that's what I was hoping would happen!
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
It is made difficult by the finger print scanner being on the back of the device. If it was on the front the functionality would be unnecessary. I like the scanner on the back for in the hand use but it is a limiting factor during use on a table/flat surface.
byproxy said:
i couldn't get this to work. anyone else successful?
Click to expand...
Click to collapse
1) You must be rooted
2) type
Code:
SU
into terminal
3) type the code
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
My last phone before this one is the Droid Mini. So far the Z5C is infinitely better in everything (but my expectations/standards are pretty low...) except that the Active Display feature from Motorola was awesome. From a bit of Googling, there are some other apps that copy this functionality to various degrees, but maybe some of you can give more specific insight than the articles?
1.) First of all, I'm confused. This article below states that Motorola released the app on Google Play Store for the general Android population... but it doesn't come up when I search it on my Z5C. What the hell?
http://gadgetstouse.com/featured/to...lay-notifications-alerts-android-device/19901
2.) If the Moto app is not available, any opinions on the alternatives? From reading a few articles, sounds like Dynamic Notifications is my best bet. Thoughts?
I tried xposed module, but it used proximity sensor, so it is not the same thing. I also miss that feature a lot from my nexus 5x, double tap to wake is kind of replacement when phone is laying on the table. When you take it out from a pocket, pressing the button isn't such a big deal. I couldn't find any reasonable replacement so I learnt to live without it
I really don't understand why other manufacturers don't copy-cat this feature. It was without question the greatest feature of my old phone.
I tried out Dynamic Notifications, but it's weird. First, it didn't play nice with the existing lock-screen and login structure. When I had a notification, pressing the power button no longer took me to the lock screen -- instead it just turned off and locked the screen. It's as if Dynamic Notifications became a second lock screen, and the power button toggled it on/off, and I had to tap the home key to get to the actual lock screen. On top of that, after getting to the actual lock screen it seemed to somehow screw up the fingerprint login because I kept getting prompted to use my other login method (PIN in my case). Most weird of all, it had some crazy bug when I used Uber. I was trying to check where the Uber car was on the map, and it threw me to the Dynamic Notifications screen, with the Uber notification showing. I logged in again, pulled up Uber again, checked the location of the Uber on the map, and it instantly did it again! And again... So screwed up.
TL;DR: Do not use this app, at least not on this phone. It's buggy and/or just makes you jump through extra hoops when logging in.
Yeah I also have double tap enabled. It's okay I guess.
Nexus 5x had a dedicated hardware sensors for that matter, I guess that may be the problem. Anyway I agree with you that every manufacturer should implement it.
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
try use ambient display is an xposed module
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
So I finally got around to trying out AcDisplay. That video that is on the app download page shows how you can wake up the phone using proximity sensors, when pulling it out of your pocket or even waving your hand over it... But none of this works at all. Not even a little bit. Does that mean that the Z5C does not have any proximity sensors built into it?
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Sent from my HTC 10 using Tapatalk
BillTheCat said:
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Click to expand...
Click to collapse
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Click to expand...
Click to collapse
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Davey126 said:
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Click to expand...
Click to collapse
Thanks for that info. Very interesting site, but way above my pay grade. I guess by "extended period" that scenario would be a store demo unit that's constantly powered, or a home scenario of similar sort.
Here's what I took away from a brief overview, if anyone else is looking on:
(Sourced from 'How to Prolong Lithium Based Batteries' from Battery University)
From: Battery University:(emphasis mine)
Similar to a mechanical device that wears out faster with heavy use, the depth of discharge (DoD) determines the cycle count of the battery. The smaller the discharge (low DoD), the longer the battery will last. If at all possible, avoid full discharges and charge the battery more often between uses. Partial discharge on Li-ion is fine. There is no memory and the battery does not need periodic full discharge cycles to prolong life.
Environmental conditions, not cycling alone, govern the longevity of lithium-ion batteries. The worst situation is keeping a fully charged battery at elevated temperatures. [I'm reading this as a warning for those of us with quick charging cables]
The question is asked, “Should I disconnect my laptop from the power grid when not in use?” Under normal circumstances this should not be necessary because charging stops when the Li-ion battery is full. A topping charge is only applied when the battery voltage drops to a certain level. Most users do not remove the AC power, and this practice is safe.
Click to expand...
Click to collapse
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Click to expand...
Click to collapse
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'. However, that one is important on MM as it prevents your device from waking and/or staying awake when in motion. Still, might be worth disabling to see if it makes a difference.
Rebooting after app updates is generally unnecessary unless recommended by the developer.
Additional thoughts:
- verify working mode is Root + Boost (Xposed)
- keep the list of apps to explicitly Greenify short (demonstrated bad actors); implicit doze will take care of the rest
While my preference leans towards Greenify (ease of use; flexibility; long term track record; community support) there are several other fine apps with similar functionality. Force Doze pops to the top of the list. Occationally a user will report issues with one while the other works fine. Another option to consider.
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
If you have greenified any system apps, please reconsider. One of them may be the culprit.
If nothing else works, ungreenify everything and start from scratch. Greenify one app at a time, observing the behavior for some time before greenifying the next. You may find the culprit. Laborious, but effective.
Davey126 said:
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'...
Click to expand...
Click to collapse
tnsmani said:
If you have greenified any system apps, please reconsider. One of them may be the culprit...
Click to expand...
Click to collapse
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
BillTheCat said:
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
Click to expand...
Click to collapse
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
tnsmani said:
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
Click to expand...
Click to collapse
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
No appwise recommendations can be made since the device, ROM, kernel, apps etc vary vastly not to speak of the the specific usage pattern of the individual.
What is recommended though is to greenify those apps which you don't use often but which keep running. Do not greenify apps which you often use.
As for system apps, be careful, but the same principle applies. Don't greenify something like PlayServices because its running is essential and it will continuously try to wake up draining battery.
Install BBS and monitor which apps drain battery and then greenify only those which drain but will not cause issues if greenified. Always greenify one app at a time to see the effects.
In general, greenify as less apps as possible.
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
hjbuzzi said:
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
Click to expand...
Click to collapse
I experienced this same issue on an older XT1030 which is the mini varient of a 2nd gen Moto X. Spent quite a bit of time trying to diagnose the issue (like you) and had devised various work-arounds that were never quite satiafsctory. Also rocking Greenify w/Xposed but ultimately determined that was not a direct factor with the proximity sensor glitch.
What fixed it (for me) was Gravity Screen which you can find in the Play Store. Takes a bit to get understand how to configure but very nice once everything is set up. One downside is you will probably want to disable Moto's active screen function - at least during initial configuration. Good luck.
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
tnsmani said:
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
Click to expand...
Click to collapse
Ah. So I'm not hallucinating after all...
Sent from my HTC 10 using Tapatalk
Well guys, it looks like I'm going to have to abandon Greenify. I just can't seem to find any combination of settings that won't interfere with the proximity sensor. Unfortunate, really, because it's a great app and I even bought the donation package, but it's just making my life miserable.
Anyway suggests for alternatives would be appreciated. I have one mention for 'force doze'. Anything else?
Sent from my HTC 10 using Tapatalk
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
hjbuzzi said:
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
Click to expand...
Click to collapse
Aggressive doze is neither needed nor beneficial on most configs. However, it can result in erratic app/device behavior. Suggest disabling and observe drain over several charge/discharge cycles. If only looking at at sleep performance be sure to include 1-2 min after waking as the device plays 'catch-up'. If there are no overall benefits to aggressive doze why introduce the potential for side-effects?
I'm used to having my Android phones use apps like KinScreen or Gravity Screen to keep my screen on by motion. On my new Mate 10 (ALP-L29 8.0.0.119 (C636) I'm finding that no matter what I do, the phone's setting for display on time always control, even though I've excepted out both apps from battery optimization and from automatic control of their launch (manually set to run in the background). Anyone experience the same issue or have any thoughts? I don't know if this is an Oreo problem or a Miui one. Thx.
I am having the same issues, no matter what, with persistent notification active, the screen does not stay awake with kinscreen. Installed Wakey, seems to be working at least sometimes... Should be based on your eyes watching the screen...
According to TecTiq, the maker of KinScreen, it's a Miui problem. I'm not the only one to report it. Oh well....
One other possibility is to set your default screen timeout to something long, and then install Proximity Service, which seems to work well on the Mate 10 and turns on and off your screen by covering the proximity sensor. Creates a permanent notification, but installing AutoNotification cures that (as well as the other running notifications, like background Android processes, that you don't want).
EDIT: Nope, belay that! Once the phone sleeps, Proximity Service is still killed (even if excepted from Launch and Battery Optimization). Back to the drawing board....
So here's a ROM that i would recommend even tho it's in beta Corvus OS it's android 12 and everything works even the Camera but sadly not the greatness of Sony's Camera app...i personally haven't tried it with the Custom Kernel Kirisakura just yet but i will and report back on here if they place nice together...Magisk also works great with this ROM you just have to be careful what you flash...
Hopefully our device will be fully supported soon.
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Ainz_Ooal_Gown said:
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Click to expand...
Click to collapse
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
UsernameNotRecognized said:
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
Click to expand...
Click to collapse
True that...but hey it's there Incase people get bored lol
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Alright some more shenanigans and needing to do a clean install further I do know some more things now.
1. is still broken, I'll try flashing a different kernel perhaps.
2. It's actually not so bad. It will remember and auto apply on reboot after a couple seconds. Gesture and notification bar may be slightly borked, but that's fixed fast by reloading system UI and switching between gesture and button navigation. The thing about recents has been resolved by switching to a different launcher with it's own quickswitch (lawnchair).
3. Acca works fine.
4/5/6 Nothing.
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
UsernameNotRecognized said:
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
Click to expand...
Click to collapse
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
thatguy222 said:
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
Click to expand...
Click to collapse
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
UsernameNotRecognized said:
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
Click to expand...
Click to collapse
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
kevinmcmurtrie said:
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
Click to expand...
Click to collapse
A what now? I do recall the proximity sensor not working really well with dt2w but at least it worked and I didn't notice some significant battery drain.
I did see some things about dt2w being disabled because the touch interface is powered when the screen is powered and this can't be decoupled. I'm not sure if this applies to this phone though.
Regardless, it shouldn't really matter as the X1 III is an OLED screen anyways. So as long as it's full black it should be fine(?)
I'm not asking for the perfect solution and if battery drain slightly increases that's a worthwhile investment to me. At least provide the option. Don't decide what I want because it has potential side-effects (just warn or something lol).
Actually I'm going out on a limb and stating that dt2w should be enabled by default if the device's screen is an OLED screen. Overlay and device specific things be damned.