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
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
danvee said:
Just the tip of the iceberg.
With the exception of your #3, most users won't see the issues that you've listed.
Check this thread out - an interesting read ....
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[1-25-false]
Click to expand...
Click to collapse
You are correct. I did not want to overload the list.
I too have had the random freezes and occasional reboots.
I have something to add here. I keep my nexus 7.2 (2013) in a moko case and often use it with the case folded back all the way. When the freezes occur, I noticed that if I move the case cover slightly away, the freeze stops, and when I bring it back, it freezes again. So, in my opinion, the freezing is magnet related. If so, a weaker magnet or more back padding might help with that. I've had no freezing when I use the Nexus out of the case. Have not yet tried additional shielding.
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
beware of the "the problems only represent a small vocal group blah blah" posts you'll get. I ended up returning mine to best buy for good today. I couldn't find myself dealing with and trying to replace this unit x amount of times to get a properly working one. Back to the drawing board I go.
I don't think any other device in the history of Android devices I've owned has a more 'vocal' group of problems in the General/A&A forums. It's ridiculous how bad the quality control for this tablet is.
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Anderson2 said:
I hope it is OK to start such a general thread and that this is the correct sub forum for it.
I am an owner of a 2012 Nexus 7 who also purchased the 2013 Nexus 7. While there are many improvements in the new 2013 nexus 7 (speed, display, etc.) there seem to also be frustrating problems that a number of users (including myself) have all encountered with no satisfactory solution resulting in much wasted time. I thought it would be useful to put them together in one thread and see what they may possibly have in common.
1. Usb connection to a pc. The device is not recognized to permit usb file transfers. Many potential solutions have been suggested (mtp/ptp off/on, usb debugging off/on, etc.) but these have not worked for me and many others.
(Potential work around: flash stick and stickmount work for me for file transfers. Another slower method is wifi transfer using ES Explorer, or email attachments).
2. Adb device is not recognized when using WugFresh toolkit. Faulty drivers, user error, etc have been blamed. I've tried them all with no benefit. Still can't get the Nexus recognized despite numerous attempts and methods.
(I'm no expert but I suspect the problem is probably related to #1. The pc cannot detect the adb device in those cases because it cannot detect the Nexus in the first place).
3. GPS problems. Supposedly helped (or worsened) by latest update. Don't know because I don't use GPS much and have not installed the latest OTA update, afraid it will mess up my root and I won't be able to get WugFresh to detect the Nexus again. (Took me days of attempts the first time).
There are probably other problems but the above are the most common ones.
If the moderators agree, I think this thread might be useful.
Click to expand...
Click to collapse
albundy2010 said:
Try a different USB cable / port.
And toolkits are lame. Use fastboot.
Click to expand...
Click to collapse
Used a different cable, different pc, different port. No difference.
I would use fastboot but am a newbie and it is over my head to do that. Afraid I'll really mess things up.
gogol said:
I experienced #1 with my original N7.
And that was USB driver issue. I fixed it by, really, removing all kind of drivers that are on my pc (Win7 64).
I remember uninstall all the drivers as well from the device manager, right click uninstall.
I tried removing drivers from WugFresh and it did not work.
Then #2, I managed to use the PDAnet driver.
Now, it's working for both MTP and ADB
Click to expand...
Click to collapse
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
sfhub said:
#1 and #2 have to do with older drivers confusing your installation. If you work on it, almost everyone that has posted has eventually gotten both to work.
#3 GPS issue is fixed. There's an update you can use to just get the GPS fix and nothing else, no OS upgrade, no loss of data, etc.
http://forum.xda-developers.com/showthread.php?t=2421373
Click to expand...
Click to collapse
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Anderson2 said:
I've been working on it for several days now. Hours and hours of wasted frustrating time. Tried everything suggested (which may be part of the problem). Need someone to talk me through it once. There really should be a direct download of the necessary windows 7 drivers I could just download and install on the pc and solve the problem.
#3 I'm rooted with stock rom. I don't use GPS much so that is not a major problem.
The major problem is that though I'm rooted I can't do a Nandroid backup and without it it's scary for a newbie to do anything that could mess things even further. Took me days to get WugFresh's adb recognized and finally root in a few minutes after that.
"Wish you were here...... "
Click to expand...
Click to collapse
Hmm you could download the goomanager app and then install TWRP, by then you can do a nandroid backup without any hassle.
Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
You can install the PDAnet driver from WugFresh. It's option no. 3 if I am not mistaken.
Anderson2 said:
#1 I believe the Nexus connected fine before I used WugFresh which made me uninstall a bunch of drivers. I now think maybe I uninstalled some essential driver but have no way to restore things because the restores don't go back far enough.
#2 where do I get the PDAnet driver?
Click to expand...
Click to collapse
Update : SUCCESS!!
It was the cable stupid!
I can't believe the hours I wasted because of this stupid cable. This must be the cable I had used when I finally successfully rooted the Nexus after multiple tries (including different cables, etc). I own several USB cables and in my hours and days of trying to get this to work I went through them all at one time or another.
I now labeled this cable as the one to use for connecting between the Nexus and the PC. It is hard to believe that a cable could make that much difference! I was of course aware that the cable could be a problem but this much of a problem?! Unbelievable. What could be so different with this Asus cable? What could be missing in the other cables?
For the record this is the cable that came with the original Nexus 7 charger. Now I have it labeled to avoid going through all this again.
I'm one happy camper! You guys have no idea how frustrating it is to follow every ones advice and still have no success. You start to feel really stupid.
Thank you all for your wonderful and patient support. You guys (and gals) are great. Sorry to have wasted your time too.
Hey guys, really need help here. Honest noob here so please try to understand my situation. I updated to Windows 8.1 to see what were the changes but unfortunately I realised I didn't have my activation key, so I decided to use a program called Windows 8.1 Key Finder Ultimate just to see all the features before buying the key ( I don't have money, I'm just a poor student)
So I installed it, and clicked on it. Then it prompted me to install again, which I found peculiar. So I scanned the exe and nothing was wrong. I installed the thing and tried to run it, but it did the same thing so I tried KMS activators instead. From KMSAuto Pro to KMSPico, nothing worked. Something I did along the way triggered a sound driver to install, and it definitely wasn't a Realtek driver, which is my soundcard manufacturer. I didn't really pay much attention as it was 2-3am, and I assumed it would just stop installing due to conflicts with the real driver.
Decided to sleep, went to school at 7, came back home and decided to turn on my laptop to listen to my new CD. No sound. I assumed its just WMP having issues with the CD, so I tried my other players. Nothing! Decided I should try to see the speaker settings and check vol. etc but I can't play any test tone, with the computer telling me "Failed to play test tone". I panicked for awhile but went on a solution hunt. I tried everything from a clean boot to driver update to uninstall then install, disabling audio and re-enabling, so many and nothing works. Five hours later I'm here desparate to find answers from the gurus. (I realised I have no restore points, which is really idiotic of me...)
I remembered the sound driver that installed itself, so I intended to find it and murder it. But being the noob I am, I don't know how to find the right thing in event logs and all the mumbo jumbo. Is there a way to see what changed recently, or installed recently (not only programs) or even what was running a certain periods of time (don't say task manager because I'm not looking for what's running but rather what RAN). Also, are there any ways to see all drivers installed apart from device manager and isolate them to diagnose the issue at hand?
Any solutions provided to me is greatly appreciated, and should be free is possible. I don't have any money on me and I can't find a job to support myself due to school, so please understand that this laptop is really valuable to me and I need all the help I can find here. If any other detail is needed I'd gladly provide them. And please don't condone me for my mistake and stuff, I'm still learning as I go along...
syngamer96 said:
Hey guys, really need help here. Honest noob here so please try to understand my situation. I updated to Windows 8.1 to see what were the changes but unfortunately I realised I didn't have my activation key, so I decided to use a program called Windows 8.1 Key Finder Ultimate just to see all the features before buying the key ( I don't have money, I'm just a poor student)
So I installed it, and clicked on it. Then it prompted me to install again, which I found peculiar. So I scanned the exe and nothing was wrong. I installed the thing and tried to run it, but it did the same thing so I tried KMS activators instead. From KMSAuto Pro to KMSPico, nothing worked. Something I did along the way triggered a sound driver to install, and it definitely wasn't a Realtek driver, which is my soundcard manufacturer. I didn't really pay much attention as it was 2-3am, and I assumed it would just stop installing due to conflicts with the real driver.
Decided to sleep, went to school at 7, came back home and decided to turn on my laptop to listen to my new CD. No sound. I assumed its just WMP having issues with the CD, so I tried my other players. Nothing! Decided I should try to see the speaker settings and check vol. etc but I can't play any test tone, with the computer telling me "Failed to play test tone". I panicked for awhile but went on a solution hunt. I tried everything from a clean boot to driver update to uninstall then install, disabling audio and re-enabling, so many and nothing works. Five hours later I'm here desparate to find answers from the gurus. (I realised I have no restore points, which is really idiotic of me...)
I remembered the sound driver that installed itself, so I intended to find it and murder it. But being the noob I am, I don't know how to find the right thing in event logs and all the mumbo jumbo. Is there a way to see what changed recently, or installed recently (not only programs) or even what was running a certain periods of time (don't say task manager because I'm not looking for what's running but rather what RAN). Also, are there any ways to see all drivers installed apart from device manager and isolate them to diagnose the issue at hand?
Any solutions provided to me is greatly appreciated, and should be free is possible. I don't have any money on me and I can't find a job to support myself due to school, so please understand that this laptop is really valuable to me and I need all the help I can find here. If any other detail is needed I'd gladly provide them. And please don't condone me for my mistake and stuff, I'm still learning as I go along...
Click to expand...
Click to collapse
You can use the reliability monitor under control panel >system and security>action center >maintenance to see a nice time line of events.
If you have a key for windows 8, you can easily and freely update to windows 8.1 using the store (you have to install all windows 8 updates first).
It is best to avoid using fishy .exes because they can damage your windows install and even install mallware.
This is in other phones forums also. Can anyone come up with a solution for this? I absolutely do not want my phone "connecting as installer" when I plug it into my computer. I tried the option in 8#0808# and selecting MTP + ADB, but it doesn't survive a reboot.
Haaaalp.
scriz said:
This is in other phones forums also. Can anyone come up with a solution for this? I absolutely do not want my phone "connecting as installer" when I plug it into my computer. I tried the option in 8#0808# and selecting MTP + ADB, but it doesn't survive a reboot.
Haaaalp.
Click to expand...
Click to collapse
I have been having this happen too. I wonder if the Root caused that to glitch to where it won't save as a MTP, but as an Installer...
I would like this fixed too, maybe even with the option to default to USB 3. Is it only our phone model with verizon crap doing this, or is it all models?
I imagine someone could at least make an xposed module to do this.
Spedkiller said:
I would like this fixed too, maybe even with the option to default to USB 3. Is it only our phone model with verizon crap doing this, or is it all models?
I imagine someone could at least make an xposed module to do this.
Click to expand...
Click to collapse
It is only ours, and it is really pissing me off too. I deleted the .iso file /system/etc and it still keeps doing it. Searched the forum, the entire internet too and no good answer that works for our phone. Someone please PM me if you figure out a way. Might have to be a smali edit
Guess no one has looked into this.