The default bug view has changed. See this FAQ.

Motorola Defy users get low memory warning

VERIFIED FIXED in Firefox 7

Status

Fennec Graveyard
General
P2
critical
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: tarend, Assigned: mbrubeck)

Tracking

({verified-aurora, verified-beta})

Trunk
Firefox 7
ARM
Android
verified-aurora, verified-beta

Details

(Whiteboard: [landed m-c 5/24] [purely android code])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Motorola Defy users seem to see our low memory warning even though the device is officially supported based on https://www.mozilla.com/en-US/mobile/platforms/
It would be good to know the contents of /proc/meminfo on the Defy to find out more.

Related to Bug 649841 - opening this separate bug so we can specifically test on a Defy.
(Assignee)

Comment 1

6 years ago
blassey pointed out on IRC that we could just remove the low memory warning, now that we are blacklisting (in the Market) the devices it was meant to apply to.
(In reply to comment #1)
> blassey pointed out on IRC that we could just remove the low memory warning,
> now that we are blacklisting (in the Market) the devices it was meant to
> apply to.

This idea has merit. Any real use for this annoying message now that we can (and do) blacklist?
(Reporter)

Comment 3

6 years ago
I am all for removing clutter. However, alternative distribution channels that we are looking at may not have blacklisting. Also, I wonder if we would have cases were we officially support a device but detect that they have so much stuff installed and running on their phone that the *available* memory may make Fennec run slower than usual. In that case we would turn that warning into something useful that tells users how to free up memory, recommend moving apps to SD card, etc.
(Assignee)

Comment 4

6 years ago
(In reply to comment #3)
> I am all for removing clutter. However, alternative distribution channels
> that we are looking at may not have blacklisting.

There are only two devices that can run Fennec but have less than the suggested RAM requirement, and it looks unlikely that any such more devices will be introduced.  The Android Market is and will remain the primary distribution channel for those two legacy devices.

> Also, I wonder if we would
> have cases were we officially support a device but detect that they have so
> much stuff installed and running on their phone that the *available* memory
> may make Fennec run slower than usual. In that case we would turn that
> warning into something useful that tells users how to free up memory,
> recommend moving apps to SD card, etc.

The Android OS will automatically unload running processes to free up RAM, and will also warn the user about low disk storage space and recommend moving or uninstalling apps.  We shouldn't need to do this ourselves.  Anyway, our ability to add hypothetical new warnings would not be impacted by removing the current low-total-RAM warning.
(In reply to comment #3)
> I am all for removing clutter. However, alternative distribution channels
> that we are looking at may not have blacklisting. 
again, I think that is up for these alternative distribution channels to solve
> Also, I wonder if we would
> have cases were we officially support a device but detect that they have so
> much stuff installed and running on their phone that the *available* memory
> may make Fennec run slower than usual. In that case we would turn that
> warning into something useful that tells users how to free up memory,
> recommend moving apps to SD card, etc.
I suspect that's what is happening with the defy. The current message doesn't speak to that though, so I'd suggest filing a different bug for it.
(Assignee)

Updated

6 years ago
Depends on: 652787
(Assignee)

Comment 6

6 years ago
Created attachment 534872 [details] [diff] [review]
patch

Remove the memory warning dialog.
Assignee: nobody → mbrubeck
Status: NEW → ASSIGNED
Attachment #534872 - Flags: review?(blassey.bugs)
Attachment #534872 - Flags: review?(blassey.bugs) → review+
(Assignee)

Comment 7

6 years ago
http://hg.mozilla.org/mozilla-central/rev/a0543ec5f10a
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 7

Comment 8

6 years ago
Can someone please verify this bug?
We will have access to a Defy when the Deviceanywhere account is activated. Are we taking this patch for Firefox 6 or backing out bug 652787.
status-firefox5: --- → unaffected
status-firefox6: --- → affected
tracking-fennec: --- → ?

Comment 10

6 years ago
I verified this using Deviceanywhere on Motorola Defy build ids:
Mozilla /5.0 (Android;Linux armv7l;rv:8.0a1) Gecko/20110712 Firefox/8.0a1 Fennec/8.0a1 and 
Mozilla /5.0 (Android;Linux armv7l;rv:7.0a2) Gecko/20110711 Firefox/7.0a2 Fennec/7.0a2

I didn't saw any memory warning dialog, therefore I am marking it as verified fixed
Status: RESOLVED → VERIFIED
tracking-fennec: ? → 6+
status-firefox7: --- → fixed
status-firefox8: --- → fixed
Attachment #534872 - Flags: approval-mozilla-beta?

Updated

6 years ago
Whiteboard: [landed m-c 5/24] [purely android code]

Updated

6 years ago
Attachment #534872 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
http://hg.mozilla.org/releases/mozilla-beta/rev/1c05f5b86b7b

Comment 12

6 years ago
Beta and aurora are string frozen. This is just removing strings, but it would have been better to just create an extra patch that drops the usage of those string and leaves them unused, and make the removal go through the regular channel updates from central to aurora to beta.

Comment 13

6 years ago
Axel, do you want us to revert and do what you suggest in comment 12?
status-firefox6: affected → fixed

Comment 14

6 years ago
Thanks, but no thanks. Just for future reference.
Xperia x10i

Mozilla/5.0 (Android; Linux armv7l; rv:8.0a1) Gecko/20110727 Firefox/8.0a1 Fennec/8.0a1 ID:20110727081800

Mozilla/5.0 (Android; Linux armv7l; rv:7.0a2) Gecko/20110727 Firefox/7.0a2 Fennec/7.0a2 ID:20110727044233 

Mozilla/5.0 (Android; Linux armv7l; rv:6.0) Gecko/20110721 Firefox/6.0 Fennec/6.0 ID:20110721142609
Keywords: verified-aurora, verified-beta
You need to log in before you can comment on or make changes to this bug.