Hello, if someone know how to fix battery drain, please help. Google Play service all time drain battery... Factory reset didnt help.
[ROM][OFFICIAL][A12][A13][A14][Dipper] Pixel Experience [AOSP]
- Thread starter GiaSen
- Start date
Hello my friend
I don't know how to apply this fix. Can you help? and does this way solve the problem?
I tried to disable the google assistant apps. I tried to clean/disable/update/uninstall updates of Google Play Services but nothing. The battery drain is huge.
I know that's free work but i hope in a new update because due to this battery drain problem and the microphone problem i'm not liking this ROM anymore(PE 12 plus), but it was my favourite (PE 11 Plus)
I know that's free work but i hope in a new update because due to this battery drain problem and the microphone problem i'm not liking this ROM anymore(PE 12 plus), but it was my favourite (PE 11 Plus)
Sadly I have to agree on the battery drain issue. Seems like an urgent issue, also not fixed here after trying the forementioned solutions.I tried to disable the google assistant apps. I tried to clean/disable/update/uninstall updates of Google Play Services but nothing. The battery drain is huge.
I know that's free work but i hope in a new update because due to this battery drain problem and the microphone problem i'm not liking this ROM anymore(PE 12 plus), but it was my favourite (PE 11 Plus)
@GiaSen & @Manosdocpap Thanks you very much for your work 
the link won't work it's getting error : file not found
Last edited:
D
Deleted member 12186321
Guest
I tried to disable the google assistant apps. I tried to clean/disable/update/uninstall updates of Google Play Services but nothing. The battery drain is huge.
I know that's free work but i hope in a new update because due to this battery drain problem and the microphone problem i'm not liking this ROM anymore(PE 12 plus), but it was my favourite (PE 11 Plus)
Yeah. Disabling and clearing things fixed it for me but only for a week. Today it started draining again. Then I tried that command mentioned by erics9n above. It worked.
Tell me, can someone come across, the "System Update" application takes up almost 4GB of data, as I understand it, these are OTA files, can they be deleted somehow?
postimg.cc
photo 2022 06 30 14 54 25 — Postimages
transmits the sound received from the microphone to the handset during a phone call.
is this bug fixed or not ???
Last edited:
Unfortunatly, it is not. At least not for me.
Seems to be the same for @Manosdocpap, as mentioned by himself, two posts above yours.
Last edited:
Google Recorder cannot live transcribe on newer versions
When the newer versions sees that you have a Pixel 6 in build.props, it tries to load a more complex ML model to get better transcription using the Tensor Cores. Since the hardware cannot keep up, there's simply no output. Rolling it back to the older 2.3.385115740 makes it work again but you lose multilingual.
Can someone test with build.props of Pixel 5 or Pixel 4?
When the newer versions sees that you have a Pixel 6 in build.props, it tries to load a more complex ML model to get better transcription using the Tensor Cores. Since the hardware cannot keep up, there's simply no output. Rolling it back to the older 2.3.385115740 makes it work again but you lose multilingual.
Can someone test with build.props of Pixel 5 or Pixel 4?
I'll try this method because also with this new build i have the same battery drain problem ;(
I receive an error on Windows Powershell (runned as administrator):
Exception occurred while executing 'disable':
java.lang.SecurityException: Shell cannot change component state for com.google.android.gms/com.google.android.gms.chimera.GmsIntentOperationService to 2
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:24182)
at com.android.server.pm.PackageManagerService.setComponentEnabledSetting(PackageManagerService.java:24081)
at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:2201)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:240)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:24844)
at android.os.Binder.shellCommand(Binder.java:950)
at android.os.Binder.onTransact(Binder.java:834)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4818)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:8901)
at android.os.Binder.execTransactInternal(Binder.java:1184)
at android.os.Binder.execTransact(Binder.java:1143)
255|dipper:/ $
Last edited:
After update to the last build Yesterday, i cant install instagram app. Cant find it at playstore as well. It says my device is not supported... Wtf?
Last edited:
Similar threads
- Locked
Top Liked Posts
-
1
I'm a backend dev with some devops experience.
I've always wondered if my own build would be the same as the official PE build...
Doesn't need a certificate in the building proces to sign some binary? To pass that strict safetynet validation? Is it even possible to build the exactly the same binary what PE build process does? -
7
development is stoppoed until a good rom accepts me as maintainer of dipper, I will try LineageOS2
It's better apply the new recovery before start the sideload since the old one no have support for dynamic super partitions...2Hi everyone, I've been using the latest PE14 ROM for a week now, and it's my first time trying custom ROMs. I want to express my gratitude to the developers for their hard work. I'm really excited about this new experience as the stock ROM doesn't compare to PE. Although there are some bugs that need fixing in future updates, such as the lack of call recording, which can be resolved with rooting.1
I'm a backend dev with some devops experience.
I've always wondered if my own build would be the same as the official PE build...
Doesn't need a certificate in the building proces to sign some binary? To pass that strict safetynet validation? Is it even possible to build the exactly the same binary what PE build process does?1
Payment actually works fine.
Another observation is now the google service doesn't recognize the phone as a full valid pixelphone as before.
Google photos application doesn't say it's a pixel phone.
And the phone (call) application shows a floating message after first start
"This device is not supported and phone calls may not work correctly."
However the calls works fine.
Is there way to fix this?
Thanks again
-
72
PixelExperience for Xiaomi MI 8 [dipper]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 14 (12 and 13 also available)
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Jhenrique09 Paypal
GiaSen PayPal
If you liked my work, give me a beer, thanks!
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
- Android OS version: 14.0.0
- Security patch level: Up to date
- Build author/Device Maintainer: GiaSen
- Device Source code: https://github.com/PixelExperience-Devices
- Source code: https://github.com/PixelExperience
- ROM Developer: jhenrique09
13April update up
Changelog
**Device Specific Changes:**
- Etude kernel: Op.11 No.4
* Linux 4.9.267
* some upstream fixes of cpufreq_stats
* fixed an issue where the frequency of big CPU cores is locked to a maximum of 1286MHz; the frequency of the big cluster is supposed to be restricted under 1286MHz if you battery is at or below 10%, as part of Qualcomm's thermal mitigation, but on previous versions, the frequency restriction was not removed after the phone is charged above 10%
* default to suspend to RAM instead of s2idle (suspend to idle) for around a 25% reduction of idle battery drain
* DO NOT use a third party kernel without proper support for Pixel thermal hal
- Adjusted thermal configs to delay CPU frequency drop and smoothen the thermal throttling curve
- Implemented dynamic thermal profile to work with Pixel thermal engine
* the option is accessible under Settings/Battery/Optimization profiles (in case you are wondering, they had no effect on PE11 before this change)
* thermal configs are dynamically loaded on a per-app basis
* only the gaming profile is available besides the default profile, because other use cases are covered well enough by the default profile
* the gaming profile maintains CPU frequency at even higher temperature compared the default profile
* surface temperatures are measured by an infrared thermometer with matching emissivity to ensure they stay below the allowed maximum values of continuously held electronic devices in IEC 60950-1 (2005) standard
* thermal profile is NOT a replacement for proper cooling. If you want better performance, you should cool your device. - Eliminated all SELinux neverallows and cleaned up unneeded or broken sepolicy
* the latest Riru installation should work now. Note that if you use any mods like this, you will not receive support from me
- Updated telephony blobs from pyxis 21.3.31 to fix random qtibus crashes in the background
- Went back to Secure Element 1.0 to work with the updated blobs
- Stopped enforcing s2idle from userspace init script so the kernel can suspend to RAM for better idle battery drain
- Cleaned some unused config overlays
**ROM update highlights:**
- April security update
- Fixed the issue of weather information not showing up in "At a glance" on the home screen of Pixel Launcher
- Improved Face Unlock. The issue of front camera being occupied should happen less frequently. Let me know if you still encounter it - Devices will only use dark boot animation from now on
- Translation updates9
