-
Notifications
You must be signed in to change notification settings - Fork 527
Issue with random@boot #1164
Comments
I also tested this on https://play.google.com/store/apps/details?id=aws.apps.networkInfoIi to see which dataset it receives I have found that it can now read my real data. I don't know if this has something to do with changing the setting or if the issue was there prior to changing it |
Edit: after another reboot the app now receives app specific fake data, the check is set to random at boot, the db shows null=use global fake dataa |
This is a good find! |
@an0n981 can you please try if this version does fix the problem: http://d-h.st/rKf Thanks for all your bug reports! Is the issue with the database inconsistencies solved now? |
Now instead of resetting to random at boot, it resets to both random at boot and use global data unchecked. The db still shows random@boot as null. Apps that have random at boot set save the setting properly. I will do some extensive testing on the db tomorrow and report anything newsworthy |
Now unchecking 'use global data' does not stick |
There is one other thing to fix/improve: "saving an empty fake value will result in using the empty value, instead of the global value" |
@an0n981 could you please test this version: http://d-h.st/yMy NULL settings values are not stored into the database anymore and existing NULL values will be deleted from the database on reboot after installing this version. Empty application settings in the dialog are deleted from the database, so the global setting will be used (if any). |
Very nice. Everything working as promised |
Thanks for testing! This saves some data, which is good for performance. |
Setting random@boot to 'use global data' reverts to 'random at boot' after reboot. However running a select on the setting db shows the proper value null. I have tested this on uid 1000, google play store and afwall+ (user app)
The text was updated successfully, but these errors were encountered: