yashsingh1/xdaforums huggingface dataset:
[OnePlus X Android Development] rinigus:
2.1.3.7/beta-6 testing

We have pushed 2.1.3.7/beta-6 images and updated packages yesterday at OBS for OTA. Please note that there has been rather limited testing of them (mainly checked few things after flashing and performed OTA as well).

So, at this stage, I would propose it for testing by the ones that are ready to

* report the issues (on the top of known issues on beta-6 release);

* know how to get back to earlier version if they have to;

* accept that it may lead to downtime.

Both testings are welcome - OTA and clear image flashing. So, choose your normal route for the update.

For those, who did OTA already, I would suggest to make it again (2.1.3.7->2.1.3.7). I would expect that the updated patterns will be picked up at this case too.

In my case, I haven't seen anything alarming so far and all seems to work as it should. [MENTION=1082346]kimmoli[/MENTION] was planning to test later tonight, but plans may change or may have to be changed.
[OnePlus X Android Development] klinglerware:
It worked fine with a clean flash. So far so good, though I did not test with a sim card.
[OnePlus X Android Development] kaulian:
I have just redone an upgrade from 2.1.3.7 to the new 2.1.3.7 :)

Everything is OK (It's my main phone)

Not bug discover

One big enhancement is no more freeze in Browser.

BIG BIG thanks to [MENTION=7078096]rinigus[/MENTION] and [MENTION=1082346]kimmoli[/MENTION] for the update
[OnePlus X Android Development] John944S2:
Also from me very big thanks to [MENTION=7078096]rinigus[/MENTION] and [MENTION=1082346]kimmoli[/MENTION] for this update:good:! I am going to flash and test it soon.

How about Bluetooth Low Energy, do you have any news about that for onyx?
[OnePlus X Android Development] rinigus:
There are no updates regarding BLE for onyx/SFOS. I think, if you want it to happen, you would have to work on it yourself. I mainly use BT in a car, but together with enabled GPS and display on for navigation, I don't think BLE will make my battery consumption go away. However, if you do own BLE devices then you may have a good reason to look into it.
[OnePlus X Android Development] rinigus:
Since there have been no complaints by those who updated to 2.1.3.7, everyone is welcome to do so.
[OnePlus X Android Development] Kermit13:
than I will start to do so...;) the notification LED isn 't working when getting new telegram messages, SMS are not coming or

very late.
[OnePlus X Android Development] elvarr:
rinigus, hello!

Does not work:

1) Led

2) Me am very, very badly heard in a speakerphone.

3) And also:
[OnePlus X Android Development] rinigus:
Re LED: I can confirm more moody behavior of LED. I am also missing LED notification on new email. On charging, it takes time before it shows up.

Re SMS: when sending SMS from other phone, I've got SMS immediately. So, for me, it works as before and there are no issues.

---------- Post added at 22:49 ---------- Previous post was at 22:42 ----------

Re LED, see message before. I also opened an issue at https://github.com/kimmoli/sfos-onyx-issues/issues/51

Re badly heard. Check and test different settings using getprop/setprop. See discussion on some settings at https://github.com/kimmoli/sfos-onyx-issues/issues/2 ; I am still using the settings that I found for myself on normal calls. Don't use speakerphone, though.

Where are the files that you propose to change coming from? What is the difference between them and the ones that we have from CM12.1?
[OnePlus X Android Development] Kermit13:
maybe the SMS stuff is provider related, will be hard to find out...but in this times not such important.

In the beginning of this port I also played with setprop / getprop and the voice quality is pretty good.. no need to change anything.

What I recognized is that when using the speaker on a call now I always have to increase the volume, isn 't

saved from the last call.

In summery the port is still great, also having the feeling that battery consumption is better than before. Since the last update,

two days ago, I am on 70 % now :good:
[OnePlus X Android Development] elvarr:
Spoiler(-) (Different)

The attached file Speaker+Fix+CM12.1.zip ( 251,44 KB )

(description of the fix) --

https://translate.yandex.ru/web?url=http://4pda.ru/forum/index.php?showtopic=711207&lang=ru-en

Message #89 --

https://translate.yandex.ru/web?url=http://4pda.ru/forum/index.php?showtopic=711207&st=80&lang=ru-en

Checked: lfc222222, cvp.
[OnePlus X Android Development] rinigus:
Changes in the base are relatively difficult. It has to be also warranted. Was the speakerphone fine before 2.1.3.7? Do you have the same issue in CM12.1 which is used as a current base? The links that you posted are not really giving any details of the fix, nor the source code.
[OnePlus X Android Development] elvarr:
On images 2.1.0.11 there were problems with speakerphone (echo, volume up, down not work). Problems solved after using Speaker+Fix+CM12.1.zip.

On 2.1.3.7, this does not work. In normal mode and in speakerphone, I can not adjust through volume up, down. I updated via OTA.

But this is a trusted site.
[OnePlus X Android Development] rinigus:
[MENTION=7323498]elvarr[/MENTION], does this fix help after OTA as well? Or not anymore, if I understood correctly. I am starting to work on the next update and then see if we still have the issues with speakerphone. It is difficult for us to push anything into the parts which are occupied by base. I am not sure we are intended to do so. Hence, for us, it will be difficult to apply such fix.

Has anyone tested speakerphone using CM12.1 base that we use? Do you have the same issues in Android CM12.1 from our base?
[OnePlus X Android Development] elvarr:
rinigus, became worse after 2.1.3.7...:(
[OnePlus X Android Development] John944S2:
Hi everyone,

I did some tests after a clean install:

- SMS all good, no problems

- no LED

- volume on phone calls through handset ear speaker: is adjustable and works fine

- volume on phone calls through internal loudspeaker: seems to be locked to loudest volume

- voice call sound quality is good on both ends

Overall quality of the port is still very good so many thanks again!
[OnePlus X Android Development] rinigus:
[MENTION=7323498]elvarr[/MENTION], this is actually good news! If I managed to make it worse, there is a chance I can revert it in future :). It may take some time, though.
[OnePlus X Android Development] paulivil:
Heads Up! SurfaceFlinger for sfdroid needed

This may only concern those who would like sfdroid running on onyx. There is now a new library in the droidmedia middleware called libminisf.so and it needs to be added to droidmedia.rpm. Helpers are already updated to pack it in, it just needs to be built from updated sources. I don't know the proper way to patch the sources with the AudioPolicyService patch needed by onyx. droidmedia-0.20180315.1 has the required source file but needs to be patched, I guess. Update: I see this will be covered in the next release. libhybris-libGLESv1 is needed for sfdroid_renderer. Either that or sfdroid implementation needs to be updated, I guess.
[OnePlus X Android Development] bitwelder:
Great to see some activity on the OPX! Thanks to everyone who's working on it.

So, should I be able to see an OTA update available for my device with 2.1.0.11, or not yet?
[OnePlus X Android Development] rinigus:
you will not see update as such, you have to perform it yourself via commands in terminal. see instructions with the release for the commands.

as for status: testing 2.1.4.14 now; led/act dead fixed; speaker phone calls not. (minisf is in)
[OnePlus X Android Development] Kermit13:
when you go forward with that speed we have sailfish 3 before Jolla ;)
[OnePlus X Android Development] rinigus:
Reporting bugs, discussing features, PMs

Please refrain from sending me or other developers personal messages (PMs). If you want to suggest a feature, fix something, report a bug, PM is not for that. With the respect of PMs, I don't think that onyx port warrants any. The only good use for PMs I have seen was related to non-disclosing personal information when asking to fix address lookup in maps software. Even then, a public issue is filed first and personal details were sent separately.

For onyx, I haven't seen any use of PMs. Your messages are of greater use if they go to public forum and can become common knowledge.

Please note that, unless I find that this PM was justified due to personal info disclosure and that info was vital, I am going to ignore PMs from now on.
[OnePlus X Android Development] elvarr:
Hello, rinigus!

I have found orginal Speaker+Fix+CM12.1.zip. He is established through twrp-->install.

If you have time, check please on basic CyanogenMod 12.1-20160201 (on the Android).

The camera works very well on 2.1.3.7. I have rebooted 10 times and everything is normal with camera.

Thanks!
[OnePlus X Android Development] rinigus:
Together with kimmoli, we checked just plain CM this weekend and found that you cannot adjust call volume in speaker phone mode nor normal call mode. So, SFOS is a bit better now - normal call volume can be adjusted.

While you found the original ZIP, I wonder whether you managed to find original source code for this fix? GitHub repo, patches, ...?

As for whether to include it into some base fixes into SFOS distribution - I, personally, am not very motivated to include them. I am happy that such fix exists and its maybe up to users to decide if they want to install it. If its conveniently packaged into ZIP, even better.
[OnePlus X Android Development] elvarr:
Thanks for answering!

I did not find the source code :(.

I am glad that you managed to establish "normal call volume ..."! Speakerphone (Speaker+Fix+CM12.1.zip) depends on him.
[OnePlus X Android Development] adhit_barker:
Is android apps support for this OS?
[OnePlus X Android Development] smatkovi:
yes and no, you can install sfdroid but then calls don't work anymore....

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

does any of you use isodrive? for me it isn't working and i also didn't manage to compile it on the device itself

---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------

i just installed the keyboard-layouts via terminal and it worked fine
[OnePlus X Android Development] elvarr:
rinigus, I read on github - https://github.com/kimmoli/sfos-onyx-issues/issues/52

Same thing with me:

getprop | grep "audio\|mic\|speaker"

[ro.qc.sdk.audio.ssr]: [false]

[ro.qc.sdk.audio.fluencetype]: [fluence]

[init.svc.audiod]: [running]

[audio.offload.buffer.size.kb]: [32]

[audio.offload.gapless.enabled]: [false]

[tunnel.audio.encode]: [false]

[persist.audio.fluence.mode]: [endfire]

[persist.audio.fluence.speaker]: [false]

[persist.audio.fluence.voicerec]: [false]

[persist.audio.fluence.voicecall]: [true]

[persist.audio.DiracEnable]: [true]

[persist.audio.DiracHeadset]: [2]

[persist.speaker.prot.enable]: [false]

I deleted everything from:

/data/property/

/home/nemo/.config/pulse/

Rebooted and nothing.

I removed everything, flashed 2.1.0.11 -> 2.1.3.7 -> speaker-fix.zip.

And now, everything works with volume of voicecall in speakerphone mode, in normal mode.
[OnePlus X Android Development] rinigus:
I have added our findings as a comment to that issue. Would you mind adding your findings as well. Also, please state that we don't have sources for speaker-fix.zip.
[OnePlus X Android Development] nfs22:
Dear X Users and Devs,

I'm really happy to see that their is still live in this port. The new version is quite stable and to me it seems that the battery life increased a lot. Did you have the same experience about battery lifetime? I'm also happy to hear that the LED notifications seems to work again in the next release. But then there is light usually there is also shadow and i want to ask all of you if you face the same problem as I do, it's about sending and receiving text messages (SMS) and happend also in the previous version. It happens really often that i receive Messages hours after they have been send or in worst case they don't arrive until i do a complete restart. Also when i send Messages they stay often marked as "Sending" some of my friends say they received my messages but i never can be sure if it has been send successfully or not. So i need to restart again and again and again :/ As this is really annoying i start to look a bit around and installed the ofono app to get more detailed logs about the transmission. If I send a message that stay in state "sending" there appears no log entry at all so I think that the problem is located in the messaging app / framework. So i want to ask you if someone knows if it's possible to restart the app / framework without doing a complete restart and how to help to debug (maybe generate more detailed logs) or work around this problem. Another problem since the update is that all mp3 streams in all apps (allradio , sailwave, native jolla player) have glitches (they stuck for a millisecond) do you also experience that?

Thanks to all who are working on the port and also the users how trust in this port and the devs.

Best regards

André
[OnePlus X Android Development] Kermit13:
glad that I am not the only one with the "sms" problem ;)

What I recognized too is that the main camera stops working after some time, only a reboot is helping then.

The battery lifetime is really incredible :good:
[OnePlus X Android Development] Giridhararaju.R:
Try installing another SMS app and see if the problem persists.

I use SMS Organiser by Microsoft, I'm using LOS 15.1 though.
[OnePlus X Android Development] elvarr:
Kermit13, how to restart camera.

ps aux | grep camera
camera 965 0.0 0.4 something there still...
devel-su kill -9 965

Thanks, cvp!
[OnePlus X Android Development] Aviver:
Can you guys help me?

Which version of Twrp do you use and which version of CM 12.1 do you use to flash this rom.
[OnePlus X Android Development] Kermit13:
have a look in here https://sailfishmods.de/2016/07/oneplus-x-sailfish-os-installieren/
[OnePlus X Android Development] rinigus:
2.1.4.14 release [beta7]

2.1.4.14 is released (OTA and image are available). It fixes few bugs introduced in the previous release (LED, act dead), moves to backported bluetooth drivers and bluez5. Don't know whether it brings BLE, but users are encouraged to check it out. As for updated bluetooth, now, on my setup, I can call multiple times using a headset or hands-free system in a car without a need for disconnect. As a known bug, bluetooth connection to the car system doesn't sync contacts and you get just a number without the callers name. Hopefully, it will be resolved in future releases.

As always, for the cautious ones, wait few days and see if there are any major complains regarding the update. I have been running it for some time, but its always possible to miss some bug.

Before update, check the known issues with OTA description. The ones who update early are encouraged to report their findings.
[OnePlus X Android Development] John944S2:
Flashed it and got BLE scanner app from openrepos finding BLE devices. Also requesting services does work! Will start on adding BLE support for heart rate devices for my app Laufhelden now.

Rinigus you really made it, donation under way :good::good::good:
[OnePlus X Android Development] rinigus:
Great to hear that BLE works, thanks for reporting it!
[OnePlus X Android Development] nfs22:
Dear all,

yesterday i did OTA Update to 2.1.4.14 and it did it's job without any issues and everything works fine right now. Due to the upgrade warehouse and storeman (< v0.16) are uninstalled, as they do not work with the new release, so don't wonder if some apps are missing as i did. Bluetooth is working nice with my pebble round watch (not working with BLE) and also with the Jamo DS7 Sound System (Bluetooth 4.0), my JBL GO (Bluetooth 4.1) is not working and breaks Bluetooth until a complete restart. After the JBL GO was connected i wasn't able to deactivate Bluetooth and while shutting down the phone it didn't power off (stayed powered on with red led). i would like to help figure out the Problem if someone tell me where to look for more details.

Best regards
[OnePlus X Android Development] adhit_barker:
Do someone have instal alian dalvik on OPX? https://mega.nz/#!hAdSkD7A!3vyN3hYnJyU-7uybIlgnsgL43VxTt3dQIiJxRDVsC0c
[OnePlus X Android Development] rinigus:
Hi! I wonder if all got updated. Try to run zypper se bluez and check out that only bluez5 packages are installed, no bluez4 ones. You may also try to delete all old BT connections and establish them as new ones. Let me know if it helped
[OnePlus X Android Development] nfs22:
Hey Rinigus,

there are only bluez5 packages installed. All paired devices had been disappeared after the update. I'm very happy that you spend your time on keeping the port alive so the bluetooth problem is not a big thing i can connect the speaker by cable. I just want to do my part by helping debugging the glorious SF on our beloved Onyx :)

André
[OnePlus X Android Development] smatkovi:
i just tried under 2.1.3.7, it appears in the settings, but aliendalvik won't start, maybe i have a broken sfos, i tampered with some qt-system-files while trying to compile something
[OnePlus X Android Development] rinigus:
Keep aliendalvik discussion out of here. Its illegal to install it on OPX and it has nothing to do with this port.

---------- Post added at 08:58 ---------- Previous post was at 08:51 ----------

OK, so some trivial fixing didn't work :).

bluez5 is rather new effort on ported devices and maybe its some general problem. So, its great that you want to debug it and its only through such constructive feedback we can make it better.

Let's look into it a bit more. In terminal, please acquire the logs using

devel-su
journalctl -f > bt.fails.log

and then try to pair with BT device that doesn't work. Then you could look into that log, delete all personal info (such as MAC/IMEI or similar) and post it. One way to post the log is to use one of many pastebin-like services.
[OnePlus X Android Development] bitwelder:
I have updated to 2.1.4.14 and it seems to work quite OK. THANKS!

One question though (that I wanted to ask already since a while): what's the status of the battery indicator? At least on my OPX I find it pretty much unreliable, even with this latest build.

Often it sits at a pretty high charge % for a long time, only to jump unexpectedly to a low value some hours later.

How is it on your devices?
[OnePlus X Android Development] Kermit13:
I can't confirm this. The battery indicator goes linear down depending on usuage.

Since last update have to charge it only every third day :) but I don't play the whole day with the phone...
[OnePlus X Android Development] kaulian:
same issue with my phone, it is more often since last update
[OnePlus X Android Development] rinigus:
If I am not mistaken, it could be also wearing of the battery. Now, to check whether its SFOS issue or the hardware one, I would suggest:

* backup your SFOS installation in TWRP, preferably to SD card

* flash CM that we use as a base

* run on that android for few days and check if you see the same battery issue or not

* report your findings

* restore SFOS from backup

There maybe less painful ways to do it, but I am not aware of it

PS: On my device, it runs rather predictably, without major jumps. Although, it maybe your description fits https://github.com/kimmoli/sfos-onyx-issues/issues/4
[OnePlus X Android Development] bitwelder:
First of all, thanks for all the comments.

Before trying any reflashing, etc. I did a test regarding battery charging, and I wasn't much pleased by the results.

I turned off the phone (while battery was already 90%) and plugged it to a charger with a USB meter, to measure the current draw for the device.

Charge started at ~1000-1200 mA, which shortly reduced to ~500 mA (which looks quite normal to me).

However, a few hours later, when the device should have been fully charged already (as also confirmed by the 99%/100% screen) the phone was still taking 200-250 mA from the charger, and the top of the phone was getting mildly warmer than the rest. I would have expected that the device would have cut off the charger when charge was complete.

That confirms my previous experience with this phone that if left to the charger it doesn't seem to turn off the charge phase, and depending where the device dissipates that excess charge, that may have worn off the battery.

Question is, where the battery management comes from, is it Sailfish code or is it part of OnePlus f/w ?
[OnePlus X Android Development] rinigus:
Interesting data, thanks for doing it. I don't know which part of the stack is responsible for cutting off the charger (1+ FW/CM 12.1/SFOS). I would suggest to join IRC #sailfishos-porters on freenode.net, explain the issue in few sentences and link to your post. Then wait patiently for reply. If there is no reply in 24h, try again (you can always ping me and kimmoli on IRC). There are porters who have been working on ports for years and I would expect someone would be able to help us out.
[OnePlus X Android Development] winesh:
Correct me if I'm wrong, but I thought that the last charging 10% of an android devices always isn't normative. Because of the constant fueling and decreasing of the charge, to prevent damage being done on a lithium battery. A lithium battery has limited charge cycles, android counter this by playing with this cycle in a way that a full cycle isn't actualle full.
[OnePlus X Android Development] wolneykien:
This Package is for device: ONE; this device is OnePlus

Hi there,

I'm just trying to install the Sailfish OS (onyx, beta 7) on an OnePlus X phone (E1003, Onyx, 16GB). For both CyanogenMod (12.1, latest) and Sailfish OS itself I've got that very same error: "This package is for device: ONE; this device is OnePlus". I'm using the latest available TWRP recovery.

I've already tried to modify the `META-INF/com/google/android/updater-script` making it check for the OnePlus device string. The CyanogenMod first seemed to install properly, but it doesn't boots.

What kind of a problem it could be? Is it really a wrong device? But it looks like OnePlus X as far as google images shows that. And another thing: TWRP is twrp-3.2.1-0-onyx.img and it works.

And what does it mean: "I was on new BL" above?

Thanks in advance!

Paul.
[OnePlus X Android Development] Kermit13:
you still have the wrong bootloader, I had the same problem.

I can have a look tonight if I can find the right one on my laptop.
[OnePlus X Android Development] wolneykien:
Okay, that would be nice.

And I've just realized that I should start wit a STOCK OnePlus X image as the Sailfish Hardware Adaptation Gide says. Probably, that should be the step number 0 at Adaptations/libhybris/Install_SailfishOS_for_onyx. (Sorry, I can't post URLs here yet).
[OnePlus X Android Development] Kermit13:
another short feedback, today I was able to use the first time BT with my parrot car kit. :o

Had to use it a couple of times.... stable connection, good voice quality

Good job :good:
[OnePlus X Android Development] John944S2:
Sailfish bootlogo

Hi everyone,

I created a SFOS bootlogo for the Oneplus X. You can just install it with twrp.

The design is very basic, if someone has a better one I can create a new logo.

See here
[OnePlus X Android Development] elvarr:
rinigus, I have found how to receive a working compass.

1) changed gps.conf

2)

ln -s /system/etc/selective-spn-conf.xml /etc/selective-spn-conf.xml
ln -s /system/etc/sensor_def_qcomdev.conf /etc/sensor_def_qcomdev.conf

It can be all without value.

Then after reset, as before, freezings of a compass after 15-60 seconds.

Restarted and has started AIDA64-->Sensors... I have checked gpsinfo. And everything works. Have switched off AIDA64 and compass has stopped in gpsinfo. Restart gpsinfo and compass stopped. As you have already understood, AIDA64 helps. Guys, check, please.
[OnePlus X Android Development] XqepX:
How usable is this ROM for a basic daily usage?

(WhatsApp, Browsing, YouTube, Music)