Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
I recently bought a cardboard. But cant taste many apps because my Android smartphone doesn't have a Gyroscope sensor. So i searched for an app that can mimic the gyroscope functionality by pressing keys or something.
I got these...
1. https://github.com/memsindustrygroup/Open-Source-Sensor-Fusion/wiki/Virtual Gyro
2. http://www.mcubemems.com/products/igyro/
These aren't any app, but proof that Virtual Gyroscope exists. Some lenoveo phones(Like K3 note) use them. So plz let me know, is there any app that can do the same effect in any android device with Accelerometer & Compass sensor. Or, any app that can mimic the effect pressing volume/headphone key.
only look left/right action is required , Accelerometer does look up/down.
Yes by this i wont get a head tracking experience, but at least I can look around and select files to watch videos. Developers can make app(if doesn't exist already) following this idea. I think, it will help many.
Thanks in advance
Hi, I'm also looking for some app that fakes gyro sensor as I have the same problem. In theory a dev could interpret those algorithms from that Github repo and make an emulator, unfortunately this is out of my knowledge.
So I hope someone could help us poor ungyroscoped people.
Yeah, it's big problem with most phones to use VR apps/games that require gyroscope. I have the same problem.
Google should think about gyro pseudo emulation with accelerometers in their Cardboard API or at least implement there something like this lib: https://code.google.com/p/openintents/wiki/SensorSimulator
so anyone could use different phone (with gyro) as remote gyro for phone in cardboard glasses or write gyro emulators much more easily (as this lib can open TCP port for remote sensors data).
Technically, yes, it should be possible, using Xposed.
I am working on a module that eliminate the jitter in unreliable phone's gyroscopes. It does so by hooking to the function that distpaches the various sensors' data to every apps that require them, and it fakes the values before these data get sent.
Since you can easily access any sensor's data, you can do any sensor fusion you want by using the accelerometer and magnetometer, or even just the touch screen, and then fake the gyroscope's values.
If you are interested, here is the Xposed module I'm working on, which shows how to hook to the gyroscope and fake the values:
On github: lrq3000/JitteryGyroFixForCardboard
And to implement sensor fusion, you can either use the new virtual sensors of Android 4, or code it yourself, there's a very good open source app that shows it all here:
On github: KEOpenSource/GyroscopeExplorer
Hey thank you for that info! I'll be taking a look at that as soon as I can, although I'm not an avid dev I hope we can get something for our phones.
shafiaszad said:
I recently bought a cardboard. But cant taste many apps because my Android smartphone doesn't have a Gyroscope sensor. So i searched for an app that can mimic the gyroscope functionality by pressing keys or something.
I got these...
1. https://github.com/memsindustrygroup/Open-Source-Sensor-Fusion/wiki/Virtual Gyro
2. http://www.mcubemems.com/products/igyro/
These aren't any app, but proof that Virtual Gyroscope exists. Some lenoveo phones(Like K3 note) use them. So plz let me know, is there any app that can do the same effect in any android device with Accelerometer & Compass sensor. Or, any app that can mimic the effect pressing volume/headphone key.
only look left/right action is required , Accelerometer does look up/down.
Yes by this i wont get a head tracking experience, but at least I can look around and select files to watch videos. Developers can make app(if doesn't exist already) following this idea. I think, it will help many.
Thanks in advance
Click to expand...
Click to collapse
Yes, same problem here. The facts, med-low or med or med-high device not attached by gyro, except xiaomi. Some people on quorra debated, they have idea to make an app which can do headtracking with camera by detecting pixel shift. Yes i like that idea and the idea sounds possible, but it out of my knowledge. Can anyone make app like that? Or maybe we can ask google to make the app?
Thanks
What about emulating gyro using accelerometer and compass? In the Google Play is app for phones without gyroscope, (we are in space: LINK) so it is possible
I would love to see something like this too. This dev has several VR apps and the head tracking all works perfectly on my Moto G 3rd gen which has no Gyro, so I know it is possible. I've played House of Terror and the head tracking works extremely well and pretty smooth too, I wonder what their method is, I assume compass + accelerometer. https://play.google.com/store/apps/developer?id=Lakento
shafiaszad said:
I recently bought a cardboard. But cant taste many apps because my Android smartphone doesn't have a Gyroscope sensor. So i searched for an app that can mimic the gyroscope functionality by pressing keys or something.
I got these...
1. https://github.com/memsindustrygroup/Open-Source-Sensor-Fusion/wiki/Virtual Gyro
2. http://www.mcubemems.com/products/igyro/
These aren't any app, but proof that Virtual Gyroscope exists. Some lenoveo phones(Like K3 note) use them. So plz let me know, is there any app that can do the same effect in any android device with Accelerometer & Compass sensor. Or, any app that can mimic the effect pressing volume/headphone key.
only look left/right action is required , Accelerometer does look up/down.
Yes by this i wont get a head tracking experience, but at least I can look around and select files to watch videos. Developers can make app(if doesn't exist already) following this idea. I think, it will help many.
Thanks in advance
Click to expand...
Click to collapse
Same problem. I also have a k3 note and it has a virtual gyro. i think there must be something that uses accelateometer and magnetometer to detect direction and angle.(and i think this is possible)
Guys try vr player from play store then goto settings and there would be orientation detector set it to accelerometer +compass and you are donw
Same Problem
lrq3000 said:
Technically, yes, it should be possible, using Xposed.
I am working on a module that eliminate the jitter in unreliable phone's gyroscopes. It does so by hooking to the function that distpaches the various sensors' data to every apps that require them, and it fakes the values before these data get sent.
Since you can easily access any sensor's data, you can do any sensor fusion you want by using the accelerometer and magnetometer, or even just the touch screen, and then fake the gyroscope's values.
If you are interested, here is the Xposed module I'm working on, which shows how to hook to the gyroscope and fake the values:
On github: lrq3000/JitteryGyroFixForCardboard
And to implement sensor fusion, you can either use the new virtual sensors of Android 4, or code it yourself, there's a very good open source app that shows it all here:
On github: KEOpenSource/GyroscopeExplorer
Click to expand...
Click to collapse
I bought a vr case and have the same problem my galaxy sm a510m (A5 2016) doesnt have gyro! When i saw that i couldnt believe it.... it opens with my fingerprint for the love of crist!!! :crying:
Any solutions?
I have a moto g 3 and can't experience Pokemon go neither vr visor from one plus
Sent from my MotoG3 using XDA-Developers mobile app
Is there still hope?
If there is no way (for whatever reason) to emulate a gyro...is there a method to add a gyroscope sensor to an android?
Sent from a Samsung Galaxy J7 user
Same here, i too need an APP that simulate the gyro functions.
Hope that someone could implement that using compass and accelerometer!
Thanks
Some app like this would be so cool...
I was a bit dissapointed after buying the Moto X Play and noticing it doesn't have gyroscope so no Augmented Reality on Pokemon GO.
Im so sad, i had a moto g2 and bought motog3 1 month ago, this thing doesnt have a gyroscope while motog2 had one. Is there no solution for this? I mean, with something like a virtual gyroscope
pokulan said:
What about emulating gyro using accelerometer and compass? In the Google Play is app for phones without gyroscope, (we are in space: LINK) so it is possible
Click to expand...
Click to collapse
I've tested with my Moto G 3rd and works well. I hope somebody develop some hook in Xposed to work with accelerometer and compass...
or lests just hope the pokemon go app support accelerometer + compass it in the future.
I feel where you all are coming from. I agree there needs to be an app, an xposed module, or something to get this functionality. I'm gonna try and figure this out, there's a post on stackoverflow about this. A guy was talking about how in order to do it you'd need to recreate files similar to the ones that poll the actual hardware. He's basically saying you need to create some sort of mock gyroscope polling code right above the hardware level. I don't think that's the best approach, we gotta go top down not bottom up on this. I don't know much about the inner workings of android but I know this, looking at how to grab sensor data just using a plain app uses the classes sensor and sensor manager. As far as i can tell these are fed with information by the sensor event listener. That is fed by the object sensor event. It states right on the documentation "This class represents a Sensor event and holds information such as the sensor's type, the time-stamp, accuracy and of course the sensor's data." Its a generic sensor class which means we could possibly give it a fake gyroscope right?
Now, back to the sensor event listener, on the documentation it says "The application doesn't own the event object passed as a parameter and therefore cannot hold on to it. The object may be part of an internal pool and may be reused by the framework.". That means sensor event listener is literally just the messenger and should take whatever it finds as long as its valid. It seems like it will take whatever is passed to it correctly if we can make an event that it hears.
Now, amazingly on the sensor event page shows some fantastic stuff. Sensor event class is literally a 4 field class and I believe gets its values from that "hardware polling code" that sits above the hardware level. (the code that other guy was talking about.). If we can just make up some sensor events that mimic a gyroscope using accelerometer + compass and hope that the sensor event listener is configured to pick it up (I don't see why not) then I think this could be a possible solution. With all that being said, I'm just a beginner when it comes to android. I'm a college kid with a background in c and java just trying to piece the puzzle pieces together and play some pokemon lol.
Edit: So I may have been way off the mark, I'm not sure anymore. I found this though, a way to use actual custom sensors with android http : // riansanderson.blogspot . com/2012/03/integrating-sensors-into-android . html . Sorry for the spaces, I can't post links. After more java delving it seems it is not possible to create your own spoofed sensor or sensor event if your code is not in the same package as android.hardware.Sensor or SensorEvent
Edit2: So I guess unless you can get code to run in that android.hardware package, you'd have to do something like that link above and make like a fake driver for fake hardware.. I suppose if you could modify android.hardware.sensor to just make a gyroscope sensor and take the values from the accelerometer and modify those on the fly.
Try this solution
hello all from Egypt
this tutorial isn't mine or my invention you can say it's information sharing
I am Waleed and i have Huawei honor 4x which has no gyroscope at all, but i found some solution to this problem which is:
1- you must have ROOT (without root you can't do anything at all)
2- install root explorer if it isn't installed in your mobile and be sure to allow root permission to it
3- download the attached xml file which activate soft gyroscope in your mobile and place this file in your SD card
4- open root explorer and copy the xml file you downloaded and go to this path "/system/etc/permissions" and paste the file there and be sure the file exists in this place
5- reboot the phone then install any app from Google play to check the gyroscope i suggest sensor box
6- I hope this information is valuable and useful for you
thanks
xposed module to modify user apps for leanback support such as emulators or sideloaded **free** games that never show up on Android TV such as NSTV.
The idea behind this to make it work is really simple....somehow the module will:
1. Load ALL user apps that don't have leanback support
2. Modify either permanently/load the app's manifest to add leanback LAUNCHER & other lines to it.
3. On restart Theoretically it should work with almost all apps being modified for Android TV.
Side note:
Any app/game that only has touch support will NOT work at all since those apps probably don't have either controller, keyboard, & mouse support at all and it will be just redundant to mod them...
(Tried playing cod zombies on NSTV...I tried all key mapping apps and nothing worked.)
THIS MODULE WILL PROBABLY REPLACE THAT **SIDELOAD LAUNCHER**
From the way I wrote this you should have already guessed that the module has NOT been made yet, since more research is needed to be done in order to progress any further than an idea, but I'm posting it now for anyone that's wants to tackle this project or help me make it(new to xposed module developing.)
Xstar410 said:
xposed module to modify user apps for leanback support such as emulators or sideloaded **free** games that never show up on Android TV such as NSTV.
The idea behind this to make it work is really simple....somehow the module will:
1. Load ALL user apps that don't have leanback support
2. Modify either permanently/load the app's manifest to add leanback LAUNCHER & other lines to it.
3. On restart Theoretically it should work with almost all apps being modified for Android TV.
Side note:
Any app/game that only has touch support will NOT work at all since those apps probably don't have either controller, keyboard, & mouse support at all and it will be just redundant to mod them...
(Tried playing cod zombies on NSTV...I tried all key mapping apps and nothing worked.)
THIS MODULE WILL PROBABLY REPLACE THAT **SIDELOAD LAUNCHER**
From the way I wrote this you should have already guessed that the module has NOT been made yet, since more research is needed to be done in order to progress any further than an idea, but I'm posting it now for anyone that's wants to tackle this project or help me make it(new to xposed module developing.)
Click to expand...
Click to collapse
No need for an xposed module. just a new launcher, there's a few out already, not great though
for the mapping, I don't think it's possible to do that, xposed or not due to different mappings per game, the shield TV community is tiny, without many developers onboard.. will be a tough to get anyone with knowledge to write anything at this stage.
xd4d3v said:
No need for an xposed module. just a new launcher, there's a few out already, not great though
for the mapping, I don't think it's possible to do that, xposed or not due to different mappings per game, the shield TV community is tiny, without many developers onboard.. will be a tough to get anyone with knowledge to write anything at this stage.
Click to expand...
Click to collapse
I been using es file explorer, but I want native support though for my games/emulators
Xstar410 said:
I been using es file explorer, but I want native support though for my games/emulators
Click to expand...
Click to collapse
ES file explorer to start sideloaded apps?
try sideload launcher, or HAL launcher for a full launcher replacement.
xd4d3v said:
ES file explorer to start sideloaded apps?
try sideload launcher, or HAL launcher for a full launcher replacement.
Click to expand...
Click to collapse
nah, Im saying I been using it for everything & its great, but I would like to see my non-native tv apps on the leanback lists for games...I hate to modify them manually since it is a bit annoying
Why don't you guys just use Kodi as your launcher?
I've looked into the same issue, mainly because of the norwegian TV app GetTV that is ment for customers to watch TV on any device in and out of the house and with NSTV i would have 1080p native from the IPstream instead of the 1080i the cableboxes they deliver can handle.
To make apps work that way, they need a layout compateble with DPad navigation, so changing the manifest wouldn't help much i think, and if you create an app to launch with an overlay for the app you would need to run an emulated new version of android and in that instance launch the app and have cursor/leanback support for non-native apps, that would drain the power and create even more issues, best way to do this would be for Nvidia to add a cursor mapping profile for the gamepad controller og tv remote (ex. "trippleclick search to start 'mousemode'." and then use the directional keys to move the cursor around)
Zacharybinx34 said:
Why don't you guys just use Kodi as your launcher?
Click to expand...
Click to collapse
Speaking personally, because that would make this flagship device very limited in terms of what you can do outside of Kodi. Who would buy a device as powerful as the Shield TV then use it simply for watching video in Kodi?
Leanback is terrible. I use Smart Launcher Pro myself, lots of options, support for remotes and automatic categorisation of applications and games.
Beefheart said:
Speaking personally, because that would make this flagship device very limited in terms of what you can do outside of Kodi. Who would buy a device as powerful as the Shield TV then use it simply for watching video in Kodi?
Leanback is terrible. I use Smart Launcher Pro myself, lots of options, support for remotes and automatic categorisation of applications and games.
Click to expand...
Click to collapse
You can create links to android apps within Kodi.
Zacharybinx34 said:
You can create links to android apps within Kodi.
Click to expand...
Click to collapse
Yes, I'm aware of that. But the whole process is limited and the interface less than ideal for a device of this type, or at least if used to its potential. If we were talking about a system of limited specification that was used for little else other than video playback and a few additional apps (for example, an Amazon Fire Stick) then it would perhaps make sense. But I have 60+ applications and games installed on my Shield TV. And the idea of having to access them from within Kodi, an application which was not designed with this in mind, is unappealing to say the least.
This is funny. I enjoy how the discussion is on modifying Leanback Launcher, but all the suggestions are "Don't use Leanback Launcher".
I for one actually like Leanback and the way it works on my TV with a remote. Like it was designed for it.
In terms of the discussion at hand - this isn't that hard to implement. You don't have to hook *every* package - you just need to hook the bit of Leanback Launcher that enumerates the packages and then modify that code to always return "yes" when asking if it has the Manifest permissions for Leanback.
As I find this quite intriguing and know a bit about Xposed - I think I'll take a look at this today if time allows. I happen to have both the nexus player and shield TV system images lying around (access to both versions of Leanback), so I may just be making this.
I'll post back here if anything comes of it.
Also, I wonder if I can force the "Live Channels" app to display at the top of Leanback's home interface, like it does on my parents' Samsung w. Android TV.
While we're modifying leanback...Should we put the "non-leanback" apps in their own row, or in the same row as all the other apps?
digitalhigh said:
This is funny. I enjoy how the discussion is on modifying Leanback Launcher, but all the suggestions are "Don't use Leanback Launcher".
I for one actually like Leanback and the way it works on my TV with a remote. Like it was designed for it.
In terms of the discussion at hand - this isn't that hard to implement. You don't have to hook *every* package - you just need to hook the bit of Leanback Launcher that enumerates the packages and then modify that code to always return "yes" when asking if it has the Manifest permissions for Leanback.
As I find this quite intriguing and know a bit about Xposed - I think I'll take a look at this today if time allows. I happen to have both the nexus player and shield TV system images lying around (access to both versions of Leanback), so I may just be making this.
I'll post back here if anything comes of it.
Also, I wonder if I can force the "Live Channels" app to display at the top of Leanback's home interface, like it does on my parents' Samsung w. Android TV.
While we're modifying leanback...Should we put the "non-leanback" apps in their own row, or in the same row as all the other apps?
Click to expand...
Click to collapse
Its own row would be great actually.. Otherwise I feel that things could become a little bit too messy. Or you could simply let the user select that via the module's option[emoji14]
Xstar410 said:
xposed module to modify user apps for leanback support such as emulators or sideloaded **free** games that never show up on Android TV such as NSTV.
The idea behind this to make it work is really simple....somehow the module will:
1. Load ALL user apps that don't have leanback support
2. Modify either permanently/load the app's manifest to add leanback LAUNCHER & other lines to it.
3. On restart Theoretically it should work with almost all apps being modified for Android TV.
Side note:
Any app/game that only has touch support will NOT work at all since those apps probably don't have either controller, keyboard, & mouse support at all and it will be just redundant to mod them...
(Tried playing cod zombies on NSTV...I tried all key mapping apps and nothing worked.)
THIS MODULE WILL PROBABLY REPLACE THAT **SIDELOAD LAUNCHER**
From the way I wrote this you should have already guessed that the module has NOT been made yet, since more research is needed to be done in order to progress any further than an idea, but I'm posting it now for anyone that's wants to tackle this project or help me make it(new to xposed module developing.)
Click to expand...
Click to collapse
can't wait for this I hate HAL, costomizing the stock launcher is the way, best of both worlds: original features AND customizations:good:
A little update:
I did some initial research into this, and found the method we need to hook in order to make this happen.
http://forum.xda-developers.com/xposed/development/hooking-protected-list-inner-class-odd-t3306186
I haven't had more time to dive into this further, but I do have the initial framework started for a module. No idea when I will be able to tackle it more, but at least we have an idea of what needs to be done for anybody else who may be interested in this and know Xposed.
i do like the stock launcher,but needs more cosmetic,but i did found that the apk call OmniSwicth is wonderfull,the only thing is not fully working if somebody make work that would be remarkable,i do like the interface and using my fire tablet 7 inches with a combination the droidmote apk is the best so far for my shield tv if someone try this would know what i am talking, i am not a developer but i will be happy is somebody from XDA make this app OmniSwicth works
Anyone remember GEL Xposed before it became GNL? Thats what we need for this. I actually like the way leanback works, I just want it to load all of my apps.
Yea that's the thing that kills me about AndroidTV, its so crippled in terms of apps. I love the interface but the lack of apps sucks, it would be amazing if someone could figure out a hack that would allow the play store to show all apps.
Sent from my Pixel C using Tapatalk
digitalhigh said:
This is funny. I enjoy how the discussion is on modifying Leanback Launcher, but all the suggestions are "Don't use Leanback Launcher".
I for one actually like Leanback and the way it works on my TV with a remote. Like it was designed for it.
Click to expand...
Click to collapse
ME TO, if it weren't for the crap play store and the lacking all the installed apps.
I installed this ROM http://forum.xda-developers.com/shield-tv/development/rom-t3321787 last night and I already miss the Leanback Launcher and how it "just worked" with the remote, the stock interface (and Nova for that matter) just don't navigate well with the remote.
honestly my dream setup would be the factory OS with the Leanback Launcher, but rooted with the FULL play Store and all the installed apps shown in the Launcher.
daniel644 said:
ME TO, if it weren't for the crap play store and the lacking all the installed apps.
I installed this ROM http://forum.xda-developers.com/shield-tv/development/rom-t3321787 last night and I already miss the Leanback Launcher and how it "just worked" with the remote, the stock interface (and Nova for that matter) just don't navigate well with the remote.
honestly my dream setup would be the factory OS with the Leanback Launcher, but rooted with the FULL play Store and all the installed apps shown in the Launcher.
Click to expand...
Click to collapse
I installed the leanback launcher and it works well on restyle
pspbyer said:
I installed the leanback launcher and it works well on restyle
Click to expand...
Click to collapse
How did you manage this. I tried and it would not let me install leanback launcher
Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Sheikboy said:
Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Click to expand...
Click to collapse
Good idea! I don't use my TouchPad very much anymore away from it being my alarm clock on the Touchstone dock.
I'd definitely try to upgrade it to an Alexa enable tablet if possible.
Will follow this thread with interest!
Sent from my Nexus 5 using Tapatalk
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Sheikboy said:
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Click to expand...
Click to collapse
Use the Evervolv ROM.
shumash said:
Use the Evervolv ROM.
Click to expand...
Click to collapse
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Sheikboy said:
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Click to expand...
Click to collapse
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
shumash said:
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
Click to expand...
Click to collapse
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
thedeathspirit said:
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
Click to expand...
Click to collapse
Get Assistant - Root works
I still haven't been able to fix the WiFi on my Touchpad. It works perfectly in webOS, but it just remains stuck on "Turning WiFi On" on every single Android ROM iIve tried. I'm not quite sure what to do at this point
shumash said:
Get Assistant - Root works
Click to expand...
Click to collapse
Thank you, I'll try.
I have one specific app that I'd like to keep but it won't auto-rotate like all the other apps and insists on being "upside down" with no in-app way to change it. All my other apps have no issue following the system auto-rotate. I have done a cursory net search and found a handful of "rotation managers" that claim to do this. I'd prefer an ADB solution but if a rotation manager is the only way to fix this can anyone recommend something for me?
Note that I will not install any app on my device that requires google play store or google play services to operate which does limit my options somewhat.
BTW thanks for all the help so far and into the future.
Try rotation control, works pretty well for me
This is easy find with Google.. you probably can rotate it upside down i.e. 180° like this using adb..
Changing Android Device orientation with ADB
I'm using Android 4.4 on a real device and I want to set the device orientation via adb. I don't want it done with uiautomator since it won't last after the termination of the uiautomator code. H...
stackoverflow.com
if not working you probably have to edit the manifest..
AmmarHaseeb said:
Try rotation control, works pretty well for me
Click to expand...
Click to collapse
Rotation control is the one I found as well. Good to see a 7 year old app that still performs its function cleanly and reliably. Also good to see my somewhat random choice validated.
Thanks
CXZa said:
This is easy find with Google.. you probably can rotate it upside down i.e. 180° like this using adb..
if not working you probably have to edit the manifest..
Click to expand...
Click to collapse
Thanks. I did stumble across this but it's way beyond my understanding.
Pretty much everything on this site is beyond my understanding but I'm very grateful to have found a site of knowledgeable folks willing to help a tyro out.
Thanks again.