Related
I'm posting this on the four android-related forums that I participate in, in hopes that someone has seen this before and knows what to do.
Here's what I had:
- Droid 2 Global, unlocked, rooted, with Fission ROM, using Rogers Wireless, a GSM network in Canada
- it had been working just fine for 5 months
Here's what I did:
- Used RSDLite and the SBF loader to flash the stock 2.4.330 firmware as seen here: http://droid.koumakan.jp/wiki/SBF
- ended up with a bootloop, as the directions said I would. cleared data and cashe, no problem, phone booted.
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- Used stock recovery mode to upgrade to 4.5.607 (gingerbread) firmware as seen here: http://droid.koumakan.jp/wiki/4.5.607_Firmware
- I used the file linked to from here: http://www.droid-life.com/2011/08/22/gingerbread-build-for-the-droid2-global-leaks/
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- rooted phone using the adb method that is out there. rebooted and confirmed root access. installed a couple apps that need root. tested phone functionality, all was well. used APN backup/restore and APN Manager to make backup files of my APNs
- As described here, http://droid.koumakan.jp/wiki/CyanogenMod Installed Droid 2 Recovery Bootstrap and ROM Manager in order to flash CWM. rebooted into CWM, factory reset, installed the latest release (10/06), and rebooted
- started up phone, switched to GSM mode, phone app crashed immediately (as is to be expected, based on known bugs), rebooted for it to take effect
Now here's the problem:
- phone can make calls and receive texts with no problem, but cannot get data. wifi also works.
- went into wireless settings, mobile networks, access point names, nothing shows up. Clicked "add APN". entered the APN info that had worked for me before at the past two junctions. hit menu button, then save. takes me back to the APN screen, but no APN shows up.
- repeated this cycle a few times following reboots, etc. Eventually the phone gets to the point where the "add APN" button will not even come up when the menu key is hit.
- during the above, was also checking the "network operators" setting. The phone does locate all of the networks that are "in the air" but no matter which one I choose it will tell me "your sim card does not allow a connection to this network"
- used root explorer to check /data/data/com.android.providers.telephony/databases/telephony.db. There is a list of about 1500 APNs. There are multiple entries for Rogers including all of the ones I tried to enter that appeared not to save.
- used APN backup/restore and APN manager to attempt deleting existing APNs, restoring the ones that were known to work, etc. Nothing works. These programs do work, and when I check the telephony.db file I can see what they have done to the file, but they are unfortnately unable to make any APN "stick" at the APN screen, and apparently that is the only way that it will work.
more info:
- I've noticed that the list of rogers entries seems to get larger and larger as I go through this process multiple times. I may be wrong, but it seems that this telephony.db file might not actually get changed or updated when you flash a new kernel/firmware/mod/rom to the phone.
- I'm sure that the lack of a list of APNs and the "sim card does not allow connection" message are related. For whatever reason there seems to be a bug in CM7 where the telephony.db file has problems "talking" to the APN screen in settings. But it must not affect most people.
- yes, I have tried a new SIM card.
- yes, I have tried clearing cache, data, dalvik, and fixing permissions.
- Anyone else on Rogers Running CM7 on a D2G? If so, I'd love to talk to you. Maybe I could convince you to send me a working CWM backup. I imagine that if you're a conscientious rommer, you have a backup made folling a fresh install of CM7.
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Edit: I have a XT860 which is in for repairs - once I get it back and I have a reliable daily phone I plan to experiment with the new GB based CM4D2G. Hopefully this week...
leobg said:
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Click to expand...
Click to collapse
Yes, everything works really well with stock rom. I was quite impressed, as it was my first GB experience. Unfortunately, as with cars, I am all about the "options", and I can't seem to let go of a feature once I have experienced it. I love CM7 and I really want to make it work for my D2G.
I posted this same thing at the rootzwiki thread, and one of the head developers said "You my friend may finally have identified where the gsm data issues are coming from. it isnt just you, it's 98% of the gsm users that arent having data". Another user got me to change a couple of permissions. I thought he was onto something but it didn't work, either. Nonetheless, I think I brought enough attention to this issue and also gave them something to work with through all my trial and error. I am optimistic.
But, for now, I think I have to take CM7. I want my data! I am really tempted to just give stock GB a shot. But Blur scares me. Most people don't seem to like it, though I admit I don't fully understand what Blur is! I see there is MIUI and apex, angel Hexen and VenusX. I might have to try them first.
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
greek_lover_69 said:
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
Click to expand...
Click to collapse
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
seventieslord said:
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
Click to expand...
Click to collapse
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
I wish it was that easy, but it's not. I have tried a number of solutions similar to that but no dice. I appreciate the attempt though.
Sent from my DROID2 GLOBAL using XDA App
For the record I have that problem on the D2g flashed with the latest builds of cyanogen rom, (with the same SIMs perfectly working on D3 and D2g with the stock rom), and the airplane mode trick doesn't works too.
So far I haven't found a solution
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Thanks, i guessed that if a proper fix may be hard to find, a workaround was easy enough, I'll try it later with the gingerbread froyo.
dobosininja said:
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Click to expand...
Click to collapse
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
seventieslord said:
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
Click to expand...
Click to collapse
I gave this a try, and no dice. Too bad.
Thanks anyways.
The Solutor said:
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
Click to expand...
Click to collapse
I now own a D3. CM9 is doing the exact same thing to me!
I tried what you said and I am still not getting data. phone and texts work though, just like before.
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
StriferZer0 said:
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
Click to expand...
Click to collapse
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any effect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
adiv.paradise said:
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any affect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work, though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
Click to expand...
Click to collapse
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
StriferZer0 said:
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
Click to expand...
Click to collapse
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
adiv.paradise said:
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
Click to expand...
Click to collapse
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
StriferZer0 said:
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
Click to expand...
Click to collapse
That you can do. There are multiple guides out there for completely resetting back to stock, for situations like needing to return a phone to Verizon and wanting to erase any trace of your fooling around with OS components. For me, I seem to be completely unable to connect the phone to computer via USB, so ODIN is completely out. Thinking I might bring it to Verizon and see what they can do. I've currently got it on JellyWiz RLS13, which is based on the stock TW JB OTA, so hopefully that's close enough that it won't throw any flags for them and they can do some magic or something and reset the IMEI.
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
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...