CyanogenDefy/android_device_motorola_jordan — comment on commit 386bc24c99bc01f19e798c47a1b7cb193b84e075
File:  line 0
By maniac103:

> cmparts use WRITE_SECURE_SETTINGS, it is to reduce the search when i will need them... also it is WRITE but also required for READ/WRITE

Yes, CMParts uses Secure, but it also needs it for writing e.g.
lockscreen settings or for enabling the permission management stuff. I
don't see DefyParts needing that, also not long-term.
I also fail to see why DefyParts should need to write to the SD card,
what do you have in mind there?

> my idea : fix easily some buggy settings on version "check", like the brightness toggle recently...

Do I get this correctly: You want to workaround framework bugs (a broken
update path is always a bug) by adding stuff in a Defy specific setup
utility? If yes, I ... don't think this is a good idea. We should aim at
fixing stuff at the source, not workaround it. If patch submission is
too slow, we rather should fork more repos than doing weird stuff just
because we are 'in control'.