i recently made the move from a nexus5 to the OPO. i flashed @Sultanxda's CM12.1 w/ CAF kernel (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-12-1-t3120259) and all has been well for the most part. i still can't EXACTLY reproduce it but while the screen is off, grabbing the phone a certain way, touching a screen the certain way, or POSSIBLY (least likely, i think) pressing a volume and/or power button while lifting the phone up - starts google music playing, as if i'd just tapped the play button.
i can't figure this out for the LIFE of me and hope someone can shed some light on this. anyone experience anything similar, or know if there's an option i have enabled (or disabled) that'd result in this behavior?
TIA!
leaving this here in case someone else has a similar "problem" - this is my first time on a CM12.1 ROM and i had no idea that 1. there are gestures (which work while screen is off) and 2. that they're enabled by default. they affect/control: camera, music, and flashlight. turning them off fixed my problem(s).
ce_rob said:
i recently made the move from a nexus5 to the OPO. i flashed @Sultanxda's CM12.1 w/ CAF kernel (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-12-1-t3120259) and all has been well for the most part. i still can't EXACTLY reproduce it but while the screen is off, grabbing the phone a certain way, touching a screen the certain way, or POSSIBLY (least likely, i think) pressing a volume and/or power button while lifting the phone up - starts google music playing, as if i'd just tapped the play button.
i can't figure this out for the LIFE of me and hope someone can shed some light on this. anyone experience anything similar, or know if there's an option i have enabled (or disabled) that'd result in this behavior?
TIA!
Click to expand...
Click to collapse
Probably the gestires are getting triggered. Switch off the gestures in Settings->Gestures.
Related
Hey guys,
This forum has been wonderful for me so I thought I would pass along my own personal experience with a couple of items.
First 'the Clip' case - great - I love mine. For those that have had concerns about the main home/back/menu/search buttons not being lighted, the clip is perfect for helping to find these keys. If you insert your tablet camera up (not upside down to uncover the usb port), the right hand clip is the perfect tactile way to find menu (just above) and back (just below). A good way to navigate these buttons in darker settings.
Second - the static/hissing/white noise problem people have experienced. I know several people have indicated it is a hardware problem and to replace your tablet, that was not an option for me as it did not start until after the 30 day return period. I have found, however, that if you set your screen to NEVER sleep and instead use the power buton to put the screen to sleep, it cuts down on the occurences significantly. Additionally, if it does happen (it has happened twice in the last week), it recovers for itself. You get the noise for ONLY the existing sound that is supposed to be playing and the next sound (whether it is a feedback sound, a notification, etc), it will have corrected itself. At least that's what my experience has been.
To all the developers out there (and especially roebeet) - thanks for everything, I love this tablet due to your hard work. I am running TnT lite 4.2.5 and am very happy with it.
how do you get the screen to never sleep?
Go to settings, display, screen timeout and set to never.
dwebww said:
Second - the static/hissing/white noise problem people have experienced. I know several people have indicated it is a hardware problem and to replace your tablet, that was not an option for me as it did not start until after the 30 day return period. I have found, however, that if you set your screen to NEVER sleep and instead use the power buton to put the screen to sleep, it cuts down on the occurences significantly. Additionally, if it does happen (it has happened twice in the last week), it recovers for itself. You get the noise for ONLY the existing sound that is supposed to be playing and the next sound (whether it is a feedback sound, a notification, etc), it will have corrected itself. At least that's what my experience has been.
Click to expand...
Click to collapse
I understand you in regard of this XD i've been having this sound problem, but bought mine overseas (i'm from Chile) and my brother threw the boxing into the trash, so doubt that there is a cheap way to replace mine .
Do you prefer some ROM in particular? Now i'm toying with VEGAn 7, but i can't play more than 2 or 3 mp3 songs without getting sound off, i'll try your "fix" to see if the situation improves
webman418 said:
Go to settings, display, screen timeout and set to never.
Click to expand...
Click to collapse
hmm.. I guess VeganTAB 5.1.1 doesn't have that option.. bummer..
i had to change the tablet language to english to find that option for some reason
Hi!
My Sensation has been experiencing some weird behaviours.
Although the rotation is locked on the rom (I tried several, all same issue), it still rotates. The only way to stop this is through the launcher options and force vertical mode.
It wakes up during the night, out of the blue. Nothing running, no processes waking it up.
Sometimes I'm browsing stuff (like this morning, browsing the TB backup list), and it kept going back like I pressed "Back" button.
Now, I tried several roms since, all same behaviour (Sense, AOSP, CM, etc..).
Used an app to test the sensors, they all seem to be responding accordingly, although I don't exclude a sensor issue, for some reason it shows normal behaviour in everything else. The rotation works properly as in, turning the way it should, but if it's locked, why it keeps rotating?
Did anyone ever experienced anything like this? I searched on google / xda, there's some odd cases here and there and either they ended up being sensor files being corrupted or uncalibrated.
Anyone care to shed a light on this?
Thank's a lot
Update: New sympthom, on Sense 3.6, it seems like Dock Mode is being called randomly too. This makes me consider a sort of loose contact or alike :S
Anyone?
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.
Hello All.
Anybody else have the same issue like me?
I have around 4 seconds lag during wake-up phone with double-tap. But only when phone goes to sleep with camera application opened in front.
This is strange.
If camera app is opened in front and phone goes to sleep - long wake-up with double-tap.
With power button wake-up -> phone wake-up immediately.
If phone goes to sleep with any other application opened in front (home screen, any other app) -> double-tap wake up phone immediately.
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?[/QUOTE]
Just tried mine and seems to work fine on double tap
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
nedalnib said:
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
Click to expand...
Click to collapse
Now that I have watched the video,, mine acts the same.
That's a "normal" behavior, on android when the screen brightness needs to change this lag always appear. I develop an app to turn screen off by changing the brightness and timeout times, and happens this same lag in a various devices seems to be an android issue.
So what I did to "hde" the lag was to add a screen with some info like day, date and time.
But on your case there is no solution yet.
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
nedalnib said:
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
Click to expand...
Click to collapse
Because camera change the screen brightness, the problem is in changing screen brightness and not the action that you are performing.
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
nedalnib said:
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
Click to expand...
Click to collapse
That one I don't know for sure, but I think that can be due to the way the it turn the device.
Double tap is controlled by "lockscreen app/kernel", the power button and fingerprint it android native code and kernel, can be that but just htc knows!
Did you tried to ask then about that in twitter or via support emaill?
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
nedalnib said:
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
Click to expand...
Click to collapse
Hum, nice ideia.
Ok, let us know what they answer
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...