sleep & wakeup is not always right

by robert_mu » Wed, 22 Jul 2009 15:15:45 GMT


Sponsored Links
 i all:
The phenomena happens again,here is the log(I use UART3 and ext0
to wakeup the system,after wakeup,the system enter sleep immediately):
PS:the platform is pxa310,linux kernel is 2.6.28



# echo mem > staterequest_suspend_state: sleep (0->3) at 45477172821
(2000-01-01
00:01:01.888458187 UTC)

# save exit: isCheckpointed 1
save exit: isCheckpointed 1
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
robert:PWER=0xf AD3ER=0x83
UART3
wakeup wake lock: evdev
CPU frequency from 312 MHz to 624 MHz
usb usb1: root hub lost power or was reset
otg default b device
soc-audio soc-audio: scheduling resume work
Restarting tasks ... <6>soc-audio soc-audio: starting resume work
soc-audio soc-audio: resume work completed
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:09.595825193 UTC)
mmc1: error -22 whilst initialising SDIO card
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.09 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
robert:PWER=0xf AD3ER=0x83
UART3
CPU frequency from 312 MHz to 624 MHz
usb usb1: root hub lost power or was reset
otg default b device
mmc1: error -22 whilst initialising SDIO card
soc-audio soc-audio: scheduling resume work
Restarting tasks ... <6>soc-audio soc-audio: starting resume work
soc-audio soc-audio: resume work completed
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:14.560180653 UTC)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.58 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
robert:PWER=0xf AD3ER=0x83
EXT0
CPU frequency from 312 MHz to 624 MHz
usb usb1: root hub lost power or was reset
otg default b device
mmc1: error -22 whilst initialising SDIO card
soc-audio soc-audio: scheduling resume work
Restarting tasks ... <6>soc-audio soc-audio: starting resume work
soc-audio soc-audio: resume work completed
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:24.575897218 UTC)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.58 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
robert:PWER=0xf AD3ER=0x83
EXT0
CPU frequency from 312 MHz to 624 MHz
usb usb1: root hub lost power or was reset
otg default b device
mmc1: error -22 whilst initialising SDIO card
soc-audio soc-audio: scheduling resume work
Restarting tasks ... <6>soc-audio soc-audio: starting resume work
soc-audio soc-audio: resume work completed
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:24.575897218 UTC)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.58 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
robert:PWER=0xf AD3ER=0x83
EXT0
CPU frequency from 312 MHz to 624 MHz
usb usb1: root hub lost power or was reset
otg default b device
mmc1: error -22 whilst initialising SDIO card
soc-audio soc-audio: scheduling resume work
Restarting tasks ... <6>soc-aud



sleep & wakeup is not always right

by Elvis Dowson » Wed, 22 Jul 2009 15:24:05 GMT


 Hi,     I'm facing the same issue with android-2.6.29 and android-1.5 SDK
build, on overo TI OMAP 3503 platform. Here are my observations, if someone
has a fix for this it would be great.

Observation 01
----------------------

I get the following kernel error message on bootup, could you recommend a
fix for this?

mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110

regulator: Unable to get requested regulator: vmmc_aux
regulator: Unable to get requested regulator: vmmc

SR1: VDD autocomp is not active


Observation 02
----------------------

After the system goes to suspend mode, if I press the a key that sends an
event via the serial UART3 debug console, it wakes up briefly and then
immediately goes back to sleep, and I see the following messages on the
console.

The same thing happens if I press the touchscreen briefly. I am using an
ads7846 touchscreen controller connected to a 4.3" LG-Philips LCD display,
with the gumstix overo earth (TI OMAP 3503) and palo43 board.

Powerdomain (core_pwrdm) didn't enter target state 1
Powerdomain (usbhost_pwrdm) didn't enter target state 1
Could not enter target state in pm_suspend
wakeup wake lock: mmc_delayed_work
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:04:08.555633537 UTC)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)


Observation 03
----------------------

If I press the touchscreen for a long time (> 2 secs), it comes out of
suspend mode with the following error messages

Powerdomain (core_pwrdm) didn't enter target state 1
Powerdomain (usbhost_pwrdm) didn't enter target state 1
Could not enter target state in pm_suspend
wakeup wake lock: mmc_delayed_work
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
request_suspend_state: wakeup (3->0) at 109015166614 (2000-01-01
00:04:37.537445064 UTC)
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:04:37.575256342 UTC)
D/SurfaceFlinger(  888): Screen about to return, flinger = 0x16f328

Best regards,

Elvis

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

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


Sponsored Links


sleep & wakeup is not always right

by robert_mu » Thu, 23 Jul 2009 18:40:48 GMT


 Hi,thanks for your reply :)
today I meet this error a few times,It seems that when I use the
peripheral device such as T flash card,a copper line dragged  from my
board to connect the Oscilloscopes(for test something),the error
occurs with a not low probability,is my judgement right?what condition
will cause your error there?

 thanks


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

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



sleep & wakeup is not always right

by robert_mu » Wed, 29 Jul 2009 09:47:07 GMT


 t seems that the lock state is not right ,that would cause this
error,now in driver level,when wake up,I hold a lock for 5 seconds,It
seems the second wakeup is right,it's better than former,but I don't
think it is the best way to fix this,perhaps do something in app level
is better,can anybody give me some idea?

On 73 60 robert_mu <mjko...@126.com> wrote:
--~--~---------~--~----~------------~-------~--~----~

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



Other Threads

1. Less than beginner ... completely clueless questions :)

Hello!

I've been looking around for some info about android for any phone,
other the T-mobile and HTC developer platform.

I have a linux based phone, the yujua Inid, sold in spain as Funker
f901 and in Thayland (Where I got it) as i-mobile 904.

IT has an Intel PXA270 processor at 400mhz, 64mb RAM and 128mb Flash
NAND ram, touchscreen, 2mpx autofocus camera with light. It seems to
cope ok with minimum requirements for android phone.

The process to get its nand flash rewritten is suspiciously similar to
that of HTC android enabled phones.

I got to press and hold a button in the cel, plug it in the usb port,
and it is recognized as a serial port. I have an utility on the PC
that allows me to load different libraries and files, and they get
into the phone, in order to get it actualized.  The utility reads
either a large .bin file (which as I coud see, is comprised of the
different libraries and files, all packed inside) or each file
separately.

Mi linux and phone development knowledge is close tu null. So please
excuse me if I am just writing obvious things.

The individual files that this "phone upgrading thingy" loads and
burns into the phone need to be loaded under the following titles:

Kernel, root FS, Program FS, User Data FS,  User Local, Tat, Grps2121,
patch, SysParm_Ind, SysParm_Dep.

OR else I just select a huge BIN file wich seems to have inside 7
files packed in it, that get stuffed (it takes 30 minutes) into the
phone.

Can anyone tell me if they recognize any useful information from
this ? Is there a way I can install android on this phone ? What kind
of info is needed (I can search!) ... anyone is willing to help
me ? :)  Is this the correct group ?

Regards,

Enrique.

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

2. Solution Related to emulator

I have the solution of problem related to android emulator problem.
"I'm trying to get the HelloAndroid app up and running. I can run the
emulator from the command line just fine, but there seems to be an
issue from running it within eclipse when i'm ready to launch my app.
I tried searching for some of these terms and found no luck, anybody
else with this issue or some advice? "


The solution is go to "Run Dialogue Box" then "Target" and check the
"Emulator" as "Manual" and every

when you run the Application the new Emulator will Launched. the
Problem will Solve

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

3. receive post using a DefaultHttpServerConnection object

4. Android VM for Windows5 Mobile

5. Could not find XXXX.apk!

6. Problem with istallation Android on Eclipse

7. Play Audio File (stored in files directory)