Refund on Books?

by carnivalcom...@gmail.com » Mon, 23 Mar 2009 08:06:24 GMT


Sponsored Links
 Why are there refunds allowed on books (whether they are digital comic
books or motion comic books or any other regular books)? This does not
seem fair since it can be downloaded, read and then refunded and yet
they still get to keep it and re-read it as many times as they want.
I think there should be a no refund on this sort of application.  We
have had several refunds on our motion comic book which has voice-over
and music to it. Some people have downloaded all four chapters and
then had them refunded.  But I'm sure they're still enjoying them any
time they want to.  I think it should be up to the developer as to
whether or not to allow refunds on their products. It would be known
to the buyer before they buy, that there is no refund.  Then it is up
to them if they want it or not.

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



Refund on Books?

by Stoyan Damov » Mon, 23 Mar 2009 09:00:40 GMT


 If a user requests a refund, the software (the book) is being
uninstalled automatically by the Market application.
This, however, won't stop a user read all short/comic books in the ~24
hour period and then request a refund.

On Mon, Mar 23, 2009 at 12:44 AM, carnivalcom...@gmail.com



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


Sponsored Links


Refund on Books?

by Jon Colverson » Mon, 23 Mar 2009 09:03:47 GMT


 On Mar 22, 10:44pm, "carnivalcom...@gmail.com"



When a buyer uses the refund button the app is automatically
uninstalled from the phone.

--
Jon

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



Refund on Books?

by carnivalcom...@gmail.com » Mon, 23 Mar 2009 10:36:30 GMT


 Thanks for the answers.








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



Refund on Books?

by lbcoder » Mon, 23 Mar 2009 11:11:10 GMT


 You know, it actually seems quite inappropriate and exceedingly RUDE
to be selling that type of content in the APPLICATIONS market. Media/
books/other data != applications. It would be very nice if that crap
wouldn't be polluting the market. There is no reason that these things
should be marketed as applications. If you want to sell books, give
away or sell a READER APPLICATION that provides access to a
SUBSCRIPTION SERVICE. Sell or give away ONE reader application that
can subscribe to or buy MANY books/comics/whatever.

Note that this would also solve YOUR problem with refunds since YOUR
service is subject to YOUR TERMS.


On Mar 22, 10:36pm, "carnivalcom...@gmail.com"




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



Refund on Books?

by Eric Mill » Mon, 23 Mar 2009 12:41:31 GMT


 Hey, calm down. It's not the seller's fault that Google only gave them
the choice of Applications, or Games.  Neither is a good fit.

-- Eric







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



Refund on Books?

by madcoder » Mon, 23 Mar 2009 19:06:50 GMT


 My opinion is that it should be up to the developer for the refund
period, if any at all are offered.  For example, a developer could
market an app as refundable within x hours of installing, or not
refundable at all.  In the end, it's still up to the consumers to
decide to buy or not to buy.  Why is this such a bad concept?  If
someone buys an app, and it doesn't work, and the developer fails to
fix it, then call the credit card company and get it charged back.

If I think an app might be crap, then I'll wait for reviews, either in
the market or somewhere on the web.  People whine about the Apple App
store but it still manages a tremendous amount of sales.  To say that
each and every item can be returned before 24 (or 48) hours is
horrible.

Until Google/OHA changes this, there is probably going to be plenty of
people abusing the market.  And OHA members can look forward to VERY
weak Android Market sales profits.









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



Refund on Books?

by Incognito » Mon, 23 Mar 2009 20:10:58 GMT


 Android market could simply add a category for books or media. That would 
adress your complaint. This is how iphone does it.





You know, it actually seems quite inappropriate and exceedingly RUDE
to be selling that type of content in the APPLICATIONS market. Media/
books/other data != applications. It would be very nice if that crap
wouldn't be polluting the market. There is no reason that these things
should be marketed as applications. If you want to sell books, give
away or sell a READER APPLICATION that provides access to a
SUBSCRIPTION SERVICE. Sell or give away ONE reader application that
can subscribe to or buy MANY books/comics/whatever.

Note that this would also solve YOUR problem with refunds since YOUR
service is subject to YOUR TERMS.


On Mar 22, 10:36 pm, "carnivalcom...@gmail.com"


Thanks for the answers.




On Mar 22, 10:44 pm, "carnivalcom...@gmail.com"



Why are there refunds allowed onbooks(whether they are digital comic
booksor motion comicbooksor any other regularbooks)? This does not
seem fair since it can be downloaded, read and then refunded and yet
they still get to keep it and re-read it as many times as they want.

When a buyer uses therefundbutton the app is automatically
uninstalled from the phone.

--
Jon




      


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



Refund on Books?

by originalman20 » Mon, 23 Mar 2009 21:03:33 GMT


 I don't respond to many of the posts here as I am not a developer or
technician of any kind. However, this particular post caught my attention. I
think both ideas stated previously would be sufficient.
1. User uploading a text reader application (for sale or not) and allow
users to buy books through there. Giving you control over refund rules. The
app would be something like the "textonphone" app.

2. Petitioning amongst other mobile book developers to have a books and
media category in the market. Unfortunately, you would still be subject to
the markets refund policies this way.

My 2 cents...






Android market could simply add a category for books or media. That would
adress your complaint. This is how iphone does it.



it actually seems quit...

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



Refund on Books?

by lbcoder » Tue, 24 Mar 2009 05:57:36 GMT


 Eric:
Yes it is the seller's fault and I'll tell you why;
In order for this media crap to be sold correctly, the SINGLE PROGRAM
that they post should ITSELF provide the facility to buy/download/
install said media, which should be stored either on the sdcard or
within the private data space for that application.








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



Refund on Books?

by Eric Mill » Tue, 24 Mar 2009 08:31:25 GMT


 That's a good point, but I could see the advantage of Android's
built-in Google Checkout and refund system being too convenient to
turn down, rather than building one's own payment gateway for inside
your app.

That said, hopefully Google will introduce an in-app pay system down
the road, like Apple just announced for iPhone 3.0.  There's also
nothing stopping a 3rd party doing it, and by my memory at least one
has, but the name slips my mind.

-- Eric









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



Refund on Books?

by Eric Mill » Tue, 24 Mar 2009 08:35:06 GMT


 r, let's look at this from a consumer's point of view.  A 24 hour
refund policy is wonderful. Every single person I inform about the
refund policy is taken aback by how great it is.

If Google turns it into something publishers can opt in or out of,
then that's one more thing consumers have to think about while
purchasing apps, and many are not going to pay enough attention.
People are going to feel deceived if most of the apps are refundable,
but suddenly they buy a $10 app that is not.

I don't really care if this weakens Android Market sales margins. If
the Android is a big success, the sales margins are still going to be
high enough, and the # of potential customers high enough, that people
will continue making apps for them.

And by the way - I am a publisher, of a paid app (or I will be in a
few days, we're just setting up administrative details now), and this
is still my perspective.

-- Eric

On Mon, Mar 23, 2009 at 7:06 AM, madcoder <paperga...@gmail.com> wrote:

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



Refund on Books?

by Disconnect » Tue, 24 Mar 2009 08:52:53 GMT


 That would get you kicked out of the market.

Google decided nobody needed addons, subscriptions or anything other than
straight purchases. Anyone who does so is stealing from the carriers (or
google, in the case of the ADP1/holiday phones) and thats Not Allowed.

(Check the TOS)










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



Refund on Books?

by Paper Coder » Tue, 24 Mar 2009 11:15:34 GMT


 4 hours return periods are great for consumers, I'll agree one hundred
percent. It will likely draw more consumers to the platform and coerce them
to go through the trouble of signing up for Google Checkout.

In the end, however, I believe sales will suffer horribly, and the same
availability of content may not compare to the iPhone. In the end, Apple
may win based on the flood of developers that decide to stop making apps for
the Android if sales are too poor.

If you make an incredible app, that people need to use over and over, then
you can make money. If you make any form of entertainment that can be
completed within 24 hours, and the app has no reuse/replay value, then the
ability to make money may be severely limited. No matter how great the app
is. The return process is just toooooo easy and toooooo long.

Reusable/useful utilities will rule, games will not, IMO.

(Opposite of the iPhone)



On Tue, Mar 24, 2009 at 7:34 AM, Eric Mill <kproject...@gmail.com> wrote:


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



Refund on Books?

by Incognito » Tue, 24 Mar 2009 18:32:29 GMT


 gree.

On Mar 23, 2009, at 8:34 PM, Eric Mill <kproject...@gmail.com> wrote:


Er, let's look at this from a consumer's point of view. A 24 hour
refund policy is wonderful. Every single person I inform about the
refund policy is taken aback by how great it is.

If Google turns it into something publishers can opt in or out of,
then that's one more thing consumers have to think about while
purchasing apps, and many are not going to pay enough attention.
People are going to feel deceived if most of the apps are refundable,
but suddenly they buy a $10 app that is not.

I don't really care if this weakens Android Market sales margins. If
the Android is a big success, the sales margins are still going to be
high enough, and the # of potential customers high enough, that people
will continue making apps for them.

And by the way - I am a publisher, of a paid app (or I will be in a
few days, we're just setting up administrative details now), and this
is still my perspective.

-- Eric

On Mon, Mar 23, 2009 at 7:06 AM, madcoder <paperga...@gmail.com> wrote:

My opinion is that it should be up to the developer for the refund
period, if any at all are offered. For example, a developer could
market an app as refundable within x hours of installing, or not
refundable at all. In the end, it's still up to the consumers to
decide to buy or not to buy. Why is this such a bad concept? If
someone buys an app, and it doesn't work, and the developer fails to
fix it, then call the credit card company and get it charged back.

If I think an app might be crap, then I'll wait for reviews, either in
the market or somewhere on the web. People whine about the Apple App
store but it still manages a tremendous amount of sales. To say that
each and every item can be returned before 24 (or 48) hours is
horrible.

Until Google/OHA changes this, there is probably going to be plenty of
people abusing the market. And OHA members can look forward to VERY
weak Android Market sales profits.



On Mar 23, 11:41 am, Eric Mill <kproject...@gmail.com> wrote:
Hey, calm down. It's not the seller's fault that Google only gave them
the choice of Applications, or Games. Neither is a good fit.

-- Eric

On Sun, Mar 22, 2009 at 11:10 PM, lbcoder <lbco...@gmail.com> wrote:

You know, it actually seems quite inappropriate and exceedingly RUDE
to be selling that type of content in the APPLICATIONS market. Media/
books/other data != applications. It would be very nice if that crap
wouldn't be polluting the market. There is no reason that these things
should be marketed as applications. If you want to sell books, give
away or sell a READER APPLICATION that provides access to a
SUBSCRIPTION SERVICE. Sell or give away ONE reader application that
can subscribe to or buy MANY books/comics/whatever.

Note that this would also solve YOUR problem with refunds since YOUR
service is subject to YOUR TERMS.

On Mar 22, 10:36 pm, "carnivalcom...@gmail.com"
<carnivalcom...@gmail.com> wrote:
Thanks for the answers.

On Mar 22, 6:03 pm, Jon Colverson <jjc1...@gmail.com> wrote:

On Mar 22, 10:44 pm, "carnivalcom...@gmail.com"

<carnivalcom...@gmail.com> wrote:
Why are there refunds allowed onbooks(whether they are digital comic
booksor motion comicbooksor any other regularbooks)? This does not
seem fair since it can be downloaded, read and then refunded and y



Other Threads

1. How to use NDK on Windows

Hi All,

I have installed Cygwin 1.7.7 for Windows.During the installation, i
selected to install GNUMake 3.8.1. All those went through smoothly.

After installation, I check the version of make using following
command:

/bin/make

The version  is GNU make 3.81.

So I export the path using:
export GNUMAKE=/bin/make

However when I tried to run ndk-build, I still get following error:
You are using a non-Cygwin compatible Make program.

What am I wrong?

Thanks!

Cindy

-- 

2. iMX51 NFS Mount Issue

Hi guys:

      I am trying using NFS with my iMX51 EVK board. But I got following
error:

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
IP-Config: Complete:
     device=eth0, addr=10.67.174.129, mask=255.255.255.0,
gw=255.255.255.255,
     host=lowiq-laptop, domain=, nis-domain=(none),
     bootserver=10.67.174.128, rootserver=10.67.174.128, rootpath=
Looking up port of RPC 100003/2 on 10.67.174.128
PHY: 0:00 - Link is Up - 100/Full
Looking up port of RPC 100005/1 on 10.67.174.128
*VFS: Mounted root (nfs filesystem) on device 0:11.  // seems the VFS mount
NFS successfully!*
Freeing init memory: 176K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
EXT4-fs (mmcblk0p2): barriers enabled
kjournald2 starting: pid 2081, dev mmcblk0p2:8, commit interval 5 seconds
EXT4-fs (mmcblk0p2): internal journal on mmcblk0p2:8
EXT4-fs (mmcblk0p2): delayed allocation enabled
EXT4-fs: mballoc enabled
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode
EXT4-fs (mmcblk0p5): barriers enabled
kjournald2 starting: pid 2082, dev mmcblk0p5:8, commit interval 5 seconds
EXT4-fs (mmcblk0p5): internal journal on mmcblk0p5:8
EXT4-fs (mmcblk0p5): delayed allocation enabled
EXT4-fs: mballoc enabled
EXT4-fs (mmcblk0p5): recovery complete
EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode
otg is idle for some times,so we close the clock 9203120
close otg clk ok
init: cannot find '/system/etc/install-recovery.sh', disabling
'flash_recovery'
enabling adb
adb_open
# warning: `wpa_supplicant' uses 32-bit capabilities (legacy support in use)
scsi 0:0:0:0: Direct-Access     USB TO I DE/SATA Device   0009 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] Attached SCSI disk
pmem: request for physical address of pmem region from process 2162.
request_suspend_state: wakeup (3->0) at 25142872403 (1970-01-01
00:24:02.982773495 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 26238520902 (1970-01-01
00:24:04.078421869 UTC)
*init: untracked pid 2092 exited // in the SD boot condition, i do not see
this statement and the screen show Android UI*
pmem: request for physical address of pmem region from process 2219.
request_suspend_state: wakeup (0->0) at 30472309163 (1970-01-01
00:24:08.312209880 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 32148828027 (1970-01-01
00:24:09.988728619 UTC)
init: untracked pid 2190 exited
pmem: request for physical address of pmem region from process 2284.
request_suspend_state: wakeup (0->0) at 36381294036 (1970-01-01
00:24:14.221194628 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 38059705784 (1970-01-01
00:24:15.899607126 UTC)
init: untracked pid 2242 exited
pmem: request for physical address of pmem region from process 2321.
request_suspend_state: wakeup (0->0) at 42282143656 (1970-01-01
00:24:20.122044373 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 43359964285 (1970-01-01
00:24:21.199865127 UTC)
init: untracked pid 2307 exited
pmem: request for physical address of pmem region from process 2372.
request_suspend_state: wakeup (0->0) at 47575349909 (1970-01-01
00:24:25.415250751 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 49251375904 (1970-01-01
00:24:27.091277496 UTC)
init: untracked pid 2344 exited
pmem: request for physical address of pmem region from process 2438.
request_suspend_state: wakeup (0->0) at 53474052538 (1970-01-01
00:24:31.313952880 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 55145303902 (1970-01-01
00:24:32.985204744 UTC)
init: untracked pid 2395 exited
pmem: request for physical address of pmem region from process 2503.
request_suspend_state: wakeup (0->0) at 59358250285 (1970-01-01
00:24:37.198150377 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 61040894286 (1970-01-01
00:24:38.880796628 UTC)
init: untracked pid 2460 exited
pmem: request for physical address of pmem region from process 2540.
request_suspend_state: wakeup (0->0) at 65245001403 (1970-01-01
00:24:43.084902120 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 66332020534 (1970-01-01
00:24:44.171921751 UTC)
init: untracked pid 2525 exited
pmem: request for physical address of pmem region from process 2591.
request_suspend_state: wakeup (0->0) at 70563173659 (1970-01-01
00:24:48.403074626 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 72243315028 (1970-01-01
00:24:50.083215620 UTC)
init: untracked pid 2562 exited
pmem: request for physical address of pmem region from process 2656.
gsl_kmod_open: kgsl_driver_entry error
gsl_kmod_open: kgsl_driver_entry error
gsl_kmod_open: kgsl_driver_entry error
request_suspend_state: wakeup (0->0) at 76548420035 (1970-01-01
00:24:54.388320752 UTC)
Not all allocated memory blocks were freed. Doing it now.
Freeing list entry #0, gpuaddr=ab000000
Freeing list entry #1, gpuaddr=ab040000
Freeing list entry #2, gpuaddr=ab080000
Freeing list entry #3, gpuaddr=ab081000
Freeing list entry #4, gpuaddr=ab082000
Freeing list entry #5, gpuaddr=ab083000
Freeing list entry #6, gpuaddr=ab0c3000
Freeing list entry #7, gpuaddr=ab103000
Freeing list entry #8, gpuaddr=ab104000
Freeing list entry #9, gpuaddr=ab105000
request_suspend_state: wakeup (0->0) at 78219549276 (1970-01-01
00:24:56.059450868 UTC)
init: untracked pid 2614 exited
pmem: request for physical address of pmem region from process 2707.
*gsl_kmod_open: kgsl_driver_entry error   // I do not known what does this
means....*
*gsl_kmod_open: kgsl_driver_entry error*
*gsl_kmod_open: kgsl_driver_entry error*
*
*
After check the init.c code I found this error will cause a infinite loop
and just means the boot progress is hang...
Does any have met this error before? Or any one could give me any hint!
Any comments is highly appreciated!
PS. If i using the same image but with SD boot way, the Android OS can boot
normally!
Thank you!

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

3. Logcat don't work anymore...

4. How can I keep dynamic views focused through an orientation change?

5. Produsen Smartphone Android Saling Memangs

6. Problem with context menu

7. Chm reader