Related
I'm sorry if this has been discussed at length already, looked through a number of pages and didn't find much.
I bought this phone last August (07) and at the time, it was pre-loaded with WM5. It wasn't until a few weeks ago that I realized that you could update it to WM6. Upgrade was smooth enough, got the GPS to work (sweet) but at times, this phone just stops re-sponding all together. You have to tap a button seveal times to get a response and writing an email when it is like this is beyond frustrating. Then it works fine for the rest of the day. No real predictable time that it happens, seems to be very random. Sometimes after I plug it into my computer it will do it for abit after I unplug it. I don't have many programs running. Seem to have about 30-40% memory available at all times.
So in short, at random times it REALLY slows down to the point of uselessness and then a half our later it's fine.
Is this normal for WM6? If so I have to say the pros don't always outweigh the cons.
I would say that is not normal well at least my experience hasn't been that way
If you have updated since then there has been a 6.1 release for the phone.
Just looked at it again more closely, would appear I'm already at 6.1.
When i press the power button, there's a 0.5s delay before the screen turns on. Is this normal, or just with mine?
You flashed it with anything or running stock?
Sent from my GT-I9000 using XDA App
running JM2
Any custom kernels for lagfix / oc?
Sent from my GT-I9000 using XDA App
Nope, just flashed jm2, and rooted, nothing else.
Dunno then, might be normal. Its even worse with the lagfix kernel.
Sent from my GT-I9000 using XDA App
Hmm ok, thanks for you fast reply's!
OMG! are you guys for real!
this is >insert slur here<
a fraction of a second for the screen to turn on from off is normal on any phone device.
....
Don't label me with the same brush as the op. I was trying to ascertain if he had the startup lag from the custom kernel used for the lag fix with samset. I said it was probably normal - I refrained from calling him an impatient fussy so and so. Abuse him all you like, leave me out of it.
Sent from my GT-I9000 using XDA App
How is this normal on any device? as my touch diamond didn't have it, my ****ty nokia 5800 didn't have it, my htc artemis, htc tytn II, do i need to continue?
It's 0.5s-1.5s. But mostly 0.5s, that's why i said that.
If you don't have a solution, just don't post , i flashed jp3 to try it out, and the delay i've got from jm2 is gone. Hmmm, guess the delay wasn't normal after all.
Damn, i feel like i'm on a chatbox with 12-year old's.
And no, i don't mean Bynar010 to be clear.
Hello all.
This wake up lag is killing me, coz its 1.5s most of the time.
I did apply the lag fix kernel, and that was worse at times. So now i simply reflashed it (JM5 now) and removed the SD card.
Is there anything else I gotta to to remove this fix, or re-flashing removes it ok?
Thanks in advance
I am also having this problem. It can be anywhere from half to three seconds . I have just flashed to jm5 and applied the one click internal lag fix. Anyone know what I can do to fix this. Thanks in advance.
Same problem here on JM2 + 1 click lag fix. I previously use JM2 + memocan and not found this problem. Wondering why others with 1 click lag fix didn't realize this since it's very longer (mine's about 3 sec).
3 second is nothing...
just pressing the POST button to this took more than 3 sec
In that case not only this phone sux, but your internet connection isn't much better..
Please just reply if you can help us with this problem. I like the phone, but the power-on delay is just annoying. I use it instead of a watch too. Wouldn't you care if you had to look at least 3 seconds at your watch before you could see the time, EVERY time you looked?
As i said, this is just annoying, other phones i've owned didn't have a delay like this, not even the WM ones.
i don't know about you, but the last WM phone and PalmOS phone i've had took at least 1 sec to display
yes i use my phone as a watch as well, i don't carry a watch with me
Just to throw it out there, mine lags about 0.25 to 0.5 seconds on average. I'm on JM5 without root.
Do you mean lag when you press the power button to unlock your phone, or when you switch on your phone? It's of course normal during switching on the phone. But I also experience a lag when unlocking the phone (~1 second). It only happens when I haven't used the phone for 5 minutes or more. Doesn't happen if I lock it and immediately try to unlock it again. I believe it's the chipset waking up from sleep or something.
@ AllGamer:
The ones i had: HTC: S100, Artemis, Kaiser, Touch Diamond.
They all went on faster. I didn't have the problem at first (with stock firmware), guess it started after my first flash (to jm2), but the problem stays when i flash back to the stock firmware, that's the strange part..
@ ssj4Gogeta1:
I mean the delay when you press the power (or home) button when the phone is already powered on, and it happens everytime, even when i press the power button, wait 5 seconds, and press it again. Nowdays, it's at least 1.5s every time.
Lol, would be great if i meant the power-on time.
the thing is, all phones i've had, will go slower and slower the more apps i install into them
the same applies to SGS.
to keep them fast, i always only install apps that i'm really going to use.
i used to clam every single piece of software i can put my hands on into the phone before, that always lags the phone to death.... although so far the SGS is holding quite well
still testing out a lot of software, but once i'm done i'm going to stream line it with only the stuff i want in it.
Regarding the delay with the Home button, that is not the same as Power button.
See now we understand you better, it does takes a split second after you wake up the phone with the home button.
however anything longer than 1 sec is not quite right, if you have that sort of lag, try optimizing the phone.
recent firmware updates like JH1 or JH2 depending where you are, have made vast improvement on performance
in the worse case scenario you can try the one click lag fix from the Dev section of the forum
are you still on the stock firmware?
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.
I'm not sure if it's because I'm rooted or what, but I noticed most basic games lag really bad on my phone, like fallout shelter for instance it locks up for a few seconds every couple of seconds and it's pretty annoying... Any ideas?
KyleBryant said:
I'm not sure if it's because I'm rooted or what, but I noticed most basic games lag really bad on my phone, like fallout shelter for instance it locks up for a few seconds every couple of seconds and it's pretty annoying... Any ideas?
Click to expand...
Click to collapse
Since I've had this phone I have had some performance issues with games and apps. Some of them were very strange (Ie: certain graphics or images showing up as black boxes.) Most of these were fixed via app updates. Still having some strange issues with certain apps being cutoff at the bottom (ie Snapchat just had a black bar on the bottom which makes it hard to send a message because you cannot press the send button.) I am now a month and a half into this phone. I am experiencing lag even while scrolling through apps or switching apps. I am also experiencing strange delays with the keyboard popping up when I touch a text field. It's hit or miss. Overall I still love the phone.
Side question. How did you root?
Sent from my Moto E (4) using Tapatalk
I posted a guide to rooting here https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
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.