squall wrote:Thanks for help testing MeoqZedong, glad it works again.
catmando, I just checked up on chromecast and it looks like the easiest way to add chromecast is to let android handle it, but it will have an action bar at the top of the screen. Would that be ok? The other way will be for me to handle everything myself, but will be a lot more work.
If anyone comes across instances where Hataroid doesn't quit properly, can you let me know what settings you were using and if you can reproduce it? Thanks.
Ah, cool, now I understand. My Galaxy S3 is still on Jelly Bean v4.3, not on KitKat v4.4 yetsquall wrote:Ok cool, I'll investigate chromecast further in a later version then (once the current problems with the sdk upgrade are sorted out).
Immersive mode only works only on kit kat and it allows the app to go full screen without any menu bars or anything else to get in the way (and you can bring them back with a swipe at the edge of the screen). Although I've never seen it in action myself
Jamesbeat wrote:I just want to say a huge thank you for this!
I've been struggling along with Stoid, but it's awful. No matter what I tried, I just couldn't get the keyboard to register numbers, so I was stuck on the menu on most disks.
I found Hataroid through this site via a Google search, not by searching in the Play store. I had to search by name to get it to show up, which obviously didn't work until I actually knew that there was an emulator called Hataroid!
Would it be possible to add support for moving the mouse using the D-pad (or analogue stick on the Shield) when in mouse mode for those of us with physical game controls?
Stoid has this feature, which is about the only good thing I have to say about it.
A backup of the apk should be fine. On the ouya, do you have the following option in your system menu:
- Developer options -> Don't keep activities?
Can you try making sure it is disabled (not ticked) and see if that fixes the issue?
Users browsing this forum: No registered users and 3 guests