*NEW* Command Center v2.5.54.0 for M11xR1/R2, M15x, M17xR1/R2 Discussion Thread

NOTE TO ALIENWARE LEGACY OWNERS - this command center does NOT support Legacy models (if its Pre-Dell, then its a legacy model).

Looks like we have a Command Center update. This is v2.5.54.0 which is a universal update/installer for the M11xR1, M11xR2, M15x and M17xR2. For M17xR1 the release notes do not specifically state support for R1 - See bottom of this post with updated info.

Post your findings. Item #6 sounds interesting...

CC Installer Download Page @ Support

------------------------------------------------

EDIT - July 7th -

Looks like the M17xR1 has been added - M17xR1 CC Installer Download Page @ Support

IMPORTANT NOTE: For the M17xR1, according to the CC release notes, you will need to update the Synaptics Touchpad driver to v15.0.15.0 or later. This driver is not listed on the M17xR1 support page. Grab it HERE

 

Installed CC update now when you try to tap on virtual scrolling you get a giant error code you push ok in error code window and it closes cc and you are back on desktop with no ability to adjust virtual scrolling.

System.ArgumentException: Value does not fall within the expected range.
at SYNCTRLLib.SynDeviceCtrlClass.GetLongProperty(SynDeviceProperty eProperty)
at AlienLabs.TouchPad.Domain.Classes.TouchPadAPIClass.GetPropertyFlagValue(SynDeviceProperty property, SynScrollingFlags flag)
at AlienLabs.TouchPad.Domain.Classes.VirtualScrollingServiceClass.get_IsEnabledChiralMotion()
at AlienLabs.TouchPad.App.Presenters.VirtualScrollingPresenter.refresh()
at AlienLabs.TouchPad.App.Views.Classes.ViewFactoryClass.newVirtualScrollingControl()
at AlienLabs.TouchPad.App.Views.Classes.ViewFactoryClass.newView(ViewType type)
at AlienLabs.TouchPad.App.Views.Classes.ViewRepositoryClass.getByType(ViewType type)
at AlienLabs.TouchPad.App.Presenters.TouchPadPresenter.activate(ViewType type)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at AlienLabs.TouchPad.App.Helpers.EventTriggerClass.fire(ViewType value)
at AlienLabs.TouchPad.App.Presenters.NavigationPresenter.changeViewLinkSelected()
at AlienLabs.TouchPad.App.Views.Xaml.NavigationControl.ViewLink_Checked(Object sender, RoutedEventArgs e)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.RadioButton.OnChecked(RoutedEventArgs e)
at System.Windows.Controls.Primitives.ToggleButton.OnIsCheckedChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, OperationType operationType, Boolean isInternal)
at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
at System.Windows.Controls.Primitives.ToggleButton.set_IsChecked(Nullable`1 value)
at System.Windows.Controls.RadioButton.OnToggle()
at System.Windows.Controls.Primitives.ToggleButton.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

 

Checked on M11x and no error message. Are you using the v14.0.12.0 Synaptics driver for the 17xR2?

If not, try uninstalling the current Synaptics driver, reboot and then install v14.0.12.0. If this still does not correct the issue, suggest you uninstall Command Center, reboot into Safe Mode, run CCleaner's Registry Scan, reboot and re-install CC. Perhaps something went funky with your install.

Any other 17xR2 owners seeing this issue?

 

Yes, I can confirm the same error. I am using v14.0.12.0.

 

Had this issue once. I solved it by uninstalling CC and synaptics. Then reinstalling synaptics and then CC. Hope it helps.

 

I have the v14.0.12.0 and I did all as you said and it is the same.

 

You have to uninstall both cc and synaptics and then reinstall. Was that what you did?

 

I have the v14.0.12.0 and I did all as you said and it is the same. My unit is unchanged from factory delivery you would expect a simple update to work with out making things worse. Now what

 

Try what fractal suggested - nice tip fractal.

 

So, any feedback on the new CC ?
I am usually quite reluctant to install new CC versions as Dell seems to screw them up quite consistently so i prefer to let others be their lab rats

 

The first time I only reinstalled CC it didn't work. The second time I uninstalled TP driver uninstalled CC booted to safe mode used cleaner same as first time booted reinstalled TP driver than CC again no help still the same error code. When I downloaded new driver again there was an install X64 and X86 whats the difference. And any other ideas like how to go back to old CC that worked.

 

got an error message so i uninstalled and reinstalled and it seems to be ok now

 

x64 is a windows 64 bit driver while x86 is for 32 bit windows.
Do you know which one is installed ?
If not :
Press Windows Logo key + Pause/Break Key and in a window that will open look for system type, it will either be 64 bit or 32 bit.
I doubt that it would let you install the wrong type though...

 

The first time I only reinstalled CC it didn't work. The second time I uninstalled TP driver uninstalled CC booted to safe mode used cleaner same as first time booted reinstalled TP driver than CC again no help still the same error code. When I downloaded new driver again there was an install X64 and X86 whats the difference. And any other ideas like how to go back to old CC that worked.

 

@fastlane1
we completely understood you the first time you posted, no need to repost.

 

Yep, I find it hard to believe no 15x or 17xR2 owners have not updated. I am very tempted to give it a go with R1 however given the history I think I will wait for 17xR1. 11xR1 has no issues.

 

so, i updated just now.. installed over the old one just fine.
Rebooted and looks like it's working fine for now (even accepted my old theme).
The only hiccup i saw is that my H key stopped working, i restarted and it came back to normal..

 

I installed the new version on my M15x and am not having any problems to speak of ..... I was on a fresh install of Windows though so i cant speak for people upgrading etc....

 

Did you try virtual scrolling in CC I still get error message after trying reinstall of both CC and TP driver. Virtual scrolling seems to be the only fault I get. Any ideas from anyone will be appreciated.

 

yep, virtual scrolling does not work for me either. but my touchpad is disabled anyway so i don't care.

 

Thanks at least I know it is not a problem of mine but something with the update and hopefully some day it will get corrected. All I use is the touch pad the laptop is always on my lap, don't really see a way of using a mouse unless I got a wireless mini mouse and used it on the side of the face next to the touch pad has anyone every tried that, it could maybe help the other problem o the TP being JUNK

 

just updated on my m15x, also got the virtual scrolling error...

 

fractal, can you try uninstalling the touchpad driver, reboot and then re-install the touchpad driver? See if that does the job - if not, we know 17x touchpad has an issue with this version of CC.

Thanks!

 

I did that about 3 different ways and times including putting in the windows driver and replacing over that and replacing from the device driver and the uninstall in control panel with every combination of reinstall with CC

 

Everything works like a charm over here

 

Did you try clicking on virtual scrolling in CC on Alien touch

 

Product: Command Center -- Error 1935.An error occurred during the installation of assembly component {6D321E57-3E99-3B87-BF23-2CDFF3361CB4}. HRESULT: 0x80070002. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC90.CRT,version="9.0.30729.1",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"

i get this on m11 r1

 

Yeah...? What about it?

 

Sure, I guess I should follow my own advice
will try it and report back..

 

That is were the error comes in. Their is a lot of areas to CC that work OK but that is the problem the virtual scrolling I am sure plenty of people install CC look it over and think it works fine when parts of it don't

 

I installed the Synaptics Scrybe software today(drv ver. 15.0.9) and now virtual scrolling works in CC.
Also see they have a new generic driver 14.0.3:
Drivers | Synaptics
I did not try the driver by itself.

 

On My M11x R1 all was *almost* correct, only face login was corrupted. In low light condition it didn't light up white screen, so in the dark it can't recognize face anymore.
I returned to previous CC (A06, 2.5.48) and I'm fine.

 

Oh yeah, that makes sense why mine works now.

I have Scrybe as well

 

yup, after installing synaptics scrybe, all back to normal now..

tq

 

Problem here is, it should not generate an error (without scrybe). Good posting guys - nice info on errors. Hopefully the AW folks will take a look at this.

 

I have the same issue. Facebright no longer seems to work. Rolling back.

 

Yes, I'm not able to use FaceBright anymore, Is there a way to start it again without rolling back, asking just in case I miss something

 

hmmm why when i try to install it on the m11x does it say to insert the last disk of something?

 

sorry posted wrong thread

 

I have this same problem man, I would just go with the traditional password. Though I don't use one since I don't lend anyone my M15x, it's too valuable I just disabled mine because it became a useless luxury

 

I,m not sure of what you are talking about but anyway you need to have a password set in order for face reconition to work so the user is forced to ethier enter the password of be reconised by aliensens

 

This is essentially correct. Without a password, your account has no security at all - with or without AlienSense. Further, if you only have 1 account created and it is not password protected, then Vista and Win7 both will simply auto-logon to that account when the machine is booted. This does not give AlienSense a chance to run.

I would recommend simply password protecting your account. This will both dramatically improve your overall account security as well as allow you to use all of the convenience and security features of AlienSense.

 

Ill try this one;
AlienSence is a supplemental entry to the Windows password, thus when Aliensence works it sends your windows password and logs you in.
AlienSence can be enabled in various strengths, including disabled, through Command Center/ AlienSence/ Advanced Feature (top right corner). You can delete 'Your Biometric' (face biometric) and restart the recognition phase (there).
As for the AutoBright, it is on the bottom center of the facial recognition screen. -- Place a sticky note over your cam and the 'lack of rocognition of a face wil give you more time' to see the Drop Down Box. -- Try these. I just deleted my biometric and the second login found my face instantly. watching.. -h-

 

Works for me so far. Nothing to report..

 

They are finishing up testing on the R1, but the plan is to release soon.

 

There will actually be a new version of the Touchpad driver released later today (hopefully) that resolves the main problem everyone is seeing. I missed a driver sign-off on Friday as I was off watching the USA game, so I apologize as it was expected to web-post at the same time as the new AWCC. Let me know if you have any problems after installing the new touchpad driver.

Will continue to look into the other items...

 

Thanks for the update Brian....

 

Brian, i volunteer to beta test that new touchpad driver

 

i would really like to be beta testing that driver

EDIT: its available now

 

Thanks, here is the link for those wanting it, shows compatibility with M15x and M17xR2:
Drivers and Downloads