So I was running eclipse 3.2.2 and recently fastbooted back to stock kk 4.4.2 and now my dialer is misbehaving. I read people running 3.3 eclipse had issues with dialer but I know for sure I was on the previous version of Eclipse, and I don't know if any of this has anything to do with my dialer problems. I had also been using xposed and gravity box but flashed the disabler zip in twrp.
So on stock, when my screen is on and I receive an incoming call, the soft keys disappear and I see a notification for a call, but the call screen does not pop up and I can't access the notification bar resulting in the call being unable to be answered. Didn't want to factory reset with an ota right around the corner but I'm guessing that's my best option?
Sent from my XT1060
Solved by returning to stock and factory reset as found here
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my XT1060
Related
I have a MotoX on KK 4.4 rooted.
Recently (since it started bugging about the 4.4.2 OTA update) I notice that occasionally and seemingly randomly, the device with make the animation for switching apps. The active app (even the home screen) fill fade out, then back in again. it almost appears as if the App is switching to something else that is NOT displayed, then back again.
Apps react to this as if the app was suspended and reactivated (Games pause, emails and websites refresh, etc).
I thought it may be something I added from rooting, i.e. Xposed, but I uninstalled all root apps and the behavior persists.
Any advice?
I never had that, I have an rooted and bootloader unlocked Moto X, Gravity Box and other frameworks enabled, I thing the best you could do is to reset your phone, and maybe re-do de update.
Bumping thread.
Update: I tried resetting my phone back, and it went away, but as soon as it started trying to push the 4.4.2 update (which fails to install anyway) the problem returned.
Is anyone else experiencing this issue?
jaredtritsch said:
Bumping thread.
Update: I tried resetting my phone back, and it went away, but as soon as it started trying to push the 4.4.2 update (which fails to install anyway) the problem returned.
Is anyone else experiencing this issue?
Click to expand...
Click to collapse
Sometimes when there is modified system files, the OTA update will fail. And to restore this files, maybe the best option is returning to your Stock Android (the same version you are using at the moment), guide here, works flawlessly: (http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515)
And then trying to do the OTA update, remember that soon we'll get 4.4.3, so maybe this bug could be fixed.
Hi,
A few days ago I flashed to Carbon ROM 4.4.4 from Novafusion.
Everything went smoothly until I tried to install/activate Xposed framework. (Without any modules active at that moment)
After the reboot, al my settings were set to default, the home button registers touches but does not redirect me to the homepage, the quick settings button doesn't react and my notification panel stays empty, whether there are notifications or not.
I performed a factory reset via TWRP and everything was back to normal. But Xposed framework had to be activated again. Tried it a second time, same results. So, is there a way to have a factory reset while keeping Xposed framework activated? Knowing never being able to use Xposed again would make me very very sad.
I looked into other threads concerning similar issues, but the only solution would be a factory reset, and that doesn't help me any further. Also, I haven't found a similar case wherein the issue was caused by activating Xposed framework.
Any help would be kindly appreciated.
coeurdefleur said:
Hi,
A few days ago I flashed to Carbon ROM 4.4.4 from Novafusion.
Everything went smoothly until I tried to install/activate Xposed framework. (Without any modules active at that moment)
After the reboot, al my settings were set to default, the home button registers touches but does not redirect me to the homepage, the quick settings button doesn't react and my notification panel stays empty, whether there are notifications or not.
I performed a factory reset via TWRP and everything was back to normal. But Xposed framework had to be activated again. Tried it a second time, same results. So, is there a way to have a factory reset while keeping Xposed framework activated? Knowing never being able to use Xposed again would make me very very sad.
I looked into other threads concerning similar issues, but the only solution would be a factory reset, and that doesn't help me any further. Also, I haven't found a similar case wherein the issue was caused by activating Xposed framework.
Any help would be kindly appreciated.
Click to expand...
Click to collapse
Are you using ART? Because Xposed isn't compatible with it, yet.
So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TRP like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3
Just thought I'd post this issue I was having up until last night until I decided to wipe my phone, install a new Rom and use superuser instead of my usual supersu.
I was on maximusHD Rom and recently had a binary and software update for supersu, after this update I was unable to make or receive calls, basically when trying to make out going calls the phone I was calling was ringing but I couldn't hear it ringing my end, then it would cut off, as for incoming calls, my phone would ring but upon answer I couldn't hear anything and would have to hang up, it got so bad to the point where I was no longer receiving text messages either.
So last night I wiped my phone and installed arhd 81, during the options whilst installing it asks if you would like supersu or superuser, I chose supersu, the Rom installed and upon booting up, after all the updates where complete, hey presto, same issues as above started again, so I wiped again and this time chose superuser, all went fine and I tested my phone along the way with my partners phone, to make sure it wasn't something else causing the problem, I've had no problems so far and it looks like it was the update to supersu that caused the original problems.
Just wondering if anyone else has experienced these issues ?
Same problem here after updating to supersu 2.16.
Returning to an old version of SuperSU is not enough? I have similar problems, but I cant' uninstall the app now...
I have reinstalled supersu, and updated the binaries using the normal method instead of using TWRP, my last call was normal so that might be a (temporary) fix.
As title says, I just upgraded to Oreo with OTA and I can't answer calls.
I can hear the phone ringing but nothing is displayed to accept/refuse the call.
I also tried using Google Dialer as a replacemente but nothing appears there too.
Dialer is present in the apps, and I can use it normally if opened. But even if I start a call from there I can't close it because the screen with the running call (the one with image and bottom keys for speakers, etc) is not appearing at all.
Phone is rooted with Magisk and TWRP.
Keeping your data intact please try to flash the full OOS 5.0 rom. OTA update might have screwed the system.
lontu said:
Keeping your data intact please try to flash the full OOS 5.0 rom. OTA update might have screwed the system.
Click to expand...
Click to collapse
I tried again with Google Dialer and it's working. So it's a problem with stock dialer. Can anyone send me the stock dialer APK from OOS 5?
Are you by any chance using the 'Enable Native Call Recording' module in magisk? If yes, then get rid of that.
fluster84 said:
Are you by any chance using the 'Enable Native Call Recording' module in magisk? If yes, then get rid of that.
Click to expand...
Click to collapse
No, I knew that already. I only have the default ones that come with magisk (auto_mount, system, module.prop, update).
I think I just need to reinstall the stock dialer, but can't find the APK and I don't know how to extract it from the full zip system image.
I'll keep the google dialer in the meantime.
matrixino said:
No, I knew that already. I only have the default ones that come with magisk (auto_mount, system, module.prop, update).
I think I just need to reinstall the stock dialer, but can't find the APK and I don't know how to extract it from the full zip system image.
I'll keep the google dialer in the meantime.
Click to expand...
Click to collapse
Try to clear dialer data. It same as reinstall
Im having the same issue, so let me know if you figure out the solution.
No problems should be there after upgrade.
This shows a problematic Oreo setup.
Better have a factory reset so all apps will be installed correctly.
Sent from my i15-TCL using Tapatalk
Did you guys solve the problem?
I'm having the same problem and have enabled call recording using magisk. I tried upgrading to 5.0.2 and still the same. Please advice.