HI,
My GWA 2 is getting rebooted randomly, I was able to collect dump logs , copied it on computer and can see @@@@@@ characters in kernel log around crash time, no other alarms in logs, After enabling debug mode, On crashing now watch goes into a screen with watchdog logo in background and some watch details on top, but no touch/button works to see rest of the logs. I am able to pass all the test in test mode. I have reset watch multiple times. Can some tizen developer help me in debugging, What other steps I can do to easily diagnose the issue? Can I get the backtrace of the OS crash?
Related
Hoping someone knows how to do this...
I have recurring reboots when I use google maps navigation, and I am trying to narrow the problem down to hardware or software. I am trying to use adb to capture the event in a log, but there is a buffer (delay) between the events on the phone and them showing up in the log on my PC screen. So when my phone spontaneously reboots, I don't see anything in the log that is causing it. I'm guessing it just doesn't have time to get it out of the buffer before the reboot. Of course, upon reboot, the log is cleared and I can't see anything.
Does anyone know of an adb logcat option or an entirely different approach that will eliminate this buffer and give me real-time activity monitoring so I can see the reboot in the log? Any other way to solve this problem??
All,
this morning I thought My watch is already broken. no proper input handling was possible anymore, gestures were not recognized, Displayed content was moving without touching the display.
Reset was not possible as it would habve required interaction with the watch which was not possible anymore.
My only solution was to drain as much battery (using the remote camera app) and wait until the battery became empty. After a restart, the watch behaved properly (sigh!) so no HW issue. First thing I did to have at least a chance to interact with the watch should the behaviour happen again: I enabled developer mode so that I can use adb get some logcat and reset the watch.
Anyone eles experienced that by now?
Any better solutions?
Thank you,
thunder
thunder-62 said:
All,
this morning I thought My watch is already broken. no proper input handling was possible anymore, gestures were not recognized, Displayed content was moving without touching the display.
Reset was not possible as it would habve required interaction with the watch which was not possible anymore.
My only solution was to drain as much battery (using the remote camera app) and wait until the battery became empty. After a restart, the watch behaved properly (sigh!) so no HW issue. First thing I did to have at least a chance to interact with the watch should the behaviour happen again: I enabled developer mode so that I can use adb get some logcat and reset the watch.
Anyone eles experienced that by now?
Any better solutions?
Thank you,
thunder
Click to expand...
Click to collapse
Shut down the watch by holding the power button on the back.
Hello,
I've had the zenfone 2 for about a month now and there is an ongoing problem with my contacts:
- When I go to my text messages (also sometimes whatsapp logs) the contact names are gone and only the numbers show.
- When I go to the phone dialer, it just keeps loading and nothing comes up, or sometimes the dialer loads but my recent calls log is gone.
- When I go to my contacts page it is empty.
(I have screenshots of the above issues for clarification)
I can solve this problem temporarily by emptying the cache of the "contacts" app and the "asus calling screen" app, but the phone keeps glitching at least once a day.
Has anyone else experienced this?
Does anybody have a solution for this issue?
Thanks,
Ariel
Same issues as your Zenfone 2
cwangari said:
Hello,
I've had the zenfone 2 for about a month now and there is an ongoing problem with my contacts:
1 - When I go to my text messages (also sometimes whatsapp logs) the contact names are gone and only the numbers show.
2 - When I go to the phone dialer, it just keeps loading and nothing comes up, or sometimes the dialer loads but my recent calls log is gone.
3 - When I go to my contacts page it is empty.
(I have screenshots of the above issues for clarification)
I can solve this problem temporarily by emptying the cache of the "contacts" app and the "asus calling screen" app, but the phone keeps glitching at least once a day.
Has anyone else experienced this?
Does anybody have a solution for this issue?
Thanks,
Ariel
Click to expand...
Click to collapse
1 - I have seen this as well
2 - Same here
3 - Same here
What I have noticed is the following:
4 - When I go to dialer, it takes literally over 15-20 seconds to pull up the call log history. It almost seems like its searching for this data and then there is a delay in posting it.
5 - SMS app (regardless of which one it is, have used stock, GoSMS, ChompSMS, others) hangs up, starts doing weird things, as if the processor is trying to play catch-up with the buttons pressed. If I let it be, it comes back to the last commands pressed. Reminds me of the old Microsoft windows days...
6 - Battery is draining very very fast. I see a full charge around 6:30AM, then the phone reaches 40% by noon. This started happening a few weeks ago, so I am thinking a software update caused this issue.
7 - Bluetooth communications with the car console is very slow. It sometimes takes 15-20 seconds for the phone to drop the call if I press the hangup button on the steering wheel of my car.
8 - Really close to giving up on Android. Can anyone help?
Is there an ASUS live customer support that I can call for help? Does anyone have this number handy?
-- Faisal
Same here
Yep - can confirm. I have the same issue.
One thing that worked for me was selecting the 'Contacts to display' tab and removing some of the sources.
I thought that since it was polling information from so many different sources at real time, it might be slowing down.
This temporarily worked, but the issue came back.
Extremely frustrating problem - you don't expect these kinds of bugs to make their way through QC.
This is what fixed most of my issues
Mister_Simon said:
Yep - can confirm. I have the same issue.
One thing that worked for me was selecting the 'Contacts to display' tab and removing some of the sources.
I thought that since it was polling information from so many different sources at real time, it might be slowing down.
This temporarily worked, but the issue came back.
Extremely frustrating problem - you don't expect these kinds of bugs to make their way through QC.
Click to expand...
Click to collapse
I flushed application cache for contacts and a few other apps, and restarted the phone. Contacts were fine afterwards.
was the issue solved or there is a suggestion how to solve it?
I have the same issue..Any solution??
Clear data option for all Asus apps which will clear cache itself. Or you can hard reset your phone.
Starting early July, my Pixel 2 XL on stock Google ROM has been crashing constantly. Tried a whole sort of troubleshooting but cant seem to fix it. Looking to see if someone can see something that I dont.
Symptoms
When Pixel 2 XL, on (PQ3A.190705.001, Jul 2019), charging and left alone, the phone would become unresponsive for up to 5 minutes, then proceed to do a soft restart and show the Phone is initializing. No problems when running the phone off the charger.
Troubleshooting
Tried the basic troubleshooting steps from Google Support (Update to latest system update, remove free space, safe mode, factory reset)
Tried reflash June factory image from Google (PQ3A.190605.003, Jun 2019)
Tried different charger
Disabled digital wellness app
Disabled the Private DNS and uninstalled Blockada (heard issues with it)
Nothing seems to work. Google support suggested that I get it exchanged under warranty, however, I feel like it is a software issue more than hardware. This is because when I monitor it under logcat when it stops responding, I see there is a whole bunch uncaught FATAL EXCEPTION so it seems that something is causing it to error out.
I am not too familiar with Android logs so I cant pinpoint it out. If anyone have more expertise can help with taking a look at the log to see what the root cause is, that would let me know what I should do for next step (ie try Android Q Beta if it is a system issue, get a new phone if it is a HW issue, or change certain settings).
Here is the log file
Thanks
ROM: Pixel Experience (Android 10 Based)
Hi, I recently encountered a problem when I turn off my airplane mode. Usually (around 2-3 years ago), and normally on other phones, one would receive all the unreceived messages immediately after turning off airplane mode. However, this does not happen for almost two years now when I turn off my airplane mode. It usually takes around 10 minutes and up to an hour for any message to be received at any time after I turn off the airplane mode.
This gets annoying when certain apps ask for OTP authentication. Weirdly enough, some apps that are designed to detect the OTP automatically would not have problem even if the message of the OTP is received an hour later. While this is something to be grateful for, some apps still don't have that technology.
Is there any way to fix this?
For additional note: 1) I have been regularly using the airplane mode whenever I'm home since the first time I bought this phone (2018) and only encountered the problem since 2021; 2) I have tried hard reset, changing ROMs, but it only worked shortly. Once I turn the airplane mode on regularly, the delay will happen again; 3) I installed the PE 10 in 2020.
Thanks in advance!
It may be persist partition is corrupted. Search for fix on xda.
Or try to change message app.
drnightshadow said:
It may be persist partition is corrupted. Search for fix on xda.
Or try to change message app.
Click to expand...
Click to collapse
I have tried several messaging apps, all got the same error