I've been using the Fascinate and this is a problem I've had this whole time. I'm not sure if it's a hardware or a software defect.
The pixels at the edge of the screen don't seem to pick up touch input, something which I can see when I use painting apps. There is a space at the edge that doesn't get painted over. Also, when using the Lense lockscreen in CM7, it's extremely difficult to actually unlock the screen, because, since the edges don't respond, the lockscreen doesn't slide all the way down, and thus doesn't unlock.
The edges do pick up input for very brief moments sometimes, but only rarely. Do you guys know what the problem is?
It was mentioned when this device first came out. X starts to register at 8px and stop at 472px. And Y starts at 15px and stops at 785px. Not sure if that's by design, but hasn't hindered any app/ui interactions in tw for me. But I do remember this topic.
*Edit* Original Thread. Also confirmed epic does it too. Seems to be a galaxy "feature" on all models. But you're the first to notice it in 7 months and I would gather if cm7 ever went beta that an xml could be edited for the lock to reduce the gesture rate.
good day.
It's one of those features that I loved as soon as I heard about it in the original Moto X. I thought "that's real, useful, innovation." But the implementation in the 6P is poop. I can't reliably get the thing to work at all. As in, it works with movement, but I can't tell you how to reliably set it off. At all.
One other thing I've noticed is the screen is fully woken up by (I think) any touch on the screen when Active Display is on. Which seems very wasteful.
I'm guessing this is purely software because the sensors in the 6P are more than up to the task. I would also think it would be nice to have a setting to simply use the power button to, in essence, half wake the screen the way Active Display does. Then tapping on the notification will perform as normal.
Sound off if these issues are limited to just me. I actually hope they are.
Seems to work pretty well for me, i wouldn't say 100% but most times i pick up the phone, or take it out of my pocket.. it lights up
Laying down flat, picking up the device shows info.
Laying down flat, a little twist shows info.
Picking it up seems more reliable, but the nudge left or right when flat needs to be a decent "nudge". Otherwise it would be switching on constantly, which would be a waste.
And waking when touching any part of the screen when adisplay is showing is normal behavior.
Maybe when development moves ahead we'll have more control over it's behavior. I can see devs having fun with this feature.
+1 for the OP. I've been using the phone about a full day now and I've seen the active display like maybe 3 times, never when it really made any sense. Bummer.
Owned my phone less than 24hrs, installed a screen protector before using the phone. Ambient display want really working. I took the glass screen protector off, ambient display has come back. I'm wondering if the sensor is that sensitive.
Soulfulgrey said:
It's one of those features that I loved as soon as I heard about it in the original Moto X. I thought "that's real, useful, innovation." But the implementation in the 6P is poop. I can't reliably get the thing to work at all. As in, it works with movement, but I can't tell you how to reliably set it off. At all.
One other thing I've noticed is the screen is fully woken up by (I think) any touch on the screen when Active Display is on. Which seems very wasteful.
I'm guessing this is purely software because the sensors in the 6P are more than up to the task. I would also think it would be nice to have a setting to simply use the power button to, in essence, half wake the screen the way Active Display does. Then tapping on the notification will perform as normal.
Sound off if these issues are limited to just me. I actually hope they are.
Click to expand...
Click to collapse
The touch layer and the actual display are 2 different pieces of hardware, you probably can't limit what portions of the touch layer are active, it's either on or off but that has nothing to do with what pixels are turned on. Hope that helps.
Just turned it on to test. Seems to light up when its supposed to. Turned it back off because I use android wear and don't need it.
My switching from Active Display (Moto X 2013) to Ambient Display (Nexus 6) was tough, but I got used to it. My 6p seems to not work as well or the same as my N6 did.
In the morning if I wake up before my alarm I would grab my N6 to activate the Ambient Display and see the clock, as well as my notifications (I get the weather in the morning) to see if there was anything urgent (text from a coworker, etc).
With my 6p when I pick it up, nothing seems to happen, or at least not as quickly as it did with my N6. N6 would show it on almost any movement, but the 6p requires it to be fully picked up all the way and almost vertical before it shows anything. Not sure if this is gyro or software related. If I pick it up from flat and rotate 90 degrees right (like it would be if it was sitting next to my bed), effectively making it vertical in landscape mode) nothing happens. If I hold it vertical in portrait, it shows me.
Just something to get used to, I guess.
Active display is rubbish on the 6P lol. That's coming from a user BTW, its just not reliable.
I agree with OP. I sat phone beside me and noticed it would light up when I got a new message. Then a few seconds after, without touching or moving it, it would light up again (no new anything happened), then it would light up again. Not sure what's waking it up, but quite annoying. Should absolutely be a software fix though.
johnhazelwood said:
I agree with OP. I sat phone beside me and noticed it would light up when I got a new message. Then a few seconds after, without touching or moving it, it would light up again (no new anything happened), then it would light up again. Not sure what's waking it up, but quite annoying. Should absolutely be a software fix though.
Click to expand...
Click to collapse
This is one thing that is reliable for me! Lol. When a notification comes through, it will activate once, then turn off, then activate again shortly after. I'm not sure if it's mean to do this or not, but at least it's reliable.
I should make it clear though that in my short time with the device, it is a definite top quality phone. The Active Display just seems to be, for me at least, a noticeable deviation from the very high bar set by the rest of the device. I did read other reviewers with issues, but then, how much faith can you put in a 48 hour review. I've had mine for almost a week and still feel like I'm just getting to know it.
sluflyer06 said:
The touch layer and the actual display are 2 different pieces of hardware, you probably can't limit what portions of the touch layer are active, it's either on or off but that has nothing to do with what pixels are turned on. Hope that helps.
Click to expand...
Click to collapse
True-ish. It is indeed possible to have a software solution that ignores certain touch events even though the hardware layer will consistently recognise touch events as long as the touch layer is active. If the Active Display becomes just another UI, then the notification icons/regions become touch targets and the rest of the screen can be written in software to not be touch targets and thus not respond to touch inputs.
I'm not sure what this method would look like in practice. So for example, when the Active Display has been activated, would there be a way to fully activate the screen by a touch method without touching a notification? Maybe a special region at the bottom of the screen? No idea. Just thinking out loud.
Coming from Active Display on the Droid Maxx, Ambient Display is very disappointing and actually leads to my emergency dialer engaging sometimes when the phone is in the pocket of looser pants. But it doesn't display when I would like it to, with just a nudge, like the Motorola implementation.
I've messed around with my dad's phone. He has the Moto X as well. I can literally just wave my hand in front of the screen and it comes on. I thought that was awesome. This phone does seem a bit inconvenient if I just want to quickly get the time or my notifications. Then again that's why I have a (smart)watch. Not sure where I'm going with this.
Good talk....
I've figured it out! Feeling quite pleased with myself.
Based on the responses of others, I tried using it slightly differently. Now, I figured out two instances which regularly and reliably activate the Active Display.
The first is when the phone is flat on a surface, if I pick it up to be perpendicular to the floor, either portrait or landscape seems fine, it will activate. I believe this actually works from almost any starting point as long as the end point is the phone being upright and vertical.
The second is with it again starting flat on the table. Holding it by the bottom of the phone, moving it semi-quickly across the table, only about 5 cm seems needed, and then stopping quickly. This is a strange one which I only found when I bumped it into something on the table. I have a case so was not bothered testing this repeatedly.
I know correct my first statement. The feature is not poop. Well, not total poop. There are other instances that will activate it but I don't know how to do them reproducibly. If that's a word.
Hope this helps someone.
RoyJ said:
I've messed around with my dad's phone. He has the Moto X as well. I can literally just wave my hand in front of the screen and it comes on. I thought that was awesome. This phone does seem a bit inconvenient if I just want to quickly get the time or my notifications. Then again that's why I have a (smart)watch. Not sure where I'm going with this.
Good talk....
Click to expand...
Click to collapse
Thats a pretty nifty idea, if its flat... give it a bit of " These aren't the droids you're looking for" to wake the screen.
Surely cant be that hard to do.........
..... i cant do it
My active display does nothing. Doesn't activate anything even shaking the phone.
Sent from my Nexus 6P using Tapatalk
Stretlow said:
Thats a pretty nifty idea, if its flat... give it a bit of " These aren't the droids you're looking for" to wake the screen.
Surely cant be that hard to do.........
..... i cant do it
Click to expand...
Click to collapse
The Moto X (2014 and after) does it as it has other sensors on the front, the 6P doesn't. However, the Moto X (2013) did it with Kitkat as it used the proximity sensor, which was less reliable but still effective, but this was removed in Lollipop. To be fair, ambient display doesn't work nearly as well as Moto's active display. I bet a dev could activate it via proximity sensor, should people want it enough.
Soulfulgrey said:
I've figured it out! Feeling quite pleased with myself.
Based on the responses of others, I tried using it slightly differently. Now, I figured out two instances which regularly and reliably activate the Active Display.
The first is when the phone is flat on a surface, if I pick it up to be perpendicular to the floor, either portrait or landscape seems fine, it will activate. I believe this actually works from almost any starting point as long as the end point is the phone being upright and vertical.
The second is with it again starting flat on the table. Holding it by the bottom of the phone, moving it semi-quickly across the table, only about 5 cm seems needed, and then stopping quickly. This is a strange one which I only found when I bumped it into something on the table. I have a case so was not bothered testing this repeatedly.
I know correct my first statement. The feature is not poop. Well, not total poop. There are other instances that will activate it but I don't know how to do them reproducibly. If that's a word.
Hope this helps someone.
Click to expand...
Click to collapse
When laying flat - give it a quick twist - about 45 degrees - and back again.
I see most don't agree with the implementation, but think about it. If it was more sensitive, it would be waking all the time. That's definitely less battery efficient.
Once you get used to it, it's not bad at all, and I can see devs adding more control over how it works - like a sensitivity setting.
Hint hint devs!
Phazmos said:
When laying flat - give it a quick twist - about 45 degrees - and back again.
I see most don't agree with the implementation, but think about it. If it was more sensitive, it would be waking all the time. That's definitely less battery efficient.
Once you get used to it, it's not bad at all, and I can see devs adding more control over how it works - like a sensitivity setting.
Hint hint devs!
Click to expand...
Click to collapse
Tbh, the more I use it, the more I understand why it has this implementation and you are right, there would probably be a battery burden to make it more sensitive. I just wish they could have advertised it. Maybe a deep dive YouTube video or something.
Got a 6GB-RAM/64GB-flash rose X820 sent from China 6 months ago. Been very happy with it until some weeks ago.
Ghost touches did very occasionally happen several months ago, after the device had been running for weeks without rebooting.
Since I update my ROMs rather regularly, that didn't really happen all that often, thought it was some kind of software glitch.
Now things have deteriorated to the point where the phone becomes unusable: After a reboot, things work for a minute or so, and then it goes crazy, reacting to phantom button presses. Since my default home button double tap actions is "previous app" and the default menu button action is "app chooser" you can imagine what's going on on the screen: Can't watch without getting dizzy.
After a while the phone will settle down with the buttons dead: They won't react or light up on touch, just light with screen or hardware button action.
Happens with all kinds of ROMs btw., the latest Chinese stock ROMs, Mokee Marshmallow and the various Nougat ROMs I tried over the last weeks.
By now I'm pretty sure it's a hardware issue with my phone, especially since I have only ever encountered one other mention of "ghost touch" in the forum.
It may be a sad case of failing hardware, "a bad soldering point" sort of thing, pretty much impossible to fix with reasonable effort for a phone at this price.
But I know Android natively supports using on-screen software buttons and I've even had ROMs which allowed you to choose between the hardware buttons and on-screen software buttons: Yet somehow, in the current crop of Nougats I haven't really come across this option any more.
So I have two questions:
1. Do others experience similar issues with failing soft buttons? How prevalent is the issue?
2. Does anyone know if one of the CM derivatives like Remix/Mokee etc. Nougats enable foregoing the soft buttons for on-screen ones?
(3.) Would a kind developer put the option back into his ROM or tell me where to find it, so I can put it there myself?
Clearly I prefer using the "hardware" buttons, but even more clearly I prefer using (typically auto-hideable) on-screen buttons to ditching the phone, which is otherwise still going very strong and much faster than its Samsung Note 3 predecessor, which I have to fall back on until the ghost touch madness is resolved via "soft-button amputation".
BTW: I noticed that my Max was rather more bendable than I would have believed a "solid metal case" phone to be (always had plastic Samsungs before and was very happy with their practical advantages of swappable batteries, light weight and drop resilience).
It typically got to the point where it wouldn't lie flat on its face, but toggle on two corners. I would then very carefully bend it back until would rest flat again.
Can't say I saw any direct relationship between the bends and the ghost touches, during "ghost attacks" careful bending either way also doesn't change the occurrence or rapidity of the ghost touches, either.
I am also using a hardenned glass cover on the screen, which is ever so slightly lifting in one corner and could have tiny specks of dust enter between the cover screen and the original front. Since I don't have an equivalent quality replacement and Le Max doesn't have the best quality screen glass, I'm hesitating to remove it, just to see if it makes a difference for the soft buttons: I'd find it hard to believe it could make a real difference, but I wouldn't mind to be corrected if wrong.
As probably everyone has noticed, phones with curved screens (and also some flat screens) have had this super annoying "grip zone" as the manufacturers call it, enabled by default.
Ive been battling out with different manufacturers to modify this stupid functionality off without success, which is the exact reason i came here asking for help if someone has any idea or possibility to fix this on stock/rooted phones.
If you dont know what i mean by grip zones, google samsung edge touch (cant post links yet).
Im using samsung s9+ at the time (have tried: op6, 7, 7pro. Huawei p30 pro. sgs8, 9+. all of these have this grip zone enabled by default).
Ive tried using the samsungs own edge touch app (samsung store download) to disable the grip zones completely to no avail as for some mysterious reasons even the setting stays on in the app, it still reverts back to the default zone layout after random time of usage and makes it annoying to reset the app X amount of times to get it working again.
So please, anybody. If you know any possible way how to completely disable this functionality on my sgs9+, it would really help out alot!
Im sick of making million typos because the screen wont register presses on the sides if i type fast or having to zoom in on websites to click a box on the very edge on the screen or etcetcetc...