I understand that userland apps on android cannot set the system clock. Wanting to know more about how the security mechanism is set up for the system I did some digging around in the source code.
/dev/alarm is opened R/W to set the system clock using SystemClock.setCurrentTimeMillis. Can someone explain how the permissions work to determine whether or not an application has permission to set the clock. I assume it's just a user level permission, and the write bit for /dev/ alarm is only enabled for the "system user" and not the "userland user" applications run under. But, if someone can set me straight or confirm that what I'm thinking is true that would be great. Thanks. Cheers, Richard Schilling --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
