Greetings,
My problem goes as such: I purchased my X around the time it first came out, back in mid-August. I've used it with a fair degree of satisfaction, though Motorola's bloatware and crap interface annoyed me. As time has progressed though, I've noticed one continuing, impossibly frustrating issue though. For whatever reason, my particular X randomly becomes slow, then extremely unresponsive, sometimes to the point of not registering any touches at all. I've particularly noticed it while using the Swype keyboard, which at first led me to theorize that because of the intensive nature of the program, it was chewing up a large amount of RAM - on my iPod touch, I've seen somewhat similar things if I were to background a few applications and I bumped up against it's 64 MB RAM cache. However, while the lag is predominately seen using Swype, it has shown itself in a variety of places, the most frustrating of which is the lockscreen - I've been completely unable to unlock my phone at times. I've found a workaround of sorts, in which I simply re-lock the phone and then unlock it again. That can sometimes correct whatever sort of lag or unresponsiveness I'm experiencing. It is currently rooted, though this problem has reared itself even before the root. I am running a custom ROM (ApeX 1.0.2), again, has not exacerbated this obviously pre-existing condition. I've had to SBF and factory reset this phone at least once or twice, have seen no improvement in either the length of time between unresponsive periods, nor any change in how the unresponsiveness presents itself. I did run Adv. Task Killer in the past, that seemed to help in a minor fashion but I attribute that to an overall system boost in the form of freed RAM.
Having read around quite a bit, and seeing some various ignored threads here and there basically presenting this same sort diagnostic issue I'm hoping to try and create some focus on this problem. Maybe someone with some expertise into things like this can actually find a root to this issue. I'm going to have some free time soon so I'll be more than willing to guinea pig any experimentation or ideas that can be reasonably argued out. That being said, don't waste my or your time by throwing a rote 'Factory Reset/Battery Pull' at me.
-Respectfully yours, Lhowon.
My problem goes as such: I purchased my X around the time it first came out, back in mid-August. I've used it with a fair degree of satisfaction, though Motorola's bloatware and crap interface annoyed me. As time has progressed though, I've noticed one continuing, impossibly frustrating issue though. For whatever reason, my particular X randomly becomes slow, then extremely unresponsive, sometimes to the point of not registering any touches at all. I've particularly noticed it while using the Swype keyboard, which at first led me to theorize that because of the intensive nature of the program, it was chewing up a large amount of RAM - on my iPod touch, I've seen somewhat similar things if I were to background a few applications and I bumped up against it's 64 MB RAM cache. However, while the lag is predominately seen using Swype, it has shown itself in a variety of places, the most frustrating of which is the lockscreen - I've been completely unable to unlock my phone at times. I've found a workaround of sorts, in which I simply re-lock the phone and then unlock it again. That can sometimes correct whatever sort of lag or unresponsiveness I'm experiencing. It is currently rooted, though this problem has reared itself even before the root. I am running a custom ROM (ApeX 1.0.2), again, has not exacerbated this obviously pre-existing condition. I've had to SBF and factory reset this phone at least once or twice, have seen no improvement in either the length of time between unresponsive periods, nor any change in how the unresponsiveness presents itself. I did run Adv. Task Killer in the past, that seemed to help in a minor fashion but I attribute that to an overall system boost in the form of freed RAM.
Having read around quite a bit, and seeing some various ignored threads here and there basically presenting this same sort diagnostic issue I'm hoping to try and create some focus on this problem. Maybe someone with some expertise into things like this can actually find a root to this issue. I'm going to have some free time soon so I'll be more than willing to guinea pig any experimentation or ideas that can be reasonably argued out. That being said, don't waste my or your time by throwing a rote 'Factory Reset/Battery Pull' at me.
-Respectfully yours, Lhowon.
