Related
I'm having an issue with DL30 that I didn't have with any of the Eclair builds. I enable USB Debugging, and then later on in the day when I plug it in, I notice it has shut itself off.
Has anyone else noticed this? Is this just something with Froyo, a bug with DL30 or am I f'ing it up?
Yes I'm experiencing this as well. Something called KiesUSBManager seems to be buggy but I can't figure out how to disable it. Are you using a Mac by chance?
I am running on mac and I am having this problem with PDAnet. I get about 2-3 mins and then I get the boot. Thought it was just me.
I'm an app developer and not having usb debugging available or constant was a serious problem so I had to abandon DL30 in favor of JT's AOSP, which is working pretty well now at least for my needs. I'd prefer DL30 style, but after all day searching I've found no solutions. It seems to be something a Mac user of the Galaxy Tab had with 2.2, so it might be some problem with whatever samsung kies service monitors the usb connection and how that communicates with the mac OS. OS X never tries to mount the SD card even once the USB debugging flips off, so I'm not sure what the problem is. This is the only place I've seen someone else complain about it, so I'm guessing most people are on PC's and don't have the issue or they don't use USB debugging so don't care or haven't noticed.
Hi
Has anyone experienced that the tablet switches off constantly with out any any specific reason?
I could easily surf or read an email without switching off.. but then i would watch a movie and it switch off instantly or the other way around and its not even shutting down.. it just goes from powered on, to completely switched off.. It does not get hot and it does charge perfectly and the battery level does not drop/discharge radically.. it has never been dropped or manhandled. and it started doing last week
I'm on stock 3.2 PDA:KMP CSC:KMP (XAB), not rooted..
Any ideas, suggestions?
Thanks in advance
I suggest you to discuss your matter from where have you bought the notebook as there might be some problem in hardware
SofiaBrown said:
I suggest you to discuss your matter from where have you bought the notebook as there might be some problem in hardware
Click to expand...
Click to collapse
What notebook?
You might have some apps installed that cause this...?
Jay Rock said:
What notebook?
You might have some apps installed that cause this...?
Click to expand...
Click to collapse
I hope he means tab?
Im gonna give that a shot. since that's the only thing i said i yes to, after the factory reset.
ill get back with the results
Thanks
-TB-
I used to own a Galaxy Tab plus 7.0, which experienced this known problem of random reboot and/or sleep of death. You could google that to find out more.
I've since returned it for a refund. Then I picked up this used P7500 a month ago. It has not experienced not even one reboot. Sure, apps do crash from time to time, but the OS never completely froze.
How long have you owned your unit? If relatively new, I would returned it. If for a while, and only recently you experienced the problem, then I would do a factory wipe, or at least re-trace your steps and uninstall the last few apps. Also, ask yourself whether the problem is already related to certain apps. If so, get rid of those apps.
hi
Did a complete wipe.. so now its close as possible to factory default..
Could it be a battery calibration error? it works plugged in to either pc or wall socket.. works 10min after but then switches of randomly
Thanks for all the help/suggestions so far really appreciate it!
I know some mentioned the option of returning it.. But its bought in the US and im located in Denmark!
-TB-
Hi Guys,
I used the new Nexus 4 Toolkit to unlock the bootloader.
As I unfortunately dont have 10 Posts, I cant ask in this thread, so I hope it's ok to ask here.
I installed the drivers with USB-Debugging (as before for my galaxy nexus) and unlocked the bootloader.
So far everything went normal and good!
Then I wanted to root the system. It was said that I've to enable USB-Debugging again and the system will reboot.
But then :
I tap on "Enable USB-Debugging" and I'm asked If im sure. After this, nothing happens. Usually I see a information-icon, that usb-debugging is enabled in the taskbar.
This icon is now missing. And im completly not able to connect to phone via PC and use ADB.
Im slightly desperated, as anything I could do requires ADB/USB-Debugging.
Can you guys help me?
Thanks in advance.
Does your phone show up as MTP storage OK?
I remember my One X decided to cease all USB activity except charging once, a reboot sorted it.
The USB debugging icon is a little jelly bean as per the attached screenshot.
thanks for your reply.
I dont remember If it was shown as MPT-Storage - will check this immediately after work
THe Jelly-Bean-Icon showed up before, when used the toolkit to unlock the bootloader.
I also rebooted the phone several times
Ok, now everything seems to be identified correctly, again. Very strange.
Maybe the PC needed to be restarted.
Sorry for this post. It can be closed.
Thank you!
Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.
ev!denz said:
Were you able to resolve the problem?
I actually have the same problem also my Nexus 4 is getting very hot and the battery is drain within 4 hours from 100% to ~10% (about 400-800mA consumption).
All stock - I've already contacted the google support but now are holidays.
Click to expand...
Click to collapse
I've got the same problem, except my device is not loading until 100%. It gets really hot while not doing anything and it's empty in about 3 hours.
I figured out that the Nexus is only charged via "USB" although it's plugged in the charger.
Now my device is charging up until 100% but it still gets hot, is empty in about 5 hours and if I connect it in fastboot mode my laptop says that the drivers are not installed properly even though I installed the naked drivers. Re-installing the drivers does not work either, it says that my laptop already had the right drivers installed. And when I connect my device when it's booted it is not recognized at all and does not show up in the device manager. I tried three other cables... Sounds like an USB brick, right?
Ultraschorsch said:
Sounds like an USB brick, right?
Click to expand...
Click to collapse
That's what I think, too.
ev!denz said:
That's what I think, too.
Click to expand...
Click to collapse
Having the same trouble guys. Anyone found any insight into this or possibly a fix?
loopyoyo said:
Having the same trouble guys. Anyone found any insight into this or possibly a fix?
Click to expand...
Click to collapse
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...
Ultraschorsch said:
My battery life got a lot better with the new Franco kernel but the USB-debugging is just gone. I was wondering if maybe one of the recovery developers could help here. The USB brick solution for the HTC Desire was via Cyanogenmod. But I don't think that they know the solution since it isn't a very common problem as it seems...
Click to expand...
Click to collapse
Tap Build Number in about phone 10 times.
zephiK said:
Tap Build Number in about phone 10 times.
Click to expand...
Click to collapse
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.
Ultraschorsch said:
Thanks, but I already did that when I rooted my N4. Turning USB debugging on and off and on again didn't help.
Click to expand...
Click to collapse
Yea...computer doesn't even recognize nexus under recovery or fastboot menus..I think it's really fooked up. Just submitted a rma request to lg so will see how this plays out.
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
I have teh same problem.
1) the battery drains like crazy, even with franco kernel lastest nightly
2) USB debugging does not work now... when plugging into the pc the phone is just not found...
3) I can reboot to recovery but that doesnt do me any good since I cant do jack from it.
anyone has any insight ? what can be going on that the phone is not showing up in windows
studjuice said:
I have the same problem. Did the rma work out? I am wondering about doing that too and how to go back to stock without usb working...
Click to expand...
Click to collapse
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
spaceman860 said:
return to stock with a bad USB n4
http://forum.xda-developers.com/showthread.php?p=36046198
Sent from my Nexus 4
Click to expand...
Click to collapse
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes. If your on stock with a locked bootloader your warranty is still good
Sent from my Nexus 4
al3b3d3v said:
even if you return it to Stock, you still cannot connect to USB...
what to do ? call google and ask for an RMA?
Click to expand...
Click to collapse
Yes, I called Google but they don't have any N4's in stock. so I keep rooted until I get a new device from them.
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
Every since the last OUYA update I can't get Beast Boxing Turbo to load. I tried uninstalling, reinstalling, rebooting, etc. It loads the initial screen and then crashes back to the OUYA menu screen.
Is anyone else having the same issue?
chrisanthropic said:
Every since the last OUYA update I can't get Beast Boxing Turbo to load. I tried uninstalling, reinstalling, rebooting, etc. It loads the initial screen and then crashes back to the OUYA menu screen.
Is anyone else having the same issue?
Click to expand...
Click to collapse
Ive never gotten mine to work, even before the update. It always crashes on me.
mysticg said:
Ive never gotten mine to work, even before the update. It always crashes on me.
Click to expand...
Click to collapse
That sucks.
What's strange is that after flashing CWM and re-setting up my wireless adb it loaded up just fine. Not sure what's going on so I'll chalk it up to gremlins and confirm that it's not a large-scale issue with everyone.
it was the first game i downloaded when i got my machine yesterday, and it gets to the title screen (i assume) with the press any key prompt and then goes back to ouya game menu. Cant get it to work at all.
Cleared the game cache/data/uninstalled etc and no luck. I have not modded my ouya in any way.
Hey, I'm the developer of Beast Boxing Turbo, found this thread with a google alert. Sorry to hear several of you are having problems.
Are you all using USB keyboards or third party controllers attached to your OUYA by any chance? If so, can you see if the game works if you disconnect those, restart your OUYA and try again?
I've had a few reports of crashes when USB keyboards are connected but haven't been able to reproduce the problem on my end. If it IS a problem for you please post the details of the hardware you have connected. Thanks!
You know what, I do have my Motorola Nyxboard usb remote/keyboard combo attached. Sometimes I have to restart my Ouya launcher to make the Ouya recognize it so the fact that BBT started working after I flashed CWM (and thus Ouya didn't recognize that the controller was plugged in) kind of verifies your assessment.
Thanks for stopping by, love the game!
chrisanthropic said:
You know what, I do have my Motorola Nyxboard usb remote/keyboard combo attached. Sometimes I have to restart my Ouya launcher to make the Ouya recognize it so the fact that BBT started working after I flashed CWM (and thus Ouya didn't recognize that the controller was plugged in) kind of verifies your assessment.
Thanks for stopping by, love the game!
Click to expand...
Click to collapse
No problem, glad you like it! For everyone else in this thread, the new update doesn't crash any more if you have a bluetooth keyboard connected! I did run into some problems with a USB keyboard seizing the first player position, but it shouldn't crash. That might just require a console reboot and activating the controller before plugging the USB keyboard in. I reported it to OUYA as a bug so we'll see how that goes.