GUIDE: fine-tuning performance and battery for your S7 or S7 Edge - Verizon Samsung Galaxy S7 Guides, News, & Discussi

This is a follow-up post to my GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Verizon Galaxy S7
So you want even better performance and battery life than what I include in my flashable update package and in my deep debloat flashable update package? Not afraid to get your hands dirty with more hands-on config? Not afraid to fork over a few dollars to get the nice root apps we need to do so? Well okay then, let's dive in!
Disclaimer: You tweak your phone at your own risk, even if you follow my guide exactly. If something doesn't work right for you or you have problems, feel free to report it so I can modify my guide accordingly, but I'm not offering anyone specific support or help with any of this process. This is just what I do to make my phone that much more optimized.
{
"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"
}
Apps you'll need:
Android Google Play Store apps you'll need:
Amplify (including in-app pro activation)
ForceDoze (free)
Greenify (including pro package)
L Speed [ROOT] (free)
LeanDroid (including in-app pro activation)
Android Xposed modules you'll need:
Amplify (installed via Play Store app)
Greenify (installed via Play Store app)
(don't forget to activate Xposed modules after you've installed them, then reboot your phone)
Additionally, you'll need the Xposed framework installed and functional. Check my root guide under Recommended Next Steps if you need help with that.
You'll notice that I don't use any task managers (with the slight exception of Greenify, but it's going to be set up to deep-sleep apps, not kill them). You'll also notice I don't use any CPU tweaking apps -- the default settings from our carrier does really well and are persistently set by my flashable update package anyway.
Configuring Android
Note: all of the changes in this section will be in your device's main settings.
Note: on my Verizon Galaxy S7, I use the 'Global' preferred network node (under 'Mobile networks'). Others have recommended LTE/GSM/UMTS instead -- use whichever works best for your device.
Tap on Wireless and networks: More. Tap on Nearby device scanning and turn it off.
Tap on Phone: Display and wallpaper. Tap on Always on Display and turn it off. If the AODService [com.samsung.android.app.aodservice] package is uninstalled or frozen, it should already be off.
Tap on Personal: Location. Enable Location if it's turned off so that you can tap on Improve accuracy and turn both Wi-Fi scanning and Bluetooth scanning off. Turn Location back off if you like. I only enable Location when I need it. Still in the Location settings, tap at the bottom on Google Location History. Tap to turn off Location History.
Tap on System: Developer options (should already be enabled from the root section of my guide). Scroll to three options labeled "Window animation scale", "Transition animation scale", and "Animator duration scale". Set all three to "Animation off".
Configuring Amplify
Note: swipe from the left in this app to get a list of sections.
Settings
Show launcher icon: checked
Choose theme: inconsequential
Service Blocking: checked
Force English: inconsequential
Scroll Item Names: checked
Wakelocks
Note: find the item in the list and tap it to configure, then tap 'ON' under 'SETTINGS' to enable controlling the wakelock, then tap the field immediately under this to configure the throttle for the wakelock.
LocationManagerService: 10 seconds
Icing: 30 seconds
GCoreFlp: 60 seconds
NlpWakeLock: 60 seconds
NetworkStats: 60 seconds
SyncLoopWakeLock: 300 seconds
AudioIn: 240 seconds
NlpCollectorWakeLock: 60 seconds
Wakeful StateMachine: GeofencerStateMachine: 10 seconds
GpsLocationProvider: 1 second
ContextManagerWakeLock: 5 seconds
UlrDispSvcFastWL: 9999999 seconds
RILJ0: 60 seconds
ImsService: 15 seconds
Alarms
Note: find the item in the list and tap it to configure, then tap 'ON' under 'SETTINGS' to enable controlling the alarm, then tap the field immediately under this to configure the throttle for the alarm.
com.android.internal.telephony.data-stall: 60 seconds
com.google.android.gms/.lockbox.LockboxAlarmReceiver: 60 seconds
com.levelup.beautifulwidgets.core.ACTION_REFRESHTIME: 120 seconds throttles the Beautiful Widgets widget refresh time
com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE: 5 seconds
Services
Note: services can either be enabled or disabled entirely, not throttled.
com.google.android/gms/com.google.android.location.reporting.service.DispatchingService: Deny
com.google.android.gms/com.google.android.location.internal.PendingIntentCallbackService: Deny
Configuring ForceDoze
Enable the ForceDoze service.
Settings:
Don't disable sensors on screen off: unchecked
Turn off while charging: unchecked
Auto-rotate/brightness fix: unchecked
Show persistent notification: checked (your preference may vary)
Ignore lockscreen timeout: checked
Whitelist apps: (none)
Disable WiFi during Doze: unchecked
Disable mobile data during Doze: unchecked
Disable motion sensing for Doze: unchecked
Doze delay: 0
(disabled) Enable Doze on unsupported device: unchecked
Disable motion sensing for Doze (root): unchecked
Configuring Greenify
Note: most of the performance savings will come from this app.
Working Mode: Boost if you don't see this option, check Xposed Installer and enable the Greenify module, then reboot -- if the Greenify module isn't there, install it from the Xposed Installer first
Shallow Hibernation (experimental): enabled
Aggressive Doze (experimental): enabled
Xposed-based Features -> Wakeup Timer Coalescing (4.4+): checked
Xposed-based Features -> Telephony Wakeup: checked
Xposed-based Features -> Don't Remove Notifications: checked
Xposed-based Features -> Block App State Abuse: checked
Xposed-based Features -> Deep Hibernation (alpha): unchecked
Xposed-based Features -> GCM push for greenified apps: checked
Xposed-based Features -> Greenifying system apps: unchecked
Xposed-based Features -> Reveal Hidden Sync: unchecked
Now you'll need to add apps you want to Greenify. From the main Greenify menu, click the [+] button at the top of the app. Scroll down and click "Show more apps". I would select almost all apps except the ones that need to automate or update the UI such as widgets, Xposed modules, print services, dialer/phone, alarm clocks, widgets, etc. Some SMS or chat apps may also need to be skipped, but I personally have Hangouts, Facebook, etc. Greenified and I still get instant notifications for new messages and e-mails just fine. Your experience may vary, so spend some time experimenting with what apps you do and don't like put into hibernation when not in direct use.
Configuring L Speed
Note: some options are preferential and should be researched accordingly if you plan on changing them or are curious what they do. For my phone, I've chosen anything that boosts performance for 'free' (no or very negligible battery cost).
L Speed requires the sqlite binaries to be installed to change some settings. I used Sqlite installer for root, which worked fine. BusyBox does not include this binary.
First, go to Menu -> Settings and enable "Use Advanced UI". This will restart the app with a different interface.
From here forward, you can swipe from the left (or use the menu in the upper left) to access different sections.
Settings:
Use Advanced UI: enabled
Dark theme: disabled (preferential)
Color navigation bar: disabled (preferential)
Force English: disabled (preferential)
Show toggle toast: enabled (preferential)
Use Fahrenheit (°F): disabled (preferential)
Apply on boot delay: 5sec
Show boot notification: enabled (preferential)
Main Tweaks:
Kernel Modification -> Kernel Tweaks: Disabled
Kernel Modification -> Kernel sleepers optimization: enabled
System Tweaks -> Battery improvement: enabled
System Tweaks -> Faster boot: enabled
System Tweaks -> WiFi sleeper: disabled
System Tweaks -> Flag tuner: enabled
System Tweaks -> Assertive display: enabled (preferential)
System Tweaks -> Improve scrolling: enabled
System Tweaks -> Liquid smooth UI: enabled (preferential)
Debugging Options -> Disable debugging: enabled (this is unrelated to USB debugging)
Debugging Options -> Disable kernel panic: disabled
Other Tweaks -> Better in call audio: enabled (does not conflict with ViPRE4Android)
Other Tweaks -> Improve image quality: enabled
CPU Tuner:
CPU Tuning -> CPU Optimizer: enabled (does not conflict with my CPU fixes startup script)
LNET Optimizer:
LNET Tweaks -> NET Buffers: Default
LNET Tweaks -> RIL tweaks: disabled
LNET Optimizations -> Google DNS: disabled (preferential)
LNET Optimizations -> Faster streaming: enabled
LNET Optimizations -> Fast dormancy: enabled
IO Tweaks
Storage IO Tweaks -> SD tweak: Light
Storage IO Tweaks -> IO Boost: enabled
Storage IO Tweaks -> IO Extended Queue: disabled
Storage IO Tweaks -> Partition remount: enabled (preferential: gives more permissions to the SD card)
Virtual Memory
Memory Management Tweaks -> OOM Killer: Enabled
Memory Management Tweaks -> Cache Reclaiming: Minimum
Memory Management Tweaks -> Cache Allocation: Medium
RAM Manager
RAM Manager Options -> Ram Manager: Balanced
Seeder
Seeder Options -> Default
Cleaner
Cleaner Options -> Run cleaner on boot: disabled (preferential)
FStrim
FStrim Options -> Run fstrim on boot: disabled (preferential)
Configuring LeanDroid
Note: I only use LeanDroid's features to compliment Do Not Disturb (aka "Blocking Mode") during specific hours. Tasker or other automated programs could do this, but that's a more in-depth guide. Additionally, this setup will add a persistent notification that you can use to pause/unpause LeanDroid or jump to its settings. That notification can be disabled by going into the app, clicking the [...] menu in the top right, and choosing "Hide notification". I like having it there to know it's on and to pause/unpause it if I'm not using Do Not Disturb for some reason.
LeanDroid master on/off switch: enabled
Disable... -> Wi-Fi: checked
Disable... -> Cellular data -- leave it unchecked if you want the phone to be cut off from all data during Do Not Disturb hours / check it if you want it to be blocked
Disable... -> Cellular radio: unchecked
Disable... -> Bluetooth: checked -- unless you feel that Bluetooth connectivity is important during Do Not Disturb hours
Disable... -> Network location: checked -- unless you feel that location availability is important during Do Not Disturb hours
Disable... -> GPS location: checked -- unless you feel that GPS availability is important during Do Not Disturb hours
Switch... -> Cellular network mode to [varies]: unchecked -- you could check this and enable 2G or 3G if you are allowing Do Not Disturb hours to have access to cellular data, but want to restrict it to lower speeds (uses less battery than LTE/4G)
Switch... -> [varies] after screen off [except] -- multiple options here, set it to '5 MIN' after screen off and click 'EXCEPT ->'
EXCEPT-> Except [varies]-[varies] -- time range, I have mine set from 7:00 AM to 11:30 PM because at 11:30 PM is when my Do Not Disturb is enabled on my phone (until 7:00 AM the next day), adjust yours as necessary
EXCEPT-> remaining options: unchecked -- set as desired, but I have them all off
Restore... -> After screen on: selected
Restore... -> After screen unlocked: unselected
Restore... -> Every [varies] after screen off: unchecked -- configure if you want data enabled in short bursts during Do Not Disturb hours
Restore... -> Data after waiting [varies] for Wi-Fi to connect: unchecked
Use these settings in tandem with Samsung's built-in Do Not Disturb on a schedule. Your phone won't hardly touch any battery overnight if left off the charger (unless you're in a really horrible reception area and/or roaming or something -- cellular radio is still active for phone calls).
For example, I charged my phone to full and then unplugged it overnight while I slept. Here's how battery usage looks in the morning:
The radio antenna is left on, so calls, texts, and MMS can come through (but may be silenced depending on your Do Not Disturb settings), but data is strictly prohibited so if you need e-mail or chat alerts, etc., you would want to enable data every X minutes for X minutes. This will increase battery usage slightly, but not by much.
Enjoy!

For Greenify, what do you mean by "Working Mode: Boost"? My only two options are Root and Non-Root. Did you mean Root instead of Boost?

SanguiniusWept said:
For Greenify, what do you mean by "Working Mode: Boost"? My only two options are Root and Non-Root. Did you mean Root instead of Boost?
Click to expand...
Click to collapse
Get the greenify xposed module. Install that too. And reboot. Now the option will be there.

SanguiniusWept said:
For Greenify, what do you mean by "Working Mode: Boost"? My only two options are Root and Non-Root. Did you mean Root instead of Boost?
Click to expand...
Click to collapse
cuezaireekaa said:
Get the greenify xposed module. Install that too. And reboot. Now the option will be there.
Click to expand...
Click to collapse
Updated my guide to reflect the Greenify Xposed module neceessity, thanks @cuezaireekaa

Good to know. Haven't installed Xposed yet. I was trying to get some battery life and performance baselines before I get that far.

SanguiniusWept said:
Good to know. Haven't installed Xposed yet. I was trying to get some battery life and performance baselines before I get that far.
Click to expand...
Click to collapse
You're gonna be able to tweak your battery best once you have xposed installed. The two main battery saving apps, greenify, and amplify rely heavily on xposed. Painless process, but if you don't feel comfortable, re read things and go slowly because there is gonna be maintenance when tweaking this hard. ;P
Have fun, and keep full stock firmware for your specific device handy on your PC just in case bootloops

Any idea of performance gain and battery gain?

cuezaireekaa said:
You're gonna be able to tweak your battery best once you have xposed installed. The two main battery saving apps, greenify, and amplify rely heavily on xposed. Painless process, but if you don't feel comfortable, re read things and go slowly because there is gonna be maintenance when tweaking this hard. ;P
Have fun, and keep full stock firmware for your specific device handy on your PC just in case bootloops
Click to expand...
Click to collapse
It's not at all a case of wariness. I've used Xposed for years, first on a Droid Bionic and then on my S5. I have every intention of putting Xposed on my S7, but I'm taking it slow so I can basically have a bit of a "changelog" on my phone. I'll probably put it on in a few days, after I know everything I need to know about my current performance profiles. Thanks for the concern and the info

downhillvinnie said:
Any idea of performance gain and battery gain?
Click to expand...
Click to collapse
Here's a sample video I recorded on my phone (720p @ 30fps)... even recording didn't slow it down, so this video is a fairly decent preview of the kind of performance/responsiveness I'm getting. I took the video for a friend and didn't edit it so it's kind of all over the place as far as personal data and random clicking but you'll get the idea.
As far as battery goes, the thing doesn't use hardly any battery if I'm not touching it. On standby, it could go days. Since I've been developing and testing stuff (and it's my daily phone), it never gets to sit that long, but for example it uses about 1% battery overnight while I sleep and probably 1-2% battery per hour during non-blocking/LeanDroid hours.
(keep the laughter of my cheesy game selection to a minimum, bwahaha)

psouza4 said:
Here's a sample video I recorded on my phone (720p @ 30fps)... even recording didn't slow it down, so this video is a fairly decent preview of the kind of performance/responsiveness I'm getting. I took the video for a friend and didn't edit it so it's kind of all over the place as far as personal data and random clicking but you'll get the idea.
As far as battery goes, the thing doesn't use hardly any battery if I'm not touching it. On standby, it could go days. Since I've been developing and testing stuff (and it's my daily phone), it never gets to sit that long, but for example it uses about 1% battery overnight while I sleep and probably 1-2% battery per hour during non-blocking/LeanDroid hours.
(keep the laughter of my cheesy game selection to a minimum, bwahaha)
Click to expand...
Click to collapse
Sent from my SM-G930V using XDA-Developers mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
downhillvinnie said:
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock i thought was retty good
Sent from my SM-G930V using XDA-Developers mobile app

downhillvinnie said:
Sent from my SM-G930V using XDA-Developers mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Stock i thought was retty good
Click to expand...
Click to collapse
Can only get better from there -- love it when the highest battery drain is the screen!

When I try to donate to get the pro features in Amplify, the Play Store unexpectedly quits. After reviewing your rooting guide, the one thing I missed (or noticed I missed...) was to enable su at boot, which I have now done and rebooted. I'm on S7 regular, and used your fix+debloat.
Update: I am trying to bill my Verizon account, I'm betting the debloat disabled the Verizon checking...
nope... using a credit card crashes too

pbaird said:
When I try to donate to get the pro features in Amplify, the Play Store unexpectedly quits. After reviewing your rooting guide, the one thing I missed (or noticed I missed...) was to enable su at boot, which I have now done and rebooted. I'm on S7 regular, and used your fix+debloat.
Update: I am trying to bill my Verizon account, I'm betting the debloat disabled the Verizon checking...
nope... using a credit card crashes too
Click to expand...
Click to collapse
I'm also getting a FC when attempting to donate for the pro features in Amplify.
Edited to add: I also tested LeanDroid's in-app purchase and got the same result. I'm wondering if something with the de-bloat removed a service component?

pbaird said:
When I try to donate to get the pro features in Amplify, the Play Store unexpectedly quits. After reviewing your rooting guide, the one thing I missed (or noticed I missed...) was to enable su at boot, which I have now done and rebooted. I'm on S7 regular, and used your fix+debloat.
Update: I am trying to bill my Verizon account, I'm betting the debloat disabled the Verizon checking...
nope... using a credit card crashes too
Click to expand...
Click to collapse
kansaswaldo said:
I'm also getting a FC when attempting to donate for the pro features in Amplify.
Edited to add: I also tested LeanDroid's in-app purchase and got the same result. I'm wondering if something with the de-bloat removed a service component?
Click to expand...
Click to collapse
Potentially... what does logcat say?

psouza4 said:
Potentially... what does logcat say?
Click to expand...
Click to collapse
Reviewing logcat, the most noticeable error is as follows:
07-14 09:56:58.635 E/labHelper(17750): In-app billing error: Null data in IAB activity result.
If you want, I can post the entire log.

What about the force close exception details?

Best way to view and save logcat? I just tried alogcat, but I'm seeing much.
Update - downloaded logcat extreme, lets you do app specific. I'm attaching google play store results.

psouza4 said:
What about the force close exception details?
Click to expand...
Click to collapse
Is this helpful? I also included the entire log as an attachment.
(22728): Shutting down VM
07-14 10:20:12.529 E/AndroidRuntime(22728): FATAL EXCEPTION: main
07-14 10:20:12.529 E/AndroidRuntime(22728): Process: com.ryansteckler.nlpunbounce, PID: 22728
07-14 10:20:12.529 E/AndroidRuntime(22728): java.lang.NullPointerException: Attempt to invoke interface method 'android.os.Bundle com.android.vending.billing.IInAppBillingService.getBuyIntent(int, java.lang.String, java.lang.String, java.lang.String, java.lang.String)' on a null object reference
07-14 10:20:12.529 E/AndroidRuntime(22728): at com.ryansteckler.inappbilling.IabHelper.launchPurchaseFlow(IabHelper.java:394)
07-14 10:20:12.529 E/AndroidRuntime(22728): at com.ryansteckler.inappbilling.IabHelper.launchPurchaseFlow(IabHelper.java:346)
07-14 10:20:12.529 E/AndroidRuntime(22728): at com.ryansteckler.nlpunbounce.HomeFragment$5.onClick(HomeFragment.java:532)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.view.View.performClick(View.java:5697)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.view.View$PerformClick.run(View.java:22526)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.os.Handler.handleCallback(Handler.java:739)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.os.Handler.dispatchMessage(Handler.java:95)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.os.Looper.loop(Looper.java:158)
07-14 10:20:12.529 E/AndroidRuntime(22728): at android.app.ActivityThread.main(ActivityThread.java:7224)
07-14 10:20:12.529 E/AndroidRuntime(22728): at java.lang.reflect.Method.invoke(Native Method)
07-14 10:20:12.529 E/AndroidRuntime(22728): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
07-14 10:20:12.529 E/AndroidRuntime(22728): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
07-14 10:20:12.529 E/AndroidRuntime(22728): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
07-14 10:20:12.529 I/PersonaManager(1419): mKnoxInfo is empty
07-14 10:20:12.529 W/ActivityManager(1419): Force finishing activity com.ryansteckler.nlpunbounce/.MaterialSettingsActivity
07-14 10:20:12.529 W/VirtualScreenManagerService(1419): failed to move task TaskRecord{50e1bc9 #2078 A=com.ryansteckler.nlpunbounce U=0 sz=1}
07-14 10:20:12.529 W/VirtualScreenManagerService(1419): moveTaskBackToDisplayIfNeeded(): top activity or app is null
07-14 10:20:12.529 D/FocusedStackFrame(1419): Set to : 0
07-14 10:20:12.539 D/InputDispatcher(1419): Focused application set to: xxxx
07-14 10:20:12.539 D/InputDispatcher(1419): Focus left window: 22728
07-14 10:20:12.539 D/PointerIcon(1419): setMouseIconStyle1 pointerType: 1001 iconType:101 flag:0 pid:1419 uid:1000
07-14 10:20:12.539 D/PointerIcon(1419): setMouseCustomIcon IconType is same.101
07-14 10:20:12.559 E/android.os.Debug(1419): ro.product_ship = true
07-14 10:20:12.559 E/android.os.Debug(1419): ro.debug_level = 0x4f4c
07-14 10:20:12.559 E/android.os.Debug(1419): sys.mobilecare.preload = false
07-14 10:20:12.579 D/ViewRootImpl(1419): #1 mView = com.android.internal.policy.PhoneWindow$DecorView{4c65b90 V.E...... R.....I. 0,0-0,0}
07-14 10:20:12.579 D/ISSUE_DEBUG(1419): InputChannelName : d6c448e Application Error: com.ryansteckler.nlpunbounce
07-14 10:20:12.579 D/InputDispatcher(1419): Focus entered window: 1419
07-14 10:20:12.579 D/PointerIcon(1419): setMouseIconStyle1 pointerType: 1001 iconType:101 flag:0 pid:1419 uid:1000
07-14 10:20:12.579 D/PointerIcon(1419): setMouseCustomIcon IconType is same.101
07-14 10:20:12.579 V/BroadcastQueue(1419): [background] Process cur broadcast BroadcastRecord{7d0a4af u0 android.intent.action.DROPBOX_ENTRY_ADDED qIdx=4}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{57cba1b 2671:com.google.android.gms/u0a18}
07-14 10:20:12.589 D/NetworkPolicy(1419): isUidForegroundLocked: 10259, mScreenOn: true, uidstate: 2, mProxSensorScreenOff: false
07-14 10:20:12.589 I/PersonaManager(1419): mKnoxInfo is empty
07-14 10:20:12.599 I/SurfaceFlinger(651): id=476 createSurf (193x193),1 flag=4, olpunbounce
07-14 10:20:12.619 D/libEGL (1419): eglInitialize EGLDisplay = 0x7f836e1188
07-14 10:20:12.619 I/OpenGLRenderer(1419): Initialized EGL, version 1.4
07-14 10:20:12.629 D/StatusBarManagerService(1419): manageDisableList userId=0 what=0x0 pkg=Window{d6c448e u0 d0 Application Error: com.ryansteckler.nlpunbounce}
07-14 10:20:12.639 W/DisplayListCanvas(1419): DisplayListCanvas is started on unbinded RenderNode (without mOwningView)
07-14 10:20:12.649 I/PersonaManager(1419): mKnoxInfo is empty
07-14 10:20:12.669 V/WindowStateAnimator(1419): Finishing drawing window Window{d6c448e u0 d0 Application Error: com.ryansteckler.nlpunbounce}: mDrawState=DRAW_PENDING
07-14 10:20:12.669 D/ViewRootImpl(1419): MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
07-14 10:20:12.679 D/libEGL (651): eglInitialize EGLDisplay = 0x7fea4a22d8
07-14 10:20:12.679 V/WindowStateAnimator(1419): Finishing drawing window Window{d6c448e u0 d0 Application Error: com.ryansteckler.nlpunbounce}: mDrawState=HAS_DRAWN
07-14 10:20:12.689 V/AlarmManager(1419): Expired Alarm result :8
07-14 10:20:12.689 D/libEGL (651): eglInitialize EGLDisplay = 0x7fea4a22d8
07-14 10:20:12.699 I/PersonaManager(1419): mKnoxInfo is empty
07-14 10:20:12.719 V/BroadcastQueue(1419): [background]

I just did a cleaner log capture, I think. This includes all apps/system, but only for the timeperiod in which I produced the error.

pbaird said:
I just did a cleaner log capture, I think. This includes all apps/system, but only for the timeperiod in which I produced the error.
Click to expand...
Click to collapse
After reviewing the log for exceptions, the first thing I would suggest is checking if Google Play Services has an update in the Play Store

Related

Optimal battery life w Liquid Smooth [guide]

My current recommendations for optimal battery life are as follows: 3.8.0 exp 1 (Lean Kernel)(imoseyon)
this started as an IRC question & i decided i'd like to have something as a reference for those who'd like to maximize battery life with their respective setups. Feel free to post some screen shots of your battery life to show others your sucess!
battery 101 - cut the services (not in use) off !
How to configure Lean Kernel for optimal battery and secondly performance
Please download / flash your mods ROM / kernel / also flash lean tweaks (jakebites)
inside Lean Tweaks:
`enable 'File system speedup' (aka mount disc noatime)
`enable zram
`enable SD card speedup (set to base 2048)
this will all take effect once you reboot (it uses init.d scripts which require a reboot)
`Go to kernel menu > set customer vibration value > set vibration (/haptic) to 1000
install franco.kernel.apk
https://play.google....m.franco.kernel
go straight to system settings > more > *tick* NFC on [off]
next, disable logcats: liquid control > prop modder > *tick* disable logcats (also within franco.kernel.apk *tick* turn off logger)
liquid control > general > *tick* boot animation on [off] ; android bugmailer *tick* on [off] ; Check in service on [off] *tick*
best to manually toggle 3G / SYNC / LTE / GPS / bluetooth (obviously) as they are not in use - these are some of the biggest battery thieves unless you wantto use powersaver;
Power saver optimal settings:
~powermode: power saver / default
~by request (thanks terryrook) here are some preferred powersaver settings (top to bottom)
*tick* enable powersaver [on] off
Screen off action: *tick* [data off]
data action delay: [10 mins] (should be tailored to your preference (this is a great baseline)
Sync action:[ Autosync Off (delayed)]
Time Interval: [12 hrs] (i prefer this / + syncing each time i want my mail etc)
Screen-off Wifi action: [untouched]
Sync data usage: [Prefer Wifi]
Sync mobile data preferences: Prefer 3G
Not only do I use franco.Kernel apk for access to Franco's latest releases, I also use it for functionalities:
Sqlite defrag on boot,
Disable logger
Set max freq for s/o
Etc!
set your brightness with the slider to your liking - i stay in the area of 50%. Display = #1 battery hog
~Governor InteractiveX (interactive for additional stability)
~Max freq: 1650 (highest stable freq for your device) ( my thinking is the quicker the info is processed, the less processing time)(works for me) (you may want to experiment with this!)
~Min freq: 350 (as franco once said, less disatance between min / max = less time spent switching frequencies)
default IO sechduler
lastly for now, remmeber that your GPU settings will greatly affect batery life! i keep my gpu at 307 unless i dgaf about battery at time (for LK inside terminal simply type $su [enter]; $oc gpu 0 [enter]
if you're using set on boot, make certain that you have (lets say feature A) feature A set on boot for instance within either franco.Kernel.apk OR leantweaks. if you have feature A set on boot in both franco.Kernel & leantweaks, you will end up negating any battery benefits.. bc the system expending energy uselessly
Sent from my Galaxy Nexus using xda premium
First off I'd like to say ur rom is sick fast and i haven't had 1 reboot or issue since applying it on my verizon nexus. I also get great battery life now. 4-5 hrs screen time and 15 hrs total. Here's kind of a noob question though. I've rooted my android phones in the past.... g1, my touch my touch 3g, and my touch slide. All I really did was flash roms backup tweaks n stuff like that. What and how exactly do u mess with the kernal? Isn't the Franco kernal in liquid 1.4 already? Or are you saying buy the app on the market to keep it updated? Thanks for your help
Sent from my Galaxy Nexus using Tapatalk 2

[GUIDE]Tips to Improve your android battery life

TIPS TO IMPROVE BATTERY LIFE
General
Put ur phone to sleep via notification power widget(CM Settings) to prevent wakelocks(awake while screen off).
Conectivity
Turn Wi-fi and Bluetooth off when not in use.
(Power Control Widget ...OR... Settings > Wireless and Networks)
Location
Disable Wireless Network Positioning.
(Settings > Location)
Disable GPS Satellites.
(Power Control Widget ...OR... Settings > Location)
Display
Manual Brightness: Lowest (0)
Auto-rotate screen: Off
Animation: No animation
Screen Time-out: 30secs or less.
(Power Control Widget ...OR... Settings > Screen & display)
For even lower brightness, set dim level to 10 or below
(CM Settings > Display > Automatic Backlight > Screen Dim Level)
Wallpaper and Widgets
Use static background instead of live wallpapers.
Darker wallpapers are recommended for AMOLED screen.
Use less active widgets (high refresh rate)
(Long press Home Screen)
Network
Turn Airplane mode on while you are sleeping.
Turn off Data Transfer (network internet connection) when not in use.
Turn on Airplane Mode when you(user) sleep.
(Power Control Widget ...OR... Settings > Wireless & networks)
Use 2G/GSM Only, not 2G+3G/HSDPA.
(Power Control Widget ...OR... Settings > Wireless & networks > Mobile networks)
Accounts & Sync
Disable background data transfer. (Turn on when using Android Market)
Disable Auto-sync accounts.
(Settings > Accounts and Sync)
Applications
Disallow Mock Location.
(Settings > Applications)
Sound & Vibrations
Set vibration only on silent mode.
Disable haptic feedback. (Vibration on UI interaction)
(Power Control Widget ...OR... Settings > Sound)
Language & Keyboard
Disable Keyboard Vibration / Set vibration to 0ms
(Settings > Language & Keyboard)
Rom Modules - Tweaks to your rom. Works for both stock and modded roms.
If there's undervolt module for your rom, use it.
Custom CPU governor such as smartass, smartassV2
(!) For some CM7 Roms, smartass makes your phone very lag, try smartassV2 or ondemand.
CPU & Processor
Reduce processor speed (Underclock).
Choose [powersave/conservative/smartass] governors. (!) Quite laggy.
[APP] SetCPU for Root Users
-Set processor speed and governors.
Extras
Use less UI-replace apps like CallerID, WidgetLocker, GO Locker etc.
Background and Running Apps
Use task killer ONLY for apps/games u wont use for the next few hours.
Dont leave task killer in the notification bar, kill it together.
(!) If u kill every system apps, your phone have to re-run them all over again. Thus battery drains.
(!) Watch what you kill
[APP] Titanium Backup's Freezing function (PAID VERSION)
-Prevent the apps from running without uninstalling them.
-Frozen apps wont be shown in App Drawer and cannot be launched. (You can defrost if you want)
-Safe common system apps to be frozen: (actually most of them are safe, what u freeze is what wont work)
Market (Market wont work)
Gmail (Market wont work)
Google Apps (affects Market)
Google Search (affects Market)
Google Talk
FOTAkill
Pico TTS (Speech to text wont work)
TTS Service (Speech to text wont work)
Voice Search (Voice Search wont work)
Voice Dialer (Voice Dialer wont work)
(!) Don't freeze apps like Sync, Settings, Package Installer, Messaging and some obviously important apps.
[APP] Autostarts
-Managing apps running automatically in most situations.
-e.g: during startup, after startup, widgets updating...
CyanogenMod Settings (Only available in Cyanogenmod Settings)
-Render Effect - N1 Calibrated
-Overscroll Effect - Disable
(CM Settings > Interface)
-Automatic Backlight Settings - Set Dim Level + Uncheck Allow light decrese
-Screen on/off animation - Disable
(CM Settings > Display)
-Haptic Feedback Tweaks - Disable all
(CM Settings > Input)
-CPU Settings - Adjust accordingly.
(CM Settings > Performance > CPU Settings)
-VM Heap Lower it, increase it if u play HD games.
(CM Settings > Performance)
Battery Saver App
Search on Google Play, there's tonnes.
Thankssss
Theawesomeguy4 said:
TIPS TO IMPROVE BATTERY LIFE
General
Put ur phone to sleep via notification power widget(CM Settings) to prevent wakelocks(awake while screen off).
Conectivity
Turn Wi-fi and Bluetooth off when not in use.
(Power Control Widget ...OR... Settings > Wireless and Networks)
Location
Disable Wireless Network Positioning.
(Settings > Location)
Disable GPS Satellites.
(Power Control Widget ...OR... Settings > Location)
Display
Manual Brightness: Lowest (0)
Auto-rotate screen: Off
Animation: No animation
Screen Time-out: 30secs or less.
(Power Control Widget ...OR... Settings > Screen & display)
For even lower brightness, set dim level to 10 or below
(CM Settings > Display > Automatic Backlight > Screen Dim Level)
Wallpaper and Widgets
Use static background instead of live wallpapers.
Darker wallpapers are recommended for AMOLED screen.
Use less active widgets (high refresh rate)
(Long press Home Screen)
Network
Turn Airplane mode on while you are sleeping.
Turn off Data Transfer (network internet connection) when not in use.
Turn on Airplane Mode when you(user) sleep.
(Power Control Widget ...OR... Settings > Wireless & networks)
Use 2G/GSM Only, not 2G+3G/HSDPA.
(Power Control Widget ...OR... Settings > Wireless & networks > Mobile networks)
Accounts & Sync
Disable background data transfer. (Turn on when using Android Market)
Disable Auto-sync accounts.
(Settings > Accounts and Sync)
Applications
Disallow Mock Location.
(Settings > Applications)
Sound & Vibrations
Set vibration only on silent mode.
Disable haptic feedback. (Vibration on UI interaction)
(Power Control Widget ...OR... Settings > Sound)
Language & Keyboard
Disable Keyboard Vibration / Set vibration to 0ms
(Settings > Language & Keyboard)
Rom Modules - Tweaks to your rom. Works for both stock and modded roms.
If there's undervolt module for your rom, use it.
Custom CPU governor such as smartass, smartassV2
(!) For some CM7 Roms, smartass makes your phone very lag, try smartassV2 or ondemand.
CPU & Processor
Reduce processor speed (Underclock).
Choose [powersave/conservative/smartass] governors. (!) Quite laggy.
[APP] SetCPU for Root Users
-Set processor speed and governors.
Extras
Use less UI-replace apps like CallerID, WidgetLocker, GO Locker etc.
Background and Running Apps
Use task killer ONLY for apps/games u wont use for the next few hours.
Dont leave task killer in the notification bar, kill it together.
(!) If u kill every system apps, your phone have to re-run them all over again. Thus battery drains.
(!) Watch what you kill
[APP] Titanium Backup's Freezing function (PAID VERSION)
-Prevent the apps from running without uninstalling them.
-Frozen apps wont be shown in App Drawer and cannot be launched. (You can defrost if you want)
-Safe common system apps to be frozen: (actually most of them are safe, what u freeze is what wont work)
Market (Market wont work)
Gmail (Market wont work)
Google Apps (affects Market)
Google Search (affects Market)
Google Talk
FOTAkill
Pico TTS (Speech to text wont work)
TTS Service (Speech to text wont work)
Voice Search (Voice Search wont work)
Voice Dialer (Voice Dialer wont work)
(!) Don't freeze apps like Sync, Settings, Package Installer, Messaging and some obviously important apps.
[APP] Autostarts
-Managing apps running automatically in most situations.
-e.g: during startup, after startup, widgets updating...
CyanogenMod Settings (Only available in Cyanogenmod Settings)
-Render Effect - N1 Calibrated
-Overscroll Effect - Disable
(CM Settings > Interface)
-Automatic Backlight Settings - Set Dim Level + Uncheck Allow light decrese
-Screen on/off animation - Disable
(CM Settings > Display)
-Haptic Feedback Tweaks - Disable all
(CM Settings > Input)
-CPU Settings - Adjust accordingly.
(CM Settings > Performance > CPU Settings)
-VM Heap Lower it, increase it if u play HD games.
(CM Settings > Performance)
Battery Saver App
Search on Google Play, there's tonnes.
Click to expand...
Click to collapse
So how long does your battery life runs?
cariojophel19 said:
So how long does your battery life runs?
Click to expand...
Click to collapse
Lol don't take so much tension of turning on and off things
Just see my signature to actually increase battery life along with performance ... I get an easy 3day battery and goes through 1½ days on a holiday and about 7-8 hours on continuous 2g browsing and 5-6 hours on 3g browsing ... this is wayy beyond of wat the device was said to by Samsung ... and all this with good performance ... see my sign
__________________________________________
"lts not who u r inside, its wat u do that defines u..."
———–——————————————
--->make ur phone faster and more battery efficient
--->partition and link apps to sd?!?!?
--->cool 3d games for galaxy y (no root no lag)
sanny5 is right check his post.
mine was 5 - 6 days max with stock rom + hell's kernel + some personal tweak ( both init.d and build.prop ) + removed some bloatware apps.
rmhoh said:
sanny5 is right check his post.
mine was 5 - 6 days max with stock rom + hell's kernel + some personal tweak ( both init.d and build.prop ) + removed some bloatware apps.
Click to expand...
Click to collapse
Lol I wasn't talking about Max... if u keep it just like that it goes even longer... I was talking about average usage and average usage according to me is
1- 24/7 online on fb
2- xda
3- any content browsing except videos and songs
4- occational games (2or4 fruit ninja arcade first example)
5. 24/7 wats app
6. Messaging
7. And some messing around with Android stuff on free time
8. Ebooks
This is wat i meant when I said 2 days
Internet is always on ...
I'm happy that u liked my guide
__________________________________________
"lts not who u r inside, its wat u do that defines u..."
———–——————————————
--->make ur phone faster and more battery efficient
--->partition and link apps to sd?!?!?
--->cool 3d games for galaxy y (no root no lag)
cariojophel19 said:
So how long does your battery life runs?
Click to expand...
Click to collapse
Never quote the OP it's annoying edit it out
You were the first to comment who else could u be talking to
PHONE SLOW CLICK ME?
_____________________________________
"Your signature has been granted superuser permissions"​
Lol
Lol ur closing everything..best is Close your phone and go get A Nokia 1100 lol better use tweaks and custom kernel than using your way...plus i will save alot of time of mine
FINALLYYY!!
rmhoh said:
sanny5 is right check his post.
mine was 5 - 6 days max with stock rom + hell's kernel + some personal tweak ( both init.d and build.prop ) + removed some bloatware apps.
Click to expand...
Click to collapse
Someone who has the same taste as mine. Id like the stock rom retained plus a custom kernel to save my battery.
2-3 days max would be already enough for me since I dont really play games that much.
Youre a kabayan? Why u not showing up at the filipino thread for SGY?
Thanks bro. Imma try hells fusion.
---------- Post added at 08:41 PM ---------- Previous post was at 08:30 PM ----------
sanny5 said:
Lol I wasn't talking about Max... if u keep it just like that it goes even longer... I was talking about average usage and average usage according to me is
1- 24/7 online on fb
2- xda
3- any content browsing except videos and songs
4- occational games (2or4 fruit ninja arcade first example)
5. 24/7 wats app
6. Messaging
7. And some messing around with Android stuff on free time
8. Ebooks
This is wat i meant when I said 2 days
Internet is always on ...
I'm happy that u liked my guide
__________________________________________
"lts not who u r inside, its wat u do that defines u..."
———–——————————————
--->make ur phone faster and more battery efficient
--->partition and link apps to sd?!?!?
--->cool 3d games for galaxy y (no root no lag)
Click to expand...
Click to collapse
Well thats awesoooooooooooooooooooooooooooooooooooooooooooooooooome. :highfive:
Battery Accelerated Drainage
Hi,
I have S2 Plus running android 4.2.2. It has a very nice battery life when used for calls and sms.
My problem is that I experience a massive battery drainage even after turning off the WiFi.
It seems that something keeps on and never shuts down.
Does anyone have experience with the cause/resolution for this?
I appreciate your help.
Murad.

[ROM][JB][4.2.2] Vanilla RootBox - geeb CDN *unofficial* [07.03.13]

Thread Closed as Per OP.
For further Development please use link provided. >>>> HERE​
......
{
"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"
}
Description
Vanilla RootBox is built straight from RootBox sources & Google Sources
and always carries a very light installation with no extra/useless apps.
This means, you can enjoy a pure Android experience combined with PA/AOKP/CM features and some cherry-picks.
Keep in mind Jelly Bean is only at the beginning stage of development and there will be minor bugs.
If you're wondering how this ROM differs from any other AOKP roms out there
Try it yourself and choose the one that meets your requirements
Recommended Install
Wipe Data/Factory Reset (This does not affect your Internal/External storage)
Wipe Dalvik Cache
Flash RootBox
Flash JB GAPPS
Wipe Dalvik Cache
Reboot
If you decide to "DIRTY FLASH" I will not support any problems you encounter
Credit/Thanks
Bajee
IOMonster *TheCubed*
The CyanogenMod Project
AOKP
Teamhacksung
Paranoid Android
DaXmax
Rodries
Pier
BigDenn
Shelnutt2
Chadouming
sk8erwitskil
dvhexer
JankA4U - graphics / bootanimation
PonyExpress
Everyone else I forgot to mention
Trialsrider1
Haze028
Shorelinedev
N4 devs
Open Source
Downloads
| --> July.03-2013
Gapps
| --> Banks Gapps - HERE
| --> Recommended Gapps are banks minimal or multiDPI - then update whatever necessary on store. thanks
| --> gapps-4.2.2-jb-6.30.2013-signed.zip
Disclaimer / Warning!: I'm not responsible for any reason should you bork your phone
Donations
If you want to donate, feel free to do so otherwise don't forget to hit thanks and show your appreciation for all the hard work that goes into this.
RootBox Sources
My Github Sources
Changelog
May.2013
May.03
Email force close when pressing back key after selecting characters
Add turn off action to WiFi Tether notification
Framework: CustomToggle Improvements (!Advanced)
FW: settings: arrayList API rework
Fix Per-App Color
WiFi text - Fixed
Clock - Fixed
SignalText - Fixed
WiFi Icons - Fixed
Signal Icons - Fixed
Fix Notification Shortcuts FC
updated Superuser
Fix CustomToggle Actions
Camera: HDR: Read parameters for hardware HDR support
On mako and geeb(and soon find5), HDR mode is a scene-mode. Software HDR
uses Util.isCameraHdrSupported to check whether or not hardware
already supports it, which should also set software HDR flag.
However, this method is not called soon enough to set this flag
on time, so we call it before checking for software HDR status.
updated wifi to prima 3.2.3.110 caf
https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git
May.06
Camera: Fix Handsfree NPE
PAC: Fix Battery icons
Fix Pie Toggle.
RC: Ribbon fix reset method derp.
Default back to LTE/WCDMA/GSM if supported
Currently after unchecking the 'Use only 2G networks' option, the
default Network Mode is 'WCDMA Preferred'. This patch will change
the behaviour so that if the mobiel supports LTE, the default mode
upon unchecking 'Use only 2G networks' is LTE/WCDMA/GSM
Phone: Add blacklist unknown numbers functionality
This way you can choose to block numbers not
in your contact list
Add counters to missed and blacklisted calls
notifications
Do not attempt to do any matching against the '0000' number.
Additionally, uncheck 'block unknown' when its dependency 'block
private' is unchecked to make the shared pref values follow the expected
behaviour.
Profile Toggle: Update chosen profile
Once a profile has been changed, the proper state was not being updated by the toggle. It's now fixed by using a broadcast instead.
FW: Navring ShouldUnlock method
Don't unlock for the ring options, and power
Fix Auto-Brightness
Changing Automatic Brightness option or setting up Notifiction shortcuts was causing a SystemUI crash. This should fix that issue.
Remove Hold back to kill from RB Settings.
This feature is available through RC.
Add MHL support with kernel that comes with rom
Added smartmax governor to kernel
and alot more other minor things
May.06 v2
Fix: camera does not show up on secure lockscreen
Due that on secure lockscreen the startup order is
onCreate->onResume->onPause->onResume and all listeners
are already killed there is no need to kill the
voice listeners which will cause a pause when
the user try to access the camera from a secure
Lockscreen
FW: Ribbons - Long swipe App window.
Window similar to recents with all the users apps.
Options to control app color, background color, and
background opacity.
On touch listeners for targets and close button
Make dividers colorize with text.
Fixed animations make columns spacing work automagiclly
No more AOSP Launcher, Track own Launcher Trebuchet ported from CM
and rootbox and also some PA touches.
May.08
Correct attachment type for Mms only has subject
Mark the attachment type of Mms only has subject as TEXT
avoid to show Mms View as untimely
Allow theming via Theme Chooser: add missing values for landscape and tablets
Trebuchet: Fix drawer vertical orientation bugs
Issue: https://jira.cyanogenmod.org/browse/CYAN-901
Audio: Organize, include only newer ringtones
Remove duplicate notifications
Acrux=Antares and Bellatrix=Betelgeuse.
Duplicate Media cleanup
Clean duplicate notifications and ringtones.
JIRA : https://jira.cyanogenmod.org/browse/CYAN-292
Hidden Statusbar Pulldown
Currently the Statusbar can be hidden through various options. While this is on
though, notifications, signal, battery, etc cannot be seen. Sure you could just
unhide it real quick but Hidden Statusbar Pulldown allows you to swipe down and
reveal the Statusbar for a configurable amount of time before hiding again
Kernel:
new prima drivers 3.2.3.112
added new governor DANCEDANCE
what is dancedance? find out here
http://forum.xda-developers.com/showpost.php?p=36879068&postcount=2685
May.10
Correct attachment type for Mms only has subject
Mark the attachment type of Mms only has subject as TEXT
avoid to show Mms View as untimely
kernel: new wifi drivers (prima)
Rework Hidden StatusBar logic (WIP)
mainly resync with sources up to date
other minor little things...
May.18
Fix up notification LED behaviour
- Commit 5713307 (in ICS) attempted to
fix the problem that the notification LED wasn't reenabled after
turning off the screen again, but introduced another bug in the
process: If another pending notification with LED at the time when the
notification with the new magic flag introduced by that commit (which
was used by phone and MMS apps) was active, the LED still wouldn't be
turned on at screen off time. Also, this commit didn't handle locking
correctly.
This commit essentially reverts 5713307 and makes sure the LED is
reevaluated when the screen is turned off again.
- This change also makes the assignment of the LED when multiple pending
notifications want to use the LED more clear: The notification with
highest priority gets the LED. If multiple notifications with same
priority exist, the most recent one gets the LED.
PHONE & MMS
Kill off use off FORCE_LED_WITH_SCREEN_OFF notification flag.
NotificationManager has been fixed to reenable the LED when turning off
the screen.
kernel
udpate prima 3.2.3.119
https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git
May.22
JIT: Performance fix for const doubles
Some recent Arm processors take a performance hit when
creating a floating point double by loading it as a pair of singles.
Legacy code to support soft floating point doubles as a pair of core
registers loaded double immediates in this way.
With the CL, we handle double immediates as a single unit.
Fix JIT bug related to immediate doubles
Change 256211 (JIT: Performance Fix for const doubles) introduced a
defect that can cause the JIT to use the wrong floating point
double constant in traces in which the following conditions hold:
o Two (or more) different 64-bit floating point constants are used.
o The physical register holding the first constant is still live
at the time the second constant is used.
o The low 32 bits of the two constants are identical.
In this situation, the load/copy optimization pass will incorrectly
determine that the two constants are the same, delete the load of
the second constant and re-use the first constant value.
Note: this problem only occurs with 64-bit floating point literals.
64-bit long literals are unaffected.
This CL works around the problem, and a subsequent CL will rework
disambiguation of 64-bit immediates in a somewhat cleaner fashion.
libsysutils: fix null pointer and memory leak issue
In SocketClient::quoteArg function
1. Fix potential null pointer accessing issue
2. Fix potential memory leak introduced by realloc fail
Settings: Option to force keyboard to show enter key (2/2)
Original SlimRoms feature! Not everyone likes emoticons
about 21 added commits to kernel
see here for more info https://github.com/houst0nn/kernel_msm/commits/jb-geeb
bunch of other crap but who cares...
you guys probably don't understand all those fixes but just a butt feeling
the rom should give you alittle more vrooooooooooom!!!! and I don't mean benchmarks but just overall user feel. *don't quote me I can't test*
I would like to think.. let me know the results pls and thanks.. more updates comming up, been busy working on my m7 rom
anyways enjoy...
May.24.2013
Bring back RB behaviour
When navbar is set to zero, chevrons are disabled since statusbar is still visible. Let's keep the chevrons
even if the statusbar is visible and let the user decide through RB Settings.
Add transparency settings for lockscreen
This will enable the user to set the transparency level
for the lockscreen.
FW: Ribbon v1.0 overhaul
Thickness Increase max && decrease min
Configurable long swipe and long press swipe areas
consolidate and cache views for smoother animations
User adjustable animantion duration
Add dismiss options for swipe ribbon
- Always dismiss on click
- never dismiss on click
- Don't dismiss for navbar action
fix app window crash if user has fast fingers and to much time
on their hands...
Swipe ribbon drag handles now get their own location, height,
width, and opacity.
Hide apps from app window
Hooks to dismiss app window if softkeys or navbar buttons pressed
Fix app window to pull all components also IE camera and messenger.
Rub some unicorn polish on the on touch glow. The giant boxes were
a bit ridiculous.
If ribbon is empty but toogles are not, just show toggles no flipper.
add adb wireless to toggle map
Phase 1 of the Animation chooser. Simple helpers to let users
choose the animation for the swipe ribbon and app window.
ill be adding some fancier animations for now just some of
the stock AOSP one.
Add lots o animation options. Also preload animations instead
of creating them at run time, should smooth things out a bit.
Keyboard IME hide, Vertical spacing App window, Cache resources.
Fix IME hide when navbar hidden.
Longpress on app window now takes you to app info.
Per-app PIE color
Since we're using Per-app color now, let's use it for PIE as well.
Fix layout of MultiWaveView and GlowPadView.
If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
the right
Fix that by not using width in the calculation, as the inset size
already takes it into consideration.
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
Fix message composing in DarkUI with emojis enabled
fix xxhdpi inverted launcher icon for Mms (HTC ONE)
Mms: set notification number attribute for messages
This will enable also the notification count overlay properly
May.27.2013
RB Settings: Update icon for keyboard enter
AudioService: Remove STREAM_NOTIFICATION from ringer mode streams
EthernetDataTracker: Set network available on connected
This change fixes state mismatch found in the bugs below,
and makes the code look consistent with disconnect().
In startMonitoring(), reconnect() is called before mNMService.registerObserver().
Then dhcpThread.run() could finish without getting interfaceLinkStateChanged() callback.
In such a case, mNetworkInfo has connected but not-available state - which is contradictory.
FW: Fix Menu Overflow Disable Option
The three button Menu Overflow would display no matter what setting was seleted within ROMControl, this commit makes a slight change to correctly return a result that reflects the users selection through ROMControl.
I had to enable then disable the option for it to function correctly (no reboot required)
Remove opaque check in preparing dirty region
Since preserve swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage being present from the previous process in the color buffer.
SystemUI: show blue dc-hspap icon when connected to Google services
TelephonyManager: hide NETWORK_TYPE_DCHSPAP
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
SystemUI: fix vertical date not showed while on Pie
SystemUI: show date on 2 lines in status bar
This allows showing of the full day of the week, and removes
the blank space above the date (which always felt strange to
me when clicking it to access the calendar).
It also fixes a spacing issue on smaller screen devices that
causes the quick settings button to be partially chopped off
when the AM/PM clock settings are enabled.
Fixed an accidentally dot showed in some languages (for ex. US english)
Bluetooth: Fix MAP accept threads sometimes spinning endlessly.
Randomly (under no obvious precondition), the MAP access threads spinned
endlessly after enabling BT, because mServerSocket.accept() always threw
IOExceptions, probably because the actual socket was already closed.
This change makes sure to exit the thread when that happens to not waste
CPU cycles and battery power.
This tracks similar changes done to the BluetoothPbapService and makes
sure to follow the (working) PBAP flow.
May.29.2013
Add Multi-Part and Split SMS Configs
Fix a number of issues with T9 dialer.
- Fix an ArrayIndexOutOfBoundsException (like reported in
[1]) which happened when highlighting the last digits of a number and
the number had additional characters after those digits.
- Fix another potential ArrayIndexOutOfBoundsException due to the
highlighting code relying on normalNumber being a subset of number,
which wasn't the case due to number being additionally sent through a
formatter. Fix that by running the formatter before normalizing.
- Fix number highlighting not working if the number match occured at the
end of the number.
- Fix number type label & formatting not being updated on locale
changes.
- Fix T9 search not being triggered when pressing the dial button to
recall the last dialed number.
Remove DEBUG to avoid to run checking at every turn
Needn't to run storage checking in DEBUG mode at every turn,
it will make "DELETE OLD MSGS" always be checked in Mms Settings
Enhance the Easy Selector
- Follow GoogleUI Guidelines
- Fullscreen selector
- Added groups support
Mms: Go TRDS 2.0
use propper configuration values now
MMS app: fix crash when MMSC setting is NULL
An APN with a null MMSC column prevented the MMS app
to find the next APN in query.
MMS: Fix lookup of vanity addresses
Avoid the use of the function PhoneNumberUtils.stripSeparators for non-strict
phone numbers.
Camera: Add TrueView
This commits adds the ability to show the complete image sensor frame
rather than the cropped preview used by aosp to fill the entire
screen.
Fix wrong log information in DevicePolicyManagerService
When user reset password their password,
if password doesn't match target quality of device,
DPM print a log why can't reset password.
however log message isn't correct information.
in log context, it have to exist current quality
and target quality. this patch can help print correct log
Avoid IllegalArgumentException in Preference.java compareTo()
In some situations the collection.sort() algoritm fails in compareTo()
with a: java.lang.IllegalArgumentException: Comparison method violates
its general contract!, due to a more strict validation of the compare
contract.
Fix CalendarView to show the month title properly.
Step to reproduce:
Do this test on a Tablet (i.e. do in multi-pane layout)
1. Settings > Date & time > Uncheck the Automatic date & time checkbox.
2. Select 'Set date' and set the month to January and Done.
3. Re-select 'Set date' then you will find no month title just above the calendar.
Framework/base: Added synchronization block to avoid race condition
Fix for the synchronization issue leading to access of an array
Index out of bounds. Issue occurs due to race condition between
removing the activities of a crashed process from history stack
and resuming a separate activity.
SystemUI: Fix Tablet UI Date View
Mobile indicator has been removed, is still showed in quicksettings mobile tile. http://goo.gl/1ZtuS
TRDS 2.0: Update Dark toggle state
June.2013
June.03.2013
Reduce observers in SystemUI: StatusBarIconView
Currently, for each status bar icon view there is a observer that
listens for changes of STATUS_BAR_NOTIF_COUNT. With one
notification usually having one or more status bar icons
you may end up easily with 10+ more observers for ~5 notifications.
With this commit the internal observer class becomes a singleton.
This means there is now only one observer for all status bar icons
and additional binder calls on new notification are avoided.
Reduce observers in SystemUI: KeyButtonView
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all buttons.
On my Nexus 10 it reduced the observer count from 48 to 4.
Reduce observers in SystemUI: BatteryBarController
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all instances.
On my Nexus 10 it reduced the observer count from 15 to 3
Fixing crash in PhoneNumberUtils getNumberFromIntent
Handling intent with no data when trying to retrieve number from
intent.
audio: Add overlay to fix analog docks.
Of particular interest to devices using libhardware_legacy and
affected by commit 5a484b7: http://goo.gl/rVR1Z
which restricted the routing of AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET
to docks using FORCE_ANALOG_DOCK cases. The EXTRA_DOCK_STATE_CAR case is
returning FORCE_BT_CAR_DOCK, preventing the dock audio from routing properly.
Add an overlay option for overriding to FORCE_ANALOG_DOCK.
FW: Menu Overflow Disable - Different Implementation
Original method I used to enable the menu overflow disable option incorrectly disabled the menu overflow altogether for some devices due to a late night derp.
This implementation of the check to confirm if the menu overflow has been disabled through ROMControl should hopefully correct this issue.
Pie: set Big as default for item gap (2/2)
Screen: http://goo.gl/aocZ7
Pie: updates (2/2)
-pie angle: fixes, cleaning and new value (Huge)
-pie size defaults
-strings updates
Pie: Fix and easy recalculation for Chevron and Pie
Pie: set angle default to 12° (1/2)
Pie: let Chevron adapt itself from pie's angle.
> This make Chevron able to recreate the battery bar when the angle changes.
Fix unresponsive statusbar area.
Framework: GlowPad Torch
LongPress GlowPad...Torch.
Release...No Torch.
FavoriteToggle: DismissKeyguard
Small Fix
ClockActions: Dismiss Keyguard
Kanging SteveSpear's Brilliant
dismissal method here.
Doesn't require an activity
as ...OnNextActivity() does
Fix MAP SDP record generation
Give the bluetooth app API to register a server socket for a specific
UUID/port pair. It needs that for registering two OBEX server instances.
Fix Profiles - Ring Mode
Fix: AUTO_TIME and AUTO_TIME_ZONE moved to Global google
Frameworks: airplane_mode_on moved to global google and CM
Improve auto-brightness handling
- Add a setting to control the auto-brightness algorithm responsitivity
- Make the algorithm react much faster when the ambient brightness
increases quickly, e.g. when receiving a call in bright sunlight.
Settings: Call Ring mode what Google calls it, not Silent mode
Silent mode -> Ring mode cleanup
Fix Notification shortcuts icons picker FC
Allow changing auto-brightness responsitivity.
Adapt torch intent for Glowpad
Change intent for this feature as we do not use AOKP'S torch
Lockscreen Longpress: Unlock Logic
In my opinion, we should unlock after
user removes their finger.
This matches short-press unlock better
and allows the user to change their mind
on a target (I do that a lot).
Added a vibration action on longpress
being true.
Fix SMS sending.
ACTION_SEND_MESSAGE must be routed through the privileged receiver now,
otherwise it'll be dropped in SmsReceiver.
BatteryIcon with Center Text should be fixed now
Q & A Thread - HERE - thanks to PonyExpress
IF you have questions about PIE bug look HERE any I honestly don't know why it's hard for some of you to use the SEARCH and LOOK HERE ABOUT THIS ISSUE
ATTENTION
For those of you that are LGPNST'ing back to old original TOT or flashing the original KDZ .. to be able to boot AOSP roms.
for best and stability use the latest Official JB kdz to flash then root and then unlock then flash this rom.. thanks
another note.. if you are on the old ICS and haven't flash original LG JB. u can grab the newer modems for your phone HERE
dont' forget to hit thanks if u appreciate the work.. ENJOY!
Reserved...
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Sweet. Now get back to working on a sweet stock rom.
LG Optimus G E971/3/5
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Hello Houstonn, I'll test when back from work, however, about AOKP / CM bugs, are there in your rom the same reboots as Chadouming's cm 10.1 rom?
Sent from Somewhere using my Puppet Master
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
So far so good. loving dark rootbox!
Sent from my Optimus G using Tapatalk 2
Running good on E975 also. Just missing camera, but that was expected.
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Is the kernel still sticking at 384mhz on this new build Houston?
Sent from my Optimus G using xda app-developers app
---------- Post added at 11:07 AM ---------- Previous post was at 10:32 AM ----------
I can confirm that the kernel is not sticking at 384mhz on this new build. This might be your best ROM yet Houston. Everything is smooth as butter. No issues with anything as of yet. Keep up the great work:thumbup:
Sent from my Optimus G using xda app-developers app
Nice to see more stock Android ROMs. Sad that there's little ROMs based on LG software. Keep it up though!
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Great ROM but I hate to say but I don't have a notification light.
Nothing for SMS or even when I go to test.
Also does anyone know how to use chadoumings color settings?
Otherwise kick ass ROM!
E973.
Sent from my Optimus G using Tapatalk 2
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Ya no notification light for me either. Nor does it blink red when it's charging. Not a huge deal breaker for me though.
Sent from my Optimus G using xda app-developers app
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Also can confirm that my phone is once again fast and responsive, no longer getting stuck at the 384.
Sent from my Optimus G using xda premium
Pretty slick ROM. I like some of the customizations but it's almost overwhelming at times but power to the people! Look forward to testing it a bit more. NFC does not appear to work at this time either. Toggle just won't check. The true test will be stability. Additionally, the LTE toggle doesn't work and I'm not in an LTE area so I'm not sure if LTE works at all but I imagine it does and the toggle is just broken.
EDIT: LTE is in fact working.
I cant seem to get this to boot. After flash I see the LG logo for a second then black screen. Have tried reflashing and rebooting several times. Do you need to kdz to stock first? I am coming from 4.1.2 on the LGE971 Using clockwork recovery
dspot said:
I cant seem to get this to boot. After flash I see the LG logo for a second then black screen. Have tried reflashing and rebooting several times. Do you need to kdz to stock first? I am coming from 4.1.2 on the LGE971 Using clockwork recovery
Click to expand...
Click to collapse
Make sure you are wiping data/cache/dalvik cache before booting.
Re: [ROM][4.2.2][AOSP/AOKP/CM/PA] LGOG Vanilla RootBox [initial release]
Thanks bro, Still no go.. Any chance you or anyone could post the md5 for the ROM?
Thx
Sent from my LG-E971 using xda app-developers app
so led notification, nfc and camera isn't working? anything else? very tempted to flash.
dspot said:
Thanks bro, Still no go.. Any chance you or anyone could post the md5 for the ROM?
Thx
Sent from my LG-E971 using xda app-developers app
Click to expand...
Click to collapse
MD5: d980b19b6d6816e6cb280c7e3ecf5bac
qjai said:
so led notification, nfc and camera isn't working? anything else? very tempted to flash.
Click to expand...
Click to collapse
Camera works on the E971/E973 (Canadian) variants. It's just the E975 it's broken on. The ROMs been out less than a day so it's hard to say what it's really like. Make a NANDroid backup and try for yourself. If you don't like it, it's 5 minutes to get back to the way you were.
dpvu said:
MD5: d980b19b6d6816e6cb280c7e3ecf5bac
Camera works on the E971/E973 (Canadian) variants. It's just the E975 it's broken on. The ROMs been out less than a day so it's hard to say what it's really like. Make a NANDroid backup and try for yourself. If you don't like it, it's 5 minutes to get back to the way you were.
Click to expand...
Click to collapse
yea I plan to do so, but then after flashing those jb roms, I noticed my storage partitions keep moving to /0 or /0/0 folders so in the end, takes a very long time to recover my stuff for the new rom, as well as just returning to the backup.
sorry.. the LEDS were my mistake I was trying some other things out and forgot to set them back on... I'll look into the NFC as well as it was working on my previous test builds.. all the issues are mostly due to me changing a few upstream sources due to the recent problems we've been getting, by changing some sources I'm managing to get better stability instead of having reboot issues and sod issues.. will have another build out shortly.. as for now getting familiar with the rom features is the best I can say till I have the next release with issues addressed. thank you

Themes / Apps / Mods [App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)

{
"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"
}
About this ap:
Refresh Rate Mods
Change default refresh rates
-Easily change the overall refresh rate settings of devices supporting multiple refresh rates.
-Set supported mid refresh rates as the maximum refresh rate limit for battery savings (e.g. 96hz instead of 120Hz).
-Quick settings shortcut
-Tasker plugin support
Motion smoothness mode switcher(Normal, Adaptive or High)***
-Set you device motion smoothness mode to stationary refresh rates (high mode) for better smoothness if so desired on Samsung devices with native Adaptive motion smoothness with a little trade-off to the battery.
-Apply adaptive mod on device that don't natively support adaptive mode [premium]
-Tasker plugin support
Per-app refresh rate settings:
Set different refresh rate settings for every app either adaptive or fixed(stationary) [premium].
Motion smoothness on power saving mode
-GMH will apply a workaround to bypass 60Hz limitation on Power Saving Mode (PSM) on supported Samsung smartphones.
-Automatically apply workaround when PSM is enabled [premium]
Need extra steps starting OneUI5.* except when rooted with magisk and using lsposed(experimental). Test it first
Screen-off Mods:
Force to Lowest Hz
-Force the lowest refresh rate on screen-off or Always-On Display(AOD) to improve standby power consumption a bit.
-Select refresh rate to set for AOD/screen-off[premium]
-Tasker plugin support.
Auto apply power saving mode during screen-off ***
Auto disable Autosync***
Quick-doze mod
-Quickly enter doze mode during screen-off that can not be interrupted by motion [premium]***
-Tasker plugin support
Auto SENSORS OFF (experimental non-root workaround)
-Device sensors will automatically turn off while screen is off until the device is unlocked to help minimize battery-draining motion-triggered wakelocks while device is not being used [premium]
-Tasker plug-in support
- Supports up to OneUI4.* only
Others
Battery protection mod (Experimental)
-Option to set maximum charge to 86%-95%(for OneUI4+)[premium]
Customizable refresh rate monitor
-Use statusbar or overlay which you can place anywhere on screen.
-Tasker plugin support
Net speed statusbar indicator
OneUI inspired UI. Dynamic theme and Icon. Manual language selection
Note: The premium license is on a per device basis (not per user).
***these marked features require a one-time ADB procedure (this is not root)
Galaxy Max Hz background service is highly optimized. Background battery usage p is very negligible .
Info:
This app targets older android sdk in order to control refresh rates without ADB setup or root. Just tap OK the dialog that says "This app was built for an older version of Android...." when opened for the first time. If OK button is not visible, just tap the blank space on the lowest portion of the dialog.
If google play protect will prompt during install that the app is built for older version of android and doesn't include the latest privacy protections, you can ignore it and proceed to the installation. For privacy related concern, please refer to FAQ No. 3.
Download
v8.0.0
Changelogs
Github wiki
Localization/Translations ​Contributors
Italian: @Orlaf
German:devj3ns, drbeat
Russian: @a43
Swedish:Steffe2
Turkish: osmanakar312
Greek: Nick
Spanish: @Sebastiansm
Czech: @Chrono Leggionaire
Simplified Chinese: @xiaolu7233123
French: @Jaxom84
Polish: @Pichulec
If you want to contribute on translations, please send me a message
Great that you've brought support to fold 4! I have small issue, it is randomly setting me on standard instead of adaptive,before I do any changes in settings (apart from ash obviously). Any ideas? Thanks!
morley636 said:
Great that you've brought support to fold 4! I have small issue, it is randomly setting me on standard instead of adaptive,before I do any changes in settings (apart from ash obviously). Any ideas? Thanks!
Click to expand...
Click to collapse
Maybe triggered by power saving mode being turned on?
It looks totally different on my fold 4? It's like stuck on adaptive but seems to be letting me set per app rate.
Does the screen off 10 work with aod?
Smittyzz said:
It looks totally different on my fold 4? It's like stuck on adaptive but seems to be letting me set per app rate.
Does the screen off 10 work with aod?
Click to expand...
Click to collapse
We don't have the Z Fold4 to test yet but it should be since Z Fold4 is capable of 10Hz.
the problem with 10Hz is that all apps (instagram, reddit etc) that shows videos are stuttering, so I need to use 24-120hz on those apps.
tribalfs said:
We don't have the Z Fold4 to test yet but it should be since Z Fold4 is capable of 10Hz.
Click to expand...
Click to collapse
I more less was thinking if the aod holds the screen on 24/7 if the 10hz lock still happens?
Looking to save battery if I can loli need aod on due to media controls with the phone "off"
Either way thanks
[email protected] said:
the problem with 10Hz is that all apps (instagram, reddit etc) that shows videos are stuttering, so I need to use 24-120hz on those apps.
Click to expand...
Click to collapse
Yes, that's a known limitation of GMH when setting min hz to 10Hz (for these apps which are restored from backup or not installed directly from play store).
For device like ZFold4, It's recommended to keep default min refresh rate to 24Hz and just use the per app settings to adjust individual app refresh rate settings to your liking..
Hey, thank you very much for this amazing app!
Two Issues:
I can just choose between "standard" and "adaptive" mode. The "high" option is greyed out. Why is that, and how can I use high mode?
I can't use the Tasker plugin. I can just add the plugin, but the edit button doesn't show the configurations. Am I doing this wrong?
Questions:
Can you add a QS tile/toggle for "PSM when screen is off"?
the option to limit the refresh rate while tying is just 60Hz, why can't this be lower like 10-24Hz?
At the top of the app it shows the device and says the model, Android 12, but it says "OneUi4.5", but it's on "OneUi4.1.1."
Thank you very much for your help
Mr6P said:
Hey, thank you very much for this amazing app!
Two Issues:
I can just choose between "standard" and "adaptive" mode. The "high" option is greyed out. Why is that, and how can I use high mode?
I can't use the Tasker plugin. I can just add the plugin, but the edit button doesn't show the configurations. Am I doing this wrong?
Questions:
Can you add a QS tile/toggle for "PSM when screen is off"?
the option to limit the refresh rate while tying is just 60Hz, why can't this be lower like 10-24Hz?
At the top of the app it shows the device and says the model, Android 12, but it says "OneUi4.5", but it's on "OneUi4.1.1."
Thank you very much for your help
Click to expand...
Click to collapse
What version of the app you installed?
And what is the exact model number of your device?
Thank you.
That OneUI4.5 version is a bit strange. That value is actually read from a field in OneUI's Build class.
tribalfs said:
What version of the app you installed?
And what is the exact model number of your device?
Thank you.
That OneUI4.5 version is a bit strange. That value is actually read from a field in OneUI's Build class.
Click to expand...
Click to collapse
It says: Version 8.0.0, I set it to alpha update channel. It doesn't say "beta" like in your screenshot here
In settings app, it says: SM-F936B/DS
I don't understand the One UI version either
I bought premium, and it also says that it's activated
------------------------
EDIT: I cleared cache & data and installed the most recent version from GitHub. Now the "high" mode is available again.
I've set up Adaptive to 24-96Hz. Now I have a weird bug, that locks the front screen to 24-60Hz and on the main screen it's correct 24-96Hz. No PSW or anything.
I don't know how to use the Tasker plugin. When I open it, then it just shows a long block of text, (see attached screenshot). There's an edit button (pencil icon) at the top right, but pressing it does nothing. Is there any configurator or even an (G)UI? Or how am I supposed to use the plugin?
Thank you very much
Hi there. Despite changing the update channel to beta, I cannot get the beta version of the app. Tried clearing cache and data several times but still no success. Any idea? I also bought a license. Thought that was the issue but still no update to beta. Helps please? Really wan to use high refresh in PSM. THANKS.
"Keep Smoothness on PSM" is missing on OneUI 5 beta, G998B.
LeeXDA18 said:
"Keep Smoothness on PSM" is missing on OneUI 5 beta, G998B.
Click to expand...
Click to collapse
I'm on oneui 4.1.1
Just reporting that the per-app settings master toggle seems to be ignored. I set my device globally from 10 Hz to 120 Hz and found that YouTube would fall down to 10 Hz when playing videos rather than 24 Hz (which also shouldn't happen). I rectified that by setting YouTube alone to 24 Hz - 120 Hz, but forgot to activate the master toggle for per-app settings. When I switched to YouTube however, it was now working correctly. It wasn't until later that I discovered that I never changed that setting, and testing with it both enabled and disabled seem to have no impact on the behavior. Only completely resetting the individual setting for the YouTube app restored the original (buggy) behavior.
Mr6P said:
...
------------------------
EDIT: I cleared cache & data and installed the most recent version from GitHub. Now the "high" mode is available again.
...
Click to expand...
Click to collapse
Great!
Mr6P said:
..
I've set up Adaptive to 24-96Hz. Now I have a weird bug, that locks the front screen to 24-60Hz and on the main screen it's correct 24-96Hz. No PSW or anything.
..
Click to expand...
Click to collapse
Seems Samsung set higher brightness threshold for 96hz on the front screen which disables 96hz on low brightness condition. Unfortunately, this is beyond control of GMH or any third party app.
Mr6P said:
I don't know how to use the Tasker plugin. When I open it, then it just shows a long block of text, (see attached screenshot). There's an edit button (pencil icon) at the top right, but pressing it does nothing. Is there any configurator or even an (G)UI? Or how am I supposed to use the plugin?
Thank you very much
Click to expand...
Click to collapse
Please check #16 in FAQs.
Thank you.
jooniloh said:
Just reporting that the per-app settings master toggle seems to be ignored. I set my device globally from 10 Hz to 120 Hz and found that YouTube would fall down to 10 Hz when playing videos rather than 24 Hz (which also shouldn't happen). I rectified that by setting YouTube alone to 24 Hz - 120 Hz, but forgot to activate the master toggle for per-app settings. When I switched to YouTube however, it was now working correctly.
Click to expand...
Click to collapse
I believe that the installed youtube app was restored from backup and then subsequently updated from play store.
This is related to the limitation I mentioned here. Thank you.
tribalfs said:
Yes, that's a known limitation of GMH when setting min hz to 10Hz (for these apps which are restored from backup or not installed directly from play store).
For device like ZFold4, It's recommended to keep default min refresh rate to 24Hz and just use the per app settings to adjust individual app refresh rate settings to your liking..
Click to expand...
Click to collapse
tribalfs said:
I believe that the installed youtube app was restored from backup and then subsequently updated from play store.
This is related to the limitation I mentioned here. Thank you.
Click to expand...
Click to collapse
I understand that youtube not correctly applying 24 Hz falls under the limitation you mentioned, however shouldn't setting the per-app profile for youtube to 24 Hz minimum, but not having the master per-app toggle on not alter youtube's behavior at all from the global behavior set?
jooniloh said:
I understand that youtube not correctly applying 24 Hz falls under the limitation you mentioned, however shouldn't setting the per-app profile for youtube to 24 Hz minimum, but not having the master per-app toggle on not alter youtube's behavior at all from the global behavior set?
Click to expand...
Click to collapse
No, global behavior for apps detected as video player is 24hz min unless higher min hz is set as default.
tribalfs said:
No, global behavior for apps detected as video player is 24hz min unless higher min hz is set as default.
Click to expand...
Click to collapse
I get that, but with the GLOBAL setting set to 10-120, and the master per-app toggle OFF--meaning NO settings within per-app settings should affect behavior--YouTube falls down to 10 Hz during playback when the YouTube per-app setting is left cleared, but correctly plays back at 24 Hz when its per-app setting is set to a minimum of 24 Hz. Why is YouTube's per-app setting having an affect on refresh rate within the YouTube app when the master per-app toggle is set to off?

Themes / Apps / Mods [App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)

About this app:
Refresh Rate Mods
Change default refresh rates
- Easily change the overall refresh rate settings of devices supporting multiple refresh rates.
- Set separate refresh rates for power saving mode and for low battery state [1]
- Quick settings shortcut
- Tasker plugin support
Refresh rate (motion smoothness) mode switcher(Normal, Adaptive or High)[2]
- Set you device motion smoothness mode to static refresh rates (high mode) for better smoothness if so desired
- Tasker plugin support
Per-app refresh rate settings:
-Set different refresh rate settings for every app either adaptive or static [1]
Keep selected refresh rate mode on power saving mode[1]
- On devices with One4 or lower, GMH will automatically apply a workaround to bypass 60Hz limit on Power Saving Mode.
- Need extra steps on OneUI5.* except when using magisk and lsposed(experimental). Test it first.
Screen-off Mods:
Screen off/AOD refresh rate (Force to Lowest Hz)
- Force the lowest refresh rate on screen-off or Always-On Display(AOD)
- Tasker plugin support
- Select custom refresh rate for AOD/screen-off [1]
Auto apply power saving mode during screen-off [2]
Auto disable Autosync
Quick-doze mod
- Quickly enter doze mode (than usual) during screen-off that can not be interrupted by motion with customizable maintenance window interval [1][2]
- Tasker plugin support
Auto SENSORS OFF (non-root workaround)
- Device sensors will automatically turn off while screen is off until the device is unlocked to help minimize battery-draining motion-triggered wakelocks while device is not being used [premium]
- Tasker plug-in support
- Supports up to OneUI4.* only
Others
Battery protection mod
- Option to set maximum charge to 86%-95%(for OneUI4+)/40%-95% if rooted [1][2]
Quick resolution switcher
- Easily switch to any supported resolutions using the included quick setting tile[2]
- Tasker plugin support
Customizable refresh rate monitor
- Use statusbar or overlay which you can place anywhere on screen.
- Tasker plugin support
Animation mod
Net speed statusbar indicator
OneUI inspired UI.
[1] Enabled for premium users (with 2 days premium trial)
[2] These features require WRITE_SECURE_SETTINGS permission granted thru a one-time ADB procedure (this is not root)
Info:
This app targets older android sdk in order to control refresh rates without ADB setup or root. Just tap OK the dialog that says "This app was built for an older version of Android...." when opened for the first time. If OK button is not visible, just tap the blank space on the lowest portion of the dialog. If google play protect prompts during install that the app is built for older version of android and doesn't include the latest privacy protections, you can ignore it and proceed to the installation. For privacy related concern, please refer to FAQ No. 3.
Download and changelogs
Github wiki
--reserved--

Categories

Resources