Ive read that Xposed for Lollipop has issues with Sygic.
Is this true??
UPDATE 2015 10 10: rovo89 has taken a personal look at the problem and it seems to be fixed in later versions of Xposed. Here is his comments thruout this thread if you don't want to read the entire thread (like I had to do):
rovo89 said:
Could you try this test build please? It fixes a problem that results in crashes (dump contains "art::Field_get"). It also disables Xposed's resource hooking mechanisms inside the Sygic process, as they have implemented something very similar which also replaces resources at low level.
Click to expand...
Click to collapse
rovo89 said:
Forgot to mention that after flashing this, you have to clear the Dalvik cache or reinstall Sygic. Obviously, tests only make sense if you're using the original/unpatched app and experience crashes with Xposed v70.
Click to expand...
Click to collapse
rovo89 said:
That's totally correct, but for the average user, it's a much simpler to simply delete the whole cache or reinstall the app.
Cool, thanks for testing! So I'll publish an official update soon with these fixes and also commit and push them to GitHub. I'm pretty sure that the authors of unofficial versions will quickly pick them up.
Click to expand...
Click to collapse
rovo89 said:
There's already an option that disables resource hooking completely for the whole ROM. That's useful in case the ROM itself comes with resource-modifying code. Sygic is the first application I'm aware of that "hacks" the system code at such a low level. So I don't think such an option would be required, and in most cases, people wouldn't know exactly when to use it, which would result in strange bug reports for modules which stop working if you disable the wrong thing.
Click to expand...
Click to collapse
rovo89 said:
Are you referring to my comments above? I just said they're modifying resources. Didn't check what they do with that in details, maybe replacing drawables/texts on the fly? I haven't checked whether they do any changes to GPS.
Click to expand...
Click to collapse
rovo89 said:
Not crashing for me with the (expired) trial. Maybe you block access to contacts with some app or module?
Click to expand...
Click to collapse
rovo89 said:
Sygic is working fine for me with v71 - as much as I could test without buying premium. If you still have issues, please send me the logcat of the crash. I can't exclude that there are still issues, but I can't look at them without the log.
Click to expand...
Click to collapse
rovo89 said:
I can't make any sense out of this. It's looking for the class com.flurry.android.FlurryAgent and can't find it. It doesn't seem to use the app's class loader though but the system class loader, so maybe that's a bug on their side. Then again, this might not even be the root cause, as it only tries to load this class because something in Android_ContactsReadNext seems to have failed. If you use any kind of privacy app or ROM feature that might block access to contacts, that could be the reason. It might also be a contact with invalid or too long fields. Have you tried if the same issues appear without Xposed?
Click to expand...
Click to collapse
rovo89 said:
You probably mean the general issues with Sygic that I've fixed with v71. There seems to be an (individual?) issue where the app still crashes when going to the contact selection, but works fine otherwise.
Click to expand...
Click to collapse
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
godmode1970 said:
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
Click to expand...
Click to collapse
Downgrading to 15.0.4 works. Anything else just fails.
Im sure it is NOT a Sygic problem, its Xposed interfering with Sygic.
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Same here on One M8 with stock lollipop 5.0.2 ROM. Sygic works only till 15.0.4.
Sygic crashes with Xposed for Lollipop on Moto G 2014
On Moto G 2014
... crashes on Motorola Stock ROM 5.0.2
... crashes on CM12.1 (5.1.1)
Sygic version: 15.1.15
(works fine with Xposed on KitKat)
rabah5 said:
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Click to expand...
Click to collapse
Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:
Go into /system/bin/ and delete app_process32 and app_process32_xposed
Rename app_process32_original to app_process32
Delete dex2oat and rename dex2oat.orig to dex2oat
Repeat the above step for oatdump and patchoat
Go up a directory and then into the lib directory
Delete libart.so and rename libart.so.orig to libart.so
Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
Delete libxposed_art.so
Go up a directory and delete xposed.prop
Go into framework directory and delete XposedBridge.jar
Reboot your device.
Yeah, Sygic is completely broken with Android 5.0 and Xposed.
Any fix to sygic 15.x.x on android 5 + xposed?
Thanks all!!!
AFAIK, Sygic is working on this problem, but it is a low priority issue for them, so they didn't wrote any ETA.
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
ciccio83q said:
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
Click to expand...
Click to collapse
Legally, you should try to search and download an official apk of version 15.0.4, install it and disable auto update in Play Store.
The app you search for is called RootCloak but it does not make any difference.
Sent from my NotePRO 12.2 LTE using Tapatalk.
Well. To be onest with you I found only modded apk. And it bothers me because I don't wanna use a cracked app when I paid for it. Thanks anyway. No xposed for now.
Can someone give the 15.0.4 package. The support gives me only the 15.0.9 package which is crashing at start too..
Thanks
I'm running Sygic 14.7.4 on my device with Xposed and it's fine with 2014.09 TA maps. 15.x.x does not work-crashes.
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
_mysiak_ said:
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
Click to expand...
Click to collapse
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Surely, this is Sygic 15.0.4 original (official) version:
Link for download
ciccio83q said:
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Click to expand...
Click to collapse
Create an empty file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
For example from TWRP or terminal type this command and reboot:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
You can create flashable file, or terminal shortcut to speed up the process. To enable Xposed again, just delete the "disabled" file (through file manager or from terminal again).
Source
I've tried 15.0.4 it's working but crashing during navigation, the moment you start navigation it'll crash. Checked with Nexus 7 DU 5.1.1 and Xiaomi Mi3 Mokee 5.1.1.
Related
Xposed Framework will not install on my Straighttalk Samsung Centura for nothing. I tried installing different versions of Xposed Installer and that didn't help. Yes, I'm rooted. I use other root apps with no problem. I use Superuser. It works fine. Ok, so when I press Install/Update on Xposed Installer I giver it Superuser permissions and it says Install/Update with the little circle going around. It stayed like that all night. What am I doing wrong? I started thinking and I even changed /system permissions to r/w with File Explorer because my installation mode is Classical(write to /system directly) and thag didn't either. Does Xposed Installer use any data because I'm currently throttled and my 3G speeds are so slow. So I was wondering when you press Install/Update does Xposed Installer download something or no? Can someone please tell me what I'm doing wrong here?
Have you tried a different installation method? Also, can you post a logcat when the circle keeps on spinning?
Only the "Downloads" section uses the Internet.
GermainZ said:
Have you tried a different installation method? Also, can you post a logcat when the circle keeps on spinning?
Only the "Downloads" section uses the Internet.
Click to expand...
Click to collapse
I took a couple of screenshots. I'm not very techy. I don't know what a logcat is. :/
TreQuanYoung said:
I took a couple of screenshots. I'm not very techy. I don't know what a logcat is. :/
Click to expand...
Click to collapse
To change the installation mode: tap "installation mode".
To take a logcat: Google "logcat". There are plenty of great tutorials around that cover pretty much everything.
EDIT: Also make sure you're using the latest version of the Xposed Installer.
GermainZ said:
To change the installation mode: tap "installation mode".
To take a logcat: Google "logcat". There are plenty of great tutorials around that cover pretty much everything.
EDIT: Also make sure you're using the latest version of the Xposed Installer.
Click to expand...
Click to collapse
What installation mod should I change it to? And yes I tried using the latest version. That's why I'm using v2.6
TreQuanYoung said:
What installation mod should I change it to? And yes I tried using the latest version.
Click to expand...
Click to collapse
Any of the recovery methods. One is automatic, the other manual - pick whatever you want.
A logcat of the classical installation method will be useful if you want to see it fixed (if possible), so you probably want to do that first if you care.
TreQuanYoung said:
That's why I'm using v2.6
Click to expand...
Click to collapse
Too bad 2.6.1 is the latest stable version. Shouldn't make a difference, though.
GermainZ said:
Any of the recovery methods. One is automatic, the other manual - pick whatever you want.
A logcat of the classical installation method will be useful if you want to see it fixed (if possible), so you probably want to do that first if you care.
Too bad 2.6.1 is the latest stable version. Shouldn't make a difference, though.
Click to expand...
Click to collapse
Ok, do you want me to screenshot the logcat?
TreQuanYoung said:
Ok, do you want me to screenshot the logcat?
Click to expand...
Click to collapse
No, please paste the full logcat somewhere like pastie.org or bpaste.net. You can also zip it and attach it here.
GermainZ said:
No, please paste the full logcat somewhere like pastie.org or bpaste.net. You can also zip it and attach it here.
Click to expand...
Click to collapse
Also I didnt mention that when I give it Superuser permission, a popup keeps saying "shell has been granted Superuser permissions". I think that's normal though. It only does it for about a minute and the circle keeps spinning
TreQuanYoung said:
Also I didnt mention that when I give it Superuser permission, a popup keeps saying "shell has been granted Superuser permissions". I think that's normal though. It only does it for about a minute and the circle keeps spinning
Click to expand...
Click to collapse
Didn't the Xposed Installer warn you about a segmentation fault? Check the FAQ and try the build there (search for "segmentation fault").
GermainZ said:
Didn't the Xposed Installer warn you about a segmentation fault? Check the FAQ and try the build there (search for "segmentation fault").
Click to expand...
Click to collapse
Thank you so much for your help. I installed XposedInstallerStaticBusyBox_v1.apk and Xposed Framework is installed. I just have to reboot.
using xposed frameworks for long time now, I have a lot of old versions of my modules on phone
where are this module versions stored?
how can I delete this old versions I never will reuse/reinstall again?
Frank
Not sure it will help, as you surely noticed that before. Anyway.... In the "Modules" section of Xposed, a long press on the module you want to get rid of will bring you the option you're looking for.
To add to what Roudier said, modules are just like normal apps and can be uninstalled the same way.
I think everyone misunderstood the question.
I think he's asking where the old versions of each module are stored, as it's possible to uninstall the latest version of a module and install an older version that you had installed without downloading it again.
Basically, where are the downloaded files stored?
kingvortex said:
I think everyone misunderstood the question.
I think he's asking where the old versions of each module are stored, as it's possible to uninstall the latest version of a module and install an older version that you had installed without downloading it again.
Basically, where are the downloaded files stored?
Click to expand...
Click to collapse
That's handled by the download manager, it's usually cleared after a reboot if I'm not mistaken.
Doesn't sound like that's what he's asking about, though.
GermainZ said:
That's handled by the download manager, it's usually cleared after a reboot if I'm not mistaken.
Doesn't sound like that's what he's asking about, though.
Click to expand...
Click to collapse
That's how I read it.
[email protected] said:
I have a lot of old versions of my modules on phone
where are this module versions stored?
how can I delete this old versions I never will reuse/reinstall again?
Click to expand...
Click to collapse
He's seems to be specifically asking about old versions of modules there.
In any case, I actually wanted to know where old versions of installed modules were stored so I could delete them and your reply provided the required information. They were all in the download manager and were not deleted after a reboot, so I manually deleted the specific old versions of modules that were no longer required. Thanks.
kingvortex said:
That's how I read it.
He's seems to be specifically asking about old versions of modules there.
Click to expand...
Click to collapse
you absolutly right.
I want to remove my old versions of modules.
kingvortex said:
In any case, I actually wanted to know where old versions of installed modules were stored so I could delete them and your reply provided the required information. They were all in the download manager and were not deleted after a reboot, so I manually deleted the specific old versions of modules that were no longer required. Thanks.
Click to expand...
Click to collapse
@kingvortex,
can please told me, where download manager is storing this modules
[email protected] said:
you absolutly right.
I want to remove my old versions of modules.
@kingvortex,
can please told me, where download manager is storing this modules
Click to expand...
Click to collapse
I deleted them via the download manager.
Enter it via "Downloads" in your app drawer, then long press any item you want to delete and a trash icon should show up to allow you to delete them (at least that's how it works on my device).
Hi,
that's easy
I must confess that I rarely used the App Drawer and the download app I've never particularly noticed
This is about to change, thanks for the hint :good:
Frank
You're welcome.
This has been fixed xda postNote: This is a temporary solution until someone fixes this in Xposed. Also I use my module "SnapColors" as a example throughout this post but this fix should for work any module. I've tested it with other modules and it works. If the module did not previously work on 5.0 then ignore this post and continue on with life.
TL;DR Version:
I found a temporary solution of getting modules to work on 5.1 for modules that worked on 5.0 but don't work on 5.1.
Non-TL;DR Version: Backstory and how I found his temporary solution
So a couple days ago I decided to start working on bring my module(s) to Xposed running on 5.1. In doing so what I noticed with a lot of the modules they seem to crash the app without throwing any kind of error whatsoever. Take for example one of my modules "SnapColors", if SnapColors was enabled in Xposed Installer SnapChat would always crash without throwing any error it wouldn't even say anything along the lines of "process has stopped unexpectedly" it would just close the app. So because of this behavior it led me to believe something was wrong with Xposed and not with my module(s). So I went thought what could be broken in Xposed thats causing this because 5.0 is just one up to 5.1 so the changes couldn't be that big. I went though the things that could cause this and came across "dalvik-cache" I remember reading somewhere Xposed makes some changes to the cache file (.dex) thats created during the creation of dalvik-cache files. So then I thought what if in 5.1 a small change was made to the process of making the dalvik cache files and thats what is causing the problem. So I decided to delete the dalvik cache file for SnapChat which is what my module was hooking into, then I tried opening SnapChat again but it crashed so I tried opening it again and what do you know it opened without any problems with my module fully working without any problems. The fix was kind of a guess too.
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
What you have to do is delete the dalvik cache file for the app the module is for.
Example: SnapColors a module for SnapChat, so we have to delete the dalvik cache file for SnapChat.
What you need:
1) A file manager with root access, or terminal knowledge.
2) Package name example for SnapChat its "com.snapchat.android". How to get the package name look below theres a how to.
Steps for deleting the cache file:
Make sure the app is not running in the background close it if it is.
Method 1) Via terminal command:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@"package name here without the quotes"*
Example command for SnapChat would be don't forget the "*" at the end:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@com.snapchat.android*
Method 2) Via file manager: Navigate to /data/dalvik-cache/arm/ look for a file starting with the name [email protected]@"package name here without the quotes".apk delete this file and thats it.
Now try and open the app if it doesn't work close the app then try opening it again. make sure that apps not running in the background before trying again.
Getting package name
Via terminal command:
Code:
ls /data/data/ | grep "the app name here without quotes"
Via app: Install https://play.google.com/store/apps/details?id=com.electricsheep.asi
Open it-> Apps tab-> Tap the app-> look for "Package name:" should be the first thing.
Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix
mmamedov said:
Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix
Click to expand...
Click to collapse
Yup. I wish I could help but my knowledge of c++ is limited.
Why are apps on 5.1 creating this dalvik file if the runtime is ART?
r25txe said:
Why are apps on 5.1 creating this dalvik file if the runtime is ART?
Click to expand...
Click to collapse
The files are used by art despite the name of the folder "dalvik-cache". I think don't quote me on that.
Subscribed
sent from your moms phone
Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app
Programming4life said:
Yup. I wish I could help but my knowledge of c++ is limited.
Click to expand...
Click to collapse
Enough knowledge to help me out on twitter ALLLL the time! Lol
Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks
lolzas said:
Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
mjrifath said:
Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
Another step into 5.1 with xposed.. Only needs rovo magic Touch.. Thanks for it...
Programming4life said:
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
Click to expand...
Click to collapse
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...
spaxon said:
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...
Click to expand...
Click to collapse
I said ~95% because some modules need to be updated strictly for lollipop and won't work no matter what. Its more like 99% but 95% just in case.
Programming4life said:
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
Click to expand...
Click to collapse
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?
spaxon said:
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?
Click to expand...
Click to collapse
After installing a module you must enable it and then do a reboot/soft reboot yes that is true. Gravitybox LP and Flat Style Bar Indicators both modify the android system itself so theres nothing we can really do until someone fixes this bug in Xposed's code.
What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk
Youtube background playback don`t works with that method
FuMMoD said:
What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Android doesn't like it when the permissions are changed for a cache file so it'll just fc the app.
jabarel said:
Youtube background playback don`t works with that method
Click to expand...
Click to collapse
Worked for me you may have a out dated version of YouTube or YouTube background.
Im running truepure Rom. Would love to have android pay working, but just cant get it going. Assuming will have to live without for a while...
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
rsmiff said:
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
Click to expand...
Click to collapse
As I understand, Android pay pretty much only works works with stock ROM due to system system Partition Modifications made on custom Rom's. I understand some devices have had limited luck with Custom Roms but for the most part, Stock only. All that said, I just upgraded to MM 6.0 on Friday and then Rooted using the Beta System less Root method from the forum and Android Pay works like a charm, added cards no problem and works perfect at the retailers that accept it. Most recently, RiteAid in my area. This root is not a full root as I understand but the apps I use get permissions without an issue , Quick Boot is my must have and it works just fine. (Did notice ES File Explorer wont' allow full access to my device but Root Browser did. Adding XPOSED would still disable Android Pay since it modifies the partititons , I really wish that was not the case but I really love Android pay so for now, I might just have to do without it. I am sure you saw the Root Method but just in case, the link is below. Follow the instructions carefully and don't forgot to hit the Do Not Install button in TWRP (Your device does not appear to be rooted) every time you reboot from there . You'll know what I am talking about as soon as you get to that point.
Anyway, good luck!
Mike
http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405
EDIT: And I broke pay somehow... So I guess this is not a great guide...
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
timeToy said:
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
Click to expand...
Click to collapse
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
So it seems that flashing zips that modify the system partition in any way will break Android pay, but not if you modify it while in the OS itself. I've been using the cigital safteynet playground app to check each time I make a modification. Definitely make a backup of /system so you can always restore Android pay functionality if a mod breaks it.
Also using Xposed WILL break Android pay. I try not to miss it much, but honestly I've got my MXPE pretty much perfect for me, and what apps I use that require root are all working well with systemless root.
Sent from my XT1575 using Tapatalk
timeToy said:
- Renamed system\recovery-from-boot.p to .bak in TWRP
Click to expand...
Click to collapse
What does this do?
EVR_PR said:
What does this do?
Click to expand...
Click to collapse
This prevent the stock recovery from overwriting TWRP
I actually have TWRP in read only mode, which allows stock to overwrite it, and the file ends in .p.
Will changing it to .bak allow me to remove the read-only status?
bb12489 said:
However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
innoman said:
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
Click to expand...
Click to collapse
Well the flashable zip as the folder structure laid out inside it, so just use that to know where to move the files. Usually the permissions are rw-r-r in most folders, but just check other files in the directories to make sure what permissions to set. That's all I've done to get the dialer working at least. I imagine it works for other things as well.
bb12489 said:
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
timeToy said:
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
Click to expand...
Click to collapse
I followed the same steps that bb did and am getting the same results you are. Android Pay was working just fine with systemless root and Adaway, but so far, DPI changes and the Google Dialer have both broken Android Pay for me.
I lost it manually installing the new emoji font pack and google keyboard. I manually copied the files over and fixed the permissions.
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Jay794 said:
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Click to expand...
Click to collapse
That's because it isn't but it should be coming to the UK in the next few weeks according to rumours.
Sent from my LG-D855 using Tapatalk
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Shtiff1 said:
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Click to expand...
Click to collapse
maybe it is enough if you download the module-template edit config.sh and module.prop to an ID if your choice and in config.sh also the REPLACE part with /system/app or priv-app/Lockscreen/ ?
something like this maybe? but here ends my know-how
Shtiff1 said:
I'm looking for a module to be created, or if I could do it not sure. Something to do the same as "lockscreen disabler" did in Xposed. Willing to donate. App in question for exchange email is "Email MOTOEMAIL.00.05.0072". Currently running XT1254, 6.0.1, stock rom. Thank you.
Click to expand...
Click to collapse
First, that's not a donation you're talking about, it's a bounty.
Second, if it can't be done without Xposed, it can't be done with Magisk. So don't hold your breath.
wiQbold said:
maybe it is enough if you download the module-template edit config.sh and module.prop to an ID if your choice and in config.sh also the REPLACE part with /system/app or priv-app/Lockscreen/ ?
Click to expand...
Click to collapse
What? I don't think you understand what the REPLACE part of the config.sh file does.
During installation, that little entry puts a file called "replace" in each folder listed, in the module folder structure. Every time Magisk mounts a module and finds that file it will completely wipe (systemlessly, of course) the corresponding folder in /system.
If you want to replace a file on your device with one you've edited, all you have to do is to put that file in the module zip, under the same folder structure it can be found on your device. After that Magisk's Magic Mount will do it's thing...
Didgeridoohan said:
First, that's not a donation you're talking about, it's a bounty.
Second, if it can't be done without Xposed, it can't be done with Magisk. So don't hold your breath.
What? I don't think you understand what the REPLACE part of the config.sh file does.
During installation, that little entry puts a file called "replace" in each folder listed, in the module folder structure. Every time Magisk mounts a module and finds that file it will completely wipe (systemlessly, of course) the corresponding folder in /system.
If you want to replace a file on your device with one you've edited, all you have to do is to put that file in the module zip, under the same folder structure it can be found on your device. After that Magisk's Magic Mount will do it's thing...
Click to expand...
Click to collapse
right. my consideration was to wipe the lockscreen folder in system to disable it
wiQbold said:
right. my consideration was to wipe the lockscreen folder in system to disable it
Click to expand...
Click to collapse
Ok. In that case I believe you haven't quite understood the request...
Didgeridoohan said:
Ok. In that case I believe you haven't quite understood the request...
Click to expand...
Click to collapse
that could be true. do not have any device older then nougat and can t try the xposed-module.
thought it disable only the lockscreen.
wiQbold said:
that could be true. do not have any device older then nougat and can t try the xposed-module.
thought it disable only the lockscreen.
Click to expand...
Click to collapse
From what I can tell it disables the lockscreen while tricking apps that require a lockscreen into thinking it's enabled.
Easy-ish with Xposed, impossible with Magisk unless you manually edit the app in question to not detect the lockscreen state and then use a Magisk module to mount it to your device.
Didgeridoohan said:
From what I can tell it disables the lockscreen while tricking apps that require a lockscreen into thinking it's enabled.
Easy-ish with Xposed, impossible with Magisk unless you manually edit the app in question to not detect the lockscreen state and then use a Magisk module to mount it to your device.
Click to expand...
Click to collapse
That is correct. When i opened phone before it just had swipe up to open. Now I have to enter lock code every time. I haven't done anything with adb before, always do everything from the phone. I've seen the apk "exchangenopin" but I can't try it, cause I can't download the apk anywhere. Those from other thread seem to go to ad sites. I figured that it wouldn't of been that difficult because the exchangenopin "supposedly" works w/o Xposed. That's why I was hoping for a module. I found something to replace my "insert custom text" module from Xposed, now just need something to replace for lockscreen. Lol. Liking Magisk though.
I experienced the same problem with my realme 5i smartphone, I tried to install the latest Magisk via the OrangeFox recovery because I had never rooted my smartphone before. but I have installed pixel 5 archipelago project. In this case, after installing magisk and successfully entering the lockscreen, here the problem occurs because I can't enter the lockscreen PIN and can't do anything, I can't even turn off my phone. But here I found a solution, namely using a google account and trying to wipe data via the Google Play application, namely find my devices and then delete it there and it worked for me