I've seen similarISH issues but nothing like what I'm having happen... I'm sure its happened to someone but its now buried in the depths of the internet never to be seen again, So here we go.
I last night Flashed back from NC5 back to MK2 4.3 had no problems during this process that I could see, No Cache issues, no bricking, nothing.
Was able to Re-root my phone, all my root apps working just fine.
But today I noticed I had 2 missed calls and 1 VM. So I proceeded to call my VM and the phone call never went through and my phone seemed to slow way the hell down almost like when your RAM is filling on a PC or a memory leak in a game. It then Showed the call icon up in the notification bar about 10 seconds later and 10-15seconds after that it went away and went back dial a # screen in "phone".
One time I got "com.android.phone has stopped" but only 1 time. And i tried about 30 different fixes for that issue. That popup has only happened 1 time though.
And after all the fixes I still Cannot make phone calls.
I CAN TEXT NO PROBLEM THOUGH. Which from what i have read on most threads with people having this problem they cannot.
EDIT: Audio and video files are not working either... which I imagine is why i couldn't make a screen cap video showing the issue
cwliias said:
I've seen similarISH issues but nothing like what I'm having happen... I'm sure its happened to someone but its now buried in the depths of the internet never to be seen again, So here we go.
I last night Flashed back from NC5 back to MK2 4.3 had no problems during this process that I could see, No Cache issues, no bricking, nothing.
Was able to Re-root my phone, all my root apps working just fine.
But today I noticed I had 2 missed calls and 1 VM. So I proceeded to call my VM and the phone call never went through and my phone seemed to slow way the hell down almost like when your RAM is filling on a PC or a memory leak in a game. It then Showed the call icon up in the notification bar about 10 seconds later and 10-15seconds after that it went away and went back dial a # screen in "phone".
One time I got "com.android.phone has stopped" but only 1 time. And i tried about 30 different fixes for that issue. That popup has only happened 1 time though.
And after all the fixes I still Cannot make phone calls.
I CAN TEXT NO PROBLEM THOUGH. Which from what i have read on most threads with people having this problem they cannot.
EDIT: Audio and video files are not working either... which I imagine is why i couldn't make a screen cap video showing the issue
Click to expand...
Click to collapse
Well maybe I'd try flashing the Non-hlos modem that corresponds to your bootloader ( nc5 ?? )
And if that doesn't help any or you've already tried that you may just be out of luck and have to Odin back to full NC5 then go back through that whole process. Just one of them things
Sent from my SCH-I545 using Tapatalk
Related
I am having a weird issue with my LTE involving texts. This morning I restarted my phone and then a little bit later I got a couple text from some friends asking what I was talking about. I went into Handcent and looked at my conversations and found one text, which I sent on 6/5 or 6/6, was either resent or just sent for the first time this morning following the restart of the phone.
I called one of the guys asking him about the message sent to him and he said he never received it when I originally sent it, even though my phone showed it sent successfully.
Has anyone experienced anything like this?
this happens to me too. the radios seem to be able to only do one thing, so if while you sending, it needs to reconnect, connect to wifi,3g, or if you get a text, chat, or phone call while the first action is going (sending a text in this case) it seems to just hang. the thing being sent won't finish but looks like hanging forever (I've found some texts like 2 days later still spinning) and whatever the other action was won't come through. I've been told about chats or texts or talks sent to me I never receive if sending something, or usually the thing will hang for like 5 minutes and then I see I voicemail icon pop up and, surprise surprise, it came 5 minutes prior when my txt was hanging(it still is hanging, hangs forever) or a website loading hangs or connecting to wifi that never finishes. something about how this thing handles multitasking is just rubbish.
I think it has something to do with the way switching back to browser reloads the page, switching back to gmail reloads the composing page, switching back to angry birds forgets your pause and restarts the game, basically,I think they borked the multitasking somehow. sense itself reloads, quite embarrassing when trying to show off the phone, when you press home button from certain apps.
I've read if you flash a custom rom, it fixes all this. seems drastic to me, you'd think a hack would fix this.
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.
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 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.
Few odd issues I'm having with my phone. Updated a few weeks ago to Lollipop, full stock. Did a factory reset after receiving the upgrade. Everything was pretty good. Not sure if another update went out a few days ago? I noticed some icons changed and I think a few more changes in camera and gallery. Since then, (past few days) my messaging app keeps force closing. I've cleared it's cache. Not sure what else to do.
Another issue I've had for a WHILE, prior to lollipop, is constant/intermittent beeping throughout phone calls. It sounds like I or the other person keeps hitting buttons on the keypad, however, neither of us are. This happens quite a bit throughout every phone call, and it's not notifications coming through.
I had a similar issue...
After the update to Lollipop, my phone decided that it no longer wanted to be a phone. The Process com.android.phone would stop responding.
I went into recovery and wiped the cache from there, which helped for about two weeks. Then several apps updated, and the problem re-surfaced & refused to go away.
I eventually ended up downloading the RUU file from HTC, and running it. After backing up all of my data. (THIS WILL WIPE YOUR PHONE COMPLETELY!!!)
It's been two weeks, and no issues since running the RUU.
I personally would recommend skipping the trial and error & just go for the RUU.
You can download the RUU here:
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Good Luck!