Related
If you are using this workaround and are happy with it, please show it and press the thanks button.
Thank you,
Bazoocaze
Latest updates
29/nov/2012: Fuel Gauge Fix on Google Play
I published the Fuel Gauge Fix application v1.6.3 on the Google Play:
Free version:
https://play.google.com/store/apps/details?id=br.bazoocaze.fuelgaugefix.free
Donate version:
https://play.google.com/store/apps/details?id=br.bazoocaze.fuelgaugefix.donate
There is no differences between versions - install the version you want. Uninstall the standalone version before installing the play store version. The application data will not be transported between the standalone version and play store version, so take note of your customizations before uninstalling.
Changes in version 1.6.3:
-Added an option to allow changing the notification icon type.
18/sept/2012: Kernel patch (unlocked bootloader) for ICS .587
See the Patched kernel download section.
13/set/2012: CM9/10 FXP patched kernel
Thanks to svanteson
http://forum.xda-developers.com/showthread.php?t=1763227
12/set/2012: Locked bootloader patch updated to work with .587 stock firmware
http://forum.xda-developers.com/showthread.php?p=28871812#post28871812
10/aug/2012: Doing some research
You asked, so I'm doing some more research on an automatically way of restarting from software an early aborted charging process.
APK Updates
11/feb/2012: New FuelGaugeApp v1.6
There is a new FuelGaugeApp version - now it supports CPU clock detection.
APK Fix From Bazoocaze:
Please use the latest version, and with patched kernel v4 or later. See "Android APK helper". See "APK Issues".
v1.6 Detects CPU clock and calculates CPU consumption
v1.5.4: set battery to 100% on charger disconnected
v1.5.3: old - test version
v1.5.2: old - updated charger detection
v1.5.1: old - updated to sense GPS state and screen brightness
v1.5: old - this version was deployed with a bug in charging logic - please dont use
v1.4: old - updated menu icons, and show battery % on notification text.
v1.3: old - updated notification icon[/B]
v1.2: old - ugly notification icon, first charge issues
v1.1: failed - found a noob bug on APK - sorry
v1.0: failed
v1.0: failed
Stock kernel Driver Updates
v4: use this: allow driver to fake report 85% battery. Use with lastest APK FIX for online battery capacity changes. See "Kernel Issues". See "Warnings"
v3.1: failed: allow driver to fake report 85% battery. See "Issues". See "Warnings".
v3: failed: success: allow driver to fake report 100% battery. See "Issues".
v2: failed: leave/enter ROM mode (flash mode) - failure to write to 0x16 (0x0B) i2c address
v1: failed: reset / factory restore fuel gauge - failure to write to 0xAA (0x55) i2c address
FAQ
[Q] What is this?
[A] This is a workaround/patch to 0% battery issue caused by downgrading firmware from 2.3.4 to 2.3.2.
[Q] I need this patch?
[A] If your battery shows 0% and your android shutdown and does not charge, try to remove battery for 30 seconds and put it back. If this does not solve the issue, flash back stock 2.3.4 firmware. If this does not solve the issue, replace your phone using your warranty from Sony. If this does not solve the issue and you wish to take the risks, then this workaround is for you.
[Q] What kind of failure is this 0% battery issue?
[A] This is an unrecoverable hardware failure on the fuel gauge controller of the Arc/Neo. On our research, we concluded that no software can correct this.
[Q] There will be an official patch from Sony?
[A] No, because it's an unrecoverable hardware failure.
[Q] What I need to take this workaround?
[A] You have two options: unlocked bootloader and locked bootloader
Primary method - for locked bootloader / unlocked bootloader: you need root, BusyBox, android 2.3.3 or later, and follow the steps on http://forum.xda-developers.com/showthread.php?p=28871812#post28871812
Alternate method - for unlocked bootloader: if primary method fail, you need and unlocked bootloader device, android 2.3.3 or later, and follow the steps on this thread.
[Q] Primary method: what are the steps to apply the fix on my phone - (locked and unlocked bootloader)?
[A] First, read the full post, especially the FAQ.
Next, see http://forum.xda-developers.com/showthread.php?p=28871812#post28871812
[Q] Alternate method: what are the steps to apply the fix on my phone (only for unlocked bootloader)?
[A]
Only use this method if the primary method does not work for you.
1. First, read the full post, especially the FAQ. In case of doubt, you can use this guide to know how to do things:
http://forum.xda-developers.com/showthread.php?t=1133650
2. Unlock your booloader
http://forum.xda-developers.com/showthread.php?t=1551494&highlight=bootloader
http://forum.xda-developers.com/showthread.php?t=1034087
3. Grab the most recent kernel patch from this thread. The file is boot.img.xxx.7z for your phone (ARC / NEO). We call this the kernel patch, or only the patch.
4. You must be same firmware and patch version, so if you aren't firmware xxx, use flashtools to flash the correct firmware, and wipe the data if downgrading firmware version. You can find some recent stock firmwares in the [Firmwares (.FTF)] section.
http://forum.xda-developers.com/showthread.php?t=1304634
5. Use fastboot (or flashtools) to flash boot.img contained in file boot.img.xxx.arc.7z (or boot.img.xxx.neo.7z for NEO users). Flash the .img file, not the .7z file .
http://forum.xda-developers.com/showthread.php?t=1116970
PHP:
fastboot flash boot boot.img
6. Now you have a phone showing allways 85% battery capacity.
7. Install most recent FuelGaugeFixV??.apk from this thread (Bazoocaze version).
8. For the first time, make sure the charger is plugged, and select "Start full charge" from the apk fix menu (use the menu button to show options). A full charge takes 2h00 ~ 2h30 for stock charger, and 3h00 ~ 3h30 for USB.
9. Now you have a fully charged phone, and apk fix updates battery % acordingly to phone usage.
10. If you wish, you can now root your phone using the instructions on the section [Root for unlocked bootloaders].
11. See "Kernel issues" and "APK issues".
12. Press the tanks button on this thread, and optionally feel free to buy me some gift/beer/pizza/coffe.
http://forum.xda-developers.com/donatetome.php?u=4215483
13. Finish
[Q] There is another way of obtaining online battery % via software?
[A] Simple answer: no. Calculating battery % needs a coloumb counter hardware, that is the fuel gauge in our case. No fuel gauge, no coloumb count, no battery %.
Extended answer: there is no way of obtaining online battery capacity without the help of the fuel gauge, because battery dont have a "% capacity", but have a "full charged maximum capacity" and the actual capacity is the amount of charge left from the total minus the cumulative coloumb count of current drained by phone. The fuel gauge is responsible for sensing the coloumb count, and without it, we are only poor guessing the actual battery % capacity. This way, if the fuel gauge had an unrecoverable hardware failure, none can be made by us nor SE to recover the phone capacity of reporting battery status - its impossible to calculate without a coloumb counter in hardware.
[Q] But I installed your stuff and the battery % seems to be increasing / decreasing with use / charge. You said its impossible to obtain battery % via software. Whats happening?
[A] It's a guess value calculated based on peripheral usage of your phone, and not on stats measured from battery module. The usage is based on statistical usage of my phone, so maybe its not correct, but works.
[Q] I flashed the patch, and now my phone is not charging. Can you help?
[A] Do not let the phone runs out of charge. Recharge frequently. Try to charge with other chargers, and on the USB on PC. Try to leave the phone shuted off charging on PC, and go back after a time (1 hour) to see if the phone gets back on. If this does not work, I cannot help you.
[Q] What are the risks?
[A] See [Warnings] section.
[Q] I dont know how to {flash boot.img / unlock bootloader / use fastboot / use flashtool / etc}. Can you help?
[A] Every tool and proceding on this thread can be found on the XDA forum. Search in the forum for links / tutorials / manuals / guides.
[Q] I want this on CM / MIUI / Stock version xxx. You version/firmware sucks. Please, can you make a patch for the other version/firmware?
[A] See "Compatibility" section, or ask your favorite custom kernel / firmware developer to generate a patched version based on my work. Also, I did post the source code of my changed version of fuel gauge kernel driver, so you can make your own modified kernel version, or port the changes to CM / MIUI or other custom firmwares. Please respect my work and time spent and give me the credits on the kernel patch if you copy/use it.
[Q] I installed your stuff and my battery % is stuck on 85% or other value. Can you help?
[A] Have you installed the Fuel Gauge Fix APK and started the monitor service?
Also, make sure you dont have a task killer messing with the apk fix - it must runs ALL THE TIME to monitor peripheral usage. Also, make sure you installed the correct version of kernel and apk fix - check app version and kernel version, to make sure you have latest version. Also, you need to be on correct stock firmware version before patching the kernel.
If all versions are ok, try to stop the apk fix service and clean app data. If this cannot help, flash stock firmware (watch out to match the firmware version and kernel version), wipe the data, patch the kernel, and install app fix.
[Q]I'm using the patch, but I don't know why it seems like the phone turns off itself and needs to plug in after only X hours of usage or something.
[A] First, you can't charge offline (android not booted up). If the battery percentage doesn't change, battery driver stops the charging process.
Also, remember to choose the app option "Start full charge" BEFORE connecting the charger. Otherwise, the sudden negative variation on the battery charge caused by the option "Start full charge" selected AFTER connecting the charger may stop the process by safety measures.
[Q] Can you hide the icon on notification bar or add it in menu setting?
[A] Yes. Look into the application menu options.
[Q] I want to compile my own version of patched kernel?
[A] See the [Compile your own version] section.
[Q] Where can I find the firmware .FTF files to flash on my device?
[A] You can find some recent stock firmwares (not patched) on the [Firmwares (.FTF)] section. Please note that this versions are STOCK, not patched. Don't forget to apply the kernel patch after flashing this firmwares.
[Q] What can I do and cannot do with this patch on my phone?
[A]You cannot:
- Charge your phone offline (Android not running). The charge will stop after some minutes.
- Charge your phone with the Fuel Gauge Fix App not running. The charge will stop after some minutes.
- Leave your phone charging for a long time / charge it at night. The battery will start to discharge after it reach 100%, so you must disconnect it from the charger after that.
- Connect the charger and then select "Start Full Charge". The charge may stop after some minutes. You must select "Start Full Charge" before connecting the charger. You can try to charge without selecting "Start Full Charge" (if the battery percent is low) and see if it work.
You can:
- Use your phone as you want.
- Use it while charging.
- Play games.
- Set your battery percent to 100% if you charge for more than 1h30 and the percent stops below 100%. In this case the calculated charging rate may be slower than the real charging rate, and the real battery may be reaching 100% before the calculated percent.
- Fine tune the software battery capacity and consumption parameters on the Fuel Gauge Fix App. Try to take a mean of total consumption starting from 1500000uA from your usage, and change the value accordingly. The percent will reflect the value, so if you lower the value (say 1400000) you will get a low percent early, and if you rise the value (say 1600000), you will get a low percent later. Don't forget to mantain the charge current value with a relative value for a 1h30 to 2h30 charging time. Ask for help on thread to know more.
[Q] I like your work, and it worked fine for me. Thank you.
[A] I'm glad to know this. So, hit the thanks button, for me to know you liked. Or buy me some coffe, beer and pizza (fuel of a dev).
APK Issues
All versions:
- When the phone runs out of charge, the phone will simply shutdown without warning. There will be no Android warning, since the dead fuel gauge is the responsible for notifying the system about battery empty. This issue cant be fixed - you need to live with it.
- There is no way for the charger monitor to guess the current charge, so it starts with 100% on the first run. If your battery status is low when you start the monitor for the first time, maybe you get out of charge early before reaching 0%, and them you cant get a full charge until you reach a low percent value again. Use the "Start full charge" menu option on apk fix to make the phone take a full 3 hours charge.
- The phone does not charge to 100% and the charge process stops early: your are not using the correct firmware / patch / apk fix. Verify the instaled versions and install correct version. Also, do not use the phone during charge, because the charge process may be disable by an overheat event occured during charge.
- The phone does not charge to 100% and the charge process stops early: maybe your battery is full and the charging process is done. Disconnect the charger, and set battery to 100% if needed.
Kernel Issues
All versions:
- You must use the same Kernel and System version. This way, your Arc/Neo must be in the correct firmware before applying the kernel patch. Look for the patched kernel version on this thread, and flash the corresponding firmware/ROM stock version. If you dont use same Kernel and System ROM version, maybe you get temporary innoperant Wifi or other hardware malfunction until flash correct version.
Try to flashtool the correct .FTF firmware before flashing the patched boot.img, and see if your issues go away.
- If your phone stops charging, try with different chargers (official / others), and with charging via USB on PC.
- Try to not let your phone shutdown by running out of charge. The battery has a safety circuit to prevent undercharging that shutdown before lower limit, but case the protection fails and battery voltage runs below the lower limit threshould, the battery may become permanent disabled by safety circuit.
- If you know what are you doing, you can try this (kernel patch needed) on android shell to modify battery % capacity (the 85 indicates 85%):
Code:
echo 85 > /sys/class/power_supply/bq27520/set_capacity
The /sys/class/power_supply/bq27520/set_capacity file only exists in our patched kernel.
Android APK helper
Please use latest version. Use with patched kernel v4 or later. See "APK Issues".
v1.6:
Last changes:
- Detects CPU clock, and calculates CPU consumption accordingly.
v1.5.4:
Last changes:
- Set battery to 100% on charger disconnected event, after a minimum charging time.
- Charging statistics, like average charge and discharge time.
v1.5.3: test version
v1.5.2: old
v1.5: old
v1.4: old
v1.3: old
v1.2: old - must be kernel patch v4
v1.1: old
v1.0: old
Fuel Gauge Fix APK description
Its a service that runs all the time, calculating battery consumption / charge, and updating the battery % of the phone, trying to mimic te lost functionality of the defective fuel gauge. Use it in conjuntion with the patched Kernel. Its does not works without the patched Kernel (missing set_capacity functionality in kernel).
How to use the APK
- The APK needs android 2.3.3 or later.
- The APK needs patched kernel ou patched fuel gauge module.
- Install the latest patched kernel / module from this thread (watch out for kernel patch firmware version requirement), and this APK.
- The APK only update the battery % on patched kernels.
- Open the APK (Fuel Gauge Fix), Click "Start monitor", and configure the "Charger Monitor" to start on boot.
- Test the APK to see if it changes the battery % on phone.
- If it wont work, look into the screen of APK, on field "Patch status", and report here you problem.
- If it works now you can use your phone (mostly) normally.
- For the first time, and when necessary, do a full charge on the battery, selecting the menu option "Start full charge".
How APK fix works
- Runs every 1 minute on screen disabled, and every 5 seconds on screen enabled.
- Scans for connected / enabled hardware, like charger, screen, bluetooth, wifi, celular.
- Starting from v1.6, it will take in count the CPU clock / usage, too. Use CPU Spy APK to debug CPU usage.
- Generate consumption prediction for enabled hardware.
- Simulate coloumb counting on in memory battery stats, charging / discharging the stats accordingly, and updating the battery % show by phone.
- There is an 1% limit, that is, the phone will never shutdown while there is power on the battery.
- On the first run, the fix start with 100% stats. Full charge your phone to help sincronize the calculated value with the real value. The real value cant be get by software, thanks to the faulty hardware fuel gauge.
- The fix memorize the last stats, so if you stop the service or reboot the device, the monitor must maintain the same stats on next run. Use the app menu to reset stats to 100%.
Kernel / ROM compatibility list
0% friendly: this kernels / ROMs already have the kernel patch, so you only need to install the Fuel Gauge Fix APK start the monitor service:
[ARC/ARC S] DoomKernel (thanks to DooMLoRD)
[ARC/ARC S] CM9/10 FXP kernel (thanks to svanteson)
http://forum.xda-developers.com/showthread.php?t=1763227
[NEO] NightElf (thanks to Night-Elf)
forum.xda-developers.com/showthread.php?t=1468043
0% unfriendly: the developers of these work choose to not integrate the kernel patch, so you will have a hard time trying to make the patch working:
- CyanogenMod 7 / 9 / 10
- FXP
Warnings
- Very important: I just now discovered that the battery temperature sensor may have stopped to work properly because of the the fuel gauge issue. Thus, the battery may overheat in extreme situations, which reduces the average life of the battery or can even result in fire in rare cases. Even so, the sensor is still read correctly by the controller BQ24158, which inhibits the charging in event of overheating (temp > 45oC). Either way, avoid charging the battery and operating the phone at the same time, to minimize the heat generated during charging. Also, please charge the battery away from the sun or hot spots, and no more than three hours on the charger. Knowing this, if you think there is a risk for you or your equipment, please do not use this patch.
- This is an experimental kernel, compiled from stock kernel source code supplied by Sony. Use it on your own risk.
- If you unlock your bootloader, you have NO WARRANTY from Sony.
Requirements for the kernel patch
- Xperia Arc/Neo
- Firmware version 2.3.3 or later (APK fix requirement)
- Unlocked bootloader
- Fastboot (to flash the boot.img)
Credits
Initramdisk from DooMLoRD thread
First APK Fix script v1.1 from FiDra
steryman for various patched version
JasonStein for his MIUI patched version
DooMLoRD for patched DooMKernel version
svanteson for CM patched version
zdzihu for the first locked bootloader patch
Kernel sources from Sony
ARM compiler from CodeSourcery
IDE from Eclipse team
Android SDK from Google
Patched kernel download
If you think my work is helping, please press the thanks button.
- All versions here are STOCK kernel, unless explicitly stated. Ignore the image/logo on startup. For other kernels, see "Other kernels" section.
v4:
- Look in the download file name for version information. You must use the same firmware and patched kernel version. See "Kernel issues".
ICS 4.1.B.0.587
ARC: boot.img.4.1.B.0.587.lt15i.7z - 7 MB
http://www.mediafire.com/?jssaye1xm2ohva6
NEO: boot.img.4.1.B.0.587.mt15i.7z - 7 MB
http://www.mediafire.com/?ns8049q084kihio
(old) ICS 4.1.B.0.431
ARC: boot.img.4.1.B.0.431.lt15i.7z
http://www.mediafire.com/?ttldhug1zl487nk
NEO: boot.img.4.1.B.0.431.mt15i.7z
http://www.mediafire.com/?4so293y7o899kwa
- (old) NEO boot.img patched kernel .62:
http://www.mediafire.com/?7g6gz2mpp1ljb46
- (old) Patched Kernel for Xperia ARC / NEO (one zip file, 2 img files - choose arc/neo to flash) version 4.0.1.A.0.283:
http://www.mediafire.com/?64ogvfgp8xp8btg
Stock firmwares (.FTF)
These are stock firmwares, not patched, not rooted. You can flash this firmware using flashtools, then flash the boot.img patch.
If you have an unlocked bootloader you can use the method described in the section "Root for unlocked bootloaders" to root your device after firmware flashing.
GingerBread Android 2.3
NEO Firmware 4.0.2.A.0.42 Android 2.3.4 Generic Global(World)
MT15i_4.0.2.A.0.42_GLOBAL.7z
http://www.mediafire.com/?ic223ahl1sbftbj
http://115.com/file/e6gvbzgp
http://www.multiupload.com/ZHYL4RSZGW
ARC Firmware 4.0.2.A.0.58 Android 2.3.4 Generic HK
http://www.wupload.com/file/2536357702/LT15i_4.0.2.A.0.58_Generic_Global_HK.rar
ARC Firmware 4.0.2.A.0.42 Android 2.3.4 Generic Global(World)
LT15i_4.0.2.A.0.42_Generic_Global.ftf
http://www.wupload.com/file/2328127472/LT15i_4.0.2.A.0.42_Generic_Global.ftf
ARC ICS 4.0.4
LT15i_4.1.B.0.587_Generic Global World.7z
188Mb
http://www.mediafire.com/?xucot63l30epa4y
LT15i_4.1.B.0.431_Generic Central Europe 1 (cust_1247-1041).7z
188Mb
http://www.mediafire.com/?6jrtwqvn2f9mj1d
LT15i_4.1.B.0.431_GenericWorldFR.7z
195Mb
http://www.mediafire.com/?qbip855iltbv5is
Root for unlocked bootloaders
Please use this thread:
http://forum.xda-developers.com/showthread.php?t=1871981
Source code
In this post you can find the source code of my changed version of fuel gauge kernel driver (bq27520-kernel-driver.7z), so you can make your own modified kernel version, or port the changes to CM / FXP / MIUI or other custom firmwares. Please respect my work and time spent and give me the credits on the kernel patch if you copy/use it.
Compile your own version
This are simplified steps. If you dont know how to do, search in the forum.
- First, download the stock kernel source for Xperia (watch out for the correct version), or the sources for your custom ROM you want to use if its not compatible with stock kernel. The developer thread of dev Kalled from Sony (search on developer thread) has some instructions on how to compile the kernel.
This is the direct link to download Sony stock kernel sources:
http://developer.sonymobile.com/downloads/opensource/
- For the ARM compiler, download the CodeSourcery arm eabi compiler version 2010q1.
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1294
- Install the compiler on Linux (You can use a virtual machine if you have Windows - use Virtual Box or VMWave Player, both are free for home use).
- Overwrite the bq27520 driver source code with the patched driver from this thread.
- Next, follow the guide on Kalled thread to select phone version and compile the Kernel.
- In the end of compilation, you get a zImage file, that is YOUR Kernel. Congratulations.
- You need a ramdisk. If you are targeting a custom ROM, get a ramdisk compatible with your custom ROM. Also, you can go to DoomLord thread about ramdisk and get a ramdisk suitable for your building. Or generate/use your own ramdisk if you know how. If you use other's ramdisk, give theirs credit.
- With kernel image and ramdisk, generate the file boot.img using mkbootimg tool from Android SDK, or abootimg tool from kubuntu repositories.
- If you choose to use mkbootimg, download a compiled version of mkbootimg, or compile your own version from Android SDK.
- Now you have a boot.img file. Flash it on your phone using fastboot and you are done.
Supporters
The following people have appreciated my work and time spent on this, and made me a contributiuon/bought me some gift:
- Beatmakernolv
- icet925
Thank you so much. I'm glad you like my work.
What about xperia neo? are you gonna modify kernel for us too?
did not work, the battery is at 0%
jojora said:
did not work, the battery is at 0%
Click to expand...
Click to collapse
Can you post the initialization logs?
PHP:
adb shell dmesg > output.txt
Post the output.txt file.
log file
this is log file of my arc
DAVIDSIKH said:
What about xperia neo? are you gonna modify kernel for us too?
Click to expand...
Click to collapse
I compiled a Neo Kernel version (.283).
If you try it, try to save the logs and post here for debugging.
Bazoocaze said:
I compiled a Neo Kernel version (.283).
If you try it, try to save the logs and post here for debugging.
Click to expand...
Click to collapse
Can you make sin file or ftf file to flash by flashtool my arc can not unlock bootloader.
Thank you very much!
Sent from my LT15i using XDA Premium App
jojora said:
this is log file of my arc
Click to expand...
Click to collapse
Thank you.
PHP:
<3>[ 6.701660] bq27520 0-0055: Failed recover ROM mode
<6>[ 6.701751] bq27520 0-0055: PATCH: entering failure recovery
<3>[ 6.702056] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<6>[ 6.702178] bq27520 0-0055: PATCH: get_status: failed to write - 0xfffffffb
<6>[ 6.702331] bq27520 0-0055: PATCH: first status: 0xfffffffb
<6>[ 6.702453] bq27520 0-0055: PATCH: reseting controller
<3>[ 6.706390] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<3>[ 7.719360] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<6>[ 7.719512] bq27520 0-0055: PATCH: get_status: failed to write - 0xfffffffb
<6>[ 7.719635] bq27520 0-0055: PATCH: reset status: 0xfffffffb
<6>[ 7.719757] bq27520 0-0055: PATCH: factory restore controller
<3>[ 7.719970] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<3>[ 8.729339] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<6>[ 8.729461] bq27520 0-0055: PATCH: get_status: failed to write - 0xfffffffb
<6>[ 8.729614] bq27520 0-0055: PATCH: factory restore status: 0xfffffffb
<3>[ 8.729827] msm_i2c msm_i2c.0: (00aa) Error during data xfer (-5)
<6>[ 8.729949] bq27520 0-0055: PATCH: get_status: failed to write - 0xfffffffb
<3>[ 8.730163] bq27520 0-0055: PATCH: failed
Lines containing "PATCH:" are the recovery commands I'm sending to the controller during driver load. The problem is worse than I'm thinking - the fuel gauge is not responding for the write commands.
But I see that two important case tests that I wrote did not execute at all. I will correct this bug and generate another kernel version.
Ghost_kh_07 said:
Can you make sin file or ftf file to flash by flashtool my arc can not unlock bootloader.
Click to expand...
Click to collapse
Sorry. Locked bootloader only allow kernel and firmwares signed by Sony, for security reasons. Customs Kernels/firmwares only with unlock-BL.
Try fix battery 0%
Hi Bazoocaze
this is log of my arc with the new kernel
not work for me.
My LOG attached
thx
Plz,we need your help,waiting for your solution.
Let me have a try.
So what's more ? Is it working for the neo ?
If you are able to, might I suggest looking at the 146 rev. and compare it to the 283 rev. to see what differences it is sending/receiving to the battery or the i2c driver?
Im pretty sure anyone who flashes to rev.283 (the original) has no luck at all in regards to any battery status change, but with rev.146 I believe everyone has had the 1% battery status, so whatever the 146 is doing is allowing for some form of percentile increase of the battery charge.
I wonder if in the 146 the driver starts for a short burst of time and then crashes right away giving it the 1% mark that we all see, where as in any other version it doesnt even get far enough to show the 1%.
I dunno, there has to be something there that is pretty drastically different that we can go from using the phone all day to not being able to use it at all unplugged.
SireJoe said:
If you are able to, might I suggest looking at the 146 rev. and compare it to the 283 rev. to see what differences it is sending/receiving to the battery or the i2c driver?
.
Click to expand...
Click to collapse
Thank you for your point, I will diff the drivers to look for changes.
Until now, my research on this showed that the fuel gauge has it's own firmware, that are upgraded if needed each system startup (the firmware are 2 files contained in the system ROM). Moreover, the firmware is merged with proprietary battery data local to the fuel gauge before each firmware upgrade. I think that the system downgrade resulted in failure to downgrade the fuel gauge firmware/local data, leaving the fuel gauge in an invalid internal state.
Anyway, I'm working on a driver version that fakes the battery status, showing 100% all the time, to help people with no warranty options from Sony.
Can you upload the kernel.sin? Or would I even be able to flash it seeing as how it may not be signed?
If you could even upload it anyways. I am always looking to try something out to get this issue resolved.
Hi. I wrote a new version (v3) that try to (fake) lock the battery capacity to 100%.
Try this, and report back if it function properly on your phone. In case it fails, pelase post the log dump.
I think the charger will still works, because the charging process is based on the real battery voltage, and not on the reported value from the dead fuel gauge.
It works on my neo! now it shows 100% all the time. Thank you for your hard work
Me Too!! It's Work !! ^^.....!! Thanks Bazoocaze to let me live together with my Arc again!!!!
After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.
Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102
[Guide] Root Pixel XL Android 11 (R) Unlock/Lock Bootloader + Install Custom ROMS + Update Magisk/Systemless Root
Introduction
This Guide is for Google Pixel XL owners that want to Install/Flash Custom ROMs, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel XL phone with an unlocked bootloader.
An Android 11 (R) Custom ROM(s) (Update(s) 9. below).
A Computer with the latest working SDK Platform-tools r. 34.0.3 installed.
Important Notes:
If you use the Linux or Windows version of SDK Platform- tools r. 34.0.3 you must set the environment variable - See Note(s) for instructions on setting the enviroment Variable
If you have any problems with SDK Platform-tools 34.0.3. You can get SDK Platform-tools 33.0.3 here.
Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
Updates
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Alpha
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta - app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
TWRP - TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R). (Q)
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.2 14Feb
SDK Platform-tools - r34.0.3 May 22, 2023
Custom Kernels
Google Pixel XL ROMs, Kernels, Recoveries, & Other
ElementalX Kernel Manager
My other guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Credits/Thanks/Recognitions
@topjohnwu - Magisk
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Bootloader/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data/Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number 7 times or until you see you're a Developer.
Tap back > Developer Options and toogle OEM Unlock on and, toggle USB Debugging on.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Important: Do not relock your bootloader until you have returned the device to Stock..
Boot bootloader
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times or until you see'You are a Developer. Tap Back > Developer options and toggle OEM Unlock off.
Install/Flash Custom ROM with @badabing2003 PixelFlasher
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones. by badabing2003
Install/Update Magisk Modules
Download Modules
Fox Magisk Module Manager Releases
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Fox2Code/FoxMagiskModuleManager
Open Fox2Code/FoxMagiskModuleManager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Fox2Code/FoxMagiskModuleManager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs for Pixel XL
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMS
Google Pixel XL ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
[OFFICIAL] LineageOS 18.1 for the Google Pixel XL by npjohnson
[ROM][11.0] crDroid 9.99 [UNOFFICIAL][marlin/sailfish] By blckbear
Themes, Apps, and Mods
Google Pixel XL Themes, Apps, and Mods
Other: TWRP Backup
TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R).
Has anyone tried using the current TWRP and Magisk?
I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.
shiodooru said:
Has anyone tried using the current TWRP and Magisk?
Click to expand...
Click to collapse
Yes. Didn't work, just rebooted twice (I think) then booted directly into android.
Therev86 said:
I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.
Click to expand...
Click to collapse
I have the same problem with AdAway too. I'm guessing that we don't have write access.
Trylr said:
I have the same problem with AdAway too. I'm guessing that we don't have write access.
Click to expand...
Click to collapse
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again
Therev86 said:
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again
Click to expand...
Click to collapse
Hey that worked. Thanks.
I have 10 on my phone. I just took the OTA a few hours ago. This may be a bit off topic but I can't get picture to play on Amazon video or Google movies only audio and captions. Hulu YouTube and Netflix work fine.
EDIT: AFTER A RESTART ALL VIDEO APPS WORK FINE. I'M THE dumbass ?
Useless without twrp
There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.
Is anyone having good results with the battery life? It sucks for me.
H0wdy said:
Is anyone having good results with the battery life? It sucks for me.
Click to expand...
Click to collapse
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.
Hi
Why the pixel imprint suddenly gone from my pixel xl?
I used your guide to unlock bootloader and get root on Android 10 and it worked perfectly. Thanks.
Trylr said:
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.
Click to expand...
Click to collapse
The battery life only got bad after I upgraded, so I doubt it's hardware.
H0wdy said:
The battery life only got bad after I upgraded, so I doubt it's hardware.
Click to expand...
Click to collapse
How long have you been on Android 10? It always takes a few days at least for everything to settle down. More battery usage early.
salpsuc said:
There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.
Click to expand...
Click to collapse
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs
It works but it cannot decrypt. You will have to remove any passwords/patterns before booting into it
AP2FTW said:
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, sadly we're still waiting. I was just offering a correction.
so i did the magisk patched method but i still don't have root in magisk? i took the boot.img out of the factory image and did it as i was told to...
anything i'm missing?
it's flashing it to boot_a, is it supposed to do something else?
Since I originally wrote this I have found an even easier way that works 100% without root using Setting database editor so I've updated this guide to the better method.
as a few of us 2XL owners will know Google derped sounds on the factory image of Q and our nice charging sound has been replaced with a horrible Error sound (Google Bug tracker.)
after a few weeks of waiting & trying to fix the issue myself I have finally managed to figure it out...
turns out they're trying to access sounds from the WRONG location
UI sounds on factory Q image seem to trigger from /product/media/audio/ui but this directory only has boot animations, no audio as these files are actually located in /system/media/audio/ui
it's probably why upgrading from 9 to 10 keeps the audio settings but factory flashing doesn't.
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the settings database editor (link above)
Code:
open a terminal app and type(or copy paste) the line below;
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
or using adb:
Code:
adb shell
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
using setedit go to the global tab and look for each of the UI audio settings, switch /product/media/audio*.* to /system/media/audio/*.*
Restart your phone to apply the settings.
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Minor notes:
I'm unsure why the charging sound is dictated by wireless_charging setting.
I've had a report that settings revert after a few reboots, I've not had this myself and I've rebooted a lot but if it happens just reapply the changes in setedit.
You can also change the sounds to files on your system, I've not had luck pinpointing my sdcard folder but I have been able to change Lock.ogg to Dock.ogg as a test.
(/Sdcard/download didn't work)
_________( Old method )_________
This is my first write up so please bear with me
please note I'm not responsible for any messups you make doing this
it can be done on a terminal emulator, I prefer ADB shell
in order to sucessfully do this you will need HiddenSettings magisk module
Thank you skittles9823
I'm unsure if you need busybox but the module certainly looks for it
Code:
[B][COLOR="red"]adb shell[/COLOR][/B] or launch your [I]TerminalApp[/I]
taimen:/ $[B][COLOR="red"]su[/COLOR][/B]
taimen:/ [I]#[/I] [B][COLOR="red"]hidden[/COLOR][/B]
4 - All settings
[CHOICE]:[B][COLOR="red"]4[/COLOR][/B]
3 - Modify settings
[CHOICE]:[B][COLOR="red"]3[/COLOR][/B]
===== Modify Settings =====
[Search?]:[B][COLOR="Red"]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/COLOR][/B]
press enter & reboot your phone.
That is pretty much it, hopfully the android team fix this next patch.
I'll add some notes from what I have found through tinkering
you must reboot after modifying EACH setting.
you can see the "=" is not added when changing the settings wireless_charging_started_sound=/system/media/audio/ui/ChargingStarted.ogg (wrong)
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg (Right)
Here are all the settings i can find
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg (this causes an error on my phone)
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Awesome job figuring this out. Hopefully Google will fix this in the November system images since You've done all the work for them.
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Nightf0x_007 said:
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Click to expand...
Click to collapse
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
co4 said:
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
Click to expand...
Click to collapse
Does settings revert back after multiple reboots ? Cause this happened to me
Nightf0x_007 said:
Does settings revert back after multiple reboots ? Cause this happened to me
Click to expand...
Click to collapse
I've yet to have anything revert yet if it does happen I'll post, I guess you can reapply the settings? Or once they revert can they be re changed?
Awesome it worked I have all my sounds back!!!!
krolla03 said:
Awesome it worked I have all my sounds back!!!!
Click to expand...
Click to collapse
I'll add that it's been reported that setting may revert and reapplying will fix it again
co4 said:
I'll add that it's been reported that setting may revert and reapplying will fix it again
Click to expand...
Click to collapse
so far so good
Thank you SOOO much! :highfive: It works on my Pixel 2. Had to reset it to factory after the December update killed my Pixel launcher app. After the reset I faced this horrible charging sound and the lack of lock sounds, too.
God this was driving me crazy on a warranty replacement Pixel 2. 3rd replacement and finally it boots and the battery is decent.
I don't know if I would have noticed but for having 2 phones side by side. After that, I couldn't un-hear it.
What about Effect_tick.ogg? Is there any way to set this custom sound?
Hi,
I've tried the first method, but I couldn't grant permissions in the Terminal app, it fails!
I don't have root.
Can anyone help?
Thank you so much
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Mandrutz said:
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Click to expand...
Click to collapse
I have this also on my pixel 2 does anyone know the ADB script for that?
For everyone having battery issues with MIUI 12 and don't want to make a clean reinstall or unlock your bootloader,try this things out:
Previously, activate debug options (click multiple times Miui version on "settings"-"about phone"), search for it (under "settings" - "additional settings") and enable usb debugging (under "developer options", activate "developer options" and "usb debugging"), after that, connect with your usb cable to PC (check that you have adb properly installed on your PC:https://www.xda-developers.com/install-adb-windows-macos-linux/ and https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/, then run the following commands on a cmd window:
1. using adb, disable system traceur
Code:
adb shell pm disable-user com.android.traceur
2. make an apps optimization
Code:
adb shell cmd package bg-dexopt-job
Depends on how many apps do you have installed on your system, this probably takes between 30sec~45mins. Your system isn't stuck...
I had battery problems as well but this two things improve a lot my experience, just check my actual graphs
Now i have this insane battery backup in my device running miui 12 global
Edit 7/08 - I will answer some questions about this thread:
1. The first command will disable Android system for recording logs. It's safe if you don't need to make debugging on your phone.
2. The second command will make an apps optimization from ART cache. Sometimes, when you update or upgrade your system, apps doesn't optimize themselves, generating more consume of system resources including battery.
3. However, this last command isn't needed to be performed if you doesn't have a bad battery life behavior when you update your system but I recommend that you make it everytime after your phone get an update.
4. This will work no matter if you have a non-rooted locked bootloader device.
Hope this help you guys!
espaciosalter20 said:
For everyone having battery issues with MIUI 12 and don't want to make a clean reinstall or unlock your bootloader,try this things out:
Previously, activate debug options (click multiple times Miui version on "settings"-"about phone"), search for it (under "settings" - "additional settings") and enable usb debugging (under "developer options", activate "developer options" and "usb debugging"), after that, connect with your usb cable to PC (check that you have adb properly installed on your PC:https://www.xda-developers.com/install-adb-windows-macos-linux/ and https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/, then run the following commands on a cmd window:
1. using adb, disable system traceur
2. make an apps optimization
I had battery problems as well but this two things improve a lot my experience, just check my actual graphs
Now i have this insane battery backup in my device running miui 12 global
Click to expand...
Click to collapse
Can you share the latest screenshot of battery stats?
AsimRauf_44 said:
Can you share the latest screenshot of battery stats?
Click to expand...
Click to collapse
when the current cycle ends, i will share the latest one...
espaciosalter20 said:
when the current cycle ends, i will share the latest one...
Click to expand...
Click to collapse
Okay thank you, waiting
AsimRauf_44 said:
Can you share the latest screenshot of battery stats?
Click to expand...
Click to collapse
Well, it's seems that my stock battery statistics isn't working well or at least, as supposed to be. My last battery cycle was about 36hrs from 100% to 15% with 11 hrs SOT average but in my stock battery stats only shows 18hrs with 4:45 SOT. i had installed 3c battery monitor as well but some times wasn't properly registered because miui aggresive closing app in background.
Anyway, last charging to 100% was at 28/07 9:35pm to 15% at 30/07 9:30am. That's meaning one day an a half with 15% left to spare.... surely, almost two days of 100% to 0%.
Check my screenshots.
Non authoriced device
tweetyfiestuky said:
Non authoriced device
Click to expand...
Click to collapse
What did you tried? When you got that error?
tweetyfiestuky said:
Non authoriced device
Click to expand...
Click to collapse
revoke USB debugging and make sure to agree/accept the prompt on the phone once command has been entered on terminal/cmd
How can I roll this back?
I turned off MIUI optimization in Developer Option, it seems that battery has improved.
ssunjoo said:
How can I roll this back?
Click to expand...
Click to collapse
Code:
adb shell pm enable com.android.traceur
AsimRauf_44 said:
I turned off MIUI optimization in Developer Option, it seems that battery has improved.
Click to expand...
Click to collapse
MIUI optimisation shouldn't be disabled...
---------- Post added at 09:11 ---------- Previous post was at 09:10 ----------
I did it successfully... Now we'll see...
---------- Post added at 09:22 ---------- Previous post was at 09:11 ----------
What is result If I disable system traceur in daily using of phone?
Currently getting about 7hrs SOT... Gonna try this tonight and report back!
Sent from my POCO F2 Pro using XDA Labs
What does traceur do?
Hi there, i tried your method and worked for me But now i have different issue. Do you know how to improve battery / disable AOD?
Is there a bug in miui 12? Battery stats are only available for past 24 hours. Not able to get complete battery stats from 100-0.
AsimRauf_44 said:
Is there a bug in miui 12? Battery stats are only available for past 24 hours. Not able to get complete battery stats from 100-0.
Click to expand...
Click to collapse
This should be explained to Xiaomi ignorant engineers dev
This problem has been raised hundreds of times and hundreds of beta versions have been released so far but there is still a problem !!
hussein1 said:
This should be explained to Xiaomi ignorant engineers dev
This problem has been raised hundreds of times and hundreds of beta versions have been released so far but there is still a problem !!
Click to expand...
Click to collapse
I had huawei previously, didn't had these types of bugs ?*?* don't know why people at Xiaomi are eager to release builds before checking these simple things
i tried this method... ran the 2 commands... and it is actually working !!
got 9 hours SOT at the 20% mark
so far no side effects
johan.gutierr said:
What does traceur do?
Click to expand...
Click to collapse
just system logging on android events... It just for debugging purposes