Related
Hi!
I have a g1 and its freezing constantly. before one month it starts to freeze and I downgrade it to rc29 and root it and put cyanogen 4.1.999 and continue to update all cyanogen releases and it stops freezing. Now I am runing 4.2.4 and before two weeks the freezing thing get started again. first it starts to freeze when it get hot, when I use it for long time and it get hot in my hands. That was rerely happening first few days. Than it starts to freeze when charging and lately even when on standby. If it freezes when on standby the phone don't respond in any way only some times the volume buttons work and I can hear the sound of changing the volume when I press it, and even sometimes I can receive calls but the display don't work and no lights on buttons part. On the other hand when it freezes when I work on my phone it just freeze and there is no any respond from the phone. Buttons light are on and display is on. sometimes it get off, sometimes the display get off and buttons light is still working. Some times the freezing thing start in stages, firstly touchscreen and ball press won't respond. But I can move to another icon using ball and even enter it using the enter button on qwerty keyboard. And after some time even that part stop working and the phone is completly freezed. when I pull the battery out and return it back right after some times it wont turn on. And I just pull it off and leave it like that for half hour or more and it turn on normally. The only issue last few days it even starts to freeze while booting. I make a logcat and grabed the last_kmsg and its available in the attachment.
I hope someone is going to help me
ps. The phone is without warranty and there is no t-mobile or htc service center in my country.
Sounds like a hardware issue man, you may be SOL... You can try wiping everything, and re-flashing cyanogen 4.2.5, and see if that helps your issue.
Also, try underclocking your CPU, to help it not overheat as much, as that seems to be what your saying is causing the problem.
Leme know how that works out.
Try flashing a build that did not freeze for you, and stick on it for at least a week or two. If that build starts to freeze, it may be hardware.
I did wipe everything and put a fresh cyanogen rom 4.2.4. and it still occur.
How can I underclock my CPU?
btw. Thanks for help I hope its not serious hardware problem...
I pasted this in Google's official forum but no reply. Can anyone one here please reply to this?
******************************
Here it goes:
The phone is perfect. Works very well. With a small annoying issue.
Sometimes after calling some someone when I hang up and keep it aside, the screen times out (which is normal).
But later when i try to wake the phone by pressing power button it does not do anything. No matter which button i press the phone lies dead.
Take out the battery and the phone starts working great as if nothing happened.
I have experienced this issue atleast 5 times. I tried factory reset just to make sure any random application is not doing this. But, after couple of weeks the issue came again.
I am not sure if HTC is the only one that can help because I am basically scared that they might screw other areas of phone which are working just fine.
Can this be solved by Froyo? Should I wait for it come OTA?
Also, there can be an application which wakes up phone via trackball but would that help?if no button is responding.
Please help guys!!
Always include:
Carrier:Singtel
Country / Language:Singapore
OS / Browser / build number (if applicable):2.1-update 1 (Unrooted, waiting for Froyo OTA)
Try calling your phone from another line first. That would happen to me on my HD2 (a really awesome phone if it didn't suck ass so bad) and, sometimes calling it from another line would cause it to wake up.
OK
Will try to call from another phone once the issue re-occurs.
Should get Froyo by this week as per google so lets see if that can eliminate the issue.
Just now this issue reappeared. I tried calling my phone with other phone but it just kept ringing, no response on N1.
I tried connecting charger and usb but again phone lies dead.
Pull-push battery and now I am typing this message with same phone.
Still wating for froyo ota.
Guys, pls suggest if someone is facing same issue.
I know Leo Laporte had this problem with his N1. Because the power botton is used for unlocking the phone it is more prone to having issues. Everything on his phone was fine, then the power/wake button stopped working. He pulled the battery and could never get it to boot up again, since the power button didn't work. He called up HTC customer service and they sent him out a new phone minus the battery and back cover. That may be the easiest solution to your problem.
I had that problem at one point, although not so severely. Froyo put an end to it but I have a strong feeling the problem will return since I am starting to notice a ~1/2 second lag between pressing the button and the phone waking up.
I think the problem lies in the hardware/software interaction for the button. Can you try something:
-Plug in your phone to your computer
-Start logCat* on your computer
-Keep messing around with your phone while its still connected (logCat will keep scrolling by itself, displaying the system log - if it doesn't, scroll to the bottom of the log and it should begin auto-scroll)
-Wait for the problem to come back
-Press the power button ONCE and see if ANYTHING shows up in logCat that coincides with you pressing the button.
The reason I say this is that I tried this with my phone (i'm a dev so I had it plugged in at the time already) and when I clicked the power button, although the screen would not turn on, logCat would indicate that the Android system registered the click.
Post the results for everyone, if you would be so kind.
*logCat is part of Android-SDK and can be downloaded from the Android Developer's Resources.
it's most likely a hardware issue with the button itself. 3 weeks ago I had a very similar problem where the button was working 1 out maybe 5 times. I called up HTC and they sent me a new one (well technically they're refurbished but I honestly couldn't tell the difference). I was rooted and everything, but they still didn't charge me for it. New phone is still working just fine.
So give them a try.
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
MSigler said:
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
Click to expand...
Click to collapse
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
maniacx21 said:
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
Click to expand...
Click to collapse
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
musashiken said:
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
Click to expand...
Click to collapse
Ahh. I believe you misunderstand my intention;
The logcat output won't explicitly say that the sleep/wake button was pressed, rather you would see some indication of background [system] activities reacting to the press (you would see 'x many' log entries appear RIGHT when you clicked the power button). There would be no way to tell for sure if you see it after the fact. You would essentially be clicking the button with your finger while staring at the logcat output on your computer. You could not do that with alogcat (from the market) as the [device's] display would be off at the time.
*I bolded alogcat to differentiate it from logcat.
For those unfamiliar, the Android system (and activities spawned by applications) send 'messages' to a sub-system in the Android-OS called logcat. The logcat is used by developers to find out at what part of the program an error occurred while debugging as they can output detailed error logs to it from their app. Logcat also outputs things such as results from OTA checkins so Google can debug the OTA system to make sure it is pulling the correct download paths, ect. This was put in place by Google devs (and led to the public finding out the google server addresses of the Froyo 'test' builds).
On average, there are 2-3 logcat entries added per second when the device is being used, and about 0.1 logcat entries per second when the device is in standby mode. What we are looking for in this case is whether there is a sudden surge of entries when the button is pressed, indicating that SOME part of the Android system recognized the press. The entries wouldn't have anything to do with the button itself, but if the same [few] entries come up EVERY time you press the power button and nothing happens visually, you know something was triggered.
Logcat is a software that runs on your computer (what we want in this case) that lets you view log entries in real time. Alogcat on the other hand, is a software that RUNS ON YOUR PHONE that allows you view log entries in real time.
Let me know if you have any questions!
Do you use a taskiller? Ever since I got burned by a taskiller, I've been wary about them. Not wary enough to uninstall them though.
Not a fix:
But a workaround would be using Trackball Wake to circumvent having to use the power button to wake your device. Especially since you are not running on Froyo.
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
Hi,
since a couple of days the phone freezes and reboots frequently after each battery change until network time sync is completed... In detail:
- After reinserting the battery and restarting the device it boots normally, I can enter the code to unlock the SIM and the touch screen is usable
- After a few seconds or so, the touch screen freezes, and does not respond to any action. The home and back buttons respond though.
- Then after a minute or so, the device restarts but does not ask for a new code. Is usable for a few seconds and freezes again.
- This cycle continues until the device has sync'd the time. After that it runs stable.
The device is rooted but runs the stock rom (4.1.2). I wouldn't be surprised it some app causes the trouble, but how can I detect this? Played with logcat already but there's not enough time to start the log recorder after a restart before the system freezes the first time.
Thanks in advance for any help and hint!
Andreas
Hello everybody,
I'm not an expert in android or any other phone software, that's why I kindly ask you for help.
Trying to install an air company application from Play store on my desire 500, I got a message saying there is no enough memory to install it. The phone froze with this screen without any reaction on touching, sweeping etc. The only thing I could do was to restart it. After initial screen and entering SIM card PIN code the home screen appeared and began blinking at uneven periods of 0.5 - 1 s. It wasn't possible to control it in any way. Yet, the phone became hot and quickly drained the battery. I removed the battery, put it back, charged it and turned on the phone - it showed the same behavior. After 200 attempts I managed to unlock the screen and to make it operative. Didn't find anything suspicious except that it's hot, takes more current than the charger could supply (battery diagram goes down although charging is on) and reacts very slowly on touching and sweeping. When connected to computer HTC sync manager starts automatically but doesn't establish connection (No phone connected). After expiring wake time and the screen gets black and power button is pressed, the same blinking appears.
I made a hard reset (luckily I have a backup) but nothing changed even the phone is now completely naked, as came from the shop, without additional apps, files, contacts, nothing.
Please advise what could I do to solve the problem. This is my only phone and I can't afford a new one.
I could give all info I have concerning firmware, OS etc.
Thanks in advance!
Best regards
Emil
P.S.
Android 4.1.2
Build 1.34.901.2 CL364226
Kernel 3.4.0-g996394e