Related
I can no longer hold home to get to the task manager. Holding down home does nothing now and I can't figure out why or what I could have done to cause this. Restarting doesn't fix it. Anyone know how I can restore this function without reflashing? The last thing I did was install Xposed Framework with modules 'App Settings 0.4' and 'xMulti Window Mod 1.3' so I'm thinking that's what caused it but I'm not sure why.
ROM: Tweaked 2.4.1
Kernel: Stock
Your best bet is to try and disable the new modules in xposed. Or disable xposed all together Then reboot..... also there's nO need to post in multiple threads. Patience
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Your best bet is to try and disable the new modules in xposed. Or disable xposed all together Then reboot..... also there's nO need to post in multiple threads. Patience
Click to expand...
Click to collapse
Disabled the two modules and rebooted. That fixed it. Re-enabled them, rebooted, problem came back. Double checked and the modules are configured as instructed. Everything on my phone seems fine and working great except this one little issue and it's an annoying one. I don't want to give up this MOD so there must be a way to isolate this but I must admit I'm lost.
After searching high and low, i've finally found the screen off animation i wanted, this particular mod is not mine i'm just providing a find for anyone who is in the same situation.
Thanks to @zst123 for originally posting this
Requirements:
Root access
Custom recovery
Rom running android 5.0XXX
Also note functional on 5.1.XXX ROMs.
*New section for Marshmallow ROMs.
1. Go here and download this http://forum.xda-developers.com/attachment.php?attachmentid=3292041&d=1430517906
or this one if you're on android 5.1 http://forum.xda-developers.com/attachment.php?attachmentid=3313055&d=1431639027
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3631566&d=1454436795
2. Download the Alpha build xposed framework from here http://forum.xda-developers.com/attachment.php?attachmentid=3200857&d=1425849071
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
3. Reboot to recovery and install the .21 or build or the .22 build if you're on 5.1XXX or the v80 sdk23 build if you're on 6.0.XXXX then reboot *NOTE* boot can take some time, 10 minutes at times
4. Once booted, install the alpha build apk downloaded in step 2 using a file manager.
5. Open Xposed and navigate to download, search for screen off animation and download the module.
6. Navigate to modules and enable them, reboot your device.
7. Open the app and choose a screen off animation.
8. Perform a reboot, Done.
FYI, it has been known that xposed can cause bootloops on the M9 so tread carefully and back up prior to installing it.
I can confirm that this and xposed with this installation method works as expected on Leedroid, other ROM's should work but I haven't tested them.
Can also confirm that for the most part, sense 6 toolbox and XUI Mod work too, and again this is not my software.
PS: Just like to add that the screen off Vertu animation is my personal favourite, it's a classy finish to a phone that deserves it.
------------------THEMING------------------
@ineedone This is his theme.
You need to flash the theme after xposed, clearing cache and dalvic after the initial installation of Chameleon. If you don't then you can (not always) end up in a boot loop, if you didn't wipe the caches then power down and boot back to recovery.
The initial boot after wiping the caches can take a long time, 10 minutes + is not uncommon.
This can also be assumed for any other mods which affect a lot of the ROMs system files.
Confirmed with Newest Leedroid and chameleon.
http://forum.xda-developers.com/showthread.php?t=3082322
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
aooga said:
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
All sorted, thanks mate, oversight on my part.
Posted in error
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Aye I've used gravity before but have avoided it as I get everything I need from xui and screen off animation. I don't even use sense toolbox no more. I've read that Xposed works with 5.1 and there is a framework for it but as I haven't tested it on a HTC device I've not added it to the OP that its fully functional.
Gravity needs a big update, there have been quite a few broken bits for a while, also found gravity was always very heavy on the system too, might have just been me.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
neverborn said:
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Stock as in not rooted or stock as in rooted on a stock rom, if it's the latter then it should work. That's probably the best way to use these mods. Unfortunately screen off animation as far as I know does not function as of yet. I'm away for a week now, but will be doing some testing of all the mods on my return.
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
That is literally what you are meant to do, some modules are functional, some aren't. For me the screen off animation didn't work and so strange as it might sound, I would miss it and as such I have retained 5.0.2, I really do not see any difference between the two, all modules work, nothing appears broken to me and the battery life is as good as I need it to be. To answer your question in short I get the same message with screen off animation, as if it's not installed. It's because it's not been updated. Either wait for it to be updated or downgrade like me
Updated op. Screen off animation working properly on 5.1, been using it for a while now.
neverborn said:
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
dladz said:
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
Click to expand...
Click to collapse
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
oemfoefoee said:
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
Click to expand...
Click to collapse
Actually in that part of the tutorial, you only need a soft reboot. Regular if you need it but not necessary.
help!
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Vinncent said:
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Click to expand...
Click to collapse
Boot loops are a risk I've written how I was able to get xposed without boot loops but I've also warned that it can happen. If you follow my instructions you stand a food good chance
working great on the latest ViperOne rom... thanks man...
dladz said:
Boot loops are a risk Ive written how I was able to get xposed without boot loops but Ive also warned that it can happen. If you follow my instructions you stand a food chance
Click to expand...
Click to collapse
Food chances are the best!
Works on my m9:highfive:
Krsmqn said:
Food chances are the best!
Works on my m9:highfive:
Click to expand...
Click to collapse
Haha Bloody Auto correct.. Guess my phone is telling me to be a fatty ..
apaquette420 said:
working great on the latest ViperOne rom... thanks man...
Click to expand...
Click to collapse
No worries
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end
deleted
All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
Update: TWRP install method added for those not using Magisk. Just flash the zip and good to go.
Magisk Module v2.1a: Update Sep 5, 2017
https://www.androidfilehost.com/?fid=817550096634797320
TWRP Install:
https://www.androidfilehost.com/?fid=889764386195918352
Thanks intall working
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Great Tweak mate! Thank you so much
I'm expecting an important call today, but will test thoroughly later.
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
badcrow35 said:
Thanks intall working
Click to expand...
Click to collapse
I don't own a OnePlus 5, I have a 3 but I saw a Turkish text and decided to write. How did you get access to OnePlus 5? Have you imported it from abroad or are you living in abroad?
Brought with my friend from abroad UK
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Click to expand...
Click to collapse
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Can anyone confirm if the zip works?
dustintinsley said:
All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
https://www.androidfilehost.com/?fid=889764386195917884
Click to expand...
Click to collapse
Work like a charm wish everything went this easy
Awesome, works just fine. This has been driving me bonkers lol.
Working great! I use xxx rom with latest Magisk. Thx! :highfive:
dreams.sri said:
Can anyone confirm if the zip works?
Click to expand...
Click to collapse
I have not tested it as I use Magisk, but it should work. Worse case is that it will still not answer from notification. Should not cause any boot loop or anything like that. Have you tried the zip? There should be no issues with it, if you have issues please let me know so I can fix it...
Binary Assault said:
Awesome, works just fine. This has been driving me bonkers lol.
Click to expand...
Click to collapse
Same here man. It was driving me nuts. I'm kinda OCD so I had to figure it out. Glad others find it useful...
But OnePlus Dialer Is Better Than Google One ?
Krsambhav16 said:
But OnePlus Dialer Is Better Than Google One ?
Click to expand...
Click to collapse
Not sure that I agree, but to each his own...
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Donald Nice said:
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Click to expand...
Click to collapse
You can do it either way. I prefer doing it via Magisk, but either should work.
does it vibrate when the call connects?
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Thanks for taking time to make it. Just tried and TWRP throws error 6.
Has anyone got this working? I've done everything and the new power menu appears and the Cards and Passes does show up in gestures for about 30 seconds and then disappears. When press the power button it only shows the new power menu and not the cards.
https://www.xda-developers.com/enable-quick-wallet-access-google-pay-pixel-android-10/#disqus_thread
Same issue here. I don't even get the option for cards and passes in gestures menu....
i had to reboot like three times and then the cards magically appeared. It's not something that works instantly.
qman66 said:
i had to reboot like three times and then the cards magically appeared. It's not something that works instantly.
Click to expand...
Click to collapse
Thanks. There is something else connected. I did this mod yesterday and have rebooted multiple times. Are you on a custom kernel?
elreydenj said:
Thanks. There is something else connected. I did this mod yesterday and have rebooted multiple times. Are you on a custom kernel?
Click to expand...
Click to collapse
no
Got it working, but my option to enable it appeared in a different place.
Maybe do a reboot, put your code in if you have one, and then just let the phone sit for awhile.
Sent from my Pixel 4 XL using Tapatalk
Curiousn00b said:
Got it working, but my option to enable it appeared in a different place.
Maybe do a reboot, put your code in if you have one, and then just let the phone sit for awhile.
Click to expand...
Click to collapse
What do you mean by a different place?
elreydenj said:
Thanks. There is something else connected. I did this mod yesterday and have rebooted multiple times. Are you on a custom kernel?
Click to expand...
Click to collapse
I'm on a custom Kernal. Booted many times and the gesture appears but still disappears in a matter of seconds. Very frustrating.
warrencoakley said:
I'm on a custom Kernal. Booted many times and the gesture appears but still disappears in a matter of seconds. Very frustrating.
Click to expand...
Click to collapse
So am I. I wonder if there is a correlation between the custom kernel and the gesture not appearing.
warrencoakley said:
What do you mean by a different place?
Click to expand...
Click to collapse
Yours appeared above Flip to Shh and mines appeared at the bottom of the list.
Sent from my Pixel 4 XL using Tapatalk
elreydenj said:
So am I. I wonder if there is a correlation between the custom kernel and the gesture not appearing.
Click to expand...
Click to collapse
Well the dev didn't specify in his installation instructions that you needed to be on a stock kernal. The only requirement was to be in Android 10. I've tried a few reboots and nothing.
Curiousn00b said:
Yours appeared above Flip to Shh and mines appeared at the bottom of the list.
Click to expand...
Click to collapse
Ah ok. Very strange. Not sure what are or not the full requirements are for installation. It's a bit vague from the dev and no real support on it.
warrencoakley said:
Well the dev didn't specify in his installation instructions that you needed to be on a stick kernal. The only requirement was to be in Android 10. I've tried a few reboots and nothing.
Click to expand...
Click to collapse
You do have the SQLite module installed, yes? GPay fix as well?
1. Install SQLite Module
2. Install GPay Fix
3. Reboot
4. Install GooglePayPowerMenu Module
5. Reboot and wait it out some
Sent from my Pixel 4 XL using Tapatalk
Curiousn00b said:
You do have the SQLite module installed, yes? GPay fix as well?
1. Install SQLite Module
2. Install GPay Fix
3. Reboot
4. Install GooglePayPowerMenu Module
5. Reboot and wait it out some
Click to expand...
Click to collapse
This is what I have installed. My GPay has been working for a long time with these modules installed.
Do I need to do anything else?
The gesture just disappears after a reboot.
Working here :good:
Working fine here. I had to reboot 2 times, disable and re-enable the toggle in order to make it work. Now it runs perfectly fine
warrencoakley said:
This is what I have installed. My GPay has been working for a long time with these modules installed.
Do I need to do anything else?
The gesture just disappears after a reboot.
Click to expand...
Click to collapse
Those are the correct modules and it should be up and running.
After reading things, they sound like scripts so that's why I suggest letting it sit for a little after you boot up. Try reinstalling the modules and try to get the option to come up for you once more.
Sent from my Pixel 4 XL using Tapatalk
Curiousn00b said:
Those are the correct modules and it should be up and running.
After reading things, they sound like scripts so that's why I suggest letting it sit for a little after you boot up. Try reinstalling the modules and try to get the option to come up for you once more.
Click to expand...
Click to collapse
Ok I'll try and reinstall all those modules. Yes as they are scripts it may take a few minutes to run but they don't. Not sure if the permissions should be changed or correct. The creater has another module like this for the live caption which I installed and again are scripts and run perfectly so not sure what's going on. After multiple reboots it appears in gestures and just disappears and nothing happens. See attached.
TENN3R said:
Working fine here. I had to reboot 2 times, disable and re-enable the toggle in order to make it work. Now it runs perfectly fine
Click to expand...
Click to collapse
Did you have issues with the gesture toggle disappearing?
Curiousn00b said:
Those are the correct modules and it should be up and running.
After reading things, they sound like scripts so that's why I suggest letting it sit for a little after you boot up. Try reinstalling the modules and try to get the option to come up for you once more.
Click to expand...
Click to collapse
Tried reinstalling all the modules again and toggling the switch on and off and while doing it in gestures again it just disappeared. No idea what's going on. Not sure if one of my modules is conflicting with this module or not? Just strange it's kind of the same script as live caption but just does not want to play ball