Active Topics

 


Reply
Thread Tools
Posts: 288 | Thanked: 1,103 times | Joined on Jul 2014
#501
Originally Posted by m4r0v3r View Post
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)
 
Posts: 16 | Thanked: 2 times | Joined on Feb 2015
#502
Originally Posted by RealJohnGalt View Post
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's Avatar
Posts: 435 | Thanked: 684 times | Joined on Apr 2012 @ Netherlands 020
#503
Originally Posted by boebbele View Post
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.
 

The Following User Says Thank You to jellyroll For This Useful Post:
Posts: 16 | Thanked: 2 times | Joined on Feb 2015
#504
Originally Posted by jellyroll View Post
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!
 
Posts: 89 | Thanked: 194 times | Joined on Feb 2010
#505
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)

Last edited by JohnHughes; 2016-02-23 at 17:48.
 
Posts: 69 | Thanked: 85 times | Joined on Mar 2013
#506
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
 
Posts: 426 | Thanked: 1,812 times | Joined on Dec 2013
#507
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


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)

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.
__________________
Donation for my sailfish apps via PayPal

Donate using Liberapay
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#508
Originally Posted by nh1402 View Post
why not cm13 as base? (mainly for sfdroid)
weve already spoken about this, am ghosalmartin, ill probably be taking a look this weekend
 

The Following 2 Users Say Thank You to m4r0v3r For This Useful Post:
Posts: 602 | Thanked: 735 times | Joined on Mar 2011 @ Nantes, France
#509
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?

Last edited by romu; 2016-02-25 at 08:21.
 
Posts: 426 | Thanked: 1,812 times | Joined on Dec 2013
#510
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.
__________________
Donation for my sailfish apps via PayPal

Donate using Liberapay
 
Reply


 
Forum Jump


All times are GMT. The time now is 23:31.