Hi,
I have a OnePlus 3 which is about 7 months old now. I'm running stock 6.0.1 (OOS 3.2.7) with Xposed. ElementalX kernel and TWRP recovery (if that matters) ... I use Kernel Adiutor for a few misc tweaks (vibrator, LED, hostname) and AKT Profiles is set to Fusion Conservative - which limits GPU as well. I have been using various Xposed modules without any issue until the following happened.
I had installed Parallel Space - an app which allows dual WhatsApp capability. I started experiencing random soft reboots and shutdowns. So I uninstalled it. Then I cleared cache and ART cache. I also uninstalled a few apps that I had installed in the past month.
I am still experiencing reboots and I cannot pinpoint the cause. The reboots/shutdowns occur when the screen is off. Always when the screen is off.
I'm bad at reading logs, so can't figure out from the logcat either.
Anyone who can help me out, will be greatly appreciated! I will provide all logs as necessary.
[EDIT] Solution: Do not let any app make use of the proximity sensor to manipulate the screen. For example, apps which switch off the screen when flipped might be the culprit.
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
cl0g said:
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
Click to expand...
Click to collapse
Nope, no Magisk. Only Xposed.
Providing logs from logcat. Will provide anything else if required.
A few more logs containing fatal errors.
I thought the problem was solved by uninstalling this app called "Pixoff", but no, it still persists. Also, the LED is glowing orange, without any notification pending. During screen on as well as off.
Can you please flash stock ROM and check once if the same problem persists?
hrishikeshgramani said:
Can you please flash stock ROM and check once if the same problem persists?
Click to expand...
Click to collapse
That is what I'll have to do if changing settings or regular fixes don't work... But I don't want to jump to it right now because there's a lot of tweaks I'm running and they will be destroyed.
Also, it was running perfectly until last week. I have uninstalled all apps that I got in the last month. Cleared ART cache and normal cache. Haven't restored to factory settings yet.
I'm experimenting with disabling Xposed modules one by one, although I don't think it's a module problem - because I've had them since eternity.
What I have concluded is - I downloaded a rogue app from the Play Store which has left it's data and that is the cause of reboots... I might be wrong though.
Hence, I would really appreciate if someone would go through the logs and figure it out.
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
cl0g said:
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
Click to expand...
Click to collapse
Will do that next time, thanks!
Okay, so I figured this out. Proximity sensor is having issues. I had enabled "Proximity wake" in GravityBox and that was causing problems. Disabled it and Everything was fine as ever.
To verify that proximity sensor was at fault, I tried Pixoff's flip to Black screen feature - it uses the proximity sensor to figure whether device is in pocket or flipped... And yes, phone rebooted there too.
Phone is running fine as long as the sensor is used only during calls (to switch screen off)
But what I cannot understand is why this is happening in the first place! I mean, proximity sensors are supposed to be used in this manner only, right?
Nevertheless, if anyone wants to help, they are welcome. Otherwise my issue is solved.
Related
Hi all,
I just started having severe battery drain issues on my DHD this morning (~17% drained in 1.5 hours)
I installed Watchtower to check if there were any rogue processes that were eating up my CPU time. I noticed that this process called "isl29028_wq" was using about 30% of my CPU constantly, but I can't seem to figure out what it is, since nothing shows up on Google.
The only apps I installed recently were Layar and Google Goggles, which I've already removed.
Does anyone know what this process is?
Thanks!
Google says, "isl29028" without "_wq" is a low power ambient light and proximity sensor...
http://www.intersil.com/products/deviceinfo.asp?pn=ISL29028
Maybe is its driver running wild?
Now that you mention it, I have noticed Android System using the sensor quite frequently. I wonder if this is the cause of my poor battery.
This probably HTC's ****ty workaround for the mis-calibrated proximity sensor. First time I have ever seen it so severe.
I suggest going for a custom kernel and using my DHD Proximity Sensor Recalibrator app to to fix your issue (in app section).
Edit: Could also be light sensor related. Same chip.
leppie said:
This probably HTC's ****ty workaround for the mis-calibrated proximity sensor. First time I have ever seen it so severe.
I suggest going for a custom kernel and using my DHD Proximity Sensor Recalibrator app to to fix your issue (in app section).
Edit: Could also be light sensor related. Same chip.
Click to expand...
Click to collapse
Thanks for the suggestion, but I haven't really encountered any proximity sensor related issues during calls. I also forgot to mention that I'm using Android Revolution 2.0.11, which I believe uses Apache's kernel.
I'm going to poke around somemore and see if theres an app thats causing my sensor to go wild.
When this happens again, run the following:
Code:
adb shell dmesg > dmesg.log
and attach it to your post.
That could help us see what happens.
leppie said:
When this happens again, run the following:
Code:
adb shell dmesg > dmesg.log
and attach it to your post.
That could help us see what happens.
Click to expand...
Click to collapse
I tried running that command through USB, but the log simply says "demsg: not found".
EDIT: I just flashed ARHD 2.0.12, which uses an updated kernel. Let's see how it goes.
Hello!
i am having this issue by a couple of weeks, two days ago i found that process was continuously using 30-50% of cpu and my phone was very laggy...
i was unable to find a solution, anyone has a tips for me?
@@dgco86: did you find a solution? I wiped my handheld but after logged in with my google credentials, Market installed all my previous application automatically, so i don't know if this issue is app related or not...
Please help me, i really don't know how to solve the issue... Maybe changing my phone?
An update:
i tried EVERYTHING, such as wipe, factory reset, i follow the procedure found here to full reset the device, but i am still having this damn issue... isl29028_wq takes 30-70% of cpu randomly and gives my phone laggy and block also automatic brightness.. the only way to solve (temporary) the problem is to give a short call to someone, after have closed it everything comes back to work! But after a while, issue comes again...
Ah, i forgot to tell you that i am running a stock version of Android updated to the last version via OTA
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good:
I've only noticed this since running the August security updated and its happened across three ROMs so far (Screwed, Pure Nexus, LOS (No gapps)). Sometimes the screen takes for ever to power up. Once it is up the lock screens responsiveness varies greatly. Not always in the same instance as the screen issue but when unlocking the device it will momentarily freeze. Sometimes locking itself again..
Curious if anyone has seen anything similar.
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
jhs39 said:
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
Click to expand...
Click to collapse
I'm restoring from tibu.
pcriz said:
I'm restoring from tibu.
Click to expand...
Click to collapse
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
jhs39 said:
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
Click to expand...
Click to collapse
It's happened without any apps installed as well. I haven't tried safe mode yet no
are you using immersive mode?
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
pcriz said:
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
Click to expand...
Click to collapse
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
diabl0w said:
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
Click to expand...
Click to collapse
Yeah that would make sense if you are seeing the same thing. I may jump back to a known good build and see what happens
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
pTeronaut said:
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
Click to expand...
Click to collapse
Thank you, I'll try that!
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
p1r473 said:
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
Click to expand...
Click to collapse
Check this thread. ?
https://forum.xda-developers.com/pi...e-problems-t3666479/post73629247#post73629247
Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.
rdmack said:
Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.
Click to expand...
Click to collapse
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.
I got this problem. How to get rid of this.
Harrygsr said:
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.
Click to expand...
Click to collapse
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:
Harrygsr said:
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:
Click to expand...
Click to collapse
Is it really hardware problem? I am on leedroid and ohio wake lock started yesterday. I tried disable Htc Push Client, but not works. I also flashed Elite Kernel, but no change.
andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks @andybones , I'll be very happy if @fagyi help me .
I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.
mcmorariu said:
I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.
Click to expand...
Click to collapse
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.
Grubmi said:
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.
Click to expand...
Click to collapse
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.
Grubmi said:
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.
Click to expand...
Click to collapse
that does look crazy
when I had the hardware issue, it was consistently sucking up battery whether day or night...
I still recommend replacing the charge port, may be an intermittent short in that PCB.
I got a Xiaomi Mi 10T Lite and it's running on Android 11 since some weeks.
But after it updated to Android 11, it sometimes goes black when I'm using it for a while and I've to unlock it all the time.
It goes black and then returns to the lock screen.
Does anybody else also have this problem and is this a bug that I should report?
I've also a logcat, I think that it will be useful.
Logcat link: https://drive.google.com/file/d/16aGo7nzgde6bN9NMU-yavc9IZNT_FPU6/view?usp=drivesdk
Googole said:
I got a Xiaomi Mi 10T Lite and it's running on Android 11 since some weeks.
But after it updated to Android 11, it sometimes locks itself when I'm using it and In have to unlock it all the time.
It goes black and then returns to the lock screen.
Does anybody else also have this problem and is this a bug that I should report?
Click to expand...
Click to collapse
Sounds like you have something running that is causing a soft reboot of your phone
I've been using android 11 on this device for a while and not had any such issues
Mine is going back to Xiaomi today, mine keeps going into a boot loop and lasts for 3 hours or so sometimes before it sorts its self out, if I reboot it it just carry's on into boot loop, it often starts this when it is charging, at the moment the phone is unusable, so it is going back for them to check out.
TheFixItMan said:
Sounds like you have something running that is causing a soft reboot of your phone
I've been using android 11 on this device for a while and not had any such issues
Click to expand...
Click to collapse
I really don't know what causes it.
Googole said:
I really don't know what causes it.
Click to expand...
Click to collapse
Is this problem fixable?
Googole said:
Is this problem fixable?
Click to expand...
Click to collapse
Quick fix would be to factory reset your phone
Long fix would be to do an Adb logcat and record the exact moment your device soft reboots and see what it is but even then it maybe hard to work out what is causing it
TheFixItMan said:
Quick fix would be to factory reset your phone
Long fix would be to do an Adb logcat and record the exact moment your device soft reboots and see what it is but even then it maybe hard to work out what is causing it
Click to expand...
Click to collapse
I have done several factory resets, it did not improve my phone and the ADB logcat is not something I know about so I have now sent it back, I love the phone but I can't deal with the continued frustration it causes me, I am happy if they fix the issue and send it back to me, if not I would probably purchase another one.
My wife also has this phone (I purchased 2 at the same time) she does not have any issue with hers and we have pretty mush the same Apps and everything on the phones, I have even used her charger to see if that's causing some of the issue..
I will keep you all informed of the out come.
I've readed on Reddit that people experience crashes on their Xiaomi all the time.
So I've updated Webview and I'll let you know if the problem is solved.
Googole said:
I've readed on Reddit that people experience crashes on their Xiaomi all the time.
So I've updated Webview and I'll let you know if the problem is solved.
Click to expand...
Click to collapse
There was a bug yesterday that caused Google apps (and others that use Web view) to force close due to a bug in webview. This only effected a specific version of webview and was fixed in a few hours. I didn't notice any such issues on my device but I was using latest beta version.
As long as your webview and chrome is up to date your apps will function correctly (in regards to webview)
I tried that, but that didn't resolve the issue.
I have also done a factory reset but the bug still appears.
I know for sure that there is nothing wrong with my phone, so it must be a MIUI side issue and I'll report that bug to them.
So that means the topic is closed.
Thank you for your help!
Googole said:
I tried that, but that didn't resolve the issue.
I have also done a factory reset but the bug still appears.
I know for sure that there is nothing wrong with my phone, so it must be a MIUI side issue and I'll report that bug to them.
So that means the topic is closed.
Thank you for your help!
Click to expand...
Click to collapse
If you have done a factory reset and the problem still exists & you haven't installed any other app which could cause a soft reboot without any logs you will never know why it's doing it.
You could also have a hardware fault
It's very unlikely related to MIUI otherwise everyone (or a very high % of users) would also have the same issue and they are not. It's related to your device.
There's only two main bugs with MIUI android 11 on this device
1 - 3rd party launchers gestures & an icon of the app you're using appearing in the top left of screen when closing an app which has a work around of launching the system launcher then switching to 3rd party launcher.
2 - notification layout is incorrect with text too far aligned to the left. This doesn't effect functionality but looks wrong & could slightly crop off the far left of text.
I've done some research, asked the same question at more forums and tried some things and I'm convinced that this is a bug because of these reasons:
- My phone worked perfectly fine on Android 10
- I don't think there is a app that causes this bug because they worked perfectly fine on Android 10.
- There is no chance that there is anything wrong with my device because I'm really careful with it and I didn't done dangerous things for my phone
I'll report it to Xiaomi through Services and Feedback
Ok, if you read my message #7 above I explain about my phone going into reboot and boot looping etc, I have sent it back to Xiaomi on Tuesday, and this morning I have tracked the repair, They Say:
1. Fault category: Electrical - Other
2. Awaiting Component
So my phone obviously has a HARDWARE fault. I am pleased with the speed Xiaomi are dealing with this - so far.
See the OP
Googole said:
See the OP
Click to expand...
Click to collapse
Your logcat is not accessible to the public via that link and I hope the logcat was recorded at the exact time the issue happened
TheFixItMan said:
Your logcat is not accessible to the public via that link and I hope the logcat was recorded at the exact time the issue happened
Click to expand...
Click to collapse
I've changed the settings now, it should be accessible for everyone.
It wasn't recorded at the exact
moment the issue has happened but I really hope it could be useful because it recorded the crashed that happened earlier this day.
Googole said:
I've changed the settings now, it should be accessible for everyone.
It wasn't recorded at the exact
moment the issue has happened but I really hope it could be useful because it recorded the crashed that happened earlier this day.
Click to expand...
Click to collapse
Do you have a messaging widget on your home screen?
Can you remove all widgets from your home screen and then see if your phone continues to restart.
Looks like something is happening when you receive a message and the widget is failing to update
If it's a 3rd party app or launcher with the widget uninstall it
I don't have a widget, I use the default launcher because I can't use Smart Launcher 5 (which I used on Android 10) with gestures.
I use the default time and weather widget from Xiaomi which is linked to the default Weather and Clock app.
I've removed all my widgets from the home screen, I'll let you know if that works.
Googole said:
I don't have a widget, I use the default launcher because I can't use Smart Launcher 5 (which I used on Android 10) with gestures.
I use the default time and weather widget from Xiaomi which is linked to the default Weather and Clock app.
Click to expand...
Click to collapse
That is really the only error in your logcat (it also doesn't seem a complete logcat and only a part of one)
As mentioned the logcat needs to be recording at the exact moment the restart happens.
Other things you can try is clearing data of the following
Google services framework
Google
Google play services
TheFixItMan said:
That is really the only error in your logcat (it also doesn't seem a complete logcat and only a part of one)
As mentioned the logcat needs to be recording at the exact moment the restart happens.
Other things you can try is clearing data of the following
Google services framework
Google
Google play services
Click to expand...
Click to collapse
I guess I'll try to install Smart Launcher then, and then I'll try the things you advised me.
If the problem is still there, I'll make a new logcat.