Hi I've recently rooted and installed a custom recovery to my Oneplus 3t. I have also installed Xposed and have very few modules in use. However whenever I try to make a call, my phone drops the call right away. Even when other people try and call me, it goes straight to voicemail. I don't have any custom kernel installed and I don't have a way of identifying the issue. I do have a backup of my system right after it was rooted (fresh install) but I'd like to avoid having to flash that backup and lose all the apps/data on my phone right now.
Any suggestions on how to fix this?
I had this issue on my MotoG2 with Xposed aswell. I'm not sure which models caused it. I reflashed and reinstalled everything (Xposed included) and it worked. Waiting on my 1+3T due Dec6
Related
Hi everyone,
I've owned a HTC One since 3 months now, and I started trying to customize it a little. So, I followed the different guides I found on this site, and successfully managed to unlock my bootloader, install TWRP and finally flash a custom rom.
I flashed the Android Revolution HD v12.1 , and everything worked fine. Then, I made a backup with Titanium Backup Pro, no problem again. So I decided to push a little further by installing the CM 10.1 nightly version for the One; indeed, that's a nightly, for sure. I then got back to my previous custom rom and used my TB's backup to restore my datas.
I did not notice the problem immediately, but it was obviously present from the beginning : it appears that I'm not receiving anymore any notifications coming from any app I installed from the Store. I tried to uninstall then install the apps again, did not work. I looked a little bit in TB's option and I found one called "Manage Android ID", TB told me my One had a different Android ID from the previous one; I tried to restore the previous one, but still, I don't receive any notification from my apps !
I have no problem with message, call, missed call... notifications.
So, how can I fix this quite annoying problem ?
Thanks a lot.
A little bump, I need you guys!
try formatting your phone and installing an app, then check for notifications.
Ideally before changing from ARHD to CM, you should format the phone. Also titanium backup tends to have issues when you restore across different implementations.
Currently, I have ARHD. I just tried CM but TB tends to bug the entire system while restoring, anyway that's not the problem.
Of course, even though I didn't mention it, I made a FULL Wipe with TWRP each time I installed a new ROM.
I think -obviously I'd say- that the problem is caused by TB, but I'd like to know if there is any possibility to fix it without wiping the phone and installing ARHD, without using TB; Doing it this way would solve the problem I guess, but if I could avoid to lose quite a lot of data, I'd be glad !
Thanks for trying to help me.
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.
Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks
I have the Same Problem
I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?
Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?
So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.
Hello again XDA!
So this has become much more frustrating that I thought it would. My phone normally operates fine, just a couple minor software issues here and there, latest issue being my alarm not going off, tried disabling amplify in xposed as the issue only occurs if the phone has been idle for the night, figured maybe amplify might be blocking the wakelock or something. Just thought I'd share in case the module could be the root cause of both issues.
The issue I'd really like to ask about has to do with booting. As I said, the phone generally runs fine, but any time I reboot(or my phone dies) I have to wipe the dalvik in TWRP or else android just hangs on bootup indefinitely. Not only is this always a slow process(generally 15 mins of downtime) but it drains about 30% battery in the process. Just wondering if anyone has had this issue and fixed it without wiping and reinstalling a rom from the ground up.
Currently running latest ICE Lollipop build 7.1.3, elementalX 22.4-sense kernel, and latest firmware, 4.19 I believe. Xposed running with just a handful of modules (greenify, snapprefs, xblast, youtube adaway, sense toolbox). I have tried using stock kernel and uninstalling xposed framework and apk to no avail. What does work is a clean install of the same rom with the same basic setup, but I didn't want to have to reconfigure everything if I didn't have to, so I restored my backup in the meantime.
I can't get a logcat ATM, maybe tomorrow after work if I have some time. I'm also not 100% sure how to grab one anymore since its been years since I last posted one, but would be happy to provide one soon.
cheers!
Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks
Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.
Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks