Question How to read a log file from S21 Ultra - Samsung Galaxy S21 Ultra

I have a hardware issue on my Samsung and am preparing it for repairs or replace. I took a Dumpstate/Logcat/Radio log by dialing *#9900# and copied everything to SD.
The fault is that the sound cuts during calls and need reboot before I can hear anything at all.
I know the exact time when the fault occurred yesterday during a call. Where should I look among the log files and is there any app that highlights the issues ?
It is related to speaker and microphone so in one word - sound

Now that you know the exact time when the fault occurred yesterday, why not search the log file to see what exception message is at that time? You should be able to get some clues.

You can also post the log information near that moment and let everyone here try to analyze it for you. Or just submit it to Samsung technical engineers for help.

James_Watson said:
You can also post the log information near that moment and let everyone here try to analyze it for you. Or just submit it to Samsung technical engineers for help.
Click to expand...
Click to collapse
Yes, but what file could contain that information? It saved like..a bunch of folders and files under 'log' folder

Related

Galaxy Note Crash report

Hi people. I wanted to report my horrible experience today and i found no general thread to add my input so i created one.
At some point during the day i opened the S note app to browse some notes i'd written last night when the phone froze while trying to open one. I pressed down the power button to restart the phone but all it did was shut down so i plugged the charger in to see if the battery died (weird because it was still at 70%+). The phone responded to this and the offline battery charging screen appeared.
I tried to boot the phone after that and indeed i saw the galaxy note logo appearing and that's all i saw. The phone wouldn't carry on to the samsung logo. So it just froze again there. I restarted ofc and the phone booted normally and for 5 minutes it was okay until...
Until i tried sending an sms at which time the same thing happened.
Not to tire you guys further the same thing has been happening for the remainder of the day up until half an hour ago where the most recent crash took place.
The issue happened mostly during a cpu speed shift. I know this because it happened as i was waking the phone a couple of times and while i generally used it for something active(yes like opening notes)
I am worried sick and i have been browsing my guarantee papers thinking of returning the phone for another one.
Has anyone else got the same issues? The samsung quick start guide says that if you get fatal errors and such you should reset the phone. Well i did several times and at one point i had a reboot where the screen went all bad with random color rows like a major screen error.
Would you recomend i give it in or do you have any ideas about what might have caused those issues?
Thank you for your time.
After tons of crashes, a glitched screen that scared the beejeezus out of me and a hard crash that made my device emit a high pitch sound similar to a bomb countdown I think i am getting close to what is making my Note crash that hard.
I guess i am one of the few people that actually uses the Note as a... Notepad!
I write many notes on it, mostly capturing good ideas that come spontaneously and generally when i want to capture a thought and trap it in my phone for later utilization. Problem is the Note can't handle it(At least that's what i think it is).
I have stored in my S-Memo application approximately 30 notes, most of them written in the old fashioned keyboard way and full of text, whereas a few others written in the Galaxy Note way with the S-Pen.
Now whenever i open the S-Memo app my phone crashes without even opening the app. It freezes on the black screen interval between my tapping the S-Memo icon and actually opening it. Now that's not the only occasion my Note crashes but it's the surest and plus it's where the problem started in the first place.
[Update] I just tried deleting all the notes and the phone got stuck while deleting. But finally they have been deleted.
I will keep the thread updated if i run into other problems. I am trying to narrow down the problem. If it gets stuck again then it's probably not the notes.
After deleting the S memo notes my phone is back to normal.
No crashes, no freezes, no nothing.
I would like to hear other people's feedback on the matter. Does your phone behave the same after writing 30+ heavily written notes on S-Memo?
If yes then Samsung sure picked the wrong name for it's phone. It does everything BUT notekeeping!
Anyway. My 5 cents guys. Peace, out!
Sorry if this is not your case (and I am probably writing these rather late), but I am having a similar issue with my notes. While trying to open a note from inside S Memo app, I am receiving a crash report ("The application S Memo (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly. Please try again.The application S Memo (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly. Please try again.").
This crash is not happening to all my notes. So I tried to see how are the notes that is crashing different from the other notes that is not crashing. In my case is the note date (written at the bottom of each note). The notes that when I am trying to open the application crashes have a creation date 01.01.1970 while the others are having the correct date.
This change in the creation date probably happened yesterday when I updated my phone to XXKL7.
PS. The notes are only crashing within the S Memo app. They are not crashing for example if I try to open them as a Widget that I have exported in the home screen.
I can't find a way to change the date, so I will try to export the notes and delete them.
I will keep you posted.
BRGDS,
Stathis
Thank you for the info on this issue. I love my Note, but sometimes I get the feeling that Samsung has been sending the Galaxy Note out to the marked without the proper testing beforehand. It looks as if your Note has a problem with handling to many notes at the same time, and since the note-handling is one of the phones major features, I really hope this is something Samsung fixes before they sending out the upcoming ICS-update.
Thank you for the info on this issue. I love my Note, but sometimes I get the feeling that Samsung has been sending the Galaxy Note out to the marked without the proper testing beforehand. It looks as if your Note has a problem with handling to many notes at the same time, and since the note-handling is one of the phones major features, I really hope this is something Samsung fixes before they sending out the upcoming ICS-update.
Click to expand...
Click to collapse
Actually thank you for reminding me of this issue. I forgot to update this topic.
The thing is that the issue happened again a few days after i erased those memos. I called the store that sold me the device and asked to give it back to them. They said that one way or the other they will have to hand it over to samsung for them to see.
They advised i wait after the holidays to really get some decent feedback.
Thing is that ever since i called the store my note has been it's normal self again.
I suspect though that under heavy use it will do the same again, but i cannot determine what triggers those freezes.
I have got two years of waranty. After the first week where the store just replaces your device no questions asked i now have to abide by the standard procedure, so i keep a close eye on my note for any glitches, malfunctions and freezes.
Truth is that some part of me wants to forget this ever happened and not pursue the way to finding out what the problem is in fear that samsung will find some loophole out of their posteriors and not replace my device.
I will not push it but if the phone breaks down again i will have to send it to them.
Now if there is any of you who knows of any diagnostic tools for the Note i would greatly appreciate it.
btw i believe the same thing about samsung, their devices are poorly tested but their devices policy are open source in comparison to Apple and i like that. Sometimes i think that Apple is there just to piss off people and give it's competitors the edge with their overprotecting policy.
kdiomedes said:
Sorry if this is not your case (and I am probably writing these rather late), but I am having a similar issue with my notes. While trying to open a note from inside S Memo app, I am receiving a crash report ("The application S Memo (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly. Please try again.The application S Memo (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly. Please try again.").
This crash is not happening to all my notes. So I tried to see how are the notes that is crashing different from the other notes that is not crashing. In my case is the note date (written at the bottom of each note). The notes that when I am trying to open the application crashes have a creation date 01.01.1970 while the others are having the correct date.
This change in the creation date probably happened yesterday when I updated my phone to XXKL7.
PS. The notes are only crashing within the S Memo app. They are not crashing for example if I try to open them as a Widget that I have exported in the home screen.
I can't find a way to change the date, so I will try to export the notes and delete them.
I will keep you posted.
BRGDS,
Stathis
Click to expand...
Click to collapse
Stathi
I have no clue what to make of your issue. I myself try to understand what is happening but you are the second person to report an issue with the S-Memo application.
At least your phone did not freeze and crash. That should be consoling.
My problem happened when i created a folder within the S-memo and stored some notes inside. It could be the folder or it could be the files but after the first crash and reboot the thumbnail of one of the notes had trouble showing up and instead was replaced by a blank thumbnail, as if the text inside had been erased(but when you browsed the note you found out that it wasn't).
I don't know if that helps but that all i can think of.
In my case it seems that the problem is more generic, but i have no clue where it originated.
As i said above if it happens again i will send it back to samsung. If it keeps happening to you i suggest you do the same. Don't let them sell you a 600-700euro device without making sure it works perfectly. Remember the making of the device cost wisely is ridiculously lower. It might even amount to something in the vicinity of 50 euros for the materials and the assembly altogether.
To sit back and accept a faulty device is making their pockets rich selling snake oil to the people.
Well, I tried to enter the folder that the S Memo keeps the notes but couldn't fix anything. Finally I sync them to my evernote account and did a factory reset.
I'll come back if I find anything useful. I think too, that Samsung doesn't thorough exam the updates.
Btw, I am not the second person to report such a problem but the forth. It's http://forum.xda-developers.com/showthread.php?t=1362249 and http://forum.xda-developers.com/showthread.php?t=1347157 that I just found out.
I'd like more info on this problem also. I haven't had the S Memo app crash but I have noticed some odd behavior. Luckily I haven't written any important notes, just been fooling around to see how the app works. It seems like some notes mysteriously disappear and maybe reappear later or just are deleted and I've had notes duplicate themselves. I just thought it was something I was doing wrong since I wasn't really doing anything usefull with the app.
Now that I'm aware of the quirks, I'll pay closer attention to what I'm doing.
For anybody who was modifying/saving/deleting notes, were you doing it from the SD Card /Application/SMemo/cache and /Application/SMemo/switcher? Just curious... It seems like their file naming scheme is a lot to be desired with variations of the same memo being named strokeXX.png, thumbXX.png, prevXX.png, and a syncXX.png if you did a sync. The XX is incremented for every note created, but I've noticed when deleting an earlier note then creating a new one later, that numbering system can get out of allignment and weird things happen.
That's all my observations for now but I certainly won't be putting any really important information in a note.
MP
I have had the same crash problem with some new notes. They didn't have the faulty date that I saw after the update to KL7.
Fortunately, I am able to synch them and same the information they contain.
I'll check the files that you say and maybe we could figure out why is it happening.
Sent from my GT-N7000 using XDA App
Hi. Sad to say that imhaving this issue right now. I have only 4 memos with just doodles in them and some text none of which are working. All memos created and saved via the s memo shortcut cannot be reopened and causes the system crash. Widget memos seem to work ok but opening them via the smemo sshorctut causes crash as well.. I hope help comes soon...
Sad to report I have the same problem!
I have 4 drawing on my a memo application and can't open the two more retail drawing! I am using firmware gt-n7000ubkk1 maybe installing another firmware will work :a
Any help or solution would be great!
Sent from my GT-N7000 using xda premium
I updated my firmware to the latest open Europe one and the problem stop! So the best to solve this problem is to.flash a new firmware!
Pure vida guys!
Sent from my GT-N7000 using xda premium
Sent from my GT-N7000 using xda premium

[APP][2.3.3+][NFC] NFC ReTAG PRO --> Temporary SALE

Hello everybody,
just started a temporary sale for NFC ReTag PRO...
Use any NFC tag (write protected and re-writable) to trigger multiple functions on your device!
You can use this app to associate multiple functions (e.g. toggle Wlan, Bluetooth, Mobile Data, Airplane mode, start navigation,run Tasker task, launch any installed app, use media buttons, call a phone number, add a timestamp, calendar entry and many more) to a specific NFC Tag via an app internal database.
Get it NOW and save some money
Link to the Support thread:
forum.xda-developers.com/showthread.php?t=1477138http://
Free version also available !
Nice and first! Downloading now...
Text to speech bug
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
GenePaton said:
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
Click to expand...
Click to collapse
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
ascsa said:
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
Click to expand...
Click to collapse
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
GenePaton said:
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
Click to expand...
Click to collapse
No Problem ... ... but let´s move to the official support thread (http://forum.xda-developers.com/showthread.php?t=1477138&page=100) ...because this is an old thread ...NFC Retag PRO is currently NOT on sale ... and we shouldn´t confuse the users ...
Just to clarify for any other readers, my e-mail answer to your last post :
The Galaxy S3 GT-I9300 (international model) is one of our main testing devices. Not sure if, there is a problem with the Vodafone Rom or the Australian T model, but it´s working fine here on 4.1.2.
Had a short look at our code and the official api and everything seems fine ... but without a log file or better a device on which we could reproduce the error it´s nearly impossible to be sure ...However, you mentioned it happens with other apps, too , so I would bet on some Vodafone "enhancements" ...
Btw. have you tried the Samsung TTS engine (settings--> language& input -->text-to-speech output--> preferred engine) instead of the Google engine?
I notice there are several versions of tasker. Which do I need?
Muscipula
Sent from my SM-G903F using Tapatalk

[Q] grievingDad needs HELP!

My son ODed on 11.17.14. I have been looking over his phone for some time. In a moment of utter stupidity I deleted all SMS messages. Links from me, his mother, his sibling and his friends. I have been looking online for ways to recover msgs. Dr. fone appears to be one of the best but does not work on his phone. It appears it would work if the phone was rooted. I have downloaded and installed towelroot. The app says the phone is not supported. I have found and used the three Mod string modifiers. the app still says the phone is not supported. I even went to the ATT device support center and they said they could not help. Please anyone, help me recover my son's messages. Its the last words I will ever have from him.
Thank you.
update grievingDad
Rereading post, additional info may be needed:
Model number
SAMSUNG-SM-G900A
Android version:
4.4.2
Kernal version
3.4.0-2178781
[email protected] #1
Tue Jul 22 13:58:46 KST 2014
Build number
KOT49H.G900AUCU2ANG3
If anything else is needed let me know.
grievingDad needs HELP!
Another thought,
I live in Baton Rouge, La. Available at 225-278-6466
If anyone is in town, New Orleans, or vicinity, I will come to you for help.
I am desperate to recover these msgs.
thank you.
Download AT&T messages if it is not already installed. After you log in it will start downloading all of the logs, sms, calls, etc.
@grievingDad,
I truly do not intend to be callous in this situation, but I will make a few points here and some may be helpful.
1) I don't know who you are, and since I do not know you, I cannot be certain of your motives for even trying to retrieve deleted messages. If you have truly lost someone and your motives are as simple as they appear in your firt message, my heart goes out to you and I wish you all the best in trying to retrieve your son's messages. I only say this because I would not even attempt to retrieve deleted messages for someone if they were doing it for spiteful or illegal reasons (Example: Jealous lover, disgruntled employee, etc.). There are probably more illegitimate reasons to retrieve another person's messages than legitmate ones. I am guessing that is why you will have a difficult time finding someone to help you with this directly. I am not an attorney, but even helping you to retrieve deleted messages sounds like a slippery slope.
2) You may be able to get an attorney to petition AT&T for a record of the messages. I believe that they have to keep them for a certain period of time for legal reasons. I'm not sure how accessible the messages will be. I remember trying to get a copy of one of my own messages (many years ago), and I wasn't able to get it from them. I know that messages are subpoenaed in court, but you might have to involve a judge to get them.
3) If your son used Hangouts for messaging (not the stock messaging app), you may be able to get the messages through his Google account. You might be able to ask Google for his password. I suspect that it would invole contacting Google and send them an official copy of the death certificate. I doubt that it would be easy.
4) It is possible that you could something wrong and brick the phone. In other words, you would never get anything off of it.
5) Consider the possibility that the messages may really be gone forever. Some things in the digital world offer the ability of recovering from "Oops!", but some things are meant to be deleted permanently. I am not trying to be a pessimist. All I am trying to do is counter the notion that everything is hackable and data is never really lost.
I don't think your being callous, just pointing out things i didn't consider.
1) It never occurred to me that that the post would be interpreted as nefarious. I know using names instead of handles is not very common, but if you wish you can look up his obit in the Baton Rouge Advocate. His name is William McCardle. My name is Douglas. I can be found at the number listed above in the same city. I'm not an attorney either, but I don't believe providing information on rooting a phone would lead to any type of prosecution. The service for all four numbers on the family plan are in my name.
2) I took the phone to the ATT device service center. I assumed if it was possible to retrieve msm from their servers they would have advised me there. But maybe not. I will contact ATT directly and/or consult with the family atty.
3) Hangouts is on the phone, but doesn't appear to have any msgs. Nothing is in Archives. The msms icon was one of the four permanent icons at the bottom, so I assume it is the stock messaging app.
4) I have copied/backup the device to Kies 3 and copied all photos to my computer. Even if the phone is bricked, it is worth the risk to get the msms back.
5) Its good you pointed out that not all data is recoverable. I was aware that even an App was able to retrieve msms, that some may be corrupted or overwritten due to reuse of the memory space.
6) Lastly, my motives are just that simple.
Thank you for the reply. Any further input would be greatly appreciated.
The App AT&T messages will recover just about every message sent and received from the line.
I don't recall if it recovers MMS messages.
It should be on the phone already. If not you may be able to download in he play store.
I used it once when I was going to be out of a service area. Connected to WiFi and used the app. While using the app it seemed to download every message ever sent and received. Took forever and I could not stop it.
Success
Thanks to those who replied. Installed the att msgs app and all the texts have been downloaded.
Just wish I had followed the advise on the 3rd when it was first suggested.
grievingDad said:
Thanks to those who replied. Installed the att msgs app and all the texts have been downloaded.
Just wish I had followed the advise on the 3rd when it was first suggested.
Click to expand...
Click to collapse
I kept meaning to go back and check this thread earlier to see how you made out. I am glad to hear that you were able to recover the messages. All the best.

Need help with understanding weird log files found on my phone

I've attached the log files I've also coincided their creating with a phone call received from a weird number can anyone tell me what this is.
joemm said:
I've attached the log files I've also coincided their creating with a phone call received from a weird number can anyone tell me what this is.
Click to expand...
Click to collapse
Where on the phone were they located? In what folder and internal or SD Card? By looking just at the content of files, it mentions media, audio, processing. Did you install any call monitoring or audio enhancing app? Phone has "extra volume" feature during call? - just thinking out loud
I found them in a folder called ttxlogger.log and it weird I would get a call from that unknown min st and a log would be created
joemm said:
I found them in a folder called ttxlogger.log and it weird I would get a call from that unknown min st and a log would be created
Click to expand...
Click to collapse
I don't have any of these, but is seems something is logging stuff. Were they always there? If it is unknown caller, then could it be that you have T-Mobile's spam call protection?
joemm said:
I've attached the log files I've also coincided their creating with a phone call received from a weird number can anyone tell me what this is.
Click to expand...
Click to collapse
I'm not sure if this will hep you at all but i also get this folder with a number of log files inside.
I am using a OnePlus 3T but the app i have pinned it down to is called CMSV6, a piece of software for accessing tracking data, live streaming and remote video upload from devices in commercial vehicles (which is part of my job).
I realized it was this app creating the logs because of the IP address in my log files is the same address as the server used to host the data that the app is showing.

Question What's going on in this Preloadinstaller.txt log file?

Found the following log in my files last night after a period of issues with my phone such as the notifications being reset, various digital wellbeing entries disappearing and some data loss etc despite me quite literally only using this thing for Facebook and YouTube.
Ignoring additional back story (someone else uses my phone regularly, need to know what's been done before I take issue with it), what on earth is going on in this log, and why/how was it even generated in the first place?
I'm autistic so unfortunately I have found myself both unable to drop this or find answers so I figured I'd look here.
If someone could explain if this is normal everyday behaviour for the phone, and if not what would be needed for this to happen (never seen the log before and it's in a folder with thousands of others, most of which are in an "adlg" folder).
To clarify, I did not request the logs nor do I know how to get them to generate so I am completely at a loss here.
Thanks so much!
This looks like same topic as started by @Baguete2963....
Are you posting under different names?
OnnoJ said:
This looks like same topic as started by @Baguete2963....
Are you posting under different names?
Click to expand...
Click to collapse
Nice catch! I'll take it from here.
Thread closed!

Categories

Resources