Something terribly wrong with my CPU!! - Xiaomi Redmi Note 3 Questions & Answers

Yesterday my phone started to heat to much i checked the frequencies in kernel auditor and found them to be quite low i knew that they were thermal throttling so I left it and now my little cores won't turn on at they turn on for a sec or 2 and then turns off my performance had decreased as the second big core can also not getting turned on.

First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.

gooomis said:
First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.
Click to expand...
Click to collapse
That dudnt work man can anyone help???

gooomis said:
First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.
Click to expand...
Click to collapse
I don't know about overheating, but disabling automatic applying the kernel settings after a reboot may solve the problem with cores not enabling.
Sent from Note 3, Xiaomi Redmi Note 3.

mr.loverlover said:
I don't know about overheating, but disabling automatic applying the kernel settings after a reboot may solve the problem with cores not enabling.
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
Dude it's just not working I tried to disable the first little a53 ko and I found that it is not been disabled by any means on my rooted tab S2 and so it was the case with my redmi Note 3 also but now the a 53 Court is just disabled but now the kernel I think just automatically disabled the first a53 Core and doesn't let me turn on any other cores except one is a72 core which is very weird reboot clearing the Dalvik cache even performing a factory reset and I even tried to install nitrogen OS but it doesn't seem to fix the problem but my device was working a few days ago even last night it was just working fine but after that overheating issue that chip is not working I guess properly

It seems chip stopped working :/
I'd flash through edl latest global dev in miflash with option flash_all if I were you...then if problem persist you can be 100% sure its HW fault

Androbots said:
Dude it's just not working I tried to disable the first little a53 ko and I found that it is not been disabled by any means on my rooted tab S2 and so it was the case with my redmi Note 3 also but now the a 53 Court is just disabled but now the kernel I think just automatically disabled the first a53 Core and doesn't let me turn on any other cores except one is a72 core which is very weird reboot clearing the Dalvik cache even performing a factory reset and I even tried to install nitrogen OS but it doesn't seem to fix the problem but my device was working a few days ago even last night it was just working fine but after that overheating issue that chip is not working I guess properly
Click to expand...
Click to collapse
what I meant is disabling the master switch for CPU settings, so that they won't be applied after a reboot.

mr.loverlover said:
what I meant is disabling the master switch for CPU settings, so that they won't be applied after a reboot.
Click to expand...
Click to collapse
I am using stock rom without root and using cpu x to monitor the settings
Update:Kept it in freezer for 3hours and now its freezing cold and my is powering on and i am yet to see the cores
Update 2: cant believe my eyes the cores on again wooohooo!!!

Related

[Q] Royal Mess

Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.

[HELP] Phone reboot every 5-10 seconds (Kenzo)

I encountered this problem about 2 weeks ago
I have flash every ROM (Official, MIUI based custom ROM, and AOSP) including in fastboot mode
and only CM12.1, CM13 and RR survived from random reboot
I won't use both CM13 and RR because its RIL
Now i used CM12, but I have super fast draining battery
My phone will die, even in standby, because Android OS and System used battery more than SOT
When I checked it, the CPU always stay awake and won't enter deep sleep, so my phone always went heating even in standby (screen turned off)
The only problem I would fix is the random reboot issue when I used MIUI and other Custom ROM I had mention above
This is driving me crazy. Does it hardware problem or something?
If not, how to fix fast draining battery from CM12.1?
Sorry for my bad english
putrairlangga said:
I encountered this problem about 2 weeks ago
I have flash every ROM (Official, MIUI based custom ROM, and AOSP) including in fastboot mode
and only CM12.1, CM13 and RR survived from random reboot
I won't use both CM13 and RR because its RIL
Now i used CM12, but I have super fast draining battery
My phone will die, even in standby, because Android OS and System used battery more than SOT
When I checked it, the CPU always stay awake and won't enter deep sleep, so my phone always went heating even in standby (screen turned off)
The only problem I would fix is the random reboot issue when I used MIUI and other Custom ROM I had mention above
This is driving me crazy. Does it hardware problem or something?
If not, how to fix fast draining battery from CM12.1?
Sorry for my bad english
Click to expand...
Click to collapse
hello I would like to know if you solved because I have a very similar problem to your......
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Sent from my Redmi Note 3 using XDA-Developers mobile app
samanderson said:
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
the problem is only present in rom stock because it seems to work just a core of 6 and do not know how to solve
HydroAG said:
hello I would like to know if you solved because I have a very similar problem to your......
Click to expand...
Click to collapse
No, I haven't have you?
samanderson said:
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Click to expand...
Click to collapse
I just tried Flash Official ROM via Fastboot (MiFlash) but my problem still exist like I mentioned above
HydroAG said:
the problem is only present in rom stock because it seems to work just a core of 6 and do not know how to solve
Click to expand...
Click to collapse
but why it didn't happen before?
I often wipe and flash my device, does it caused the problem?
Hi, i'm having the same issue as yours, have you try to send for repair? Xiaomi centre at my place refuse to repair it as mine from china set, any luck at your place?
Edit- mine was unlocked officially, don't think it related to this issue as it was working without any problem previously,the last thing i did before this happened was making a call in lte before it turned off suddenly, then heat up a lot and keep on rebooting,
asared89 said:
Hi, i'm having the same issue as yours, have you try to send for repair? Xiaomi centre at my place refuse to repair it as mine from china set, any luck at your place?
Edit- mine was unlocked officially, don't think it related to this issue as it was working without any problem previously,the last thing i did before this happened was making a call in lte before it turned off suddenly, then heat up a lot and keep on rebooting,
Click to expand...
Click to collapse
No I could not solve, even to me has happened after a call was 7.2 on global you?
I live in Italy therefore it is difficult to send it to a service center
HydroAG said:
No I could not solve, even to me has happened after a call was 7.2 on global you?
I live in Italy therefore it is difficult to send it to a service center
Click to expand...
Click to collapse
I'm on aosp when this happened, maybe it is hardware related,
Will try to send it to repair shop nearby and hope they can do something about it, it's only a month and now it's completely unusable, maybe just a bad lemon unit
Same problem here...I bought this phone from China and it worked fine for 10 days...Suddenly it begun to rebooting every 20-30 seconds, i can't do anything in the phone...
I managed to flash it with other roms and the problem remains...
I am absolutly disgraced for this....I loved this phone, it lasted only ten days....
Rofellos_Chile said:
Same problem here...I bought this phone from China and it worked fine for 10 days...Suddenly it begun to rebooting every 20-30 seconds, i can't do anything in the phone...
I managed to flash it with other roms and the problem remains...
I am absolutly disgraced for this....I loved this phone, it lasted only ten days....
Click to expand...
Click to collapse
where did you buy it?
xGiorgos said:
where did you buy it?
Click to expand...
Click to collapse
Goldway store, aliexpress...I am still in the protection period so i think it won't be difficult to obtaining a refund...But still i prefer to fix it...
I think is a hardware problem though...i think it has something to do with the energy or temperature managment or circuitry...
Rofellos_Chile said:
Goldway store, aliexpress...I am still in the protection period so i think it won't be difficult to obtaining a refund...But still i prefer to fix it...
I think is a hardware problem though...i think it has something to do with the energy or temperature managment or circuitry...
Click to expand...
Click to collapse
Should be hardware problem and there's nothing we could do i guess, there's a few people affected already.. problem with this model and we're the first.. so sad. Luckily my nexus 5 still going strong despite the screen shattered, even can see the circuit inside, showed the difference between brands quality.
Did someone with this problem can Instal CM13 ROM with fingerprint compatible?
because mine always stuck in Mi Logo and then can't enter TWRP until it re-unlocked and back to MIUI with Mi flash to able flash TWRP)
If not flash fastboot MIUI, the TWRP can't be installed even the phone have unlocked
WTH is going on with my phone
putrairlangga said:
Did someone with this problem can Instal CM13 ROM with fingerprint compatible?
because mine always stuck in Mi Logo and then can't enter TWRP until it re-unlocked and back to MIUI with Mi flash to able flash TWRP)
If not flash fastboot MIUI, the TWRP can't be installed even the phone have unlocked
WTH is going on with my phone
Click to expand...
Click to collapse
It is almost ending its lifespan, I presume.
Unlock, twrp and flash cm. if all else fails, go to Service Center
Sent from my Unlocked kenzo, the power unleashed
any news with that issue?
cause of what i understood , there is a bug hardware isuue with Charging Controller on Xiaomi Redmi Note 3 pro ,
and hardware must be repaired....
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Ivanlai said:
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Click to expand...
Click to collapse
Thanks Ivanlai,
What Exactly do you mean by your answer?
did you had this Problem on your Xiaomi Device?
had you manage succesfuly solving it?
my device is new and i dont want to do something that will harm the Warrenty.
I haven't had this situation exactly, but the reason I said to tick flash all is because I have bricked and bootlooped my device before.
By ticking the flash all option, it reduces the risk of some remnants of the previous ROM causing conflict.
Also, I tried several different global stable ROMs before I successfully unbricked my device.
As for warranty, I remember someone mentioning that a xiaomi customer service operator emailed them saying that rooting and flashing custom ROM would not void the warranty, but I would email them again on this issue just to make sure.
Ivanlai said:
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Click to expand...
Click to collapse
Ivanlai said:
I haven't had this situation exactly, but the reason I said to tick flash all is because I have bricked and bootlooped my device before.
By ticking the flash all option, it reduces the risk of some remnants of the previous ROM causing conflict.
Also, I tried several different global stable ROMs before I successfully unbricked my device.
As for warranty, I remember someone mentioning that a xiaomi customer service operator emailed them saying that rooting and flashing custom ROM would not void the warranty, but I would email them again on this issue just to make sure.
Click to expand...
Click to collapse
Thanks Ivanlai,
very strange what happening to my device.
reboots stopped (have no idea of what reason : recharge again from 5% battery, get into test mode (push 3 button for 10 sec': vol+, vol-, power).
but now other issue showed up : very lots of screen glitches, can use the phone like this, like some bad soldering inside.
first time i got into test mode, there were also screen glitches,
but now, whenever i get into test mode, downloading mode or the 3rd mode (with phone and cable picture), there is not glitchs at all,.
but after phone is starting - lots of screen glitches !!
i am lost
I also bought my Redmi 4 Prime from goldway store, do you know what is their return policy like?

Battery shows negative value

Hello guys,
I've recently bought a Redmi Note 3 Pro (3GB RAM) and the first time I booted it up it showed that it has -2% battery life. Since this seemed strange I tried to charge for several hours, but no change was noticed. I then tried with a battery calibration app, tried factory reset and restarting the phone, but nothing helped. I am also not able to go in recovery mode for hard reset as it states that there is no charge ...
The strange thing is that the phone is working for now and I am using for a second day with still the same bug. This leads me to believe that the problem is most likely caused by incorrect battery stats saved on the phone, but I am not sure. I am also not willing to root it or flash it since it is brand new and I might lost the warranty.
Can you guys suggested me a solution for this or the problem is not easily recoverable?
Thank you for the time and answers!
I have the exact same problem, tried resetting everything, I suspect it is a hardware problem.
awedxz said:
Hello guys,
I've recently bought a Redmi Note 3 Pro (3GB RAM) and the first time I booted it up it showed that it has -2% battery life. Since this seemed strange I tried to charge for several hours, but no change was noticed. I then tried with a battery calibration app, tried factory reset and restarting the phone, but nothing helped. I am also not able to go in recovery mode for hard reset as it states that there is no charge ...
The strange thing is that the phone is working for now and I am using for a second day with still the same bug. This leads me to believe that the problem is most likely caused by incorrect battery stats saved on the phone, but I am not sure. I am also not willing to root it or flash it since it is brand new and I might lost the warranty.
Can you guys suggested me a solution for this or the problem is not easily recoverable?
Thank you for the time and answers!
Click to expand...
Click to collapse
Try updating, I had this issue with custom ROM's something certain boot images have this bug.
I flashed a new boot image and bug was gone but had no wifi reverted back to latest global stock via MiFlash.
If you have TWRP try the ROM here https://xiaomi.eu/community/threads/6-7-7-11.32639/ it seems ok.
Did anyone find a fix for this issue. I have the same problem. Battery percentage shows negative 2% and I can't get into recovery because of that. When I press Power and Volume + It shows the battery icon in red and won't let me into recovery. I have the Redmi Note 3 Pro Snapdragon version.
I tried flashing a couple of ROMs via MiFlash with no positive results.
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
5t4m said:
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
Click to expand...
Click to collapse
What rom are you using?
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
The Radon V1.8 Kernel actually causes this bug on MIUI based roms, so don't flash the kernel.
Radon Version 1.9 will resolve the battery bug on MIUI and other roms.
Talking about cm/aosp I tried almost all combination kernel/rom.
No success except for this particular cm with camera patch.
Same problem with battery, showing -2% but phone is working... Plz provide solution asap
If u run MIUI, just download FASTBOOT ROM, restart phone to FASTBOOT MODE and flash ROM using this tool. But if u run custom ROM just flash custom kernel (like RADON).
5t4m said:
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
Click to expand...
Click to collapse
Fixed the -2% Bug on latest CM13-Snapshot for me!
You Sir are awesome
flashed the latest global firmwareware(not developer one) solved my issue, also now my phone updates OTA.
Use only the official rom. custom that sellers flash usually is a junk just with additional options for menu's language!
Same problem with battery, showing -2% but phone is working... Plz provide solution asap what to do. .. mobile automatically switch off too
Geeta_ghai said:
Same problem with battery, showing -2% but phone is working... Plz provide solution asap what to do. .. mobile automatically switch off too
Click to expand...
Click to collapse
Flash the latest miui ROM in edl mode using miflash. That is the answer.
No
No that is not the answer it's a hardware issue short circuit in motherboard
induna said:
Flash the latest miui ROM in edl mode using miflash. That is the answer.
Click to expand...
Click to collapse
androidnandroid said:
No that is not the answer it's a hardware issue short circuit in motherboard
Click to expand...
Click to collapse
Hmm, well flashing an official ROM in edl mode has fixed this problem for many people, including myself. So it would seem that in most cases at least it IS a software issue that can be fixed by flashing.
My phone came from Banggood and a vendor ROM that wouldn't even support my FP reader, Goodix, and which booted up with the -2% battery bug out of the box. Flashing the official global stable ROM, 8.0.2.0 at that time, fixed all of the issues.
Hmmm may be sir but that doesn't seem to fix mine although mine is from xiaomi only and the problem came after using 6 month suddenly without any reason one morning
Ok guys there are 2 solutions to this problem one is drain your battery and don't charge it for 2 3 days drain it like he'll coz after switch off still some juice is left you have to drain completely and other rapid method is open your redmi note 3 and disconnect battery cable and reconnect it... The problem is not software its hardware where battery reading stuck at minimal which is - 2 ... Thinking minus two hours coz at zero still some battery left for edl and fastboot mode time and alarm... Fixed my redmi note 3 hope it will help you.. Coz tried all method format... 10 times flash all roms through fastboot mode Coz updater mode won't work coz of low battery reading... Enjoy guys
I am having a same issue with redmi note 3 SD version. Tried everything Global BETA ROM, STABLE ROMs but didnt solved my issue. Showing -2% bettery in every ROM which i have flashed.
I am facing a similar problem where my phone showed -2 as battery level but my phone is not booting at all without any charger attached. and even when the chargr is connected it boots upt the Mi Logo and then displays an empty battery which wont charge even when tried for hours. Please help
razy111 said:
I am facing a similar problem where my phone showed -2 as battery level but my phone is not booting at all without any charger attached. and even when the chargr is connected it boots upt the Mi Logo and then displays an empty battery which wont charge even when tried for hours. Please help
Click to expand...
Click to collapse
I had the exact same problem like this one on xiaomi redmi note 3 pro sd. I tried flashing fastboot miui 10 official but the problem still there. I also tried changing the usb charging port but still the same. I tried plug in the charger and hold power and + volume and it stuck at mi logo.
I want to know if anyone fix this?? Please help.

Deep Sleep Issues, event wakelocks 0-8

Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...

Battery drain and heating problem.

Hello,
I am having some battery problem.
I am currently on 10.3.12.0 (EU) build,( before that i was on 10.3.11.0 (EU)) which i flash directly via twrp, because i was not able to get the ota update, it always failed to install. Yes i followed the instructions for ota with magisk.
Since the 10.3.11.0 update, the battery get bad, i was getting around barely 10h sot, now it super bad- can not get even 3h SOT + there is massive heat issue 40° for no reason.
CPU frequencies are not loadable ( since the beginning ) in kernel auditor, gsm battery or any app. (see the screenshots)
It can be only monitored in real time, and it is showing for every scroll spikes to the maximum.
There is battery drain even in Stand by- 5-10 %.
What will you advise me.
Thanks in advance!
Some screenshots.
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
_mysiak_ said:
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
Click to expand...
Click to collapse
Thank you for the fast answer!
I am using terminal emulator, because i am not able to use PC at the moment.
I will add later the proper data if needed.
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Thank you !
I was just thinking about the same app, but i am using it since Sunday, and the problem is since the previous update( i was on the 10.3.10.0 only for 2 days)
But i am hoping this will solve everything!
Thank you again!
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
alexandarpb said:
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
Click to expand...
Click to collapse
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
_mysiak_ said:
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
Click to expand...
Click to collapse
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
alexandarpb said:
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
Click to expand...
Click to collapse
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
_mysiak_ said:
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
Click to expand...
Click to collapse
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
alexandarpb said:
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Click to expand...
Click to collapse
Kernel adiutor seems to be not working correctly, even for Mi A1 it required special version of the app. I guess it's not compatible with our device. Also it seems that it messed up the minimum CPU frequencies on my phone, try to uninstall the app and reboot, it might help "unstucking" your little cores.
About the CPU states, the issue is here:
testResults
file_not_exists:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
It's either stock Android Pie behavior or Xiaomi forgot to implement this feature.
Edit: someone at Xiaomi probably really forgot to enable this.. https://android.googlesource.com/ke...ease/Documentation/cpu-freq/cpufreq-stats.txt
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
alexandarpb said:
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
Click to expand...
Click to collapse
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
_mysiak_ said:
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
Click to expand...
Click to collapse
In fact maybe that is the case, after typing tune2fs i can see that mount count is FIVE, i think that is why Ota has a problem.
Maybe i should flash stock fastboot image ?
Sapper Morton said:
Indeed, it has been tampered with; you should flash system image again, and if you use TWRP, be sure to follow as _mysiak_ explained, don't allow remount; also, check for other partitions if you want to restore manually, or for it to be easier, just run flash_all_except_data_storage, and do the OTA installation afterwards, the latest Magisk patched files are up, in the [ROOT] thread, by Typhus.
Click to expand...
Click to collapse
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
alexandarpb said:
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
Click to expand...
Click to collapse
1. unpack fastboot rom (tgz - Tar Gnu Zip)
2. unpack unpacked file again (tar). Then you will see flashing script files and images.
3. connect phone via fastboot
4. switch to partition A
5. run flash_all_except_storage.bat
6. wait for it to finish, phone will reboot automatically
7. congrats, you have fully stock phone now
The latest version of MiFlash should work fine, though I never used it. In each case you must make sure that you are on partition A.
hi again,
i would like to flash latest fastboot rom,(flash_all_except_storage.bat) because maybe have done something and have several unusual problem- heating again+40°C, while riding my bike, that cause and battery drain(less than 5 sot), super slow booting, so is the procedure the same as before? is the android 10 script have something different?
thank you!
P.S
Did it like before. Not sure if that fix my previous problem

Categories

Resources