![]() |
Re: SailfishOS 2.0 on Nexus 5
thanks, but doesn't change a thing ...
|
Re: SailfishOS 2.0 on Nexus 5
Quote:
|
Re: SailfishOS 2.0 on Nexus 5
So it might be different hardware revisions here.
I am out of ideas currently why it works here and does not work for you. Is there anyone else using this so file and it is working ? |
Re: SailfishOS 2.0 on Nexus 5
What about the kernel we have to flash to use TWRP recovery plus Multirom? Could it have any impact as there are different versions out there?
|
Re: SailfishOS 2.0 on Nexus 5
Good idea.
My kernel version string is (obtained with uname -a): Quote:
I will search for fixed .so file |
Re: SailfishOS 2.0 on Nexus 5
that's the same sfos kernel i use for 2.0.1.7
|
Re: SailfishOS 2.0 on Nexus 5
Linux Jolla 3.4.0-cyanogenmod-g9b77194 for me, and I flashed CM11.
|
Re: SailfishOS 2.0 on Nexus 5
I updated the .so file with a version that has a fixed proximity sensor.
In messwerk however to get any values you need to cover the sensor first. Then it starts kicking in. https://www.dropbox.com/s/pgqv0bqobd...sm8974.so?dl=0 (Yeah link did not change, I replaced the file on my dropbox) |
Re: SailfishOS 2.0 on Nexus 5
Quote:
p.s. Found explanation above. |
Re: SailfishOS 2.0 on Nexus 5
Quote:
Searched the various different forum entries that popped out with different ROMs for OnePlus and Nexus5. Found a thread checked it and found out there was a fixed sensors.msm8974 for the OnePlus apparently. This one seems to be the first version I had. So I downloaded the rom and grabbed the restore original version (which seems to be from CM12 or 13) Hope that explains it :) edit: If it works for everyone now it would be nice if someone could point that out in the original bug report on bugs.nemomobile.org |
Re: SailfishOS 2.0 on Nexus 5
Yeah, seems to work fine for me!! Great job! This should be spread to the porters team to see how it can be integrated into the SFOS installation procedure.
Thanks, really. |
Re: SailfishOS 2.0 on Nexus 5
Bad news, sensors framework crashed even with this new driver.
|
Re: SailfishOS 2.0 on Nexus 5
Did it really crashed or went to deep sleep state.
Deep Sleep state means it takes a few seconds after a long standby for it to wake up all sensors again. You can start messwerk and see when the sensors start to work again. Usually after.20 secs here. |
Re: SailfishOS 2.0 on Nexus 5
I think it crashed, but I'll be more careful the next time.
|
Weird issue, open to suggestions
Edit: nvm, reinstalled
|
Re: SailfishOS 2.0 on Nexus 5
I confirm, sensors crashed, again some minutes ago.
|
Re: SailfishOS 2.0 on Nexus 5
If it really crashed (the process) then there should be something in the journalctl log.
Can you take a look. If that happens (sorry but I am not still 100% sure what you mean by crashed) is the sensors.qcom and sensorfw process still running ? (Can you check that via ssh) And if it is then please describe in the most detailed way you can what you mean by crashed. |
Re: SailfishOS 2.0 on Nexus 5
No problem, I'll give you the most information I can get the next time it happens. With the original driver, the sensors processes were not shutdown, they were always present, just eating too much CPU.
I'll check with this new driver. |
Re: SailfishOS 2.0 on Nexus 5
I am also running CM11 + 2.0.0.10 + llelectronics pointed .so.
and journalctl has: Mar 01 08:08:57 Jolla sensorfwd[847]: int HybrisManager::handleForType(int) No sensor of type: 5 Mar 01 08:08:57 Jolla sensorfwd[847]: Node ' "alsadaptor" ' state changed to invalid Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "adaptor 'alsadaptor' can not be started" Mar 01 08:08:57 Jolla sensorfwd[847]: Node ' "alssensor" ' state changed to invalid Mar 01 08:08:57 Jolla sensorfwd[847]: "alssensor instantiation failed" Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "sensor has not been instantiated" Mar 01 08:08:57 Jolla sensorfwd[847]: int HybrisManager::handleForType(int) No sensor of type: 8 Mar 01 08:08:57 Jolla sensorfwd[847]: Node ' "proximityadaptor" ' state changed to invalid Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "adaptor 'proximityadaptor' can not be started" Mar 01 08:08:57 Jolla sensorfwd[847]: Node ' "proximitysensor" ' state changed to invalid Mar 01 08:08:57 Jolla sensorfwd[847]: "proximitysensor instantiation failed" Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "sensor has not been instantiated" Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "requested sensor id 'alssensor' not registered" Mar 01 08:08:57 Jolla sensorfwd[847]: int HybrisManager::handleForType(int) No sensor of type: 1 Mar 01 08:08:57 Jolla sensorfwd[847]: Node ' "accelerometeradaptor" ' state changed to invalid Mar 01 08:08:57 Jolla sensorfwd[847]: SensorManagerError: "adaptor 'accelerometeradaptor' can not be started" Mar 01 08:08:57 Jolla sensorfwd[847]: ASSERT: "accelerometerAdaptor_" in file accelerometerchain.cpp, line 48 and sensors.qcom is leaking memory in a single day 1m -> 22m. |
Re: SailfishOS 2.0 on Nexus 5
Looks like the error message I had on the .so file that did not work at all for me.
Does this one work for you at all ? Or does this error message pop up on later usage ? |
Re: SailfishOS 2.0 on Nexus 5
maybe we can check in cpu-z in android have in each device to be certain that we talk about same hardware:
in my case: APDS-9930/QPDS-T930 proimity & light AK8963 magnetometer second thing: who has sfdroid running or installed and who not? MPU6515 gyroscope i have it installed but reverted init , so not running |
Re: SailfishOS 2.0 on Nexus 5
I have D821E 16Gb running minimal Sailfish, no sfdroid, no dalvik.
With the last llelectronics .so the proximity is working, rotation is not. Never seen sensors taking CPU more than 6% with this .so. On idle phone the sensors* take less than 0.3%. |
Re: SailfishOS 2.0 on Nexus 5
Forgot: errors appear only at phone bootup
|
Re: SailfishOS 2.0 on Nexus 5
It basically means the .so file does not support your gyroscope/accelerometer so orientation is not working.
It is really strange as it is working here in 2.0.1.7 So either it is a software thing in 2.0.1 that make it work here or we have really different sensors. |
Re: SailfishOS 2.0 on Nexus 5
I run a D820 (European model)
MPU6515 too, didn't managed how to get the proximity/light sensor reference. I run the @llelectronics .so, and rotation doesn't work either. With Messwerk, rotation works for X and Y axis only, not for Z axis. |
Re: SailfishOS 2.0 on Nexus 5
Who has android partition loaded in sailfishos?
Maybe that has an influence too? |
Re: SailfishOS 2.0 on Nexus 5
1 Attachment(s)
Wow thats ultra strange. I have everything working here.
Also Position Z Axis. Also running MPU6515. The only thing I noticed is that it took some time after reboot to kick in. So at least 1 minute before I got data for the Z-Axis. But I got data. See attached screenshot |
Re: SailfishOS 2.0 on Nexus 5
I've just tested some swaps between the original driver and the new one. And I confirm that the rotation on Z axis doesn't work at all. So I switched back to the original driver and re-enabled the sensors watchdog.
|
Re: SailfishOS 2.0 on Nexus 5
Looking at https://developers.google.com/androi...mmerheadlmy48m
it seems that drivers for sensors are packaged for LG and QCom separately. I assume we should swap both. Just an idea. |
Re: SailfishOS 2.0 on Nexus 5
Romu, the N5 D820 is a North American model. D821 is European model.
|
Re: SailfishOS 2.0 on Nexus 5
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 :D |
Re: SailfishOS 2.0 on Nexus 5
May be porters can hint if this is meaningful.
|
Re: SailfishOS 2.0 on Nexus 5
2 Attachment(s)
Quote:
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 :-) |
Re: SailfishOS 2.0 on Nexus 5
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. |
Re: SailfishOS 2.0 on Nexus 5
2 Attachment(s)
new zip files with some additional driver files
|
Re: SailfishOS 2.0 on Nexus 5
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*. |
Re: SailfishOS 2.0 on Nexus 5
I'll try 2.0.1.7
|
Re: SailfishOS 2.0 on Nexus 5
I added the SFOS version on the Google sheet.
Just to be sure, for our testing:
Thanks. |
Re: SailfishOS 2.0 on Nexus 5
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):
Enjoy! |
Re: SailfishOS 2.0 on Nexus 5
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 |
All times are GMT. The time now is 16:28. |
vBulletin® Version 3.8.8