Galaxy A05 Resolution Bug After Reboot: Scrcpy Issue

by Admin 53 views
Galaxy A05 Resolution Bug After Reboot: Scrcpy Issue

Hey guys, I ran into a super weird issue with my Samsung Galaxy A05, and I'm hoping you can help me figure it out. I use this phone as a secondary device for some not-so-important stuff, and I usually control it from my PC using scrcpy. The touch functionality is busted, so scrcpy is the only way I can use it. But now, after a reboot, the phone is displaying an incorrect resolution, and the screen won't turn on. Let's dive into what's happening and how we might fix it. This is a head-scratcher, so buckle up!

The Problem: Incorrect Resolution and a Dead Screen

So, I was using my Galaxy A05 (model sm-a055m, running Android 15 with One UI 7) earlier today, and things felt a bit sluggish. I noticed the battery was draining faster than usual, which is never a good sign. Thinking a restart might help, I went to reboot the phone. However, instead of using scrcpy's built-in restart option (which I usually do), I made a rookie mistake. I asked an AI chatbot for the command to power off the phone. Long story short, I ended up running adb shell reboot -p while scrcpy was active. Oops!

After the phone powered back on, that's when the real trouble started. Scrcpy was reporting an incorrect resolution: 1080x2408. This is a problem because the actual screen resolution of the Galaxy A05 is 720x1600. Because of this resolution mismatch, the phone's display just won't turn on. It's like the phone is trying to display something it physically can't, causing the screen to remain black. The phone is on, but I can't see anything. I'm completely in the dark, and all I can do is hope there's a fix.

Running adb shell wm size confirms the issue. It reports "physical size 1080x2408." I tried to set the correct resolution using adb shell wm size 720x1600, but even after that, when I re-check with adb shell wm size, it still shows "physical size 1080x2408 override size 720x1600." It seems like the phone is stuck on the wrong resolution, and I'm locked out.

This is a frustrating situation, especially since the phone is essential to some of my daily routines. I am also worried about potential data loss, as I have important files on the device. Let's see if we can get this fixed. This bug is particularly annoying because it prevents me from even seeing what's going on, making troubleshooting a nightmare. Hopefully, we can find a solution that doesn't involve factory resetting the phone, as I'd prefer to avoid that if possible.

What Could Have Gone Wrong? Possible Causes and Troubleshooting

So, what in the world could have caused this resolution issue? There are a few possibilities, and we can explore some troubleshooting steps to try and resolve the problem. I'll break it down into a few potential causes:

1. ADB Command Mishap:

My initial blunder, running adb shell reboot -p while scrcpy was active, might be the root cause. This command issues a power-off signal, and while it shouldn't mess with the resolution, it's possible that something went wrong during the reboot process. Perhaps there was a timing issue, or a conflict with scrcpy's connection. It is important to remember what happened before so that the process can be properly reverted. This is a strong suspect due to the timing and the fact that the issue started immediately after the reboot.

2. Display Driver Corruption:

Another possible cause is the corruption of display drivers or related system files during the reboot. If the system couldn't properly load the display drivers during startup, it might have defaulted to an incorrect resolution. This could happen if the reboot process was interrupted or if there were temporary glitches in the system files. Display drivers are responsible for telling the phone's hardware how to render what's on the screen, and problems here can lead to various display issues. The error message is not super helpful, but it provides a good starting point for investigation.

3. Software Bug:

It could be a bug in the Android version (Android 15), One UI 7, or even a conflict with scrcpy. Perhaps the interaction between these elements led to an incorrect resolution being set during the reboot process. Software bugs are a part of life, and sometimes, unexpected interactions between different pieces of software can cause chaos. It is really important to know where the problems come from, so we can know how to properly solve them.

4. Hardware Problem:

In some, albeit less likely, scenarios, there could be a hardware problem, such as a damaged display controller, which is responsible for controlling the screen. This would be a more serious issue, as it could mean a hardware repair is needed. However, since the problem arose suddenly after the reboot, a hardware issue is less probable. It's still good to consider this, though, since hardware problems can sometimes manifest in unexpected ways.

Troubleshooting Steps:

Here are some things I plan to try to get the phone back up and running. I'll update with the results:

  • Restarting ADB and Scrcpy: This might seem simple, but restarting the ADB service and reconnecting with scrcpy could potentially reset any temporary states or errors that might be causing the resolution issue. Make sure that both the ADB and scrcpy connections are in good working order. Try disconnecting and reconnecting the phone as well.
  • Forcing the Resolution with ADB: I'll try setting the resolution again, and then rebooting the phone from adb this time to see if the change sticks. The commands are: adb shell wm size 720x1600 and then adb reboot. It is really important to remember to reboot after these commands to apply the new settings.
  • Checking for Updates: I will check for any available software updates. While unlikely, there's a chance that an update could fix the issue or provide a workaround. Keeping the phone updated is essential for both performance and security.
  • Trying a Different Scrcpy Version: Since the problem started after a reboot, I will see if there is another scrcpy version I can use. This will eliminate the possibility of a version-specific bug.
  • Factory Reset (Last Resort): If all else fails, I'll consider a factory reset. This is the nuclear option, as it will erase all data on the phone. Backups are critical, which is why I'd like to avoid this. If nothing else works, this will be the final step. I may lose all my data but can possibly retrieve a working phone.

Seeking Help: What to Do Next

I'm reaching out to you guys because I'm a bit stumped. This is a weird one, and I could really use some expert advice.

  • Community Forums: I will post on forums like XDA Developers and Stack Overflow. There's a good chance someone has encountered a similar issue and knows a fix.
  • Genymobile: I will try to reach out to the scrcpy developers to see if they've encountered this issue before or have any suggestions. It's possible that a bug or incompatibility with the phone is causing the resolution problem.
  • Android Development Community: I will also consult with the broader Android development community. Their expertise could shed light on possible causes and solutions.
  • Samsung Support: If the problem persists, I might even try contacting Samsung support. They might have a specific solution for this phone model. However, I am not really sure what the result will be here, because I don't think they know this issue.

Any insights, suggestions, or potential solutions would be greatly appreciated. Let me know what you think, or if you've seen something similar before! This resolution bug is driving me crazy, and I'm really hoping to get my Galaxy A05 back to normal.

Update: Additional Information and Troubleshooting Results

Okay, guys, I've done some more digging and testing. Here's what I've found so far, along with any troubleshooting results. This section will be regularly updated as I try different things and learn more.

1. Re-attempting Resolution with ADB:

I tried setting the resolution again using adb shell wm size 720x1600 followed by a reboot. Unfortunately, after the reboot, the incorrect resolution of 1080x2408 was still being reported, confirming that the settings are not persistent. Something is preventing the change from sticking, or it is being overridden by another setting. I also tried setting the display density with adb, but this did not fix the resolution problem.

2. ADB Shell WM Density:

I tried using the command adb shell wm density 320. I was trying to change the display density, which in some cases could influence the resolution settings, but this did not fix the issue.

3. Scrcpy Version Test:

I tried scrcpy version 3.3.2, to rule out a bug in the specific version I was using, but the issue remained the same. So, that eliminates the scrcpy version as the culprit.

4. Boot into Recovery Mode and Wipe Cache Partition:

I managed to boot the phone into recovery mode. From there, I wiped the cache partition. This can sometimes resolve display or software glitches. After the cache wipe and a reboot, the issue persisted, still reporting the incorrect resolution.

5. Factory Reset is not the solution:

I also considered backing up all the files and resetting the phone but I found out that the phone's display is still not turning on even after the factory reset. I'm afraid that the problem is not a software bug but a hardware issue. The phone is likely beyond repair. I am currently trying other methods.

6. Contacting Samsung Support and Other Forums:

I've reached out to Samsung Support and posted on XDA Developers to see if anyone has any ideas. I'm waiting for responses from both sides. This is an important step to see if this is a known issue. It is important to remember what happened before so that the process can be properly reverted.

I will keep you updated. Keep the suggestions coming!