Related
Hi,
Since two days I'm a happy and proud Note owner, but there's one thing, that makes me really go crazy:
I installed the program "Widgetlocker", because the standard lockscreen is quite broing. It actually works quite good, but sometimes the standard lockscreen still apears. Not instead of the widgetlocker, but additional. So I always have to unlock two lockscreens.
Does anybody else has got this problem? And how can I fix it?
I tried to find a solution in different forums and in the program configuration, without sucess!
Thanks for help!
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
I turned on root helper and home helper in settings, that fixed it for me. I'm on Stock Rooted XXKK9 if that helps.
Sent from my GT-N7000 using xda premium
I presume you have set the lock screen to "none" in the actual phone settings too?
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Where? Can't find any option like that....
Thanks for help
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Lol, i accidentaly hit the thanks button. You're welcome!
Sent from my HTC Desire HD using xda premium
drjp77 said:
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
My widgetlocker works fine. Been using it since day 1. Hmm.. Sorry. Not sure how to help.
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
The_Steph said:
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
Click to expand...
Click to collapse
Thanks @ everybody for the help, but unhappily it's still not working properly.
The problem always apperas, when the phone's sleeping and a gTalk message comes in.... but ONLY, when the gTalk ppop-up is activated......
Any (more) idea?
you are leaving it running all the time aren't you?
I use to have the same problem, very rarely but it was still annoying. I have put a lock on widgetlocker so if I ever close all programs, widgetlocker is still running. It's not happened since but it's only been a few days so I'll see.
chrcad said:
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
Click to expand...
Click to collapse
Some pop-ups cause this if they're designed to appear underneath the stock lockscreen rather than dismiss it.
For now:
1) Easy Wake Mode disables the system lockscreen
2) WL Settings > Long-press volume down for Experimental > Aggressive Dismiss stock lockscreen. This should work, but it's not well tested yet so it's off by default.
Hi all. This is very odd. Whenever my finger approaches my screen, I see a circle on my screen. I know you can enable this sort of behavior (not exactly but similar) in Developer Options, however I do not have that box ticked. I cannot for the life of me figure out why this is happening. Any help would be appreciated.
Hi, I think you'll find you have glove mode turned on in display options.
BenTescort said:
Hi, I think you'll find you have glove mode turned on in display options.
Click to expand...
Click to collapse
Thank you, Ben! That's what was causing it! Thanks for your help!
Glad I could help. Cheers.
ShermCraig said:
Hi all. This is very odd. Whenever my finger approaches my screen, I see a circle on my screen. I know you can enable this sort of behavior (not exactly but similar) in Developer Options, however I do not have that box ticked. I cannot for the life of me figure out why this is happening. Any help would be appreciated.
Click to expand...
Click to collapse
I tough it was due to "Show touches"
Edit: I'm already late on my response..haha
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.
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
TonyGzl92 said:
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
Click to expand...
Click to collapse
I get this too if I have missed calls. I turned off the settings in phone app and it still does it.
TonyGzl92 said:
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
Click to expand...
Click to collapse
So i switched off smart alert and it stopped doing it for me.
borijess said:
I get this too if I have missed calls. I turned off the settings in phone app and it still does it.
Click to expand...
Click to collapse
May be you guys should try turning off the setting and restart, if that doesnt solve the problem go to recovery mode and clear cache. Let us know if any of that works.
On a side note: I have been facing weird ass issues with this phone just today my phone wont go to mute by using volume key while receiving a call. Like someone calls you and your phone is ringing, you just want to silence the ringtone you can use volume key (Press once), Flip the phone or put your palm over it (If you have the settings on). I tried multiple restarts and switched on and off the settings many times. It was fixed when i restarted my phone to download mode (This happened by mistake i wanted to go to recovery) anyhow that fixed it.
warriorvibhu said:
So i switched off smart alert and it stopped doing it for me.
May be you guys should try turning off the setting and restart, if that doesnt solve the problem go to recovery mode and clear cache. Let us know if any of that works.
On a side note: I have been facing weird ass issues with this phone just today my phone wont go to mute by using volume key while receiving a call. Like someone calls you and your phone is ringing, you just want to silence the ringtone you can use volume key (Press once), Flip the phone or put your palm over it (If you have the settings on). I tried multiple restarts and switched on and off the settings many times. It was fixed when i restarted my phone to download mode (This happened by mistake i wanted to go to recovery) anyhow that fixed it.
Click to expand...
Click to collapse
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
*Detection* said:
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
Click to expand...
Click to collapse
But I have that setting turned off.
TonyGzl92 said:
But I have that setting turned off.
Click to expand...
Click to collapse
Did you follow the steps i suggested ?
Also try clearing system cache in the boot menu.
If that doesn't get it, modify the appropriate notification setting, lol.
That can be a daunting task but sort of fun because you can streamline your notification settings as you do so.
*Detection* said:
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
Click to expand...
Click to collapse
warriorvibhu said:
Did you follow the steps i suggested ?
Click to expand...
Click to collapse
Yeah, I've done that
blackhawk said:
Also try clearing system cache in the boot menu.
If that doesn't get it, modify the appropriate notification setting, lol.
That can be a daunting task but sort of fun because you can streamline your notification settings as you do so.
Click to expand...
Click to collapse
What do you mean about the appropriate notification setting?
TonyGzl92 said:
Yeah, I've done that
What do you mean about the appropriate notification setting?
Click to expand...
Click to collapse
That's the trick.
Figuring out which app is responsible.
blackhawk said:
That's the trick.
Figuring out which app is responsible.
Click to expand...
Click to collapse
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
If they catch it. Consider which sensors and operation triggers it, cause and effect, to narrow it down.
Playing with Android is fun... Android witch hunts are how you really learn about Android's gooey layer tricks.
Google searches on older Notes and parallel Samsung models can turn up answers many times.
This model is too recent; so not near as much online troubleshooting info. Google searches encompass threads on this forum as well so it can be a good way to find the needle in the Android stack. Do not time limit searches.
On my 10+ with it's baffling bt poor audio I found the answer with something written about the N9.
Many of these issues are long standing.
Samsung finally fixed the bt settings issue in a Wearables update. That took years.
Only persistence is omnipotent...
I figured that out by chance..
It's the edge-compass app
Just delete it from edge apps and it'll go away.. cheers
blackhawk said:
That's the trick.
Figuring out which app is responsible.
Click to expand...
Click to collapse
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
samialhout said:
I figured that out by chance..
It's the edge-compass app
Just delete it from edge apps and it'll go away.. cheers
Click to expand...
Click to collapse
Well, I've checked all that and nothing, I don't even have the compass edge panel. But I think I'm able to replicate the issue, it mostly happens when my phone is face down on a surface and I pick it up and turn it to me, I don't have a case on it yet and I'm starting to think that it might have something to do with the edge screen but so far no luck
Use good lock. It has a module to detect vibrations and tell you what they are
Nice catch
TheMadScientist said:
Nice catch
Click to expand...
Click to collapse
Yeah, I installed it yesterday. But no vibrations are registered there so honestly I don't even know what to think now.
On the other hand when I switched from my note 10 plus I used smart switch, and now I'm thinking I should do a fresh start on my n20U.
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
Exactly check if you have Notistar from good lock switched on. That cache might need clearing.
I just go with it lol. I'm nutz. I'll feel my **** vibrate in my pocket when its sitting on the table. So I don't pay much mind to phantom vibrations. ???
TheMadScientist said:
I just go with it lol. I'm nutz. I'll feel my **** vibrate in my pocket when its sitting on the table. So I don't pay much mind to phantom vibrations. ?
Click to expand...
Click to collapse
It does suck some battery life though. It's one of the features I disable on my 10+ mostly because I find it annoying.
It's cool though how much you can customize notification behavior; one of the biggest reasons to go with Samsung is customization.
I play around with Settings a lot.. never crashed a load doing it. It's just occasionally gets time consuming to sort it out.
I use KOReader which wasn't working well with the Pixel 7 Pro because of the front camera hole.
So I made it so the app would draw over the camera. This means the status bar icons also draw over the camera hole.
Now I want to revert back to the default state so the system and apps won't draw over it.
I thought I did it via Developer Options, Display Cutout. But it's already set to "Device default".
Now I can't figure out how to go back to the default.
Is there some other setting that could affect this?
vurtomatic said:
I use KOReader which wasn't working well with the Pixel 7 Pro because of the front camera hole.
So I made it so the app would draw over the camera. This means the status bar icons also draw over the camera hole.
Now I want to revert back to the default state so the system and apps won't draw over it.
Click to expand...
Click to collapse
How did you do this? There's where your answer lies...
vurtomatic said:
I thought I did it via Developer Options, Display Cutout. But it's already set to "Device default".
Now I can't figure out how to go back to the default.
Is there some other setting that could affect this?
Click to expand...
Click to collapse
If you can't find and correct the hidden user setting you altered you'll need to do a factory reset to purge the erroneous setting.
blackhawk said:
How did you do this? There's where your answer lies...
Click to expand...
Click to collapse
That's what I'm trying to figure out by asking here! I can't remember
I thought the Developer setting was how I did it, but that hasn't helped.
vurtomatic said:
That's what I'm trying to figure out by asking here! I can't remember
I thought the Developer setting was how I did it, but that hasn't helped.
Click to expand...
Click to collapse
Try toggling Developer options off temporarily.
blackhawk said:
Try toggling Developer options off temporarily.
Click to expand...
Click to collapse
Hi thanks for your time helping with this, really appreciate it.
Not sure if I'm misunderstanding you, but I will try disabling "Developer options" completely. The phone is now rebooting after I disabled that.
(I've tried to switch between different "Display cutout" settings and going back to "Device default" hoping it'll fix it, but it didn't.)
vurtomatic said:
Hi thanks for your time helping with this, really appreciate it.
Not sure if I'm misunderstanding you, but I will try disabling "Developer options" completely. The phone is now rebooting after I disabled that.
(I've tried to switch between different "Display cutout" settings and going back to "Device default" hoping it'll fix it, but it didn't.)
Click to expand...
Click to collapse
Exactly. Sometimes Developer options goes nuts. Disabling resets all changes to default settings.
If an app you installed started this, reinstall it and see if you can disabled what caused it with the app's settings. That's the easiest way to access the hidden setting change. After it's fixed get rid of that poorly coded app!
Had a reader the altered the display color. After uninstalling the app the change remained. Reinstalled, turn off the setting that caused it, uninstalled the buggy app. It should have reset the hidden user settings to default when uninstalled. Rarely some Android apps don't uninstall cleanly and cause damage to the system. I avoid "sampling" in part because of this. This OS (Pie) load is 3 yo now... still running strong with no system upgrades or updates.