Related
So, this isn't about the Galaxy Nexus per-se, but I know many of you are scared of the change to MTP and the interaction with the computer, especially those of you coming from Gingerbread directly through to the Galaxy Nexus.
I've had a Motorola Xoom (which doesn't support USB mass storage mode) for a while. Simply put, there is _no_ native support for MTP in OS X (10.7 or lower). If you plug your Galaxy Nexus into your Mac, nothing will happen at all. OS X won't see it, DoubleTwist doesn't see it, Songbird won't and iTunes (obviously) won't see it. As far as I know, there's no way of enabling your Mac to see the device natively, and all of the software designed for other MTP devices that I've tried doesn't work.
In fact, the only way your Mac will ever see it is if you download Google's Android File Helper software. This program, once installed, runs in the background, and whenever you plug in your Honeycomb (or ICS) device, it pops up a window showing the contents of the phone's memory. From here (and only from that window), you can pull files from the phone/tablet or put them onto it.
This works acceptably, but with a few hangups. First, unlike a normal finder window, only one transfer can occur at once, and there's no queueing. So, if you drop one folder on to copy, you're not able to move anything else onto or off of the card until it's finished. Also, large transfers (~10 GB) don't work particularly reliably, and may fail partway through, so you may consider dragging files in in groups. Finally, and most frustratingly, it will often not be up to date with what files are on the device, especially if you've recently deleted them. So, folders or files may still show up that you've recently deleted. Maybe this has been changed in ICS (I hope so!), but that's my experience.
That's your primary way on or off the device. I've had limited success using DDMS for transferring files on and off of the device, and although it's clunky and requires USB debugging mode, it's the most reliable way I've found for transfers that fail in the Transfer client. In practice, I'd recommend using something like SwiFTP to copy (smaller) files to and from your device, and avoiding the hassle when you can.
In short, you definitely CAN use OS X to transfer files onto and off of your Galaxy Nexus, but it's not as easy as it was for Gingerbread Devices, and tools like DoubleTwist and Songbird can no longer access your device at all (in their current versions). You can get around this using AirSync for DoubleTwist to load music, or doing so manually, but it's kludgey. It's unlikely that Apple will choose to support MTP in future versions of OS X (it's a Microsoft protocol now used mostly by Android), but hopefully Google will improve the tool as time goes on.
Sorry if this is all well known and obvious, but if you were on the fence about the GNex because of this, don't be. The MTP switch is annoying, but nothing showstopping, even for OS X. Just FYI.
wanderfowl said:
I've had a Motorola Xoom (which doesn't support USB host mode) for a while.
Click to expand...
Click to collapse
Which doesn't have USB Mass Storage mode (not USB Host - this is USB OTG where you can plug in other USB peripherals into the Xoom). Sorry just a pet peeve watching people confuse the two.
Thanks for an informative post. MTP looks like it is going to cause headaches to every non-Windows device by the looks of it. Ironic for a Linux based device ; ).
Jebus99 said:
Which doesn't have USB Mass Storage mode (not USB Host - this is USB OTG where you can plug in other USB peripherals into the Xoom). Sorry just a pet peeve watching people confuse the two.
Thanks for an informative post. MTP looks like it is going to cause headaches to every non-Windows device by the looks of it. Ironic for a Linux based device ; ).
Click to expand...
Click to collapse
Whoops! Edited
So WiFi File Explorer outta work though if your other ftp type app did?
Thanks for the info. I remember using the app on my MacBook when I had the Xoom. I didn't mind it too much, but it was a tad annoying having to open the app rather than just pop open 'finder' and go. FWIW it DID work just fine for my couple months with the Xoom.
So WiFi File Explorer outta work though if your other ftp type app did?
Click to expand...
Click to collapse
Yeah, FTP apps of all sorts work fine. I use Transmit on the Mac to access the phone via FTP, and that works like a charm.
martonikaj said:
Thanks for the info. I remember using the app on my MacBook when I had the Xoom. I didn't mind it too much, but it was a tad annoying having to open the app rather than just pop open 'finder' and go. FWIW it DID work just fine for my couple months with the Xoom.
Click to expand...
Click to collapse
It works fine to the internal storage. Maybe I should've said explicitly that I had more issues using the Android File Transfer app with the SD Card in the Xoom.
I'm glad Google gave this a thought, now they should make one for linux too, but they probably won't.
wanderfowl said:
iTunes (obviously) won't see it.
Click to expand...
Click to collapse
My post is pointless, but hell will freeze over before iTunes recognizes a Samsung device, lol. If it wasn't for laws and standard, they wouldn't allow their PC to recognize Samsung devices either.
eksasol said:
I'm glad Google gave this a thought, now they should make one for linux too, but they probably won't.
Click to expand...
Click to collapse
That's the nice part about Linux. The people working on Linux have an active incentive to add this functionality, as it improves the experience. With OS X, they have an active (marketing) reason to not add it, anti-competitive behavior. Don't give up hope
wanderfowl said:
It's unlikely that Apple will choose to support MTP in future versions of OS X (it's a Microsoft protocol now used mostly by Android), but hopefully Google will improve the tool as time goes on.
Click to expand...
Click to collapse
It's a protocol native to the USB standard since 2008 so if Apple want to be standards compliant they should implement it. There are lots of other devices that use it as well.
wanderfowl said:
As far as I know, there's no way of enabling your Mac to see the device natively, and all of the software designed for other MTP devices that I've tried doesn't work.
Click to expand...
Click to collapse
Those apps probably just need an update to libmtp.. for some reason that library has the device ID of every device it supports hardcoded in, rather than working out whether a device supports mtp in other ways as things like windows do.
If anyone has ported mtpfs to OSX you should be able to get that going (will probably do that myself when I get time.. Android File Transfer is OK but a bit quirky).
blunden said:
It's a protocol native to the USB standard since 2008 so if Apple want to be standards compliant they should implement it. There are lots of other devices that use it as well.
Click to expand...
Click to collapse
Trust me, I'm not defending it, but I can't imagine Apple in its current state implementing a change which would help in supporting a competitor's product (especially Android) just to be open and compliant. Given how willing Apple as a company is to cut off its nose to spite its face, I doubt that they'll rush to help their users here. Prove me wrong, Apple.
TonyHoyle said:
Those apps probably just need an update to libmtp.. for some reason that library has the device ID of every device it supports hardcoded in, rather than working out whether a device supports mtp in other ways as things like windows do.
If anyone has ported mtpfs to OSX you should be able to get that going (will probably do that myself when I get time.. Android File Transfer is OK but a bit quirky).
Click to expand...
Click to collapse
I've tried working with the existing mtpfs ports, but wasn't able to get very far at all. I'm hoping that ICS will spur people to develop further on that, maybe pulling it into MacFUSE.
wanderfowl said:
Trust me, I'm not defending it, but I can't imagine Apple in its current state implementing a change which would help in supporting a competitor's product (especially Android) just to be open and compliant. Given how willing Apple as a company is to cut off its nose to spite its face, I doubt that they'll rush to help their users here. Prove me wrong, Apple.
Click to expand...
Click to collapse
You certainly have a point and is the primary reason I dispise Apple as a company.
My main point was that it's not to be considered a "Microsoft protocol" as it's been part of the USB standard for years now. Nothing is stopping any OS from implementing it and as a standard they really should as it brings some nice improvements like not requiring the OS on the PC to have support for the filesystem used on the device. Considering FAT32 and exFAT are basically the only filesystems that work in all major OSes, the former being old and having severe limitations and the latter requiring a license it's nice to be able to use something like ext2/3/4 or any other filesystem of choice and still maintain compability.
Apple hasn't typically been particularly resistant to implementing standards and protocols used to communicate with 3rd party devices. Also, the major force behind Apple's resistance to just about everything is gone now... We'll see if they continue the trend without him.
Just bumping this again for the new crop of ICS users
So I've just gotten my VZW Gnex, and unfortunately, Android file transfer seems to have the same problems with not refreshing the files in the folder as it did on the Xoom.
That said, if you're trying to get into a given folder and your Android File Transfer can't see the contents (or the folder itself), just reboot the phone and when it comes back up, the new folder should be there and right as rain.
wanderfowl said:
OS X won't see it, DoubleTwist doesn't see it, Songbird won't and iTunes (obviously) won't see it.
Click to expand...
Click to collapse
If syncing with iTunes is your goal, you left out iSyncr. Our app can sync Android 3.0 and 4.0 devices with iTunes on a Mac over USB (and WiFi). If your Android device is supported by Android File Transfer, it is supported by iSyncr.
As always, you can shoot me an email if you are having an issue with this.
-Justin
I seem to be having a new issue. All of a sudden, I can't sync anything to my XOOM. I had to unlock, and re-unroot it to install ICS on it. I don't know why, but everytime I begin a transfer to my XOOM Android File Transfer instantly says that my my device is locked and I need unlock the screen and/or it can't access the media storage device. It's really frustrating. I can't push the SU.zip bc it gets lost in between the "Ext SD Card" and the "Internal SD Card." Long story short... my Xoom boots into ICS and runs perfectly fine, but I can't finish the root process. Any help?!
Android File Transfer supports files up to 4gb in size. This may be why you are having trouble transferring files that are 10 gb. At least this is the case in OS X Lion
Sent from my Galaxy Nexus using xda premium
So, I have been having problems with the Bluetooth on my S4 since I got it, and so have some other people based on my research. I am now hearing scattered reports that whatever update AT&T put out (the apps on the SD card update) has solved the problem. I am wondering how hard it would be to look at the update, see what they did, and implement that change on my device somehow? Or, do you think it's heavily tied into other things that wouldn't make it easy? I really don't care about the apps on the SD card and such, but I really need my Bluetooth to work correctly pairing with my vehicle, and I'm getting annoyed that I have had to jump through the hoops I do currently to make it work when the phone is brand new.
As a side note, Windows 7 is telling me it can't find drivers for my phone as well when pairing to my PC via Bluetooth. This also isn't helpful. Possibly not related to the first problem, but has anyone else solved this? I searched around a little and found not much more than "me too" and "same here", but no one really solved how to get it connected properly.
EDIT: I found some information on this update. It looks like the Bluetooth stuff was definitely patched as I suspected. I am still wondering if we can somehow patch this into our phones.
Reference material:
The updater script is HERE which lists Bluetooth a number of times.
Single posts by user Aou posted HERE and HERE also list the Bluetooth changes.
I also found a copy of the update HERE.
So, can I pull the updated stuff from that file and install it on my phone? Or is it more complicated than that?
I use Ford Sync with mine. I have no problems at all.
You may try clearing cache and data on blue tooth. I heard that can solve your problem.
On your pc insall Kies...it will install drivers fir you. Then get rid of Kies...its useless.
Hope this helps
Sent from my SGH-M919 using xda premium
Thanks for the reply. Are you connecting both calls and media audio to your Ford?
A Google search for "Galaxy S4 Bluetooth issues" will show plenty of people having issues, so it's not just my device. Also, this problem has persisted since new, it has NEVER worked right. It has also persisted through multiple ROMs and plenty of wipes and clears. It is an issue in the device itself, hence why the AT&T update fixed it for other people.
Also, not only are the drivers available separate from Kies on Samsung's website (which I use on my laptop), but I do have Kies installed on this PC and it still doesn't work.
Using both media and phone with hyundai premium audio. Syncs contacts and works perfectly every time. Not a single problem with this phone.
I'm not trying to argue that there is something wrong, but there is obviously something different between various manufacturers of vehicles. Here are some threads discussing the problem:
http://forums.androidcentral.com/samsung-galaxy-s4/278206-galaxy-s4-bluetooth.html
http://forums.androidcentral.com/ve...96510-bluetooth-paired-but-not-connected.html
http://forums.androidcentral.com/samsung-galaxy-s4/290639-bluetooth-will-not-auto-connect-car.html
In one of the threads I have read (can't remember which one), at least two people who previously had the problem said the OTA update from AT&T fixed it. That's all I am getting at. I am wondering what it was in the OTA update that fixed it since obviously I am one of the unlucky people who are experiencing this problem.
Maybe I missed it but what's the issue exactly?
Something that's bugging me, and might be your issue also, is when I'm in the car the phone doesn't automatically connect to my car.
I have a 2012 Jeep Liberty equipped with uConnect and everytime I turn my phone on I have to manually select uConnect in the Bluetooth devices list to pair my device. I don't have to reset it up and pair it from scratch but it doesn't automatically pair for some reason.
02CWRX said:
Thanks for the reply. Are you connecting both calls and media audio to your Ford?
A Google search for "Galaxy S4 Bluetooth issues" will show plenty of people having issues, so it's not just my device. Also, this problem has persisted since new, it has NEVER worked right. It has also persisted through multiple ROMs and plenty of wipes and clears. It is an issue in the device itself, hence why the AT&T update fixed it for other people.
Also, not only are the drivers available separate from Kies on Samsung's website (which I use on my laptop), but I do have Kies installed on this PC and it still doesn't work.
Click to expand...
Click to collapse
Yes. Everything works. I just had to delete my S3 from Sync.
I have not had any problems at all.
As far as ur pc goes....dumb question. ..did you restart after installing drivers? Some people forget to do that. Just asking.
Sent from my SGH-M919 using xda premium
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
Saintfyre said:
Maybe I missed it but what's the issue exactly?
Something that's bugging me, and might be your issue also, is when I'm in the car the phone doesn't automatically connect to my car.
I have a 2012 Jeep Liberty equipped with uConnect and everytime I turn my phone on I have to manually select uConnect in the Bluetooth devices list to pair my device. I don't have to reset it up and pair it from scratch but it doesn't automatically pair for some reason.
Click to expand...
Click to collapse
Try deleting cache and data on the Bluetooth
Sent from my SGH-M919 using xda premium
Saintfyre said:
Maybe I missed it but what's the issue exactly?
Something that's bugging me, and might be your issue also, is when I'm in the car the phone doesn't automatically connect to my car.
I have a 2012 Jeep Liberty equipped with uConnect and everytime I turn my phone on I have to manually select uConnect in the Bluetooth devices list to pair my device. I don't have to reset it up and pair it from scratch but it doesn't automatically pair for some reason.
Click to expand...
Click to collapse
This is similar to mine, but not the same. I guess I wasn't very specific, but then again, I'm not trying to solve the problem any other way than seeing the feasibility of porting whatever fix was in the OTA update because I don't believe anything else will fix it. I also contacted the engineering department of the vehicle device and they told me it's a known issue isolated to the Galaxy S4.
Anyway, my phone will reconnect to call audio, but gets stuck connection to media audio and will never connect unless I toggle Bluetooth off then on again. Or, it will connect to call audio, but not re-select the media audio. Everytime I turn off Bluetooth or the car, I have to either re-pair, or toggle it to get it to fully connect. Once it does connect, it's fine.
For what it's worth, the Bluetooth Auto Connect app in the market might fix your issue of automatically re-connecting. Check it out HERE. I had played with this app hoping it would solve my issue by telling it to automatically connect both calling and media audio, but it didn't. Nor did A2DP volume which does similar things. This one can also automatically start an application on connection (for instance I was having it auto start Pandora for me). It also has a feature that can capture your GPS location at the time of disconnect. This means you could get out of your car in a huge parking lot, it captures the GPS location, and you can navigate back to the car later easily. That one can be seen HERE.
Check them out, might fix your problem.
alloycowboy said:
Yes. Everything works. I just had to delete my S3 from Sync.
I have not had any problems at all.
As far as ur pc goes....dumb question. ..did you restart after installing drivers? Some people forget to do that. Just asking.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Yes. Multiple times. Again, Google search "Galaxy S4 Windows 7 drivers" will give you a whole list of people who have the same problem...
Strange thing to note. The phone pairs with my laptop running Windows 7 much better. I can play audio through the laptop from the phone, transfer files, etc. The desktop PC displays a message that says the device "needs troubleshooting". When I do that, it says the driver cannon be found, yet it works ok with my laptop. Very strange.
I think I got a fix for you here.
Saintfyre said:
Maybe I missed it but what's the issue exactly?
Something that's bugging me, and might be your issue also, is when I'm in the car the phone doesn't automatically connect to my car.
I have a 2012 Jeep Liberty equipped with uConnect and everytime I turn my phone on I have to manually select uConnect in the Bluetooth devices list to pair my device. I don't have to reset it up and pair it from scratch but it doesn't automatically pair for some reason.
Click to expand...
Click to collapse
This I can recommend a fix for. I had the same issue with my Clarion aftermarket deck (issue did not occur on my previous Android devices). Google Play Store has an APK called "Bluetooth Auto Connect". This runs as a background process and will fix the issue for you.
\\
Still wondering about extracting whatever they did to the Bluetooth...
Thanks everyone about the recommendation for Bluetooth Auto Connect. Hasn't failed since I installed it, way more convenient now.
Thank you!
Hey guys, I have searched high and low for a solution to this problem but have come up empty so far. I just got a joying head unit and everything, including the easy connected app, seemed to work without issue. I decided well since I had the headunit running next to my pc that I would flash Malaysk's custom rom before installing it. After that, I reinstalled the app from various sources including the oem app but none of them seem to allow me to connect my same exact devices anymore.
Why is this important for me? I had planned on controlling a tablet in the back seat for my son who is still to young to put on show without trouble. Essentially, this would allow me to never have to reach back there to help him out.
I have read, from joying, that it would no longer work after flashing new firmware but that seemed to not be the case from some things I had read here (please correct me if I am wrong on that). Tried different cables and ports but no luck. I did read that a license might need to be carried over but not sure what that entails as I can find ZERO info on this easy connected app/problem. I hope that this is a very simple fix and that I did not jump the gun again for the chance to flash a new device (its addicting and I blame XDA for my problems...).
I did try and find some other apps that might allow me to do the same thing. RemoDroid seemed promising but didn't function. Most other ones are meant for controlling from a pc or browser and just weren't useful for the task at hand. I am open to solid suggestions. I use all Android devices and avoid the Apple juice. Any insight you guys can offer will help a tired Dad out. Thanks!
Edit: Solved-ish
The easy connect app seems to function now intermittently. Not sure there was a specific thing that I did to fix it. Seems to work when I launch easy connect app right after booting up and nothing else. Messing with other apps seems to cause a problem for my devices. Also, switching between my devices(phone and tablet) may also have been causing a problem, not sure yet. I suppose I'll just keep trying to make it work reliably until I break it again.
On the previous version of the easy connect app, you were able to disable Drive Mode from launching. Not so on the newer version with Android WiFi. If anyone has a solution to that I would appreciate it as the Drive Mode app is useless for my needs.
Note 4 - USB - works great. I have yet to try over wifi
Note 10.1 N8013(lollipop rom) - USB/Wifi - works great (disable smooth mode, remote device screen cannot be turned on with easy connect "Home" button)
http://forum.xda-developers.com/and...1024x600-rk3188-joying-try-uploading-t3262030
I tried several different apk's but they all have similar results and end with a connection failure.
I haven't yet tried going back to stock firmware so that might be worth trying. I installed the headunit in my car so I'm not as willing to keep flashin it as I have to park down the street from my house.
So not sure what magic I used but I was able to get it working for a moment and then it stopped again. USB and Wifi android mirroring were working so I know my current firmware/setup is functional!! Once I got it working I started configuring some other apps and when I went to run it again it wasn't connecting. I guess I'll just keep messing with it until I can figure out what got it working again.
With the newer version of the easy connected app, I can no longer disable launching of drive mode on connect. Is there a way to disable that option with the 1.4 version?
Hi.
Is it possible mirror in wifi with android?
Can you explain the way?
Inviato dal mio SM-G920F utilizzando Tapatalk
Hi everyone,
I am a big fan of Samsung, especially, note series. I am using two devices same time included: Note 10+, Note 9. I updated software in both of them last week. Everything is ok so far but I encounter the big issues of cable to connect PC.
I can not use my original cable (type C to C) to connect my phone to PC. It had worked before the software updated. I tried to reinstall drivers or Samsung DEX but nothing changed so far. This problem happened not only in my Note 10+ but it also happened in my Note 9.
Besides, I tried with my USC 3.1 to C, USB 2.0 to C result in one of them work which is USB3.1 to C. It means the communication between Mobile and PC is operated via USB3.1 only. I try to find more information about these issues.
I really need your advice now, guys. Please give me some ideas or way I can fix this problem. Does also anyone have same problems with me??
Look at the error messages on the PC.
Clear the cache on the 10+'s boot menu.
Check all related settings on both machines.
If everything's running well and stable... I avoid updates.
blackhawk said:
Look at the error messages on the PC.
Clear the cache on the 10+'s boot menu.
Check all related settings on both machines.
If everything's running well and stable... I avoid updates.
Click to expand...
Click to collapse
Tks your advice. The problem is my PC didn't recognize my phone like it used to do. Nothing happened when I connect my phone to the PC via type C-type-C(USB 3.1 gen 2 to type C) or USB 2.0-TypeC. I used a USB viewer to check the connection, however, the result is negative. Otherwise, the connection works normally when I use USB 3.1 gen 1 to type C, USB viewer also can detect the connection from the phone.
Stephen NG said:
Tks your advice. The problem is my PC didn't recognize my phone like it used to do. Nothing happened when I connect my phone to the PC via type C-type-C(USB 3.1 gen 2 to type C) or USB 2.0-TypeC. I used a USB viewer to check the connection, however, the result is negative. Otherwise, the connection works normally when I use USB 3.1 gen 1 to type C, USB viewer also can detect the connection from the phone.
Click to expand...
Click to collapse
I haven't played with this yet... as I expect the same fun you're having:laugh:
Bad or wrong cable or maybe a driver issue.
Maybe missing MS libraries (side by side errors is always that).
Use the MS Event viewer to see the errors.
Maybe reload the driver(s). The correct driver may be bundle in other Samsung PC apps you haven't installed.
Make sure the phone USB is correctly configured in Developer Options .
blackhawk said:
I haven't played with this yet... as I expect the same fun you're having:laugh:
Bad or wrong cable or maybe a driver issue.
Maybe missing MS libraries (side by side errors is always that).
Use the MS Event viewer to see the errors.
Maybe reload the driver(s). The correct driver may be bundle in other Samsung PC apps you haven't installed.
Make sure the phone USB is correctly configured in Developer Options .
Click to expand...
Click to collapse
I tried all of your recommendations above, however, nothing works until now. I tried to contact supporters from Samsung and other Samsung android. I recognized the problem only happened in Exynos devices. Somebody in the Vietnamese forum had the same issues as me and his devices are also using Exynox.
So that anyone in this forum has experienced that problem please confirm in this forum for tracking. I figured out the technology inside this problem which is my phone can not use D+/D- from USB 2.0 anymore. I do not know that problem occurred due to Firmware or Hardware falures. Try to find something is useful, and recommendation from you guys. Thanks and have a nice day.
Stephen NG said:
I tried all of your recommendations above, however, nothing works until now. I tried to contact supporters from Samsung and other Samsung android. I recognized the problem only happened in Exynos devices. Somebody in the Vietnamese forum had the same issues as me and his devices are also using Exynox.
So that anyone in this forum has experienced that problem please confirm in this forum for tracking. I figured out the technology inside this problem which is my phone can not use D+/D- from USB 2.0 anymore. I do not know that problem occurred idue to Firmware or Hardware falures. Try to find something is useful, and recommendation from you guys. Thanks and have a nice day.
Click to expand...
Click to collapse
Is Windows Event Viewer showing any error messages when you try to connect?
blackhawk said:
Is Windows Event Viewer showing any error messages when you try to connect?
Click to expand...
Click to collapse
Nothing happened, I think somehow my note 10 plus D+/D- of USB were dead which result in PC can not detect the signal. I tried to use USB cable to test the resistor in D+/D-. The result is OL(in VOM). In my opinion, somehow firmware affects my D+/D- ports which cause the lost connection. I got it from the last update firmware from official Samsung. Before that, everything goes right, stable connection to pc, stable charge with the adapter.
Stephen NG said:
I tried all of your recommendations above, however, nothing works until now. I tried to contact supporters from Samsung and other Samsung android. I recognized the problem only happened in Exynos devices. Somebody in the Vietnamese forum had the same issues as me and his devices are also using Exynox.
So that anyone in this forum has experienced that problem please confirm in this forum for tracking. I figured out the technology inside this problem which is my phone can not use D+/D- from USB 2.0 anymore. I do not know that problem occurred due to Firmware or Hardware falures. Try to find something is useful, and recommendation from you guys. Thanks and have a nice day.
Click to expand...
Click to collapse
Stephen NG said:
Nothing happened, I think somehow my note 10 plus D+/D- of USB were dead which result in PC can not detect the signal. I tried to use USB cable to test the resistor in D+/D-. The result is OL(in VOM). In my opinion, somehow firmware affects my D+/D- ports which cause the lost connection. I got it from the last update firmware from official Samsung. Before that, everything goes right, stable connection to pc, stable charge with the adapter.
Click to expand...
Click to collapse
Try a known good cable. Try another PC for clues of the root cause.
It could still be a setting or apk issue in the Samsung; of course it could be completely the firmware.
Even if the PC sees/doesn't see the connection being made it could still be a driver issue there.
Event Viewer has it's limits but was a good starting point. I had a similar issue with a PC USB driver and it was a real time consuming pain. After rolling back drivers multiple times and many reboots latter, it worked.
Keep googling and playing with it... you'll find it.
Once I have a fast,stable platform that's running well I rarely update.
Tired of MS, Android, Samsung, AT&T, etc screwing up my OS loads. Malware, Trojans, viruses, etc. have cost me one OS load max in 16 years even on very outdated OSs.
None on Android that required a reload... not one in 6+ years.
Of course it can happen but it's obvious that for me that most times updates/upgrades are the real malware:laugh:
Stephen NG said:
I tried all of your recommendations above, however, nothing works until now. I tried to contact supporters from Samsung and other Samsung android. I recognized the problem only happened in Exynos devices. Somebody in the Vietnamese forum had the same issues as me and his devices are also using Exynox.
So that anyone in this forum has experienced that problem please confirm in this forum for tracking. I figured out the technology inside this problem which is my phone can not use D+/D- from USB 2.0 anymore. I do not know that problem occurred due to Firmware or Hardware falures. Try to find something is useful, and recommendation from you guys. Thanks and have a nice day.
Click to expand...
Click to collapse
I have the same problem on exynos note 10 plus 5g! Have solved yet?
Meh... Rule #1, if your Android OS is running fast, stable and fulfilling its mission, let it be.
My 10+ hasn't been updated in over a year and a half. Current OS load is over a year old still fast and very stable with little maintenance needed.
Security has not been an issue.
The easiest fix, now, would be to flash the firmware* that was working.
If that doesn't work the C port PCB may have failed. I would suspect that before a mobo failure.
*during production run Samsung will substitute chipsets as supply demands. This may lead to firmware updates being incompatible if the correct instruction set is omitted and/or incompatible for those chipset(s).
Yes this happens and worse Samsung has to physically examine the phone to determine precisely which chipset was used. Then Samsung engineers can hopefully rewrite the firmware to be compatible with all devices... or replace the chipset(s)
blackhawk said:
Meh... Rule #1, if your Android OS is running fast, stable and fulfilling its mission, let it be.
My 10+ hasn't been updated in over a year and a half. Current OS load is over a year old still fast and very stable with little maintenance needed.
Security has not been an issue.
The easiest fix, now, would be to flash the firmware* that was working.
If that doesn't work the C port PCB may have failed. I would suspect that before a mobo failure.
*during production run Samsung will substitute chipsets as supply demands. This may lead to firmware updates being incompatible if the correct instruction set is omitted and/or incompatible for those chipset(s).
Yes this happens and worse Samsung has to physically examine the phone to determine precisely which chipset was used. Then Samsung engineers can hopefully rewrite the firmware to be compatible with all devices... or replace the chipset(s)
Click to expand...
Click to collapse
Don't u think ur software is half-baked if u r on December 2020 patch android 10? My phone restarts randomly and some of the features don't even work!
Vicky078 said:
Don't u think ur software is half-baked if u r on December 2020 patch android 10? My phone restarts randomly and some of the features don't even work!
Click to expand...
Click to collapse
If you haven't done a factory reset, do so. It won't run right until you do. Do not use SmartSwitch.
I'm thankfully still running Pie. Still have overlay support for trusted apks. Karma Firewall's valuable logging feature is fully functional as well.
Google went Apple insane with scoped storage starting with 10 and has been in a high G flat spin ever since. Rather than cut to idle and recover they jam it into the afterburner indent like a rank G-Loc rookie. 12 is going wet
It's one reason I didn't buy the 20U.
Hello All,
I'm new to this forum, so I'm not really sure if this should be general, dev, or just a technical question. Also I'm a software dev, but am not too familiar with android other than lightly using Android Studio for app dev.
Basically my problem comes down to this. I use a custom OpenWrt device as an ethernet dongle for my laptops by loading the g_ether driver. I would like to do this for an android phone as well. Right now I'm trying the s20 and s22 (pretty sure whatever solution I come to will work for both); however, when I plug my dongle in, the phone will see the dongle with all the correct device descriptors and all that, but will not connect and attempt to get an IP.
My current guess is that the phone just doesn't have the right drivers on there (cdc_ether or cdc_subset), or that it is not loading them.
Thus far I've tried poking around with termux, but have not gotten too far. I was hoping this community may be able to help me figure out how to get the phone to use the dongle.
Lastly, would really rather not root the phone unless completely necessary.
Thank you all for any advice!