When I purchased this phone on Swappa, everything worked, with the exception of phone calls. I assumed it was a ROM issue, but I have since tried mulitiple ROMs, with no success at resolving it. The culmination came this morning when I used the LG flash tool to fully restore it to factory settings, and the problem persists. The symptoms are as follows: when trying to make a call, the dialer opens, the call tries to connect, shows "dialing" then disconects. On a very rare occaision it will successfully connect, but I have yet to observe any pattern. Everything else works, sms, data, etc, and I have replaced the SIM card to rule that out. I will post a logcat in the first comment of when it fails, and I will try to get one of when it connects for comparison, but we'll see how that goes.
Code:
[ 02-15 15:28:14.035 4864: 4874 I/CallHandlerService ]
CallHandlerService - onDisconnected: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 4864: 4864 I/CallHandlerService ]
CallHandlerService - ON_DISCONNECT_CALL: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 1471: 1471 D/CallNotifier ]
onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1455568080816, subscription = 0
That seems to be the most relevant series of lines from the failure logcat. Full log attached, if anyone knows what specifically to look for.
I really don't know what to look for, and the full log is too long to post, so I will attach it here.
Does anyone have any ideas what is wrong, or what I need to do to get this device to work reliably? Is it possible that it is the SIM reader? (seems unlikely since SMS and data work, and calls work intermittently.) Also worth noting, calls seem to connect immediately after a reboot fairly consistently.
Bump?
Bump x 2?
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
rassawyer said:
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
Click to expand...
Click to collapse
I don't think it's hardware. Sounds like an internal setting got messed up. I assume you've cleared everything that's clearable from recovery.
I suggest you flash CM13. If you still have the problem, ask the CM guys for help.
I have the same problem. Wife has same phone, doesn't have problem (but has software version d85021q). I am currently using sock rooted 20f, flashed 21r modem. tried different roms all have the same problem. sim works fine in my old S4. data and texts work fine. Calls try but then stop with call ended. problems with receiving calls too. Signal strength is -108db same as hers, the S4 is about the same maybe -106db. here's a list I have tried.
1. stock KK rom
2. stock rooted 20f rom
3. RR 5.5.8 rom
4. fulmics 2.7 rom
5. latest cm 12.1 nightly
6. flashed 20f modem
7. flashed 21r modem
I would try flashing MM roms but without the baseband updates would I be in the same boat? Also worried about being stuck with MM if I want to return to LP.
I did pretty much everything possible to try to resolve this, with not success. I tried multiple custom roms, I used the LG Flash Tool to try multiple version of factory rom, and never had any luck. Always the same issue, everything worked but phone calls. I gave up, and bought a device with a shattered screen, and swapped the board over into my good body. Of anyone comes up with any ideas, I'm very interested. I have the equipment to even do on board repairs/component replacements, but I don't know what to try to replace, since the radio obviously works or data and texts wouldn't work.
I've tried pretty much everything imaginable from a software/firmware standpoint... I've tried multiple custom ROMs, I've used the LG Flash Tool to flash multiple version of stock, and multiple modems, etc. I always ended up with the same result. Everything worked but phone calls. I finally gave up and bought a device with a smashed screen, and swapped that board into my body. I'd still be interested if anyone has any insights. I have the equipment necessary to replace board level components, etc, but I don't have the equipment to test them, so I don't know what to try replacing. The radio is obviously functional, since text + data work...
Related
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2
I flashed CM 10.1 (CDMA version) the other day and since then, phone calls haven't really worked. I can make outbound calls, but can't really receive inbound ones. When the calls connect, I can hear everything on the other line, but they can't hear me at all. I managed to reinstall Sprint Zone, and the network test shows Voice fails, and tells me I need to update my profile. The funny thing is, my data network works better than on the stock ROM.
Onto tried solutions:
CM 10.1 doesn't have a menu to update profile or prl, and the methods in the forums and on the web for manually updating PRL are way above my head. Special dialer codes like ##3282# don't work at all. Got off the phone with Sprint Customer Care this morning, and even though the lady was nice, she pretty much told me I'm SOL. If ANYONE has a solution, or at least a temporary fix for making calls, please, for the love of God reply. I'm really freaking new to this and lost all my backups somewhere along the way, so restoring it to pre-flash isn't an option.
EDIT: Finally figured out how and successfully flashed the factory FXZ for 4.1.2. Problem Solved.
You need to do any/all PRL updating before flashing a custom ROM.
Reflash stock, get everything working there - update your PRL, make sure voice works (inbound, outbound etc). Then flash a custom ROM.
Also, I recommend something newer - CM10.1 is really old at this point. CM11 is pretty stable, even the nightlies - although note, they are all built under a unified device name, look for moto_msm8960
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
I hope this goes to the right place, if not can someone direct me to where it goes.
I'm having an issue with what appears to be the phone app. i can call out but when the recipiant picks up all they here is a beep like a old school fax whine. I've searched this issue and I'm at a loss. Phone is Oneplus 7t with 18.1 hotdogb with no Google.
Thanks for any help,
Lowdownin
It is not just the phone app from my digging. I am also having the same issue with Signal, as well as another dialler I have installed to test. It also happens when using a SIP client both in the Phone app and separately (Mizudroid).
Regardless of how the call is made (inbound to me or outbound to another), all they hear is a high pitch tone. I can hear them fine. Hitting mute stops the noise for them, however unmuting restores it.
I have checked and the phone records sound via the microphone and when in speaker mode and the playback is perfect.
As per @Lowdownin928, I am at a loose end. I am in the process of downgrading and will report if that has an effect.
New ROM released today, tried that first - https://download.lineageos.org/hotdogb. No change.
Downgraded to the last before the one I was having trouble with - lineage-18.1-20210926-nightly-hotdogb-signed.zip - however this has the same issue.
At this stage I cannot work out why the ROM could cause this but then using other ROM's does not fix, even when doing a full wipe. Something else is going on.
Am looking at reverting to a t-mobile or international ROM to go way back and see what happens. If that does not fix it then I am stumped, as it seem to not be hardware. Very, very strange.
OK, so have installed an original t-mobile version of Android 10.0.3 for the 7T and low and behold, it works perfectly. No issue with outbound calls from SIM or SIP, did not bother testing further.
For reference, factory default t-mobile rom I used was at https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/, put phone in EDL mode and run the MDM. Came up fine.
Proceeded to System Update to v. 11.0.1.4.HD63CB. Reboot then tested for outbound noise on calls - no problems at all.
So at this stage the only way to fix this is to revert to the stock ROM, even with 11 it works fine. I have no idea what has happened with the LineageOS ROM but there is a fault somewhere. I am heading off to ask the question (and hope you will as well) but hope all this detail gives you an idea of where to go.
Just had a thought - there may be other ROM's that work fine, it could only be LineageOS that has this issue. If you don't need the feature set then look around in here.
Super surprised no-one else has had this issue, but there you go.
Success. Thanks to LuK1337, Lineage Team Member on the Reddit Support area this seems to have cleared the issue.
---
T-Mobile firmware isn't supported, you can flash retail one by following https://wiki.lineageos.org/devices/hotdogb/fw_update
---
So bootloader, flash lineage recovery, enter fastboot mode inside lineage recovery, flash all the .img's as laid out and then follow the rest of the install. Took a long time and careful reading but this was the key for the phone noise.
Thanks LuK1337.
Just wanted to let you guys know that I was also having the same issue and this solved it for me. Thanks so much dmc.kiint and LuK1337