Related
Is there any hack already that will let me to get a video out of the nexus one? If so where can I read more about it?
If not, is anyone working on suck hack? again, where can i get some more info on it?
Thanks, xda!
Search. And the answer is no.
(Technically, you could install Sven Killig's kernel with USB host support and HDMI dongle drivers, make cables, buy USB2HDMI dongle for $100 or so, and then you could have some way of video out. But given the question and the lack of skills to search the forum, I don't think these skills are enough to make such modifications - including the fact that this kernel can't be used for anything else, since it disables normal USB device functionality).
Jack_R1 said:
Search. And the answer is no.
(Technically, you could install Sven Killig's kernel with USB host support and HDMI dongle drivers, make cables, buy USB2HDMI dongle for $100 or so, and then you could have some way of video out. But given the question and the lack of skills to search the forum, I don't think these skills are enough to make such modifications - including the fact that this kernel can't be used for anything else, since it disables normal USB device functionality).
Click to expand...
Click to collapse
I have used the search, I just didn't find the answer, thought to ask maybe someone heard about any news on the topic.
I have seen the usb host hack, and that is what I'm thinking about, but was interested if there were some better options to do it (aka via the 3.5 like the samsung galaxy s does).
So back to my question, is anyone working on anything like that besides the usb host hack aka via the 3.5, or maybe a way to directly use a micro usb to hdmi cable?
I'd have a lot of money if I had $1 for every time it needs to be explained.
There will be no integrated video out of any kind for Nexus. Ever. Because there is no HW for it inside.
kostiak said:
I have used the search, I just didn't find the answer, thought to ask maybe someone heard about any news on the topic.
I have seen the usb host hack, and that is what I'm thinking about, but was interested if there were some better options to do it (aka via the 3.5 like the samsung galaxy s does).
So back to my question, is anyone working on anything like that besides the usb host hack aka via the 3.5, or maybe a way to directly use a micro usb to hdmi cable?
Click to expand...
Click to collapse
You didn't search enough.
The hardware is not there to output video though the 3.5mm jack, nor the usb port.
Hi all, I did a search under this forum and do not actually found any info.
Actually, many older Android phone/device do come with USB Host (OTG) function, hardware or software, with hacks or officials,
Mod/Hacks:
MOTO droid, N1, ZTE Blade, etc
Officials support:
Samsung GS2, MOTO Xoom, MOTO Atrix4G, EEETransformer, Many CN crappy Android Tablet.
I tried using a OTG Cable with a USB thumbdrive on LGP9xx but no luck, browsing thru the system I found that there are USBDisk DIRs on / or /mnt/USBDisk, there are no define on vold.fstab at all on LG, not like the MOTO Xoom..
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
So my wild guess is it was not turned on kernel level?
As far as I can tell, there is USBHost OTG support on Tegra2, seen post related to that on that, I understand that hardware might not be wired (that's what we gonna check), anyone any info/hints/directions/ideas about this on the LGP9xx?
It would just be great if we can use OTG on LG99x...
thanks.
utp said:
Hi all, I did a search under this forum and do not actually found any info.
Actually, many older Android phone/device do come with USB Host (OTG) function, hardware or software, with hacks or officials,
Mod/Hacks:
MOTO droid, N1, ZTE Blade, etc
Officials support:
Samsung GS2, MOTO Xoom, MOTO Atrix4G, EEETransformer, Many CN crappy Android Tablet.
I tried using a OTG Cable with a USB thumbdrive on LGP9xx but no luck, browsing thru the system I found that there are USBDisk DIRs on / or /mnt/USBDisk, there are no define on vold.fstab at all on LG, not like the MOTO Xoom..
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
So my wild guess is it was not turned on kernel level?
As far as I can tell, there is USBHost OTG support on Tegra2, seen post related to that on that, I understand that hardware might not be wired (that's what we gonna check), anyone any info/hints/directions/ideas about this on the LGP9xx?
It would just be great if we can use OTG on LG99x...
thanks.
Click to expand...
Click to collapse
It needs to be turned on via menuconfig. I could do a quick compile later, if you want. The downside is, that a enabled USBHost disables the slave mode. So no mass storage (Or you implement something like holding back while booting up etc to enable usb host)
Benee said:
It needs to be turned on via menuconfig. I could do a quick compile later, if you want. The downside is, that a enabled USBHost disables the slave mode. So no mass storage (Or you implement something like holding back while booting up etc to enable usb host)
Click to expand...
Click to collapse
Wow, that's a quick and straight to the point reply!!!!!
I think I can live without a slave mode, most of my files are copied to the phone by samba, dropbox or ftp....
just wonder what trick did SGS2 or others uses, I know many of the devices which support OTG has 2 diff USB port, 1 for host and 1 for slave, but I "think" got that working too in 1 port, wonder is it the same as our case here that needs special reboot or so? (SGS2 is not available here yet...so I have never tried it instead of watching in on the youtube VID online...)
Anyway, THANKS! waiting for your releases. thumbs up to all DEVs!!!!!!!!
utp said:
Wow, that's a quick and straight to the point reply!!!!!
I think I can live without a slave mode, most of my files are copied to the phone by samba, dropbox or ftp....
just wonder what trick did SGS2 or others uses, I know many of the devices which support OTG has 2 diff USB port, 1 for host and 1 for slave, but I "think" got that working too in 1 port, wonder is it the same as our case here that needs special reboot or so? (SGS2 is not available here yet...so I have never tried it instead of watching in on the youtube VID online...)
Anyway, THANKS! waiting for your releases. thumbs up to all DEVs!!!!!!!!
Click to expand...
Click to collapse
Don't know. One part maybe only with other hardware drivers. The reboot solution would be best for us (but needs some work). So the easy enable via menuconfig would be enough. Anyway I started to working on this, but I don't know if my otg cable isn't working (slave function was disabled but host didn't worked). So I wanted to test it anyway. What do you need? only mass storage?
The compile could take a while (working on fixing cust toolchain build)
I am aiming on USB thumb drive, keyboard and mouse..thx..
Honeycomb 3.1 has USB Host support.
Hopefully someone can pull it out and use it somehow.
Since there's no source it might not be easy.
Or you can just wait for Ice cream Sandwich(Q4 2011), i'm guessing there will be Host support.
Any news on development?
i think the usb port of phone has no more power to use the flashdrive.
So is this a dead project? Or is there any hope left?
Not being picky or challenging to admin, I originally post this thread under development, which is should be more related since I am not asking generally how to "use" USB Host but related to kernel/drivers development....
I think this thread in general would not actually get much development attention at all...
Anyway, nope, no news, I understand hacks/dev is not a piece of cake, thanks for everyone who is working on the topic here!!!!!!!
and since CM distro do not support USB host at all, then I would suggest there may not be enough attention or momentum at all on this...
dusitmon123 said:
i think the usb port of phone has no more power to use the flashdrive.
Click to expand...
Click to collapse
I may not agree, I did use a O2Graphite with a USB host cable with a USB jostick, and keyboard+mouse on many CN made crappy Tablets, they just works...
Many USB devices do not drain that much power, especially some Flashdrives...
Hello
So is this thread as good as dead, or is anyone trying to develop this?
as far as seen on the thread, it seems dead.....
hello
the usb memory stick must be formatted in fat32 to work.
Which specfic cable works with it?
flavianoxxl said:
the usb memory stick must be formatted in fat32 to work.
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk
Nothing works with it, no-one has produced a kernel with OTG support for the P990.
No idea what that post is about.
I thought I would put all of my findings in one thread, feel free to ask questions below.
Dock Connector
The dock connector is functional in the latest branch of the Nexus 7 kernel found on android source (android-tegra3-grouper-3.1-jb-mr1-fr). The top pin is ground, the second is the right audio channel, the third the left and the bottom pin is 5V. Upon connecting the ground and 5V lines the audio on the dock connector is enabled and the internal speaker is disabled. I used a piezo element to check so I'm not sure how good the audio is, but it is definately there.
Variants
From the kernel source code there are 3 different project ids but 4 names. Nakasi (the standard Nexus 7), Nakasi 3G, Bach and ME370TG. Nakasi 3G and Bach share the same project ID. This is interesting as the project id table states that Nakasi and ME370T are the same, but also separates the ME370TG and Nakasi 3G. It is also revealed that there are, or have been, two power management ICs and two GPS ICs used in the product. For power management both a TI chip and a Maxim chip have been used, though I believe all? of the current Nexus 7 have the Maxim one. The two GPS' used have been the BCM47511 and BCM4751. In addition to this there have been 4/6 PCB revisions. SR3 appears to be very early as some of the code excludes it, and it also has ID 0 assigned. ER1-ER3 appear to be the current series and my C9O Nexus 7 is revision 3, this can be checked in the bootloader, it is noted as "HW VERSION" or version-hardware in fastboot ("fastboot getvar all").
In my kernel compile below I have added a simple debug output that displays the PMIC ID, project ID and pcb ID. If you decide to test the below kernel for the dock functionality it'd be appreciated if you post the output from /proc/kmsg. The line that I have added looks something like "HEADSET: PMIC: 0 Project ID: 0 Revision: 3 UART_enable:1". This means that I have the Maxim PMIC, it's a Nakasi device and the PCB is revision ER3. The reason it's in headset is explained below.
Fastboot OEM Commands
The oem lock and oem unlock commands are well known, however through looking at the bootloader run through strings I have found 4 additional commands that may be of use. I have found oem off-mode-charge 0 and oem off-mode-charge 1. These appear to enable or disable off mode charging, eg charging without the device being on. The more interesting command is however oem uart-on (and oem uart-off). This causes the bootloader to pass debug_uartport=lsport,0 to the kernel, I am not sure however where "lsport" is but it is referenced in arch/arm/mach-tegra/common.c, if uart is not enabled in the bootloader (evident by fastboot getvar all showing uart-on as no) then the bootloader passes debug_uartport=hsport. The 0 appears to indicate the port it outputs on.
Headset UART Output
In the headset driver (/sound/soc/tegra/headset.c) there is reference to a debug board that can be used to get a UART output. From what I understand this is enabled by setting a line-out pin low, however I am having issues working out which one. I have also attempted to enable this for anything inserted, and while this worked, my simple 4 connector 3.5mm plug breakout didn't reveal any data. I'm leaving this one out there for other people to try. For reference, https://android.googlesource.com/kernel/tegra/+/b0d6be9e2033745e46624e518f55e067b75bcd50 is the commit when the debug board was added. I also commented out it's PMIC check to ensure that it did not stop because I have a Maxim PMIC. This should not matter I believe it is just a way to filter out retail Nexus 7s as it can supposedly cause issues with powered headphones.
The driver also shows the possibility for headset support, however I have yet to investigate this.
Kernel Build
I have built a kernel in an attempt to enable as much of the above as is possible. It has working dock functionality and some additional debug information in relation to the headset UART output. My only changes from the default branch are in headset.c and are as follows:
Code:
if(project_info == GROUPER_PROJECT_BACH ||
(project_info == GROUPER_PROJECT_NAKASI/* && pmic_id ==GROUPER_PMIC_TI*/))
UART_enable = true;
revision = grouper_query_pcba_revision();
printk("HEADSET: PMIC: %i Project ID: %i Revision: %i UART_enable: %i\n", pmic_id, project_info, revision, UART_enable);
It should be fairly obvious what bit of code it replaces, it's in headset_init(void).
I have only provided the kernel as a ramdisk and zImage as the ramdisk depends upon the ROM you use. If you use CM10 then these will work, else you'll have to extract the ramdisk from your current boot.img with a tool such as abootimg. This can be run using the fastboot boot command, "fastboot boot zImage initrd.img" or by using the fastboot flash:raw command, "fastboot flash:raw boot zImage initrd.img". The latter is permanent while the former is once only.
This kernel does not support overclocking, special IO schedulers or any special "optimizations". It never will, it is purely to work out how to activate some of the hidden functions in our Nexus 7s.
Note to Moderators
Wasn't really sure where this thread should go, if you feel this should be moved then please do.
Update
Update to the status of UART. I have successfully got it recognizing the headphone port as a debug board, however I cannot yet get any output. To make it see a debug board, ensure that you have a 4 piece connector (yes the Nexus 7 hardware supports a headset) and connect ground to band 3 (band 1 being the tip) and 3.3v to band 4. When you plug it in it'll be reported as debug board if using my kernel.
So to make a speaker dock, is it really just as basic as hooking up the right speaker to the right pogo pin for sound to start playing?
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
ben1066 said:
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
Click to expand...
Click to collapse
Right. Of course. It is just that I remember when someone was reverse engineering the galaxy nexus dock I believe the dock had like a motherboard and chip that needed to be decoded for the dock (and everything else) to work properly.
But this is so simple! Maybe I will take the plunge with this one to try and build myself.
Not so here, it works straight off the bat. Also got the ME370T schematic and it appears I'm connecting to the UART right, I think maybe the kernel is doing something wrong, or I've killed the port on my Nexus 7 with a massive 3.3V, that seems unlikely as I was also using 3.3V to make it detect it as a debug board.
ben1066 said:
Also got the ME370T schematic
Click to expand...
Click to collapse
Omg please share
Google is your friend, it's not that hard to find. I shouldn't really post a direct link.
ben1066 said:
Google is your friend, it's not that hard to find. I shouldn't really post a direct link.
Click to expand...
Click to collapse
Do you mean the one on baidu? I was hoping for one that has the full 90 pages
I only have the 44 page one unfortunately, however it does contain the UART specific bit. I'm now wondering if the odm_production_mode fuse disables it. I don't suppose if anyone still has an ICS Nexus 7 and if they could get me in touch with them?
Coming soon to a Nexus 7 near you.
jonnyg1097 said:
So to make a speaker dock, is it really just as basic as hooking up the right speaker to the right pogo pin for sound to start playing?
Click to expand...
Click to collapse
I'm going to assume that this will be a line level signal. You will need a preamp/amplifier to power your speaker.
Mr. Thompsn said:
I'm going to assume that this will be a line level signal. You will need a preamp/amplifier to power your speaker.
Click to expand...
Click to collapse
I see, I am no sound expert so I got a question to ask... if I dont have one of those attached to it will sound still come out but just not clearly or not come out at all? Or what if I were to use put one in and it's not needed would it affect it in any way?
You will need amplification to get any reasonable volume above that for headphones.
Can we charge the N7 through those +5v and ground pins? Possible touchstone charger case mod?
We can charge however the kernel will need modifying to ignore it when it comes down to audio, otherwise you will end up having no audio out while it's charging, at least through the speaker. Headphone port overrides the dock.
Asus dock
I had wondered what those pins were for when I unboxed my N7. Isn't Asus supposed to be coming out with a dock for this thing? I saw a picture of it a week or two ago and I really want it.
Not to sound pessimistic, but I think the Nexus 7 II will be shipping before anyone gets around to making a pogo dock...
Sent from my Nexus 7 using Tapatalk 2
ben1066 said:
We can charge however the kernel will need modifying to ignore it when it comes down to audio, otherwise you will end up having no audio out while it's charging, at least through the speaker. Headphone port overrides the dock.
Click to expand...
Click to collapse
I'm not really interested in the sound part. The only thing I miss from my HP Touchpad is the inductive charging. These pogo pins seem like the easiest way to add inductive charging to my N7.
Sent from my Nexus 7 using Tapatalk 2
ben1066 said:
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
Click to expand...
Click to collapse
so clarify this for me. There is only single channel audio from the pogo dock port?
Hi,
i would really need a USB Ethernet adapter for my Galaxy Note. I searched forums and all i found was for tablets. I also noticed several times that people were talking that you can build the driver for specific device from official driver. If i understand right i could buy some USB Ethernet adapter and then build it's driver for galaxy note? Or not? Or is there maybe some "universal" driver already made?
I would be really thankful if someone explained this a little more.
Tnx
Moved To Q&A
Please do not post questions in a dev section.
alyosha said:
Hi,
i would really need a USB Ethernet adapter for my Galaxy Note. I searched forums and all i found was for tablets. I also noticed several times that people were talking that you can build the driver for specific device from official driver. If i understand right i could buy some USB Ethernet adapter and then build it's driver for galaxy note? Or not? Or is there maybe some "universal" driver already made?
I would be really thankful if someone explained this a little more.
Tnx
Click to expand...
Click to collapse
The drivers are included in the linux kernel of android, so the driver support is directly linked to the version of the kernel used on your device.
A small search gave me a result: look for USB to RJ45 Ethernet Adapter on amazon (you'll need a USB - micro usb adaptater tho.
shoutr said:
The drivers are included in the linux kernel of android, so the driver support is directly linked to the version of the kernel used on your device.
A small search gave me a result: look for USB to RJ45 Ethernet Adapter on amazon (you'll need a USB - micro usb adaptater tho.
Click to expand...
Click to collapse
So if i understand there are drivers already in kernel? Because i'm almost sure i red before that there are no drivers in kernel so this doesn't work out of the box.
I have OTG adapter so this is not problem. I'll try and buy some adapter and we will see if this will work. I have hydra-core kernel on stock rom.
alyosha said:
So if i understand there are drivers already in kernel? Because i'm almost sure i red before that there are no drivers in kernel so this doesn't work out of the box.
I have OTG adapter so this is not problem. I'll try and buy some adapter and we will see if this will work. I have hydra-core kernel on stock rom.
Click to expand...
Click to collapse
Sadly you'll have to try by yourself, but apparently, the one i found on amazon (around 16£) works on android 3.1+ devices.
shoutr said:
Sadly you'll have to try by yourself, but apparently, the one i found on amazon (around 16£) works on android 3.1+ devices.
Click to expand...
Click to collapse
Aham Do you maybe have Name and model of that device?
How about this? MicroUSB to RJ45..no need of a OTG in between I havent try it though..just found it on ebay & amazon..
http://www.amazon.com/Micro-Etherne...&sr=8-6&keywords=USB+to+RJ45+Ethernet+Adapter
http://www.ebay.com/itm/Tablet-5PIN...ablet_A_V_Cables_Adapters&hash=item4abdf06875
Ebay Adapter
Hi,
here is my unhelpful comment:
I have one of the little buggers (see attached image) boght on eBay:
Search for "USB to LAN RJ45 Network"
It works under Linux and identifies itself as:
"Davicom DM9601 USB Ethernet" and uses the Linux-Kernel-Module dm9601 (as it seems).
(NOTE: One strange thing: The newly bought device uses a MAC address, that was registered to an colleague on our network here. So it spoofs the address?!?!)
Combined with the Host-USB-Adater (OTG) it can be connected to the N7000 - BUT:
A) The LED lights up and blinks to show the trafic on the line
B) Nothing happens on the screen
C) In Elixir it shows up as
Name: /dev/bus/usb/002/002
ID: 2002
Product-ID: 38656
Vendor-ID: 4070
I Get no Menu to configure the wired connection.
So I guess there is no Driver.
I Used Hydracore v7 and Thor Kernel 0.26. (which is WAAAY slower then hydracore)
are there other things I could try?
This looks an interesting idea, wonder is its possible to to have PoE as well, disconnecting network access just to charge would be pretty annoying otherwise.
I moved to CWM 10.1 so could attach various USB devices like thumb drives and keyboards to my HD plus. I've been very pleased with how well it works, but I find it simply won't recognize my USB dac. Has anyone had any success or even tried getting the Nook to recognize a USB DAC? The tablet would be a terrific front end for my audio system if I didn't have to go through the earphone jack.
Unfortunately, this is not a common request. I remember trying to get it working on my Nook Simple Touch (never did, though). I believe that support has to be added in the kernel, so unless we can convince someone to hack up a custom kernel I bet it will never work.
Thanks, Tsunami.
you will need to compile the necessary linux kernel modules for your specific DAC.
just look what modules it uses on an ubuntu or debian installation and compile them für your device.
Thanks, Jann. I'll probably need the idiot's versin of that before I give it a shot.
What DAC are we talking about?
I've got a Fiio e7
The hifimediy sabre android dac
http://hifimediy.com/index.php?route=product/product&path=62&product_id=124