So why is it that even when I running a 1.3Ghz phone sometimes games like Dungeon Defenders run REALLY smooth and no issues, but then later I will try to play it and it will run like a bag of spanners, and is completely unplayable?
Rebooting phone often sorts this out, but why should I have to? The GPU has dedicated RAM, all unnecessary applications have been shut down, even put into flight mode.. and still it freezes for seconds (sometimes for a LONNGGGG time), and just generally stutters badly on the screen.
I thought maybe it was to do with the stock rom, but a factory reset proved that the stock rom is fine, but later it screws up. So I try the V20Q rebuilt rom, and stefans's gueste kernel and it still does it.
What is going on? Is the phone running out of resource? Is the second CPU not starting up? What is going on, and how can I find out?
Does it happen after at least 24h of runtime?
No. I've not measured it, but can happen within 8 hours I imagine. I have tried different batteries to rule out a voltage problem.
Is there a memory and dual CPU monitor tool I can use in the back ground to try and find out the problem.. or at least get a head start on the issue?
Oh forgot to mention, whilst it's lagging, even on the initial Dungeon Defenders start up screen... it's very unresponsive, and can take several seconds to identify I pressed something.
Scougar said:
No. I've not measured it, but can happen within 8 hours I imagine. I have tried different batteries to rule out a voltage problem.
Is there a memory and dual CPU monitor tool I can use in the back ground to try and find out the problem.. or at least get a head start on the issue?
Oh forgot to mention, whilst it's lagging, even on the initial Dungeon Defenders start up screen... it's very unresponsive, and can take several seconds to identify I pressed something.
Click to expand...
Click to collapse
If you want a monitor tool, use system panel pro version.
However if the phone begins to be unresponsive after some time, it is because there is memory leak. It is a common problem in stock-based roms. ATM only reboot can solve this issue.
If you flash CM-based roms, the phone will be always smooth.
I did download system panel lite, but will grab 'pro' on Wednesday to help monitor the cpu usage (both cores) and free memory etc.
I actually like the stock V20Q rom... real shame :-(
markop90 said:
If you flash CM-based roms, the phone will be always smooth.
Click to expand...
Click to collapse
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
I will buy the system tool tomorrow and try and monitor what the heck is going on.
It should easily be running this program, there is no reason why it's performing so badly and causing the phone to be unresponsive.
Interesting... whilst running Antutu today, I only got 4900 to 5000 points @ 1.2Ghz. I can get about 7000 at this speed so I wondered what was going on. I checked out systempanel, and it appears to only be using 1 core. Hmm...
@-sandro-
What kernel do you use?
With ironkrnL 32 or 48 there is no lag. Not even after a week without switching the last reboot.
As per sig, using Stefan's gueste v1.1 kernel for stock rom's (V20Q).
(My setup is his kernel + the rebuilt V20Q italian rom from LG with the 'tweak' pack).
Is the ironKRNL compatible with V20Q stock?
-sandro- said:
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
Click to expand...
Click to collapse
You just have an unstable setup, I haven't rebooted in days and I'm running smooth
IRASadPanda said:
You just have an unstable setup, I haven't rebooted in days and I'm running smooth
Click to expand...
Click to collapse
I could say my phone runs "smooth" but then I bench it (The bench will show bad results), or play a game and it can be a stuttery mess.
-sandro- said:
wrong. It happens in CM roms too I have to reboot every day to avoid starting to experience lagginess which becomes unbearable on day 3
Click to expand...
Click to collapse
NEVER happened to me with CM7...it has an excellent memory management
Please, I don't want to discuss different ROM's. I would like help diagnosing the cause
I have now put on gueste v1.2 release candidate, and can see the 2nd core activating earlier. However, I'm still getting random results, and I can't say for sure whether or not the CPU 2 is activating as system panel isn't historically recording the CPU level of CPU 2 individually :-(
In Antutu.. you can see the FPS is down as well even after running a 2nd time. It's all very wierd. (I got 7250, then the next run I got 4900(ish) !)
EDIT: Upon testing, what I noticed the most was that CPU Floating point scores and 2D graphics were at least half of what they should be, whilst 3D score was barely affected at all. This to me points to an issue with the CPU side of things.
Related
I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?
I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12
Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.
The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.
If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.
Hey Guys, I've posted in other conversations about bad battery life with blitzkrieg and it seems pretty split down the middle between those who experience good battery life and those who don't. I did follow the advice and wait several days after I re-flashed blitz and my battery has yet to level out. I keep background data off at night when I go to bed, I went to bed with 93% battery left and woke up 7 hours later with a 23% battery life - while the phone was at rest.
I also have a problem about once every two days my phone will freeze up and restart. When it happens it just gets froze on screen and the whole phone vibrates for 20-30 seconds and then restarts.
Has anyone experiences these problems and found a solution to them? Should I change my settings at all?
I really don't want to get an extended battery but with the life my phone is currently getting I don't see much more of an option.
Thanks guys,
The phone freeze/reboot is a known issue with no known resolution. Before I dropped my last phone it had that problem consistently from stock v4 through every variant of the ota updates, revolt roms, gingervolt roms, kennels, scripts, no scripts, blah blah etc.
Now, however, I picked up a second Revo and have run it through gb and flashed gv 1.3, blitz 2.1 and various scripts and tweaks virtually mirroring my old device. I did that Monday morning and haven't had a single instance yet! These guys here do awesome work..
As for the battery draining, I haven't put my extended battery back on this phone yet because I was curious how the stock would perform with these mods. For the first couple days I was discharging at an even 10% an hour. Yesterday and today its dropped to 7.5%. Why? No damn idea. But I can live with that.
So, nothing terribly helpful here but just a disclaimer that your mileage may vary and a nod to the devs here doing kickass work. Good enough that I actively went looking for another Revo instead of fussing with a second line upgrade. That speaks volumes.
Oh yeah I'm not dissing the devs at all they're great!
The revo is a strange device all the reboots due to GPS and airplane mode I'm sure is a hardware fault because every revo I've had has done it and I'm on my third. I love blitz and can't live without my overclock lol I'm just wondering if there's special settings or CPU governors I'm not using that would help.
Sent from my VS910 4G using XDA App
I've used CPU Master and am on ROM toolbox now. Can't say I've seen a significant difference between the two as far as battery goes. I've used both ondemand and smoothass, same deal.
I did have some luck limiting reboots on my first by bumping up the min to 768 but haven't needed to bother on this phone so its 2 something. No extra settings or anything. : )
Guess it's just the screwy differences in hardware that make some a better build quality than others. Well I said I wouldn't do it, but I lied...
I'm restoring to my GV 1.3 pre-blitz image as I type this. Guess I like battery over performance, we'll see...I may be back to blitz.
Can somebody explain the difference between ondemand and smoothass. I still don't understand them that well. Thanks!
I didn't read the whole thread but seeing profiles for the kernel helps a lot like when my screen is off my phone is set to minimum on the min and max which sometimes causes lag turning on but once the screen comes on it's up and running fine. At that level if I keep the screen off it takes nearly an hour to drop a percent.
Sent from my VS910 4G using xda premium
Perhaps this is not the best reference but here is one about charging your Lion battery:
This link won't paste:
[URL="http://dottech.org/tipsntricks/17705/tip-condition-your-new-cell-phones-battery-to-make-it-last-longer-but-be-sure-to-condition-it-properly/[/URL]
It points out two possible issue:
1) over discharge (perhaps our meters account for this,
2) getting the battery hot, my phone does warm up setting on the charger, sounds like the usb port charging might be better for the battery?
I've been using the note for a few days now, i've noticed that it heats up quite a lot. Under charging it is understandable... But even when the screen is on for is say 10-15 mins straight... Does anyone elses phone heat up too?
Sent from my GT-N7000 using XDA App
yep, every smartphone I have used does that (GS1,GS2, Note, Tab 7" tab 10.1) and some feature phones do it (iPhone, HTC wildfire etc).
Think about it, dual core 1400mhz running, and batteries always heat up with heavy drain and charging.
Mine has normal temperature under regular use (IE a browser etc. - not really causing higher load), gets quite warm if playing a game for example (higher load, not sure how high).
How long does your battery last? (heat = energy)
I used to have over heat issues but eversince i use franco's kernel 6 the issue has gone away.
i use sfock LA4 with root, bloatware removed and franco's kernel. all good and no heatind issues even when charging.
There is an app called "Elixir" that can monitor the temp of the various sensors within the phone. I've used it on every device I put a custom kernel on. Setup a homescreen widget so you can see the temp at all times. If it tops 45c then you panic a little and let it cool down
which rom and kernel did u use?
Mine heats up only when I charge. I don't mind, I like warm stuff.
Mine gets pretty warm too, especially at extensive use and charging at the same time.
yeah mine gets warm too, especially when browsing using Dolphin browser. The highest temp it touch is 51 degrees. Other than that it quite ok. Usually temp between 28-31 degrees.
When I was on stock rom and connected to gps +charging at the same time, my note used to heat up to extreme temperatures. enough to make me want to shut it off to avoid any hardware damage to internal circuit. It used to become burning hot at the top part of the phone. Now I have LA4 rooted stock rom with bloatware removed and using franco's kernel #6. Now my phone barely gets warm when I am charging and using gps at the same time.
aftabbabar said:
When I was on stock rom and connected to gps +charging at the same time, my note used to heat up to extreme temperatures. enough to make me want to shut it off to avoid any hardware damage to internal circuit. It used to become burning hot at the top part of the phone. Now I have LA4 rooted stock rom with bloatware removed and using franco's kernel #6. Now my phone barely gets warm when I am charging and using gps at the same time.
Click to expand...
Click to collapse
I am on rooted la4.
Exactly what is safe to remove in terms of "bloatware"?
Did you just flash franco kernal 6 with mobile odin over the rooted la4?
Yes, my phone used to heat to levels you couldn't even hold it or touch the screen or your finger would burn. That happened with GPS or PocketCloud. After putting up Franco's kernel, heating is totally gone.
Sent from my NotePhone
flash francos kernel in recovery from cwm. I deleted all samsung apps and all the apps i wll never use. the list is long. there are threads where people list the apps that can be safely removed.
I'm in the boat as gent0r mine will get fairly warm when used under heavy work and charging. But its alarming at this point. Not like sarius where he thought it was melting his case!
Sent from my Xoom using XDA App
mine always with <50c still acceptable for me
I used Franco's latest kernel and my Note's temperature suddenly went up.. it raised the heat more...
I reflash back to Abyss Note and the temperature is back to Normal again..
Usually heating issues are caused
1.) when your using Data Connection thru Carrier (surfing, auto-syncing emails, news feeds, twitter, facebook and etc.)
2.) when your playing graphic extensive games
3.) and lastly when your Note's display is always ON, all the time (like watching movies all the time.)
mine doesnt really heat up, except one time when using titanium backup. the process just stopped and the phone got extremely hot.
it never does that in normal usage though
we must remember we are taking battery temperature as an indication to CPU temperature. In reality your CPU could be getting fried at 50 degrees battery temp depending on circumstances. We news to access the CPU temp sensor if there is one. Does the phone shut off when overheating? Like a failsafe? Or is it just the hardware failing?
Edit - the reason I say this is I remember on the n900 forums a guy dismantled his overclocked phone which was dependent on battery temperature (safe temperatures were established and overclock was dependent on battery temp) and when he saw the state of the main board and scorching around the CPU he was very shocked.
Sent from my GT-N7000 using XDA App
letters_to_cleo said:
I used Franco's latest kernel and my Note's temperature suddenly went up.. it raised the heat more...
I reflash back to Abyss Note and the temperature is back to Normal again..
Usually heating issues are caused
1.) when your using Data Connection thru Carrier (surfing, auto-syncing emails, news feeds, twitter, facebook and etc.)
2.) when your playing graphic extensive games
3.) and lastly when your Note's display is always ON, all the time (like watching movies all the time.)
Click to expand...
Click to collapse
Its always best to reboot 2 or 3 times after flashing a new rom or kernel. Also wiping cache n dalvik helps.
While flashing new kernel, always use kernel cleaning script. I have been using battery indicator pro till now, will try the mentioned sw 'elixir' n see the difference.
Franco v2, speedmod v1 are better kernels imo.
Moved To Q&A
Please post all questions in the Q&A section
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch. Betterbatterystats gave a temperature of 52C and avg of 50. Needless to say, my battery also runs out very quickly like this, also dropping about 5% an hour when the screen is off.
Another thing I've noticed is that SDcard takes 25% of my battery usage, and when I go to storage settings, it will infinitely calculate. I mounted my storages and chkdsked them, fixed some corrupted files but the problem still persists. The only storage I haven't mounted is the internal storage, which I'm unable to do. I can't seem to connect to adb from recovery and mounting /data alone does nothing. After about 10 mins of using the phone, it becomes too hot(burns my hand) and it will shut down.
I've replaced 2 batteries so it's very unlikely that it's a battery issue. Also tried other chargers and wiping everything.
Phone OS: 4.1.2 stock LT5 before.
Did factory wipe/dalvik wipe + flash to CM11 4.4.4 and the problem is still present.
Betterbatterystats doesn't indicate a draining app, just high temperature.
Removing the external SD card and sim card had no impact.
I'm getting deep sleep when I turn off the screen, so it's not media scan being stuck. Mediascan disabled and problem still persists.
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Poopfeast said:
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch.....
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Click to expand...
Click to collapse
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
julian67 said:
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
Click to expand...
Click to collapse
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
edit: just flashed to omnirom and it's still burning my hand.
In the team win recovery repairing internal storage gives me the error: unable to repair /emmc, so I just wiped it, problem is still there.
Poopfeast said:
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
Click to expand...
Click to collapse
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
julian67 said:
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
Click to expand...
Click to collapse
Thanks for taking your time to write this. I've already disabled GPS/sync and turned on power saving. Clearing the storage now lets android calculate properly, and the Media/sdcard is gone from battery usage. But it's still running very hot and draining. CPUspy says 20% on 1400 and the rest on 800mhz when I'm using it. The system is freezing often and generally really slow.
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.
Temperature seems to drop to a reasonable 35C when I'm in airplane mode.
With everything on and sync off it's not going above 40C even when watching videos or something, so I guess it's all good now.
So basically what I've done to fix it:
Wipe internal storage and repair all partitions
Flash to OmniROM
Turn off Sync/GPS
Problem seemed to be mainly on the internal storage corruption, maybe related to my bugged chip.
Poopfeast said:
.....
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.......maybe related to my bugged chip.
Click to expand...
Click to collapse
According to eMMC Brickbug Check my Note is exactly the same as yours - supposedly "Insane chip" but Memory check passed with no problems, and guess what? It works 100% perfectly running 4.1.2 rooted. I have the full capacity of storage available to me, apps do not freeze, everything works as good as new. It is absolutely stable and reliable and terribly boring (just how I like it). It never surprises me or does any weird stuff at boot or crashes or freezes. All the hardware features work, all the supported video and audio codecs and formats work, the networking is rock solid, I can rely on my VPN when away from home, GPS gets a fix in no time, battery life is excellent, video playback is great etc. etc..
I bought my 16GB GT-N7000 a few months ago, a used item on ebay. It is an unlocked retail UK item (boxed with all manuals, paperwork, accessories etc) so no network/vendor bloatware but it was supplied by the seller with Supernexus ROM installed and was obviously suffering from the usual problems often described by users of custom ROMs on exynos. After various frustrating episodes and trials of different ROMs I used ODIN 3.09 to flash an official Samsung ICS 4.04 firmware and 16GB pit file to restore the partition table and stock firmware. Then I ran Kies on Windows XP on the "virgin" restoration. It recognised the hardware and the firmware and notified me of the update to 4.1.2. I went ahead and updated over ethernet and also captured the official 4.1.2 firmware for purpose of backup.
Since then I have tried out various ROMs and have always been able to revert to stock Samsung 4.1.2 via ODIN and without going back to the scary brickbug "insane" ICS versions. As far as I can tell the brick bug is irrelevant if you aren't stuck on ICS. After trying numerous ROMs of various android versions I am in no doubt at all that if you spend half the time setting up a rooted stock Samsung firmware as most people spend setting up ROM X/Y/Z you actually get a much more reliable and useful device.
If you need a known-good pit file for a 16GB GT-N7000 you can use this: ftp://takla.linuxd.org/Q1_20110914_16GB.pit
I had a similar issue lately. Go to developer settings and activate the cpu load display. Processes and their cpu load along with a bar graph will appear on the screen. I found out that google's music app was hanging on my phone. This did not show up in BetterBatteryStats!!!
My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.
Ahmer Jamil Khan said:
My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.
Click to expand...
Click to collapse
Flash factory image, lock bootloader, and RMA.
Evolution_Tech said:
Flash factory image, lock bootloader, and RMA.
Click to expand...
Click to collapse
What is RMA?
Ahmer Jamil Khan said:
What is RMA?
Click to expand...
Click to collapse
Returning the phone to the seller to be exchanged for a new device. RMA https://www.google.nl/search?q=rma&ie=utf-8&oe=utf-8&gws_rd=cr,ssl&ei=sihYVcWrCcyBU-vVgIgM.
gee2012 said:
Returning the phone to the seller to be exchanged for a new device.
Click to expand...
Click to collapse
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?
Ahmer Jamil Khan said:
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?
Click to expand...
Click to collapse
Probably a hardware issue, it can happen
Probably not a good idea to charge in recovery as all cores are always maxed out, causing it to be hot anyway.
Reflash the stock kernel using the flashify app from app store. This will rule out software issues
https://play.google.com/store/apps/details?id=com.cgollner.flashify
After looking at thread like these , i am reluctant to use the Quick Charger that came with the phone. I normally charge the phone with USB (PS4) or a normal Samsung Charger
Where people go wrong is using the phone while fast charging. Playing a graphics intensive game or streaming video while fast charging isn't typically good for battery temps
No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.
madmartian said:
No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.
Click to expand...
Click to collapse
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:
simms22 said:
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:
Click to expand...
Click to collapse
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.
madmartian said:
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.
Click to expand...
Click to collapse
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.
I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.
danarama said:
I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.
Click to expand...
Click to collapse
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues
simms22 said:
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.
Click to expand...
Click to collapse
My results are specific to certain high-battery-drain games. I am seeing my battery usage HALVED while playing certain games after making this change. These games tend to have a lot of animation. General use or "normal" (not unusually high) battery drain games are likely closer to your 5%.
Likewise, I noticed these games use a lot less battery on my older phones (with lower resolution screens).
If a phone is overheating during "normal" (not high drain) situations, then lowering the resolution may not be effective.
my phone only heats up when it is charging goes up to 45c
simms22 said:
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues
Click to expand...
Click to collapse
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk
danarama said:
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no. it has to be run every time you boot up.