Ticket #118 (closed defect: fixed)

Opened 3 years ago

Last modified 20 months ago

permissions on /mnt_data/download restricts market

Reported by: Brian J. Murrell <brian@…> Owned by: bubu
Priority: minor Milestone: Android 2.3 Bull
Component: Android 2.3 Version: Android 2.2 - alpha2
Keywords: Cc:

Description

I figured out what my problem was with Market not being able to install applications, saying (in the log) that there was not enough storage space.

I changed the permissions on /mnt_data/download to 777 (of course, overly/too permissive, some experimentation will be needed to figure out the least restrictive permissions needed to function) and market was working wonderfully.

Attachments

Change History

follow-up: ↓ 2   Changed 3 years ago by dm8tbr

  • priority changed from major to minor
  • milestone changed from Android 2.2 alpha3 to Android 2.2 beta1

Is that the only location it tries? Because that's on the regular first partition filesystem (which can be ext3 OR fat32).
Does other software use this location too? I'm a bit hesitant to introduce a new shell script (which also needs to be written by someone) only to enable a market that does not officially allow this device.

in reply to: ↑ 1   Changed 3 years ago by Brian J. Murrell <brian@…>

Replying to dm8tbr:

Is that the only location it tries?

It appears to be, yes.

Because that's on the regular first partition filesystem (which can be ext3 OR fat32).

OK. So if it's fat32 there'd be no such thing as permission problems as there's no such thing as permissions!

Does other software use this location too?

That, I don't know.

I'm a bit hesitant to introduce a new shell script

Why is a new shell script needed to alter the permissions of a directory in the distribution? When is this directory created? It's at that time you'd need to set the permissions (or umask before creating it) and then leave it alone.

(which also needs to be written by someone)

chmod 777 /mnt_data/download

Done. :-)

only to enable a market that does not officially allow this device.

"Officially allow"? Why play into all of this "officially allow" nonsense? Market works just fine on openAOS Froyo.

As an Android developer, I wouldn't want Google gating access to potential customers based on their whim of what's allowed to connected to the market and what's not. It's exactly these shenanigans which is why we (Android users) are not iP{phone,{a,o}d} users.

  Changed 3 years ago by bubu

  • status changed from new to accepted

  Changed 3 years ago by bubu

  • status changed from accepted to closed
  • resolution set to fixed

fixed for openaos-froyo-alpha3_pre3-20101028.img

  Changed 2 years ago by chnapsy@…

  • status changed from closed to reopened
  • resolution fixed deleted

Hello,

Have exactly the same issue on alpha5.
chmod 777 /mnt_data/download doesn't seems to fix the problem.

  Changed 22 months ago by dm8tbr

  • milestone changed from Android 2.2 beta1 - DO NOT USE to Android 2.3 Bull

Is this issue now verified fixed?

  Changed 20 months ago by divx118

  • component changed from Android 2.2 to Android 2.3

  Changed 20 months ago by divx118

  • status changed from reopened to closed
  • resolution set to fixed

Add/Change #118 (permissions on /mnt_data/download restricts market)

Author


E-mail address and user name can be saved in the Preferences.


Action
as closed
The resolution will be deleted. Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.