[ROM] [7.x] nAOSProm for Xperia S

[ROMfan]

GPS lockin takes so long. Is it a bug or sth?

 

[millosr]

Camcorder fix

We have finally succeed to fix the camcorder in android 7
@mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video .

Technically, in android 7 camera and media servers are separated in two processes so official way to handle this is to update vendor HAL to allow that:
http://source.android.com/devices/camera/versioning.html#hardening

Since our vendor HAL is closed source we can't do that easily. Luckily guys from Cyanogenmod team (big thanks to them) found a way to re-integrate these 2 servers:
http://review.cyanogenmod.org/#/c/165008/

There were also some necessary changes for frameworks/av and qcom/media projects (thanks to RonGokhale) :
https://github.com/mickybart/android_frameworks_av/commit/b51845c31ff3f8a53f05f1401e39ea4c52babd71
https://github.com/mickybart/androi...mmit/18914a00cd87b192dd74012419961b4d5591f118

I have build incremental OTA update for the fix. You should flash it only if you have nAOSP-7.0-b04. It just updates necessary libraries, adds integrated media/camera server, removes old camera server, and appends one property to /system/build.prop. You don't have to flash gapps and to clean caches. If something goes wrong you can return to recovery and reflash original nAOSP-7.0-b04 and gapps to return to previous state.

Btw, twrp recovery included in b04 didn't work fine for me so I had to extract and flash recovery from nAOSP-6.0. For your convenience I have share it. You can flash it from adb shell while android is running:
dd if=/sdcard/recovery-6.0.img of=/dev/block/mmcblk0p11

Downloads:

nAOSProm-7.0-b04-camcorder-fix.zip
Google drive: http://bit.ly/2dTZqiY
Dropbox: http://bit.ly/2eetefC
md5sum: 2a3823e01142784a7e07439c8c08076a

recovery-6.0.img
Google drive: http://bit.ly/2e6Wi5l
Dropbox: http://bit.ly/2eAwU78
md5sum: a40e75e743616890a09d1c75c303cd9c

Cheers

 

[frov]

We have finally succeed to fix the camcorder in android 7
@mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video

Wauw, this is quite impressive :laugh:
You guys rock indeed. I will flash & test imm.

---------- Post added at 02:03 PM ---------- Previous post was at 01:30 PM ----------

@millosr @mickybart
So I just downloaded the camcorderfix.zip and uploaded to XS/B04.
In TWRP (the one from B04 still) I dirty flashed the zip (from /data/media/0), and it logged the following (the specific lines):

Update ROM components
Delete old camera server
Modify build.prop

I did NOT wipe anything, I booted and tested: ... IT WORKS
I used the Google Camera app 2.5.052 and made a few small videos. Also taking pics still works fine.
Great!!! :good:

 

[mickybart]

A quick word
I have not a lot of time since 2/3 weeks but I will try to catch unanswered question/bugs reported soon.
I hope to create a b05 before the end of the month that will permit to remove the alpha stage

Thanks to @millosr for his help and the incremental release for b04

 

[patrol-cz]

anyone who is using substratum can please update to version 238 from play store and see if you can apply/re-apply overlay(s) ? I just need a confirmation for Substratum Team that it ends in error. 231 is working fine.

Thanks.

Unfortunately you're right. I just tried it and it ended in error with and after a reboot the phone was unthemed. However, restoring a profile worked.
Pavel

---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------

We have finally succeed to fix the camcorder in android 7
@mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video .

Technically, in android 7 camera and media servers are separated in two processes so official way to handle this is to update vendor HAL to allow that:
http://source.android.com/devices/camera/versioning.html#hardening

Since our vendor HAL is closed source we can't do that easily. Luckily guys from Cyanogenmod team (big thanks to them) found a way to re-integrate these 2 servers:
http://review.cyanogenmod.org/#/c/165008/

There were also some necessary changes for frameworks/av and qcom/media projects (thanks to RonGokhale) :
https://github.com/mickybart/android_frameworks_av/commit/b51845c31ff3f8a53f05f1401e39ea4c52babd71
https://github.com/mickybart/androi...mmit/18914a00cd87b192dd74012419961b4d5591f118

I have build incremental OTA update for the fix. You should flash it only if you have nAOSP-7.0-b04. It just updates necessary libraries, adds integrated media/camera server, removes old camera server, and appends one property to /system/build.prop. You don't have to flash gapps and to clean caches. If something goes wrong you can return to recovery and reflash original nAOSP-7.0-b04 and gapps to return to previous state.

Btw, twrp recovery included in b04 didn't work fine for me so I had to extract and flash recovery from nAOSP-6.0. For your convenience I have share it. You can flash it from adb shell while android is running:
dd if=/sdcard/recovery-6.0.img of=/dev/block/mmcblk0p11

Downloads:

nAOSProm-7.0-b04-camcorder-fix.zip
Google drive: http://bit.ly/2dTZqiY
Dropbox: http://bit.ly/2eetefC
md5sum: 2a3823e01142784a7e07439c8c08076a

recovery-6.0.img
Google drive: http://bit.ly/2e6Wi5l
Dropbox: http://bit.ly/2eAwU78
md5sum: a40e75e743616890a09d1c75c303cd9c

Cheers

Many thanks for this work! I updated and it really records videos .
Regards, Pavel

 

[heavens dragon]

Unfortunately you're right. I just tried it and it ended in error with and after a reboot the phone was unthemed. However, restoring a profile worked.
Pavel

thanks for confirmation i will forward the issue to dev

 

[mickybart]

@heavens dragon, there is some "substratum" commits for Android 7.0 to provider better themes (materialize, more color controls etc).

Do you think that we need them for a future version ?

This is already integrated into PureNexusProject (where I picked up Layers 4.0 for nAOSP 6.0)

Thanks for the feedback

 

[heavens dragon]

@heavens dragon, there is some "substratum" commits for Android 7.0 to provider better themes (materialize, more color controls etc).

Do you think that we need them for a future version ?

This is already integrated into PureNexusProject (where I picked up Layers 4.0 for nAOSP 6.0)

Thanks for the feedback

yes i think if you want to build an OMS rom or Rom with better themes support those commits will be needed.

 

[Darth Inferno]

We have finally succeed to fix the camcorder in android 7 @mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video .

@mickybart
@millosr excellent work guys, testing've noticed that when recording video recording, is a bit laggy but not the play, very similar to the bug of the stock ROM in jelly bean

Note I use cinema fv-5 app and stock nougat app camera

No problem flashing the zip on last TWRP

 

[nageswarswain]

We have finally succeed to fix the camcorder in android 7 @mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video .

@mickybart
@millosr excellent work guys, testing've noticed that when recording video recording, is a bit laggy but not the play, very similar to the bug of the stock ROM in jelly bean

Note I use cinema fv-5 app and stock nougat app camera

No problem flashing the zip on last TWRP

Yes I noticed it too...

 

[mickybart]

Headset

Hi Guys, I think that my jack is "more or less broken" on my phone. (I tried on 7.0 and 6.0 b14 with old kernel too and I have the same behaviour)

When I plug a headset in the jack, sometime the phone switch on it (or not).
If it switch on it, I'm hearing perfectly with the headset (but it happens to have small distortion that can sound like a higher volume).
If I unplug the headset from the jack, sometime it is take into account but not always.

For example I'm able to run the FM Radio application without the headset (plug it a first time and I can remove it....) => I have the idea to remove the constraint to have the headset plugged because the reception is good without

Another way to quickly see the issue is to :
- restart the device (just to be at the same initial state)
- start FM Radio (that will ask for the headset)
- plug headset (FMRadio should switch to main FM interface)
- unplug headset (FMRadio should go back to the screen to ask for headset plug)
- plug it again, unplug it, plug it again etc... (you should have the good behaviour if everything is fine on every case) => please try to do it A LOT OF TIME

The wrong case will be : unplug the headset but the FMRadio doesn't swith to the screen to ask to plug headset... and the FM will continue to play.

To add more detail, I was thinking that the issue was due to the new kernel but I have the same on 6.0 b14 with the old kernel from b13. I was an heavy user of jack because I'm using it since 4 years for phone call or play sound on my sound system.
I'm still using Sony original headset and I have cleaned my jack.

This is strange because some time I can do the procedure a lot of time without issue at all, but sometime not !

So thanks a lot for your feedback

 

[mirhl]

Everything seems fine on b13

 

[nageswarswain]

@mickybart I am also facing issues on headset..I posted logcat about this few days ago..please check

 

[ajayzone2]

Headset

Hi Guys, I think that my jack is "more or less broken" on my phone. (I tried on 7.0 and 6.0 b14 with old kernel too and I have the same behaviour)

When I plug a headset in the jack, sometime the phone switch on it (or not).
If it switch on it, I'm hearing perfectly with the headset (but it happens to have small distortion that can sound like a higher volume).
If I unplug the headset from the jack, sometime it is take into account but not always.

For example I'm able to run the FM Radio application without the headset (plug it a first time and I can remove it....) => I have the idea to remove the constraint to have the headset plugged because the reception is good without

Another way to quickly see the issue is to :
- restart the device (just to be at the same initial state)
- start FM Radio (that will ask for the headset)
- plug headset (FMRadio should switch to main FM interface)
- unplug headset (FMRadio should go back to the screen to ask for headset plug)
- plug it again, unplug it, plug it again etc... (you should have the good behaviour if everything is fine on every case) => please try to do it A LOT OF TIME

The wrong case will be : unplug the headset but the FMRadio doesn't swith to the screen to ask to plug headset... and the FM will continue to play.

To add more detail, I was thinking that the issue was due to the new kernel but I have the same on 6.0 b14 with the old kernel from b13. I was an heavy user of jack because I'm using it since 4 years for phone call or play sound on my sound system.
I'm still using Sony original headset and I have cleaned my jack.

This is strange because some time I can do the procedure a lot of time without issue at all, but sometime not !

So thanks a lot for your feedback

My Headphone Jack is Broken too

Now i am Using This Bluetooth Device

U too Use Something Like That

 

[moe18]

Headset

Hi Guys, I think that my jack is "more or less broken" on my phone.......

I have not experienced that issue with headphones on my phone, I listen about 4 hours each day to music on it and don't have the issue you mentioned. I'm on nAOSP 7.0 b04 at the moment.

 

[frantisekz]

@mickybart I am using SoundAbout app for "enforcing" media audio output to jack even if detection doesn't work properly (I've killed my jack connection detection by dropping phone to snow ~year ago)

 

[nageswarswain]

@mickybart I am getting very low sound while calling in earspeaker...even I can't listen anything when outside...is there any solution to this or has to replace the spare

Sent from my Pixel using XDA-Developers mobile app

 

[patrol-cz]

thanks for confirmation i will forward the issue to dev

Yesterday I found a new update to the Substratum engine (release 350) and today another one (to 351). However, neither of them works here.
The new thing is, that a failure log appears. There is the screenshot.
Regards, Pavel

 

[mickybart]

Everything seems fine on b13

@mickybart I am also facing issues on headset..I posted logcat about this few days ago..please check

Do you have the same issue on b13 ? if yes that means that this is a hardware issue like some other reported :/

My Headphone Jack is Broken too

Now i am Using This Bluetooth Device

U too Use Something Like That

I have not experienced that issue with headphones on my phone, I listen about 4 hours each day to music on it and don't have the issue you mentioned. I'm on nAOSP 7.0 b04 at the moment.

@mickybart I am using SoundAbout app for "enforcing" media audio output to jack even if detection doesn't work properly (I've killed my jack connection detection by dropping phone to snow ~year ago)

Thanks a lot guys for your feedback. I can conclude that this is not a software but a hardware issue. I will check to include a quick button to "simulate" the jack detection.

http://electronics.stackexchange.co...phone-detect-if-3-5-mm-jack-circuit-is-closed

@mickybart I am getting very low sound while calling in earspeaker...even I can't listen anything when outside...is there any solution to this or has to replace the spare

Sent from my Pixel using XDA-Developers mobile app

I will try to work again on the earspeaker to increase the volume (I read somewhere that Android 7.0 should have some thing to increase it for accessibility). On my side at the maximum volume I can ear the person. I have cleaned my earspeaker protection too to try to remove some dust and it was benefit (~ 1 year ago).
FYI, I have removed small protection on my Sony headset maybe 2 years ago (too dusty and impossible to really clean them)... the sound volume difference was really important (not a placebo) !

My last assumptions doesn't means that the earphone issue is not a software issue and it is true that earphone communication is not really comfortable in noisy place.

I will probably try to go back on stock ROM to be able to do a real comparison because anybody are agree or reported the same thing about the earphone volume. Maybe I should try to disable everything relative to dual mic.

 

[heavens dragon]

Yesterday I found a new update to the Substratum engine (release 350) and today another one (to 351). However, neither of them works here.
The new thing is, that a failure log appears. There is the screenshot.
Regards, Pavel

that error was due to some mistake in app itself but it's fixed in 351 as for the previous error we were getting move back to 231, the devs of substratum is still working on fix it's only happening on our device as far as i know.