Since I have owned the N1 I have noticed that the screen will sometimes loose it calibration. Recently I have found though that when it starts to behave irregularly, if I turn off the display and use the slide to unlock mechanism built into the phone, the calibration is restored.
I was wondering if there was some type of calibration function to the unlocking feature of the N1, or if it is simply a placebo effect. If there is a calibration function, I wonder if there is a way to call it outside of the lock screen.
It's not a placebo, pretty much everyone has to do it once in a while.
my favorite is when I'm typing on the on screen keyboard and it's hitting keys WELL below where I'm actually typing.
I just consider it a glitch and assume it is being worked on. No biggee...
Related
I'm not sure if I'm describing this correctly in the title so let me try and elaborate -
I've used probably 10-15 different ROMs for my Nexus 10 and lately every single one I try, I have the same issue when I have the screen titled down horizontally towards me while reading in bed ( think holding it up while lying on my back, angled down at me so I can read ), where the screen blacks out/goes to sleep.
Then I have to tilt it back so it's vertical again and sometimes it puts me at the lock screen but more often I have to hit the power button to get the lock screen back, infuriatingly I then sometimes get stuck in a loop of hitting power to get to lock screen as it's going back to lock screen so then it kills the display again so then I have to hit power again etc etc. Once the screen is back and displaying everything is fine until some random amount of time ( between 5 seconds & 5 minutes ) when the screen just goes black again - presumably when I move/adjust my position or the angle of the screen.
Anyway - I believe this is version independent, I don't think it's the ROMs, it's like it's something built-in to the OS.
The only thing I can figure is it's either related to the accelerometer detecting that I'm tilting the tablet horizontally so the screen is facing down and thus it is killing the display, OR it's the light sensor detecting a darkening of the light since I would be angling the screen away from a direct light source and so it kills the screen thinking I'm placing it face down on a table.
Possibly related - I've also noticed since 4.2.2 ( maybe coincidence ) that I can't rotate my screen 180 degrees and be able to unlock the device. No matter what, if I flip that sucker around it instantly kills the display and locks the screen. I've got auto-rotate on, so I know that's not the issue, and if I hit the power button to get the lock screen up, then unlock it INSTANTLY locks again and kills the screen. It's like there's a setting now that says I CAN rotate if I want to but there's no point because I can't actually unlock the screen to do anything. Keep in mind this ONLY happens when flipping it 180 - if it do it 90 or 270 and have it vertical there is no issue, it is literally only when it is flipped 180 that this occurs.
Am I over thinking this or is there something really, really obvious I'm missing? I've gone over every setting I can think of and the only thing remotely screen related is the sleep timer but it doesn't matter how long I make it or if I even turn it off entirely - every time I get into bed to read I have to mash the power button to get the screen going again. It's minor in the grand scheme of things but it is incredibly frustrating when all I want to do is read before going to sleep, just stay open damn it !
I hate to shameless bump this but does anyone know what I'm talking about? If I tilt my N10 past a certain degree ( I want to say it's around 30 degrees or so ) the screen just goes to sleep, how do I stop this? I've used a ton of different ROMs so it seems to be something consistent and/or a fundamental "feature" of JellyBean and/or Android in general.
Astriaal said:
I hate to shameless bump this but does anyone know what I'm talking about? If I tilt my N10 past a certain degree ( I want to say it's around 30 degrees or so ) the screen just goes to sleep, how do I stop this? I've used a ton of different ROMs so it seems to be something consistent and/or a fundamental "feature" of JellyBean and/or Android in general.
Click to expand...
Click to collapse
If nothing else, I would say it rather "seems" to be a hardware issue, because I've never seen this behavior on my own device. That said, I can't say I've heard of many people talking about this either.
Rirere said:
If nothing else, I would say it rather "seems" to be a hardware issue, because I've never seen this behavior on my own device. That said, I can't say I've heard of many people talking about this either.
Click to expand...
Click to collapse
Thanks for replying! Good point - I've just assumed it wasn't something specific to MY N10 because I can't imagine why it would happen from a hardware perspective since it's never been damaged ( dropped, scuffed ) in any way. Unless I just got a bad egg with a faulty accelerometer or light sensor or something, which is also possible.
I suppose if no one else is experiencing this and it's isolated to me and is ROM independent than it must be hardware. Either that or when I'm laying in bed I generate large bursts of electromagnetic activity that cause it to think I've closed the "smart" cover. :cyclops:
Screen Timeout
I don't know if any of this matters, but I am just curious.
What is your Screen Timeout setting? Have you tried increasing this? Do you have it set to lock screen upon pressing the power button? Have you tried changing it? Do you use a pattern lock, pin code, other?
SmokinCharger said:
I don't know if any of this matters, but I am just curious.
What is your Screen Timeout setting? Have you tried increasing this? Do you have it set to lock screen upon pressing the power button? Have you tried changing it? Do you use a pattern lock, pin code, other?
Click to expand...
Click to collapse
My screen timeout is set to 10 minutes, though it doesn't seem to matter what I set it to - I just set it to 30 and the same thing happens after a second of tilting it.
I have screen lock via slide, but while I do lock/kill the screen via pressing the power button I just realized I've never actually set it to do this. I guess I thought it was a built-in feature - I've just gone through all the settings I have ( currently using FlamingMonkey AOSP ROM for reference ) and I don't see any option anywhere to enable/disable this feature. :S
Maybe there is an issue with my power button and when I tilt the tablet it jiggles it enough that it "presses" down and locks?
Use ultimate rotation control from store and force the lockscreen to landscape at all times.
Astriaal said:
My screen timeout is set to 10 minutes, though it doesn't seem to matter what I set it to - I just set it to 30 and the same thing ould be there for your ROM too. happens after a second of tilting it.
I have screen lock via slide, but while I do lock/kill the screen via pressing the power button I just realized I've never actually set it to do this. I guess I thought it was a built-in feature - I've just gone through all the settings I have ( currently using FlamingMonkey AOSP ROM for reference ) and I don't see any option anywhere to enable/disable this feature. :S
Maybe there is an issue with my power button and when I tilt the tablet it jiggles it enough that it "presses" down and locks?
Click to expand...
Click to collapse
I think that you are on the right track. The option to lock the screen on hitting the power button is under the Security settings for stock android. It should be there for your ROM too.
I constantly hit my power button when sitting it down or picking it up. That is why I disable the instant lock option.
Hey guys,
i noticed something strange on my tn7.
Sometimes (maybe 50% of the time) when i open the (original) slide cover to wake up the screen, the touch screen is very unresponsive.I can touch, but it notices only ~10% of what i am doing and is extremly laggin. when i then turn off the screen with the button and turn it on with the button again, everything is fine.
Also when doing this i have to wait for the screen to go off completly - if i wake it when the backlight is still on but the screen is black, the issue stays.
This never happens when i wake the tab with the button though, only with the slide cover. Thats what is kinda strange i think..
Anybody got an idea on how 2 fix this?
Running rooted Stock Kitkat.
Thanks
This is a problem that has existed since this tablet was released and persists still to this day. All you can do is cycle the screen off/on with the power button, unfortunately. Seeing as how this hasn't been solved in the last 10 months and Nvidia is showing signs that they're abandoning this tablet to focus on the Shield Tablet, it will probably never be fixed.
Screen lag
I have a similar issue on mine. I've had mine now about six months and it's very intermittent but at certain times, especially when the battery is low, the keys down the left side lock up and become unusable. I bought the tegra note 7 because of the stylus which I prefer to touching the screen with my index finger, but I don't much like the stylus itself which could have been made of better materials I think. I also find that sometimes it doesn't register clicks, then it will be perfectly ok for a little while. I had hoped with the tegra 4 and the much hyped stylus it would be very responsive but it's inconsistent. Anyone else recognise these flaws?
I also get this intermittently but only ever when waking it up with the cover, its never happened when turning on with the button. When it does happen a quick off and on with the button resolves the issue
I searched, and didn't find any other posts about this, but the search engine here seemed a bit flaky.
I installed SlimKat 4.4.4.build.8.0 on my Samsung Galaxy S3, um, last year I think it was. I had previously been using SlimBean, having dumped the original Samsung ROM fairly shortly after I bought it. Since then there has been weirdness that relates to the proximity sensor.
I used E-Robot to disable the screen when anything is close to the proximity sensor. So put it face down, screen off; put it in my shirt pocket face inwards, screen off; leave it on the desk face up so I can see the screen, screen on. Naturally - hold it to your ear on a phone call, screen off, though that's a basic function of the proximity sensor, it did that anyway. On the flip side, if it was blanked and you uncover the sensor, the screen would come back on, but it would be the Lightning Launcher lock screen that I prefer. I got used to Lightning Launcher from SlimBean.
After installing SlimKat, when covering the sensor, first the volume controls show for a few seconds, THEN the screen goes off. Coming out again, the Lightning Launcher lock screen would not show. This got a bit awkward before I figured it out. I usually put my phone in my shirt pocket screen inward, so that the sensor triggers the screen disable. But now, since the volume control is showing for a few seconds first, I discovered that my chest would brush against the screen, randomly adjusting one of the volumes as it went in my pocket. Since I usually have the volume turned all the way up, the only way was down. I missed a few phone calls that way before figuring out why my phone wasn't ringing.
So I have disabled that E-Robot thing now. BTW, there's no way to turn the SlimKat screen blanker off? I would have tried that first, but could only find how to set the timeout, not how to turn it off.
More recently, though this may be a new hardware problem, but it's a big coincidence ... now the proximity sensor refuses to work at all. It always thinks it's covered. This is a really big pain, since as mentioned above, the proximity sensor is designed to disable the screen when you hold it to your ear, only now it disables it the moment the phone call starts, AND refuses to enable it after the phone call is over. The sensor still thinks it's being held to your ear, the screen stubbornly refuses to switch on, no matter what buttons I press. Only way I can get out of that state is to pull the battery. This is not good. (On the other hand, this sort of thing is why I always get phones with swappable batteries, as a very experienced computer dude, I know that sometimes you just have to kill the power.) So anyone I call gets to hear my swearing as I rip the case open and pull the battery out, before I can end the phone call. Though pulling the battery naturally ends the call. lol
About the same time I noticed the proximity sensor no longer working, I noticed the up volume button also isn't working. That could have been broken for awhile, I rarely use either volume control. Part of the reason for doing this entire proximity sensor disabling the screen thing is so I could avoid wearing out the physical buttons. The S3 is old, but I like to keep my computer hardware running for a long time.
Sooooo, proximity sensor and volume controls interact in odd ways, then both fail. That's a pretty big coincidence. Though having just written that, I have come up with a new theory. Maybe some common part of the physical circuitry for the sensor and the button was going flaky, such that the sensor triggering sent noise through the up volume control, triggering the on screen volume controls before blanking. Still, a coincidence that it only happened after installing SlimKat. Also, wouldn't this trigger both volume controls and screen disable at the same time, rather than within a few seconds? No idea how Lightning Launcher fits into this new theory.
So I'm still not sure what's causing this, or how to fix it. Other than going back to SlimBean to see if that fixes anything. It doesn't look like I can go forward, 4.4.4 looks like the last SlimRom made for the S3. At least according to OTA.
Anyone got any ideas? "Buy a new phone" isn't a good answer for me right now, can't afford it.
onefang,
I have a S3 that I ran the Slimkat 4.4.4 build 9 on for a while (9 months). There is a known issue with the CM package (used in SlimKat) that causes the volume button not to work correctly. When you are on a call, the call volume can not be raised or lowered. There may be other issues. I am currently running the CyanogenModCM12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att rom and the performance is much better than Slimkat.
Hello everyone,
So, I'm having a bit of a strange problem with my Yotaphone 2...
I did a factory reset on it a while back, and everything went fine, except now, when the screen is locked, I can no longer unlock the e-ink screen by dragging up the lock icon on the bottom of the e-ink screen. I have to use the hardware power button, which is a little bit inconvenient at times. I've spent quite a while trying to locate what setting got effected to make it not function, but with no luck. Anybody have any idea where I can turn this function back on?
It happened to me too, I think it was something related with the Lollypop update, but could be some setting that has changed and that I cannot find. However, I found that if I double tap before tracing the finger motion, it usually works. That's why I didn't look further into the issue.
alienBaboso said:
It happened to me too, I think it was something related with the Lollypop update, but could be some setting that has changed and that I cannot find. However, I found that if I double tap before tracing the finger motion, it usually works. That's why I didn't look further into the issue.
Click to expand...
Click to collapse
No luck for me. I'm still on Kitkat anyway...
Looks like I might be stuck...
alienBaboso said:
It happened to me too, I think it was something related with the Lollypop update, but could be some setting that has changed and that I cannot find. However, I found that if I double tap before tracing the finger motion, it usually works. That's why I didn't look further into the issue.
Click to expand...
Click to collapse
Actually, scratch that... after your double tap suggestion, I started randomly tapping around managed just once to get it to unlock from a screen touch, but have not been able to replicate the movement so it happens again. What movement exactly do you use to get it to unlock?
Update:
Seems to be some kind of sensitivity issue. I can get it to unlock about once out of every 50 swipes. Less than ideal.
I leave the phone with the E-ink screen facing up (to prevent the gyroscope from switching sensitivity to the amoled display instead), then press twice the lock icon, and on the second time my finger touches the E-ink, I drag it up to the center of the phone. It took a bit of practice but now I can get it to work consistently. The double tap is because if the phone has been inactive for a while, it enters sleep mode, and it looks like that turns off the finger gesture recognition. Other possible explanations are that maybe you don't press the screen firmly enough, or maybe you placed some plastic sheet over the back display and that reduces sensitivity.
I noticed that the unlock gestures on the EPD work only when the phone recognizes that you've it in the hand or you're using it. So I take it and I unlock it effectively. Trying to unlock when it lays down and you haven't moved it for a while brings to your experience.
Thanks to both of you for the advice... unfortunately, neither seems to be doing the trick. Just a caution for any other people who are thinking of doing a factory reset - it seems to seriously impact sensitivity for the e-ink unlock, so be aware.
I never succeed to do slide up unlock even within 1st tutorial. Double tap unlock was the only workaround for me. Also activated glove sensitivity mode.
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Sounds like Doze.
I don't find anything related to Doze or "standby" about this screen.
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
David_26 said:
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Click to expand...
Click to collapse
thophan1975 said:
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
Click to expand...
Click to collapse
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
Sounds like there is an issue with the proximity sensor (not light sensor).
It's setup to turn the second screen off as well as disable knock on if the phone is in your pocket. Even during daylight hours if you put your finger within an inch of the sensor when the main screen is off, it should trigger it.
It seems your sensor may just be messed up.
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
There are a few apps on the play store you can try to fix it if you are rooted. You could also try a sensor app to see if the proximity sensor is showing feedback properly although you might need to be rooted for the apps to show the proximity sensor properly (not sure). My note 4 had a hardware test in the service menu not sure how to do it on V20 though.
Same Issue
Edit: Resolved the issue. Please read this post. There is a small rubber gasket-type thing that sits in the hole of the phone's frame where the proximity sensor is positioned. That rubber gasket was not included with my replacement screen. I pulled the rubber piece out of my original, broken screen, and installed it into my replacement screen. I am no longer having issues with the phone in the dark.
I am experiencing the same issue. I have a T-Mobile LG v20 (H918) and I cracked the screen last week. I ordered a replacement LCD assembly and installed it myself. Everything works fine during the day or in a well lit room, but at night, in a dark room, I experience all of the issues you are reporting. I am finding other posts online with our same issue, but as of yet, no resolution.
Even though the second screen is set to always be on, at night, in a dark room, it turns off almost immediately after locking the phone. It is almost as if the phone is in a "deep sleep" or something, because the following also occurs:
Knock On will not wake the phone
Fingerprint sensor will not wake the phone
Even connecting to the phone via AirDroid / AirMirror the phone doesn't wake
Need to press the power button multiple times to wake phone
Providing a light source immediately turns on second screen and resolves all issues