• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

LineageOS 19.0 [S] [12] (Unofficial) Mi Pad 4 Plus (clover)

Search This thread

crypticc

Senior Member
Aug 22, 2009
1,138
121
London
I decided to try this on my Xiaomi Mipad 4 as they have basically same hardward (Clover but 7" WiFi not the large-screen plus version)

ROM: lineage-19.0-20211119-UNOFFICIAL-clover
GAPPS: NikGapps-omni-arm64-12-20211018-signed
Clean install

Booted okay and after adding login details it's now recovering my apps from google backup. Google discovery that you get by swiping the homescreen from left to right is empty (edit : got it working just by doing a single search from the google-address bar. The discovery page the started working okay)


Left Pull-down menu looks sized for a telephone but I can live with that. however, many of the other menus and popups are only half-width. e.g. the aforementioned Google-Discovery/Google Home pages.

I'll update here once app installations and updates done, and again after a few days.

thanks @saber_op
 
Last edited:

crypticc

Senior Member
Aug 22, 2009
1,138
121
London
Hi - brief update. Google location services is the main service which I can see is not behaving crashes. e.g. Google Maps can't find location. If this is because I'm running Mi Pad 4+ rom on Mi Pad 4 then just say and I'll go back in my box.

Subset of logcat below

Code:
11-21 21:59:29.754 20822 20893 I DynamiteModule: Considering local module com.google.android.gms.providerinstaller.dynamite:1 and remote module com.google.android.gms.providerinstaller.dynamite:0
11-21 21:59:29.754 20822 20893 I DynamiteModule: Selected local version of com.google.android.gms.providerinstaller.dynamite
11-21 21:59:29.766 20822 20893 I NetworkManagementSocketTagger: tagSocketFd(-1, 805307399, -1) failed with errno-9
11-21 21:59:29.767 20822 20822 W SystemServiceRegistry: No service published for: contexthub
11-21 21:59:29.769   682   725 E BpfUtils: Failed to get socket cookie: Protocol not available
11-21 21:59:29.769 20822 20893 I NetworkManagementSocketTagger: tagSocketFd(116, 805307399, -1) failed with errno-9
11-21 21:59:29.802 20822 20822 E inertial-anchor: Requested sensor:14 and fallback sensor: 2 are both unavailable.
11-21 21:59:29.802 20822 20822 E inertial-anchor: Requested sensor:14 and fallback sensor: 2 are both unavailable.
11-21 21:59:29.817 20822 20822 D CompatibilityChangeReporter: Compat change id reported: 148180766; UID 10059; state: ENABLED
11-21 21:59:29.870 20822 20822 W SystemServiceRegistry: No service published for: contexthub
11-21 21:59:29.875 20822 20822 E NanoAppLogging: Failed to begin contexthub communication
11-21 21:59:29.878 20822 20822 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
11-21 21:59:29.884  1481  1503 I ServiceWatcher: [GeofenceProxy] connected to {com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService}
11-21 21:59:29.931 20822 20893 E AlarmManager: Failed to set alarm
11-21 21:59:29.931 20822 20893 E AlarmManager: java.lang.SecurityException: Caller com.google.android.gms needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.os.Parcel.createException(Parcel.java:2409)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2392)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2334)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:359)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:947)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:907)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at android.app.AlarmManager.setExactAndAllowWhileIdle(AlarmManager.java:1175)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at pwk.i(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at wwd.c(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at wwc.g(:[email protected]@21.42.18 (190400-410302452):6)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at com.google.android.gms.gcm.connection.HeartbeatChimeraAlarm.h(:[email protected]@21.42.18 (190400-410302452):7)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at wwl.J(:[email protected]@21.42.18 (190400-410302452):25)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at wwl.E(:[email protected]@21.42.18 (190400-410302452):118)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at wwj.run(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:29.931 20822 20893 E AlarmManager:  at java.lang.Thread.run(Thread.java:920)
11-21 21:59:29.944 20822 20822 I Fido    : [CableAuthenticatorChimeraService] Registering broadcast receiver.
11-21 21:59:29.965 20822 20822 I Thunderbird: starting outgoing sms listener [CONTEXT service_id=226 ]
11-21 21:59:29.988 20822 20906 E AlarmManager: Failed to set alarm
11-21 21:59:29.988 20822 20906 E AlarmManager: java.lang.SecurityException: Caller com.google.android.gms needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.os.Parcel.createException(Parcel.java:2409)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2392)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2334)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:359)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:947)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:907)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at android.app.AlarmManager.setExactAndAllowWhileIdle(AlarmManager.java:1175)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at pwk.i(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at wwd.c(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at wwc.g(:[email protected]@21.42.18 (190400-410302452):6)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at com.google.android.gms.gcm.connection.HeartbeatChimeraAlarm.f(:[email protected]@21.42.18 (190400-410302452):12)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at com.google.android.gms.gcm.connection.HeartbeatChimeraAlarm.g(:[email protected]@21.42.18 (190400-410302452):4)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at wwl.z(:[email protected]@21.42.18 (190400-410302452):5)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at wwi.run(:[email protected]@21.42.18 (190400-410302452):21)
11-21 21:59:29.988 20822 20906 E AlarmManager:  at java.lang.Thread.run(Thread.java:920)
11-21 21:59:29.998  1481  1503 I ServiceWatcher: [fused] connected to {com.google.android.gms/com.google.android.location.fused.FusedLocationService}
11-21 21:59:29.999  1481  4060 I LocationManagerService: fused provider loaded extra attribution tags: [activity_recognition_provider, awareness_provider, fused_location_provider, geofencer_provider, network_location_calibration, network_location_provider]
11-21 21:59:30.012 20822 20906 E AlarmManager: Failed to set alarm
11-21 21:59:30.012 20822 20906 E AlarmManager: java.lang.SecurityException: Caller com.google.android.gms needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.os.Parcel.createException(Parcel.java:2409)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2392)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2334)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:359)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:947)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:907)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at android.app.AlarmManager.setExactAndAllowWhileIdle(AlarmManager.java:1175)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at pwk.i(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at wwd.c(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at wwc.g(:[email protected]@21.42.18 (190400-410302452):6)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at com.google.android.gms.gcm.connection.HeartbeatChimeraAlarm.f(:[email protected]@21.42.18 (190400-410302452):12)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at wwi.run(:[email protected]@21.42.18 (190400-410302452):44)
11-21 21:59:30.012 20822 20906 E AlarmManager:  at java.lang.Thread.run(Thread.java:920)
11-21 21:59:30.071 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.scheduler.ACTION_PROXY_SCHEDULE cmp=com.google.android.gms/.chimera.PersistentInternalBoundBrokerService }
11-21 21:59:30.071 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.scheduler.ACTION_PROXY_SCHEDULE cmp=com.google.android.gms/.chimera.PersistentInternalBoundBrokerService }
11-21 21:59:30.089 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.pseudonymous.service.START pkg=com.google.android.gms }
11-21 21:59:30.090 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.pseudonymous.service.START pkg=com.google.android.gms }
11-21 21:59:30.092 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.nearby.exposurenotification.START cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.093 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.nearby.exposurenotification.START cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.097 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.contextmanager.service.ContextManagerService.START pkg=com.google.android.gms }
11-21 21:59:30.097 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.contextmanager.service.ContextManagerService.START pkg=com.google.android.gms }
11-21 21:59:30.104 20822 20908 D CompatibilityChangeReporter: Compat change id reported: 150935354; UID 10059; state: ENABLED
11-21 21:59:30.109   769   769 E [email protected]_sdm660.qti: ThermalHAL not initialized properly.
11-21 21:59:30.109 20822 20908 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
11-21 21:59:30.109  1481  1513 E ThermalHalWrapper: Couldn't get temperatures because of HAL error: ThermalHAL not initialized properly.
11-21 21:59:30.110   769   769 E [email protected]_sdm660.qti: ThermalHAL not initialized properly.
11-21 21:59:30.110 20822 20889 E AlarmManager: Failed to set alarm
11-21 21:59:30.110 20822 20889 E AlarmManager: java.lang.SecurityException: Caller com.google.android.gms needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.os.Parcel.createException(Parcel.java:2409)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2392)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2334)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:359)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:947)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:907)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at android.app.AlarmManager.set(AlarmManager.java:817)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pwk.k(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pwk.o(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pwk.e(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at com.google.android.contextmanager.controller.EventHandler$AlarmSetter.c(:[email protected]@21.42.18 (190400-410302452):8)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at ebo.run(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at ebs.handleMessage(:[email protected]@21.42.18 (190400-410302452):3)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pyx.run(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pzh.c(:[email protected]@21.42.18 (190400-410302452):6)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at pzh.run(:[email protected]@21.42.18 (190400-410302452):7)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at qdn.run(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.110 20822 20889 E AlarmManager:  at java.lang.Thread.run(Thread.java:920)
11-21 21:59:30.110  1481  1513 E ThermalHalWrapper: Couldn't get temperatures because of HAL error: ThermalHAL not initialized properly.
11-21 21:59:30.110   769   769 E [email protected]_sdm660.qti: ThermalHAL not initialized properly.
11-21 21:59:30.110  1481  1513 E ThermalHalWrapper: Couldn't get temperatures because of HAL error: ThermalHAL not initialized properly.
11-21 21:59:30.115 20822 20908 W SystemServiceRegistry: No service published for: wifirtt
11-21 21:59:30.119 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.udc.service.START cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.119 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.udc.service.START cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.130 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.tapandpay.service.BIND pkg=com.google.android.gms }
11-21 21:59:30.130 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.tapandpay.service.BIND pkg=com.google.android.gms }
11-21 21:59:30.136 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.icing.LIGHTWEIGHT_INDEX_SERVICE cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.136 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.icing.LIGHTWEIGHT_INDEX_SERVICE cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.144 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
11-21 21:59:30.144 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
11-21 21:59:30.147 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.herrevad.services.LightweightNetworkQualityAndroidService.START pkg=com.google.android.gms }
11-21 21:59:30.147 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.herrevad.services.LightweightNetworkQualityAndroidService.START pkg=com.google.android.gms }
11-21 21:59:30.148   628  2527 W libperfmgr: Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1
11-21 21:59:30.151  1481  5429 D WifiNl80211Manager: Scan result ready event
11-21 21:59:30.152  1481  5429 D WifiNative: Scan result ready event
11-21 21:59:30.157 20822 20822 I Herrevad: [2] xxs.a: updateListenState
11-21 21:59:30.162 20822 20908 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
11-21 21:59:30.163 20822 20822 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.usagereporting.service.START pkg=com.google.android.gms }
11-21 21:59:30.163  1481  1609 D WificondScannerImpl: Filtering out 19 scan results.
11-21 21:59:30.166 20822 20908 W SystemServiceRegistry: No service published for: wifirtt
11-21 21:59:30.169 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.nearby.sharing.START_SERVICE cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.169 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.nearby.sharing.START_SERVICE cmp=com.google.android.gms/.chimera.PersistentApiService }
11-21 21:59:30.177  8000  8000 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot1
11-21 21:59:30.177   576   576 I hwservicemanager: Since [email protected]::IRadio/slot1 is not registered, trying to start it as a lazy HAL.
11-21 21:59:30.178  8000  8000 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot1...
11-21 21:59:30.181   576 20915 W libc    : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot1": error code: 0x20
11-21 21:59:30.181   576 20915 I hwservicemanager: Tried to start [email protected]::IRadio/slot1 as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
11-21 21:59:30.208 20822 20908 W SystemServiceRegistry: No service published for: wifirtt
11-21 21:59:30.216 20822 20889 E AlarmManager: Failed to set alarm
11-21 21:59:30.216 20822 20889 E AlarmManager: java.lang.SecurityException: Caller com.google.android.gms needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.os.Parcel.createException(Parcel.java:2409)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2392)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.os.Parcel.readException(Parcel.java:2334)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:359)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:947)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.app.AlarmManager.setImpl(AlarmManager.java:907)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at android.app.AlarmManager.set(AlarmManager.java:817)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pwk.k(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pwk.o(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pwk.e(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at com.google.android.contextmanager.controller.EventHandler$AlarmSetter.c(:[email protected]@21.42.18 (190400-410302452):8)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at ebu.d(:[email protected]@21.42.18 (190400-410302452):3)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at edl.<init>(:[email protected]@21.42.18 (190400-410302452):9)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at edf.<init>(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at edd.<init>(:[email protected]@21.42.18 (190400-410302452):1)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at efw.aH(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at efw.bo(:[email protected]@21.42.18 (190400-410302452):3)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at efv.run(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at ebs.handleMessage(:[email protected]@21.42.18 (190400-410302452):3)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pyx.run(:[email protected]@21.42.18 (190400-410302452):2)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pzh.c(:[email protected]@21.42.18 (190400-410302452):6)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at pzh.run(:[email protected]@21.42.18 (190400-410302452):8)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at qdn.run(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.216 20822 20889 E AlarmManager:  at java.lang.Thread.run(Thread.java:920)
11-21 21:59:30.219 20822 20822 I NearbySharing: NearbySharingService created [CONTEXT service_id=194 ]
11-21 21:59:30.224 20822 20908 D CompatibilityChangeReporter: Compat change id reported: 182185642; UID 10059; state: ENABLED
11-21 21:59:30.225 20822 20908 E AndroidRuntime: FATAL EXCEPTION: GoogleLocationService
11-21 21:59:30.225 20822 20908 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 20822
11-21 21:59:30.225 20822 20908 E AndroidRuntime: java.lang.IllegalStateException: Telephony is null
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at android.telephony.TelephonyManager.requestCellInfoUpdate(TelephonyManager.java:6389)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at bagb.handleMessage(:[email protected]@21.42.18 (190400-410302452):77)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at aahh.mN(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at aahh.dispatchMessage(:[email protected]@21.42.18 (190400-410302452):11)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:201)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:288)
11-21 21:59:30.225 20822 20908 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:67)
11-21 21:59:30.228 20822 20908 I GCore-Chimera-Crash: CmUKCWNvbnRhaW5lchCn8ZJmGEAggPqzo6w-KgVnYW1lcyoDcG
11-21 21:59:30.228 20822 20908 I GCore-Chimera-Crash: F5Kg90ZmxpdGVfZHluYW1pdGUqDnZpc2lvbi5iYXJjb2RlKhF2
11-21 21:59:30.228 20822 20908 I GCore-Chimera-Crash: aXNpb24uY3VzdG9tLmljYSoKdmlzaW9uLm9jcgobCgdlbnByb2
11-21 21:59:30.228 20822 20908 I GCore-Chimera-Crash: 1vEKX39_wHGIECIPCytYiG6eYDIAA=
11-21 21:59:30.228 20822 20908 I GCore-Chimera-Crash: GCore-Chimera-Crash
11-21 21:59:30.228 20822 20908 I DeviceDrDatabaseHelper: Cleaning stale data from database!
11-21 21:59:30.237 20822 20908 W DeviceDoctorHandler: Crash Hash: 514138f76b215f63d04e54746f200dd02ea519b4
11-21 21:59:30.237 20822 20908 W DeviceDoctorHandler: Shushing crash.
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler: FATAL EXCEPTION: GoogleLocationService
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler: Process: com.google.android.gms.persistent, PID: 20822
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler: java.lang.IllegalStateException: Telephony is null
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at android.telephony.TelephonyManager.requestCellInfoUpdate(TelephonyManager.java:6389)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at bagb.handleMessage(:[email protected]@21.42.18 (190400-410302452):77)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at android.os.Handler.dispatchMessage(Handler.java:106)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at aahh.mN(:[email protected]@21.42.18 (190400-410302452):0)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at aahh.dispatchMessage(:[email protected]@21.42.18 (190400-410302452):11)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at android.os.Looper.loopOnce(Looper.java:201)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at android.os.Looper.loop(Looper.java:288)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:   at android.os.HandlerThread.run(HandlerThread.java:67)
11-21 21:59:30.237 20822 20908 E DeviceDoctorHandler:
11-21 21:59:30.241 20822 20822 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.trustlet.bluetooth.service.BIND pkg=com.google.android.gms }
11-21 21:59:30.241 20822 20822 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.trustlet.bluetooth.service.BIND pkg=com.google.android.gms }
11-21 21:59:30.244  1481  4840 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
11-21 21:59:30.245 20822 20908 I Process : Sending signal. PID: 20822 SIG: 9
11-21 21:59:30.266  1481  4840 I ActivityManager: Process com.google.android.gms.persistent (pid 20822) has died: fg  BTOP
11-21 21:59:30.267  1481  1517 I libprocessgroup: Successfully killed process cgroup uid 10059 pid 20822 in 0ms
11-21 21:59:30.268   683   683 I Zygote  : Process 20822 exited due to signal 9 (Killed)
11-21 21:59:30.271  8963  8963 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.checkin.START pkg=com.google.android.gms }
11-21 21:59:30.272  1481  1503 I ServiceWatcher: [GeocoderProxy] disconnected from 10059/com.google.android.gms/[email protected]
11-21 21:59:30.272  1481  1503 I ServiceWatcher: [HardwareActivityRecognitionProxy] disconnected from 10059/com.google.android.gms/com.go[email protected]1
11-21 21:59:30.272  1481  1503 I ServiceWatcher: [network] disconnected from 10059/com.google.android.gms/[email protected]
11-21 21:59:30.272  1481  1503 I ServiceWatcher: [GeofenceProxy] disconnected from 10059/com.google.android.gms/co[email protected]1
11-21 21:59:30.272  1481  1503 I ServiceWatcher: [fused] disconnected from 10059/com.google.android.gms/[email protected]
11-21 21:59:30.274  1481  3962 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(uid/pid:10059/20822, [email protected])
11-21 21:59:30.274  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.nearby.exposurenotification.service.ExposureMatchingService in 65536000ms for start-requested
11-21 21:59:30.275  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentDirectBootAwareApiService in 1000ms for connection
11-21 21:59:30.276  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.PendingIntentCallbackService in 46137344000ms for start-requested
11-21 21:59:30.277  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.stats.eastworld.EastworldService in 184549376000ms for start-requested
11-21 21:59:30.277  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.common.stats.GmsCoreStatsService in 738130395136ms for start-requested
11-21 21:59:30.277  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.clearcut.debug.ClearcutDebugDumpService in 88076189696ms for start-requested
11-21 21:59:30.278  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.tron.CollectionService in 130015035392ms for start-requested
11-21 21:59:30.278  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geocode.GeocodeService in 21501952ms for connection
11-21 21:59:30.278  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentBoundBrokerService in 10997ms for connection
11-21 21:59:30.279  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.HardwareArProviderService in 2031484928ms for connection
11-21 21:59:30.279  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.nearby.sharing.ReceiveSurfaceService in 22544283336704ms for start-requested
11-21 21:59:30.279  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.network.NetworkLocationService in 33281701576704ms for start-requested
11-21 21:59:30.279  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.nearby.messages.service.NearbyMessagesService in 8320962265088ms for start-requested
11-21 21:59:30.279  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.contextmanager.service.ContextManagerService in 2751194988544ms for start-requested
11-21 21:59:30.280  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.auth.trustagent.GoogleTrustAgent in 11005316825088ms for connection
11-21 21:59:30.280  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.auth.account.authenticator.GoogleAccountAuthenticatorService in 3422216519680ms for connection
11-21 21:59:30.280  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.gcm.nts.SchedulerService in 44019119816704ms for start-requested
11-21 21:59:30.280  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.gcm.GcmService in 268422873088ms for start-requested
11-21 21:59:30.280  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fido.authenticator.service.AuthenticatorService in 25228369461248ms for start-requested
11-21 21:59:30.281  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.reporting.service.ReportingAndroidService in 83988ms for connection
11-21 21:59:30.281  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.location.persistent.LocationPersistentService in 27912724021248ms for start-requested
11-21 21:59:30.281  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService in 123988ms for start-requested
11-21 21:59:30.281  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.location.nearby.direct.service.NearbyDirectService in 2303808ms for start-requested
11-21 21:59:30.281  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.auth.setup.devicesignals.LockScreenService in 86967719034880ms for start-requested
11-21 21:59:30.282  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fido.fido2.pollux.CableAuthenticatorService in 103062035234816ms for start-requested
11-21 21:59:30.282  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.thunderbird.EmergencyPersistentService in 146011708194816ms for start-requested
11-21 21:59:30.282  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.deviceconnection.service.DeviceConnectionWatcherService in 22015901696ms for start-requested
11-21 21:59:30.282  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.FusedLocationService in 56618909696ms for connection
11-21 21:59:30.282  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.lockbox.service.LockboxBrokerService in 163984ms for connection
11-21 21:59:30.283  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService in 113798379732992ms for start-requested
11-21 21:59:30.283  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentInternalBoundBrokerService in 203984ms for connection
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.contextmanager.service.SystemMemoryCacheIntentOperation.INIT cat=[targeted_intent_op_prefix:com.google.android.contextmanager.service.SystemMemoryCacheIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.chimera.container.IntentOperationService.SAVED_INTENT pkg=com.google.android.gms cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.contextmanager.service.SystemMemoryCacheIntentOperation.INIT cat=[targeted_intent_op_prefix:com.google.android.contextmanager.service.SystemMemoryCacheIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.gms.common.broadcast.DELIVER_BROADCAST cat=[targeted_intent_op_prefix:.common.broadcast.BackgroundBroadcastReceiverSupport$PersistentReceiverIntentOperation] cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Canceling start item Intent { act=com.google.android.chimera.container.IntentOperationService.SAVED_INTENT pkg=com.google.android.gms cmp=com.google.android.gms/.chimera.PersistentIntentOperationService (has extras) } in service com.google.android.gms/.chimera.PersistentIntentOperationService
11-21 21:59:30.283  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentIntentOperationService in 188957086187520ms for start-requested
11-21 21:59:30.283  1481  4840 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentApiService in 20992ms for connection
11-21 21:59:30.287  1481  1514 W BroadcastQueue: Background execution not allowed: receiving Intent { act=com.google.android.location.internal.server.ACTION_RESTARTED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentInternalReceiver
11-21 21:59:30.293  1481  1514 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10059; state: DISABLED
11-21 21:59:30.294  1481  1514 D CompatibilityChangeReporter: Compat change id reported: 177438394; UID 10059; state: DISABLED
11-21 21:59:30.294  1481  1514 D CompatibilityChangeReporter: Compat change id reported: 135772972; UID 10059; state: DISABLED
11-21 21:59:30.294  1481  1514 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10059; state: ENABLED
11-21 21:59:30.294  1481  1515 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10059; state: ENABLED
11-21 21:59:30.308   683   683 D Zygote  : Forked child process 20919
11-21 21:59:30.311  1481  1515 I ActivityManager: Start proc 20919:com.google.android.gms.persistent/u0a59 for broadcast {com.google.android.gms/com.google.android.gms.gcm.nts.SchedulerReceiver}
11-21 21:59:30.313 20919 20919 W main    : type=1400 audit(0.0:1810): avc: denied { write } for dev="cgroup2" ino=2 scontext=u:r:zygote:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
11-21 21:59:30.317 20919 20919 E libprocessgroup: Failed to write '20919' to /sys/fs/cgroup/uid_10059/pid_20919/cgroup.procs: Permission denied
11-21 21:59:30.317 20919 20919 E Zygote  : createProcessGroup(10059, 0) failed: Permission denied
11-21 21:59:30.335 20919 20919 E .gms.persisten: Not starting debugger since process cannot load the jdwp agent.
11-21 21:59:30.366 20919 20919 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10059; state: ENABLED
11-21 21:59:30.416 20919 20919 V GraphicsEnvironment: ANGLE Developer option for 'com.google.android.gms' set to: 'default'
11-21 21:59:30.416 20919 20919 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
11-21 21:59:30.417 20919 20919 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
[/SPOILER]
 

GregEden

Senior Member
Feb 6, 2020
155
68
Melbourne
@crypticc I have a MiPad 4 LTE 8", not a plus. The ROM works. You need to increase the font size in Settings -> Display -> Font size to Large. Also increase Display Size to Large. You can try extra large even. My GPS was slow to work the first time. Install this app and let it test
The version of the MiPad without the LTE chip does not have a GPS. I have Google Maps and maps.me installed and they work. I would suggest you uninstall Google Maps and then re-install.

Plus I only install NikGapps Basic then add apps from the Playstore and do not restore from backup.

Also install gboard, make it the default, add the number row and increase the size in the settings. Another thing to make it more tablet than phone.
 
Last edited:

crypticc

Senior Member
Aug 22, 2009
1,138
121
London
@crypticc I have a MiPad 4 LTE 8", not a plus. The ROM works. You need to increase the font size in Settings -> Dispaly -> Font size to Large. My GPS was slow to work the first time. Install this app and let it test
The version of the MiPad without the LTE chip does not have a GPS. I have Google Maps and maps.me installed and they work. I would suggest you uninstall Google Maps and then re-install.

Plus I only install NikGapps Basic then add apps from the Playstore and do not restore from backup.
Hi Greg

Thanks. I think the issue with location is because for some reason Googlemaps wanted Google Location enabled, and Google Location Accuracy (the Wifi backup) also enabled. IF I disabled the latter then it momentarily worked but on App restart said it needed Google location services permissions.

I installed NikGapps Omni because I couldn't find "Basic". I obtained from here...
"https://sourceforge.net/projects/nikgapps/"

Another ROM (Android 11) admittedly targeted for Mi PAD 4 clover (not plus) doesn't do this and works. In that ROM I can have "Use location" enabled and Google Location Accuracy disabled, and then Google Maps works/finds my location and without giving errors in logcat.


Incidentally, I also noticed that restore from Google Play, whether from backup or just clicking "install" was taking an age. It wasn't WiFi bandwidth issue as a quick test of that showed >400MBit even while Google Play was baulking.
Looking in Logcat it also looked related to Google Location services being spammed 100s of times before accepting an installation of each app.


I'll have another go at this ROM another day as apart from that issue this ROM was to my eyes "smooth". I'll also try what you suggested, but for a day or few I'm trying another. Thanks though.


Chris
 

GregEden

Senior Member
Feb 6, 2020
155
68
Melbourne
I still have microphone issues. The sound recorder works but Google assistant crashes every time. Duolingo cannot hear my voice. Here is a lot but I do not have root access
 

Attachments

  • 2021-11-25_14.44.zip
    1.5 KB · Views: 4
  • Like
Reactions: sabar_op

pndwal

Senior Member
I decided to try this on my Xiaomi Mipad 4 as they have basically same hardward (Clover but 7" WiFi not the large-screen plus version...
Another ROM (Android 11) admittedly targeted for Mi PAD 4 clover (not plus) doesn't do this...
Actually, these ROM's target all Clover (Mi Pad 4) variants (WiFi, LTE, Plus...) just like official firmware IINM.

The designation in this thread (and in threads for previous LOS versions) may be a bit misleading; The title should probably be "Mi Pad 4 (Plus) China (clover)" as designated for (latest) firmware here:
https://xiaomifirmwareupdater.com/firmware/clover/weekly/9.8.29/

Parentheses here indicates 'Plus' is a variant. PW
 
  • Like
Reactions: sabar_op

crypticc

Senior Member
Aug 22, 2009
1,138
121
London
Actually, these ROM's target all Clover (Mi Pad 4) variants (WiFi, LTE, Plus...) just like official firmware IINM.

The designation in this thread (and in threads for previous LOS versions) may be a bit misleading; The title should probably be "Mi Pad 4 (Plus) China (clover)" as designated for (latest) firmware here:
https://xiaomifirmwareupdater.com/firmware/clover/weekly/9.8.29/

Parentheses here indicates 'Plus' is a variant. PW


Thanks

I'm giving Lineage OS 18.1 a spin for now.
 

sabar_op

Senior Member
Jun 30, 2010
342
682
Xiaomi Mi Pad 4 Plus
Actually, these ROM's target all Clover (Mi Pad 4) variants (WiFi, LTE, Plus...) just like official firmware IINM.

The designation in this thread (and in threads for previous LOS versions) may be a bit misleading; The title should probably be "Mi Pad 4 (Plus) China (clover)" as designated for (latest) firmware here:
https://xiaomifirmwareupdater.com/firmware/clover/weekly/9.8.29/

Parentheses here indicates 'Plus' is a variant. PW

The lineage source 19.0 is still not officially release yet even as a BETA so some features is still not implemented yet.
Write the lcd density (for screen/display) in build.prop is now not supperted yet and makes seperate rom for plus and non plus version. I can build for non plus (without gps) but I think better to wait until lineageos is officially release it while I want to finalise to build PE 12.
 
  • Like
Reactions: senseii and pndwal

pndwal

Senior Member
The lineage source 19.0 is still not officially release yet even as a BETA so some features is still not implemented yet.
Write the lcd density (for screen/display) in build.prop is now not supperted yet and makes seperate rom for plus and non plus version. I can build for non plus (without gps) but I think better to wait until lineageos is officially release it while I want to finalise to build PE 12.
Ok; so is LCD density here for Plus?; sorry, I haven't read whole thread. 😬

I have non-Plus, LTE. It has GPS...

I think we just lack larger battery, Quick charge, fingerprint sensor & large screen; it's still 1200 x 1920 pixels, but ~283 ppi density. PW
 

GregEden

Senior Member
Feb 6, 2020
155
68
Melbourne
I think we just lack larger battery, Quick charge, fingerprint sensor & large screen; it's still 1200 x 1920 pixels, but ~283 ppi density. PW
If I plug my MiPad 4 LTE 8" into a USB-PD charger that also supports QC 3 it will charge at 7w - measured via the battery section of Inware. Not super fast but better than a standard charger.
 

pndwal

Senior Member
If I plug my MiPad 4 LTE 8" into a USB-PD charger that also supports QC 3 it will charge at 7w - measured via the battery section of Inware. Not super fast but better than a standard charger.
What wattage are you getting w/ standard charger? (Can you give QC 3.0 result also at same charge % level?)

Interesting GSM Arena rates Battery Charging as 10W for both standard and Plus models...

FWIW, using Multi port Aukey charger and Ampere app (Nb. I'm still on LOS 18.1) at around 45% charge level I'm getting 960ma max using QC 3.0 compatible port, but 1030ma from standard port. After 10 min charging I get 910ma max using QC 3.0 compatible port, but 970ma from standard port.

I'm getting fairly consistent voltage readings between 3.8v & 3.9v. So I'm getting approx. 4.0w max according to Ampere but no improvement with QC 3.0 for me...

Anyway, seems QC is not implemented in non-Plus models due to hardware limitations.

Edit:

I just installed Inware app to compare:

At 47% charge I'm getting around 3.5w using standard port when readings settle down. Using QC 3.0 compatible port I'm getting more wild fluctuation, between 1w and 3.5w.

PW
 
Last edited:

GregEden

Senior Member
Feb 6, 2020
155
68
Melbourne
What wattage are you getting w/ standard charger? (Can you give QC 3.0 result also at same charge % level?)

Interesting GSM Arena rates Battery Charging as 10W for both standard and Plus models...

FWIW, using Multi port Aukey charger and Ampere app (Nb. I'm still on LOS 18.1) at around 45% charge level I'm getting 960ma max using QC 3.0 compatible port, but 1030ma from standard port. After 10 min charging I get 910ma max using QC 3.0 compatible port, but 970ma from standard port.

I'm getting fairly consistent voltage readings between 3.8v & 3.9v. So I'm getting approx. 4.0w max according to Ampere but no improvement with QC 3.0 for me...

Anyway, seems QC is not implemented in non-Plus models due to hardware limitations.

Edit:

I just installed Inware app to compare:

At 47% charge I'm getting around 3.5w using standard port when readings settle down. Using QC 3.0 compatible port I'm getting more wild fluctuation, between 1w and 3.5w.

PW
I will take a while as mine is fully charged. But I was getting up to 2000mA from a USB- PD charger. - mine is not a plus. Mostly it sat at 1700 - 1800. But now at 98% battery it is back to slow rates.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Hi OP

    You are using Pixel build now. Are you continue to update los 19 ?

    Thanks

    I will continue once the los 19.0 source is released officially.
    10
    New update : build date 20211230 (see 1st post for the link), changelog :
    - December security patch
    - Upstream update of lineage source.
    - Kernel update 4.4.296 (thanks to pix106).
    3
    I'm just guessing that 20211129-clover+ is the last release with SELinux enforcing due to December release using new software stack.
    Have I guessed correctly? Anyone? Thanks in advance 😉

    LineageOS Dec build is enforcing....
    2
    Thanks. Might be worth updating the OP when you solve any of the 'known issues'! 😉👍

    Thanks.
    Anyway...if rom build already get 'enforcing level', it will stay there in the next rom build, except it's mentioned in changelog of new rom build.
    2
    Dirty flash lineage-19.0-20211230-UNOFFICIAL-clover.zip with NikGapps-basic-arm64-12-20211227-signed.zip over lineage-19.0-20211129-UNOFFICIAL-clover.zip

    So far so good. Nothing to report.
  • 18
    LineageOS 19.0, see this link

    Installation instructions :
    - Perform a backup of your current ROM (optional)
    - Use latest TWRP for clover
    - Reboot into recovery/twrp, format data, then reboot into recovery/twrp again.
    - Flash ROM.
    - Flash GApps (NikGApps is tested) is optional.

    What's working:
    Display, Audio, Bluetooth, Wi-Fi, GPS, fingerprint, sensors, RIL (?), let me know.

    Known issues :
    - Disabled Encryption
    - Lagging to open camera/snap only for 1st time.
    - SELinux is permissive
    - Others that may come from lineage source
    - Magisk but will work with manual patching of boot.img.

    Please post the bug along with log (use syslog).

    Source :

    Kernel : clover
    Device tree : sdm660
    11
    Uploading new rom 20211112 (see 1st post for the link) :
    Changelog :
    - Nov security patch
    - SELinux is enforced
    - Upstream update of lineage source
    - Device is certified without magisk
    - Fix battery icon, support monet, etc...
    10
    Update : latest version lineage-19.0-20211105-UNOFFICIAL-clover-new.zip pass safetynet.
    10
    New update : build date 20211230 (see 1st post for the link), changelog :
    - December security patch
    - Upstream update of lineage source.
    - Kernel update 4.4.296 (thanks to pix106).
    10
    Hi OP

    You are using Pixel build now. Are you continue to update los 19 ?

    Thanks

    I will continue once the los 19.0 source is released officially.