Database Develop

FRF91 Heat issues?

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!

Battery not charging after Nookie Froyo 0.6.8(eMMC) install

I tried to find similar threads but the closest I found were people having battery charging issues with Phiremod rom and they were advised to clear the battery stats in recovery mode, which I did try but still the NC won't charge.
I haven't actually let it drain to 0(it's currently at 23%) to see if it really isn't charging or if it's a software thing that is not showing the correct battery level.
Has anyone had a similar experience and been able to fix it? Or do you think it's not a matter of the installed rom and rather maybe the NC itself is "bad" and I need to return it?
Any help would be greatly greatly appreciated. Especially since this is my wife's NC and I told her how "cool" this whole rooting, rom'ing thing was and that nothing bad should happen

Most likely it's the NC USB cable. It doesn't have a good design and fails often. I had problem with mine.

DOH!
Wow this is so embarrassing.
After your suggestion, I went to go check my wife's cable and noticed that she had the right cable with the "N" all nice and lit up...to bad she had it in her HTC Inspire plug!!^%$%^! And her Inspire in her NC plug adapter.
Hmmm...now to figure out how to delete this post...don't wanna give Nookie Froyo rom a bad name but insinuating it cause charging problems.

Actually I noticed this about nook. I plug in a general micro-usb cable, the battery % doesn't change at all.
The minute I switch back to the stock NC plug (with the led logo), the battery instantly shows it fully charged.
Does this mean I can only charge using the NC cable?

duoxx said:
Actually I noticed this about nook. I plug in a general micro-usb cable, the battery % doesn't change at all.
The minute I switch back to the stock NC plug (with the led logo), the battery instantly shows it fully charged.
Does this mean I can only charge using the NC cable?
Click to expand...
Click to collapse
I believe the NC cable has extra pins that allow it to charge the NC faster. In addition, the NC charger is a 1.9 amp unit whereas most bricks are less.
A regular USB cable will charge your nook if you turn the nook off. It charges much slower though (overnight for a full charge).

Battery takes a VERY long time to charge from a wall charger

It's not normal for a nook to charge 10% -> 60% in 6 hours, correct?
Has anybody experienced the same issue?
I installed Honeycomb right after getting nook -> then i did nookie color ->
First I noticed it on Ultimate Droid FW, so I than I flashed to CW7 latest nighty with OC'd kernel, and now i am back to nookie froyo. and the issue still exists.
I haven't found any tools that do battery/power tests..
I was just charging nook for an hour, without using it.
went from 19% to 26%.
I think its quite low.
Thanks

i find the wall charger charges insanely fast. the usb charging is the one that is snails pace for me.
maybe try wiping your battery stats in CWM?

when you say "from a wall charger"
Do you mean the one included with the NookColor? or a different one?
With froyo on emmc, and HC on microSD, I find re-charging via the included 1.9A charger pretty good. Charging from a 1a cell phone charger is slow. And charging via USB port on PC, doesn't happen.

Wall charger -- the NookColor 1.9A charger.

.me said:
Wall charger -- the NookColor 1.9A charger.
Click to expand...
Click to collapse
Are you pairing that with the original Nook Micro usb cable? or are you using a different usb cable?
The cable that came with the nook as 2 extra pins that allow for the fast charging. standard usb cables wont have this.
If you are using the original cable and the original block. I would say that they are defective,
I have never heard of a Rom or Kernel effecting the charge rate like that but you might try going back to stock and see if its the same results.
*O and it should only take 3 hours from 0% -> 100% with the Nook cable and Block that came with the Nook Color."

Alright, thanks. I'll try the stock rom.
Can I exchange nook color in the store for this problem? or there's a procedure for that?
Cheers

Yeah I'd definitely say it should only take 2-3 hours to get a full charge from empty. 6 hours is way too long with the nook charger, that sounds more like the time it would take with a standard usb port charging it.

.me said:
Wall charger -- the NookColor 1.9A charger.
Click to expand...
Click to collapse
Are you using the B&N cable as well? You must use both or you'll only get .5A.

.me said:
Alright, thanks. I'll try the stock rom.
Can I exchange nook color in the store for this problem? or there's a procedure for that?
Cheers
Click to expand...
Click to collapse
Depends on when you bought it. If it's still in the right time frame, you can just exchange it in-store. If not I'd recommend looking thru the website and/or calling about it instead of going in-store since they probably know more.

I think doing the wiping battery stats in CWM did the trick.. its charging quite fast now.
Thanks everybody for your help!

i had been running into this.. and could figure it out... i will try wiping bat stats too and see how it goes... thanks for the tip!

Modify Clockwork to allow charging while off?

So I just found this:
http://forum.xda-developers.com/showthread.php?p=12513699#post12513699
and a modified version for my HTC Aria phone. It works great!
Is there any chance a dev here can modify CWM for eMMC to work in this way?

Pretty sure the Nook doesn't need any HTC hacks to charge while off.

isn't it an issue with the cm7 builds not being able to go into deep sleep (or having that option turned of or something?) cuz it causes problems with wifi?
i thought the not turning off if plugged in issue was related to this

nemith said:
Pretty sure the Nook doesn't need any HTC hacks to charge while off.
Click to expand...
Click to collapse
Not sure if you were trying to be a smart-ass or not, but obviously my Nook isn't made by HTC, however if I plug it in while it's turned off, guess what, it turns on.
I believe it's a Clockwork "hack", not an HTC specific hack, but I could be wrong.
djlim4 said:
isn't it an issue with the cm7 builds not being able to go into deep sleep (or having that option turned of or something?) cuz it causes problems with wifi?
i thought the not turning off if plugged in issue was related to this
Click to expand...
Click to collapse
My HTC Aria is running CM7 and this hack worked perfectly for it.

911jason said:
Not sure if you were trying to be a smart-ass or not, but obviously my Nook isn't made by HTC, however if I plug it in while it's turned off, guess what, it turns on.
I believe it's a Clockwork "hack", not an HTC specific hack, but I could be wrong.
My HTC Aria is running CM7 and this hack worked perfectly for it.
Click to expand...
Click to collapse
That is because it is actually supposed to turn on when you plug it in. You should have it plugged in and then shut off to have it charge while off. No need for a HTC clockwork mod, as the problem was only with HTC devices.

I know you can turn it off after it starts charging, but it's not supposed to turn on, as you say, the stock Nook doesn't.

911jason said:
I know you can turn it off after it starts charging, but it's not supposed to turn on, as you say, the stock Nook doesn't.
Click to expand...
Click to collapse
Yes it does. Plugging in any nook while off turns it on.

Really? Guess I missed that in the day or so that I had an unmodified Nook.
Still would like to hear from a dev whether or not the system could be modified to not fully boot when connected. It seem illogical to me to have a device as power-hungry as the Nook boot up when you want to charge it, which will slow down the charging process.

911jason said:
Really? Guess I missed that in the day or so that I had an unmodified Nook.
Still would like to hear from a dev whether or not the system could be modified to not fully boot when connected. It seem illogical to me to have a device as power-hungry as the Nook boot up when you want to charge it, which will slow down the charging process.
Click to expand...
Click to collapse
Day of stock? Pft 10 minutes.
But yes, it does seem completely bass-ackwards to have it do that.

Isn't this driven by the whole USB then microSD then EMMC boat loader? It makes sense to me that the device be turned on when plugging in USB if your first boot device is USB.

Ahhh... didn't realize that the Nook had USB booting, that would probably kill this. I thought it was just SD, then eMMC. Bummer.

djlim4 said:
isn't it an issue with the cm7 builds not being able to go into deep sleep (or having that option turned of or something?) cuz it causes problems with wifi?
i thought the not turning off if plugged in issue was related to this
Click to expand...
Click to collapse
It's not wifi it's the touchscreen and other parts go too far into sleep and will never recover. This has nothing to do with charging or recovery.

911jason said:
I know you can turn it off after it starts charging, but it's not supposed to turn on, as you say, the stock Nook doesn't.
Click to expand...
Click to collapse
After plugging in the USB turn your nook off by holding the power button. It will continue to charge
911jason said:
I believe it's a Clockwork "hack", not an HTC specific hack, but I could be wrong.
Click to expand...
Click to collapse
It's a hack implemented by Clockwork to replicate the same behavior that the stock HTC recovery does on your phones.
Before this hack was in place plugging in your HTC Aria while off would force it to boot into recovery with no real reason. This modification just boots into a "off-mode charging" screen which was implemented using the recovery ramdisk and kernel but a different userspace program.
The Nook doesn't need this as it's implemented in hardware quite well.
1) The nook will turn on automatically.
2) There is not enough power the bootloader will display a screen needing more of a charge
3) It seems, based on my testing, that the nook will continue to charge even when the device is full turned off.
So in conclusionL I am glad it worked for you on your HTC Aria, but this hack is for specific HTC phones and does not apply to the nook color.

911jason said:
Really? Guess I missed that in the day or so that I had an unmodified Nook.
Still would like to hear from a dev whether or not the system could be modified to not fully boot when connected. It seem illogical to me to have a device as power-hungry as the Nook boot up when you want to charge it, which will slow down the charging process.
Click to expand...
Click to collapse
From the B&N Nook Color User Guide:
To charge your NOOKcolor from a wall outlet, do this:
1. Assemble the power adapter and microUSB cable. Insert the large end of the USB cable into the matching receptacle on the power adapter.
2. Plug the NOOKcolor end of the USB cable into your NOOKcolor.
3. Plug the power adapter into a compatible electrical outlet. If your NOOKcolor was turned off, it will now turn itself on.
NOTE: Depending on how much power remains in the battery, it might take around 3-4 hours to fully recharge
your NOOKcolor. Do not turn of your NOOKcolor while it is charging.
NOTE: Once your NOOKcolor has enough power to turn on, you can see how much power remains in the
battery by checking the battery charge indicator in the right corner of the Status Bar. You may need to
drag the green NOOK symbol to the right across your screen to unlock your NOOKcolor and display
the Status Bar, which runs along the bottom of the screen.
4. Once your NOOKcolor has fully charged, unplug the power adapter from the electrical outlet. Unplug the USB
cable from your NOOKcolor.
Click to expand...
Click to collapse
Seems like there is a design reason for that.

What? You can boot off USB too? I didn't even know that!

sorry, i was totally off i guess, thanks for the clarifications guys.
I've powered my NC off after i've plugged it in and have come back to an already booted device.
This is not once or twice, it's pretty much all the time.
Maybe i just have a weird device? I DID buy it off craigslist used... but i've had no issues at all as far as user functionality goes in the month or so i've had it.

nemith said:
After plugging in the USB turn your nook off by holding the power button. It will continue to charge
Click to expand...
Click to collapse
I knew that, but was trying to avoid that step.
Thanks for all the info guys, I still think since the Nook does charge after powering off, it would be nice if someone could find a way to skip that whole boot/power-down process so I can just plug it in and walk away.
djlim4 said:
I've powered my NC off after i've plugged it in and have come back to an already booted device.
This is not once or twice, it's pretty much all the time.
Maybe i just have a weird device? I DID buy it off craigslist used... but i've had no issues at all as far as user functionality goes in the month or so i've had it.
Click to expand...
Click to collapse
Are you running the stock ROM? Mine did the same thing until I installed a different ROM. HC and CM7 both stay off when charging after I have powered them down.

I've been running CM7 nightly builds off emmc mostly, if not the tablet tweak ones before they were integrated.
Not something I consider an issue for me, but I've yet to do any complete wipe since I first flashed CM7. I might try phiremod over the weekend unless the fascinate forum blows up with new stuff (our 2.2 source code finally dropped today), in which case I'll do a complete wipe and see if the problem persists.
EDIT: Yes, i'm running with the latest OC kernel
EDIT 2: Ok... I didn't notice before, but I guess I have a sort of faulty usb? not sure but it flickers from time to time, like on and off. I've never really paid attention to it while it charges, but i just noticed that the light on the N went off and came back on a few seconds later and confirmed that it flickers from time to time on its own. So on the bright side i guess i don't have hardware with an anomaly, too bad I have a charging cable with a mind of its own

Are you running one of Dalingrin's Overclock Kernels? I'm guessing not, since that would be the only other difference.

nemith said:
After plugging in the USB turn your nook off by holding the power button. It will continue to charge
Click to expand...
Click to collapse
ADude said:
From the B&N Nook Color User Guide:
3. Plug the power adapter into a compatible electrical outlet. If your NOOKcolor was turned off, it will now turn itself on.
NOTE: Depending on how much power remains in the battery, it might take around 3-4 hours to fully recharge
your NOOKcolor. Do not turn of your NOOKcolor while it is charging.
Click to expand...
Click to collapse
Seems like there is a design reason for that.
Click to expand...
Click to collapse
I've been plugging it in and then powering it off to charge. Now I find out that the guide specifically states to not turn off your NOOKcolor while it is charging.
Will charging while it's powered off screw up the battery calibration?
edit: one thing I've noticed is that if charging powered off, the usb light never turns green when it becomes fully charged.

my captivate lag when plugin charge

i have problem on my captivate:
my phone become lag and can not control when i plug charge until i remove battery and reboot
if i use 2.3.5 KI2 then problem is solve
any tip for me?

noone.dk01 said:
i have problem on my captivate:
my phone become lag and can not control when i plug charge until i remove battery and reboot
if i use 2.3.5 KI2 then problem is solve
any tip for me?
Click to expand...
Click to collapse
I had some similar issues with another Android phone. The problem was in the charger, too much noise was bugging the phone. If you have Fast Charge option enabled in 4.2.2, the load on charger increases along with the noise in charging line. Not sure if it's your case, just sharing some experience.

Are you using a laptop to charge? I know sometimes when you charge through the laptop, media sync can chew quite a bit of cpu cycles.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

rajaaurrank said:
Are you using a laptop to charge? I know sometimes when you charge through the laptop, media sync can chew quite a bit of cpu cycles.
Click to expand...
Click to collapse
True, but only if you have USB data transfer enabled. Otherwise no data connection between the two and no media sync either.

no bro, i use default.
i have test with too much rom, after flash new rom i plug charge soon and ... lag

noone.dk01 said:
no bro, i use default.
i have test with too much rom, after flash new rom i plug charge soon and ... lag
Click to expand...
Click to collapse
Bro, the problem is in one of the following:
1. charger (try different charger of plug the phone to your computer's USB - same result?)
2. phone's charging circuit (not easy to fix)
3. battery's charging circuit (try different battery, each one has own charge control logic - same result?)

Val D. said:
Bro, the problem is in one of the following:
1. charger (try different charger of plug the phone to your computer's USB - same result?)
2. phone's charging circuit (not easy to fix)
3. battery's charging circuit (try different battery, each one has own charge control logic - same result?)
Click to expand...
Click to collapse
i think that is not my problem because on stock rom 2.3.5 and on Doc's master 4.04, my phone work normally
i think problem is on code of rom
what is your opinion?

noone.dk01 said:
i think that is not my problem because on stock rom 2.3.5 and on Doc's master 4.04, my phone work normally
i think problem is on code of rom
what is your opinion?
Click to expand...
Click to collapse
If same thing happens with different ROMs, then most likely it's not a software related issue.

If you feel it is software/rom related try "timelines usage" app (available on playstore)
That can tell you what task is occupying your cpu.
I think the issue is battery/hardware related which is aggravated by most roms..except the one. Timelines usage might help to narrow down ...
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

Re: charger lag
Another reason (not as likely) could be that the ROMs you installed had the Battery Bar option and Charging Animation enabled. I use the battery bar at the top of the status bar instead of using a battery icon or text, and the animations while charging slow my device a bit. I can't recall if the charging animation is enabled by default. If it is hardware-related, it is interesting that you are not seeing this issue while on GB or ICS.