-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: After applying Standard selection Phone Link is broken #350
Comments
Hi @sla-te, if I understand this correctly, you already reverted whole Standard selection but it still fails? You can try reverting "Disable app access to Bluetooth devices". |
@undergroundwires Thank you for hinting on this one and I tried but it didn't fix it. Yes, correct I tried reverting the whole Standard selection and additionally I also tried reverting the "All" selection, despite I never actually applied it, hoping it would fix it :). |
As you already reverted "Standard", this should have been caused by privacy.sexy but another software/configuration/hardware issue. Irreversible scripts are just cleanup scripts that would have no impact on what you're experiencing. You need to restart after reverting "Standard" as you already did it. Reverting "All" should be safe. It can restore other settings set by other apps. If you find out the reason (if there was a bug with reversion process), please inform back so we can fix it. |
Well, I wouldn't have opened the ticket without having tried everything I could think of. I can though confirm that it did work before running privacy.sexy (and I encourage you to reproduce it on by using my reproduction steps, I am certain, that it will work). Would appreciate if you could provide me suggestions on how I could find out what is causing it. Also from what I can tell there are quite some selections, where you cannot select "revert" for. |
It's hard to reproduce for me but someone else in the community can help. I do not have physical access to a Windows machine with Bluetooth access. You're right, these scripts should all have revert codes as they're pretty straightforward to restore. I have some work on local branches that I haven't pushed yet, so my last comment is incorrect for the latest released version. If you're confident that this is caused by privacy.sexy, the best troubleshooting way, going through all I think deleting If we figure out this script, I'll document it remove it from Standard right away. |
Alright, was hoping there might be an easier way, ill do my best to go through all of them then hehe |
@undergroundwires I found it x)
|
Thank you @sla-te for the information. I'll document all of the "Disable app access" scripts. Document that this script breaks Phone Link in the title and move it to Strict pool. Hopefully all Standard scripts will be documented, reversible and non-breaking meanwhile still being as aggressive as possible regarding protecting privacy. |
This commit adjusts the recommendation level for scripts that disable UWP app access to accommodate user issues #121, #339, #350. It also extends their documentation to reflect the new changes and with cautions. Changes: - Add caution text for all scripts about potential impacts. - Move disabling app access to notifications from 'Standard' to 'Strict'. This addresses #121 and #339, where users report lack of notification as unintended side-effects. - Move disabling app access to phone calls from 'Standard' to 'Strict'. This addresses #350 where its effect on the Phone Link app was reported as an unintended side-effect.
0.13.4 is just released 🎉. It improves app disabling to resolve this issue, some of the improvements include:
Please create new issues for further ideas/problems. |
Description
After applying Standard selection Phone Link is broken (and even reverting "All"), does not fix it back.
I can confirm it did work before. Specifically what does not work is the feature, that you can accept and make
calls via Phone Link on Windows (Messages and Apps still work).
OS
Windows 11 Version 22H2 (OS Build 22621.3447)
Reproduction steps
Screenshots
Additional information
Worth to mention, that I first had problems getting it to work, having applied the standard settings of ShutUp10. After applying the "Undo all changes" action and a reboot, it worked perfectly (I also already tried running that again hoping it would revert the changes made by privacy.sexy but it didn't help). So my guess is that anything privacy.sexy does is somewhat not revertible and causes the breakage. Any hints regarding how to provide detailed error information when running Phone Link to pinpoint the root cause is highly appreciated because I kind of enjoyed using this feature.
I also already tried running the script provided by #315 (comment) but it also didn't fix it.
The text was updated successfully, but these errors were encountered: