This one will.
I'll merge 04200 and released ASB tag for mido tomorrow.
MoeSyndrome-vanilla-mido-20200418-1448.zip
13 MB
New #mido test build with branch lineage-17.1 at commit 1da71807e217 ("Merge remote-tracking branch 'kp/msm-3.18/LA.UM.8.6.r1/master' into lineage-17.1").
AIM-System-V4.0-Official-mido-20200420-0602 zip (vanilla variant)
- Merged latest zeelog's changes
- AIM source sync
- RSSNR signal level ignored
- Removed unused camera firmwares
- MoeSyndrome Kernel (Vanilla) updated to
Face Unlock is no longer available due to removal request from Motorola Mobility.
- Merged latest zeelog's changes
- AIM source sync
- RSSNR signal level ignored
- Removed unused camera firmwares
- MoeSyndrome Kernel (Vanilla) updated to
g1da71807e217Face Unlock is no longer available due to removal request from Motorola Mobility.
KudProject | CI Builds pinned «AIM-System-V4.0-Official-mido-20200420-0602 zip (vanilla variant) - Merged latest zeelog's changes - AIM source sync - RSSNR signal level ignored - Removed unused camera firmwares - MoeSyndrome Kernel (Vanilla) updated to g1da71807e217 Face Unlock is no…»
KudProject | CI Builds
AIM-System-V4.0-Official-mido-20200420-0602 zip (vanilla variant) - Merged latest zeelog's changes - AIM source sync - RSSNR signal level ignored - Removed unused camera firmwares - MoeSyndrome Kernel (Vanilla) updated to g1da71807e217 Face Unlock is no…
AIM-System-V4.0-Official-mido-20200421-0825.zip (vanilla variant)
- ZeeLog's changes reverted to as of 2 April 2020
- Reverted SDM blobs to LA.UM.8.6.r1-03400-89xx.0 (breaks LiveDisplay)
My builds will only sync with ZeeLog changes if they remain for 14 days without any single force pushes (stability reasons); though they've to always been double-checked because there'll still be issues to be ironed out.
For all ROM source-related issues, redirect all your blame to @SeekNDstroy. Kthxbye.
- ZeeLog's changes reverted to as of 2 April 2020
- Reverted SDM blobs to LA.UM.8.6.r1-03400-89xx.0 (breaks LiveDisplay)
My builds will only sync with ZeeLog changes if they remain for 14 days without any single force pushes (stability reasons); though they've to always been double-checked because there'll still be issues to be ironed out.
For all ROM source-related issues, redirect all your blame to @SeekNDstroy. Kthxbye.
MoeSyndrome-vanilla-mido-20200427-0250.zip
13 MB
New #mido test build with branch lineage-17.1 at commit 82d6ed31b1c4 ("mido: defconfig: Regenerate to remove prima config features").
Forwarded from KudProject Updates (Archived)
Yes, I just noticed that you can't flash latest vanilla zip on unrooted mido otherwise you'll get System has been destroyed message.
This is the last build that'll work just fine for non-rooted users. Underlying problem has been reverted and it'd be fixed on next CI build.
This is the last build that'll work just fine for non-rooted users. Underlying problem has been reverted and it'd be fixed on next CI build.
Telegram
KudProject | #WorkFromHome
New #mido test build with branch lineage-17.1 at commit e985788613cf ("Merge remote-tracking branch 'kp/msm-3.18/LA.UM.8.6.r1/master' into lineage-17.1").
MoeSyndrome-vanilla-mido-20200502-1344.zip
12.3 MB
New #mido test build with branch lineage-17.1 at commit 82d6ed31b1c4f ("mido: defconfig: Regenerate to remove prima config features").
KudProject | CI Builds
MoeSyndrome-vanilla-mido-20200502-1344.zip
This build should flash and boot just fine for non-Magisk users.
Forwarded from KudProject Updates (Archived)
2 May 2020 update:
As I mentioned before, a new vanilla build has been pushed to CI and release, reverted a change on installation behavior that breaks booting for non-Magisk users.
Even though the SCM version changes on today's build, there's essentially no other changes being made on kernel's side, so Magisk users running previous kernel build can ignore this update. Sorry for any inconvenience caused by previous 2 release builds.
To act as a reminder, release build is always signed with my release key.
As I mentioned before, a new vanilla build has been pushed to CI and release, reverted a change on installation behavior that breaks booting for non-Magisk users.
Even though the SCM version changes on today's build, there's essentially no other changes being made on kernel's side, so Magisk users running previous kernel build can ignore this update. Sorry for any inconvenience caused by previous 2 release builds.
To act as a reminder, release build is always signed with my release key.
twrp-3.3.1-2-KudProject-mido.img
22.2 MB
#mido: ROM with msm-4.9 kernel soon(tm). This recovery is required to flash such ROMs.
MoeSyndrome-vanilla-mido-20200504-2056.zip
12.4 MB
New #mido test build with branch lineage-17.1 at commit e4c45aed15a38 ("mido: input/touchscreen: Update kernfs_path usage for 4.9").
KudProject | CI Builds
MoeSyndrome-vanilla-mido-20200504-2056.zip
From this build onwards for mido, are 4.9 kernel.
MoeSyndrome-vanilla-mido-20200505-0045.zip
12.4 MB
New #mido test build with branch lineage-17.1 at commit d00c98750f7e3 ("FIXME: msm: ipa_uc: Don't panic on error type IPA_HW_ERROR_NONE").
MoeSyndrome-vanilla-mido-20200505-1624.zip
12.4 MB
New #mido test build with branch lineage-17.1 at commit dda6d0ca3f4e6 ("FIXME: msm: ipa: Avoid overusing BUG()").
👍1
KudProject | CI Builds
MoeSyndrome-vanilla-mido-20200505-1624.zip
- Fixed bootanimation display bug
- IPA driver sucks
- IPA driver sucks
MoeSyndrome-vanilla-mido-20200507-1504.zip
12.4 MB
New #mido test build with branch lineage-17.1 at commit 37e9d494e6087 ("FIXME: ARM64/dts: mido: Disable VADC support").
MoeSyndrome-vanilla-mido-3.18-20200513-1717.zip
12.2 MB
New #mido test build (3.18) with branch lineage-17.1 at commit 768eaee7515f4 ("fingerprint: goodix_mido: Update indentations to fix compiler warnings").