yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diablo009:
Looks like you enabled "talkback" when you were enabling accessibility settings for this app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brawndo89:
Nope. I looked online and it's happening to a lot of Samsung users. I thought that at first too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
I had this issue before, it went away though.

The way I solves it was disabling or freezing a few apps. I can't remember what they were called, look for stuff like pico TTS, Google speach, tapatalk, text to speach etc.

Also make sure you don't accidentally check Enhance web accessibility, in i believe it's accessibility setting. Now that I think of it, that might be what solved the problem in the end, making sure it is Disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingofdevils:
Hello, I have a curious issue; When I use Light Flow in my SGS3 (Europe) never enter in deep sleep. I try some configurations and I have same issue. Curious is first time I install it, SGS3 enter in deep sleep, but after first charge always works at 200mhz, never enter in deep sleep.

Sorry for my english!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
Try the following:

Go into your phone settings, accessibility and switch off and back on light flow.

Go into your phone settings->apps(or applications)->select light flow and make sure "show notifications" is checked.

Then restart your phone (ie power it off and back on)

Go into your phone settings, display, led indicators and make sure only "notifications" is checked.

Go into lightflow, settings and make sure all of the following are off:

Direct mode

S3 root mode

USA/Canada S3 mode.

Then go into lightflow, notifications, missed call and select the color red.

Press the phones "home" key and switch off the screen.

Then try get a missed call and see if the led flashes red.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingofdevils:
Thanks Andrew! now notifications works succesfully. I´m try to charge and see if deep sleep works properly after one or two complete recharges.

EDIT: Deep sleep works properly too!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JuanG:
Hi! I'm having some issues with wakelocks and LightFlow. I saw that while LightFlow is installed and wifi is enabled I have a lot wakelocks from wlan_ctrl_wake and wlan_rx_wake. I can't ensure that the wakelocks are originated by LightFlow but I have made several test and these are the results. If the wifi is disabled, that doesn't happen.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
As lightflow doesn't have any association with wifi (or use any data connectivity) I can see how the two would be related. If you can try without wifi to see if you have the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JuanG:
You are right. I confirmed it with some new tests. The wlan wakelocks are originated by any application that require transmit or receive data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SoundsLegit:
I have a no rooted stock rogers i747m and this app talks when I move around on home screen and open folders. It starts announcing things. I have talk back disabled.... What gives.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diablo009:
Could you please add an option (atleast in the paid app) to allow the amount of time to test each color, or an option to test the color of an app right in the apps page itself, than go out, and then through a different menu? Its a lot time consuming to test for a color, esp if there are like many apps in the list.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
so, sorry to ask this, I did not really get any info in the last few posts.

are the wake lock issues resolved yet? I love the concept of the app, but it is a bummer that it eats my battery!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
See here: http://www.folioflow.com/lightflow/samsung.html

Samsung finally look like a fix will be coming with android 4.2

---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------

If you are on android 4.1 and don't use s3 root mode or s3 usa/canada mode it should be fine. Those other options were really there for the bugs in the samsung drivers for android 4.0

---------- Post added at 11:13 PM ---------- Previous post was at 11:13 PM ----------

There's a little test tubes icon at the top of the notifications pages which will just add the current notification into the stack of currently outstanding notifications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JuanG:
I think that a good new feature would be to add an option that allows configure a time between same notifications. For example sometimes in whatsapp groups there is a notification every 5 second when there are too many people in the group. An option that allows configure the time between one notification and another of the same type would be very useful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akulp:
Is there any chance to turn off "Light Flow Notification (Tap to celar manual notification)" in (upper slide down) taskbar?

Its annying, because every time my phone call ends there's a notification up there? Why? Is there any setting for that?

Same problem is if I get SMS. I get light flow notification. I tap new message notification in taskbar, i read message, but "Light Flow Notification (Tap to celar manual notification)" message in tasbar is still there.

I have to confrim and tap it again to release LED light....

Android 4.2.2, stock ROM, nexus 4.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moe6:
Anyone else getting immediate force closes with the new update today?

Had to clear the app, seems to work now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nephilim:
The FC's are due to the new gmail update. I am not going to update gmail until light flow works with it.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mistic92:
Update on the way :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
Handcent

I am going to try LightFl w again, on my S3 (AT&T) , and so far it seems ok, but I do need to check wake locks. But with that being said, the only issue that I am having is that Handcent pro's notifications are not working. I have Handcent setup so that different friends txt me, the light is a different color, for Example Steve is Green, Erin is Purple, etc.

right now, when I get notifications from handcent, I get no lights at all.

Ideas? help, please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
The update has fixed the crash but I can no longer get LED notifications for Gmail. Is is working for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
I'm planning on adding it in.

---------- Post added at 07:07 AM ---------- Previous post was at 07:06 AM ----------

Which version of android are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DerKiLLa:
Everything is fine with the update, thank you ;)

No problems with gmail notification, but i deacitivated and activated it to be sure and it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
I'm on a rooted, custom 4.1.1 rom (LoserROM). In LightFlow settings, I'm using "Samsung S3 Root Mode".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
Here are some of the things I've tried so far with no resolution:

I cleared all data from both Gmail and LightFlow and then uninstalled them both in order to reinstall and reconfigure from scratch. I tried with and without "Root Mode". I've tried the various option within LightFlow for "Clear notification style".

According to the debugger widget, the notification is being recognized by LF but the on and off times always differ by 0.001 seconds so the LED is being switched on and off so quick, it cannot be seen.

Hope these details help.

P.S. One other oddity; I now have a notification for Google Now in LF that is enabled by default and it cannot be edited. I don't use Google Now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moe6:
Latest update fixed the issue :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
And you have a Galaxy S3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fevves:
Sorry for this, but I don't know where else to post since I have SGS II and not III. Still, up untill yesterday my gmail and light flow worked just fine. Now I have latest gmail and latest LF 3.60 and it won't light up fron button leds anymore.

I'm on custom ICS 4.0.4 with BLN enabled kernel which works just fine with old versions and I keep on thinking of reverting to old versions throught TB, but I wouldn't want to lose updated features of both apps.

Is there a way to get front button leds lit back again with gmail?

Again, sorry if this is not appropriate to ask here, but no SGSII dedi thread exists so to ask there.

ps: Andrew, I think most of the people that are posting on the Store and having SGSII don't have a slightest idea what they're talknig about, nor they have rooted phone with BLN enabled kernel.

TIA.

Edit: Reverted back by uninstalling gmail update in my system, apps option and front led buttons are lit again. Still, I'm on old gmail 4.0.5 bersion for the moment. Hope this helps somehow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psenseny:
I emailed Dev and he knows of this issue and will have a fix shortly. This Dev is awesome!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
Thanks for the help! And I agree; one of the best devs going.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
Latest update (3.6.1) has everything working perfect again. Love this app!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] khuls:
This app is wonderful, I can't imagine using a phone without it. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lesp4ul:
How to disable talkbalk on S3? I already removed talkback.apk but it still active..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reksikana:
Nice App

Not practical to be running all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
If you've figured out a way to do that for an app that is capable of intercepting all of your notifications, please email the developer as I'm sure he would be interested in understanding how that's done. In the meantime, I'm perfectly fine with the 15MB of RAM being consumed on my phone, considering all that this app does for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
See this thread http://developer.samsung.com/forum/...=GeneralB&messageId=204387&messageNumber=2156

Especially 15th march post where samsung say they've fixed the issue and it'll come in their next software update.

---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------

I'm also hoping to reduce the memory footprint of the app as I've a few ideas of things that I can do about that :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericjackson:
Is it supposed to use this much battery? I've tried different settings. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
No that's not normal. Try switch off root mode, s3 root mode snd usa/Canada s3 mode if they are on. They were really for s3's running android 4.0 with Samsungs buggy led drivers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericjackson:
Thank you. Root mode was on. I'll try it today and see how it goes. Love the app and so does my wife. It's always good to see a developer on forums helping others as well as themselves to make their apps better than the rest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
What are known issues if running stock touchwiz based ROM? Is the talk back issue the only one?

And is it correct that I should not check the root mode box or the s3 us/Canada box?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
As long as you are on android 4.1 or above don't check the s3 modes as you'll have fixed drivers.

For full details about the accessibility bug see here www.folioflow.com/lightflow/samsung.html

Check out the link to Samsungs forums in this page too .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Annita:
Great App!!! I hope this is not answered yet but I have a question though, I would like to know where the backup file is saved when I create a backup of the settings? It will be very helpful to know where it's saved (add it to the FAQ) or let us select where we want to save it (it would be great to have it in the external memory, as I think it's now stored in the internal one).

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewpmoore:
It's stored onto your sdcard (or virtual sdcard on devices without one), then just a /lightflow directory. You should see the file names matching the backup names. The file can be read in a text editor.

I'll add it to the faq. The app itself uses an internal stored version of the settings, but the backup is external to allow you to transfer or keep a history.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jp0469:
The latest version (3.6.3) is causing lots of wake time for me. Strange because I've never had wake lock issues with this app. I've tried both with and without root mode. (I typically use the Galaxy S3 root mode option because I like being able to have the LED on even when the screen is on.) I've rolled back to 3.6.2 for now but I though I'd share just to see if other are experiencing similar issues.
[T-Mobile, Samsung Galaxy SIII] jroyjohnson:
the developer has claimed the latest version on the play store is working for rooted phones, but I still am not having the best of success. I thought I'd start a thread and see how others are fairing.

The newest version has some improvement; being able to select different colors for different notifications and actually getting them to go off when you've pulled down the notification bar. however, it doesn't blink for me at all. When i get a text or email the corresponding light is a steady constant light if the screen is asleep. If you wake it up the light either disappears or only lights up very infrequently.

I've read some posts before the latest versions came out that some users had success getting it to work by actually turning Accessibility off. This seems to turn off the entire app for me.

anyone having better luck?
[T-Mobile, Samsung Galaxy SIII] xanderdad:
I have had the current version working correctly both on a stock TW rom, and now on CM10. The flashing lights haven't been implemented yet, however he is working on it.

The only thing I had to do on the Samsung TW rom was disable Samsung TTS in the manage apps settings. Once I set it to S3 root mode, everything worked perfectly.

I suggest you follow his blog here:http://www.folioflow.com/ff/page/website/lightflow/pageId/1826
[T-Mobile, Samsung Galaxy SIII] jroyjohnson:
I have done all that including following the developers blog. I have accessibility on, only have the light flow notifications turned on, allowed SU access to light flow app, and have tinkered around with it all weekend but it still isn't working correctly. It works fine when the screen is on, but when the screen is off it gives a solid light.
[T-Mobile, Samsung Galaxy SIII] xanderdad:
Its not supposed to blink get, that's why I linked you to his blog.
[T-Mobile, Samsung Galaxy SIII] -FuRBz-:
A blinking light will kill the battery or at least use more juice. Dev did say he is looking into that feature tho
[T-Mobile, Samsung Galaxy SIII] JawjaBill:
Developer advises blinking uses more battery than solid notification. Go figure.
[T-Mobile, Samsung Galaxy SIII] civicvx94:
Since I installed Light Flow, whenever the screen is off the LED glows a faint green. First I disabled Light Flow and the led still glows green. I unchecked it under Accessibility and rebooted, still green. Just had to uninstall and reboot to get it to stop. Anyone else have this issue? Is there a setting I'm missing somewhere?
[T-Mobile, Samsung Galaxy SIII] oilfighter:
I had that issue when I restored from an old version of light flow. The newest version that I installed straight from the Play Store works fine.
[T-Mobile, Samsung Galaxy SIII] doubleohseven:
I believe to get other colors other than green, you need to be rooted and go into the app settings and check "S3 root mode" or whatever its called...

Works perfect for me.

EDIT: I think the updated app (as of today) should work whether your rooted or not.
[T-Mobile, Samsung Galaxy SIII] xanderdad:
The update version today also supports blinking in adjustable intervals.
[T-Mobile, Samsung Galaxy SIII] DOG666:
You guys should just install cm10 on your phones, it already comes with notification light settings & it works perfectly :good: :)
[T-Mobile, Samsung Galaxy SIII] SmokeRob:
I would agree with that almost fully except it's a pain setting up different notification sounds between e-mail and sms/mms. It's also nice to be able to have it make notifications at intervals from missed calls/sms and the light to go away eventually if you want.

But I do have to say, I'm on CM10 - Paranoid Android ROM(latest build) and light flow is working like a charm for me right now. Looks like the bugs have been worked out for the most part.
[T-Mobile, Samsung Galaxy SIII] zappoo:
Hi guys.. I have an international S3 and since a recent Lightflow update, I regularly get lightflow causing wakelock for hours. even with no outstanding notifications. I've uninstalled, re-installed - same problem.

Happened 3 times this week. reboot fixes it.
[Desire Q&A, Help & Troubleshooting] the catfishman:
I've been happily running CM7 for the past year and yesterday while I was browsing the phone suddenly turned off and starts bootlooping, I then tried to get into recovery to flash one of my backups but I couldn't get into recovery anymore. I can get into the bootloader (vol down, back and power key) but if I select recovery from the menu it starts bootlooping again. I was hoping someone knows what's going on.

I used revolutionary to root the phone, had clockworkmod recovery installed (don't think it was the latest version, haven't updated it since I've installed it a year ago) and was running CM7.2 (latests stable version).

I also apologise in advance because you guys must be sick of people asking what to do with a 'bricked' phone but I'm still hoping someone can help me.
[Desire Q&A, Help & Troubleshooting] nlooooo:
You have the explanation how it all works in my signature.

Just flash recovery.img via fastboot.

Sent from my HTC Desire using Flashes and Thunders
[Desire Q&A, Help & Troubleshooting] the catfishman:
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.
[Desire Q&A, Help & Troubleshooting] nlooooo:
Not sure what link you said is dead, they all work. I meant on this one "Before Crying for Bricked Device - How Nexus One and HTC Work ".

All you need is recovery.img download it from here:

http://www.clockworkmod.com/rommanager/

and flash it via fastboot.
[Desire Q&A, Help & Troubleshooting] handy5876:
Both your ROM and recovery are bootlooping. But importantly your bootloader is fine and therefore you can easily recover. First get your recovery in order by flashing recovery from fastboot. Thereafter when you are able to get into recovery flash your ROM in the normal manner or restore your nandroid.
[Desire Q&A, Help & Troubleshooting] the catfishman:
Thank you both! I flashed the recovery.img and could get into the recovery mode again! it's restoring my last back up as we speak, so hopefully it's working again.
[Desire Q&A, Help & Troubleshooting] nlooooo:
If it all work go here:

www.4ext.net

and get rid of that buggy cwm recovery.
[Desire Q&A, Help & Troubleshooting] the catfishman:
Well.. today it started bootlooping again in the same way as described in the first post and now the method I used yesterday to fix it doesn't work anymore. If I flash a new recovery.img now and subsequently try to go into the recovery mode it starts bootlooping again... so now I'm wondering if I should just flash the RUU via pc to at least get my phone working again... do you guys think that would work?

edit: can I even run the RUU in fastboot usb?
[Desire Q&A, Help & Troubleshooting] handy5876:
RUU is the solution if all else fails. But only use 2.3 Android RUU. And remember to downgrade hboot first.

Before you get into that I would try :-

- Flash a different recovery and try to get into recovery. But this time dont restore your nandroid. Flash a ROM afresh.

- Remove your sdcard and try to get into recovery. Wild guess !

- Also try formatting your system, sdext etc partitions as given in Bortaks thread.
[Desire Q&A, Help & Troubleshooting] the catfishman:
I tried flashing a different recovery (amon ra) but that also didn't work, when I tried to get into recovery mode it got stuck on the HTC boot screen (with some weird extra lines through the image).

I will try to remove the sd card.

Another weird observation, the phone doesn't seem to be charging anymore, at least... the led doesn't turn on when it's plugged in.. :confused: it get's weirder and weirder.
[Desire Q&A, Help & Troubleshooting] jmcclue:
like handy says full wipe, wipe/factory reset, wipe dalvik and format all partitions except sdcard then do a clean install of a different rom. restoring the nandroid, u could just be restoring the problem.

edit: just read ur post bout charging, looks like HW not rom or recovery problems

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] the catfishman:
yeah but the weird thing is that this started this morning, I charged it last night (when all of this stuff was already happening).
[Desire Q&A, Help & Troubleshooting] nlooooo:
Run 2.3 ruu as fast as you can, you're on a good way to hboot or radio brick.

:banghead: constuction material guaranteed...

Sent from my HTC Desire using Flashes and Thunders
[Desire Q&A, Help & Troubleshooting] the catfishman:
Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.
[Desire Q&A, Help & Troubleshooting] nlooooo:
You can easily go s-off and root now just go here:

www.revolutionary.io

And the rest is history...

Sent from my HTC Desire using Flashes and Thunders
[Desire Q&A, Help & Troubleshooting] the catfishman:
yeah, I will probably do that in a few weeks, I just moved to another country 2 days ago so I kinda need a functional phone these weeks... aand.. thanks for the help guys
[Xperia Play Q&A, Help & Troubleshooting] mohammed arbad:
i was install ics on xperia play and i can't operate any games like 9mm or nfs hot pursuit
[Xperia Play Q&A, Help & Troubleshooting] jeff7424:
ICS isn't for gaming. If you want best gaming performance I suggest you to roll back to GB.

Sent from my awesome Xperia Play
[Xperia Play Q&A, Help & Troubleshooting] fma965:
what do you mean "operate"? do you mean they don't load or touchpads don't work? or what?
[Nexus 7 Q&A, Help & Troubleshooting] sfunk:
Hi There,

I am considering getting a Nexus 7 to read books and also to record band rehearsals. What is the quality of recordings like made with this thing? How sensitive is the mic? Can it record loud sources without clipping? A full band rehearsing? A drum kit?

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] bkmaracas:
http://i.minus.com/jJJXARjnjx2j7.wav

Little bit of guitar here to give you a clue, was my first test. N7 was sat on a whirring laptop. Isnt too bad, little bit sizzly, fixable with eq tho. and your band may be loud for it, but some physical filter or placement should resolve that after a test run. Guitar is suitably complex sound so decent indicator-

This is recorded16bit 48k (tape machine app) wave - as good as we can get quality wise.

Some playback apps expect 44k so may playback weird on a n7 but you haven't got one yet so no worries!

Also was pretty easy to upload this to minus just nowfrom the n7 so that's good too. :)

Sent from my Nexus 7