[CLOSED][APP][XPOSED][6.0+] XPrivacyLua Pro companion app

[M66B]

I'm using latest pro version 0.35. Love the dark theme.
Theme switch doesn't work when pro App was called via xprivacylua. When I start pro App directly it works.
Doesn't work means I have dark theme even the switch is off. Do I enable switch it changes to white. Going back to xprivacylua and start pro App again (via xprivacylua) its dark and switch is off.

There is a note below the check box, does that help?

 

[Phoost]

There is a note below the check box, does that help?

I'm talking about the dark theme of Pro App.
Let's report it this way.
I'm on dark theme in lua and start to Pro.
Switch is off but Pro is dark.
Change switch, means enable it and Pro changes to white.
That's weird.
It's still reproducable. Switch doesn't reflect the status when Pro was called from lua.

 

[Pogo]

Would you consider to move "Dark Theme" checkbox from the top of the screen somewhere down or in the menu?
On my Nexus 5 with 5" LCD I need now to scroll down to get Log View button. IMHO, the Log View button is typically used way more more than Dark Theme button.

 

[M66B]

I'm talking about the dark theme of Pro App.
Let's report it this way.
I'm on dark theme in lua and start to Pro.
Switch is off but Pro is dark.
Change switch, means enable it and Pro changes to white.
That's weird.
It's still reproducable. Switch doesn't reflect the status when Pro was called from lua.

I will see if I can reproduce this.

 

[M66B]

Would you consider to move "Dark Theme" checkbox from the top of the screen somewhere down or in the menu?
On my Nexus 5 with 5" LCD I need now to scroll down to get Log View button. IMHO, the Log View button is typically used way more more than Dark Theme button.

Moving the switch to the menu a good idea.

Edit: this has been done in the just released version 0.36.

Changelog:

• Moved theme switch to menu
• Small improvements and minor bug fixes

 

[Phoost]

This version fixed my theme switch issue.

 

[badabing2003]

@M66B,

Thanks for the updates,

I updated both XPrivacyLua and the companion app to the latest, rebooted and checked Build.Fingerprint in the companion app, to my surprise it was still set enabled.

Also I was looking around the definitions and noticed ActivityManager.getRecentTasks and few others within the group was in gray, I wondered why, drilled to the details to see what it was about and they all showed enabled.

Are these some UI glitches or I'm misunderstanding the proper use?

Thanks
BB

 

[M66B]

@M66B,

Thanks for the updates,

I updated both XPrivacyLua and the companion app to the latest, rebooted and checked Build.Fingerprint in the companion app, to my surprise it was still set enabled.

Also I was looking around the definitions and noticed ActivityManager.getRecentTasks and few others within the group was in gray, I wondered why, drilled to the details to see what it was about and they all showed enabled.

Are these some UI glitches or I'm misunderstanding the proper use?

Thanks
BB

Only the Build.Fingerprint hook was disabled and nothing else was changed to the hooks:
https://github.com/M66B/XPrivacyLua/commit/b721af4742cc01dbd58ea7ba36a1f6c516b1f272

 

[badabing2003]

Only the Build.Fingerprint hook was disabled and nothing else was changed to the hooks:
https://github.com/M66B/XPrivacyLua/commit/b721af4742cc01dbd58ea7ba36a1f6c516b1f272

Thanks,

I understand that, my questions are:

1- why Build.Fingerprint was still enabled in the companion app after the update?

2- why some enabled hooks are showing up in gray in the companion app.

Thanks
BB

 

[M66B]

Thanks,

I understand that, my questions are:

1- why Build.Fingerprint was still enabled in the companion app after the update?

2- why some enabled hooks are showing up in gray in the companion app.

Thanks
BB

I don't know and I cannot reproduce it.

Did you update to the latest version of XPrivacyLua and did you hard reboot?

There is really no change that can explain this.

 

[badabing2003]

I don't know and I cannot reproduce it.

Did you update to the latest version of XPrivacyLua and did you hard reboot?

There is really no change that can explain this.

Yes to both.
Is it possible that because I had unchecked Build.Fingerprint for few apps like lastpass for granular control while keeping use tracking on this could have happened?

See attached for the gray issue.
Thanks
BB

 

[M66B]

Yes to both.
Is it possible that because I had unchecked Build.Fingerprint for few apps like lastpass for granular control while keeping use tracking on this could have happened?

See attached for the gray issue.
Thanks
BB
View attachment 4417688View attachment 4417689

Editing a hook will make a copy of the hook, so that is likely the cause of the Build.FINGERPRINT stuff.

getRunningServices is enabled for API levels up to 25 only (check the min/max SDK field), so I guess you are using a more recent Android version.

 

[badabing2003]

Editing a hook will make a copy of the hook, so that is likely the cause of the Build.FINGERPRINT stuff.

getRunningServices is enabled for API levels up to 25 only (check the min/max SDK field), so I guess you are using a more recent Android version.

Thanks, the gray mystery resolved, yes I'm running Oreo 8.1, I believe sdk 27

As for the Build.Fingerprint I didn't edit the hook, I just made lastpass not restrict it while keeping use.tracking checked.

Thanks
BB

 

[M66B]

@M66B,

Thanks for the updates,

I updated both XPrivacyLua and the companion app to the latest, rebooted and checked Build.Fingerprint in the companion app, to my surprise it was still set enabled.

Also I was looking around the definitions and noticed ActivityManager.getRecentTasks and few others within the group was in gray, I wondered why, drilled to the details to see what it was about and they all showed enabled.

Are these some UI glitches or I'm misunderstanding the proper use?

Thanks, the gray mystery resolved, yes I'm running Oreo 8.1, I believe sdk 27

As for the Build.Fingerprint I didn't edit the hook, I just made lastpass not restrict it while keeping use.tracking checked.

Isn't this contradicting: "it was still set enabled" and "not restrict it" ?

Anyway, I have tried multiple scenarios and I cannot find any problem. Since it will not happen often that an existing hook will be disabled and this therefore can be considered an edge situation, I am not going to put more time into this minor problem. Just disable/enable/delete it to set it as it should be set.

 

[badabing2003]

Isn't this contradicting: "it was still set enabled" and "not restrict it" ?

Anyway, I have tried multiple scenarios and I cannot find any problem. Since it will not happen often that an existing hook will be disabled and this therefore can be considered an edge situation, I am not going to put more time into this minor problem. Just disable/enable/delete it to set it as it should be set.

Yeah sure, not asking you to invest time on it, just reporting it.
You be the judge of the importance.

Just to be clear,
- I never edited the definition.
- It was enabled in the previous version, part of use.tracking
- I had use.tracking applied to most apps, including lastpass, which in effect had build.restriction applied.
- I then went into granular selection in the companion app (for lastpass) and unchecked Build.Fingerprint (restriction, not definition) while keeping all other use.tracking checked for lastpass.
- updated both apps, rebooted.
- definition was still enabled.
That's all

Not sure why that would be contradictory.

Of course I disabled it once I saw it was still enabled.


Thanks.
BB

 

[Phoost]

One issue I noticed today:
Open xprivacylua, start pro App for an App.
Pro App started with two tabs. "Global" and "App" .
Select manage hooks in App tab. Close manage hooks via "back" or the symbol in the left upper corner. Pro tab "App" disappeared. There is only "global" anymore.

One wish for manage hooks: possibility to sort by name and/or search field

 

[M66B]

One issue I noticed today:
Open xprivacylua, start pro App for an App.
Pro App started with two tabs. "Global" and "App" .
Select manage hooks in App tab. Close manage hooks via "back" or the symbol in the left upper corner. Pro tab "App" disappeared. There is only "global" anymore.

One wish for manage hooks: possibility to sort by name and/or search field

Actually, this only happens when you use the back symbol in the action bar.

 

[M66B]

@Phoost the just released version 0.37 fixes your problem

 

[Phoost]

@Phoost the just released version 0.37 fixes your problem

Happened with both wsys for me but doesn't matter. You fixed it:good:

 

[OSheden]

Sorry for having used the wrong thread.
So here is my question: Could you add a search box in the log of the pro companion to allow us to search all the resrictions for a specific app?