View Single Post
Posts: 97 | Thanked: 318 times | Joined on Feb 2012 @ Switzerland
#361
@mautz

Originally Posted by mautz View Post
I didn't change anything in pulseaudio settings, but alot of things have changed since my last builds...i'll investigate what is new in the audio section.
Sorry. I was not clear enough. I mean in the CM13 port in general, the max sound settings are much louder than in CM12. You have to take in to account, that I am still on CM12 in daily use...


The 60-sensors-hammerhead.conf is now integrated in my configs so sensors should work out of the box after updating. Thanks for your help.
There are really strange things happening. I did a fresh install and upgrade, after other users mentioned some networking problems on 2.2.0.29. I see that after the initial 2.2.0.29 upgrade, all sensors are gone, whereas after my upgrade starting from 2.1.3.15 I had the Magnetometer and the Rotation Sensor working.

So right now, in 2.2.1.18, all sensors are gone, even though you added the .conf file.

UPDATE: I found the relevant log entries in journalctl...
Code:
[D] unknown:0 - There is no sensor manager yet, do not initialize "rotationsensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "proximitysensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "orientationsensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "magnetometersensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "alssensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "gyroscopesensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "compasssensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "alssensor"
[D] unknown:0 - There is no sensor manager yet, do not initialize "accelerometersensor"
2nd UPDATE: I have to realize that my Nexus 5 is dying. I lost WIFI and all the sensors..


Can i replace your old bt script with the new one in my configs?
Sure. For me it is rock stable and robust on my 'daily runner' CM12 port. My first tests show the same for CM13.


Regarding cm12.1, i'm not sure if this base is still completely supported by libhybris, the adaptation layer between android an SFOS, so i'll ask some people in #sailfish-porters about this.
I see. I guess there are some other ports too that are still on a CM12 base.


Now let's wait for the new SDK, to bring 3.0.0.5 to the Nexus
YESSS!!!

Last edited by minimec; 2018-11-09 at 13:00.
 

The Following 2 Users Say Thank You to minimec For This Useful Post: