Related
So I thought my FRF91 had issues but now I'm thinking it's heat.
I was using FRF91 with Google Maps Navigation plugged into a cheap eBay car charger.
Within 20-30 seconds of running Navigation, the phone would reboot.
I did this 3 times in a row, and it would reboot.
I went back to FRF85B, and all was well.
Then I was thinking, the phone was pretty hot when this happened, I checked *#*#INFO#*#* and on FRF91 when it rebooted it was like 38C!!!
(Also on FRF85B, the Temp was in F and not C... weird).
Anyways, today I was driving around back on FRF91 and it crashed again (not plugged in) but was sitting on the dash and it got hot.
So anyone know, is FRF91 pretty sensitive to heat that it would reboot if it goes over a certain temp?
Anyone using a "brand" name car charger? Does your phone heat up?
I have a Belkin charger, and when using Navigation you could almost fry an egg on the thing.
same, i typically use nav and stream music in the N1 car dock, thing gets damn hot. wondering if i should put some sort of shade around it on the top ...
nxt said:
So I thought my FRF91 had issues but now I'm thinking it's heat.
I was using FRF91 with Google Maps Navigation plugged into a cheap eBay car charger.
Within 20-30 seconds of running Navigation, the phone would reboot.
I did this 3 times in a row, and it would reboot.
I went back to FRF85B, and all was well.
Then I was thinking, the phone was pretty hot when this happened, I checked *#*#INFO#*#* and on FRF91 when it rebooted it was like 38C!!!
(Also on FRF85B, the Temp was in F and not C... weird).
Anyways, today I was driving around back on FRF91 and it crashed again (not plugged in) but was sitting on the dash and it got hot.
So anyone know, is FRF91 pretty sensitive to heat that it would reboot if it goes over a certain temp?
Anyone using a "brand" name car charger? Does your phone heat up?
Click to expand...
Click to collapse
I don't know if this would be of any help, but since FRF91, when i charge my phone over USB (plugged on the computer), my phone gets auround 41°/42° C.
For information, it happens on MCR21 with default kernel, and just by letting the phone charging with screen on.
And since there, no reboot at all.
So i'm not sure your reboot prob would be heat related
If I'm running something heavy while charging on the car, I at least point the vent to it and turn it up to blow a good amount of air on it.. If it's hot, I'll go ahead and turn on the AC.
Kinda sucks gas milage, as I almost never use AC otherwise, but keeps the phone cool.
Anyone else have reboot with heat issues? I'm right now listening to podcast, and charging my phone and bam it reboots, then within 2 minutes it reboots again.
I check the temp and it's 38C. I pop out the battery and it's not even warm!!!!! The phone itself was hot. I unplug it and within 2 minutes the temp calls down to 35C.
Anyone got any ideas? This is all stock ATT Nexus One FRF91.
Pretty useless if I can't use the dang phone when it's charging.
Sent from my Nexus One using Tapatalk
Sent from my Nexus One using Tapatalk
Ok good its not only me that noticed the heating issue..charging my phone it gets bananas and using the net is bad as well..going back to 85b
I'm having the exact same issue. Every time my phone gets even a little bit hot, it reboots itself. Maybe it's an issue with the ATT/Rogers N1 specifically, since the only people I've seen who have the problem are on those phones.
Same issue here. Was driving back up to CT from D.C. yesterday and the phone reboot during Google Navigation use.
Funny thing is, when I used it last week to drive down there for the holiday, there were no issues.
Could it have been the fact that it was scorching hot even with the AC running?
Sent from my Nexus One using XDA App
I'm using N1 in Indonesia, tropical country with glaring sun all the time
Yesterday I'm trying to use sat nav without charging in the car, yes it was hot to touch
but never reboots, I'm also on FRF91.
But I think if the battery didn't die first it would reboot due its high temp.
I think what we experienced here is result of constant high usage of data + gps
Jreddekopp said:
I'm having the exact same issue. Every time my phone gets even a little bit hot, it reboots itself. Maybe it's an issue with the ATT/Rogers N1 specifically, since the only people I've seen who have the problem are on those phones.
Click to expand...
Click to collapse
No I have the Tmobile version (i'm using WIND) and it get mad hot..Through charging and anything net related (i only use wifi). As well connected to usb (obviously since it also charges).
My Nexus gets broiling hot when charging in "USB" mode - which you will get plugged into a USB port OR plugged into almost any non-HTC charger. Basically, it limits it to ~450ma draw, and I imagine that HTC didn't engineer this well and some wasted current just gets shunted as heat. This does NOT happen when charging in "AC" mode off of the HTC charger.
That waste heat may be a really stupid engineering problem, BUT, I've had my phone overclocked, plugged in to a 2A charger brick, but in USB mode, incredibly hot to the touch and showing 43deg or more while running graphics benchmarks or games, and I've never seen a problem. If "only" 38deg is giving you heat-related issues, that seems like a defect, and I'd look to get a warranty replacement before the board dies.
big_adventure said:
My Nexus gets broiling hot when charging in "USB" mode - which you will get plugged into a USB port OR plugged into almost any non-HTC charger. Basically, it limits it to ~450ma draw, and I imagine that HTC didn't engineer this well and some wasted current just gets shunted as heat. This does NOT happen when charging in "AC" mode off of the HTC charger.
That waste heat may be a really stupid engineering problem, BUT, I've had my phone overclocked, plugged in to a 2A charger brick, but in USB mode, incredibly hot to the touch and showing 43deg or more while running graphics benchmarks or games, and I've never seen a problem. If "only" 38deg is giving you heat-related issues, that seems like a defect, and I'd look to get a warranty replacement before the board dies.
Click to expand...
Click to collapse
completely agree but whats funny as the heat issue never happened with froyo 50-85
Hmmm. My problem is not simply the heat, but the fact that the slightest bit of heat seems to cause my N1 to reboot itself. Anyone having similar issues, or perhaps suggestions on what I can do? I've unlocked my bootloader, but I'm running stock firmware. Hopefully this isn't a hardware issue
My Nexus gets broiling hot when charging in "USB" mode - which you will get plugged into a USB port OR plugged into almost any non-HTC charger. Basically, it limits it to ~450ma draw, and I imagine that HTC didn't engineer this well and some wasted current just gets shunted as heat. This does NOT happen when charging in "AC" mode off of the HTC charger.
Click to expand...
Click to collapse
This absolutely does not happen. The charge is limited by the power supply, the phone is pretty much "blind" to the source. A more likely cause is the phone is TRYING to pull the .5A of charge and only getting .45A, causing to attempt to compensate and thus running more inefficiently. Also, as far as heat goes, do you turn the screen off out leaver out on while charging the device?
-------------------------------------
Sent via the XDA Tapatalk App
MaximReapage said:
This absolutely does not happen. The charge is limited by the power supply, the phone is pretty much "blind" to the source. A more likely cause is the phone is TRYING to pull the .5A of charge and only getting .45A, causing to attempt to compensate and thus running more inefficiently. Also, as far as heat goes, do you turn the screen off out leaver out on while charging the device?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
REEEEEAAAAALY?
I sincerely hope that you meant to say that this absolutely does not happen to YOU.
There's been a ton about this, on this forum. There are two pins in the USB connection that, if they are open (like on a computer or with most chargers), cause the Nexus to see itself in "USB" mode, and to not draw more than ~.45-.50A. If those two pins are shorted, you get "AC" mode, and the phone will take up to about 1A.
I use several different bricks with the Nexus (iPhone brick - [email protected], iPad brick - spec'd as 10watt, several different thrid-party AC/USB bricks - all between 1.6 and 2.0A @ 5V, Milestone charger .9A @ 5.9v) and get the same story out of all of them - USB mode and a hot phone (36-38C with the screen off and the phone relatively inactive) during charging. I've never had the slightest performance problem, so I don't worry about it. If I use stock the N1 charger OR one other off-brand (so off-brand that there is nothing useful written on the case other than 2.0A @ 5V) charger, I get "AC" mode - where the phone accepts about .95A @5V, and does NOT get hot (32-34C during charge). This has been consistent with Eclair (stock and several Cyanogens) and every version of Froyo (FRF50, FRF83, FRF85B and FRF91).
My old BB Bold 9000 pulled over 1.5A @ 5V out of all of the 2A chargers that I have - it would fully charge in under an hour without getting hot. My wife's Curve 8900 charges fast as well - so I know that the chargers can do it. It's just the HTC hardware that limits the draw.
I say HTC, because I have confirmed the EXACT SAME behavior on a friend's HTC Desire. He was wondering why it took him all day to charge the phone off of a non-HTC power brick.
The phone is ABSOLUTELY not blind in this - it is the one drawing the current. I suspect that the USB-mode draw is just poorly done (at least on some phones), and there there is some leak. Maybe a specific hardware revision?
daeshawn said:
completely agree but whats funny as the heat issue never happened with froyo 50-85
Click to expand...
Click to collapse
That is weird, because it definitely did happen to me (using a plethora of different kernels and speeds). Are you running anything else non-stock (kernel, OC, UV, etc.) that you were not running before?
That is weird, because it definitely did happen to me (using a plethora of different kernels and speeds). Are you running anything else non-stock (kernel, OC, UV, etc.) that you were not running before?[/QUOTE]i just put back in paul froyo 50 and it heats a littel when charged but nothing out of the norm from many devices i've charged. The only other froyo i've used was Kang o rama (85B) which doesnt heat up for me..as soon as i put in any froyo 91 in i get mad heat...I currently gonna test with applications as maybe its an app that is causing it somehow..I could be completely wrong but worth a try..But as I said i'm back to pauls froyo 50 and no heating issues
daeshawn said:
i just put back in paul froyo 50 and it heats a littel when charged but nothing out of the norm from many devices i've charged. The only other froyo i've used was Kang o rama (85B) which doesnt heat up for me..as soon as i put in any froyo 91 in i get mad heat...I currently gonna test with applications as maybe its an app that is causing it somehow..I could be completely wrong but worth a try..But as I said i'm back to pauls froyo 50 and no heating issues
Click to expand...
Click to collapse
As long as you've got a running, reliable phone that does what you want and doesn't catch fire, you don't need the highest version number (says the guy who is now running CM nightly builds...).
If you feel like figuring out what is killing off your phone:
First, take a good backup!
Then, do a factory wipe and reload FRF91.
See if you get the same behavior. If you do, it's 91 on your phone. If not, it's one of your apps.
So, if you do not see the "unusual" heating, try restoring your applications and running them like you usually would. Try using a script (if you are up to it) or OS Monitor plus a logcat to see what is eating you up.
yeah i originally put in the old radio and went back to emother's 1.9.2...then put in pauls froyo 50 (which included the new radio). So far added my apps and no extreme heat. Only when on wi-fi but the heat i'm getting was the same i normal got in the beginning and minimal heat when ac charging (before it would get extremely hot). When i come home from work imma try his froyo 91. I'm thinkin it also is stemming from a game Hero of Sparta and a facebook chat app. If i'm correct thats when i first noticed heat issues. but could be wrong i'll let you know
when i have my phone in my car dock i have one of the vents in my car pointed at the thing blasting AC all over it!
helps so much!
My first o2x had random reboots and bsod.
When i received my second handset, I didn't trusted the charger so I bought one on ebay (5v, 1.0a) and used it for 1,5 month now without any reboot or bsod.
Yesterday I went to my girlfriend and took an other charger with me, i plugged my o2x in and bam, it totally frozen inmediatly! After rebooting the device by taking out the battery i tried it again and had the same issue. I also tried ANOTHER charger, with another ampere output. When i connected that charger to the phone, my phone went crazy (opening programs without touching the screen. Also my touches weren't recognized untill I disconnected the device.
Now i've connected my ebay charger again to my device and have no problems at all!
For those who want to try to get rid of the bsod and reboots, try this charger:
http://cgi.ebay.nl/ws/eBayISAPI.dll?ViewItem&item=320574017791&ssPageName=STRK:MEWNX:IT
This is not my shop or a promotion to the seller or whatever...
It's no guarantee, but for the few euros I would try it!
Let me know if it works for you, it does for me
Well, my girlfriend have a SE Xperia Pro Mini and used my old Desire charger. The screen was useless with the charger. Menu opened up and closed automaticly and the touch was useless.
Result: Broken battery, when the phone shut off and she put her own charger (original) the battery is 100% after 15 mins and back to 0% after a few hours without use.... Be careful with different chargers with different volt and amp. Just saying
Edit: By the way, my phone had many reboots in the beginning and none when I charged it. I had the reboots problem when I plugged in SD-card. After I removed it, I don't have had any reboots for 2-3 weeks.
i can't agree that the bsod and freezes are caused by the charger
i had the same like axepted, no reboot or freeze while charging, only at night when phone was idle
after testing cm nighly i flashed back to latest stock from http://forum.xda-developers.com/showthread.php?p=12890619#post12890619 and since then i had neither a bsod nor a freeze, so imho it has to be a software issue
yesterday i changed to cm7 rc1 and it also works fine
frittenpiekse said:
i can't agree that the bsod and freezes are caused by the charger
i had the same like axepted, no reboot or freeze while charging, only at night when phone was idle
after testing cm nighly i flashed back to latest stock from http://forum.xda-developers.com/showthread.php?p=12890619#post12890619 and since then i had neither a bsod nor a freeze, so imho it has to be a software issue
yesterday i changed to cm7 rc1 and it also works fine
Click to expand...
Click to collapse
U sure bro the reboot problem gets over ? as im thinking of buying this phone but im confused after knowing its reboot problems
U sure bro the reboot problem gets over ? as im thinking of buying this phone but im confused after knowing its reboot problems
Click to expand...
Click to collapse
the problem is not that big, here in danmark its only 1% of the phones where have problems.
smokeweedevery said:
the problem is not that big, here in danmark its only 1% of the phones where have problems.
Click to expand...
Click to collapse
Ohk bro
Im just wondering if the phones in India also have this kind of problems
all phones can have problems its not only optimus, lets take sgs2 it have screen problems. and you can always return the phone if it has problems
thnx mate
u helped me
Just flash the latest CM7 nightly and you're good to go. I just bought on from Delhi yesterday and its been running like a charm on CM7
anshmiester78900 said:
U sure bro the reboot problem gets over ? as im thinking of buying this phone but im confused after knowing its reboot problems
Click to expand...
Click to collapse
i can't promise that, if necessary, a reflash will be the sollution, but in my case it was.
also LG is actually working on a bugfix, they wanted to release it in june but delayed to july
@sid1712: CM released a RC some days ago too, i flashed it yesterday and it works really fine
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
I take care to exit unused applications, etc, but this still occurs. In fact, I have tried rebooting to ensure nothing is left running in the background. Oddly, it occurs EVEN WHEN PLUGGED INTO THE CAR OR USB outlet... Most often this occurs when I'm using the device for navigation, so GPS, and DATA will be on. The notice has also popped up during other applications. It has happened when using LTE but also when LTE is disabled.
Is this something that everyone is experiencing? If you are, can you please post your Service provider, your SPECS, any mods, or if you have made any progress in stopping it. Lets see if we can track this down.
Mad Medik said:
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
Click to expand...
Click to collapse
That's strange. I've never seen a message like that. It doesn't sound like something native to Android / Sense, do you have any battery monitoring / power control apps installed that could be giving this message? How long does your phone last on a charge if you don't plug it in?
I've seen that error before. I wasn't using the USB cable and charger that came with my phone and that cable was damaged in the USB socket. Have you tried other plugs?
Sent from my HTC Raider X710e using XDA App
The reason you are probably seeing that on car or USB charger is due to then not proving the right amount of power. If you have the screen brightness set high and using navigation it uses quite a bit of power. Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Sent from my GT-I9000 using xda premium
Ive had that happen once when I was playing a really graphics intense game. I was over at a friends house and had it plugged into his computer to charge and was showing him how much better a game looked on my phone than his and it did that. I was using the 3 usb ports on the front of his tower, and he also had his phone and a headset plugged in that front hub as well, and since that hub is powered by one connection on the motherboard I just figured the 3 devices (mainly the 2 phones) were just drawing too much power at the time.
I have had it happen when I was playing a graphics intensive game while plugged into USB on my computer, but never when plugged into AC or car charger.
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
I would find someone with a vivid and try on it, maybe the battery is dead.
Sent from my HTC Vivid via Tapatalk
Mad Medik said:
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
Click to expand...
Click to collapse
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
rquiett said:
Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Click to expand...
Click to collapse
It looks like this is bang on. Apparantly computer USB ports for USB 1, 1.1 are minimum 200 mA with 500 mA recommended. Not sure about USB 2.0. Interestingly there is a proposal for USB 3.0 to allow for 20 Amps or more so you could easily power a laptop and other devices through a USB connection.
The HTC Holiday draws something more than 500 mA and presumably a max of 1 Amp as this is what the included HTC wall charger is rated for.
Anyhow, I guess I will have to pick up a new car charger, because the USB port in my car only pushes 500 mA max, and same for my current car charger.
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
jebise101 said:
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
Click to expand...
Click to collapse
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Mad Medik said:
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Click to expand...
Click to collapse
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Pirateghost said:
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
Click to expand...
Click to collapse
jebise101 said:
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Click to expand...
Click to collapse
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Mad Medik said:
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Click to expand...
Click to collapse
once you have done your recovery you dont need to do it again until you update the recovery with a newer version. its a one time thing, unless you relock stock RUU the device.
the ph39img.zip was configured for at&t vivid. you would probably need to modify it for any other holiday device.
if you are restoring from a backup, did you make sure and flash your boot.img from your backup first? otherwise you will be stuck at that HTC screen for a lot longer....just boot into HBOOT and flash the stock boot.img
Hi guys.
My note has been doing this for the past week or so:
The phone says it's charging, there's a lightning bolt sign in the battery symbol most of the time, then it'll flash off to just show a battery symbol (as it should be when not plugged in) then it'll change to just a black space. Then it'll flash back to a charging icon, then normal, then the black space, it's a cycle.
When it is actually plugged in it doesn't do the above, it just says it's charging and it does charge. But it won't let me connect USB or anything as it thinks it's already plugged in?
Does anyone know any fixes?
I've already changed to Jellybean firmware, factory restored, did a restore on CWM, wiped caches etc etc and still broken?
Anyone had the same problems? Or know any fixes?
Thanks in advance.
Oli
Try a different kernel (probably the culprit) ... also try pulling out the battery for 10 minutes
Sent from my GT-N7000 using Tapatalk 2
Pulled the battery out mate, but yeah will try an alternate kernel
It might be a problem with your phone's usb/charging port
Just try cleaning the charging port
The same thing happened with me I just cleaned the usb port with tooth stick slowly and worked again like charm it has been like 2 months till now If I helped jus click the thanks button enjoy yr day
micro usb port problem possibly... clean in
Sent from my GT-N7000 using xda premium
Have tried to clean out with a tooth pick, how else could I clean it?
So do you find any change after cleaning it
Still the same
oli3107 said:
Still the same
Click to expand...
Click to collapse
Is it happening with all roms including stock or just CM based? If its cm specific then try flashing stock rom.
Its because phone detects your phone is already connected. Just get your usb port replaced and it will be okay hopefully..
My GT-N7000 yesterday developed this issue:
When I boot it (no USB cable to power it), the battery shows empty (grep battery icon, with a charging circle).
A second or so later, it switches to show a half-full battery, with charging dots below. and it vibrates for about a second.
Again, another second ro so later it goes back to showing an empty battery and the cycle continues.
If I attach a UCB charging cable, it boots fine, shows the battery as 100%
If I remove the charging cable, it loses power. When switched on again, this all starts over.
I saw this on ICS (4.0.4, stock, German) and there i also had the battery icon in normal more switching between
charging and blinking to not charging. I found a recommendation that upgrading might help, so I
did apply the JB update I had downloaded a few days ago, but this does happen
under JB too (OTA German 4.0.4, then flashed with Phil's-stock plus cwn6)
Is there anything can can be done? Is this a hardware issue or something that some form of total reset might cure?
As it is, I cannot use the phone w/o having it externally powered through my powerbank or car charger.
This happens with two batteries, so it's not the battery that is broken
I really think this one is battery problem as I have experienced the same thing..
are the batteries you tested New?
just my 2 cents.
Sent from my GT-N7000 using Tapatalk 2
noteandfound said:
I really think this one is battery problem as I have experienced the same thing..
are the batteries you tested New?
Click to expand...
Click to collapse
No, I've had both a fow a while.
I may buy a third just to test but I fear I may have to get a replacement phone soon , sniff
Though I would suggest that you get a new set of batteries...they solved the problem for me.
While you are at it, please search the forum for another solution that worked for me- "cleaning the micro-usb slot"...its an easy process but needs to be done a little carefully.
either of the two would definitely work for you...speaking from experience!
sejtam said:
No, I've had both a fow a while.
I may buy a third just to test but I fear I may have to get a replacement phone soon , sniff
Click to expand...
Click to collapse
Bro..i had the same problem..this morning,when the phone showed 100% in charged mode..as soon as i unplugged the charger..the charging %age goes down to 15% immedietly.. i went and bought a new charging port(only that usb charging port = very small),removed the old usb port and soldered the new usb port to the note..This works like charm..but this probably void the warranty ..so,if u want..its upto u..i wont recommend it but it works like charm for me
Get a new battery
Sent from my GT-N7000 using Tapatalk 2