As the Android design guide itself states, "deviate with purpose." Everyone so far in the comment thread is on the right track.
There's not usually a good reason to come up with something custom to accomplish something that already has an established idiom
on any platform you're targeting, Android or otherwise. Don't migrate system interaction patterns from elsewhere just to have some misguided form of consistency between ports of your app that you publish on different platforms. That serves to confuse and alienate your users. A feeling of "intuitiveness" comes from leveraging what your users already know, and when you contribute to a cohesive feel on a platform it helps reinforce that for every other app as well.
But at the same time, there's also no reason why your app's star functionality shouldn't be your own. Have hero moments. If we tried to bake that into the UI toolkit itself or into Holo it wouldn't be special when you need it to be.
Most importantly, the design guide should be seen as a catalog of solved problems, of UX wheels you don't need to reinvent. If you have unique functionality that you want to expose, don't just squint at the design guide until one of the patterns there looks appropriate. Make sure it's familiar enough that users can figure it out, but don't be afraid to make different things be different.
Your app's UI is its identity. It should be recognizable at a glance over someone else's shoulder as both uniquely yours and
a great fit for the platform it's running on.+Juhani Lehtimäki
We have a few sessions at Google I/O this year you might be interested in, and as usual they'll be on YouTube later.