Reply
Thread Tools
Posts: 602 | Thanked: 735 times | Joined on Mar 2011 @ Nantes, France
#551
That's a pretty big number of driver versions! But that could worth the try to test them in a systematic way and share our results. I can start a Google doc which you help to track our testing. Any volunteer?

@beobatcher: so let's say I've a D821
 

The Following User Says Thank You to romu For This Useful Post:
Posts: 9 | Thanked: 1 time | Joined on Mar 2016
#552
May be porters can hint if this is meaningful.
 
Posts: 69 | Thanked: 85 times | Joined on Mar 2013
#553
Originally Posted by romu View Post
That's a pretty big number of driver versions! But that could worth the try to test them in a systematic way and share our results. I can start a Google doc which you help to track our testing. Any volunteer?

@beobatcher: so let's say I've a D821
on that google drivers website :
we have a sensors config file, sensors blob and sensors.qcom bin file that have to be replaced at the same time.

i've two zip files one for 5.0.1 version and one with latest 6.0.1 version
each zip file has config files with info where those files have to be copied

found 3 extra sensor** .so files for each version in /system/vendor.lib folder

now lets do some testing :-)
Attached Files
File Type: zip n5jolla_601_sensordrivers.zip (251.3 KB, 73 views)
File Type: zip n5jolla_501_sensordrivers.zip (236.1 KB, 76 views)

Last edited by frullewulle; 2016-03-02 at 16:26.
 

The Following 2 Users Say Thank You to frullewulle For This Useful Post:
Posts: 602 | Thanked: 735 times | Joined on Mar 2011 @ Nantes, France
#554
Just created a google sheet: https://docs.google.com/spreadsheets...it?usp=sharing

@frullewulle: imho, it would be better to identify the driver set by the code number we find on the Google page. Not 5.0.1, but LMY48D, etc. Just in case we want to test more than 2 versions.

EDIT: would also be great to document which exact files have to go to which exact folder.

Last edited by romu; 2016-03-02 at 16:55.
 

The Following User Says Thank You to romu For This Useful Post:
Posts: 69 | Thanked: 85 times | Joined on Mar 2013
#555
new zip files with some additional driver files
Attached Files
File Type: zip n5jolla_LRX22C_sensordrivers.zip (262.0 KB, 75 views)
File Type: zip n5jolla_MMB29Q_sensordrivers.zip (294.0 KB, 85 views)
 

The Following User Says Thank You to frullewulle For This Useful Post:
Posts: 9 | Thanked: 1 time | Joined on Mar 2016
#556
We have @llelectronics with happy set of dependencies for 2.0.1.7.

If i put his sensors.msm8974.so into my 2.0.0.10 i will get broken sensors setup. Simplest cause for this would be that that 2.0.0.10 is the source this dependency mismatch.

We need to track down these dependencies and make the happiness reproducible.
While we don't know the exact set of dependencies we could start comparing sizes/md5s for find / -name *sensor*.
 
Posts: 9 | Thanked: 1 time | Joined on Mar 2016
#557
I'll try 2.0.1.7
 
Posts: 602 | Thanked: 735 times | Joined on Mar 2011 @ Nantes, France
#558
I added the SFOS version on the Google sheet.

Just to be sure, for our testing:
  • sensors.msm8974.so -> /vendor/lib/hw/
  • sensors.qcom -> ??
  • sensor_def_hh.conf -> ??

Thanks.
 
Posts: 602 | Thanked: 735 times | Joined on Mar 2011 @ Nantes, France
#559
I spent few moments to collect the sensors drivers and related files from the Google web site. I've got the drivers from all Android available for the N5. You can get the zip here: https://www.dropbox.com/s/5bevanvywvv6w4r/N5.zip?dl=0

I managed to find the location for each sensor files (thanks to everyone who can confirm):
  • sensors.msm8974.so -> /vendor/lib/hw
  • sensor_def_hh.conf -> /system/etc
  • sensors.qcom -> /system/bin

Enjoy!
 

The Following User Says Thank You to romu For This Useful Post:
Posts: 9 | Thanked: 1 time | Joined on Mar 2016
#560
So, now on 2.0.1.7

Original sensors.msm8974.so: cpu 8% for both processes

Replacement sensors.msm8974.so (md5: 5d5005fbd4c819136b766bb125209ba2)
Error in journalctl mostly same, except now additionally
Code:
[root@Jolla nemo]# systemctl status sensorfwd
sensorfwd.service - Sensor daemon for sensor framework
   Loaded: loaded (/lib/systemd/system/sensorfwd.service; disabled)
   Active: failed (Result: start-limit) since Thu 2016-03-03 19:26:30 EET; 32min ago
 Main PID: 1252 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/sensorfwd.service

Mar 03 19:26:30 Jolla systemd[1]: sensorfwd.service start request repeated too quickly, refusing to start.
and nothing moves in Messwerk.
 

The Following User Says Thank You to tolake For This Useful Post:
Reply


 
Forum Jump


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