Just wondering if anyone else is having this issue.
After waiting for the VF 2.2 OTA update, it finally arrived yesterday morning. Great. Except now ADB doesn't detect the phone.
Plugging it in, putting it in debug mode etc and going trying ADB devices shows an empty list. Putting the phone in recovery and trying fastboot devices shows it with no problems.
If I plug in my HTC Magic (on 2.1-update1) and my Nexus One, adb shows only the Magic in the device list. ddms also doesn't detect the N1 but does detect the Magic without any problems.
I've tried reinstalling the driver, reinstalling the whole SDK, installing all updates, doing a factory reset on the device and everything else I can think of. Nothing seems to fix this issue. It's been logged in the android bug tracker, but not many people seem to be having the issue. The bug is here: http ://code.google.com/p/android/issues/detail?id=9437 (sorry had to break it up because I'm not allowed to post links yet)
I'm not sure if this has anything to do with Windows 7, but from searching it seems there have been other issues with W7 and the N1 when using adb.
What I just don't get is that it's only affecting a few people. What could be so different about my N1 that's causing this and not causing it for almost everyone else? It makes no sense to me.
Having the same issue. I put an issue in http: //forum.xda-developers.com/showpost.php?p=7636799&postcount=129.
Tried ADB with a HTC Legend. No problem. But on my Nexus ONE the ADB don't announce itself on the USB bus.
Just to make sure; USB Debugging is enabled in the phone, right?
Yepp. USB debugging is on.
Sent from my Nexus One using XDA App
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone
Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.
I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.
TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.
Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?
Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"
Thanks, but links are broken.
Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)
And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...
My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.
So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.
lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?
It just started when I was trying to transfer files from my phone to win7.
It does it every time too:
When I connect the phone and the 'USB connection' window pops up, only 2 programs force close, Lookout and Folder Organizer. They do not force close if I connect using PC Mode, Windows Media Sync, or Charge Only. Just with USB Mass Storage, and it is consistent and always only those 2 programs. I took about 5 screenshots of logs while it was happening that I put in a zip if anyone can understand them. I am amazed how much log material there is even for one minute of time...
I am rooted, Eclipse 3. and those 2 programs have been installed for a few days with connections to the pc going without FC's.
Thank you
richsapf said:
It just started when I was trying to transfer files from my phone to win7.
It does it every time too:
When I connect the phone and the 'USB connection' window pops up, only 2 programs force close, Lookout and Folder Organizer. They do not force close if I connect using PC Mode, Windows Media Sync, or Charge Only. Just with USB Mass Storage, and it is consistent and always only those 2 programs. I took about 5 screenshots of logs while it was happening that I put in a zip if anyone can understand them. I am amazed how much log material there is even for one minute of time...
I am rooted, Eclipse 3. and those 2 programs have been installed for a few days with connections to the pc going without FC's.
Thank you
Click to expand...
Click to collapse
It's because the apps are running from the scars and when you mount it with windows your phone can't see it anymore
Hi Willis...thank u so much... did you know that from experience or did the logs indicate that?.. I could have sworn those were installed on main phone...odd.. because I have had both those programs for years each time I flash a rom.... I will move them...why didn't all the other apps on the sdcard fc? Just curious. So what lines in the log would indicate a fc. I briefly scanned them but could not fully understand them.
Rich
richsapf said:
Hi Willis...thank u so much... did you know that from experience or did the logs indicate that?.. I could have sworn those were installed on main phone...odd.. because I have had both those programs for years each time I flash a rom.... I will move them...why didn't all the other apps on the sdcard fc? Just curious. So what lines in the log would indicate a fc. I briefly scanned them but could not fully understand them.
Rich
Click to expand...
Click to collapse
just from experience/problem solving/troubleshooting as well the fact that you mention everything works fine until you mount your sdcard as a mass storage device. Your logs indicated "unknown resources" when launching an app although I do some some dalvik permission errors after that which seems a little off but the resources are unknown/not found because they are removed from your phone when the card is mounted in the computer instead of the phone
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.
UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.
Hey guys, I've searched endlessly online and can't seem to figure out what the problem is. It's not the "optimize battery settings", that's where most of the guides online start with. I've checked the data savings settings and from what I can find there is nothing wrong there either.
I keep android web messages and the whatsapp pc app open on my computer all day so I can coordinate with my guys at work.. but the pc apps keep getting disconnected. I have an odd feeling it has something to do with a wifi timeout, but I can't find any settings for it.
In order to get them to come back alive I have to unlock my phone and open either the whatsapp or android messages.
This is a very recent problem within the past week or two I would say. I don't have any app killing managers or anything like that installed either.
If anyone has any insight I'd greatly appreciate it - thank you!
I've the same problem and already tried to exclude WhatsApp from battery optimizations. I have raised the concern with the support team. I don't think it's related to Wifi connection as it gets connected as soon as WhatsApp is opened on phone. But I've never thought it this way so will try to troubleshoot more now and get back to you.
Hope someone else have a solution.
Sent from my SM-N960F using Tapatalk
krash2k said:
Hey guys, I've searched endlessly online and can't seem to figure out what the problem is. It's not the "optimize battery settings", that's where most of the guides online start with. I've checked the data savings settings and from what I can find there is nothing wrong there either.
I keep android web messages and the whatsapp pc app open on my computer all day so I can coordinate with my guys at work.. but the pc apps keep getting disconnected. I have an odd feeling it has something to do with a wifi timeout, but I can't find any settings for it.
In order to get them to come back alive I have to unlock my phone and open either the whatsapp or android messages.
This is a very recent problem within the past week or two I would say. I don't have any app killing managers or anything like that installed either.
If anyone has any insight I'd greatly appreciate it - thank you!
Click to expand...
Click to collapse
I'm using Note 9 and having the same issue for a long long time.
You may try to time how long it takes to lose connection - it should be very consistent at 30 minutes.
---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------
Paras Lehana said:
I've the same problem and already tried to exclude WhatsApp from battery optimizations. I have raised the concern with the support team. I don't think it's related to Wifi connection as it gets connected as soon as WhatsApp is opened on phone. But I've never thought it this way so will try to troubleshoot more now and get back to you.
Hope someone else have a solution.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
tried the same thing, adding whatsapp to the exclusion list, not useful.
Try these:
General Management -> Battery
Turn off "Battery life optimiser" & go to Advanced settings, turn off "App power monitor"
It works for me.
I have been facing these problem with my home-wifi and office-wifi. Everything is fine when connected to 4G, but I only have limited data usage. My device's problems started after upgrading of routers. There were other routers which gives perfectly timed notifications when connected. Have been trying to solve it by all the ways I could find on the internet. Finally,today I managed to solve the work-wifi issue temporarily with the adb command method. I cant confirm yet about my home-wifi.
I found the adb workaround in a samsung community forum. (Search in google: S9 delayed notification issue)
It is still a temporary solution and must repeat after reboot and need PC to do.
It requires setting phone to usb debug mode and connecting to it.
The adb command to send is.... adb shell dumpsys deviceidle disable
If you have never used adb before, the instructions are here https://www.xda-developers.com/quickly-install-adb/
Good luck.
shahoom59 said:
I have been facing these problem with my home-wifi and office-wifi. Everything is fine when connected to 4G, but I only have limited data usage. My device's problems started after upgrading of routers. There were other routers which gives perfectly timed notifications when connected. Have been trying to solve it by all the ways I could find on the internet. Finally,today I managed to solve the work-wifi issue temporarily with the adb command method. I cant confirm yet about my home-wifi.
I found the adb workaround in a samsung community forum. (Search in google: S9 delayed notification issue)
It is still a temporary solution and must repeat after reboot and need PC to do.
It requires setting phone to usb debug mode and connecting to it.
The adb command to send is.... adb shell dumpsys deviceidle disable
If you have never used adb before, the instructions are here https://www.xda-developers.com/quickly-install-adb/
Good luck.
Click to expand...
Click to collapse
Sounds like battery optimization is what's the problem. Is WhatsApp set to "optimized?
Bober_is_a_troll said:
Sounds like battery optimization is what's the problem. Is WhatsApp set to "optimized?
Click to expand...
Click to collapse
I tried turning off all battery optimisations at everywhere I could from inside the phone and even in performance mode too, notifications just wouldnt come in time. Now after turning deviceidle off through adb, notifications seem working even after battery optimising is turned back on.