Hi, > > is there any solution being worked on? Anything I could test? Anything I > > could help with? > > > > I would very much like to see this fixed before it escapes into the wild > > > Not that I know of. Perhaps uploading a fix to AOSP or hitting one of the
Well, if I knew what kind of fix would be accepted? > android Google > groups would be better. Then perhaps you could get a Google Android > engineer involved. Any hints which groups? I had the impression that Nick was a "Google Android engineer"? > Also, as a possible work around, would soft links work for you? Nope. And apart from the fact that it wouldn't work for me, it seems mildly crazy to me to randomly disable well-established functionality "for security reasons" and to then expect people to work around the breakage ... after all, experience shows that code full of platform-specific workarounds tends to be so much more reliable and secure than a unified standard-conforming portable codebase! /s Regards, Florian _______________________________________________ Seandroid-list mailing list Seandroid-list@tycho.nsa.gov To unsubscribe, send email to seandroid-list-le...@tycho.nsa.gov. To get help, send an email containing "help" to seandroid-list-requ...@tycho.nsa.gov.
