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
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
Am I missing something here? App is not compatible with some of your devices.
Htc Evo- check
Transformer Tablet- no check
I need to understand the developer side of this coin. I have been trying to persuade Jawbone to update their android app "Jawbone Companion" to support my tablet. I don't know, but I assume their would be a publisher option in Google Play to add or delete supported devices so that they cannot be installed on those from the Play store. For example, I had to go to the website to find the app because search shows no results on the tablet.
It's a bluetooth headset. It supports 2.1+edr. App supported on Android OS 4.0, OS 2.3 and select OS 2.2 phones. Transformer tf300 has bluetooth. It supports 3.0+edr. It has ICS and is certainly more capable than a 2.2 phone.
Sooo the only difference I see from this side is a bigger screen. I have emailed at least 3 app makers that I use frequently and they just keep saying it's not tablet supported. So do they just have to add devices to some file that cross checks with Google Play or is the code for my tablet so drastically different that they would have to write a whole new app for tablets?
A technical explanation link of the whole developer process regarding this would be nice.
Update to OP
I have found a method of downloading apk files in the Chrome browser with the APK Downloader extension. It only works with Chrome and I logged into my wife's account, did a quick search for my apps in question, then proceeded to download them to pc by making play think it was sending the apk to my wife's "supported" phone. Then I manually transferred the apks to my "unsupported" tablet where they are now running fine, no errors and no resolution problems.
I have emailed the developers of these apps and they have blown me off by saying that tablets in general are not supported, I emailed them all back telling them their apps were working fine and I didn't understand why they couldn't have allowed me to just download it the easy way.
So are they just being lazy? This just reinforces my reasoning that the phone and tablet are about the same and don't require any more coding than any other app that has problems on certain phones. Seems to me as long as the resolution is high enough and it allows auto rotation that any phone app should run on a tablet, and I don't see why they all keep telling me apps are not supported.
Until then I guess I'll just get my apps the way I described.
yap the apkdownloader would be the way i recomended to you =)
dunno why they dont support tablets
in some cases u dont have to understand them
feel lucky u find a way to make it work
Sorry Guys,
As there doesn't seem to be a whole lot of interest in this project and as no one stepped forward to assist, I'm afraid I'm going to have to abandon this project.
Thanks for following.
___________________________________
OK Guys,
I've run into a bit of a brick wall and need some input from other developers. One of the required APKs from the Q needs a class not included along with my CM9 or Samsung stock roms. The class appears to be called "android.os.UpdateLock". So how do I go about ripping the class out of the Nexus Q rom and injecting it into CM9? Any help would be very appreciated!$!
--------------------------------------------------------------------
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
You can already do that on most android devices. The Q just takes it to the big screen conveniently.
The function of being able to control the Google queue of device A from device B, C, D etc does not exist. Or at least I'm not aware of an app that does that.
I believe that I've tracked down the apk that does it on the nexus but I need to deodex the apps and can't seem to find a tool that works. Anyone out there deodex this rom yet?
JoeJonnyBoy75 said:
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
Click to expand...
Click to collapse
This is a pretty nice project and there is nothing like this happening in Android now, besides the nexus Q. I'd like to see a future port of it to Google TV devices
auad said:
I'd like to see a future port of it to Google TV devices
Click to expand...
Click to collapse
Would love to have this functionality in an APK for me Google TV. Don't see why it wouldn't work, well other then no bluetooth on the Revue....
Still very interested in this thread regardless of GTV. I will be following your progress. Thanks!
.
I'm looking for this as well.
I have 3 spare HTC EVO's, and they all have HDMI out. I would like to be able to just plug them into the TV and use my other phones to control them / play music / etc. Maybe even throw XBMC on them with the ability to control from another phone..
They're slower, and less memory..but it may be doable.
Did anyone dig into this? I'd like this for the latest port of Android for a Raspberry Pi and willing to do some of the (noob)stuff myself.
That would be awesome to use any HDMI equipped phone along with the Nexus Q functionalities. I'm really interested.
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Vettekult said:
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Click to expand...
Click to collapse
Not true, Q runs ICS...
Let me know...
what I can do to help. If you give me a run down on what you would like me to try as far as pulling files from the q or my connected devices just shoot me a PM and i'll give it a shot. I too would love to add this functionality to my spare devices laying around.
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
joeavery2 said:
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
Click to expand...
Click to collapse
Ok so here is some more detailed info for those of you still following the project.
HubBroker.apk is the app that is for all intents and purposes the "launcher" for the nexus Q. It will install on the Galaxy Tab and Nexus 7. It takes over your "home" and replaces it with a picture of the Nexus Q and a welcome sign. This app looks to be only the launcher as it doesn't do anything if you tap on it. Also having the app running doesn't allow the Nexus Q app (from your phone) to find the device.
So I assume that that the Q is controlled via bluetooth to get it setup and running. Including configuring the Wifi, network settings, etc. Oddly enough the app does send a request to android system to turn on the bluetooth and changes the bluetooth device name to Nexus Q.... The ... part is a odd string of characters that I assume is used in case you happen to have multiple Nexus Q's.
Now as just having the app doesn't seem to work (Phone finding the Q). I've replaced all the bluetooth libs with the ones from the Q. Still nothing. I've migrated all the other APK files and then I get FCs all over, and still no connection. I haven't tried replacing the whole system yet, but I assume the hardware differences would be to great. The only other piece of the puzzle I have yet to attempt it merging the kernels or at least the init parts of the kernel relating to bluetooth.
If you have any questions though let me know. I've been up and down this thing.
Why don't we just flash the img on an old phone and see if that works?
zAo_ said:
Why don't we just flash the img on an old phone and see if that works?
Click to expand...
Click to collapse
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Cool, Thanks.
Sent from my Galaxy Nexus using xda premium
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Galaxy nexus has very similar hardware. Someone should try porting it.
Sent from my Nexus 7 using xda premium
If someone still interested in the project, i'm very interested in it, i have a galaxy nexus (almost same hardware) so we can give it a try, im also a android developer, so if it need to build some apk for it to work, i could give a shot.
Anyway, if there is someone interested just post here and we do all we can to make that work.
edit: Only one problem, as I'm out of USA, i need the q apk to test if it will connect or not. I cant download from play store.
I'm sure there will be so many people interested in it. I just think that not to many of them enter this category on forum
I also need the nexus q image so I can flash it. I tried searching it but didnt find
So the goal here is to have a tablet in our home gym that I can cast music to a nearby receiver and to have a timer displayed. The device in question is an ancient Xelio tablet and I believe the model to be P900BK if that's of any use. It's currently running Android 4.0.4 and doesn't come stock with the Android Google Play App Store although it has Slide Me and I partially side loaded the Play Store but most of the newer apps I'm trying to install fail some form of validation that occurs in the background whenever I try to run them. I found an APK for Google Play Music that was compatible (I think) with Android 4.0.4 and casting wasn't an option then so it wasn't there.
In a perfect world I'd be able to install Google Play Music (Now has to be YouTube Music though I suppose) and this app here: Hero Timer - WOD Timer Crossfit and HIIT Since it's free and easy to see like the timers most gyms use. I could also use Flex Timer or something else but most all I would want to use for ease of viewing from a distance don't appear to be compatible. The Slide Me app store has nothing of any use that I can find.
I guess the easiest solution would be to find 2 apps in the Slide Me app store that stream music via Chromecast and one that's a good timer that allows for intervals and is large enough to see from a distance on a smaller tablet but as of now I can't seem to find anything that fits that bill. My guess is I won't either on the former due to Google locking that streaming feature down and the latter is mostly trash from what I can tell.
So, any thoughts on this? I'd rather not invest a boat load of time into rooting and potentially bricking this device if I can avoid it but if it's the only option I guess I don't mind. I'd just have to wait until I can carve out enough time to do this which may not be right away. If I do explore this option, one of my concerns is hardware. I'm not sure the ancient hardware this device sports can handle much in terms of ROMs or latest whiz-bang apps or features.
I'm not sure it even has the guts to do what I'm asking but I was hoping someone here who knew the answer could offer up some solutions as I've been out of the custom Android device game for a number of years now.
Thoughts?
This low-end tablet was released 2013-07-09. It runs on Android IceCream. You only can install and run apps on it what are compatible with this Android version.
jwoegerbauer said:
This low-end tablet was released 2013-07-09. It runs on Android IceCream. You only can install and run apps on it what are compatible with this Android version.
Click to expand...
Click to collapse
Right after you finished typing that and you read it back to yourself did you think "Yeah, he'll find this useful" before you clicked submit?
Yeah I don't find the appeal of ATV, I rather have a full pure Android box instead maybe because I am too used to the versitility of a full pure Android OS. Do people just like it for all those recommendations cluttering their desktop screen ? I find it annoying that I can't even use an apps like RSS Player !
EdT586 said:
Yeah I don't find the appeal of ATV, I rather have a full pure Android box instead maybe because I am too used to the versitility of a full pure Android OS. Do people just like it for all those recommendations cluttering their desktop screen ? I find it annoying that I can't even use an apps like RSS Player !
Click to expand...
Click to collapse
You can change the launcher to whatever you like. Attached you will find my setup.
It has my streaming clients, games for my son and some apps I use.
In Android TV I only need 1 remote: I can turn on/off my TV with it, change volume and navigate. It's also very wife friendly
If anything, ATV is clutter free with the right launcher and is designed to be used with remote. For a TV box, you don't really need million options, that pure android gives you.