[Q] cm9 buttons dont illuminate - Verizon Droid Incredible 2

I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9

You have to use auto brightness.

cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply

pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium

cm9 illumination
Thank you....I appreciate it

Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.

atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.

Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable

pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.

RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?

Related

[Q] CM7 Light sensor issues

Hello,
I recently bought an Incredible for my girlfriend on craigslist. It was only 2 months old (in great condition to boot). Either way after flashing CM7.0 I noticed that the automatic backlight setting did not work. I just set it to around 25% and figured I would figure it out later. After 7.0.2.1 came out I flashed that and no change. I then decided to figure it out. It seems that after waking the sensor doesn't work unless really flooded with direct bright light (such as the flash light from my incredible). After that it works mostly as intended.
Here is how I tested it. I lock the phone when in the custom light levels screen. When unlocking the Sensor (filtered / raw) is at 10/10 and will not change no matter what I do until I hit it directly with a bright light. I believe that it will also change eventually letting it just sit. Most of my tests involved using bright light sources. After that the sensor works just fine and changes almost instantly when I cover it with my hand and then move it into regular room light. Is this a known issue? I checked the bug tracker briefly but did not see anything. I have had two others test. One had fine light sensor response the other had the same issue as me.
Anyone have any idea?
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
k_nivesout said:
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It does work but the sensor doesn't respond in a timely fashion.
Have you tried changing the sample interval?
Sent from my ADR6300 using XDA App
What settings are you using? I.E. do you have filtering enabled? What is your window length? Sample interval? Etc.
I've never seen anyone discuss this as a CM7 bug. Based on the way you are describing it, it sounds like you might just need to tweak your settings.
For example, if your window length is very long and sample interval slow, that might be why your readings are taking so long to update. As for why the reading changes as soon as you hit it with a bright light, you could be tripping the reset threshold.
Just in case you haven't checked it out already:
Numerical explanation of the CM7 automatic backlight settings
I will check when she gets off work. All I did was flash cm7. I didn't mess with light sensor settings.
Ok... I have checked it... Not good. Sample intervals were set to 1s. Even still they were not enabled. Messing with the settings didn't yield any results either. It was still sluggish until hitting it with bright light...
I would search, there are multiple threads around where people have posted their settings, I would try those then tweak it to your liking. Also check out byrong's thread, the man knows his stuff.
Sent from my ADR6300 using XDA App
The automatic brightness sucks on stock as well. Just turn it off. You can't see the screen in bright sunlight no matter what the setting is, and you can see it just fine at 64/255 inside. All the automatic brightness does is give you a headache.

Softkey backlight?

I love the DINC2 so far, but one thing that I wish I could change is the softkey brightness.
Are they supposed to be always on? Even with the clock in night mode?
I tried LED hacks and a few other brightness control apps, but no luck so far.
Does anyone know of an app that can dim/turn off the softkey backlight?
siskiou said:
I love the DINC2 so far, but one thing that I wish I could change is the softkey brightness.
Are they supposed to be always on? Even with the clock in night mode?
I tried LED hacks and a few other brightness control apps, but no luck so far.
Does anyone know of an app that can dim/turn off the softkey backlight?
Click to expand...
Click to collapse
LOL just flash virtuous 2.35 softkeys don't work, but everything else does. No softkeys lighting up is not all that bad.
Sent from my ADR6350 using XDA App
That's an idea! *g*
If I get desperate and there are no other solutions, I might try it.
Does global mode work with virtuous?
Nope
Sent from my rooted GB ADR6350
Well, so much for that!
Thanks for letting me know.
what rom are you running? stock? on cyanogen mod the softkeys go out on night mode in the clock app.
Right now I'm running the debloated stock, but am thinking of skyraider zeus.
Had it on there yesterday, but then lost mobile service after unlocking the SIM, and decided to try the stock rom. Service came back, and now I'm chicken to try flashing again.
Does global mode work with cyanogen? I will use this phone in Europe later this year and want a stable rom with working global.
siskiou said:
Right now I'm running the debloated stock, but am thinking of skyraider zeus.
Had it on there yesterday, but then lost mobile service after unlocking the SIM, and decided to try the stock rom. Service came back, and now I'm chicken to try flashing again.
Does global mode work with cyanogen? I will use this phone in Europe later this year and want a stable rom with working global.
Click to expand...
Click to collapse
According to post #18 SkyRaider Zeus does work in global mode. I haven't tested it, but I have been running SkyRaider Zeus for about a week now and I love it.
Yep, that's part of the reason I want to use it, but I'd like it even better if it had softkey backlight control, too. I guess I will have to risk flashing and seeing what happens with the softkeys.
When I ran it yesterday, it was bright daylight, and I only noticed how annoying the backlit keys were later that night, when the phone was running debloated stock.
There's no risk flashing most stable roms from the dev section. Make sure you have a working backup of your current rom and you're good to flash new ones. I had an issue trying to mess with global mode on my phone once and it required me to do a restore of a working backup I had then all was fine again.
Also in the cm7 thread this post confirmed working global mode recently. http://forum.xda-developers.com/showthread.php?p=17245922
Sent from my Incredible 2 using Tapatalk
Thanks for the info!
When I ran into the no service problem after unlocking the Sim, I restored via cwm, but nothing
worked. Got an endless 'loading, this can take several minutes. Please wait.
This was the backup of the stock ROM, though.
Sent from my ADR6350 using XDA App
if you had issues restoring a backup in clockwork then it wouldnt have been because you unlocked the sim card. sounds like you had a corrupt backup or something went wrong with the backup you were trying to restore. but out of curiosity, how long did you let it try to restore before you gave up?
The restore went through successfully, according to CWM, but when the phone restarted, I was stuck with: Loading! It can take several minutes. Please wait.
I waited for an hour, and then flashed the debloated ROM.
What happened after the SIM unlock (I was running Skyraider Zeus at the time), was that I lost my mobile service.
I am sorry to hear you are having problems. I hope you didn't lose any data. I run cm7 nightlies. I have heard that cm7 supports global mode. I also use an app called "Screen Filter". When I was unrooted/stock, the app would not turn off my softkey backlight (there is an option to enable or disable softkey backlight), but on cm7, the feature works. I have two widgets, one set at 46.8% without softkey backlight, and one set at 97.8%, also without softkey backlight. The second one barely dims the screen, and turns the softkey backlight off. And best of all, with cm7 I am able to assign one of them to long press search key, so I can turn off the softkey lights from anywhere. I have not tested it, but there is a chance this could work on a rooted sense rom (the screen filter setting). I know it works on cm7 though.
Also, with cm7 you can control the brightness of the softkeys (if you only want to dim them) if you customize the auto-brightness (the setting is built into the rom), but then you have to use auto-brightness (I do that as well).
Hope that helped!
DalekCaan said:
I have heard that cm7 supports global mode. I also use an app called "Screen Filter". When I was unrooted/stock, the app would not turn off my softkey backlight (there is an option to enable or disable softkey backlight), but on cm7, the feature works.
Click to expand...
Click to collapse
Thank you!
You don't know how happy it makes me to hear that cm7 does global and screen filter works with the softkey backlight!
I'm a big fan of Screen Filter, anyhow.
Can you tell me where I can find the latest stable version of cm7 to try out? Or do I need to grab a nightly?
Any ideas on battery use, and signal strength with cm7? I have pretty horrible signal strength with the debloated stock rom, though it was no better with the unrooted stock.
siskiou said:
Thank you!
You don't know how happy it makes me to hear that cm7 does global and screen filter works with the softkey backlight!
I'm a big fan of Screen Filter, anyhow.
Can you tell me where I can find the latest stable version of cm7 to try out? Or do I need to grab a nightly?
Any ideas on battery use, and signal strength with cm7? I have pretty horrible signal strength with the debloated stock rom, though it was no better with the unrooted stock.
Click to expand...
Click to collapse
There is no stable version yet, but here is the link for the nightlies:
http://forum.xda-developers.com/showthread.php?t=1156343
I find them stable enough for daily use. I have used WiFi, GPS, Bluetooth, 3G, Tethering, SMS and MMS with Handcent, etc. and have never had any problems (other than the compass issue with AOSP, which I really don't mind, as it's fine when I'm moving).
There is also a beta:
http://forum.xda-developers.com/showthread.php?t=1153261
if you don't want to deal with nightlies. I haven't used it, but I have heard it's good enough for daily use.
I do have pretty bad signal strength with this rom, however I have always had bad signal strength and have never dropped a call/had to resend a message. At best I can get around -80 dbm, but usually I'm around -90.
My battery use has been okay. Not 72 hours like some people report (I don't see how that's possible with any rom), but with ~2 hours of screen on time, I'm usually just below 50% at the end of the day. So I charge every night, but I never worry about making it through a day. I use the Tiamat kernel because without it the speaker on calls is too low for me, but another benefit is that Tiamat includes the smartass governor, which is supposed to help battery life.
Thanks again!
I'll check out cm7.
Yes! It works!
I have the latest nightly and screen filter controls the backlight!
Thanks a million, and also for mentioning the long press option.
Now I use that for turning off the soft keys when reading. Much nicer than having to go back to the home screen.

Is backlight of touch input dynamic?

Hey all,
I experienced something a few mintues ago. I installed a new rom, Blissdroid. I 'discovered' that the backlight of the touch input (under the screen) was reacting dynamicly to sunlight. It went off in full sun. I couldn't find a setting to let it lighten up all the time.
I went back to Virtuous Unity, 2.35. It seems like the same thing is happening. I don't know if it's just normal (and I never discovered it before) or is there a setting I have to change (because I can't find one)?
Someone who can help me?
Thanks!
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
dstylazz said:
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
Click to expand...
Click to collapse
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Nahsen said:
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Click to expand...
Click to collapse
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
trh1341 said:
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Oh, so it is just a normal feature of DHD? Weird that I just discovered that yesterday
rcmix 4.0 and roms that use rctweaks have settings for this. alternatively you can set it to your exact preference if you edit framework-res according to this:
http://forum.xda-developers.com/showthread.php?t=1034743&highlight=systemui+apk
the link is manly aimed at tweaking your autobrightness, but it has info on butons too
Thank you. I only feared a problem, caused by changing ROM, as I never saw that before. I Thought those inputs were always lighten up, in every dark/bright situation.
depends on rom authors preference i suppose
if you are using sense 3.5 runnymede port, you can also flash tweaks as addon. some very nice features in there
Thank you all. I'm not great in flashing ROMs, certainly nog all those tweaks. I tried Virtuous Affinity and Blissdroid, but in both I heard a pop sound after playing music, sound, ringtone,... It seemed like I was not alone.
So I went back to Virtuous Unity 2.35, which doesn't give me any problem, except for a random bootloop from time to time (for example after playing Angry birds and once just after sending a message) what I can fix by replacing the battery. This happens 1 time in 3 months or so.
I just don't want to brick my phone, so I don't experiment much. Maybe one day, when I've got a new phone, I can use my DHD to experiment more.

Cant adjust the screen brightness....

Just now replaced my ribbon cable as i faced some problem with my old one.
But after replacing it i was not able to adjust the screen brightness, by adjusting the screen brightness only my softkey light brightness is adjusted not my screen brightness.
So whats the solution for my problem? really confused
some one help me on this please!!! My battery drains cause of this full brightness
ramprabhu19 said:
Just now replaced my ribbon cable as i faced some problem with my old one.
But after replacing it i was not able to adjust the screen brightness, by adjusting the screen brightness only my softkey light brightness is adjusted not my screen brightness.
So whats the solution for my problem? really confused
Click to expand...
Click to collapse
Are you sure it's a hardware issue (OK sound stupid but it's easiest to check if it's a software issue)? Try a couple of different ROMs, from the latest CM10.1 test builds all the way to rock hard stable CM7 and stock ROMs. It's interesting that soft key light is being changed though; did you mix up some wires or something? Also, not to insult your intelligence but you have turned off autobrightness, haven't you?
HTCDreamOn said:
Are you sure it's a hardware issue (OK sound stupid but it's easiest to check if it's a software issue)? Try a couple of different ROMs, from the latest CM10.1 test builds all the way to rock hard stable CM7 and stock ROMs. It's interesting that soft key light is being changed though; did you mix up some wires or something? Also, not to insult your intelligence but you have turned off autobrightness, haven't you?
Click to expand...
Click to collapse
Sorry i forgot to mention those things... i already tried many roms, still the problem persist. and i dont think that i mixed up the wires cause it doesnt have much wire connections in the ribbon cable and they are just plug in type so we cant make wrong in the connections.
Even tried external apps to control the brightness... still the soft key ligh is adjusted not the screen brightness
http://forum.xda-developers.com/showthread.php?t=2268259
demkantor said:
http://forum.xda-developers.com/showthread.php?t=2268259
Click to expand...
Click to collapse
in that thread you mentioned about increasing the brightness... what about the lowering the level?
i tried those codes...but nothing happened
I'm doubting it is software then, you have tried different ROMs and manually changing brightness so I will assume you need to replace your LCD. Being I have never seen this issue before this is just my best guess and what makes sense to me. It is doubtful that the flex is causing this issue and the screen itself is to blame
Sent from my Nexus 7 using xda premium
demkantor said:
I'm doubting it is software then, you have tried different ROMs and manually changing brightness so I will assume you need to replace your LCD. Being I have never seen this issue before this is just my best guess and what makes sense to me. It is doubtful that the flex is causing this issue and the screen itself is to blame
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i dont think that the lcd is defective...i think my new ribbon cable is not supporting this,...but i dont know how and why?? (might be its because made in china?)
can i change the brightness level thru build. prop editor?
its very possible but it really doesnt make sense how the cable wont support it, do you have your old to test against?
and i doubt build.prop will change a thing as we have already attempted manually changing it and it appears to be hardware
demkantor said:
its very possible but it really doesnt make sense how the cable wont support it, do you have your old to test against?
and i doubt build.prop will change a thing as we have already attempted manually changing it and it appears to be hardware
Click to expand...
Click to collapse
yes am having the old one, but its fault is about the display..so cant use that any more... i tried to figure out the brightness option in build prop, but i cant find that option...can u help me on this?
truthfully i dont know of anything in build.prop that would be changed to change brightness level, ill dig around in a bit but nothing off the top of my head.
but again if using adb to change brightness or any other manual method wont change then there is a hardware fault somewhere as this happens across all roms.
i guess i never asked, is the screen the same brightness in recovery and bootloader?
if so you will need either a new lcd or flex cable
but in general even if we use low brightness in phone, while getting into recovery or bootmenu it will be in normal brightnes..i think so,....so i dont find any difference in brightness level at recovery page..but do we have options to change brightness level in recovery mode?
That would be coded into your recovery and bootloader respectively, I couldn't say how esay that would be to change, probably near impossible in hboot and still hard in recovery. Don't know the brigtness value in them but I assume high
I guess there is an off chance a sensor is malfunctioning, download z device test from market and test them, but this shouldn't be a symptom of a bad sensor.
Really you need to find out what hardware to change
Sent from my RubiX NonSense using xda app-developers app

Problems with screen brightness, LED notifications, Xprivacy / slowness

So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
fivemill said:
So I seem to have a whole bunch of problems with my D851, and am curious if others have the same problems and know of fixes. Mine has 20g (stock Lollipop) installed, and is rooted.
Main problem: enabling Xprivacy makes this phone become significantly slower. The settings menu crawls with Xprivacy turned on. Anyone else experience this?
Auto brightness is *way* too dim to use. Surely, I must not be the only person experiencing this? I see a few people mention it in passing, but it doesn't seem to be an big deal. Are people not using auto brightness? Or do most folks not have this issue? All other devices I have with Lollipop allow a brightness range if set on auto. This one doesn't ? Can I get this feature somehow?
Even when I set the brightness manually, it keeps getting reset to 100% some half the times it wakes up from sleep. Anyone else experiencing this? Anyone know of a fix?
Also, the display off time never gets set. I set it to 30sec or 1min, and it always gets reset two 2 min.
The notification LED is virtually useless. It blinks once in like 20 seconds when I get an email (gmail app). I rely on this. Is there a fix to get it to blink every second or 2 seconds? Light manager didn't work.
What I don't understand is, since I experienced all these issue on pretty much a phone out of the box + rooted, I'm surprised they don't seem to be common problems.
Thanks in advance.
Click to expand...
Click to collapse
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Still_living714 said:
I think maybe you got a dud. Try flashing a rom and see if problems stop,if they don't then get another phone through warranty
Click to expand...
Click to collapse
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
fivemill said:
Thanks, I think that was a part of it, but not all of it. I tried flashing stock on a different unit, and I found that the brightness issue was largely (but not fully) better, and the display settings not getting set issue went away. The Xprivacy and LED notification issues remain, and will occur on all units as far as I can tell. I haven't seen anything here that contradicts that info.
Click to expand...
Click to collapse
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Still_living714 said:
I have xprivacy and my phone is still very smooth plus my LED works just fine. I even changed the colors
Click to expand...
Click to collapse
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
fivemill said:
Thanks a bunch for the info, this is good to know, and good to hear from another D851 user. The Xprivacy issue may be less easy to measure. The LED issue may be more objective. I have no trouble with changing LED colors. It's the blink rate that's at issue. Are you able to get it to blink say, twice per second, or even once per second when you get new email in your gmail app if you use that? Are you using any kind of an LED app?
Also, are you running Lollipop? Stock? Rooted? Thanks.
Click to expand...
Click to collapse
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Still_living714 said:
I'm always rooted lol I'm running fulmics 5.0 and in the settings it gives you the option of length and speed of the LED. I highly recommend that rom if you want to try out marshmallow.
Click to expand...
Click to collapse
Very good to know again, thanks for the recommendation! And the LED options are an additional reason. I'll try out fulmics soon.

Categories

Resources