Database Info

BLN Pro

I'm not really sure what forum to add this to, so please excuse if its on the wrong one. I would like to install the BLN app, but I dont know which kernel to use, or if its even supported. I found a thread here that showed an infuse kernel, but it looked like it made a whole bunch of changes, all i want is to be able to use the bln app if possible. can anyone point me in the right direction, or know if this app can even be used with the infuse? thanks!

I THINK you can use BLN with the froyo roms but it currently does not work in any GB ROM. I'm still relatively new to infuse and never used any froyo ROM besides stock. I know for certain its a no-go in GB. Causes too many instability issues. I would check bedwa's earlier infuse kernel thread. He seems to be the go-to Guy for kernels. The thread mentions its for froyo in the title and should say if BLN is supported in the first post.
BTW, I'm not aware of any kernel that turns on just BLN.

BLN is in Defuse 1.5 and the latest Infusion Froyo releases, HOWEVER:
It's flaky as hell on Froyo and for some people may have caused system stability issues.
Every attempt at implementing it in Gingerbread led to unstable devices - Bozo or another kernel dev might take a crack at it again sometime, but since it's proven to be such a pain it's a low priority while there are bigger fish to fry.
I can tell you I won't be putting any effort into it - the feature is just not worth enough to me to justify the level of effort required to get it to work in a stable manner.

Yeah I'm back on froyo and using the infusion kernel and the bln gets really annoying. Especially since it won't disable for me.
Sent from my SAMSUNG-SGH-I997 using xda premium

why is it so flakey?? it works great on my galaxy s i9000t with speedmod kernel in froyo? is it just that the developers of the bln enabled kernels have not taken the time to integrate it correctly?

lgkahn said:
why is it so flakey?? it works great on my galaxy s i9000t with speedmod kernel in froyo? is it just that the developers of the bln enabled kernels have not taken the time to integrate it correctly?
Click to expand...
Click to collapse
We have a different touchkey controller chip - it's annoying. Every attempt to implement BLN for this chipset has resulted in:
1) Weird flaky timing - this is due to the architecture of the touchkey controller driver in Froyo, it's very BLN-unfriendly
2) Random reboots - trying to add BLN into the Gingerbread version of the touchkey controller driver causes a lot of potential nasty race conditions involving entering/exiting suspend. Every time LinuxBozo found a bug and squashed it, another bug surfaced. After a week of messing with it, he ripped it out and we're focusing on other higher-priority stuff like Bluetooth for CM7.

Yeah I switched back to the community kernel from the infusion kernel on infused 1.6. The lights blinking were totally random and there wasn't even a notification. When I did have a notification the lights would just stay on. And like I said, this was with bln friggin disabled! Lol. I've never cared for the feature to begin with. Not that hard for me to push the power button and see if I have something.
Sent from my SAMSUNG-SGH-I997 using xda premium

Captivate switched to LED notifications?

Hey, lately my captivate decided to switch its notification ways. Instead of vibrating and showing that i got a text at the type, it just stays silent and turns on LED home buttons. I have no clue what i changed. I don't have any LED hack apps. If this happened to you, please help. Thanks
Captivate
Froyo
Rooted

Perhaps you flashed a new kernel w/ BLN (Back Light Notification)...

phrix626 said:
Perhaps you flashed a new kernel w/ BLN (Back Light Notification)...
Click to expand...
Click to collapse
This and more information would help. What rom and kernel are you using?
Sent from my Captivate

curti.nogg said:
This and more information would help. What rom and kernel are you using?
Sent from my Captivate
Click to expand...
Click to collapse
i cant 100% remember, it's stock room, but i think i flashed a speed kernel. ill try to google and find it
i think this was it and yea has some bln crap...
http://forum.xda-developers.com/showthread.php?t=893880

AVega5 said:
bln crap...
Click to expand...
Click to collapse
Thats a matter of opinion
Some people flash kernels for bln alone

BenKranged said:
Thats a matter of opinion
Some people flash kernels for bln alone
Click to expand...
Click to collapse
crap for me lol
i used the bln control app, but now after my phone vibrates on a text the notification goes away and is freezing up
EDIT: It's fixed now woot, thanks guys. Now I just have to find out why it's been freezing up today, I ran the stability test and neocore for 10 hours as I was sleeping and no errors came up. Will do again tonight.

Freeze issue on Imnuts' 1/15 kernel

I'm having an annoying issue with my Charge. Whenever I try to record with the Camera the phone just freezes and reboots after about 10 seconds. Yes I'm undervolted, which is what I'm suspecting as the issue but I went into Voltage Control and set the voltages back to 0 and to no avail, it still just froze and rebooted. I tried overclocking to 1.2Ghz without undervolting that clock speed at all(1GHz and below were still all undervolted) and it still just froze and rebooted.
The weird thing is this happens on the stock undervolt settings that the kernel comes with. I'm going to assume Imnuts' just didn't have the time to test all the apps individually for stability issues when implementing his undervolt script. I know it's an issue with the kernel(almost positive it's from the undervolting itself because i had stability issues exactly like this back on EE4 when i would undervolt) because if I reboot and flash imoseyons 4.0.0 kernel recording is fixed.
edit: I just tried removing my Voltage Control boot settings so there shouldn't be any undervolting going on(aside from the stock undervolt script thats included with the kernel) and it still just freezes and reboots. I'm guessing it's either the undervolt script or the kernel itself. Anyone else have this issue? If so how'd you fix it? Thanks in advance.

just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.

mromblad said:
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
Click to expand...
Click to collapse
How long did you let it record? and was it on 1280/720? It usually freezes on me after about 10-20 seconds

I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me

adrenaline_rush said:
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
Click to expand...
Click to collapse
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.

shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.

dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.

just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....

Mine did the same thing and I am just using the kernel and the new eclipse
Sent from my SCH-I510 using xda premium

I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.

Also getting freeze-up when trying to record HD vid.
Running Tweakstock 1.1 and PBJ 0115
edit: *UPDATE* - I just flashed Imoseyon's 4.0.0 kernel to test, and HD recording worked flawlessly. So it does seem to be the kernel which is causing the issue (in my case at least). Can anybody tell me how to pull a logcat so I can send it over to imnuts?

cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
Where did you find the kernel? Everything works great except the video.
Does anyone know of a stock, rooted version?
Sent from my SCH-I510 using xda premium

shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
I believe it's an issue with Imnuts' 1/15 kernel, not the ROM.
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
See anyone running Imos kernel doesn't have the issue so I don't believe that Eclipse is the problem, although it is still possible.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
Yeah I remember back when Gummy2.0 was released I had that issue. I know it's not the same thing though because whenever I would record it would give me an error message like "This SD card does not support HD video recording" or something like that and it would just close the camera app, it wouldnt just freeze and reboot.
shrike1978 said:
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
Click to expand...
Click to collapse
I'm positive it's not a problem with the SD card. I'm on Tweakstock so for now it's to be assumed that the kernel is the problem since cujo6801 already tested Eclipse with Imos kernel and had no problem, but adrenaline_rush tested Eclipse with Imnuts' kernel and it froze/rebooted. Pretty sure it's a kernel issue at this point.
jimc5423 said:
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Click to expand...
Click to collapse
Try your actual Camera and attempt to record video @ 1280/720, then tell me if it reboots.

I got the freeze and reboot every time with Eclipse and PBJ at 720p. Flashed Tweakstock with PBJ and it worked. Then tried Eclipse with the ep4d kernel and that worked too. I thought it might be the camera so I copied the one from from Tweakstock into Eclipse and 720p recording worked fine undervolted and oc'd to 1200.
Edit: Tried it again since reflashing updated Eclipse and it locked at 10 seconds. Guess I was lucky last time. Shot multiple 45 second plus videos ok.
Sent from my SCH-I510 using XDA App

Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium

kvswim said:
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Same config and instant, several attempts.

benb1974 said:
Same config and instant, several attempts.
Click to expand...
Click to collapse
Tweastock with PBJ freezes and reboots on mine too. Never froze on Tweakstock with included kernel

Checked the comments on Imnuts' kernel over at RootzWiki and i can confirm it's a problem with the kernel, in addition to that the HDMI port doesnt seem to work.

I have been getting froze screens and 1 reboot also, since running imnuts kernel. I thought it was maybe the ROM but doing a little research IM finding the kernel has an issue. I didn't try the camera with imnuts kernel but I've flashed imo 4.0 kernel and the recording does work w/o force closing on me.
Sent from my SCH-I510 using XDA App

Also be careful overclocking on PBJ, I set it to 1600 max on SetCPU, and after a few moments it froze and rebooted. When it rebooted, as soon as SetCPU was granted SU, there goes another freeze. I wasn't able to change the settings due to the freeze, and after a few reboots I was taken to the setup screen like you would see after a factory reset. But this came with random F/C errors and lots of non-functional apps. You can't do anything at this point but restart from stock+PIT and go up from there. Reflashing the ROM, kernel, restoring, even ODINing another ROM won't rid the F/C hell.
Same thing as this, when I tried to use the Voodoo screen tuner:
http://forum.xda-developers.com/showpost.php?p=21629058&postcount=176
Oh also people stated imyosen kernel was a battery drain, but it's been very good on battery so far.

Stable and Fast ROM?

I just got my G2x from my Optimus V and I'd like to flash a new ROM. I've already rooted it. What ROM is stable and as close to pure Android as possible? I hate all the bloatware that come on these phones from the carriers. I've been reading through all the ROMs in the Dev section but my head is spinning.

If you want super pure, your best bet is probably to stick with stock, since the G2x came with vanilla Android. Use Titanium Backup to freeze/uninstall all the bloat you want gone.
Sent from my LG-P999 using xda premium

CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2

bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
Thanks, I actually flashed 7.2 a few minutes before I read your post How do I flash the new Kernel?
EDIT: Nevermind, got Faux 050 flashed

bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.

hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
Yup, I've been reading a lot and saw some of the things you've mentioned, but thanks for the ideas.
I haven't touched basebands, should I do anything with them?
I'm on 7.2 Stable, do I need a new kernel to OC/UC? I can't seem to get it to work as nothing comes up when I'm in the CM menus.
I'm familiar with nAndroind backups as I did them religiously on my last Optimus V phone.
EDIT: Nevermind, I flashed Faux 050 now and can OC/UV now.

Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...

hairycheapo said:
Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...
Click to expand...
Click to collapse
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.

Superorb said:
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.
Click to expand...
Click to collapse
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...

hairycheapo said:
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...
Click to expand...
Click to collapse
I use GrooveIP on my other phone where it doesn't work on 3G b/c VM service is so ridiculously slow. It should work on 4G though, but I won't be able to test until the end of the month.

Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...

hairycheapo said:
Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...
Click to expand...
Click to collapse
Well, when you come from 100-140kbps 2-5mbps is screaming fast! As long as data is reliable inside buildings around town I'll be a happy camper. It's late here too, but I can't stop playing with my new phone

I spoke too soon... Battery was at 50% a minute ago and now it's stuck on 100%. Tried rebooting and wiping battery stats but no good.

hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium

FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?

FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
It's the lack of proper ext4 support.
hairycheapo said:
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?
Click to expand...
Click to collapse

[Q] BLN and Viber on Nexus S

Hello everyone!
I have a question.
I have a Nexus S with BLN turned on. It's working excellent except when i receive a message
via Viber it doesn't turn on. Actually it turns on but it turns off in a second because the screen
turns on.
So my question is: Is there a way to disable the screen turning on when i get a message on Viber so that
BLN could work?
Thanks!

lakyboss said:
Hello everyone!
I have a question.
I have a Nexus S with BLN turned on. It's working excellent except when i receive a message
via Viber it doesn't turn on. Actually it turns on but it turns off in a second because the screen
turns on.
So my question is: Is there a way to disable the screen turning on when i get a message on Viber so that
BLN could work?
Thanks!
Click to expand...
Click to collapse
U should be able to depending on what ROM ur using since it should give u control of the wake issue.
What ROM RU using?
Vs Nexus S4G using tapatalk2

vidaljs said:
U should be able to depending on what ROM ur using since it should give u control of the wake issue.
What ROM RU using?
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
I've changed numerous roms and the message always turns on the screen. It doesn't unlock it, only turns it on.

lakyboss said:
I've changed numerous roms and the message always turns on the screen. It doesn't unlock it, only turns it on.
Click to expand...
Click to collapse
Ru using NSTools?
If not change kernels and use NSTools so u can control the length of the BLN.
Some ROMs kernels are just basic, so getting a better kernel gives u more options and control.
Search ur ROMs thread to see what kernels work best with it.
Good luck
Vs Nexus S4G using tapatalk2

vidaljs said:
Ru using NSTools?
If not change kernels and use NSTools so u can control the length of the BLN.
Some ROMs kernels are just basic, so getting a better kernel gives u more options and control.
Search ur ROMs thread to see what kernels work best with it.
Good luck
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
I've used NSTools since i rooted my Nexus which was in december of 2011.
And i always use Marmite kernel which has plenty of options so...
Nonetheless, thanks for your help man!
If it won't work, it won't work. I can live without the light for Viber messages.

lakyboss said:
I've used NSTools since i rooted my Nexus which was in december of 2011.
And i always use Marmite kernel which has plenty of options so...
Nonetheless, thanks for your help man!
If it won't work, it won't work. I can live without the light for Viber messages.
Click to expand...
Click to collapse
It's a Viber issue. Viber team has stated multiple times they would fix this, yet haven't because they lack the "man power". Usually a pretty simple fix, heck, it has to be implemented for the screen to turn on rather than for it NOT to turn on, but whatever.
http://forum.xda-developers.com/showthread.php?t=2029574&page=5

BLN problem
Hi all!
I've Nexus s/CyanogenMod/Marmite 8.5 BM.
The BLN keys don't work with the marmite kernel but work with stock cyanogenmod, marmite does not support BLN or I've made an error?
thanks ......

Install NSTools from Play and activate BLN.

nexusesse said:
Hi all!
I've Nexus s/CyanogenMod/Marmite 8.5 BM.
The BLN keys don't work with the marmite kernel but work with stock cyanogenmod, marmite does not support BLN or I've made an error?
thanks ......
Click to expand...
Click to collapse
Marmite supports BLN but not blinking.. if u want the blinking leds u could use BLN CONTROL from play google.. It should works on CM 10 too..