Samsung a30

[realartin]

Hi i dl all version of your android 11 arm 64 ab And i flashed on my samsung a305f It is amazing fast and responsive and i love it thank you The main issue is i haved randomly reboot s I try to flash other kernels but problem is still / steel here I use another build that they are using your build as the main build like havoc os but the problem ( rendom reboot ) is here Please fix it Tnx a lot.

[phhusson]

I have no Android 12...

[realartin]

Sorry i mean android 11 😣🥺

[phhusson]

That's using my AOSP GSI v300.m? Using STOCK UNMODIFIED OEM kernel and vendor? NO MAGISK

[realartin]

I try latest and stock oem unlocked (for installing the os) not change anything no magisk i have randomly reboot so then o try to test any thing else and i have the problem again and again

[phhusson]

Ok. Are the "random reboots" after 10 minutes every time? Are you running OEM's Android 10 as vendor?

Do you get logs in /sys/fs/pstore?

[realartin]

Yes random reboot some time after 10 minutes some time after 20 some time after 30 sec Yes latest android 10 stock Original oem I don't have logs for yours , but i have logs for havoc that's help ? I can install yours now and take logs I have this issue sense android 11 gsi yours and others they are using yours , but your 10 gsi is great and no problem even with kernel costume and magisk

[phhusson]

I want logs on my GSI, yes.

Do you get random reboots if you don't touch the phone at all? Maybe let it boot, and start a youtube video, but nothing else, and let it keep running.

Le mar. 23 févr. 2021 à 10:41, realartin notifications@github.com a écrit :

Yes random reboot some time after 10 minutes some time after 20 some time after 30 sec Yes latest android 10 stock Original oem I don't have logs for yours , but i have logs for havoc that's help ? I cam install yours now and take logs I have this issue sense android 11 gsi yours and others they are using yours , but your 10 gsi is great and no problem even with kernel costume and magisk

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784039979, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OX55JMU44N7V5HTCJLTANZ3BANCNFSM4YCDHQBA .

[realartin]

Ok So now i back up my stock rom , then fresh insatll yours then let play your tube and i dont do any thing and i dont install andy kernel and any magisk and then if crashed (absolutely 🥺😟) i take log after reboot For taking log i can use system log from google store or you give me local address ? I mean i need to do anything for taking logs or it's there? (Where) Tnx best regards

[phhusson]

You need to grab logs from /sys/fs/pstore NOT FROM LOGCAT

Le mar. 23 févr. 2021 à 10:46, realartin notifications@github.com a écrit :

Ok So now i back up my stock rom , then fresh insatll yours then let play your tube and i dont do any thing and i dont install andy kernel and any magisk and then if crashed (absolutely 🥺😟) i take log after reboot For taking log i can use system log from google store or you give me local address ? I mean i need to do anything for taking logs or it's there? (Where) Tnx best regards

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784043001, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OXTJBIQN47KBZYT7ATTAN2PPANCNFSM4YCDHQBA .

[realartin]

hi , random reboot again https://drive.google.com/file/d/1UY8L3MWyHzNaW_kj0LEpivxyivII48wp/view?usp=sharing

[realartin]

hi is log right? what is the problem?

[phhusson]

Humpf thanks Samsung, this log is way too short. You need to grab /proc/last_kmsg

Le mar. 23 févr. 2021 à 12:37, realartin notifications@github.com a écrit :

hi is log right? what is the problem?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784139022, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OVGG7A2YMC2NSWXHVDTAOHPZANCNFSM4YCDHQBA .

[phhusson]

last_kmsg attached in private.

Issue found in last_kmsg is: <0>[ 1008.611502] I[3: swapper/3: 0] Kernel panic - not syncing: Software Watchdog Timer expired 1000s

@realartin are you really sure that the device doesn't simply always reboot after 16 minutes and nothing else?

[realartin]

what do you mean?

[realartin]

yes always reboot , about timing idk but alwayse reboot (hard reboot) and nothing else every thing works fine

[realartin]

how to solve it? there is any way to solve this issue or like this for havoc that based on yours too? tnx alot i know you r busy send me tips i follow them and make it right best regard

[realartin]

<0>[ 1008.611502] I[3: swapper/3: 0] Kernel panic - not syncing: Software Watchdog Timer expired 1000s <0>[ 1008.611521] I[3: swapper/3: 0] s3c2410_wdt: watchdog reset is started to 30secs <6>[ 1008.611543] I[3: swapper/3: 0] s3c2410-wdt 10060000.watchdog: s3c2410wdt_set_heartbeat: timeout=30, divisor=93, count=6093750 (0000fff5) <6>[ 1008.611564] I[3: swapper/3: 0] s3c2410-wdt 10060000.watchdog: Watchdog stop done, WTCON = 5c18 <6>[ 1008.611584] I[3: swapper/3: 0] s3c2410-wdt 10060000.watchdog: Watchdog start, WTCON = 5c39 <4>[ 1008.611617] I[3: swapper/3: 0] CPU: 3 MPIDR: 80000103 PID: 0 Comm: swapper/3 Tainted: G W 4.4.241-Eureka_R5.0_A305_P/Q/R #1 <4>[ 1008.611628] I[3: swapper/3: 0] Hardware name: Samsung A30 KOR SINGLE 02 board based on EXYNOS7904 (DT) <4>[ 1008.611639] I[3: swapper/3: 0] Call trace:

[realartin]

why eureka kernel is here ? i clear data full clear every thing and install phhh >? what?

[phhusson]

Did you flash stock unmodified oem boot.img again?

Le mar. 23 févr. 2021 à 13:40, realartin notifications@github.com a écrit :

why eureka kernel is here ? i clear data full clear every thing and install phhh >? what?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784172674, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OSFUFHRUG4LDVW333TTAOO2JANCNFSM4YCDHQBA .

[realartin]

no i just do : clear data / yes > clear cache art cache system data then install phhh

[phhusson]

So, when you answered to my second message: https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784035834

You lied?

[realartin]

no men i think that is fresh install

[realartin]

in every toturial said this is fresh install

[realartin]

so i need to flash stock rom again ?

[phhusson]

You flashed full stock rom from odin before flashing GSI?

[realartin]

no i clear data from twrp / in every toturail said that .... then flashed this gsi or others

[realartin]

clear data : type : yes clear cache system

[phhusson]

yes flash stock rom. Wiping data will not remove the custom kernel you would have installed.

[realartin]

https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ i use this tutorail

[realartin]

sorry, i try it and i will tell you the result tnx for your time sir

[phhusson]

This tutorial assumes you are running stock oem unmodified rom Which is litteraly the first thing I asked you.

[realartin]

idk that so sorry

[realartin]

if i flash the stock booot image that would help or i need to fully flash stock rom?

[realartin]

no problem i fully flashed stock

[phhusson]

It depends on what you changed. You can start with just boot image.

23 févr. 2021 13:58:10 realartin notifications@github.com:

if i flash the stock booot image that would help or i need to fully flash stock rom?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub[https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784182765], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAA4OT6DQ3IZG6GISGIYUTTAOQ6FANCNFSM4YCDHQBA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][https://github.com/notifications/beacon/AAAA4OVUUHSL4SEZWS2BMMTTAOQ6FA5CNFSM4YCDHQBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF26233I.gif]

[ponces]

Most likely this is the same issue I had here A40 and A30 share the same kernel - Exynos 7904 This is Samsung's fault...

[phhusson]

It can hardly be Samsung's fault considering it works on Android 10.

Le mar. 23 févr. 2021 à 14:02, Alberto Ponces notifications@github.com a écrit :

Most likely this is the same issue I had here https://github.com/phhusson/treble_experimentations/issues/1511 A40 and A30 share the same kernel - Exynos 7904 This is Samsung's fault...

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1730#issuecomment-784185214, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OVEMQ4NVM2K5TLSNYTTAOROJANCNFSM4YCDHQBA .

[realartin]

so i flash the stock rom ok? so now i install twrp then phh gsi ok then your saying is samsung fault so then need to flash another kernel ? or not

[ponces]

Sorry, keep going with phhusson's request. Don't mind my comment

[realartin]

ok i will go with dave sure sorry for your time and tnx

[ponces]

It can hardly be Samsung's fault considering it works on Android 10. Le mar. 23 févr. 2021 à 14:02, Alberto Ponces notifications@github.com a écrit : … Most likely this is the same issue I had here <#1511> A40 and A30 share the same kernel - Exynos 7904 This is Samsung's fault... — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1730 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OVEMQ4NVM2K5TLSNYTTAOROJANCNFSM4YCDHQBA .

So, is this AOSP's fault? Weird that it only affects these two devices that share the same kernel. Or do you had reports of the same issue on another device? I believe you have a Samsung S9, right? Do you have this issue?

[phhusson]

I've had many reports of such issue on various Samsung devices, and it was always using "something" else, and flashing back to original fixed it, except in your case.

[realartin]

so there is hope ... if yours would be ok then that mean i was wrong about freash install , good old time with s3 you need to just flash rom.zip and there is no need to this things m but i want to say thank you for your hard work men :)

[ponces]

The thing is: i'm not using a completely stock kernel version. The version that I'm using has Samsung securities disabled (mandatory for booting TWRP) and a small change in the MTP drivers to be able to use it with your GSI. Without this change, Samsung MTP drivers will be considered which are not compatible with AOSP. Most likely, by flashing the stock boot this issue would be fixed but I would not be able to boot TWRP nor use MTP.

[realartin]

if it's not i need to dl linux base like ubuntu and create my costume kernel without samsung security or disabling kernel panic idk ?

[realartin]

The thing is: i'm not using a completely stock kernel version. The version that I'm using has Samsung securities disabled (mandatory for booting TWRP) and a small change in the MTP drivers to be able to use it with your GSI. Without this change, Samsung MTP drivers will be considered which are not compatible with AOSP. Most likely, by flashing the stock boot this issue would be fixed but I would not be able to boot TWRP nor use MTP.

if i had the issue i can flash this ?> phh please answer

[ponces]

The thing is: i'm not using a completely stock kernel version. The version that I'm using has Samsung securities disabled (mandatory for booting TWRP) and a small change in the MTP drivers to be able to use it with your GSI. Without this change, Samsung MTP drivers will be considered which are not compatible with AOSP. Most likely, by flashing the stock boot this issue would be fixed but I would not be able to boot TWRP nor use MTP.

if i had the issue i can flash this ?> phh please answer

Proceed with flashing stock boot! This is my recommendation! The kernel source is not exactly the same, the defconfigs have a few differences between a30 and a40. So if the recommended step does not work, then, yes, you will need something similar to my solution but applied for a30.

[realartin]

tnx

[realartin]

now i flashed stock firmware then twrp then wipe data .../ now phh gsi v300m installed now is booting ... let see what happen

[phhusson]

Okay I better understand the issue now, and what @ponces kernel change did.

There are two competing watchdogs. In this log, the hardware watchdog is properly reset every 100s, but the software watchdog is triggered, but never reset.

@ponces 's kernel disables hardware watchdog, which was previously working so not the cause of the issue. My guess is that disabling hardware watchdog means watchdogd can reset only one watchdog at a time.

My guess is that original kernel doesn't have soft watchdog enabled, only hardware.

Please send me your /vendor/etc/init/init.samsung.bsp.rc and /proc/config.gz