Database Users

Difficulties with this phone.

My main phone for the past year and a half has been a Huawei mediapad x2. Tmobile had the black Friday trade in deal for this phone, so I turned in my very unreliable note 4 and hoped to have a very nice, very affordable 2nd phone, with LTE to boot (mediapad only gets hspa +)
Fast forward a couple days and I have a lot of issues with this phone. With the stock app load out plus Facebook messenger and pie Control, I get an error every time I try to give permission to an app that a screen overlay is detected. Running marshmallow on the mediapad did not give this issue. Both of these apps are mandatory for me, but the error forces me to turn off drawing over apps any time I want to set a new permission. Very inconvenient. Is there any stock tmobile app that might be causing a conflict?
Second, piecontrol seems to think the edge pixels on both sides are dead pixels, as does Swift key, making typing a p a real chore. Are the edges supposed to respond to touch?
Finally, YouTube freeze frames when I change orientation or pop out of and back into the app. Not even the thumbnail, it just freezes up on a frame and won't resume proper playback until I pause the video, leave the app, come back, and resume it.
Any advice on any of these issues?

I've noticed that if I have a chat head open, it says to turn off screen overlay. Once I close out of the chat head, it allows me to give permission. I'm sure the same can be said for any app that is currently laying over the top of another app. Try closing whatever is on top and let me know. For what it's worth, once Nouget is released, you won't have that issue anymore. I'm currently running the beta of 7.0

Closing out the chat head unfortunately did not fix my issue. Is there any other ways to work around this?

Snap despite drawer also causes the overlay issue.
I do not think any of the problems posted are related to the phone.
Sent from my SM-G935T using XDA-Developers mobile app

I'll look into exchanging it then, it struck me as odd that a top tier phone like this struggles with YouTube, which I must have.

I exchanged the phone for an identical device. Every issue persists as before. Of the issues I mentioned, the app overlay detected is grueling and the YouTube issues are highest priority to deal with. Is there any sort of app I can use to collect feedback, or would providing a list of all apps on the phone help?
If it matters at all, I have the newer coral blue variant, I don't know if that could possibly have different software than the ones that launched earlier this year.

All games lag after a few minutes, app switcher fixes lag temporarily

So I don't know when this started happening but almost every single game on my Galaxy S7 lags after about a minute of playing, like the frame rate will get cut down from 60fps to a choppy 30-50fps, and stay that way unless I exit to the home screen and back into the game or press the app switcher button for a second and go back into the game, then it jumps back to 60fps for a little bit and the lag goes away but it always comes back.
I have no idea what's causing this problem and I'm tempted to factory reset my phone to see if that fixes it because I've tried almost everything (disable game launcher and tools, disable the packages, game mode, high performance mode, delete cache, rebooting, etc.)
Does anyone else have this problem and could it be a certain app using resources in the background that's causing lag? I'm on the stock rom from at&t, no root and no bootloader unlocked, everything is pretty much vanilla.

Finally after months of trying to figure this out, I fixed it by pure luck.
Every Galaxy S7 user should do the following:
1. Download Game Tuner
2. Create a custom profile
3. Set FPS to 60
NOW ON TO THE MOST IMPORTANT STEP!
4. Set HW Performance to +4
HW Performance affects the stupid throttling that games seem to do that prevents smooth 60fps in an effort to preserve battery life and keep heat down I'm guessing. Setting it to +4 fixed all the lag I was getting in every single game.

Need Help Finding Root Cause of UI slowdown

Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.

I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.

Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.

Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.

Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.

Daydream View Controller Bugged?

I'm not entirely sure what caused it, and I've tried everything I can think of to reset it but nothing seems to work. My Daydream View remote/controller doesn't seem to do anything but recenter when holding any button, and does nothing when pressing any button.
When any VR app starts Daydream kicks in and hijacks it, even if it's not a Daydream app (including players), even if Daydream is disabled and all its data wiped (VR services is still there), it asks you to hold to home button while pointing forward to recenter begin. Except that doesn't work anymore so no VR app works.
At this point so it doesn't hijack non-Daydream apps I'm going to try uninstalling VR services so it ****s off. But if anyone can point me to how I can get the Daydream controller working, I'd be grateful.
Edit: Wiping VR services and reinstalling it seems to have it working so far. That couldn't have been done without root, I guess any average user who runs into this problem is SOL, just like the few search results of similar issues I found. Always root your phones kids.
But honestly, for non-Daydream usage, it's better off to uninstall all of it so your battery doesn't get lit on fire. Removing all of Goolag's BS will result in the phone running whatever VR video or app normally instead of having their Daydream/VR services running + NFC + Bluetooth + GPS + other BS they have running which makes the battery hit 50 ****ing degrees Celsius in 20 minutes rendering "Daydream" useless.

Cyrus D. said:
I'm not entirely sure what caused it, and I've tried everything I can think of to reset it but nothing seems to work. My Daydream View remote/controller doesn't seem to do anything but recenter when holding any button, and does nothing when pressing any button.
When any VR app starts Daydream kicks in and hijacks it, even if it's not a Daydream app (including players), even if Daydream is disabled and all its data wiped (VR services is still there), it asks you to hold to home button while pointing forward to recenter begin. Except that doesn't work anymore so no VR app works.
At this point so it doesn't hijack non-Daydream apps I'm going to try uninstalling VR services so it ****s off. But if anyone can point me to how I can get the Daydream controller working, I'd be grateful.
Edit: Wiping VR services and reinstalling it seems to have it working so far. That couldn't have been done without root, I guess any average user who runs into this problem is SOL, just like the few search results of similar issues I found. Always root your phones kids.
But honestly, for non-Daydream usage, it's better off to uninstall all of it so your battery doesn't get lit on fire. Removing all of Goolag's BS will result in the phone running whatever VR video or app normally instead of having their Daydream/VR services running + NFC + Bluetooth + GPS + other BS they have running which makes the battery hit 50 ****ing degrees Celsius in 20 minutes rendering "Daydream" useless.
Click to expand...
Click to collapse
I guess you can uninstall the updates wthout root, then update. or download an apk and reinstall it. But yeah, not as surefire as root

Choose an username... said:
I guess you can uninstall the updates wthout root, then update. or download an apk and reinstall it. But yeah, not as surefire as root
Click to expand...
Click to collapse
That was the first thing I did since it could be done directly without an app like Titanium Backup (which is what I ended up using), but that didn't work. Fixing the bug required a full uninstallation of Google VR services.

Randomly low performance?

Hey I just got my Z4. Upgraded from a Z2 Play. I bought direct from Motorola off their website. I'm having really strange 2D performance issues, and was wondering if anyone else is having similar issues because they seem outright stupid for a phone as beefy as this one is to be doing this.
OK, so, this is going to sound super vague because I did try to nail it down with a ctrace, but wasn't able to come up with anything conclusive.
Sometimes, when drawing 2D only, my phone will drop to 30fps or lower. This happens in both in the launcher/normal apps and games (Fire Emblem Heroes)
However, when the phone is drawing in 3D (Dragalia Lost) the phone never drops below 60fps, ever, for any reason.
I have tried the developer option to force 2D Drawing on the GPU. This does not change the behavior at all.
This happens regardless of what MotoMod I have attached (None, Car Dock, Projector, 360 Camera)
This seems really weird to me. The phone isn't getting hot. It happens both plugged in and unplugged. Fresh reboots and not. What's interesting about this is it's exactly the opposite of my Z2 Play, which Dragalia F***ing hated (It would run fine for anywhere from 5 to 30 minutes, and then it would crash) but FEH would run fine on, and never ever have issues, ever, even if the phone hadn't been rebooted in like, 3 months. And the Z2 Play is just generally a weaker, crappier device in every way (Except Ram, I had the 64gb/4gb model of the Z2 Play) than the Z4, I kind of "expect" the Z4 to just do everything the Z2 did but better.
I'm not a particularly heavy user (I upgraded from my Z2 Play because the battery was expanding, not because it was insufficient) and both of the games mentioned are the only things I do on my phone that could be considered to "Push" the phone in any way (Push in quotes because Dragalia and FEH are both REALLY light games.)
Has anyone else noticed any strangeness like this?

I have the same issue, and yes, it's really hard to describe and difficult to determine what causes it.
What it actually looks like to me is that the digitizer randomly goes into a powersaving mode and samples input at a lower frequency. When scrolling through any app, if you hold your finger down, it'll make it look like it's running at 30fps or less. But if you fling a page that can scroll, for the most part the scrolling animation will be full 60fps.
I know for certain that if you reboot the phone, you're more likely to trigger it soon after boot. But, if you suffer through the agonizing experience, the phone will eventually fix itself for the next week or so before it happens again.
Here's the weird part, not everyone is affected by the weird performance. My theory is most people can't detect it or don't care, or there's a particular app that is prompting the digitizer to behave badly. No idea what it is though.

damentz said:
I have the same issue, and yes, it's really hard to describe and difficult to determine what causes it.
What it actually looks like to me is that the digitizer randomly goes into a powersaving mode and samples input at a lower frequency. When scrolling through any app, if you hold your finger down, it'll make it look like it's running at 30fps or less. But if you fling a page that can scroll, for the most part the scrolling animation will be full 60fps.
I know for certain that if you reboot the phone, you're more likely to trigger it soon after boot. But, if you suffer through the agonizing experience, the phone will eventually fix itself for the next week or so before it happens again.
Here's the weird part, not everyone is affected by the weird performance. My theory is most people can't detect it or don't care, or there's a particular app that is prompting the digitizer to behave badly. No idea what it is though.
Click to expand...
Click to collapse
It's definitely not the digitizer though! I have some data! Fire Emblem Heroes has an autobattle mode, This is as likely to happen during an autobattle when I am providing no input (Phone sitting on desk/just watching while holding) as it is when I'm scrolling through my list of apps.

Same problem here, pretty sluggish experience compared to my girlfriend's G7 Plus.

I've noticed that since the latest update, this issue has gone away for me. Anyone else confirm?

I don't think it was the update, but certain apps seem to exaggerate performance issues. I fixed mine by marking Pokemon Go (the only 3d game I play), as "Restricted" under battery usage settings.
I've been testing this configuration for about 2 days now and it looks like that solved it.

Just to set the record straight, the Android 10 update fixed the random performance problems that have plagued the device so far. There is some hitching right after a reboot, but if you let the phone settle, it's fine until the next reboot.