My phone is rooted and has Xposed, Snapprefs, and Snapchat 9.21.1.0 installed. When I tap on the Snapchat icon, my phone hangs for a few minutes. It doesn't respond to any of my touches/button presses. On top of that, Snapchat usually just ends up not loading, and then my phone will crash and restart within a minute of being "usable" again. Is there any way to fix this? This does not happen if Snapprefs is uninstalled/disabled. I logged into Snapchat before installing Xposed, and I have RootCloak installed, with Snapchat in the apps, and "Snapprefs","Snapprefs.apk","XposedBridge" and "Xposedbridge.jar" in the keywords in RootCloak.
D168 said:
My phone is rooted and has Xposed, Snapprefs, and Snapchat 9.21.1.0 installed. When I tap on the Snapchat icon, my phone hangs for a few minutes. It doesn't respond to any of my touches/button presses. On top of that, Snapchat usually just ends up not loading, and then my phone will crash and restart within a minute of being "usable" again. Is there any way to fix this? This does not happen if Snapprefs is uninstalled/disabled. I logged into Snapchat before installing Xposed, and I have RootCloak installed, with Snapchat in the apps, and "Snapprefs","Snapprefs.apk","XposedBridge" and "Xposedbridge.jar" in the keywords in RootCloak.
Click to expand...
Click to collapse
Which Xposed framework version do you have installed on your device along with Xposed Installer?
Does Xposed Installer say that the framework is active (in green text)?
Short Circuit said:
Which Xposed framework version do you have installed on your device along with Xposed Installer?
Does Xposed Installer say that the framework is active (in green text)?
Click to expand...
Click to collapse
It's not an issue with Xposed as far as I know. Every other module that I have installed works fine. I have version 81, and it's active.
The issue is with Snappprefs. After uninstalling it, I was able to use snapchat just fine again. Seems there's some bug with it :/
Also, do you also have issues with Snapchat camera going dark when recording videos, and the front camera being way too dark compared to the normal camera app?
cid7 said:
The issue is with Snappprefs. After uninstalling it, I was able to use snapchat just fine again. Seems there's some bug with it :/
Also, do you also have issues with Snapchat camera going dark when recording videos, and the front camera being way too dark compared to the normal camera app?
Click to expand...
Click to collapse
Sorry, I didn't realize there was a response. I don't/didn't have any other issues with Snapchat other than the Snapprefs issue
Related
Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?
Anderson2 said:
Am I the only one with stock 4.4.2 whose camera freezes?
I've been battling the problem that if I use the camera on the Nexus 5 it will sometimes freeze the phone. It may happen after a variable amount of pictures are taken. Suddenly the phone freezes and only a reboot will get it back to normal. I've asked in this forum without success and then found this
http://stackoverflow.com/questions/5880096/problem-using-camera-api-on-android?rq=1
Any solutions anyone?
Click to expand...
Click to collapse
What's your phone setup? Are you rooted with a custom ROM?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146
Anderson2 said:
Rooted, stock 4.4.2 ROM.
Nova prime launcher.
No syncing on anything.
Use xprivacy, AFWall+, gravitybox. (but all 3 disabled with no improvement).
Camera is essentially unusable because of need to reboot every few pictures. Screenshots in my other thread.
http://forum.xda-developers.com/showthread.php?t=2761146
http://forum.xda-developers.com/showthread.php?t=2761146
Click to expand...
Click to collapse
dont disable the exposed, delete it(remove everything xposed completely), reboot, then try your camera
I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.
Anderson2 said:
I would hate to do that because I really like xposed. But I'll make a nandroid backup, and then do as you say. If it's no better, I could always restore the nandroid. But nobody else has noticed any connection between xposed and Google camera. I "believe" the problems started when I updated to the latest camera update. Wish I could find the pre update camera app.
Click to expand...
Click to collapse
xposed causes many many random issues that are undocumented. for many not a single issue, for others its like a phone full of gremlins.
Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?
Anderson2 said:
Well, tis done. I'll see if the camera behaves. It takes time for it to act up....
Fwiw, I've used xposed for quite a while and the camera freezing only started about 4-6 weeks ago. Maybe it was a recent update.
I uninstalled xposed. Where should I look for files to delete to ensure a good test?
Click to expand...
Click to collapse
honestly, i dont know. i have never needed or been willing to use xposed. an uninstall and a reboot should be fine(dirty flashing your rom again would be best, but i think it will be fine without). just give it some time to test. if its not xposed, restore your backup and we will look further.
I'm afraid to say anything, but I think uninstalling Xposed did it. Will wait longer before breathing a sigh.....
Thank you.
A feature I use all the time is the quick reply feature of the messaging smart extra.
After the latest update, I went to use it and instead of a list of quick responses I got a white screen with "I'm here!" in a large font which then disappeared and the watch went back to the watch face.
I cleared all the data, same issue.
Then I uninstalled it and reinstalled it. Same again.
Has anyone got the same issue?
Can anyone confirm it is working for them?
If it is working for you, do you have the smartwatch xposed module too?
mckenzis said:
A feature I use all the time is the quick reply feature of the messaging smart extra.
After the latest update, I went to use it and instead of a list of quick responses I got a white screen with "I'm here!" in a large font which then disappeared and the watch went back to the watch face.
I cleared all the data, same issue.
Then I uninstalled it and reinstalled it. Same again.
Has anyone got the same issue?
Can anyone confirm it is working for them?
If it is working for you, do you have the smartwatch xposed module too?
Click to expand...
Click to collapse
Do you have find my smartwatch... that sounds like the window that opens... I have the xposed module
You were correct! Thanks. However, when I uninstalled "find my watch", the messaging app appeared twice. Uninstall, then reinstall didn't fix it. Deactivated the smartwatch xposed module, restart watch and phone, this time the icon for calendar opened the quick reply of the messaging app! Uninstall xposed, reinstall sw2 software, reset watch, now it appears to be working normally, however I can't overlap widgets Will check forum for updated hacked apk!
Solved
I solved this issue by reinstalling the stock Sony versions, resetting the watch, then after it was back and functioning normally, I reinstalled xposed framework and module.
Now it is all working perfectly
mckenzis said:
I solved this issue by reinstalling the stock Sony versions, resetting the watch, then after it was back and functioning normally, I reinstalled xposed framework and module.
Now it is all working perfectly
Click to expand...
Click to collapse
Indeed reinstalling one-by-one did helped. I guess the problem was caused by restoring all at once with Titanium.
This morning I came into work and as I unlocked my phone it did NOT ask me for my pattern. I have a number of Xposed modules working, but none have been activated in the meantime of this happening. When I go to Security, my last option is still set, yet I'm not asked to enter any of the option whens unlocking the screen.
Anyone had anything like this happen? I really don't believe I've changed any settings between the security working and not working. This is very troublesome. I'll do a complete reinstall of everything if I have to, but I wanted to see if anyone has heard of this in the meantime.
frankwhite8536 said:
This morning I came into work and as I unlocked my phone it did NOT ask me for my pattern. I have a number of Xposed modules working, but none have been activated in the meantime of this happening. When I go to Security, my last option is still set, yet I'm not asked to enter any of the option whens unlocking the screen.
Anyone had anything like this happen? I really don't believe I've changed any settings between the security working and not working. This is very troublesome. I'll do a complete reinstall of everything if I have to, but I wanted to see if anyone has heard of this in the meantime.
Click to expand...
Click to collapse
Never happened here. Try to uninstall Xposed Framework then reboot and try again.
Primokorn said:
Never happened here. Try to uninstall Xposed Framework then reboot and try again.
Click to expand...
Click to collapse
It's somewhere in the Xposed modules. When I uninstalled the framework, it asked right away for my PIN. I'll go back and see which module is giving me the problem. So far I have installed:
Blurred System UI
Burnt Toast
Chrome New Tab (Xposed)
Complete Action Plus
Gravity Box KK
Notification Count
Shaky
Shortcut in App Info
Unicon
YouTube AdAway
I know I changed a setting (I think in Gravity Box) that makes the lockscreen always require the slider. Then it would ask me for my security PIN or Pattern. But I've had then running for a few weeks now. Blurred System UI is a newer mod for me and I was trying out a Translucent mod for KK as well yesterday, but I uninstalled that.
We'll see. Might even go to the L Preview for a while. It worked great for me, but I missed the Xposed additions.
Thanks for the advice. Good call.
frankwhite8536 said:
It's somewhere in the Xposed modules. When I uninstalled the framework, it asked right away for my PIN. I'll go back and see which module is giving me the problem. So far I have installed:
Blurred System UI
Burnt Toast
Chrome New Tab (Xposed)
Complete Action Plus
Gravity Box KK
Notification Count
Shaky
Shortcut in App Info
Unicon
YouTube AdAway
I know I changed a setting (I think in Gravity Box) that makes the lockscreen always require the slider. Then it would ask me for my security PIN or Pattern. But I've had then running for a few weeks now. Blurred System UI is a newer mod for me and I was trying out a Translucent mod for KK as well yesterday, but I uninstalled that.
We'll see. Might even go to the L Preview for a while. It worked great for me, but I missed the Xposed additions.
Thanks for the advice. Good call.
Click to expand...
Click to collapse
It seems it was Shaky that was causing the issue. I've uninstalled it and won't go back since I don't use it much.
http://forum.xda-developers.com/showpost.php?p=54479878&postcount=44
The title basically sums up this post. I am rooted with magisk, have Franco Kernel installed, as well as edXposed. I have magisk hide turned on for Snapchat and NO third party apps installed that could affect Snapchat (no snap++ or anything like that). This is the forth or fifth time that Snapchat has locked my account for using third party apps and I don't want to loose my account. If anyone has a fix for this or knows if anything I have installed IS affecting Snapchat please help me out! This problem occurred before I had Franco kernal or edXposed installed so I don't think it could be those.
I've tried several times, but unfortunately when i root my device,CODM crashes without any warning. It's not like opens and crashes immediately. Sometimes after loading screen, sometimes in the middle of the match. It just closes, not minimized. What could be the problem. I've got, Magisk, EdExposed, CustoMIUIzer.
tapu_afrad said:
I've tried several times, but unfortunately when i root my device,CODM crashes without any warning. It's not like opens and crashes immediately. Sometimes after loading screen, sometimes in the middle of the match. It just closes, not minimized. What could be the problem. I've got, Magisk, EdExposed, CustoMIUIzer.
Click to expand...
Click to collapse
try uninstalling xposed, it is usually the culprit, rooting (Magisk) shouldn't cause that.
Culprit is the "Magisk Manager". Without root, just the app installed the CODM crashes.
has anti root (like super mario)
You have to have magisk I made the game and apart magisk renamed the application, in magisk settings it puts something like recompiling application with a random name, there put the name you want and that's it, it works perfect, it happened to me and I went crazy. Greetings
niosa said:
has anti root (like super mario)
You have to have magisk I made the game and apart magisk renamed the application, in magisk settings it puts something like recompiling application with a random name, there put the name you want and that's it, it works perfect, it happened to me and I went crazy. Greetings
Click to expand...
Click to collapse
Thanks, recompiling app solved the issue.