Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 10 hrs, 19 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 3 hrs ago -
n770 youtube video (0)
to General by nmdv - 6 days, 2 hrs ago - more...
| The Following 2 Users Say Thank You to akira.pwr For This Useful Post: | ||
|
2016-06-26
, 09:22
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#752
|
Originally Posted by akira.pwr
You need to do a new flash unfortunately. Here's info http://piratepad.net/bhP8fbzYgT . We're close to OTA support for it, but users will be able to edit repos on preexisting cm12.1 installs (no need for a new flash to obtain OTA support and updated packages).
I didn't knew there was a 12.1 build for Nexus5, which version of cm do you use? the guide for installation is the same than before? Can I upgrade from actual cm11 to cm12.1 without wipes? Does it works with multirom?
Thanks
 |
|
2016-06-26
, 09:41
|
|
Posts: 115 |
Thanked: 72 times |
Joined on Feb 2011
@ Vicenza, Italy
|
#753
|
What's the advantage to use cm12.1 instead cm11?
| The Following 3 Users Say Thank You to akira.pwr For This Useful Post: | ||
|
|
2016-06-26
, 14:09
|
|
Posts: 426 |
Thanked: 1,812 times |
Joined on Dec 2013
|
#754
|
Better driver support mostly.
This leads to better camera support (I think it should be fully supported)
Better power saving (no sensors bug anymore)
Better bluetooth support (no annoying disconnects)
This leads to better camera support (I think it should be fully supported)
Better power saving (no sensors bug anymore)
Better bluetooth support (no annoying disconnects)
| The Following 5 Users Say Thank You to llelectronics For This Useful Post: | ||
|
|
2016-06-26
, 18:28
|
|
Posts: 69 |
Thanked: 85 times |
Joined on Mar 2013
|
#755
|
Originally Posted by llelectronics
sensors bug is still there for me, its device independent...
Better driver support mostly.
This leads to better camera support (I think it should be fully supported)
Better power saving (no sensors bug anymore)
Better bluetooth support (no annoying disconnects)
| The Following 2 Users Say Thank You to frullewulle For This Useful Post: | ||
|
|
2016-06-26
, 18:43
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#756
|
Originally Posted by frullewulle
Are you running the sensors.msm8974.so that has the laggy z-axis?
sensors bug is still there for me, its device independent...
Line 12 here: http://piratepad.net/bhP8fbzYgT
Edit: reason I ask is that I haven't heard of the issue with that, and was planning on making a "sensorsfix3.zip" with that blob.
Edit2: in an attempt to get rid of some logcat spam regarding audiopolicy, I accidentally massively increased speaker and headset volume, as well as mic volume in calls. Coming with OTA support shortly
.
Last edited by RealJohnGalt; 2016-06-26 at 19:17.
 |
|
2016-06-26
, 19:42
|
|
Posts: 654 |
Thanked: 2,368 times |
Joined on Jul 2014
@ UK
|
#757
|
Originally Posted by RealJohnGalt
How did you do it / what did you change?
Edit2: in an attempt to get rid of some logcat spam regarding audiopolicy, I accidentally massively increased speaker and headset volume, as well as mic volume in calls. Coming with OTA support shortly
| The Following 2 Users Say Thank You to Feathers McGraw For This Useful Post: | ||
|
|
2016-06-26
, 19:49
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#758
|
Originally Posted by Feathers McGraw
It was completely unexpected. On a build with broken camera, I saw a lot of audioflinger-related spam in logcat during debugging. Even after fixing the camera, the spam was still there.
How did you do it / what did you change?
I ended up implementing audioflingerglue (lines 107-157 of http://piratepad.net/hadk-faq), which resulted in reducing the audioflinger logcat spam and increasing volumes.
Edit: If you're asking for FP2, another solution for increasing per-output/input gain is manually editing mixer_paths.xml in the device repo, rebuild hybris-hal, build_packages.sh, then install the updated packages to test. As I said, the audioflingerglue solution wasn't meant to be a solution for volume.
Edit2: While I'm at it, there's also kernel solution for managing output gain using sysfs interfaces. You can cherry-pick a commit like https://github.com/RealJohnGalt/andr...55cfa68e538fd7 or faux123's solution since fp2 also looks to use wcd9320. Then edit on the fly, test, and set using a systemd service or similar.
Last edited by RealJohnGalt; 2016-06-26 at 20:28.
| The Following 5 Users Say Thank You to RealJohnGalt For This Useful Post: | ||
|
|
2016-06-27
, 15:49
|
|
Posts: 69 |
Thanked: 85 times |
Joined on Mar 2013
|
#759
|
Originally Posted by RealJohnGalt
Well every blob that has a different files size then 89.36 Kb results in a not starting sensorfwd.service and sensors.qcom
Are you running the sensors.msm8974.so that has the laggy z-axis?
Line 12 here: http://piratepad.net/bhP8fbzYgT
Edit: reason I ask is that I haven't heard of the issue with that, and was planning on making a "sensorsfix3.zip" with that blob.
Edit2: in an attempt to get rid of some logcat spam regarding audiopolicy, I accidentally massively increased speaker and headset volume, as well as mic volume in calls. Coming with OTA support shortly
only thing i can do for now is dissabling some sensors in primaryuse.conf file in /etc/sensorfw directory
| The Following 2 Users Say Thank You to frullewulle For This Useful Post: | ||
|
|
2016-06-27
, 23:51
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#760
|
Update: Just got everything pushed and updated on a home project (https://build.merproject.org/project...e:RealJohnGalt) 
.
Now going to change some specs for versions to better match (from when I originally based some stuff off cm11). Then test an OTA myself from an older release by modifying the repos manually on device. Next do a build with the proper repos added (for fresh installs). And finally, include instructions on how to update repos from preexisting builds and OTA. Note: even though these packages are up on OBS, please don't use them yet or add the repo.
Edit: ota'd successfully from 2.0.0.10 to 2.0.1.11, instructions coming soon
Last edited by RealJohnGalt; 2016-06-28 at 02:35.
.Now going to change some specs for versions to better match (from when I originally based some stuff off cm11). Then test an OTA myself from an older release by modifying the repos manually on device. Next do a build with the proper repos added (for fresh installs). And finally, include instructions on how to update repos from preexisting builds and OTA. Note: even though these packages are up on OBS, please don't use them yet or add the repo.
Originally Posted by frullewulle
I'll have a new test sensor zip to flash shortly, and would love it if you could test a bit. Working on the above first.
Well every blob that has a different files size then 89.36 Kb results in a not starting sensorfwd.service and sensors.qcom
only thing i can do for now is dissabling some sensors in primaryuse.conf file in /etc/sensorfw directory
Edit: ota'd successfully from 2.0.0.10 to 2.0.1.11, instructions coming soon
Last edited by RealJohnGalt; 2016-06-28 at 02:35.
Thanks