I've had a gt-s6810 for a ~3-4years. Recently I've noticed this lag. Smartphone very slow reacts on call: I start call to it - reaction starts after ~5 sec, I finish call - reacts the same. NAND Flash is corrupted, or smth? Reset to factory default I did, didn't help. Stock Android.
Related
hi, i have experienced this problem 2~3 times .
The problem:
My touch pro 2 freezes, and then doesnt even turn off .I talk out battery, put it in, and start it,[without holding any key] it shows the first screen holds there for along time, automatically restarts again.Then the phone turns 'on' but all software installed, messages, contacts are wiped clean.all shortcuts, wifi ,phone settings too.its like a hard reset
It has happened 2-3 times, and I am unable to replicate the situation when it happened.Once during call it happened, other while browsing
'ROM I was Using? Jackos manilla rush and smart movie.
Note:after this resetting the phone works without a problem.until after few weeks it again happens.
hi, i have experienced this problem 2~3 times .
The problem:
My touch pro 2 freezes, and then doesnt even turn off .I talk out battery, put it in, and start it,[without holding any key] it shows the first screen holds there for along time, automatically restarts again.Then the phone turns 'on' but all software installed, messages, contacts are wiped clean.all shortcuts, wifi ,phone settings too.its like a hard reset
It has happened 2-3 times, and I am unable to replicate the situation when it happened.Once during call it happened, other while browsing
'ROM I was Using? Jackos manilla rush and smart movie.
Note:after this resetting the phone works without a problem.until after few weeks it again happens.
Whats the problem?
I have a HTC Touch Pro2 (ATT) with the stock Windows Mobile 6.5 ROM installed.
The g-sensor works fine after you first boot up, and then completely stops working at some random interval. After this occurs, trying to calibrate the sensor results in the two animated levels freezing after first twitching a bit. Attempting calibration obviously does not fix the problem.
I tried using sktools to restart the g-sensor driver. The driver will apparently stop, but it will not restart.
The only thing that works is a reboot. Honestly, I wouldn't mind rebooting this damn thing every time but it also freezes for like 15 minutes after I restart it. If you hit the power button to put the phone to sleep right after booting up, it will remain asleep and not respond to anything for almost a half hour. Sometimes calling it will wake it up though... and then it freezes again when you put it to sleep if it's within 20 minutes of boot up. The service process (services.exe) and manila show high CPU usage during this time.
Also the notification manager does not start up automatically; its service needs to be started manually each time. Setting it to manual startup mode does not fix anything.
Halp
Stock ROM?
Have you tried some of the aftermarket ones? Some of the issues in the stock ROM were fixed by the community.
Have you tried a hard reset to see if there is an app messing with your phone?
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Tipika said:
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Click to expand...
Click to collapse
Cant say Ive had the exact same issue, but have had similar. Could be a number of things. Some ROMs have problems with phones rebooting when WiFi is turned on. Not sure about CM7 though. I would recommend making a nandroid backup, and reflash your ROM. If it stops happening, it is likely an app or something corrupted causing it. If it continues, go back to a stock ROM and see how it acts. If it stops now, then it was probably something wrong with the ROM. If it continues, it may be a hardware problem that cant really be fixed. (try a different SD card too.)
Yes, sometimes when i turn on wifi, the phone reboots, but it is a different behaviour - the "wifi reboot" it's a system crash, so the screen suddenly turns in the mt3gs boot logo.
When this happen, it is starts to vibrate a lot (for example, it happened at 4am, it woke me up, even if it was far from my ear), then "dies" for a few seconds (doesn't respond to any button press), and then reboots
very strange...
My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
theperson333 said:
Hi,
My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
Click to expand...
Click to collapse
The problem occurred yesterday, so I tried to flash back to stock when the phone "seems to fix itself" again. I got flashtool ready, pulled the battery, inserted again, held the vol_down and connected the USB cable. The phone entered the qualcomm USB HS download mode. I remembered seeing that VOL_UP and VOL_DOWN would cause this mode to be entered aswell as missing kernel. I knew the kernel asn't missing since the phone sometimes boots fine. To further confirm this, I took the battery out, put it back in and connected the usb cable. As expected, the phone entered fastboot, as if the VOL_UP key was being held.
I tried drying the phone out, using silica desiccant, in a moisture shield bag, in case water was shorting the VOL_UP traces. No success. To my knowledge, the phone should be dry anyway. The volume switch feels fine, when pressing it, suggesting the problem is after the switch.
Could the VOL_UP button cause the crashing at the various stages outlined in the OP? I've made them bold in the quote. I also noticed that phone entered CWM whilst in my pocket and enabled, disabled and enabled again rainbow mode. I didn't even know that existed. When the phone boots normally, the VOL_UP key acts like it doesn't exist. When the phone crashes during boot, the main board seems to heat up.