Related
Hi there, guys.
First up, sorry if I'm posting in the wrong place. From what I've seen, this looks like it might fit here, but if not, I kindly ask a mod to redirect me. Thanks!
I have started seeing these "HDMI sticks" popping up recently, and I got rather curious about them. So much, in fact, that I have spent several hours trying to figure them out, and thinking about whether I should get one, and in case I should, which one. However, either I have been searching on the wrong places or I have simply gone through so much stuff that I seem to know less each passing minute... :S
So, since you guys have this subforum up, I though you could lend me a hand, so I might understand these things a bit better.
If possible, I would like to know:
- Is there any version available of these sticks with 2GB of RAM? I'm guessing not, from what I've seen. Primary reason for this: I'd like to make a Torrent box out of one. Also, I'm guessing 1GB of RAM might work, especially if I manage to get Linux working?
- What are the options for sticks with Bluetooth? So far, I've seen the MK802 IIIs, the MK809 II, the iMito MX2, the GK802 and the MK808B, but am I missing anything else?
- Which one is considered to be the best, in terms of build quality and problems? I have seen many complaints about WiFi issues, should I be worried?
- Is there a way to bitstream DTS/AC3/DTS-MA? I have read it might be, but I'm not 100% sure.
- Does the YouTube app support preloading? I have had that problem with my N7 (which doesn't support it, while my i9000 does...)
- Which one is being most actively developed (both on the Linux and custom firmware areas)? Also, any limitations known limitations on Linux?
Right now, I am considering either an MK802 IIIs or the 808B, which seem to have pretty much all the options, and are quite cheap at the same time. What do you guys think?
Thanks in advance for your help!
Miguel
__Miguel_ said:
Hi there, guys.
First up, sorry if I'm posting in the wrong place. From what I've seen, this looks like it might fit here, but if not, I kindly ask a mod to redirect me. Thanks!
I have started seeing these "HDMI sticks" popping up recently, and I got rather curious about them. So much, in fact, that I have spent several hours trying to figure them out, and thinking about whether I should get one, and in case I should, which one. However, either I have been searching on the wrong places or I have simply gone through so much stuff that I seem to know less each passing minute... :S
So, since you guys have this subforum up, I though you could lend me a hand, so I might understand these things a bit better.
If possible, I would like to know:
- Is there any version available of these sticks with 2GB of RAM? I'm guessing not, from what I've seen. Primary reason for this: I'd like to make a Torrent box out of one. Also, I'm guessing 1GB of RAM might work, especially if I manage to get Linux working?
- What are the options for sticks with Bluetooth? So far, I've seen the MK802 IIIs, the MK809 II, the iMito MX2, the GK802 and the MK808B, but am I missing anything else?
- Which one is considered to be the best, in terms of build quality and problems? I have seen many complaints about WiFi issues, should I be worried?
- Is there a way to bitstream DTS/AC3/DTS-MA? I have read it might be, but I'm not 100% sure.
- Does the YouTube app support preloading? I have had that problem with my N7 (which doesn't support it, while my i9000 does...)
- Which one is being most actively developed (both on the Linux and custom firmware areas)? Also, any limitations known limitations on Linux?
Right now, I am considering either an MK802 IIIs or the 808B, which seem to have pretty much all the options, and are quite cheap at the same time. What do you guys think?
Thanks in advance for your help!
Miguel
Click to expand...
Click to collapse
i am more or less in the same boat, and i'm holding off the purchase atm, btw here are my findings:
- yes there is one model with 2gb but i don't remember the name and it's not popular at all. 1GB should be more than enough btw.
- i think you listed them all, minus maybe some nearly-unknown ones
- there isn't a "best" one. each has its own share of problems... most common is wifi, then video resolution, then a/v sync, then bugged roms/availability of custom roms, wifi/bt chipsets not supported by custom roms, overheating etc etc, the list is really long and i don't remember them all, but actually none of the available sticks is 100% issue free
- not really sure on this one but afaik it depends on the stick and the rom.
- dunno
- mk808. linux limitation is that hw video acceleration is not present, which basically means no accelerated 2d, no 3d, no hw video decode
i was going to buy the mk808b. it has heatsink and runs at full 1.6ghz while the mk802III does not. unfortunately though the mk808b's wifi sucks and while there is a linux distro available (pic untu) it doesn't/won't offer gpu acceleration which is pretty big
the best option would instead be the odroid but it is not a stick and costs much more.
I bought the MK808. It came rooted. I installed fullscreen, xbmc (hardware accelerated), and auto start. I then configured xbmc to read media from my windows shares, setup bluecops repo so I can stream media from abc, cbs, nbc, etc.. Wifi has been stable for me, but I have caused it to reboot a few times by overloading it (downloading movie info while setting up a stream and trying to add another vidoe location at the same time caused it to reboot). But now the system boots up, goes fullscreen, and starts xbmc Media Center Software on startup. It's not perfect, but I'm starting to like it.
Braccoz said:
the best option would instead be the odroid but it is not a stick and costs much more.
Click to expand...
Click to collapse
Thanks for the reply.
Yes, the ODroid, especially the 2nd versions, are quite interesting, but much more expensive. The U2 is over twice the price of an 808B/IIIs, and that's not even considering the extra eMMC daughterboard or cables needed (though it has double the RAM and CPU cores). Plus, I'm assuming that Linux will have the same problems as the MKs now have, since, well, it has the same GPU...
Maybe I'll be better off waiting for the Chinese New Year? From what I know, they'll stop just about everything between February 8th and February 15th. Can it be they'll present more options, like something based off the RK3188 chip?
Also, I don't necessarily *need* a stick, since it will be connected not to the TV but to an amplifier. It just so happens that sticks seem to be cheaper, more prevalent and with better 3rd-party firmware support than non-sticks... Maybe I should look into the X5 or the Prometheus?
Oh, by the way, any idea if Android has any limitations on webcam resolution? I read somewhere that the maximum video resolution for calls is 640x480, even if you have better hardware, because of the OS...
And, since I'm asking, I've seen something about 1080p firmwares. Can I assume that the stock firmwares are 720p upscaled to 1080p, which would mean video playback would also be upscaled? Or does the upscale only apply to the desktop, and video is properly rendered?
Androidawg said:
I bought the MK808. It came rooted. I installed fullscreen, xbmc (hardware accelerated), and auto start. I then configured xbmc to read media from my windows shares, setup bluecops repo so I can stream media from abc, cbs, nbc, etc.. Wifi has been stable for me, but I have caused it to reboot a few times by overloading it (downloading movie info while setting up a stream and trying to add another vidoe location at the same time caused it to reboot). But now the system boots up, goes fullscreen, and starts xbmc Media Center Software on startup. It's not perfect, but I'm starting to like it.
Click to expand...
Click to collapse
Thanks for the input. That would be my preferable setup, also, since XBMC is now able to properly access hardware acceleration.
If I may ask, does it handle audio properly, as in DTS bitstreaming and the likes?
Miguel
__Miguel_ said:
Thanks for the input. That would be my preferable setup, also, since XBMC is now able to properly access hardware acceleration.
If I may ask, does it handle audio properly, as in DTS bitstreaming and the likes?
Miguel
Click to expand...
Click to collapse
I have a full 1080P HD version of Die Hard that is listed as DTS (it is a .mkv). It is a huge file (13.7 GB) I am running it straight through HDMI to my TV and the sound is working. I did have to tinker with the audio because it was about 2 millisecs behind the picture. Once I fixed that it was perfect. Any of my .avi files have been perfect. Hi Def .mp4 files have been perfect as well.
Androidawg said:
I have a full 1080P HD version of Die Hard that is listed as DTS (it is a .mkv). It is a huge file (13.7 GB) I am running it straight through HDMI to my TV and the sound is working. I did have to tinker with the audio because it was about 2 millisecs behind the picture. Once I fixed that it was perfect. Any of my .avi files have been perfect. Hi Def .mp4 files have been perfect as well.
Click to expand...
Click to collapse
Good to know. XBMC rocks... hehe
Now, are you using a 1080p firmware, or the stock one (which I believe upscales)? In either case, can you check if there's upscaling going on? And, is the problem of movies not running in true full-screen because of the task-bar I've read about resolved?
Oh, and sorry to be nosy, but how do you get XBMC to auto-run on boot? Is there an option in the program, or can it be set as the default launcher?
Thanks!
Miguel
__Miguel_ said:
Good to know. XBMC rocks... hehe
Now, are you using a 1080p firmware, or the stock one (which I believe upscales)? In either case, can you check if there's upscaling going on? And, is the problem of movies not running in true full-screen because of the task-bar I've read about resolved?
Oh, and sorry to be nosy, but how do you get XBMC to auto-run on boot? Is there an option in the program, or can it be set as the default launcher?
Thanks!
Miguel
Click to expand...
Click to collapse
I used two apps, one called fullscreen, it hides the taskbar and it can be set to run on boot. I used another app called auto start. It lets me choose apps to auto start when the android OS fires up. I set it to auto start xbmc. I don't think it is upscaling because I have a 720 TV and I had to do some tinkering in the settings to get the display to shrink down and fit my screen.
Please don't ask for Moonlight help on Nvidia's forums! It's not their responsibility to support this app. Ask on this forum, another non-Nvidia forum, by email, etc
What happened to Limelight?/Why did you change your name?
On April 21, 2015, we received a Cease and Desist letter from Limelight Networks, Inc. They also do streaming services and were concerned about confusion between this project and their company trademarks. To comply with the terms of their C&D, we've decided to rename our project to Moonlight.
Quick Links
Main website: https://moonlight-stream.org
Help: https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide
Discord: https://moonlight-stream.org/discord
PC GitHub project: https://github.com/moonlight-stream/moonlight-qt
iOS GitHub project: https://github.com/moonlight-stream/moonlight-ios
Android GitHub project: https://github.com/moonlight-stream/moonlight-android
Android GitHub releases page (APKs): https://github.com/moonlight-stream/moonlight-android/releases
Embedded port (for Raspberry Pi and other embedded devices): https://github.com/irtimmer/limelight-embedded
GearVR port (for GearVR devices): http://sideloadvr.com/detail.php?id=14
iOS version
The iOS port of Moonlight is now on the App Store: https://itunes.apple.com/us/app/moonlight-game-streaming/id1000551566
Windows, Mac, and Linux port
PC port binaries: https://github.com/moonlight-stream/moonlight-qt/releases
PC port source: https://github.com/moonlight-stream/moonlight-qt
Moonlight for Chrome OS
Download the latest version from the Chrome Web Store.
General Streaming Latency Information
The latency of streaming is dependent on the device you're streaming to and the network you're streaming over. Different devices have different H.264 hardware decoding latency. After streaming, a toast will show up with latency numbers. It will show the total client latency and the portion of the total client latency spent waiting for the hardware decoder. Note that the total client latency does NOT include network latency, so the real latency is higher than the number you see. The total client latency is a measure of the time that the first packet in a frame is received to the time that the frame is released for rendering on screen.
Anecdotal Hardware Decoder Latency Numbers
These are some latency numbers (from memory) I've seen on my test devices as of Moonlight Android 4.0.1. I'll try to keep updating this as I test.
Tier 1 devices:
Tegra 4 - Nvidia Shield - 5 ms - 1080p60 supported
Intel Atom/Bay Trail/Moorefield - Nexus Player - 8 ms - 1080p60 supported (may need a USB OTG Ethernet adapter for consistent performance)
Razer Forge TV - 10 ms - 1080p60 supported - H.265 supported
Tegra X1 - SHIELD Android TV - 10 ms - 4K60 supported - H.265 supported in hardware but needs changes in Moonlight to work well
Tegra K1 - Nexus 9 - 15 ms - 1080p60 supported
Tegra 3 - OUYA and Nexus 7 (2012) - 17 ms - 1080p60 supported
Tier 2 devices:
Broadcom VideoCore IV - Fire TV Stick - 20 ms - 720p60/1080p30 supported
Exynos 7420 - Galaxy S6 - 20 ms - 1080p60/4K30 supported - H.265 supported
Snapdragon S4 Pro (rebranded 600) - Nexus 7 (2013) - 20 ms - 720p60/1080p30 supported
Snapdragon 801 - HTC One M8 GPE - 20 ms - 1080p60 supported
Snapdragon 800 - Nexus 5 - 20 ms - 1080p60 supported
Snapdragon 600 - Fire TV (2014) - 30 ms - 720p60/1080p30 supported
Tier 3 devices:
MediaTek devices - Fire TV (2015) - 55 ms - 1080p60 supported - H.265 supported
Adding games/apps that aren't automatically found
You can stream any almost any game or app by adding the EXE file to GFE manually (if it's not found by the automatic app scan). Open GeForce Experience, click the Preferences tab, click GameStream on the sidebar, then click the add (+) button on the right. Browse to the app or file you want to add and click OK. You can rename the app using the edit button on the right (near the add button).
Using Moonlight as a remote desktop solution
You can stream the entire Windows desktop via Moonlight. Follow step 2 from this guide
Streaming over the Internet
Install the Moonlight Internet Streaming Helper on your host gaming PC to enable streaming over the Internet. If your router supports UPnP, you won't need to make any manual changes.
If the above tool isn't able to enable Internet streaming automatically or your router doesn't support it, forward these ports manually:
TCP 47984, 47989, 48010
UDP 47998, 47999, 48000, 48010
General requirements for current APK:
SoC capable of decoding H.264 High Profile in hardware (Snapdragon, Exynos, Tegra 3 or higher, Rockchip, and more)
Android 4.1 or higher
GeForce Experience with a GTX 600/700/800/900 GPU or GTX 600M/700M/800M (GT-series not supported)
Xbox, PS3 (with SixAxis app), Moga (B/HID mode), Shield, or Ouya controller (other controllers may work too in HID mode)
Mid to high-end wireless router (preferably dual-band 802.11n or better)
Good wireless connection to your Android device
Troubleshooting tips:
1. Make sure GeForce Experience is open, up-to-date, and that you've scanned for games.
2. Make sure your device is on the same network as your computer for initial pairing.
3. Try disabling any firewall software running on your machine.
4. Try rebooting your machine. Sometimes the streaming software gets into a messed up state where it won't work normally until the machine is rebooted.
5. Make sure your Android device has a strong wireless connection (and your PC too, if it's connected wirelessly).
6. For Internet streaming, make sure to install Moonlight Internet Streaming Helper on your host gaming PC, then run the Moonlight Internet Streaming Tester that it installs to troubleshoot further.
7. To check if GFE is working properly, try navigating to the following URLs on your GFE PC:
http://127.0.0.1:47989/serverinfo?uniqueid=1234
https://127.0.0.1:47984/serverinfo?uniqueid=1234
For those with latency issues, please see this post.
Device-related issues
Depending on the wireless chipset on your phone/tablet, you may have a bad streaming experience if Bluetooth is active while streaming. Unfortunately, there's nothing we can do about this. If you experience significant connection degradation with a Bluetooth controller connected, you could try connecting the controller to your PC (see the section above), a USB Ethernet adapter, or controller that connects directly to your Android device (assuming your Android device supports USB OTG)
Older Changes:
Update 12 - March 13, 2014:
Significant video quality improvements. Lower video latency. New UI that makes it easier to choose the best streaming settings. Transient messages are displayed while streaming if network or device problems are detected.
Update 11:
Tegra hardware decoding latency bug is fixed. Hardware decoding is now used by default on Tegra and Rockchip devices. Performance is vastly improved on Tegra devices (1080p60 decodes in real-time, even on Tegra 3). The parser bug causing additional artifacts and image corruption is (finally) fixed.
Update 10:
Added options to force either hardware or software decoding. Reduce audio decoding CPU usage. Fix image quality and performance regressions from update 9.
Update 9:
Reduced CPU usage of video decoding. Added options to choose target resolution (720p or 1080p) and FPS (30 or 60).
Update 8:
Added a checkbox to choose image quality vs performance (only for CPU decoding). Optimize CPU decoding further. The frame rate is now playable on the Ouya with its Tegra 3..
Update 7:
Connectivity issues should be resolved now. Update to the latest APK if you were experiencing connection failures with the last couple of releases.
Update 6:
There's now GUI feedback when connecting. The whitelist for hardware decoding (that only included Qualcomm decoders) has now been replaced with a blacklist (currently containing TI and Nvidia decoders). The Exynos decoder in Exynos 5 Octa has been confirmed to work.
Update 5:
The app will now request a new reference frame if packet loss occurs on the video stream. This means that the stream will recover from blockiness and artifacting that occur when video packets get lost. CPU decoding for non-Snapdragon devices is a bit better. Fixed back button on Shield.
Update 4:
Added multithreaded CPU H264 decoding support for non-Snapdragon devices with ffmpeg. Both landscape orientations now work. This grows the APK significantly so don't be alarmed when this download is larger than previous builds.
Tegra 4 is now very smooth in the games I've tested. Tegra 3 works significantly better than before, but still not perfect (and won't likely ever be as smooth as Snapdragon or Tegra 4).
For Qualcomm devices, a dual-core SoC (even as old as Cortex-A8 stuff) is sufficient due to the hardware decoder. For other devices, CPU decoding will now be used. These devices will need more CPU horsepower (a quad-core Tegra 3 is almost enough).
Look forward to keyboard support and a better GUI coming in the next several days.
Update 3:
Frame pacing improvements for Snapdragon and Tegra devices, although Tegra still has more latency than Snapdragon devices. If you have issues with blockiness or discoloration in the video stream, make sure that you have a good wireless connection. Moonlight doesn't currently deal with packet loss as well as the Shield streaming app.
Update 2:
PS3, Xbox, Shield, and Moga Pro controllers are working with the latest APK.
Update:
Audio is now working. Video is working pretty well on Snapdragon devices (with some lag on Tegra devices). I've attached the current APK here for those that want to test. Due to the framework we're using for video decoding, this app requires Android 4.1 or higher. This is still in alpha so expect bugs.
Original post:
Here is a demo of a WIP app that uses the same Shield streaming technology to stream to any Android device. Controller and mouse input works. Keyboard input isn't implemented yet. Video support works (minus some artifacts at rare points and minor frame pacing issues). Audio doesn't work yet (not sure what format it is).
We've had success with very low H264 decoding latency on Snapdragon S4 Pro/600 devices (like the 2013 Nexus 7 and HTC One), but the Tegra 3/4 decoder has a high latency per frame (~1 second) that makes streaming more laggy on devices like the Ouya, 2012 Nexus 7, and even the Shield itself.
The next big step to a release-ready app is audio support (and the obligatory code cleanup). I'd be happy to respond to any questions about the way the app or the GFE streaming protocol works. If there's significant interest in this, I'll try to put more time into finishing it ASAP.
Demo video (a bit old now):
http://www.youtube.com/watch?v=0VOti83qZRU
Downloads:
I'd recommend downloading the app from the Play Store. Updates are automatically applied through the Play Store when they are released. Crash reports also get to us automatically if you use the Play Store version and click the Report button if Moonlight crashes.
Google Play Link
Sometimes APKs are more convenient for sideloading and other things, so they will continue to be posted.
You can find the latest APKs on the GitHub page here: https://github.com/moonlight-stream/moonlight-android/releases
cgutman said:
Here is a demo of a WIP app that uses the same Shield streaming technology to stream to any Android device. Controller and mouse input works. Keyboard input isn't implemented yet. Video support works (minus some artifacts at rare points and minor frame pacing issues). Audio doesn't work yet (not sure what format it is).
We've had success with very low H264 decoding latency on Snapdragon S4 Pro/600 devices (like the 2013 Nexus 7 and HTC One), but the Tegra 3/4 decoder has a high latency per frame (~1 second) that makes streaming more laggy on devices like the Ouya, 2012 Nexus 7, and even the Shield itself.
The next big step to a release-ready app is audio support (and the obligatory code cleanup). I'd be happy to respond to any questions about the way the app or the GFE streaming protocol works. If there's significant interest in this, I'll try to put more time into finishing it ASAP.
http://www.youtube.com/watch?v=0VOti83qZRU
Click to expand...
Click to collapse
sounds very promising you should post this info over the nexus 7 forum HTC and Samsung forums you will get more interest there
I will be happy to try it on my note 3 if you get audio working
very interesting work however I think you might find this
http://forum.xda-developers.com/showthread.php?t=2506438
a better alternative to work on, maybe if you find a way to get splashtop THD algorithm for streaming, which is leaps and bounds ahead of nvidia's solution. A plus point of this is you can stream anything, your not restricted to just steam and big picture mode.
Really cool!
Tested on Asus TF300 its lagging a lot but i really like what you are doing!
Keep up the good job!
Some questions:
Why no pair button? I had to discover the pair url and do it by hand.
Also why the mac is not read from the android system? Had to change it before compile.
You forgotten to put the link for the code... cant post because new user
danielb7390 said:
Really cool!
Tested on Asus TF300 its lagging a lot but i really like what you are doing!
Keep up the good job!
Some questions:
Why no pair button? I had to discover the pair url and do it by hand.
Also why the mac is not read from the android system? Had to change it before compile.
You forgotten to put the link for the code... cant post because new user
Click to expand...
Click to collapse
The pairing should take place on the first connection. When we get the /pair URL, it should prompt for pairing on the PC. The MAC wasn't read simply because this was some proof of concept code written in a hurry. I'll be fixing that (and other things) shortly.
There's also no UI feedback yet as to what's going on (since we've mostly been debugging it with ADB over the network). I might add some toasts for now to indicate what's going on. In general, it needs cleanup in the UI area along with some code cleanup of some of the early stuff we wrote. There's code in there for mDNS discovery (like the Shield's app uses) which does work but we lack the UI to display the results. We'll also eventually have a proper game selection UI (since we also know how the Shield's app requests game thumbnails), so games can be launched without using Big Picture.
The code link wasn't posted originally because it's a very early proof of concept, but since you asked: https://github.com/cgutman/limelight
EDIT: You were right about the pairing bug. I forgot that we checked if it was paired before attempting to connect. I've added a pairing button and fixed the hardcoded MAC address.
Nice!
"early proof of concept" that works!
I will be following the updates!
Stoped working!
Don't know what happened i cant pair...also tried the same way i did yesterday ( manually through firefox) and it doesn't accept!!!
Really don't know whats going on here!!
danielb7390 said:
Don't know what happened i cant pair...also tried the same way i did yesterday ( manually through firefox) and it doesn't accept!!!
Really don't know whats going on here!!
Click to expand...
Click to collapse
Try pairing using the button. It's possible that the MAC address that you specified manually isn't the same one that the code selects now.
Got it working
Got it working after a pc reboot... stupid windows as always!
Anyways i believe theres a problem in your connection layout i can't click the pair button until i resize "mDNSResultView" because its on top of the buttons or its something else!
Also it's supposed to be working the DNS find? No pc's come up on the list.
I get 1s lag is this normal or i have some problem on my end?
danielb7390 said:
Got it working after a pc reboot... stupid windows as always!
Anyways i believe theres a problem in your connection layout i can't click the pair button until i resize "mDNSResultView" because its on top of the buttons or its something else!
Also it's supposed to be working the DNS find? No pc's come up on the list.
I get 1s lag is this normal or i have some problem on my end?
Click to expand...
Click to collapse
The connection layout problem was some code that someone accidentally committed because they didn't diff what they were committing. They've been publicly shamed
The layout is fixed now so the pairing button should work again.
The H264 stream that is being fed to the decoders currently isn't 100% perfect. There are a few issues we're still trying to work out. The Snapdragon decoder seems to be the most lenient and fast. The Tegra decoder seems to be fairly lenient as well, but does have the 1 second lag which is common to both Tegra 3 and Tegra 4 devices. I'm not sure if the decoder is just too slow for real-time decoding or if we're doing something wrong, but I suspect the latter since I think Shield itself uses the hardware H264 decoder when streaming the normal way. Both of these decoders handle our H264 stream better than TI's hardware decoder and Google's software decoder which both crash immediately with "Decoder Failed -2". I'm working on fixing the H264 stream issues in the "av" branch.
If you need me to test something just say!
The stream is a standard rtsp stream or has something special?
The sound doesn't work why? Can't find the proper decoder?
danielb7390 said:
If you need me to test something just say!
The stream is a standard rtsp stream or has something special?
The sound doesn't work why? Can't find the proper decoder?
Click to expand...
Click to collapse
It's an RTP stream but it seems to have some proprietary 56-byte header between the RTP header and the media payload. It also sends both audio and video on the same RTP stream with the same packet type, so we need to find and remove the audio to parse it separately. I'm working on getting video decoding working 100% on all devices to see if I can root out the bad data causing the software decoder to fail (which might be the audio). I had originally assumed the audio was AAC since we were looking at an H264 stream and the two formats are commonly bundled together, but it appears the audio is something else. At this point, our best guess for the audio format is Opus.
I guess you already tried to open the stream with some player? Or capture the data and try to play it with vlc for example?
Probably saying garbage but whatever!
I just bought an xperia z ultra, I would like to try this out how do I go about it.
You need a pc that meets the requirements for shield streaming
and compile the source code using android SDK.
I don't know if i cant provide a apk.
Can this thread be moved? It's not relevant to the Shield.
Audio is here with the latest code! Turns out that audio was coming in over UDP port 48000. I wrote a JNI binding for the Opus reference decoder and fed the data to the AudioTrack class.
danielb7390 said:
You need a pc that meets the requirements for shield streaming
and compile the source code using android SDK.
I don't know if i cant provide a apk.
Click to expand...
Click to collapse
I've attached an APK that you can use for testing to this post.
nielo360 said:
I just bought an xperia z ultra, I would like to try this out how do I go about it.
Click to expand...
Click to collapse
It should work fine with the attached APK since that phone has a Snapdragon 800 which plays nice with our H264 stream.
LVNeptune8 said:
Can this thread be moved? It's not relevant to the Shield.
Click to expand...
Click to collapse
Sure, ideas for the new location?
Audio its working!
Video still has delay seems little bit better but still needs some work
The middle controller button the "xbox home" button doesn't work at least for me! Its needed to open the steam overlay.
danielb7390 said:
Audio its working!
Video still has delay seems little bit better but still needs some work
The middle controller button the "xbox home" button doesn't work at least for me! Its needed to open the steam overlay.
Click to expand...
Click to collapse
The xbox home button unfortunately sends key events like the Android home button which makes it problematic to intercept. Instead, I've made it so Back+Start will open the steam overlay.
The video delay issue is possibly an issue with Tegra's decoder or how we're interfacing with it. The problem with Google's software decoder and TI's hardware decoder is that the stream that we're getting is H264 high profile, while Android only requires implementing H264 baseline profile. Qualcomm's hardware decoder does high profile perfectly well. Tegra 3 and 4 also support high profile hardware decoding but they seem to decode very slowly, particularly when a large portion of the screen changes. The current plan is to look into software decoding of the H264 stream for devices that have problematic decoders, while letting the Qualcomm devices decode in hardware.
There's an updated APK attached to this post.
Where can I send you a donation?
I have an nVidia SHIELD and Nexus 7, but the only thing I don't like on the shield is the screen size so I'd LOVE to be able to play on my Nexus 7 with a 360 controller, etc so this project looks fantastic!
EDIT: Also, I'm just wondering, but how does this compare to Splashtop THD? Is it using the same NVENC and RTP methods for encoding and sending data? I am thinking about purchasing an ASUS TF701T tablet but one of the main (?) purposes would be remote streaming some games from my desktop. It's confusing that you say that Tegra chips are slower because isn't Splashtop THD (made for Tegra) extremely low latency?
OK, so coming from Surface RT, this thing is small, really small, but I like it, because its soooooo much faster than the Surface RT was. I found myself using my surface for consumption 95% of the time, and the other 5% was doing remote access work. Now, I don't even have to use remote access, x86 support is amazing.
- No web compromises at all - Silverlight support (Time Warner Cable streaming TV - device got really warm doing this, probably why its not supported on WinRT), Java, all the Google stuff, just work with x86, no more sad workarounds through crappy 3rd party apps for RT. Not sure what having Silverlight, Java, Chrome will do to the battery, but so far, its pretty great. I streamed NFL game through IE yesterday, still had 70% battery left after 3.5 hour continuous stream. The back of the device gets warm, but not bad at all.
- Install TouchMousePointer - http://www.lovesummertrue.com/touchm...-us/index.html for those times where you need mouse pointer support on your desktop. I tried to use an Android trackpad app, it didn't work. Im going to be getting new Nokia Lumia 929 on release day, hopefully it works in the MS ecosystem.
- Active Pen support (Synaptics) - I have yet to use this, but reviews elsewhere aren't so great. For the most part, they say that if your a printer, its terrible. If you use cursive for note taking, its good. I am coming from a really bad capacitive (almost unusable), so any improvement will be good........not to mention that I didn't have to spend 1200$ on Surface Pro to get active digitizer. (eta on stylus delivery is 11/7), ill update my review then.
- Bluetooth mouse is a bit laggy, not sure if its my mouse, or the tablet. Maybe a driver update is needed. It seems a bit jumpy......going to see if I can try a different one, hopefully its just the mouse, and not the hardware.
- Micro USB - I really wish I could plug in non powered USB drives via an OTG cable adapter, but unfortunately they do not work. I will have to buy a powered hub to get it to work. Kind of annoying, but its the price you pay to have a device this small. The fact that I can connect to home group, and utilize file transfer via wireless network is a great feature of windows 8.
- No wired external display options - I have yet to try using MHL - anyone try this yet? Im hoping that it works. If not, Ill have to try a Miracast receiver - I am concerned with any lag that could occur though.
- Accessories...........or lack thereof - there are no accessories, dell has an overpriced case (40$), and a 35$ stylus that others suggest shouldn't cost more than 10-15$. I would love to find a good case that would prop it up........Not sure why other OEMs don't understand the importance of a good integrated kickstand - really missing this from the Surface. Wondering if a case from a Note 8, or Kindle, or Nexus would work, don't have time to compare sizes, etc........too busy tinkering, and installing real software on this thing.
- Performance - FAST....a lot faster than I thought.......this isn't your typical Atom processor, check out youtube, there are some videos of this thing playing some serious games at 30fps.....it is legit. Windows apps from the store are super fast, switching between them, etc.........see below for some desktop apps ive installed:
(note, I chose older versions of software purposefully because they are much less taxing on the cpu, but still serve 98% of their purpose):
- AutoCAD 2007 - runs great, faster than on my laptop (its an old laptop with core2duo processor, and AMD gpu). I haven't tried anything 3D, but I assume it will handle basic functions fine - im not going to render anything with it - that's what remote access is for, but in a pinch, if I need to I can open files natively. It tells me that its not compatible with windows 8, but files open no problem. I think im missing some fonts, etc, but for the most part, running AutoCAD on a 8" screen is freaking cool.
- Photoshop CS6 - runs great, haven't tried anything gpu intensive - it opens images Pretty quick.
Want to try Lightroom, Google Earth, VLC, Spotify desktop version, Remote desktop - yes, im going to set up so I can remote access my tablet.........don't ask, just because I can - and that's the beauty of Windows 8!!!...........32gb is pretty limited....I might return it for the 64gb version - unless there any way to install x86 apps, and/ or move installed metro apps to the SD card?
Loving it so far, it has some minor issues, so close to being the PERFECT portable device. If I were an OEM mfr, id make full USB port a priority - if you have to have a small hump on one end to support it, then so be it, its sooooooo much better to not have to have an OTG adaptor cable. Also, HDMI out should be standard as well, especially since Miracast is still somewhat new tech.
UBNAS81 said:
- No web compromises at all - Silverlight support (Time Warner Cable streaming TV - device got really warm doing this, probably why its not supported on WinRT),
Not sure what having Silverlight, Java, Chrome will do to the battery, but so far, its pretty great.
unless there any way to install x86 apps, and/ or move installed metro apps to the SD card?
Loving it so far, it has some minor issues, so close to being the PERFECT portable device. If I were an OEM mfr, id make full USB port a priority - if you have to have a small hump on one end to support it, then so be it, its sooooooo much better to not have to have an OTG adaptor cable. Also, HDMI out should be standard as well, especially since Miracast is still somewhat new tech.
Click to expand...
Click to collapse
Warm isnt why silverlight wasnt support on windows RT (winRT and windows RT are not the same btw, although it is true that there is no silverlight on WinRT I guess). Its obsolete and hardly supported by microsoft, they dont want to bother porting tech that they cant be bothered with on x86 any more to win32 on ARM too.
Silverlight, java and chrome wont effect the battery on your tablet any more than they would on a laptop really.
Its normal windows 8.1, so you can install x86 desktop programs onto whichever drive you want, hence why most software installers specifically ask where to install, just set that to SD card. There is no requirement to use C:/Program Files for win32 applications. That one I thought was common knowledge for all windows users.
Full size USB port would be nice but you wont get full current from it. The battery cannot supply enough current, nothing to do with overall size of the system. The same restriction applies to most windows tablets, android tablets, android phones and more rarely laptops too (although usually old ones).
It really was dumb of dell to not stick a video output somewhere on the device, that almost puts me off the thing entirely.
SixSixSevenSeven said:
Warm isnt why silverlight wasnt support on windows RT (winRT and windows RT are not the same btw, although it is true that there is no silverlight on WinRT I guess). Its obsolete and hardly supported by microsoft, they dont want to bother porting tech that they cant be bothered with on x86 any more to win32 on ARM too.
Silverlight, java and chrome wont effect the battery on your tablet any more than they would on a laptop really.
Its normal windows 8.1, so you can install x86 desktop programs onto whichever drive you want, hence why most software installers specifically ask where to install, just set that to SD card. There is no requirement to use C:/Program Files for win32 applications. That one I thought was common knowledge for all windows users.
Full size USB port would be nice but you wont get full current from it. The battery cannot supply enough current, nothing to do with overall size of the system. The same restriction applies to most windows tablets, android tablets, android phones and more rarely laptops too (although usually old ones).
It really was dumb of dell to not stick a video output somewhere on the device, that almost puts me off the thing entirely.
Click to expand...
Click to collapse
Are you referring to Silverlight the API or Silverlight the video format xD? The API was integrated in .Net and winRT.
mcosmin222 said:
Are you referring to Silverlight the API or Silverlight the video format xD? The API was integrated in .Net and winRT.
Click to expand...
Click to collapse
I was not aware of any video format known as silverlight so you tell me which one I meant.
The API was always .NET based but uses one hell of alot of extensions. Silverlight programs will not run on a bare .NET virtual machine, even the windows 8 one. Easily proven with this lovely thing called trying it at home. .NET was integrated to winRT, silverlights "extra bits" were not.
Last major update to silverlight was december 2011. All releases since have been patch only. Silverlight has poor support outside of windows. Silverlight is entirely unsupported on android, iOS and linux, it seems rather unstable on OSX although that could just be the ancient OSX memory leak (personally witnessed OSX memory leaking on over 10 machines, yet you mention it on the apple forums asking for help in a polite manner and your thread gets deleted or they attribute it to firefox which is great but of the machines I have seen the issue on only 1 had firefox installed, my dads current mac it actually seems to be iTunes, quicktime, vuze and dropbox which are the main offenders) plus my dads mac having hardly any RAM probably compound this. Flash also sucks yet I would choose it over silverlight any day. Any company that limits itself to using silverlight for anything web based is utterly idiotic, except maybe in a thin client environment in some sort of corporation with windows thin clients perhaps, but even then I doubt the suitability in that role...
SixSixSevenSeven said:
I was not aware of any video format known as silverlight so you tell me which one I meant.
The API was always .NET based but uses one hell of alot of extensions. Silverlight programs will not run on a bare .NET virtual machine, even the windows 8 one. Easily proven with this lovely thing called trying it at home. .NET was integrated to winRT, silverlights "extra bits" were not.
Last major update to silverlight was december 2011. All releases since have been patch only. Silverlight has poor support outside of windows. Silverlight is entirely unsupported on android, iOS and linux, it seems rather unstable on OSX although that could just be the ancient OSX memory leak (personally witnessed OSX memory leaking on over 10 machines, yet you mention it on the apple forums asking for help in a polite manner and your thread gets deleted or they attribute it to firefox which is great but of the machines I have seen the issue on only 1 had firefox installed, my dads current mac it actually seems to be iTunes, quicktime, vuze and dropbox which are the main offenders) plus my dads mac having hardly any RAM probably compound this. Flash also sucks yet I would choose it over silverlight any day.
Click to expand...
Click to collapse
Actually, Silverlight was a native API wrapped with .net methods to call from .net language. It was introduced with windows vista and most of it consumed by the WPF API implemented latter. The API itself survives through an open source implementation called Moonlight and is a viable cross platform GUI API.
mcosmin222 said:
Actually, Silverlight was a native API wrapped with .net methods to call from .net language. It was introduced with windows vista and most of it consumed by the WPF API implemented latter. The API itself survives through an open source implementation called Moonlight and is a viable cross platform GUI API.
Click to expand...
Click to collapse
Errm, no it doesnt seeming as moonlight was scrapped, besides, did you ever try moonlight? The thing did not work at all for anything more complex than hello world. Plus you said yourself, native API, entirely contradicting your previous statement of it being part of .NET, you dont really know yourself do you.
My point still stands. Unsupported on linux. Buggy on OSX. No longer being updated besides patching on windows. Not supported on mobile. Yep, totally a viable cross platform GUI.
SixSixSevenSeven said:
Warm isnt why silverlight wasnt support on windows RT (winRT and windows RT are not the same btw, although it is true that there is no silverlight on WinRT I guess). Its obsolete and hardly supported by microsoft, they dont want to bother porting tech that they cant be bothered with on x86 any more to win32 on ARM too.
Silverlight, java and chrome wont effect the battery on your tablet any more than they would on a laptop really.
Its normal windows 8.1, so you can install x86 desktop programs onto whichever drive you want, hence why most software installers specifically ask where to install, just set that to SD card. There is no requirement to use C:/Program Files for win32 applications. That one I thought was common knowledge for all windows users.
Full size USB port would be nice but you wont get full current from it. The battery cannot supply enough current, nothing to do with overall size of the system. The same restriction applies to most windows tablets, android tablets, android phones and more rarely laptops too (although usually old ones).
It really was dumb of dell to not stick a video output somewhere on the device, that almost puts me off the thing entirely.
Click to expand...
Click to collapse
I have Photoshop installed on C - in order to move it to the sd card, can I just copy paste from C/Program files, or do you recommend re-installing to that particular location? Do you think there will be any noticible drop in performance from running application from micro sdhc card?
UBNAS81 said:
I have Photoshop installed on C - in order to move it to the sd card, can I just copy paste from C/Program files, or do you recommend re-installing to that particular location? Do you think there will be any noticible drop in performance from running application from micro sdhc card?
Click to expand...
Click to collapse
My experience with copy/pasting from C to another drive has been varied. Some applications will do it happily (GTA san andreas survived with a just a broken start menu shortcut, libre office died entirely. I would uninstall and reinstall to guarantee it survives the trip.
SD card read/write speeds should be fairly similar to the eMMC storage of the venue anyway. Application performance shouldnt be altered much.
Only other difference would be wear levelling. SSD's in desktop PC's may be slated for reduced lifetimes compared to old style magnetic hard drives, but SD cards are even worse. But they are cheap to replace and thankfully are replaceable unlike the internal storage on the tablet. Nor are they going to die on you next week, some people are regularly using raspberry pi's which boot the full system from SD card without issue (some people have also had them die from wear levelling in the pi after some heavy usage). If a pi can boot and run a full OS from SD, windows can run an application from an external SD card.
Did you tried out any games? i was wondering whether it can run old games like NFS most wanted or underground II.
rkoforever90 said:
Did you tried out any games? i was wondering whether it can run old games like NFS most wanted or underground II.
Click to expand...
Click to collapse
Havent tried yet, focusing on getting software I use most..........I do want some NFS, or something like it on the tablet, especially since EA has completely ignored windows 8 from a Racing / Sports game point of view. There are on screen controlers that can be used
What im wondering, is it worth it to install new games on it - say Tiger Woods 2013, and run on lower settings.........or to just go for say, TW2010, and let it run higher. I assume that because of ATOM graphics limitations on full Windows games it might be better to run older games than the newest.
Maybe i try out Call of Duty Modern Warfare from 3 or 4 years ago instead of trying to run Ghosts on the thing. I dont even know if it would run, but im just wondering if goign with older games would be a better move, any thoughts?
Cant hurt to try old and move newer if you have the games available.
UBNAS81 said:
Havent tried yet, focusing on getting software I use most..........I do want some NFS, or something like it on the tablet, especially since EA has completely ignored windows 8 from a Racing / Sports game point of view. There are on screen controlers that can be used
What im wondering, is it worth it to install new games on it - say Tiger Woods 2013, and run on lower settings.........or to just go for say, TW2010, and let it run higher. I assume that because of ATOM graphics limitations on full Windows games it might be better to run older games than the newest.
Maybe i try out Call of Duty Modern Warfare from 3 or 4 years ago instead of trying to run Ghosts on the thing. I dont even know if it would run, but im just wondering if goign with older games would be a better move, any thoughts?
Click to expand...
Click to collapse
yep.me too thinking of the same ,iam planning to get a baytrail windows 8 tab with 10inch display and a keyboard(not sure know which one to buy though ) .anyway it will be a bit far fetched idea to run new games on a weak processor.but id like to play 1 or 2 old games like NFS underground II or resident evil 4.
How is the Wi-Fi on the VP8? I have the latitude 10 and the Wi-Fi has always seemed sluggish. The 5g always connects at the same speed as the 2.4Ghz band. Glad to hear the bay trail performs well.
Sent from my SAMSUNG-SM-N900A using Tapatalk
ElAguila said:
How is the Wi-Fi on the VP8? I have the latitude 10 and the Wi-Fi has always seemed sluggish. The 5g always connects at the same speed as the 2.4Ghz band. Glad to hear the bay trail performs well.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
You do have a 5ghz router right?
Yep and a 5Ghz extender as well. My phone will connect to either of the 5g connections at least 150mb. But not so for the latitude. I am hoping the VP8 would connect faster. It will be here tomorrow.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I have an old Linksys G router at home, that desperately needs replacing, but just haven't gotten around to it. It hasn't given me any issues with streaming media, so I just haven't been motivated, but I am really looking to boost my home wifi speeds with one of the routers that can has USB media streaming capability. That being said, my DV8P has had no issues with WIFI. My Surface RT (which I am selling), had so many issues with limited wifi. No issues with this device so far.
Just came across this video...........http://www.youtube.com/watch?v=jPPY4m8iY0k&feature=youtu.be
full desktop computer in 8" tablet with USB 3.0 docking station. I will be buying one of these asap.
UBNAS81 said:
Just came across this video...........http://www.youtube.com/watch?v=jPPY4m8iY0k&feature=youtu.be
full desktop computer in 8" tablet with USB 3.0 docking station. I will be buying one of these asap.
Click to expand...
Click to collapse
Well not really...
It is plugged into a SINGLE micro USB 2.0 socket.. So you can NEVER get USB3.0 speed and if you use some monitors with the Pluggable, i doubt the data transfer rates will be high (and i am talking about USB 2.0 speed and not USB 3.0).
thE_29 said:
Well not really...
It is plugged into a SINGLE micro USB 2.0 socket.. So you can NEVER get USB3.0 speed and if you use some monitors with the Pluggable, i doubt the data transfer rates will be high (and i am talking about USB 2.0 speed and not USB 3.0).
Click to expand...
Click to collapse
The micro USB is USB3.0
SixSixSevenSeven said:
The micro USB is USB3.0
Click to expand...
Click to collapse
... And who said this? The Pluggable Guys?
The only thing, which i really trust would be the Dell specs OR if a Owner would present us some speed-tests or details from the Device-Manager in WIN8.1:
http://www.dell.com/us/p/dell-venue-8-pro/pd?oc=fncwv8p01h&model_id=dell-venue-8-pro
"Ports & Connectors
1 x Micro-AB USB2.0 (for trickle charging and data transfer)
1 x Headphone and microphone combojack
1 x 3FF micro-SIM slot (coming soon, optional with WWAN configuration)"
It is not that I would be unhappy about USB 3.0, but it is just USB 2.0..
Edit: The Dell Venue Pro 11!! has USB 3.0.. Not the 8"
Those of you with GTX 600/700 series GPUs in your desktops might be interested in Limelight. Limelight is a 3rd party client for Nvidia's GameStream protocol (same software the Nvidia Shield uses). We've used the Ouya as one of our main test platforms and it works very well (with hardware accelerated H.264 decoding) as of the latest update. Tegra 3's H.264 decoder is very good, and can even handle 1080p60 (although the quality is bad for now due to issues with Nvidia's encoding profile on the PC side)
Over Ethernet, it streams 1080p30 or 720p60 flawlessly with low input latency.
Depending on your router and the location of your Ouya, 720p30 (or higher) over WiFi may also work.
The Ouya controller is fully supported, along with the Xbox 360 and PS3 controllers. The Ouya controller's touchpad works for controlling the mouse while streaming. The main problem with the Ouya controller is the lack of a Start and Back button (like the Shield/Xbox/PS3). The Ouya button is mapped to Start but it seems to work inconsistently. PS3 and Xbox 360 controllers are recommended if you need those buttons.
Right now, you'll have to sideload this app but we could put it on the Ouya store if people like it.
The download link is in the main post on the Shield forum: http://forum.xda-developers.com/showthread.php?t=2505510
Hopefully you all enjoy it. Feel free to post Ouya-specific issues here or general issues on the main thread.
Very cool... Thanks for posting!
Have 3 Ouya's all able to stream 1080p 30fps. Pretty darn playable. Artifacting is the only issue I have with these and the ouya's but as cgutman said that is more of problems on the host machine encoding. Defiantly enjoying this. Well done sir.
I do have a problem streaming from Galaxy SII, but thats the only device so far that was not able to stream from my GTX 770.
Hi! First time poster, I think.
So I have this... Probably tedious idea. But I've read up about the hardware and, while I haven't worked extensively with arm assembly before I have on other systems. The intel 8051, gameboy and x86. Oh. And also I really, really like to learn about low level stuff.
I am aware of the unpracticality of this setup, but I'd like to have something to tinker around with, see if I can do something interesting with it. Would be cool to se how good a NES, SNES or N64 emulator could get.
Anyway, I have a few questions. Any help/answers would be appreciated:
1. After some light research it seems like it has a VideoCore IV gpu, VC 4 seem to have support for resolutions up to 1080p, and have a limited instruction set but it's still enough that some applications (in theory) could run on the cores of this GPU. Is this correct? Also does it have 4 cores?
2. How can I extract specific parts of the hardware drivers from the stock rom? In this case I'd like... you know, most of 'em that are specific to the hardware, at least as a reference point. So screen, touch, bluetooth, usb controller, buttons, wifi, speakers, thermal, gyro, sdcard interface, you get the picture.
3. How is cpu and gpu clock speed controlled by the kernel normaly? How is it capped/overclocked?
4. How does a general micro usb type b to hdmi adapter connect the wires? What is the theoretical highest resolution that would be stramable through such a adapter?
5. How exactly is the hdmi protocol defined? What signals goes where at what time?
Edit: The resolution depends on the version of the adapter, with support for up to 1080p. So if anything is the bottleneck for this part it'll be that the cpu doesn't have enough time processing the writes. Also depending on the version it's either "frame" dependant or "packet" dependant, if I understand correctly packets are used to signal when certain bits of information get's transmitted, thus making the window for when the signal can arrive wider.