My XA2 H3113 is extremely slow since Saturday, each animation takes 3-4sec instead of 0.5sec.
Typing is almost not possible and videos are displayed with ~ 1/5 speed.
Also booting takes at least 5x as long as usual.
I had not changed anything before. My device was not rooted, just Lineage & MIndTheGapps. I used it since April with this configuration.
So far I have tried the following:
From Lineage 18.1 last July build:
0)reboot
1)Updated to the current build.
2)Reset everything with TWRP & directly into Android
3)Tested other custom roms
4)2xSony OEM Rom flashed with https://github.com/munjeni/newflasher (UK Edition)
5) Lineage 18.1 last build installed and CPU Speed ->max (Settings->Battery)
6) Animations removed
Nothing helped. Anyone else have suggestions?
What occurred before it slowed down?
Check download folder for files you didn't download.
If you didn't change anything it may be a virus or rootkit. I don't know that system's vulnerabilities.
Look for excessive CPU cycle and memory usage by apks and services.
Sounds like it's fixing to crash and burn on you
@blackhawk
I flashed 5x a new ROM -> All partitions were formatted several times.
mx82 said:
@blackhawk
I flashed 5x a new ROM -> All partitions were formatted several times.
Click to expand...
Click to collapse
It's either the firmware, software or it's hardware then.
If it was a rootkit the reflash would have erraticated it... as long as the rom is clean.
Try it in safe mode.
Check for memory leaks and apks/services using excessive memory, CPU cycles or battery.
I tried the save mode -> nothing changed, the phone was still extremly slow.
In the last two days the phone was fast again 2x for ~ 3-5minutes.
Is there a possibility to force the phone to set the cpu permanently to maximum frequency?
Go back to the rom that worked before you damage hardware.
There's no good reason it should be running hot with a lite load.
Androids should not need high CPU usage at idle/lite loads and it's counterproductive to do so.
I am using the rom which worked month before the XA2 became slow: Lineage OS 18.1
Last night I charged the phone (nothing else).
Today, the XA2 worked just as fast as before last Saturday. Even reboots did not change that.
I had the same thing for 5 minutes 2x before.
Let's see if it stays like this.
mx82 said:
I am using the rom which worked month before the XA2 became slow: Lineage OS 18.1
Last night I charged the phone (nothing else).
Today, the XA2 worked just as fast as before last Saturday. Even reboots did not change that.
I had the same thing for 5 minutes 2x before.
Let's see if it stays like this.
Click to expand...
Click to collapse
Check for a memory leak.
Related
Hi,
I'm using s4 mini LTE I9195 with CM11 M6, f4ktion 1.4.0 kernel, BN3 modem, TWRP 2.7 recovery
All was working fine, average battery drain on idle was 1%-2% (not great, but fine), and suddenly it rocketed to drain 15%-30% per hour.
I usually use Android Tuner's battery measure stats to track drain statistics over time.
After checking it, I"ve noticed that it () the drain) started in the middle of the night.
So it's not due to "I launched this App, and then..." It just went nuts on it's own...
I've checked which process is to blame and the first one with max battery consumption is:
com.android.systemui (with KitKat logo) followed by Android System, then Screen, and then all the usuals.
I tried to do reboots, disable wifi/nfc/rotation/data/sync/anything else/kill user apps - no effect ...
It still drains about 20% per hour on system and systemui for the whole day now :crying:
And I have no idea what causing it / how to revert it...
So, do you have any suggestions on how to trace this bug?
What to search for in logs?
Any thing else?
I'm not a big pro on android OS subsystem, so advises are welcomed!
I'd love to help, but I actually stumbled upon this thread while googling to help myself
I'm using Note 2 (N7100), running CM11 - newest nightly (although I flashed it today, after slightly recharging the battery once I noticed the problem) and Devil3 kernel.
I'm having the same issue - yesterday everything was fine, I've left the phone to charge over night and display time as usual and in the morning nothing seemed out of the ordinary, until 6 hours later. After those 6 hours my battery was fully depleted (whereas normally lasts whole day and is not even close to being depleted). com.android.systemui and Android System seem to be the problem for me too.
I've also tried turning off some functions, uninstalling some apps, turning off notification privileges for others. Even, as said earlier, flashed newest nightly. Nothing helped. Using phone with without flashing Devil3 kernel didn't help.
Anyone have any ideas?
Just try to flash stock software and again CM.
Try a older version of CM11, and if stability is a priorty stay on CM 10.2
OK, so I've tried a few things, and had a few surprising outcomes:
I've analyzed the CPU load with various tools, as Android Tuner, OS Monitor, and All-In-One Toolbox.
Most of them reported Android System using 30% CPU, and com.android.systemui using 25% CPU, all on the highest frequency.
But All-In-One Toolbox recognized top process instead of Android System as Lockscreen android process, so maybe there is a hint there...
(and I don't use any custom lockscreen stuff beyond stock CM's one)
So, backed up the current troublesome system (let's call it BKP_NEW), just in case, and decided to restore a full NANDroid backup I had from a week ago (and the issue is just from yesterday).
Restored all 6 partitions (/system, /boot, /cache, /efs, /modem, /data), rebooted, and....
...The issue was still present! Crazy battery drain just as before!
Very confusing... Then I went for a factory reset - it fixed the issue, but I have to start from scratch with all the SW installs and config, and I don't have a week to waste setting everything up again, and potentially running into the same issue some time later.
So, I've decided to move further back, and restored a two week old NANDroid backup > reboot > No issue presents
But it was just too weird, since the delta between 1-week old and 2-week old backup is infinitesimal.
So, out of curiosity I've decided to restore the BKP_NEW (the one of the system with the issue present)... and after the restore it works just fine! (WTF?!?!)
After thinking on it for a while, my conclusion is that there was some problem with some part of system that was wiped/fixed in TWRP's Factory Reset, but is not touched/overwritten during the NANDroid 6-partition restore.
But again, this is just my assumption, need someone more knowledgeable to confirm this possibility...
(maybe @ne0zone75 can advice on this?)
Since that, all is working fine (at least so far).
And if my assumptions are correct, @Ksenios, you can try to do this, and still have working system with all apps and configs (If youre comfortable with recovery / backups management).
hi,
(passing bye from google - just a note)
com.android.systemui cpu high usage (about 37%),
on my huawei media pad x2 (gem702l) but only while charging (and just sometimes), if that gives something for someone, any clues why ?
Hello people! I have strange problem.
Yesterday my phone freezes and rebooted, SIM was not working. I was on 30.3. 2106 cm nightly.
From that time, my phone randomly freezes and then immediately rebooted.
Before that, I was playing with CPU governor values, can that damage hardware? (No heat or something like that, but SIM)
Tried many cm13 builds, aosp's, fulmics, cloudy, another kernels, reflahed modem, another battery..
Every ROM was after clean install, apps installed from play store, few with restored data, tried with and without them, same with Xposed, doesn't matter anything.
Anyone know what is it? My phone leaving?
Sorry for bad English. Thanks David.
Tell us, which baseband version you have.
Only 21c on cm13 works. So this one.
OK, I had the same problem too.
I fixed it by removing Kernel Adiutor (yeah, Kernel Adiutor). Then I installed V21C (13.2-00002) modem and rpm/tz partitions (V21C too) posted by @Step-han right here.
I don't know how it works on cm but I'm using stock mm and it works good
Let's try it! I will post results
@jaro1221 It works! Thank you man! Maybe it was caused by installing Fulmics, which reflahed modem.
Thanks!
Having this same problem,first the sim not detected,then from a couple of days apparently random freezes and reboots that persist across stock based and aosp/cm Roms. But I noticed that the freezes and reboots occur only when the device is warm. Not hot,warm as in if the CPU temp is above 60�° C. If it is below 60, the phone can be used for hours without a problem. Any ideas? Could it be hardware related? I've used for months my g3 , and it rarely crossed the 70�° , and did not have this problem. I'm using a d855 16 GB if that matters.
Update: Just in case this could be useful for someone. First,my device got worse,it couldn't boot at all even while cold. it could not get past the lg logo,not in rom,not in recovery. I fixed my problem, maybe temporary, by using some folded aluminium foil. I opened the phone, and put some of it between the mother board and the display, in the same place where you can apply the thermal mod,and then some other between the board and the back case, under the place where the power and volume buttons are. I closed the phone and it booted up, I'm using it for half a day now, installed some games, played while monitoring the CPU temperature. It can go up to 70 degrees and it did not freeze,nor reboot as far. I rebooted some times myself to test if it would detect the sim card,and it had no problem so far,but maybe it is to soon to tell. So... I will update if something happens.
Hi guys,
I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;
in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!
I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;
I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).
Nothing changed.. it appears 2-3 times per day.
Anyone of you got the same error? which could be a solution?
I had exactly the same problem, but flash rom via adb fixed that.
not experiencing any.. stock non rooted...
Kshysiek said:
I had exactly the same problem, but flash rom via adb fixed that.
Click to expand...
Click to collapse
Sounds interesting.. will try! Thx in advance
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated
Running ExperienceOS by Jamal btw, which is based on stock OB28
I have had this as well. Just keeps rebooting randomly.
Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.
I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.
Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
Sent from my ONEPLUS A3003 using Tapatalk
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
Sent from my ONEPLUS A3003 using Tapatalk
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
creezalird said:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
Click to expand...
Click to collapse
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
basvanasperdt said:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
Click to expand...
Click to collapse
Same here
Been in SuperSU for 3 days. No issues so far
Op3 ob28
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:
$ uptime
02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24
*I had not tried using super su instead.
What can we do to debug this issue? Seems like everybody is trying to guess in the dark...
---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------
If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.
Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...
Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...
Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
simpele said:
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Click to expand...
Click to collapse
strange1712 said:
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Click to expand...
Click to collapse
abhibnl said:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
Click to expand...
Click to collapse
Kshysiek said:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
Click to expand...
Click to collapse
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
candiesdoodle said:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
Click to expand...
Click to collapse
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.
Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?
No. It's no solution. It's a vague trial.
tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.
I'm absolutely losing my mind please help
A little story time, skip to the end for my question;
So, how to start - One day I unlocked my bootloader, went for some android 11 rom and all was fine. Then android 12 was released and I downloaded the crdroid 12 rom, where I was experiencing some battery drain issues. So I downloaded pixel experience rom. The Bluetooth died because of this rom's cursed source code. I flashed the latest miui fastboot rom and the Bluetooth issue still persisted (remember this for later - not all the drivers flash with the Rom). I fixed the Bluetooth issue by switching several miui roms, also made a guide if you're interested. That fixed the Bluetooth issue and I went for pixel plus ui rom. It was a bit laggy, so I switched to the shiny new Evolution X rom. It was amazing, so much stuff co customize, etc. Well, i experienced another battery drain issues, so I just went for the stock miui with magisk pixelify module. Im pretty fine with this rom, and I thought the problems are gone, because it stock and everything should be fine. Well no. The battery drain issue persists. I was wondering what even is happening, so I opened battery settings. That said that the top apps wasting my battery is screen, Google services and android system. I downloaded a CPU usage stats app, which showed me that the cpu usage is at 99% (I think it's correct as the phone is overheating). The app with most cpu usage was using only 1%. I don't know if this is a firmware bug or whatever, but I think some rom broke it and the latest stock miui didn't overwrite that driver, as written above with the Bluetooth issue.
So, how can I make my phone be as it was released from xiaomi with all the drivers to actually use the hardware correctly?
Thanks in advance for any replies, I'm seriously going to throw my phone out of the window
Also the way how I install the stock Rom is by downloading the latest fastboot rom, extracting it and executing ./flash_all.sh file.
SOLVED! My problem was because of my credit card. I have my cc in the phone case. The cpu was going insane because it was constantly detecting the card and loading info from it. Literally turning off NFC fixed this whole issue. Bruh.