maemo.org - Talk - SailfishOS 2.0 on Nexus 5

Page 15 of 21

« First

< Prev

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - SailfishOS 2.0 on Nexus 5 (https://talk.maemo.org/showthread.php?t=94620)

tolake

2016-03-03 18:23

Re: SailfishOS 2.0 on Nexus 5

One reboot later sensorfwd is alive. In Messwerk all except rotation-Z
are moving. So, same as it was in 2.0.0.10.

romu	2016-03-03 20:01

Re: SailfishOS 2.0 on Nexus 5

Problem with your procedure is the MD5 doesn't give the ROM version where it comes from. It would be great if you could fill in the Google Sheets with your results, and that would be even interesting as you're still in 2.0.0.10.

The archive given in my dropbox link provides you with all available sensor drivers plus some simple scripts to install and restore the drivers.

frullewulle

2016-03-03 21:39

Re: SailfishOS 2.0 on Nexus 5

@ romu: thanks for your zip file

I think there are more files involved in our problem:

build.prop in /system has sensor settings

there is a libsensor1.so, libsensor_reg.so and libsensor_user_cal.so in /system/vendor/lib

there is libsensorservice.so in /system/lib

for the google sheet; it would be good to have the version of cm on wich we installed sailfish on
in my case it is a bit confusion: i see KTU84Q and KTU84P in the build.prop file and also ro.cm.version=11-20141008-SNAPSHOT-M11-hammerhead

romu	2016-03-04 08:21

Re: SailfishOS 2.0 on Nexus 5

Same to me, KTU84P/Q, but if you try to "ls -al" those 2 folders, you'll see the sensors files have the exact same size, so I would bet they're the same.

Ok, let's downloads the packages again to isolate those additionnal files, let me few hours to do so.

I've added the CM version column to the Google Sheet.

frullewulle

2016-03-04 10:14

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by romu (Post 1500610)

I do notice a difference in cpu usage between 2 sensors.msm8974.so files with the same file size: what makes it even more difficult to retrieve which versions works well and which one not...

romu	2016-03-04 12:56

Re: SailfishOS 2.0 on Nexus 5

Done, the ZIP has been updated with the additionnal files. The installation/restoration have been updated as well. Time to run our testing!

romu	2016-03-04 15:56

Re: SailfishOS 2.0 on Nexus 5

Plain and simple : unable to start the sensorfwd service if the driver are newer than my underlying CM11 (KitKat).

m4r0v3r

2016-03-04 15:58

Re: SailfishOS 2.0 on Nexus 5

well those binaries were built for newer versions of android.

romu	2016-03-04 16:08

Re: SailfishOS 2.0 on Nexus 5

Yes, I know, tested just in case.

m4r0v3r

2016-03-04 16:14

Re: SailfishOS 2.0 on Nexus 5

I guess if an aosp6 rebase is successful maybe the situation improves. Only reason I attempted an aosp6 rebase is because I want better bluetooth. At the moment though things aren't going so well

RealJohnGalt

2016-03-04 19:19

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by m4r0v3r (Post 1500644)

I guess if an aosp6 rebase is successful maybe the situation improves. Only reason I attempted an aosp6 rebase is because I want better bluetooth. At the moment though things aren't going so well

When you say "better bluetooth," do you mean that you have working bluetooth audio with the cm11 base?

Edit: the sensor disparity is quite possibly related to bootloader version. When bootloader changes have broken blobs, z axis rotation has seemed (from my experiences) to have been the first to go. If you check strings or glance through leaked qcom vendor sources, you'll see that the differing blobs support the various hammerhead hardware.

romu	2016-03-05 10:29

Re: SailfishOS 2.0 on Nexus 5

Since yesterday, I run the sensors drivers from KOT49H (so older than the KTU84x based which are the ones in CM11) and they haven't crashed yet.

BluesLee

2016-03-05 11:30

Re: SailfishOS 2.0 on Nexus 5

You know about the general bug 820: sensors: random crashs?

KOT49H CPU consumption is too high, those of llelectronics work perfectly in Messwerk and CPU consumption is okay, but rotation stops working in lipstick, that's what i observe with 2.0.1.7.

romu	2016-03-05 14:54

Re: SailfishOS 2.0 on Nexus 5

Thanks for this information. So, I made some analysis and yes, the KOT49H driver eats too much CPU but not in the same way as does the KTU84x.

With the KTU84x (the CM original driver), the driver eats CPU when it crashes.

The KOT49H didn't crash during my testing (I've switched to the KRT16M to see how things are going). I saw it eating too much CPU, but only when the phone was awake. As long as the phone is asleep, the CPU consumption is far from being significant. So, imho, that could be an acceptable tradeoff, because my N5 is asleep most of the time.

I'm keeping the KRT16M for a moment.

m4r0v3r

2016-03-05 17:51

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by RealJohnGalt (Post 1500659)

basically headsets working with it. since they work with the Jolla phone but things go to **** on the N5

Jef91

2016-03-13 02:45

Re: SailfishOS 2.0 on Nexus 5

Anyone out there using the Nexus 5 with Sailfish on T-Mobile US and have MMS working? I've tried all the APN settings I can think of and none of them seem to allow me to send a picture message.

romu	2016-03-13 18:16

Re: SailfishOS 2.0 on Nexus 5

MMS doesn't work for me on the N5 in France.

Feathers McGraw

2016-03-13 20:55

Re: SailfishOS 2.0 on Nexus 5

I couldn't get MMS to work for me on the N5 in the UK, but I don't know if that's because I bought the US version of the phone my mistake, or because of something specific to the Hammerhead port, or because it just doesn't work at all on Sailfish.

In my experience, MMS is pretty flaky on Sailfish anyway - I can receive MMS messages on my Jolla phone, but not send them (EE, UK).

KylliOrvokki

2016-03-14 10:15

Re: SailfishOS 2.0 on Nexus 5

I have working MMS with Jolla phone and Oneplus One in Finland. And I think I had it also with Nexus5 when I had that phone (If I hopefully remember right).
So MMS's are working with at least Jolla and Oneplus One with Sailfish Port.

Do you have "Settings - Mobile network - MMS Access Point" visible in Nexus 5?

If yes -> I would say that there is just some configuration problem with towards your Network provider.

ps.
https://together.jolla.com/question/...us-to-improve/

abyzthomas

2016-03-14 12:20

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by Jef91 (Post 1501238)

Anyone out there using the Nexus 5 with Sailfish on T-Mobile US and have MMS working? I've tried all the APN settings I can think of and none of them seem to allow me to send a picture message.

It usually works if you switch to 2g. I think I got it working with 4g but I am not sure if it is working anymore.

Try the following setting:
Con name: T-Mobile MMS
apn: internet2.voicestream.com
proxy: 216.155.165.50
proxy port: 8080
mms message center: http://216.155.174.84/servlets/mms

Jef91

2016-03-14 16:24

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by abyzthomas (Post 1501313)

These APN settings work when I set my cell network to prefer 3g or 2g only. Does not set on 4g (LTE) which is fine I suppose. Thanks for the work around.

oenone

2016-03-16 14:56

Re: SailfishOS 2.0 on Nexus 5

What is the verdict on the sensors crashing bug and how best to fix it?

I have a bug that restarts the device every whenever (when not in use), which seems to keep the sensors working (although might be related), but ideally bugs would be quashed.

szymeczek34

2016-03-16 15:30

Re: SailfishOS 2.0 on Nexus 5

Hi, I was wondering if Sailfish on N5 has anything like Facebook Messenger with instant message notifications?
Also, is it possible to use it on a daily basis? I remember owning N4 a year ago and SFOS on it was not good enough. For simple stuff like browsing the net it was fine but making calls was a terrible experience.

Blackberry is now dropping Facebook support through their app which means no more Hub integration and since none of my friends text anymore I kinda don't see myself checking the website every now and then. For that I can simply go back to using my N9.
Thanks.

romu	2016-03-16 16:49

Re: SailfishOS 2.0 on Nexus 5

I use my N5 with SFOS on a daily basis...I don't use my Jolla phone anymore. But I think there is no Facebook Messenger even if they are some initiatives to reborn a FB application on Warehouse.

szymeczek34

2016-03-16 16:57

Re: SailfishOS 2.0 on Nexus 5

Do you experience many irritating inconvieneces during the day? Like screen not unlocking after a call or not being able to answer a call or sudden restarts?
Have you tried this?
https://openrepos.net/content/nodeve...senger-account
Seems like it might be the thing I need although when I used something similar on the N9 there was a huge battery drain caused by it.

Bundyo

2016-03-16 17:10

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by romu (Post 1501475)

I use my N5 with SFOS on a daily basis...I don't use my Jolla phone anymore. But I think there is no Facebook Messenger even if they are some initiatives to reborn a FB application on Warehouse.

There is a Facebook Messenger account plugin which does a rather good job.

romu	2016-03-16 19:53

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by szymeczek34 (Post 1501479)

Do you experience many irritating inconvieneces during the day? Like screen not unlocking after a call or not being able to answer a call or sudden restarts?

Restart ? Never.

The most annoying issue to me is the random crash of the sensor processes. It can occur 2 times in a week, or 2 times in a day...random. But with a single command in a terminal you can restart the service and get your sensors back. There is no workaround yet.

In the past year, I've got 4 or 5 lipstick crashes, in that case, you can't control the touchscreen, so you can't answer a call. Again, from a terminal through ssh, you can restart lipstick.

From time to time, when I receive a call, it fails and I hear the familiar sound which can be heard when there is a signal issue. But that's not often, and when it happens, the call appear on the phone, so I can call my peer back in seconds.

Quote:

Originally Posted by szymeczek34 (Post 1501479)

Have you tried this?

https://openrepos.net/content/nodeve...senger-account[/QUOTE]

Didn't know, thanks.

szymeczek34

2016-03-17 13:44

Re: SailfishOS 2.0 on Nexus 5

Thanks for all the feedback, I think I'm gonna buy one. Oh, just one more quick question: for Sailfish it doesn't matter whether I buy16 or 32GB version of the Nexus, right?

Feathers McGraw

2016-03-17 15:42

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by szymeczek34 (Post 1501551)

Thanks for all the feedback, I think I'm gonna buy one. Oh, just one more quick question: for Sailfish it doesn't matter whether I buy16 or 32GB version of the Nexus, right?

Either is fine. Make sure you get the right model/modem for your country!

szymeczek34

2016-03-17 16:43

Re: SailfishOS 2.0 on Nexus 5

Great, thanks!

m4r0v3r

2016-03-18 08:38

Re: SailfishOS 2.0 on Nexus 5

for people who have multirom and want music both on android and sfos, have the music on android and use the new tracker location patcj to add the android folder and reboot

RealJohnGalt

2016-03-18 10:08

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by szymeczek34 (Post 1501465)

Aside from the sensors issue (which is more of an minor annoyance with the llelectronics script), the only other issue would be the bluetooth issue. It will fail within a few minutes of audio, and require a reboot to enable (so unusable).

Feathers McGraw

2016-03-18 16:55

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by RealJohnGalt (Post 1501611)

True, this prevents using smartwatches too.

szymeczek34

2016-03-18 20:24

Re: SailfishOS 2.0 on Nexus 5

That's a bummer, anyway, thanks guys a lot!
I'm also considerating OnePlus X, it's not much more expensive than a used Nexus 5. Has anyone had any experience with that cell? It looks quite good on paper, Sailfish is said to be working well with the exception of camera and most of all it's brand new.

DJJonosound

2016-03-19 08:42

Re: SailfishOS 2.0 on Nexus 5

Quote:

Originally Posted by szymeczek34 (Post 1501645)

I own a oneplus x in white at the moment. The only issues are that for me on OxygenOS video playback stutters and is just generally bad, and also its still on 5.1.1 which sucks, as I would love to get 6. (Haven't used a custom rom because oxygen has a great amoled theme) Also patchy LTE from what I have heard (lack of bands), but I'm not fussed as my phone plan doesn't support LTE and I really don't need it.

Apart from that, the build quality is sublime, the screen has really good colour, and in general its pretty well rounded. The omission of features like NFC is a bit annoying but I can live without (I do miss mobile payments though) The build and design are the main reasons I bought it, its top stuff.

romu	2016-03-21 16:48

Re: SailfishOS 2.0 on Nexus 5

Hi,
I've recently seen than when the sensors driver crashes, it may eats too much CPU (we all know that) but the process may also be shutdown for good. So, I've modified the watchdog script to restart the service if no sensor process is found. I'm far from being a bash expert, feel free to correct me if I did something wrong.

Code:

#!/bin/bash

 

# This checks every 1/2 minute and kills if

# sensors.qcom process is eating more than 8% CPU for 1 minute

 

TERM=linux

export TERM

 

kill_count=0

 

while true; do

  sensors_pid=$(ps aux | grep sensors.qcom | grep -v grep | awk '{print $2}')

  

  # If the process has crashed it may not be running,

  # so we restart it

  if [ -z $sensors_pid ]; then

    systemctl restart sensorfwd

  else

    cpu_usage=$(top -b -p $sensors_pid -n1 | grep $sensors_pid | awk '{print $9}') 

    echo $cpu_usage

    echo "CPU Usage of sensors.qcom: ${cpu_usage/.*}"

    if [[ ${cpu_usage/.*} -ge 8 ]]; then

            if [[ $kill_count -ge 1 ]]; then

                    echo "CPU Usage of sensors.qcom too high restarting..."

                    systemctl restart sensorfwd

                    kill_count=0

            else

                    echo "CPU Usage of sensors.qcom too high! Setting kill_count + 1"

                    kill_count=$((kill_count+1))

            fi

    else

            echo "Nothing to do"

    fi

  fi  

  sleep 30

done

romu	2016-03-23 12:02

Re: SailfishOS 2.0 on Nexus 5

This script is buggy. Just experienced a sensor crash. As a result:

sensors.qcom processes was still active and ate about 0% of CPU
sensorfwd process was not running

I tweaked the script to monitor sensorfwd instead of sensors.qcom. And I'll see how things are going.

Code:

#!/bin/bash

 

# This checks every 1/2 minute and kills if

# sensorfwd process is eating more than 8% CPU for 1 minute

 

TERM=linux

export TERM

 

kill_count=0

 

while true; do

  sensors_pid=$(ps aux | grep sensorfwd | grep -v grep | awk '{print $2}')

  

  # If the process has crashed it may not be running,

  # so we restart it

  if [ -z $sensors_pid ]; then

    systemctl restart sensorfwd

  else

    cpu_usage=$(top -b -p $sensors_pid -n1 | grep $sensors_pid | awk '{print $9}') 

    echo $cpu_usage

    echo "CPU Usage of sensorfwd: ${cpu_usage/.*}"

    if [[ ${cpu_usage/.*} -ge 8 ]]; then

            if [[ $kill_count -ge 1 ]]; then

                    echo "CPU Usage of sensorfwd too high restarting..."

                    systemctl restart sensorfwd

                    kill_count=0

            else

                    echo "CPU Usage of sensorfwd too high! Setting kill_count + 1"

                    kill_count=$((kill_count+1))

            fi

    else

            echo "Nothing to do"

    fi

  fi  

  sleep 30

done

romu	2016-03-25 09:22

Re: SailfishOS 2.0 on Nexus 5

I'm feeling a bit alone on this thread :D

The watchdog script has a problem, but this may come from the way it is setup on my N5.

The .sh file is in my /home/nemo folder. The watchdog service file has been added to systemd and stands in /lib/systemd/system.

The issue is the watchdog doesn't work if you don't unlock the phone. This morning, I saw the sensors framework was crashed. And once I unlocked the phone, the watchdog did its work as expected.

Is there any way to get this to work even if the phone is locked?

m4r0v3r

2016-03-25 13:13

Re: SailfishOS 2.0 on Nexus 5

could be due to wakelocks?

romu	2016-03-25 15:04

Re: SailfishOS 2.0 on Nexus 5

What's wakelocks?

All times are GMT. The time now is 16:26.

Page 15 of 21

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8