AT&T LK7 rom stock with Perseus kernel "alpha 34".
I'm having an issue with my call log. It's not showing all the incoming calls. Whether I answer it or reject it, doesn't matter. I've received 7 calls today, answered 3, let one ring and rejected one, and two were auto-rejected. Only the two auto-rejected calls show up. None of the other calls are showing on my call log, even the 3 I answered, one of which was a 10-minute long call.
I did a factory reset about a month ago, but it was doing this before then, too, AND it was doing it before I installed Perseus kernel.
Anybody have an idea what's going on?
Edit: Seems like it's a fairly common issue on 4.1.2. I did some Googling around and found that if you rotate into landscape in the call logs, the missing logs show up. I guess that works as a work-around for now.
Related
I have gotten a major problem the latest weeks. When I get an incoming call sometimes, the screen flashes to and from the "incoming call screen" (you know with the answer button) to the wallpaper. Which means I can't answer that call. Also, if I poke around too much while I have this problem on a call, the phone just reboots.
However, I may have a suspect. I am running faux007u. I am not whining here, just wondering if that may be the cause? If so I'll just try his m version or go back to stock
The reason for me writing this instead of just re-flashing the kernel an await the problem is because it would be nice to know if anyone else have had this problem.
Trying to keep that thread in development clean.
I have just installed Hyperdrive for the 2nd time. Totally wiped and formatted system and sd card. Flashed ROM (Note 3 UI), didn't reboot, flashed T-mobile pack, flashed KT kernel with cache wipes in between. Let sit for 10 minutes before doing anything. Made minor changes, Setup APN, rebooted liberally. Went to test things out and found I could not answer a call. When I slide the green phone to answer, the ringing stops but won't answer call. I looked for anything that may have changed the dialer (phone) operation and unchecked them. I had this problem my first install and mentioned it in the thread with no response. Anyone have any idea?
I was wondering...There is an option to reject call with a text by sliding up and making your choice... could that be it?
EDIT: After continuing to poor through searches I checked the call settings under "Auto Call Reject" It was set to auto reject. I was telling my wife about this. Her phone is a bone stock Note 3 unrooted (3 weeks old). She tells me she has been having problems receiving calls too. I checked the same settings on hers and it was set to auto reject calls too. Promptly turned feature off and rebooted. Now both are fine. Now this becomes a heads up for others.
Today I returned a call to my wife. Later I checked the call log, and it said "Answered Remotely" in green text, instead of displaying her number like it usually does.
I called back, and asked her about it, she didn't do anything special, she says. We continued to talk a bit, and the call was dropped. She tried calling back twice, but the calls hung up as soon as I answered. The call log for those two inbound calls to me says "Answered Remotely" as well. It seems to be random.
What is going on? I have never seen that before.
xxbigpigxx said:
Today I returned a call to my wife. Later I checked the call log, and it said "Answered Remotely" in green text, instead of displaying her number like it usually does.
I called back, and asked her about it, she didn't do anything special, she says. We continued to talk a bit, and the call was dropped. She tried calling back twice, but the calls hung up as soon as I answered. The call log for those two inbound calls to me says "Answered Remotely" as well. It seems to be random.
What is going on? I have never seen that before.
Click to expand...
Click to collapse
It might be a malware, but I'm also experiencing the same issue. I'm concerned my contacts are attempting to spy on me or something, like wtf
Is anyone else having a problem answering calls? On an incoming call, I can hit the green button over and over, yet it won't answer. Sometimes, I can get to the full dialer screen where I can swipe down to answer, but in my panic to answer, can't seem to get to it every time.
I've also noticed that oftentimes, pressing a contact to dial them will take up to 30 seconds or so. Just as with an incoming call, I can press it over and over, to no effect... then all of the sudden, it will start dialing.
My first sim is TMO, and the second is AT&T. I am still on 5.0.3 and have been ignoring the 5.0.4 update, since I'm worried about losing TWRP and magisk and don't feel like farting around with it right now. If I knew it would fix the problem, I might be a little more motivated to do so, but it only seems to fix an incoming call sound issue (not quite the same as what I'm experiencing... but maybe related?).
I went ahead and updated to 5.0.4, hoping it would help, but it didn't. I've noticed that if I press power to turn off the screen/mute the ringer, then turn it back on, I can get to the full dialer screen and accept/reject the call. Also, this freeze is easy to reproduce from the dialer log. If I browse for a sent/received call from earlier in the day and tap that, it won't bring up the sim card choice (TMO or ATT) until after 30 seconds or so.
If anyone has seen this issue, please chime in. I'm at my wit's end.
I have some issues with incoming calls. Sometimes it vibrates but doesn't show any incoming call only when I have missed it afterwards. I don't know what causes this behaviour and if it is related to your issue. I'll switch from OxygenOS 5.0.4 to LineageOS 15.1 soon so I didn't look into that and I'm not going to
I'm not sure, but it definitely seems to have something to do with the dialer itself. My guess is because I'm using two sims. When dialing a call, it's almost as if the box to select a sim to dial pops up behind the dialer....
Try wiping dialer cache then reboot, go to recovery and wipe cache/dalvik and see if it helps. btw, I find no difficulty in answering phone call.
lemonade747 said:
Try wiping dialer cache then reboot, go to recovery and wipe cache/dalvik and see if it helps. btw, I find no difficulty in answering phone call.
Click to expand...
Click to collapse
Pretty sure I tried that, but not since the latest update. I'll give it another shot!
This has happened twice and the only fix was to do a factory reset. Seemingly at random I'll stop receiving a call notification and my phone does not ring. The only way I know I missed a call is if they leave a voicemail because I'll get an alert for a new voicemail. I was literally looking at my phone and had a voicemail pop up and it didn't ring or anything.
I was rooted, stock rom for years and out of the blue I started to get only a voicemail but never heard my phone ring and no missed call notification and nothing in the incoming call log. Did a factory reset, updated apps and everything was working fine on the stock unrooted rom (just in case a magisk mod messed it up). Now out of nowhere it started again, no ring and no incoming call display. The 3xL is no longer being updated and was working as normal after factory reset with the newest rom from the google website.
I would rather not have to keep doing this every 2-3 weeks because I don't know when exactly it stops working because if they don't leave a voicemail I have no idea I had missed a call. Phone is not in DND/silent because I've held my phone looking at something and just get a voicemail and the phone didn't ring or show incoming call so I know that is not the problem. If this is a widespread problem I have not seen any reports of it and a factory reset should have solved it if was a regular software issue but the same problem started happening twice now.
Edit: I've tried multiple dialers, truephone, and I've disabled Wifi calling but still no change.
E2: Ok, finally tried out a non stock rom, LineageOS. Incoming calls are working again, I didn't doubt they would after a reset because they seemed to work after the last time I reset to stock rom. I'll see how things go I guess.