Database Users

thinks its charging....

so i've noticed multiple times today (just got it yesterday, rooted) that the charging indicator flashes on and off. this keeps bringing it out of standby. although sometimes the screen turns on without it saying charging but that seems to be a known issue.
but whats up with the charging flashing

full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?

Strange
Never had this issue on my a500 - but have the exact same issue on my Samsung Intercept with a slightly damaged charging port - after unplugging the system will still show as charging and offer to mount as an external storage device - even though it's not plugged into anything.
Had the random screen on when I was still on a 3.0 based rom - have you registered your tablet with Acer and upgraded ota to 3.1? Can also manually flash 3.1 update.
best of luck!

i just updated my last post,
but yeah im on the latest ota 3.1 in the US and registered

lbhocky19 said:
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Click to expand...
Click to collapse
Yes! Easy as hell too.
Check this out, and good luck!
(How to root a500 3.1 stock)
http://forum.xda-developers.com/showthread.php?t=1138228
(Edit: the method you linked to looks like the same method described here at XDA. May not solve your problem)

well cancel my happiness. did a reboot and now it fully thinks its charging. no flickering.
even plugged it in and unplugged and still says charging.
this time i plugged it in and rebooted. at least the notification went away
edit: and its back.

really strange....
May want to just return it and snag a new one if that is easy/possible.
After your full reset did you do any Modding/install any apps? May be possible something you are running is causing the issue, but I am really stumped on this one.
Could always get cwm running and reset the battery cache, but I am pretty doubtful that is gonna do anything.

same problem for me here.though I did not root my device yet.it shows charging with no charger plugged in.also recognized that my battery indicator sometimes remains on a certain percentage and hangs.after a restart it shows the actual battery level.I am on stock rom 3.0.1...maybe I send it back tomorrow.because this is really enoying...

yup. mine just started doing the hanging at one percentage til reboot

don´t know if it´s software or even hardware related

the fact that we have identical problems makes me think software

[Q] Usb not recognized by anything all the sudden

Ok so makes no sense ive not had any problems like this. Ive had my phone for months. All the sudden last night i plug it into my ps3 to move over a video file and Boom. the Ps3 freezes in such a way that all the controllers stop working and i cant do anything on it. Unplug the phone and after a few seconds things go back to normal. I plug it into my Usb hub (4 way splitter from Tmo) on the ps3 and it works (albeit very very slowly). Try to go back to just the ps3 and again it stalls and the pc wont even see it. Today trying to fix the problem ive changed to 4 different roms, tried mounting in recovery and tried to get my PC to recognize it every way i know and nothing is working. The charging light comes on but nothing else seems to happen on the ps3 or computer. Thanks in advance pros

Bump. Please help if u can guys. Thanks

ooo i had this issue earlier this week, installed like 3 different roms and it wouldnt see it, but all of a sudden it came back up.
what I did was wipe data/factory, cache, davlik, went into mount and storage formatted everything that gave me the option, mounted usb and installed Royal Panache rom. rebooted twice and it showed again.
hope this can help you.

srivers33 said:
Ok so makes no sense ive not had any problems like this. Ive had my phone for months. All the sudden last night i plug it into my ps3 to move over a video file and Boom. the Ps3 freezes in such a way that all the controllers stop working and i cant do anything on it. Unplug the phone and after a few seconds things go back to normal. I plug it into my Usb hub (4 way splitter from Tmo) on the ps3 and it works (albeit very very slowly). Try to go back to just the ps3 and again it stalls and the pc wont even see it. Today trying to fix the problem ive changed to 4 different roms, tried mounting in recovery and tried to get my PC to recognize it every way i know and nothing is working. The charging light comes on but nothing else seems to happen on the ps3 or computer. Thanks in advance pros
Click to expand...
Click to collapse
I had a similar issue with my nexus s and a dev told me to partition SD card or power down phone. Plug it in go to recovery and find mount SD card try that
Sent from my Nexus S 4G using Tapatalk

So i tried both ideas, interesting results. I had already tried getting it to work in recovery and no joy. Flashed the latest CWM 5.0.1.0 and still nothing.
Then tried Royal Panache and the phone seems to see the comp, lets me pick what kind of connection i want to use but then nothing else happens on the comp. A
Any new tips?

srivers33 said:
So i tried both ideas, interesting results. I had already tried getting it to work in recovery and no joy. Flashed the latest CWM 5.0.1.0 and still nothing.
Then tried Royal Panache and the phone seems to see the comp, lets me pick what kind of connection i want to use but then nothing else happens on the comp. A
Any new tips?
Click to expand...
Click to collapse
did it show up on the panache rom then? when you say it didnt show up on the computer, it didnt pop up and it didnt show in the "computer" section where it shows all drives?

Yes exactly.on panache only, it Shows in the phone but its as if the comp then can't see it. Still works fine with the hub but nothing else, have tried different computers, ROMs, cords, recovery images. The only way it works is through the hub. THIS MAKES NO SENSE.......could un rooting fix this? Could it maybe be the sdcard?

This happens to me...
Sent from my HTC Glacier using XDA App

This happened to me and flashing the latest unity kernal fixed it.
http://forum.xda-developers.com/showthread.php?t=1050106

ok, so virtuous didnt help. The rom didnt work alone neither did using the latest kernel. Unrooting now. will keep all posted.

no dice mates, all the way back to stock and no difference. Like the panache ROM, the notification shows up, but it doesnt seem to make any real difference. Doesnt show on the comp or ps3 and so im on the phone with TMO now.

[Q] Weird reboot loop

Updated the wife's phone to CM7 some time ago because stock was getting really sluggish and unreliable for her. Wanted to give it some new life. Been running ok (a bit better than stock) but still not great. Kinda flaky, she says. I haven't had a lot of hands-on with it since setting it up, but she says it has poor battery life, likes to freeze up, etc... But overall, an improvement.
Today, she gets up, and her phone won't power on. I know her charger can be a bit temperamental, so pull and replace the battery, then hook it up to mine to try and get it to boot.
It powers up long enough to show her she has a lost call, then spontaneously reboots again. Now it's stuck in a loop while plugged in. It boots, gets to the lock screen, reboots. I can get into recovery (but it looks like stock recovery, not clockwork, so I can't reflash CM7 to see if that helps).
I wanted to try flashing a stock SBF so I could get it booting again, (or at least take it into Verizon), but it doesn't even power up when plugged into a USB cable hooked up to the computer, only on the charger.
Any thoughts? I'm kinda stumped, and not as familiar w/ the Droid 2 as I am w/ my HTC G2.
*Edit*
Eh, after sitting on the charger for awhile while I typed this, it actually came up and seems to be staying up. I guess the battery was just very VERY low? Nevermind!

Sbf the phone back to stock and use a more stable rom. Custom roms from what i am noticing can have 2 installs of the same rom and give 2 completely different results. I had this problem with my current rom miui 2.2.10. On my first install it was complete garbage, crashing constantly even with system apps. Then i Sbf'd back to GB using the newly released GB sbf file you can find in this forum. Then re-installed miui and it works fine now. So it could just be you got a bad install. Try miui 2.2.10 over at rootzwiki, its a solid rom.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/

Bluetooth and Wifi broken

I have absolutely no idea what is going on with this. Currently when i try and turn on bluetooth it will sit and think for about 15 seconds like it's turning the radio on, then just fail and go back to thinking the radio is off. When i try to activate wifi it does the same, but says error.
I am running neutrino 2.7, but was seeing this on 2.6 as well. I did a full wipe and re-install last night, and installed apps one by one to try and find what broke it. I thought i had identified google voice as the culprit, but with that uninstalled and almost no other apps installed bluetooth and wifi broke this morning.
if i flash a radio it will fix it maybe once in 5 tries, and only for about 20 minutes or so, then it fails again.
this started last week around the same time AT&T started throttling my data for going over 3.5gigs. No idea if that is related.
any ideas, things to try, etc?

Make a backup and flash the stock rom and stock radio for that rom, see if it still happens. I've read of others having wifi and bluetooth problems, you may try reading in those threads.
Sent from my MB860 using xda premium

Problem!!
you resolved the problem??? any idea???

nope, not yet. I've tried other kernels, and other versions of neutrino (was on EE, tried GT), nothing. Even with a clean wipe it's being dumb.
Downloaded the stock AT&T rom in fruitcake form, going to try that next.
From some reading i think there might actually be some phones with a hardware defect where some soldering wears out and starts messing up the bluetooth/wifi. I'm praying that isn't my phone because i'm well out of warranty.

i have the same issue on CM9 as of yesterday. no amount of wipes or different CM9 roms helps, haven't tried any GB roms yet though.

check this thread:
http://forum.xda-developers.com/showthread.php?t=1205775&highlight=wifi+error

i've read that.
flashed stock AT&T rom today, still have problems. not amused.
backing up my data, formatting all sd cards, wiping everything and trying again.

I'm with this problem too, Im running morrisoft rom since last month and I didn't any update, change configs or flash anything before It starts, so wierd...my wifi+bluetooth was working at night them in the next day it wasn't anymore lol..
(it happened today btw)
i ill try change my rom and see what happens...

same issue on a completely clean wipe. pretty sure at this point it's a hardware issue and not software.
I'll try the "fix" posted in the other threat at some point.

clean wipe has no effect. Wifi will sporadically work, bluetooth won't. I'm pretty sure based on how inconsistent the issue is this is a hardware issue. Not amused at all. No warranty left on this phone, and no upgrade until october.

This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")

taylrjones said:
This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")
Click to expand...
Click to collapse
They didn't want to repair it because they knew it had been unlocked? Are we talking about motorola?

same thing happened to mine..... it was a hardware issue, had it replaced...sorry..

[Q] N4 USB stopped working yesterday

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