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
Related
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
Hey guys,
I have an issue I'm facing at the moment. I have purchased 3 Samsung Galaxy Nexus devices for my family, and one for myself. I wanted to setup all our devices for them and pre-install essential apps for them, and lay it out in a way which makes each device identical so that my family (which is new to Android) can all get the same easy experience from their devices, rather than everyone getting a different LG/Samsung/HTC device and having to deal with differences in skins every time someone phones me with a question about their device.
Here is what I have done:
1. Unlocked bootloader, root, installed CM10.1.2 + gapps onto my own personal device. Clean install, wiped everything.
2. Setup android with a temporary Gmail account, installed about 20 apps, setup the homescreen, changed a few settings for simplicity, change wallpapers, etc.
3. Once I was satisfied, I removed the google account, rebooted to recovery (CWM 6.0.3.2) and made a Nandroid backup which was later copied to my home server.
4. Unlocked Bootloader, rooted and installed CM10.1.2 + gapps on all the other devices, booted the device then transferred the Nandroid backup from my home server to each of these other three devices. Restore the backup, reboot, all seems fine so I setup new individual google accounts, and away I went. Everything works fine, at least so it seems.
Now the issue is that I'm having came a day or two after I got everything setup on each device. At the moment I'm having serious issues with the Google Play Store and Push Notifications. Almost all devices intermittently have issues with this. The play store issue I'm getting is [RPC:S-5:AEC-0], and prevents me from downloading or updating apps. Push notifications is not working either. For example, Google hangouts notifications don't notify me of messages on devices intermittently unless I manually check the app. Same goes with facebook and snapchat notifications. Very annoying. Tried all sorts of fixes such as removing the Google account, rebooting and adding it again, but no luck.
It seems like there is some sort of conflict with each device, but I don't understand why. I changed the Android ID on each device hoping that would help, but still no luck. If anyone could offer an explanation why this issue is occurring I would love to hear it!
Cheers.
Edit: Tried making a titanium backup of one device and moved it to a rooted Galaxy S2 running CM10.1 nightlies, and no such issue. Also, updated one nexus device to the latest nightly, still no fix. Hopefully this information will help someone be able to point out the problem somewhere.
Okay, so I've been playing with a couple of these devices today, and by removing a google account, rebooting the device and then adding the google account again, it makes the play store work on that device, but breaks functionality on the other devices. Would someone with a low-level understanding of Android care to explain why this is?
I'm going to try doing a factory reset on one of these Nexus devices and restore a Titanium Backup and see if that helps, unless anyone has any suggestions?
The different accounts are linked to the play store separately, you are best off to just downloaded each app and set up each phone with its own gmail account. I know it sounds time consuming but it would take less time than you've been spending already.
As you learn more about android there are lots of ways of doing almost exactly what you want here, but learning right now will take less time and effort than downloading 20 apps to three different phones
Sent from my Nexus 4 using xda premium
demkantor said:
The different accounts are linked to the play store separately, you are best off to just downloaded each app and set up each phone with its own gmail account. I know it sounds time consuming but it would take less time than you've been spending already.
As you learn more about android there are lots of ways of doing almost exactly what you want here, but learning right now will take less time and effort than downloading 20 apps to three different phones
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but at the same time I'm using my family as guinea pigs to test whether it's possible to clone devices like this, as I'm in charge of the IT department at our organisation and I suggested it may be possible to deploy a large number of identical rooted android devices through the organisation (probably around 30-40 devices to start with). At this stage though, there seems to be some issues with doing this. Would you be able to point me in the direction of how I could clone Android to several devices, or at least deploy an identical setup to several devices? Perhaps I'll need to customize my own ROM based on Cyanogenmod? Chances are I'll be having to support different hardware as well. This may include the Galaxy Nexus, Nexus 4, Xperia Z and the LG Optimus 4X HD.
Well the absolute best way, in my opinion, would be to create your own ROM.
And by this I don't mean you need to learn how to port or build from source (at least not at first) just some simple zipkanging will do for something like this
Take the ROM.zip, open it, take out apps and such you don't want, add it the ones you do, rezip and sign
Now flash this to each phone and they will all have the same ROM and can just add their Google account.
Now if you want to have certain settings or the system ui look different than this you will need to learn how to decompile some apks and edit xml files, but start slow, do what is easy and what you can't figure out let me know and I'll try to help
Sent from my Nexus 4 using xda premium
demkantor said:
Well the absolute best way, in my opinion, would be to create your own ROM.
And by this I don't mean you need to learn how to port or build from source (at least not at first) just some simple zipkanging will do for something like this
Take the ROM.zip, open it, take out apps and such you don't want, add it the ones you do, rezip and sign
Now flash this to each phone and they will all have the same ROM and can just add their Google account.
Now if you want to have certain settings or the system ui look different than this you will need to learn how to decompile some apks and edit xml files, but start slow, do what is easy and what you can't figure out let me know and I'll try to help
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thought this might be the case.
Is it relatively simple to copy the changes I make to one ROM (eg for a Galaxy Nexus) for another ROM (eg. for a Nexus 4)? Is there some sort of Android virtual machine I can test or build this in?
Not simple at all, I was referring to multiple phones of the same type. Its easy to create identical ROMs to be flashed between 30 n4s or 30 genexs, but to create the same identical ROM to work in both types of phones would require source builds matched to each device tree
Which if you know little about android, java, c++ etc, then you have a real long journey ahead of you.
If you want to have an identical ROM (based off one already in existence) be flashed to 30 identical phones this is relatively easy depending on what all you want
Like I said, start small, learn what's easily obtained, then try for something bigger
Sent from my Nexus 4 using xda premium
demkantor said:
Not simple at all, I was referring to multiple phones of the same type. Its easy to create identical ROMs to be flashed between 30 n4s or 30 genexs, but to create the same identical ROM to work in both types of phones would require source builds matched to each device tree
Which if you know little about android, java, c++ etc, then you have a real long journey ahead of you.
If you want to have an identical ROM (based off one already in existence) be flashed to 30 identical phones this is relatively easy depending on what all you want
Like I said, start small, learn what's easily obtained, then try for something bigger
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The idea was to use CM10.1 as a base and simply add in some apps + app data and change some settings. Setting up the homescreen in a certain way would be part of that. The Galaxy Nexus, Nexus 4, Xperia Z, and LG Optimus 4X HD all support CM10.1 stable.
If I setup a device the way I want it, would it be possible to extract some of these custom configurations from the live device to a flashable ROM?
Just because there is the same ROM for each phone doesn't mean they are exact, but in your case probably good enough. But the change you would make would be to each individual ROM (on computer not on phone) and then flashed these new versions of your ROM to each phone.
You can not make changes to your phone when running the os and extract these changes and flash them to another phone easily, near impossible to do it to a different phone make
Like I have been saying, take a ROM, open it up on PC, change what you need, flash to phone. The simpler the changes the easier it is to do. This will have to be done on a case by case basis if you are doing it to multiple types of phones
Now if you give me a list of what you want to change exactly there may be a few things you can do on your phone but in reality this is the harder way, doing all the work on PC is the easier way
Sent from my Nexus 4 using xda premium
Yes, I understand that. I think what I'll have to do is record the changes I make to one ROM in a changelog of some sort, and then simply recreate these changes manually to other ROMs. Through the PC of course.
demkantor said:
Just because there is the same ROM for each phone doesn't mean they are exact, but in your case probably good enough. But the change you would make would be to each individual ROM (on computer not on phone) and then flashed these new versions of your ROM to each phone.
You can not make changes to your phone when running the os and extract these changes and flash them to another phone easily, near impossible to do it to a different phone make
Like I have been saying, take a ROM, open it up on PC, change what you need, flash to phone. The simpler the changes the easier it is to do. This will have to be done on a case by case basis if you are doing it to multiple types of phones
Now if you give me a list of what you want to change exactly there may be a few things you can do on your phone but in reality this is the harder way, doing all the work on PC is the easier way
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well for example, here are the outdated and rough changes I need to make to the settings (this is just a note of the changes in the settingsof the ROM to make it run way I wanted on the device). Attached it as a PDF as I couldn't copy the formatting.
Most of that should be doable by decompiling systemui.apk and settings.apk, somewhat time consuming and depending on your experience a steep learning curve, but should be able to do it
Sent from my Nexus 4 using xda premium
I along with the others in the community have recently been served by GOOGLE with the pull of the apk servers.
If you happen to hard reset your Q then your Q can no longer be setup rendering it useless.
I am willing to payout $50.00 to any dev that can engineer an apk that will allow the user to setup a stock NEXUS Q without googles servers.
The APK will have to do the following -> access and setup the initial setup, this includes, wifi, bluetooth, nfc and adb debugging to be able to load APK's to the systems as I am sure many will be coming that will make the Q worth building this for, hence why GOOGLE pulled the servers because they saw this coming ....all as the original apk did but without the GOOGLE servers or need for servers.
I have 3 of these units and they are great for music, I love the internal amps and want to retain all the internal functions of the ports, also the audio is better quality when stock compared to rooted and cm10.1'ed.
I have one working setup still, one on the shelf and one with cm10.1 working with cheapcast.
Bounty is as follows this will be updated as members add their payment amounts.
IAN-$50.00
***If you are going to attempt this or have questions DEVS email me is best.***
Thanks-Ian
ianandamy said:
I along with the others in the community have recently been served by GOOGLE with the pull of the apk servers.
If you happen to hard reset your Q then your Q can no longer be setup rendering it useless.
I am willing to payout $50.00 to any dev that can engineer an apk that will allow the user to setup a stock NEXUS Q without googles servers.
The APK will have to do the following -> access and setup the initial setup, this includes, wifi, bluetooth, nfc and adb debugging to be able to load APK's to the systems as I am sure many will be coming that will make the Q worth building this for, hence why GOOGLE pulled the servers because they saw this coming ....all as the original apk did but without the GOOGLE servers or need for servers.
I have 3 of these units and they are great for music, I love the internal amps and want to retain all the internal functions of the ports, also the audio is better quality when stock compared to rooted and cm10.1'ed.
I have one working setup still, one on the shelf and one with cm10.1 working with cheapcast.
Bounty is as follows this will be updated as members add their payment amounts.
IAN-$50.00
***If you are going to attempt this or have questions DEVS email me is best.***
Thanks-Ian
Click to expand...
Click to collapse
put this to the top sticky please
Even if somebody makes an apk, there's still the issue of getting it on a stock locked Q.
lokifish marz said:
even if somebody makes an apk, there's still the issue of getting it on a stock locked q.
Click to expand...
Click to collapse
it would be used from your phone like the factory apk
The problem I see is the Q's original BT authentication method has to hacked. If this passes through the servers then this is a serious hurdle. You cannot pair anything that requires you enter a pin on the Q as the dialog doesn't even exist. Considering how crippled stock is, unlocking and installed either a stock based ROM or CM10 would be my suggestion.
Lokifish Marz said:
The problem I see is the Q's original BT authentication method has to hacked. If this passes through the servers then this is a serious hurdle. You cannot pair anything that requires you enter a pin on the Q as the dialog doesn't even exist. Considering how crippled stock is, unlocking and installed either a stock based ROM or CM10 would be my suggestion.
Click to expand...
Click to collapse
Well if someone can write a stock rom or explain how to get adb debugging via usb working without the need to authorized it that would be a start. Because adb via wifi doesnt get the prompt and once you hookup a mouse in host mode you can not get the same usb to mount adb.
Any suggestions??
That is the biggest road block for me, while i know you can work around that it is a big crippling part of the q.
Is there enough interest for a dev to look at the factory setup procedure and see if they can re engineer around needing the servers? ? IDK
ianandamy said:
Well if someone can write a stock rom or explain how to get adb debugging via usb working without the need to authorized it that would be a start. Because adb via wifi doesnt get the prompt and once you hookup a mouse in host mode you can not get the same usb to mount adb.
Any suggestions??
That is the biggest road block for me, while i know you can work around that it is a big crippling part of the q.
Is there enough interest for a dev to look at the factory setup procedure and see if they can re engineer around needing the servers? ? IDK
Click to expand...
Click to collapse
There has been a working stock based ROM for about a year now. Prior to Google killing the Q function it worked as a dual mode with Nova Launcher as a desktop. Even now the desktop mode still works. All that's needed is a keyboard. Also ADB starts on boot even on a fresh install and even after a hard reset. In the current test build everything except Q mode and BT work.
Lokifish Marz said:
There has been a working stock based ROM for about a year now. Prior to Google killing the Q function it worked as a dual mode with Nova Launcher as a desktop. Even now the desktop mode still works. All that's needed is a keyboard. Also ADB starts on boot even on a fresh install and even after a hard reset. In the current test build everything except Q mode and BT work.
Click to expand...
Click to collapse
Are you talking about the one I used in my tutorial?
In dual boot does it have external AMP support?
So it does not prompt you for authorizing ADB once you try to? all 4.2.2 roms include that unless someone deved around that.
Yes I can adb in recovery on the rom I am using but not once booted into the rom it comes up unauthorized.
My Q's must have internal amp support. That is the whole point of the Q, if it doesn't why wouldn't I just go get a Denon Receiver and plug in a chrome cast??
ianandamy said:
Are you talking about the one I used in my tutorial?
In dual boot does it have external AMP support?
So it does not prompt you for authorizing ADB once you try to? all 4.2.2 roms include that unless someone deved around that.
Yes I can adb in recovery on the rom I am using but not once booted into the rom it comes up unauthorized.
My Q's must have internal amp support. That is the whole point of the Q, if it doesn't why wouldn't I just go get a Denon Receiver and plug in a chrome cast??
Click to expand...
Click to collapse
Which tutorial, what ROM?
The ROM I'm talking about supports every function that the stock Q does. BT never worked correctly without a workaround on the Q initially. The needed support was missing in the stock firmware when they released it.
It does not require ADB auth to connect.
Again, it supports every function that the stock Q does as well as having Nova as a "desktop".
(hint- check my sig)
Lokifish Marz said:
Which tutorial, what ROM?
The ROM I'm talking about supports every function that the stock Q does. BT never worked correctly without a workaround on the Q initially. The needed support was missing in the stock firmware when they released it.
It does not require ADB auth to connect.
Again, it supports every function that the stock Q does as well as having Nova as a "desktop".
(hint- check my sig)
Click to expand...
Click to collapse
So how do you log in to it without the nexus q apk not working now since its stock based?
I'm game to try this on my one rooted q running cm10.1 is it possible to and chromecast support or cheapcast to it?
Sent from my Nexus 4 using xda app-developers app
ianandamy said:
So how do you log in to it without the nexus q apk not working now since its stock based?
Click to expand...
Click to collapse
Are you talking ADB or initial setup? If you are talking ADB, then there is no login. Simply connect the Q to your computer and start ADB. If you are talking inital setup then you connect a KB and hit the "HOME" key and it skips setup and takes you to Nova launcher.
darb said:
I'm game to try this on my one rooted q running cm10.1 is it possible to and chromecast support or cheapcast to it?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your best option is to use BubbleUPnP and AirCast or similar app to fill in the gaps. Depending on how things go I may have an update in the next week or so.
Lokifish Marz said:
Your best option is to use BubbleUPnP and AirCast or similar app to fill in the gaps. Depending on how things go I may have an update in the next week or so.
Click to expand...
Click to collapse
that would be great if you could.
thanks
Lokifish Marz said:
Are you talking ADB or initial setup? If you are talking ADB, then there is no login. Simply connect the Q to your computer and start ADB. If you are talking inital setup then you connect a KB and hit the "HOME" key and it skips setup and takes you to Nova launcher.
Your best option is to use BubbleUPnP and AirCast or similar app to fill in the gaps. Depending on how things go I may have an update in the next week or so.
Click to expand...
Click to collapse
how is that updated rom coming for the q?
ianandamy said:
how is that updated rom coming for the q?
Click to expand...
Click to collapse
Not well. Check the weather in San Diego (over 90deg) and imagine no AC and the only ventilation is air from the outside.
Upnpcast...
For everyone still looking for Chromecast support: You may try upnpcast by bubbleguum. It runs as a service on your phone / tablet and enables you to cast to any dlna renderer on your network.
The cool thing about it is, that it works right out of the gmusic app on your phone. As soon as a dlna device is detected on your network,the chromecast button will appear in the gmusic app. Just select the renderer you want to play to and you are good to go.
To play to the Q, install cm10.1 and a dlna renderer (I use bubbleupnp). Running for hours now without a prob. Note though, that the app is 1.99 for unlimited use.
Due to the oppressive heat in my home I purchased some portable A/C units. It cost me going to and speaking at the Big Android BBQ this year which kind of bites as it was to one my last one for a while (baby on the way). Good news is that it is cool enough to run my box and now have a ton of time to dev.
How would you guys fell about xbmc/yatse vs bubble? I'll post more details as they become available.
Lokifish Marz said:
Due to the oppressive heat in my home I purchased some portable A/C units. It cost me going to and speaking at the Big Android BBQ this year which kind of bites as it was to one my last one for a while (baby on the way). Good news is that it is cool enough to run my box and now have a ton of time to dev.
How would you guys fell about xbmc/yatse vs bubble? I'll post more details as they become available.
Click to expand...
Click to collapse
I installed your ROM last night working well. Is there a way to default it to boot to the launcher without it being attached to a keyboard or display seems some of the other streaming options don't load till it hits the launcher screen other then that cheapcast is always working for me. Wish we could also get the q to sleep when unused and turn off the ring.
Can we build a chromecast rom without using cheapcast? I.e lunch the same software as the chromecast device on our Q's?
If we build chromium content shell for android and feed it the app.conf from the chromecast firmware OTA (I cant post links so I cant post the full app.conf)? Or do we need something more? Any linux/android experts have a clue? We can build the content_shell using the build instructions on the chromium wiki @ goggle code. (I cant post outside links). I cant find any web-server or something like that in the chromecast OTA 12940 firmware dump I found on the internet. Does the content_shell include a web-server?
app.conf
Code:
[
{
"url": "${POST_DATA}",
"local_only": true,
"app_name": "Fling",
"use_channel": true
},
{
"url": "XXX/tv?${POST_DATA}",
"app_name": "YouTube",
"use_channel": true
},
{
"url": "XXX/tv/i/mixed?${POST_DATA}",
"allow_empty_post_data": true,
"app_name": "IMAX",
"use_channel": true
},
{
"allow_empty_post_data": true,
"dial_info": "<port>9080</port><capabilities>websocket</capabilities>",
"command_line": "/bin/logwrapper /netflix/bin/netflix_init --data-dir /data/netflix/data -I /data/netflix/AACS -D QWS_DISPLAY=directfb -D LD_LIBRARY_PATH=/system/lib:/netflix/qt/lib -D NF_PLAYREADY_DIR=/data/netflix/playready -D KEYSTORE=/data/netflix/AACS -D KEYBOARD_PORT=7000 -D ENABLE_SECURITY_PATH=1 -D DISABLE_SECURITY_PATH_VIDEO=0 -D DISABLE_SECURITY_PATH_AUDIO=1 --dpi-friendlyname ${FRIENDLY_NAME} -Q source_type=12&dial=${URL_ENCODED_POST_DATA}",
"app_name": "Netflix",
"external": true
},
{
"url": "XXX/cv/receiver.html?${POST_DATA}",
"app_name": "ChromeCast",
"use_channel": true
},
{
"url": "XXX/video/avi/eureka?${URL_ENCODED_POST_DATA}",
"allow_empty_post_data": true,
"app_name": "PlayMovies",
"use_channel": true
},
{
"url": "XXX/eureka/sample/tictactoe/tictactoe.html?${POST_DATA}",
"allow_empty_post_data": true,
"app_name": "TicTacToe",
"use_channel": true
}
]
it seems like the content_shell is launched with this script
Code:
#!/bin/sh
exec /bin/logwrapper /chrome/content_shell --webcore-log-channels=Media --app-config-path=/app.conf --vmodule=*third_party/libjingle/*=3,rendezvous_connection=2,*=0 --js-flags="--trace_gc"
Alright, So we've seen Firefox running on Android Wear, however we can't enter any menus due to no softkeys on the device. I have been trying to install apps such as "Virtual Button Bar" and SoftKeys for Root Users onto the watch and they install and run. But only the home button works. Neither the back or menu button seems to work in any application.
Has anyone else attempted to get some softkeys for controls in unsupported apps that may be able to enlighten me more on why these keypresses seem to be ignored by the OS..
ShadowEO said:
Alright, So we've seen Firefox running on Android Wear, however we can't enter any menus due to no softkeys on the device. I have been trying to install apps such as "Virtual Button Bar" and SoftKeys for Root Users onto the watch and they install and run. But only the home button works. Neither the back or menu button seems to work in any application.
Has anyone else attempted to get some softkeys for controls in unsupported apps that may be able to enlighten me more on why these keypresses seem to be ignored by the OS..
Click to expand...
Click to collapse
With LMT all the keys that can get on-screen are working just fine in apps that support them but the problem is the app can't be launched (FC-most probably because it has an action bar) so you can't edit the buttons or the size of them, they just work but are over sized.
Ranomez said:
With LMT all the keys that can get on-screen are working just fine in apps that support them but the problem is the app can't be launched (FC-most probably because it has an action bar) so you can't edit the buttons or the size of them, they just work but are over sized.
Click to expand...
Click to collapse
I wonder if you can install LMT on your phone, customize it first, then go to /data/data/... or an appropriate location to grab the config and push it into the watch.
I'm also considering buying a GW, so if this somehow works, please let me know.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
I wonder if you can install LMT on your phone, customize it first, then go to /data/data/... or an appropriate location to grab the config and push it into the watch.
I'm also considering buying a GW, so if this somehow works, please let me know.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Yes ofc it will work but the problem with that is that it will take a lot of time to customize the settings right for the watch and each time you copy the files to data/data remember that you will need to set the right permissions, owner and SELinux context for each and every file and considering that currently SELinux contexts can differ from one device to an other and from one ROM to an other that will be really time consuming and hard as you will have to find an app on your watch that has the same types of files to see the SELinux contexts for each of them.
To say it short yes you can do that but it will probably take you at least 1 day and I don't have the time or patience to do that and I doubt many people on this forum will but ofc if you do buy a G Watch have a go at it and tell us just how much time you've wasted.
Ranomez said:
Yes ofc it will work but the problem with that is that it will take a lot of time to customize the settings right for the watch and each time you copy the files to data/data remember that you will need to set the right permissions, owner and SELinux context for each and every file and considering that currently SELinux contexts can differ from one device to an other and from one ROM to an other that will be really time consuming and hard as you will have to find an app on your watch that has the same types of files to see the SELinux contexts for each of them.
To say it short yes you can do that but it will probably take you at least 1 day and I don't have the time or patience to do that and I doubt many people on this forum will but ofc if you do buy a G Watch have a go at it and tell us just how much time you've wasted.
Click to expand...
Click to collapse
Hmm, I doubt it would take that much effort, because I've tried manually moving config for some other apps without even touching the permissions, and they seem to fix that automatically. System apps don't like that way, though.
But seeing how Android Wear hates ActionBar, thus making many of my apps unavailable, I don't know if I'd still buy one. Yes I do want something Android on my wrist, but if it's just time-telling and Google Now (which is not even available here in China), then I'm not paying that chunk for it.
What apps do you have, then?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Hmm, I doubt it would take that much effort, because I've tried manually moving config for some other apps without even touching the permissions, and they seem to fix that automatically. System apps don't like that way, though.
But seeing how Android Wear hates ActionBar, thus making many of my apps unavailable, I don't know if I'd still buy one. Yes I do want something Android on my wrist, but if it's just time-telling and Google Now (which is not even available here in China), then I'm not paying that chunk for it.
What apps do you have, then?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Well you are talking about moving configs to the same phone I guess? Also if not were you on android 5.x+ cause if yes SELinux has became really strict, to the point that if you mess up some contexts on any file in the data partition you could even get a bootloop (happened to me) or have all your apps disappear and be unable to install any app until you fix up the SELinux context (again happened to me), which you will have to do using adb in that state if you don't happen to have and file manager with root capabilities installed in /system/app or /system/priv-app.
Also to answer your question: yes most normal android apps don't work but there are some that do, even some games and some are even really playable, moreover there are enough useful android wear apps out there, I don't know what you plan to use your watch for but for me it does way more than enough, after all it's a watch, it's not like I'll ever want to spend a lot of time looking at it doing anything but I can do some fast reading on it when I need (not like I'll ever read a whole book on it, that's why I have an android e-book reader or even my phone in the worst case scenario), browsing the internet fast (ofc it needs to be connected to a phone with a data connection), receive and send messages, reject calls, even some light or not so light gaming, even things as Temple Run 2, can play music when I don't have my phone using a bluetooth headset/speaker), the only thing I miss is a full office suite, really, I am writing a novel at the moment and never know when I get some inspiration and have to write down what I have in my mind pretty fast so I don't forget, would love to just be able to write on the watch and not have to take out my phone for that.
Also I would suggest that if you have the money you should go with a watch that has wi-fi like the G Watch R or Urbane cause then you will be able to use the internet without a phone, also the screen of the G Watch is really bad in the sun, I had a Sony Smartwatch 2 before and that was way more limited software wise (and for that reason had a battery life of over 1 week) but the screen was miles ahead, I could see everything in powerful sun light without even setting the brightness to the maximum, on the G Watch I can barely see anything with the brightness at maximum in not so powerful sun light.
Does LMT contain the menu button by default? I could care less if it's a little oversized (as long as it's not to big for 150-175 DPI), but I'm about to reset my watch using the restore tools because I screwed up root while trying to get SoftKeyz (EDIT: I believe was the name of the softkey app I was trying to make work, can't remember and just finished resetting) to work correctly.
Ranomez said:
Well you are talking about moving configs to the same phone I guess? Also if not were you on android 5.x+ cause if yes SELinux has became really strict, to the point that if you mess up some contexts on any file in the data partition you could even get a bootloop (happened to me) or have all your apps disappear and be unable to install any app until you fix up the SELinux context (again happened to me), which you will have to do using adb in that state if you don't happen to have and file manager with root capabilities installed in /system/app or /system/priv-app.
Also to answer your question: yes most normal android apps don't work but there are some that do, even some games and some are even really playable, moreover there are enough useful android wear apps out there, I don't know what you plan to use your watch for but for me it does way more than enough, after all it's a watch, it's not like I'll ever want to spend a lot of time looking at it doing anything but I can do some fast reading on it when I need (not like I'll ever read a whole book on it, that's why I have an android e-book reader or even my phone in the worst case scenario), browsing the internet fast (ofc it needs to be connected to a phone with a data connection), receive and send messages, reject calls, even some light or not so light gaming, even things as Temple Run 2, can play music when I don't have my phone using a bluetooth headset/speaker), the only thing I miss is a full office suite, really, I am writing a novel at the moment and never know when I get some inspiration and have to write down what I have in my mind pretty fast so I don't forget, would love to just be able to write on the watch and not have to take out my phone for that.
Also I would suggest that if you have the money you should go with a watch that has wi-fi like the G Watch R or Urbane cause then you will be able to use the internet without a phone, also the screen of the G Watch is really bad in the sun, I had a Sony Smartwatch 2 before and that was way more limited software wise (and for that reason had a battery life of over 1 week) but the screen was miles ahead, I could see everything in powerful sun light without even setting the brightness to the maximum, on the G Watch I can barely see anything with the brightness at maximum in not so powerful sun light.
Click to expand...
Click to collapse
Thanks for compiling such a long response for me :thumbup:
As my signature says most of my devices are on 5.1. Moving some game saves across devices works nicely, though moving contacts database involves modifying owner and permission, but not SEL context - to be honest, I don't even know that ever matters.
Sure I don't have many things in mind when it comes to "what to do with GW"... Back when I was using the Gear, I had quite some apps on it, but most of the time I use it as a timekeeper. But not being compatible with ActionBar is so shocking - I can't imagine how many apps I've used on the Gear so nicely won't work with GW, the most important of which are Greenify, LMT and Root Explorer. Looks like I still have to do much research before I decide on a purchase.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Thanks for compiling such a long response for me :thumbup:
As my signature says most of my devices are on 5.1. Moving some game saves across devices works nicely, though moving contacts database involves modifying owner and permission, but not SEL context - to be honest, I don't even know that ever matters.
Sure I don't have many things in mind when it comes to "what to do with GW"... Back when I was using the Gear, I had quite some apps on it, but most of the time I use it as a timekeeper. But not being compatible with ActionBar is so shocking - I can't imagine how many apps I've used on the Gear so nicely won't work with GW, the most important of which are Greenify, LMT and Root Explorer. Looks like I still have to do much research before I decide on a purchase.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I just looked at your signature and now I know why you had no problem with moving data from one device to an other: all your devices are running CM so they will all use the same security contexts but CM's security contexts are different from normal stock AOSP's contexts and both are different from the contexts used in Samsung TW ROM's, I can bet that if you try to move the data to a stock nexus or some other device running a manufacturer ROM or an other custom ROM than CM (most do use the same contexts but some don't) you will get into problems. SELinux contexts seem to be now just as important as permissions, sometimes you can get around with the wrong owner but if you have wrong Permissions or SELinux contexts you might mess up more than what you were changing.
Also about the app compatibility thing....I don't really miss many apps that I run on my normal devices, the only one I can actually think of is Titanium Backup (and an office app as I said), I found a good replacement for root explorer in MiXplorer, greenify is totally un-needed and wouldn't be too useful even if it worked (I'm actually not sure if it does or not, to me that layout looked like the action bar is either a non-default implementation so it might work without it) because the xposed installer doesn't work (FC-same reason, action bar) but I think xposed could work if someone adapted the installer (doesn't seem to me that the OS-level differences are so big, it's more of the framework), didn't yet try but just for a lol will flash the xposed lollipop zip and see if I can still boot.
An other option for you might be to buy a Gear S, as far as I can see there is some development going on towards running (initially) android wear on it and further afterwards full android.
Ranomez said:
I just looked at your signature and now I know why you had no problem with moving data from one device to an other: all your devices are running CM so they will all use the same security contexts but CM's security contexts are different from normal stock AOSP's contexts and both are different from the contexts used in Samsung TW ROM's, I can bet that if you try to move the data to a stock nexus or some other device running a manufacturer ROM or an other custom ROM than CM (most do use the same contexts but some don't) you will get into problems. SELinux contexts seem to be now just as important as permissions, sometimes you can get around with the wrong owner but if you have wrong Permissions or SELinux contexts you might mess up more than what you were changing.
Also about the app compatibility thing....I don't really miss many apps that I run on my normal devices, the only one I can actually think of is Titanium Backup (and an office app as I said), I found a good replacement for root explorer in MiXplorer, greenify is totally un-needed and wouldn't be too useful even if it worked (I'm actually not sure if it does or not, to me that layout looked like the action bar is either a non-default implementation so it might work without it) because the xposed installer doesn't work (FC-same reason, action bar) but I think xposed could work if someone adapted the installer (doesn't seem to me that the OS-level differences are so big, it's more of the framework), didn't yet try but just for a lol will flash the xposed lollipop zip and see if I can still boot.
An other option for you might be to buy a Gear S, as far as I can see there is some development going on towards running (initially) android wear on it and further afterwards full android.
Click to expand...
Click to collapse
Hmm, you got a good point there. I also move data between one of the CM phones and the TF300TL tablet, but SEL is nonexistent in Android 4.2, so I guess you're right.
Gear S is way out of my reach - if I had that cash I'd buy a ZenWatch, a 360 or even an Omate TrueSmart without hesitation. But thanks for letting me know all this anyway - I choose not to look at GW and Android Wear at this moment.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Hmm, you got a good point there. I also move data between one of the CM phones and the TF300TL tablet, but SEL is nonexistent in Android 4.2, so I guess you're right.
Gear S is way out of my reach - if I had that cash I'd buy a ZenWatch, a 360 or even an Omate TrueSmart without hesitation. But thanks for letting me know all this anyway - I choose not to look at GW and Android Wear at this moment.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
You could instead look at a Gear Live then, it at least has a heart rate sensor and a way better screen for outdoors and at least in my country it is in the same price range as the G Watch (actually cheaper) but yes, I can't totally recommend android wear as it is right now, it's good enough (at least for me) but I can also see why a normal pure android watch could be way better yet I have faith that this will change.
Also I really can't recommend the Omate or any other MediaTek smart watch as 1st most of them have no resistance to water whatsoever, 2nd they have no support from and 3rd the firmware on them has so many security holes and other flaws it looks like a schweizer.
EDIT: I forgot to say that if you want full android you could search for a SmartQ Z-watch, as far as I know that is a pretty good one and also pretty cheap (on pandawill when it was on "last time sale" it was sold for 30$ and I am talking about the normal not the lite one, the lite one isn't worth it) but I don't think it will be updated anymore, yet android 4.4 is pretty good compared to other android smart watches.
Ranomez said:
You could instead look at a Gear Live then, it at least has a heart rate sensor and a way better screen for outdoors and at least in my country it is in the same price range as the G Watch (actually cheaper) but yes, I can't totally recommend android wear as it is right now, it's good enough (at least for me) but I can also see why a normal pure android watch could be way better yet I have faith that this will change.
Also I really can't recommend the Omate or any other MediaTek smart watch as 1st most of them have no resistance to water whatsoever, 2nd they have no support from and 3rd the firmware on them has so many security holes and other flaws it looks like a schweizer.
EDIT: I forgot to say that if you want full android you could search for a SmartQ Z-watch, as far as I know that is a pretty good one and also pretty cheap (on pandawill when it was on "last time sale" it was sold for 30$ and I am talking about the normal not the lite one, the lite one isn't worth it) but I don't think it will be updated anymore, yet android 4.4 is pretty good compared to other android smart watches.
Click to expand...
Click to collapse
Z Watch? No thanks, I've tried that *before* the Gear, and I sold it within a week and lost $15 in the process - crappy 1GHz MIPS which is not only slow but also lacks compatibility for almost everything I throw at it - not even a custom launcher or a weather app would work. Omate's MTK is indeed unfavorable, and that's why I haven't already got one. And there aren't many people who sell Gear Live here. Which leaves me zero feasible choice.
I guess I could call it an end to my hunt of smartwatches, until something like Neptune Pine (but thinner and lighter) shows up. Thanks for helping me analyze the situation all this time!
AndyYan said:
Z Watch? No thanks, I've tried that *before* the Gear, and I sold it within a week and lost $15 in the process - crappy 1GHz MIPS which is not only slow but also lacks compatibility for almost everything I throw at it - not even a custom launcher or a weather app would work. Omate's MTK is indeed unfavorable, and that's why I haven't already got one. And there aren't many people who sell Gear Live here. Which leaves me zero feasible choice.
I guess I could call it an end to my hunt of smartwatches, until something like Neptune Pine (but thinner and lighter) shows up. Thanks for helping me analyze the situation all this time!
Click to expand...
Click to collapse
Well the compatibility thing has changed as ingenic released a compatibility layer (something like libhoudini for intel CPU's) so as far as I can see from a friend's Z Watch it can run almost anything one would throw at it (ok, anything a bit rational, only apps that can actually be useful on a watch) but yes that CPU is not the fastest and the firmware is not really optimized enough so you would need a custom ROM and perhaps some RAM management script like L Speed to get it lag-free yet I can say my friend's z watch behaves pretty well on Dj Droid, it wasn't really lag-free the 2 weeks time we exchanged watches so I could test it but that's just cause I was using xposed and quite a few modules and also had about 100 apps installed, the lag wasn't really the problem for me, the annoying thing for me was the app load times, it would take me up to 1 minute to launch a 3d game.
This being said I would still recommend you to wait for something better, smartwatches right now are good but I see a lot more potential and I am sure in a few years we will see amazing ones, perhaps as good as our older phones in regards to app compatibility and flexibility, who knows, perhaps they'll even be as powerful as our current phones (as far as it goes phones in 1 year will probably be much powerful than our current phones so anything's possible).
EDIT: I also forgot to say that many apps have been adapted for MIPS since then so even without the compatibility layer there are enough apps working on the Z Watch.
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wireless controller pairing not implemented
No audio over hdmi (so, no audio at all)
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-13.0-20160224-UNOFFICIAL-foster.zip
OLD RELEASES:
cm-12.1-20150819-UNOFFICIAL-foster.zip
cm-12.1-20150720-UNOFFICIAL-foster.zip
cm-12.1-20150709-UNOFFICIAL-foster.zip
missing default android keyboard?
installs fine boots into CM - displaying in 1080p on my monitor just fine.
missing android keyboard.
works fine with usb keyboard (logitech k400r)
amazon app store installs fine, recognizes all apps - minecraft PE crashes on start
touch pad / mouse freezes intermittently
netflix installs but does not play
great start, looking good.
I'm finding all kinds of interesting things working on this... Well, I got the stock libs 'working'. HDCP (or something in the graphics stack) locks up the system on boot when using a custom built kernel. From within CM or even from Nvidia's aosp tree. It will only boot with the kernel pulled out of an official boot image. I compared the ikconfig out of the official kernel with what I'm building in CM and they match. So, I'm kinda lost as to what black magic is at work here... Is something doing a crc check? Is there black box GPL violations in the stock kernel? I don't know. And I had a custom kernel booting stock when I was first trying multirom stuff. So that makes me *really* confused. For the moment, I've disabled kernel compiles in my device tree and I'm shipping a blob kernel. And I hate doing that.
Haven't looked at the missing keyboard yet.
Wifi is closer, but still not there. The wlan0 interface seems to init, but the p2p interface fails and brings it immediately back down. I'll do some more research into that over the weekend.
The screen flickers at times. Don't know why, but I think I saw some system props that affects the screen drawing on stock, once I find those again I should be able to fix that.
The OMX libs work now. Which means game streaming works. I tested a grid game already. Don't have Windows, so I can't test local streaming. And theoretically the aforementioned Netflix problem should be fixed by this as well.
I'm kicking off a build to run overnight (takes 4+ hours for a clean release build [on a AMD FX 9370, no less]), so I should have this stuff up first thing tomorrow morning (pending life (r)).
Edit: And... build failed. Starting over... So, looking at this afternoon now.
Edit 2: Well... I can make it boot when I tinker with it manually, but I'm not having much luck making a reproducible build from source. So... I'll have a release eventually, but with 4 hour rebuilds, I can't say when at this rate.
Steel01 said:
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wifi doesn't enable. (ethernet works fine, though)
Keyboard not installed
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-12.1-20150709-UNOFFICIAL-foster.zip
Click to expand...
Click to collapse
screenshots ?
Glad to see ATV gettin some action ... ooooo hel I'm excited. I've been fastbooting your twrp img. for a few things and its working quite nicely on my pro model. BIG BIG thanks for that @Steel01 Does it look like there will be any issues reguarding which version console its running?
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
yey! please keep going! AOSP + Kodi + Support for official remotes would be awesome!
Steel01 said:
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
Click to expand...
Click to collapse
is it a hybrid rom ?
@[email protected]: Kodi is of great interest to me as well, so I'll work to make sure works well.
@aniel300: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.
I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.
I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.
So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:
1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.
2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.
3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.
Some things still need work, though:
1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...
2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.
All in all, this looks like a very usable test build, if not a daily driver for some use cases.
Hi steel01
I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.
Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm
Good luck on this, thank for you hard work
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.
Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.
I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.
Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.
I think the best thing to do its going back to the basic.
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.
@duanim: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.
There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.