https://forums.androidcentral.com/e...bmRyb2lkLmxpZ2h0Zmxvd2xpdGUiXQ&token=N7FANsuy..
Hi,
Just a quick message to say I've finally pushed a new version of light flow v3.1.0 into the play store.
It adds flashing rates for root s3 users.
It also adds compatibility for non-root users (including flash rates).
Things to note:
- The flash rates use more battery than the always on option in the app.
- The led can take a little while to "settle down" once the screen has been switched off. This is because we have to battle with Samsung's default blue flashing light.
Note it may take a few hours to show on the market as it can take a while to replicate across all the google servers.
Thanks
UPDATES from the dev's blog:
23 August 2012 - seems to be working for some people more than others. Fixing one or two bugs and investigating others. Note I've only one more day left to look at this before going on vacation (being from the UK I would call it a holiday ) for a couple of weeks. Hopefully I'll manage to get another release out to fix some issues before then.
24 August 2012 - Anyone familiar with logcat who's got the blue flashing light issue?
If so I would love some logcat output. Go into light flow, tools, logging and select "console logging". Then run logcat, get a notification and wait for the blue light to start flashing (after probably initially having the correct color). Then send me through the logs to the e-mail address shown on the market. Thanks
It seems like the blue light issue is related to what method of security you have on your lock screen. If you have no security it seems to work, other methods seem to cause it to allow the default blue to flash. I think our code that's running behind the scenes it maybe not allowed to run that clears the blue light when the screen is locked.
Hi,
Just a quick message to say I've finally pushed a new version of light flow v3.1.0 into the play store.
It adds flashing rates for root s3 users.
It also adds compatibility for non-root users (including flash rates).
Things to note:
- The flash rates use more battery than the always on option in the app.
- The led can take a little while to "settle down" once the screen has been switched off. This is because we have to battle with Samsung's default blue flashing light.
Note it may take a few hours to show on the market as it can take a while to replicate across all the google servers.
Thanks
UPDATES from the dev's blog:
23 August 2012 - seems to be working for some people more than others. Fixing one or two bugs and investigating others. Note I've only one more day left to look at this before going on vacation (being from the UK I would call it a holiday ) for a couple of weeks. Hopefully I'll manage to get another release out to fix some issues before then.
24 August 2012 - Anyone familiar with logcat who's got the blue flashing light issue?
If so I would love some logcat output. Go into light flow, tools, logging and select "console logging". Then run logcat, get a notification and wait for the blue light to start flashing (after probably initially having the correct color). Then send me through the logs to the e-mail address shown on the market. Thanks
It seems like the blue light issue is related to what method of security you have on your lock screen. If you have no security it seems to work, other methods seem to cause it to allow the default blue to flash. I think our code that's running behind the scenes it maybe not allowed to run that clears the blue light when the screen is locked.
Last edited: