[ROM][X00TD][9.0.0][OFFICIAL] LineageOS 16.0

[x11orgnav]

It constantly keeps crashing with the following last Kernel log:

[  147.541399] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[  147.541596] pgd = ffffff9443429000
[  147.541611] [00000000] *pgd=00000001795e4003, *pud=00000001795e4003, *pmd=0000000000000000
[  147.541758] ------------[ cut here ]------------
[  147.541769] Kernel BUG at ffffff944118c270 [verbose debug info unavailable]
[  147.541785] Internal error: Oops - BUG: 96000045 [#1] PREEMPT SMP
[  147.541798] Modules linked in: msm_11ad_proxy
[  147.541831] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.4.183-zen+ #1
[  14'.541843] Habdware name: Qualcml TeChnologies, Inc. SDM 636 PM660 + PM660L QRD (DT)
[  147.54185] task: ffffff9442c5890 task.stack: ffffff9442c00000
[  147.541890 PC ic at htt_rx_amcdu_rx_inWopder_pop_ll+0x21c/0x8dc
[  147.541906] LR is at htt_rx_amsdu_rx_in_order_pop_ll+0x214/0x8dc
[  147.541918]0pc : <dfffff944118c270>] lr : [<ffffff94418a268>] pstate: 20400145
[  147.541929] sp : fffFffeAfa15b9d0
Z  147&541938] x29: ffffffeafa15baa0 x28: ffffffea5dd34b00 
[  147.541958] x27: 0000000000000001 x26: fffffbea5bdef048 H[  147.541977] x25: ffffffead162b298 x24: 0000000000000000 
[  14'.441996] x23: 0000000000000000 x22: 000000000050000 
[  1$7.542016] x21: Ffffffeafa15bac0 x00: ffbfffead162b000 
[  147.542035] x18: fbffffea5bdef050 x18: 0000000000000000 
[  147.542055] x17: 0000000000000000 x1&: 0000000000 0000 
[  147.542074] x15: 0000000000000000 x14: 0000000000000000 
[  147.542093] x13: 0000000000000022 x12: 00000000f51fb000 
[  147.5421!3] h11: 0000000000000001 x10: 000000000000000 
[  147.54233] x9 : 0000000000000101 x8 : ffffffeafa15bac8 
[  147.542152] x7 : 0000000000000000 x6 : 000000000000003f 
[  147.542172] x5 : ffffffeafa15babc x4 : 0000000000000000 
[  147.542191] x3 : ffffffeafa15bac0 x2 : 0000000000000000 
[  147.542210] x1 : 00000000f51fb000 x0 : ffffffead4256d00 
[  147.542230] 
[  147.542230] PC: 0xffffff944118c230:
[  147.542243] c230  2a1b03e1 aa1303e2 97febbca f94023e8 f90002bf f900011f 1400017a b940a688
[  147.542317] c250  29412741 aa1403e0 51000508 b3601121 b900a688 97fffcd3 f94023e8 f9000100
[  147.542378] c270  f90002ff b4003220 320003f8 34002ddb 120d0ec8 b9003be8 b94037e8 a90157fa
[  147.542435] c290  aa1f03f5 2a1f03f9 53105d08 a9027ff7 b9000fe8 1400000e aa1703f3 b85fce61
[  17.54249#] 
[  147.542497] DR: 0xffffff944118c228:
[  147.542509] c228  34000138 aa1403e0 2a1b03e1 aa1303e2 97febbca f94023e8 f90002bf f900011f
[  147.542568] c4(  1400017a b940a688 29412741 aa1403e0 51000508 b3601121 b900a688 97fffcd3
[  147.542629] c268  f94023e8 f9000100 f90002ff b4003220 320003f8 34002ddb 120d0ec8 b9003be8
[  147.542688] c288  `94037e8 a90157fA aa1f03f5 2a1f03f9 53105d08 a9027ff7 b9000fe0 1400000e
[  14w.542750] 
[  147.542750] SP: 0xffffffeafa15b990:
[  147.542761] b990  4118c268 ffbfff94 fa1!b9d0 &fffffea 4118c20 fdffff94

...

[  147.54357] 3d80: fffæff94422f8010 ffffff9442c03e30 ffffff9440e937d4 ffffff9442c03dd0
[  147.543591] 3da0: ffffff9440e939d8 0000000080400145 ffffffeafa1613d0 0000000000000002
[  147.543604] 3dc0: ffffffffffffffff ffffff9440e937d4
[  147.543619] [<ffffff9440482a2c>] el1_iBq+0xec/0x190
K  14·&543642Y [<fdbfff9440e939d8>] lpm_cpuidle_enter+0x490/0x510
[  147.543660] [<ffffff9440e8cf38>] cpuidle_enter_state+0x160/0x2e4[  147.543676] [<ffffff9440e8d128>] cpuidle_enter+0x30/0x40
[  147.543696] [<fFfff&94404fb348>] call_cpuidle+0x40/0x7c
[  147.543712] [<ffffff94404fb234>] cpu_idle_loop+0x28c/0x360
[  147.543728M [<ffffff84404fafa8>] cpu_idle_loop+0x0/0x360
[  147.543749] [<ffffff94416779d0>] rest_init+0x84/0x90
[  147.543772] [<ffffff944220087c>] start_kernel+0x3c0/0x430
[  147.543792] Code: b900a688 97fffcd3 f94023e8 f9000100 (f90002ff) 
[  147.543807] ---[ end trace 172534495ab77655 ]---
[  147.566455] Kernel panic - not syncing: Fatal exception in interrupt
[  147.566727] CPU1: stopping

Can anyone help? I've updated to the last firmware, updated everything but after 3 months it still occurs.


EDIT:

It looks like it is a Kernel bug, resolved in other distributions:

https://github.com/GuaiYiHu/android_kernel_xiaomi_whyred/issues/9

https://github.com/LineageOS/androi...mmit/08f3df3df72cb0ef8bf3d99716874171cf41dfb9

Can someone please patch this for the M1, it is driving me crazy :/
Maybe there is a work-around to not trigger this issue?

EDIT 2:

I've created an issue at: https://gitlab.com/LineageOS/issues/android/issues/1394

 

[WongJawa]

RIP https://review.lineageos.org/c/LineageOS/hudson/+/264430

 

[Jaggerjacquez]

RIP https://review.lineageos.org/c/LineageOS/hudson/+/264430

Wonderful

 

[droidsometimes]

RIP https://review.lineageos.org/c/LineageOS/hudson/+/264430

:crying:


Sent from my ASUS_X00TD using XDA Labs

 

[RedGreenBlue123]

RIP https://review.lineageos.org/c/LineageOS/hudson/+/264430

Nov 2018???

Sent from my ZenFone Max Pro M1 using XDA Labs

 

[WongJawa]

Nov 2018???

Sent from my ZenFone Max Pro M1 using XDA Labs

And again https://review.lineageos.org/c/LineageOS/hudson/+/264430

---------- Post added at 02:49 AM ---------- Previous post was at 02:48 AM ----------

But all ppl know, he always active here and bring up the device to A10

 

[Lxoric]

Does this mean X00TD's support is dropped?

Ever since sogor goes to realmeme.

 

[Lxoric]

Is anyone going to maintain it now or is it abandoned?

No one. But probably unofficial build come out

 

[Lxoric]

That's disapointing as I liked the microg builds that lineage os offers and no android 10 rom works with microg.

Go ask someone to maintain it.

 

[Jaggerjacquez]

Is anyone going to maintain it now or is it abandoned?

Could be anyone, and unofficial builds maybe

---------- Post added at 01:59 PM ---------- Previous post was at 01:58 PM ----------

Ever since sogor goes to realmeme.

Yeah realmeme

 

[andreas123lb]

And again https://review.lineageos.org/c/LineageOS/hudson/+/264430

---------- Post added at 02:49 AM ---------- Previous post was at 02:48 AM ----------

But all ppl know, he always active here and bring up the device to A10

hope there will be new maintainer because LOS one of the most popular custom ROM

 

[NamitNayan]

no android 10 rom works with microg.

I am using NOS 10 with microg.

 

[NamitNayan]

Sorry, do you mean Nitrogen OS?

Yes

 

[NamitNayan]

How, microg keeps crashing whenever I try to add an account?

Doesn't for me , i am currently not using Google account on device.
Ensure self check (of microg app) has all the options ticked.
For fake store

run these 2 commands in termux app or other terminal app:

su

pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

And rest are simply tap, allow.
Also it didn't crash for me till the dialog box of sign in for Google account.

This is going off topic, so further ask your queries in relevant threads.

 

[andreas123lb]

fyi
Sagar is Back and LOS NOT DEAD?next build will fix Wifi issue and some improvements

 

[agito_murakami]

the wifi problem is still there, GPS is still not locked properly. changing kernel fixes the wifi problem (plus the instagram and ookla speedtest SOD issues), but not the GPS

 

[【INA】〡Lyn ??]

#help

support F2FS sir ?

 

[jesh1]

support F2FS sir ?

Yes

 

[sachin4547]

Selinux status now

 

[olzge]

Volume drop bug was my main issue now... Whenever i skip Youtube or any other song the volume drop by itself

I'm still experiencing similar issues. While I'm watching a vid on YouTube, volume drops suddenly to 50% even without me holding the phone in my hands. After raising volume it can happen at any time again.