HIBY R6 - DAP Dual DAC Balanced Out - Great Reviews and Over 500% Funded @ Indiegogo!
Jun 6, 2019 at 3:35 PM Post #6,016 of 6,628
Well,I was having issues with battery drain using 1.2 when I was not using it. When I first loaded it up I checked the unit before I went to bed. It was at 85%. Woke up 7 hours later and the battery was completely drained. Charged it back up and put in standby/sleep mode and checked it an hour later and it was down to 83% and the unit was very warm. Warmer than it gets when I actually use it. All apps were closed, wi-fi and bt were both off during all this.

Needless to say I did a rollback to an older version of the fw. :)
 
Jun 6, 2019 at 3:49 PM Post #6,017 of 6,628
How do you do a rollback? New version sucks... the battery dry.
 
Jun 6, 2019 at 4:11 PM Post #6,018 of 6,628
How do you do a rollback? New version sucks... the battery dry.
I have battery issues with the new update and the wifi seems worse than before (and it wasn't great already). Not very happy to be honest. How do you guys roll back to the previous version?
@Joe Bloggs , maybe it would be time to give us root so we could try to improve the battery life on our own?
 
Jun 6, 2019 at 5:51 PM Post #6,019 of 6,628
I have battery issues with the new update and the wifi seems worse than before (and it wasn't great already). Not very happy to be honest. How do you guys roll back to the previous version?
@Joe Bloggs , maybe it would be time to give us root so we could try to improve the battery life on our own?

The links to tools, downloads and instructions are included in Post #1. Joe has made a detailed version of the process which is much easier to follow than the official HiBy video. I recently rolled back from 1.2 and all battery issues vanished.
 
Jun 6, 2019 at 7:35 PM Post #6,021 of 6,628
V1.12 International and the battery drain issue started about a week ago. Something is driving the battery nutes when idle. Runs hot too

Yeah, ever since I installed 1.2 I have been having battery drain issues. Even after rolling back to 1.1 and 1.12. Prior to loading 1.12 I was able to leave the unit in standby mode for a coupe of weeks losing about 2-3% battery per day. The LED was always off. Now I am having to recharge the unit almost every day. The power button LED is always lit now so something is running in the background. I am not sure what it is. I have not loaded any apps onto it since rolling back.

I wish I had never loaded 1.2 to begin with :)
 
Jun 6, 2019 at 7:37 PM Post #6,022 of 6,628
I never installed 1.2 and this is happening to me. I was going to try 1.2 for the auto-power-off but all I see is bad news. But it might not be the firmware but something else triggered by the date or some other software that is causing this.
 
Last edited:
Jun 6, 2019 at 8:00 PM Post #6,023 of 6,628
I have the same issue. From looking at logcat (which I can provide if it'll help troubleshoot) there seems to be an issue with google's ad services in the background (All part of com.google.android.gms) that keeps crashing and restarting. I wonder if this is preventing the cpu governor from going into low power mode, and just keeping it at max cpu frequency draining the battery.

Even when nothing is running, it keeps killing the services and restarting. Here's a small snipet of the logs that keep repeating when at idle, but if you'd like me to provide more for troubleshooting purposes I'd be happy to):

06-06 18:56:46.373 482 505 I mmid : select timeout: wait for receiving msg
06-06 18:56:46.997 1094 1108 I ActivityManager: Start proc 13176:com.google.android.gms.persistent/u0a12 for service com.google.android.gms/.chimera.PersistentApiService
06-06 18:56:47.015 1094 3227 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.015 1094 3227 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.015 1094 3227 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.021 1094 3227 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.021 1094 3227 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.021 1094 3227 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.023 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.023 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.023 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.024 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.024 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.024 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.025 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.025 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.025 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.028 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.028 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.028 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.029 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.029 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.029 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.030 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.030 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.030 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.032 1094 1108 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.032 1094 1108 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.032 1094 1108 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.043 13176 13176 I zygote64: The ClassLoaderContext is a special shared library.
06-06 18:56:47.045 13176 13176 I zygote64: The ClassLoaderContext is a special shared library.
06-06 18:56:47.116 13176 13176 W DynamiteModule: Local module descriptor class for providerinstaller not found.
06-06 18:56:47.126 13176 13176 W ProviderHelper: Unknown dynamite feature providerinstaller
06-06 18:56:47.129 13176 13176 I DynamiteModule: Considering local module providerinstaller:0 and remote module providerinstaller:0
06-06 18:56:47.130 13176 13176 W ProviderInstaller: Failed to load providerinstaller module: No acceptable module found. Local version is 0 and remote version is 0.
06-06 18:56:47.137 13176 13176 V NativeCrypto: Registering com/google/android/gms/org/conscrypt/NativeCrypto's 284 native methods...
06-06 18:56:47.160 13176 13176 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
06-06 18:56:47.163 13176 13176 I ProviderInstaller: Installed default security provider GmsCore_OpenSSL
06-06 18:56:47.209 13176 13176 I GmsApplication: Registering the BackgroundBroadcastReceiverSupport receiver.
06-06 18:56:47.266 13176 13176 I GmsReceiverSupport: Registered Receiver for 19+1 IntentFilters
06-06 18:56:47.283 13176 13181 I zygote64: Do partial code cache collection, code=26KB, data=19KB
06-06 18:56:47.284 13176 13181 I zygote64: After code cache collection, code=24KB, data=18KB
06-06 18:56:47.284 13176 13181 I zygote64: Increasing code cache capacity to 128KB
06-06 18:56:47.294 13176 13176 W Primes : Primes not initialized, returning default (no-op) Primes instance which will ignore all calls. Please call Primes.initialize(...) before using any Primes API.
06-06 18:56:47.367 13176 13176 I DynamiteModule: Considering local module com.google.android.gms.googlecertificates:4 and remote module com.google.android.gms.googlecertificates:4
06-06 18:56:47.367 13176 13176 I DynamiteModule: Selected local version of com.google.android.gms.googlecertificates
06-06 18:56:47.494 1094 3227 D ContextHubService: Added callback, total callbacks 1
06-06 18:56:47.499 1094 2374 D ContextHubService: System supports 0 hubs
06-06 18:56:47.501 13176 13176 W ChreGmsCore: Unable to construct RealContextHub.
06-06 18:56:47.501 13176 13176 W ChreGmsCore: java.lang.IllegalStateException: No ContextHubs were found in the platform.
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bshi.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):8)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfqj.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):15)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfms.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):16)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfne.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfne.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at com.google.android.location.geofencer.service.GeofencerStateMachine.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):25)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfnf.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at bfov.<init>:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at com.google.android.location.internal.GoogleLocationManagerChimeraService.onCreate:)com.google.android.gms@17455020@17.4.55 (040406-248795830):6)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at efl.onCreate:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at qif.onCreate:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3339)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.app.ActivityThread.-wrap4(Unknown Source:0)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1677)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.os.Handler.dispatchMessage(Handler.java:106)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.os.Looper.loop(Looper.java:164)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at android.app.ActivityThread.main(ActivityThread.java:6501)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at java.lang.reflect.Method.invoke(Native Method)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
06-06 18:56:47.501 13176 13176 W ChreGmsCore: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
06-06 18:56:47.543 13176 13181 I zygote64: Do partial code cache collection, code=56KB, data=50KB
06-06 18:56:47.543 13176 13181 I zygote64: After code cache collection, code=56KB, data=50KB
06-06 18:56:47.544 13176 13181 I zygote64: Increasing code cache capacity to 256KB
06-06 18:56:47.678 1094 2374 I WifiService: getWifiEnabledState uid=10012
06-06 18:56:47.678 13176 13176 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
06-06 18:56:47.680 1094 3227 I WifiService: getWifiEnabledState uid=10012
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: Unable to assign LocationManager blame through WorkSource
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.os.Parcel.readException(Parcel.java:2004)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.os.Parcel.readException(Parcel.java:1950)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:691)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:900)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:846)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bgsd.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bgsc.a(Unknown Source:0)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfko.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):8)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfkr.g(Unknown Source:7)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfkr.e:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at com.google.android.location.fused.FusionEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):106)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfhu.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):16)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfew.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfet.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfgs.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfen.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfht.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfjc.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfep.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfig.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bfiq.handleMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.os.Handler.dispatchMessage(Handler.java:106)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at aeue.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at bgso.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.os.Looper.loop(Looper.java:164)
06-06 18:56:47.729 13176 13206 E LocationManagerCompat: at android.os.HandlerThread.run(HandlerThread.java:65)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: FATAL EXCEPTION: FlpThread
06-06 18:56:47.731 13176 13206 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 13176
06-06 18:56:47.731 13176 13206 E AndroidRuntime: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2004)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1950)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:691)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:900)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:504)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bgsa.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):10)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bgsd.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bgsc.a(Unknown Source:0)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfko.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):8)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfkr.g(Unknown Source:7)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfkr.e:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at com.google.android.location.fused.FusionEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):106)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfhu.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):16)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfew.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfet.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfgs.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfen.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfht.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfjc.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfep.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfig.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bfiq.handleMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at aeue.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at bgso.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
06-06 18:56:47.731 13176 13206 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
06-06 18:56:47.737 13176 13202 I GeofencerStateMachine: Network location disabled.
06-06 18:56:47.743 13176 13206 I GCore-Chimera-Crash: ChcKCWNvbnRhaW5lchDgxGoYQCCWj5uDQSAA
06-06 18:56:47.743 13176 13206 I GCore-Chimera-Crash: GCore-Chimera-Crash
06-06 18:56:47.751 13176 13206 I DeviceDrDatabaseHelper: Cleaning stale data from database!
06-06 18:56:47.773 13176 13206 W DeviceDoctorHandler: Crash Hash: 61e1548b51bb1336f74b7acd3c154dd162a7d737
06-06 18:56:47.818 13176 13176 W ChimeraUtils: Non Chimera context
06-06 18:56:47.818 13176 13176 W ChimeraUtils: Non Chimera context
06-06 18:56:47.827 13176 13206 W DeviceDoctorHandler: Shushing due to low average crash frequency.
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: FATAL EXCEPTION: FlpThread
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: Process: com.google.android.gms.persistent, PID: 13176
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.os.Parcel.readException(Parcel.java:2004)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.os.Parcel.readException(Parcel.java:1950)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:691)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:900)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.location.LocationManager.requestLocationUpdates(LocationManager.java:504)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bgsa.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):10)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bgsd.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bgsc.a(Unknown Source:0)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfko.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):8)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfkr.g(Unknown Source:7)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfkr.e:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at com.google.android.location.fused.FusionEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):106)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfhu.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):16)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfew.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfet.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfgs.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfen.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfht.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at com.google.android.location.fused.StationaryThrottlingEngine.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):12)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfjc.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfep.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):2)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfig.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):1)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bfiq.handleMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.os.Handler.dispatchMessage(Handler.java:106)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at aeue.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):3)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at bgso.a:)com.google.android.gms@17455020@17.4.55 (040406-248795830):5)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at aeue.dispatchMessage:)com.google.android.gms@17455020@17.4.55 (040406-248795830):4)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.os.Looper.loop(Looper.java:164)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler: at android.os.HandlerThread.run(HandlerThread.java:65)
06-06 18:56:47.827 13176 13206 E DeviceDoctorHandler:
06-06 18:56:47.844 1094 3227 D CompatibilityInfo: mCompatibilityFlags - 0
06-06 18:56:47.844 1094 3227 D CompatibilityInfo: applicationDensity - 320
06-06 18:56:47.844 1094 3227 D CompatibilityInfo: applicationScale - 1.0
06-06 18:56:47.846 13176 13206 I Process : Sending signal. PID: 13176 SIG: 9
06-06 18:56:47.847 1094 1108 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
06-06 18:56:47.847 1094 1108 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
06-06 18:56:47.866 1094 3946 I ActivityManager: Process com.google.android.gms.persistent (pid 13176) has died: fore IMPF
06-06 18:56:47.867 1094 1110 W zygote64: kill(-13176, 9) failed: No such process
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentApiService in 4000ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.contextmanager.service.ContextManagerService in 67108864000ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService in 5514738008064ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService in 109051904000ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.auth.account.authenticator.GoogleAccountAuthenticatorService in 240518168576000ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentDirectBootAwareApiService in 43996ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentIntentOperationService in 1343936ms
06-06 18:56:47.868 1094 3946 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.network.NetworkLocationService in 3848015819309056ms
06-06 18:56:47.910 1094 1110 W zygote64: kill(-13176, 9) failed: No such process
06-06 18:56:47.910 1094 1110 I zygote64: Successfully killed process cgroup uid 10012 pid 13176 in 43ms


I'm going to check permissions and cache to see if it has anything to do with it.

Sorry to everyone for the long message. Just trying to help get this issue sorted out.

EDIT: Just to add, when hooked up via ADB and just running top, I can see system_server using a lot of cpu at idle (which may be due to me running top, hard to tell) and com.google.process.gservices constantly using CPU.
 
Last edited:
Jun 7, 2019 at 12:18 AM Post #6,025 of 6,628
I also noticed the battery drain after the update, I had to enable Idle shutdown to maintain any battery when not in use, but the battery is not lasting as long when in use, @Meanstreak242 post explains why. NEED a fix Hiby!!
 
Jun 7, 2019 at 1:04 AM Post #6,026 of 6,628
I hope it helps them narrow it down, but this doesn't mean this is the issue. The Android build tree can get pretty complex with all the patches that get added to it. Small changes in the build tree can have unexpected consequences in ways that sometimes you can't really predict.

Unfortunately since I don't have root access, I'm very limited in what I can do to troubleshoot. (And if anyone from Hiby would like me to test I'd be happy to.)
 
Jun 7, 2019 at 6:57 AM Post #6,029 of 6,628
@Joe Bloggs , i've wanted to rolled back to Marshmallow, and i've tried the ROM you've provided, but it doesn't work. Just confirming if it's the right MM image or not?

Thanks and regards
Dear daduy,
That depends on how it's not working... details?
 
HiBy Stay updated on HiBy at their facebook, website or email (icons below). Stay updated on HiBy at their sponsor profile on Head-Fi.
 
https://www.facebook.com/hibycom https://store.hiby.com/ service@hiby.com

Users who are viewing this thread

Back
Top