Hard to tell. Works fine on my N5. I still have to test lockscreen tweaks on a device with fingerprint sensor. My 5X is still bootloader locked running everything stock.super stoked. thanks so much @C3C076 for your hard work on this. i love this module!! finally... everything i need in one place!!
happy to support your work sir. unlocker purchased!
i do seem to be having an issue with the trusted wifi. perhaps i'm confused as to how this function works. i've checked the box for the wifi i'm currently on and it's still requesting my pin. is this function in the program not intended to enable smart unlock?
i'm on a stock (rooted) 6p. i have rebooted after changing the setting in GB.
k. thanks.
perhaps someone running a 6p can test and chime in to see if it's just something funky with my device.
You can map Search action as pie key long press action. Will open either now on tap or standard search depending on whether now on tap feature is turned on.Would it be possible to map Google now on top to Pie controls circle (o) button?
Thanks again for releasing this so quickly!
Strange. Never heard of something like that in relation to GB. But I saw people mentioning that pin/password is not recognized after rom restore via twrp recovery.@C3C076
Thanks for the quick update.
I have this bug, it doesnt recognize my pin when i try to unlock muy phone
Moto x 2014
Works fine on stock rom.Thanks a lot !! You just made early MM Builds "usable for me" !!
Testing on AOSParadox Project 2.0 - 20151115.
Most of it working so far. But the long press for home button works only first time after change. From the next time the default behavior kicks in.
Yes, can reproduce.In expanded desktop (immersive) System UI crashes when using the search key in pie control (on n9 and n5 stock).
And thanks for this module.
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.