Related
I've been having a few issues with a couple of games freezing and have also had the phone get quite hot, particularly around the camera end. The two games I've had freeze up a lot are Fruit Slice and Pinball Classic, neither are spectacular graphics wise. Basically the games just freeze up and either I'm ejected to the home screen or I have to power off/restart. Occasionally I do get the "Force Close" box, but not very often, this contrary to what I would expect if it were just a normal bug related issue. sometimes it crashes after 5 mins or so, other times straight away. What makes me think it might be overheating is that once it does freeze up, it will do so again almost instantly if I relaunch. The rest of the phone seems okay in operation, I've run a few benchmarks and stress tests, all run okay so far. However (and it is a BIG however), once the phone has got warm, if I go to adjust my screen brightness I am limited to how high I can raise it and receive the following message: "To avoid overheating, maximum brightness has been reduced" (I've attached a screen print below).
Does anybody else get these issues or that message?
Got that "To avoid overheating..." message too while using Navigon Mobile Navigator inside my car (attached to charger).
In some other post I also read about a message like "To avoid overheating, the charging process has been paused", but this depends on the temperature of the battery only (I think).
Regarding the crashing games, that might be a problem of the game. But I had some crashing games, too, but I could not find a relation to the temperature of the phone.
Anyway, it could still be a heat problem.
In my opinion it would had be better for samsung to make the phone some mm thicker to better deal with heat and including a more powerful battery than just claiming to have the thinnest superphone.
Anyway, its still a great device.
Useful to hear it happens on other handsets, in fact I've now found a few threads talking about the issue happening on other models of samsung phone, such as the Infuse.
On the crashing games front, would you mind trying out Fruit Slice for a bit, to see if it hangs on you? If it dosen't crash after 10 mins or so I would think you're okay.
about overheating
i did experience it
when i left the phone in the car it became very hot and i get the same message
TacticalTimbo said:
On the crashing games front, would you mind trying out Fruit Slice for a bit, to see if it hangs on you? If it dosen't crash after 10 mins or so I would think you're okay.
Click to expand...
Click to collapse
I'll try that as soon as I have it back (and if I remember to test), its currently at the repair facility because of a faulty camera.
EvilGeniusHST said:
I'll try that as soon as I have it back (and if I remember to test), its currently at the repair facility because of a faulty camera.
Click to expand...
Click to collapse
Cheers, really appreiated. Just to update, I played it again just now, managed 3 games before it froze and kicked me out to the home screen; again no crash dialoge asking force close/wait?! I also checked my temp immediatly after it crashed, using Stability Test V1.5, it reported 31c, which dosen't sound too hot from what I've heard...who knows, cheers agian though!
EvilGeniusHST said:
I'll try that as soon as I have it back (and if I remember to test), its currently at the repair facility because of a faulty camera.
Click to expand...
Click to collapse
Cheers, really appreiated. Just to update, I played it again just now, managed 3 games before it froze and kicked me out to the home screen; again no crash dialoge asking force close/wait?! I also checked my temp immediatly after it crashed, using Stability Test V1.5, it reported 31c, which dosen't sound too hot from what I've heard...who knows, cheers agian though!
sorry about the double post
Okay, I've been playing now about 15+ minutes without any problem. The phone doesnt get even hot, just a little bit warm. Using Navigon Navigator it gets a LOT more hotter.
So maybe you should try a factory reset? Or its a faulty phone...
By the way, I had display brightness set to Auto and I'm on german KE7 firmware.
hello so i have a r800x and recently i went to play temple run and the runner was staying to the left of the screen. so i thought it was just the app and re downloaded it but same problem. so i got a device test to test my sensors and the accelerometer was off to the left when i was holding it straight. so i got a friends phone a samsung fascinate and it was fine so can someone help plzzzz...... P.S. i tried a calibrator with no avail so plz help
I have this issue too but only in temple run. Temple run brave and other similar games are good.
Sent from my Xperia Play using xda app-developers app
Its a problem of the xperia play, i checked it on two R800a devices and its the same, on every game or program the accelerometer is tilted to the left.
I have the same problem with the last update of Temple run, I thought that I was the only one with this issue. All the other games don't have the problem so, I think is a bug from the game with its last update.
Don't worry it's just lag, when the system starts to get stressed, the accelerometer will temporarily stop working. If it gets more stressed, it will stop serving touch screen response, ultimately triggering an ANR (application not responding).
It also happens with Running Fred when your device gets stressed by trying to run lots of apps at the same time, etc. But I believe this type of lag is the developer's fault when coding the app.
Sony Xperia Play - Tapatalk 2
thanks
DanielEGVi said:
Don't worry it's just lag, when the system starts to get stressed, the accelerometer will temporarily stop working. If it gets more stressed, it will stop serving touch screen response, ultimately triggering an ANR (application not responding).
It also happens with Running Fred when your device gets stressed by trying to run lots of apps at the same time, etc. But I believe this type of lag is the developer's fault when coding the app.
Sony Xperia Play - Tapatalk 2
Click to expand...
Click to collapse
thanks i think your right mainly cuz the play has so little ram
I think that the heating up issue has been adressed already, so I was just wondering if anyone can recommend
a temperature app that I can use to measure the heating up of the phone.
Also, which temperature is considered "OK", and from where are we talking about "danger zone",
and what can become damaged if the phone gets into the danger zone often?
I found a great game (might and magic clash of heroes), but with the phone heating up,
I find myself cutting gaming short to let the phone cool down a little.
When I say cuting gaming short, I mean 15 minutes tops, anything beyond that and I can make omlets on the screen.
I also found the game stops being responsive (i.e. I'm unable to enter commands properly),
as if the hot screen is somehow preventing accurate control. Maybe it's just the game, maybe it's the phone.
gnjuss said:
I think that the heating up issue has been adressed already, so I was just wondering if anyone can recommend
a temperature app that I can use to measure the heating up of the phone.
Also, which temperature is considered "OK", and from where are we talking about "danger zone",
and what can become damaged if the phone gets into the danger zone often?
I found a great game (might and magic clash of heroes), but with the phone heating up,
I find myself cutting gaming short to let the phone cool down a little.
When I say cuting gaming short, I mean 15 minutes tops, anything beyond that and I can make omlets on the screen.
I also found the game stops being responsive (i.e. I'm unable to enter commands properly),
as if the hot screen is somehow preventing accurate control. Maybe it's just the game, maybe it's the phone.
Click to expand...
Click to collapse
for the app u asked > u can search play store easily
https://play.google.com/store/apps/details?id=src.schimi.temperatureguardfree
https://play.google.com/store/apps/details?id=ccc71.bmw&hl=en
and almost of time thr s no danger for phone with its heat
but if u think u have problem with battery discharging and heat or ... then try to flash another stock rom
:good:
Currently on Stock and there are various instances where my device will either freeze or overheat and turn off. The temperature is about 96 degrees right now where I live and let's say I'm outside for like 15minutes my device will have turned off and refused to turn on unless I cool it down. Is my device a bust? Should I consider changing it?
Sounds extreme, but even in 65F weather my device will overheat and shut down if I'm fast charging + watching video or otherwise moderately using it.
I have temperatures over 30°C here, the phone wouldn't even notice... I played intensive stuff while it was charging (RR3)
Did you unlock the bootloader?/did you do anything to the system?
I realized it was something related to the stock rom. Something was constantly running cause the device to overheat and freeze
reV17 said:
I realized it was something related to the stock rom. Something was constantly running cause the device to overheat and freeze
Click to expand...
Click to collapse
I don't have this issue, other than, occasional hiccups but with chrome. When this starts, I wipe cache because my phone tells me it's stored around 500MB of cache in chrome alone at that point. I usually have to do this every few days... It is very annoying...
In your case I would try that first, if it doesn't work, FDR it. It does indeed sound software related. I know saying FDR is really a cookie cutter solution, but it really could solve this issue.
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.