No, it is not possible to modify output power. The one and only effect is that volume range is distributed over more steps.Is it possible that changing number of volume steps in GB also modifies the output power of built-in speaker?
I'm just asking because my phone's main speaker broke. I've had number of volume steps increased from default 15 to 25 by GB (for music only).
NOT TO BLAME ANYONE,
maybe I've set it wrong or it couldn't make any damage, IDK.
Sent from my ASUS Zenfone Go (ASUS Z00VD) using XDA Labs
Hardware limitation. Most of the devices can be woken up only by power button when CPUs are offline (deep sleep).Using the volume buttons to Wake feature not working in Zenfone 5 with Lollipop.
It works if I use it right after the screen goes off. But later, after sometime, it does not work. Probably the process gets killed, but the other customizations are working perfectly.
My power button is broken, so I wanted to use this feature.
Hardware limitation. Most of the devices can be woken up only by power button when CPUs are offline (deep sleep).
Some devices allow it using volume buttons as well as it's supported at hardware level (volume buttons can wake up CPUs from sleep).
Nothing I can do about it.
Make sure you choose desired expanded desktop mode in Display tweaks.
Thanks for your reply anyways. As you are a master in this field, can you please show me any other way of bypassing the power button? Using exposed modules?
I used apps that uses the Proximity sensor, but it keeps the sensor engaged all the time. Appears, it might damage the sensor.
As is detailed in the OP, GravityBox is designed to be used with stock, vanilla AOSP ROMs, not OEM and custom ROMs. In other words, Google Play Edition and Nexus devices. All OEM ROMs (TouchWiz, Sense, Xperia, Moto, etc.), and custom ROMs (CyanogenMod, ParanoidAndroid, etc.) differ significantly in their code base from pure AOSP. And as most of these ROMs are closed source, and the developer does not have access to all the devices, it means that GravityBox is not designed for, or tested on, these devices and ROMs.
Even though the Moto devices look like stock Android, they are as much custom under-the-hood as TouchWiz or Sense. It's just that Motorola decided to implement a skin that resembles stock Android, rather than a custom skin like Samsung has done. But the changes to the core code mean that many of GravityBox's features will not work, and actually do cause some well-known bugs. The same goes for ParanoidAndroid, there are just too many changes to the core code for GB to be reliable.
If you choose to use GravityBox on a ROM it was never intended to be used with, then you do so at your own risk, and without any support. You should always have a good nandroid backup and be familiar with ADB and Fastboot. At any time, a ROM update or GravityBox update may cause any/all GravityBox features to break, and worst case, send your device into a bootloop. This is just an unfortunate reality of using a mod on a device it wasn't intended to be used on. Any user who wishes to improve or fix bugs on their unsupported ROM is more than welcome to download the source code for GravityBox (links to Git in the OP) and work on debugging and fixing the bugs on their own.