Related
So I have a ADP-1 and about once a day it freezes after you put it in standby I end up having to take the battery out and putting it back in and reboot, when I say it freezes it is unresponsive to any buttons you push. I thought it was an app causing this so I run advanced task manager and kept only weather widget running as far as apps go. as far as processes go i don't know what can be turned off or not so I have not alltered them. I am running cyan 3.6.5. Any way to tell what is causing this. It boots back up fine everytime and only does this once a day. Any Ideas?
gtrplr71 said:
So I have a ADP-1 and about once a day it freezes after you put it in standby I end up having to take the battery out and putting it back in and reboot, when I say it freezes it is unresponsive to any buttons you push. I thought it was an app causing this so I run advanced task manager and kept only weather widget running as far as apps go. as far as processes go i don't know what can be turned off or not so I have not alltered them. I am running cyan 3.6.5. Any way to tell what is causing this. It boots back up fine everytime and only does this once a day. Any Ideas?
Click to expand...
Click to collapse
Try wiping and reflashing the newest cyanogen mod.
anything I should know about the latest? everything the same.
gtrplr71 said:
anything I should know about the latest? everything the same.
Click to expand...
Click to collapse
Pretty much the same, auto a2sd if you have card partitioned right. I'm liking it alot. The latest is 3.6.7.2
I keep reading about compcasche do I have to do that I am not comfortable in the console.
I've never had to do much in console with Cyanogen's but thats just me. I just flashed this on there and away I went.
http://forum.xda-developers.com/showthread.php?t=537204
do you know if android plus theme works with the new ROM? Just looked it does not
Post back with how it works out for you
Try turning off your data roaming.
Settings -> Wireless Settings -> Mobile Network -> Data Roaming
or something like that
That should fix it, if not, reflash your ROM
P.S Android + will not work with Cyan 3.6.7-2
Cyan will be releasing 3.6.8 today, and OhMarni will port it as soon as everyone thinks its stable.
thanks! You guys are great
after disabling data roaming the phone went about 48 hours and froze again tmobile said there is basically no info about that problem that they could give me being that I upgraded the recovery the warranty has been voided. Any other Ideas?
it froze up again and I called it from My wifes phone and It unfroze the buttons blinked twice and the screen came on so this is app or ROM related. is there an app that can record the functions on the phone to see what the last function was that is causing the problem?
gtrplr71 said:
it froze up again and I called it from My wifes phone and It unfroze the buttons blinked twice and the screen came on so this is app or ROM related. is there an app that can record the functions on the phone to see what the last function was that is causing the problem?
Click to expand...
Click to collapse
read up on adb, get it to work and type adb logcat
you shouldn't have told tmo you upgraded your recovery, rooted......
if all else fails, flash RC29 (DREAIMG.nbh) and start over
Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.
well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.
2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.
I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?
yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.
Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.
Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.
try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...
I've searched with google and on these forums, but still haven't found an answer to this situation. Here's what I'm seeing and I'm not quite sure how to make of it.
This is on a rogers htc dream with the ebi1 port of roms. I've had 2 different roms with the same incident.
Main symptoms:
- Home and call buttons don't work
- Holding power button only gives reboot or power off
- - power off actually reboots
- can't receive calls. calls in go straight to voicemail
I had this happen on an éclair build after a long usage time(9 months?) and clearing davlik didn't work, so doing a full wipe + install fixed the issue. The new rom i used was cyanogenmod 6.1 with froyo, and everything worked fine after install. However, after installing all the apps back in, moving some to sd, getting gapps synced up correctly, etc etc, and rebooting, the same symptoms reappeared.
This seems to be some kind of issue with the phone module (is there such a thing?). I've ruled it out being a button hardware issue since the buttons feel and work fine in recovery and when i had the clean flash on. This happened on two different roms with two different android releases, so I'm thinking it's either an apps issue or some other kind of configuration issue that causes the phone functionality to partially disappear.
The only solutions I've found is to fullwipe and install, but i've tried it and it repeated itself after first reboot. So I won't go down that route just yet.
I'm not familiar with android but is there a way to access any kind of logs or how to do some debugging to figure out why these functions are missing?
So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).
I've had my HTC One for a year and a month. No problems so far (other than the purple tint thing, but everyone gets that)...until last night
I got a couple of phone calls , and when I answered, I found that I couldn't hear the other person and they couldn't hear me either. When I made some calls myself, I couldn't hear the tone in my own phone, though I could hear the phone I was calling (my landline) ringing. Answering on the landline, I couldn't hear anything on my phone and the landline couldn't hear anything either
I was running Android Revolution 81 with Elemental X at the time. I tried the usual fixes, wiping the caches, reflashing the kernel, and neither worked. When I flashed a new rom - ViperOne 7.0.1 - the problem was fixed in the one call I made to my landline. This morning, the issue came back
I don't think the mic and speakers have any problems, because the speakers work fine and the mic was also ok when I made a test video. Pretty sure the radio is alright too, since I can send/receive calls and wifi is also working normally (is wifi related to radio though? I'm not sure)
To phrase it eloquently: halp pls
Help!
Hi, I'm having the exact same problem, it started on Friday and I don't have any idea how to fix it, I can't find anywhere on the internet with a solution either.
I hope someone gives a solution too, I use my phone a lot and need this problem fixed asap!
Were you able to fix this? My HTC One started to do this since yesterday.
Mine started today, any fix known at the moment?
I'm using insertcoin.
I read your OP and thought I'd written it - exactly the same problem! Been running ARHD 81.0 for some time now, phone was working fine yesterday, but today no dice - can't hear anything, either the phone ringing or the person when they answer, and they can't hear me, whether it's an incoming or outgoing call.
I've had the same problem all day today with about 30 calls.
I'm running stock 4.3.3 and i did a factory reset, working perfect at the moment.
Only recent change was installing skype app.
intenseandroid said:
I've had the same problem all day today with about 30 calls.
I'm running stock 4.3.3 and i did a factory reset, working perfect at the moment.
Only recent change was installing skype app.
Click to expand...
Click to collapse
Same problem for me too- Running 4.4.3 w/ HTC Sense 6.0 on HTC One M7. Can't see any recent additions that could have caused it. Did a factory reset which fixed it for nearly a day, then back to the start again.
Safe mode doesnt help. Interestingly there was a similar problem on the Nexus 4 last year- Look at google forum post "Can't hear anything when calling on Nexus 4 after android 4.2.2 update"
I haven't had this issue myself, as I'm on the Verizon m7 anyways.
But I did see a post regarding this in these forums, and the suggestion was to clear data for the latest Google Play Services update.
Then reboot.
Why that effects it, I really don't know, but certainly worth a shot, seems like an easy fix if it works for you guys.
Something to do with the latest update messing up voice calls...
Good luck. :good:
santod040 said:
I haven't had this issue myself, as I'm on the Verizon m7 anyways.
But I did see a post regarding this in these forums, and the suggestion was to clear data for the latest Google Play Services update.
Then reboot.
Why that effects it, I really don't know, but certainly worth a shot, seems like an easy fix if it works for you guys.
Something to do with the latest update messing up voice calls...
Good luck. :good:
Click to expand...
Click to collapse
Thank you so much, this fixed it
So I have read on on about this problem.. It started happening to me one Sunday the 6th of December, So i googled it as we always found a couple solutions.
Clear data on:
Google play services
Google play store
Google play framework
Clear cache on:
Google play services
Google play Store
So I did that on Sunday and it all worked out fine the phone had the problem resolved.
But then Monday afternoon rolled on by and I need my phone for work and i try to make a call and it does the same thing. So not thinking its a big deal i do the wipe and all that jazz and it doesn't fix it this time.. So I re install my Rom Viper 7.0.1 and hope that that fixes it.
That fixed again for a a couple hours till this morning.. Now I don't understand why this is happening to the phone. But I really need a REAL fix not a temp fix for it to keep coming back and having to wipe my dalv cache just to make a phone call.. Its annoying.. So what I am wondering is if i go buy a new phone. Will this just happen as soon as I sync my google account with the phone and update all the apps again.
Any info on how I can actually fix it I was going to try to switch to a the GPE Rom cause I figure its half the size might not have the same problem.. But if it is related to the google apps then It will just keep doing it will it not?
me too
Hii my phone started to have the same problem since yesterday, if u have a solution not temporary plz tell it
Covering the back mic with tape solved the problem for me !!
Ref: https://www.youtube.com/watch?v=zAGTtYwQ1Ts
Solution From HTC Support Chat - Try This - Worked For Me
First go to Settings> Battery (or Power or Energy) and ensure that Fastboot is unchecked. After doing this, power the device down.
Press and hold the Volume Down button and the power button at the same time. Continue holding both keys until you see the 3 Android images on the screen and as soon as you see this screen let go of the keys
Turn off the device
Once turned off, Press and hold the Volume Down button and the power button at the same time. Continue holding both keys until you see the 3 Android images on the screen and as soon as you see this screen let go of the keys
Navigate to “Recovery” using volume buttons, then press power to select. After about 10 seconds of blackness, the screen will change to display a phone on its back, with the update symbol above it. Momentarily it will change to an image of a phone with a red triangle and exclamation mark.
Press and hold volume up then press the power button once. You will see something very similar to the example shown. -- e:can’t open /cache/recovery/command e:/ failed to mount /sdcard (no such file or directory exists) e:/ failed to mount /sdcard (no such file or directory exists) e:/ failed to mount /sdcard (no such file or directory exists) -- A new screen will give you options like Reboot system now, Wipe Cache partition, and Wipe Data/Factory Reset.
Navigate to “Wipe cache partition” the volume down button and select with Power. Navigate to “Reboot System Now” with the volume buttons and select with power.
PondaRox said:
I've had my HTC One for a year and a month. No problems so far (other than the purple tint thing, but everyone gets that)...until last night
I got a couple of phone calls , and when I answered, I found that I couldn't hear the other person and they couldn't hear me either. When I made some calls myself, I couldn't hear the tone in my own phone, though I could hear the phone I was calling (my landline) ringing. Answering on the landline, I couldn't hear anything on my phone and the landline couldn't hear anything either
I was running Android Revolution 81 with Elemental X at the time. I tried the usual fixes, wiping the caches, reflashing the kernel, and neither worked. When I flashed a new rom - ViperOne 7.0.1 - the problem was fixed in the one call I made to my landline. This morning, the issue came back
I don't think the mic and speakers have any problems, because the speakers work fine and the mic was also ok when I made a test video. Pretty sure the radio is alright too, since I can send/receive calls and wifi is also working normally (is wifi related to radio though? I'm not sure)
To phrase it eloquently: halp pls
Click to expand...
Click to collapse
Me too starting 12/9/14
I'm experiencing the same problem. Started 12/9/14. I'm on a tmobile htc one m7. Android 4.4.3. All stock.
Follow up
jrunyan24 said:
First go to Settings> Battery (or Power or Energy) and ensure that Fastboot is unchecked. After doing this, power the device down.
Press and hold the Volume Down button and the power button at the same time. Continue holding both keys until you see the 3 Android images on the screen and as soon as you see this screen let go of the keys
Turn off the device
Once turned off, Press and hold the Volume Down button and the power button at the same time. Continue holding both keys until you see the 3 Android images on the screen and as soon as you see this screen let go of the keys
Navigate to “Recovery” using volume buttons, then press power to select. After about 10 seconds of blackness, the screen will change to display a phone on its back, with the update symbol above it. Momentarily it will change to an image of a phone with a red triangle and exclamation mark.
Press and hold volume up then press the power button once. You will see something very similar to the example shown. -- e:can’t open /cache/recovery/command e:/ failed to mount /sdcard (no such file or directory exists) e:/ failed to mount /sdcard (no such file or directory exists) e:/ failed to mount /sdcard (no such file or directory exists) -- A new screen will give you options like Reboot system now, Wipe Cache partition, and Wipe Data/Factory Reset.
Navigate to “Wipe cache partition” the volume down button and select with Power. Navigate to “Reboot System Now” with the volume buttons and select with power.
Click to expand...
Click to collapse
UPDATE: This only worked for one call (checked my voicemail), then back to not working. I tried the solution again, did not work a second time. Got back on with HTC Support, they want to do a Master Reset, so I am backing everything on my phone up first. Will repost if this works.
very curious to see how this plays out but i feel its google causing the problem therefore it will likely come back. hoping to not have to reset mine. such a hassle to do
Having the same issue since yesterday. Did a full format, reinstalled ViperOne 7.0.1 and tried to call with no apps in it and it worked multiple times.
Then I restored Titanium backup and calls have the same issue.
I think it's caused by some app but IDK
Sent from my HTC One using XDA Free mobile app
---------- Post added at 10:01 AM ---------- Previous post was at 09:04 AM ----------
Maybe I found someway to fix this
I deleted all data and cache from Play Framework, Play Services, Play Store, Contacts, Telephone
Then, in recovery, I wiped dalvik and cache and now it works
Sent from my HTC One using XDA Free mobile app
The fault lies with google play service, they updated it and for some reason is buggy.
Uninstall Google Play Service
You can do this via Titanium backup
Once uninstalled you will notice no more gps, no more google playstore etc. You can hear audio when making calls. If you want google services install the following apk
Google Play Store 5.1.11
http://www.apkmirror.com/apk/google-...re-5-1-11-apk/
Do not update the software otherwise you will have the same audio issue until google fix this and release another update. Hope this helps you all, I have tested this and since midday I can confirm it is working fine for me along with the google services
This might sound stupid but I uninstalled chrome after flashing a a fresh version of my ROM didn't work and now my phones back to 100%. It's been fine for a few days now with no issues.
So this sums up what I've done as of late which works,
Uninstall chrome
Reflash your ROM
I hope this fixes the issue for you guys like it did for me.
EDIT: Running ViperOne 7.0.1
I have the same issue. Wipe cache + dalvik cache in recovery didn't help. Running ARHD 82.0.