Related
I'm very confused about battery use that my Tab shows. I installed Overcome ROM v2.0.1 HERMES Rom, everything is working fine, but... same problem i had with stock Froyo. Screen capture included in post...
Is this OK?
Samsung Galaxy Tab, buyed in Croatia, T-Mobile
Why not? What would you expect to see for power use?
How long between charges ?
You didn't understand, i think that display must be on the top of the list.
Isn't that how it's supposed to be.
Sent from my GT-P1000 using XDA App
So, it's a bug? Of ROM or...? And is there a solution?
Every Gtab Gingerbread Firmware has Android System on top, it seems to be different from Froyo where we had Display on top, though battery performance seems the same as before.
That was my case.
Solved with new Overcome v3.0.1-JUPITER
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you on a custom rom or stock rom ?
If on custom what rom and kernel u using?
Flashing another kernel may help
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you sure it's totally off? I had this issues when phone looked like it's turned off, but when I pushed buttons for a while it was waking up, so I didn't have to restart it. Some people recommend using jBroid Kernel Cleaning script before you flash new kernel.
And if it's happening after installing new ROM I would recommend to flash stock ROM, then doing a full wipe twice and then flashing ROM you currently use or want to use.
I don't have such problem anymore so it might help.
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
docsportello said:
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
What apps do you have installed? I had this problem with both WidgetLocker and NoLed.
WidgetLocker I have just given up with - wish id never bought the stupid thing, as it's never worked reliably on my Note or my tablet! (rant over).
NoLed I traced the problem to the flash-the-screen battery saving features. Changing it to leave the screen on all the time when notifying hadn't seemed to use any more battery life and my dead screen problems have gone away.
Just something to consider!
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
squicky said:
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
Click to expand...
Click to collapse
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
kelvin fong said:
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I think its a stock kernel and ROM he's on... Even though he says 'custom ROM' he also says its never been rooted, so how would he get the custom ROM working if not by rooting the phone?!
That being the case it must be something interfering with the sleep mode so its probably best to check what has been installed recently, remove those apps one by one over a period of time and check if the problem goes away!
Yes it's a stock rom I am using and the issue happens randomly... Is it maybe lockscreen app? I read the users' comments and no one mentioned such a problem...
Sent from my GT-N7000 using XDA
me too my ho jus shuts off by itself.. I m using KL1 kernel wif KL3 rom
Note randomly shuts down - Did you solve this issue?
Hi,
I was wondering if you managed to solve this issue as I am experiencing the same issue where the phone randomly switches off when the screen is locked.
I am using easy battery saver app which sets the sleep schedule to check network data every 15 min.
Cheers
Galaxy Note 2 shuts down
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
thanks for the heads up with NoLed....I just hope my issue ( phone's screen just dies when not in use - but I think the device is on as the headphone jack responds with the disconnection sound when unplugged) gets resolved...
I was thinking too that philz cwm may be affecting it ( kernel issues )? ...any way I will update as time passess
Since the LPY update my Note got really hotter on regular use (phone call, internet browsing), Am I an isolated case?
No you're not alone, I've noticed same with mine since installing lpy.
Not sure of the cause, gonna try full wipe and re-instal.
Sent from my GT-N7000 using xda premium
Mine gets hot too. I installed it as a full wipe. Just waiting for UK ics before I do another full wipe.
DON'T WIPE!!!! It could trigger the eMMc bug. I did the same and now I am scared to flash anything official or not. Read before you do anything and don't use CMW or stock recovery unless it's absolutely necessary
jimsey said:
No you're not alone, I've noticed same with mine since installing lpy.
Not sure of the cause, gonna try full wipe and re-instal.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1633938
don't wipe or it will die!!
It's heating my phone's upper area only
Sent from my GT-N7000 using XDA
I think it is mostly due to Deep Sleep bug and incorrect modem.
_A.T.Omix_ said:
Since the LPY update my Note got really hotter on regular use (phone call, internet browsing), Am I an isolated case?
Click to expand...
Click to collapse
Same here. I have seen a masive increase in temperture as stated above on the top part of the phone. Using a temperture app i get from 38 to 41C in some cases.
Sent from my GT-N7000 using xda premium
Same with me, just upgraded my phone to official ICS and the phone is overheated, battery drain !!
Hope they solve this ASAP.
ICS makes use of dual core (GB just single), so yes...it will always be a little hotter than on GingerBread.
To check if your phone enters deep sleep, install CPU SPY from Google Play.
If it has a lot of awakenings (see battery stats on settings) use betterbatterystats to check what process / application is awakening your phone.
Hope it helps...
nunosm said:
ICS makes use of dual core (GB just single), so yes...it will always be a little hotter than on GingerBread.
To check if your phone enters deep sleep, install CPU SPY from Google Play.
If it has a lot of awakenings (see battery stats on settings) use betterbatterystats to check what process / application is awakening your phone.
Hope it helps...
Click to expand...
Click to collapse
This is correct
[FiX] Galaxy Note ICS OVERHEATING PROBLEM SOLVED
[FiX] Galaxy Note ICS OVERHEATING PROBLEM SOLVED:
1 Go to settings- developer options - UNCHECK "Dont keep activities"
2 Use go launcher ex (or some other good launcher...) instead of default launcher
3 Instal from google play android assistant and use it to clean cache and stop most of background process
4 install from google play "cpu master free" (MUST HAVE ROOTED PHONE) and set 1000 MHz for MAXIMUM, and check box "set on boot"
5 Turn off gps, bluetooth, sinc, WiFi, Packet Data and all other stuff that you dont use at moment...
P.S. DO NOT expect that your phone will be cold as ice after you do this...
ICS is build that you can use max. out of dual core, and galaxy note is pretty slim and back is made out of plastic...All that increase heating problem...
Hope i helped! =D
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
Has anyone found a solution of new firmware (custom or stock)
that fixes this issue where you have no idea of your battery
level and your battery can be ruined because it drains too far?
Can anyone confirm if SONY is aware of this major problem?
How do you use your device with this issue? Any tricks you use
to live with it?
Can anyone confirm when they upgrade to firmware 4.2.2
ie: 10.3.1.A.0.244 or 10.3.A.0.423
they have killed their battery completely?
(ie: it won't take a charge anymore and the phone is ruined?)
> It happens when your battery is 20-35% and u do a battery reset (power+volup)
SO, as long as you don't do this, you don't get the bug?
-Why are you performing this action anyhow?
-Why not just hold the power button and restart your device that way if needed?
Can anyone confirm if a regular reboot (using either the reboot command from terminal or by using an app to reboot) also triggers the bug?
> Installing the 4.1.2 binary does NOT fix the issue;
What if you roll back to stock 4.1.2, or you are on 4.1.2?
Is the bug for sure not there?
Is the bug just on all versions so far of stock and custom 4.2.2?
Is the bug on 4.3?
Does the bug cause the device to think there is more charge than
the battery actually has, thus draining it too low and killing it?
What is the best way to fix the bug once it occurs and is
there any way to tell if the bug is occurring? Someone mentioned
charging it all night is the only way you know you are at 100%?
What devices is the Battery BUG on besides SONY XPERIA Z (ie: model C6602)?
So, to live with this bug, never reset your device, and if you do,
do it before you put it on your charger for a very long time?
Btw, how long would it need to be on the charger worst case?
Battery bug is most likely due to battery stats. Once they are cleared/ reset then the bug goes away. See if u can reset them in cwm or twrp. It has nothing to do with the hardware. I always flash roms on full battery and never had that bug.
Sent from my C6603 using Tapatalk 4 Beta
Wiping battery stats does nothing.
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
Also, the bug is very real - http://forum.xda-developers.com/showthread.php?t=2348174
Sent from my C6603 using Tapatalk 4
I found a solution don't reboot or turn off your phone
Sent from my C6603 using xda premium
Maybe I didn't got the bug because last time I had to was about a month ago, when flashing new rom. Well I did flashed some mods as well. Maybe reset stats while on 100% and flash new rom.
Sent from my C6603 using Tapatalk 4 Beta
LOL. Resetting stats does nothing! It deletes the batterystats.bin file. That file is deleted every time your phone is charged anyway and doesn't have any effect on the battery percentage that is displayed.
Please read the article I linked you to earlier.
Sent from my C6603 using Tapatalk 4
I never had the battery bug!
I've a C6602 and from the original 4.1.2 and the following updates (now the 4.2.2 [0.244]) always the battery was correct!
I've also used all the above-mentioned method of reboot...
because of some games (specially Let's make pottery) and reboot to CWM or normal Reboot with Powerwidget never made the bug!
hope that helps!
The bug is fixed on the latest 244 update.
Hi.
I never had this battery bug on my XZ.
Me too, I don't have this bug before and after 4.2.2
I've had this bug for a long time, but once i've flashed cm 10.2 it's gone.
Gesendet von meinem C6603 mit Tapatalk 4
sebastianlow said:
The bug is fixed on the latest 244 update.
Click to expand...
Click to collapse
Don't think it is
Sent from my C6603 using xda premium
MAJOR BUG Check
Odd. Some people have this MAJOR BUG and some do not??!?!
I will upgrade my UNITED STATES phone by flashing an .FTF.
I'll see if I get this BUG or not. Anyone have a link to
C6602_10.3.1.A.0.244 .FTF for UNITED STATES that doesn't
think they have this bug?
> u shud calibrate the battery in order to get exact output.
Anyone know how to do this?
emrause- you say you don't have the bug on 0.244.
Did you flash your .ftf and which one did you flash?
Are you on stock rom? What is your region?
sebastianlow-
I have read several posts that the bug is still there in the 0.244 thread.
Is it gone for you and did you flash the .FTF? Which one?
> It seems that Spanish FW is free from this bug.
I thought if we flash the .244 .FTF there is no difference in regions!?
Can we safely flash it to our United States phone?
Anyone have a link to it? Will anything change to Spanish?
Does anyone know where to get the latest good .244 .FTF
10.3.1.A.0.244 that we can flash to our United States phone?
I was going to use C6602_10.3.1.A.0.244_Generic India.
Is this one not good and Spanish one is?! Will it change
our keyboard or language or radio stuff incorrectly?
kingvortex- Do you have the bug? Which firmware are you using and did you flash a .FTF?
Did you roll back to 4.1.2 or are you living with the bug?
As long as we don't reset the phone around 20-35% with a battery reset (power+volup)
are we ok? Also if we do reset, just put it on the charger for a long time?
Anyone know how long it takes to fully charge a SONY XPERIA Z roughly before it
switches to trickle charge on the standard US plug adapter?
Anyone have quick answers to any of these or any input on this battery bug?
I'd like to flash the latest to my phone. I have a United States Phone.
Is flashing an FTF a good way to update? What method and
which .FTF should I use? Does the region matter? Anybody have any ideas or links?
Anyone know if the New firmware: 10.3.1.A.1.10 addresses this BATTERY BUG
or is this MAJOR BUG still there?
TIA
its a sony kernel level bug, no solution unless you use a custom kernel which is NOT based on sony source, unfortunately, we have no such kernel at this moment
My xz has battery level bug with 4.2.2 423 and 244 versions. it had not any bug when 253.
Does 10.3.1.A.1.10 fix it possibly?
Do they list frmwares and what is in them anywhere? (ie what fixed)
Also, how do you live with this bug? ie- what do you do so your battery doesn't get ruined and so
you know when your phone is running low if the battery indication is not reliable?
Is the trick to this bug to never reboot your phone during the day and if you do, always charge it
for a long time (ie 100% plus trickle charge) and then the battery is always correct?
This is a pretty major bug. Does SONY know about it?
kkd28- Are you going to roll back to another firmware which does not have the bug?
Do you never reset your device so the bug isn't much of a problem for you?
Anyone else roll back because this battery bug is so bad?
Anyone suffering from this bug can kindly post here a few debug info about the battery?
Those relevant files are on this folder: /sys/devices/platform/msm_ssbi.0/pm8921-core/pm8921-charger/power_supply/battery
The charge_full, charge_now, voltage_now and capacity are the relevant ones. The the last one should be the same number as the capacity listed on the Android user interface, but it wouldn't be true if it is a ROM issue rather than a kernel one.
It is possible to analyze the health of the battery with those numbers. There is also a health file on that folder, whose content should be "Good" otherwise you are on a bad shape.
It should be noted that Android will use the current voltage, not the current charge, to decide when to turn off or stop charging a battery. Also it should be noted that as long as the battery is healthy, there is no risk ruining it even with a bug on Android. Those batteries have a swicth which will be activated in case of low voltage and it will suspend the power supply.
There is no risk in ruining your battery except you are draining it too quickly.
It would be even better if one could post the content of those files right before and after the bug happening.
Regards,