Related
These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.
AgalychnisCallidryas said:
These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.
Click to expand...
Click to collapse
Hmm. The only issues I've had are related to system apps randomly being uninstalled. It is definitely frustrating, especially when my phone app disappears.
I have had the same issues. Contacted Verizon and they sent me a x2. I really miss sense but do not miss the issues. This happened on all 4 of the inc2's Verizon sent me.
Droid 3 tomorrow if I can! 3 phones in two weeks: Inc, Inc2, Droid 3! New record!
Nvm, going for a new inc2. Also, now my google account is gone and I can't add it back. This is causing market not to open. LOL. Can you say lemon?
Everthing that happened to to happened to me
Sent from my ADR6350 using XDA Premium App
My volume will.be.all the way up even alarm volume but all my alarm does is vibrate
Sent from my ADR6350 using XDA Premium App
Really hope the next one is better.
It sucks to hear you having all these problems. I too just got the Dinc2 coming from the original Dinc. I am having none of the issues you are having, updated latest gingerbread OTA, non-rooted. The only problem i had was a lagging touchscreen when using a certain cable charger combo, but once i switched cables everything was fine.
AgalychnisCallidryas said:
These are issues I have. I am running 2.3.3 OTA, unrooted.
1. Bootloop, factory reset fixed.
2. When I manage applications, if I click on an app, it reroutes me to a different one, so I often uninstall the wrong app.
3. Touch screen sometimes fails, reboot fixes.
4. Clock app disappeared, the factory reset mentioned earlier fixed it.
These just really annoy me.
Click to expand...
Click to collapse
I'm having the same issues as well. It's annoying but better than issues I've had with other phones.
Seems to be on a phone by phone basis. Imma try Inc2 #2 lol.
Hope you have good luck. I went through 4 before I had enough.
HTC responds to me:
"Dear **** *****,
Thank you for taking the time to contact HTC, ****. We are sorry to hear about the issues you have experienced with your HTC Incredible 2 after the recent update. We will gladly assist you with this inquiry.
With regards to the clock/alarm feature missing, this is something we are aware of and we are working on a resolution. Currently, we do not have an ETA as to when this fix will be available.
With regards to the other issues you were experiencing, these are not known issues at this time. For the failure to load issue, the only thing we could offer for that is to preform the factory reset. With regards to the market app, we could suggest you clear the data from the app by going to menu>settings>applications>manage applications>all(at the top)>market>clear data. Once the data is cleared we would ask you to restart your phone and try again.
It is entirely possible that the update did not apply correctly during the setup process causing the issues you have experienced. This could be why the factory reset has corrected these issues at this time.
If you run into any of these issues again, we would suggest that you try your phone in safe mode before jumping to a factory reset. This will disable third party apps and drivers from launching when the phone is powered on. You will still be able to make and receive calls, text messages, email, and use the internet.
To put the Incredible 2 into Safe Mode, use the following steps. Be patient with these steps, you may not get it into Safe Mode on the first attempt.
With the phone powered off, remove the battery for 10-20 seconds and re-insert it.
Press the Power key on your device
When you see the white screen with "HTC" on it, press & hold Menu key until OS loads.
"Safe Mode" text will appear on the lower left of screen to advise that you are in safe mode,to get out of safe mode just restart the phone.
If the issue was not happening while the device was in safe mode, this would indicate some kind of conflict or interference from a third party application. You would need to rule them out by uninstalling the apps until you find that the phone is working normally again, and then avoid using that app or combination of apps.
We deeply regret any inconvenience this has caused you, ****. As always, we are here to answer any technical questions or concerns you may have between 6am to 1am EDST, 7 days a week for your convenience, or by phone at 1-866-449-8358.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number *****************.
Sincerely,
Angela
HTC"
Okay I don't know if this is a bug in every Android version that still hasn't been fixed or is it an app that's causing it.
What happens is when I would be using an app like for example Google talk. I would try opening YouTube it would open calculator. And if I try opening messaging it would still open calculator. No matter which app I'd open it would open the wrong app. And I either have to kill all apps or restart my phone
I had this issue only my G2, my Nexus S, Anyone else having this?
Can't recall if I had it on my Sensation or not...
Sent from my Galaxy Nexus using xda premium
This has never happened to me. Are you completely stock?
Sent from my SGH-T989 using xda premium
I have had a similar error on multiple versions of android where you hit the back button and it starts to cycle through several different apps.
Yup happens to me on a few occasions. It just cycles like axion said
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
I've seen this once on my Galaxy Nexus only, never on a Nexus S, of GS2. A reboot seemed to resolve the issue. I've not seen it again since.
joshnichols189 said:
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
jonathan3579 said:
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
thequinox said:
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
Click to expand...
Click to collapse
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Happened to me too. Usually helps to get rid of all alps in multitasking menu.
jonathan3579 said:
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
krohnjw said:
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
Click to expand...
Click to collapse
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Lowtrash said:
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Click to expand...
Click to collapse
No, I've just backed down the stack. I am curious as to the trigger for the behavior though as it is a rather uncommon occurrence.
krohnjw said:
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
Click to expand...
Click to collapse
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that? To add to that, if a device pre-ICS did have this problem... Would it not be considered defective? *Keeping in mind that most people don't have the problem.* I have absolutely no issues no matter the number of apps I have open. So is my device defective because everything opens as it should? As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
jonathan3579 said:
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that?
Click to expand...
Click to collapse
Where do you see this claimed to have happened on any pre 4.0 rom?
I had this issue only my G2, my Nexus S, Anyone else having this?
Click to expand...
Click to collapse
jonathan3579 said:
I have absolutely no issues no matter the number of apps. As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
Click to expand...
Click to collapse
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
krohnjw said:
Where do you see this claimed to have happened on any pre 4.0 rom?
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
Click to expand...
Click to collapse
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Yep I know what you mean, happens to me on Google Music.
Th easiest solution I found was to force stop the app that's bugged out.
I've had this too. Swiping away the app I'm trying to open and the one it is opening instead has fixed it for me.
jonathan3579 said:
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Click to expand...
Click to collapse
Defective software I have no issue with - that's a harsh classification for a bug, but not incorrect.
Your statement of "Return it" followed by "most of us do not have these issues" seemed to imply a belief that the physical unit must be defective (in comparison to a unit that did not experience this issue) rather than a behavior or set of behaviors causing as software issue as most users do not experience this. Thereby returning would resolve the issue.
Given the symptoms present when this occurs I can't imagine this to be true i any way, shape or form. Especially given that this bug has existed since 4.0 hit AOSP and on builds for the Nexus S as well (hence why it's absurd to blame this on a singular hardware fault of a single device).
I am interested in reproducing the issue, or capturing a logcat the next time it occurs (it only seems to happen when I am in the car unfortunately) to see if the WindowManager of ApplicationManager are supposedly starting the proper activities or the issue might lie with the package manager.
I've had this happen when i open a lot of apps without closing them and use the multitasking button to switch between apps.
So here's a weird one: I'm running stock 4.1.2, and after the update I noticed the alarm going off when I set it... but only for about a second before turning itself off. It doesn't happen consistently - it only seems to happen when I leave the phone charging overnight. If I set the alarm for a minute from now, it goes off as it should. Anyone experience this? Any ideas?
I've tried setting the alarm to repeat weekly, clearing the clock app's data, and, yes, doing a full factory reset. The issue returned. Sometimes I think it might have to do with whether Google Now or Aurora (alpha Firefox) have recently added something to the notification bar, but that's pure speculation.
Don't want to install an app to rectify this, but I suppose I will if I must.
Thanks
P.S. - This thread appears to be nearly identical regarding a GSIII, but even if disabling the lock screen is a work-around, I can't do it.
P.P.S. - Any chance Samsung will be issuing any further updates (bug fixes), or can we expect this most recent update to JB to be the last?
Bump
Nobody else has this issue!?
Nrbelex said:
Bump
Nobody else has this issue!?
Click to expand...
Click to collapse
I have had it from time to time. Haven't found a fix for it.
Sent from my SPH-D710 using xda premium
graydiggy said:
I have had it from time to time. Haven't found a fix for it.
Click to expand...
Click to collapse
Well at least I'm not going crazy. I encourage you and anyone else having this issue to star it on the Android bug tracker: http://code.google.com/p/android/issues/detail?id=43430
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)
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.