I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
timekillerj said:
I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
Click to expand...
Click to collapse
I do have the echo problem but it doesn't happen often and usually goes away if I just call them back which I think might just be a signal problem.
As far as the rebooting issue, your phone will reboot itself if there is low memory for the phone to function meaning there is something running in the background that you don't necessarily see when you open the recent apps to close. That's why I got task killing apps that help close apps that you don't want running (Clean Master App does it pretty well). As for me the only time I get reboots is when I'm running multiple apps that's a bit intensive causing my phone's memory to drop down to like 300MB +/- 100MB like games plus some messenger apps to talk to people I play with. Worst case scenario is that you going to have to contact Tmo or Samsung for warranty and best case scenario is you just figure out whats running background or clear cache now and then.
timekillerj said:
I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
Click to expand...
Click to collapse
Do a full Wipe (Wipe Data, System, Dalvik Cache and Cache) and go back to stock. That's how I solved all of my problems
timekillerj said:
What else can I try here? Anyone else experience this? I'm out of ideas.
Click to expand...
Click to collapse
I think I've read in a couple of threads that if you let it sit for 5 minutes after it comes back up after a full wipe and then just cancel out of all the automatic setup screens, then reboot and set it up manually it seems to fix this. I haven't had the problem so I can't verify this, but hey, anything is worth a try.
Good luck.
Related
Is anyone experiencing a problem with the Gtablet where apps are randomly exiting or closing ( but not FC's) and it's like you're hitting the back button? Sometimes windows of previously closed apps are randomly popping up? Doesn't happen all the time but very annoying when it happens. This thing happened even when I had the stock rom build 4349 , branch 1.2 and now flashed with CM7.03 pershoot. After a while without doing anything, and it's like it finished hitting the back button several times, then it settles and works fine again. I'm tempted of sending it to Viewsonic for repair but maybe someone had this issue before and had some solution or answer to what's going on. Thanks.
This has happened to me several times before, but it usually fixes it self, usually I clean the screen and the capacitive buttons. And i think that stops it. Or sometimes it may just be the app, I was having problems exactly like the ones you are describing with Opera Mobile Browser. You should also try to wipe all data/cache and format your sd card if it doesn't stop.
Thanks for the reply. I decided to send it to Viewsonic. It needed fixing of the charging connector anyways. I told viewsonic support about the problem, he seemed to know about it. So far I have not received it yet. I thought about the screen and tried cleaning it but not sure if it fixed the problem. Tried formatting the SD card too.
I have had my Rezound for 30 days today. This morning while driving into work my phone was on the Verizon GPS dock and the died due to low battery. It was the first time I actually let it discharge completely. Later at work I got a call and the ring tone I set up for that person was different. I went into all the contacts I assigned ring tones to and they were all changed. I then opened up GO SMS and all the notifications I had assigned were all changed as well. There does not appear to be any rhyme or reason to the pattern of the changed ring tones and notifications and nothing else on the phone appears to have been affected.
I used to have a problem like that occasionally on my HTC EVO 4G, but that was only when I was restoring some nandroid backups. Obviously that would not be the case with the Rezound, so I am left with a question. Was it an issue with the GPS Dock or the battery discharge completely? Or could it be that it discharged while on the GPS dock? I searched the forum and could not find anyone with this exact same issue so not if this is something new or an old issue. Minor annoyance I guess, but we all know how long it takes setting up your ring tones and notifications.
Mine did the same thing yesterday except that it had a charge.
Then last night it just started boot looping for no reason.
Sent from my ADR6425LVW using xda premium
Now that I started looking at the phone it started flickering so I am thinking I might have to do a factory reset to see if that fixes it.
mikehager66 said:
Now that I started looking at the phone it started flickering so I am thinking I might have to do a factory reset to see if that fixes it.
Click to expand...
Click to collapse
Mine had similar problems, my apn changed on its own and couldnt get a data connection, and my ringtones changed. I reset the apn to default which fixed the data but then I kept getting 1x when my wifes was on 3g. So anyway did a factory reset and everything working great now.
yeah, i thought it was go sms...go was changing my text noise to a SONG in my music folder lol...and my ringtone sometimes changed back to default, but that was because i had my ringtones on the external SD, when they should be on internal..everytime you plug it into the PC, it'll reset to the stock ringtone. but yeah as for tones, idk why that does it.
I am 'glad' I am not the only one, but not sure if I want to do a factory reset in case the phone got boinked or to just reassign the notifications and ring tones. If multiple phones had this issue and it seems to be on the day they had a huge network outage could that be the cause.
I've had issues with notifications changing randomly, generally when it dies or I do a full reset. My favorite was when I missed some important calls because it changed my ringtone to silent. I refuse to do a factory reset, though. Too much hassle, so I periodically check my sounds.
Sent from my Rezound in a tiny corner of hell.
Ugh, my phone wasn't doing this at all. Then I did a factory reset to try to take care of the Mobile Hot Spot issue, and now my notification sounds are changing.
Time for an OTA update, hTC!!
Has anyone been calling Verizon to report this issue? Squeaky wheel gets the oil or else we're just whining to each other on the internet.
isn't it , squeeky wheel gets the grease? lol
Temp Root
This only happens after I temp root. It unmounts the SD card and changes all of my custom ringtones for different contacts.
Leave more info of this buggy issue
My wife had the same issue once!!! But I haven't encountered after that, can you guys leave some info for reference? BTW, if ur custom ringtone is mp3. saved in external storage, did you remove SD card or set disk drive mode while issue happening?
My device
ROM version:1.02.605.6
Issue happened step: Can't repro!!
It's happening to me now and it started when I changed out my battery. Probably just a coincidence. Having to keep fixing ring tones is a pain in the ass.
KORM via the beast known as the Rezound.
I was having the same issue because I was temp rooting a lot. I fixed this by putting the ringtone and notification that I always use into the system/media/audio. This prevents it from changing it to something else, or to nothing selected, when the SD card is unmounted.
Sent from my ADR6425LVW... An HTC Rezound
Seen this a few times in recent days myself (Unrooted/ Stock). Not 100% sure, but it looks like the SD card is somehow getting ninja unmounted when the battery dies (or is about to die) because i'm also not able to access anything on the SD card after that happens. I'll try to test again today to confirm if this is the actual trigger. For me, a reboot automatically remounts the SD card correctly - restoring any missing ringtones/notifications in apps, without having to manually set up each one. The odd thing is that when this happens, settings > sd & phone storage still shows the SD card as mounted. Also weird: manually unmounting/ remounting the SD card via will let me re-access some files (photos), but ringtone links are still dead. A reboot fully solves the issue until the next occurance. This probably needs to be reported as a bug.
It has been happening to me a lot. Seems like I reboot my phone and at least 1 ringtone will default to Silent.
I just moved all my ringtones and notifications to the system/media folder. I will see if it sticks.
dustintheweb said:
Seen this a few times in recent days myself (Unrooted/ Stock). Not 100% sure, but it looks like the SD card is somehow getting ninja unmounted when the battery dies (or is about to die) because i'm also not able to access anything on the SD card after that happens. I'll try to test again today to confirm if this is the actual trigger. For me, a reboot automatically remounts the SD card correctly - restoring any missing ringtones/notifications in apps, without having to manually set up each one. The odd thing is that when this happens, settings > sd & phone storage still shows the SD card as mounted. Also weird: manually unmounting/ remounting the SD card via will let me re-access some files (photos), but ringtone links are still dead. A reboot fully solves the issue until the next occurance. This probably needs to be reported as a bug.
Click to expand...
Click to collapse
Confirmed yesterday that "about to die" wasn't the trigger. Will try to let it die all the way to see if I can get it to barf again.
I am having this issue also and it is driving me crazy. It is also changing to like a random ringtone and my alarm sound even has changed. I have not hooked it up to my PC in a few days and am not rooted or unlocked. Only thing I can think of is when I rebooted it since I do not let it die very often. I was beginning to think my phone was haunted ;P LOL j/k But seriously it should not do this!!
Same issue with downloaded notification tones and alarm sounds changing and/or resetting. It hasn't happened in a while. I won't speculate the cause at this point. Glad it's not just me.
dustintheweb said:
Confirmed yesterday that "about to die" wasn't the trigger. Will try to let it die all the way to see if I can get it to barf again.
Click to expand...
Click to collapse
Let the phone fully die last night. Plugged in & charged to about 75% before I turned it back on. Checked to see if Alarm was able to read SD ringtones. YEEEEUUUUP.
So it seems like this issue is random, which makes it slightly more annoying.
W/e, it's a bug that is somehow related to rebooting & hopefully it will be caught/ fixed by HTC in the next patch. For me, the issue is rare and a manual reboot fixes the borked notifications. I can live with that for a while.
I've had this happen on reboot as well. It, along with the network bootloop issue, seem to be completely random upon reboot and everyone needs to make sure to report these bugs to HTC. These are both VERY annoying!
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
I flashed Android 4.2.2 to my International GS3 sometime back and noticed that the phone would often shut down on its own and when restarted, I cannot hear the person on other side during calls. This would go on till I turn off my phone for good 20-25 mins and then restart. Has anyone faced something similar and help? Thanks.
This can be caused by having the wrong modem but is usually solved by having a boot animation with sound. Try clearing caches and fixing permissions after.
Sent via TCP/IP
A rather annoying issue has started to plague my Z2 and I was wondering if anyone else has come across it?
For the past two or so weeks it I've been having a number of missed calls (important one as well), this is despite the fact the phone as been three foot away from me. I've not heard it ring. Which is defeat the whole point of the thing.
I've now found out that occasionally it seems to want to stop making any sound. No notifications, ringtones etc. During one of it's tantrums I tried to play a MP3 via Doubletwist and it simply skipped through all of the album in record time without a single sound being played.
The only way to rectify this PIA issue is to reboot the phone.
I've also noticed that the vibrate is also occassionaly turned off, which is equally annoying.
Does anyone have any idea what could be causing this?
My phone is on 402 and rooted.
Thanks for any advice.
Do you have any apps installed like "sd card fix" or something like that? An app that should bring back the Feature to write on sd card with other then system app? For me these apps are making similiar problems. After deinstalled, everything working as it should be.
Thank you for your reply!
I've gone through and checked, and I don't have anything like that on my phone.
My old Galaxy S3 used to play up at times by refusing to receive calls and I found out it was down to my ringtone which seemed to be 'corrupt'. A reboot and it was back up and running.
This though is odd, as I don't have ANY sound. It's as if the sound part of the phone has given up the ghost!!!
I'm not even sure what makes it happen, which is REALLY annoying. At least then I could rectify it. It just happens.