Yes, i didnt test but should work.
[ROM][UNOFFICIAL] LineageOS-16.0 & 17.1 [mako]
- Thread starter voron00
- Start date
Ok it just happened again. Immediatelly after the reboot i checked this file but it doesn't exist. Then I checked these other locations https://stackoverflow.com/questions/6071547/where-does-android-store-shutdown-logs, but only tombstone and dropbox folders exist and contained some files which you can find attached. I don't know if it's gonna be of any help but i couldn't find much more. Thanks again.
That file won't get created automatically. Follow the steps is section 3 in this tutorial:
https://forum.xda-developers.com/showthread.php?t=1520508
And attach the generated file here.
@voron00 no one reported such issue on carbon and I also don't have this issue, might be something from rom source side? (Note that I still have those extend system partitions commits)
Nitin
Last edited:
There is no last_kmsg file on first boot after SOD. It appears after next manual reboot for example.
Here is my dmesg, tombstones folder right after SOD and last_kmsg but after next manual reboot:
https://drive.google.com/folderview?id=1t3OOBKautnZmw3D4tqFFZmrV9BRzojc0
Also there is a problem with Play Market for me, it crashes very often. Here is 2 logcats, crashes at ~22:46 and ~22:55:
https://drive.google.com/folderview?id=1-0sN_U97OBj3f6mIe78CnKW7N7H4Q-DD
SOD happens again, and again can't generate last_kmsg on first boot. Any alternative ways to get useful info?
P.S. Похоже это происходит: "Для начала стоит отметить тот факт, что в большинстве случаев оперативная память Android устройства не очищается при рестарте SoC. Эту особенность использует механизм, который обеспечивает появление файла /proc/last_kmsg. Но порой для принудительного рестарта SoC приходится долго удерживать кнопку Power, что влечёт за собой либо полное, либо частичное изменение содержимого оперативной памяти. В данном случае я рекомендую подключать устройство к ПК через USB-кабель, что бы содержимое оперативной памяти не изменялось (по крайней мере на моём устройстве это работает)."
Here is my dmesg, tombstones folder right after SOD and last_kmsg but after next manual reboot:
https://drive.google.com/folderview?id=1t3OOBKautnZmw3D4tqFFZmrV9BRzojc0
Also there is a problem with Play Market for me, it crashes very often. Here is 2 logcats, crashes at ~22:46 and ~22:55:
https://drive.google.com/folderview?id=1-0sN_U97OBj3f6mIe78CnKW7N7H4Q-DD
SOD happens again, and again can't generate last_kmsg on first boot. Any alternative ways to get useful info?
P.S. Похоже это происходит: "Для начала стоит отметить тот факт, что в большинстве случаев оперативная память Android устройства не очищается при рестарте SoC. Эту особенность использует механизм, который обеспечивает появление файла /proc/last_kmsg. Но порой для принудительного рестарта SoC приходится долго удерживать кнопку Power, что влечёт за собой либо полное, либо частичное изменение содержимого оперативной памяти. В данном случае я рекомендую подключать устройство к ПК через USB-кабель, что бы содержимое оперативной памяти не изменялось (по крайней мере на моём устройстве это работает)."
Last edited:
Nothing useful in logs regarding SOD unfortunately, but seems like it can be caused by some apps? Because on clean system there is definitely no SOD. Need some time to test this ...
Last edited:
The first thing I noticed - notifications LED not blinking, it's glow constantly now
Thanks
, LED is ok now. Did you need any logs to track down Play Market crashes? It's still crashes for me on latest build.Play store crash is not related to rom i think, try to clear play store data or update to latest app version.Thanks
It seems that clearing data helps, no crashes so far, thanks. Overlaping text in VK app also gone, probably app related too.
SOD happened again on latest build, but still can't generate the last_kmsg. I didn't find a way to get data from the phone, when it in SOD. Touching the power button erases last_kmsg on boot.
Here is the list of installed apps (via >adb shell pm list packages)
I saw similar post from you on other threads also; why not read the recent posts? or even better flash the ROM and check them yourself?
Nitin
Last edited:
I found one more thing to add to SOD issue.
Maybe it's somehow connected to deep sleep of the device? That it doesn't wake up properly?
I usually install this app https://play.google.com/store/apps/details?id=com.franco.doze which just puts the device to deep sleep immediately when locked as opposed to default behaviour which is after few minutes of inactivity. And now i noticed that with this app in action the SOD happens much more often...
Maybe it's somehow connected to deep sleep of the device? That it doesn't wake up properly?
I usually install this app https://play.google.com/store/apps/details?id=com.franco.doze which just puts the device to deep sleep immediately when locked as opposed to default behaviour which is after few minutes of inactivity. And now i noticed that with this app in action the SOD happens much more often...
New build uploaded, please try this one for sod, i dropped all kernel patches except those that are needed from rom to work properly.
Some observation from me (build from 23/03)
I have Vkontakte app messenger and it uses LED for notifications by default. It has in app settings for LED. I have disabled these in app settings at 26/03 and where is no SOD's since then. This app still uses LED for notifications, but now it controlled by system. I have other apps, which uses LED but Vkontakte app uses LED on my phone more than other apps.
Not so much time has passed tho will stay at this build more
(build from 23/03)I have Vkontakte app messenger and it uses LED for notifications by default. It has in app settings for LED. I have disabled these in app settings at 26/03 and where is no SOD's since then. This app still uses LED for notifications, but now it controlled by system. I have other apps, which uses LED but Vkontakte app uses LED on my phone more than other apps.
Not so much time has passed tho
will stay at this build more
Last edited:
G
GuestD0639
Guest
So I was bored and decided to borrow a couple makos from a buddy, flashed a recent build, installed a bunch of apps and used them periodically. No SOD. Another guy I know gets the sleep of death on his mako regularly regardless of what ROM he's using - even stock. I've seen it first hand. Like others have said before I'm convinced it's a hardware issue. It's the luck of the LG manufacturing draw!
Aaaand get the SOD today, so didn't help. But i received a message in that timeframe (in VK app), so maybe it still related to app or LEDSome observation from me
I have Vkontakte app messenger and it uses LED for notifications by default. It has in app settings for LED. I have disabled these in app settings at 26/03 and where is no SOD's since then. This app still uses LED for notifications, but now it controlled by system. I have other apps, which uses LED but Vkontakte app uses LED on my phone more than other apps.
Not so much time has passed tho
New build with april security patches uploaded.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone