asked 2016-08-17 21:34:42 +0300
Intex Aqua Fish supports 2300\1800\850 frequencies, Bands 3,5 (FDD) and 40 (TDD). But it doesnt work in Russia, or the USA for example. What can be done to make 3G, 4G/LTE work again?
answered 2016-08-20 14:58:57 +0300
The droid-modem-l500d-eu package in adaptation0 contains the EU modem firmware. Jolla Cs have this package installed, while I guess Aqua Fishes ship with the droid-modem-l500d-in sibling (note: they obviously conflict with each other).
You may try installing it, keeping in mind that this operation may brick your phone.
The firmware should be flashed at the next reboot after issuing this command as root:
add-preinit-oneshot /var/lib/platform-updates/flash-modem.sh
(note: I haven't tried doing the inverse (-eu -> -in) on my Jolla C, and I won't. Pick this answer as an FYI and keep in mind that if something goes wrong you get to keep both pieces)
EDIT: As I'm seeing on the net Europeans finally getting their imported Aqua Fishes from India and referring to this answer, I'd like to stress that this hasn't been tested at all and may very well not work. I posted this answer because it might be worth a try and might be better than referring to obscure guides on XDA. Try it only if you're ready to eventually kiss your new toy goodbye.
Sounds like you just install that package from repos. Probably reflashes the modem during install/reboot for you. However, you should probably wait until that actually has any chance of giving you extra bands: https://together.jolla.com/question/137336/lte-with-jolla-c/
attah ( 2016-08-20 19:00:01 +0300 )editAssuming you are using a linux OS on you PC, I think you can try somenthing like this.
Create and use a work dir:
mkdir modem_firmware
cd mode_firmware
Donwload repomd.xml, which contains relative URI to packages list; pay attention to OS release in URL. You have to substitute "c2NlZ2xpYXU6cGFzc3dvcmQ=" with your credentials, base64 encoded:
echo -n "scegliau:password" | base64
c2NlZ2xpYXU6cGFzc3dvcmQ=
curl -c /tmp/cookie.jar -b /tmp/cookie.jar -L -v -k -H 'Authorization: Basic c2NlZ2xpYXU6cGFzc3dvcmQ=' https://store-repository.jolla.com/releases/2.0.2.45/jolla-hw/adaptation-qualcomm-l500d/armv7hl/repodata/repomd.xml
and you should see something like this:
[...]
<data type="primary">
<checksum type="sha256">72a2f27c7d57d941f573b3dfc4e9dd7881e3aca2eac86bdabf7ba393ac8c4290</checksum>
<timestamp>1465392648</timestamp>
<size>14873</size>
<open-size>120284</open-size>
<open-checksum type="sha256">23a7cd09c6d516f9618dd4dc1ca3c7280c10166b746f94fcb2dd456821fb4e41</open-checksum>
<location href="repodata/72a2f27c7d57d941f573b3dfc4e9dd7881e3aca2eac86bdabf7ba393ac8c4290-primary.xml.gz"/>
</data>
[...]
where "location" is the URI of packages list file. Then you can use that URI to do:
curl -c /tmp/cookie.jar -b /tmp/cookie.jar -L -v -k -H 'Authorization: Basic c2NlZ2xpYXU6cGFzc3dvcmQ=' https://store-repository.jolla.com/releases/2.0.2.45/jolla-hw/adaptation-qualcomm-l500d/armv7hl/repodata/72a2f27c7d57d941f573b3dfc4e9dd7881e3aca2eac86bdabf7ba393ac8c4290-primary.xml.gz -o adaptation0_l500d.xml.gz
gunzip adaptation0_l500d.xml.gz
grep droid-modem adaptation0_l500d.xml | grep href
and you'll see something like:
<location href="armv7hl/droid-modem-l500d-eu-0.0.8.2-10.8.1.jolla.armv7hl.rpm"/>
<location href="armv7hl/droid-modem-l500d-in-0.0.8.2-10.8.1.jolla.armv7hl.rpm"/>
In next step, you'll donwload EU version of firmware:
curl -c /tmp/cookie.jar -b /tmp/cookie.jar -L -v -k -H 'Authorization: Basic c2NlZ2xpYXU6cGFzc3dvcmQ=' https://store-repository.jolla.com/releases/2.0.2.45/jolla-hw/adaptation-qualcomm-l500d/armv7hl/armv7hl/droid-modem-l500d-eu-0.0.8.2-10.8.1.jolla.armv7hl.rpm -o droid-modem-l500d-eu-0.0.8.2-10.8.1.jolla.armv7hl.rpm
and then unpack it:
rpm2cpio droid-modem-l500d-eu-0.0.8.2-10.8.1.jolla.armv7hl.rpm | cpio -idmv
Now you have two usefull file in your work dir:
./boot/NON-HLOS.bin
./var/lib/platform-updates/flash-modem.sh
which are firmware and command to launch to flash it (inside shell script).
Waiting my phone (it's in Mumbai now...) I'm hoping this can help you to try a reflash of modem firmware.
scegliau ( 2016-08-20 19:09:10 +0300 )editThe postinst script in the RPM schedules the reflash by itself, but it - understandably - does so only on upgrades. The reflash can be scheduled manually with:
add-preinit-oneshot /var/lib/platform-updates/flash-modem.sh
I haven't tried (and won't try) switching the modem firmware on my Jolla C to the -in variant so I can't say that this method works, but if it's true that the Jolla C and Aqua Fish share the exactly same hardware (and I don't have any reason to believe they don't) installing the -eu package (and scheduling the reflash) should work.
Using the package is cleaner than flashing manually, and it also ensures that the modem firmware gets updated along with the rest of Sailfish.
g7 ( 2016-08-20 19:58:34 +0300 )editanswered 2016-08-28 18:36:50 +0300
I try flash modem EU on Intex. It's not work and try erase modemst1, modemst2 and flash persist. Try with QTSP and QXDM flash values from Jolla C on Intex (like manual unlock bands on OnePlus One ). Try custom values. Driver to connect with QTSP/QXDM in Diagnostic mode https://yadi.sk/d/by5jzvtZuVZwH (Lenovo Diagnostic Interface)
It's all not work.
Thanx Coderus and russian community, who trying with me and help.
I tried with:
pkcon remove droid-modem-l500d-in
which remove intex version and automatically install eu; then I manualy flash firmware. At reboot I'm not able to use SIM and my logs are full of:
Sep 01 12:20:01 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:02 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Sep 01 12:20:05 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:07 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:09 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:11 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:13 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:15 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:17 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:18 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Sep 01 12:20:21 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:23 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:25 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:27 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:29 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:31 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:33 Sailfish connmand[624]: [ofono] ERROR! GDBus.Error:org.ofono.Error.InProgress: Operation already in progress
Sep 01 12:20:34 Sailfish ofonod[622]: Power request failed: GENERIC_FAILURE
Rollbacking, connected to a WiFi :-), with:
pkcon remove droid-modem-l500d-eu
and a manual reflash, everything works again. Here in northen Italy I can use LTE with original firmware (Vodafone here uses Band-3), so this is not a big problem....but sure I'd like to flash eu firmware.
scegliau ( 2016-09-01 15:01:34 +0300 )editI live in the middle of germany in outside of any city in an rural area. My Jolla 1 always connects to Internet with LTE. I think it must be the LTE Band 800 Mhz. 2 Days ago I got my Aqua Fish. This Phone only connects with 3 G (UMTS) or 2G. In the City the Aqua Fish connects with LTE. I think it must be the 1800 Mhz Band. The Specs of Aqua Fish says, that it supports the 850 Mhz Band. So the Difference between 800 Mhz and 850 Mhz should not be to big. I think it must be possible to activate the 800 Mhz Band on the Aqua Fish with a small Software Update. In another Thread somebody told me, that Jolla Zendesk said, there are small Differences in the Hardware between the Jolla C and Aqua Fish and so its not possible to activate the LTE Band for Europe. But the Difference between 800 Mhz and 850 Mhz should be small enough to bridge it with a small Software Change. Correct me if I am wrong with my thoughts.
naalaa ( 2016-09-03 21:58:54 +0300 )editAqua Fish has band 5, which is 824MHz – 849 MHz (uplink) and 869 MHz – 894 MHz (downlink). Band 20 (800MHz) however is 832 MHz – 862 MHz (uplink) and 791 MHz – 821 MHz (downlink) according to wikipedia. The uplink frequencies are quite close, but the downlink ones are rather different, so I doubt it's only a software limitation
answered 2016-08-18 18:04:36 +0300
I've found the guide for qualqomm devices, but its for Android devices... anybody want to try it? :D http://forum.xda-developers.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269
unfortunately this is not working on the Intex Aqua Fish.
I tried it with the following configuration:
01877 rf_bc_config RF Band Configuration
2307813334318580608 10000000000111000000000000000000001111111110000000001110000000
04548 rf_bc_config_div RF BC Configuration Diversity
2307813334318580608 10000000000111000000000000000000001111111110000000001110000000
00441 band_pref Band Class Preference
0x0380 0000001110000000
00946 band_pref_16_31 Expand Band Preference 16 To 32 Bits
0x0FF8 0000111111111000
02954 band_pref_32_63 Bits 32 To 63 Of Band Pref
537329664 100000000001110000000000000000
06828 LTE_BC_CONFIG LTE BC Config
18446744073709551615 1111111111111111111111111111111111111111111111111111111111111111
or like Jolla C: 524357 10000000000001000101
06829 lte_bc_config_div LTE BC Config DIV
18446744073709551615 1111111111111111111111111111111111111111111111111111111111111111
or like Jolla C: 524357 10000000000001000101
But it still can't connect to the LTE Band 20 (800MHz).
Also additionally flashing the firmware to "EU" did not help either :-( It gives the same error as scegliau already posted about.
So it really has to be a hardware limitation as some of you already told...
PS.: GSM+UMTS configs pic
stateoftheart ( 2016-11-19 21:43:35 +0300 )editanswered 2016-08-19 15:24:50 +0300
Maybe someone with a JollaC can dump (with dd) content of /dev/block/platform/msm_sdcc.1/by-name/modem and someone else with AquaFish can try to flash it like an original NON-HLOS.bin. I'm still waiting for mine intex phone....when it'll arrive, probably, I'll try
answered 2016-09-09 16:44:13 +0300
I see lot of proposed process, but I cant see if anyone really succeeded doing it. please can someone confirm that it is practically possible and that it works?
thank you, at least it's clear.
so, we are curently completly out of possibility to get a Sailfish powered phone in europe: - Jolla C: out of stock - Intex Aqua Fish: uncompatible - Oysters SF: Not available
I will pray nothing happen to my old Jolla the first
permidion ( 2016-09-09 21:29:16 +0300 )editanswered 2017-09-25 07:42:58 +0300
I have successfully used the method posted here and there to unlock all wcdma bands on my aqua fish. Unfortunately, achieving these needs M$WIN and a lot of proprietary software.
Diagnostic mode of devices running sfos could be enabled within "Settings/USB".
NOTE: Please leave the gsm bits as-is, otherwise the sim2 will go malfunctional when sim1 is used as the primary card. wcdma bits could all be selected with no seen drawback. Fortunately, all modification applied with such method is reversible.
Unlocking LTE bands needs using NV-items_reader_writer posted here to modify NV 6828 and 6829. (both share the same content) These two nv items will revert to their last value if unlocking is failed after the phone reboots to apply their modification, so if your modifications are retained after reboot, the unlocking seems to succeed.
Using NV-items_reader_writer to read values of NV 6828 and 6829 (via "Range") to a text file (hexdump-like format), you can now modify the file according to the "Byte-swapped" representation of the value calculated with NV Calculator, then use NV-items_reader_writer to write the modified text file back to phone. Wait until all the signal indication bars turn dark, then write the modified text again. After another 10 seconds you can turn off and relaunch the phone. After its reboot, read the two NV Items again to check whether modifications are retained.
I have modified NV 6828 and 6829 of my own phone from 14 00 00 00 80 00 (bands 3,5,40) to D5 00 08 00 E0 01 (bands 1,3,5,7,8,20,38,39,40,41), but have not tried sim cards provided by carriers other than China Unicom, which is said to work on bands 1,3,8,40,41.
@mr.upolo - why you want to ask private? :)
Share it with us, I'm the one who would like to unlock that too. But I have still no time for it.
I just wanted to know, if it unlocks some frequencies for Europe, if somebody try it ;)
@persmule - thx for your information man ;)
tom.i ( 2017-10-02 13:42:12 +0300 )editanswered 2016-11-05 11:25:27 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Intex Aqua Fish is working perfectly, also on LTE/4G in Switzerland. I'm a very happy customer :-)
answered 2016-08-17 22:29:25 +0300
Isn't the Oysters phone due to drop soon? much better specs than the aquafish TBH
Is it? For me the qualcomm chipset is superior to the mediatek chipset. The other specs are similar. Besides that - the mockups show three buttons under the screen. If they keep them in the phone it shows that oyster neither understands nor really cares about sailfish.
LameDuck ( 2016-08-17 23:57:29 +0300 )edit@LameDuck The MT6753 in the Oysters SF (and in my wife's Elephone P8000, BTW) beats the Snapdragon 212 to a crap. The camera sensor is miles ahead. Overall, the specifications of the SF are the same as the P8000, which is a fine phone even when running Android, so I am pretty sure that it will fly when running SFOS.
Giacomo Di Giacomo ( 2016-08-21 11:27:06 +0300 )editanswered 2016-08-20 00:28:28 +0300
Y think that the answer is here: https://www.frequencycheck.com/compatibility/bz7rcnY/intex-aqua-fish-td-lte-dual-sim/russia Aquafish seems to work partially with tele2 in Russia.
For France it's the same problem :-( But you must have 3G on the aquafish ?
answered 2017-10-02 13:37:32 +0300
How can I add u in xmpp?
Asked: 2016-08-17 21:34:42 +0300
Seen: 9,781 times
Last updated: Sep 26 '17
Does it not support more? It is the same as the Jolla C, and that phone support more. Same snapdragon. Maybe we need to wait for a new update of SailfishOS.
richdb ( 2016-08-17 23:25:23 +0300 )edit@richdb: The snapdragon chipset supports all LTE bands, but only some of them are unlocked on the phones. The unlocked bands d iffer on Jolla C and aqua fish. I don't know wheter this is a pure software issue or whether there are (minor) HW differences (e.g. antenna design) as well.
LameDuck ( 2016-08-18 11:18:38 +0300 )editretagged, so it's easier to find
nightmare ( 2016-08-18 19:40:34 +0300 )editI am using Intex Aqua Fish in Russia. LTE works perfectly at least within MTS.
Fedorka ( 2016-08-20 15:14:51 +0300 )editFedorka, which region?
mr.upolo ( 2016-08-21 09:46:19 +0300 )edit