I don't think it's enough just to change some file paths. For example,
libhardware exposes access to "partial wake locks" and "auto off timeout",
two things that don't exist in the new 2.6.27 driver (also, the new
wakelocks have an associated timeout). The code should be removed and
changes should
Hmm, actually the BatteryService change should be backward compatible,
so it is just the SD door and wired headset detect that would break if
you ran the new userspace with the 2.6.25 kernel.
Mike
On Wed, Dec 10, 2008 at 7:52 AM, Mike Lockwood <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 10, 2008 at
On Wed, Dec 10, 2008 at 1:24 AM, Brian Swetland <[EMAIL PROTECTED]> wrote:
>
>
> We changed the wakelock APIs in 2.6.27. The current userspace code is
> not compatible with the new APIs. A large source update (as we complete
> our perforce to git transition) is coming soon which will bring these
We changed the wakelock APIs in 2.6.27. The current userspace code is
not compatible with the new APIs. A large source update (as we complete
our perforce to git transition) is coming soon which will bring these
back into sync, but for the moment you may need to stick with 2.6.25.
I believe th