I've been trying to isolate the cause of random restarts on the Warp, since the B08 update doesn't seem to have reduced their frequency.
One angle I've been following is that it could be a problem with my launcher (Launcher Pro). I've gone through and tried to reduce its memory use (turned off screen caching -- which isn't really necessary on a system as fast as the Warp, unchecked the "keep launcher in memory" and "try to prevent forced closes" options, but no joy yet in terms of reducing the restarts.
It would be interesting to know what launchers people are using? Is anyone experiencing this issue with stock launcher, or is it more common with some alternative launchers than with others? Feel free to reply to this thread with your experiences with the stock and non-stock launchers.
The other area I'm starting to think about is the correlation that many people have mentioned between browser use and restarts. Usually, though not always, I'm either using a browser or have done so in the last few minutes when the restart occurs. But what occurred to me just now, when it happened not on my phone but on my Honeycomb tablet, is that it happens a lot when I'm using a newsreader or twitter client and click a link from within that app that results in a browser opening to display the page. That initial page load works fine, but I frequently (on both the Warp and my tablet) end up with a frozen system followed by a system restart if, instead of returning immediately to the original app, I browse to another page or otherwise continue using the browser window.
One way or the other, I'm convinced it's a memory management problem. Both the Warp and my tablet have 512MB memory, compared to the 1GB on a lot of more high end systems, and I suspect that both systems have heavily tweaked the OS's memory management routines to try to extract maximum performance from a relatively limited memory space.
If that really is the issue, the ultimate answer needs to come from ZTE's engineers, but in the meantime maybe we can assemble a knowledge base of usage patterns or apps that seem to increase or reduce the frequency of the problem, and even come up with best practices guidelines for minimizing the problem.
One angle I've been following is that it could be a problem with my launcher (Launcher Pro). I've gone through and tried to reduce its memory use (turned off screen caching -- which isn't really necessary on a system as fast as the Warp, unchecked the "keep launcher in memory" and "try to prevent forced closes" options, but no joy yet in terms of reducing the restarts.
It would be interesting to know what launchers people are using? Is anyone experiencing this issue with stock launcher, or is it more common with some alternative launchers than with others? Feel free to reply to this thread with your experiences with the stock and non-stock launchers.
The other area I'm starting to think about is the correlation that many people have mentioned between browser use and restarts. Usually, though not always, I'm either using a browser or have done so in the last few minutes when the restart occurs. But what occurred to me just now, when it happened not on my phone but on my Honeycomb tablet, is that it happens a lot when I'm using a newsreader or twitter client and click a link from within that app that results in a browser opening to display the page. That initial page load works fine, but I frequently (on both the Warp and my tablet) end up with a frozen system followed by a system restart if, instead of returning immediately to the original app, I browse to another page or otherwise continue using the browser window.
One way or the other, I'm convinced it's a memory management problem. Both the Warp and my tablet have 512MB memory, compared to the 1GB on a lot of more high end systems, and I suspect that both systems have heavily tweaked the OS's memory management routines to try to extract maximum performance from a relatively limited memory space.
If that really is the issue, the ultimate answer needs to come from ZTE's engineers, but in the meantime maybe we can assemble a knowledge base of usage patterns or apps that seem to increase or reduce the frequency of the problem, and even come up with best practices guidelines for minimizing the problem.
That's not what I want to hear...I love Launcher Pro. But I have to admit I've been having the same kinds of problems myself. It freezes about 50% after a system restart -- I have to wait until the Warp gets around to displaying the Force Close box before and Launcher Pro restarts before I can do anything.
