When the screen is off and I recieve an incoming call, the flash light rapidly and repeatedly switchs on and off. How do I turn this feature off? I can't find it in settings.
Update: it was a Tasker profile doing it.
That is not a standard feature on the Pixel series yet.
You must either have a custom rom, mod or app that is causing the issue.
vandyman said:
That is not a standard feature on the Pixel series yet.
You must either have a custom rom, mod or app that is causing the issue.
Click to expand...
Click to collapse
I don't have a custom ROM or mod and can't find what app might be causing it. I think it's just some hidden setting related to accessibility.
Worse case would doing a factory reset fix it?
mustardseeds said:
I don't have a custom ROM or mod and can't find what app might be causing it. I think it's just some hidden setting related to accessibility.
Worse case would doing a factory reset fix it?
Click to expand...
Click to collapse
I went digging in accessibility settings and all the phone app settings and couldn't find this anywhere. A factory reset would fix it since it isn't a thing by default.
It turned out that it was a Tasker profile being triggered unintentionally. I have one to shake the phone to turn on the flash light if on the lock screen. I have no clue why incoming calls would affect it.
Glad you solve your issue and replied to this.
Your other issue,,, do you have the vibrant set to on?
vandyman said:
Glad you solve your issue and replied to this.
Your other issue,,, do you have the vibrant set to on?
Click to expand...
Click to collapse
Yes there is a vibrate pattern when torch it togled. I wonder if this activate the shake-left/right context?
Related
I searched and couldn't find any one else posting this question. I just got the Note last night. I've used Go SMS pro for a long time and want to stick with it. Everything set up fine except the notification doesn't vibrate. I sent them a request but I doubt I'll hear back.
I still have my tbolt and double checked all vibration settings and it still doesn't work. Has anyone had this problem and fixed it?
Thanks
schrochem said:
I searched and couldn't find any one else posting this question. I just got the Note last night. I've used Go SMS pro for a long time and want to stick with it. Everything set up fine except the notification doesn't vibrate. I sent them a request but I doubt I'll hear back.
I still have my tbolt and double checked all vibration settings and it still doesn't work. Has anyone had this problem and fixed it?
Thanks
Click to expand...
Click to collapse
Same issue here. When I set my phone to vibration mode via widget locker, I don't get vibration notification. Fix will be appreciated!
Are you saying you get vibrations at other times?
I just set the phone to silent mode and then it works....hmmm that doesn't make sense. I'm I missing something?
Actually the only sounds I like are vibrations for texts(no tone), phone calls and my alarm. So I would be good if I could hear the phone and the alarm
Ok this is weird.
In silent mode, if I adjust the haptic vibration it determines how much it vibrates in Go sms, even if I have haptic feedback turned off. Notification vibration doesn't effect the gosms notification vibration afaict
So I uncheck silent mode and check haptic feedback. Nope doesn't work...So does this happen to others with Go SMS pro? I'm also using Go Launcher if that matters.
I wasn't getting much help because this was probably an erroneous problem. I think the issue was restoring my settings that I had saved from my previous phone.
I decided to just uninstall/reinstall and do the settings manually.
Works fine now....
Makes we wonder about other settings and backups I restored...
Similar issue
Go SMS vibrates for notifications, but it's not as intense as the stock messaginf app. I've checked all my settings...everything checks out, but it's hardly noticeable in my pocket. I've tried reinstalling it, but it has the same results.
schrochem said:
Are you saying you get vibrations at other times?
I just set the phone to silent mode and then it works....hmmm that doesn't make sense. I'm I missing something?
Actually the only sounds I like are vibrations for texts(no tone), phone calls and my alarm. So I would be good if I could hear the phone and the alarm
Click to expand...
Click to collapse
schrochem said:
Ok this is weird.
In silent mode, if I adjust the haptic vibration it determines how much it vibrates in Go sms, even if I have haptic feedback turned off. Notification vibration doesn't effect the gosms notification vibration afaict
So I uncheck silent mode and check haptic feedback. Nope doesn't work...So does this happen to others with Go SMS pro? I'm also using Go Launcher if that matters.
Click to expand...
Click to collapse
I have inverse issue. I am unable to turn OFF the vibration. Permissions work all over the system except the SMS notification in Go SMS. It won't stop vibrating in any mode and in any case. I have tried all apps but unable to fix it.
BTW, I have sky vega 760S, it is rooted but I am unable to install CWM or any custom recovery. If I could flash a custom ROM, like I had CM10 in my previous 760, this issue had been gone.
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
EDIT:I fixed it! turns out it was a hardware problem which occured after i replaced the screen. It was fixed by following instructions on this youtube video,called "How to Fix Proximity Sensor Issue for Samsung Galaxy S3, S4, or Note 2" ( i can't link right now because I'm new, so just look it up on youtube.) so if anyone encounters the same problem hope this video will help!
Hey guys. New to the forum I tried to do a bit of searching but couldn't really find an answer.
So I have two questions/problems I guess.
First off when I go into a call, sometimes the phone screen goes black as soon as I start the call, and won't turn back on until I hang up using the power button. From what I understand it's due to the proximity sensor always being on? But I have not been able to find a solution to this.
Secondly is, I've noticed with the lock screen notifications, when I ticked the option for wakescreen when receiving notifications, and when the screen is off, the proximity sensor is on. and when i untick the wake screen option, it goes off again.
I'm using Fusion-Boeffla Rom latest version as of now, 26-02-14 one. But this problem has been around when I was testing different roms such as temasek unofficial CM.
Any ideas how to fix this?
Thanks in advance!
1- go to calls -> settings -> uncheck turn of screen during calls.
Sent from my GT-I9300 using Tapatalk
amirTor said:
1- go to calls -> settings -> uncheck turn of screen during calls.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I can't find that setting unfortunately, also is this a hardware problem or software?
Jerryxmas said:
I can't find that setting unfortunately, also is this a hardware problem or software?
Click to expand...
Click to collapse
www.youtube.com/watch?v=z7kx27c1Iao&cd=1&ved=0CDQQtwIwAA&usg=AFQjCNHPZTtRTQj2KfBVwUOb3cUm-UNSkA
And its probably a kernel / rom issue
Sent from my GT-I9300 using Tapatalk
i can't click the link, but i've seen that option in stock samsung roms before, but i can't seem to find it on my rom. And you're right, its very likely its a rom/kernel issue, i may try a different rom or even stock to see if it helps =) thanks
I've noticed that no matter what setting I have it on, my tablet (M5 8.4) automatically lowers the screen brightness in Chrome and YouTube, but more noticeably in Chrome.
Any way to disable this?
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
thref23 said:
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
Click to expand...
Click to collapse
I've checked every possible setting, and read online everywhere, but to no avail. It also dims in Firefox. It dims as soon as you go into the app. After an online search, I found many Huawei owners with EMUI 8.0 having this issue. There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Funny. Would love a solution as well as this is rather annoying
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
thref23 said:
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
Click to expand...
Click to collapse
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Click to expand...
Click to collapse
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
kev1807 said:
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
Click to expand...
Click to collapse
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
xKevin said:
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
Click to expand...
Click to collapse
hmhm. I was quite sure it was a System process - since the "bug" (dunno whether you read the thread on keyboard and brightness ...) appears with the system-icon when in Desktop-Mode ...
Great. there is a fix for this. now I need a non-root fix ... :-/
Yes, try the app ilux. Let that control brightness.
Steffe89 said:
Yes, try the app ilux. Let that control brightness.
Click to expand...
Click to collapse
Do you have a link to this app? I can't seem to find anything relevant when searching for ilux.
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Up until now I thought a reboot would bring the "wonderful" feature back ...
How comes that you mention a reboot is needed?
How do you disable it? I can only do a force stop
I'm not sure how to disable it without root (I imagine adb might work). With root, most use Titanium Backup to freeze it. I'm using Service Disabler to disable the associated services instead. Service Disabler is awesome if you are rooted, underrated app and great for EMUI because, for example, you can disable individual parts of the Tablet Manager app without breaking the features you want.
You might not need to reboot. When I initially froze it using Xposed Edge Pro, but didn't reboot, it didn't change anything for me. Could have been due to Xposed Edge Pro.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
scott.eden said:
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Click to expand...
Click to collapse
Was there any negative outcome from disabling power genius?
krisu253 said:
Was there any negative outcome from disabling power genius?
Click to expand...
Click to collapse
None for me.
thref23 said:
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Click to expand...
Click to collapse
I cannot find Power Genius?
I can confirm following the above article will allow you to remove the power genius package from the Mediapad M5 8.4 on EUMI 9.1 without root.
Thank you sooooo much... You can't believe how annoying this was. No need to even reboot either and it doesn't return if you do.
Now I just need a way to too keep the custom 740DPI after reboot and this tablet will be perfect
Just updated to Oreo on my H830 today. When I was on Marshmallow/Nougat, disabling KnockOn was as easy as using the Quick Shortcut Maker app to disable it.
Now, it doesn't seem like there is an option to disable it using the app. Does anyone have a solution?
Update for OTA?
Enviado desde mi LG-H830 mediante Tapatalk
I am having the same exact issue. It seems when LG rewrote their settings interface from scratch, they actually remembered to remove the hidden settings this time (Only God knows why the settings are even hidden and now completely disabled to begin with). Unless they just changed the name of the "KnockOn" Setting.
Its a shame too, because one of the first things I would always do whenever I needed to factory reset.etc was to download QuickShortcutMaker and disable KnockOn right away. But now I can't do this. Hopefully someone finds a workaround. Why can't LG just let us disable these things?
NullaVisus said:
I am having the same exact issue. It seems when LG rewrote their settings interface from scratch, they actually remembered to remove the hidden settings this time (Only God knows why the settings are even hidden and now completely disabled to begin with). Unless they just changed the name of the "KnockOn" Setting.
Its a shame too, because one of the first things I would always do whenever I needed to factory reset.etc was to download QuickShortcutMaker and disable KnockOn right away. But now I can't do this. Hopefully someone finds a workaround. Why can't LG just let us disable these things?
Click to expand...
Click to collapse
Excuse me just a quick question. Why would you disable it?
OverplayOfficial said:
Excuse me just a quick question. Why would you disable it?
Click to expand...
Click to collapse
My point exactly i don't think it's draining slot of battery.
I'm curious why they disable it.
1) Battery-saving concerns
2) Avoiding accidental wakes
3) Absolutely no point in keeping it on if the user doesn't want it
Because it can be triggered by accident. And depends on how you setup the phone, it could cause annoying problems if phone is turned on by accident.
nookin said:
Because it can be triggered by accident. And depends on how you setup the phone, it could cause annoying problems if phone is turned on by accident.
Click to expand...
Click to collapse
I may be wrong but I think it's not that easy to trigger it. As the phone don't turn the screen on unless the proximity sensor is not triggered, the phone inside a pocket or in a situation like that won't turn the screen on.
but I'm not saying this applies to all situations
Most accidental trigger occur while holding the phone or dropping off the phone. I think the point OP trying to make is that owner should have the option to turn the feature off. If you need the knock-on feature, by all means keep it. I use the fingerprint reader to turn phone on. Knock-on is really just a way for me to make mistakes.
I have the same issue.
I had KnockOn disabled and updated to Oreo; now double tap to wake doesn't work (using default LG home) .
Normally this would be OK but recently power button started giving some trouble so double tap to wake would be a good feature to have.
Unfortunately can't find the menu to re-enable it in Oreo.
Hoping someone one finds a way and post it here