Related
After Emailing Imate asking various questions on the specs of their up and coming K-Jam they sent me this ....
States Bluetooth as 1.1
It says "Compliant with v1.1" which doesnt rule out the possibility that its 2.0. Also their information is very sketchy... 1.2/2.0 MP camera (for god sakes... which is it?)... and Wireless B/G/E/I compliant (it only appears to be B compliant).
I believe the camera is 1.3Mpixel with some built-in function to interpolate to 2Mpixel.
The network could be 802.11b/g/e/i compatible and still have a top speed of 11Mbit implemented...
802.11g adds higher speed, shorter preamble and support for the OFDM encoding scheme. So it could support the 802.11g at 11Mbit, preventing the device from dragging older g access points down when connected (Some of the older 802.11g access points fall back to limiting EVERYTHING connected to 802.11b speeds when a 802.11b device connects.)
802.11e just adds Quality Of service support and bursting
802.11i improves the security with 802.1x support and CCMP support
I do agree that the Bluetooth support they list is merely what was certified AT THE TIME that the document was originaly created. We'll have to see what is real when we start getting our hands on it.
Robert Harrold
I can't see how the Wizard will hve BT 2.0 when the Universal doesn't. The Universal is the all singing all dancing device that people pay a premium for. So there is no way the Wizard at the cheaper market will have a better spec IMO.
Also note that according to Microsoft the Wizard has a newer build of WM5 on it than the Universal as well !! See: http://blogs.msdn.com/jasonlan/archive/2005/09/24/473604.aspx#comments
Just tested the link of Firmware 2.4.65 for Gen8 device...
Now currently downloading....
http://update.archos.com/8/gen8/gen8_2.4.65/firmware_archos_android_gen8.aos
Sent from my A101IT using Tapatalk
where did you get it?
On Archos HP still the old one
They updated the change log, but for some unknown reason they did not update the link to download the new version of firmware.
Version 2.4.65 - October 20th, 2011
Internationalization: add Korean translations support
Video: improve SMI subtitle support and provide better subtitle codepage/encoding detection
Applications: increase reactivity of applications constantly updating sound volume without any change in value (e.g. fruit ninja)
A101 accessory: add support for Archos 3G key
A101 accessory: add support for some USB Ethernet adapters (chipsets: RTL8150, ASIX AX88xxx, Davicom DM9601, SMSC LAN75xx, SMSC LAN95xx, NetChip 1080, MosChip MCS7830)
A70 hard drive based devices: fix unit loosing mass storage happening sometimes on recent models
Accelerometer: apply calibration right away without requiring a reboot to take effect
PTP: fix USB host camera support
yes just tried to use the autoupdate - it downloaded it and then while clicking install it told me - its NOT for my device (funny)
well lets try the manual way
I'm currently downloading the firmware, new root package will be released soon
edit: Rooting is available: http://forum.xda-developers.com/showthread.php?p=18786332#post18786332
anyone any idea when these changes/fixes will be implemented in UD? I'm interested in the last one (usb camera)
cheers
b
Finished updating my Archos last night. Haven't really tried if the changes posted in the Archos website has been applied. As of now I have not encounter any problem yet.
Change log for this firmaware can be found in Archos website.
I got the link from Arctablet.com website.
Sent from my A101IT using Tapatalk
Could someone already updated check if the Cinema plugin is included in the new version? Obviously, someone who didn't buy the plugin,
(playing a video with AC3 audio, for example)
Thanks!
"A101 accessory: add support for Archos 3G key"
Is there also a support for A70 by using an USB host adapter? I think the only differnenz in this case is that the A101 has a standart USB port.
No, as the A70 with the std FW only deliveres 100mA, which definately is not enough for the dongle.
enteo said:
Could someone already updated check if the Cinema plugin is included in the new version? Obviously, someone who didn't buy the plugin,
(playing a video with AC3 audio, for example)
Thanks!
Click to expand...
Click to collapse
Just checked the update on my 2 day old 101 and it still required the cinema plugin...........I cant believe that I have to pay for a plugin, on what is now old technology, with the release of gen9. Cant believe that you should have to buy a plugin at all for what is a basic use of the 101, playing video files. If i knew before buying I wonder if I would have bought it at all.
Stop wining, this is known since the beginning and we have more than enough discussions about that.
It is your own fault that you didn't read that info that is clearly stated on the box and on the archos site.
This firmware update is okay but I no longer have my OpenAOS multi-boot menu. I reflashed the kernels after I did the root for this firmware and the menu.lst file is still present but it just boots up with the Archos screen and then goes to my Froyo screen.
Would someone please confirm how the 2.4.65 fw compares with the stability and performance of 2.1.8 fw.
Thanks in advance.
70IT 8G
2.1.8 fw
zeam 3.1.5
you can use a dongle with an RJ45 with a cable usb host throughout the Gen8
see photos
http://www.jbmm.fr/2011/11/gen-8-archos-nous-cache-des-choses/
Hi,
WebTop (with full ubuntu mod) works fine with Trendnet TU2-ET100 (asix chipset).
I have just added these 2 lines in "/osh/etc/network/interfaces" for DHCP autoconfiguration :
auto usbeth0
iface usbeth0 inet dhcp
Doum
Nice to know. Ethernet might come in handy for a lot of people docking as their PCs.
I guess any other USB ethernet card that works with a normal Linux PC should work here.
Hello there,
First I would like to say that I'm glad that in the last few weeks i finally managed to let my heavy 15.4' 9 cell Dell Laptop on the Office and bring home the Atrix + LapDock everyday including weekends and holidays
I have what i need on my LapDock + FullUbuntu: gedit, gnome-terminal, OpenOffice, PDF readers, Psi+ (jabber client with PGP Encryption), GNUPG, Mumble Voice Chat, Firefox (with client SSL certificates ) and OpenVPN.
Everything else, like e-mail, music and video players i'll prefer running on the Android
So, i want to buy this USB -> Ethernet adapter to make it even better!
I thought buying the TrendNet but it seems somewhat bigger than other adapters that use the same "chipset" (ASIC). I also find those adapters cheaper than the TrendNet one:
http://www.ebay.com/dsc/i.html?_nkw...=0&_trksid=p3286.c0.m270.l1313&LH_TitleDesc=1
I think i will buy this one:
http://www.ebay.com/itm/NIB-REAL-US...ltDomain_0&hash=item56471dfaff#ht_2136wt_1026
It seems great but now i'm not entirely sure what's the chipset on the TrendNet: AX88772A or AX88772B?
The one i'm buying uses the AX88772B.
The difference seems to be very small, the drivers seems to be the same and the "B" version supports checksum offloading and it's intended for Low Power consumption. Here's the detailed specs of both chips:
http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=97;71;101
http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=105;71;101
So, what do you guys think?
Did you get it yet? If you did, how does it work?
blingmaster said:
Did you get it yet? If you did, how does it work?
Click to expand...
Click to collapse
I bought this one from Deal Extreme:
http://www.dealextreme.com/p/usb-2-0-10-100mbps-rj45-lan-ethernet-network-adapter-dongle-34691
It's really cheap, small and uses the AX88772B chipset.
But i'm not able to test yet, simply because it's not here yet
I bought using standard Air Mail that takes something like 20 days to get here in Brazil... And when it does arrive here it's going to take 10 more days (or even more) for Brazilian (Fuc***) Customs to release it for Brazilian Postal Service to finally deliver it... This sucks.
But well, i promise that as soon as I get it, i will test and put the results here.
Merry Christmas!
Post resurrection alert!
I tried this with an Airlink 101 today. I didn't add the extra lines listed in the OP, but I did start the dhcp client manually and it got an address and webtop was happy. Does anyone know if the android portion of the phone is able to use the wired Ethernet connection? From my quick test it didn't seem like it did.
I have a much slimmer Cisco USB to Ethernet adapter that I plan to try. I used the Airlink because it was lying around on my desk doing nothing.
And with all the webtop talk starting up, this may be of interest to others.
AX88772B not working
Well, mine did not work
I bougth this one from DealExtreme:
http://www.dealextreme.com/p/usb-2-0...r-dongle-34691
As i said before, it uses the AX88772B chipset.
I have confirmed that and installed the driver for my MacBookPro and it's working just fine.
I have downloaded the drivers from:
http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=105;71;101
It's noticeable that there is also a driver for Android but it's the source code, not the compiled kernel module.
So i think i'll will need to get the Atrix kernel source compile the driver with the headers and prey to work...
Maybe it's something with my ROM... I have updated to the latest Motorola official 2.3.6 build for Brazil.
Could you guys tell me what's the output of these two linux commands, as soon as you plug the USB device ( the last 10 lines or so):
$ dmesg
and
$ lsmod
Victor.
This is awesome.
Can't wait until they bring the webtop to CM7. It was a loss when I upgraded, but the smoothness and capabilities of a CM7 rom are worth the loss of the webtop... for now.
It's good to know that when it get's working again I can use a USB to Ethernet with the Ubuntu mod.
Thanks!
thenicnet said:
Can't wait until they bring the webtop to CM7. It was a loss when I upgraded, but the smoothness and capabilities of a CM7 rom are worth the loss of the webtop... for now.
It's good to know that when it get's working again I can use a USB to Ethernet with the Ubuntu mod.
Thanks!
Click to expand...
Click to collapse
Don't hold ur breath.....cm9 is underway don't think webtop is gonne come yo cm7 but u can always mirror with lapdock
root, make changes, then unroot
Would like to be able to use a usb ethernet adapater on my unaltered Atrix running 2.3.4. If I were to root, make the changes to the two lines and then unroot again, would the changes remain?
In Post 6 above there is mention of the usb ethernet adapter only working under webtop. Is there a way to make it work on the phone itself as well, i.e., for the phone browser / market / email / etc.
Hello.
When it connected to my HDDOck - eth0 not detected. In the webtop (I webtop2sd) lights icon - an unknown usb connection ...
Any advices to solve this issue ..
i have this issue also, connecting usb broadband detects it as cd-rom drive. i have zte mf627 broadband kit. ill attached screens later. dmesg result show port but has no device name.
gradd said:
i have this issue also, connecting usb broadband detects it as cd-rom drive. i have zte mf627 broadband kit. ill attached screens later. dmesg result show port but has no device name.
Click to expand...
Click to collapse
A nearly 2 yr old dead thread just had to be brought back to the surface? esp with your results being the same as the previous member's results?
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?
I have a "Tata Sky HD" Set-top Box and I was about to throw this in garbage but before I want to know what is happening under the hood.
I search on internet and I found nothing except this. I'm noob so sorry for if say something silly.
I found this specifications.
Product : TATA SKY HD
Original Maker : Technicolor
Product Model Number : DSI729TAT
Chipset : STiH237 BHKB B3L
Type : ST40 -32 BIT
Architecture : RISC
RAM : 2GB [ SK Hynix H5TQ2G63FFR H9C
Storage : 1GB [ Spanison ML01G100
Power : 12v DC
Software: busybox 1.18.2 , mtdwrap, uclibc, Linux Kernel 2.6.32.59_stm24_0211, ST drivers: embx.ko, embxmailbox.ko, ics.ko, ics_user.ko, lxload.ko, mme.ko, mme_user.ko, LZO Decompression Library 2.03, Decompression Utility
PORTS : 1 HDMI 1.2/1.3/1.4, 1 USB 2.0, SAT-IN & 2 Audio 1 Video Out , 1 Optical S/PDIF (for Dolby Digital Plus Audio ), 1 Digi Card.
I Found 1 UART PORT Which would be used while extraction of Firmware.
AFTER SOME REASEARCH I FOUND THAT IT HAS SIMILAR TO ARM-CORTEX-A9 AND MALI-400 GPU. (MAYBE I'M WORNG)
IDEA : It has a a Good processor and ram which can run as raspberry-pi os.
so we can repurpose it as a Media Center, Gaming Console, NAS, Smart Home, Small Server or a Mini Computer.
storage is low so we have to add some storage. I'm not sure how this is possible. except swapping the NAND flash Chip.
GOAL 1 : Extract Firmware and Extract Paid Decryption key which is use to verify the sat-in signals. ( a stb which don't required subscription to watch any tv channel )
i think they modified the software which capture the unencrypted signal and if we have a signal receiver then we are good to go. but for big companies wants to earn money so they added these barriers which needs decryption. and if the satellite is sending encrypted signal then we need to find the key. ( i know it's hard that's why we are here. I'll love to hear you thoughts on these)
GOAL 2: Change the Firmware and install Linux.
Goal 3: Find a way to use it as media server with increased storage and add a wireless module for WIFI access.
I'm not sure it is possible or not. but i think its possible. just think about it a small hardware can collect signal from satellite and decrypt the signals in HD with Dolby HD audio. we just need to find a way to access this.
I SHARED MY IDEA AND I DON'T KNOW MUCH ABOUT THESE.
PROBLLY I'M GOING TO ACCESS THIS WITH UART INTERFACE AND TRYING TO ACCESS THE BOOTLOADER.
OR MAYBE DESIGN A CUSTOM KERNAL.
I'M SEARCHING FOR COMPATIBLE FIRMWARE WHICH I CAN MODIFY AS I NEED.
EXTRA : I FOUND A SIMILAR STB WHICH USED IN RUSSIA "NTV PLUS SET TOP BOX" HAS SIMILAR PROPERTIES LIKE TATASKY HD BUT WITH EXTRA I/O PORTS.
THANK YOU. IF YOU HAVE ANY ADDIONAL IDEA THEN I'LL LOVE TO HEAR THAT.
Links Used For Gathering Information
Chipset : https://www.st.com/en/digital-set-top-box-ics/stih237.html
RAM : https://www.electronicsdatasheets.com/manufacturers/sk-hynix/parts/h5tq2g63ffrh9c
OS information : https://www.technicolor.com/node/1899
Storage : https://www.qdatasheet.com/search.jsp?sWord=ML01G100&page=2&op=i
RISC BASED TOOLS AND APPS : https://www.riscosopen.org/content/downloads/common
This is probably the UART. You will most likely get a shell and U-Boot logs provided that it's not fused-off (ST microcontrollers can have debug interfaces fused off during flashing at the manufacturer)
How to find the pinout:
GND will have continuity with metallic parts of the board (heatsinks, HDMI ports, etc)
VCC will measure 1.8-5V DC depending on logic level
RX will not measure very much voltage
TX will go crazy during boot on an oscilliscope.
Try baudrate 115200 8n1
$cronos_ said:
This is probably the UART. You will most likely get a shell and U-Boot logs provided that it's not fused-off (ST microcontrollers can have debug interfaces fused off during flashing at the manufacturer)
View attachment 5877483
How to find the pinout:
GND will have continuity with metallic parts of the board (heatsinks, HDMI ports, etc)
VCC will measure 1.8-5V DC depending on logic level
RX will not measure very much voltage
TX will go crazy during boot on an oscilliscope.
Try baudrate 115200 8n1
Click to expand...
Click to collapse
Well i don't have oscilloscope yet, soon I will try your guide, thanks for guidance. I will try to update upcoming experiments.
dyal96 said:
IDEA : It has a a Good processor and ram which can run as raspberry-pi os.
so we can repurpose it as a Media Center, Gaming Console, NAS, Smart Home, Small Server or a Mini Computer.
storage is low so we have to add some storage. I'm not sure how this is possible. except swapping the NAND flash Chip.
GOAL 1 : Extract Firmware and Extract Paid Decryption key which is use to verify the sat-in signals. ( a stb which don't required subscription to watch any tv channel )
i think they modified the software which capture the unencrypted signal and if we have a signal receiver then we are good to go. but for big companies wants to earn money so they added these barriers which needs decryption. and if the satellite is sending encrypted signal then we need to find the key. ( i know it's hard that's why we are here. I'll love to hear you thoughts on these)
Click to expand...
Click to collapse
I think we can utilize the usb port on the back to add the external storage, as the usb port is used for storing the TV recording (as far as I can recall), and for the uart part, we can also use it for accessing root shell in the initial step, to figure out the operation method and framework.
I don't have any idea about the encryption keys, it would be cool if there's a way for that.
I have the same STB, would love to repurpose the old box, what's your progress on this so far ?
If you have a multimeter, you can check if the pins are for UART, RX voltage would be very low, TX voltage would be fluctuating upon boot, check continuity for GND with any grounded part like the HDMI port shield or the AV port silver port, VCC would be 3.3 or 5 volts