about the market 15 minutes refund window

by nick » Mon, 20 Dec 2010 15:57:03 GMT


Sponsored Links
 It seems that the new 15 minute refund windows is live, but is it so
in every country with paid apps? And if so, how does it look from
Google Checkout? I would expect that order state will change to
Charged/Shipped within more or less 15 minutes. This is not the case
in Japan though. It still takes about 24 hours for the order state to
change to Charged/Shipped. So the question is: is the new refund
window not active everywhere or is it just orders update only once a
day?

-- 



Re: about the market 15 minutes refund window

by TreKing » Mon, 20 Dec 2010 23:23:24 GMT


 



I believe it's the latter. Awesome, ain't it?

-------------------------------------------------------------------------------------------------
TreKing < http://sites.google.com/site/rezmobileapps/treking> ; - Chicago
transit tracking app for Android-powered devices

-- 


Sponsored Links


Re: about the market 15 minutes refund window

by Zsolt Vasvari » Tue, 21 Dec 2010 07:26:54 GMT


 It's still exactly like before.  The orders get updated with the 24hr+
rolling schedule.






-- 



Re: about the market 15 minutes refund window

by nick » Tue, 21 Dec 2010 09:51:35 GMT


 


Thanks for the confirmation. I have some orders that updated in less
than 24 hours,
but most are updated in about 27 hours. As usual, the ways of the
Market are mysterious.





-- 



Re: about the market 15 minutes refund window

by nick » Tue, 21 Dec 2010 10:14:01 GMT


 


Please don't hijack threads. Start a new topic with your question,
don't just reply to any random message that happens to be on top.

Thank you.

-- 



Re: Re: about the market 15 minutes refund window

by TreKing » Tue, 21 Dec 2010 12:02:27 GMT


 





He didn't - it's a separate GMail message. If you're viewing through Google
Groups online, well, that interface sucks and sometimes crosses posts.

-------------------------------------------------------------------------------------------------
TreKing < http://sites.google.com/site/rezmobileapps/treking> ; - Chicago
transit tracking app for Android-powered devices

-- 



about the market 15 minutes refund window

by metal mikey » Tue, 21 Dec 2010 12:35:58 GMT


 @Jiang: To solve your problem, first you need to make your own thread
and stop being so rude as to hijack pre-existing threads.
...2nd warning, <facepalm>



-- 



Re: about the market 15 minutes refund window

by metal mikey » Tue, 21 Dec 2010 13:05:46 GMT


 @TreKing: because the subject was changed, gmail lists it as a 2nd
conversation, however it remains bound to the same thread in Google
Groups because it continues to use the docid from the original thread
(that had its subject changed). Try emailing yourself an email with a
certain subject, then in gmail reply to that email but 'Edit Subject'
to something different...you'll see you'll get a seperate thread in
gmail.

-- 



Re: about the market 15 minutes refund window

by Zsolt Vasvari » Tue, 21 Dec 2010 14:38:41 GMT


 Changing subject back.




-- 



Re: about the market 15 minutes refund window

by Brill Pappin » Tue, 21 Dec 2010 15:32:18 GMT


 Actually that kind of fits with the processor industry and banking in 
general.

Typically transactions are batch processed daily. This is similar to a 
retail setting were the registers are closed out daily.
It's a legacy of when we used paper for all this stuff, but the banks still 
run the same way, so everyone else has to as well.

What I'm saying, is that its makes complete sense to me, having worked with 
this stuff before, that it doesn't look like anything is different... it's 
because its actually not different on the Checkout side and it's on purpose.

Any agreement to automatically refund the user is a Market thing, not a 
Checkout thing but your viewing your transactions in Checkout.

I hope that reduces the confusion :)
- Brill Pappin

-- 



Re: Re: about the market 15 minutes refund window

by TreKing » Tue, 21 Dec 2010 23:06:37 GMT


 



Oh, gotcha, that makes sense. I always assume it's Google Groups being it's
crappy self. I take back my defense of the hijacker =P

-------------------------------------------------------------------------------------------------
TreKing < http://sites.google.com/site/rezmobileapps/treking> ; - Chicago
transit tracking app for Android-powered devices

-- 



Re: Re: about the market 15 minutes refund window

by Nikolay Elenkov » Fri, 11 Feb 2011 16:46:46 GMT


 Hi,




Sorry I missed your reply.

It does make sense when you think of it in the context of batch processing.
It's just hard to imagine that Google uses a cronjob that fires every
morning at 2 am
and goes through a bunch of CSV files downloaded over FTP :)

Anyway, they must have changed something, because orders are
now processed after about 4 hours. Someone has been playing with cron :)
It is better this way, just wish I could figure out the new payment schedule...

-- 



Other Threads

1. OOT: Windowsmobile jadi Windowsphone

Setelah windowsmobile versi 6,5 maka windowsmobile berganti nama menjadi 
windowsphone. Apakah ini strategi menghadapi Android versi 2?


Salam,

Agus Hamonangan


Sent from my BlackBerry Jave  
Powered by XL GPRS/EDGE/3G Network
--~--~---------~--~----~------------~-------~--~----~

2. Failed to run cupcake on emulator

The cupcake can't boot up on the emulator. Can anybody help me check
what is the problem? please see the Logcat

I built cupcake images and kernel by myself.


mille...@millerfu-desktop:~/cupcake$emulator -kernel ~/kernel/arch/arm/
boot/zImage -system out/target/product/generic/system.img -ramdisk out/
target/product/generic/ramdisk.img -initdata out/target/product/
generic/userdata.img -avd AndroidSDK




08-19 03:39:07.593: INFO/DEBUG(539): de{*filter*}d: Aug 13 2009 14:28:58
08-19 03:39:07.613: INFO/vold(538): Android Volume Daemon version 2.0
08-19 03:39:07.724: ERROR/vold(538): Error opening switch name path '/
sys/class/switch/test2' (No such file or directory)
08-19 03:39:07.724: ERROR/vold(538): Error bootstrapping switch '/sys/
class/switch/test2' (No such file or directory)
08-19 03:39:07.724: ERROR/vold(538): Error opening switch name path '/
sys/class/switch/test' (No such file or directory)
08-19 03:39:07.724: ERROR/vold(538): Error bootstrapping switch '/sys/
class/switch/test' (No such file or directory)
08-19 03:39:07.724: DEBUG/vold(538): Bootstrapping complete
08-19 03:39:08.092: DEBUG/qemud(547): entering main loop
08-19 03:39:08.702: DEBUG/qemud(547): fdhandler_accept_event:
accepting on fd 10
08-19 03:39:08.712: DEBUG/qemud(547): created client 0xe078 listening
on fd 8
08-19 03:39:08.732: DEBUG/qemud(547): client_fd_receive: attempting
registration for service 'boot-properties'
08-19 03:39:08.732: DEBUG/qemud(547): client_fd_receive:    ->
received channel id 1
08-19 03:39:08.746: DEBUG/qemud(547): client_registration:
registration succeeded for client 1
08-19 03:39:09.283: DEBUG/qemud(547): fdhandler_accept_event:
accepting on fd 10
08-19 03:39:09.283: DEBUG/qemud(547): created client 0x10028 listening
on fd 11
08-19 03:39:09.283: DEBUG/qemud(547): fdhandler_event: disconnect on
fd 11
08-19 03:39:09.892: INFO/qemu-props(557): connected to 'boot-
properties' qemud service.
08-19 03:39:09.912: INFO/qemu-props(557): exiting (0 properties set).
08-19 03:39:10.883: DEBUG/qemud(547): fdhandler_accept_event:
accepting on fd 10
08-19 03:39:10.883: DEBUG/qemud(547): created client 0xe078 listening
on fd 8
08-19 03:39:10.883: DEBUG/qemud(547): client_fd_receive: attempting
registration for service 'gsm'
08-19 03:39:10.883: DEBUG/qemud(547): client_fd_receive:    ->
received channel id 2
08-19 03:39:10.892: DEBUG/qemud(547): client_registration:
registration succeeded for client 2
08-19 03:39:11.032: DEBUG/AndroidRuntime(541): >>>>>>>>>>>>>>
AndroidRuntime START <<<<<<<<<<<<<<
08-19 03:39:11.032: DEBUG/AndroidRuntime(541): CheckJNI is ON
08-19 03:39:11.243: DEBUG/dalvikvm(541): DexOpt: incorrect opt magic
number (0xff ff ff ff)
08-19 03:39:11.243: DEBUG/dalvikvm(541): Stale deps in cache file;
removing and retrying
08-19 03:39:11.583: INFO/(542): ServiceManager: 0xac38
08-19 03:39:11.633: INFO/AudioFlinger(542): AudioFlinger's thread
ready to run for output 0
08-19 03:39:11.663: DEBUG/dalvikvm(541): DexOpt: --- BEGIN
'core.jar' (bootstrap=1) ---
08-19 03:39:11.703: INFO/CameraService(542): CameraService started:
pid=542
08-19 03:39:12.213: ERROR/dalvikvm(575): Too many exceptions during
init (failed on 'Ljava/lang/NoClassDefFoundError;'
'java.lang.NoClassDefFoundError')
08-19 03:39:12.222: ERROR/dalvikvm(575): VM aborting
08-19 03:39:12.354: INFO/DEBUG(539): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
08-19 03:39:12.354: INFO/DEBUG(539): Build fingerprint: 'generic/
generic/generic/:Donut/Donut/eng.millerfu.20090813.134359:eng/test-
keys'
08-19 03:39:12.363: INFO/DEBUG(539): pid: 575, tid: 575  >>> /system/
bin/dexopt <<<
08-19 03:39:12.363: INFO/DEBUG(539): signal 11 (SIGSEGV), fault addr
deadd00d
08-19 03:39:12.373: INFO/DEBUG(539):  r0 00000330  r1 0000000c  r2
0000000c  r3 00000026
08-19 03:39:12.385: INFO/DEBUG(539):  r4 deadd00d  r5 00020228  r6
ad06eba4  r7 00000000
08-19 03:39:12.385: INFO/DEBUG(539):  r8 00000000  r9 00000000  10
00000000  fp 00000000
08-19 03:39:12.385: INFO/DEBUG(539):  ip ad083ef8  sp be947aa0  lr
afe13f0d  pc ad03b88a  cpsr 20000030
08-19 03:39:12.413: INFO/DEBUG(539):          #00  pc 0003b88a  /
system/lib/libdvm.so
08-19 03:39:12.413: INFO/DEBUG(539):          #01  pc 0003af48  /
system/lib/libdvm.so
08-19 03:39:12.423: INFO/DEBUG(539):          #02  pc 0003b1c4  /
system/lib/libdvm.so
08-19 03:39:12.423: INFO/DEBUG(539):          #03  pc 0005ced6  /
system/lib/libdvm.so
08-19 03:39:12.423: INFO/DEBUG(539):          #04  pc 0005d110  /
system/lib/libdvm.so
08-19 03:39:12.433: INFO/DEBUG(539):          #05  pc 0005d9ee  /
system/lib/libdvm.so
08-19 03:39:12.433: INFO/DEBUG(539):          #06  pc 0003af4e  /
system/lib/libdvm.so
08-19 03:39:12.433: INFO/DEBUG(539):          #07  pc 0003b1c4  /
system/lib/libdvm.so
08-19 03:39:12.443: INFO/DEBUG(539):          #08  pc 0005ced6  /
system/lib/libdvm.so
08-19 03:39:12.443: INFO/DEBUG(539):          #09  pc 0005d110  /
system/lib/libdvm.so
08-19 03:39:12.443: INFO/DEBUG(539):          #10  pc 0005d9ee  /
system/lib/libdvm.so
08-19 03:39:12.453: INFO/DEBUG(539):          #11  pc 0004f3be  /
system/lib/libdvm.so
08-19 03:39:12.453: INFO/DEBUG(539):          #12  pc 000506d6  /
system/lib/libdvm.so
08-19 03:39:12.453: INFO/DEBUG(539):          #13  pc 000508b2  /
system/lib/libdvm.so
08-19 03:39:12.463: INFO/DEBUG(539):          #14  pc 00008e5a  /
system/bin/dexopt
08-19 03:39:12.463: INFO/DEBUG(539):          #15  pc 00008f14  /
system/bin/dexopt
08-19 03:39:12.463: INFO/DEBUG(539):          #16  pc 0000bd60  /
system/lib/libc.so
08-19 03:39:12.473: INFO/DEBUG(539):          #17  pc b000163c  /
system/bin/linker
08-19 03:39:12.473: INFO/DEBUG(539): stack:
08-19 03:39:12.473: INFO/DEBUG(539):     be947a60  000001e3
08-19 03:39:12.473: INFO/DEBUG(539):     be947a64  ad065b67  /system/
lib/libdvm.so
08-19 03:39:12.483: INFO/DEBUG(539):     be947a68  afe39f90
08-19 03:39:12.483: INFO/DEBUG(539):     be947a6c  afe39fe4
08-19 03:39:12.483: INFO/DEBUG(539):     be947a70  00000000
08-19 03:39:12.483: INFO/DEBUG(539):     be947a74  afe13f0d  /system/
lib/libc.so
08-19 03:39:12.483: INFO/DEBUG(539):     be947a78  00020228  [heap]
08-19 03:39:12.483: INFO/DEBUG(539):     be947a7c  afe12f29  /system/
lib/libc.so
08-19 03:39:12.493: INFO/DEBUG(539):     be947a80  00020228  [heap]
08-19 03:39:12.493: INFO/DEBUG(539):     be947a84  ad083e1c
08-19 03:39:12.493: INFO/DEBUG(539):     be947a88  00020228  [heap]
08-19 03:39:12.493: INFO/DEBUG(539):     be947a8c  ad06eba4  /system/
lib/libdvm.so
08-19 03:39:12.493: INFO/DEBUG(539):     be947a90  00000000
08-19 03:39:12.503: INFO/DEBUG(539):     be947a94  afe12f8d  /system/
lib/libc.so
08-19 03:39:12.503: INFO/DEBUG(539):     be947a98  df002777
08-19 03:39:12.503: INFO/DEBUG(539):     be947a9c  e3a070ad
08-19 03:39:12.513: INFO/DEBUG(539): #00 be947aa0  ad083e1c
08-19 03:39:12.513: INFO/DEBUG(539):     be947aa4  ad03af4d  /system/
lib/libdvm.so
08-19 03:39:12.513: INFO/DEBUG(539): #01 be947aa8  00020228  [heap]
08-19 03:39:12.513: INFO/DEBUG(539):     be947aac  ad06eba5  /system/
lib/libdvm.so
08-19 03:39:12.513: INFO/DEBUG(539):     be947ab0  ad06eba4  /system/
lib/libdvm.so
08-19 03:39:12.513: INFO/DEBUG(539):     be947ab4  00020228  [heap]
08-19 03:39:12.513: INFO/DEBUG(539):     be947ab8  ad06eba4  /system/
lib/libdvm.so
08-19 03:39:12.513: INFO/DEBUG(539):     be947abc  00000000
08-19 03:39:12.574: INFO/DEBUG(539):     be947ac0  ad06eba4  /system/
lib/libdvm.so
08-19 03:39:12.574: INFO/DEBUG(539):     be947ac4  ad03b1c9  /system/
lib/libdvm.so
08-19 03:39:12.603: WARN/dalvikvm(541): DexOpt: --- END 'core.jar' ---
status=0x000b, process failed
08-19 03:39:12.603: ERROR/dalvikvm(541): Unable to extract+optimize
DEX from '/system/framework/core.jar'
08-19 03:39:12.613: DEBUG/dalvikvm(541): Failed on '/system/framework/
core.jar' (boot=1)
08-19 03:39:12.613: DEBUG/dalvikvm(541): VM cleaning up
08-19 03:39:12.613: DEBUG/dalvikvm(541): LinearAlloc 0x0 used 4100 of
4194304 (0%)
08-19 03:39:12.633: WARN/dalvikvm(541): JNI_CreateJavaVM failed
08-19 03:39:12.633: ERROR/AndroidRuntime(541): JNI_CreateJavaVM failed


thanks in advance.
Miller Fu

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:  http://www.***.com/ 
-~----------~----~----~----~------~----~------~--~---

3. How to listen # or other

4. wifi vs. ota...

5. Plugin

6. map with compass like indicator

7. custom events