Xperia XZ Serious Overheating Issues - Sony Xperia XZ Questions & Answers

Hey guys in the past week my XZ has been having some serious overheating issues. Even just idling at the home screen it sits at around 40-45c. It seriously makes the phone unusable since when you open anything it just warms up quick and throttles hard. I was thinking it was the last patch that came out so I unlocked the bootloader and tried out a couple of roms like carbon rom which was buggy as hell and slimbit aosp. No improvement. Tried out eXistenZ 6.0 which is what im still on now and no improvement. I honestly have no clue whats going on if anyone can help me that'd be great. Do you guys think my battery could be needing replacement? The phone isint even a year old. I have also tried the FSCv2 mod and still no improvement.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Change habit that after clean flash instantly install everything that exists in the playstore , especially various CPU/memory/battery monitors.
Install one aplication at a time until you find the problem.
btw, carbonrom Is excellent rom like all the other AOSP ROMs for the XZ

uglavnom_bezopasni said:
Change habit that after clean flash instantly install everything that exists in the playstore , especially various CPU/memory/battery monitors.
Install one aplication at a time until you find the problem.
btw, carbonrom Is excellent rom like all the other AOSP ROMs for the XZ
Click to expand...
Click to collapse
I don't think its a certain app I installed since it just started happening out of nowhere after no new apps have been installed. Android battery menu doesn't show any excessive battery drain from apps either. Even after I did a clean flash it was getting super hot and throttled in the setup process.
*Edit* It actually got to 50c while simply replying to your reply in Chrome and lagged tf out of my keyboard. Literally about to throw this phone at a wall.

So I've undervolted the cpu and the phone still reached 53c after browsing Instagram for about a couple minutes. Im seriously loosing my **** at this point. Im seriously thinking that this phone needs a new battery or something even tho its less than a year old.

Update. Did a fresh install of stock rom using flashtool and it throttled during the setup process and still throttles with no apps just trying to send a text message or simply play a song using google play music. Seriously nobody has a clue what is going on? I literally have to have my phone next to a fan just to do anything on it.

I discovered that my battery is only at 38c usualy so I think its safe to say that my battery is okay. My cpu is constantly pinned at 45+ and I only get about 3-4 hours out of a full charge. Did google play services get an update or something? I have no apps installed in my phone still. I seriously need any help

Related

[Q] How to eliminate GTALK_ASYNC_CONN wakelocks?

I have a Nexus S 3G, and installed bone-stock, and got it to idle for 3 days 19 hours, give or take.
I wanted to try CyanogenMod, installed the latest stable (7.1), disabled Data Syncing, have a single GMail account, no apps installed and lose about 2-3% per hour battery life sitting still. I'm using the GladDOS 1.8 Kernel, which is what I used to get the 3 day idle before.
BetterBatteryStats shows that I have 11m23s of GTALK_ASYNC_CONN partial Wakelocks (this is over a 1 hour time period).
I used Titanium Backup to uninstall Google Talk, and still get the Wakelocks.
I'm going to re-install stock and re-verify stock idles fine.
Any ideas? I've searched high-and-low, and it appears it's a known issue, but I've yet to stir up an answer.
Anyone?
Thanks!
-Dan
I know its been a few weeks guys and apologies for pulling this back up but i suppose its better than starting a new thread.
I have pretty much the exact same problem as plymptop above, i installed betterbatterystats and after only 2 hours its chewing through battery power and pointing to GTALK_ASYNC_CONN"my email address" /android_talk etc and beside this it says "Count: 94.
I had my phone returned to stock 2.3.3 a week or so ago and this wasnt a problem but it seems no matter what custom rom i install, i still get high battery consumption. Anything from 6-12 hours with little or no use.
Anyone got any pointers on what i can do to correct this? Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Surely we cant be the only ones having this problem?
I'm loosing the will to live because of this phone. If i dont get it sorted soon im gonna shoot it and buy the new one.
Spectre Nine said:
I know its been a few weeks guys and apologies for pulling this back up but i suppose its better than starting a new thread.
I have pretty much the exact same problem as plymptop above, i installed betterbatterystats and after only 2 hours its chewing through battery power and pointing to GTALK_ASYNC_CONN"my email address" /android_talk etc and beside this it says "Count: 94.
I had my phone returned to stock 2.3.3 a week or so ago and this wasnt a problem but it seems no matter what custom rom i install, i still get high battery consumption. Anything from 6-12 hours with little or no use.
Anyone got any pointers on what i can do to correct this? Thanks in advance.
Click to expand...
Click to collapse
Disable automatic backup in Privacy settings. Report back after this.

[Q] Processes Slowly Rising until crash when Idle

Hey everyone I have a Verizon Galaxy S3 that has been rooted and flashed with Liquid Smooth Jelly Bean.
Originally on Stock Rom (GIngerbread) It ran smooth and never really went above 600-700mb but after I flashed it, It will stay at about 600 for a while but it will slowly get higher and higher until it is at 1.5k and things will freeze and it will crash. I won't even be using it, it will be sitting idle and the next thing I know its risen to maximum capacity. I never had that problem on Stock Rom so I am wondering if it is something to do with the Roms. I've tried CM10, Liquid Smooth, and Codename and it happens with all of them. I've flashed stock aand re-rooted and everything between roms so I had a fresh start but it doesn't work. Any ideas?
Stock Gingerbread? We were never on gingerbread, just ICS. Which we are still on officially...
After you have opened a few processes and exited them do you hold down the home button until the task manager thingy pops up and then kill the ones you don't need off? If not that may be why. I have had to do that even on stock because if I forgot to kill them my phone would freeze and start crashing all kinds of stuff. On my old RAZR when I exited apps they would close after 5 or so minutes but I have found that isn't the case on the GS3.
Sent by one of my many Anthromorphic Personifications
Using back button to exit apps kill them and leave them in multitask as recent apps but they are not running. Using home button moves them to multitask as running apps and are active for multitasking. Exit with home will eat battery and memory.
I know all about killing the apps and the App Managing System. There are no open apps and not but 6 system processes running all about 10mb yet it still skyrockets and then crashes. for the time being I went back to stock rom to see if the problem persists, which if it does then i can assume its a factory defect.. But so far its not giving me any problems on stock
jesseag7 said:
I know all about killing the apps and the App Managing System. There are no open apps and not but 6 system processes running all about 10mb yet it still skyrockets and then crashes. for the time being I went back to stock rom to see if the problem persists, which if it does then i can assume its a factory defect.. But so far its not giving me any problems on stock
Click to expand...
Click to collapse
Never seen it but I stay away from CM and AOKP. Too many problems, too many broke features and too many bricked phones for me. LOL
I think i figured it out. I got rid of all my GoCalendar,GoSMS,GoClock, and GoTaskManager Widgets and it seems to be running very nicely. Those were the only things that could have possibly been robbing juice from my phone and it looks like they were indeed the culprit. Thats unfortunate though because I really liked having those widgets :crying:
So i was wrong and it still persists. Here's a screenshot of Go Task Manager where it says only 3 processes are running yet its at 93% capacity.. I have no idea whats going on and I really need help with this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay so apperently its the Media Storage Process that is killing my memory. for most people it just kills thier battery but mine has been having an adverse affect on my processing power and RAM. But glad its figured out incase anyone else has the same problem as me. They should really post that somewhere on the OP of the Jellybean ROMs because its kind of a big deal...

Will My NS Explode?

I've been having this issue the past couple of months (ever since Google updated their Play Store to the white version) -- its Android OS has been constantly around 60%:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It goes berserk like that even after freshly flashing a new ROM (4.1.2/4.2.1/4.2.2).
I'm a little worried, since I've read last month someone's NS burst on fire: http://www.reddit.com/r/WTF/comments/1ay4cd/woke_up_to_my_nexus_s_on_fireanker_battery/
P.S. I'm not sure if this has to do with this issue -- but, my NS' USB port has been damaged, and I've been using an external battery charger (+ extra OEM battery) to charge its battery.
IIIV said:
I've been having this issue the past couple of months (ever since Google updated their Play Store to the white version) -- its Android OS has been constantly around 60%:
It goes berserk like that even after freshly flashing a new ROM (4.1.2/4.2.1/4.2.2).
I'm a little worried, since I've read last month someone's NS burst on fire: http://www.reddit.com/r/WTF/comments/1ay4cd/woke_up_to_my_nexus_s_on_fireanker_battery/
P.S. I'm not sure if this has to do with this issue -- but, my NS' USB port has been damaged, and I've been using an external battery charger (+ extra OEM battery) to charge its battery.
Click to expand...
Click to collapse
disable auto update apps on play store
leap_ahead said:
disable auto update apps on play store
Click to expand...
Click to collapse
That's the first thing I did after the Play Store app updated itself and my NS' Android OS is still around 60%.
So, if this continues will my NS eventually blow up? I don't wanna risk it blowing up while in my pants pocket or while sleeping in my bedroom.
IIIV said:
That's the first thing I did after the Play Store app updated itself and my NS' Android OS is still around 60%.
So, if this continues will my NS eventually blow up? I don't wanna risk it blowing up while in my pants pocket or while sleeping in my bedroom.
Click to expand...
Click to collapse
I would say if the port is damaged you run the risk of damaging the phone further probably shorting the thing out. To say that the port has caused the issue I don't know.

Battery drain from a non-running app?

Hi. Its been a few days since my Nexus 5 battery has been drained pretty fast. Lasts only about 4 hours after fully charged with little use. Since I recently started working in a really poor reception area I figured that was the problem, my phone constantly trying to find a signal, but when I go to the details, I see that Instagram is responsible for using up 40% and it wasnt even running!
Im no developer, or even experiencied android user, but, how is this possible?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
javiwankenobi said:
Hi. Its been a few days since my Nexus 5 battery has been drained pretty fast. Lasts only about 4 hours after fully charged with little use. Since I recently started working in a really poor reception area I figured that was the problem, my phone constantly trying to find a signal, but when I go to the details, I see that Instagram is responsible for using up 40% and it wasnt even running!
Im no developer, or even experiencied android user, but, how is this possible?
Click to expand...
Click to collapse
Welcome to android and app permissions. It's accessing a number of things on your phone with location probably being the number one. Get something like xposed and app ops to tame what the app is allowed to access. You should also get gsam or BBS to get a closer look at what is using your batery.
This happened to me last night with a messaging app I used to replace hangouts. It dropped about 12% overnight with data and WiFi all off.
I looked in battery use and messaging sucked most if it up. I cleared data in the messaging app and that fixed it. Later today I switched back to hangouts until I download another messaging app. I don't trust that one now.
Sent from my Nexus 5 using XDA Free mobile app
Thanks for your reply. I'm guessing I need root for Xposed and those other apps ? Like I said I'm just an ex iPhone user who just converted to Android. So haven't given myself the time to tweak around.
Sent from my Nexus 5 using Tapatalk
you dont need xposed. looks like instagram had a stuck process or was stuck syncing. a reboot usually fixes that. there are other ways to fix things, other than installing xposed(as xposed could bring in its own issues). there are many apps out there that help, greenify being one of them. also, there are a few great apps to help you stop wakelocks that are out of control.

Cm12 Mobile radio active issue?

In KitKat Display was the highest battery drainer. Now i switched to lollipop ,
Problem is that in c12 based Roms mobile radio active time is insanly high and drains my battary a lot.(See image)Does anyone else got this issues and is there any fix for this?
I usually do clean installs of my roms. When i am in wifi my battery life is mich better.
Here is chrome for example, but nearly every APP runnimg im the background has the same behavior.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seeing the exact same behavior on my device
Same for me.
which is installed gapps?
mobile radio active
someone managed to solve it?
Same problem here, it's on majority of my apps and the screen time is all the way at the bottom. I've switched Roms, modems and firmwares. I really don't want to go back to lollipop lol.
Any solution?
Same problem here. Clean install of CM12S. When I'm on WiFi I have no problem.
I think it's this is a know issue of lollipop. No one knows why. Someone have the problem someone not...
I can suggest you to go on privacy guard and block keep alive from the apps who use most of the battery... And sometimes check if they are running and close them...
Until someone find the fix... Like Wakelock...
shrubber83 said:
Same problem here. Clean install of CM12S. When I'm on WiFi I have no problem.
I think it's this is a know issue of lollipop. No one knows why. Someone have the problem someone not...
I can suggest you to go on privacy guard and block keep alive from the apps who use most of the battery... And sometimes check if they are running and close them...
Until someone find the fix... Like Wakelock...
Click to expand...
Click to collapse
Problem also here...IT's not a wakelock issue...Looking for a fix!
This is a screenshot the difference drain between WiFi and 3G
Issue ist still there in CM12.1 . Thibking about switching back to Kitkat.
Same problem, COS12 with default kernel. I changed the modem to see if the OxygenOS' one could fix this and one particular app (WhatsApp) went from 3+ hours/day to 40min/day with similiar use and signal reception, but others remained high
Even 5.1.1 has it
I can't believe this annoying bug hasn't already been fixed as I can't believe why the entire group of lollipop users all around the world is flooding the web underlining it.
I've tried at least 3 different 5.1.1. based ROM and they all have this bug (not to mention how many different 5.1 based ROM I've already tested or 5.0.2 as well for what matters).
Funny thing tho, the first day I'm using the ROM the bug never appears: it's only after a couple of days that the mobile radio active stats spike up to 2 or 3 hours for some apps that use internet (it could be spotify, google search, etc.)
Really hope someone comes up with a fix, this is getting more than annoying...

Categories

Resources