maemo.org - Talk
Page 51 of 84 « First 414950 51 525361 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)

nh1402 2016-02-23 10:49
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Originally Posted by m4r0v3r (Post 1499569)
if this issue has been fixed maybe its time to look at a cm12 port to see if the drivers have improved at all.
why not cm13 as base? (mainly for sfdroid)

boebbele 2016-02-23 11:19
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Originally Posted by RealJohnGalt (Post 1499554)
I recommend terminal or ssh paired with "devel-su cp -f SENSOR_SO_LOCATION /vendor/lib/hw/"
Dont work for me! "only readable filesystem"

jellyroll 2016-02-23 12:22
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Originally Posted by boebbele (Post 1499572)
Dont work for me! "only readable filesystem"
Move the file to /android/media/0/ start sfdroid and copy it from /android/media/0/ to /vendor/lib/hw/ by using a root file explorer.

boebbele 2016-02-23 14:04
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Originally Posted by jellyroll (Post 1499580)
Move the file to /android/media/0/ start sfdroid and copy it from /android/media/0/ to /vendor/lib/hw/ by using a root file explorer.
It works! Thank you!

JohnHughes 2016-02-23 17:40
Re: SailfishOS 2.0 on Nexus 5
 
Overly complex bit of script:

Code:
sensors_pid=$(ps aux | grep sensors.qcom | grep -v grep | awk '{print $2}')
Could just do
Code:
sensors_pid=$(ps ax | awk '/sensors.qcom$/{print $1}')
And, of course,
Code:
cpu_usage=$(top -b -p $sensors_pid -n1 | grep $sensors_pid | awk '{print $9}')
Could be
Code:
cpu_usage=$(top -b -p $sensors_pid -n1 | awk  -v pid=$sensors_pid '$1 == pid {print $9}')
(edited to get rid of more excess grep's)

frullewulle 2016-02-23 17:45
Re: SailfishOS 2.0 on Nexus 5
 
even with a better blob, after a while, i still see a bigger memory usage of sensors.qcom
even more then 12 Mb after a day, and we start with 8 à 900 kb

so still a memory hole somewhere.

i was thinking to try with mixed sensors solution as mentioned in SailfishOS-HardwareAdaptationDevelopmentKit-1.1.1 chapter 13.9

https://github.com/mer-packages/sens...nsord-tbj.conf

llelectronics 2016-02-23 18:28
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Overly complex bit of script:
...
I don't want to start a flamewar or discussion about programming styles.
But in general grep is faster than awk most of the times :)


Quote:
even with a better blob, after a while, i still see a bigger memory usage of sensors.qcom
even more then 12 Mb after a day, and we start with 8 à 900 kb
Yeah I also noticed that it is using quite some RAM.
Lets see if it will stop rising or not or if there is another solution.
(There are several threads for Android about sensors.qcom memory usage)

Quote:
i was thinking to try with mixed sensors solution as mentioned in SailfishOS-HardwareAdaptationDevelopmentKit-1.1.1 chapter 13.9
Sounds interesting. Keep us updated on this.

m4r0v3r 2016-02-23 23:24
Re: SailfishOS 2.0 on Nexus 5
 
Quote:
Originally Posted by nh1402 (Post 1499570)
why not cm13 as base? (mainly for sfdroid)
weve already spoken about this, am ghosalmartin, ill probably be taking a look this weekend

romu 2016-02-25 08:13
Re: SailfishOS 2.0 on Nexus 5
 
Hi,
I've a problem with the watchdog script. Yesterday night, my sensors were obviously crashed. I checked the systemd service and it was running.

So, I see some possibilities:
  • I did a bad watchdog service setup
  • The watchdog script is buggy
  • The sensors framework can crash without actually eating enough CPU to trigger the watchdog

Any idea?

llelectronics 2016-02-25 11:10
Re: SailfishOS 2.0 on Nexus 5
 
Did you start messwerk to see if it was still showing something for accelerometer or orientation? Maybe it was the effect I described before where lipstick lost orientation sensor capability.

Anyhow I advise everyone to stop using watchdog and just replace the sensors so file like described in my post.
It works way better this way and running it for a couple of days I can clearly see an improved battery life.
The memory leak thing is a minor issue in my opinion as it is not always doing it. I have a memory usage about 3 MB for 2 days already so its not even an issue always.
I did not managed to track when and why the menory usage grows yet.


All times are GMT. The time now is 07:37.
Page 51 of 84 « First 414950 51 525361 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8