hey guys came across an interesting discussion! i cant post in dev boards yet... however, this guy provides some answers, maybe some of the elders may want to take a look. EDIT: i cant even post an outside link read code box i guess...
Code:
Hi All,
I've spent some time today dithering on the Nexus S and host mode and I think the way to approach this is different from the Nexus 1 host driver hack.
The Nexus S uses a Fairchild USB switch (fsa8480) to detect device connections. I believe the point is to allow the device to handle multiple functions like charging, UART and USB access simultaneously.
The Switch will detect OTG connections. Plugging in a microB to A convertor with pin 4 grounded to 5 causes the fas9480 driver to wake up and report an OTG attachment. It also calls into the S3C_UDC_OTG driver to configure it up and create a vbus session. (start charging)
The problem is that in the Nexus S kernel, this driver is device mode only. There is no code to put it into Host mode and the chip can only be in Host or device mode. It can't do both at the same time. Also, the few people that have tried to use host drivers have found that they must disable the device code (including charging capability) to get the hubs to enumerate.
It appears that the OTG core in the samsung part is from DesignWare. There are synopsis reference drivers up here:
*************check edit reason for driver link*****************
The register map appears the same, and the code supports host and device mode as well as dynamic switching based on HNP negotiation.
It seems like the best way to approach this would be to integrate this code and use the fsa9480 discovery as the hook to force host mode (when OTG is detected) or device mode when other devices are detected.
The demo we were under the gun to support will probably just use Nexus one, however I thought the rest of you guys would want to see this. I think if done right, you could have host mode, gadget mode and charging all in the same kernel.
Steve
--
Steve Modica
CTO - Small Tree Communications
---not my words, or even me. just though people may want to know!
I am thing I missed something but my Shield cant find my pc. Geforce experience says everything is good but the wifi, and says I need wireless a/g router or a wireless n router is needed, I have a wireless n access point but no router.
Here is what Geforce experience says about my pc.
GPU
GeForce GTX 660
GeForce GTX 660
GeForce GT 620
CPU
Inter(R) Core(TM) i7-3820 CPU @ 3.60GHz
Memory
63.95 GB
Current Resolution
1920 x 1080, (60Hz)
Driver Version
326.41
Operating System
Microsoft Windows Ultimate
If more specific PC specs are needed please tell me.
Is your PC on wireless, or do you have it wired to the network? Also, from 1wayjonny:
Please check your advanced wireless router settings and check if IGMP snooping is enabled.
If so try to disable IGMP snoop or any jitter correction like WMM as well.
Hope this helps, it took hours to figure out the router setting.
No my PC is not on wireless, it is connected to a gigabit Switch. I am not sure if that switch goes to the WiFi AP or if it goes to another switch then the WiFi AP.
I already looked for IGMP snooping and did not see anything close to that.
chevyowner said:
No my PC is not on wireless, it is connected to a gigabit Switch. I am not sure if that switch goes to the WiFi AP or if it goes to another switch then the WiFi AP.
I already looked for IGMP snooping and did not see anything close to that.
Click to expand...
Click to collapse
And you've checked that your SHIELD has taken the update (you'd know, it requires a reboot like any OTA)
It might be related to my problem, but check these:
1. Are the IP of your shield and PC on the same network, only last number is different? (ex. 192.168.1.*) If so then they are on the same "router".
2. You are already on the beta drivers, make sure you have the newest Shield firmware like agrabren mentioned.
3. Reboot everything.
4. In Geforce experience, have you had it scan for games? This is a must and must be done first.
5. Now go to Preferences and click on the Streaming Tab. Is "Allow..." checked? If so, click the reset button.
6. Try going to PC Play on your shield and hopefully it will see your PC.
oushidian said:
It might be related to my problem, but check these:
1. Are the IP of your shield and PC on the same network, only last number is different? (ex. 192.168.1.*) If so then they are on the same "router".
2. You are already on the beta drivers, make sure you have the newest Shield firmware like agrabren mentioned.
3. Reboot everything.
4. In Geforce experience, have you had it scan for games? This is a must and must be done first.
5. Now go to Preferences and click on the Streaming Tab. Is "Allow..." checked? If so, click the reset button.
6. Try going to PC Play on your shield and hopefully it will see your PC.
Click to expand...
Click to collapse
1.
my PC has a static IP of 192.168.0.76 netmask 255.255.255.0 gateway 192.168.0.1
my shield ip is dhcp and 192.168.0.6
2.
yes
3 i can do that but it may do more harm then good.
4.
yes
5.
yes
6.
No Dice
agrabren said:
Model Number
SHIELD
Android version
4.2.1
Kernel Version
3.4.10-g65c8a35
[email protected] #1
Fri Jul 26 23:30:03 PDT 2013
Build number
JOP40D.8857_206.8556
If this isn't what you're showing, PM me and I'll help get you fixed.
Click to expand...
Click to collapse
my shield matches the above.
Rebooting is always the magic elixir
My problem was my shield could see my PC but not acknowledge the connection. I fixed it by uninstalling Geforce Experience and reinstalling it (scanning for games, clicking reset under streaming, then trying it). Try uninstalling GE (not the drivers), rebooting, reinstalling and giving it a go.
oushidian said:
3. Reboot everything.
Click to expand...
Click to collapse
Define everything please.
a list of everything (I can currently think of) on my LAN
1 24 port gigabit switch (stuck at 100Mbps)
1 5 port gigabit switch
1 DSL Modem
1 Printer
1 WiFi AP
4 Servers (lan only)
? WiFi Devices
2+ Desktop PCs
1 FXO/FXS voip adapter
1 2xFXS voip adapter
There is probably more I have forgotten.
Some of those things have a good chance of having problems after rebooting.
chevyowner said:
Define everything please.
Click to expand...
Click to collapse
I was thinking of just the PC and the Shield, but looking at the list of things on your network I'm thinking the PC might not be the problem. There might be something in the AP or the two switches that is preventing the Shield from seeing it. You might try getting some Android network tools (ping and such) to test if the shield can see the PC's IP. I haven't done network troubleshooting with Android so I can't recommend any good methods, but you could probably find some forums on XDA that would help.
I'd try the reinstall of Geforce Experience first just to make sure it's not that.
ping says that both the shield and pc can see each other. reinstalling GFE
chevyowner said:
ping says that both the shield and pc can see each other. reinstalling GFE
Click to expand...
Click to collapse
I had to uninstall both my graphics driver and GFE client and reinstall them to get mine working...
And dang, that's a heck of a setup.
If you search for mDNS or Bonjour tools, they have a discovery tool that should help you find your GFE PC. That's how SHIELD does it.
I have reinstalled GFE, Drivers, and have restarted both my pc and shield no diffference. Shield says "No available GeForce GTX PCs Found"
Hi
I have this running on a DAP-1525 access point so its OK that it is not the router.
I saw you looked for the IGMP, and that sucker was my exact issue after hours. The funny thing is it was default while the router did not have this default from factory.
Would you mind sharing what AP model you have?
sure my access point is a trendnet TEW-638APB. Thought I posted that, but it looks like i did not.
chevyowner said:
sure my access point is a trendnet TEW-638APB. Thought I posted that, but it looks like i did not.
Click to expand...
Click to collapse
I'm fully stumped. At work, I have the following setup (which is a closer match to your setup than my home setup)
1x NetGear Gigabit Switch
1x NetGear N900 Wireless Router in AP mode (only cable is from switch to internet port)
2x PCs connected to Gigabit Switch
The discovery traffic is mDNS (also known as Bonjour) so if anything is configured to filter that out, that'll be a problem. It's also considered a broadcast packet, so you may be able to research Bonjour or mDNS and your wireless AP or other equipment... If you have another computer on the network, there are tools for mDNS discovery, you could use those to see if the PC is appearing (but I don't remember it's discovery name).
Wish I could be more help, but not really my area. I'm an Android guy. You can also try grabbing a logcat on your device, it may say something when you go into the TegraZone dashboard.
will try logcat, and I did try using mdnsscarn from http://sourceforge.net/projects/mdnstools/?source=navbar and windows that spits out "Port 47989 is open on 192.168.0.76"
chevyowner said:
will try logcat, and I did try using mdnsscarn from http://sourceforge.net/projects/mdnstools/?source=navbar and windows that spits out "Port 47989 is open on 192.168.0.76"
Click to expand...
Click to collapse
That sounds like the port... But there should be a service name with it from mDNS...
Can I get the exact name for that mdns service, I can't find anything close to dns or mdns running on my computer.
actully I can find something but only dnscache.
My only other suggestions for debugging is make sure the nvStreaming service is running. If you start the Task Manager (right click on start bar) then look for NVSTREAMER.EXE. If it's not running that's the main problem. There's a service for it (Admin tools/services) that I think GFE installs. If it's there and not running then try starting it. If it's not there at all then I guess reinstall GFE again.
Another thing I can think to try is turn off windows firewall (or any that you are using) in the Control Panel.
The last thing is to isolate your setup to just the Shield, wireless AP, and PC. Plug the AP (LAN port) directly into the PC so it's just serving the Shield wirelessly and the PC wired. If the AP is just a simple WAN port (no LAN) then see if you can set it up as a bridge (a pain) or better yet, try another AP. Hopefully you can isolate the problem.
I have a nvstreamsvc.exe but no nvstreamer.exe
Turned on windows event logging.
From Error group.
Code:
[CODE]The description for Event ID 1 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
NvStreamSvc
NvVAD endpoint registered successfully [0]
Code:
The description for Event ID 1 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
NvStreamSvc
Unregistering VAD endpoint [0]
[/CODE]
From Information group
Code:
[CODE]UpdateThe description for Event ID 3 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
NvStreamSvc
Started [0]
I turned on Windows event logging, and I have the following errors.
Code:
The description for Event ID 3 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
NvStreamSvc
Stopped [0]
Code:
The description for Event ID 3 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
NvStreamSvc
Do not restart event received from SSAU [0]
[/CODE]
When I use MTP even on Windows, I can't help but abhor Google's decision to go with it. You can only do one operation at a time, and it's awful slow, among a number of other issues I've had with it.
I understand why Google did away with UMS, but has anybody ever looked into hacking in any alternatives? One thing that came to mind is having the device simulate a USB ethernet adapter, and running a CIFS server on the phone that doesn't require authentication provided it comes from the USB port (otherwise, just use an app like funkyFresh's Samba FIlesharing over wifi with standard authentication.)
If not that, SOMETHING? I just can't stand MTP anymore.
Hey all. I wanted to make a little "Public Service Announcement" regarding an issue that I have had for quite some time and finally solved tonight. I'm hoping it will help someone else because the symptoms of the issue were very strange and an answer was not forthcoming through standard searching.
I have an HTC M8 (Verizon) and I have been having problems with my "Mobile Hotspot" feature for a while. I thought the issue happened after my first upgrade to Marshmallow, but as it turns out the issue was with my Windows 10 PCs (read on...).
Basically, I was able to connect to my phone's Wifi "Mobile Hotspot" without any problems from an iPad tablet or from my wife's Samsung phone. However, when I tried to connect from my Windows 10 PC I had very strange symptoms.
As per my profession, I consider myself somewhat an expert on Windows and networking in general (not "the expert" but "an expert" ). What was so strange about this issue was that the Windows 10 PCs would see the SSID from my phone without a problem. they would connect after providing the encryption key, and they would even get an IP address from the phone's DHCP server. But, after that, they failed to communicate on the network at all. Not even able to ping the phone (default gateway).
I won't go into the details of all my troubleshooting steps (everything from reboots to wireshark analysis), but honestly nothing worked. I determined it must be an issue with Windows 10 after having two different Windows 10 laptops fail to connect properly. I remembered that I didn't have these issues when my system was running Windows 7.
Even armed with this information I was unable to research to any suitable solution online, when I came across a post somewhere that hinted at a similar connectivity issue. The poster seemed to indicate that the Microsoft drivers caused some issues with their devices that was resolved using older vendor drivers.
Both my Windows 10 laptops in questions are quite old. They were never meant to run anything past Windows Vista/7. Because of this, the vendors didn't really offer complete driver packages for these systems for Windows 10. But, during the Windows 10 installation, the OS detected all the hardware in these laptops automatically and, until today the provided Microsoft drivers seemed totally functional.
I hunted down the latest drivers I could find from the vendors (HP/Dell) and using device manager forced the installation of those driver packages. Immediately upon update to those drivers I was able to connect 100% properly to the Mobile Hotspot and access the Internet.
As it turns out, it seems both laptops had Broadcom based cards - so I suspect the issue may be specifically with Microsoft's Broadcom driver.
Hopefully this comes up in a search for the next person having similar issues.
So I'm not entirely sure if this question goes in this forum or not, but I need to get access to the data partition of a device to analyze its contents. The device is a Skylight picture frame running an RK3128 with an unknown Android OS (locked down, guessing version 5?). I'm interested in inspecting the device because it's happened to either pick up or was shipped with a nasty addon from China. I'm not sure how "common" this sort of business is from a picture frame, I know there was a thing with insecure picture frames before but this is my first actual find.
Basically, this picture frame seems to be monitoring network traffic of any user-connected network. It then reports randomly sized encrypted payloads back to several different adups servers on every initial connect and on a random schedule thereafter. This wouldn't really be that suspicious, except that it's scanning for and attempting to connect to any Wifi network with a weak password and an Internet connection in the background. It will connect to any SSID using any number of dumb/weak passwords, I'm guessing from an internal table. If it doesn't get an Internet connection within 30 seconds, it moves on to the next network. All the while, the Android UI just insists that there's no network connection possible although it can see networks (likely because something in the background has stolen the radio). Additionally, it scans and connects to any insecure Bluetooth devices nearby, but I don't have a way to intercept its communications currently.
Skylight support immediately played quiet when asked how to access their device to assess the malware and "are talking to our senior developers to figure out a fix". The "senior developers" (I'm sure in China) also denied any possibility of getting inside the storage of this. I'm suspicious that they may have knowingly shipped this with malware, or added it after the fact and I would like to prove it. I split the frame open since I was pretty sure it would just be a generic board like a Pi inside, possibly with serial pads or other development options. However, I don't know what I'm looking at or if it will meet my goals. There are OTG-DP and OTG-DM pads next to the Micro-USB port, a USB-A port, a 5v barrel connector and a large number of unmarked pads around what appears to be an expansion ribbon connector spot.