Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Is not Sony fault, you are messing around with Custom settings and Apps. BTW, Pimp my Z1 should be coordinate with Custom Kernel like the Doom one, but you still on Locked Bootloader then you are working on Stock one which do not have the option to be tweeked. In this case half of the Setting in Pimp my Z1 will not work or will not work properly, so do not complain. Try just to find the best settings with what you got.
eclyptos said:
Is not Sony fault, you are messing around with Custom settings and Apps. BTW, Pimp my Z1 should be coordinate with Custom Kernel like the Doom one, but you still on Locked Bootloader then you are working on Stock one which do not have the option to be tweeked. In this case half of the Setting in Pimp my Z1 will not work or will not work properly, so do not complain. Try just to find the best settings with what you got.
Click to expand...
Click to collapse
Yeah, that's why i posted this topic. If i use pimp my z1 (or i guess any other kernel tuner/oc app) and change governor to performance, all lag is gone. While using unrooted stock rom with standard governors gives quite some lag and stutters when scrolling through standard apps like phone and gmail. I'm just trying to find the cause of that. Also because i can't believe that this hardware has problems simple actions like this scrolling.
I also read that on other devices like the xperia z people have problems with lag in the ui like this. So maybe it's also because of android 4.4 or something.
saintgein said:
Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
The "performance" governor is the least intelligent governor there is. It has no clocking logic. All it does is "keep CPU at maximum speed at all times". I'm sure you can see why this is a bad idea on a device that can (and does) overheat when the CPU is at high clocks, and where the power consumption should be restricted to make the battery last more. You shouldn't use performance as your day to day governor.
But it is smoother, of course. Since there is no logic, it runs at full speed all the time, while other governors only drive your CPU to 2.3GHz when it's absolutely necessary. 1GHz is more than enough for the UI (and this is in fact how "project butter" is implemented on Snapdragon phones: when there is a finger on the screen, the minimum clock goes up to something around 1GHz). The fact that you can detect lags mean that Sony didn't go nuclear and just make the CPU run too fast.
saintgein said:
Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
The best governor for me is SmartassV2 set to 1 core and the rest on either ondemand or interactive. Use Doomlords kernel along with Pimp My Z1 app for per core governors. I'm not sure of you can do that for UB. If you cant, then just change Rom for me ihackers is the smooth on stock governor, which i think is onDemand - im currently using CM11 just moved from iHackers 4.1 2 days ago
yup owns Z1 and stuff. Also if I've helped you don't forget to hit THANKS - actions speak louder that words.
Steve_max said:
The "performance" governor is the least intelligent governor there is. It has no clocking logic. All it does is "keep CPU at maximum speed at all times". I'm sure you can see why this is a bad idea on a device that can (and does) overheat when the CPU is at high clocks, and where the power consumption should be restricted to make the battery last more. You shouldn't use performance as your day to day governor.
But it is smoother, of course. Since there is no logic, it runs at full speed all the time, while other governors only drive your CPU to 2.3GHz when it's absolutely necessary. 1GHz is more than enough for the UI (and this is in fact how "project butter" is implemented on Snapdragon phones: when there is a finger on the screen, the minimum clock goes up to something around 1GHz). The fact that you can detect lags mean that Sony didn't go nuclear and just make the CPU run too fast.
Click to expand...
Click to collapse
So getting the minimum clock to about 1ghz using interactive governor should be enough?
RealiableCandy4 said:
The best governor for me is SmartassV2 set to 1 core and the rest on either ondemand or interactive. Use Doomlords kernel along with Pimp My Z1 app for per core governors. I'm not sure of you can do that for UB. If you cant, then just change Rom for me ihackers is the smooth on stock governor, which i think is onDemand - im currently using CM11 just moved from iHackers 4.1 2 days ago
yup owns Z1 and stuff. Also if I've helped you don't forget to hit THANKS - actions speak louder that words.
Click to expand...
Click to collapse
I'm on a locked bootloader like i said in the op.
saintgein said:
Hello
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. ....Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
Wow, if you use performance all the time then your CPU is at max all the time. No matter what you are doing, no matter if your screen is off or if you have just put to one side...
It will kill your battery and burn out hardware very quick.
gregbradley said:
Wow, if you use performance all the time then your CPU is at max all the time. No matter what you are doing, no matter if your screen is off or if you have just put to one side...
It will kill your battery and burn out hardware very quick.
Click to expand...
Click to collapse
I got that, that's why i'm looking for better ways to do that. It just doesn't feel right that i have to do stuff like that to get a smooth working ui. Maybe i'm a perfectionist, but this s800 hardware should be able to do the call log/phonebook and gmail without stuttering right?
I'm using interactive governor atm with minimum clock 600. I notice that helps a bit already.
Hey Xda'ers, I have this weird (and really frustrating ) problem with my Xperia Z, when it enters Deep Sleep mode, sometimes it won't come back (won't turn on the screen & wake up.) I keep tapping the status bar (got CM11 Nightly & tap to wake option enabled) and hitting the power button to wake up, but it never does, then it just reboots.
The only workaround i've found it's to implement a partial wakelock so the cpu keeps running even if the screen is off, but thats eating my battery away. I Bought the phone a month ago and since its arrive, has this problem, i know it's a software problem cause if it wasn't, then there would be no workaround like the cpu kept running all the time (or at least my noob brain figures that out ). it's been really frustrating. the most frustrating part is not finding ANYWHERE on the internet (not even here on XDA) any resemblance to the same problem im facing, they are all different kinds of rebooting problems, but not even one the same as mine, it means my problem it's really new or special, or i'm not looking up really well, anyways it's been so frustrating for me this month, cause i repeat, since it arrived it has this problem.
First i thought it was a Wifi Problem, cause it happens when i get a notification meanwhile is asleep (i've seen it happen more often but it happens with or without a notification too.) and the screen off; When i try to wake up to see the notification, the problem triggers and it wont wake up, so i installed "Advanced Wifi Lock" (I saw a thread with a similar problem but with an Xperia Pad of some girl on the Sony Mobile Forums, and one guy posted this solution as the only workaround he had found to the same problem.) and the problem was solved.
But then i realized that it was eating my battery, so i changed to "Wakelock Power Manager" (cause i read it was a lighter weigh solution than "Advanced WiFi Lock") and there, there is this option for the implementation of various degrees of wake lock, since i thought it was a wifi problem, i turned on the "WiFI_Mode_Hi_Perf" which is a wakelock that keeps the wifi running in a high performance mode even while in deep sleep, i thought this was a lighter solution to my problem, but then the deep sleep reboot problem started again :crying:. so i tried increasing the level of wakelock to a "Partial_Wake_Lock" which is a wakelock that keeps the CPU running even while the screen is off, but this wakelock won't let the phone enter in a deepsleep mode, so it's the "Advanced Wifi Lock" problem all over again. Battery Drain . And this pisses me off, cause my battery, that should have a more than 14 life hours, just have those with a 4-5 hours of screen on time with a mild use of whatsapp and facebook.
I don't know what to do, i've tried flashing other Stock Firmwares, 4.1, 4.2, 4.3, 4.4, reflashing the original (was a 4.1 "10.1.1.a.1.307 customized hk"),, rooting and flashing roms, and the problem persists. I left CM11 on cause i like it and i don't think it has anything to do with the rom or firmware cause i've tried so many already.
Finally, over a month of trials and reading and so, so, so, but SO much frustration, i come to you guys, i don't know what to do anymore, Please Help .
Just bumping with some screenshots with details about my phone, i guess it will be easier to solve the problem, if posible, somehow. Muy Xperia Z is a 6603 model btw.
Note: I set the minimun CPU frecuency to 486 because i had the weird "buzz" sound problem sometimes with whatsapp & messenger notifications, & found that solution here over the forums, anyways, the problem was there way before that change.
I ask for some help again developers, i didn't wanted to start a help thread before i did my research & exhausted all my options, but i've done everything i could, & still got no solution, hope the screenshots help .
Sent from my Xperia Z using XDA Free mobile app
I had the same thing, and mine was fixed with increasing my minimum CPU speed to 384. Runs like a dream now!
I know you'v said you've tried a whole load of different roms but have you tried any different kernels? Mine seemed to come up only when using certain kernels.
i had the CPU running on 384 since i bought it, i only recently changed cause of the buzz problem, & no, i haven't tried different kernels, only different roms, i don't know how to flash a kernel only.
What kernel do you have? & Just to be sure, you had the same rebooting problem when it went to deep sleep mode right?
Thanks for answering.
Sent from my Xperia Z using XDA Free mobile app
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
mervluk said:
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
Click to expand...
Click to collapse
With once a day or every other day i could live with it too, i guess it's worth to let the phone deep sleep and save more battery even tho it reboots once a day or sometimes none, the battery saving should be greater than the annoyance, i hope mine was like that, but as soon as i release the cpu wakelock & let the cpu get into deep sleep, the problem begins, i get like 10 reboots in a day, and if only the reboots just happened when i weren't looking, but no, they barely happen this way, it happens when i try to use it and i notice it won't wake up, it's a really weird problem, & i find it very weird that no one has it. (you two guys are the first that i know have this kind of problem, and still, it's slightly different, for the number of reboots at least.) although it's good to know finally someone has the same issues as me, though i don't have high hopes since you told me you haven't found a solution.
I wanna try flashing a different kernel as orangejuice43 said, but i don't know how, or any compatibility issues with the rom i have (CM11 Nightly), sides, i don't know which kernel would be good to try.
Thanks for answering!
Flashed succesfully "Lightning Kernel v. 8.0" for CM11, will test for a few hours or days hopefully, if reboot comes i'll notify you guys, so far this is the first "new" solution i try.
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Jorge Plascencia said:
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Click to expand...
Click to collapse
Flash another ROM...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
That's a shame, I'm using lighning v8 and my problem is sorted. Sorry I can't be of much more help... lets hope a more knowledgeable person may be able to contribute for you.
Have you got an app like Trickster MOD installed to control the Kernel etc? might give you more of an insight as to what's going on. If you set a governor that keeps your Z from going into deep sleep it may be a bit better for your battery life than the wakelock solution...
This might help for information about Kernels
http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
Sorry for the late reply, i was on a trip so i couldn't actually test & give any feedback.
I downloaded Trickster Mod for my lightning kernel but all i could understand (after reading the post orange kindly shared.) was that every governor has this different settings that mod the cpu functionality & can be picked to adapt your own needs, i really doubt that any of them help with my problem, but as orange suggested, one may be a better choice compared to the wakelock fix i have used lately. i learned that since i flashed the lightning kernel, my governor was Interactive all this time, i really didn't noticed any battery drain or saving, i felt it just the about the same as before with the stock CM11 kernel.
a new question is, which kernel has the option or the setting for keeping the cpu awake? cause i didn't read any of them did this, or at least i didn't understood that any of them did this. anyways, that would be only another work around for the deep sleep reboot problem.
I though, read something interesting about frequencies and voltage of the cpu on the Thread, this:
Q. "Well i have set my favorite governor as screen-on governor and another one as screen-off governor. Why the hell is the phone not waking up after deep sleep. I need to force-restart the phone by pressing power button for about 10 secs. Is it a sleep-of-death?"
A. Yes it is. Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state.
Didn't get it? Examples for Wrong combinations: (screen-on:screen-off):-
ondemandX:smartassV2
Examples for right combinations:-
ondemand:smartassV2, lulzactive:smartassV2
Click to expand...
Click to collapse
The Question resembles just exactly what my problem is, my phone enters into deep sleep and then it won't wake up, the only difference is that i don't have to force restart it, it just. when i try to wake it up, restarts itself, with no need of long pressing the power button, and sometimes, i just find that the phone is off, and then i do have to start it by long pressing the power button (plain old power on.), but that brings me another question, isn't that maybe the problem is on the frequency & voltage side of my CPU? maybe the stock kernel (not CM11, and for the matter CM11 too, cause the problem persists, even with lightning kernel...) came with a rare code line or something? i dunno, im just wondering, maybe it doesn't make sense, but its just that the question and problem stated there on the thread about governors and kernel settings, resembles very much what my problem is.
I hope someone can orient me about this or make a mental link with something (maybe) wrong about my kernel or phone, could it be hardware? :crying: . I don't know, maybe i should try another kernel? maybe i should go back to Stock ftf and try another kernel? any suggestions or long shots are apreciated.
Thanks for the replies, & sorry for all the descriptions and text, it maybe kind of boring -_-.
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Jorge Plascencia said:
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Click to expand...
Click to collapse
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Jorge Plascencia said:
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Click to expand...
Click to collapse
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Jorge Plascencia said:
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Well yeah that's right. I suggest you to wait for others. I may be wrong.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Jorge Plascencia said:
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
mervluk said:
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
Click to expand...
Click to collapse
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Jorge Plascencia said:
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Click to expand...
Click to collapse
If you are saying after 1 hour of unboxing so I think you need to talk with the seller. Maybe you will get another Z.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
baconbeacon said:
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
Click to expand...
Click to collapse
did u tryed to install a custom rom? or a stock but flashing a kernel?
op3n said:
did u tryed to install a custom rom? or a stock but flashing a kernel?
Click to expand...
Click to collapse
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
baconbeacon said:
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
Click to expand...
Click to collapse
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
op3n said:
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
Click to expand...
Click to collapse
Well, if that's normal, this shouldn't be an issue. Though I do wonder where's the big little concept gone.
Did it ever occur to you guys that it might be dynamic hotplugging and a specific configuration/setup is being used ?
Or is it in your case really being buggy and broken ?
You left something working in the background and monitored how the cores behaved ?
Using different apps ? (say: kernel adiutor [or kernel adiutor mod], EX Kernel Manager, CPU Z, etc.)
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.