yeahoon

@jay-zi, yes. you should replace the kext. I installed HWMonitor, using menubar to get battery & temperature information. I found default battery icon's percentage doesn't change when I discharge the battery. It was only changed when I made some event with AC adapter. We should use HWMonitor to get exact battery percentage.

When I used VoodooBattery kext, I felt refresh rate was too long. Battery Percentage decreased like 90% > 85%, not like 90% > 89% > 88%... I tried to use Rehabman's OS-X-ACPI-Battery-Driver. DSDT patch for EC(as described in the project) was not needed, but It didn't work. After DSDT Mutex patch, I could use the kext. (2013-12-05 version) Download Link: https://code.google.com/p/os-x-acpi-battery-driver/downloads/list Please use with DSDT file attached. DSDT.aml.zip

When I tried to upgrade my system from E6410 Intel Graphic to Nvidia Graphic, I think I met same problem with DLinkOZ and deano019s. I tried to boot with USB Memory Stick, but I couldn't - KP after CPU recognition. I could boot with old AppleACPIPlatform.kext file. I had a question - why my system couldn't boot without old AppleACPIPlatform.kext? Finally, I think I found the reason - It's compatibility issue between newest AppleACPIPlatform.kext and BIOS option about VT-D. (BIOS - Virtualization Support - Enable VT for Direct I/O : Uncheck) After re-installed, I found a defect about battery detection. With old AppleACPIPlatform.kext I could use AppleSmartBatteryManager.kext with perfect monitoring, but now I can only use VoodooBattery.kext - monitoring works but is not perfect.

@Jake Lo, I made issue lists like below, is there another issue? 1. [All ALPS] - Change two finger horizontal scrolling direction. 2. [ALPS v5] - Initialize device 3. [E6x30] - Release version KP 4. [E6x30] - In the scrolling with trackstick, left button click produces double-click 5. [E5x30] - Can't tap to click 6. [All ALPS?] - When detach fingers after two finger scrolling, cursor bounces. And my opinion is like below, 1. Easy 2. Need to analyze & compare linux, working source code and our source code - This issue will take more times. 3. If we want to find KP point, we need to test with 3 or 4 specialized compiled kexts. 4. Is it correct? Please reproduce the situation and share the log. 5. In my case, I didn't touch any setting in SynapticsPane. I could enable 'tap to touch' with Trackpad setting only. 6. Need to analyze & compare linux and our source code. They are almost same but there's structural differece.

First of all, congratulations! When I see the kext file, I think this kext is based on Rehabman's VoodooPS2Controller v1.7.5. And I found GitHub pages. https://github.com/AppleLife/VoodooPS2 I think this code will definitely help us. Thank you.

For E6230/E6430/E6530, I reverted one part about device initialization has some compiler warning - Please try with this. I think it will have no side-effect to E6220/E6420/E6520 because these models have same hardware id with E6410. And, let's see about scrolling behaviors. [Trackstick - Pressing middle button] 1. Trackstick Up - Scroll Down 2. Trackstick Down - Scroll Up 3. Trackstick Left - Scroll Right 4. Trackstick Right - Scroll Left - I think these behaviors are like holding some paper(with middle button) and move(with trackstick movement) to see unseen part. [Trackpad - Two finger or Side Area] 5. Two finger Up - Scroll Down 6. Two finger Down - Scroll Up 7. Two finger Left - Scroll LEFT (?) 8. Two finger Right - Scroll RIGHT (?) 9. Side Area Up - Scroll Down (?) 10. Side Area Up - Scroll Up (?) For trackpad scrolling direction, these behaviors are as-is. I didn't make any changes. So, let's talk about correct direction. If we fix the direction with discuss, I'll update. Debug_ALPS_131207.zip Release_ALPS_131207.zip

Your device is processed as ALPSv5 in the RehabmanMerge code. The implementation of ALPSv5 seems to be same with ALPSv6 from http://www.emmestech.com/linux/downloads/alps.c So I added device ID to be processed like ALPSv5. Device was initialized(or not), but you couldn't use it. In this situation, the reason may be.. 1. Implementation of ALPSv5 is not completed - Any ALPSv5 device can't be run. 2. Hardware-specific Issue - Some ALPSv5 device works, but your device can't. Anyway, I need deeper understanding of hardware to solve this. I hope we could find some way.

Here it is. (Debug & Release Build) - Some Optimizations - Just Doubled Trackstick movement speed. For 32bit build, I'll find some way from Rehabman GitHub page. Thank you. Debug_ALPS_131206.zip Release_ALPS_131206.zip

Here is version 2. Changes - Independent button click processing. Now we can use any combination (Trackstick Button + Touchpad movement / Touchpad Button + Trackstick movement) Please try this and share the result. Debug_2.zip

Please try with this and share the log. E7_730350_EC_730202.zip

Here is the fix 1. Please try. Thanks.

Here is the fix. Please test and share the log.

I get it. It seems trackstick buttons are different between E6410 and other models. E6410 takes button event like I suggested before.(left=1, right=0, middle=0...) But, I can't find this from E6420's log. I guess E6420's trackstick button are linked with trackpad button. It will be another job to change E6420. I'll see how to change it. Thanks.

I wonder why you couldn't use left/right button of trackstick. Not just trackstick scrolling. Could you use trackstick left/right button with RehabmanMerge version?

In both logs, device loading is normal but you couldn't use any trackstick button. I thought that you could use trackstick buttons with 0.zip at least.. So, this issue is not from my mod. I didn't make any changes on those two files(synapticsconfigload/Voodoops2Daemon), but I don't know what kind of version you used before. Please test with two files from 0.zip or 1.zip - (no difference between 0.zip and 1.zip) How was RehabmanMerge you used before? If trackstick buttons were normal with it, I'll track changes.