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

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.

Related

[Q] ATT One X Display Phone - Strange Issue

I'm very keen on buying this phone tomorrow and was in the ATT corporate store and found a very strange issue on the live display unit. Everytime I opened any app and hit the home button it would take about 5~7 seconds before showing the home screen. I tried playing with the settings but it did not help. I also restarted the phone but the issue still persisted. I new to android platform (coming from iPhone) and looked at the setting (related to personalize). After talking to the ATT rep he mentioned that few folks have also complained about it but was not sure why this happens. He then suggested that they will return this unit so battery can be replaced or we can reset the phone to factory settings. I took his permission and attempted the reset After reboot the phone worked normally with absolutely no lag.
Q1. Is this a known issue? Are folks with this phone experiencing this after a extended time of use. Does anybody know what this lag might be due? Any specific wallpaper causes this lag. I tried changing wallpaper but it did not help
I really want to get this phone but if the above issue is rampant then I want to hold off buying it tomorrow.
BTW: I tried buying it today at target (mobile store managed by radio shack) they were ready to sell and went thru the upgrade process but just before the last screen it blocked them from selling (radio shack corporate policy) cannot sell the phone today but will sell it tomorrow.
Settings -> Developer options -> Don't keep activities.
Some people have had to switch it on, come out of options, go back and switch it off. (the tick was incorrectly cleared, whilst the option was on)
thanks
Thank u for your feedback. Can u elaborate on what caused it? Sorry from your feedback I could not figure out the cause.
From what you described (7 second delay coming back to sense) it's not a lag (or sense crashing as some have described it). It's sense reloading.
The Android UI is based on activities, they stack, and the history is typically kept, until Android decides to kill an activity, usually due to low memory available. If activities are not kept, they have to reload from scratch.
Since Android can take away a previous activity at any stage, the developer must save its state when transitioning to a new activity. By not keeping activities, it's easier to test that each activity is correctly saving its state.

5 Issues with Lineage OS on Samsung Galaxy S6

Hi All
First time really contributing to this but I feel like some super-duper hacker (not that I know anything!). I'm smart and can play around with things. I actually trained as a lawyer, went into recruitment but am now considering moving into computing! This is fun and you can be involved in projects. However my eye has developed a nasty twitch... Recruitment is dead now anyway. (Any tips on how I can begin getting into programming/app development/ XDA work etc whatever it is would be appreciated, (I literally have no idea where to go but I'd like to!)).
Anyway, back on topic:-
So...I've been up for the past 24 hours with a new laptop and at first rescuing my Samsung Galaxy S6 which got caught in a bootloop with no recovery, (had to hard reset, lost all data), upgraded Android to Nougat. It all started when I went to do a recovery boot to get Magisk to work but it all went haywire. :crying:
Happy to give you a system specs - models - builds etc, if there's a good way of doing that let me know and I'll post so you techies can take a look and see what might be the reasons behind the issues. I'm running a 'bug report' through Developer Options at the moment and can post this if useful? I have a Bug Report that I've generated if this is useful to anyone in getting to the bottom of these issues, let me know and I can send...
Ok, so with no further waffling, the issues I've seen so far in the short time I've had this lineage-14.1-20170307-UNOFFICIAL-Nexus7420-zerofltexx-2 (this is the Zip file that I found for the Samsung Galaxy S6 which I understand is only developmental at the moment, it doesn't have its own one yet?)... (in descending order of importance):-
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
bestfootie said:
Hi All
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
Click to expand...
Click to collapse
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
bestfootie said:
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
Click to expand...
Click to collapse
9. I'll also add in here that call volume and volume in general seem really low.
As a result of these nine bugs I'm going to have to revert back to an older version, quite possibly Stock Android, unfortunately... :crying:

Huawei Y7 Pro 2018 LDN-LX2 mini-review + issues

Approximately 3 weeks ago I got a Huawei Y7 Pro 2018 ( Model: LDN-LX2 ; no English page yet)
Looks like the other similar phones in neighboring markets are the
Huawei Nova 2 (Nova 2 Plus would probably = Y9)
Huawei Y7 Prime
Overall for appx $170 USD it performs well. Coming from Zenfone 2 Max (5000 mAh battery) I have to be more mindful of charging the phone more often.
---------------------------------------------------
Some user interface issues I've noticed so far:
------
1) screen lock internet usage notification is persistent. I turned off all notifications for "phone manager" app but it ignore my request.
2) Some apps will not continue to run in the background even though i give them full permission to run in the background. Google Translate and 1Password are 2 good examples and some music apps seem to also have some issues (see below). Huawei UI/optimization software seems to close background process anyway or otherwise mess with them without user consent.
3) music apps would stop playing music after screen lock + screen off after 7-10 seconds. When you wake the screen back up, the audio will immediately resume. Tried with VLC player and MX Player. Then when I switched to huawei stock music player, no problems. I spend over an hour in MX Player/VLC Player settings menus trying to see why this was happening. Somehow the problem seemed to resolve itself but I don't remember exactly what I did (Google Play update, closeAll open apps, etc). That never happened to me before so it stuck out.
4) Tried to enter recovery mode (hold Vol Up and Vol Down and power button simultaneously from cold start until the Huawei logo flashes with slight vibration). You see the EMUI logo for 2-3 seconds followed by "Software update failed" message. The only option available is "Reboot phone now".
Phone is NOT rooted. I don't know why recovery mode is broken. And why/how recovery mode was broken so easily!?! [you go to recovery mode when regular mode is not working properly ]
5) I cannot permanently disable the Touch-Disable mode. This maybe an issue with XMUI 8.0.0 which took this option away with oreo update. Sometimes I would start my unlock swipe from the top of the phone and then it breaks the swipe with the touch-disable message, forcing me to restart the swipe.
6) I reported some of this to huawei support (via their hiCare app). Their copy and paste reply was
a) clear cache in recovery mode, or
b) factory reset.
If one of these didn't work, then copy the IMEI # and they will assist further. I have sent in the IMEI #s, so we'll see what they say.
q: Does huawei have a forum for its users?
q: Anyone else have similar problems with Huawei device or other android phones?
----------------
Verdict (after 2+ weeks of daily use):
-----------------
This is my first huawei device. I didn't really consider things like update cycles and how reliable the user interface is. It was a budget phone, I needed something quickly as the old phone broke and I was on the move. I was actually looking at the Zenfone 4 Max Pro or Max Plus M1 as I gotten used to Asus and they seem to be decreasing the bloatware over the years.
- It does perform well in that app opening and switching is pretty fast. (no gaming, mostly web surf with multiple tabs, translation software, occasional music or ideo, banking apps). I usually have about 1.5GB ram available at any given time.
- I cannot customize the lock screen apps. The quick setting tiles are lacking, but there is supposed to be a paid app that allows customization.
- Camera is pretty decent. I'm not a camera enthusiast, but for a budget phone the back camera is acceptable. Haven't really tested the front camera too much. I wish the stock camera app had camera/camcorder modes combined so that it only takes one tap to choose which one to begin (you have to switch between camera/camcorder; it's not combined with 1 tap access to either. I've tapped camcorder app thinking it would start recording...but it is just initializing camcorder. You have to tap it again to begin recording.)
- Charging is slower than I would expect from 2018 phone; it takes over 2.5 hours to charge from 3% to almost 100% (1A charger).
- dedicated dual nano-sim slots w/separate microSD card slot :good::good:. Some phones advertise dual-sim but share 2nd sim slot with micro-sd card (note to manufacturers: spend the extra $0.30 USD and keep all the slots separate, eh?).
- startup and shutdown are acceptable 20-25 seconds to home screen and 8-12 seconds to power off.
- scrollshot (scrolling screenshot to capture off-screen stuff in a single image) is built-into the stock screenshot program :good::good:. They also have screen recording which is a nice touch.
- Unboxing: Did NOT come with any case. But it did come with a plastic (not glass) screen protector. Thailand major shops still do not stock the cases for this as it is still a very new variant. Neither did Malaysia. I did find a case that fits 85% and I didn't "have to" cut anything out....but I forgot the model it was intended for. I had to go to 8 shops and I was just glad I found some protection against drops.
The Y9 had fingerprint reader, 4000mAh battery vs 3000mAh, dual front camera (with flash??) and a slightly bigger screen (or better resolution). Plus it came with bonuses (selfie stick, etc). Perhaps the extra $70 USD was worth it? At that price point though, I would look to other brands (e.g. Asus) if the Huawei UI / recovery mode/etc are unreliable.
For most locals the Y7 pro 2018 is very functional. Maybe some of these problems are simple update issues or can be fixed in some obscure settings menu.
-----------------------------------------------------------------------
-----------------------------------------------------------------------
Edit 08 May 2018:
Huawei email support left something to be desired But I did go back to the phone shop that I bought the phone and I was able to prove to them that there is some type of defect with the recovery mode. I did this by using another staff member's Huawei and booting it into recovery. Then to prove it further, we took the floor models of the Y9 2018, Y7 Pro 2018, and Y7 2017 and we saw that only the Y7 Pro 2018 model had the error. This was further proof that I am not crazy.
View attachment 4497426
As a final check, a new Y7 2018 was provided out of the box and we checked recovery. No problems with menu (it was in Mandarin initially, but after going through phone 1st launch setup and changing system language to English US, then restarting phone and activating recovery mode, it was in English as shown in photo).
View attachment 4497427
But here is the thing. The phone's system info menu had the exact same specs as the problem models. The only thing different was the IEMI #s.......WTF?
purchased phone
View attachment 4497429
unbox test
View attachment 4497428
A possible fix
You must do a factory reset within the setting > reset menu. Backup your phone (contacts, settings, etc) and do a factory reset from within the settings > system settings > reset. You can reset without wiping all the internal memory (photos can be retained), but I wouldn't trust that.
Reset took maybe 10 minutes or so, maybe less. The restoring of your files is what takes longer, depending on how many apps and such you had. Then I tested recovery mode (before and after the 1st time startup setup) and it seemed to be repaired.
I still conclude it is a manufacturer defect for recovery mode to be shipped broken or to break so easily. The other problems where I suspect programs are being killed in the background even though they are exempt still exist. The phone overall is still usable, which is a good thing.
note: Huawei recovery boot was reached by holding Volume Up button when phone is restarted or [from power off] Power on phone and press/hold Volume Up button. Hold it until the EMUI recovery menu appears. Phone was NOT plugged in.
Was able to repair the "Software update failed" screen in recovery boot mode. I edited the OP with the details. I have rebooted several times into recovery to test it and it seems fixed. Hopefully for good.
Roms
Im not found firmware LDN-LX2 models by nova 2 lite at anywhere. Have some error while booting up.

System Keeps Crashing

Starting early July, my Pixel 2 XL on stock Google ROM has been crashing constantly. Tried a whole sort of troubleshooting but cant seem to fix it. Looking to see if someone can see something that I dont.
Symptoms
When Pixel 2 XL, on (PQ3A.190705.001, Jul 2019), charging and left alone, the phone would become unresponsive for up to 5 minutes, then proceed to do a soft restart and show the Phone is initializing. No problems when running the phone off the charger.
Troubleshooting
Tried the basic troubleshooting steps from Google Support (Update to latest system update, remove free space, safe mode, factory reset)
Tried reflash June factory image from Google (PQ3A.190605.003, Jun 2019)
Tried different charger
Disabled digital wellness app
Disabled the Private DNS and uninstalled Blockada (heard issues with it)
Nothing seems to work. Google support suggested that I get it exchanged under warranty, however, I feel like it is a software issue more than hardware. This is because when I monitor it under logcat when it stops responding, I see there is a whole bunch uncaught FATAL EXCEPTION so it seems that something is causing it to error out.
I am not too familiar with Android logs so I cant pinpoint it out. If anyone have more expertise can help with taking a look at the log to see what the root cause is, that would let me know what I should do for next step (ie try Android Q Beta if it is a system issue, get a new phone if it is a HW issue, or change certain settings).
Here is the log file
Thanks

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