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 purchased the Nyko Playpad assuming because of the packaging that it would simply sync and then i would key map and i would be playing Castlevania:COTM right now after years of not owning an actual GameBoy. I tried the suggested/"included free software" available from the play store, I got the controller synced in APP mode, which only works for initial boot and in the app its self. It does not work as a mouse or HID input. One of my emulators has iCade support; so I set the controller to iCade, synced and then went to key map. Failure. I've gotten as far as getting the controller to recognize 2-4 commands from the controller at a time; however, they inputs were, I: straight into the google seach app thinger II: the back key III: 5/* IV: 8. so no really anything useful for playing any sort of game or even browsing in mouse mode.
I began re-reading all of the instructions, reviews and watching Nyko's how-to stuff on YouTube. Over the course of 5 hard hours of me being neck deep in failure and coding I don't fuly understand, I found my problem. Sense lacks proper l2cap support, apparently...
I tried Bluez IME, and its respective hid enabling apk. That did not work for me either.
So, right now, I'm looking at unlocking and possibly rooting.. I guess, I'm not ready to admit defeat and return the controller right yet. Will Cyanogen/any other stable homebrew unlock this for me without msoftware, I goe losing camera, BT, etc... functions? Will a simple unlock and a flash of the BT fix the issue or is it too closely tied to the sense input system? I'm not too familiar with all the coding, but I have been an Ubuntu user for about a decade, I know it's like the baby step, but it's quick and has me at least a little familiar with the Android's linux based system.
Stats-
model number: HTC6435LVW
hardware version: 003
Android version: 4.1.1 w/ Sense 4+
software number: 2.06.605.1 710RD
Any other stats needed can be gladly provided.
Help, guidance and ibuprofen are all greatly appreciated.
Unfortunately, unless someone has tried that specific controller with the software that you want to run, you'll just never know for sure.
Thanks to your post though, I just tried a Zagg Flexx keyboard which has never worked with Sense (4.1, I haven't tried newer Senses) and didn't work with CM 10.1. It is working just fine for me on CM 10.2.
Well snap, you think if i set up CM 10.2 it would be kosher and i could reinstall my emulators and game roms, proceed to link via BT and actually be able to use the thing as an input device?
I was going to just jump the gun and do it, but I'm having issues even compiling adb and the like... I'm on Ubuntu 12.10, afaik. The htc guide offers windows instructions, but only files for linux/mac use. I got stuck on a ".bin" step... the first one actually..
Could I get a step-by-step and a complete list of what I actually need? I've been all over and through 80+ page threads and watched an hours worth of youtube guides, many of which are thanks to this forum, and thank you, but I'm lost...
Guru guidance is much appreciated.
As I said, no way to know for sure unless someone has actually tried it. Every device potentially acts differently.
It should be easy to install (not compile) adb for linux. You need to install the Android SDK from Google and make sure you select the right component to get adb. Searching for
install adb linux
should give you easy instructions.
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.
Hi, I've been using Ubuntu Touch Vivid Vervet on my Nexus 4 for past few days and I have some questions:
0) Do I use the best version? I've found out it should be released on 2015, so is this some preview version? I'm using 15.04 (r1)
1) Is there a way how to get notifications from apps? I mean for exmple emails (gmail) or facebook (not necessary), mainly the emails concerne me
2) is there a way how to change default white background on apps scope?
3) is there way how to get step counter working? I've seen it on screenshots on welcome screen bubble statistics and I'd like to have it too
4) how updating works? Does this welcome screeen bubble statistics persits after flashing new/other builds? Can I somehow backup and then restore it?
5) can I somehow access internal storage? (I dualboot with lollipop).. I've found this guide, but it doesn't work, I guess because it is almost one year old and I have newer release. It fails on this command
Code:
$sudo mount --bind /userdata/media/0 ~/Mount
saying this path doesn't exist or something like that
6) When calling, other side complains that he/she can barely understand what I say (I can hear them ok), that sound quality is very poor. I don't have this issue on Android, so it shouldn't be HW error. Is this known bug or is it connected to wrong release I maybe use?
Thanks
Hi!
The recommended channel for end-users is called "ubuntu-rtm/devel". That's the channel which the commercial Ubuntu phones which will be realeased soon will use as well. It gets a lot of updates but is still somewhat behind the devel channel. Therefore, you get much more stable builds.
The devel-proposed channel is what the developers of the OS are using. It always contains the latest software but the drawback is that it sometimes doesn't even boot. The "normal" devel channel infrequently gets updated, stable builds from the devel-proposed channel but those are pushed out very infrequently.
Therefore, I'd recommend every end-user to go with the "ubuntu-rtm/devel" channel instead of the "normal" devel or devel-proposed channels.
GMail notifications should work if add your GMail account in the settings and tick the checkbox which allows the GMail (web-)app to use it.
I am currently working on some fixes for some issues with that feature. Maybe you're hitting the same ones as I do.
Changing the background is not supported. You can only change the lockscreen background. (There's an option in the settings for that.)
What do you mean with "step counter"? Do you want the phone to count how many steps you make? If that's what you're looking for, then I have to tell you that it's currently not possible.
After logging in to your Ubuntu One account in the settings app, you'll get update notifications whenever a new build is available. (Updates are very unlikely to appear on the devel (vivid) channel though as described above.)
I read you're dualbooting with Lollipop so switching channels won't be that easy. I wrote a little backup script a while ago, which requires an Ubuntu PC with the Ubuntu SDK installed though. Here's the link: https://github.com/nikwen/phablet-scripts
For sharing data, check out this thread. It worked for me when I tried it: http://forum.xda-developers.com/showthread.php?t=2595752
The sound issue could indeed be an issue with the devel (vivid) channel. Maybe it will be better on the ubuntu-rtm/devel channel. However, I really don't know.
If you have any further questions, feel free to ask.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
I'm also having issues with the notifications; this is the most recent thread I could find on this subject. I have the notification checkboxes ticked in the System Settings menu, but I haven't received a single notification from anything besides SMS. I'm running 15.04 (r1).
optimaldante said:
I'm also having issues with the notifications; this is the most recent thread I could find on this subject. I have the notification checkboxes ticked in the System Settings menu, but I haven't received a single notification from anything besides SMS. I'm running 15.04 (r1).
Click to expand...
Click to collapse
I guess you're on the devel channel, right? I really suggest switching to the stable channel, which is, although based on 14.10, more up to date than the 3-months-old devel builds.
Actually, I fixed my notification issues some time ago and have now been waiting to get my patches reviewed and merged for almost two months. I've almost given up that this will ever happen...
If you want to increase the problem's importance, please select that the following 4 bugs affect you:
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405645
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405646
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405649
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405651
You can use the Ubuntu One account from your phone to log in.
Maybe that creates some pressure so that the patches will eventually be merged.
nikwen said:
I guess you're on the devel channel, right? I really suggest switching to the stable channel, which is, although based on 14.10, more up to date than the 3-months-old devel builds.
Actually, I fixed my notification issues some time ago and have now been waiting to get my patches reviewed and merged for almost two months. I've almost given up that this will ever happen...
If you want to increase the problem's importance, please select that the following 4 bugs affect you:
[snip]
You can use the Ubuntu One account from your phone to log in.
Maybe that creates some pressure so that the patches will eventually be merged.
Click to expand...
Click to collapse
AHA! That did it!
For anyone else who's having the same issue and is using MultiROM, make sure you select Utopic Unicorn in the drop-down menu instead of the devel version.
optimaldante said:
AHA! That did it!
For anyone else who's having the same issue and is using MultiROM, make sure you select Utopic Unicorn in the drop-down menu instead of the devel version.
Click to expand...
Click to collapse
Well, the utopic channel is very outdated, just like the devel channel. Use the ubuntu-touch/stable channel instead.
nikwen said:
Well, the utopic channel is very outdated, just like the devel channel. Use the ubuntu-touch/stable channel instead.
Click to expand...
Click to collapse
There isn't a /stable channel in MultiROM. I don't really know what I'm doing. Can you tell?
Out of these channels, which one should I use?
devel
devel-proposed
ubuntu-rtm/14.09
ubuntu-rtm/14.09-proposed
ubuntu-rtm/devel
ubuntu-rtm/devel-proposed
utopic
utopic-proposed
vivid
vivid-proposed
I have a Nexus 5, so I'm not officially supported yet. Is that why there's no /stable channel?
optimaldante said:
There isn't a /stable channel in MultiROM. I don't really know what I'm doing. Can you tell?
Out of these channels, which one should I use?
devel
devel-proposed
ubuntu-rtm/14.09
ubuntu-rtm/14.09-proposed
ubuntu-rtm/devel
ubuntu-rtm/devel-proposed
utopic
utopic-proposed
vivid
vivid-proposed
I have a Nexus 5, so I'm not officially supported yet. Is that why there's no /stable channel?
Click to expand...
Click to collapse
That makes sense, of course. I didn't know you were using a Nexus 5.
I'd recommend going with "ubuntu-rtm/14.09" then, as the stable channel is currently just an alias for that one:
Code:
ubuntu-touch/stable (alias to ubuntu-touch/ubuntu-rtm/14.09)
However, that will probably change in the future.
stable
im using 14.09 and get no notifications only for email and text messages
im hoping the real ubuntu phone i get that ive ordered the facebook / twitter / google notifications work
nikwen said:
That makes sense, of course. I didn't know you were using a Nexus 5.
I'd recommend going with "ubuntu-rtm/14.09" then, as the stable channel is currently just an alias for that one:
Code:
ubuntu-touch/stable (alias to ubuntu-touch/ubuntu-rtm/14.09)
However, that will probably change in the future.
Click to expand...
Click to collapse
wayneward said:
im using 14.09 and get no notifications only for email and text messages
im hoping the real ubuntu phone i get that ive ordered the facebook / twitter / google notifications work
Click to expand...
Click to collapse
I really beg you: Please select that the following bugs affect you (login with the Ubuntu One account which you also used to set up your phone):
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405645
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405646
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405649
https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1405651
Fixes are there. It's just that nobody is looking into merging them.
I'm currently trying to create some pressure here and people marking them as affecting them would really help!
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.