This thread was archived. Please ask a new question if you need help.
Cant install FF 4.0 beta on my Android Eris running a custom ROM build of Froyo 2.2.1? I find it hard to believe that my handset wouldn't be supported, or ???
I have an ANDROID ERIS [ROOTED] running a Custom ROM that is a combination build of "AOSP -&- CyanogenMod (v6.2)"
It is called [Vanilla Tazz v28] or [Tazz Froyo v28] ... it runs ANDROID-oS version FROYO 2.2.1 [FRG83D] ....
Basically, the Tazz Froyo ROM customization enables my (('end-of-life'/'dead-to-Verizon')) handset to perform far beyond the supposed 'limitations' of the Droid Eris !
It has many of the capabilities that newer stock VZW handsets have, etc .....
MY POINT IS .... WHY CAN'T I GET ~FF 4.0 beta~ TO INSTALL ON MY DEVICE ?!?!
I have been A RELIGIOUS FIREFOX USER (PC/Laptop) FOR AT LEAST, 10 YEARS ?!?! - Well, when I got my Android, FIREFOX was the first browser I went for ... it was still in development at the time. Since then, I have been really unhappy with all MOBILE versions of FIREFOX (or FENNEC,etc.) to this date. They've been FAAAAR TOOO BIG > MB's (RE: 'Dolphin HD' -but- especially 'Dolphin MINI Browser' for Android - it's one of the BEST Droid browsers-hands down !!) ... but I am a HARD-CORE FIREFOX SUPPORTER & WOULD LOVE SOME HELP GETTING THIS TO RUN ON MY ANDROID ERIS !!!!
PLEEEEAAASSSE HELP ME GET FF 4.0 BETA TO RUN, SO I CAN USE FOX-TO-PHONE .... otherwise, I'll just have to go after GOOGLE CHROME for it's CHROME-TO-PHONE function .... I like EVERYTHING -FIREFOX- sooooo much more !!!!
All Replies (1)
While Android 2.0 is a min requirement, the cpu the phone or tablet or such device has is what makes the (huge) difference on whether current release of mobile Firefox will work or not.
You mean the HTC Droid Eris which is a modified variant of the HTC Hero.
Sorry but this phone is not compatible with the current mobile Firefox releases due to the ARMv6 (ARM11) CPU it uses (Qualcomm MSM7600A) when the releases work on ARMv7 cpu's. If it is not in Market then it likely means the hardware is not compatible.
You can perhaps try the experimental ARMv6 nightlies (Fennec).
Modified by James