Related
(Bare with me, this IS wm6 related)
Okay, so i got this qtek 9090 from a trade online, and the owner pointed out that he had used it for some time now and it worked without problems.
However that seems not to be my experience. At first I was a little worried that it did not came with a charger.. Only a USB cable. No worries i thought, I will just charge it through USB. Now I have had some experiences where phones wouldn't charge from some of my computers, apparently because of some boards that put out lower amps than others. However I knew atleast one computer should have no problem charge ordinary cell phones.
So i plugged it in, and to my worries the battery kept going down... Untill the phone was dried from power and everything got lost again.. and again.. and again.. It seemed a little odd that it apparently deleted everything each time, since the backup battery indicated 100%.
So at last it went into flightmode and I shut it down with the powerbutton and let it be connected.. The first many hours nothing happened.. But suddenly, when i did an occasional check, it said 3% battery. I went to sleep and the next morning it was fully charged. I used it all day in school and it held its power real fine.
Now I got the feeling that this probably was caused by the low amp output from the computer, making it unable of charging to the extend where the phone would still be able of running whilst charging. So i figured i would order a 220v (the powercurrent here in Denmark) -> 5v USB that outputs 700mA, to make a quicker charge.
Well, to day I was gonna receive that adapter, and since I'd read that the wm6 apparently draines the battery some bit, I waited untill today to upgrade to wm6.
I upgraded and everything truely runs quick and stable. But when i recieved the adapter and plugged it in, i was horrified. The power kept going down, as I had experienced when it was plugged into USB.
Now my girlfriend really wanted to play bejeweled on this thing, so she did and then shortly afterwards we took a few hours nap. I had her plug it in the new adapter to charge it. When i woke up i saw the screen blinking.
I could se it was rebooting over and over again, as it had done the first time it completely lost power..
Now besides that extremely annoying charging problem, I now had another concern....
The boot screen shows NONE next to the R and the G.
Next to the D is the wm version displayed.
Any help would be greatly appreciated.
red LED?
Hm.. By doing a hard reset it shows numbers next to R and G again.
It continuely reboots, display boot screen, shuts down, LED is red, reboots, displays boot screen, shuts down, LED is red again and again.
If i hard reset it some times it will at one point stay off, but the LED still lights red.
And now I question wether 700mA is even enough for charging the BA?
1. Higher power given by power supply does not mean, you will get faster charging
2. If you use WM5/WM6 and have Bluetooth turned on, device turns on every few minutes (bug/feature of the driver needed to keep Bluetooth running: look for BigMike's fix for more information). If your deivce is set up to turn off after long time (for ex. 5 mins), battery might drain out in half a day.
3. Check power settings (delays for device power down etc.)
4. In WM6 be sure, that audio manager is not running (prevents device from deep sleep, allows only screen shutdown)
5. If battery shows up 100% and after disconnecting device discharges in less than 2h being turned on all the time (wifi, bt, phone, screen all the time turned on) it means, that battery might be worn. Consider exchange.
R and G showing NONE is normal in WM5/WM6 because of bug (unfixable for now) in the device and it's incomatibility with this OS: after turning on from power down (taking battery out or total discharging) make soft reset just when R NONE G NONE shows up on the screen. Everything will be normal.
jakubd said:
1. Higher power given by power supply does not mean, you will get faster charging
2. If you use WM5/WM6 and have Bluetooth turned on, device turns on every few minutes (bug/feature of the driver needed to keep Bluetooth running: look for BigMike's fix for more information). If your deivce is set up to turn off after long time (for ex. 5 mins), battery might drain out in half a day.
3. Check power settings (delays for device power down etc.)
4. In WM6 be sure, that audio manager is not running (prevents device from deep sleep, allows only screen shutdown)
5. If battery shows up 100% and after disconnecting device discharges in less than 2h being turned on all the time (wifi, bt, phone, screen all the time turned on) it means, that battery might be worn. Consider exchange.
R and G showing NONE is normal in WM5/WM6 because of bug (unfixable for now) in the device and it's incomatibility with this OS: after turning on from power down (taking battery out or total discharging) make soft reset just when R NONE G NONE shows up on the screen. Everything will be normal.
Click to expand...
Click to collapse
AFAIK the lower the mA output, the slower the charge period.
I have had wifi, bluetooth, beam off. I've set shutdown to 2 minutes. I've set it to low brightness and etc.
As i mentioned it had no problems going a whole day of usage in school.
Didn't know about the bug in wm6 that makes only the screen shut off, but at the momemt i can't even boot the device, apparently because it has no batterypower. And having it connected to the charger makes no real difference (other than it will display the bootscreen and perhaps even the Windows Mobile welcome screen thing, for a few seconds.. then go dead again.)
I've had it in the charger for about an hour or two, still not enough power to boot it up.
It feels like it's just not charging sometimes.. And other times it will charge just fine.
Found out about the reset to solve the NONE issue, but i still don't know what it means that its LED is red all the time?
Even 500mA is enough for sure, as charging from USB works fine.
Device will shut down soon after turning on if there is not enough power in battery, even it if is charging. Leave it charging (amber led on the right) for some time. RED led means low battery and no charging (AFAIR).
jakubd said:
Even 500mA is enough for sure, as charging from USB works fine.
Device will shut down soon after turning on if there is not enough power in battery, even it if is charging. Leave it charging (amber led on the right) for some time. RED led means low battery and no charging (AFAIR).
Click to expand...
Click to collapse
Hmm, i see. I just don't understand why it's not charging then :/
trylleklovn said:
Didn't know about the bug in wm6 that makes only the screen shut off
Click to expand...
Click to collapse
This is not a bug - thanks to this you can still listen to your music keeping device with screen turned off, when you don't need it to spare battery.
trylleklovn said:
Found out about the reset to solve the NONE issue, but i still don't know what it means that its LED is red all the time?
Click to expand...
Click to collapse
Red LED (right one) means low battery, no charging. To charge this led must be amber. Details - you must look for manual.
jakubd said:
This is not a bug - thanks to this you can still listen to your music keeping device with screen turned off, when you don't need it to spare battery.
Red LED (right one) means low battery, no charging. To charge this led must be amber. Details - you must look for manual.
Click to expand...
Click to collapse
Okay.
It's odd still. When i connect the charger the right LED starts to light red.
If it means that its not charging, there must be something wrong, since it only happens when connecting the charger..
it can be amber or red. Those are different colors and meaning.
You can confirm it charges touching the battery - it becomes slightly warm after some time.
jakubd said:
it can be amber or red. Those are different colors and meaning.
You can confirm it charges touching the battery - it becomes slightly warm after some time.
Click to expand...
Click to collapse
I KNOW that, but it is not going amber. It stays red all the time.
Found this thread that discusses a similar problem; http://forum.xda-developers.com/archive/index.php/t-233782.html
Apparently it shows RED light all the time if the battery is dead.. However i hardly doubt that the battery, which could power the phone just fine for and entire day, should be dead.
However, one suggestion in the thread was to take out the battery for some time and then try again. So I will do that for now.
Behavior has changed a bit now..
The LED is still red when i connect the charger. However, if i try to turn it on following happens:
Boot Screen shows for a couple of seconds...
Windows Mobile startup screen appears and the LED changes to orange/amber..
After a few seconds the screen turns black and the LED changes to red again...
And then after a few more seconds the boot screen appears again and everything is repeated, over and over.
If I disconnect the charger the boot screen appears, the wm startup screen appears, this time with a flashing red LED.. shortly after the phone turns off.
trylleklovn said:
Behavior has changed a bit now..
The LED is still red when i connect the charger. However, if i try to turn it on following happens:
Boot Screen shows for a couple of seconds...
Windows Mobile startup screen appears and the LED changes to orange/amber..
After a few seconds the screen turns black and the LED changes to red again...
And then after a few more seconds the boot screen appears again and everything is repeated, over and over.
If I disconnect the charger the boot screen appears, the wm startup screen appears, this time with a flashing red LED.. shortly after the phone turns off.
Click to expand...
Click to collapse
I've seen this problem before. The charger is not putting out enough power to both charge and boot the BA. So what happens is that it starts charging enough to start boot, but as soon as it has enough power to start the boot, it immediately drains it by starting to boot with screen at full brightness.
What I do in this case is to try to catch it just as it starts to boot and turn the backlight off by holding down the power button for 5 sec. This turns off the backlight so there is less drain and the thing can boot up and start charging.
All in all, its a pretty stupid bug but what the hell, there is a solution to it.
Good luck.
motisu said:
I've seen this problem before. The charger is not putting out enough power to both charge and boot the BA. So what happens is that it starts charging enough to start boot, but as soon as it has enough power to start the boot, it immediately drains it by starting to boot with screen at full brightness.
What I do in this case is to try to catch it just as it starts to boot and turn the backlight off by holding down the power button for 5 sec. This turns off the backlight so there is less drain and the thing can boot up and start charging.
All in all, its a pretty stupid bug but what the hell, there is a solution to it.
Good luck.
Click to expand...
Click to collapse
This seems to work atm. (just a few seconds since it successfully booted)..
Does this mean that the device really cant charge if its not "on" ?
(I can see its booted and the LED is now orange. If only it will stay this way untill it has been recharged further ))
trylleklovn said:
This seems to work atm. (just a few seconds since it successfully booted)..
Does this mean that the device really cant charge if its not "on" ?
(I can see its booted and the LED is now orange. If only it will stay this way untill it has been recharged further ))
Click to expand...
Click to collapse
It can charge when it is off. BUT... When its off, its not really off... It has to finish booting and then you can turn it off. Then it will charge faster as it only has minimum drain on the battery. As I said before, its a stupid design.
motisu said:
It can charge when it is off. BUT... When its off, its not really off... It has to finish booting and then you can turn it off. Then it will charge faster as it only has minimum drain on the battery. As I said before, its a stupid design.
Click to expand...
Click to collapse
Well we can certainly agree on that
So does the phone also basicly use to much power to be used and charged at the same time? Which would explain why it seemed to lose power even though it was connected to the charger.
Although it still doesn't add up for me, as at one point i was playing a game on it, while charging and then it charged real fast, where you would expect it to use more power
Oh well, if only it keeps charging now i'll be glad
trylleklovn said:
Well we can certainly agree on that
So does the phone also basicly use to much power to be used and charged at the same time? Which would explain why it seemed to lose power even though it was connected to the charger.
Although it still doesn't add up for me, as at one point i was playing a game on it, while charging and then it charged real fast, where you would expect it to use more power
Oh well, if only it keeps charging now i'll be glad
Click to expand...
Click to collapse
I have found that if you only use the USB cable to charge, it takes much longer (if at all) to charge if it is on. Thats why I bought cradles that have external power suppies as well as the USB sync cable. With this configuration, it gets to full charge in about 90 minutes.
Hm.. yeah.. I let it charge for some time, until it shut down and the LED changed to red again.. The same thing has happened about 3 times now.. If I try to navigate it with the brightness off it will shut down after a few clicks..
Seems like either the battery is completely dead or it's simply not charging.. :/
Think i have to buy a new battery and a cradle, although i didn't really want to spend money on this phone as i got it virtually for free (through a trade of a w810i)
trylleklovn said:
Hm.. yeah.. I let it charge for some time, until it shut down and the LED changed to red again.. The same thing has happened about 3 times now.. If I try to navigate it with the brightness off it will shut down after a few clicks..
Seems like either the battery is completely dead or it's simply not charging.. :/
Think i have to buy a new battery and a cradle, although i didn't really want to spend money on this phone as i got it virtually for free (through a trade of a w810i)
Click to expand...
Click to collapse
Get it to orange and then push the power button (short push) to turn it off (not long push which only turns off the backlight). Then let it charge for an hour or 2 (or even all night). By then, it should work OK.
motisu said:
Get it to orange and then push the power button (short push) to turn it off (not long push which only turns off the backlight). Then let it charge for an hour or 2 (or even all night). By then, it should work OK.
Click to expand...
Click to collapse
Yeah, i tried that. As soon as i press the power button it goes to red again.
Update..
A litte update (i might as well document everything I find out here, if anyone should run into a similar problem).
Now, I've had the device connected to the charge for some time now.
What happens is that the device boots up, automaticly dimms down to no light (since i once had hold down the power button, to dimm down light).
Then it boots up, and i can see everything running.
I can navigate to the battery status menu, which shows
Battery: 0% (charging)
Backup battery: 25%
After a few minutes the device shuts down, and the LED goes red again. But after about a half a minute it will try to boot up again, and it goes through everything again.
What I've noticed is that the backup battery slowly increases, and while im writing it has gone all the way to 75%. The good thing about this completely automatic procedure is that it apparently slowly charges, at least, the backup battery.
My theory is that the backup battery has first priority in the system, so that the regular battery wont charge untill the backup battery is up. And since the backup battery can't apparently be used for actualy powering the system, the system will continuesly reboot because of lack of power, theoreticly untill the backup battery reaches 100% and it starts to charge the regular battery.
The whole problem seems to be cause by some charging malfunction, so that both batteries has been completely discharged. I hope that by letting it continue to reboot, charge, reboot, charge, etc. it will revive the battery.
I will return with more info tomorrow.
Any suggestions are still greatly appreciated.
Phone was on about 60%. Plugged in the charger, downloaded Bricked Kernel to add to my r11 Modaco Cyanogenmod rom. Ran antutu and the screen went to the charger symbol. Pressed the power button then the charger symbol went and the red light started flashing.
Read up on here and tried the volume up + power for 60 seconds and plugged in the charger. Nothing
Tried volume down + power for 60 sends and plugged in the charger - Google symbol then into bootloader. This allowed me to get into teamwin, where I could recover my backed up image. Pressed reboot. Nothing just the red light again.
Been on a 1.5a charger for over an hour and still flashing
I'm now trying the charger in recovery mode.
I would take the back off and disconnect the Battery but my darling Mrs has had a clearout so I don't have the right screwdrivers :/
Anyone had this particular combo?
Had the red led ligth too after flashing some roms and testing it out. It powers off and shows the red led. Nothing works. I noticed that my n4 was very hot so i let it cool down for about 3 hours. After that all was fine and my n4 booted up normal. Had a heart attack as i see this red led. I think it is becouse the n4 is overheating but dont know. Hope that helps you
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4
ChaosChris said:
Had the red led ligth too after flashing some roms and testing it out. It powers off and shows the red led. Nothing works. I noticed that my n4 was very hot so i let it cool down for about 3 hours. After that all was fine and my n4 booted up normal. Had a heart attack as i see this red led. I think it is becouse the n4 is overheating but dont know. Hope that helps you
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4
Click to expand...
Click to collapse
Thanks
I did notice it was hot when it first happened. Its been a while now though and certainly feels cool to touch.
When I do boot into bootloader or recovery, as soon as I unplug the charger it turns off again. :/
Perhaps I'll leave it longer (in the fridge ) and try it again
mrew42 said:
Thanks
I did notice it was hot when it first happened. Its been a while now though and certainly feels cool to touch.
When I do boot into bootloader or recovery, as soon as I unplug the charger it turns off again. :/
Perhaps I'll leave it longer (in the fridge ) and try it again
Click to expand...
Click to collapse
It sounds that your battery seems to be defect. I know that some one on xda says that removing the backcover and then remove the battery and plug it in again solve that for him. Dont have the link right now but there is a thread about the red led issue. Try to Google it a bit
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4
Thanks again
I found that thread but am currently missing the right screwdrivers to remove the back. That's for tomorrow when I can pick some up from the phone shop. Damned piece of crap LG nonsense. First no USB OTG and now this!!
Battery is definitely munged. Whenever I manage to get into Recovery (TWRP) tha clock is always back at 12:00.
Soon as I unplug the charger, even after an hour or so, it shuts down. After a full night just on charge, just the flashing red light, no response to pressing the power button.
Just gone through the Google replacement process, but being Thursday evening it will probably be Monday at the earlier before it turns up.
On a lighter note I stuck CM 10.1 on my wifes SGS. Apart from being smaller, slower and with a quarter of the memory, the Helium back restored without a hitch and I have virtually the same experience .....
I was on my computer when i remembered i has something written in my tablet's notes that was important. I took it out of my bag and noticed it wouldn't turn on, it was out of battery (hadn't touched it for about a week). I just plugged it in the proper asus charger and put it down and went straight back on my computer.
I decide to check on it after 2 hours thinking it would be near or fully charged. I pick it up and noticed it was on a blank back lit screen. I unplugged it and then the screen turned straight off. Wondering if it didn't charge at all i re-plugged it in. There was no google logo (rooted), instead it turn on with a lit black screen and off and repeating a few times and then small thin artifact pixels run across the screen (red, blue and yellowy colours) and then stay at a black lit screen like when i first picked it up. I had just noticed a small buzzing sound while this was happening and still does so when stuck at the screen. I'm pretty sure it was buzzing when i had found it.
I redid what i had done (unplug, replug) and watch to see if it did the same thing. It did. I tried to power it off while it was at the black screen and it did, but then it would turn back on and etc. Same if i tried to enter boot loader or any key combinations.
I've tried disconnecting the battery and reconnecting and same effect (tried it without battery attached also)
I have a feeling it is dead now and i have no other ideas (checked many forums but got nothing).
Any help would be appreciated.
yvgamer94 said:
I have a feeling it is dead now and i have no other ideas (checked many forums but got nothing).
Any help would be appreciated.
Click to expand...
Click to collapse
It's surely hardware failure, have take some humidity or something like that?
Try press power for 60 seconds, if you wont see any Google logo there's some hardware failure you need to RMA ( http://en.wikipedia.org/wiki/Return_merchandise_authorization )
found the fix
I found away to fix my nexus 7. You could be right how it might have a minor hardware fault, live in australia in the high hot tropics (high humidity). I decide just to plug it into my computer usb charger instead of the proper charger since it had a lower max amp output. Against my ear, a much fainter buzzing is still heard but this time, there was nothing. No power, no back lit black screen, just a very faint buzzing. Decided to let it sit just to see what happens. After an hour or so, i decided to press the power button and noticed there was a battery charging signal. To my delight, I'm sure it was in working order now so i powered it on and oh how relieved i was.
I determined that my device might have had a small hardware fault that made it draw to much power from the 2 amp original charger and thus why the tablet could not boot up properly (from battery depletion). Either that or my charger could be bugged to. But the thing is, since it charged to slow from the usb, i plugged in the proper charger and it worked fine. Just have to try not deplete my battery i guess.
Thanks.
The title pretty much explains it.
My N4 died on me today after running an Antutu Benchmark. I was running on Android 4.4 with the latest Fauxkernel (v29).
I can't boot it up anymore without the charging cable plugged in. When the charging cable is plugged in, the LED flashes red once, the display turns on and shows me the battery charging indicator and turns off just a couple seconds later also with the LED flashing red once. If I attempt to turn it on, the Google sign appears but the phone turns off immediately after that and once again, say Hi! to the red LED.
Pretty much tried everything so far, charging my battery, getting into the recovery menu, pushing down the power+VOL Up buttons for 60 seconds, etc. Nothing helped.
Maybe you guys know any way to fix it? I don't wanna open my device nor replace the battery if possible.
Thanks in advance.
2 ways to fix it. first, leave your phone on the charger for 3-4 hours. thwn try to boot it into the bootloader and press turn off the phone. let it charge further. if that doesnt work, remove the back cover, remove the battery, then clip the battery back in. the second method works 100%.
simms22 said:
2 ways to fix it. first, leave your phone on the charger for 3-4 hours. thwn try to boot it into the bootloader and press turn off the phone. let it charge further. if that doesnt work, remove the back cover, remove the battery, then clip the battery back in. the second method works 100%.
Click to expand...
Click to collapse
I can get into the bootloader but once I select power off, the phone just turns on again and shows me the battery charging indicator. Not sure if it's supposed to be like that but the indicator is completely filled so that would probably mean the battery is full.
Not sure if I have the right screwdrivers to open the back.
xSalamanderman said:
I can get into the bootloader but once I select power off, the phone just turns on again and shows me the battery charging indicator. Not sure if it's supposed to be like that but the indicator is completely filled so that would probably mean the battery is full.
Not sure if I have the right screwdrivers to open the back.
Click to expand...
Click to collapse
the reason for rlod is that the phone thinks that it is under 0% battery. leave it on the indicator that is filled, thats a good start. when that filled indicator starts the reguler behavior that it looks like its filling(up and down), thats when your phone will be fixed. leave it charging for a few hours.
simms22 said:
the reason for rlod is that the phone thinks that it is under 0% battery. leave it on the indicator that is filled, thats a good start. when that filled indicator starts the reguler behavior that it looks like its filling(up and down), thats when your phone will be fixed. leave it charging for a few hours.
Click to expand...
Click to collapse
Alright, I'll try that out. It's kinda annoying though that the display turns on every few seconds and turns off again but if it's going to work later that'll be worth it. Thanks alot!
if worst comes to worst, remove the battery and plug the battery back in. this will "reset" the battery(like a normal battery pull for devices with a removable battery).
seems the post may drive users a mis-understanding to AnTuTu Benchmark, I will ask our engineer to double check.
Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)
I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.
I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.
Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"
charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.
I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.