yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] radbme:
After sending my logs to Jolla about MMS, I got a reply from Jolla's MMS (and ofono) specialist. He said, "It's indeed a data call format mismatch. Here is how I'm planning to resolve this issue:

hxxps://git.merproject.org/mer-core/ofono/merge_requests/90

Once that is merged, you (or whoever is maintaining the port) should be able to add dataCallFormat=6 to /etc/ofono/ril_subscription.conf and the problem should go away."

But after some more back and forth I'm running ofono-1.17+git29-10.2.2.jolla.armv7hl which is apparently not working with the patch. He then replied, "I guess I promised a bit too much. I did give a try but this patch doesn't merge well on top of 1.17+git29. You would have to wait until ofono gets upgraded to mer/1.18+git3 or later (not sure which version of SailfishOS it's going to be, whatever comes after 2.0.5) and add

dataCallFormat=6

to either [Settings] or [ril_0] section or /etc/ofono/ril_subscription.conf. Then simultaneous data calls should start working and you should be able to send/receive MMS with mobile data on."

So I guess we wait until 2.0.5 or whenever the updated ofono gets merged. It was really nice of him to help me out though. He knew it was a port too but was very helpful. :)
[Nexus 4 Android Development] Kubino:
At the end of last week I made fresh install of SFOS gamma 7.1 but I don't see much difference in battery drain. Today I made fresh install again but with this as base (newer CM11, the FOSS zip). I will see whether it will make any difference.
[Nexus 4 Android Development] Kubino:
With the newer base camera and sfdroid doesn't work (when I run sfdroid in terminal, write "Can't find service: power") so I will reflash again :D. And cpu sleep 0% all the time and cpu usage over night 25% (this combination = -15% down after night).
[Nexus 4 Android Development] deshmukhrb2000:
Newer SAILFISH OS UPDATE:FISKARSINJOKI out
[Nexus 4 Android Development] ddaggebi:
Just wanted to bump SFOS up.

Any news on cm12.1 based SFOS or the newest salifish update being ported?
[Nexus 4 Android Development] rinigus:
Here is a short update regarding the status.

Re CM12.1: the main issue is in the release of CM12.1 base. The several SFOS ports were developed against CM12.1 YOG7D while N4 has only YOG4P released. We have made our own builds of CM YOG7D and used them as a base. Unfortunately, for legal reasons (android device blobs), we cannot distribute our CM build through the same channel as SFOS. To circumvent the problem, the small sets of scripts (https://github.com/rinigus/patcher) has been developed that should allow to use YOG4P as a base while you install SFOS and later apply an update that would bring you to YOG7D level. These scripts have not been tested thoroughly - I and ballock (bolek1337 on xda, the main developer of the port) have been quiet on porting recently.

Note that CM12.1 base does not have working SFDroid - SFDroid development has slowed down since summer. As for other parts: to my knowledge, all was working on CM12.1 except the front camera.

Re update to the next release: I don't know much about it. Maybe ballock has worked on it meanwhile.
[Nexus 4 Android Development] ddaggebi:
Thanks for the update! Appreciate it!

It is little sad that there are no SFdroid, but doesn't matter that much when you have SFOS.
[Nexus 4 Android Development] radbme:
Got MMS fixed! Ok here's what to do if you're having issues with MMS not working when wifi is disconnected directly from Jolla's MMS guy, Slava:

1. Download rpms from here http://repo.merproject.org/obs//home:/slava:/test/sailfishos_2.0.0.10_latest_armv7l/armv7hl/ - look for something close to ofono-1.18+git9-70.1.armv7hl.rpm for the latest version and then do the same thing for libmce-glib, you will definitely need it.

2. Suppose you now have these rpms:

ofono-1.18+git3-66.1.armv7hl.rpm

libmce-glib-1.0.1-10.3.1.jolla.armv7hl.rpm

copy them to the phone:

$ scp ofono-1.18+git3-66.1.armv7hl.rpm libmce-glib-1.0.1-10.3.1.jolla.armv7hl.rpm nemo@192.168.2.15:/tmp

3. ssh into the phone and install the packages:

$ ssh nemo@IPADDRESS

nemo@IPADDRESS password:

[nemo@Sailfish ~]$ devel-su

Password:

[root@Sailfish nemo]# cd /tmp

[root@Sailfish tmp]# pkcon install-local *rpm

<suppose rpms get installed successfully>

[root@Sailfish tmp]# systemctl restart ofono

Then once you have the latest ofono installed you need to edit /etc/ofono/ril_subscription.conf:

$ devel-su vi /etc/ofono/ril_subscription.conf (if you get an auth failed here reboot the phone and try again)

and add "dataCallFormat=6" to the Settings section, i.e.

[Settings]

dataCallFormat=6

If this section is missing, add it. Then it should work (if I haven't forgotten anything else). And if it still doesn't work, please take another log and sent it to us.
[Nexus 4 Android Development] zephir_1:
Workaround for Fiskarsinjoki required

Version 2.0.4.13 is still experimental and does not work out-of-the-box on Nexus 4 after OTA update from 2.0.2. Camera is not responsive. No action on GPS. However main features such as voice call, SMS, network are working.
[Nexus 4 Android Development] Kubino:
I was using 2.0.4.14 and no problem with camera. I didn't use GPS. I am using 2.0.5.6 now.
[Nexus 4 Android Development] HAF-MED:
Sailfish ver 2.0.5.6

Hi, I have nexus 4 with multirom and I want to install on it Sailfish ver 2.0.5.6

Please tell me who can I do that?
[Nexus 4 Android Development] Kubino:
From latest release of Sailfish for Nexus 4 (gamma 7) you can upgrade to 2.0.5.6 on your risk using this. Maybe it will be better upgrade first to 2.0.4.14 and then to 2.0.5.6.
[Nexus 4 Android Development] HAF-MED:
Hi;

Thanks very much for your help:)

I have upgrade first to 2.0.4.14 and then to 2.0.5.6

but camera don't work!
[Nexus 4 Android Development] Kubino:
on 2.0.5.6 GPS works (I tested today) and camera too on my N4.
[Nexus 4 Android Development] Kubino:
Now I know why camera doesn't work for you. In repo are new version of some packages from 30 November and I had previous version of these packages. Today I made update and get these packages from 30 November and camera doesn't work too. In Android-Sfdroid camera still works (but only taking a photo, video not).
[Nexus 4 Android Development] bolek1337:
Sorry about that. The packages used to be built against the latest stack, so might have started to build against 2.0.4 or 2.0.5. Some incompatibility might have sneaked in.

A new 2.0.5.6 image is just around the corner, so stay put :)
[Nexus 4 Android Development] HAF-MED:
keyboard predictions! on nexus 4 sailfish

Hi, Thanks very much

Please can you tell me who can I install: jolla-xt9 and jolla-xt9-cp

to have keyboard predictions!
[Nexus 4 Android Development] Kubino:
No need to apologize, it's my risk. I fix camera today with this older package of gstreamer1.0-droid (it's from this OnePlus X repo).

Downloaded the rpm file, pkcon remove gstreamer1.0-droid, devel-su rpm -i <package> and after reboot camera works again :).
[Nexus 4 Android Development] radbme:
Follow this for keyboard predictions. http://xdaforums.com/jolla-sailfish/general/nexus-5-jolla-store-fix-warehouse-t2912717
[Nexus 4 Android Development] HAF-MED:
Thanks very much for your help
[Nexus 4 Android Development] radbme:
I just went ahead and OTA'd to 2.0.5.6 for fun. Rolled back the rpm to get the camera to work and all is well. BUT I can't shutdown. No matter what I try to shutdown, the phone restarts. I'm at a loss. Anyone know what I can try?

Edit: after trying multiple times it finally stayed off. Weird.
[Nexus 4 Android Development] radbme:
Is GPS still a no-go in SFDroid?
[Nexus 4 Android Development] Kubino:
I think still no-go but I didn't test it. Why do you need it?
[Nexus 4 Android Development] radbme:
I'd like a navigation app.
[Nexus 4 Android Development] rinigus:
The work on SFDroid has stalled a bit, as far as I can see. For navigation, you could use Poor Maps. It's quite decent and while it does not have spoken instructions (yet) you could use several backends that should cover your navigational needs. Note that if you use older SFOS (2.0.2.x), you would have to install a bit older Poor Maps (see OpenRepos Poor Maps page and comments within).

Just don't forget to submit issues if you have any problems with it. That way you could help the development and make the navigation in SFOS better. Check whether anyone submitted it already in GitHub and use it if you have a new problem.
[Nexus 4 Android Development] radbme:
That app looks really nice. I'll give it a look soon. I wonder if it displays imperial distances.
[Nexus 4 Android Development] Kubino:
There is also MoNav.
[Nexus 4 Android Development] bolek1337:
gamma8 image

I uploaded a new 2.0.5.6-gamma8 image to

http://images.devaamo.fi/sfe/mako/gamma8/ - see installation and upgrade instructions at: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_mako

I did a limited amount of testing, but it seems to be running fine. Please report back if you find any regression errors.

This image is still based on the cm11 image.

sha256sum of the image:

2c611f9cd45d1978dce86ce2c2fe8b3b9ba0ecd2c7c52354a26c82cacb0dc9e5 sailfishos-mako-release-2.0.5.6-gamma8.zip
[Nexus 4 Android Development] Wolfsen:
First of all thank you very much for your work!

I installed the gamma8 image and want to restore the backup that I've made according to the description in Q&A 13. The problem is, I can't find the backup under Settings->System->Backup. I can't do a new backup either. It says that I do not have a cloud service account or there is no memory card.

Do I have to do something else beside putting the backup to $HOME and extracting it there?

Thank's in advance for your help!
[Nexus 4 Android Development] stejoo:
Massive thanks! I was really looking forward to it.

This is the first time I did the OTA. All went well.

I disabled some repositories as described in the wiki.

I have re-enabled my openrepos repositories using "ssu er <reponame>".

But 1 remains: the adaptation0 repo I disabled in the OTA process.

Should I enable that as well? Or was it meant to be (kept) disabled?

Thanks again :)
[Nexus 4 Android Development] ddaggebi:
Should we not use SFDroid in Gamma8?
[Nexus 4 Android Development] bolek1337:
I see no reason not to use it - unless you plan to use pure Sailfish and port your favourite apps to it, which is a good idea, too.

I am not sure what the problem there is, but if you backed up from a pre-2.0.2 device, then this may apply to you: https://together.jolla.com/question/136773/backup-restore-from-jolla1-to-c-not-work/

You can leave it disabled, since the 'dhd' repository is basically the same as adaptation0.
[Nexus 4 Android Development] Wolfsen:
Thanks for the link. It might be a problem, but it should be fixed since 2.0.4 (

).

I guess the problem has to do with the recognition of the emulated sdcard. I changed the ownership of /sdcard to nemo:nemo according to https://together.jolla.com/question/138603/wrong-premission-after-sd-card-formated-by-native-storage-app-to-ext4/ to make sure it has nothing to do with that, but the problem persists.

When I check the storage under settings->system->storage, it does not show the sdcard either.

For all of you using gamma8:

Does the sdcard show up?

Is it possible to make a backup?
[Nexus 4 Android Development] Nine-H:
hey guys, this thread is huge. I'm having a weird issue: my wifi works fine but mobile and bluetooth aren't.

I'm running CM13 as internal rom, and sailfish as a multirom secondary, I used the cm11 base rom and gamm8 to install, and then I added the radio.img from the 4.2.2 factory image from google (using multirom's "add radio.img" feature) because the list of radio.img files in the nexus 4 forum is completely out of date and most of them got scrubbed off their hosting sites.

I'm wondering if I got the radio wrong or what, I can get a dial tone on voice calls, but my phone won't detect my carrier settings for mobile data, it says it's on 3g not hsdpa. bluetooth is completely dead, but works fine in android.

Wifi is good. Great speed, stable connection, connects OK. Which AFAICT indicates that radio is working, but the other two don't want to come up at all.

The FAQ told me to copy radio.img to the sailfish root partition and edit a systemd config file to point to it, this has left me with an unbootable and (due to the way sailfish changes ssh and ip) unrecoverable sailfish partition, which I've reinstalled. Where specifically would be a "safe place on the root directory"?

Any insight would be great, because I haven't used sailfish since 1.x (didn't have any problems then) and they seem to have fixed all the UX things that used to annoy me. Pretty sure I've done something stupid but I'm not sure what.
[Nexus 4 Android Development] moriel5:
Since you are using CM11 as the base, I think that you would want the radio from 4.4.4?

You can simply download the Nexus 4's factory image from Google's developer page, and extract the radio from there.
[Nexus 4 Android Development] vetzki:
Dont use mulitorms add radio option

instead change /etc/systemd/system/local-fs.target.wants/firmware.mount

example:

[nemo@Sailfish ~]$ cat /etc/systemd/system/local-fs.target.wants/firmware.mount

[Unit]

Description=Droid mount for /firmware

Before=local-fs.target systemd-modules-load.service

[Mount]

#What=/dev/mmcblk0p1

What=/usr/local/etc/radio-mako-m9615a-cefwmazm-2.0.1700.98.img

# you can also use home directory

....

---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------

i've also a question regarding extra repo, instructions on https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_mako tell to disable it but not to enable it again, so I assume its not necessary for anything?
[Nexus 4 Android Development] stejoo:
The "extra" repository is empty on my device.

I just have the "home" and "adaptation0" repositories disabled for now.

Here's an overview of what I have at the moment, after the OTA and re-enabling of my openrepos repositories:

,---
| SailfishOS 2.0.5.6 (Haapajoki) (armv7hl)
'---
[nemo@Sailfish ~]$ ssu lr
Enabled repositories (global):
- apps ... https://releases.jolla.com/jolla-apps/2.0.5.6/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/2.0.5.6/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/2.0.5.6/jolla/armv7hl/

Enabled repositories (user):
- dhd ... http://repo.merproject.org/obs/nemo:/testing:/hw:/lge:/mako/sailfish_latest_armv7hl/
- mw ... http://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfish_latest_armv7hl/
- openrepos-Dax ... http://sailfish.openrepos.net/Dax/personal/main
- openrepos-MartinK ... http://sailfish.openrepos.net/MartinK/personal/main
- openrepos-Osanwe ... http://sailfish.openrepos.net/Osanwe/personal/main
- openrepos-ade ... http://sailfish.openrepos.net/ade/personal/main
- openrepos-basil ... http://sailfish.openrepos.net/basil/personal/main
- openrepos-llelectronics ... http://sailfish.openrepos.net/llelectronics/personal/main
- openrepos-otsaloma ... http://sailfish.openrepos.net/otsaloma/personal/main
- openrepos-ruedigergad ... http://sailfish.openrepos.net/ruedigergad/personal/main
- store ... https://store-repository.jolla.com/mako/armv7hl/?version=2.0.5.6

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
- home ... https://download.jollamobile.com/home:/honeybadger/latest_armv7hl/
- adaptation0 ... https://store-repository.jolla.com/releases/2.0.5.6/jolla-hw/adaptation-lge-mako/armv7hl/
- extra ...

Don't know if this is the way it should be, but it seems to be working alright.

I do get a "Updates available" notification in Warehouse, but nothing is listed... Haven't looked into figuring that one out yet (any tips?). Performed a reinstallation of Sailorgram by hand because it wasn't updating properly. But a removal and reinstall worked just fine.

I think I'm gonna try and see how to perform updates from the command line. Just like I used to on the Nokia N900 with Maemo. ;)
[Nexus 4 Android Development] vetzki:
thanks, completely missed that extra points to no url at all :o
[Nexus 4 Android Development] bolek1337:
I think you are mentioning the known-bug in this adaptation, see "Status" on https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_mako and question 16 in FAQ.
[Nexus 4 Android Development] vetzki:
Unfortunately, there is still a crackling sound when listening with headphones on very low volume (or muted), is there a way to fix this?

I noticed this issue also with a aosp android build but there it only occurs in lockscreen (not if device unlocked or in standby. also not if statusbar pulled down in lockscreen)
[Nexus 4 Android Development] retro486:
First off, thanks for keeping the N4 updated on Sailfish!

I'm trying to compile this locally myself and I can't seem to find a good combination of already working *_defconfig, mako.xml, and KS files to make sure my base environment is good. I see you uploaded your KS file but could you also post your *_defconfig and mako.xml files? I can't seem to get even the older mer-hybris mako repos to compile and the HADK PDF needs to be badly rewritten.

Thanks again!
[Nexus 4 Android Development] bolek1337:
Interesting find. But no, I've no solution for this at the moment.

mako.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako"
name="mer-hybris/android_device_lge_mako"
revision="hybris-11.0" />
<project path="kernel/google/msm"
name="mer-hybris/android_kernel_google_msm"
revision="hybris-11.0" />
<project path="rpm/"
name="mer-hybris/droid-hal-mako" revision="master" />
<project path="hybris/droid-configs"
name="mer-hybris/droid-config-mako" revision="master" />
<project path="hybris/droid-hal-version-mako"
name="mer-hybris/droid-hal-version-mako" revision="master" />
</manifest>

For *_defconfig, I guess you mean the kernel config as in:

https://github.com/mer-hybris/andro...b/hybris-11.0/arch/arm/configs/mako_defconfig
[Nexus 4 Android Development] retro486:
Hm so you're using the same files I am.... Alrighty. That stock defconfig gives me a lot of warnings and some errors I have to fix... You don't?
[Nexus 4 Android Development] bolek1337:
I don't remember warnings, but surely no errors. Do check your android tree download succeeded without interruptions. It's a common first thing that breaks. Also, I built the android components inside ubu-chroot, not in the sdk directly. Feel free to ping me on Freenode #sailfishos-porters for some specifics.
[Nexus 4 Android Development] Wolfsen:
Thanks for the hint! I tried to mount the SD card according to the description in question 16 in the FAQ but there is no

mmcblk0p28

in

/dev

:(

Everything with the emulated SD card worked without any problems in Gamma6 that I've used before.

Do you experience the same issue?

---------- Post added at 11:06 PM ---------- Previous post was at 10:54 PM ----------

[MENTION=4415714]radbme[/MENTION]: I've also tried to get the keyboard predictions and followed the description in the link you posted. The result of the command

pkcon install store-client jolla-xt9 jolla-xt9-cp

was: "... jolla-xt9 could not be found". Do you have an idea what I could do to solve the problem?
[Nexus 4 Android Development] radbme:
Hmm. That's odd. It should work. Are you using SSH to install or the on-device terminal app? Make sure you're not skipping steps. I'll try it out in a little bit to see if I can get it to duplicate.
[Nexus 4 Android Development] Wolfsen:
Hmm. That's odd. It should work. Are you using SSH to install or the on-device terminal app? Make sure you're not skipping steps. I'll try it out in a little bit to see if I can get it to duplicate.[/QUOTE]

Thank you for the very quick answer and your help!

I used the on-device terminal app. By repeating the whole process I just figured out that I missed some letters, I used

ssu dr adaption0

instead of

ssu dr adaptation0

. I repeated everything but still get the same error with the missing jolla-xt9 :(
[Nexus 4 Android Development] Kubino:
It is mmcblk0p23.
[Nexus 4 Android Development] Wolfsen:
[MENTION=2677317]Kubino[/MENTION]: Thanks, the mounting worked now. But I still face the problem with /sdcard not being recognized since the link to /storage/emulated/legacy can not be found, probably due to restricted access for user nemo. I do not use (and never did) Android or CM on my Nexus4, so there is no need to get access to Android-data collected before (at least this is what I understand when reading 16. in the FAQ. I just want to get the backup to work as in Gamma6, but that is still not possible due to /sdcard not being recognized by the system.

The chmod-settings are the same as in case of Gamma6:

lrwxrwxrwx root root /sdcard -> /storage/emulated/legacy

and for the linked location

lrwxrwxrwx root root /storage/emulated/legacy -> /mnt/shell/emulated/0

drwxrwx--x root sdcard_r /mnt/shell/emulated/0
[Nexus 4 Android Development] Kubino:
way to sdcard is /media/0/
[Nexus 4 Android Development] radbme:
I can confirm I'm having the same issue. I'm stumped. I'm about to reflash gamma 7.1 and see if it works in there. Perhaps the creator of this fine port can explain.

---------- Post added at 10:57 PM ---------- Previous post was at 10:23 PM ----------

I can confirm that code still works in gamma 7.1. As a workaround since I believe you've just flashed gamma 8, you could reflash cm11 and gamma 7.1, install the keyboard predictions and then OTA to gamma 8. It might be possible to flash gamma 8 over top too without wiping first if you want to try that but I'm not sure how successful that will be.
[Nexus 4 Android Development] radbme:
I can't leave well enough alone so I went ahead and tried a dirty flash of gamma 8. No good. It wipes all settings and deletes all files! I went ahead and tested the code anyway to get predictions and it still failed in the same spot. So I reflashed gamma 7.1 and the code worked fine. I'm not OTAing to 2.0.5.6 and I'll report back if predictions are still there. I have a feeling they are since this is how I got to the version myself the last time and drove it for a day or so. I would have noticed if they were missing. I'll let you know.

---------- Post added at 12:13 AM ---------- Previous post was at 12:00 AM ----------

Yep. OTA to 2.0.5.6 from gamma 7.1 with predictions installed worked fine. Fully updated and predictions are still there. It's a workaround but it works.
[Nexus 4 Android Development] Kubino:
I have some freezing when someone call me after last update. Black screen and I can only hold power button to shutdown (with wifi on I can ssh to phone from PC and kill lipstick solve it). After reboot it is ok for some time.
[Nexus 4 Android Development] Wolfsen:
I had the same issue with Gamma6 several times.
[Nexus 4 Android Development] rinigus:
I have seen it as well and it seems to me that Jolla has closed this backdoor for ported devices. We would probably have to develop an open-source solution for predictive keyboard. In long term, that's for a best... Just rather painful transition and, at present, I have heard only of one developer looking into it (a bit). See

https://together.jolla.com/question...-for-a-not-yet-officially-supported-language/
[Nexus 4 Android Development] radbme:
Well at least we know this isn't just for the N4 port. So for those curious, the solution to get keyboard predictions is to install Gamma 7.1, install warehouse and xt9, and then OTA for all future updates.
[Nexus 4 Android Development] slash.tux:
Gent, do you know where I can find an image of CM11 to install Sailfish ?
[Nexus 4 Android Development] radbme:
https://download.cyanogenmod.org/get/jenkins/90767/cm-11-20141115-SNAPSHOT-M12-mako.zip

OP, with the CM shutdown, the link on the wiki needs to be updated to this one.
[Nexus 4 Android Development] slash.tux:
Thanks for your amazing work, i can try Sailfish.

Regarding the bluetooth in the setting there is a msg : Bluetooth not avalaible.

Do you have an idea how to troubleshoot it ?

For the rest everything is fine, so far.

Thanks