Question Issues afteratest update - Samsung Galaxy S21 FE

S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?

Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that

blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...

I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.

Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.

If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.

Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.

Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.

no such issues here with the eu version. definitely an upgrade in every way.

After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.

I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.

d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?

xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.

blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?

xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.

blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.

Related

Screen sometimes slow to turn on, occasionally freezes when attempting to unlock.

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

Lots of different small issues

Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
luckyvictor said:
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
Click to expand...
Click to collapse
Try to update I never had any of those issues
I have also these problems. I have February update.
madmanwild said:
I have also these problems. I have February update.
Click to expand...
Click to collapse
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
rob420p said:
Try to update I never had any of those issues
Click to expand...
Click to collapse
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
luckyvictor said:
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
Click to expand...
Click to collapse
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
madmanwild said:
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
Click to expand...
Click to collapse
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
luckyvictor said:
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
Click to expand...
Click to collapse
I am on stock but I do have root.havent done much modification yet waiting for twrp
rob420p said:
I am on stock but I do have root.havent done much modification yet waiting for twrp
Click to expand...
Click to collapse
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
luckyvictor said:
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
Click to expand...
Click to collapse
Honestly I don't think so I really haven't messed with the battery besides putting a %
luckyvictor said:
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
Click to expand...
Click to collapse
Yes, all off - battery adaptation and manually set no optimization on my app...

Uresponsive black screen after updating to Android 10

After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.
https://support.google.com/pixelphone/thread/14074635?hl=en
Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.
So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.
I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.
I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.
@MeetFace, yes! Same here since the November update. Something isn't right.
I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.
darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!

My Xiaomi Mi 10T Lite goes black after using for while after Android 11 update, is this fixable or a bug that I should report?

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.

Bluetooth gone

After the latest update on 10+, function for Bluetooth, on pictures, gone...along with several other options. I'm sending a screenshot. What you see, that's it. Thought I had to scroll down, but nope
What update?
Go to the Wearables app.
All permissions need to be enabled.
Goggle Play Services must be enable at least initially.
Clear system cache.
Network reset.
Last night, came up UI one version 4
Rule #1 if an OS is fast, stable and fulfilling its mission... let it be.
This N10+ is still running on Pie, it's current load will be 2yo in June. Fast, very stable with minimal maintenance. Updates especially firmware can break things, permanently. The highest I would upgrade the N10+ to is Android 10. I also have one N10+ running well on 10.
I see no valid reason to upgrade either. Security simply is not an issue with these devices as such.
You'll need to find a workaround if the solutions I provided fail to work.
In addition see if any Wearables updates are available. Other related app updates as well.
If you get tired of trying to find the issue, factory reset. It may or may not work...
blackhawk said:
Rule #1 if an OS is fast, stable and fulfilling its mission... let it be.
This N10+ is still running on Pie, it's current load will be 2yo in June. Fast, very stable with minimal maintenance. Updates especially firmware can break things, permanently. The highest I would upgrade the N10+ to is Android 10. I also have one N10+ running well on 10.
I see no valid reason to upgrade either. Security simply is not an issue with these devices as such.
You'll need to find a workaround if the solutions I provided fail to work.
In addition see if any Wearables updates are available. Other related app updates as well.
If you get tired of trying to find the issue, factory reset. It may or may not work...
Click to expand...
Click to collapse
I just updated, as usual. Unfortunately find errors afterwards
J448BLE said:
I just updated, as usual. Unfortunately find errors afterwards
Click to expand...
Click to collapse
J448BLE said:
I just updated, as usual. Unfortunately find errors afterwards
Click to expand...
Click to collapse
After updates clear the system cache.
I'll try that. Where do I go?
Boot menu.
Where's that?
Power off. Hold the volume up button immediately after engaging the power on button. Continue to hold the volume up button until the menu appears.
I won't lose information off my phone?
J448BLE said:
I won't lose information off my phone?
Click to expand...
Click to collapse
No. Just don't mistaken hit the factory reset option next to it.
OK. Cheers bud
J448BLE said:
After the latest update on 10+, function for Bluetooth, on pictures, gone...along with several other options. I'm sending a screenshot. What you see, that's it. Thought I had to scroll down, but nope
Click to expand...
Click to collapse
On the bottom row, you have to scroll right until you see the ellipses (three dots). Click that and scroll down until you find Bluetooth.
That works. Used to scrolling down, never realised scroll right. Cheers
Samsung likes to hide settings sometimes. Some appear only if you double tap a word or box for example.
Nervous tapping sometimes does solve problems...
So true!

Categories

Resources