Nav buttons stop working with disabled lock screen profile - LineageOS Questions & Answers

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.

Related

S5 klte - Lineage OS + Screen Filter Overlay Issue

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.

S4 Mini LTE with Lineage keeps crashing after SMS

I have the latest Lineage 14.1 on my S4 Mini all seems to be fine except that it crashes and then reboots from time to time. This seems to be happening after sending SMS messages, but not always. I did have this problem before with the stock OS, so probably not Lineage specific but as it's still happening, I'm guessing a setting somewhere that needs to be looked at?
Thanks
cancunia said:
I have the latest Lineage 14.1 on my S4 Mini all seems to be fine except that it crashes and then reboots from time to time. This seems to be happening after sending SMS messages, but not always. I did have this problem before with the stock OS, so probably not Lineage specific but as it's still happening, I'm guessing a setting somewhere that needs to be looked at?
Thanks
Click to expand...
Click to collapse
The LineageOS [st]advanced[/st] reboot menu on my S4 Mini doesn't work at all, a long press of the power button performs a soft reboot, rather than opening the options, when "advanced restart menu" is selected in Developer Options.
Also, selecting "kill app back button" long press option soft reboots the device when the foreground app is killed and I land on my home screen. Long pressing back while already on the home screen on its own also performs a soft reboot, btw. Rather than simply restarting the launcher.
Both options need to be unchecked for me and I now use different methods(3rd party apps) to achieve their results.
Maybe your issue is related? Try unchecking those two options and re-testing...
*Edit: Even without Advanced Restart Menu checked, my device only ever performs a soft reboot, regardless of which option, even Power Off, is chosen. Just tested.
I usually use NEO Power Menu for Xposed, anyway, but disabling these and retesting still produces only a soft reboot, for every option.
Thanks for those ideas, on my phone I have 'Advanced Restart' checked and it's working, or at least the option to boot into recovery does. The 'kill app back button' option was unchecked. I've changed my sms app to Signal to see if it makes any difference.
I did read somewhere else outside XDA about some call settings that could be changed, but I can't find that link any more.
* Update to clarify my above posts; I've resolved the Power Menu issues I was having on 14.1 to be related to Substratum Legacy System overlays. Uninstalling Substratum overlays on my device returns the full functionality of my reboot menu and Power button.
It does not, however, fix the long-press Back button to kill foreground app issue I mentioned. It still force-closes the System and performs a soft restart on my device, without overlays installed.
I've since went back to the I9195-LineageOS-15.1-experimental build by Arco, which by *far and large*, has simply the best battery life of any custom build I have used available here. The various missing features, in my case, can easily be overlooked, as most can be implemented via various 3rd party methods, and are definitely worth sacrificing in the meantime for such a battery life.
I've thought for months that my hardware has been on its last legs because of really over-excessive battery drain whilst using various different custom ROMs.
Resurrection Remix would be my OS of choice but I really can't justify using that fantastically feature-rich OS any longer on this handset, not after using the above LOS 15.1 build and remembering what it was like not to have to charge my battery every time I was near a power source. It's absolutely great!
* Sorry for the off-topic blurb, this was meant to be just a quick update about the overlays/Power Menu issue... :/

can't enable cellular data - Home , recent apps button stopped working

Nexus 6 - stock Android
Android 7.0
Not rooted
Rebooted the phone when the phone seemed hung up. The notifications, home and recent buttons (The circle and square buttons) stopped working after the reboot. Only back button is working. The notifications don't work too. I can't enable the cellular data as well, and Google ID doesn't sync. In short only voice features (calling & text) work.
Interesting,but may not be notable ,is when the phone was rebooted and these functions we're lost, vibrate on key press was enabled.(which wasn't the case before)
I gather through threads here that some have successfully restored home and recent apps buttons as well as notifications by running setup wizard through Nova Launcher. But unfortunately I don't see the SetupWizardUpgradeActivity or setupTestActivity under setupWizard, when I tried to use Nova Launcher.
Has any one seen same/ similar issues with Nexus or other Android devices ?
Complete reset seems to be only other option. I am trying to avoid a complete reset if possible. ( I can't backup to restore after reset due to sync issue - device stopped sync)
Appreciate any help.
Wrong section. This is Pixel XL thread.
Understood. I see a number of pixel device owners reporting similar issues. (It looks like more of a SW issue than HW related). The Nexus 6 threads aren't that active and was hoping to get help from Pixel users if they saw and fixed similar issues.
I think it's called SetupExitActivity. It has no title, at the very bottom

Help with lockscreen issue on lineageos 17 :(

Running lineageOS 17 on a xiaomi mi 9 lite, loving it, but i made a mistake.
I have my phone rooted and have been messing around with edxposed and magisk and i was trying to see if i could enable some sort of face unlock feature through a mod. found one called hidden settings and i started poking around, and i tried to change the value of this one called "lockscreen.options=enable_facelock" through the terminal, hoping it would enable a face recognition header in the settings somewhere, but instead, it had a very strange effect. first, that string no longer exists in android secure settings on my phone, and second, now my phone will not lock through normal means. using the power button, waiting for timeout, nothing, as soon as i wake the screen, the padlock icon is already open and the screen swipes itself up and goes to my unlocked home screen as though it had recognized my face and unlocked itself...only it didn't, because even trying this with my thumb over the camera has the same result.
anyway, i don't know what to do, but i need my phone to lock. so far the only thing ive tried that works is to use the lockdown mode button in my power menu, but that's a hassle. anyway, any help would be appreciated, my goal is to avoid a factory reset as well.
thanks in advance
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
kurtn said:
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
Click to expand...
Click to collapse
actually it was simpler than I thought...turns out nothing was broken at all. in fact one element was functioning better than i expected it to. a while back i was messing around on my previous phone, a rooted oneplus 5 running resurrection remix, and i started fiddling with tasker...anyway, at some point i had issues with the native smart lock features so i set a profile in tasker to unlock the phone when the screen turns on as long as i am connected to my home wifi network. apparently when i restored all my apps to the new phone through my google account it saved a ghost of that profile...i didn't catch it because it wasn't listed in the tasker interface, so i assumed none of my old automations had transferred. i figured it out when other old profiles started to activate, and eventually i remembered that i hadn't set any of that stuff up on this phone yet :victory::laugh:
in any case, thank you for the input...to be honest i would rather have a less experimental setup, but the mi 9 lite doesn't have much development yet so i'm choosing the best from what is available.

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.

Categories

Resources