Hi, I've been using this rom version since a long time and didn't run into problems, when I had this problem I tried clean flashing several times and it wasn't solved. So it's probably a hardware problem.
The Problem: When I am on a call, whether on phone, messenger , telegram or google meet, I can be heard well on loudspeaker mode, but when on phone mode I can rarely be heard. I figured that out: when I make a continuous sound, the first milliseconds can't be heard but after that all is heard until it stops then I have to repeat the process again. So speaking normally isn't heard at all. Can this be to moisture inside microphone ? If so, how can I fix it? Thanks.
Related
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.
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
stane37 said:
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
Click to expand...
Click to collapse
I have the same problem with my phone. Any solution for this problem thx
Reflash, reflash, and if it happens again - reflash. The screen lock/unlock workaround was working about 90% of the time. I gave the phone to my father (clean new flash) and he didn't experience any issues with the rom so far.
Hi
I've recently got one of the EU 1/8 Omate Truesmart watches. To start with it was fine, but after realizing I had missed some calls yesterday I realized that the watch made no sounds and the mic wasn't working either when I made some test phone calls. The vibrate does still work. I've changed the Modes in the Audio Profile but that doesn't seem to have made a difference.
Has anyone else had these problems?
I suspect the mic and speaker are in different parts of the watch, so I'm guessing its a software issue rather than something has shaken loose. I tried to work out how to reset the watch, but so far I haven't worked out how to do that (I haven't patched it yet, so it still has the original version of the firmware etc).
Thanks for any assistance
Somehow I managed to get the sound and mic working again . The last thing I was trying was to turn the watch off and on repeatedly, pressing or holding the two buttons down while it booted. One of the other posts suggested that I could get to a menu to reset the watch this way. Whilst I never saw a menu, on one occasion it did take longer to boot than normal (a few extra seconds) so I may have selected an option with out realising.
I've been reading here for months waiting for my TS to arrive and today it has!
I quickly found that all sound and mic was not working and my heart sank. But reading this question and the poster's own reply, and a hint from elsewhere, I turned off "fast boot" in the accessibility menu, shut down and restarted, and hey presto, sound input and output works fine. The "fast boot off" setting seems to be required in order to make the device really reboot.
Many, many thanks to all here who have been contributing to the knowledge base on this device. Hopefully I can now contribute, if only from the point of view of a non-expert man-in-the-street end user, from time to time.
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.
I rooted my phone a month or two ago using odin and TWRP recovery, and I also flashed a new rom (Resurrection Remix 6.0.1). I have since had constant issues with my bluetooth headphones, which are the only bluetooth device i use with this phone. I have searched online and looked at many forums but I couldn't find very much information to help me. My issue is that there are random times where the audio from my headphones gets very choppy and unintelligible, kind of like static. It only occurs for a few seconds though, then everything resumes perfectly fine. Another big issue I have is that when I wake the screen, the same audio choppyness will occur and it will usually stay like that on the lockscreen, and when I unlock my phone, it goes away after a bit. My phone will also randomly show the message "Bluetooth messenger has stopped working" sometimes, usually after my phone is unlocked after a while of not using it. I have turned off my phone's doze function, cleared the cache many times, and factory reset it to no avail. Hope you guys can help.