All of the Android devices that I've played with will have applications running as root (and therefore, if the underlying FS supports it, the files are owned by root as well). POSIX systems will honor user designations from other remote systems (in this case, the phone's designations from Android itself). All POSIX systems that have the idea of a "root" user designate the UID 0 to root, hence there is some level of security that travels with the file no matter where it goes.
I have a feeling, however, that is a fun aside from the issue you're seeing (since these devices are meant to plug into any machine and be accessible, methinks what's being mounted is FAT32), in which case it's some issue with the automounting support that's built into the version of Fedora you're using. I'd start by barking up that tree and see if someone else has run into a similar problem (FAT32 partition of an Android auto-mounted by Fedora in a way that's preventing access by Joe Linuxuser) and, more importantly, what solution they've come across. I mean I could offer a solution that'll work on any Linux out there, but it's neither pretty nor permanent.