Has anyone had the same problem after installing O2Plus?
My phone seems to lockup completely after making a call or attempting to make a call.
It may well be another programme causing it, but it seems to have a problem returning back to the Today screen.
The only way to recover is to remove the battery and replace it, then restart the phone.
OK, here's something strange that I still haven't figured out why this happens or how to stop it. My Kyocera Echo phone has a different ring tone than what I hear when it starts quietly ringing when no one is calling. I turned it on this morning and used Advanced Task Killer to kill all the apps that start up with my phone that my start up manager seems not to catch, and then when I came back to my phone after getting breakfast, I noticed it was ringing. It happens sporadically even when the phone is idle for a while and it isn't how long it's on or what time of day it is (alarm) or any app that's running (I think.) I think it might be something to do with the firmware or a background app or something. AVG didn't find any viruses on my phone either.
Any ideas of what to check or anyone fix this issue before?
UPDATES:
I noticed that when I tried using Lookout Mobile on my phone, that I no longer have the program called "Hot Reboot" on my phone and I think it removed it. I haven't had it off of there long enough to tell if that's what glitched it up or not, but so far I haven't noticed it ringing. Maybe it's a virus. A lot of people seem to have it, so maybe they made it so it's just buggy on the Echo. I'm not sure.
Update:
No it isn't that program...
Update:
I did a factory reset and as long as it isn't a firmware bug or a rootkit virus or something, I should be rid of it now. I'll keep this post updated in case it comes back. I only installed a few of the programs I had on it before.
Update:
Ok, so it started doing it again....
Update:
Good news! I'm making progress and I found out that the program causing this issue is actually the dialler program. When it started ringing again I tried the volume button and it gave me the volume control for "In call volume." So, I tried to make a call to my voicemail and the ringing stopped when it connected. So there's some kind of issue with the dialler thinking I'm in a call and yet it rings with a ringtone that wasn't set as a ringtone when it shouldn't be ringing at all and the max volume is still super quiet. I'm not sure why this is happening even after a factory reset. Neither of my antivirus programs saw it as a virus either, so I'm still not sure what's going on yet.
Update:
I called Sprint today and they said it was a known issue and so I updated my software, but I thought I did that before and still had the issue. Maybe it didn't take the last time, but both my friend and Sprint said to update it. I take it as synchronicity was trying to get me to update it and that will fix it. I'll let you know if that was the issue or not.
Update:
OK, in conclusion, the update patch that I used above is what fixes this issue.
I am new to xda, I hope I found the right place for this problem.
I have a phone which is running android 7, the phone is supposed to be a Samsung s8, but I bought it second hand and it seems to be a mix of many things
Anyway, the problem I am having is that for no apparent reason sometimes when a call is received the phone does show the incoming call and does not ring. The call appears only as a missed call.
The way to reset that works is to delete the cache of the phone app. But that works only for a few minutes and then the problem recurs
It doesn't seem to be consistent, however sometimes it seems like setting the phone to do not disturb or silent mode triggers this behavior, and then even after returning to normal mode, the calls do not appear.
Another thing this that it seems like in safe mode I do not have enough this issue
I am not %100 sure about that either
Any idea what setting could cause this problem?
Thamk you to all who have ny suggestions
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.
What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?
As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.
I have this weird issue since I've updated to OOS 10.01. When my phone is locked and I receive a phone call the screen flashes with the caller info for a second then goes back to the lock screen and then goes back to the caller info screen. This happens every time I receive a phone call when the phone is locked.
Any insights?
Thanks
Please help, any insights/suggestions?
This is driving me nuts
Thanks
Something causes this issue, I have not been able to pinpoint the cause. I tried stock and rooted OOS 10 but no difference. I experienced the problem with both setups. Does not happen after a fresh install, but after a while starts to happen all over again.
Anybody else experiencing the same problem ?
Thanks
OK just a short recap, haven't had the issue for a while now. Still trying to find the cause.
Things I did differently since the last full wipe:
- did not install viper4android
- did not enable call recording
- did not give "Auto Dark Mode" app write permissions via adb (this is the one I believe is the most likely candidate)