Related
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
Ok, i was looking through a few possible ways of doing this. I own 2 Asus Transformer TF300T's and a TF101. Bot of my TF300T tablets have the keyboard docks. I saw a few different Windows OS emulators for android devices and was wondering if, due to not having an actual computer to use, I could actually use a Windows OS emulator on my TF300T to root another device? I know it is a long shot, but I would like to know what the developers on here think about it and also, if it actually could be done, and how the best way to do this wuld be.
I see a lot of views, but no possible answers. The dock i have has USB port as well. Or maybe no one has a possible answer or has not tried it yet?
Another reason I ask is because my android phone, when pluged into my usb port on my keybord dock allows me to use it as a storage device. I was thinging that a windows emulator would take it one step further and allow me to actually root a device, if done properly. Plus, I did download the windows emulator that is in the play store, the good one. I am actually going to download a Windows XP img file and try and see how well it would run on my talet, but if all goes well, I wanted to try and root an android device with it. I just dont want to brick the device or screw it up somewhere along the line. If someone could give me some examples or if they know the best steps to take regarding this, please let me know.
Grantomas121 said:
Another reason I ask is because my android phone, when pluged into my usb port on my keybord dock allows me to use it as a storage device. I was thinging that a windows emulator would take it one step further and allow me to actually root a device, if done properly. Plus, I did download the windows emulator that is in the play store, the good one. I am actually going to download a Windows XP img file and try and see how well it would run on my talet, but if all goes well, I wanted to try and root an android device with it. I just dont want to brick the device or screw it up somewhere along the line. If someone could give me some examples or if they know the best steps to take regarding this, please let me know.
Click to expand...
Click to collapse
Still nothing on this? well, i did find the one emulator app on the play store, but getting an OS to load up is causing me some issues....
I know this is super old but sparked my interest enough to do a simple goto search... youtube. Just remember it is at your own risk and could possibly not work out and losing function of your device is a possibility.. Also I don't recommend follow links in the discriptions.. I tend to get program names and do my own research (GitHub) for downloads..
Hullo.
Looking for a little advice from folks about sideloading apks to multiple android devices at once (like, 8 or 9 of em). Searched around the forums a bit and couldn't find anything directly relating to this issue, so I figured I'd ask. I dunno if this belongs more in App development, but its an Android specific issue so...
At present I'm using Test Flight App (I'd post the URL but I'm too much of a noob here) to manage builds and releases. Its really great for getting beta builds out to the studio team, and to various beta testers and potential partners.
However there are a few issues with it, which are particularly problematic for quick iterations etc.
1) Actually downloading the apks is a manual process per device. So if you've a small QA team (or are working solo) it takes alot of time to get the newest build onto everything.
2) Each build has to be uploaded via the Test Flight website, then distributed to users on a build by build basis. This is a difficult to automate process, so makes having any kind of continuous integration system for nightlies etc. difficult at best.
I've been looking into possibly doing something like installing a Dropbox on each device and automating CI builds to a dedicated folder, which is shared via Dropbox to everything, but its a bit of work up front to get it working and I may still have to actually manually install the things each time.
Any of you guys had any experience attempting to do something like this?
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Dansixminute said:
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Click to expand...
Click to collapse
How about Wireless ADB?
Check ADB Wireless on Play Store. (Unfortunately all phones must be rooted, because it requires ADB port to be set to 5555)
https://play.google.com/store/apps/details?id=com.wave18.adbwireless
I think you are using batch file to get ADB script for all devices.
Press Thanks if helped.
Would it be possible to emulate android on an android phone? As in, you could supply an app with an android version (or have the app build it for you) an emulate or run it. Any time it asks for something device specific, it would simply run the request back to the stock OS. Said app would kill all but the essential android processes to improve performance. And to return, it could add a shortcut to the app drawer that would close everything and return to the stock. Using this, could we create universal, or at least wider, distributions of android?
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Darkcon said:
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Click to expand...
Click to collapse
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
The Original Leppa said:
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
Click to expand...
Click to collapse
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Darkcon said:
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Click to expand...
Click to collapse
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
The Original Leppa said:
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
Click to expand...
Click to collapse
Hmm you've got a point there, this could be used to root a phone thats unrootable effectively, like the android emulated inside an Iphone that some people did in the Iphone 4 days
all depends on implimentation, you'd have to set up the emulator to trigger normal events, like power saving cpu states etc in response to the emulated android os's requirements
I've been thinking.
Let's say you decide to emulate AOSP Nougat. You then installed the official Pixel Launcher. While emulating, it would act as it should, as it would be entirely identical to if you were running Nougat.
Then you close the emulation. You then try to open Pixel Launcher; it's already installed. Would it crash?
Ok then...
Would I just look for adb? Or does adb simply ask something else to emulate?
hello. i thought to be smart and download the APK through a downloader in browser on PC, but is still not able to install. it just says "App not installed".
ANYHOW... i feel this app should work just fine on the phone. problem is is that the company don't want it on other phones. so, there are some HTC and Sony apps from my past that won't install to a Coolpad phone i have.
is there any way to modify the APK so it will properly install? i don't believe the app to actually be incompatible, it is just proprietary to a different brand of phone.
the app i most want right now is > https://play.google.com/store/apps/details?id=com.sonymobile.xperiaweather
i used this to download it > https://apps.evozi.com/apk-downloader/
thanks for reading! i await any responses
@sk74261700027
If your phone's Android is rooted, you can try to edit Android's build.prop file housed in /system, will say change there brand / model settings according to your needs. Use a "BuildProp Editor" app to manage this,
jwoegerbauer said:
@sk74261700027
If your phone's Android is rooted, you can try to edit Android's build.prop file housed in /system, will say change there brand / model settings according to your needs. Use a "BuildProp Editor" app to manage this,
Click to expand...
Click to collapse
shoot. i have yet to figure out how to root this phone. it doesn't seem like there is any public root method for this phone yet. drat.
but if i could do that on the phone... shouldn't it also be possible to do this in the APK? i also don't know exactly what info that would be put there even if the phone was rooted. meh.
i figured worst case, i could use the regular Android software on PC to make changes to the APK. other then that, i think it could be possible to make changes to the APK with luckypatcher, but am not certain about that.
@sk74261700027
I never made use of LP.
You of course can try to decomplie an APK, rewrite app's source code and afterwards recompile it and then correctly sign the APK. Personally never have done so.
jwoegerbauer said:
@sk74261700027
I never made use of LP.
You of course can try to decomplie an APK, rewrite app's source code and afterwards recompile it and then correctly sign the APK. Personally never have done so.
Click to expand...
Click to collapse
oof. that sounds complicated. lol :/
i know there is Android Studio and SDK tools, but there is a lot there and i don't know exactly what is needed. i was just hoping that changing an APK for proprietary apps to install on non-proprietary devices was a normal thing, and that there would be a straight forward way to do this. sadly, i don't see any guides on this.
might just have to look around for something more generalized, like what you were talking about. i am surprised that there isn't a normal process for this type of thing. meh
well, thanks anyhow. thank you for replying here. at least that might give me an idea on where to go from here. in the meantime, imma just give this thread some more time. see if anyone knows anything more specific about this.
P.S. oh yeah! i do recall some kind of google market app that would allow you to change, or emulate, a device to download apps from the Play Store that are stated as not being compatible. will have to look for that and see if it still works. if someone knows where to find this, that would be really great.