Related
AT&T LG G3, love the phone. I'm down for the lollipop update, but I can't seem to remedy one new Lollipop problem.
At various times, i haven't figured out exactly what causes it, but when i drag down my notification bar, during just normal use of my phone, I can see various notifications from applications, but NO DETAILS, only a line saying "Unlock to see sensitive". Of course my phone is unlocked as I AM USING IT!! I tried going into settings/sound/notifications/turning SHOW ALL NOTIFICATIONS on, and then you can go into apps individually to set notification preferences, but nowhere does it say anything about setting sensitivity for individual apps. This seems to be a bug. I've dug through all the possible settings.
One example that has happened to me many times is i'll be on the phone talking, i hear a notification tone, put on speaker phone and drag down my notifications to see what it is, and i only see the app icon, with "Unlock to see sensitive". Then if i press the notification it brings up the application no problem, but that is a pain and i didnt want to open the app, just see the notification. This is sure frustrating.
Any help greatly appreciated.
???????
I am also having random occurrences where all of my drop-downs say unlock to see sensitive. Locking and then unlocking the phone fixes it I have no idea what causes it
I am having the same issue haven't figured out the cause or a fix
I just started having the same issue. I went to Display >>> Lock Screen and noticed that my setting had been set to Swipe to Unlock, even though I've always had it set to None. I switched it back to None and now I can see the notifications again.
This randomly happens to me too. Checking the power button automatically locks screen option is a bandaid solution for me
Based on this thread:
http://forum.xda-developers.com/lg-v10/help/knock-to-wake-t3239674
So far it's only a confirmed suspicion, but it's already happened to several people including myself. Accessing the hidden menu may break the knock on feature, even without doing any modification in it.
Possible Solutions:
-Hard Reset (100% working)
-Deleting Finger Prints (I've only seen this working on 1 person in another thread)
Please report if this has happened to you and if you've done something else to solve the issue. Thanks!
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Nope, doesn't break it. Been in the hidden menu to access Engineering Mode a bunch of times already and knock-on works fine.
Went in there to unlock the APN fields. Knock-on works fine.
Sent from my LG-H901 using XDA Free mobile app
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
toastido said:
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
Click to expand...
Click to collapse
Nope that didn't break it either
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
toastido said:
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
Click to expand...
Click to collapse
Obviously we need more data on this issue, there could be other variables in play as well but that's why we're raising the awareness of the knock on issue.
@toastido haha it's all good.
LancerV said:
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
sentry07 said:
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
Click to expand...
Click to collapse
Dial 277634#*#
I'm anxiously awaiting everyone now saying their knock on is broken ?
Didnt break mine! Thanks for the info to get into hidden menu though
nope mine still works but i do have issues with the screen in calls but thats it. but but was that way when i got it.
i think your hidden menu theory is good but my knock doesnt work but it stopped after i did a rest because the apn got messed up and it wouldnt let me add a new one. so i found this out this problem seams random as hell and if i turn knock pattern on to unlock the phone the knock works to turn the screen on but not off. i also noticed my second screen doesnt have the flash light on it when off anymore. so i will be doing a reset tomorrow unless anyone knows how to get the secound screen apps back when the screen is off. i think those apps are related to the tap on
It did break mine. Went to menu and hit apn unlock. No crash or anything. I noticed it not working immediatly. Knock code does still work.
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
joachim123 said:
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
Click to expand...
Click to collapse
mines the same no quick toggles
Mines the same no quick toggles but i found the answer with out rest on another post. i figured it out that its just something crashing the hidden menu doesnt matter what even force closing causes this problem. which is what i did seeing that the first time i used it nothing happened but the second time when the problem happened i cleared all apps and it stopped working. i'm guessing they disable it if something crashes it.
the knock on actually just gets turned off. Here's the quote for the answer make sure both knock on settings are on and it works instantly so no reboot needed.
-LBT- said:
Get yourself Quick Shortcut Maker, launch it, change the search type to 'Normal', search for 'Knock On', click on 'Settings', then on 'Try'. On the next screen, switch Knock On back and forth and see if that works.
Click to expand...
Click to collapse
clockcycle said:
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
Click to expand...
Click to collapse
you are a genius and life saver!!! thank you.
hidden menu did break it, confirmed.
I'm hoping someone else is having this same issue since the MM update.
When I first got the Note 5 on lollipop, I set up a smart lock with my home location so I didn't have to use my fingerprint when I was at home. I also set up the s view case to automatically unlock the phone when opened. On lollipop this worked pretty much flawlessly.
Since the update though, both are somewhat finicky. Sometimes it works just fine while other times it's smart lock that still wants my fingerprint. At other times, smart lock is fine, I only need to swipe to unlock, but the s view case doesn't unlock the screen when opened. I'm hoping it's just an overlooked bug in the first MM software and will be corrected with future updates.
I have factory reset the phone and done everything I can think of to fix it. It's not a big deal as it doesn't hurt functionality at all, it's just a bug I've noticed. Also, I think a good option under the smart lock settings would be "when connected to a certain Wi-Fi access point" but it's not an option.
Has anyone else noticed this and fixed the issue? Thanks
Same issue. Set up paired with my Zenwatch and it seems to be about 50/50 whether I can slide to unlock or have to use fingerprint.
Same thing here. Its def a bug. I have tried clearing out my google settings, location settings, location cache, everything other than a master reset for the most part.
Honestly it never works right since the mm update. Wouldnt even give it a 50/50..
BUT
What i have noticed is if i simply press the home screen twice, one to wake, then again but lightly pressing, it unlocks automatically. The finger print scanner reads the print so quick it gets you straight to the home screen.. shouldnt have to do this. but it works pretty well to unlock quickly. Plus, dont have to slide anymore and get prints/smudge on the screen.
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.