Why is app taking so long to show up

by KoZoMo .com » Fri, 28 May 2010 03:52:19 GMT


Sponsored Links
 Hi,

We've been waiting patiently for our app to appear but it is still not
there. Is there a delay due to 2.2? The app is iGoals Italy.

Regards,

Michael

--



Other Threads

1. sleep & wakeup is not always right

Hi 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-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)




--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Why force java 1.5?

Recently the build system will check if java version is 1.5, and stop
if the version mismatch. I'm unhappy with such unnecessary checking.

My system is Fedora 11, I can use its default java compiler, openjdk
1.6, to compile Android without problem. In fact I just removed the
unnecessary checking, and it compiled fine. I can run the emulator
well. I didn't notice any abnormality yet.

Any comment?
--~--~---------~--~----~------------~-------~--~----~

3. Is arm-eabi-gcc support iwmmxt?

4. is it possible to display a multi column list ?

5. Where can I find good remote Android developers?

6. Getting exception if directional key pad is pressed, pls help

7. Bitmaps and AppWidgets