Originally Posted by Luxferro
Explain how a sideloaded app taken from Google play shows on home page then? A version not available on amazon.
the plex thing, who knows. it's a paid app so that's one major difference with everything else we've been playing with.
it's not the classname - amazon is using the same exact namespace as google and anyone else.
because you don't go messing around with namespaces. no one does. for one thing, changing the classname is a licensing problem - quite likely breaking the law. and in practical terms, you could easily end up having 2 versions of the same app fighting over the same resource media/settings/etc. deadlock and threading issues, dirty reads abound.
if I sideload com.pandora.gtv taken from google, it stays in the kiddie menu.
if I sideload the pandora apk that I ganked from the amazon app store, it goes to the app menu.
but in both cases, running "adb shell pm list packages -f" reports that the firetv sees the app as: com.pandora.gtv
how does the firetv decide what happens when you sideload an app? I don't know. I have a moderately good guess.
- some extra indicator/tag files
- different RSA signatures/certs (check out META-INF)
- possibly non-trivial differences in the manifest xml
below is some info about some indicator files that are in the amazon apks. but not in non-amazon apks.
you can see that 2 of the files are identical between the 2 apks, but still generically saying hey this is some amazon apk not a regular one.
and then there is 1 file that is different. some sort of specific signature or hash.
(each com.amazon.content.id.$FOO file simply contains "$FOO" - it's some sort of unique generated string but no idea what it relates to)
between this stuff and the RSA certs, that's probably how the firetv is set up to decide how to sort out where to put things.
I imagine similar with OUYA or any platform where this kind of split-userspace thing is going on...