Database Develop

[Q] Phone apps/games keeps pausing

Hey guys, Idk why but recently my phone is going crazy
I first noticed this a few months ago, I was playing Injustice and it kept pausing. At that time my internal memory was 75% full, so I thought that might be the problem so later I uninstalled the app
But recently all my other games and video streaming apps(Twitch ,YouTube etc) keeps pausing, my Album app is bugged (though the Movies app works fine), camera force closes. Even my keyboard acts buggy sometimes. I tried formatting my phone memory, still no effect.
I think it could be a virus but I tried Clean Master (I guess this isn't a good choice) and it shows nothing is wrong
So do you think it's a virus? If it is, what should I do and if not, any particular solutions?
Thanks in advance guys and I hope I posted this thread in the proper section

NovaCrono said:
Hey guys, Idk why but recently my phone is going crazy
I first noticed this a few months ago, I was playing Injustice and it kept pausing. At that time my internal memory was 75% full, so I thought that might be the problem so later I uninstalled the app
But recently all my other games and video streaming apps(Twitch ,YouTube etc) keeps pausing, my Album app is bugged (though the Movies app works fine), camera force closes. Even my keyboard acts buggy sometimes. I tried formatting my phone memory, still no effect.
I think it could be a virus but I tried Clean Master (I guess this isn't a good choice) and it shows nothing is wrong
So do you think it's a virus? If it is, what should I do and if not, any particular solutions?
Thanks in advance guys and I hope I posted this thread in the proper section
Click to expand...
Click to collapse
If you're rooted, try clearing the cache and dalvik cache. Or maybe reinstall the ROM, that's what I usually do when my phone starts acting up. It's annoying, but worth it. What ROM are you on BTW?

Plum Crazy said:
If you're rooted, try clearing the cache and dalvik cache. Or maybe reinstall the ROM, that's what I usually do when my phone starts acting up. It's annoying, but worth it. What ROM are you on BTW?
Click to expand...
Click to collapse
Well Actually I'm using the stock 4.3 ROM and I haven't even rooted my phone
I tried rooting it, but couldn't unlock the bootloader

You don't need to unlock the bootloader to root Try TowelRoot. My advice is to do a fresh install with Flashtool, with a non-carrier specific ROM (no bloatware). When I was on eXistenZ Ultra, my phone slowed down after a few days. I think this happened on the stock ROM too, it might be a bug.

Plum Crazy said:
You don't need to unlock the bootloader to root Try TowelRoot. My advice is to do a fresh install with Flashtool, with a non-carrier specific ROM (no bloatware). When I was on eXistenZ Ultra, my phone slowed down after a few days. I think this happened on the stock ROM too, it might be a bug.
Click to expand...
Click to collapse
I tried TowelRoot, it shows that my phone is rooted but when I use other apps to check my root status like Root Checker or Titanium Backup it shows "The phone isn't rooted"
Damn, I suck at this

Did you flash a superuser app after rooting?
You can check root with the app 'root check' (appstore)
Sent from my C5303 using XDA Free mobile app

Maybe TowelRoot doesn't work properly on .207 (if you're on that firmware). Have you followed the instructions in this thread? You might have missed something - http://forum.xda-developers.com/showthread.php?t=2783885

Problems with my Note 5

Hi guys,
I rooted + installed Xposed on my Note 5 a couple months back and it's been working fine until today when a couple calls dropped out randomly. It then gave me an error saying "Unfortunately the process com.android.phone has stopped" and it also said something like "Messages has stopped". I lost reception, and when I tried to open my Messages app it crashed straight away.
I restarted about 10 times, and did a factory reset through recovery mode (twice) and still had the same issue.
I then tried to install Dr Ketan ROM using the instructions in this post. I followed the instructions perfectly but I keep getting a "KERNEL IS NOT SEANDROID ENFORCING" error and it gets stuck at that screen and won't boot. I've left it for up to 30mins and still no luck. I've done a factory reset a few times and tried installing Dr Ketan ROM twice now. I'm using the 920i kernel so shouldn't be an issue.
I don't really care about root and custom ROM (I'd actually prefer to stay away) so I might try flash a stock ROM. Any other thoughts/advice/tips? Anyone know why I had the first issue, or why I'm having the issue not being able to boot?
I'm on my phone 24/7 for work so need it fixed ASAP!!
Cheers

Try going back to stock rom through odin
Sent from my SM-N920C using Tapatalk

jonno92 said:
Hi guys,
I rooted + installed Xposed on my Note 5 a couple months back and it's been working fine until today when a couple calls dropped out randomly. It then gave me an error saying "Unfortunately the process com.android.phone has stopped" and it also said something like "Messages has stopped". I lost reception, and when I tried to open my Messages app it crashed straight away.
I restarted about 10 times, and did a factory reset through recovery mode (twice) and still had the same issue.
I then tried to install Dr Ketan ROM using the instructions in this post. I followed the instructions perfectly but I keep getting a "KERNEL IS NOT SEANDROID ENFORCING" error and it gets stuck at that screen and won't boot. I've left it for up to 30mins and still no luck. I've done a factory reset a few times and tried installing Dr Ketan ROM twice now. I'm using the 920i kernel so shouldn't be an issue.
I don't really care about root and custom ROM (I'd actually prefer to stay away) so I might try flash a stock ROM. Any other thoughts/advice/tips? Anyone know why I had the first issue, or why I'm having the issue not being able to boot?
I'm on my phone 24/7 for work so need it fixed ASAP!!
Cheers
Click to expand...
Click to collapse
hi,
Firstly, I must say my Note5 is not rooted, stock Rom.
Marshmallow.
Secondly, when reading your post above it reminded me
of similar issues i had in past with my old Note 3, /Note4
I also had "this stopping and that stopping"
(Similar as you.)
Found the culprit to be Xposed Framework.
As well as some modules you used/install
in Xposed.
After uninstalling Xposed and modules, factory
resetting (just like you) etc i still had issues.
Flashed stock Rom afterwards and eventually
managed to sort issues out.
( I had to flashed stock Rom, maybe about 2 or 3 times thereafter then only was it fixed. .)
So for me it sounds like, Xposed /module being
the culprit /suspect ?
I also recommend flash, your correct latest
stock Rom (make sure its the latest and correct Rom)
Good luck
Post note
what i am also saying that Xposed /module most probably "broke"replaced........" something" system framework ?
Also i used Xposed for a long time, then suddenly had issues.

hmptec said:
Try going back to stock rom through odin
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
All sorted - I had to flash stock ROM through Odin. This was my only way out!!
Cheers

Lost root access after a week, possibly by entering "smart manager"

I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..

I have the same problem?? Did you get any answer from any body? Do I have to re root again?

Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem

Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.

WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?

Flash SuperSU 2.74 and delete 'SecurityLogAgent'

I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse

Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.

Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.

Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.

Root won't "stick"

I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??

Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.

Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...

I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app

Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?

Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..

Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?

Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...

Thanks! I'll give that a try when I get home today.

S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!

Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...

Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app

marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.

https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app

Sudden random freezes

It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.

minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance ?

minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..

dodjob said:
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance
Click to expand...
Click to collapse
Hmm, i will try this when I get home from work, thanx.
Benjamin_L said:
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
Click to expand...
Click to collapse
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?

minnuss said:
Hmm, i will try this when I get home from work, thanx.
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
Click to expand...
Click to collapse
Let us know!

dodjob said:
Let us know!
Click to expand...
Click to collapse
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.

minnuss said:
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
Click to expand...
Click to collapse
That sucks big time ? the only time I got a freeze was as I wanted to empty chrome beta cache. After the reboot, all went back as it should be...

I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?

This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.

minnuss said:
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
Adb root shell. Can't think of a way this could damage anything if you just set the one property

hacktek said:
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
Click to expand...
Click to collapse
Did you have device rooted for a while, or it was always stock ?
Benjamin_L said:
Adb root shell. Can't think of a way this could damage anything if you just set the one property
Click to expand...
Click to collapse
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.

minnuss said:
Did you have device rooted for a while, or it was always stock ?
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
Click to expand...
Click to collapse
It's always been stock.

I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???

kaiwanted said:
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
Click to expand...
Click to collapse
Yes this happens when lots of I/o is done on the internal disk. I hope this is just a missing optimization and not a hardware issue. But let's bug xiaomi with it. I assume you also have the 64GB version?

@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.

minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
I read a lot regarding how people brick their phone with TWRP and rooting, so for now I will not use this future. But to reset my phone I will think about. Anyway I need this phone to use all my applications, not only a couple of them, because of this freezing (.
Thanks for suggestions.

minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.

kaiwanted said:
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
Click to expand...
Click to collapse
I did the same thing. Went through my application list, uninstalled everything I didn't need and the issue went away. I cleared like 5% of storage space with still over 50% left but it seems to have helped.

reflashed all stock, enabled camera 2 api using mi a2 toolkit (magisk method) and I have the same. Cleared everything and run flash_all.bat. enable cam 2 api again and still have the same issue. clean install of apps doesn't fix it. Any idea on how to fix the sudden freeze?
Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
if I completely root the device, I will still have the random freeze?
also, if I factory reset the device in the settings, the camera 2 api will be gone? thanks

minnuss said:
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
I did it via twrp and adb shell setprop persist...
No issues here at all.