S5 klte - Lineage OS + Screen Filter Overlay Issue - LineageOS Questions & Answers

I had been running on a late May build of Lineage OS until recently without issue (5/17 I think). This week I updated to the most recent build and have noticed that one of the apps I've used for years has started behaving strangely. I use "Screen Filter" overlay app to darken my screen and turn off the hotkey lights overnight. Since updating I have found the app is behaving strangely after my phone has been idle for a while. The notification for the app still shows up, but it is set to a different brightness level than when I originally enabled it and the hotkey lights are reactivated. Since this happens while the screen is off for extended periods but doesn't seem to be an actual crash of the application I am at a loss for how to diagnose the problem. I rolled back to the July 26th build (the oldest download I could find) and this issue is still occurring, but I am not knowledgeable enough to know what might changes occurred between 5/17 and 7/26 that might cause this behavior.
Any suggestions or ideas on what might be the culprit and if there's any solution besides sticking with May software if I want to use Screen Filter?
Thanks!
<Mod Edit>
Reposted here:
https://forum.xda-developers.com/galaxy-s5/help/s5-klte-lineage-os-screen-filter-t3682337
Thread closed.

Related

Background apps super low priority / not triggering

My SGS4 (T-Mobile) is a bit over 2 years old now. I had been running a modified TouchWiz rom (I believe it was this one: http://forum.xda-developers.com/showthread.php?t=2679913), but recently I started having problems where the phone was missing triggers - alarms wouldn't go off, TextSecure would receive all my messages all in one big lump only after I opened the app, stuff like that.
I tried reflashing a number of ROMs, and I've currently landed on a recent CM12.1 nightly, but I'm still getting this problem where apps running in the background don't seem to have enough priority to get the phone to wake up and alert me that something is happening.
Does anyone know of a way to figure out what's going on? Any suggestions on diagnosing this?
(I have tried messing with PrivacyGuard on CM12.1, in case it's a separate issue, but the problem persists with it enabled or disabled).

Long wake delays on non oos 8.1 roms

Some 5t users noticed a very long wake delay on using 8.1 custom roms. It seems the screen is on as it reacts to touch input but stays rotaly black. Sometimes it even goes back off by itself when the phone is still locked. I lately noticed there is somekind of light below the amoled when the delay occurs. I was only able to see it when my screen was cracked due an accident. So the only logical explanation to me is that there must be somekind of black overlay preventing the user from seeing the content. Also the fact that some users never saw this bug on thair device it is possible that this issue is caused by some kind of google setting which is getting synched and the rom isnt fully compatible yet as it hasnt that implementation yet.
Many people keep saying its caused by pocket mode.
But its still present no matter what setting is used and even occurs after a fully clean installation of the rom without any changes to the default settings.
The only fully working workaround (no body is mentioning) i found out by my self, is to fully disable the lockscreen. xou have to disable swipe lockscreen too. The wake delay will never occure when there is no lockscreen at all.
I made this poll to see how many people had this problem and who didnt.
Who ever saw the wake issue by himself will understand the fact that i think all current 8.1 roms are almost impossible to use when having a lockscreen. Esspecialy at the morning it can take minutes to wake the phone no matter what unlock method/ swipe/ gesture/ password/ fp
i also provided all kind of logs and found the error lines. I showed them to all the devs of the different roms in telegram a month ago. But all we get is: "Disable pocket mode" and it clearly doesnt fix the problem.
one thing i also noticed is, that the problem started when the expanded screen feature got included (im not saying that disabling or enabling expanded desktop causes the issue)
Im not blaming any dev. Im just afraid this bug is beeing ingnored as most people never saw it happen.
I hope the dev will sort this issue as its literally the only bug preventing me from using custom roms.
Did you manage to fix the issue without disabling the lockscreen? I just got the phone yesterday and having this problem
Don't have any bugs you said above, just one issue that no body help me till now, in lastet ob4, the output sound when recording video/sound is really really low compared to the stable 5.04, I have to set the volume to the maximum level to hear clearly. I said this thing many times but may be it's just me, no one else.
do you use expanded desktop enabled on all apps? If so there's a Xposed fix http://repo.xposed.info/module/fr.merams.r.deepscreenoreo

Notification bar pull down stutter after unlocking phone

I searched forum for similiar issues but could not found anything(though there are some reddit topics).
When I wake the phone with power button or fingerprint sensor, and try to pull down notification bar, there is a stutter/lag lasts 1-2 seconds. Lets say you pull up for app drawer there is nothing but pull down and there it is.
Also wallpaper seems to affect it a little bit but it might be a placebo effect as it still stutters(light the way wallpaper seems to solve it a little bit.).
It started after Android 10 update and I even tried to clean flashing whole rom but result is same and I do not have any UI altering apps.
It seems like a slow wake up issue and may be playing with sleep frequencies might solve it but I did not root so it is not a option for me.
Is anyone else facing this ? Vanilla or custom roms/kernels ?
Yep, I have the same issue. It's pretty annoying, but I did get it to stop, for me at least it seems the new gesture navigation is causing this because I can't get it to stutter while using the 2 or 3 button navigation methods. I've had this happening since I updated to Android 10 (stable release, not beta) but after a while it just fixed itself, unfortunately my phone ran out of battery yesterday and today after I booted it up it came back to haunt me :/
Alright I got it to stop, disabling both "New notification" and "Double-tap to check phone" did it for me. Hopefully this helps.
Scythe said:
I searched forum for similiar issues but could not found anything(though there are some reddit topics).
When I wake the phone with power button or fingerprint sensor, and try to pull down notification bar, there is a stutter/lag lasts 1-2 seconds. Lets say you pull up for app drawer there is nothing but pull down and there it is.
Also wallpaper seems to affect it a little bit but it might be a placebo effect as it still stutters(light the way wallpaper seems to solve it a little bit.).
It started after Android 10 update and I even tried to clean flashing whole rom but result is same and I do not have any UI altering apps.
It seems like a slow wake up issue and may be playing with sleep frequencies might solve it but I did not root so it is not a option for me.
Is anyone else facing this ? Vanilla or custom roms/kernels ?
Click to expand...
Click to collapse
I have exactly the same issue on my Pixel 2XL, manage to fix it by disabling Google Feed on the left of the main home screen. Try it let me know if it works.
Update 1: disabling google feed doesn't work. I try to switch back to 3 button navigation and the issue gone.
I do not know how but now it is smooth everytime I try to wake phone and double tap+alwayson display is enabled. Also I tried all wallpapers and it works without any stutter.
Probably monthly updates fixed it, idk.

Galaxy S9 locks itself when screen is rotated. (Samsung support unable to fix issue)

First of all, let me state that I am desperate. After going through many fixes and channels, I cannot find a fix. Let me also state that I am new to the forums, and apologise if I miss out anything here. Do let me know if I have missed out any important information.
The issue: When the orientation of the screen changes to landscape, the phone immediately enters the lockscreen.
Further defining the issue: This issue occurs only when the orientation of the screen changes. When screen rotation is locked and the phone is turned on its side, the screen orientation is unable to change and the issue does not occur.
Device specs:
One UI version: 2.0
Android version: 10
Baseband version: GX960FXXS8DTD1
Kernel version: 4.9.118-17633310 #1 Mon Apr 20 13:03:37 KST 2020
Build number: QP1A.190711.020.GX960FXXS8DTD1
Android security patch number:
1 Apr 2020
Timeline of issue (includes events leading up to issue and attempted fixes. Please note that I do not know what I am doing.):
9 March - Bought Galaxy S9 second hand from a phone shop, factory resetted prior to purchase. No issues watching YouTube videos or Netflix videos. Phone is kept at home and charged regularly.
? Apr: Phone settings are adjusted and a theme is downloaded. No issues still.
8 Jun 7:00am - Phone is prepared for daily use. App Inspector and ADB Debloater are used hide some apps (read: every form of Bixby) . Only system apps with a clear and unneeded function are hidden. Multiple apps are installed from the Play Store. One third party app, Ymusic, is downloaded from a website.
This app has not caused any issues on 3 other Samsung devices (S7 Edge, Note 9, S7). APK extractor is used to extract Video Editor from a Galaxy S7, and it is installed on the Galaxy S9. The S7 does not have any issues.
All apps downloaded are already present on the Galaxy S7 with no issues except for a remastered version of a game called "There Is No Game Jam Edition". The older version of the game has no caused any issues.
8 Jun 12:13pm - Two videos are watched on the YouTube app in fullscreen with no issue. Soundcloud is visited. Visited drugs.com and reddit.com. Watched more videos on YouTube app. Tested smallest possible delay in double pressing left menu button to switch between apps (like alt-tab but for Android). Discovered that while the S7 has no noticeable delay, the S9 requires more than half a second to pass after the first press in order for the second press to cause the next app in the list to be selected. If the two presses are back to back with no delay, the S9 simply stays on the app selection screen.
8 Jun 2:13pm - Watched a video on YouTube app. Turned screen to landscape, and phone locks itself.
8 Jun 2:58pm - Engaged Samsung official support in remote control session. Samsung tech used General Management in settings to reset all settings twice. Tech also removed lockdown mode from power button menu. Tech uninstalled some possible culprit apps: Ymusic, 1.1.1.1, Malwarebytes. Tech guided me to boot into safe mode. Issue persisted even in safe mode. Tech instructed me to factory reset phone. He also stated that if the issue persisted, I would have to send it to Samsung's service centers for an inspection. I expressed concern that I may have caused the glitch and that following the same setup procedure as before would simply cause the glitch to return.
Note that I also do not have access to my laptop to "debloat" , as I have sent it for servicing on the morning of 8 Jun. In addition, I have developed some sort of swollen infection on one of my fingers that makes typing into a command prompt to "debloat" not just uncomfortable but also very unhygienic (I did not see pus until this time). Writing this on a mobile device, on the other hand (or my thumbs) , is OK.
8 Jun 6:29pm - Posted this issue on Samsung Reddit and twice on corresponding Discord. Posted on Google Android help forum.No replies on all. Messaged Android enthusiast friends (who may/may not be technically competent). Friends suggested deleting One UI cache and data. Issue persists.
9 Jun 10am - Posted issue on Tech Support Reddit's live chatroom. Some members suggested posting to XDA.
9 Jun 1:34pm - Discovered that minimum delay between presses of left menu button to switch apps is now insignificant.
are you sure all you did is debloating? because I did it once and I got zero problems, beside debloating shouldn't cause your phone to do that far. and non of the apps you mentioned above could cause the problem imo.
My suggestion :
- just use custom rom, if you want to stick to OneUI but got no Bixby and unnecessary Samsung apps or what so ever just flash Alexis ROM (OneUI 2.1 already). It is a bit tricky, since you have to unlock bl, and flash twrp and other thing. but it worth imo.
- if not, just flash again the stock firmware and redo the debloat
I am very sure all I did was disable and hide some apps with obvious purposes (such as Bixby) with ADB. While I am open to the possibility that something I disabled caused the issue, it makes no sense that a few hours would pass before the issue appeared. All I did in those few hours was watch YouTube videos use Ymusic, so I could not have possibly picked up any form of malware (which would be blocked by Malwarebytes anyway) or made any changes to break my system.
For now, I am going to factory reset my device and test landscape orientation after disabling each app while simultaneously praying to the Android gods that nothing goes wrong. Alexis ROM looks like the solution I am looking for, but unfortunately I know my limits and installing a custom ROM is beyond them.
This is a problem with my stock android s9
I'm frankly just about to give up. I factory resetted the device and redid installing all the apps, set them all up and got the settings in order. Guess what, the same exact glitch occurred out of the blue. Along with two more- a noticeable delay when double pressing the overview button and the lock screen clock settings being un-clickable. I'm running out of patience and hope for this device, but then again all the others I have are equally broke. Pity, was hoping to start working food delivery, too.
UPDATE: With guidance from a friend, I have used Odin to flash a friend's functioning copy of Android 10 on my device. I am going to configure it as usual and pray that nothing goes wrong. Will update here in about 24 hours' time, the time it usually takes for the glitch to appear. It should be noted that yesterday, I was watching videos on Landscape mode just fine until I decided to finish up changing my settings. That was when the glitch occurred, so I highly suspect that some setting I changed is causing it.
UPDATE 2: After flashing my friend's ROM, I went on to install only 1 app (App Inspector) and remove only 4 system apps while paying attention to any changes(disabling Always On Display broke my lockscreen clock settings so that was nice). Still, I could rotate the phone to landscape just fine. It was when I pressed the setting "lock home screen layout" that the glitch occurred. On one hand, this adds up, as the glitch occurred soon after changing this setting yesterday. On the other hand, I do not recall changing this setting the first time I configured my phone. I will experiment further and update this thread.

Nav buttons stop working with disabled lock screen profile

I recently upgraded from LOS 18.1 to 19.1. I was having issues with battery drain and finally decided to upgrade. The battery issues are completely fixed. A new issue cropped up with my profiles however. I have a "home" profile that disables the lock screen when my phone connects to my home wifi.
Since the upgrade, when my lock screen is disabled, my home and recent apps button stop working. Other things stop working as well like being able to copy paste between apps. My somewhat usable workaround for now has been to enable the recent apps screen when double tapping the home button, for some reason this works. I can return home by tapping the outer edge of the recent apps screen. This is what I'm running for device and OS:
Device - Poco X3 Pro (Vayu)
OS - LineageOS 19.1 microg Oct. 24, 2022 release(from https://lineage.microg.org/)
Recovery - TWRP
I found a bug report on Gitlab for the exact same issue here: https://gitlab.com/LineageOS/issues/android/-/issues/5189
They're reporting it as fixed for the most recent builds, which I'm currently running and still having the problem.
I'd really like to avoid a device wipe and reinstall as I have some MFA apps for work that would be a big pain to get going again. Does anyone know of any fixes? I'm guessing it's permissions related of some kind as it's like the device is only half unlocked or something. I've tried creating a new profile as well as disabling profiles, rebooting, and trying again, nothings worked so far. Should I just open another bug report on Gitlab? Appreciate any help.
This seems to have stopped, but I have little idea as to why. I noticed it stopped after I connected my phone to my PC with a USB to transfer files. After I did that, for some reason the lock screen disable is working fully as intended now. All nav buttons work, copy+paste, etc.

Categories

Resources