[ROM][BETA][10.x] LineageOS 17.1 [clover / MiPad4/ MiPad4 Plus]

marcus.zheng

Member
Feb 14, 2009
46
1
0
Melbourne
I have been using Havoc-OS v2.8 for a while and thinking to switch to the latest LineageOS since I had really good experience with it in the pass.
It didn't let me down this time either. I flashed this ROM + Gapp Micro. The initial start-up/setup process was surprising quick and smooth.
I've been only using it for less than 24 hours and I'm already impressed with this ROM.
Everything is a lot smoother and snappier than Havoc-OS, gesture mode is really easy to use the responsive
Video play back was great, flawless Bluetooth connection.
My only very minor problem is the Trebuchet Launcher which you can set the grid size...and tap to sleep did not work, tap to wake works though
I will give 9.8/10 to this ROM so far
 

AntoRei

Senior Member
Jun 8, 2016
180
24
0
I'm using Los 17 for two days and i find it perfect. Everything works to perfection, it is also smooth and fast. I hope that very soon will be possible to use third-party launcher with Android 10 gestures. Thanks to developer for your work!
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,729
0
Lineage 17.0 ROM Testing (Personal Build)

Hello all,

My Kindle Fire HDX (https://en.wikipedia.org/wiki/Fire_HDX) has grown quite old (2013), so I started looking for a replacement a few months ago. After some research, I came across the Xiaomi Mi Pad 4 which has very nice technical specifications. I decided to give it a try and ordered a "test" device (8" wifi-only) about 3 weeks ago. It was delivered yesterday.

We should all thank @rcstar6696 and the rest of the contributors at https://github.com/xiaomi-sdm660 as the work they have done for this device is EXCELLENT. I was easily able to check out the sources and run my own test build of this ROM.

This afternoon, I flashed my personal userdebug build signed with public keys which has selinux disabled.

My process went like this:
  1. The device came with MIUI 10.3.1 installed and was already bootloader unlocked
  2. Downloaded the TWRP.img linked in this post (twrp_clover-3.3.1.img) as well as the BETA Gapps for Android 10.
  3. Downloaded the last MIUI v10 build from Xiaomi.Eu (Built 2019-08-30ish):
    https://sourceforge.net/projects/xi...i.eu_multi_MIPAD4_9.8.29_v10-8.1.zip/download
  4. Entered fastboot and `fastboot boot twrp_clover-3.3.1.img` to enter TWRP (didn't flash recovery yet)
  5. Placed the newest MIUI on the internal storage and flashed the update. I did this to make sure my bootloader and firmwares were as new as they could be. From here on out, I don't expect Xiaomi to provide any further updates for this device.
  6. Rebooted the device afterward to make sure everything booted
  7. Entered fastboot again and `fastboot boot twrp_clover-3.3.1.img` to enter TWRP (still didn't flash recovery yet)
  8. Made a backup of everything and moved it to my local HD (important to have these: mostly for the persist backup)
  9. Rebooted back to bootloader and flashed recovery this time: `fastboot flash recovery twrp_clover-3.3.1.img` and `fastboot reboot` while holding the Volume Up button to enter recovery.
  10. In TWRP, I placed my build of Lineage 17.0 and the BETA Gapps.zip on the internal storage and flashed them.
  11. I then wiped the device and rebooted

In general, Lineage 17.0 runs extremely well on the Mi Pad 4. Clearly there are a few failures below, but most have nothing to do with the ROM (GApps or SELinux disabled issues). Here is an itemized breakdown of my testing:

In the middle column
P == PASS
F == FAIL


Code:
[ROM TESTING - LINEAGE 17.0 2019-10-31 - selinux disabled - public key signed]

GPU           :P: [APP] 3D Mark: Sling Shot (Std) OpenGL ES 3.1 / Vulkan : 2074 stock : 2034 Lineage 17.0
LCD           :P: Visual
BACKLIGHT     :P: Visual
TOUCH         :P: [APP] Multi Touch Test
PWR BUTTON    :P: Manual Test
VOL BUTTONS   :P: Manual Test
CAMERA[F]/PIC :P: Camera
CAMERA[F]/VID :*: Camera
CAMERA[B]/PIC :P: Camera
CAMERA[B]/VID :P: Camera
ROTATION      :P: Rotate
SPEAKERS      :P: Audio Test
HEADPHONES    :P: Audio Test
MICROPHONE    :P: Audio Test
ACCEL         :P: Sensor Box for Android
GYRO          :P: Sensor Box for Android
ALSPS         :P: Sensor Box for Android
HALL SENSOR   :P: Cover Open / Close
USB OTG       :P: USB Thumbdrive
WIFI          :P: 2.4Ghz / 5.0 Ghz
WIFI/GPS      :P: [APP] Google Maps
WIFI DISPLAY  :F: Settings -> Display -> Cast Screen
BLUETOOTH     :P: Pair Headphones / Speaker (Audio Profile)
BATTERY       :?: Screen OFF / Wifi ON / 4 hours : Less than 1% drop (~5% day)
ENCRYPTION    :?: Settings -> Security -> Encrypt Device
SAFETY NET    :F: [APP] SafetyNet Checker (selinux/ CTS profile fail)
SCREEN RECORD :F: System Test
PLAY MOVIES   :P: [APP] Google Play Movies
YOUTUBE 4K    :P: [APP] 4K Video : Sony 4K Demo [Settings -> Quality -> 2160p]
NETFLIX       :F: [APP] Movie (selinux disabled means the app won't show in Play Store)
HBO NOW       :P: [APP] Movie
[NOTES]

personal build: public keys
selinux: disabled
BETA Gapps used: Android 10 "full" size 10/6

Launcher issues:
- Pixel Launcher Crashed -- probably beta GApps

Camera issues:
- There are 2 camera apps in my build: com.android.camera and com.android.camera2

com.android.camera application:
- Recorded Front Camera "Short Video" then app crashed when toggling to Rear Cam (Wasn't able to duplicate)
- No audio recorded from Front Camera "Short Video" for my first try (Wasn't able to duplicate)
- Front Camera video is very squashed after my first video recorded
- Setting Video to 720p manually every time before recording video fixes format aspect ratio.
(If you see close zoom of face it will record incorrectly)

com.android.camera2 application:
- Things worked a bit better but didn't spend as much time changing settings

screen recorder:
- Hung / crashed the device

youtube 4k viewing:
- Limited to 1080p view (which seems oddly correct vs. 2160p limit on stock)

I will perform more rebuilds enabling SELinux and custom signing keys as well as experimenting with the fingerprint info that is current in the clover repo (it's for Wayne device) and post my results.

- Hash
 

stangri

Senior Member
Dec 19, 2009
1,144
823
133
Burnaby
Hello all,

My Kindle Fire HDX (https://en.wikipedia.org/wiki/Fire_HDX) has grown quite old (2013), so I started looking for a replacement a few months ago. After some research, I came across the Xiaomi Mi Pad 4 which has very nice technical specifications. =
- Hash
Hello Hash, your and ggow's contributions to LineageOS for Fire HDX will not be forgotten. If it wasn't for the stupid micro-USB charging port, I would still have been using it today. Welcome to the clover-field. ;)
 
  • Like
Reactions: Hashcode

rcstar6696

Senior Member
Dec 21, 2013
2,468
8,469
0
Kassel (Hessen)
Hello all,

My Kindle Fire HDX (https://en.wikipedia.org/wiki/Fire_HDX) has grown quite old (2013), so I started looking for a replacement a few months ago. After some research, I came across the Xiaomi Mi Pad 4 which has very nice technical specifications. I decided to give it a try and ordered a "test" device (8" wifi-only) about 3 weeks ago. It was delivered yesterday.

We should all thank @rcstar6696 and the rest of the contributors at https://github.com/xiaomi-sdm660 as the work they have done for this device is EXCELLENT. I was easily able to check out the sources and run my own test build of this ROM.

This afternoon, I flashed my personal userdebug build signed with public keys which has selinux disabled.

My process went like this:
  1. The device came with MIUI 10.3.1 installed and was already bootloader unlocked
  2. Downloaded the TWRP.img linked in this post (twrp_clover-3.3.1.img) as well as the BETA Gapps for Android 10.
  3. Downloaded the last MIUI v10 build from Xiaomi.Eu (Built 2019-08-30ish):
    https://sourceforge.net/projects/xi...i.eu_multi_MIPAD4_9.8.29_v10-8.1.zip/download
  4. Entered fastboot and `fastboot boot twrp_clover-3.3.1.img` to enter TWRP (didn't flash recovery yet)
  5. Placed the newest MIUI on the internal storage and flashed the update. I did this to make sure my bootloader and firmwares were as new as they could be. From here on out, I don't expect Xiaomi to provide any further updates for this device.
  6. Rebooted the device afterward to make sure everything booted
  7. Entered fastboot again and `fastboot boot twrp_clover-3.3.1.img` to enter TWRP (still didn't flash recovery yet)
  8. Made a backup of everything and moved it to my local HD (important to have these: mostly for the persist backup)
  9. Rebooted back to bootloader and flashed recovery this time: `fastboot flash recovery twrp_clover-3.3.1.img` and `fastboot reboot` while holding the Volume Up button to enter recovery.
  10. In TWRP, I placed my build of Lineage 17.0 and the BETA Gapps.zip on the internal storage and flashed them.
  11. I then wiped the device and rebooted

In general, Lineage 17.0 runs extremely well on the Mi Pad 4. Clearly there are a few failures below, but most have nothing to do with the ROM (GApps or SELinux disabled issues). Here is an itemized breakdown of my testing:

In the middle column
P == PASS
F == FAIL


Code:
[ROM TESTING - LINEAGE 17.0 2019-10-31 - selinux disabled - public key signed]

GPU           :P: [APP] 3D Mark: Sling Shot (Std) OpenGL ES 3.1 / Vulkan : 2074 stock : 2034 Lineage 17.0
LCD           :P: Visual
BACKLIGHT     :P: Visual
TOUCH         :P: [APP] Multi Touch Test
PWR BUTTON    :P: Manual Test
VOL BUTTONS   :P: Manual Test
CAMERA[F]/PIC :P: Camera
CAMERA[F]/VID :*: Camera
CAMERA[B]/PIC :P: Camera
CAMERA[B]/VID :P: Camera
ROTATION      :P: Rotate
SPEAKERS      :P: Audio Test
HEADPHONES    :P: Audio Test
MICROPHONE    :P: Audio Test
ACCEL         :P: Sensor Box for Android
GYRO          :P: Sensor Box for Android
ALSPS         :P: Sensor Box for Android
HALL SENSOR   :P: Cover Open / Close
USB OTG       :P: USB Thumbdrive
WIFI          :P: 2.4Ghz / 5.0 Ghz
WIFI/GPS      :P: [APP] Google Maps
WIFI DISPLAY  :F: Settings -> Display -> Cast Screen
BLUETOOTH     :P: Pair Headphones / Speaker (Audio Profile)
BATTERY       :?: Screen OFF / Wifi ON / 4 hours : Less than 1% drop (~5% day)
ENCRYPTION    :?: Settings -> Security -> Encrypt Device
SAFETY NET    :F: [APP] SafetyNet Checker (selinux/ CTS profile fail)
SCREEN RECORD :F: System Test
PLAY MOVIES   :P: [APP] Google Play Movies
YOUTUBE 4K    :P: [APP] 4K Video : Sony 4K Demo [Settings -> Quality -> 2160p]
NETFLIX       :F: [APP] Movie (selinux disabled means the app won't show in Play Store)
HBO NOW       :P: [APP] Movie
[NOTES]

personal build: public keys
selinux: disabled
BETA Gapps used: Android 10 "full" size 10/6

Launcher issues:
- Pixel Launcher Crashed -- probably beta GApps

Camera issues:
- There are 2 camera apps in my build: com.android.camera and com.android.camera2

com.android.camera application:
- Recorded Front Camera "Short Video" then app crashed when toggling to Rear Cam (Wasn't able to duplicate)
- No audio recorded from Front Camera "Short Video" for my first try (Wasn't able to duplicate)
- Front Camera video is very squashed after my first video recorded
- Setting Video to 720p manually every time before recording video fixes format aspect ratio.
(If you see close zoom of face it will record incorrectly)

com.android.camera2 application:
- Things worked a bit better but didn't spend as much time changing settings

screen recorder:
- Hung / crashed the device

youtube 4k viewing:
- Limited to 1080p view (which seems oddly correct vs. 2160p limit on stock)

I will perform more rebuilds enabling SELinux and custom signing keys as well as experimenting with the fingerprint info that is current in the clover repo (it's for Wayne device) and post my results.

- Hash
Thx for the review :)
We have 2 camera because i added miui camera and snap camera from lineage. So i think two camera apps are not an issue.

About your camera issues. This is a modded miui cam to work on 10 so i was already excepting not everything will be fine.

Screenrecoder is known and work in progess by lineage guys

About youtube. I will take a look never noticed it ;)

Selinux is not disabeld its just set to permissive which is normal at this stage i guess only a handfull device are useing enforcing in 10 yet.

About fingerprint we use wayne fingerprint because clover is not certified android device. So we have to use other one. But due the restrictions google introduced not even this seems possible atm. Noe fingeprint must match security patch. So we need to use diffrent fingerprint in future. Question is which one
 
  • Like
Reactions: tombassi

rcstar6696

Senior Member
Dec 21, 2013
2,468
8,469
0
Kassel (Hessen)
##### Android 10 Beta Lineage Build #####

Xiaomi Mi PAD 4 (clover) Update 01-11-2019

Maintainer: @rcstar6696

Device Changelog:
• Updated Kernel to last CAF Release
• Updated Wifi Driver to last CAF Release
• Updated Qcom Configs from LA.UM.8.2.r1-04800
• Unified some Vendor Blobs
• Updated Kernel to 4.4.198
• Fixed Ui Lag after some days
• Added Snapcamera
• Updated Round Corner Configuration
• Set default Wifi country code (5Ghz for all)
• Fixed Encyrption
• Minor Improvements and Cleanup

Download Link: https://mega.nz/#!eRInXaYR!CxbXcS9cmydh7I7t3JCLd7CDStBFQWPuLlwoOZKx03U

Recommand TWRP: https://mega.nz/#!CQQRwSAL!VX34bYDiiZCfYAIE03ZhIfkhxyx7-fb1wm1rI6abVek

Only Magisk higher than 19.5 supported

Note: Don't except that everything is working smooth and perfect. All is Work in Progess. Keep that in mind and not officialy released by Lineage

The Build contains no Gapps. Gapps have be installed again.
 

rcstar6696

Senior Member
Dec 21, 2013
2,468
8,469
0
Kassel (Hessen)
Yep, me too, but I think these things are to be expected, it's still beta ?
For some reason I am getting much worse internet speed over wifi compared to havoc on Android 9.
Not directly a problem for android Q its Caf problem in kernel. The used kernel is based on Q tag and the wifi driver seems not working properly yet. I assume it will be fixed by caf in future releases. We already invastigate that.
 
  • Like
Reactions: ferhad.necef

mfkomega

Member
Nov 21, 2015
41
32
0
Awesome ROM, many thanks.

I have a question anyway, maybe @rcstar6696 can answer this.
My MiPad does not support multiple USB-OTG connections at the same time, e.g. charging and streaming music via USB while connected with an USB-OTG Hub.
Do you know if this is a hardware or kernel/software related issue?
My Galaxy S9 is supporting multiple USB connections with a USB-OTG Hub.

Many thanks
 
  • Like
Reactions: S-trace