keep printing android_power:wakeup and the machine can't boot

by susanner » Mon, 09 Mar 2009 08:28:58 GMT


Sponsored Links
 I don't know whether here is the proper place to post the message, because I am 
not a kernel developer, but I met a problem seems to have relashipship with the 
knowledge of the kernel.
 After I have change opencore ( mydroid/external/opencore, this is the lower 
layer  relevant to media player) using mEmulation=true ( android/ 
android_surface_output.cpp) in order to use software codec;  and copied the 
relevant lib to system/lib, my hardware board cannot successfully boot. 
and I found the libs render the problem are libandroid_services and libmedia*
here is the print, anyone could give me any clue?
print:


android_power: wakeup (0->0) at 31319546575 (1970-01-01 00:00:31.319554395 UTC)
android_power: wakeup (0->0) at 49765869810 (1970-01-01 00:00:49.765874772 UTC)
android_power: wakeup (0->0) at 67881147696 (1970-01-01 00:01:07.881152358 UTC)
android_power: wakeup (0->0) at 86564803262 (1970-01-01 00:01:26.564808337 UTC)
android_power: wakeup (0->0) at 105151896836 (1970-01-01 00:01:45.151902551 UTC)
android_power: wakeup (0->0) at 123721148756 (1970-01-01 00:02:03.721156237 UTC)
android_power: wakeup (0->0) at 141840563717 (1970-01-01 00:02:21.840571085 UTC)
android_power: wakeup (0->0) at 160263557478 (1970-01-01 00:02:40.263562703 UTC)
android_power: wakeup (0->0) at 178231158192 (1970-01-01 00:02:58.231164658 UTC)
 
 
 
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. How to test if app is shown on Market for all screensizes

Can anyone enlighten me? :)
It looks like our app doesnt show up on the market on HTC Tattoo. What else
should we specify in the manifest?







-- 

2. Trying to get rid of my last few Long calculations in my game and completely turn it into FP format. System.currentTimeMillis() giving me a headache.



That is the wrong direction to be going. Floating-point calculations are
awful on mobile devices, since they usually lack floating-point
hardware. Your game will perform better if you eliminate as many
floating-point calculations as possible, replacing them with fixed-point
equivalents.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

Android App Developer Training: http://commonsware.com/training

-- 

3. Inflating error after animation run

4. Cari aman

5. continous raw audio playback using AudioTrack.

6. UI HTC Espresso. Best!

7. How to do Both horizontal and vertical scrolling on a screen