Develop Bugs

Galaxy S3 i747m HOMESCREEN BUG..

I realized that the homescreen has some bugs especially if you disable the lock screen from settings..
It happened a few time in the past few days..
When I click the home button, the device is on, and I do not need to unlock it since the lockscreen is disabled.
Sometimes, after turning the phone screen on, all my homescreen widgets and the bottom shortcut bar(phone,contact,message,menu) would start to flashing like crazy...
The phone is still responsive, e.g. opening menus, change settings, top menu bar still slides down and up fine, everything is fine operationally except for the flashing widgets and bottom shortcuts..
I turned the screen off and back on, same flashing is present..
I have to power off the phone or restart the phone and it will return back to normal..
I believe this is definitely a software bug... Anyone familiar with this bug?

Are you running stock or are you rooted with a custom recovery?
Sent from my SGSIII with the XDA Premium App

All Stock on my GS3
No recovery mod.
Rogers Samsung Galaxy S3 i747m
Stock Samsung ROM: May 23 build Android 4.0.4 (Rogers Wireless)
My screen lock is turn off btw.
UPDATE:
Also I found out exactly what is triggering this issue..
It has to do with the Developers Options under the Do Not Keep Activities and Background Process Limit..
I am experiencing this issue only when I tick Do Not Keep Activities, and set the Background Process Limit to No Background Process...
Also, today another issue showed up with the same 2 settings ticked Do Not Keep Activities, and set the Background Process Limit to No Background Process.
Basically what it happened is that when I turn on my phone, and open windows such as messages and settings, the phone would automatically attempt to close it down after 2-3 seconds... Also due this time, I received a message, my message tone changed back to the bird chirp default message tone rather than the Pure Bell message tone I setup previously.. When I manage to open the sound settings, I took a quick look and it was still set to Pure Bell, and after a second or so, the phone closed the entire settings window down...
I just press hole the power and click on Restart...
Now the phone reboots, and the phone is back to normal...
When I went back to sound settings, all my own settings are still there
BUT
When I went to the Developer Options, the setting for Do Not Keep Activities, and Background Process Limit where back to the default values.. (Do Not Keep Activities is not UNTICKED, and Background Process Limit is set to Standard Limit automatically by my phone after the reboot.)
I thought it was weird how the phone changed my settings after reboot, and the OS acts weird before I rebooted...
After using it through out today with the default settings for Do Not Keep Activities, and the Background Process Limit, my phone is acting fine.....
Pretty sure this is a SW bug, it is not a HW problem..

I think it did exactly what it should do with those developer options enabled. That was a very aggressive setting use used and does not represent normal operation of the software.
Sent from my Red S3

So this is a known issue?
Yes, pretty much Developer Options are pretty unstable...
The only setting I kept for are Mock Location (for those apps that use GPS without my permission) and the Animation options to 0.5x so the animation is faster.
Turning the Mock Location and Changing Animation Settings do not seem to affect the stability of the Stock ROM

Why on earth would anyone with a phone this powerful want to use those two options anyways!? I would say yes u have those problems with those options on... you have plenty of resources so don't do that to your phone and yes those are "developer options" and typically only temporary testing scenarios for "developers" just leave at default and be happy with much better working phone!
Sent from my SGH-I747M using xda premium

I use those 2 memory clearing options just to extend battery life.

[Q] screen flashes the "default" lock screen when using viber

Do you guys use Viber? Whenever I have viber on, the screen seems to try to go to the "default" lockscreen. this doesn't happen all the time, but frequently enough to be really annoying. (for me, it happens probably once every few minutes. the most frequent place that this occurs is when you have the viber pop-up turned on (so you can reply viber messages while in lock screen).
my launcher is Go Launcher and the lock screen is Go Locker. I don't have another android phone to test this to see if it's a galaxy phone issue, note 2 issue or viber issue in general. Have others experienced this issue?

[Q] Lock screen and messaging issues

Hey guys,
On my OGP, I have noticed that once I press the side button to unlock the screen, the touch keys light up instantly but the actual screen takes 1-2 seconds to light up after the button press. It may have gotten worse over time, or that may just be me being paranoid. Also, in messaging settings I experimented with messaging skins, and those seemed to lag my messages a lot (like when I clicked on a conversation, it took 2-3 seconds for the conversation to load, whereas before it was instant). When I removed the skin and went back to the default one, the lag still persisted. If anyone knows how to fix these issues, I would be grateful! My device is stock unrooted with value pack update, US AT&T. Only settings I changed was turned on quad core optimization.
Thanks,
killer

Fixed the lock screen lag by removing my dewdrop screen animation. Leaving it at basic drastically increased speeds to easily under a second. Now for the messaging lag...

Does your pulldown randomly stop working?

Every once in awhile, my notifications pull-down won't pull down.
If I lock the phone, then unlock it, the pull-down starts working again.
It's been like this through multiple clean OS re-installs.
Am on Magisk 17.3.
I've had more software bugs on the PXL3 than any other phone before, including the PXL1.

I have the same damn problem. It just doesn't work all the time. I also had the issue of bright white screen on double tap to wake. So, I called Google Support for this, and the guy on the other said made me clear the cache of the phone app, force stop it, turn the phone off for 2 mins and then restart for both issues. I even asked him how this relates to the fingerprint sensor not detecting, he replied some stuff that, phone app controls the vibration and the display waking up.
Of course both problems does not occur for me frequently, so after that procedure I did not encounter the white screen problem, but fingerprint gestures were still kinda hit and miss. Although they work pretty good now, less miss count. For me they work when I swipe just the edge of index finger lightly, also if finger is very dry, it doesn't detect.

I tried the pulldown five times while this logcat was running.
I'm on Nova Launcher but think it happened on stock launcher too.

Help with lockscreen

I need help with g3 d855 and all aosp and lineage roms. G3 do not have fingerprint sensor so for me pattern lock is obious only solution. Stock g3 have notifications and lock screen immediately when screen is on but AOSP roms you have to swype first then pattern then clcik on something.
Now, problem is when you set "show pattern directly", then pbroblem is that you have to unlock it first to see time or notifications and second problem when mail or message come, screen would be on for as long as you set screen on time. For me is 2 minutes. That is very battery draining.
Custom lock screens have also that problems, everything is great, but when mesage come screen is on for two minutes instead 5 seconds.
Is there any other solution, like on stock, pattern lock.