Bugs in firefox 52=>53 on ArchLinuxARM 32 bits (ARMv7h) and how to still use it

Firefox 53 currently doesn’t compile on ARMv7h, so only firefox 52 works on ALARM/armv7h, but as the 52 package is no more in git current version, ALARM compiling sysyem doesn’t compile it with updated dependencies (ICU moved from 58 to 59 and hunspell updated too. I didn’t managed to compile firefox-esr.

I compiled former version of this too libs to be able to make firefox 52 works again.
You can find both icu-58 and hunspell 1.5.4 packages here. PLEASE DON’T INSTALL THEM, you can reinstall firefox package itself if needed with pacman -U firefox-52.0.2-1-armv7h.pkg.tar.xz
instead unarc them in a directory like this :

cd /tmp
mkdir unarc; cd unarc
wget https://popolon.org/depots/ArchLinuxARM/firefox/52/hunspell-1.5.4-1-armv7h.pkg.tar.xz
wget https://popolon.org/depots/ArchLinuxARM/firefox/52/icu-58.2-1-armv7h.pkg.tar.xz
tar xf hunspell-1.5.4-1-armv7h.pkg.tar.xz # lot of errors with SCHILY.fflags will be displayed
tar xf icu-58.2-1-armv7h.pkg.tar.xz # lot of errors with SCHILY.fflags will be displayed
cd usr/lib
sudo rsync -a libhunspell-1.5.so* libicu.so.58* /usr/lib/
sudo rsync -a icu/58.2 /usr/lib/icu/
ldconfig

That’s done. You can now type firefox to launch it :)

The nightmare of Samsung, progressive regression of basic usefull functions. (Corrected on Galaxy A after april 2 & 23, 2016 updates)

This entry was first published in mid-February 2016. April 2, 2016 system update correct the problem. Now, device can be used as MTP and PTP device.
April 23, 2016 system update correct the second problem. Now, USB mass storage device (lke usb keys) can be used trhough a USB-OTG wire.

Samsung doesn’t want anymore customers… at least with the Galaxy A series.
* Now, there is no more support for MTP/PTP (mass storage was already removed some years ago), so, you can’t anymore connect via USB on any computer and exchange files…
* Worst, USB mass storage media (like USB keys) are not recognised by USB-OTG wire :(. Why do they remove this basic functionnalities found on any Android devices, including 20$ chinese ones.
* Fuckin/Suckin Microsoft applications are added, as Samsung and Google overload was not enough, reducing battry lifetime to nearly nothing. You need lot of work to disable most of them (in settings, applications submenues), and rooting device to have really peace and battry life.

I was very used to buy Samsung phones with Samsung processors, as there was not US ones, because of current wars in several Asian (Irak, Afghanistan…) and African (Libya, etc…) countries. No Us even add lot of money (with their France, Germany, and Saudian Arabia partnerrs) to Daech, as if libyan was not enough. And as Samsung is a weaponry partner of US (like LG and Daewoo). And their are anti electronic-freedom, I will make everything to avoid them…

At the same time, chineses companies make nice phones, like Huawei with their own processors, Xiaomi, but with US, Snapdragon processors, Meizu, and taiwan chineses like Asus or some other made some too. In this area I really prefer Rockchip that work openly with the internationally made Linux kernel, and I hope to found smartphones with those fine processors. Their new generation RK3399 seems really promising for best computing and energy efficient performances. That’s definitivly last time I buy a Samsung phone :(.