Related
anyone else have a problem with the camera app freezing on 4.4.3? Tried multiple roms and kernels with full wipes between them and still have the problem. The app freezes about a half second after opening.
tpcrackpipe said:
anyone else have a problem with the camera app freezing on 4.4.3? Tried multiple roms and kernels with full wipes between them and still have the problem. The app freezes about a half second after opening.
Click to expand...
Click to collapse
no problems here. have you tried clearing the data for the camera app?
Nope. Works fine here. Maybe try a different camera app to rule out the camera itself.
thank you for the replies. If I uninstall the update and use the old stock camera it works fine. Its the Google camera that causes it to freeze. Last night the Google camera was working fine but when I woke up it would freeze.
tpcrackpipe said:
thank you for the replies. If I uninstall the update and use the old stock camera it works fine. Its the Google camera that causes it to freeze. Last night the Google camera was working fine but when I woke up it would freeze.
Click to expand...
Click to collapse
what rom/kernel are you using? any other mods? xposed maybe?
tpcrackpipe said:
thank you for the replies. If I uninstall the update and use the old stock camera it works fine. Its the Google camera that causes it to freeze. Last night the Google camera was working fine but when I woke up it would freeze.
Click to expand...
Click to collapse
Well the issue isn't the Google camera app since its not a widespread issue with people. Something else is causing it.
Camera Freeze
tpcrackpipe said:
anyone else have a problem with the camera app freezing on 4.4.3? Tried multiple roms and kernels with full wipes between them and still have the problem. The app freezes about a half second after opening.
Click to expand...
Click to collapse
I did a factory reset and clean install of 4.4.3 Kit Kat and now my camera is freezing also. Was working fine before with OTA 4.4.3.
Now when I first open the camera app, it opens and the app freezes for about 5-10 seconds then starts working. I've removed updates from the camera app which rolls it back to the old Nexus 5 camera app which works fine. As soon it is update to the new Google camera app, starts freezing again. I used Titanium backup to install all of my old apps, so Im assuming something happened there. Wish I knew of a way to fix without having to wipe out my phone and start all over.
tpcrackpipe said:
anyone else have a problem with the camera app freezing on 4.4.3? Tried multiple roms and kernels with full wipes between them and still have the problem. The app freezes about a half second after opening.
Click to expand...
Click to collapse
esyres said:
I did a factory reset and clean install of 4.4.3 Kit Kat and now my camera is freezing also. Was working fine before with OTA 4.4.3.
Now when I first open the camera app, it opens and the app freezes for about 5-10 seconds then starts working. I've removed updates from the camera app which rolls it back to the old Nexus 5 camera app which works fine. As soon it is update to the new Google camera app, starts freezing again. I used Titanium backup to install all of my old apps, so Im assuming something happened there. Wish I knew of a way to fix without having to wipe out my phone and start all over.
Click to expand...
Click to collapse
Having the same issue here..!
I noticed it the first time when the new camera was introduced (so for the last 2 releases), means also with 4.4.2!
Also for me, when I remove the updates everything is fine.
When I updated to 4.4.3 I reset my phone before (completely) so I assume wiping doesn't fix it?!
I'm nervous to say anything because I might jinx it, but it hasn't froze in a few days now.
For those wondering, stock rom and kernel, xposed installed but no new mods.
tpcrackpipe said:
I'm nervous to say anything because I might jinx it, but it hasn't froze in a few days now.
For those wondering, stock rom and kernel, xposed installed but no new mods.
Click to expand...
Click to collapse
Same here - Exposed installed, stock and rooted, but nothing other than that. Unfortunately, mine is still freezing.
Right, same here: stock ROM (rooted) with Xposed (for App ops and Dynamic Navbar mod)...
Maybe something with Xposed?!
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
Hey all,
Sorry if this has been covered elsewhere - I've searched a fair bit but found no definitive explanation..
Anyways I've installed viper4android 2.5.0.5 via magisk and it works initially. But soon enough it stops (processing=no)
I think I may need to flash it via twrp but I'm not sure ?
Has anyone got viper4android working on OP6 OOS 5.1.8? If so how?
Thanks!
Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.
Just reboot.
hurray said:
Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.
Click to expand...
Click to collapse
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!
I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.
hurray said:
I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.
Click to expand...
Click to collapse
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.
Flying Fox said:
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.
Click to expand...
Click to collapse
Which viper version and options are you using in magisk?
I've tried audio compatibility module but no help there. I turned on fx compatible mode in viper and that gets it to work and stay working!
However it silences my alarms. Which isn't ideal ?
debatingrooster said:
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!
Click to expand...
Click to collapse
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.
KrabKoyal said:
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.
Click to expand...
Click to collapse
It's stopped working again unfortunately. I might try flashing it in TWRP instead and see if that fixes it...
I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m
bassbounce said:
I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m
Click to expand...
Click to collapse
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?
Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.
I am on OOS5.18 and used the version "Viper4Android FC Magisk V15", and I flashed it via TWRP.
But the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent, you have to reboot, which makes no sense for me to reboot 10 times per day. There must be a different way to install it.....?????!!!!
Vivasanti said:
Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.
Click to expand...
Click to collapse
Thanks for the suggestion - still same problem as @mlara.particular unfortunately
mlara.particular said:
... the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent...
Click to expand...
Click to collapse
This is weird... I don't understand why it would work for some people and not others...
I've been using the v4a material version from magisk, and it works great. I had to install the audio compatibility patch along with the audio modification library in order to get certain streaming apps to work correctly. You need to install the audio modification library if you install v4a and the audio compatibility patch.
debatingrooster said:
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?
Click to expand...
Click to collapse
XXX no limits is no custom rom .. just a module in magisk and viper works great.
sakerhetz said:
XXX no limits is no custom rom .. just a module in magisk and viper works great.
Click to expand...
Click to collapse
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Sent from my ONEPLUS A6003 using Tapatalk
mossief1965 said:
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Click to expand...
Click to collapse
Experiencing the exact same issues here. Feel like I've tried everything, and now it wont even work after reboot :crying:
@Siggi and mossief.... you have installed magisk ???
sakerhetz said:
@Siggi and mossief.... you have installed magisk ???
Click to expand...
Click to collapse
Yes, of course.
Sent from my ONEPLUS A6003 using Tapatalk
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
I cleared cache in twrp and mine starting working again
Ultraman666 said:
I cleared cache in twrp and mine starting working again
Click to expand...
Click to collapse
I also wiped dalvik cache but same error exists...
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
but I am not using call recorder module...
I am using cloudflare dns and xXx no limit module only
I think xxx hast it inclueded? Try deactivating magisk modules?
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
This happened to me and after disabling all Magisk modules and rebooting I got it to recognize the SIM card again. I did dirty flash the ROM during this process with modules activated, but it didn't fix the issue until I deactivated all modules and rebooted. I think it was an issue with xXx, but when I installed xXx after detecting the SIM again I didn't have any issues.....
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
god damn me that was it...it was driving me nuts. thank you!!
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
That worked for me, thanks!
The OnePlus helpdesk was making a ticket to send the phone to recovery
I'm using a OnePlus 5. I also had the same problem after an OS update. The OnePlus Native Call Recording Magisk module was indeed the culprit!
Usually, I uninstall Magisk before an OS update. I got lazy and skipped this time. Oh, yeah, now I remember... Random time-wasting stuff like this happens half the time if I skip Magisk uninstall! Lesson learned.
I was able to use the Call Recording module again by uninstalling and then reinstalling Magisk.
Hi guys, so I didnt know that you had to unhide magisk in order to update, this morning I got the notification to update it, clicked on it, and boom, doesnt open anymore, opens for a split second and crashes.
uninstalled the shortcut, installed the apk again, but still same, won't open. Root and everything works as usualy, but It won't open the app.
I run stock OS with just magisk for rooting and some modules.
is there a way to uninstall it completely? I imagine being hidden its still installed under another package name, I tried searching for it but can't find anything....
I hope there is a solution that doesnt require wiping and starting over......
Thanks!!
FIXED, I had version 25206 installed, and when updating to 25207, it wouldnt open, found another apk of 25206, reinstalled, it works now!
For some reason, can't seem to update it, I unhide magisk, update the app, its back to not opening, something is wrong here and I cant figure out what exactly.
I've never unhidden Magisk before updating fwiw...
krakout said:
I've never unhidden Magisk before updating fwiw...
Click to expand...
Click to collapse
me neither, but I read somewhere you had to unhide it before updating just in case, thing is now it wont update, doesnt matter if its hidden or unhidden, after installing, it just crashes on opening.
EDIT: seems like its a common issue with canary builds. will wait for a fix.
iTudorS said:
me neither, but I read somewhere you had to unhide it before updating just in case, thing is now it wont update, doesnt matter if its hidden or unhidden, after installing, it just crashes on opening.
EDIT: seems like its a common issue with canary builds. will wait for a fix.
Click to expand...
Click to collapse
The exact reason I use stable. I had the same issue in the past
iTudorS said:
Hi guys, so I didnt know that you had to unhide magisk in order to update, this morning I got the notification to update it, clicked on it, and boom, doesnt open anymore, opens for a split second and crashes.
uninstalled the shortcut, installed the apk again, but still same, won't open. Root and everything works as usualy, but It won't open the app.
I run stock OS with just magisk for rooting and some modules.
is there a way to uninstall it completely? I imagine being hidden its still installed under another package name, I tried searching for it but can't find anything....
I hope there is a solution that doesnt require wiping and starting over......
Thanks!!
Click to expand...
Click to collapse
Canary Magisk 25207 had a bug in it which prevented the app from opening. It has been fixed so hopefully a new build will be released soon.
Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk
Fix #6637
github.com
Lughnasadh said:
Canary Magisk 25207 had a bug in it which prevented the app from opening. It has been fixed so hopefully a new build will be released soon.
Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk
Fix #6637
github.com
Click to expand...
Click to collapse
yep, updated this morning to the new build, all is OK!
iTudorS said:
yep, updated this morning to the new build, all is OK!
Click to expand...
Click to collapse
canary? and how do you update it? unhide first then update or just update while hidden?
amders said:
canary? and how do you update it? unhide first then update or just update while hidden?
Click to expand...
Click to collapse
yes, canary, this time I didnt do anything, left it hidden and updated, everything worked out just fine.
iTudorS said:
yes, canary, this time I didnt do anything, left it hidden and updated, everything worked out just fine.
Click to expand...
Click to collapse
ah.. ok... just got the magisk update notification.. btw do you use google wallet? if yes can it use? i'm stuck on adding card step..
amders said:
ah.. ok... just got the magisk update notification.. btw do you use google wallet? if yes can it use? i'm stuck on adding card step..
Click to expand...
Click to collapse
yes, wallet working perfectly with safetynet-fix by displax. no issues whatsoever