Some Samsung devices are supported :google play edition, Galaxy Nexus, etc. They run pure aosp, straight from Google, Android software. The rest of Samsung devices, s3,4,5, note, note 2,3, etc are using Android modified by Samsung (touchwiz). This is the reason that it's not supported. There is no feasible way to support every manufacturer, custom roms, etc with one module that does it all. Granted, gb is probably the closest thing to all in one, but the scope to be able to support that many variations is staggering.Clearly is not explained like you said by the developer, it is confusing because he says that some Samsung devices will not work but others with AOSP 4.4.will... so, obviosuly I was trying to figure it out. Thanks for the heads up but you didn't help AT ALL. I'm off.... do not patronize me.. You are the one spending time and taking space in this thread to answer a genuine doubt that I couldn't find on the internet. Ciao.
Feature request (Idea): Could you consider to add use blur effect in defautl desktop background? Do you think would be possible to do this respecting the background page position?
Thanks for share your great work.
Is there a way to turn off Ultimate Notification Control? It's not working reliably for me and I'm missing some messages. I've unchecked the apps that I created setting for and also turned off 'Default Settings', but it still is messing with my notifications.
The Heads Up feature is really awesome, great job adding it so quickly. Just one question: are there plans/is it possible to detach it from the default settings being on requirement? Right now it only works when the default settings are turned on, which means every app now listens to GB to set the notification color/vibrate/etc settings. I've already got apps that handle that.
GB enables standard heads up android functionality as it's currently implemented in AOSP automatically.Guys i had to roll back to v 3.1.7 as 3.2 enables heads up by default and there is no way to disable unless with premium version and even then it messes up all my notification settings. Can you release a fix? I'm on cm rom and have heads up disabled from rom as well.
full battery charge led indicator for nexus 5 is not possible using UNC ?
Those people just don't appreciate how impressive GravityBox is. I am willing to bet every single one of those people who are complaining about certain features only being in the donate version, or about how it doesn't work on custom ROMs, have absolutely no idea how to code an app. They know nothing about the amount of time and effort that goes into something like GravityBox, and are entirely oblivious to the fact that you do this on your own time and for zero salary. They think all you have to do is tap a button to add support for their ROM, so why aren't you just doing it?
There's never going to be a way to please everyone, and I just hope that those of us who do value and respect your hard work will keep you motivated to keep at it. I know that without GravityBox, both my Nexus 5 and 7 would be a lot less fun to use. GravityBox has allowed me to add additional functionality and customization to my devices, while keeping the ROM rock-solid stock and stable. No other custom ROM even comes close to equaling the quality and functionality of GravityBox + stock ROM on a Nexus device. So, THANK YOU for all you do to continue to deliver new and exciting features! Your time and effort is very much appreciated. :good:
Basically it's not, BUT only for Nexus 5 there is this (http://forum.xda-developers.com/showpost.php?p=53512888&postcount=8356) workaround.
Some Samsung devices are supported :google play edition, Galaxy Nexus, etc. They run pure aosp, straight from Google, Android software. The rest of Samsung devices, s3,4,5, note, note 2,3, etc are using Android modified by Samsung (touchwiz). This is the reason that it's not supported. There is no feasible way to support every manufacturer, custom roms, etc with one module that does it all. Granted, gb is probably the closest thing to all in one, but the scope to be able to support that many variations is staggering.
Sent from my VS980 4G using Tapatalk
please test something before posting, i understand perfectly that the application is made for AOSP.
gravitybox but it works 90% of touchwiz the galaxy s5.
I'm not sure how officially the Xperia Z1 4.4.2 stock is supported by GravityBox KK or not, as a happy owner I must say it works about 80% of all the features, and that's pretty amazing.
I will mention a couple of things that are missing/are buggy in this device, perhaps there is a quick workaround to fix this:
1. Navigation bar tweaks / Navigation bar ring / Navigation ring targets When switched to On, and seect 1,2 ... or 5, it allows to make the selection and it replaces it with the icons of choice, only problem, it doesn't do anything if swiped over them, for example, selecting the Tesla led toggel on/off doesn't do anything, or simply selecting shortcuts to any app works, maybe is just related to the stock z1, or not
2. After enabling Gravity Box KK in Xposed Framework, and restarting, I instantly have 2 battery icons, the one from Gravity Box, and the stock icon, after going into Gravity Box settings, and selecting any type of icon style, the stock icon dissapears and I'm left with the icon of my choice, which is great, only problem, I have to do this everytime I restart my phone, same procedure, and the old stock icon dissapears.
Everything else, and I mean, every other single option on Gravity Box KK works perfectly in the Sony XZ1 stock 4.4.2.
Thanks for developing this!!! Having a locked bootloader, Flashing a custom ROM is not something I'm considering right now, and this makes the stock sony ROM almost perfect!
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.