shellbt

• 위치 : frameworks/base/services/jni
• 파일 : com_android_server_BatteryService.cpp
• 에러메세지 :

  1. E/BatteryService( 1866): Could not open '/junk_battery/class/power_supply/battery/status'

  2. W/BatteryService( 1866): Unknown battery health[2] '100'

• 패치 내용 :

LINUX 2.6.24 AND VMWARE

Ubuntu 8.04 was recently released and continues its tradition of adding some real polish to Linux. I’ve been consistently impressed with their goals and progress - everything from improvements to Gnome and included applications to making Xorg “bulletproof” and seamless transition from Windows.

VMware Tools, whereart thou?

Unfortunately, Linux 2.6.24 (which ships with Ubuntu 8.04 and will be shipping with all other Linux distros shortly) moved some headers and symbols around, and breaks VMware Tools. VMware has not been at all forthcoming regarding updates to fix this, but fortunately their “open” offshoot works well - there’s just no simple way to install the open tools. So we’re stuck with:

1. •No tools, which works decently. Many glitches seen in the betas have been resolved, and networking, video, etc all work fine out of the box, but things like shared folders and clipboard sync are out.
   

2. •Official tools that don’t compile, but could be installed trivially.
   

3. •Open tools that compile, but cannot be easily installed.
   

From the forums, I get the sense that this is not at all unusual on Linux, and is sorely disappointing.

This reminds me of the early days of Safari/WebKit, when one had to build WebKit from source and set up environment variables to use it. These days you can just click a link and it downloads a nice wrapper application that does it all. No fuss, no muss, and it allows anyone to easily use WebKit while waiting for the official Safari builds to catch up.

A model to copy, VMware. Please take note!

In the meantime...

In the meantime there is a solution, courtesy of Mufassa on the forums. He’s only posted once, but it’s a gem - in essence, compile the open tools, and then package them up for installation by the official tools install script. Works like a charm!

So, the basic steps are:

1. •Install any dependencies not shipped with a default Ubuntu install
   

2. •Get the official and open tools, and extract them
   

3. •Compile the open tools
   

4. •Rename and tar them as expected by the official tools
   

5. •Overwrite the official tools archives with the open ones
   

6. •Install them using the official tools install script
   

First, you’ll need to add several packages, either via Synaptic or apt-get:

1. •build-essential, libgtk2.0-dev, libproc-dev, libdumbnet-dev
   

2. •xorg-dev OR libX11-dev, libxinerama-dev, libxrandr-dev, libxtst-dev
   

A couple of these are new - according to this bug report, libdumbnet and libproc were added as dependencies in the 2008-04-14 version of the tools, so other guides you see likely won’t list these.

Next, download and untar both the open tools and the official ones:

1. •Open VM Tools at SourceForge
   

2. •Offical Tools are included on an iso that can be mounted via the standard VMware GUI - when mounted you want the tar.gz, not the rpm.
   

3. •Move these somewhere convenient; I recommend the desktop.
   

4. •Use “tar -xvzf *.tar.gz” to expand.
   

Compile the open tools (if you have your dependencies straightened out, this should be fast and easy):

1. •cd open-vm-tools-*/
   

2. •./configure && make
   

Next, package up the compiled modules:

1. •cd modules/linux/
   

2. •for i in *; do mv ${i} ${i}-only; tar -cf ${i}.tar ${i}-only; done
   

3. •cd ../../../
   

4. •mv -f open-vm-tools-*/modules/linux/*.tar vmware-tools-distrib/lib/modules/source/
   

Finally, install the updated tools:

1. •cd vmware-tools-distrib
   

2. •./vmware-install.pl
   

A few notes:

1. •If you disabled Shared Folders in your VM settings, you’ll see a message “Mounting HGFS shares: failed”. Just enable shared folders and reboot.
   

2. •[Appears fixed on latest tools] Networking does not seem to properly configure itself when on the default “roaming” mode. I’m honestly not sure what is wrong here, but switching it to manual configuration with DHCP or static IP works fine.
   

3. •While this was all done on Ubuntu 8.04, I expect it will work fine in the future for new Linux versions and distributions.
   

Enjoy!

invalid-file

open-vm-tools