yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] sinichi21:
Yeah thats the only issue on it once you activate the screen the BLN thinks that you already read the message and it will turn off the lights.

UPDATE: To clarify any third party app you guys use will have a problem if the app activates the screen upon receiving the notification it will disable the BLN if your third party have a lockscreen wake disable it or disable any option that will wake the screen that way it might work im using the stock messaging app and it works fine.
[Captivate Android Development] RootTheMachine:
Same, it didn't work on 3 for me either!

Edit: After following six's advice on setting cmled to 0 sec (always on), I was able to change back to the default time (1600 ms) and now bln seems to work for now. It's very touchy like this

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] scottcwhite:
How did you get it working?I followed the same instructions and am still only staying lit for 5 seconds
[Captivate Android Development] sinichi21:
Ok here try to follow this:

1. Download the BLN app on the market

2. If you are on THS build make sure that the pulse notification is check on SETTINGS > Display

2. On NStools on the backlight notification make sure that the STATUS is ON & the TIMEOUT is 0.

3. Now on NStools also on SETTINGS tab make sure that the NStools service is NOT checked

4. Now reboot your phone

5. Now go to bln control and CHECK or ENABLE the activate BLN and its done.

6. DONT use the NStools timeout settings I think its bug use the BLN app

I think the NStools have problem on the BLN timeout option the BLN app work much better i suggest who ever have problem with setting the bln use the BLN app by neldar and also the 3rd party app like sms go pro make sure you disable the screen on option to make it work.
[Captivate Android Development] drewmiranda:
I'm running the I897 with THS ICS Build 16 and have icy glitch. I start the "BLN Control" app but it says "BLN Status: not working"

Am I missing something?
[Captivate Android Development] sinichi21:
Do you have the B5 installed? The one on the op is B4 it does not have the BLN feature install this one http://xdaforums.com/showpost.php?p=22807113&postcount=546
[Captivate Android Development] drewmiranda:
Looks like I have B3. Should I update to B5?
[Captivate Android Development] scottcwhite:
Trying this now. it worked great before on b3 without bln app. First time I've ever dl'ed the actual app from market so hopefully it works
[Captivate Android Development] sinichi21:
Well B5 if you want the bln and new tweaks then go for it you can always go back to any kernel if you dont want the update
[Captivate Android Development] scottcwhite:
Sending test email now.
[Captivate Android Development] sinichi21:
I hope it work too :( im out of option to think but maybe its god's touch that mine is working ok lol
[Captivate Android Development] scottcwhite:
Nope. App didn't fix it either. Soft keys Blinked on when the email came through and and then went right back out
[Captivate Android Development] RootTheMachine:
Still not working. Oh well, by now they probably have realized that this won't be the way to go in future builds. It's back to build 4.1 for me
[Captivate Android Development] scottcwhite:
Was it working on 4.1 or was it b3
[Captivate Android Development] RootTheMachine:
Well they didn't change anything bln related until b5, but it seems as if flashing back to b3 or 4 still causes it to not work, which doesn't make any sense. Perhaps going back to the stock kernel and then glitch b3 or 4 will make it work again
[Captivate Android Development] Geoff-dev:
Rebooted this morning and now the signal strength meter seems to be working.
[Captivate Android Development] acras:
My experience with BLN

- CMLED and LED notifications in NSTools checked

- NSTools services checked

- BLN service activated in BLN pro app

- bln flashing in bln app checked

sms, gmail, e-mail work with flashing notifications during timeout set in bln app. missed calls do not.
[Captivate Android Development] imb951:
This is happening to me as well. Using the same trusty I9000UGKG3 modem and after a few minutes of using data in any app it stops working. H icon and arrows indicate activity, but nothing is transferring apparently. Anyone else with this issue? THS Build 16, started happening with Glitch Beta 4 and now still in Beta 5.

Reboot with a cache clear seems to fix it, at least temporarily. Very strange.
[Captivate Android Development] herofmm:
+1 here. It happened on Glitch V14B5, ICSSGS. Interestingly, google-releated pages are loaded. Market, google talk, and gmail works, but other things do not work ( Other non-google web pages in stock brower, xda-developers apps do not work.) I am back to Beta3 which was very stable from my experience.
[Captivate Android Development] imb951:
Same additional symptoms here.
[Captivate Android Development] ptesmoke:
glad to see im not the only one with these strange data issues. i think its related to the nexus s modem i tried...have u guys flashed one of those modems as well?

i also seen the ths dev made changes to modem in latest test kernel...are glitch using those changes? maybe its the cause? im at a loss ive been trying everything to get my modem working right but im runnjng out of ideas..
[Captivate Android Development] tbrummell:
I would like to hear the answer to this as well...
[Captivate Android Development] sixstringsg:
Live OC will almost always be more beneficial than regular due to the RAM and GPU OC that goes along with it.
[Captivate Android Development] mindphaser2k9:
But less stable.
[Captivate Android Development] jamina1:
BLN

I just installed this (have tried both version 14b3 and 14b5) along with Neldar's BLN control app.

BLN control tells me "This kernel does not support BLN"

Any ideas?
[Captivate Android Development] imb951:
I tried both of the Nexus S modems and KF1 worked for me, but not well with the upload speed cap present. KB3 didn't work at all no matter how many times i tried or what order I flashed it in. Now I'm back to I9000UGKG3 and while my speeds are great and signal is fine, my data transfer drops after a while and is most evident when streaming music when after 2 or 3 songs it stops. The bars are blue and the arrows are going up and down but nothing is actually transferring. CM9 Build 16 and Glitch Beta 5
[Captivate Android Development] ptesmoke:
same here! but H is always lit up...i dont think thats right
[Captivate Android Development] pickupman66:
I am also having data issues. was sitting last night trying to download from the market and it took 10 mins to download a 1.49mb app. this was on Wifi or 3g (h). also it owuld not connect to my work router either. only the home one.

apps would hang at downloading....

I ended up reflasing the Rom, then the theme, then glitch 14b3, then ugkg3 (the ics version) and it seems to be somewhat working now on Wifi and the microcell. Last night it would not update my apps.
[Captivate Android Development] airtower:
not necessarily...just different. You may be able to kick the CPU up to 1.6ghz alone but not with a combination of max clock and bus multiplier (114% x 1.4 max clock for example). Try more liveOC (bus multiplier) with less max clock, or more clock and less liveOC. We're tweaking a number of different hardware components now so it's get tricky to max out each of them individually such that they harmonize stably. Then of course there's voltages to consider.

but ssg is very right. you'll see more day to day improvement in the phone with liveOC increased than CPU clock.
[Captivate Android Development] krufttangoud:
After reading the LiveOC guide in the OP and a dozen reboots, my phone is running like a raped ape.

There are no stability issues if you throw out the way you used to OC/UV. My phone definitely was a High Leakage and I have found that I can't as aggressively UV as I have in the past. But Battery life has been better than in the past and I get better performance without as much OC.

Thanks Glitch Team!!
[Captivate Android Development] danix180:
I have the same problem with BLN.

I get the BLN notification for just few seconds and that it goes off.

I tried all the suggestions in this thread and none of them worked.

I'm on Team SGSICS Captivate RC4.1 and Glitch v14-B5 kernel.

It must be a kernel issue. It was working just fine on the Platypus kernel.

Any tips are welcomed.
[Captivate Android Development] airtower:
not to push apps on anyone, but CMled works as intended so long as the screen does not activate upon notification. No BLN control or messing with settings. With no tweaks gmail notifications keep the lights on. Stock SMS app doesn't allow you to disable screen on, but goSMS and possibly others do. Decent stopgap until the issue (which lies with the screen activating) is fixed.
[Captivate Android Development] prbassplayer:
Keep in mind that even if you can't reach 1.4ghz with live OC the phone will probably feel smoother, for the fact ram and GPU get a nice boost. I think the GPU is key since ICS uses hardware acceleration. But that's my 2 cents.
[Captivate Android Development] sixstringsg:
Only if you don't spend the time to work on it. Daily, I use 800 Max speed, with 15% live oc, and it flies. If I want to OC, I use a Max of 1200 then live OC from there, but I don't see a point other than high intensity games.
[Captivate Android Development] mindphaser2k9:
I will try your advice with 800 Mhz + 15% OC, thanks.
[Captivate Android Development] sicmadek:
on stock kernel voltages?
[Captivate Android Development] pickupman66:
Hey, for those with a data issue. I jsut saw this in the ICSSGS thread. Might be worth checking out. I am going to try it.

http://xdaforums.com/showthread.php?t=1362092&page=561

Summarized:

basically the APn settings are not fully populated with port and proxy.

go to settings > More > Mobile networks > Access Point Names > ATT then look for the Proxy and Port right under the APN.

use wireless.cingular.com for the proxy and 80 for the port. leave the rest alone....
[Captivate Android Development] ptesmoke:
thanks bud. added it in.

will report back but i can confirm i still have the "stuck on H constantly" issue.
[Captivate Android Development] pickupman66:
mine woud flicker between 3g and h. but would only go to google.com. would nto go anywhere else. sometimes email woudl go thru but rarely.
[Captivate Android Development] RootTheMachine:
My guess is stock int voltages with some undervolting on the arm voltages

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] eddalysse:
Sorry if this was mentioned before, but I've been trying to restore a backup in cwm and it gets stuck in data. Switched kernels in order to flash the backup after several tries. Flash v5 and tried to backup and again it gets stuck at data
[Captivate Android Development] ptesmoke:
mine did this too! wtf?
[Captivate Android Development] shaker2k:
That has happened to me before. Now I just wipe everything (data,dalvik, cache, then format system in advanced).

Then I use titanium back up and use the market.
[Captivate Android Development] eddalysse:
Yes, thanks, I normally do that when switching ROMs, but I was trying to skip those steps, sinse I was trying an update from a ROM and didn't like it so I wanted to go back to my previous settings the "easy" way. Needed to switch kernels in order to finally get it done. The question is if it's a "bug" in V5 or in all the latest realeses?
[Captivate Android Development] shaker2k:
Yeah I have up on the easy way after it happened three times in a row. :sly:
[Captivate Android Development] voldomart13:
I just noticed this when I was reading the OP it says that beta 4 is the newest relaease but i'm running beta 5. And is anyone else having problems taking backups in cwm?
[Captivate Android Development] eddalysse:
Yes, stated a couple of posts back. Can not restore or make nandroid backups, it gets sucked at the data part, system and boot restores/backups fine, but gets stucked at data
[Captivate Android Development] topiratiko:
Restoring twice works fee me

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] eddalysse:
Tried it several times no go, switched kernel and worked. Don't get me wrong I love this kernel and all it's features. But not being able to make a nandroid backup is a big issue for me.
[Captivate Android Development] RCDuke:
I have been able to make backups via nandroid. It seemed like it was stuck on the data part, but I just waited a few extra minutes and it worked for me. Have not tried a restore though.

THS build 16 with kernel version b5.
[Captivate Android Development] drewmiranda:
I gave up on bln (at least for now) and installed NoLed. Works well.

Sent from my SGH-I897
[Captivate Android Development] eddalysse:
Will try then and post feedback
[Captivate Android Development] pickupman66:
Fwiw. 3 hours since changing apn info per my post and data still rocking....
[Captivate Android Development] sixstringsg:
For the 800, yes. For the other, that would be asking a lot of the CPU without extra power.

We're working on it.

I've been working 18 hour days this week, so the OP hasn't been updated
[Captivate Android Development] topiratiko:
Data DOES take a long time to back up or restore not sure which one because the flaw is it doesn't show files being backed up. Give it a good 5-7 minutes

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14B5
[Captivate Android Development] scottcwhite:
Just a when I Thought was starting to get this oc thing I read this and get lost again. I've read the oc guide 5 times now. I thought the highest Max you could go and still be stable was the idea. I'm well over 800. And I just can't get this voltage/leakage thing. I haven't touched the settings cause I don't get the difference between arm/int. What do I set them to to benefit battery, etc. up? Down? Both? Are my settings below way to high?
[Captivate Android Development] sicmadek:
Yea i dont understand it either. Even at 800 with 110% my phone starts freezing up.
[Captivate Android Development] mikel.canovas:
There's not going to be one guide or setting that'll work for everyone. You have to test it out for YOUR device. Lower CPU speed will be more battery friendly along with lower voltages. Int voltage is ram and CPU. Arm voltage is for the arm chip... I.e. the CPU. Lower CPU speed and higher live oc is good for ics
[Captivate Android Development] scottcwhite:
The first time I read the OC guide I thought no prob. Read this and I'll understand how this whole oc thing works. Then I started reading and realized that it was way above my pay grade
[Captivate Android Development] prbassplayer:
The int voltage is already set to high leakage. Meaning it will be stable with "most" devices. I would recommend trying to lower with arm voltage (no live oc first.). Once you get it stable start playing with Live OC and once you find the max stable revisit arm voltage. Keep at it until you find the sweet spot. You can attempt playing with Int voltage but keep in mind it's really sensitive and it's already set really close to max volt.

That's my method of getting it. My phone can handle 1300mhz @ 115% but browser and Pulse start to mess up anything past 108%. So unless I'm playing a very heavy game I run lower. Tough Sixstring gave me a idea.
[Captivate Android Development] sicmadek:
So far i dont think my phone likes anything over 105%
[Captivate Android Development] galakanokis:
thanks for this. On the phone and can't hit the thanks button. Trying these settings and working nicely. B5 has been working well for me.

Sent from I896 running ICS
[Captivate Android Development] leezrd:
Have you tried 800 mhz then live oc. I can get 120% running smooth like that. Even 1ghz at 120% and my phone hate oc
[Captivate Android Development] scottcwhite:
Only adjusting one works for me. One less thing for me to mess up. My live oc is at 110% now so I'll dial that back to 100% and then start lowering arm values. Is 25 decrease top to bottom a good value to start at ?
[Captivate Android Development] sixstringsg:
General now on OC: this is kinda of a combo of answers to questions I've seen. The goal isn't always to OC the most. It really depends on how you use your phone. If you're a gamer, Max OC is what you want. Otherwise, all you really need is a little faster GPU to make ICS fly. That's why I clock to 800 then live OC.,I get all the smoothness I need from that. If I missed a question, post in the live OC thread
[Captivate Android Development] pickupman66:
Sixstring.. I learned alot with your previous post. I am not a gamer on mine. it is more of a business device that I use to surf the net and occasionally some angry birds...

I was just doing some really low voltages in both the arm and int. device was very stable. im going to tweak them a bit with your settings...
[Captivate Android Development] 13_:
Long press post, select thanks, profit???

Sent from a device powered by hamsters.
[Captivate Android Development] tkjeeper:
I don't have the thanks option...

Sent from the frozen tundra known as Canada.
[Captivate Android Development] galakanokis:
Long press post, no thanks to select, you send me money?

Sent from I896 running ICS
[Captivate Android Development] capocaccia:
Hahahahahah.

But seriously, how do I get the COD and SOD to stop? It happens whether I use platypus or glitch. I just want stability!
[Captivate Android Development] shaker2k:
It could be so many things. Including the manufacture date of your phone.
[Captivate Android Development] capocaccia:
Ok Ill try to go through it all here.

Rom: ICSSGS RC4.2

Kernel: Glitch V14B5

Modem:I9000UGKG3

Build: 1007

Bootloaders: Gingerbread

Battery: Anker 1800mah

Never OC or UV. Never used DIDLE. I use wifi all the time at my house so my wifi was on when these SOD and CODs have occurred.
[Captivate Android Development] RootTheMachine:
Does v14 use the same default voltages as v13? I frequently reference the voltage table in the v13 thread and wonder if it's the same

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] sixstringsg:
I know the int is different, I would have to check on arm.
[Captivate Android Development] vbenkovskyy:
How about touch recovery for Samsung captivate? It's it real?
[Captivate Android Development] sixstringsg:
It is not in the SGS series yet last I checked.
[Captivate Android Development] ptesmoke:
its honestly cool for about 5mins then its a pain in the arse. i still much prefer the button controlled cwm, im way faster with the buttons lol.
[Captivate Android Development] Sepharite:
Sometimes my screen goes CRAZY, artifacting everywhere... is it because I overclcoked the phone to 1.2Ghz? It happened twice in this week, once just now.
[Captivate Android Development] daskanda:
Happened to me before too it's your voltages play around a bit more with your oc and int voltages..... It's a sign of instability
[Captivate Android Development] TheSoaresan:
Stop taking drugs around the cappy. It gets high via osmosis...
[Captivate Android Development] mindphaser2k9:
It may be. My Cappy worked stable on Froyo's Onix kernel at 1400MHz, then on GB with Talon it was running fine at 1300MHz. But on Glitch it can sporadically reboot even on 1100MHz or at 800MHz +115% LiveOC. With 120% LiveOC hanging is 100% guaranteed even on 800MHz. So I set 1000MHz with 108%, resulting in 1080MHz CPU freq, seems stable now. Maybe just a weak CPU.

I wanted to play with voltages but I don't know how to test stability then. Stability Test app works fine but then the phone can hang or reboot when market or player is started. Ok, the CPU+GPU stability test there made a reboot with 110% (CPU 1100), so this may be a proper test. Talon voltages seems about the same as in Glitch (though INT voltages in Talon are higher), so what's the problem? Do I need to increase INT voltages?
[Captivate Android Development] daskanda:
Check the live oc guide by tk-glitch in op there's some very good examples of voltages on almost every page and guides on how to stress test properly
[Captivate Android Development] mindphaser2k9:
Well, I have been set the voltage settings from Talon and what I've got: with 115% LiveOC at 1380 MHz CPU the CPU+GPU stability test worked about 10 minutes, then it crashed with 3 GPU errors, but no reboot this time! Then I've been set 112% at 1344MHz CPU and then CPU+GPU stability test crashed after 16 minutes but without GPU errors this time! The error in log was related to SurfaceTexture and libc. I'm pretty happy with such a result, seems those voltages finally made my phone stable :) The question to the Glitch team: why you don't use those voltages by default?
[Captivate Android Development] mindphaser2k9:
Now I see that I have a high leakage CPU, I have been set correspondent voltages from tk-glitch guide, it works slightly less stable then before on highest frequencies (with 1250mV INT I set before) but stable at 1320MHZ/110%, which is pretty good for me. Thank you for helping me to figure out this.
[Captivate Android Development] bentonhall:
I have this same problem. The LED implementation in B3 worked fine for me. I haven't tried B4. I didn't have any issues with B3 so I may revert back to it.
[Captivate Android Development] space_eyes:
OK found out the hard way, but I don't think this is nandroid friendly, not with sgsics anyways... running with icssgs I made a backup, went to restore and it crashes at restoring /data. Tried manually restoring just get stuck at boot screen. Was able to just install rom without kernel, nandroid test backup/install successful. So that leaves rom/kernal combo on my cappi = bad nandroid. "I'm doing it wrong..."
[Captivate Android Development] scottcwhite:
Won't do you any good. Don't know why either. I switched yo another kernel than back to b3 and it still wouldn't work. Worked before on b3 but seems that whatever changed that lost it losses it for good
[Captivate Android Development] sixstringsg:
Reflash your ROM, then B4.
[Captivate Android Development] scottcwhite:
Keep in mind I'm on a ROM not supported by kernel so I just deal with lost bln but will try this
[Captivate Android Development] Tsaukpaetra:
I think I saw something like this on the cm9 section, it freezes for a while but eventually goes through.

Sent from my SGH-I897
[Captivate Android Development] scottcwhite:
That fixed the BLN app so big thanks. I guess I'll stay on 4 until a fix a later release
[Captivate Android Development] Koizuma:
Since I read that, I gave that a go myself, clocked to 800MHz, with 125% LiveOC so my max is 1000MHz and this phone flys so far.
[Captivate Android Development] danix180:
It is for me. I got exact the same problem.
[Captivate Android Development] :
Just reminded me, when I saw this post I tested and use 120% live OC clocked at 1000MHz so Max it's 1200 MHz. Previous Max was 110% live OC at any clock speed above 1GHz
[Captivate Android Development] nsyik:
Hopefully there will be a release to support dark knight rom(4.0.4) coz this is the smoothest kernel i have ever used on cappy.... BEST GLITCH
[Captivate Android Development] imb951:
THANK YOU!!
[Captivate Android Development] Oxicottin:
4.1 works the old way without BLN control and it doesnt even have it. the only thing that sucked is you have to reflash ROM then flash the 4.1 kernel.
[Captivate Android Development] RootTheMachine:
That's what I did

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] scottcwhite:
Same here. Not a big deal though to get it working again on ICSSGS
[Captivate Android Development] bloodhawk:
Same issue. Any idea how to make a backup?

Or only way is to go back to stock kernel and then do it?
[Captivate Android Development] acras:
Just have done it this way. Flash stock, backup, re-flash glitch.
[Captivate Android Development] Malorkus:
For the LED notification/BLN issue, someone mentioned earlier in the thread that if you have or buy BLN Control Pro and enable blinking lights it works with this kernel. For me this was a fine solution since I don't mind throwing $2-3 at a dev with a useful application..
[Captivate Android Development] loserskater:
Blinking uses a lot more battery than just keeping the lights on.