Related
I am either going nuts or this is a common isue:
Normally when you tap "lock" on home screen the brightness diminishes and the phone is locked. To unlock, you have to tap "unlock" on the lower left side of the screen, hen you get a message telling you to tap again unlock in the middle of the screen and its unlocked.
Well, my Polaris only does this sequence sometimes. Especially if I let it go in standby for a couple minutes, as soon as I press any key I get another story:
In lower left corner of screen I have the word" cancel". Tapping it doesn't give me another "unlock" button on screen and the phone remains locked. I have to put it in standby from the power button and then try again to get the normal unlock behaviour.
Anyone else experiences this?
Nobody? So everybody's unlock feature works like it should?
Then I think it's reset time for my Polaris....
I personally don't use, the device lock feature... Just the standby, whith the HW buttons off... and it works just fine for me
I have noticed that when you press the central button in the TC, what you describe is what exactly happens. But this happens to me only when I do that. If a tap the screen without touching the button, I have the normal behaviour.
Yes, exactly.
@gnick: if I use the standby with HW keys lock it works ok for me also.
The issue is only with the HTC Home lock feature and the central key
dtancu said:
I am either going nuts or this is a common isue:
Normally when you tap "lock" on home screen the brightness diminishes and the phone is locked. To unlock, you have to tap "unlock" on the lower left side of the screen, hen you get a message telling you to tap again unlock in the middle of the screen and its unlocked.
Well, my Polaris only does this sequence sometimes. Especially if I let it go in standby for a couple minutes, as soon as I press any key I get another story:
In lower left corner of screen I have the word" cancel". Tapping it doesn't give me another "unlock" button on screen and the phone remains locked. I have to put it in standby from the power button and then try again to get the normal unlock behaviour.
Anyone else experiences this?
Click to expand...
Click to collapse
Yes, but very rarely and even then when I press Cancel the normal lock screen resumes and I unlock in the normal way. I have "Do not lock all buttons" selected in the Key Lock settings. Don’t know if this is significant.
2 stages for screen lock?
I use my TC while riding motorcycle, so I want several apps (TomTom, gps tracking [gps.run]), music [was WMP, but now Coreplayer] and TellmeText) running and the screen off so as to save battery power.
If you press the power button when key lock is on it will turn the display completely off, and *most* programs will keep running. TomTom is a notable exception- it stops working, presumably because it can no longer access the gps?. But better behaved/next generation GPS apps such as run.gps continue to run. WMP, bless its pathetic cotton socks, seems to work sometimes!
Are these inconsistecies uinique to my unit, or known quirks?
Anyone suggest a app that will turn the screen off and allow ALL open apps to run, including TomTom?
Thanks
I don't know how you're operating any of the buttons on the TC with riding gloves on!!
hambola said:
I don't know how you're operating any of the buttons on the TC with riding gloves on!!
Click to expand...
Click to collapse
anyone got anything more useful to add to what was a serious comment/Q
Man, the battery life sucks on this device So my quest on how to turn the screen completely off and lock the keys properly while running all software (especially GPS based such as TomTom) continues....
Anyone know of a 3rd party app that will do this?
I have not read all 200 pages, but it seems there are mixed results for running S2U2 on the Touch Cruise (http://forum.xda-developers.com/showthread.php?t=353008) ? Anyone having success?
Thanks
I know its late but I just saw this and thought I would mention that I managed to over come using TomTom without the device being on. However it doesnt save much on power as the GPS device need power to work.
But I using a simple function I wrote in my application to lock the device using the standard device lock API calls and then rather than switchingthe device into sleep mode (off) I switched it into IDLE mode, which is basically just switching the screen off, the device lock prevents any unwanted button presses.
The power button would just return this back to normal.
I have not yet worked out how to stop the device brightness changing when the screen lock is enabled on the device... :/ Which is my next task.
Ramakin...
well that would be great because even saving having the screen dimmed during lock would help battery life. And, pressing the power button to resume would be MUCH easier than stabbing around at in the sun trying to unlock the screen. It would also make TomTom behave like all other 21C GPS applications, i.e. run on idle.
So, can you send details?
During a recent motorbike trip where I just used TomTom and tracking software (even turned the phone off) I was SHOCKED at how crap the battery life was
I just started having this "bug" yesterday. Basically, what happens (randomly) is that when I press the power button, remove the stylus, or slide the phone open to wake it up I'll be met with a black/blank screen. The backlighting will be on, and the phone is responsive (can receive messages, make calls, sounds/notifications work), but I won't be able to use the screen. If I use the power button to turn the screen back off and wait a few seconds, the screen might start working again. This is completely random and I cannot duplicate it with any guaranteed process, but it seems to be when the phone is waking up from standby. After a soft reset, probably half of the time I'll be met with this same delima, which leads me to believe it's hardware and not completely software.
At the same time the phone is also struggling to re-paint the screen from the change of Landscape-to-Portrait and visa versa. Also opening and closing windows to get back to the today screen also cause a problem. I've disabled TF3D to see if that makes a difference, it doesn't. I have a blank today screen with no plugins to free up the system resources, and am still having this issue.
I'm using JD's Rom (probably around 1.3, it's been running fine with no issues up to this point).
I'm also using S2U2 1.35 (if that makes any difference, haven't had any problems until recently)
The phone has never been dropped, it's in InvisibleShield, and normally sits on my desk charging all day.
This started happening last night for no apparent reason and it's really starting to irratate me.
Any advice is appreciated. Thanks.
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
After more testing..
After some more fiddling around with the phone I'm about 90% certain it's a hardware issue. I noticed that when I slide the keyboard out if the slide portion is past the number line then the screen will stay on, but not update. I don't know how well I can explain it. If I'm typing and hold the screen to keep it from opening all the way then I can see the letters/words appear (in txt msg/email), but if I let the screen goes and it slides all the way open then the screen will stay on and only show what has already happened, any more typed characters will not appear, but if I move the screen back to the number row then the screen will re-draw and update what has happened.
Is this something that Sprint should fix no questions asked?
lulugirl896 said:
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
Click to expand...
Click to collapse
The last piece of software I installed was Gyrator 2 on Friday-ish. Thinking that it was the problem, I removed it using MemMaid. I'm going to give the phone a flash tonight and see if it is software related (hoping for the easy fix) but as the post above says, I'm almost certain it's a hardware issue. I just wish I knew how it happened. . . So much for that time putting those InvShld on.
Final Update (this can be closed)
I took it into a Sprint store and they replaced the "flip" on the top for free (I have insurance).
Point of the story/thread, this can be closed, it was a hardware issue, and now it's fixed.
I'm having an issue with my Nexus 5 after the 5.0 updates. I'm currently on 5.0.1 but had the same issue with 5.0. My device is completely stock. Just never felt like doing anything to the nexus 5. First phone I decided not to root. The issue i'm having is that every once in a while during a day I will try to turn on my phone to view any notifications or just refresh some news sites. Instead of getting the lock screen and hearing the unlock click to slide, i'm taking right to the home screen bypassing the slide to unlock. All applications at this point will glitch. For example, if i open hangouts, it will open but be blank. Spotify might open, or just be a dark gray screen. Other apps just behave very strangely. If I try to press the home button, it lights up and won't do anything. If i press the multi-task button it looks like it will show the running apps but then just shows a blank screen. If I press the back button many times, it takes me back to the home screen which might or might not be blank. The only way around this is to reboot my phone. But this is happening a few times a day. Often, i'll also see the home button and multi task button disappear. I've taken two screen shots of what it looks like. Has anyone ever seen this issue? I don't mind downgrading back to 4.x or rooting for a custom rom if that will resolve this glitch. I can also provide a list of installed apps if anyone wants to know. So what do you guys think of this?
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
An hour or so ago everything worked fine, and then I updated my playstores pending apps (only Fleksy was pending) and the "force touch" feature of the phones seems to have completely stopped working, no matter what setting I turned on or off it didn't work...
Anyone has a clue as to what can cause this?
General notes:
1. Using stock Exynos unlocked variant
2. I am using package disabler (which btw didn't improve much my battery life, but that might be just me using the phone too much ) so maybe one of the packages decided that it depends on a disabled one?
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
RazoE said:
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
Click to expand...
Click to collapse
Mine also stop working after I restart my S8 Plus, it will again work if I wait around 20 minutes. Is this software or hardware problem? Any solutions?
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Ady1976 said:
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Click to expand...
Click to collapse
How does it act up on your part? Mine would just stop working if I restart the phone & I should wait sometimes hours before it would work again.
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Ady1976 said:
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Click to expand...
Click to collapse
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
bladefrost said:
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
Click to expand...
Click to collapse
Unless your phone is unlocked no pins etc the phone will just go to the lockscreen, it's a useless feature, most people have the phones locked and thus it's a complete waste of time, it sounds to me the capacitive home button part of the screen was an afterthought because they couldn't install the fingerprint reader under the screen, just had a software update yesterday and still can't turn it off, basic stuff Samsung should enable an ON/OFF toggle switch for this.
Had the same problem with my S8 Plus India Variant(SM-G955 FD), I got my screen replaced from service center, Device was not rooted back then, so was under warranty.
But it is an hardware issue, as since then it has never gone off.
I mean when I press the home button hard it doesn't wake the phone up & no vibration. It happens when I restart the device then it would stop working for few minutes to a few hours sometimes, then it would start working again normally until I restart the phone again. I think this is just a software issue.