Database Develop

[APP][2.2+][11 Dec. 2022 - V3.1] BetterBatteryStats

I started BetterBatteryStats because I was missing the great battery history that Spare Parts allowed to call on Froyo. It has been a long journey since the first version. BetterBatteryStats provides an insight in following categories:
- General "other stats "overview: Awake, Deep Sleep, Screen On, Phone On, Wifi On, Wifi Running ratios
- Kernel Wakelocks
- Partial wakelocks
- Alarms/Wakeups
- CPU States
- Network stats
- Process stats with User and System CPU time
Use so called references BetterBatteryStats shows data for different samples over time:
- since boot
- since unplugged
- since charged
- since screen off
- custom references
- any combination of the above (e.g. from screen off to screen on)
BetterBatteryStats is calling the "batteryinfo" service of Android to retrieve data already lying there without generating overhead. Since Kitkat Google has revoked the permission for normal apps to access these stats (without valid reasons IMHO). You can read more about that here.
Fortunately and thanks to @Looki75 there is a way to work around the restrictions intruduced by google in Kitkat and run BBS on non-rooted devices. Please see here for more details.
BetterBatteryStats has been tested on Froyo, Gingerbread, Honeycomb (3.1, thanks to daveid), ICS, JB, Kitkat and Lollipop on different ROMs and Kernels.
What are wakelocks and why should you care about them?
When it comes to Android the most discussed and commented topic that I know is battery drain / battery life. I'm a quite heavy user because I spend a lot of time on the train every day reading my mails, surfing and listening to music but still my phone is off for a long time during the day and while I accept the battery being drained while I use the phone I care about it draining slowly while "doing nothing".
Wakelocks or to be more precise partial wakelocks is a pattern than helps devs to make sure that important pieces of their code do not get interrupted. Wakelocks are not bad per se, they are a tool. There are many poor implementations that make use of wakelocks and BBS helps making that transparent.
Caution: do not use and wakelock supressor tools. They will cause an erratic behavior of your phone, causing more harm than good.
Basically the phone has (simplified, kernel devs don't shoot) three states:
1. awake with screen on
2. awake
3. sleeping (that's you phone favorite state)
The transitions are from (1) to (2) and finally from (2) to (3). Now as long as you use your phone it's in (1) and does not leave that state as long as you keep using it interactively. If you stop using it the phone is aiming to go to (3) as fast as possible.
And here's where wakelocks are important: as our phones as smartphones they tend to do background processing. Some of this processing is important like e.g. making a phone call, listening to music or synchronizing your contacts.
As the phone wants to go from (2) to (3) and on the other hand you don't want to hang up while you are in a call the app keeps hold of a wakelock to prevent that transisiton. When you hang up the partial wakelock gets release and here we go (the phone goes to sleep).
So partial wakelocks is a tool and it's not something that we should forbid for obvious reasons. Now there are cases when the design on an app is not real life proven (conditions of poor of no converage) and the wakelocks have negative effects because they are held unnecessarily or for too long.
BetterBatteryStats identifies these wakelocks and using your expertise or the once from our users here you can understand what happens and find a strategy to change that for the better.
And what about wakeups?
Wakeups (alarms) is a pattern to be used when an application should to something after a certain period of time (or at a certain time). Again, an alarm is a tool and is nothing.
On the other hand there are a lot of poor implementations that BBS can help you discover:
- alarms waking up the device when all the app should do is refresh the screen: in such cases the app uses the wrong type of alarm, there are alarms that are specifically to be used only when the screen is on
- to frequent alarms: in case of e.g. poor network conditions some apps may use alarms to repeat failed network operations. Doing this too often will cause too many wakeups (and wakelocks for doing the handling)
- apps that wake up your device when you did not expect any activity while screen is off: you can use the info provided by BBS to contact the dev about such issues
Try it yourself
If you need help
Always add the whole context when asking for help. Most of the times a dumpfile is helpful, sometimes screenshots showing your observations may help as well.
Before posting a dump please make sure that the references for kernel wakelocks and alarms were processed correctly. Reading a dump takes a few minutes and it would be great if you could not waste the time of whomever studies it, aiming at helping you.
Generally a dump "since unplugged" is better than "since charged". When you start your analysis make sure to follow following procedure:
- enable watchdog processing in BBS settings
- verify from/to references is checked under custom views
- full charge device then let it run down to ~95%
- put device to sleep for at least 6 hours (no touchy!)
- wake device and launch BBS
- adjust from/to references to 'screen off' and 'screen on'
- save dumpfile from share menu
- post resulting log to this thread (or provide cloud link)
I will not reply to posts with incomplete dumps
Reporting bugs
If you want to report a bug please make sure:
- that you can reproduce the problem
- explain what the problem is, how you could reproduce it and what is going wrong (a sentence lke "xxxx does not work for me" is a waste of your time and wil be ignored)
- enable debug in advanced prefernces
- post a logcat
A good read about reporting bugs
Translations
Starting with 2.0 BBS is getting multi-language. Currently following languages are included:
- en: main language, maintained by me
- ru: translation thanks to @gaich
- cz: translation thanks to @mag01
- es translation thanks to @vldesco
- it translation thanks to @code010101
- hr translation thanks to @seky2205
- fr translation thanks to @xavihernandez
- de translation thanks to @Minty123
- tr translation and other language improvement by @Eleo
If you want to contribute with a new language please feel free to offer you service and contribute to BBS, by submitting a pull request to the github project with the translated strings.xml. But please be aware of the fact that translation is a continuous work: even if the initial effort is higher there will be unavoidable changes to the english master XMLs that will require regular updates of your translations.
If you have a recommendation for a free croud-translation service that you would prefer I am open for suggestions.
Thanks
To nobnut for donating me a Nexus S for testing
To nobnut and brandall for their support, encouragements, testing and constructive feedback in the early stages of the development.
To @Javinotfound or the new icons / logo
To suku_patel_22, jeremysherriff, Karpfenhai, Tungstwenty, It_ler, Perseus71 and mag01 for their help in this thread and their systematic testing my betas and RCs
To Entropy512 for providing support and insights about kernel wakelocks and helping making BBS a better tool

Release
Edit 2021-06-13: Google has pulled BBS from GPlay. The given reason is that I use a library (HockeyApp) that allows installations by other means than the GPlay; that is correct except that library is a) deprecated and does not have backend anymore and b) the GPlay edition does not use that library, only the xda-edition does. Anyhow, I am working on a fix
BetterBatteryStats is available on Google Play (https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats) for what I believe is a fair price. If you like my work and want to support me please fell free to show your gratitude by buying the app.
Google play users can register to be part of the public beta programme. Selected Release Candidates will be released to google play as part of the beta programm. You can enroll to the beta programme here: https://play.google.com/apps/testing/com.asksven.betterbatterystats
Follow me on Mastodon to be notified of updates and get insights in new features/developments.
xda edition: for xda-dev members I provide an always free and fully featured version of BBS (please play fair and do not redistribute the app without my consent).
Current test-release:
I have moved to an automated build system (older releases are still attached here) and do the distribution using AppCenter.
Privacy note
Access to the downloads does not require you to register to AppCenter (you still can to benefit from neat features like notifications when new releases are available)
Get release candidates here
Changelog
2.3
- Full android O support
- Unrooted devices now fully supported (with perms added using ADB)
- UI improvements and I18N
- Better support for substratum theming
- Fixes based on crash-reports
- Added application analytics
2.2.2.0
Fixed #791: bugs preventing sensor stats to show properly on pre-lolipop devices
2.2.1.0
Fixed #787, #788: bugs preventing some stats to show properly on pre-lolipop devices
2.2.0.0
Merged translations
same as RC3
Older Changelogs
2.2.0.0RC3
Fixed sensor report
Prep for release
2.2.0.0RC2
#780: Added proper Sensor Stats
2.2.0.0RC1
#659: Renamed "Other" stat to "Summary"
#398: possibility to add a note when saving a dumpfile
#682: Alarms details view is now scrollable
#772: use bolder fonts to comply with design guidelines and make reading on smaller devices easier
#677: added GPS time (sensors) to Summary
#777: folded both Text and JSON representations of the dumpfile into one file
2.2.0.0B6
#675: watchdog sometimes shows awake > 100%
#756: added LG G2 Kernel Wakelocks support and more agressive detection of LG G2, G3, G4
#759: Watchdog toast sometimes get sticky
#760: Kernel Wakelocks do not substract properly on non-root devices (or with API-mode on)
#762: alarm do not show icon on non-root devices (or wirh API-mode)
2.2.0.0B5
#733: Kernel wakelocks parser for LG G4
#753: Added option to select the destination directory for dumpfile/locat/etc. (Requires OI FileManager)
2.2.0.0B4
#715: introduced snackbars instead of many of the toasts
#731: fixed layout issues for "old" widgets with RTL languages
#749: fixed another non-root issue
2.2.0.0B3
#211: add sensor data to "other" stats
#741: improvements on non-root experience (network stats, fixes)
#748: fixed doze mode counters
Added sync time to other stats
2.2.0.0B2
#734: added doze mode stats (Marshmallow)#744, #747: more fixes for non-rooted usage
#745: fixed/more accurate Bluetooth stats for Marshmallow
2.2.0.0B1
#716: experimental: grant required permissions without having to install system app (requires root)
#735: fixed parsing of native alarms and API call for Marshmallow
#736, #737, #738: various FC from gplay crash reports
#741: improve functionality for non rooted devices (having system app installed)
2.1.0.0
No changes from RC6
2.1.0.0_RC6
Some more widget tuning
Merged transations
2.1.0.0_RC5
Some widget tuning
Merged and compacted changelog
2.1.0.0_RC4
#720, #721: "Awake" is now consistently "Awake when screen off"
2.1.0.0_RC3
I18N
More work on widget
2.1.0.0_RC2
#712: Fixed widget real estate
2.1.0.0_RC1
#708: reverted AppOps call back to older working version
#711: fixed process view sort
#713: fixed graph series
See also in-app changelog
2.1.0.0_B5
#673: permissions list scroll issue
Experimental M-preview support
Transition animations
2.1.0.0_B4
#612: kernel wakelocks for LG G3 5.0
#694: added awake ratio to dashclock
#699: merged system app changes
#702: moved to new appcompat
New Icons by Javi
2.1.0.0_B3
#693, 695: fixed crash on 2.3.x devices
#693: reverted back to "old" (small) system app apk to work around CM/LP 5.1.1 installation isuues
#696: fixed behavior of the "back" icon on older Android devices
2.1.0.0_B2
#671: revert to old AppOps calling method
#681: fixed rate dialog
#683: limit widget font size
#686: string mssing leading to @number being displayed
#687: widget opacity can be adjusted
I18N
2.1.0.0_B1
New responsive widget
#510: New System App (no need to update)
#658: Fixed various crash reports from gplay
#679: Fixed graphs being off on 5.1
#405: Fixed widget sometimes not refreshing at screen on
2.0.0.0
No functional changes from RC6
Merged I18Nalized changelogs
2.0.0.0RC6
This is the golden release: release notes have been updated for the upcoming 2.0
#650: semi transparent grey touch feedback for pre-lolipop devices
- Sorry, no fix for the unthemed dialogs: there is a bug in appcompat to that and I could not find a way around that except rewriting all dialogs and that is too much change at this point in time.
2.0.0.0RC5
#632, #633, #634, #635: Fixed package info dialog (colors, label width)
#639: added arabic (testwise)
#626: fix (again) for FC on long press using german language
2.0.0.0RC4
#626: fixes crash when long-pressing a list item
#630: added credits for I18N
#631: hotfix for issue with RC3 on pre-lolipop devices
2.0.0.0RC3
#616: no battery graph when all values are 100%
#617: no changelog showing in RC2
#618: add info to dumpfile is alarms/kernel wakelocks are from API
#621, #624: I18N
#622: material design touch feedback
#625: FC opening dashclock settings
2.0.0.0RC2
#552: fixed wrong style for overflow menu in dark theme
#609: fixed oblique lines in graphs
2.0.0.0RC1
#546: option to force EN-en locale
#569, #582, #588, #595: more translations
#583: move *api* out of the title
#585: optimized load time of graphs
#586: use white icon for watchdog notifications
#597: battery graph always shows same data
#599: FC opening credits screen
#600: clean up debug info from normal logcat
#602: fixed watchdog reporting of awake
2.0.0.0B7
#491: added frature to import/export preferences
#540: System App Dialog now includes link to the recovery ZIP as a workaround is in-app install does not work (links to XDA or gplay, depending on version)
#551: fixed "pinned" battery graph
#553: lighter cicle gauge and font
#554: settings screen and white text on the light background that appears after clean start
#558: make from-to ref spinners suppressable
#563: more I18N (thanks to gaich and mag01 fpr their hard work keeping up with me changing the strings)
#564: alarm details dialog title is too dark for dark theme
#566: add notification bar color for lolipop
#572: pass the su --context for accessing dumpsys alarm (may cause slowdown, please report on that with supersu version you are using)
#574: better performance in graphics
2.0.0.0B6
#521: make icon size and font size adjustable
#522: kernel wakelock using API fail on lolipop
#550: missing strings
#556: fixed native kernal wakelocks on lolipop
#557: no translation of array, mote stuff to strings
2.0.0.0B5
#360, #529, #534, #539: more externalized strings for I18N
#387: use of wakelocks with timeouts, because I can
#511: Themed dialogs
#517: redesigned graphs
#527: add SELinux policy to dumpfile
#532: fixed theme switching issues
#535: added Czeck, thanks to mag01
#536, #537, #538: added russian, thanks to gaich
#531: fixed alarms dialog showing infinite / Hr.
#545: merged new constants that were causing the wrong stats to be processed
2.0.0.0B4
First shot at I18N: implemented german
#495: cleanup ununsed libs
#502: cleanup assets
#518: fixed infinite wakeups per hour in alarms
#519: re-add battery from/to % to screen (optional)
#520: alignment of labele/icons
#523: theme switch only complete after restart
#524: switched back from cards layout as it takes too much real estate
#525: notification area invisible by default
#526: FC after theme switch
#528: Partial wakelocks show wrong values (thank google for changing the constants again)!
2.0.0.0B3
#484, #508: surface information about errors / failures to the UI
#493: avoid retrieving the battery level from battery info API to reduce load (and avoid service unavailable)
#497: added dark theme
#509: added % from/to back to dumpfile
#512: theme preference slider controls
#513: fixed empty release notes
#515: automatically detect SELinux preventing access to dumpsys alarm and fall back to API mode
#516: fixed alarms showing infinity in gauges
2.0.0.0B2
#496: fixed gauges in RAW stats always being 100%
#499: "since" and white header missing in raw stats
#504: failed remot to ro after system app install does not report an error anymore since the app was installed correctly
#505: advanced pref to enable alternate (API) mode for retrieving alarms (and avoid the need for permissive kernel)
#506: alarm details missing in dumpfile
Bigger changes under the hood: externalized all preferences to prepare for I18N
2.0.0.0B1
It's all new and shiny
#487: ability to save JSON format from tasker plugin
New calculation approach to avoid rounding differences
Simplified / removed unused options from settings
Removed google analytics
1.16.1.0B2
#486: watchdog does not warn
1.16.1.0B1
#446, #483: watchdog warns about 100% awake even if reading shows it's not the case
#481, #482: FC conditions from crash reports
#485: addedf more comprehensive info about BATTERY_STATS perm and Xposed setting to dumpfile
1.16.0.0
no changes from RC6 1.16.0.0_RC6
#479: attempt to fix failing system app install process on certain devices
#480: fixed Dashclock settings not opening in xdaedition
1.16.0.0_RC5
#475: more speaking text for XPosed module settings
#476: fixed dashclock API 2 manifest (kudos to DvTonder)
#477: fixed exception in method to obtain other stats from dumpsys (compat mode)
#478: fixed alarm parsing error on pre 4.2 versions
1.16.0.0_RC4
#469: Fixed network stats parsing error
#472: Fixed alarm parsing for L preview
#473: fixed wakelock being expressed in ms on L preview
#474: fixed sorting of CPU states
1.16.0.0_RC3
#470: fixed non null extra passed by certain launchers
#471: fixed batterystats service name on L preview
1.16.0.0_RC2
#464: fixed icon height in list
#466: if xposed modue is checked in advanced prefs do as if all perms were there (use at your own risk)
#467: fixed missing icons in network view
#468: fixed FC condition when creating a logcat
1.16.0.0_RC1
#463: added copy to clipboard on long-press
Merged to master1.16.0.0_B7
#462: fixed antialiasing of pie gauge to avoid pixelation
1.16.0.0_B6
#457: fixed FC on calling permissions
#458: fixed value of "other" stats gauge being off
#459: pie gauge brush too large on low density devices
#460: add setting to disable system app presence (for XPosed module users)
#461: added setting (display section) to use "old" bar gauge instead of "new" pie
1.16.0.0_B5
#452: update to Dashclock API 2.0
#453: fixed "current" reference not getting updated when BBS is called from tasker
#454: fixed network stats "lo" not matched to "Mobile"
#455: merged a few UI changes from the upcoming 2.0 branch
#456: fixed: when only one reference spinner is shown avoid Toast message
1.16.0.0_B4
#426: added occurences per minute/hours in alarms on screen and dumpfile
#450: fix for memory leak
#451: revert from JSON the Java serialization of references for better performance (references will be deleted after installation)
1.16.0.0_B3
#448: if root is available offer full featured alarms using dumpsys
#449 avoid flushing cache, imporving performance
1.16.0.0_B2
#447: system app has wrong signature
1.16.0.0_B1
#427: optimize the root calls for dumpsys if system app installed
#429: replace java serialization of references with a more flexible JSON serialization
#435: avoid crashing when appops not available (4.4.2+)
#437: better resetting of screen counters for non rooted 4.4+ devices
#439: dumpfile chapters comments reflect need for root
#440: better support for root (does not require to be enabled in advanced prefs anymore)
#441: offer to install as system app on 4.4+ is root available
#443: alarm does not require root anymore
#446: watchdog notification should never report more than 100%
1.15.0.0
Same as RC8 except the release notes
1.15.0.0_RC8
#432: make sure to ask for su rights right after enabling root features
#433: hint that the system app should be uninstalled before uninstalling BBS
1.15.0.0_RC7
#430: better fix for blocking root access
#431: fix for install as system app when package comes from gplay
A few changes in the popup for kitkat user at first run
Bump in version number causes references to be deleted at first run
1.15.0.0_RC6
#430: fixed blocking call if trying to install as system app without having root features enabled
1.15.0.0_RC5
#428: force mediascanner after saving files
Recreated icons in all densities
1.15.0.0_RC4
#421: Another attempt to fix the xxxhdpi icon
#426: fied missing process stats on kitkat
Fixed other stats not refreshing properly on kitkat
1.15.0.0_RC3
Fixed the way we manage system apps
1.15.0.0_RC2
Sharpened xxxhdpi icon
Added the ability to install BBS as system app (requires root, usefull only for kitkat right now)
1.15.0.0_RC1
#424: add proper (error) messages to notify about features not available without root on kitkat.
Add timing of screen on time when no stats can be retrieved
1.15.0.0_B6
#421: added xxhdpi assets
#423: fixed alarms parsing on 4.3+
1.15.0.0_B5
#422: fixed account info obfuscation for new account format coming with kitkat
1.15.0.0_B4
#418: re-add process stats to kitkat
Fix for potentially missed partial wakelocks where uid could not be found
1.15.0.0_B3
#419: Package info and icons re-added to kitkat partial wakelocks
#420: fixe from gplay creashreports
Added hires icon
1.15.0.0_B2
#416: readded missing other stats (kitkat)
#417: fix for duplicate partial wakelocks
1.15.0.0_B1
#414: Fixed error at launch (service not available for kitkat)
#415: re-added partial wakelocks and very basic other stats (deep sleep only) to kitkat (requires root)
1.14.0.0
Updated libs
1.14.0.0RC1
#404: Fixed text padding for short time strings
#407: added app ops for 4.3+ users
1.14.0.0B2
#401: added ACCESS_SUPERUSER to manifest permissions
#402: wrong values in wakelocks with hashed account info caused by hash being applied multiple times
1.14.0.0B1
#355: implement a permanent su shell to execute all commands
Various fixes from gplay crash reports
1.13.4.0
Same as B2, no changes
1.13.4.0B2
#391 support all implementations of sqlite
1.13.4.0B1
Refactoring of database access to avoid locking
1.13.3.0
Fix for users having FCs due to database lock problem
1.13.2.0
Fix for users having FCs at start
1.13.0.0
Unchanged from RC2
1.13.0.0RC2
#384: salted the account name before hashing
Fix for stats not reflecting the combo boxes anymore for some users after a reference refresh
1.13.0.0RC1
Fix to make sure spinners do not get out of sync
#383: Fixed battery / voltage level in dumpfile
A few typos
Added timestamp to logcat
1.13.0.0B5
#191, #334: Added "share" option for saving/sharing dumpfiles, dmesg and logcat
#381: fixed database exception occuring sometimes and potentially responsible for the blank stats happening from time to time for some users
#382: dmesg requires root for newer kernels
1.13.0.0B4
Added some logging to debug percentage problem: adb logcat | grep StatsAdapter
#377: refactored KB handling
#379: refactored "raw" stats
Stats row shows interactive areas (glow)
1.13.0.0B3
#236: mask account info
#378: fixed fallback stat in DashClock widget
1.13.0.0B2
#376: no icon in process view
#377: missing KB icon
1.13.0.0B1
#367: added dashclock support
#375: added JSON dumpfile format support
1.12.4.0
#372: Widgets do not update on a fresh install
#373: change default widget fallbacl to "boot"
#374: refresh spinners and user refresh causes the cache of refs to get flushed/reloaded from data
1.12.3.0
#369: small widget uses wrong prefs
#370: Other stat times/total time incorrect
1.12.2.0
#366: fixed FC when creating a dumpfiel from tasker
Improved logging
Fixed concurrency problems potentially leading to weird display
Fixed a caching issue
1.12.1.0
Fix migration issues from 1.11 leading to inconsistent stats
#359: make sure BatteryInfoUnavailableException does not other stats to be shown
#361: a better fix for battery/voltage using current instead of "to" stat
#363, #364, #365: fixed different error conditions from crash reports
1.12.0.2
Skipped 1.12.0.1
#356: bug when migrating from 1.11
#357: to battery % always shows current value
1.12
Same as RC12, no changes
1.12RC12
#356: fixed empty stats after screen being rotated
1.12RC11
#223: active monitoring
#346: save 'unplugged' ref at first use to avoid empty refs
#347: pref to diable widgets to be refreshed at screen on
#344: better fix for errors in parsing network/alarms causing the whole reference to be saved empty
1.12RC10
#302: added credits for used libs in app besides git (under help)
#342, #345: remove log verbosity when debug advanced pref is not enabled for cleaner logcats
#343: fixed alarms parsing of details for flg= and cmp= (both pre- and post 4.2.2)
#344: error in parsing network stats causes the reference to be saved empty (potentially a cause of reference shown as not having been created)
1.12RC9
#323: pref for saving dumpfile to private storage
#337: implement 48dp rhythm
#338: optimize list real estate
#339 (partially): fixed tiny font for widget being same as small
1.12RC8
#341: fixed alarms for android 4.2.2
1.12RC7
#327: spinner refresh issues
#331: sometimes the stats shown do not reflect the spinner selection
#333: charged and unplugged should not be in the "to" spinner as that makes no sense
1.12RC6
#307, #328; widget stops updating and stays blank
#327: spinner refresh issues
#329: fallback ref in 1x1 widget is never loaded
#330: an attempt to fix wakelock issue when su commands are blocked
1.12RC5
#326: fixed rate dialog showing at each start
Some profining
Less intrusive logging if dedug is disabled in prefs
1.12RC4
New readme and rate dialogs
#325: times in wakeup_sources are a factory 1000 to small
1.12RC3
#321: fixed spinner heights
#322: filter "0" cpu states
#324: add marker to dumfile if using wakeup_sources
1.12RC2
#320: added experimental support for wakeup_sources (newer kernels deprecate /proc/wakelocks)
1.12RC1
#318: automatically refresh current when entering the main screen (can be changed in adv. prefs)
#319: "to ref" is shown by default (can be changed in adv. prefs)
1.12B9
#316: FC when calling BBS from watchdog notification
#317: 2x2 widget showing 0 KWL/PWL
1.12B8
#312: Fixed negative CPU percentages
#313: refresh after events creating new references show inconsistent references (from/to)
#314: proper migration of default stat type prefs coming from 1.11
#315: fixed cause of "unknown error"
1.12B7
#310: fixed partial and kernel wakelocks always being the same and icons missing
#311: fixed kb reader thread not retriieving online content
1.12B6
Changed the way su operations are processed
Some fixes regarding the refresh of the spinners
Make sure all root operations are running in an own thread
1.12B5
#308: since boot can not be selected
Fixed callstack when updating a reference
Widget now have a lightweight method for obtaining the current data without causing the cache to be updated
Spinners show references sorted in ascending order
Fixed spinner not showing all existing references
1.12B4
#306: fixed broken dumpfile
Added pref to show/hide the "reference to" spinner
Added screen on reference (saved when watchdog is active)
References are now stored in a database
From/To references are chronogical
1.12B3
#303: invalidate "current" when other refs are saved
#305: dissapearing refs
1.12B2
Some tuning
#298: Fixed FC on raw alarms
#299: Watchdog does not report when awake > threshold
#300: fixed spinner height
1.12B1
#187: freeze current time
#193: add screen brightness states to "other" stats
#274: copy wakelock to clipboard
#279: add option to save dmesg
#286: add mV/h to dumpfile
#290, 292: typo, wording
#296: kbreader is now asynchronous and doesn't block UI thread when github is slow
1.11
no change from RC8
1.11RC8
#289: FC on package info screen for pre-ICS devices
1.11RC7
#288: usability issue in permission view fixed
1.11RC6
#276: another attempt at fixing scheduled dumpfile creation from tasker
#287: fixed ratio calculation for battery drain in %/h
1.11RC5
#280: added legend to permissions tab
#283: unticking watchdog option "Screen off" stops the EventHandler service
#284: added drain per hour to battery drain text on screen and dumpfile
1.11RC4
#281: Fixed bad reference on unplug when 100% charged
#276: fixed dumpfile creation from tasker
removed delimiter till a configurable version can be provided
1.11RC3
A better fix for widgets being updated
Nicer implementation of package info using a tabbed pager (using ActionBarSherlock)
Changed in-app help and messages to make the conect of references clearer
More speaking "missing ref" texts
1.11RC2
#277: more prominent delimiter in listview
fixed calculation of since value
1.11RC1
#229: show autorun and other package info like permissions and services, click on the icons
#279: reverted the time reference for since and calculations back to 1.9.x
#275: widgets do not always refresh: hack to make sure the widget always get the broadcasts from the launcher, even if the lancher is not complying with standards (see http://stackoverflow.com/questions/7390449/widget-notification-when-homescreen-app-is-restarted)
yet another attempt to fix since screen off dump incomplete when created at wakeup from taker plugin
big refactoring (only relevant for the ones reading the code)
1.10.5
No changes from RC1
1.10.5RC1
Make sure app is not installed to SD (watchdog, widgets, detecting boot and unplug won't work properly)
Writing references respect "root features" settings
Fixed error condition in widget (potentially not showing data)
Refactored broadcast handlers
Another attempt to fix dumpfile creation in tasker plugin
1.10.4
Fixed logcat permission
1.10.3
Some changes in widget code
#270: added option to save logcat from app
1.10.2
#263: adv prefs to turn on stats while plugged
#264: error happening when reading other stats should not skip the whole stats
#265: reference summary shows data instead of counts (in dumpfile and log)
#266: difference in "since" time between widget and screen
#268: error when checking charger status causes exception
1.10.1
#261: missing cpu states file causes references to stay empty
#262: battery level handling causes exception
1.10
A few changes in logging
New ?????
1.10RC3
#257: referencea are missing processes
#258: if debug pref is not checked since shows 0s
1.10RC2
#256: silent crash on progress dialog
#252: a better fix for the FC on enabling root features
Typo in prefs
Added drain to on screen battery info
1.10RC1
#251: added batter level from/to to screen (and a pref to enable/disable it)
#252: an attempt to fix the FC on enabling root features
#254: incomplete (ref missing) dump from tasker
#255: not systematic crash on creating custom ref
1.10b7
#248: added raw CPU states
#249: ratio of other stats is calculated against something that is smaller than "since"
#250: when a reference is null all stats should show that there is no reference availble
1.10b6
#247: fixed deep sleep sometimes being substracted twice, causing negative values
1.10b5
#245: source of "since" is now the reference
#246: added battery voltage/level from/to to dumpfile
Removed unneeded API calls (that were to cause to batteryinfo stopping)
New error handling exposes API errors to the user
1.10b4
#243: deep sleep not showing
#244: no stats when plugged (as some internal registers do not count when plugged, leading to inconsistencies)
Removed pre-1.9 migration code that may lead refs to be deleted at start
#235: grey background for bars
1.10b3
#234: show icon for stats providing package info
#8: call application settings when package info is available (click on icon)
Refactored error handling
Workaround to avoid SuperUser to obcess about asking for rights
1.10b2
#240: removed "test" menu
#241: fixed nested menu causing FC on SDK<14
#242: removed froyo specific references as BBS is not depending on Android's implementation of refs anymore
1.10b1
#209: added since boot ref
#227: fallback to since boot if default stat type is not available
#228: pref to control log level
#230: two step save of references to avoid empty references if su request times out
#231, #232: reorganized preferences
#233: reorganized menu
#238: process Siyah "deleted: " kernel wakelocks properly
#239: network stats / alarms are disabled by default, can be turned on in advanced prefs
1.9.2.1
#226: reference info to dumpfile
1.9.2 (|xda only)
Fixed error condition where "no ref since charged" appeared after a while when a reference was present
#224: screen on time is too high in "since screen off"
1.9.1 (@xda only)
Added more logging to references
#213: Tasker plugin does not create dumpfiles / custom refs
#216: more compact CPU state view
#218, 220, 221: various fixes from Google Play logs
I maintain A list of features to be implemented and bugs here.
Below you can find older releases.
If not required I do not recommend using these as they are not up-to-date with the most current development, features and fixes.

How-to and FAQ
How-to
I have created a GitHub project for the Knowledge Base where the online and in-app help will be maintained as well. You can find the information here:
The online help: https://better.asksven.io/betterbatterystats/help/
The how-to: https://better.asksven.io/betterbatterystats/how-to/
A good how-to by Chris Hoffman published by How-to geek
Online Hilfe auf Deutsch: http://asksven.github.com/BetterBatteryStats-Knowledge-Base/help_de.html
How-To auf Deutsch: http://asksven.github.com/BetterBatteryStats-Knowledge-Base/howto_de.html
The repo: https://github.com/asksven/BetterBatteryStats-Knowledge-Base
The Knowledge Base Project: http://asksven.github.com/BetterBatteryStats-Knowledge-Base/
FAQ
1. Q:Will BBS be fixed to support Kitkat (I get "Services could not be contacted" errors?
A: Kitkat is supported by BBS starting from version 1.15
2. Q:Why are partial statitics not available on Kikat?
A: If you have a rooted phone enable the advanced root features and all will be fine. If you have no root unfortunately you are stuck without Partial Wakelocks as Google has made changes to prevent apps to access that data (see also here)
3. Q:Why installing BBS as a system app as everything works with root?
Deprecated: BBS does not require the system app anymore
A: Starting with Kikat BBS has 3 modes: without root a limited mode provides a minimal set of stats. With root the set of stats is complete but some stats (other, partial wakelocks, processes) still use a workaround. Finally with the system app BBS is fully featured without any workaround.
4. Q:I have high wlan_rx kernel wakelock. What is it and how to proceed?
A: This kernel wakelock is caused by Wifi waking up your device. To avoid it you should turn your Wifi off if not using it, use a tool to control your Wifi state or try to find and remove the cause. More here
5. Q: Google Maps is causing a lot of overhead. Must I freeze it?
A: no, Karpfenhai wrote step-by-step instructions on how to configure autostarts and the location service to avoid that
6. Q: Are you aware of the bug in BBS causing SuperUser to ask for su-permissions over and over again
A: As you said, SuperUser is asking over and over again, it's no BBS bug as BBS only requests su rights. More here
7. Q: BBS shows "no ref since unplugged"
A: Starting from 1.9 is is mandatory to plug/unplug after boot to get a "since unplugged" reference to be created. Starting from 1.10 there is anew reference "since boot" and a preference to fall back to that reference if no other is available.
8. Q: Why can't you just skip deleting the references at boot?
A: If I could I would. In a nutshell: BBS is a passive monitoring tool; this means it does not cause any overhead collecting data but compares snapshots. Now the disadvantage of this is that it makes no sense to compare values of counters between two references (e.g. "since unplugged" and "current") if the counters were reset in between. In fact that would potentially cause negative values, in every case wrong values.
9. Q: But is used to work before. Why did you change it?
A: It didn't work, you just didn't notice. The kernel and Android reset their counters at boot. That means that there is no way to compare counters from before the boot with counters from after.
10. Q: What do the widget colors / graphics mean?
A (new round widgets): the legend is displayed if you resize the widget
A (legacy widgets): For the large widget it's pretty simple. The colors represent the values "Since" (blue), "Deep sleep" (green), "Awake" (yellow), "Screen on" (white), "Kernel wakelocks" (magenta), "Partial wakelocks" (cyan). The 100% is the max of those values.
For the small widget see here
11. Q: Where are the dumpfile and logcat saved / how are the files named?
A: Both files are saved to /sdcard, their names are BetterBatteryStats-.txt and logcat-.txt where timestamp is of the format "yyyy-MM-dd_HHmmssSSS" (starting from 1.12 there is an option in advanced prefs to save those files to the private directory /sdcard/Android/com.asksven.betterbatterystats/files).
12. Q: Are you aware of the fact that BBS does not work properly for secondary users (Android 4.2)?
A: BBS works fine for secondary users as long as you don't enable root features. The reason is not BBS but the lack of support of the multiuser feature in the superuser/supersu version you are using.
13. Q: What is *overflow*?
*overflow* is a sign that one stat counter was overrun. This may happen if you have not boote your phone since long or if some wakeup/wakelock is very frequent. The only way to see what is hidden behind *overflow* is to reboot and take a fresh reading.
14. Q: Why is 'screen off' reference not being created?
A: You have to enable the watchdog for that reference to be created
15. Q: Even after plugging/unplugging my phone no reference except 'boot' is shown
A: something is preventing the unplug event to be passed to BBS. You should check for tools like greenify or stamina mode that mask such events and make sure that BBS is whitelisted. On newer Android versions please also make sure that BBS is not "optimized" by Android, under "Settings - Battery Optimization"
16. Q: What is the watchdog and how does it work?
A: The wachdog is a feature to help you in analysing when happens when screen is off. When the watchdog is turned on a reference 'screen off' is created. You can also configure the watchdog to create a reference 'screen on'. Opionally the watchdog will notify you when screen is turned on and the awake ratio was bigger that the configured threshold. In order to avoid too much overhead in processing a threshold can be set to disable the computing for short screen off times.
17. Q: my logcat is empty and says "Unable to open log device '/dev/log/main': No such file or directory"
A: Check if you have a custom kernel that turns off logging. If not some file permissions may be broken: use the repair permissions function from your recovery
18. Q: How can I get rid of GSF wakelocks
A: GSF (google service framework) can not be avoided and in no case it should be frozen. Here are some settings that can help reducing the overhead.
19. Q: The other stat is wrong. It shows "No data connection" and "No or unknown signal" while was online with Wifi all the time
A: "No data connection" and "No or unknown signal" refer to your cell data (2G/3G) service. As you have had Wifi on for some time the cell data was turned off, consistent to what the stats say: work as designed
20. Q: I can not install BBS as a system app. What can I do.
A: BBS does not require the system app anymore
A: If you are on a version older than 4.4 you don't need to install BBS as a system app. If you are on 4.4+ you should first try the in app installer. If for some reason it fails you can use the CWM scripts attached to install / uninstall BBS as a system app
21. Q: I am suffering from a high NLPWakelock time. Is there something I can do about it?
A: Here's a good summary of what NLP is and how it can be positively impacted (thanks to @Perseus71)
22. Q: On CM12 based ROMs the launcher crashes when placing a widget. When will this be fixed?
A: I can not find anything wrong with BBS code and the crash occurs in the launcher, not in BBS. After spending quite some time trying to understand the problem I must conclude that the problem is with CM12 (other ROMs on Lollipop do not have this problem)
23. Q: I can not or do not want to root my devices but would like to use BBS to gain insight. Can this be done?
A: The answer used to be "no" but this has now changed. See post #4 for a detailed description on how to proceed.
24. Q: I can not get BBS to work. How should I proceed to find out the cause
BBS has no dependency to any root-tool and does not require root to work, it only requires specific permissions that can be granted by:
- using ADB as described in the FAQ
- letting the app grant itself the permission if root is available
25. Q: BBS Shows a permanent notification. Can I remove it?
The notification is due to the android app model having changed and now requiring apps that run in the background to show themselves. I have put the "background app" notification into a separate channel named "BBS Event Processing" so you can disable it if it bugs you: no other vital notification will be send to that channel
26. Q: What is this popup saying "Detected problems with API compatibility"?
For Android 9.0 Pie users getting the "Detected problems with API compatibility (visit g.co/dev/appcompat for more info)" popup error please see this post.
When diagnosing / analysing there are a few important things to know:
- the app (advanced settings) shows you whether the permissions were granted or not
- when checking if any acition had a positive result you should always use raw stats as the default view does a diff between two snapshots, i.e. if one snapshot is missing it may show no results
- logcat may give you some info about what is going wrong, e.g. the app not being able to contact the battery_info service

Running BBS on non-rooted devices
This is not an april's fool joke!
TLDR;
This knowledge article describes a method to enable BBS to run on unrooted devices on Android versions starting with Kitkat (on previous versions root is not a must). More about that here: http://better.asksven.org/bbs-systemapp/
As it requires a few tools to be installed on your pc it requires some basic knowledge, understanding, and the readiness to tinker and to learn.
What is describe here is a method to inject according permissions required to access the battery stats using the android debugging bridge to issue commands from the pc. This will allow to grant the needed permissions, that will survive reboots.
Credits
All credits for this brilliant approach go to @Looki75. My special thanks go to @Perseus as well as to the supportive bbs community in general for their tenacity, feedback and constant support and feedback.
Details
Congrats, you made it until here, let's get started.
We will go through all steps of the setup. If you are aware of the tools and techniques please feel free to jump to the appropriate section.
The initial post on this topic as well as the basic steps (for advanced users) can be found in this original post: http://forum.xda-developers.com/showpost.php?p=67441059&postcount=30632
1. Install necessary ADB drivers and exe on PC
This may be the tricky part but we can leverage some experience in that area. A good read:
The 15 second adb installer
2. Enable USB debugging on phone's developer options
This is pretty straight forward:
http://www.howtogeek.com/129728/how...menu-and-enable-usb-debugging-on-android-4.2/
Congratulations, your are now a developer!
3. Connect phone to PC
The easiest part: connect the usb cable on both ends. When you connect the phone to PC on ADB, some models will throw a authorization message on phone Screen asking if you authorize this pc to access the phone. Its a Android M Thing.
4. Run the commands:
This requires some explanations and some hints about how to check what may have gone wrong.
Once you have connected your phone via usb start by unlocking your phone and by issuing the command: adb devices
If it came back with a Device name instead of waiting for device or "no permissions" (on linux), then you know its safe to go ahead with the real command. Its this adb devices that also triggers the Authorize pc command.
If the "adb devices" command does not return a positive result you may want to look into:
a) on windows the proper installation of the special usb drivers
b) on linux you may need to add some udev rules. This may help: http://stackoverflow.com/questions/32151114/adb-is-not-detecting-my-android-device-on-ubuntu
If the "adb devices" returned a positive result is is safe to proceed:
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
Adapt the package name depending on which version - XDA or PlayStore (without "_xdaedition" extension) - you have installed
Update: starting with 2.3-150 two new permissions are required to support alarms fully on unrooted devices
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS (needed starting on Lolipop)
Update: starting with SDK28 (Android 11) google has restricted access to the private APIs that BBS uses. Google is fuzzy about the why and arguments in terms of privacy and security.
You will need to run the following (assuming your device is not rooted, otherwise BBS takes care of that for you) for BBS to get access to these APIs:
SDK28 (Android Pie / 9)
adb -d shell settings put global hidden_api_policy_pre_p_apps 1
adb -d shell settings put global hidden_api_policy_p_apps 1
SDK29 (Android 10 and following)
adb -d shell settings put global hidden_api_policy 1
Note: a restart may be required after applying the global settings...
See also here
Voila... congrats for your tenacity, you have earned it!

Ref, Hints and blacklist
Litterature
Article from the Android PDK about Power Management: http://www.netmite.com/android/mydr...s/power_management.html#androidPowerWakeLocks
Other useful tools
The default battery usage (Gingerbread): Settings -> About Phone -> Battery Usage
The most interesting data is shown when clicking on the graph (bars below the graph). Unjustified "awake" times when display is off is an indicator for rogue apps doing stuff in the background when you think your phone is asleep
Battery Monitor Widget
Has a great stat on battery drain over time. I use this tool regularly after leaving my phone alone for 1/2 hour to check how the battery drain looks like against my benchmark of 2-10 mAh average (optimal for my SGS2).
[android backup service]
(http://code.google.com/android/backup/index.html). It is a service that offers cloud backup/restore of your settings and offers an API for other apps to do the same (http://developer.android.com/guide/t...ta/backup.html).
You can turn it off (but will lose the automatic backup) under Setting -> Privacy ->Back up my data.
Backups are useful though but no need to do it in the cloud, I'd recommend scheduling a regular backup using titanium instead (that's my setting).
[DataTracker-FD] is fast dormancy. Find the 'secret' codes for your device to turn FD off. *#*#9900#*#* on an SGSII. (contrib. by nobnut)
[syncmanagerhandlesyncalarm] That service is documented here (http://www.kiwidoc.com/java/l/x/andr.../c/SyncManager) and is responsible for updating the accounts you have under Settings -> Accounts and Sync. High values may come from bad settings (sync too often, huge amounts of data) or poorly written providers.
[reserved for misbehaving apps]

Been looking for something like this since I installed a GB ROM!
So, basically I install this app, and then Spare Parts should work as it normally did? (or dial *#*#4636#*#*, or whatever that is)

thebeardedchild said:
Been looking for something like this since I installed a GB ROM!
So, basically I install this app, and then Spare Parts should work as it normally did? (or dial *#*#4636#*#*, or whatever that is)
Click to expand...
Click to collapse
No Spare Parts won't be of any help as BetterBatteryStats does not replace com.android.settings.battery_history.BatteryHistory (called by Spare Parts). Installing the app you will get a new icon and will get the stats when starting it

Excellent work! Just what Gingerbread needs. The very best of luck with the app!
Thank you.
Sent from my Motorola StarTac using Voodoo

chamonix said:
No Spare Parts won't be of any help as BetterBatteryStats does not replace com.android.settings.battery_history.BatteryHistory (called by Spare Parts). Installing the app you will get a new icon and will get the stats when starting it
Click to expand...
Click to collapse
Ah, I see, so I use this app instead of Spare Parts. Well awesome, thanks for the clarification, and the useful app!

This is great. What about mimicking the part in spare parts that showed percentage running time? That's valuable info too. I've seen many times where running time was pegged at 100 yet there wewettewere no partial wake locks.

lexluthor said:
This is great. What about mimicking the part in spare parts that showed percentage running time? That's valuable info too. I've seen many times where running time was pegged at 100 yet there wewettewere no partial wake locks.
Click to expand...
Click to collapse
I'd be happy to look into that. Can you give me the exact name of the option/dialog you are missing to make sure we talk about the same thing?

nobnut said:
Excellent work! Just what Gingerbread needs. The very best of luck with the app!
Thank you.
Sent from my Motorola StarTac using Voodoo
Click to expand...
Click to collapse
Thank you for the support and for the testing!

Bug in Network Usage stat
nobnut has reported incomplete stats for network usage (list does not show all apps that have generating network traffic). I reproduced this on Gingerbread where my phone only shows google maps traffic. I could reproduce this on HSDPA as well as on Wifi. The figures that are shown seem ok and increases when I use Maps.
Now interesting is that this problem can not be reproduced on Froyo where reported apps concur with the Network stats from Spare Parts.
As the stat is incomplete I'll remove it from the app till I can find a solution.

When I noticed this, it occurred to me that perhaps user apps were not reporting their data, whereas the system apps were. I can get readings for a number of apps, they are all system apps however.
This may just be concidence.

New version 0.4.0 is out. See second post for download link and changelog

Your blog link still reads 0.3.1

thebeardedchild said:
Ah, I see, so I use this app instead of Spare Parts. Well awesome, thanks for the clarification, and the useful app!
Click to expand...
Click to collapse
Not sure since I can't get there on spare parts.
It was in battery history and I think it was the default that came up that said "running" and it gives a percent of the time the phone is running.
I've seen that pegged at 100% with no wake locks, so that still indicated a problem.

Very cool, thank you for your efforts. Downloaded and following on twitter/subscribed to the thread.

nobnut said:
Your blog link still reads 0.3.1
Click to expand...
Click to collapse
oops, fixed, thank you

lexluthor said:
Not sure since I can't get there on spare parts.
It was in battery history and I think it was the default that came up that said "running" and it gives a percent of the time the phone is running.
I've seen that pegged at 100% with no wake locks, so that still indicated a problem.
Click to expand...
Click to collapse
Ok here's what I have on Froyo going to Spare Parts:
. Battery Information: useless
- Usage stats: it's an poorly formated list of apps with the launch count and CPU time
- Battery History: a list of graphable buttons with following stats: Other usage, Partial Wake Usage, Sensor Usage, GPD Usage, Network Usage, CPU Usage. Each shows a list of apps/processes with blue/red bars.
Maybe you are talking about "Other usages". Here I see % running, %screen on, %wifi on

[ROM][MI Note Pro][Leo]MIUI 8 Polish 6.11.21 + cracks + XPOSED

This is the Polish version of MIUI 8 ROM, with some goodies like status bar | button DIY + crack + theme + xposed frame layout switch.
MIUI Version: 20161121
Notes from developer: (some)
Please double clear data before the first flash into MIUI8! This would break default theme - you can download new theme! Based on the Polish version of MIUI production! No family bucket millet, millet ad! The ROM has cracked official BL lock!
Starting from the development ROM version 6.1.14, the official phone BootLoader has encryption that would have BootLoader lock. But, this ROM doesnot contain BL lock
All ROM I have done are not locked, if your device BL is not locked, you can flash this ROM
For unlock, jump to other threads
If you opened my MI - Cloud Services - Find phone, please change before flash, or boot will prompt the device is locked!
Activation need to enter the current password millet account, which is the official MI process!
Top priority
When enabled immersed status bar widget, make sure to enable MiuiPermissionRemover plug, or it will flash back part of the application
Be sure to enable setting - Advanced Settings -Xposed framework for managing -Xposed frame - Modules - Custom MIUI to open all the advanced settings features
Update this week
Update micro-channel message to the anti-withdrawal V2.6.0
Update WeChat grab a red envelope back to V1.1.0
Add new suspension ball one-handed mode module, large-screen phone can also use the phone with one hand
New suspension Ball millet new payment and NFC payment module bus, the use of payment more convenient
Optimizing the use of open phone screen state
Optimization optimization headphones phone rings when calls are not quarreling headphones
Layout Optimization lock screen password to unlock the digital interface
After the repair Close meters SIM, the status bar still displays "SIM meters" problem
Decline in the status bar jammed repair problems
Repair using some third-party theme, quick switch two page background transparency issue
Anime recent repair mission details page when switching applications
Update History
Update QQ grab a red envelope to V1.0.7
Update WeChat grab a red envelope to V1.0.9
Update micro-channel message to the anti-withdrawal V2.5.0
Add millet music being played album cover page rejuvenation Yan Gaoqing big picture, immersive views; default display is playing the lyrics, sing easier to learn to sing
New Game Accelerator: solve Cards, slow, low power consumption, speed is occupied, notice annoyance, key issues such as inadvertently, enhance the game experience
Once you've added through non-official channels millet install the application, the application will be scanned for viruses, and tips for virus application to prevent the phone poisoning
Repair Wi-Fi, and some compatibility issues Carrier Routing
Bug fixes some video files cause system power consumption
Shuffle music player optimization algorithm
Brush again adapted script, part of the system to solve the problem of APP soft link
QQ message to update the anti-withdrawal V2.1.2.1
Update micro-channel message to the anti-withdrawal V2.4.0.6
Open new payment security background scanning, some checks to support users to ignore the scan, and significantly optimize scanning efficiency
New virus scanning UI new revision, and add support for the white list
Optimization of the angle calculation support scientific calculator, trigonometric calculations easier
Optimization logic weather warning notice appears
Some repair weather interface details
Optimization Status Bar support fell to expand fast switch that supports editing switch sorting
New Desktop adjustment, the support desktop display function definitions
Add status bar customization, support the status bar icon position , size, text size, background color adjustment notification bar
Adding key customization features, supports custom menu key, Home key, back key click, double-click functionality to modify &
The new Viper Sound V2.5.0.5, the new UI and operating modes
New suspension Ball supports manual welt hidden side of the slide to the edge of the screen to hide suspension ball, do not worry about blocking
New three-finger gesture can trigger decline screenshots
Replace the Polish version of the font for domestic Font
Replace themed for domestic use
Replace calendar for domestic use
Replace weather for domestic use
New streamlined system, support for extreme lean, moderately streamlined, custom streamlined
Limit removed more streamlined system APP, affect the normal use of some features
Moderate streamline delete only part of the service function, does not substantially affect the function of normal use
Custom streamlined user self-support streamlined, streamline please restart your phone after the completion of giving effect
New QQ grab a red envelope, micro-channel grab a red envelope
When optimizing a single page notification bar shows five icons (for the original 4.5)
Notification bar at right angles Optimization card (originally rounded)
Repair Viper Sound NEON-enabled state is no problem
New window multitasking module (XP module), enabling windowed application
New animation effects switch to support IOS effects, MIUI effect switch
IOS developers with special effects animation option fast zoom, the better
New drop-down shortcuts to switch layout: 3X3 layout, 3X4 layout
Optimization of the status bar to switch without rebooting, effective immediately
Advanced Settings -ROOT - access - Start icon and select "Superman Andy / chip / SuperSU" can create a desktop icon
Crack the system limits, supported the deletion of system applications, not Cami
Assistant to optimize the screen MIUI style
Optimization support custom DPI settings, can be customized size
Xposed module optimizes all Data are transferred to the partition, user-friendly upgrade and customize the uninstallation
Optimization of removing the top notification bar search box
Add topics cracks, charges relating to the use of free, never recover
Add goggles (MIUI style), eye protection at night
Double-click the Home button to add a lock screen (the default has been opened, it can be turned off in the settings)
Restart to reboot the system to add advanced options, easier
Add connected WIFI password viewing
Add call flash, flash frequency can be adjusted
Adding key aide, perfect to replace the bottom of the phone keys, but also for partial screenshot
Adding Dolby, Viper double sound, comprehensive sound enhancement system
Add drop-down shortcut keys 4x6 layout, each row displays four buttons, more beautiful
Add custom text, alternative APP arbitrary text message
Add desktop lunar calendar, alarm clock, weather information display
Add grab a red envelope plug-in support QQ, micro letter
Add Blocked run the plug completely stop running in the background App
Adding plug-type camouflage
Add a Program Freeze function, users can freeze applications and system applications
Add resolution switching function supports three resolution switching
(Note: the resolution switching will be forced to modify the DPI, DPI switch function modifications Do not use after the resolution)
Add a status bar Toggle: IOS status bar, IOS + status bar icon, the official default status bar
Add a status bar style switching time: Display Lunar / week / time
Add key position switch: return key, menu key exchange
Add the navigation bar at the bottom of the switch, you can add virtual buttons at the bottom of the phone
Add CPU Settings You can set the CPU operating mode, the minimum frequency, maximum frequency
Add layout switching function: Settings - Advanced settings -MIUI layout switch
Mega Download Link
Note: Original link was slow, so moved to MEGA. If you want any other site, let me know.
ROM posted here
Disclaimer from source:
1. The ROM has passed my test! As a result of operating the consequences of improper, I and forums and will not assume any responsibility; please ensure that the phone at least 50% or more of the electricity front
2. Brush and ensure that the process of Brush in the phone and computer without any exception;
3. Brush risk, first brush friends, be sure to carefully read the forum brush tutorial, or peril;
4. He does not hold the copyright ROM and the program, please research and study for the purpose of lawful use;
5. I affirm each of the ROM the user does not provide any kind of guarantee, does not guarantee the suitability of the ROM does not guarantee trouble-free produce; no guarantee security and stability; nor any theoretical use this ROM encountered any user or actual loss responsibility;
6. forbidden to tamper with my ROM for secondary post! In particular, no technical content of secondary packaging to promote integration software, rights reserved!
7. If you brush into this ROM, it means that tacitly accepted the above agreement.
My disclaimer:
I am not owner of ROM.
I have used or using this ROM.
Since I liked the ROM, I am sharing the it.
I hope to update the ROM link and update history, as far as possible.
Original links given - all credits goes there.
Thanks to google translate.

Multilenguaje bro??
Enviado desde mi MI NOTE Pro mediante Tapatalk

Elvaquilla said:
Multilenguaje bro??
Enviado desde mi MI NOTE Pro mediante Tapatalk
Click to expand...
Click to collapse
As far as I remember, multi language yes. English for sure

We have an update - 6.11.7.
Will update the OP
MEGA Download link

Does it have double tap to wake?

What is "cracks" ?

EMJI79 said:
Does it have double tap to wake?
Click to expand...
Click to collapse
That's a kernel tweak - not in the ROM

gersp said:
What is "cracks" ?
Click to expand...
Click to collapse
Few as I know are related to themes, xposed modules, qq, WeChat. Lots more. Use it to find all.

sarvesvara.dasa said:
That's a kernel tweak - not in the ROM
Click to expand...
Click to collapse
Doesn't a custom ROM mean a custom kernel?

EMJI79 said:
Doesn't a custom ROM mean a custom kernel?
Click to expand...
Click to collapse
Not always.
Kernel needs source, we don't have necessary source for this device.

does this rom works better then ivans aosp marshmallow version?

derdigga said:
does this rom works better then ivans aosp marshmallow version?
Click to expand...
Click to collapse
I haven't used Ivan's version of MIUI+Mashmellow.
However, Ivan's was a particular version - which never got updated.
This is the official MIUI version +/- patches.
Use it and experience it for yourselves.

Is this rom based 6.0.1 or still 5.1.1?

FxJohnnyEng said:
Is this rom based 6.0.1 or still 5.1.1?
Click to expand...
Click to collapse
5.1.1
Sent from my Xiaomi MI NOTE Pro using XDA Labs

We have an update. 2016.11.21.
Mega Link
Update this week
Update micro-channel message to the anti-withdrawal V2.6.0
Update WeChat grab a red envelope back to V1.1.0
Add new suspension ball one-handed mode module, large-screen phone can also use the phone with one hand
New suspension Ball millet new payment and NFC payment module bus, the use of payment more convenient
Optimizing the use of open phone screen state
Optimization optimization headphones phone rings when calls are not quarreling headphones
Layout Optimization lock screen password to unlock the digital interface
After the repair Close meters SIM, the status bar still displays "SIM meters" problem
Decline in the status bar jammed repair problems
Repair using some third-party theme, quick switch two page background transparency issue
Anime recent repair mission details page when switching applications
Will update OP as well.

where are advanced settings to enable xposed module ?
Ok got it, thats in chinese menu in settings, can that menu be changed to english ?

rshahzad17 said:
where are advanced settings to enable xposed module ?
Ok got it, thats in chinese menu in settings, can that menu be changed to english ?
Click to expand...
Click to collapse
Not sure how to change in English. There are still some few Chinese menus.

can i download? hope works in my leo
can i download? hope works in my leo

tohka29 said:
can i download? hope works in my leo
Click to expand...
Click to collapse
Forget about that thread (with respect to OP) look on eu Miui site. It provides latest software, rooted, with all languages you can dream of and even OTA since recently. Every thing is explained on it except if you only wanted xposed.

General Don't disable MIUI Optimizations on the Redmi Note 10 Pro [Max] (and other issues...)

Even though disabling MIUI Optimizations allows you to have a true always on display and brings back the good old native android share menu (with Copy to Clipboard and Nearby Share), it breaks the ROM in many other places:
You cannot open files on any app (File Manager, WhatsApp, Google Drive, etc.) No PDFs or other files will open.
All permissions will be reset.
Touch gestures like 3-finger screenshot will stop working.
Battery will drain extremely fast. (Even faster than it is already draining)
UI will start stuttering more than usual.
I suggest waiting for OTAs until Xiaomi fixes all of the numerous issues with this ROM. I've also compiled a list of all the issues I'm currently facing:
1. Extreme stuttering and exceptionally low touch responsiveness. 60Hz mode is even more unusable. It stutters like a 2010 phone.
2. Notification UI messed up: Actions not aligned properly, Facebook notifications not showing up properly, and don't show up at all. Android 11's 3-way split that gave conversations priority is completely removed!
3. Text Selection Menu (Context Menu) Hijacking: Critical context menu options don't show up in the hijacked menu! I can't format text in telegram without the context menu!
4. Share Menu Hijacking: Does not have the Copy to Clipboard or Nearby Share options, making it effectively useless. Need to swipe about 100 times to get to the app I want.
5. Disabling MIUI Optimizations fixes [4], but then we can't open any files in the OS! PDFs, Excel Sheets, nothing open! (Permission Denied).
6. Control Center Home features not working: crashes on click, hold.
7. Battery Drain issue: The 2-day battery effectively lasts half a day. Again: tested with 60Hz and all "recommended battery fixes".
8. Settings button in Control Center requires double tap. A single tap never opens it.
9. Always-On UI not actually "Always On." Again, disabling MIUI Optimizations just makes the phone unusable.
10. Proximity sensor just doesn't work. I think it uses heuristics based on mobile orientation and top-speaker ultrasound, but yeah, that definitely needs to be fixed.
11. Missing NFC toggle. Not sure how to even enable it.
12. Magnetometer incorrect readings: it sometimes works, sometimes doesn't. Probably a software issue.
13. Gestures don't work at all in third party launchers and literally make the phone impossible to control without the three nav buttons, which is scary.
14. Auto-rotate doesn't work as expected: Even after rotating the phone, it needs an extra wiggle and a tilt forward to activate it.
15. Notifications just don't pop-up! WhatsApp Web can't connect to WA unless it is running in the background. Facebook notifications don't pop up until the app is opened. MIUI just disabled all background apps in an effort to better manage the RAM and Battery, but as we clearly see, it doesn't work.
16. Google Discover on MIUI Launcher glitches out of bounds.
17. Add a white border instead of black border when the front camera is in use. The black border is hardly noticeable when the front camera is being used.
This list is still pretty incomplete, but I hope they start working on at least these first.

varungupta3009 said:
Even though disabling MIUI Optimizations allows you to have a true always on display and brings back the good old native android share menu (with Copy to Clipboard and Nearby Share), it breaks the ROM in many other places:
You cannot open files on any app (File Manager, WhatsApp, Google Drive, etc.) No PDFs or other files will open.
All permissions will be reset.
Touch gestures like 3-finger screenshot will stop working.
Battery will drain extremely fast. (Even faster than it is already draining)
UI will start stuttering more than usual.
I suggest waiting for OTAs until Xiaomi fixes all of the numerous issues with this ROM. I've also compiled a list of all the issues I'm currently facing:
1. Extreme stuttering and exceptionally low touch responsiveness. 60Hz mode is even more unusable. It stutters like a 2010 phone.
2. Notification UI messed up: Actions not aligned properly, Facebook notifications not showing up properly, and don't show up at all. Android 11's 3-way split that gave conversations priority is completely removed!
3. Text Selection Menu (Context Menu) Hijacking: Critical context menu options don't show up in the hijacked menu! I can't format text in telegram without the context menu!
4. Share Menu Hijacking: Does not have the Copy to Clipboard or Nearby Share options, making it effectively useless. Need to swipe about 100 times to get to the app I want.
5. Disabling MIUI Optimizations fixes [4], but then we can't open any files in the OS! PDFs, Excel Sheets, nothing open! (Permission Denied).
6. Control Center Home features not working: crashes on click, hold.
7. Battery Drain issue: The 2-day battery effectively lasts half a day. Again: tested with 60Hz and all "recommended battery fixes".
8. Settings button in Control Center requires double tap. A single tap never opens it.
9. Always-On UI not actually "Always On." Again, disabling MIUI Optimizations just makes the phone unusable.
10. Proximity sensor just doesn't work. I think it uses heuristics based on mobile orientation and top-speaker ultrasound, but yeah, that definitely needs to be fixed.
11. Missing NFC toggle. Not sure how to even enable it.
12. Magnetometer incorrect readings: it sometimes works, sometimes doesn't. Probably a software issue.
13. Gestures don't work at all in third party launchers and literally make the phone impossible to control without the three nav buttons, which is scary.
14. Auto-rotate doesn't work as expected: Even after rotating the phone, it needs an extra wiggle and a tilt forward to activate it.
15. Notifications just don't pop-up! WhatsApp Web can't connect to WA unless it is running in the background. Facebook notifications don't pop up until the app is opened. MIUI just disabled all background apps in an effort to better manage the RAM and Battery, but as we clearly see, it doesn't work.
16. Google Discover on MIUI Launcher glitches out of bounds.
17. Add a white border instead of black border when the front camera is in use. The black border is hardly noticeable when the front camera is being used.
This list is still pretty incomplete, but I hope they start working on at least these first.
Click to expand...
Click to collapse
It is hard to believe that miui is having these many issues/bugs...only custom ROMs can save.

varungupta3009 said:
Even though disabling MIUI Optimizations allows you to have a true always on display and brings back the good old native android share menu (with Copy to Clipboard and Nearby Share), it breaks the ROM in many other places:
You cannot open files on any app (File Manager, WhatsApp, Google Drive, etc.) No PDFs or other files will open.
All permissions will be reset.
Touch gestures like 3-finger screenshot will stop working.
Battery will drain extremely fast. (Even faster than it is already draining)
UI will start stuttering more than usual.
I suggest waiting for OTAs until Xiaomi fixes all of the numerous issues with this ROM. I've also compiled a list of all the issues I'm currently facing:
1. Extreme stuttering and exceptionally low touch responsiveness. 60Hz mode is even more unusable. It stutters like a 2010 phone.
2. Notification UI messed up: Actions not aligned properly, Facebook notifications not showing up properly, and don't show up at all. Android 11's 3-way split that gave conversations priority is completely removed!
3. Text Selection Menu (Context Menu) Hijacking: Critical context menu options don't show up in the hijacked menu! I can't format text in telegram without the context menu!
4. Share Menu Hijacking: Does not have the Copy to Clipboard or Nearby Share options, making it effectively useless. Need to swipe about 100 times to get to the app I want.
5. Disabling MIUI Optimizations fixes [4], but then we can't open any files in the OS! PDFs, Excel Sheets, nothing open! (Permission Denied).
6. Control Center Home features not working: crashes on click, hold.
7. Battery Drain issue: The 2-day battery effectively lasts half a day. Again: tested with 60Hz and all "recommended battery fixes".
8. Settings button in Control Center requires double tap. A single tap never opens it.
9. Always-On UI not actually "Always On." Again, disabling MIUI Optimizations just makes the phone unusable.
10. Proximity sensor just doesn't work. I think it uses heuristics based on mobile orientation and top-speaker ultrasound, but yeah, that definitely needs to be fixed.
11. Missing NFC toggle. Not sure how to even enable it.
12. Magnetometer incorrect readings: it sometimes works, sometimes doesn't. Probably a software issue.
13. Gestures don't work at all in third party launchers and literally make the phone impossible to control without the three nav buttons, which is scary.
14. Auto-rotate doesn't work as expected: Even after rotating the phone, it needs an extra wiggle and a tilt forward to activate it.
15. Notifications just don't pop-up! WhatsApp Web can't connect to WA unless it is running in the background. Facebook notifications don't pop up until the app is opened. MIUI just disabled all background apps in an effort to better manage the RAM and Battery, but as we clearly see, it doesn't work.
16. Google Discover on MIUI Launcher glitches out of bounds.
17. Add a white border instead of black border when the front camera is in use. The black border is hardly noticeable when the front camera is being used.
This list is still pretty incomplete, but I hope they start working on at least these first.
Click to expand...
Click to collapse
I'm also having almost all problems you mentioned.
Redmi note 10 pro (sweetin)
MIUI global 12.0.6.0 stable
Bootloader locked
MIUI have sooo many bugs. I will wait for 12.0.8 update. If bugs are fixed I will wait further for 12.5 update, else will install custom rom and will say final goodbye to MIUI

crazyguyrohan said:
I'm also having almost all problems you mentioned.
Redmi note 10 pro (sweetin)
MIUI global 12.0.6.0 stable
Bootloader locked
MIUI have sooo many bugs. I will wait for 12.0.8 update. If bugs are fixed I will wait further for 12.5 update, else will install custom rom and will say final goodbye to MIUI
Click to expand...
Click to collapse
I'm on sweetinpro 12.0.6.0/12.0.8.0 on Stock with locked Bootloader. It's so frustrating that they haven't fixed trivial issues in the ROM and removed fundamental features.

I'm not having any of the mentioned issues here on my redmi note 10 pro 6/128GB sweetpro, bootloader locked. I disabled MIUI optimization right of the bat, and debloated all the xiaomi crap with this tool . I was running the latest MIUI global 12.0.10 and just updated today to MIUI 12.0.13 RKFEUXM. Still no issues. Also my battery is pretty fine, more than a day and I am heavy user (and gamer)

Regarding some of the issues (I have Redmi Note 10 Pro with global MIUI 12.0.10):
1. Extreme stuttering and exceptionally low touch responsiveness. 60Hz mode is even more unusable. It stutters like a 2010 phone.
Click to expand...
Click to collapse
Touch responsivenes does behave strange and fails sometimes. I haven't noticed any stuttering though, the 730G works pretty well for me.
2. Notification UI messed up: Actions not aligned properly, Facebook notifications not showing up properly, and don't show up at all. Android 11's 3-way split that gave conversations priority is completely removed!
Click to expand...
Click to collapse
This is very annoying and definitly needs to get fixed asap. Some notificaciones are really messed up, like chat notifications that pop up showing a different person (wrong profile and name, happens on whatsapp and Telegram).
6. Control Center Home features not working: crashes on click, hold.
Click to expand...
Click to collapse
Mine works fine.
7. Battery Drain issue: The 2-day battery effectively lasts half a day. Again: tested with 60Hz and all "recommended battery fixes".
Click to expand...
Click to collapse
After a full day I still have 50% battery, so no problem on mine.
8. Settings button in Control Center requires double tap. A single tap never opens it.
Click to expand...
Click to collapse
Just tested and it worked with 1 tap.
9. Always-On UI not actually "Always On." Again, disabling MIUI Optimizations just makes the phone unusable.
Click to expand...
Click to collapse
Unfortunately I bet Xiaomi did this on purpose to keep Always On Display away from the low-mid end phones, just like the Mi 10 Lite 5G.
11. Missing NFC toggle. Not sure how to even enable it.
Click to expand...
Click to collapse
You mean the NFC icon in control center? I mine was just not enabled. It can be enabled with the "edit" function on the control center.
15. Notifications just don't pop-up! WhatsApp Web can't connect to WA unless it is running in the background. Facebook notifications don't pop up until the app is opened. MIUI just disabled all background apps in an effort to better manage the RAM and Battery, but as we clearly see, it doesn't work.
Click to expand...
Click to collapse
Mine do pop up. Try disabling MIUI optimization for these apps, it's what I did.

TotallyNotAPigeon said:
Regarding some of the issues (I have Redmi Note 10 Pro with global MIUI 12.0.10):
Touch responsivenes does behave strange and fails sometimes. I haven't noticed any stuttering though, the 730G works pretty well for me.
This is very annoying and definitly needs to get fixed asap. Some notificaciones are really messed up, like chat notifications that pop up showing a different person (wrong profile and name, happens on whatsapp and Telegram).
Mine works fine.
After a full day I still have 50% battery, so no problem on mine.
Just tested and it worked with 1 tap.
Unfortunately I bet Xiaomi did this on purpose to keep Always On Display away from the low-mid end phones, just like the Mi 10 Lite 5G.
You mean the NFC icon in control center? I mine was just not enabled. It can be enabled with the "edit" function on the control center.
Mine do pop up. Try disabling MIUI optimization for these apps, it's what I did.
Click to expand...
Click to collapse
Turns out, all the problems I've mentioned are specifically with the Indian version of the Global ROM. We're at 12.0.6.0/12.0.8.0, and they've also removed the option to "disable MIUI Optimazations" from the developer menu. It now requires specifically resetting developer options.

You are correct about disabling MIUI optimization. My advice is don't touch it at all, not even once. I always find that down the road weird things will happen to my phone. Perhaps some problems that you are having, were the result of disabling it, even though you've turned it back on now. If it was me, I'd go for a factory data reset and see what happens.

ushgaga said:
You are correct about disabling MIUI optimization. My advice is don't touch it at all, not even once. I always find that down the road weird things will happen to my phone. Perhaps some problems that you are having, were the result of disabling it, even though you've turned it back on now. If it was me, I'd go for a factory data reset and see what happens.
Click to expand...
Click to collapse
Yeah but if you want to use third party apps like YTVanced or Aurora Store for example disabling MIUI optimization is the only solution

dumbl3 said:
Yeah but if you want to use third party apps like YTVanced or Aurora Store for example disabling MIUI optimization is the only solution
Click to expand...
Click to collapse
Yup I know... that's why it's a bummer.

Almost all the issues that OP stated in his post are true, it also happens to my unit which is the Indonesian unit with MIUI 12.0.4.0.
The most annoying one is the WA & Telegram notification issue, not only they messed up in order but the Action button is also misaligned. Seems like Xiaomi's dev team is not aware of this issue at all. Pretty unprofessional, however, this is what we deserved by buying a Xiaomi phone.
Due to all of these issues which I'm not confident will be solved in a timely manner by their dev team, I already made a post in my local adboard to sell my 1 week old RN 10 Pro and I will just buy the Samsung device again.

ushgaga said:
Yup I know... that's why it's a bummer.
Click to expand...
Click to collapse
You can turn it on after installing ytvanced. Everything is working as it should except vanced pip which I cant seem to activate in gesture navigation

Ratti1999 said:
You can turn it on after installing ytvanced. Everything is working as it should except vanced pip which I cant seem to activate in gesture navigation
Click to expand...
Click to collapse
Yepp, I installed Vanced and enabled MIUI optimization ( I needed of for files uploading). Vanced is working great. I am using navigation buttons as I am not huge fan of gestures.

dumbl3 said:
Yeah but if you want to use third party apps like YTVanced or Aurora Store for example disabling MIUI optimization is the only solution
Click to expand...
Click to collapse
ushgaga said:
Yup I know... that's why it's a bummer.
Click to expand...
Click to collapse
For YTVanced, just go to the old versions page in the download site of vancedapp.com.
Then manually download the microg for "14.21.54 and above" and install it. MIUI will allow this version to be installed. Then I downloaded YTVanced 14.21.54 and installed and using it.
The only reason I wanted to turn off MIUI optimizations is to install YTVanced, but since this method works, I don't mind anymore.
I know MIUI "optimizations" is a real PITA, but so far there seems to be workarounds for some of the shortcomings.
Once official stable custom roms are available, I'll flash to these. Right now there are 3 custom roms available, but these are newly released. Need to wait and see if others have problems or not. Once the roms are matured enough, then will be worth to migrate.
P.S. - Using Sweet Global 8/128.

motherninja said:
Due to all of these issues which I'm not confident will be solved in a timely manner by their dev team, I already made a post in my local adboard to sell my 1 week old RN 10 Pro and I will just buy the Samsung device again.
Click to expand...
Click to collapse
No need to take drastic measures.
Xiaomi is actually rooter-friendly. They allow official bootloader-unlocking, although the process takes long.
Their phones, especially the Redmi Note series are some of the best value phones you can ever find.
This is more true with this Note 10 Pro. I mean it's using Amoled and 120Hz screen with 8GB RAM and 128GB ROM wirh NFC, 3.5" jack, IR, FM radio and a huge battery. Even other more expensive flagships don't have all at one place. And the combination of features are only available in higher end flagships of other phones which cost so much more.
And let's not forget Samsung's notorious Knox counter. Even wirh Magisk Hide, some bank apps look for this counter and you can't use a rooted phone with bank apps and some other telco-apps. They look for this Knox-counter trips.
Xiaomi community is very active. There are already 3 custom roms available for Sweet. And there will be many to come. So you can already try these new roms and get rid of MIUI "optimizations" completely.
For me, i am waiting for the roms to get ironed out from it's new beginnings and let them mature with any fixes before I change my ROM. Need to make sure everything works properly before jumping ship.

amgreenhawk said:
No need to take drastic measures.
Xiaomi is actually rooter-friendly. They allow official bootloader-unlocking, although the process takes long.
Their phones, especially the Redmi Note series are some of the best value phones you can ever find.
This is more true with this Note 10 Pro. I mean it's using Amoled and 120Hz screen with 8GB RAM and 128GB ROM wirh NFC, 3.5" jack, IR, FM radio and a huge battery. Even other more expensive flagships don't have all at one place. And the combination of features are only available in higher end flagships of other phones which cost so much more.
And let's not forget Samsung's notorious Knox counter. Even wirh Magisk Hide, some bank apps look for this counter and you can't use a rooted phone with bank apps and some other telco-apps. They look for this Knox-counter trips.
Xiaomi community is very active. There are already 3 custom roms available for Sweet. And there will be many to come. So you can already try these new roms and get rid of MIUI "optimizations" completely.
For me, i am waiting for the roms to get ironed out from it's new beginnings and let them mature with any fixes before I change my ROM. Need to make sure everything works properly before jumping ship.
Click to expand...
Click to collapse
By the time I make that post a few weeks ago, my Sweet has been sold in only 1 hour since the ad went online. Currently, I'm back with the Samsung bandwagon (I bought the brand new A52 LTE) and really really happy with it With this great midrange, I did not miss anything from my previous Samsung phone, the S10.
I agree with you, Xiaomi makes good phones with unbeatable hardware specs to performance ratio, but this is the software that we will interact every day with, not the underlying hardware.
Gone are the days I spent countless hours trying every custom ROM available in our beloved XDA forums, now I just want the phone that just works without any major or annoying issue.

varungupta3009 said:
Even though disabling MIUI Optimizations allows you to have a true always on display and brings back the good old native android share menu (with Copy to Clipboard and Nearby Share), it breaks the ROM in many other places:
You cannot open files on any app (File Manager, WhatsApp, Google Drive, etc.) No PDFs or other files will open.
All permissions will be reset.
Touch gestures like 3-finger screenshot will stop working.
Battery will drain extremely fast. (Even faster than it is already draining)
UI will start stuttering more than usual.
I suggest waiting for OTAs until Xiaomi fixes all of the numerous issues with this ROM. I've also compiled a list of all the issues I'm currently facing:
1. Extreme stuttering and exceptionally low touch responsiveness. 60Hz mode is even more unusable. It stutters like a 2010 phone.
2. Notification UI messed up: Actions not aligned properly, Facebook notifications not showing up properly, and don't show up at all. Android 11's 3-way split that gave conversations priority is completely removed!
3. Text Selection Menu (Context Menu) Hijacking: Critical context menu options don't show up in the hijacked menu! I can't format text in telegram without the context menu!
4. Share Menu Hijacking: Does not have the Copy to Clipboard or Nearby Share options, making it effectively useless. Need to swipe about 100 times to get to the app I want.
5. Disabling MIUI Optimizations fixes [4], but then we can't open any files in the OS! PDFs, Excel Sheets, nothing open! (Permission Denied).
6. Control Center Home features not working: crashes on click, hold.
7. Battery Drain issue: The 2-day battery effectively lasts half a day. Again: tested with 60Hz and all "recommended battery fixes".
8. Settings button in Control Center requires double tap. A single tap never opens it.
9. Always-On UI not actually "Always On." Again, disabling MIUI Optimizations just makes the phone unusable.
10. Proximity sensor just doesn't work. I think it uses heuristics based on mobile orientation and top-speaker ultrasound, but yeah, that definitely needs to be fixed.
11. Missing NFC toggle. Not sure how to even enable it.
12. Magnetometer incorrect readings: it sometimes works, sometimes doesn't. Probably a software issue.
13. Gestures don't work at all in third party launchers and literally make the phone impossible to control without the three nav buttons, which is scary.
14. Auto-rotate doesn't work as expected: Even after rotating the phone, it needs an extra wiggle and a tilt forward to activate it.
15. Notifications just don't pop-up! WhatsApp Web can't connect to WA unless it is running in the background. Facebook notifications don't pop up until the app is opened. MIUI just disabled all background apps in an effort to better manage the RAM and Battery, but as we clearly see, it doesn't work.
16. Google Discover on MIUI Launcher glitches out of bounds.
17. Add a white border instead of black border when the front camera is in use. The black border is hardly noticeable when the front camera is being used.
This list is still pretty incomplete, but I hope they start working on at least these first.
Click to expand...
Click to collapse
I wanna install third party apk it's safe from disable miui optimization and re enable it (just disable for install the apk)

dumbl3 said:
Yeah but if you want to use third party apps like YTVanced or Aurora Store for example disabling MIUI optimization is the only solution
Click to expand...
Click to collapse
Please how can I disable MIUI optimization? I'm using Redmi note 10 pro 128/8

YTVanced is working with activated optimization on my Redmi Note 10pro SKFEUXM13.0.15.0
Bootloader locked, not rooted.

Extend your battery life - Smart debloat and optimize (works too on all S20, S21 and S22, except S22U).

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ and 5 (works on ONE UI 5 too)

Hey,
I tried running the script as admin, but kept getting several "cannot find path specified" errors. it also was unable to bring up the detected device and firmware. I have a Japanese carrier S21 with the model number SC-51B running OneUI 4.1. Is there anything I could do to get this to work?
Thanks

Snylon said:
Hey,
I tried running the script as admin, but kept getting several "cannot find path specified" errors. it also was unable to bring up the detected device and firmware. I have a Japanese carrier S21 with the model number SC-51B running OneUI 4.1. Is there anything I could do to get this to work?
View attachment 5783255
Thanks
Click to expand...
Click to collapse
Snylon said:
Hey,
I tried running the script as admin, but kept getting several "cannot find path specified" errors. it also was unable to bring up the detected device and firmware. I have a Japanese carrier S21 with the model number SC-51B running OneUI 4.1. Is there anything I could do to get this to work?
View attachment 5783255
Thanks
Click to expand...
Click to collapse
Try run as non admin. Some users are reporting this issue when try run as admin.

When I run it as non admin, it enables the adb server but gets stuck on waiting for the phone.
Edit: It works now and I'm not too sure what I did to get it work lol

You should make it a Powershell script by default. I've been using .bat files in Powershell without issue for years.

You should mention it will uninstall Samsung Internet Browser. Unfortunately, was my default browser and i lost everything...

Thank you for this. Since the Android 13 OneUI 5 update, my standby battery life has been horrible. This did help a little and it definitely slimmed down on the software and excessive services which is even better.
Referencing what @bosaad21 stated, the script removed more than what was in the description. It removed quite a bit of the Samsung ware such as Internet, Samsung Accounts, etc on my phone, but I may have done something different and am not aware. Personally, I loved the fact that it stripped out so much stuff. I like a slim OS. I only have this phone because of BOGO.
For those of you wanting to try this, if you know what you are doing, you can modify the scripts that come with the download to prevent unintallation of specific items. However, like mentioned by OP most things can be reinstalled. This is a great option if you are starting fresh after a factory reset.

Is there anyway somebody could provide a more comprehensive list of what software is removed? I would really like to use the script and debloat, and I'm more than willing to part with some Samsung applications (like Samsung Internet, Samsung Pay, Samsung Pass, Samsung Free, Galaxy Store, etc.), but I am not on a factory reset device so I have some reservations. I do use things like Samsung Biometrics (fingerprint scanner) and Samsung Accounts as well as the default system's Phone, Contacts, and Voicemail apps, so I'm not sure I could part with them too hastily. Though I have made the switch to non-Samsung Browser, Email, SMS, Password Manager, File Manager, Keyboard, Notes, Music, and Gallery so I may be overthinking. I'd greatly appreciate any advice or more detailed information!

danilomazzaro said:
View attachment 5782465
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ and 5 (works on ONE UI 5 too)
Click to expand...
Click to collapse
danilomazzaro said:
View attachment 5782465
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ and 5 (works on ONE UI 5 too)
Click to expand...
Click to collapse
FINALLY! A script that's intuitive and fool-proof. Thank you very much. Phone is already snappier and cleaner. <thumbs up>

Thanks for this, dev It has worked a treat on my S21 5G

Hello my samsung galaxy s21 is one ui 5.1 can you use script ?

My s21 didn't have any debloat. Only the settings that I tested and adjusted myself are used there. SOT made 100% on WiFi. I think that it is still possible to squeeze out of it at least 10h and 30min SOT
#Edit: The refresh rate is set to "60Hz standard" + auto brightness at all times. The energy saving is turned on at the level of 30% (after about 2 months of using the phone since my last big changes in actuall configuration... I'm propably raise only ther value at 40%). Since I managed to master very high power consumption this device with the screen off - the phone for 10 hours lying on the cabinet and not even touched at all (had done 94% of the time in Deep Sleep mode) - For these 10 hours my S21 drained the battery about 20%! Now The current consumption in DS mode ranges from 0.4% / h to 0.7% / h.
And something unrealible happened in this equipment.... Which has such a small battery, relative to how much energy it consumes...
Warning! - Im started to charge S21 every two days and at this have 3-4h SOT.

Does it work on one ui 5.1? Thk u

linternaute said:
Does it work on one ui 5.1? Thk u
Click to expand...
Click to collapse
Yes, it works well on one UI 5.1

wlodar1234 said:
My s21 didn't have any debloat. Only the settings that I tested and adjusted myself are used there. SOT made 100% on WiFi. I think that it is still possible to squeeze out of it at least 10h and 30min SOT
#Edit: The refresh rate is set to "60Hz standard" + auto brightness at all times. The energy saving is turned on at the level of 30% (after about 2 months of using the phone since my last big changes in actuall configuration... I'm propably raise only ther value at 40%). Since I managed to master very high power consumption this device with the screen off - the phone for 10 hours lying on the cabinet and not even touched at all (had done 94% of the time in Deep Sleep mode) - For these 10 hours my S21 drained the battery about 20%! Now The current consumption in DS mode ranges from 0.4% / h to 0.7% / h.
And something unrealible happened in this equipment.... Which has such a small battery, relative to how much energy it consumes...
Warning! - Im started to charge S21 every two days and at this have 3-4h SOT.
Click to expand...
Click to collapse
Advanced battery saving?

tinko975 said:
Advanced battery saving?
Click to expand...
Click to collapse
Adaptive power saving I turned off. For me, this feature lived its life and eventually I stopped using it completely. I only set the rule to enable energy saving from 40%, and at night - from 23:00 to 5:00 in the morning.

Does it works on s21+ exynos ?

vonPera said:
Does it works on s21+ exynos ?
Click to expand...
Click to collapse
Yes, it works. I'm using on S21 Exynos too.

But im using S21 plus (G996B), does it work as well or it could do something wrong ?
danilomazzaro said:
Yes, it works. I'm using on S21 Exynos too.
Click to expand...
Click to collapse

Hi, I tried your script but I get "Not installed or already uninstalled!" for every app... Do you have an idea why it happens?

[ROM][A13][OFFICIAL] OctaviOS

Courtesy of @erikdrozina - he is the Developer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OctaviOS is an AOSP-based ROM focusing on unique and smooth UI
with handy features.
OctaviOS is a reborn of Pie-based PearlOS.
​
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROM and/or kernel.
* You do this at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
​
CLEAN FLASH :
​• download and flash OrangeFox recovery
• go to the recovery, then wipe Dalvik/Art Cache, Cache, System, Data, Product and Vendor partitions. After this format Data partition and reboot to recovery
• flash the ROM
• (optional) if you flashed Vanilla version, you can flash GApps package (MindTheGapps recommended)
• (optional) flash Magisk and Disable Force-Encyrption (DFE)
• reboot to system
NOTE: If you are coming from Android 10, flash MIUI with Android 11 before starting
DOWNLOAD VANILLA
DOWNLOAD GAPPS
MIRROR
​• LineageOS
• AOSP
• SuperiorOS
• Pixel Experience
• ExtendedUI
• HavocOS
• CrDroid
• FluidOS
• others that I forgot to mention
OctaviOS Source
Telegram General Group
Telegram Device Group
Telegram Device Channel
REPORTING BUGS
As soon as the problem occurs, take a logcat!
How to take logs:
1) use an app like Matlog (root needed), start recording in the app, reproduce the bug, save the result in the app and share it in a post here or on the Telegram Device Group
2) from the PC: use adb logcat > log.txt command, reproduce the bug and then share the log.txt file
How to get ramoops:
• reboot to recovery before booting into system again
• open the terminal in the recovery
• type in the terminal cat /sys/fs/store/console-ramoops-0 > /sdcard/ramoops.txt
• boot into system and share the ramoops.txt that you'll find in the storage root folder
OctaviOS for Xiaomi Mi Note 10/Pro
Device Codename: tucana
Maintainer: @erikdrozina
Build Type: Official
Device Tree
Kernel Source
ROM OS Version: 13
ROM Kernel: Linux 4.14.299 (Phobos)
ROM Firmware Required: Must be at least 12.5.4
Based On: AOSP
VERSION INFORMATION
Status: Stable
Current stable version: 4.4
Build Date: 22/05/2023
Size: 1.4 GB | 1.7 GB
Source changelog: here
SELinux status: Enforced

KNOWN BUGS/ISSUES:
fingerprint dialog mismatches the actual fingerprint scanner position
Octavi Lab > Miscellaneous > Force stop button disables itself
clock padding on status bar is shifted. If you are rooted, you can change it with LSPosed and AOSP Mods module
if you face battery drain by Google Play Services, try to execute this shell commands (with root):
su
pm disable com.google.android.gms/.chimera.GmsIntentOperationService

What a surprise! I had to fix a Tucana of a friend this weekend, had told him there wasn't much going on for the device, but to experiment running 3rd party ROMs for a while (reluctantly he'd rather stay on MIUI with a locked bootloader).
Since the bootloader was unlocked and you guys had posted this but 2 days ago I decided to give it a spin momentarily, so these are my thoughts:
- Very nice out of the box I must say, went with the version that has GApps built in already (and thank god for that MEGA mirror, Plink wasn't cooperative).
- Installation procedure following the instructions was uneventful, rather confused about needing to format the data partition 2 times, but OK.
- The recovery though... damn, if at all possible perhaps you could try building or re-building any version of it moving forward. The current build of OrangeFox, while functional, does things on the background that I wasn't keen on, and for some reason I couldn't find a way to flash images directly through it! For example, after the Magisk app was installed in the OS and the boot image extracted and patched, I rebooted to the recovery to flash it to boot: no dice. The thing kept on thinking it was a ZIP (dafuk?) so I ended up booting directly from a TWRP build (which as opposed to OFox couldn't decrypt data) to flash the magisk patched boot image.
- Thank God for that Monet override of sorts allowing users to choose a basic color accent
- I didn't see any way to revert from the gesture based navigation to the traditional buttons, is it supported? (just curious, providing an alternative would be nice)
Now for bugs or unusual behaviors:
- Something odd was happening at the beginning in the battery section of settings, look at the following screenshot for more info (no logs, sorry, and it works as expected now, that was more or less right after installation):
Spoiler: Screenshot
- At least some WiFi icons for the statusbar need revisiting, the different stages don't match, look at Xperia's for example:
Spoiler: Screenshot
- The default home app doesn't seem to have permission to display dots over app icons by default from notifications. I wonder if it is at all possible to enable it out of the box, in other devices I've seen some bizarre defaults that leads me to believe it may not be (like... the camera app not having the Camera and Mic permissions enabled, how the hell is it supposed to work otherwise?! )
Spoiler: Screenshot
- I had chosen a different shape for the icons, Teardrop, however after configuring the home screen and drawer through its setting it was reverted back to the default round shape. Perhaps it's not worth looking into since after a reboot of the device my chosen one was applied.
- It was in Magisk and due to the nature of it I couldn't capture a screenshot, but the authentication through fingerprint dialog had the fingerprint icon displayed lower than it should have been. The light and the sensor itself was somewhere half-way up that icon. I wonder if it's app specific or the authentication dialog is baked into the OS and would need to be tweaked, I'm just mentioning it just in case
- The camera app as it is pinned in the lower row of icons of the home screen doesn't work, it may refer to some other package that is not installed because tapping over it by default a toast message appears indicating the app is not installed. Opening it through the drawer worked as expected.
Talking of which... damn that's some barebones app, there's not even an option to choose which camera sensor you want to take the picture from, much less other advanced options. I'd think about replacing it with something more functional. LieageOS' Apperture should be better while still being basic.
Also, I think even in the GApps package having a basic gallery app besides Google's Photos would be nice, something lightweight perhaps, like QuickPic or its mod: https://github.com/WSTxda/QP-Gallery-Releases
I haven't tested the vanilla version of the ROM, but the GApps one was OK, it's nice to see new things coming for Tucana users and I was pleased to see the dialer not being Google's, don't get me wrong, Google's is very nice, but the lack of an option to record a phone call is a pity.

KaoDome said:
What a surprise! I had to fix a Tucana of a friend this weekend, had told him there wasn't much going on for the device, but to experiment running 3rd party ROMs for a while (reluctantly he'd rather stay on MIUI with a locked bootloader).
Since the bootloader was unlocked and you guys had posted this but 2 days ago I decided to give it a spin momentarily, so these are my thoughts:
- Very nice out of the box I must say, went with the version that has GApps built in already (and thank god for that MEGA mirror, Plink wasn't cooperative).
- Installation procedure following the instructions was uneventful, rather confused about needing to format the data partition 2 times, but OK.
- The recovery though... damn, if at all possible perhaps you could try building or re-building any version of it moving forward. The current build of OrangeFox, while functional, does things on the background that I wasn't keen on, and for some reason I couldn't find a way to flash images directly through it! For example, after the Magisk app was installed in the OS and the boot image extracted and patched, I rebooted to the recovery to flash it to boot: no dice. The thing kept on thinking it was a ZIP (dafuk?) so I ended up booting directly from a TWRP build (which as opposed to OFox couldn't decrypt data) to flash the magisk patched boot image.
- Thank God for that Monet override of sorts allowing users to choose a basic color accent
- I didn't see any way to revert from the gesture based navigation to the traditional buttons, is it supported? (just curious, providing an alternative would be nice)
Now for bugs or unusual behaviors:
- Something odd was happening at the beginning in the battery section of settings, look at the following screenshot for more info (no logs, sorry, and it works as expected now, that was more or less right after installation):
Spoiler: Screenshot
View attachment 5841027
- At least some WiFi icons for the statusbar need revisiting, the different stages don't match, look at Xperia's for example:
Spoiler: Screenshot
View attachment 5841029
- The default home app doesn't seem to have permission to display dots over app icons by default from notifications. I wonder if it is at all possible to enable it out of the box, in other devices I've seen some bizarre defaults that leads me to believe it may not be (like... the camera app not having the Camera and Mic permissions enabled, how the hell is it supposed to work otherwise?! )
Spoiler: Screenshot
View attachment 5841035
- I had chosen a different shape for the icons, Teardrop, however after configuring the home screen and drawer through its setting it was reverted back to the default round shape. Perhaps it's not worth looking into since after a reboot of the device my chosen one was applied.
- It was in Magisk and due to the nature of it I couldn't capture a screenshot, but the authentication through fingerprint dialog had the fingerprint icon displayed lower than it should have been. The light and the sensor itself was somewhere half-way up that icon. I wonder if it's app specific or the authentication dialog is baked into the OS and would need to be tweaked, I'm just mentioning it just in case
- The camera app as it is pinned in the lower row of icons of the home screen doesn't work, it may refer to some other package that is not installed because tapping over it by default a toast message appears indicating the app is not installed. Opening it through the drawer worked as expected.
Talking of which... damn that's some barebones app, there's not even an option to choose which camera sensor you want to take the picture from, much less other advanced options. I'd think about replacing it with something more functional. LieageOS' Apperture should be better while still being basic.
Also, I think even in the GApps package having a basic gallery app besides Google's Photos would be nice, something lightweight perhaps, like QuickPic or its mod: https://github.com/WSTxda/QP-Gallery-Releases
I haven't tested the vanilla version of the ROM, but the GApps one was OK, it's nice to see new things coming for Tucana users and I was pleased to see the dialer not being Google's, don't get me wrong, Google's is very nice, but the lack of an option to record a phone call is a pity.
Click to expand...
Click to collapse
Thanx for the report.
True, tucana community is rather small and at the moment there are only two active developers for that device. But most of the things is happening on Telegram these days (links are given in the OP).
As I'm not the developer, just the tester, I can refer to only some of the issues you have mentioned (maybe the dev will elaborate later).
Actually second Data format is not obligatory, not harmful though but I'll probably remove it from the guide.
I'm pretty sure there is a way to flash .img files in OrangeFox... but I don't have tucana with me right now to check. Anyway, to install Magisk you can simply flash it in recovery. I realize it's not the recommended method now, but in case of tucana it's absolutely fine, working without any issue.
Navigation types should be found in Settings > System > Gestures.
As for permission, I think it's new Google policy introduced in Android 13. They limit permissions as much as possible and even those really needed aren't granted automatically. Actually things involved with privacy are getting more and more difficult with every Android release, not only for users, but for the app developers as well...
Stock camera app is very simple indeed, I think it's a conscious choice, but you can always find good alternatives supporting other lenses. There are good-working GCams with polished XML configs, there are also MIUI Camera ports, but much less perfect. If you have Telegram account, you can find more about camera things here:
Camera group: @minote10photography
APK channel: @minote10apk
XML channel: @minote10xml
Fingerprint dialog mismatch is a known issue and it's present on other devices as well. Probably fixable, we'll see. There are some other minor glitches like those you mentioned, hopefully they will be adressed in the next releases.
Generally the ROM is well done, allowing tucana get a second breath

Not a problem! I testdrove it for a bit and thought it would be good to report back so it keeps getting better, like you said, it seems the Tucana community isn't very engaged since many moved on to a different device. Even the one of my friend had its battery already capable to hold only 52% of what it could at the beginning
Lord Sithek said:
Actually second Data format is not obligatory, not harmful though but I'll probably remove it from the guide.
Click to expand...
Click to collapse
I followed it to the letter, since the phone wasn't mine and I just wanted to toy with it for a bit, but perhaps formatting data once (before booting into the system maybe?) is enough.
Lord Sithek said:
I'm pretty sure there is a way to flash .img files in OrangeFox... but I don't have tucana with me right now to check. Anyway, to install Magisk you can simply flash it in recovery. I realize it's not the recommended method now, but in case of tucana it's absolutely fine, working without any issue.
Click to expand...
Click to collapse
For the life of me, I wasn't able to do it on the current OrangeFox release for Tucana (11.1_3?), in other devices yes, there are ways to directly flash raw data to partitions, but not here. In any case, after the boot image is patched it could also be flashed via `fastboot`; I'm not a fan of recovery flashing Magisk to be honest, if at all possible I'd like all modifications to be systemlessly in my devices.
Lord Sithek said:
Navigation types should be found in Settings > System > Gestures.
Click to expand...
Click to collapse
So that's where it was!
Lord Sithek said:
As for permission, I think it's new Google policy introduced in Android 13. They limit permissions as much as possible and even those really needed aren't granted automatically. Actually things involved with privacy are getting more and more difficult with every Android release, not only for users, but for the app developers as well...
Click to expand...
Click to collapse
That's what I thought, but I've never built an Android distribution before, for me the default state should be consistent, sane, and functional; for me it's the whole experience what makes or breaks a product, something polished grows on me, means attention to detail.
For example, the camera app in some distros that goes without camera and mic permissions by default, seriously guys... what the hell, I *really* dislike having to spend serious time after the first boot to check and set basic things like that. I get the privacy argument, but surely everyone expects the camera app to just show pictures after tapping on it going with the example.
And if it can't be done, well... more patched to Android that are needed to make it so haha, many inbox apps ship with some permissions enabled by default.
Lord Sithek said:
Stock camera app is very simple indeed, I think it's a conscious choice, but you can always find good alternatives supporting other lenses. There are good-working GCams with polished XML configs, there are also MIUI Camera ports, but much less perfect.
Click to expand...
Click to collapse
I hope it wasn't a conscious decision and it's something that was kind of the default with the current base of the ROM and still wasn't changed, the one that's shipped right now doesn't do anybody any favors. I know there are alternatives, even in the Play Store there are plenty of camera apps, but it's the same as before: sane defaults. This device, for example, has what, 3 sensors + the macro one? And the default app uses just one of them without possibility of choosing? It may not be a big deal for many perhaps, but I think it's big enough for others to look somewhere else.
Lord Sithek said:
Fingerprint dialog mismatch is a known issue and it's present on other devices as well. Probably fixable, we'll see. There are some other minor glitches like those you mentioned, hopefully they will be adressed in the next releases.
Generally the ROM is well done, allowing tucana get a second breath
Click to expand...
Click to collapse
¡Oh! So it's a known issue an happens in other devices too? Damn... perhaps something to do with the layout? Since I was using the default gesture navigation the height of the button navigation bar wasn't present, maybe that's the thing that needs to be taken into account.
And I completely agree! Granted I didn't use the phone with OctaviOS that much (some 3 hours perhaps), but it was a pleasant experience, I think it can only get better from here with some dedication so congrats for all involved!
As for Telegram, I do use it, but I don't really have a Tucana so those groups aren't useful to me (I wouldn't be able to provide feedback on anything or try stuff) and since my friend wanted pure MIUI (not even Xiaomi.eu's) with a locked bootloader won't be of any help either hahaha but I wish Tucana users the best

Hi,
great rom, my MI 10 feels like a new modern phone now, thank you very much for development!
Everything works fine, except...
- camera crashed -> installed gcam port, not a problem any more...
- bluetooth volume is far too low, PLEASE tell me how to fix this issue. Tried development setting, but volume is still far too low. Any idea?
Thank's!

...seems to be an Apple Airphone problem, JBL box works fine...

jenzii said:
Hi,
great rom, my MI 10 feels like a new modern phone now, thank you very much for development!
Everything works fine, except...
- camera crashed -> installed gcam port, not a problem any more...
- bluetooth volume is far too low, PLEASE tell me how to fix this issue. Tried development setting, but volume is still far too low. Any idea?
Thank's!
Click to expand...
Click to collapse
Camera has always been a problem on this device for custom ROMs, but there are good GCam alternatives. You can also try to install MIUI Camera port called ANX, but there are some flaws

Thank you for this really very successful ROM. So far I haven't noticed any problems, except the camera which has problems on every custom rom with this smartphone! The interface is fast, and battery life is good.

Hi, thanks for this great ROM. Is UDFPS working for you ? Sadly it's not for me.

spOOk42 said:
Hi, thanks for this great ROM. Is UDFPS working for you ? Sadly it's not for me.
Click to expand...
Click to collapse
Yes, it works for me

spOOk42 said:
Hi, thanks for this great ROM. Is UDFPS working for you ? Sadly it's not for me.
Click to expand...
Click to collapse
It should work without AoD enabled, with AoD it struggles

Lord Sithek said:
It should work without AoD enabled, with AoD it struggles
Click to expand...
Click to collapse
Yes it is, but I don't want to use AoD.

Great OS, is there a setting for gesture control that allows swiping in the top half of the Phone in order to use in App functions such as opening the menu instead of only getting backwards?

philp97 said:
Great OS, is there a setting for gesture control that allows swiping in the top half of the Phone in order to use in App functions such as opening the menu instead of only getting backwards?
Click to expand...
Click to collapse
Not in the system, but you can control gestures bar height with AOSP Mods LSPosed module

Has this rom italian language? Thanks.

tucanuser said:
Has this rom italian language? Thanks.
Click to expand...
Click to collapse
Yes, this ROM has the Italian language.

Are there any new bugs compared to previous builds based on A12 ? Are Face unlocking, NFC, otg AOD, fingerprint, VOLTE, quick charge 18w working?

Amrch787 said:
Are there any new bugs compared to previous builds based on A12 ? Are Face unlocking, NFC, otg AOD, fingerprint, VOLTE, quick charge 18w working?
Click to expand...
Click to collapse
I did not have any particular bugs to note. Fast charging works up to 30W, fingerprint and face unlock works, NFC too, VOLTE too, OTG too, and AOD too.

1.What is latest build security patch date?
2. Is google pay working?
3. Is OTA supported? And when doing update apps settings are not changed?
4. Any bugs?