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.
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.
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.
Extremely intermittent and hard to pin point problem I'm having with my I9100 and wifi...
I am using the Chameleon ROM 3.0.2 with Dorimanx 8.16, but this also occurred with Chameleon 3.0.1 and Jeboo 2.1.
This has only happened in the last few weeks, and there have been no changes to the phone or my home network to bring this on, and everything worked absolutely fine before. I decided to spend some time this afternoon trying to sort this out, and I've gotten no where.
On a fresh boot I can connect to wifi fine, and provided the phone stays awake, I can use the internet fine. But when I put my phone down and leave it to go into sleep, often when I wake the device back up, the wifi will be connected, but the signal icons will have turned grey, and nothing will work. Sometimes when this happens the phone will automatically drop and reconnect to the wifi, and others it will remain stuck and I have to reboot the phone. But sometimes this doesn't occur at all, and the phone wakes up and wifi works fine.
I have definitely checked the Advanced Wifi settings and the sleep policy is set to Never.
When this happens, the data connection doesn't take over, it's as if the wifi remains connected but somehow decides to refuse all connections. SMS and phone calls still work fine.
I have done several factory resets, and I am currently running the phone with nothing but the default apps in Chameleon 3.0.2.
I just signed into my Google account, opened Google Play to update things like Hangouts, Maps, Search etc, and I hit Update all, then locked my phone and put it down. When I picked it up again not 3 minutes later, all the updates had failed as the wifi had crashed(?).
I have tried another router, and it still happens. All other devices connected to either router have been fine the entire time (my laptop, desktop PC, Samsung Smart TV, Nook color with CM7 and an Amazon Kindle).
I have seen a couple of other threads about this, but none of them had any answers in, they were just left with people asking about it and not getting anything concrete. Is this going to be some kind of hardware problem and the only fix is a new device?
I'm at my wit's end here, it's driving me up the wall, I'd really appreciate any ideas.
EDIT: Being an eejit, I only just found this thread http://forum.xda-developers.com/showthread.php?t=2161978 I can't seem to delete this post, so I'll just leave my apologies here, please can an admin/mod delete this thread? I'll post in the other thread I linked to above.
So i bought a Samsung Mega from ebay and seemed everything was ok. However a day or 2 later i noticed i was not able to make a call. I went and did a reset and everything was fine. I have now noticed this is a recurring problem. out of no where the network stops working and i cant make any out going calls or receive any. The bar on the phone still shows a small bar like there is a network. I also noticed that when i make a call with the phone, the screen shuts off automatically. i press the power button to get it back up and when i try to touch anything on the screen it attempts to pull down the drop down menu. It pulls it down like 2 inches and i have to mess with for the actual touch commands for it to work. as soon as i hit the button to call it shuts off. This device is already rooted and i dont know if something done to the phone has made it wonky. I dont really care about the root and if there is way to fix it i would like to hear any suggestions. this is running android version 4.2.2 kernel version 3.4.0-2052936. the Mega model is SGH-I527. Thx
Hey guys. So I've been trying to figure this out for several weeks with no luck and I was hoping you could help me. I have a Verizon LG G3 on AT&T on 10b. I can connect to 4G LTE and Edge just fine. However, when I try to make a call or receive a call on LTE, the network vanishes instantly. I'm talking from 3-5 bars to no service in within 5 seconds of calling my phone or calling from it. I've tried flashing different modems and the problem still persists. I already tried flashing the stock (what I'm on now), factory resetting, clearing the cache, etc. and have not been able to fix it. Today I called AT&T tech support and after they re-registered my phone I was able to make one phone call before the problem reappeared. When I made the call, my LTE dropped but I stayed connected through 2G/3G/Edge not sure which one.
The only other time I've had it working properly is when I had Cyanogenmod installed. However, that led to another issue. With Cyanogenmod, my phone would crash within a few minutes of booting. Most of the time I couldn't even make it through the setup. To be more specific about the crash, my screen would freeze and become unresponsive for a dew seconds and would then turn off completely. The green LED would turn on and stay on. Every time this happened I would have to pull my battery. The only way to prevent the freezing was to turn on airplane mode. If I turned off data or had the phone SIM-less it would still freeze airplane mode was the only solution.
If anyone can help me with either of these issues I would be greatly appreciative. If you need any more information or want me to post logs just let me know and I'll happily do so.
Here's a quick recap incase you don't want to read through the walls of text.
VS985 10b on AT&T
EDGE works fine
On 4G LTE network disconnects when making or recieving call
Cyanogenmod fixes network issues but freezes when not in airplane mode
Z3R01337 said:
Hey guys. So I've been trying to figure this out for several weeks with no luck and I was hoping you could help me. I have a Verizon LG G3 on AT&T on 10b. I can connect to 4G LTE and Edge just fine. However, when I try to make a call or receive a call on LTE, the network vanishes instantly. I'm talking from 3-5 bars to no service in within 5 seconds of calling my phone or calling from it. I've tried flashing different modems and the problem still persists. I already tried flashing the stock (what I'm on now), factory resetting, clearing the cache, etc. and have not been able to fix it. Today I called AT&T tech support and after they re-registered my phone I was able to make one phone call before the problem reappeared. When I made the call, my LTE dropped but I stayed connected through 2G/3G/Edge not sure which one.
The only other time I've had it working properly is when I had Cyanogenmod installed. However, that led to another issue. With Cyanogenmod, my phone would crash within a few minutes of booting. Most of the time I couldn't even make it through the setup. To be more specific about the crash, my screen would freeze and become unresponsive for a dew seconds and would then turn off completely. The green LED would turn on and stay on. Every time this happened I would have to pull my battery. The only way to prevent the freezing was to turn on airplane mode. If I turned off data or had the phone SIM-less it would still freeze airplane mode was the only solution.
If anyone can help me with either of these issues I would be greatly appreciative. If you need any more information or want me to post logs just let me know and I'll happily do so.
Here's a quick recap incase you don't want to read through the walls of text.
VS985 10b on AT&T
EDGE works fine
On 4G LTE network disconnects when making or recieving call
Cyanogenmod fixes network issues but freezes when not in airplane mode
Click to expand...
Click to collapse
I think you are talking about making calls on Voice over LTE. I am not surprised Verizon rom does not quite support it. Maybe you can try this swap boot.img hack to install AT&T rom and see if it solves your problem?
http://forum.xda-developers.com/showpost.php?p=58740774&postcount=43
Thanks for replying. That's my main theory too. However, according to my research, the VS985 didn't get VoLTE until the 12b update. I'll definitely try an AT&T ROM when I get the chance at the very least I'll probably learn something from it. Any chance there's an option to make LTE data only on this phone?