I have the official Samsung USB Connection kit. Both connectors work fine immedeately after boot, but once the device has 'slept' they do not work anymore. I get a notification that the USB Connector is connected, but whatever I insert nothing happens. LEDs (on USB sticks, mice, ...) do not light up which seems to indicate that no power is applied to the port.
I'm running stock Android, rooted. Booting into safe mode makes no difference.
Any ideas what's going on?
You're not the only one, except that in my case USB sticks do light up. IMHO Samsung seriously botched up the automounter in their last update. I wonder how long it's going to take them this time to get their act together and produce a bugfix.
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
SpicyKiwi said:
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
Click to expand...
Click to collapse
Good luck with that. I contacted Samsung support Benelux and was told it was because Amazon Germany had installed "German software" on my tablet.
Trust me, that is NOT the case...
karel jansens said:
IMHO Samsung seriously botched up the automounter in their last update.
Click to expand...
Click to collapse
I'm not sure it's the automounter. Keyboards and mice show the same problems.
sciurius said:
I'm not sure it's the automounter. Keyboards and mice show the same problems.
Click to expand...
Click to collapse
You might be right, I haven't tried one of those yet. Of course, that would mean Samsung botched up the entire USB subsystem of our Note, which is kinda even worse.
Seriously, is anything done about this usb c**kup, or what? I bought my Note, expecting it to replace my venerable Archos 101 which, incidentally, had excellent usb connectivity three blooming years ago and on Android 2.1, only to find out that not only did I have to buy motherloving adapters for the Note, but on top of that that they don't even work properly.
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
sciurius said:
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
Click to expand...
Click to collapse
Quick question, has anyone has the adapter problems while on Android 4.1.1? I tried my adapters on a shop showroom model of the Note 10.1 and they worked perfectly, but only afterwards I noticed that Note was running 4.1.1, while mine is up to date with 4.1.2.
I'm just trying to avoid having to send back a piece of equipment that, despite everything, I can barely miss.
One of the USB OTG tools (forgot which one) had a table of functioning USB host versus Android releases and last time I looked the number of 4.1.2 devices that hat USB problems was significantly higher than the 4.1.1 devices. So I have all reason to believe it is a software problem, introduced in 4.1.2.
EDIT: The tool is USB Host Diagnostics from ChainFire.
So, is there an easy way to go back to 4.1.1 on the BigNote? Mine came with 4.1.2 installed anyway and something tells me that, if I ask Amazon to downgrade for me, I'll be answered with a deafening silence, probably with a "Duh?" In there somewhere.
On second thought, scratch the easy part; is there any way to downgrade a BigNote without losing any of Samsung's added value (yes, I happen to consider most os what they added actually valuable).
Related
Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730
OK, will do. Thanks!
try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I went from a Galaxy nexus to an N5 and a lot of stuff broke. My voice dialer for one and wifi is wonky for another. Wireless charging heats up the battery so much I've quit using it.
I really like the g2 and thought about returning the N5 and getting one. Only problem is that when the G2 gets kitkat all of the problems I'm having may very well come back. I hope that isn't the case with Miracast as well although LG will probably do better testing.
Good luck with Miracast. Sorry I don't have a way to test it for you.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I tried it on my friend's LG TV and my own Samsung and neither would get very far - hope it's a simple software bug
What TV you guys using for miracast... My LG TV says wireless display but nothing about miracast
Sent from my Nexus 5 using Tapatalk
Miracast wireless Display
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
so the n4 and n7 on 4.3 work okay but your n5 on 4.4 doesn't?
if so it makes me feel a little better than it's just a software issue that (hopefully) is cleared up soon in an update
Maybe. Both the N5 and 4.4 are different from n4 and 4.3. could be a HW issue. Likely a SW problem.
peter
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
i feel like it's less of a hardware issue since miracast worked fine on my g2 and my note3 which are using the same SoC as the n5. maybe i'll try to flash 4.3 back onto my n7 and see if that connects.
is there any way to send this issue to google so they can be made aware of it?
and of course when i decide to do a logcat to see if i can see what's going on when it's trying to connect the phone (and tablet) decide not to see the tv at all for some reason.
Mis understood
Taomyn said:
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
Click to expand...
Click to collapse
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Tried to connect my N5 to Panasonic BluRay Model 230 - it finds the device, and then when you try to connect it just sits there, and sits there....
Honestly, where the hell is the V&V testing ?
prrred said:
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Click to expand...
Click to collapse
good to know, so it seems to be a 4.4 issue more than a hardware issue.
maybe i'll downgrade my n7 today to test it out. (i was going to do it before but then the 4.4 update was officially released and of course i had to flash that first!)
i also emailed google support today to see what they have to say. it's frustrating not being able to use it in the car since i don't like the actual UI of my headunit.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
adiliyo said:
good to know, so it seems to be a 4.4 issue more than a hardware issue.
Click to expand...
Click to collapse
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
theesotericone said:
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
Click to expand...
Click to collapse
Hmm if a custom kernel might help it might be enough to get me to unlock the boot loader and have to set up everything again...
Sent from my Nexus 5 using Tapatalk
bluegizmo83 said:
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
Click to expand...
Click to collapse
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
adiliyo said:
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
Click to expand...
Click to collapse
Awesome man, thanks for the info!
Does miracast work then? I'm thinking of getting a dongle, or should I just use slimport
Sent from my Nexus 5 using Tapatalk
Anyone else have a 2013 lg TV with miracast? I just got one and there is a 10-15 second lag. Its pretty much worthless.
Is there something I'm missing?
Sent from my Nexus 5 using Tapatalk
i've tried it with faux's kernel and francos, both don't work for either of my devices. i emailed google and they replied with troubleshooting info but i haven't had a chance to reply to them and try what they have said (really basic stuff, i don't think it will help)
i refuse to go to crappy crappy touchwiz to make this work, but it makes me sad that i can't use my headunit like i want to.
hi..
after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.
i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.
Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.
Let me know if the above works (battery pull).
I had this issue too, didn't realize it until I tried updating different roms...
I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.
I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.
I also updated to the latest CWM per OmniRom thread in development forum.
I trust Magamo, though, in providing the right diagnosis and solution.
mod please delete
REV3NT3CH said:
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder
Edit: like this for example https://github.com/TeamApexQ/androi...mmit/b9d389cca9f241d778f1d8206195e16dfcb3dee8
Click to expand...
Click to collapse
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.
This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.
Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.
Surprisingly, pulling the battery fixed the problem!
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Autolooper said:
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Click to expand...
Click to collapse
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
xob3444 said:
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
Click to expand...
Click to collapse
Android 4.0+ no longer supports USB Mass Storage out of the box for the internal storage, and neither do any of the custom images that I can think of. MTP is the answer here. The fact that you are getting MTP means that the device is talking over USB, which means that you are not suffering from the problem described in this thread.
Suddenly OTG and Gear VR are not working on my S8 plus. no water, drop or anything. I have the device for only 2 weeks. No OTG device works (tried with genuine type c to usb adapter). It used to work like two days ago. I did factory reset and reinstalled firmware using smart switch. In addition, Gear VR is not being recognised anymore. PC connection and data transfer using the cable work ok. I believe OTG uses different pins. May it be a hardware issue? I remember getting some high-powered device connected before it stops working at all (using just a simple mouse). I tried everything.
I saw that a number of people have the issue on samsung support website. I hope it is not a known issue and samsung just does not state it officially (like the S7 edge pink line).
Please help or let me know if you have the issue too.
Arismfg said:
Please help or let me know if you have the issue too.
Click to expand...
Click to collapse
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
cam30era said:
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
Click to expand...
Click to collapse
thank you for your reply. I have already checked the thread above. However, no working solution. Is there anyone who managed to figure out if it is a software or hardware issue? I wonder why it is stated as solved. I dont think the guy with the issue fixed it
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
povotron said:
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
Click to expand...
Click to collapse
Thanks for the reply. Does this also have to do with OTG devices not recognised? Do you have this issue too? What is strange is that Gear VR used to work. At least for a while on my unlocked S8 plus. I cannot understand how this may block the OTG devices. Is there something left in the settings that may block OTG?
By the way, I hope you are not referring to the network issue. My Gear VR is not recognised at all.
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
povotron said:
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
Click to expand...
Click to collapse
Well I gave my phone to the official samsung service and waiting for their reply. I don't think I installed any updates before and after the issue appeared (at least not firmware updates but not sure about oculus or other apps) . By the way it is not the adaptor that has the issue. I tried many others on my phone. And the adaptor works with a friend's S8 (not plus). Only one works (well not really). It iss an OTG type-c to micro usb (bought from ebay) which comes up with a notification that high powered device was connected but then nothing happens whatever option I choose. And it is not a high powered device because it used to work. I tried even a mouse with its own battery. But if it was a phone update, I think a factory reset should fix it? It did not for me.
Do you think of taking your phone to the official service too?
A full factory reset also didn't work for me. From other forums it seems that other people who have taken them in for service receive a replacement phone. Some people however then mentioned that they encountered the same issue a few months later with the replacement. I would take mine to Samsung but it's a grey import and Samsung refuse to touch them even though it's the same model sold locally. If it's definitely a hardware fault I'll consider sending it away but it would be an international service which would leave me without a phone for quite some time.
Yes, you are right. Some people saw the issue after a few months of getting the replacement phone or even after restoring their google account and settings (without being able to get it fixed by factory reset). This is what actually scares me the most because it looks like hardware issue of the phone in general. It looks like a well known issue which samsung does not officially accept. SiImilar to the pink line on S7 edge I had before. Anyway, as charging and connection to pc still work, I can give my phone and get a new model later cheaper. The last two samsung flagships came with issues that (the most important) samsung does not accept officially. Maybe it is time to change brand (always android though).
I got my phone back from samsung service. They did not replace my phone but they replaced both the logic board and the type-c board. As expected, it works again with OTG devices and Gear VR as it is like a new phone after replacing all that. Installed all apps again one by one (not restored from backup) and everything still works. Hope it stays like that. So hardware issue? Looks like it.
I know this is an old thread, but I replaced just the USB board and it didn't fix anything. So maybe it's a motherboard issue?
Hi all,
I've been running my Xtrons unit for a while now, with Malay v2 Android 8 for a few months. Everything used to work great, but since last week (without changing anything) my USB connection works crappy. My USB with music and DAB are connected directly through the two USB connections at the rear with an extension. They both stopped working suddenly, but the USB stick I have connected still has its power LED on. So there is power to it.
A few reboots later it worked again, but the next day it was gone again. I then checked the MCU settings and disabled PVR USB (I believe), and it worked again after a reboot. When it works, it works great by the way. The next day it still worked, so I was thinking I solved it.
However, the same afternoon same issue... Few minutes later (without a reboot) it worked again... Tried to disconnect everything and plug in either the DAB or the USB stick, but same result.
I strongly think its a software issue since I can 'solve' it with rebooting it sometimes. Anyone ever had something like this?
No one? Same problem today. Started my car and no USB whatsoever. 10 minutes later without doing anything everything worked fine for the remaining part of my journey to work.
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
It's a GS unit. Not sure if they're the same perhaps. Weird that it suddenly appeared.
I have the same issue.
when I connect USB/64GB and 3G dongle USB constantly reconnects. I'm on dasaita px5/4GB
1st up and not to be one of the thread patrol guys we seem to have running round the Android auto forums..
But general help questions like this should be in the QA area..
Maybe mods should shift it..
But to answer the question with a bit of experience lately..
In my USB thread on SSD's and the USB M2 casing I have used.. I found a similar thing going on with the USB ports..
As reported there.. plug in the M2 SSD (which of course is plugged into the controller in the housing)
And it's seemily pulling too much power as it affected the ability for a GPS lock..
Unplug it and GPS works..
My thinking there is as said..to me it is like it is either a software glitch and or power interruption. I am leaning more towards the power theory.
There is a bit of reading around on USB port burn out on some of the boards.. so it's almost like a case of being careful on actually plugging in to much to ...
In my case 3 USB ports..
This does bring up another point that has been bothering me the last few days as I hunt for a better storage situation..
My reading on 128g USBs via the comments section is showing up extremely hot usb's.. thus it's something to think about . As in these things in a glove compartment could end up being a fire hazard..
And or even in the case here, causing sort of interference back through the system..
Some of the more electronically minded techies with the right testing equipment would be able to have more input.. and I can bet you that the engineers in the factories making these things are not talking or reporting back to their bosses anything along these lines.. as they will be all about protecting thier jobs.. and no one is going to want to put thier hand up and say.. hey..I think we have a problem..
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
Tried the 'fix' from here, which should restart the usb hub, but all it does it restart the wifi, as can be seen in the code. The problem is that USB worked fine for me now twice while testing. So couldn't test if the 'fix' actually does help.
I can't seem to get Tasker to run with root... It says that my device is not rooted, although other apps give the SuperSU pop-up that ask for root access...
Tried the .sh file in the other tried, and an app to reset the USB hub, but no luck. Rebooting a few minutes later worked.
I have the same issue. I figured out that it is temperature related. When the outside temperature is ABOVE 11-12°C the USB works fine. When its colder It constantly reconnect every 20(?) Seconds. When the Car Heat Up enough the Error is gone again.
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Bose321 said:
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Click to expand...
Click to collapse
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
EDGN said:
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
Click to expand...
Click to collapse
Yeah I've seen that, but it's too small for me to try. I'm not that great in soldering, so don't want to ruin my unit haha.
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Ati_gangster said:
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Click to expand...
Click to collapse
Already tried that, and I have the Malaysk ROM which also has the 'fix'. Also tried to run it manually. Also have a USB Controller app that can do this.
Worked a few times but doesn't anymore now.
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
mahtew said:
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
Click to expand...
Click to collapse
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Bose321 said:
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Click to expand...
Click to collapse
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
mahtew said:
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
Click to expand...
Click to collapse
Sounds weird as well! Good luck.
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
karolp1993 said:
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
Click to expand...
Click to collapse
I think you need to see very closely in where the usb cable is welded in the morherboard and try to find cold weldings. I had same problems with my pumpkin and when i completely dissasemble it i saw a ton of cold welding and i reweld everything and its rock solid now.