Native ABI mismatch from package file

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
5 years ago
2 years ago

People

(Reporter: lambdafox, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I have a Nook Simple Touch rooted and running Android 2.1.  It uses an ARM7 cpu.  It has 256MB built in RAM. I installed a Class 10 microSD card and added a 256MB swap file on it with Swapper2.

4.0b1 is running happily.

I have tried to install the following with no success:

fennec-5.0.en-US.eabi-arm.apk
fennec-5.0b7.en-US.eabi-arm.apk
fennec-10.0.5esr.multi.android-arm.apk
and
fennec-14.0.1.en-US.android-arm.apk

ADB logcat says they do not install because of a "Native ABI mismatch from package file".

My nderstanding was that any version before 20 should run on Android 2.1 with an ARM7.  Any advice, or is this a dead end?  Thank ytou.
We can't support 2.1 due to its limited graphics API. At best version 10.0.5esr was the last build that ran on 2.1 devices. However it is long out of support.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You can always try different Nightlies from http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/

Start with different months, then different days, and narrow down exactly when it started not working. That may provide some clues.

As a starting point, you can try 2011-01-01 which corresponds to 4.0b4
(Reporter)

Comment 3

5 years ago
(In reply to Jim Chen [:jchen :nchen] from comment #2)
> You can always try different Nightlies from
> http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/
> 
> Start with different months, then different days, and narrow down exactly
> when it started not working. That may provide some clues.
> 
> As a starting point, you can try 2011-01-01 which corresponds to 4.0b4

I was able to install the final 4.0b2.  4.0b3 gives me the ABI mismatch I mentioned above. So, I went to the nightlies and found fennec-4.0b3pre.en-US.eabi-arm in 2010-10-30-04-mozilla-central-android-r7/en-US.  There were 3 files:  an apk, a checksum and a txt file.  I put all 3 in the adb directory.

First I did adb install, but it said the file already exists.  I am guessing it is not seeing the difference between the versions??  So I did and adb install -r.  This gives me an error that the certificates are not consistent.

BTW, this is my first time digging around in here...  Can you point me to a FAQ or other article that tells me what these other folders for "electrolosys", "tracemonkey", "places", etc.  Thank you.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 4

5 years ago
Not sure why, but I had to uninstall 4.0b2 in order to continue.  From this point, I followed the pattern of installing a b3pre build from the Nightlies, then if I got success moved on to the next one.

2010/10/2010-10-30-04-mozilla-central-android-r7/en-US

Success

2010/10/2010-10-31-04-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-01-04-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-02-05-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-02-13-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-03-05-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-04-05-mozilla-central-android-r7/en-US

Success

2010/11/2010-11-05-05-mozilla-central-android-r7/en-US

	downloaded twice.  same problem both times:
	
	Length is zd -- too small file 'fennec-4.0b3pre.en-US.eabi-arm.apk' is not a valid zip file rm failed for /data/local/tmp/fennec-4.0b3pre.en-US.eabi-arm.apk, No such file or directory

2010/11/2010-11-06-05-mozilla-central-android-r7/en-US

	downloaded twice.  same problem both times:
	
	Length is zd -- too small
file 'fennec-4.0b3pre.en-US.eabi-arm.apk' is not a valid zip file rm failed for /data/local/tmp/fennec-4.0b3pre.en-US.eabi-arm.apk, No such file or directory
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 5

5 years ago
Aaron,

Are you a robot?  Can you only provide answers you were programmed to provide?

I said earlier, that I am happy to seek this information elsewhere if someone can point me in the right direction.  So far, no one has.

Since I got exactly the same error from the last two nightlies I tried yesterday, you might have offered an explanation of what that error means -- generally for any build including the latest, but no, you could not find the courtesy to do that.

I ran out of time yesterday and had to go to work.  I work again today, but will be back on this tomorrow.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
(Reporter)

Comment 6

5 years ago
2010-11-30-04-mozilla-central-android-r7/en-US

Success

2010-12-14-04-mozilla-central-android-r7/en-US (last pre 3)

 INSTALL FAILED INVALID APK
 
 logcat> native ABI mismatch!
 
2010-12-07-04-mozilla-central-android-r7/en-US

 INSTALL FAILED INVALID APK
 
 logcat> native ABI mismatch!

2010-12-04-04-mozilla-central-android-r7/en-US

 INSTALL FAILED INVALID APK
 
 logcat> native ABI mismatch!

2010/12/2010-12-02-04-mozilla-central-android-r7/en-US

Success

2010-12-03-04-mozilla-central-android-r7/en-US

 INSTALL FAILED INVALID APK
 
 logcat> native ABI mismatch!

So the Native ABI mismatch error starts with the 12-03-2010 Nightly build and persists up to 10.0.5esr.

Can you tell me what changed from the 12-02-2010 Nightly to the 12-03-2010 that might have caused this?

Strategy to move forward?

Thank you.
These are the changes that are in the 12-03-04 build but not in the 12-02-04 build:

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7212a3782e38&tochange=eb4d2a3dc388
In that range, this change seems the most likely:

http://hg.mozilla.org/mozilla-central/rev/75d91c4ff0d8
From what I can tell, your device is incompatible with the change that was made in the above-linked URL. Bug 616020, which corresponds to the change, discusses this possibility but says that there are no known devices that have the problem. In theory you should be able to make a custom build without that change that runs on your device. However, note that as of Fennec v14, Android 2.2 is the minimum requirement. As Kevin said in comment 1, you would have to use the code for 10.0.5esr in order to get the most recent thing that ran on Android 2.1, and you would have to patch it to get around this ABI compatibility error. That being said, the code in 10.0.5esr is not supported any more (and probably full of vulnerabilities that have since been fixed) so it's not recommended that you do this.

If you can upgrade your device to Android 2.2 or newer then you should be able to run the latest Firefox version either out of the box or with a small patch applied.
Please stop tampering with the resolution of this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 11

5 years ago
There is currently no way to upgrade the NST to Android 2.2.  Therefore, my second best choice is to build the highest available that will work with it, considering that would be the "least buggy available..."

I have set up the Ubuntu VM on my computer, and cloned the repository with mercurial.  I cannot find the tarball for the source code for the 4.0b3 realease which I thought I would use to test the hypothesis that Bug 616020 is the problem.

Nor can I find the tarball of the source for 10.0.5esr which is where I hope to end up.

If it was downloaded when I cloned the repository with mercurial, please help me find it.  If not, please provide me info on where I can find it from mozilla.  Thank you again.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Bugzilla is not a support forum. If you need help building Firefox #mobile on irc.mozilla.org supporting such an old build is not a priority. Please leave this bug as wontfix. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html section 2 part 2
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.