I am working on a mediacenter Rom and I am looking for suggestions for remote control apps for android to control the Q anyone have any good suggestions on controlling the Nexus Q over bluetooth or wifi. This is my only hiccup for this rom.
How far have you got with the ROM yet?
right now i use Bluetooth mouse/keyboard combined with adb over wifi, do you need more control than this?
I've tried a VNC approach but it was a bit strange doing everything from a browser window, but using VNC I used the VMLite_VNC_Server_1_0_4.apk install on Nexus Q
i use ADB and a BT mouse myself at the moment to navigate through the Q. did you manage to add a different launcher on startup?
BT Keyboard?
The tutorials on this board for getting BT Mouse work fine for me. I can't get BT Keyboard working though. If anyone has had success with that let me know!
---------- Post added at 08:32 AM ---------- Previous post was at 08:26 AM ----------
Also I've compiled the kernel to support NFS and CIFS. Recommend adding that to your ROM.
Plex has worked best for me in terms of a consistent playback. This requires Plex media server to be run somewhere else. As its transcoded you can tune the bitrate for consistent playback. I've tried a variety of other players accessing the media via NFS, however none of them can handle full bitrate MKV. Probably it just exceeds the capability of the device.
Romz
My goal is to have a rom others can flash pretty easily and use an existing android device to navigate on the Q.
I'm honestly just figuring out what basic things to throw on the Q for now I might just put a way to flash gapps, but install xbmc.
Heres the process right now that im stuck with now:
-Nandroid restore using the same method I posted for restoring.
(I've been researching the possibility to have a script push and restore the the rom)
-use OTG USB with keyboard and mouse to pair with device
(I've used tablet remote from the play store but the only issue is that the text input does NOT work so searching for things on the store sucks)
But since most people got them at IO the current owners should be pretty confident with adb.
fiveipads said:
My goal is to have a rom others can flash pretty easily and use an existing android device to navigate on the Q.
I'm honestly just figuring out what basic things to throw on the Q for now I might just put a way to flash gapps, but install xbmc.
Heres the process right now that im stuck with now:
-Nandroid restore using the same method I posted for restoring.
(I've been researching the possibility to have a script push and restore the the rom)
-use OTG USB with keyboard and mouse to pair with device
(I've used tablet remote from the play store but the only issue is that the text input does NOT work so searching for things on the store sucks)
But since most people got them at IO the current owners should be pretty confident with adb.
Click to expand...
Click to collapse
How is the play store working on your ROM? able to download/update?
Are you using OTG USB with a hardware adapted or software? (just wondering)
Why do you need to Nandroid Restore the ROM as opposed to making a flashable zip and installing it over CWM?
UKROB86 said:
How is the play store working on your ROM? able to download/update?
Are you using OTG USB with a hardware adapted or software? (just wondering)
Why do you need to Nandroid Restore the ROM as opposed to making a flashable zip and installing it over CWM?
Click to expand...
Click to collapse
1. Haven't tried/ im messing with the build.prop
2. Im using an OTG cable with a USB Hub w/ a keyboard and mouse
3. CWM is a mess right now the text is super tiny on a 1080p tv and I can't get a hold of the dev on rootzwiki to get the source from him so I fix the screen resolution.
fiveipads said:
1. Haven't tried/ im messing with the build.prop
2. Im using an OTG cable with a USB Hub w/ a keyboard and mouse
3. CWM is a mess right now the text is super tiny on a 1080p tv and I can't get a hold of the dev on rootzwiki to get the source from him so I fix the screen resolution.
Click to expand...
Click to collapse
Cool
What's ur progress on the ROM so far? What source are you building it from?
Would it be easier to get the Q working using CM and then just add the xbmc app to act as a media centre? Would probably be less dedicated by could utilize the Q's full potential.
Just my 2 cents.
By the way, please don't get me wrong. I fully appreciate your work!
fiveipads said:
I am working on a mediacenter Rom and I am looking for suggestions for remote control apps for android to control the Q anyone have any good suggestions on controlling the Nexus Q over bluetooth or wifi. This is my only hiccup for this rom.
Click to expand...
Click to collapse
I think the perfect remote software AND the perfect launcher just don't quite exist yet.
One suggestion though... you can probably get the tablet remote to work properly if you tweak the key layout in your rom as I've described in this thread: http://forum.xda-developers.com/showthread.php?t=1892359
You could remap each of the letters to whatever key input is being sent by tablet remote.
Keep us updated on your progress!
dj_ghosie said:
Would it be easier to get the Q working using CM and then just add the xbmc app to act as a media centre? Would probably be less dedicated by could utilize the Q's full potential.
Just my 2 cents.
By the way, please don't get me wrong. I fully appreciate your work!
Click to expand...
Click to collapse
I agree better to have a full CM ROM on here than just an app as the front, but I think he is making a a full ROM, but not sure..
Remote
I don't see why some off you are having problems controling the Q I only used adb once to root and navigate to get my stuff ready. Has far has a controller this is the best mouse keyboard combo I found small portable controll type http://www.ipazzport.com/16A.html is a full keyboard plus it already has the android buttons on it. there is a tutorial here how to redirect the home button to call that way goes to launcher instead of the screen saver thing(http://forum.xda-developers.com/showthread.php?t=1892359). Use nova luncher it wont work with trebuchet from CM9. I have a otg cable with usb hub currently with controller, ps3 controller(yes it works fine with usb cable to play deadtriger) 16gb usb with movies(use stick mount). I apreciate the effort of getting xbmc but I also think a full android rom is better
ohh I forgot use droidmote server is far better than tabletremote
Can't wait see what you come up with OP!
chrlop said:
I don't see why some off you are having problems controling the Q I only used adb once to root and navigate to get my stuff ready. Has far has a controller this is the best mouse keyboard combo I found small portable controll type http://www.ipazzport.com/16A.html is a full keyboard plus it already has the android buttons on it. there is a tutorial here how to redirect the home button to call that way goes to launcher instead of the screen saver thing(http://forum.xda-developers.com/showthread.php?t=1892359). Use nova luncher it wont work with trebuchet from CM9. I have a otg cable with usb hub currently with controller, ps3 controller(yes it works fine with usb cable to play deadtriger) 16gb usb with movies(use stick mount). I apreciate the effort of getting xbmc but I also think a full android rom is better
ohh I forgot use droidmote server is far better than tabletremote
Click to expand...
Click to collapse
Is there a driver needing to installed for the ipazzport keyboard?
Also could you theoretically attach at 1 TB hard drive over usb OTG, with stick mount?
This of any use?
Lokifish Marz said:
This of any use?
Click to expand...
Click to collapse
Loved your work on the Photon back when I had it. Really happy to see that you're working on the Q.
UKROB86 said:
Is there a driver needing to installed for the ipazzport keyboard?
Also could you theoretically attach at 1 TB hard drive over usb OTG, with stick mount?
Click to expand...
Click to collapse
No I don't think you could do that since we don't have a custom kernel, usb mount is built in in android, maybe if you format it fat 32 it could work, good luck. I tried https://play.google.com/store/apps/details?id=com.paragon.mounter&hl=en but it won't work.
For keyboard you don't need drivers android reads those input by default even with put root.
fiveipads,
If you are still active on this, I suggest we pool resources. If the deal goes through, I'll also have a Gnex to help aid in development in about a week.
OR
Please , please , pretty please still be deving on the Q. It's lonely in Q land and its driving me crazy. :silly:
Lokifish Marz said:
fiveipads,
If you are still active on this, I suggest we pool resources. If the deal goes through, I'll also have a Gnex to help aid in development in about a week.
OR
Please , please , pretty please still be deving on the Q. It's lonely in Q land and its driving me crazy. :silly:
Click to expand...
Click to collapse
I know how to build from source pretty well. But without sources for the Q I'm not sure how to get starte. If you take a glance at threads I have started you can see all of my work. PM me if you'd like. I would like to get in on this.
Related
Hey, I'm using ICS on my touchpad and have successfully managed to get USB hosting working to a certain extent. I can use my keyboard with my touchpad with no problems at all However what I was really hoping to be able to do was get a wired xbox 360 controller working. All I get when I plug it in though is a flashing light on the controller itself, the touchpad does not seem to recognise it at all. I heard of an application on the play store called joystick center and have used their "tester" application to see if it can detect the controller. Sadly this didn't seem to work either. Anyone managed to successfully get this working? Or have any suggestions that I can try out?
Thanks for your time
Sent from my Touchpad using xda app-developers app
i think its easier to use a wii or ps3 controller since those have bluetooth built in
I thought that might be the case. Just thought I'd ask as I have an Xbox controller lying around, so would have saved me making a new purchase!
Sent from my Touchpad using xda app-developers app
i know if you want to use an xbox 360 controller on your pc you need to use a usb rf dongle thingy. the usb port on the touchpad isnt powered, and that is another hurdle to jump over.
The Xbox controller I have is the wired version, not the wireless. I have a USB hub that plugs into the mains so it can support things that require power. Have managed to get my keyboard (which requires power) to work perfectly with the touchpad.
Sent from my Touchpad using xda app-developers app
I seem to recall whenever I plugged a Wired 360 controller into a PC, it needed to download some proprietary drivers from Microsoft. I can't imagine those drivers would be built into the Touchpad, so you're probably out of luck as far as that goes.
I can confirm that both PS3 controllers and Wiimotes pair just fine with it, though. Heck, I paired not just the Wiimote, but the Wiimote+Classic Controller Pro and even Wiimote+Tatsunoko vs. Capcom Arcade Stick to the device.
kingteeb said:
The Xbox controller I have is the wired version, not the wireless. I have a USB hub that plugs into the mains so it can support things that require power. Have managed to get my keyboard (which requires power) to work perfectly with the touchpad.
Click to expand...
Click to collapse
oh i see. that is an interesting setup with the hub. its probably just a driver issue then.
Yeah I think that must be it. Any idea if there is any software out there that could address this issue? If not, I suppose I'll have to invest in a new controller!
Sent from my Touchpad using xda app-developers app
I don't know if this is really a driver, but the touchpad (with ICS) has some sort of config file specific to wired 360 controllers. The file can be found at: /system/usr/keylayout/ Vendor_045e_Product_028e.kl
If you poke around at the other things in that folder, it has files for other controllers too including a Logitech one and some steering wheels (heh).
Sent from my Nexus S using xda app-developers app
Oooh well that's a start. I'll have a poke around in there and see what I can find. I love the optimistic steering wheel config files
Sent from my Touchpad using xda app-developers app
Yeah, xbox controllers work with the touchpad, but the kernel cm9 is using doesn't have it enabled by default.
You could either recompile the kernel or just compile the necessary modules to add to your current setup.
The xbox controller actually requires two: ff-memless.ko and xpad.ko. Just stick them in /system/lib/modules once you compile them.
ff-memless.c and xpad.c are already in the tenderloin branch, so you can compile them and pop them in pretty easily. Just look in /drivers/input.
potissimus said:
Yeah, xbox controllers work with the touchpad, but the kernel cm9 is using doesn't have it enabled by default.
You could either recompile the kernel or just compile the necessary modules to add to your current setup.
The xbox controller actually requires two: ff-memless.ko and xpad.ko. Just stick them in /system/lib/modules once you compile them.
ff-memless.c and xpad.c are already in the tenderloin branch, so you can compile them and pop them in pretty easily. Just look in /drivers/input.
Click to expand...
Click to collapse
I've been doing some searching and haven't found what I'm looking for. I don't know how to compile these 2 files for the Touchpad. From what I'm reading it needs to match to the kernel. Does anyone already have the files compiled for CM9 on the touchpad and would share them?
Thanks.
I compiled a CM9 kernel today with wired Xbox 360 gamepad support. It works with the 08/19 CM9 nightly. It may work with other versions, I don't know. Please bear in mind that I am not a developer, and I haven't compiled a kernel of any kind since the last time I installed Gentoo (probably 2005 or earlier). I don't know if this kernel will blow up your Touchpad, summon demons through the speaker-hole, or end world hunger, all I know is that it worked for me, on my Touchpad, with the CM9 08/19 nightly, in John NES Lite, SNESDroid, and Trebuchet (SuperGNES Lite didn't work, it wouldn't recognize the X or Y buttons, and the Back button on the gamepad didn't work in anything I tried). I compiled the support directly into the kernel...probably not the best approach, but it was what I was able to figure out. I don't think I changed anything else in the kernel, and I didn't write any code, just ticked a few options in the make config.
Please try this at your own risk, I don't really have any idea what I am doing, and won't be responsible if bad things happen. If that doesn't scare you off (and it should, you have no idea how new this is to me!), download the attached zip file, unzip it, mount your /boot as rw and copy the uImage.Cyanogenmod.xpad file to /boot, and reboot, selecting the uImage.Cyanogenmod.xpad file in moboot when you reboot. Make sure before you do it that /boot has enough space...if it doesn't, it won't boot when you select it because it won't be fully there.
Anyone smarter than me (ie: almost everyone here) is welcome to tell me what I did wrong and how to do it better.
Has anybody compiled xpad.ko and ff-memless.ko for the Touchpad? I have been looking around and can't find anywhere else that has done this.
Regrettably I have no idea how to compile these myself, maybe I'll try giving one of those tutorials a shot. Would love to have my xbox controller working with the touchpad.
Tired_ said:
I compiled a CM9 kernel today with wired Xbox 360 gamepad support. It works with the 08/19 CM9 nightly. It may work with other versions, I don't know. Please bear in mind that I am not a developer, and I haven't compiled a kernel of any kind since the last time I installed Gentoo (probably 2005 or earlier). I don't know if this kernel will blow up your Touchpad, summon demons through the speaker-hole, or end world hunger, all I know is that it worked for me, on my Touchpad, with the CM9 08/19 nightly, in John NES Lite, SNESDroid, and Trebuchet (SuperGNES Lite didn't work, it wouldn't recognize the X or Y buttons, and the Back button on the gamepad didn't work in anything I tried). I compiled the support directly into the kernel...probably not the best approach, but it was what I was able to figure out. I don't think I changed anything else in the kernel, and I didn't write any code, just ticked a few options in the make config.
Please try this at your own risk, I don't really have any idea what I am doing, and won't be responsible if bad things happen. If that doesn't scare you off (and it should, you have no idea how new this is to me!), download the attached zip file, unzip it, mount your /boot as rw and copy the uImage.Cyanogenmod.xpad file to /boot, and reboot, selecting the uImage.Cyanogenmod.xpad file in moboot when you reboot. Make sure before you do it that /boot has enough space...if it doesn't, it won't boot when you select it because it won't be fully there.
Anyone smarter than me (ie: almost everyone here) is welcome to tell me what I did wrong and how to do it better.
Click to expand...
Click to collapse
Can you explain how did you mount /boot as rw, please ? I tried different shell commands but it always say /boot is not rewritable :crying: so i can't copy the uImage.Cyanogenmod.xpad file.
So you've got a Q, and you've learned how to adb install apps to it... maybe even put a launcher on. But if you've got an NFC capable phone/tablet, you need not mess around with a launcher: your device will be your launcher.
As most of you probably know, the Q ships with a fully capable NFC radio. But for whatever reason, google only ever gave it one official function... beaming out a link the the Q App in the Play Store. Even if you already have it installed. They could have just as easily used a tag to do that job. But I've discovered that if you're running a sideloaded app, the Q will beam that app to your phone. Clearly, we're dealing with a fully beam-compatible device.
However, the Q is programmed to automatically push it's beam out when it finds a device that can receive it. To overcome this, you must open settings (either via a launcher or via adb shell, this is well-documented) and go to the "more" menu. Turn Android Beam OFF while leaving NFC on. This allows the Q to still read your incoming beams (they act just like tags, for compatibility) but it stop apps from opening unexpectedly on your phone.
Once you've done that, you can open any app installed on your Q simply by opening it on your phone/tablet and beaming it over. You'll still need a mouse or keyboard to navigate, but you won't have to futz around with getting to the launcher. This is working on my unrooted Q.
(I don't think this has been discussed before. I hope someone finds it useful!)
Thanks for the info, I was actually wondering whether this was available on the stock firmware. When you say you still need to launch/control with OTG, do things like Youtube links not autoplay when Beamed?
dragon788 said:
Thanks for the info, I was actually wondering whether this was available on the stock firmware. When you say you still need to launch/control with OTG, do things like Youtube links not autoplay when Beamed?
Click to expand...
Click to collapse
This basically opens the app like an android app on the Q. To click on things you need a mouse and an otg cable.
dragon788 said:
Thanks for the info, I was actually wondering whether this was available on the stock firmware. When you say you still need to launch/control with OTG, do things like Youtube links not autoplay when Beamed?
Click to expand...
Click to collapse
Animal24 has it right. And yes, it's available stock and unrooted. If you send a video to the Q, it will still work. However, when the video stops, it will return to the open app, not the standard home screen. If I recall correctly, music will play in the background if an app is open, and the lights will not dance.
That all said, I haven't used the Q since the new music lauched. :/
infeKtion said:
Animal24 has it right. And yes, it's available stock and unrooted. If you send a video to the Q, it will still work. However, when the video stops, it will return to the open app, not the standard home screen. If I recall correctly, music will play in the background if an app is open, and the lights will not dance.
That all said, I haven't used the Q since the new music lauched. :/
Click to expand...
Click to collapse
With CM10.1 and XBMC, I'm planning on using the Q to replace my Revue. I'm all OTA so I don't have a cablebox for the Revue to interface with, and with Aptoide I'm going to see if I can get the new Primetime working on the Q for finding and watching shows from Netflix/etc. Hopefully some year Primetime will do generic Amazon links instead of the GoogleTV apps. I'm using the new Play Music on my Q and using my phone as a remote. I've discovered that I can't seem to beam from the new Play Music to another device, or at least when I do it won't autoplay.
dragon788 said:
I'm using the new Play Music on my Q and using my phone as a remote. I've discovered that I can't seem to beam from the new Play Music to another device, or at least when I do it won't autoplay.
Click to expand...
Click to collapse
How are you doing this? ATM, I'm using BubbleUpNp from both sides, Q and phone. This allows me to still use Google Music as well as All Access. If there is a way to get the stock aplication to work in any way, please share
FadedLite said:
How are you doing this? ATM, I'm using BubbleUpNp from both sides, Q and phone. This allows me to still use Google Music as well as All Access. If there is a way to get the stock aplication to work in any way, please share
Click to expand...
Click to collapse
Hi FadedLite,
I'm using DroidMote to use my phone as a remote to the Nexus Q. I also use ShareKM, another fantastic option that lets me mouse "over" to my Nexus Q from my laptop and control the cursor with my laptop's mouse. One thing I need to figure out is a way to trigger DroidMote Server and ShareKM to start listening on boot, otherwise I have to use my OTG plugged mouse to open the programs and start them up once.
To use Google Music with All Access on the Q, as I stated I'm running CM 10.1 and they have a Gapps package that gives you the Play Store and Play Framework, so you can install Google Play Music and Movies & TV, etc.
Hello all! My first attempt at any type of guide or help, so give me pointers if you notice a better way to go about this than what's here.
This was done by me on my Ultra that broke, but I would imagine the same works for any other device that has a Snapdragon 800, and probably earlier chipsets as well. SPMC and XBMC have documentation about the supported hardware.
Doesn't it suck when you crack the screen on your baby and she no longer responds to touch input? We've probably all been there with one device or another. But don't let that busted phone gather dust, turn it into a full fledged media center! These quad core beasts can do so much more than the phones of a few years ago. I take no credit for anything here, as I'm just passing along my experience so others can make use of a disabled phone.
I have used Plex, Chromecast, etc, but no combination of those gives me the control of XBMC, and the ability to play mostly any codecs without the need for transcoding.
A few things before I get into the steps:
1. I started with a rooted phone, but you don't necessarily need one. It just helps later on if you want more control over the device functions.
2. I recommend using the most up to date firmware possible, I am on 4.4.4 myself, using this rom here:
http://forum.xda-developers.com/showthread.php?t=2800414
3. You'll want a usb OTG cable like the one I used here, along with a cheapo wired usb mouse so you can control the phone until it is set up to work with a remote.
http://www.amazon.com/gp/product/B00871Q5PI/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
4. You'll also need an MHL adapter. I used this one here:
http://www.amazon.com/gp/product/B00KPXI4S2/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
5. You'll need wifi, assuming you have moved the sim to your next device.
6. You will want some form of controlling XBMC remotely. I use Yatse for Android, installed on my replacement phone and it's a godsend.
https://play.google.com/store/apps/details?id=org.leetzone.android.yatsewidgetfree&hl
Here we go.
1. Clean that busted phone up. Reset to factory settings, flash a new rom, OR just remove any non-essential apps. I only have my phone signed into Google so I can access the Play store, which you will want to do as well.
2. Install this if you are rooted. It will allow the phone to disable the screen when the MHL adapter is plugged in, saving battery and keeping it nice and dark around your TV. The wizard should guide you through a fairly simple set up. What you are looking for is for the app to disable/suspend/standby the screen when it detects MHL.
https://play.google.com/store/apps/details?id=com.nkahoang.screenstandby&hl
3. Install SPMC. This is a forked version of XBMC for Android, and frankly, it's better suited for this application. It has more features, and takes better advantage of the hardware.
https://play.google.com/store/apps/details?id=com.semperpax.spmc
4. After installing SPMC, you can use it as a launcher, meaning the phone will boot directly into SPMC. Just press home and you'll be given the option.
5. Launch SMPC, go into Settings-Services-Webserver and check Allow control of XBMC via HTTP.
6. At this point, you can now control SPMC with Yatse or another similar XBMC remote app on another device. Depending on your situation, you may still want that mouse to do a few more things before you connect to the TV.
Options Options Options
I use XBMC in my living room on a dedicated PC. My media resides on a NAS, wired via gigabit ethernet to an AC wireless router. Since I wanted to use this broken phone as a sort of satellite system in the bedroom, I set up a MySQL server on the same NAS. It can be daunting, but XBMC provides great documentation and this method makes getting your media onto the phone very easy.
http://kodi.wiki/view/MySQL
If you do not have another XBMC or do not wish to share the library between devices, skip this section.
1. If you have another instance of XBMC, give this a serious look, as both the library and the playback status will be synced among all devices. You can stop in one room and resume in another.
2. Running the current version of SPMC, and XBMC 13.2, I had no issues with MySQL, despite the warning to use the same build date.
3. If you have this type of setup, all you need to do is copy the advancedsettings.xml file you created from your original XBMC install, and paste it into the userdata folder deep inside the SPMC file structure. This is usually found inside sdcard/Android/data
4. Once you do this, launch SPMC and your existing library will be there.
5. I have not tried this, since I went through the trouble to set up MySQL before, but you can alternatively use Media Browser 3 to serve up your library, and it does appear
to be easier to set up. Download the XBMB3C plugin inside XBMC/SPMC to allow for this.
http://mediabrowser.tv/download/#server
Add Media
Alternatively, you can navigate to videos inside SPMC, select files, and then choose Add Source to add your media from wherever to your new library. There is lots of documentation over at the official XBMC site, so go there if this is your first foray into this type of thing.
I've found that I just have to turn the phone on when I walk into the bedroom, and it will boot directly into SPMC. From that point I can use Yatse on a different device to control the media center. When I am done watching content, the shutdown option inside Yatse will shut the phone off, and it just goes into a powered down charging state.
Mostly everything should play after the install, but you may need or want to adjust some settings inside SPMC/XBMC. Again, look to the official XBMC wiki for help if you need it.
If you're rooted, you can probably do without the USB OTG cable. You could use ADB to install packages and the shell (or a wrapper like this — worked well for me a few months back) to control the screen. This might also be useful if your screen is dead.
There is a new specific xbmc for android that comes preconfigured with the most important repositories for those that really don't want to dabble with all of that kind of stuff. Just install and all the main plugins are automatically installed for you. You can find it here http://www.tvaddons.ag/tvmc-android/
Is TVMC anything more than XBMC 13.2 with preconfigured settings? Seems redundant slightly because SPMC (version 13.3.2) actually contains fixes to XBMC 13.2 to enable hardware acceleration on more devices. With the Z Ultra specifically, under XBMC 13.2 official, even though hardware acceleration was enabled in the settings, it was not working. SPMC is built by official XBMC team members and contains "fixes" that were left out of the official spin for whatever reason. The settings are also mostly preconfigured, at least the defaults are different than regular XBMC, and for me at least, everything worked right away.
What are the possibilities for a phone that does not support MHL? (Oppo Find 5) I had the same idea after I broke my screen, but I am not sure now what to do. A mediacenter seemed great to me. A webserver is possible too, but I don't like how it won't use it's media capabilities anymore.
The device supports wireless screen (Miracast?) but I don't think that works great and I can't get it to work really.
Well, Android Lollipop will support Chromecast Mirroring, so if you are able to find a rom for that device when Lollipop makes its way around, that would work. There seems to be a good amount of development for that phone on XDA, so you might just need to wait it out a bit.
HaTeNL said:
What are the possibilities for a phone that does not support MHL? (Oppo Find 5) I had the same idea after I broke my screen, but I am not sure now what to do. A mediacenter seemed great to me. A webserver is possible too, but I don't like how it won't use it's media capabilities anymore.
The device supports wireless screen (Miracast?) but I don't think that works great and I can't get it to work really.
Click to expand...
Click to collapse
mailme45 said:
Well, Android Lollipop will support Chromecast Mirroring, so if you are able to find a rom for that device when Lollipop makes its way around, that would work. There seems to be a good amount of development for that phone on XDA, so you might just need to wait it out a bit.
Click to expand...
Click to collapse
This may be worth a look if you are interested in chromecast mirroring.
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
mailme45 said:
Hello all! My first attempt at any type of guide or help, so give me pointers if you notice a better way to go about this than what's here.
This was done by me on my Ultra that broke, but I would imagine the same works for any other device that has a Snapdragon 800, and probably earlier chipsets as well. SPMC and XBMC have documentation about the supported hardware.
Doesn't it suck when you crack the screen on your baby and she no longer responds to touch input? We've probably all been there with one device or another. But don't let that busted phone gather dust, turn it into a full fledged media center! These quad core beasts can do so much more than the phones of a few years ago. I take no credit for anything here, as I'm just passing along my experience so others can make use of a disabled phone.
I have used Plex, Chromecast, etc, but no combination of those gives me the control of XBMC, and the ability to play mostly any codecs without the need for transcoding.
A few things before I get into the steps:
1. I started with a rooted phone, but you don't necessarily need one. It just helps later on if you want more control over the device functions.
2. I recommend using the most up to date firmware possible, I am on 4.4.4 myself, using this rom here:
http://forum.xda-developers.com/showthread.php?t=2800414
3. You'll want a usb OTG cable like the one I used here, along with a cheapo wired usb mouse so you can control the phone until it is set up to work with a remote.
http://www.amazon.com/gp/product/B00871Q5PI/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
4. You'll also need an MHL adapter. I used this one here:
http://www.amazon.com/gp/product/B00KPXI4S2/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
5. You'll need wifi, assuming you have moved the sim to your next device.
6. You will want some form of controlling XBMC remotely. I use Yatse for Android, installed on my replacement phone and it's a godsend.
https://play.google.com/store/apps/details?id=org.leetzone.android.yatsewidgetfree&hl
Here we go.
1. Clean that busted phone up. Reset to factory settings, flash a new rom, OR just remove any non-essential apps. I only have my phone signed into Google so I can access the Play store, which you will want to do as well.
2. Install this if you are rooted. It will allow the phone to disable the screen when the MHL adapter is plugged in, saving battery and keeping it nice and dark around your TV. The wizard should guide you through a fairly simple set up. What you are looking for is for the app to disable/suspend/standby the screen when it detects MHL.
https://play.google.com/store/apps/details?id=com.nkahoang.screenstandby&hl
3. Install SPMC. This is a forked version of XBMC for Android, and frankly, it's better suited for this application. It has more features, and takes better advantage of the hardware.
https://play.google.com/store/apps/details?id=com.semperpax.spmc
4. After installing SPMC, you can use it as a launcher, meaning the phone will boot directly into SPMC. Just press home and you'll be given the option.
5. Launch SMPC, go into Settings-Services-Webserver and check Allow control of XBMC via HTTP.
6. At this point, you can now control SPMC with Yatse or another similar XBMC remote app on another device. Depending on your situation, you may still want that mouse to do a few more things before you connect to the TV.
Options Options Options
I use XBMC in my living room on a dedicated PC. My media resides on a NAS, wired via gigabit ethernet to an AC wireless router. Since I wanted to use this broken phone as a sort of satellite system in the bedroom, I set up a MySQL server on the same NAS. It can be daunting, but XBMC provides great documentation and this method makes getting your media onto the phone very easy.
http://kodi.wiki/view/MySQL
If you do not have another XBMC or do not wish to share the library between devices, skip this section.
1. If you have another instance of XBMC, give this a serious look, as both the library and the playback status will be synced among all devices. You can stop in one room and resume in another.
2. Running the current version of SPMC, and XBMC 13.2, I had no issues with MySQL, despite the warning to use the same build date.
3. If you have this type of setup, all you need to do is copy the advancedsettings.xml file you created from your original XBMC install, and paste it into the userdata folder deep inside the SPMC file structure. This is usually found inside sdcard/Android/data
4. Once you do this, launch SPMC and your existing library will be there.
5. I have not tried this, since I went through the trouble to set up MySQL before, but you can alternatively use Media Browser 3 to serve up your library, and it does appear
to be easier to set up. Download the XBMB3C plugin inside XBMC/SPMC to allow for this.
http://mediabrowser.tv/download/#server
Add Media
Alternatively, you can navigate to videos inside SPMC, select files, and then choose Add Source to add your media from wherever to your new library. There is lots of documentation over at the official XBMC site, so go there if this is your first foray into this type of thing.
I've found that I just have to turn the phone on when I walk into the bedroom, and it will boot directly into SPMC. From that point I can use Yatse on a different device to control the media center. When I am done watching content, the shutdown option inside Yatse will shut the phone off, and it just goes into a powered down charging state.
Mostly everything should play after the install, but you may need or want to adjust some settings inside SPMC/XBMC. Again, look to the official XBMC wiki for help if you need it.
Click to expand...
Click to collapse
Im confused. How does the phone charge while its hooked into the TV?
Roseysdaddy said:
Im confused. How does the phone charge while its hooked into the TV?
Click to expand...
Click to collapse
The mhl adapter is powered.
http://ecx.images-amazon.com/images/I/71TmMtz9uIL._SL1500_.jpg
One port to rule them all
adfurgerson said:
The mhl adapter is powered.
http://ecx.images-amazon.com/images/I/71TmMtz9uIL._SL1500_.jpg
Click to expand...
Click to collapse
I have a Galaxy Note 2 with the same issue,
What is confusing me here is the phone has one MicroUSB into which three things need to plug into it
Power
OTG for Mouse and Keyboard
MHL adapter
ShiversZN said:
I have a Galaxy Note 2 with the same issue,
What is confusing me here is the phone has one MicroUSB into which three things need to plug into it
Power
OTG for Mouse and Keyboard
MHL adapter
Click to expand...
Click to collapse
1. The mhl is a Y cable with a male micro usb on the end of cord and a female at the end with hdmi that requires power which runs adapter and charges phone.
2. OTG is only for initial setup and will not be used with mhl ( OP states this is for screens that will display but not respond to touch) after setup control will be via a second device using yatse or another remote control app.
3. See #1.
This thread is great i ened up doing this very thing after destroying the digitizer on an s3 a while ago (I was one unlucky sap to try replacing a cracked screen) and the resultof having a usless phone was made better by having a perminant xbmc device connectd to my tv-way better than satellite or cable
Awesome!
I have a few devices that I keep around. Note 2, galaxy S2, nexus 1 (and my retarded/retired phones iphone 5S, ipad and blackberry playbook). I will definitely give it a try and let you guys know how it goes.
Have you tried on your S2?
Although I've touch screen working, but my gorilla glass is broken. I dont know some are saying that they've to replace whole assemble costing $125 here. While some people on the internet say that it can be done and on ebay I saw front panel(Gorilla) being sold in India.
I just came across this thread after my own experiences with getting this going yesterday! I have an LG Optimus G (E973) with a cracked digitizer, and I was about to buy an Android box, when I realized this phone would be more powerful, and have more features, than anything I could buy in the $100 range.
I made an OTG cable myself. Very easy to do, all you need is a microUSB cable male end, and a USB female end... except, problem #1, I found out my phone doesn't support OTG power. So I had to turn it into an OTG Y-cable so it can receive power (and charge the phone) simultaneously. Then, problem #2, my kernel doesn't support OTG. I wasn't able to figure this out. So I looked for another solution.
Maybe I could install VNC or one of those ADB viewers? Hook up my computer... problem #3, not authorized for adb. Can't authorize without touchscreen. (I later discovered the device keys are stored at /data/misc/adb/adb_keys, and could have added my computer in recovery.) Went to the gf's house and found my old MacBook Air, turns out that one was authorized!
Great! I'm in... now... after fiddling around trying to get it to work in Windows and OSX, problem #4 neither VNC or ADB viewers worked. I could SEE the screen, but interaction did nothing.
Eventually, I decided to just manually run touch events from the adb shell, a la adb shell input swipe 0 0 0 1280 to pull down the menu. Armed with this, I hacked together a script with JavaScript and PHP to have a web interface I could interact with my phone through. It's SLOW as hell at 768x1280 (max 1fps, I'd say), as it uses screenshots.
If anyone is interested, here's the script I made. https:// gist.github.com/shahyar/8d24815b54b8ca1c1d9c
...It didn't end there. I decided now that I have it working, I'll reset the data. Problem #5: I forgot that this also resets debug to off. I had to calculate, using a ruler, where to swipe and tap to enable developer mode, and then enable USB debugging. I wrote an init.d script which did this.
Now, I'm just waiting for my MHL cable and Bluetooth keyboard. Let's hope those go a little better than how the rest of this adventure did.
Screen cracked and not usable
I have a further issue in that my screen is cracked and I can't see what's happening on the screen.
Any thoughts on how to set it up in this case?
Great guide, thank you for taking the time to write it mailme45
tithij said:
I have a further issue in that my screen is cracked and I can't see what's happening on the screen.
Any thoughts on how to set it up in this case?
Click to expand...
Click to collapse
I was in a similar situation when I embarked on this little project, my screen was completely dead but i could hear sounds from the physical buttons so I knew the phone was on. There are a few solutions to get your phone setup, assuming you are still looking for a solution, if not I'll just mention it for the next person in this predicament. If you didn't buy your mhl adapter yet and your screen doesn't work at all, then I suggest buying a mhl cable with CEC function; this will allow you to control your phone with your tv remote when connected. These mhl adapters cost more than the ones found on ebay but also come with more features. The rocketfish RF-G1171($12 at bestbuy) for example will work with most phones including 11-pin samsung models so if you didn't buy a mhl yet, I would recommend getting one with CEC or one that comes as part of a hub, search ebay for the 5in1 mhl. If you already bought a cheap ebay one, continue reading below.
You will need a mhl cable, otg cable and usb mouse/keyboard; These steps are for people with a dead screen and digitizer. If your screen works but touch does not, just use a otg cable and mouse and if your screen doesn't work but touch does then use mhl cable and control using the touch screen.
Note** If you had USB debugging enabled already, skip to step 5
Step 1: connect the MHL cable to your phone and connect with your TV/Monitor and wait for your device to boot into the lockscreen
Step 2: Once at the lockscreen take out the mhl cable and use the otg cable to connect your mouse and swipe to unlock, switch back to mhl cable to make sure you got passed the lockscreen.
Note** If you had a password lock or pattern lock this will be very annoying, use the otg with keyboard if its a password and use mouse for pattern; might take awhile since you will be doing the pattern blind.
Step 3: use the keyboard to navigate to Settings > About Phone > scroll to "build number" and hit enter 7x to turn on developer options.
Note** As each phones menu, app layout and UI is slightly different, you may have to switch between mhl and otg just to see where you currently as you navigate. I suggest taking your time and switching between the two for each action you make, as we will only have to go through this process once.
Step 4: with developer options enabled, navigate to the "developer options" menu and turn on USB debugging.
Step 5: At this stage there are two methods, if you are lucky option 1 will work, if it does not, sadly you will have to go through the annoying mhl/otg switching to navigate one more time.
Option 1:
Install a google chrome app/extension called Vysor on your pc
Link: Vysor
This is an app developed by Koush that allows you to connect, view and control your android device on your PC through USB. The app is still in beta phase so might not work with every phone. Drivers will need to be installed for this app to work, which can be found at the Vysor homepage(I can't link to outsite sites so just google it) along with instructions. If the app works for you, I suggest the first thing you do is turn off certain features like lockscreen and sleep timer; next install a bluetooth keyboard/mouse/controller, something that will allow you to control the phone when connected to the tv/monitor through mhl. Finally you can also do all the required setups mentioned in this thread to get kodi running and when you are satisfied with the setup, connect the phone back to the tv/monitor.
Option 2:
If you were unlucky and Vysor did not work for you, navigate to the play store by switching between mhl and otg and install an app called Teamviewer Quicksupport. Install teamviewer on your PC; launch the app on your phone and you will be given an ID, use the ID on your PC to connect to the phone. When you try to connect from your PC, you will get a confirmation on your phone; make sure your phone is connected through mhl so you can see the confirmation. switch to otg to accept then switch back to mhl since you will be prompted to install an add-on, this add-on is necessary to view your phone screen on your PC. Once the add-on is installed, you will be able to see and control your phone from your pc, use your pc to setup your phone. As mentioned in option one, turn off certain features that are hindrance like lockscreen and install a bluetooth device that will let you control your phone wirelessly.
Hope this helps people with a completely dead screen but otherwise working phone, It can be very frustrating and time consuming but once you get past the initial stuff, you should be able to either link using vysor or wirelessly using teamviewer for feature setups.
So this is a great idea, except that it doesn't work for any other apps, since I do most of my watching on Netflix and HBO and I can't figure out a way to control the phone outside of Kodi.
Content removed.
Content removed.
Content removed.
Hi Zulu, I think I saw someone get a bit of hate for this suggestion with your Nexus Player LolliRock ROM but is it possible to install the Leanback Launcher onto this full Android ROM and emulate most of the Android TV experience? My reason would be that I want the freedom of the full Play Store app and settings but I do like the Android TV interface for use from my couch.
Also, presumably this requires an unlocked bootloader but not root because I've been struggling to root my 16 GB model.
Thanks for your work.
BenjiHansell said:
Hi Zulu, I think I saw someone get a bit of hate for this suggestion with your Nexus Player LolliRock ROM but is it possible to install the Leanback Launcher onto this full Android ROM and emulate most of the Android TV experience? My reason would be that I want the freedom of the full Play Store app and settings but I do like the Android TV interface for use from my couch.
Also, presumably this requires an unlocked bootloader but not root because I've been struggling to root my 16 GB model.
Thanks for your work.
Click to expand...
Click to collapse
Sure that you can. The leanback launcher is a stupid launcher like others but just a little more stupid because not support mouse. But you can start Android TV apps also without leanback launcher. http://www.apkmirror.com/?s=leanback+launcher&post_type=apps_post
You can start the leanback launcher also like an app if you create a shortcut like in this video https://youtu.be/NMqz8e33oq8 So when you install Android TV apps, you can have all in one bad place that is the leanback launcher. Without create a shortcut for every Android TV app. ( 10 in total )
I prferer Googl Now Launcher.
People not understand that you need just more accessibility on apps and this depend from developers.
You can control an app with a mouse, dpad or controller if a developer want this.
After that you can use Android, Android TV or also Android NOOB.
One thing is sure, Android TV is limited on purpose and you can't have all apps from Google Play.
The 320 dpi in build.prop is not compatible with many beautiful apps also if you sideload.
Every standard app is better and faster than the leanback version. Try standard youtube and leanback youtube to understand.
For me the life is too short to waste time with directional keys. I never used a classic Smart TV for this reason and all my TV are Smart TV.
For this reason i like full Android.
You think that if Android TV was better than Android I lose most of my free time to build these firmware ? I'm not so stupid.
But do not worry i appreciate and respect the requests of all
To have Youtube at 1080p and up read this post
https://plus.google.com/+VideomapIt/posts/QiC1Pksvzaq
I suggest to read also the comments. to understand really what i think.
I am very tired of the forced closures made to defend the economic interests of a few.
Many of these closures are also passed off as security but are just violations of the rules for fair competition between companies.
I hope I am not overlooking something due to lack of sleep, but am I correct in saying the nvidia game controller that came with the box doesn't work in this rom? My box isn't recognizing the controller after flashing rom, gapps, and su
After reading a little closer I see it can be made to work if connected via usb, but I much rather have it work wireless since I use the box connected to a network cable and wireless network connection doesn't pose any interference for me. Is there a way to restore the wireless controller connection?
RebelebeR said:
I hope I am not overlooking something due to lack of sleep, but am I correct in saying the nvidia game controller that came with the box doesn't work in this rom? My box isn't recognizing the controller after flashing rom, gapps, and su
After reading a little closer I see it can be made to work if connected via usb, but I much rather have it work wireless since I use the box connected to a network cable and wireless network connection doesn't pose any interference for me. Is there a way to restore the wireless controller connection?
Click to expand...
Click to collapse
For the controller in wireless mode: ( wired works well )
Request it to Nvidia sayng:
Please Nvidia if you sell an hardware controller, why you not publish the drivers for Android, Windows and Linux like all other companies that sell an hardware controller ? Or explain how to add it in a custom firmware ? You publish also the source code, why not publish it as closed binaries like others parts proprietary ?
In the second post you can find an alternative to use the controller in wireless mode.
It work better than native wireless mode, everyone can compare also in Nvidia Grid. ( Grid is beautiful also with my bad adsl )
And don't forget that you can use also any other standard controller ( also a 5$ chinese controller ), because the voice search capability and audio routing is possible in this firmware in many ways. The smarter way to make voice search in google now ( the full google now ) is with a webcam attached or with a bluetooth headsets. It's smarter because you can do this without nothing in your hands. Just sayng: " OK Google " + videochats in hangout and more...
Unfortunally i can't solve this for now. The only one thing that not work, but not for my incompetence.
I don't want use bad words to explain better why this behaviour. But smart people can understand.
Has anyone tried this on a shield tablet? I would assume you ca get a close experience. Also are the Nvidia apps bundled in the rom(controller, grid, game stream)
Sent from my iPhone using Tapatalk
I like this ROM, but I have come across a few things that might make me go back to stock. The problem with wireless game controller not working unless tethered to the device (Not zulu99's fault), and Doom 3 will no longer run. You start it and it immediately just goes back to the home screen without any error to reference. I downloaded the stock image and am still debating as to whether I want to go back to stock or not.. I didn't say it before and I should have, but thanks for all the time and effort you have invested in this ROM.
RebelebeR said:
I like this ROM, but I have come across a few things that might make me go back to stock. The problem with wireless game controller not working unless tethered to the device (Not zulu99's fault), and Doom 3 will no longer run. You start it and it immediately just goes back to the home screen without any error to reference. I downloaded the stock image and am still debating as to whether I want to go back to stock or not.. I didn't say it before and I should have, but thanks for all the time and effort you have invested in this ROM.
Click to expand...
Click to collapse
you have read the second post about the controller config. it work well for me. what is your problem ? why you can't tether ? I'm curious.
zulu99 said:
you have read the second post about the controller config. it work well for me. what is your problem ? why you can't tether ? I'm curious.
Click to expand...
Click to collapse
I'm not sure what is wrong, but I'll figure it out when I have had a little more time with the device. No worries
Bboy486 said:
Has anyone tried this on a shield tablet? I would assume you ca get a close experience. Also are the Nvidia apps bundled in the rom(controller, grid, game stream)
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This firmware is for Shield Console, not for Shield Tablet.
Shield hub that have also grid inside can be downloaded directly from goole play.
for game stream i can work on the nvidia proprietary apk, but i tested Screen Stream Mirroring app and it work.
You can also record your gameplay with any app for screen recording so this is not a problem.
zulu99 said:
This firmware is for Shield Console, not for Shield Tablet.
Shield hub that have also grid inside can be downloaded directly from goole play.
for game stram i can work on the nvidia proprietary apk, but i tested Screen Stream Mirroring app and it work.
Click to expand...
Click to collapse
Forgive my confusion but isn't the point of this rom to mimic the shield console on other android devices? I have the tablet and want to add the android TV experience to it and immersive mode. Wouldn't flashing this Tom accomplish that?
Sent from my iPhone using Tapatalk
Bboy486 said:
Forgive my confusion but isn't the point of this rom to mimic the shield console on other android devices? I have the tablet and want to add the android TV experience to it and immersive mode. Wouldn't flashing this Tom accomplish that?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
No i ported full Android to Shield Console, because on Android TV you are in a walled garden and you can't have all apps from google play
In Android Tv you have also by default density to 320 dpi that is not good for standard apps.
If you like immersive mode you can simply use xposed framework.
Thanks for the clarification. With that said how can I get the android TV experience with Google now search on my tablet? Is it possible?
Sent from my iPhone using Tapatalk
Bboy486 said:
Thanks for the clarification. With that said how can I get the android TV experience with Google now search on my tablet? Is it possible?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
read the second and fifth post
about xposed framework ( for selective immersive mode) i not know if it work on your tablet, on shield console it work.
zulu99 said:
read the second and fifth post
about xposed framework ( for selective immersive mode) i not know if it work on your tablet, on shield console it work.
Click to expand...
Click to collapse
Unfortunately I get a error code when I try to install it
Sent from my SHIELD Tablet using Tapatalk
RebelebeR said:
I like this ROM, but I have come across a few things that might make me go back to stock. The problem with wireless game controller not working unless tethered to the device (Not zulu99's fault), and Doom 3 will no longer run. You start it and it immediately just goes back to the home screen without any error to reference. I downloaded the stock image and am still debating as to whether I want to go back to stock or not.. I didn't say it before and I should have, but thanks for all the time and effort you have invested in this ROM.
Click to expand...
Click to collapse
Thanks for sharing the Doom 3 problem. Yesterday after your words i had it working on my development build.
I will upload a new firmware version very soon that fix the problem.
New firmware version 1.4 updated in first post.
Compatibility with new games optimized for Tegra X1 like Doom 3
Improved performances
We seem to be missing the required "Post your home screen" thread - so let me start it off !
Here's mine. I'm using HALauncher so that I can customize the home screen to my needs. I'm a big fan of HALauncher as it allows:
1 - Control over grouping and ordering. On the Shield default launcher, most-used apps go to the front of the line, so the order is always changing.
2 - Add sideloaded apps
3 - Add web page bookmarks
4 - Add wallpaper
5 - Add custom images for apps on launchers
Full Android V1.8 and I'm loving it. Takes the place of my main computer.
..
kdb424 said:
Full Android V1.8 and I'm loving it. Takes the place of my main computer.
Click to expand...
Click to collapse
dat gocchumon wa usagi desuka wallpaper tho :laugh:
I figured I'd get in on this. This is my SATV home screen. I am using Next 3D launcher and Go Weather EX for the weather widget as the SATV doesn't have the ability to use system widgets, but Next launcher can use widgets specifically built for it like task manager, music, weather, switch, and a few others.
do you need to be rooted to use a launcher, or it just that you click on the luancher icon and then it opens the new menu interface and thats it?
up
do yo uguys mouse and keyboard to navigate? isnt that annoying and takes away from using the remote etc
WHEN you use a luancher is it default... how do you set it to be default
My home screen is just stock. But I too would like to know how you got these launchers to work? And do you have to use keyboard mouse or no?
Sent from my SCH-I545 using Tapatalk
Can you seriously do evverything with this Shield thing? And what is it?
I think it's wonderful...
RemyB__ said:
Can you seriously do evverything with this Shield thing? And what is it?
I think it's wonderful...
Click to expand...
Click to collapse
Start by looking up a few reviews on YouTube and you will see the potential, pretty much play games, watch movie, TV, play music, really just about anything with the proper setup
kdb424 said:
Full Android V1.8 and I'm loving it. Takes the place of my main computer.
Click to expand...
Click to collapse
how do you benefit from a full android experience?
I am using the sideloader and it seems to work well.
Launchers maybe?
Happy Shield TV Setup
Very happy with my Shield TV setup now.
I gave the stock experience a go for a good week before getting fed up of the limitations of Android TV, despite loving the well polished user interface.
Now running full Android 5.1 (v2.2 of zulu99's build), rooted with TWRP recovery and Xposed framework installed.
With a variety of Android TV apps sideloaded from apkmirror.com, I'm now pretty close to having everything which I had before on stock:
Slick, remote-friendly launcher: HALauncher (with lovely background / wallpaper images)
SHIELD Remote as primary input / control device, 90% functional (physical buttons, volume control, audio output when heaphones connected all work, microphone doesn't work yet)
Remote-friendly TV versions of Netflix, YouTube, BBC iPlayer, Emma for Spotify and SHIELD Hub / GeForce Now
Casting entire screen (or specific cast-enabled apps such as Netflix) from Android works and performs well enough to cast an entire movie
With all the numerous advantages of having full android, such as:
Multiple user accounts / profiles (my wife's Spotify plays no longer feed into my last.fm profile, thank god!)
Fully automated video downloading setup, thanks to Pushbullet, Advanced Download Manager and Tasker
Chrome web browser, for web browsing on your TV (finally!)
Casting screen from wife's Macbook Air and/or iPhone now works too, thanks to app "AirPlay Mirroring Receiver"
Thanks to all here who have helped get me to this stage! - primarily zulu99 for his full Android build, but everyone else who has helped by sharing tips/tricks to improve various bits of the experience.
The only thing left to get working as far as I'm concerned is the SHIELD Remote microphone.
This is a really frustrating one, as it's such a nice to have feature and really makes it feel like a futuristic device when you never need to type anything again - Google's voice recognition is outstanding.
I'm also at a bit of a loss as to what to investigate next with it; I've attempted to debug the remote from my PC but could only get it to create a single uni-directional A2DP channel for audio playback.
I guess I should start trying to dig through the kernel modules included in the stock system image.
Anyway, here's the top bit of my home screen:
and a few other screenshots showing the rest of the home screen, settings and the microphone issue.
How do you change the home launcher without changing away from stock.
Almost a real Android now!
@zulu99 Full Android 5.1 (v2.2 build), rooted with Nova Launcher. Still need to install Xposed framework and a few other bits, but getting close to having a real Android now!
Loving some of the setups you guys have! I'll have to get to work on setting mine up.
andrewthecoder said:
Very happy with my Shield TV setup now.
[...]
[*]SHIELD Remote as primary input / control device, 90% functional (physical buttons, volume control, audio output when heaphones connected all work, microphone doesn't work yet)
[...]
Click to expand...
Click to collapse
Hey,
how did you manage it to have the volume buttons of the Shield TV remote working?
I am also running zulus' Full Android and paired the remote with bluetooth but the volume buttons are not working...
Did you do anything special?
A working microphone would make it just perfect
Thanks!
justkidding2009 said:
how did you manage it to have the volume buttons of the Shield TV remote working?
Click to expand...
Click to collapse
I'm actually not entirely sure, the volume slider on the remote wasn't working for me initially either.
I had written it off as something that wasn't going to work, but then noticed it was working accidentally later on after I'd set up more apps.
I believe all I did between the time where it wasn't working and started working was:
Install a few apps made for Android TV (e.g. Netflix, BBC iPlayer, HALauncher, Emma for Spotify)
Disconnect and reconnect the controller a few times
Restart the Shield TV (NSTV) a few times
If you give the above a try and the volume controls on your remote are still not working, post in my other thread about the remote and I'll try and narrow down what's making it work for me!
andrewthecoder said:
I'm actually not entirely sure, the volume slider on the remote wasn't working for me initially either.
I had written it off as something that wasn't going to work, but then noticed it was working accidentally later on after I'd set up more apps.
I believe all I did between the time where it wasn't working and started working was:
Install a few apps made for Android TV (e.g. Netflix, BBC iPlayer, HALauncher, Emma for Spotify)
Disconnect and reconnect the controller a few times
Restart the Shield TV (NSTV) a few times
If you give the above a try and the volume controls on your remote are still not working, post in my other thread about the remote and I'll try and narrow down what's making it work for me!
Click to expand...
Click to collapse
Thanks for your support.
I will test that during the weekend
Are the volume buttons for you only working inside HAlLauncher or also in the "normal" Android Launcher?