Closed Bug 669189 Opened 9 years ago Closed 9 years ago

Unsupported Devices shouldn't find Firefox in Android Market

Categories

(Release Engineering :: General, defect, P1, critical)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tarend, Assigned: aki)

Details

Attachments

(8 files)

Users of ARMv6-based devices like HTC Wildfire, HTC Legend, LG Vortex (VS660),
Huawei Ascend, etc. keep sending in their complaints that they see Firefox in the Android Market, and the installation fails on their (unsupported) devices.

Please check the Android Market filter settings for min processor and memory requirements!
And another one: Samsung Galaxy 5 (ARMv6 processor)
There are no filters on the Android Market console for restricting amrv6 or based on memory.
Looking at the restricted devices themselves, I can see the HTC Wildfire and HTC Legend are marked as "unsupported due to your manifest".

Huawei Ascend and LG Vortex are not listed anywhere.

Samsung Galaxy 3 is "unsupported due to your manifest", but Samsung Galaxy 5 is not listed anywhere.
It looks like the Android Market uses the binary libraries included with Fennec to determine the CPU restrictions. I see we include an "armeabi-v7a.so" in our APK.
Is that something we changed recently? How can we fix this asap? User complaints are piling up in my inbox - they suddenly find Firefox in the AM but crash during installation.
For what it's worth, I was just able to find Firefox and Firefox Beta on an HTC Hero of which it was not available prior.
(In reply to comment #5)
> Is that something we changed recently? How can we fix this asap? User
> complaints are piling up in my inbox - they suddenly find Firefox in the AM
> but crash during installation.

can/should we blocklist the devices?
we did not make any change (intentionally) to this since last fall. Perhaps something has changed in the AM to break it. It would be great if RelEng could confirm that these devices do not show up on the supported device list.

Tony, if the devices are excluded by our libraries they are already blacklisted and are not available to be explicitly blacklisted. That's what I'm asking RelEng to double check.
Component: General → Release Engineering
Product: Fennec → mozilla.org
QA Contact: general → release
Version: Trunk → other
Attached image htc
The Legend and Wildfire appear to be unsupported.
Attached image LG
The Vortex doesn't appear in any list.
Attached image huawei
The Ascend doesn't appear in any list.
Attached image samsung1
Attached image samsung2
Attached image samsung3
Split screenshots due to the lovely non-resizeable in-page popup.
The Galaxy 5 doesn't appear in any list.
Since the Legend and Wildfire appear in a list (albeit the unsupported list), we can explicitly blacklist them if desired.

I'm not sure what to do with the devices that aren't in any list.
That all seems to point to this being some sort of bustage with the android market. Can we file a support ticket with them?
(In reply to comment #17)
> Since the Legend and Wildfire appear in a list (albeit the unsupported
> list), we can explicitly blacklist them if desired.
> 
> I'm not sure what to do with the devices that aren't in any list.

Please go ahead and block list those so we can limit the number of users seeing this issue.
(In reply to comment #13)
> Created attachment 543964 [details]
> huawei
> 
> The Ascend doesn't appear in any list.

i Believe the Ascend = Huawei-M860
(In reply to comment #18)
> That all seems to point to this being some sort of bustage with the android
> market. Can we file a support ticket with them?

I agree.
I don't see any way to file a ticket from the Market interface... I think this is the right solution but we'll have to dig.

(In reply to comment #19)
> (In reply to comment #17)
> > Since the Legend and Wildfire appear in a list (albeit the unsupported
> > list), we can explicitly blacklist them if desired.
> > 
> > I'm not sure what to do with the devices that aren't in any list.
> 
> Please go ahead and block list those so we can limit the number of users
> seeing this issue.

Oops, I can only "exclude" supported devices.  Since those are already unsupported, there is no exclude button/link.
More complaints are rolling in: HTC Hero (528 MHz ARM 11 processor), Huawei Ideos (ARMv6) - both marked as unsupported in our spreadsheet.
And the Motorola xt300 (528 MHz ARM 11 processor, Adreno 200 GPU, Qualcomm MSM7225 chipset, 256MB RAM)
I sent a message to Android Market support.
One of the questions they asked was "device + build number" (for Android, I believe); is it possible for us to get the build number from people reporting this issue?
(In reply to comment #25)
> I see a couple of threads about this topic IIUC:
> http://www.google.com/support/forum/p/Android+Market/
> thread?tid=7d373277e7260306&hl=en
> http://www.google.com/support/forum/p/Android+Market/
> thread?tid=382234d9ca7b3e5b&hl=en

I think we're already following these; this bug, and the corresponding Android Market issue, are about how these exclusions aren't working properly.
Assignee: nobody → aki
Another one: Samsung GEM (has 800MhZ processor and only 124MB RAM - see specs at http://www.gsmarena.com/samsung_i100_gem-3738.php)
(In reply to comment #24)
> I sent a message to Android Market support.
> One of the questions they asked was "device + build number" (for Android, I
> believe); is it possible for us to get the build number from people
> reporting this issue?

Example devices:

HTC Hero: 2.1-update 1 - Build number: 2.32.651.2 CL282911 release-keys
Motorola Charm: 2.1-update1 - Build number: BASIL_U3_03.90.7
Motorola MB511 FlipOut: 2.1-update 1 - Build number: RUTH_U3_00.25.0
And the Motorola Citrus - http://www.androidcentral.com/motorola-citrus-specs (128 - 256MB memory, Processor: Qualcomm MSM7625 528MHz)
And two more:
LG Aloha (www.gsmarena.com/lg_c710_aloha-3413.php - 600MHz ARM11, 256MB) and LG Shine Plus C710h
And the Acer Liquid Mini - 600Mhz Qualcomm processor - http://www.phonearena.com/reviews/Acer-Liquid-Mini-Review_id2692
14:52 PDT
Re: [#830494510] Your message about Android Market

Hello Aki,

Thanks for taking the time to report this problem. Our team is currently investigating why this issue pops up, and we'll let you know as soon as we hear back about a solution. Thanks for your patience, and I apologize for any inconvenience this has caused.

Regards,
The Android Market Team
And the Samsung Intercept: http://www.phonescoop.com/phones/phone.php?p=2649 - processor 800 MHz Samsung S3C6410
And the LG Optimus One P500 - http://www.gsmarena.com/lg_optimus_one_p500-3516.php - 600 Mhz ARM11 processor, 170MB internal memory
And the XPeria X10 Mini (http://www.gsmarena.com/sony_ericsson_xperia_x10_mini-3125.php) - 128MB internal memory, 600 Mhz A11 processor
And the Samsung Galaxy Mini GT S5570 (http://pdadb.net/index.php?m=specs&id=2752&c=samsung_gt-s5570_galaxy_mini) - CPU: 600 MHz Qualcomm MSM7227, 384 MB RAM
And the Samsung Galaxy Apollo I5801 - 256 MB RAM, CPU: Samsung S5P6422 667 MHz processor - see http://www.gsmarena.com/samsung_i5801_galaxy_apollo-3432.php
And the Samsung Galaxy Mini GT S5570 (http://pdadb.net/index.php?m=specs&id=2752&c=samsung_gt-s5570_galaxy_mini) - CPU: 600 MHz Qualcomm MSM7227, 384 MB RAM
And the HTC Droid Eris (http://www.phonescoop.com/phones/phone.php?p=2444) - CPU: 528 MHz MSM7600, 147 MB RAM

Do we have any update on this. We still keep getting a ton of user complaints!
From July 15, after I replied to the response pasted in comment 33:

Hello Aki,

Thank you for taking the time to write to us. Our team is currently investigating your report. We hope to have a resolution soon, and will contact you when we have an update or if we need further information.

Thank you for your patience.

Regards,
The Android Market Team


No further information to date.
From 11:35 am PDT today:

Hello Aki,

Thank you for your patience. We've made some changes recently that may
have resolved the problem. If you're still having trouble, please let us
know and we'll be happy to assist you further.

Regards,
The Android Market Team
Tested a bunch of phones listed in this discussion, and all did not locate Firefox nor Firefox Beta on the market. This seems fixed now, awesome. Thanks Aki.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.