Related
Everytime I connect my phone via USB cable to my PC it mounts the SD card in USB Storage mode.
Its not a deal breaker but definitely can be an inconvenience when trying to use the phone while charging on a PC (which is how I use my phone at work).
Anyone else run into and find a fix for this?
I kinda remember seeing someone mention a weird solution to a similar problem (maybe regarding PC charging?) that entailed changing the screen timeout.
Phone Info:
Droid 2
ROM: Fission 1.1 (installed last night over a freshly SBF-ed phone)
I see at least one other person is experiencing this:
http://forum.xda-developers.com/showpost.php?p=8747858&postcount=56
Tried swapping out SD card for a freshly formatted one and still seeing the same issue. So I'm going to rule out the SD card being at fault.
aplus01 said:
Everytime I connect my phone via USB cable to my PC it mounts the SD card in USB Storage mode.
Its not a deal breaker but definitely can be an inconvenience when trying to use the phone while charging on a PC (which is how I use my phone at work).
Anyone else run into and find a fix for this?
I kinda remember seeing someone mention a weird solution to a similar problem (maybe regarding PC charging?) that entailed changing the screen timeout.
Phone Info:
Droid 2
ROM: Fission 1.1 (installed last night over a freshly SBF-ed phone)
I see at least one other person is experiencing this:
http://forum.xda-developers.com/showpost.php?p=8747858&postcount=56
Tried swapping out SD card for a freshly formatted one and still seeing the same issue. So I'm going to rule out the SD card being at fault.
Click to expand...
Click to collapse
AngDroid, part of the development team (Team DeFuse), has asked that bugs in regards to the fission rom be posted at Droid Life. It is hard for the team to manage multiple forums. Please make a post here :http://forum.droid-life.com/viewforum.php?f=61&sid=799e04fe62c2af5a7682b052087fe5aa and you will have a greater chance at getting a resolution.
I had this problem this weekend, but I'm running the stock ROM.
Some googling didn't turn up much, other than that certain programs would cause this, none of which I had. If i had the original link I'd post it. I think i read a lot about it on the Incredible forums here.. maybe?
Anyway, the only thing I had changed recently was installing Winamp.
It turned out that it was indeed Winamp. Uninstalled it and all works fine now.
Grrr! Wish I had checked this sooner. I rolled back to a nandroid backup. I was getting so fed up with it not working correctly. Glad to know it wasn't the Fission ROM. Though I kinda didn't think it was since I was having that issue even before going from the beta to 1.1.
Oh well, guess I'll try it again later. Tired of going through settings for apps. For now.
Thanks for the response, Lithoss.
Wonder if the winamp team knows their app prevents charging the Droid 2 via PC? It's a great app otherwise.
theecho said:
AngDroid, part of the development team (Team DeFuse), has asked that bugs in regards to the fission rom be posted at Droid Life. It is hard for the team to manage multiple forums. Please make a post here :http://forum.droid-life.com/viewforum.php?f=61&sid=799e04fe62c2af5a7682b052087fe5aa and you will have a greater chance at getting a resolution.
Click to expand...
Click to collapse
Thanks for the heads up. Didn't know the official Fission rom forum was on droid-life. Will have to bookmark that.
aplus01 said:
Grrr! Wish I had checked this sooner. I rolled back to a nandroid backup. I was getting so fed up with it not working correctly. Glad to know it wasn't the Fission ROM. Though I kinda didn't think it was since I was having that issue even before going from the beta to 1.1.
Oh well, guess I'll try it again later. Tired of going through settings for apps. For now.
Thanks for the response, Lithoss.
Wonder if the winamp team knows their app prevents charging the Droid 2 via PC? It's a great app otherwise.
Click to expand...
Click to collapse
No problem.
I dont think it prevents charging.... it just mounts it too when it shouldn't.
I emailed them about it through the link in the market.. so if they read their email they should know
You're right. It does charge properly. It doesn't allow access to SD card resources though. Which means no podcasts while hooked up via USB. Deal breaker!
Hope they get it figured out soon. That was a pretty sweet interface. I liked it better than cubed (^3).
Lithoss said:
No problem.
I dont think it prevents charging.... it just mounts it too when it shouldn't.
I emailed them about it through the link in the market.. so if they read their email they should know
Click to expand...
Click to collapse
This is toggleable behavior. Check the settings in winamp and you will see something to the effect of automatically mount SD card when connected. If you uncheck that, it shouldn't do it...
@natez0r - Thanks for the explanation. Guess this time it really is a feature and not a bug!
Guess I'll give winamp another shot since that "feature" can be turned off.
natez0r said:
This is toggleable behavior. Check the settings in winamp and you will see something to the effect of automatically mount SD card when connected. If you uncheck that, it shouldn't do it...
Click to expand...
Click to collapse
What is the point of this option? seems pretty useless to me...
Please put [SOLVED] in your thread title. Thanks
Roger that!
Can I close this?
Lithoss said:
What is the point of this option? seems pretty useless to me...
Click to expand...
Click to collapse
If I were to guess, it would be for making it easier to sync with winamp when you plug the phone into your computer. DoubleTwist also has this option, but i feel like it is more of a nuisance than anything.
@theimpaler747 - Yes, my question is answered.
aplus01 said:
@theimpaler747 - Yes, my question is answered.
Click to expand...
Click to collapse
Cool, I'll close it
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...
BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists
When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta
Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.
tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post
thats happens cause you probable have another android service on your machine, bluestacks is the most used. just check if you have more than one phone plugged, remember to disable/close all others emulators, remove and plug again your phone, if it persist, reboot your machine and try agian.
rafaelsartori said:
thats happens cause you probable have another android service on your machine, bluestacks is the most used. just check if you have more than one phone plugged, remember to disable/close all others emulators, remove and plug again your phone, if it persist, reboot your machine and try agian.
Click to expand...
Click to collapse
Just go to your task manager and kill adb.exe
Should clear that right up.
This is more of a General Android questions then a G2 Question.
Barsky said:
Just go to your task manager and kill adb.exe
Should clear that right up.
Click to expand...
Click to collapse
killing adb do not solve in this case.
and i post this here cause i have an G2 and it happens with me now, but of course, it can happen with any other phone, and i want to help people using the same phone as i have, i cant help all people of xda, just making my job.
rafaelsartori said:
killing adb do not solve in this case.
and i post this here cause i have an G2 and it happens with me now, but of course, it can happen with any other phone, and i want to help people using the same phone as i have, i cant help all people of xda, just making my job.
Click to expand...
Click to collapse
Bummer. Always has for me. Perhaps completely uninstalling the LG drivers and reinstalling them would help...but I am just stabbing in the dark, now.
Barsky said:
Bummer. Always has for me. Perhaps completely uninstalling the LG drivers and reinstalling them would help...but I am just stabbing in the dark, now.
Click to expand...
Click to collapse
the case i explain here, will have more then one emulator, no mater how many times you uninstall/install the drivers, no mater how many times you remove and start adb.exe again, you will always have more than one emulator.
my intention was just warn people to check if they have bluestack or any other kind of emulator opened, in my personal case, i use bluestack for whatsapp and hay day on my pc, and just remembered that bluestack is an emulator after many hours trying to fix, but theres nothing to be fixed in this case, just close bluestacks, do whatever you need to do, and open it again.
Got this strange problem. Every time when I connect G4 with my Win7 PC via USB, the "Moto G(4)" icon shows up but it is empty under it. I will have to go to the Developer options to click on MTP again (even it is already set to MTP) to show the internal storage. This is really annoying extra step. Anyone knows what is the problem and how to fix it? Thanks.
[Update] Finally got it worked by following this thread:
http://forum.xda-developers.com/xposed/modules/mod-usb-marshmallow-1-0-t3272072
myasus said:
Got this strange problem. Every time when I connect G4 with my Win7 PC via USB, the "Moto G(4)" icon shows up but it is empty under it. I will have to go to the Developer options to click on MTP again (even it is already set to MTP) to show the internal storage. This is really annoying extra step. Anyone knows what is the problem and how to fix it? Thanks.
Click to expand...
Click to collapse
That setting in the developer options doesn't do anything. Every time you plug it in, it will default to charging and you have to click MTP in the notification. It was that way in the G3 also.
Tel864 said:
That setting in the developer options doesn't do anything. Every time you plug it in, it will default to charging and you have to click MTP in the notification. It was that way in the G3 also.
Click to expand...
Click to collapse
This is really annoying. Is there anyway to change it defaulted to MTP?
myasus said:
This is really annoying. Is there anyway to change it defaulted to MTP?
Click to expand...
Click to collapse
Not that I know of. I've done it so often on the G3 and now the G4 that it's habit.
Tel864 said:
Not that I know of. I've done it so often on the G3 and now the G4 that it's habit.
Click to expand...
Click to collapse
Finally got it worked by following this thread:
http://forum.xda-developers.com/xposed/modules/mod-usb-marshmallow-1-0-t3272072
myasus said:
Finally got it worked by following this thread:
http://forum.xda-developers.com/xposed/modules/mod-usb-marshmallow-1-0-t3272072
Click to expand...
Click to collapse
OK, I didn't know you were rooted.
It is a new security feature of Android since lolipop. It is to prevent malware on your pc targeting android connected phones. So that if you were charging it couldn't switch to connect storage without explicit approval on the phone itself.
Anyone know of any apps that would turn the hot spot on and off based off of a Bluetooth connection? I can't seem to find anything and I'm wondering if it's just not possible with this phone. I'm hoping it's not something that needs root to enable.
devlop said:
Anyone know of any apps that would turn the hot spot on and off based off of a Bluetooth connection? I can't seem to find anything and I'm wondering if it's just not possible with this phone. I'm hoping it's not something that needs root to enable.
Click to expand...
Click to collapse
Have you looked into Tasker? I don't know if you can do it but I see a lot of people doing crazy things with it.
Javiggan69 said:
Have you looked into Tasker? I don't know if you can do it but I see a lot of people doing crazy things with it.
Click to expand...
Click to collapse
I did buy the app years ago, but never learned how to use it. Might need to do some searching, see if someone has done it out knows how to.
devlop said:
Anyone know of any apps that would turn the hot spot on and off based off of a Bluetooth connection? I can't seem to find anything and I'm wondering if it's just not possible with this phone. I'm hoping it's not something that needs root to enable.
Click to expand...
Click to collapse
devlop said:
I did buy the app years ago, but never learned how to use it. Might need to do some searching, see if someone has done it out knows how to.
Click to expand...
Click to collapse
Don't worry it happen to me. Its very complex app.
bumping to see if anyone found anything that worked? I have been on a search and nothing seems to work. I was pointed to this post on Google+
https://groups.google.com/forum/#!topic/tasker/q5uSgqtwBkY
I wanted to have a shortcut on my home to turn on and off hotspot but as a Verizon customers, I can not do that, I tried 10 different apps none of them worked, here is why
Verizon added a hook into hotspot functionality that check for subscription, so if you turn it on, it will check if you are eligible for hotspot (I am) and only then will turn the hotspot on, but while it check it turn it back off (so all the apps , I guess get confused, they turn it on, but it turned off immediately)
Click to expand...
Click to collapse
This is probably why a simple toggle in Tasker does not work.
I tried the settings as listed there, and still couldn't get it to work