Not sure what recently caused this to happen, or if I should just reset stock and reload everything. Whenever I have an incoming call, I will be connect for anywhere from 1-2 seconds and it drops. Not just hangs up, but the service drops completely where the bars on the top bar show the NA symbol, the circle with a crossed line through it, and then the screen remains black other than the top bar. Then the service comes back, the clock pop-up readjusts time, and then it is fine. I can call people back with no problems, but no receiving will work. Also, randomly happening, about once a day, when you click the contacts nothing shows up, click the messages only numbers show as no names are paired to the numbers, and 75% of the apps don't open/work right. When I reboot the phone it works after, but is the only way to get rid of the fact.
Currently, I have installed Bionix 1.9 w/ Voodoo , the "gingerbread" YouTube, the JI2 GPS fix, Camera-update for the i9000 firmware, the 2,2 style Market APK, and nothing else really out of the ordinary market. Running on 2.1-update1 firmware, or the hardware locked version.
Not sure if anything is colliding or causing this, but if anyone has any suggestions before I try to just revert completely to stock and reload everything, I would greately appreciate it.
Thanks.
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 have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Try Wiping and flashing a new rom or doing a factory reset from within the recovery
Atheyst said:
I have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Click to expand...
Click to collapse
If you want to know what ROM you're on, go into Settings > About > Software information and it should say something under Software number. Mine says the name of my ROM.
Then just for fun you can pull down on the bottom of the list and see it stretch out and then boing back up when you let go. :cyclops:
But yeah, try wiping and if you do a factory reset make sure you back up any files you want to keep. Do a fresh flash if that doesn't fix it.
SOLUTION - PROXIMITY SENSOR CALIBRATION
Someone on here posted an app for rooted only devices that alters the sensitivity of the proximity sensor.
Dust can be causing the issue or you can use this app to fix it for you. The app fixed my problem instantly.
Hello guys, I would have posted this directly to the MROM thread but I can't due to not having 10 posts....so I'm posting here and hoping somebody can help me or draw attention from someone in that thread that is running this rom. I'm having a few issues with this ROM that are leaving me unable to use my phone at times and others that are just annoying.
[ROM] MROM-Olympus [CM7] build:20130330
Problems with the Phone function:
1. The biggest problem for me is sometimes trying to dial or receive calls stops working, and you don't know this, when everything else on the phone is functioning fine. A reboot will allow the phone to be able to dial out and receive calls once again. I have not noticed any patterns ...just when I get ready to make a phone call it says "dialing" and then after a few seconds a beep and it hangs up. Also as noted when this happens I'm unable to receive calls and everyone gets my voice mail. It was doing this after a install and without anything else being installed...I do feel that it's gotten worse as in happening more often but that could just be my frustration making it seem that way.
2. Another phone issue since day one: Sometimes after dialing a number the screen goes off and pressing the power button may or may not bring the screen back on or if it does the screen comes on for a split second then goes back off. It's impossible to end a call this way or to enable speaker phone, look up contacts. When it's functioning correctly a call is made then the screen goes off when i place the phone close to my ear and comes back on when i take it away. A reboot fixes this issue usually for awhile, I've also had to take the battery out twice because the power button did nothing.
Problems with the wifi tethering function:
3. Wifi tethering works but I've noticed problems on upstream packets. On 4G the phone can hit 5-6 Mbps down and 1.5 Mbps up on T-mobile. I've ran test via "speedtest dot net" which they have an android app so you can test your data speed right from the phone. Now when I connect "wifi tether" my computer to it and run the test from the computer I get the 5-6 Mbps down but the upload test takes forever to start and when it does I usually get anything from 25-220 Kbps. I performed this from linux, windows and an android tablet ..all report slow upload speeds while the phone directly running the same tests get very good performance. I'm wondering if this could be a issue with the wifi driver or possible kernel issue of sorts.
I choose this rom because from what I read it was one of the most stable and everything on the phone works which is the most important thing to me.
Thanks in advance!
Happened again today, phone uptime was 17hrs. I'd made a few phone calls and received one, pulled the phone out of my pocket to make another latter and it did it's thing where it says dialing .....a few seconds then the beep like when you hangup and then back to the contacts. I checked this time the status and it showed in service and data connected. I was also able to txt and browse the internet just not make or receive calls until a reboot.
I've replaced my broken touchscreen with new one and everything works fine until I try to call someone. i choose person from phonebook and then screen freezes but I can hear dialtone and person on the other side. I can't even disconnect a call. Then I must take out battery and put it back.
Same thing happens when I try to call someone with viber!
I flashed a new rom but same thing happens! What can I do!?