There have been a lot of problems with MTP for people with all different OS's and phone only being able to connect using Kies / Air / PTP. I too had the same problem. There was a lack of information on the internet for it. Well hopefully we can have a master list of fixes for other people having trouble because the S4 really seems to be a solid phone (I upgraded from a POS S2.)
Anyway here are a few threads to check out before checking out what my solution was.
Registry Fix - Does not apply to everyone - I did not have the UpperFilter Keys present.
Device Manager Fix
As for me, I stated I had a Galaxy S2 before. So I already had the Samsung S USB drivers. Yours could possibly be out of date. Mine was updated in April of 2013 which was the latest driver. You can find it here. Latest version at time of this post - 1.5.14.0
Samsung USB Driver 1.5.14.0 - XP/Win7/Win8
So let's get down to the fix.
Unplug phone if plugged in.
Remove Samsung USB Driver in add/remove programs. Just in case it became corrupted at some point.
{
"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"
}
Restart after removing.
Install latest Samsung USB Driver. Link Above.
Plug in phone and see if it connects and shows up under My Computer / Auto Play box pops up.
If it does, great, fixed for you. Most people that are experiencing this issue though, it will not be THAT simple. If not, continue.
Now hit WINDOWS KEY + R and in the run... box type devmgmt.msc to bring up the device manager.
In the screenshot you will see the SAMSUNG USB controller lited under USB devices with no Yellow !, this is when it is working normally.
What you may see is underneath the "System Devices" menu and above the "Universal Serial Bus Controllers" menu, you may see the Samsung USB menu there.
Expand it
Right click
Properties
Driver tab and click Update Driver.
When next menu comes up, click "Search automatically for updated driver software" so it searches the internet for the latest driver. Should go out and find the correct driver and install it. Device should now pop up through MTP. Good luck!
Steven @ RestartFirst.com
Related
Hi,
Every time I sync with my computer the time in my tilt move 1hr ahead. The time settings in the computer and the tilt are the same. Any ideas what the problem is?
Thanks
Sounds like a Time Zone related issue. Check that your phone and dekstop are in the same one.
Yes both the computer and the tilt are the same, -4 atlantic.
I also downloaded and installed a patch that I found in this forum but didn't work.
Any help please.
Thanks
Check that your time zones are same on both again, and check off the synchronize with online provider.
moddin said:
Check that your time zones are same on both again, and check off the synchronize with online provider.
Click to expand...
Click to collapse
They both the same, double and triple check!!
How do I check off the syncronize with online provider?
Thanks!!
BUMP!!!
Any Help!!!
Need some help here!!!!
Go to phone ---> menu----> options. There is a a tab at the bottom that says time zone. There is an option to have it get the time from the radio signal. DISABLE. That should take care of it.
Thanks for your suugestion, but it is allready disable. Any other idea.!!!
This happened to me too. Connect your phone to your computer let activesync finish syncing then go to Tools --> Options --> click Settings in the Options tab --> Then uncheck "Synchronize Pocket PC date and time upon connecting". That fixed it for me when I had this problem.
You could try to delete the partnership in activesync and on the phone and then try re-synching
Kinglouis3 said:
This happened to me too. Connect your phone to your computer let activesync finish syncing then go to Tools --> Options --> click Settings in the Options tab --> Then uncheck "Synchronize Pocket PC date and time upon connecting". That fixed it for me when I had this problem.
Click to expand...
Click to collapse
Hi,
Where is Tools located, in the phone or in the computer, I'm using Windows Vista.
Thanks!!
You have to go to tools in activesync on your computer. I use xp so i have no idea if activesync looks different on vista but mine look like this
{
"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"
}
on vista you use WMDC (windows mobile device centre) all you need to do is to click on the settings icon on the front page and de-select partnership from there
Partnership uninstall and intalled, still not working.
Also I just realized that the internet via PC to phone with activesync not working either. DAMMM!!!
Folks,
Sitting in a rental car wanting to connect your phone with the bluetooth handsfree?
Got a new stereo headset and want to pair it with your device?
Want to send a file via bluetooth to a friend and need pairing first?
Whenever you want to pair to a device or unpair from a device you have to go deeply into the settings of Android. If you finaly got there, the bluetooth pairing partner is out of pairing mode again...
That's the reason I wrote btPair. On opening the App you can scan for visible devices surrounding you and a red or green image shows you the current pairing status. With just one click you can pair or unpair to any device around you.
It's that simple...
Available on the Market now.
If you have questions, rants, comments or feature requests leave a message here or send me an email.
Cheers
Screenshot below
{
"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"
}
Thanks always bugged me!!!!!
Sent from my SPH-D710 using xda premium
I so needed this about two days ago, thank you!
Sent from mah 'Bolt made by Zeus himself
Thanks for buying and your response.
So, how do you like it? Everthings working as expected?
Cheers
Didn't quite like it. It's full of bugs and have sent you an email of the problem. Hope to see it resolved. Thanks.
Just to clarify: It is not FULL of bugs. There was one bug on one specific device. It was a duplicate device entry (the discovered device was listed after each discovery additionally) on a Galaxy Tab 7.0 Plus with HC 3.2.
I was not able to reproduce this behaviour my Xoom with HC 3.2 and all my other devices (including emulator). However, I made some changes and added a function to display already paired devices uppon startup of btPair, and added a button for that.
So version 1.1 is published now.
Cheers
Many thanks to the developer. Now it doesn't show duplicates anymore. Hopefully the developer will add more feature in the future.
Sent from my GT-P6200 using Tapatalk
I received an ADT-1 dev kit a few days ago. It's awesome.
I can set the gamepad to pairing mode by holding BACK and HOME for a few seconds.
I can pair the gamepad to my windows 8.1 machine just fine, and it's recognized as a gamepad.
Where there's a problem is that the 2 analog joysticks are not recognized. Also the left hand side analog trigger button is recognized as an analog stick that can move in 360 degrees. And for some reason windows is calling the axes as Accelerator and Brake. It's as if it's being recognized as a game wheel.
Is there any way to make windows think it's an xbox controller??
Hopefully the screenshot will make it clear as to what's going on.
{
"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"
}
1 week bump
Any luck?
I am looking for same answer
Not sure what's up with your controller but mine paired perfectly with my laptop on XP and I didn't get that.
Try a different driver on it.
Any links?
Does anyone have any links for the driver ? I can't find one for win7 (64bit)
Same Issue
I'm still waiting for a solution :/
I was able to make this work by using ASUS Nexus Player gamepad drivers. Steps:
1. Search for and download nexus player gamepad drivers. Currently the download is available at https://dlcdnets.asus.com/pub/ASUS/Accessory/gamepad/AsusGamepad_4_0_0_9.zip but it might move
2. Extract zip and run setup.exe
3. Finish setup and restart windows
4. Pair the gamepad if not already paired
5. Go to control panel > view devices and printers and double click on the game controller
6. Go to the hardware tab of the properties window
7. There should be two HID-compliant game controller devices. Double click on one of them
8. Click change settings
9. Go to the details tab
10. Select the device instant path property
11. If the value ends in 0001 close the window and repeat from step 7 choosing the other HID-compliant device.
12. If the value ends in 0000 go to the driver tab
13. Click on update driver
14. Click on browser my computer for drivers
15. Click on let me pick from a list of available drivers on my computer
16. Unselect show compatible hardware
17. Select ASUS > ASUS Gamepad
18. Click yes on the update driver warning
19. Click close
20. You are done! There is a new "Xbox 360 Controller for Windows" for which all the buttons are working
Since upgrading to Marshmallow, my USB connection settings won't stick. Whenever I connect by USB to my computer, it automatically goes to "charging" mode. I have to manually switch it every time to MTP. Anyone else notice this? Is there a fix? Not a big deal, but kind of a pain!
Try changing it in Developer Settings...
{
"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"
}
Sent from my SM-G925V using XDA-Developers mobile app
dSlice said:
Try changing it in Developer Settings...
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
Changing the setting in Developer Options doesn't stick either. It still reverts back to "charging" when reconnected.
Edit: My possible fix (below) didn't work either. After a while, it reverted back to just "charging". Back to the drawing board! If anyone has any ideas, please let me know!
Found a possible fix! Hoping it holds up. Settings>Developer Options> turn on USB Debugging. Then in USB Configuration, choose something other than MTP. Once that stuck, I could select MTP and it stuck. Seems to work fine and connects as media device now.
Zelmo88 said:
Edit: My possible fix (below) didn't work either. After a while, it reverted back to just "charging". Back to the drawing board! If anyone has any ideas, please let me know!
Found a possible fix! Hoping it holds up. Settings>Developer Options> turn on USB Debugging. Then in USB Configuration, choose something other than MTP. Once that stuck, I could select MTP and it stuck. Seems to work fine and connects as media device now.
Click to expand...
Click to collapse
Did you ever resolve your issue? I have the same problem with Nougat. It's Note 8.0 though. Thanks
We need:
- OnePlus Nord CE 5G
- OxygenOS 11.0.9.9.EB13AA
- root (I have Magisk without TWRP)
- App Manager (Github)
I could start to just start screaming how terrible feature it is, and we even can't permanently turn it off, but my English is bad so better let's start.
1. Open App manager
{
"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"
}
2. Open side menu.
3. Go to the second option - probably "list settings" in English.
4. Untick selected option (It will be ticked by default) - probably "user applications" in English.
5. Then in the search bar type: "tuner" and click on "Tuner audio Dirac".
6. Click Turn-off equivalent in your language (mine is ON because I turned it off before) - don't worry, just click this down pointing arrow icon.
7. Reboot
8. Test if this works:
Testing Methods:
- plug your headphones and listen same track with the same headphones on PC and phone
- go to options, pick audio related options, and then you will see Dirac options - click them, you should get white screen and then force push to options main menu (Its DESIRED effect) - after doing same thing continuously you will get settings menu crash (this only appears after doing this twice - not important thing)
When you get same results as above - congratulations: operation complete.
During testing, watch for any unexpected behaviour (You turned off a system component after all).
One important thing: Don't REMOVE/UNINSTALL a component. This app is already turned off and never self-activate (maybe until update, then do the same steps). I think removing this feature will affect negatively on system (somehow).