[Nexus 5 Android Development] magnamentis:
about lightflow

hi,

i just want to shed some more light to the led-notification issues, happening with lightflow and other apps since kitkat release, if somone does not agree with my findings no problem, but dont't bash, just ignore ore contribute your findings with good arguments please.

i had a lenghty back and forth communiction with the dev of lightflow because with kitkat the app did not perform like before, that's a fact.

now it happend that the dev got rid of the initial heavy problems with a hack ( he himself called it so in the lightflow thread ) which in simple words is connected to the screen on or off state.

currently as it happens lightflow only works properly the moment the screen is off, and i mean really off.

so what does that mean? it means that s2w, dt2w, daydream and other states which keep the screen in a not totally off state

would keep lightflow from working properly.

this means again that we currently have to decide what is more important to us, light notifications ( like for me ) or

features which keep the screen in a receiving mode like s2w and daydream.

for me, on 4 of my devices lightflow works perfectly well considering the above limitations.

the problems only apply to devices which do not have the lights working under screen-on conditions like

it is the case with samsung devices. samsung devices, unlike others can led-notify when the screen is on.

there is a setting in lightflow which allows lightflow to work under screen-on conditions which means, it works perfectly

under all circumstances, while the nexus 5 does not have this feature and thus lightlflow does not work properly with

any screen not totally off features, likes i mentioned above.

so if all this is not valuable information for someone, i'm sorry to hear that there are problems but i think it's still

good to know for many that there is a connection between screen state and light notifications working properly.

we should be aware that kikkat is still relatively fresh and changed a lot in this context and that devs will

eventually find ways to solve all these problems. for now we have to deal with transitional problems

and get the best out of it by making choices, means setting priorities where necessary

regards

Current Devices:

N7000, 4.1.2 Stock/TW

N7100, PacRom, 4.3.1, Pac Kernel

Nexus 4, PacRom, 4.3.1, Franco Kernel r199

I9100, OmniRom, 4.4.2, Gustavo_s CWM-Kernel, Xposed Framework

Nexus 5, Cataclysm ROM 4.4.2, Faux Kernel v05, Xposed Framework, Gamma 2.4<>2.5

---------- Post added at 12:49 PM ---------- Previous post was at 12:36 PM ----------

xposed itself works well but there are modules which interfere with rom settings.

so for help you should mention which modules you are using.

to answer your question as good as i can, yes i have problems with gravity box, so i had to switch it off

and i have no problems right now with xblast.

this again depends a lot on which features of the rom and the modules you are using. i currently use only

the dark background feature while other features, like the battery % text in gravity box was working well,

but it was showing my navbar upon every reboot while it is set to hide in cataclyms settings.

further the quicksettings in gravity box have to be set to off since they limit the cataclysm settings in a way i did not like,

while this might not be the case for others who like the settings how they work with gravity box. many things are

as well subject to ones individual likings, whether they can be considered as working well or not.

regards

Current Devices:

N7000, 4.1.2 Stock/TW

N7100, PacRom, 4.3.1, Pac Kernel

Nexus 4, PacRom, 4.3.1, Franco Kernel r199

I9100, OmniRom, 4.4.2, Gustavo_s CWM-Kernel, Xposed Framework

Nexus 5, Cataclysm ROM 4.4.2, Faux Kernel v05, Xposed Framework, Gamma 2.4<>2.5