Develop Bugs

Can't Access Task Manager with Home Button Anymore

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.

Visual Voicemail

OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a

tygray6 said:
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
Click to expand...
Click to collapse
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip

Okay, thanks
Sent from my HTC6500LVW using XDA Premium 4 mobile app

OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app

tygray6 said:
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you using my empty flashable.zip..?
just pull vvm.apk and put in system/app
Once I get my phone back, and or you have S-OFF this won't be an issue.
Aroma will solve a lot of these types of issues as well.

Okay, I put it in place of the null file in the app folder in your flashable zip and after re zipping it it failed when flashing
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Sent from my HTC6500LVW using Tapatalk 4
If I've helped, please hit the thanks button

tylerlawhon said:
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Click to expand...
Click to collapse
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)

andybones said:
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
Click to expand...
Click to collapse
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app

tygray6 said:
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey man thank you very much, it really does mean a lot to me!
and you're very welcome

andybones said:
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Click to expand...
Click to collapse
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone

carm01 said:
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
Click to expand...
Click to collapse
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...

andybones said:
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
Click to expand...
Click to collapse
I will give this a try sometime; kudos

[Q] Multiple Xposed Modules

I've got the following modules installed: Nottach Xposed, Wanam Xposed, XBlast Tools.
Each provides something unique that the rest don't have. The issue I'm having is that when I open up one of the modules, it loads it's settings and overwrites the other modules. Here is a sample scenario:
1) Open first module, set the number of signal bars to 6.
2) Open second module, but don't touch the default of 4 signal bars and change the color of the seekbar or something.
3) Restart.
4) The 4 bars overwrites the 6.
I know these conflicts arise with the territory when using multiple modules that have the same options for one setting. My question is, is there any possible way I can track the changes a module makes, and create a script from it that gets applied whenever I boot up my phone. Is that even possible?
It would be nice to have one script that can unify all the changes the modules make. I'm assuming it would have to be an Xposed module itself since the changes are made at startup. Anyone have any suggestions or tips I may find useful?

xdapowerapps said:
I've got the following modules installed: Nottach Xposed, Wanam Xposed, XBlast Tools.
Each provides something unique that the rest don't have. The issue I'm having is that when I open up one of the modules, it loads it's settings and overwrites the other modules. Here is a sample scenario:
1) Open first module, set the number of signal bars to 6.
2) Open second module, but don't touch the default of 4 signal bars and change the color of the seekbar or something.
3) Restart.
4) The 4 bars overwrites the 6.
I know these conflicts arise with the territory when using multiple modules that have the same options for one setting. My question is, is there any possible way I can track the changes a module makes, and create a script from it that gets applied whenever I boot up my phone. Is that even possible?
It would be nice to have one script that can unify all the changes the modules make. I'm assuming it would have to be an Xposed module itself since the changes are made at startup. Anyone have any suggestions or tips I may find useful?
Click to expand...
Click to collapse
Multiple Xposed modules is one of the best way to get your phone
all messed up... My suggestion is stick with you favorite module.
Good luck!

Misterjunky said:
Multiple Xposed modules is one of the best way to get your phone
all messed up... My suggestion is stick with you favorite module.
Good luck!
Click to expand...
Click to collapse
Well, it's a pain in the ass for the first time setup, but once everything is set, I don't have to touch it again which is plus. But if I decide to make one little change, things reset and I have to start again. Sigh. Wish all the All-in-One modules had the "On-Off" switch so they don't make any changes until you enable it and apply. Wishful thinking. :crying:

re: Xposed Modules
xdapowerapps said:
Well, it's a pain in the ass for the first time setup, but once everything is set, I don't have to touch it again which is plus. But if I decide to make one little change, things reset and I have to start again. Sigh. Wish all the All-in-One modules had the "On-Off" switch so they don't make any changes until you enable it and apply. Wishful thinking. :crying:
Click to expand...
Click to collapse
There is something else which could be done by the Xposed DEVS
to upgrade the app to make it a whole lot easier for all the users.
All the modules should create a log with time/date stamp along with the specific
changes made to the options and settings in the modules in a format which even
a noob or novice could read and fully understand all the details in the log.
Another thing which could be done to make things easier is to have a SAVE/RESTORE
option in all the modules just like like the better launchers have.

Misterjunky said:
There is something else which could be done by the Xposed DEVS
to upgrade the app to make it a whole lot easier for all the users.
All the modules should create a log with time/date stamp along with the specific
changes made to the options and settings in the modules in a format which even
a noob or novice could read and fully understand all the details in the log.
Click to expand...
Click to collapse
Agreed, that would be great to have on hand. Great idea. :highfive:

[Q] In the Phone App - the Logs are default set to Missed rather than All

So I have a rooted Note 4 with stock ROM, and I recently installed Wanam Xposed. After installing this I have noticed that when I open the Phone App and go to Logs, it always defaults to missed calls, where before installing Wanam it defaulted to All Calls. Anyone know how to fix this? I cannot find the setting in Wanam that caused this (or if it even is Wanam), nor can I find any other setting for this.

http://forum.xda-developers.com/showthread.php?p=58365213
Since you already have wanam, just delete the highlighted line in the /system/csc/feature.xml and reboot.

samep said:
http://forum.xda-developers.com/showthread.php?p=58365213
Since you already have wanam, just delete the highlighted line in the /system/csc/feature.xml
Click to expand...
Click to collapse
Beautiful, thanks!!!

DrSeussFreak said:
Beautiful, thanks!!!
Click to expand...
Click to collapse
You're welcome. If you have to redo stock, upgrade to custom Rom or if/when we're fortunate to get Xposed for lollipop, remove the line before activating wanam. If not before, then after. Ideally, the primary file is the target for developers as I explained in the original post; avoids users breaking it with wanam but still functional for non-wanam users.
Sprint choose to be unique; this fixes that so wanam works as intended.

Gravity box running on marshmallow 6.0.1

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