After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
icedmayhem said:
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
Click to expand...
Click to collapse
Right now , i am sticking with 44S + BlissPop but it pop error process from time to time =( . i just wish they fix the radio soon.
I got a roommate using CM11S works with no problem. so I might just switch back to KitKat for now.
Gh05tShie1d said:
After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
Click to expand...
Click to collapse
Sent from my XT1023 using XDA Free mobile app
does any one have possible fix ?
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
---------- Post added at 06:06 PM ---------- Previous post was at 05:45 PM ----------
Merlin696 said:
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
Click to expand...
Click to collapse
Never Mind, that didnt work either.
Tried that before, no luck but thank u regardless
Ok I got it working and have been using it for a quite a while now without issue.
First this is for CM12
Download this modem
cm-28112014-modem-flashable.zip
http : // forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734/post57129886#post57129886
Next you will need to do a firmware flash/update as well otherwise the proximity sensor wont work
bacon_firmware_update_2015_01_29.zip
http : //downloads.katinatez.com/addon/
I know I probably dont have to say it but just to make sure, these should be flashed from recovery
again you will need to take out the the spaces in the http since I have not posted enough to post links
So the fixed worked all day until I turned on my WiFi and then I failed to receive my test call. I turned the WiFi off and it worked fine again. Not sure yet what the correlation is but I think its more than just a modem issue.
I give up, i'm going back to KitKat
---------- Post added at 11:52 AM ---------- Previous post was at 11:37 AM ----------
looks like maybe just maybe the devs have finally started having the issue too
http : //t.co/h0361GBRZl
well its not a fix, but if you leave your radio on 2G calls come through just fine.
I have searched high and low and still cant find anywhere someone has a fix for this issue yet.
Having the same problem on the latest nightly. I really don't want to revert to kitkat.
Problem still persists!
I am on cm-12-20150329-NIGHTLY-bacon.zip nightly and I still have the issue! I really really dont want to go back on KitKat so temporarily I am back on my old phone.
I, too, am experiencing this strange problem. No calls or texts when set to LTE, but they do come through when set to 2G.
I am currently on the 4/5 Exodus rom with the new firmware and modem from Oxygen OS. The issue still happened after flashing the newest CM nightly so I took a chance the new firmware and modem would fix it..... No luck.
Sent from my A0001 using XDA Premium HD app
same problem as well with OxygenOS and recent CM12 nightly. I wish that someone could help find a resolution. This is nuts.
I experience the same problem when I was on Blisspop, gave up and reinstall KK.
Recently tried CM12.1 and have the same problem with that rom too, a little better perhaps.
Hope someone found a solution.
Well back to KiteKat again.
All this time and this thread is buried WAY down in the Q&A section.
Are we the only ones having this problem?
Sent from my OnePlus One
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
JohnM109R said:
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
Click to expand...
Click to collapse
I don't think it is a total flop by Google at all. It's probably some errant coding for the radio on our particular phone. I would love to try to figure out why but I have no idea how or where to even start.
Sent from my OnePlus One
OK, it isn't me then. Had a missed call on my screen yesterday when the phone was next to me all the time.
Did you all get a missed call or nothing?
I have a Dual Z3 (d6633)but since I upgraded to Lollipop I noticed a bug: use "Check with Xperia movements (in practice when you receive a call pull over to your ear and opens the conversation) first with KitKat worked well and now works only if you receive a call from SIM 1 and SIM 2 by not working:someone has noticed the same flaw?:crying:
andmart said:
I have a Dual Z3 (d6633)but since I upgraded to Lollipop I noticed a bug: use "Check with Xperia movements (in practice when you receive a call pull over to your ear and opens the conversation) first with KitKat worked well and now works only if you receive a call from SIM 1 and SIM 2 by not working:someone has noticed the same flaw?:crying:
Click to expand...
Click to collapse
You usually come up with such bugs when a new firmware is released. Have you tried repairing your phone with Sony Companion ? That might fix it.
Quote me in case you expect a reply!
Good Luck
Hi Guys,
I am having some trouble, almost every call i have the it hangs up in the middle of the call.
I think it happens more when i call to someone, then when receiving.
What this could be?
best regards,
Pedro
no i dont have such a problem but, when i got a call in waiting and i wanted to receive that than it hangs always.
same problem, fixed problem with flashing custom rom (you can use pacman, cm etc) i 'm sure this is bug because i saw some people got this bug too
but i really missed miui so now im flashed miui 7 (5.8.22) never check yet about hanging up call problem, i will report if this problem still persist on miui 7
edited : try miui 7 so far so good no hanged up when calling
Hello,
I just update to AOSP Extended ROM (Android 7.1.2 not Touchwiz) and apart from the normal bugs everything was working fine but this morning for some reason none of my call will connect the just say dialing for 2-5 mins then end and when someone calls me it doesn't ring and just goes to voicemail. I can text and receive texts perfectly fine.
I thought it was the ROM at first so I switched back to the original one I had which is King of Nougat (Android 7.0 Touchwiz) but I still have the same problem I'am not sure how to fix it and nothing I try seems to work.
My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
king901 said:
My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
Click to expand...
Click to collapse
Sounds like a hardware problem, changing roms won't do anything.
king901 said:
My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
Click to expand...
Click to collapse
The bluetooth one happened to me too. My phone's touch now no longer works even though my phone never fell, got wet, or got pressed hard.
I already tried changing roms, reflashing old and latest MIUI through fastboot and none of them fixed the issue.
jalter1213 said:
The bluetooth one happened to me too. My phone's touch now no longer works even though my phone never fell, got wet, or got pressed hard.
I already tried changing roms, reflashing old and latest MIUI through fastboot and none of them fixed the issue.
Click to expand...
Click to collapse
been working on it since yesterday nothing helped , guess i will have to wait for it to die on me
ty for replying hope your next phone isnt as bad
king901 said:
been working on it since yesterday nothing helped , guess i will have to wait for it to die on me
ty for replying hope your next phone isnt as bad
Click to expand...
Click to collapse
Try installing an Android 13 custom rom. I recommend Exolution X for now since Pixel Experience android 13 is kinda buggy
I have the same problem. And every ROM, whether official or custom, has the same problem.
Install custom ROM. Worth to try. AOSP from foxtrot on tg is perfect a12 for me and everything working perfect.