Manual enhanced and UBR FTC database opened

Hello my dear friends,

Since there are a lot of talk about UBR and FeatureTestControl value lately, brightness and screen issues, plus thanks to MikeP’s proposal, i’ve decided to update manual.

And now, new menu – UnifL Brightness Resolver is available for your pleasure, where step by step is described how to find proper/right FTC value.

I strongly advice you to read it as it will help you to understand what for is FeatureTestControl and how important it is, especially if you have issues with your laptop like Brightness/Black screen or inability to switch between cards.

Moreover, you can now submit your FTC findings to the Public (somewhat) database so other users that lost hope or nerve will be lucky to find their answer.

yeah the DB is the most crucial thing here…we need people to post in here as soon as they can….and yeah you are right this should have been done before..but still its better late than never…after all u already had so much on ur plate….

So in short 60Hz screens work. (Maybe not brightness control on AMD but I do not know since I don’t have a 60Hz screen and cannot experiment – Win 7 + Win 8) but they boot on AMD + Intel (with brightness controls).

120Hz will work from 13.8 onwards… half way. We have found the code that is responsible for the screen going black on the internal monitor.

The next issue seems to be a black screen on bootup for which there is a hotfix for now allowing it to boot on AMD (no brightness control) + Intel (brightness control).

The biggest issue seems to be FTC and it seems a bit more complex for 6850m.

Hmm, I failed to mention that my laptop is the HP Envy 17 2100-CTO, which has the Intel HD Graphics 3000 and an AMD Radeon HD 6850M. It was an issue earlier, there was some discussion on it over in the comments for 13.4 but nobody seemed to be able to figure it out. The problem was that the backlight would not turn on in the built-in display – at any brightness setting – but the driver seemed to work great when using an external display on HDMI. There may have been some switching issues… but what made the driver unusable was the lack of a built-in display.

It was like the 6850M was special (“more complex”, as you said), as we wished we could have a lack of brightness control or problems with power-saving modes that could just be fixed with a reboot. Is the 6850M still an issue? I’d rather not go through the whole process of drive images and cleaning and installing if someone just knows for sure that it doesn’t work.

Hmm sorry I assumed you were Gregory Janik who has a 120Hz screen I believe. Fascinating that the current drivers do not work for you.

They work for some people on the notebookreview forums with 60Hz screens. During setup the screen turns black but after a restart it should work fine.

Either way. Hopefully the 13.8 will work for you (Without brightness controls for AMD but working screen) but with brightness controls for Intel. And no more black screen. (there might still be a black screen during installation but that is a minimal issue right now).

Stick around please and report back when it comes out. Maybe with more 6850m testers it will make it easier to find an FTC for AMD.

I have a doppleganger lurking here? Nice. I always see others when Googling my name, maybe I can finally meet one!

But back on topic… I’m super excited you have 6850M working! (The last one I tested was 13.5, I beleive. I’m on 13.4 with the AMD driver forcibly uninstalled so I just hobble along on the Intel card. I boot into Win7 for gaming.) I don’t even care about brightness controls, I can deal with it. I will definitely report back.

I do remember reading the notebookreview forums a couple months ago, but I only saw one person that could get it working, and nobody else was able to reproduce it. It may have even been on Win7 instead of Win8. I hope I just missed some more recent info.

Lol, this is my. But Leshcats notes saying:;; ;; no backlight and brightness on 840. 000 - brightness works but no backlight. 940 - next candidate for trials.
Fail. No money no honey:)
FTC 940 is working, but so bad.

Acer Aspire 4820TG (intel gen 1 + HD 5470)
1) More than one line of the .ini file is associated with DEV_0046&SUBSYS_03591025 (my Intel card hardware ID), I continued using the first one
2) No PwrCons_SNB_AddSwSettings is present. I continued using the most similar key in my file: PwrCons_ILK_AddSwSettings
3)The values are[PwrCons_ILK_AddSwSettings]
HKR,, FeatureTestControl,%REG_DWORD%, 0xF800 ; Enable FBC, GSV, RC6, DPS, DPST5, Vista Backlight Control, GPMT, Turbo

In a previous attempt, I already saw that my official driver set the value to 0xF800, but even after I used the brightness resolver setting the value as it should be, the screen was black when resuming from sleep. Changing to intel fixed the issue, but if i switched to AMD again the display would go dark again.

These are the values I saved when trying to find the right brightness values installing the official diversAfter Intel only driver (auto update from windows)
CurControlSet AMD (0000) : 0xf800
ControlSet001 AMD (0000) : 0xf800
ControlSet002 AMD (0000) : 0xf800

hi all
when returning from sleep mode the screen is too dark and you can not change the brightness, the brightness works properly before stopping. FTC had the F940, that value catalyt work properly in 13.4, then formated my laptop (hp pavilion g4-2082la, intel hd 3000 – radeon 7670M), installed the catalyst 13.4, brightness working properly but when returning from sleep mode the screen was too dark and you could not raise the brightness, the FTC at that moment was F940 (the same value as before formatting work properly), then I changed that value by the OEM factory coming F840, but still with the same problem.
Someone can help me, can be a registry key that is wrong, I do not know.
my specifications:
intel: VEN_8086&DEV_0126&SUBSYS_183C103C
amd: VEN_1002&DEV_6840&SUBSYS_183C103C

hi Mike
thanks for reply, I have tried every value that is available: F940 F920 F840 F900 F800 F908 F000 F842 F942 FFFF, those are the ones I remember, but the point is that before always worked withthe F940, now will not work with that value, the OEM value is F840 and it does not work, format my laptop with the recovery and after that do not work FTC values ​​v2 13.4 drivers, 13.5 beta2, I have always installed these. The point is that I have total control of brightness, but in the wake of the suspension is very dark screen.
the problem is fixed when I install hp driver “C:SWSetupDriversAMDVideoHHP” but if I install the driver unifl waking from sleep mode the screen is dark for more than change the FTC.
any suggestions? I need your help

unsigned drivers tried 13.1v2.1 and 13.3beta3 and with them the FTC works with both F940 (amd and intel) and F840 (amd and intel), but if I try again, drivers are already signed 13.4v2 and 13.5beta2 do not work with those values ​​when returning from sleep mode.
is there any solution? since the 13.4 driver is the most stable for me

hello Mike
I just installed the driver hp from the factory and then installed the catalyst 13.4v2 13.5beta2 and the problem persisted (not install the 13.6beta2 as performance greatly reduced), so I installed driver again installed the hp and above 13.1v2.1 catalyst signed, and that works both the value and the factory F940 F840 fully.
To me that some registry key is not as it should, as before formatting any controller unifl worked smoothly. I made copies of the record of each driver with “brightness solve” if you can examine you leave the link:http://sdrv.ms/16AQzJ8
bye

Brightness control and wake up from standby on the AMD card only works on the Intel drivers. With leshcats help we have tried very very hard to find out on what is in charge of this. We found that the kernel itself is responsible (no registry settings helped besides FTC).

I will look at your files again but it is most likely a kernel issue meaning that your old FTC will no longer work on the new drivers. It is more likely that the FTC for the drivers has now changed to something unknown. (theory)

interesting, well, I think I’ll use 13.1v2.1 drivers for a while, but is only a detail, before reinstalling windows7 from the “partition recovery” any driver unifl work properly with “FTC F940 and F840”. Although there was one occasion that HP installed a driver from the web and had the same problem (did not work with the F840), at that time I knew nothing of the matter and then the 13.1v2.1 leshcat drivers solved that problem, thereafter any subsequent driver working with “FTC F840”. It is a complicated problem, I think.
one more thing, use the dynamic mode, as my pc does not have switchable graphics fixed mode, in this mode then you need to apply independent FTC values ​​for amd and intel?. I ask because in dynamic mode the default is the intel card and that card would be to control the brightness.

Just added 2 values to the database for the first generation HP ENVY 14 series (1xxx)
The original driver from HP used F840 in Windows 7. I haven’t been able to test this value with the UniFL drivers, but in Windows 8 that value doesn’t fix anything. Best value (so far) has been F940.
Hoping that another ENVY 14 user has found a better value to fix the no brightness control when working with the AMD card :p

Is there a standalone file for the UBR program? I dunt intend to download any beta drivers, my internet connection is too slow 🙂 if not, Ill wait for next WHQL Unifl version. its just there is the latest update for the UBR thingy, thanks.

I have an Acer 3820TG and use the unifl 13.8 driver. Switching works. Intel card works perfect. The problem is:

My original values for my HD 5650 Radeon Mobility were different for ControlSet001 (f800) and ControlSet002 (f3)

How can I set them back to these values, imho at present I can only change them both at the same time (brightness control is not working with f800 or f3 for both of them at the same time). By switching to the Radeon Card I have a black screen.

I try with F840 (the original OEM FeatureTestControl Value) but i can’t change brightness and when it weak up the screen is black.. So i try other number F842 and F940 But nothing working, in F940 the screen is always black, i’ve got an hp dv6-3109sl What can i do?

Hi, i just tried to use the brightness resolver after installing a Beta driver from AMD – because of the brightness control not working anywhere (buttons or power management) on the AMD card. I can chaneg it on intel. Anyway i followed the instructions and found the intel value – but how are you supposed to find the AMD value?

I searched for “ati2mtag_ManhattanP_PXAI” and couldnt find anything like “PweCons_SNB_ADDSwSettings”. Both AMD and Intel have the same value (F840) in the resolver thing..

I could try doing a system restore to before i updated to find the right value but unless i know what im looking for that wouldnt work.

I did a system restore to before i updated the HP graphic drivers and ran the Leshcat installer to test what values the resolver thing shows and both intel and AMD were f840. Thats the same as after installing the new Beta driver from AMD. But i still cant change the brightness when the AMD is running >..< I blame HP lol..

I am not having success anymore with brightness resolver, I’ve tried a few values, even the one I’ve found following the procedure but none of them are working, when computer hibernates or restart I have low brightness again, only in INTEL card. If I switch to AMD and then back to intel it does works and I have full brightness. But as soons as it hibernates I’ve problems again! System is Sony Vaio VPSA290X with AMD 6630 + intel 3000.

Bouncy castles utilised to become an item for young kids to appreciate in a carnival or fete, or
probably a birthday celebration or unique celebration – hired for that day or
compensated for for each and every session. Bouncy castles arrive in a
very huge selection or sizes. Children will likely be dare devils and desire
to jump of things so you need to educate them.

He also carries a handgun that they’ll use in case you fall back too far.
Okay, I know one other ones may be super difficult, but this one will be easily for the
change. The graphics of the game are very similar to that relating to Dead
Rising 2.