I've got a note 2, running 4.4.2, a note pro 8.4 running 4.4.2, and an asus win7 computer
i can run sidesync on the pc, connect the note via usb or wifi, and get keyboard/mouse sharing working just flawlessly
as soon as I attempt to do screen sharing, the note2 goes black (which it should) but the virtual phone just loads endlessly, and eventually times out. doesn't matter wifi or usb
if I launch sidesync on the tablet, and then the phone, the tablet see's the phone and attempts to make the connection. phone goes blank, and virtual phone just eventually times out, just like on the pc
has anyone gotten this working on the note 2? is there a specific version that works?
so, 5 minutes after the post, there's windows update notification, and the update is related to samsung USB driver update
do the update, reboot, and holy jebus, screen sharing works!
sorta
now I get connection (usb and wifi work) and I can see the screen mirrored. the phone screen does not black out, but I can't interact with it either. on the pc, I can see the mouse icon turn from spinny blue thing, to solid blue donut, but it does't interact with the phone. I can click the home, back and menu buttons on the bottom of the virtual phone, and they work, but nothing else does
bleh
any ideas?
Related
Hey Good afternoon.
I own a samsung galaxy tablet 3, 10.1 inches version.
it is not rooted but i sideloaded games on it.
while playing a game my device first froze then shut off, leaving a blank screen.
I am frustrated because every method i have used didnt work.
i tried the power button options along with the volume up and down, i left it charging overnight for 6 hours and tried again. and still nothing.
Also, i tired connecting to my computer by usb and it nothing showed up. it is also not showing in keis.
I am really frustrated, Can someone help me please?
Hi, I just like to share my experience with problem connection my Galaxy S3 to my 2nd new Samsung Allshare cast dongle. As you can see, I have two Samsung Allshare cast dongles. One in the bedroom, the new one for the sitting room. The first one was bought long time ago and had been working fine. Got latest ME29 firmware. Connection is fast and no problem at all. Now, the price of this dongle has dropped so I proceeded to get myself another one for the sitting room, saving me unplugging it and plugging it, etc.. The new one has the JB version of firmware. The phone detected it without any problem but it kept on showing failed to connect message almost instantly when I tapped on the detected device on the touch screen. This is how I have ended up here at this website. After hours of reading, stock.rom, custome.rom, .pdk, etc.. I was still getting nowhere. But I don't know why. I kept on seeing in my head the blue LED showing on the dongle. Well, stupid of me, I had thrown away the packaging and with it the manual. So, I tried to download it from Samsung website. There is nothing about this dongle on the UK Samsung support website. From my experience with other worldwide hardware companies, so I tried Samsung support website in other countries. And I found a customer commented on another customer's query. So, here is the solution for those people with connection problem after updating the dongle's firmware to ME29. No harm to try this before going down the custom rom route.
After updating the firmware of the Allshare cast dongle, (by the way, my S3 has the latest jelly bean on), it will say Allshare is closed. At the same time, the red LED that was flashing would be solid red now (not flashing). Unplug the power (miniUSB) from the dongle, count to 10 and plug it back. The dongle should be showing a solid red LED now. Press and hold the button at the back of the dongle for about 15 seconds and the red LED should be flashing now. At this point, you can restart your phone just in case. Or just disable the WiFi and then enable it on your S3. Now, go to the dongle, press and hold the button for one or two seconds, the flashing red LED will change to solid BLUE. Now, go to your S3, turn on AllShare. It will detect the dongle. Tap on the detected device on your S3..... lo and behold....it connects!!!!!! Just to repeat, I have not downloaded or mod my S3 in anyway.
The blue LED is only for use in the very first time of connection. So, I guess updating the firmware constitutes a "first time connection" condition. I hope this information help. Good luck all.
What app is used to update dongle? Sorry if this is a NOOB question. ..
Hi,
I have not been able to find an app either on the Google play store or the Sammy app store to upgrade firmware.
The version shown is LJ02. But I seem to have constantly re - pair every time I try to use it.
Help on the firmware elsewhere on the forums someone mentioned there was a better device now (linksys dlink? I don't remember)
TIA - Thanks in advance
Frank
When I turned on the tablet today, it hung and just went to a Samsung screen that gets dim and then bright every few minutes. It never boots.
I tried to boot to the recovery menu and wipe everything, and it still hangs. I tried to connect it to Kies and it never sees it. It makes noise when plugged in and looks like it is going to connect, but it doesn't. I have the Samsung drivers installed, rebooted the PC and have the firewall and the AV client turned off.
Any idea how to get it back up and running?
I am somewhat of a novice on Android devices, but I catch on quickly.
This is actually for my brothers phone. He broke the screen on his note 3 (it shows no video at all) so we got the Samsung Smart dock for it. It was working fine until it software updated. Upon rebooting it no longer displays and video through HDMI. I can hear the jingle as the phone boots up and I can assume that the OS is fully loaded as the lights on the keyboard and mouse come on, but still no video. Tried different HDMI cables and TVs but still nothing. I was able to flash firmware NE6 via odin just incase it failed to update on its own, but that still did not change anything. Anyone have any suggestions on how I can get this thing working again?
I have a galaxy nexus, uses the Eclipse-2.1-toro-build4 rom (old I know, but it was smooth and worked for me, so I kept it).
Last night, after keeping it in my backpack during a bike ride, I went to go use it. The screen is black and I noticed a few solid color black lines running through the screen. Screen is likely dead, my guess.
I am able to boot up the phone fine. I see the L..E.D. notification light come on, and when I get new emails (I left it on wifi the last time I used it), I'll hear notifications...
But, when I try to connect my phone through usb and attempt to connect to it via adb, I'm getting a device not found. I've connected my phone dozens of times using this method without a problem.
Anytime I issue a command with adb from my computer (ubuntu 12.04), it gives me the device not found although the device is connected via usb. This happens even when the galaxy nexus is displayed in nautilus, so it's clearly connected to the computer.
Any idea how to access my sdcard with adb then or to troubleshoot why it's not being read?
Does your phone have a screen lock? Try pressing the power button to unlock it and see if you can find the unlock button (assuming the touch screen still works). If you have a pin, it might be quite hard to get it
I can't access adb whilst my phone is locked. I think it is a security measure.