Related
USB Host Diagnostics determines your device's USB host capabilities.
USB host is a very powerful feature of recent Android based smartphones and tablets, but on many firmwares (both stock and custom) the feature is somewhat broken.
For example, at launch the Galaxy Nexus told all the apps and the Market that it supported USB host, but USB host did not actually work (this was fixed in the Android 4.0.2 update). This broke several apps.
That is just one example of many. There are even cases where OEMs advertise USB host support, but the device does not support it at all. It appears as if USB host support isn't tested by Google or the OEMs when they push out new firmwares and devices at all.
As we cannot depend on Google or the OEMs to correctly provide information regarding USB host support, and the Android framework will regularly lie about it to both the Market as well as Android apps, this application was created so you can test your device's USB host capabilities for yourself.
If you allow it, the app will also submit your results to my website, so together we can create a complete database of devices and firmwares and their USB host support.
This tool may also come in handy for those porting firmwares.
Requirements:
- Android 2.3.1 or newer
- (Optional) Root
- USB OTG cable (unless your device has a fullsize USB port)
- USB memory stick, or another USB device to test the connection with
The result database is available here:
http://usbhost.chainfire.eu/
The download can be found on Market here:
http://pkg.to/eu.chainfire.usbhostdiagnostics
It is also attached: DO NOT REDISTRIBUTE
(v1.2: 9284)
Changelog for v1.3:
- Detects some common issues with firmwares that can cause apps to be unable to use USB host, and if you are rooted, offers to (try to) fix the problem
- Gives you a unique code that can be used to locate your result, if uploaded to server
- Added option to follow me
- Fixed some more crashes
- Disabled rooted API for Jelly Bean and newer
- API 14 and higher get Holo look now
FC on Samsung Note
cmloo said:
FC on Samsung Note
Click to expand...
Click to collapse
Should be fixed now
FC on GT-I9100 (GB, XWLA4) - detecting the flash stick through the OTG USB cable seems to work on that build
galaxys2 GT-I9100 IML74K samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPB:user/release-keys Custom 2 Yes Yes Yes Yes Yes Yes Yes Yes Full
USB Sticks fail to detect the only thing I can get working is your DSLR application.
Northern-Loop said:
galaxys2 GT-I9100 IML74K samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPB:user/release-keys Custom 2 Yes Yes Yes Yes Yes Yes Yes Yes Full
USB Sticks fail to detect the only thing I can get working is your DSLR application.
Click to expand...
Click to collapse
Try my StickMount app from the Market, it's actually for the G.Nexus. Your build just doesn't have automounting and such enabled... doesn't mean USB host isn't working
FCs in 9100 XWKK5 (CFroot kernel XWKK5)
http://pastebin.com/kVENXkx1
Chainfire said:
Try my StickMount app from the Market, it's actually for the G.Nexus. Your build just doesn't have automounting and such enabled... doesn't mean USB host isn't working
Click to expand...
Click to collapse
Sweet that works!! Detects FAT32 SD cards but didnt detect NTFS USB stick.
Is that something the CM9 devs can change to enable it by default?
Northern-Loop said:
Sweet that works!! Detects FAT32 SD cards but didnt detect NTFS USB stick.
Is that something the CM9 devs can change to enable it by default?
Click to expand...
Click to collapse
For NTFS the right module has to be loaded... ntfs-3g, from the top of my head. Automounting should also be fixable, several devices do it, but I have no idea where it would be configured.
OK sent stats
Huge thanks for the Stick mount app
Now I have pen drive support on cm9 sgs2
Sent from my GT-I9100 using Tapatalk
No on all device detection checks on galaxys2 on CM9 alpha, the rest were fine.
Nice job with the app works nice on xoom
installation fails on rooted Samsung GT-S5360 (galaxy Y).
great APK, anyhow !
no usb support on tbolt running eternity latest nightly
Great utility and it works great to jump start DSLR controller on ISC.
Cheers, gonna provide results soon. Any chance for a similar app checking for MHL (USB-to-HDMI) compatibility? Thanks anyway!
I noticed that some docks for Xperia phones have a full-size USB port that they say is for USB accessories. The dock with my Xperia PLAY 4G (R800at) only passes microUSB and audio, but I'll get the adapter and try anyway. With built-in gaming controls, I doubt I'll *need* USB host support anytime soon, but it will be nice to know!
So desire HD no this functionality not eaven app can fix this?
wanna know what HTC said about this?
any chance that xbox360 controller could work ? or usb mouse >?
USB OTG Helper App with all details here -> http://forum.xda-developers.com/showthread.php?t=1588940
As mentioned by reputed Developer DooMLoRD, this may work on Play also..
Any brave people who could test this and report?
Download:
USB_OTG_Helper.apk
I used it moment ago and it didnt work. Maybe i should change file system on my pendrive (i tried 2 - both on on FAT32). which is the best?
The Play doesn't have OTG kernel drivers, DooMLoRD couldn't get them to work, so this app won't work.
See here for details
I know this. but they need tester so i tried it. doom tried to make it works in his kernel on v1-v3.
Thanks for the info guys..
Maybe some mods can move it to the General section then.
Looks interesting. So lets say the kernel had support for us play. Would this mean we could use a usb gamepad? My question is, some devices I know only work if you have a powered dongle and wireless battery device, since from what I read, most devices dont output power from its usb port.
Mysticales said:
Looks interesting. So lets say the kernel had support for us play. Would this mean we could use a usb gamepad? My question is, some devices I know only work if you have a powered dongle and wireless battery device, since from what I read, most devices dont output power from its usb port.
Click to expand...
Click to collapse
If the kernel had support, then yes we could use USB mouse/keyboard and usb drives. Unfortunately, this app uses DooMLoRD's kernel modules for the Arc and he wasn't able to get them to work on the Play
I'd love to see these working though
Question, I know with cifs manager, it has a way to load modules using insmod. So it didnt have to be in the kernel itself. Couldnt something like that work here too?
Mysticales said:
Question, I know with cifs manager, it has a way to load modules using insmod. So it didnt have to be in the kernel itself. Couldnt something like that work here too?
Click to expand...
Click to collapse
All modules work like that, but they are compiled with the kernel, so need to match.
Is there not cifs modules for the Play?
The play has cifs. (Yay) but my Streak 7.. on Honeycomb.. still wanting one compiled for that.. Thats the one I REALLY need it. Dock + cifs = Win video watching from NAS!
But yea, what I am saying is, if someone could compile a play one, we could just insmod load it without waiting for a rom dev to put it in their builds.
2.2 released!
In the news!
Current features:
Based on Asus 9.2.1.27 WW kernelsources
Backported all Linux 3.2 USB LAN drivers (bandwidth up to 250 MBit/s! tested with a SMSC LAN7500)
ISO9660 (+Joilet), UDF, FAT12 and Apple HFS file system support (USB CD\DVD access! See notes)
Voodoo Sound support!
Turned a few unneeded kernel features off and compiled with Linaro GCC, it's smaller and boots quite a bit faster than other kernels!
Installable using your favorite recovery (tested on CWM v6.0.1.4 v2)
New versions of Tegra 2 codecs for ICS based ROMs (will be provided within a separate installable .zip)
Kernel manager application to manage loaded drivers and file system modules!
Supports almost all current ICS and JB ROMs
Compatible with:
[ICS] Asus official firmware (with root)
[ICS] Android Revolution HD
[ICS] Energy™
[ICS] Revolver
[JB] LiquidSmooth
[JB] RaymanFX's CM10
[JB] ParanoidAndroid:CM10 Hybrid
If you tested this with any other unlisted ROM, please drop some feedback!
Note 1: Some USB devices may need additional power, if so, get a Y cable from eBay so you can power a USB device using a external USB power source
Note 2: External optical drivers and floppy drives will not be mounted automatically, as Android doesn't officially support them
Note 3: CSS protected DVDs are not supported (e.g. Retail movies), due to Linux kernel limitations
Note 4: NTFS is not supported 'out of the box', please use Paragon driver from Google Play
Downloads:
https://www.dropbox.com/sh/gxi0gsl0tdfapgi/Ja19Exs4Sz
(PLEASE install Busybox 1.20.2 using one of the installer apps from Google Play, it is needed for the Kernelmanager application to function properly)
Source:
https://github.com/sander-ashwin/tf101-allinone-kernel
Please report if something does not work!!
Mounting optical drives:
1: First make sure your device is proper rooted (the "mount" command we'll use needs root)
2: Install Android Terminal Emulator from Google Play and open it
3: Type "su" and press enter, you should be asked if you would like to give root access, say Yes
4: Make a mountpoint directory, e.g. "mkdir /Removable/opticaldrive"
5: Mount your optical drive (make sure it gets enough power and something is inserted in the drive) using this command: "busybox mount /dev/block/sr0 /Removable/opticaldrive"
6: You're done! If you inserted a DVD movie, you might want to install Wondershare player or some other player that is capable of playing DVDs with menus
7: If you encounter any difficulties, please reply on this thread or send me a message
Connecting your TF101 to wired ethernet:
1: Buy a TF101 USB Host connector if you don't already have one (they are very cheap online, around 12-15 dollars)
2: Connect the adapter to your TF101, plug in your USB ethernet adapter
3: Android will display a message in the lower right corner of the screen that an ethernet adapter has been connected
4: Connect the LAN cable
5: Android will display a message that your device is connected using DHCP, you can now use internet using LAN
6: If you require manual IP settings, please go to Android's settings, there you can set manual IP or DHCP (OPTIONAL STEP)
Thanks to:
RaymanFX - for inspiring me with his own kernel, and for porting CM10
Asus - for making a pretty good device
prendomiao - for beta testing
Changelog
v1.0:
First release!
v1.1:
Removed some more junk from kernel
Now actually added new filesystem drivers!
v1.2:
Backport of Linux 3.6 I2C core
A little more cleanup of unneeded features
v1.3:
Backported all Linux 3.2 USB LAN drivers
Kernel now includes support for Voodoo Sound!
v1.4:
I2C fixes + Tegra I2C driver ported from kernel 3.6
Tweaked I2C timeout, hopefully our touchscreen won't lag anymore
(this may fix the problem that the touchscreen sometimes doesn't respond for a second, because of an I2C timeout)
v2.0:
Fixed sound
Now compiled using latest Linaro GCC 4.7.2 compiler
New kernel manager application to manage loaded drivers! You're in control, so the kernel doesn't load unneeded modules anymore!
Reverted I2C changes, as they didn't really help
v2.1:
Now compatible with ROMs based on RaymanFX's CM10
Updated BCMDHD WLAN driver for CM10 kernel
A little cleanup to synchronise both ICS and CM10 versions
Updated Linaro compiler to 2012.10
v2.2:
Added some new releases for more compatibility
i tried it. there is a little change, it is a bit speedly... i don't tried videos... but it is good good work
Thank you! Hope videos will play better as Tegra 2 is really picky with HD videos.
I'm now writing a tutorial for mounting optical discs, fortunately it's not really difficult.
but drivers must support them
Well, I included them already They are in your device if you still have my kernel installed.
But Android doesn't support automounting optical drives, so we have to mount the optical disc ourselves, until someone writes an app to do it (automatically).
EDIT: please install v1.1 if you would like to use your optical drive, as I forgot to include the drivers while compiling v1.0
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
poppajules said:
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Click to expand...
Click to collapse
sainthout said:
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
Click to expand...
Click to collapse
To avoid SoDs, you need to set the lower voltage higher.
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
K900 said:
To avoid SoDs, you need to set the lower voltage higher.
Click to expand...
Click to collapse
sainthout said:
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
Click to expand...
Click to collapse
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
do you make it for jb please ?? we need it
Good to hear that the kernel works so far, hope it won't SoD.
I don't have the dock, the SoD's are just random it seems.
I'm also not working on overclocking anymore, too much files are involved which make it difficult to understand and fix.
It's also a pretty big risk, you could burn your CPU or GPU if using wrong values or something like that.
I'll leave the stock voltages and stock frequencies.
I'm now trying to fix the touchscreen issue that happens after some time. Not many people have the problem, so this won't do anything to other people.
Just updating the Linux I2C core to new 3.6 and backporting some newer touchscreen drivers.
Maybe I can also include some newer USB Ethernet drivers and backport other things.
When I implemented something that's worth trying out, I will put a new kernel version online
poppajules said:
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
Click to expand...
Click to collapse
Different JB ROMs may require different ramdisks, so it will take a little time to get it done properly and stable.
For which JB ROM would you like to use it? I might be able to take a copy of the ROM's kernel's own ramdisk and combine it with my kernel
I'm also thinking into making one for RaymanFX's new LiquidSmooth ROM, anyone interested?
prendomiao said:
do you make it for jb please ?? we need it
Click to expand...
Click to collapse
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Hi, does Android display a notification that you connected an USB Ethernet device?
And for which ROM are you trying?
mazimo said:
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Click to expand...
Click to collapse
USB Ethernet works on Android 2.3 with icon...
Ethernet doesn't have anything to do with Android at all.
The Linux kernel provides drivers which will provide Android a universal interface to control Ethernet devices.
When you plug in your USB ethernet device, the kernel will create an eth0 interface (first ethernet device interface).
Android sees that immediately and will show a little message that an ethernet device is detected.
With very old Android versions, Android doesn't really support ethernet, but some kernels do.. in that case ethernet support will be provided automatically without any notifications.
So for example, if Samsung want to support every USB ethernet device, they can, by building support into the Linux kernel.
If Asus doesn't, they don't build any support in the kernel, so the devices won't be recognised and so they will not work.
Except 1 or maybe 2 devices, the original Asus kernel doesn't support ANY Ethernet device, but my kernel supports them all
prendomiao said:
USB Ethernet works on Android 2.3 with icon...
Click to expand...
Click to collapse
new release
Everyone on older versions, please upgrade to v2.0 and try my new kernel manager application!
(Which is also my very first Android application)
Enjoy and please post feedback
If anyone would like to tryout a JB version of my kernel, please pm me!
I ran your 1.0 version, and it's great. I have MASSIVE battery life compared to before. The only issue I have noticed is with wifi reconnecting after deep sleep. It disconnects when screen is off (i verified the settings), but it has a difficult time reconnecting. I usually cycle the wifi toggle and it connects, or I click on my wifi and it connects. It's clearly not a major issue, just a little extra thought when I wake it up.
I read through and no one reported anything like this, so I figured it might be something to keep your eye out for in your later builds. I will install the 2.0 today and give feedback later. Thanks for your hard work!
Kang-aroo V2.0 1/27/2014
WHAT IS IT?
A kernel built from source and released as a daily driver, based on kangs of other proven code which has been known to be both useful and stable. It's name implies that this work is the hard work of others, not mine and I do not claim credit other than updating, merging it, and building it. I do this as a hobby and because I support open source... I have no donate button but will assist you in any way I can. Please just ask any question in the thread no need for PM, even simple questions are ok.
FEATURES:
-OC of CPU up to 1600mhz, Oc of GPU as high as you dare, with trickstermod
-mpdecision from showp1984, and custom ondemand governor (default)
-OTG hostmode and simultaneous charging/fastcharge, switchable
-hotplug DAC support, ALSO NEEDS ROM patch, more info in 3rd post
-Smartmax governor via Oxydo kernel
-ROW,CFQ,DEADLINE, and new BFQ IO scheduler implemenation per mkernal
-firm sleep rtc driver, switchable
-support for most common usb wifi adapters, including rt2800(rt3070), ath9k, rtl8187, rtl8188, rt73, so many i forget, can add any requested if they're not there
-support for all easycap devices with backported drivers from linux 3.4 via linuxtv media git, see 3rd post
-kexec multirom support as a primary and or secondary rom
CREDITS/SOURCES:
*kang of bricked kernel- uses showp1984's custom mpdecision and custom ondemand governor, as well as his implementation of CPU/GPU OC
https://github.com/showp1984/bricked-grouper-3.x
*hotplug dac and otg fastcharge, firm sleep from usbrom
https://www.github.com/mehrvarz
*Kexec support from Tassadar
https://github.com/Tasssadar?tab=repositories
*smartmax governor from sgt. meow
https://github.com/souljaboy11792/oxydo-grouper
*BFQ IO scheduler, all other IO scheds updated
https://github.com/metallice[url]
.../github.com/lostdeveloper/bricked-grouper-3.x
DOWNLOADS
V2 with all modules, SELinux disabled:
http://d-h.st/LZq
V2 minimal install, just tun and cifs modules, SELinux disabled
http://d-h.st/H5U
XDA dev crue has taken the time to make an advanced power manager. With it you can control fixed install, firm sleep, and other kernelnsettings as well as control firm sleep and change the timers for audio focus and deep sleep. I HIGHLY recomend it for this kernel and/or oxydo. Latest version:
http://forum.xda-developers.com/showpost.php?p=49854315&postcount=256&nocache=1&z=9045582152903080
http://forum.xda-developers.com/showpost.php?p=49814629&postcount=242
*****new releases can mean undiscovered issues. If you have any, please let me know so they can be fixed...ENJOY!!!!!!
__________________________
SELinux enabled: I forgot, give me a day or two, Ill get one up. this build still just changes zimage, so works on kitkat or JB4.3.
__________________________
CHANGELOGS:
Kang-aroo V2.0
1/27/2014
bugfix: trickstermod thinks the minimum touchboost freq of 910mhz is the minimum system freq....NOT ANYMORE!
bugfix: tons of dmesg errors from touchboost in franco's interactive governor...governor pulled for now
bugfix: laggy and slow aroma installer which causes black screen from twrp screensaver...GONE!!!
NEW:
-completely replace old GPU OC interface with new one from franco kernel. Users can now set GPU OC right from trickstermod, and go as high as they want.
-cgroups timer slack
-BFQ IO scheduler from mkernal, all others updated
-smartdimmer as implemented by mkernal
Kang-aroo v1.2
1/04/2014
-built wifi back into kernel, no more module
-removed init.d script for hostmode controls, too many issues, use gscript or terminal instead, more info 3rd post
-removed governor option from aroma installer, still can't solve bootloops
-Now has support for all easycap devices, tho improvement is still needed, see 3rd post for more info
-set SELINUX to disabled for now to allow cifs mounting, solve some other issues
-smartmax from oxydo, and interactive for N5 from franco kernel, use trickstermod to change, smartmax is feeling very nice
whats coming:
support for r820t dvb sticks, and hopefully also support atsc tuners and US OTA TV.
*************************************
FULL build with 307 modules:
http://d-h.st/fnw
Kernel and just cifs/tun modules:
http://d-h.st/YHM
*************************************
______old changelogs________________
Kang-aroo kernel 1.1 (12/12/2013)
-Fully updated to 4.4mr1, minus the battery driver changes.
- removed em28xx.ko for now, its not working
- smaller size, will eventually build wifi back in, but its still in module form to save size
-tested with purity rom 12/8 release, wifi is now working on this rom, and should be for all 4.4 roms now.
-Also tested purity rom with ART, reboot was slow, but subsequent reboots are taking about 20 seconds from the multirom boot screen, so all seems normal for kitkat now. ART was switched on BEFORE adding gapps, if it makes a difference.
-still running fine on smoothrom 5.3, which is android 4.3, but I will leave the older build up in case these updates cause any issues for older roms.
- everything else is the same, but DAC hotplug mod on the rom side kind've needs to be done in the source before ROM build to ensure functionality.
______________________________________________
Kang-aroo kernel 1.0:
"Kang"ed from proven sources
*Tested with smoothrom 5.3, android 4.3.1, should work with 4.4, will be updated for 4.4.
*multirom kexec code.....credits to tassadeur.
*CPU OC to 1.6, GPU OC to 484, set during install or with trickstermod
*OTG+fastcharge simultaneously, requires otg y cable for power
*USB DAC support, with hotplug (please read below)
*Usb wifi support: ath9k,rt3070,rt73,rtl8188, others
*over 200 remote controls
*easycap dc60, also included is the em288 module which supports the newest genuine easycap device, but this is a work in progress
*usb webcam as a rear system camera
*media playback after deep sleep, even with externally mounted drives
USB webcam as a "rear" camera:
Add a usb (uvc compatible) webcam as the tablets "rear" camera. The webcam must be plugged in at boot time, but is hotpluggable after that. It will apear to camera apps as a built in rear cam, the only downside to this is that the image will be off 90 degrees if you have the tablet in landscape mode, because it doesnt know that the cam is not really built in. I hope at some point to fix this, but for now i just use my webcam mounted on its side.
http://d-h.st/x5t
Autoplayback after system sleep for mounted drives
This mod is not mine, the source is here:
https://github.com/clarejor/android_packages_apps_Apollo
This is a modded version of apollo that allows autoplayback even from otg mounted drives after waking the tablet from sleep. It is a link to the authors direct download link.
https://docs.google.com/uc?export=download&id=0B8Al2jKfBcTiNUtSdkQtaEZ5MlE
DAC info:
To support DAC hotplug in your rom, you must apply a patch based on code at github.com/jacknorris. this one works for me:
http://forum.xda-developers.com/showpost.php?p=48720356&postcount=89
thanks -crue- !!!!!!
If you need, you can go into the "patches" folder and rename to 4.3,4.4.2, etc. as you need, it still works.
EASYCAP info:
These drivers were added with help from a russian thread which I was using google translate:
http://translate.google.com/transla...l=en&u=http://pccar.ru/showthread.php?t=19390
http://translate.googleusercontent....=17970&usg=ALkJrhiZTqApR8tUiNrNMyIEIk2qBxWobg
But there is easier english info about it here:
http://rootzwiki.com/topic/39717-kernel-module-cm-101-easycap-module/page-35
*the script I use for loading the modules is here:
http://d-h.st/z2g
it needs to be pushed to system/etc/init.d AND have the right permissions (RWX,R-X,R-X I think) ....... or just use it to see which modules need to be insmodded.
*and the program I used to view the device is here:
http://rghost.net/51160971
keep in mind, I tested with the cheapest one on fleabay, 5 bucks shipped and it works, but when I tested with my real EZCAP the picture is much better. see below for the results...and...read the whole thread I linked. the guy is workin like crazy on it, and it will only get better I think.
is multirom 'kexec' support included?....thx
Hi
This Kernel looks the business.
Can u tell me though is it overclock-able?
bonzer2u said:
is multirom 'kexec' support included?....thx
Click to expand...
Click to collapse
yes, I forgot, the proven tassador code is there....it DOES multiboot.
Sharpy1964 said:
Hi
This Kernel looks the business.
Can u tell me though is it overclock-able?
Click to expand...
Click to collapse
yes, CPU up to 1.6, and GPU to 484, options can be set with aroma installer, or later on with trickstermod.
I'm going to use the USB otg charging and DAC bits. Thanks.
Sent from my Nexus 7 using Tapatalk
sgt. meow said:
I'm going to use the USB otg charging and DAC bits. Thanks.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
excellent. I want to use your d2w code......gotta work out some wakelock issues tho. If you look at the main commit.....you'll see its not that many files for the DAC stuff. where you need to pay attention is the defconfig...... as usbhost is actually NOT set.
Also, there are about six or seven commits to bricked kernel from Timur mehrvarz from a few months back. All of them were cherry picked in order, and you'll need those cherrypicks first before you pick mine. just ask if you have issues..... more than happy to help.
I'm working on a sysfs interface system to make s2w completely configurable. I plan to work on touchwake as well later. I'll start tomorrow.
Sent from my Nexus 7 using Tapatalk
Mate, I added the USB hostmode patches, but now USB OTG doesn't work. I'm a complete noob to this (only adding it because of user request); any help is appreciated.
The same otg cable is used (not y cable). It worked before, but now it's borked.
Never mind. Turns out I just had to disable Fixed Install in sysfs.
sgt. meow said:
Mate, I added the USB hostmode patches, but now USB OTG doesn't work. I'm a complete noob to this (only adding it because of user request); any help is appreciated.
The same otg cable is used (not y cable). It worked before, but now it's borked.
Never mind. Turns out I just had to disable Fixed Install in sysfs.
Click to expand...
Click to collapse
Yea......I meant to tell you......you can change the default in the source. Also, as I'm sure you know, you can look at the init.d script I made for making changes stick on reboot. Of course, this is really just: 'echo "1" > /sysfs/usbhost/usbhost_fixed_install'
It's better to have found out on my own though. Thanks for all your help.
Thank you
Wow Increadible! Please keep updating it
SlavPala4a said:
Wow Increadible! Please keep updating it
Click to expand...
Click to collapse
no prob, 4.4 ipv6 updates coming soon, the "battery" driver updates I'll prolly skip.
So i've just downloaded & installed this kernel. Mainly for it's USB DAC feature...dying to have this since 4.2.2 kernels.
Sadly, not working out for me as audio is still routed to internal speakers, plugged in DAC before boot.
Wifi too cannot be turned on. Stuck at 'turning wifi on'
Came from franco r76 on purity 4.4 (2/12/13 build)
It's recognized on boot tho, and doesnt crash the table when hotplugging.
Also, i did not install the 'hotplug mod', i was testing this without it.
[ 4.442281] usb 2-1: New USB device found, idVendor=08bb, idProduct=2704
[ 4.442604] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.442779] usb 2-1: Product: USB Audio DAC
[ 4.443084] usb 2-1: Manufacturer: Burr-Brown from TI
[
Click to expand...
Click to collapse
and here's the whole last_kmsg attached...
andrew9292 said:
So i've just downloaded & installed this kernel. Mainly for it's USB DAC feature...dying to have this since 4.2.2 kernels.
Sadly, not working out for me as audio is still routed to internal speakers, plugged in DAC before boot.
Wifi too cannot be turned on. Stuck at 'turning wifi on'
Came from franco r76 on purity 4.4 (2/12/13 build)
It's recognized on boot tho, and doesnt crash the table when hotplugging.
Also, i did not install the 'hotplug mod', i was testing this without it.
and here's the whole last_kmsg attached...
Click to expand...
Click to collapse
wifi is in module form....to help with size of kernel. ill look at log and see if it was loaded. for usb dac hotplug, the rom must also be modded via the link in op. or if u build roms, you can go to jacknorris github, and pull those changes into your source. must do both.... but ill look at log and see whats goin on. only got phone right now. forgot to mention......the aroma installer doesnt wipe /system/etc, so if u got other kernel init.d scripts, they need to be removed. if you have any wifi init.d scripts, they need to occur AFTER the wifi module loads, so jusr rename them with a 90 infront. get back to you.
ok....looked at log from phone, unless I missed it I didnt see wifi module load, make sure the init.d script is there. the dac is there....and burr brown is a nice amp, use them in my guitar effects, not ssure if rom can pass audio to dac with no mods, could be wrong. the jacknorris mod works well, and the "wiredaccessorymanager.java" or whatever hasnt changed, so you should be able to do this on upto 4.4, but ive only tried smoothrom 5.3. which is android 4.3.1.
redeyedjedi said:
wifi is in module form....to help with size of kernel. ill look at log and see if it was loaded. for usb dac hotplug, the rom must also be modded via the link in op. or if u build roms, you can go to jacknorris github, and pull those changes into your source. must do both.... but ill look at log and see whats goin on. only got phone right now. forgot to mention......the aroma installer doesnt wipe /system/etc, so if u got other kernel init.d scripts, they need to be removed. if you have any wifi init.d scripts, they need to occur AFTER the wifi module loads, so jusr rename them with a 90 infront. get back to you.
ok....looked at log from phone, unless I missed it I didnt see wifi module load, make sure the init.d script is there. the dac is there....and burr brown is a nice amp, use them in my guitar effects, not ssure if rom can pass audio to dac with no mods, could be wrong. the jacknorris mod works well, and the "wiredaccessorymanager.java" or whatever hasnt changed, so you should be able to do this on upto 4.4, but ive only tried smoothrom 5.3. which is android 4.3.1.
Click to expand...
Click to collapse
Nope, no leftover init.d scripts except a 99supersu script.
Just did a clean flash with the same rom straight to kangaroo and wifi does not work either.
Cant seem to get the jacknorris patch to work on my Win7 laptop.
ADB problem solved. It was due to ADB.exe and some of it's .dll were outdated for 4.4. Got the new files from the SDK and now ADB works.
But the patcher gives this error: Checking BOOTCLASSPATH: error: Unable to parse shell output
Appearantly the patcher has to be modified for 4.4: http://rootzwiki.com/topic/37176-mod-usb-audio-support/page-4
Also, anyone has a working 4.4 rom with this kernel combination that works internal wifi and usb dac?
Appearantly folks at CM11 got the dac bit goin for N7-2013 and N5. Not on our 2012 though. Wonder if it was a kernel change or rom framework or both... http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/3615
Support for USB Audio, 3rd most starred issue on aosp: http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
For those wondering what's this about:
What is a USB DAC?
A USB Digital-to-Analogue Converter is a plug in USB device that converts digital bitstreams into analogue audio wave to be transmitted in the cables leading up to your headphones, speakers etc. It's a soundcard so to speak, but specializes higher quality audio output only and wont have any recording capabilites.
Why?
The DAC chip (that conversion chip) is usually of superior quality to that embedden internally on your motherboard or device. In layman terms, it converts more accurately, over a wider ranger of frequencies. Being an external device, it would be less suspectible to internal electronic noises and advance DACs have noise, jitter reduction methods, sometimes even its own clocksource. Different DACs have different sound signatures for different ears and taste.
Another advantage is that users may not need to alter the audio in the digital domain (EQ, Compressors, Volume, Effects) which induce losses due to poorly designed algorithms and the nature of 16/24-bit consumer audio. Most music today is processed in a 64bit domain over a very high sample rate, from the first souce to it's final output.
Why manufacturers dont slap one of these on the boards/device?
Simple business/economics, the Nexus 7 2012 sold 7 million devices.
A better chip may cost an extra dollar or lesser since they purchase in bulk.
Example, $1 increased cost x 7 million devices = $7 million lesser in profits!
Where is Android on USB audio then?
Usually not available on Nexus aka google-high-involment devices. Some vendors like Samsung, LG, HTC take it further and has usb audio support at least. It can be further improved with bit-perfect streams, higher sample rate with 64-bit float PCM decoding and effect processing, exlusive application access, low latency framework, DSD etc.
Comparision?
I know Windows, Linux, OSX has it, used it before.
iOS has it too. Ehem, my ipad1 could do it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andrew9292 said:
Nope, no leftover init.d scripts except a 99supersu script.
Just did a clean flash with the same rom straight to kangaroo and wifi does not work either.
Cant seem to get the jacknorris patch to work on my Win7 laptop.
ADB problem solved. It was due to ADB.exe and some of it's .dll were outdated for 4.4. Got the new files from the SDK and now ADB works.
But the patcher gives this error: Checking BOOTCLASSPATH: error: Unable to parse shell output
Appearantly the patcher has to be modified for 4.4: http://rootzwiki.com/topic/37176-mod-usb-audio-support/page-4
Also, anyone has a working 4.4 rom with this kernel combination that works internal wifi and usb dac?
Appearantly folks at CM11 got the dac bit goin for N7-2013 and N5. Not on our 2012 though. Wonder if it was a kernel change or rom framework or both... http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/3615
Support for USB Audio, 3rd most starred issue on aosp: http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
For those wondering what's this about:
What is a USB DAC?
A USB Digital-to-Analogue Converter is a plug in USB device that converts digital bitstreams into analogue audio wave to be transmitted in the cables leading up to your headphones, speakers etc. It's a soundcard so to speak, but specializes higher quality audio output only and wont have any recording capabilites.
Why?
The DAC chip (that conversion chip) is usually of superior quality to that embedden internally on your motherboard or device. In layman terms, it converts more accurately, over a wider ranger of frequencies. Being an external device, it would be less suspectible to internal electronic noises and advance DACs have noise, jitter reduction methods, sometimes even its own clocksource. Different DACs have different sound signatures for different ears and taste.
Another advantage is that users may not need to alter the audio in the digital domain (EQ, Compressors, Volume, Effects) which induce losses due to poorly designed algorithms and the nature of 16/24-bit consumer audio. Most music today is processed in a 64bit domain over a very high sample rate, from the first souce to it's final output.
Why manufacturers dont slap one of these on the boards/device?
Simple business/economics, the Nexus 7 2012 sold 7 million devices.
A better chip may cost an extra dollar or lesser since they purchase in bulk.
Example, $1 increased cost x 7 million devices = $7 million lesser in profits!
Where is Android on USB audio then?
Usually not available on Nexus aka google-high-involment devices. Some vendors like Samsung, LG, HTC take it further and has usb audio support at least. It can be further improved with bit-perfect streams, higher sample rate with 64-bit float PCM decoding and effect processing, exlusive application access, low latency framework, DSD etc.
Comparision?
I know Windows, Linux, OSX has it, used it before.
iOS has it too. Ehem, my ipad1 could do it.
Click to expand...
Click to collapse
So, the kernel is booting 4.4, but this ROM mod needs to be reworked a little. It seems like a ROM needs to be built with the source manually modified. Its gotta be do-able, I'm just such a fan of tabletui, that I'm not running 4.4. But I'm sure this problem can be figured out. The WiFi thing bugs the **** out of me, haven't had this issue regardless of ROM I've tried......can you look in system/lib/modules and see if "bcmdhd.ko" is there? I will go and see about 4.4 ROM mod.
well, on the same rootzwiki page you linked, there is a guy who says he used that mod on a 4.4, with a modded installer, I see that now. So, the bootclasspath errors need to be corrected, but the mod can still be done. I hate to just tell you to go ask that guy, already done that to a couple of people via PM.... Id like to see this work for everyone. ill wait to see if you found the "bcmdhd.ko" for the wifi issues, but Ill go ahead and look into making the jacknorris mod-installer work for 4.4 roms.
on second thought, the guy got those same errors, but the mod worked anyway....so it seems. See if it worked in spite of your error.
I see there are several custom marshmallow ROMs for the Nvidia Shield Portable. I'm thinking of upgrading as I'm sick of always having to move my apps around and not being able to update them. Adoptable storage solves that issue.
The ones I've found are:
CM: https://forum.xda-developers.com/nv...t/rom-cyanogenmod-12-shield-portable-t3042192
LineageOS: https://forum.xda-developers.com/nvidia-shield/development/rom-lineageos-shield-portable-t3562831
RR: https://forum.xda-developers.com/nvidia-shield/development/resurrection-remix-t3465740
Which of these is the most stable and supported? It appears CM or LineageOS.
Are any shield features supported on these? Such as (in order of importance):
Console mode
Controller
Gamestreaming (using official app, not moonlight)
Gamepad mapper
Thanks!
I'm running CM13 for the same reason, adoptable storage. Controller works but most shield specific stuff does not and other apps are needed. Let me know which one you end up on. Haven't booted mine for a while and thinking of wiping it again.
LineageOS is the continuation of CyanogenMod, I wouldn't use the cm builds anymore. And wow, somehow I missed RR getting released, need to go take a look at it sometime.
As for feature support (should apply to all custom ROMs, but I can't be 100% sure about RR):
Console mode: Yes, works fine.
Controller: Built-in works, wireless does not. Been working on the wireless support for years. I can make them pair and work, but there's no user friendly way to do so yet. See the end of the shield apps thread in the tablet section for more info.
Game stream official: No, does not work. As far as I can tell, support for the tegra 4 was completely removed from the M version of the shield hub streaming. As such, I cannot fix it. Moonlight does work, I am told. Don't use streaming myself as I don't have windows.
Gamepad mapper: This is virtually impossible to port from stock. Tincore is the alternative, but is a pain to set up.
Thanks for the informative response! Sounds like LineageOS is the way to go. If I decide I'm going to keep my portable I'll probably flash LineageOS (I'm debating selling it as I bought a GPD Win, but it's found a use as an Android TV system for my wife... so I'm debating keeping it or selling it and buying a cheap chinese system).
I've posted an atv build or two in my cm thread. Working on making atv work better in lineage right now. Been having troubles the last couple weeks, but have a couple more devs looking at the problems now. Once those settle down, I'll run another build for roth. It worked really well for the short time I had it installed. Might even end up my normal install once the kinks get worked out. But if you're interested in atv, I am working on it. If you want a really nice dedicated atv system, the shield android tv is amazing. For kodi, retroarch, etc, etc. A bit pricy, but totally worth it for the features.
Thanks, I'll look into it, but it's just a kitchen TV machine. All she really uses it for is CrunchyRoll and YouTube (hence why a cheap chinese system would be perfect).
Steel01 said:
LineageOS is the continuation of CyanogenMod, I wouldn't use the cm builds anymore. And wow, somehow I missed RR getting released, need to go take a look at it sometime.
As for feature support (should apply to all custom ROMs, but I can't be 100% sure about RR):
Console mode: Yes, works fine.
Controller: Built-in works, wireless does not. Been working on the wireless support for years. I can make them pair and work, but there's no user friendly way to do so yet. See the end of the shield apps thread in the tablet section for more info.
Game stream official: No, does not work. As far as I can tell, support for the tegra 4 was completely removed from the M version of the shield hub streaming. As such, I cannot fix it. Moonlight does work, I am told. Don't use streaming myself as I don't have windows.
Gamepad mapper: This is virtually impossible to port from stock. Tincore is the alternative, but is a pain to set up.
Click to expand...
Click to collapse
Thank you for doing all this work! As you saw based on the other threads, I am using LineageOS now. I haven't fully tested everything yet, but so far things are mostly working well.