Z1c Nougat Roms

De_Joe_991

New member
Dec 29, 2016
3
1
0
Originally Posted by derf elot

I have uploaded a new CM14.1 build, now based on Android 7.1.1. Some upstream changes from sonyxperiadev are in there too. You can grab it here: ...
Great work so far! I'm testing the current Version from Dec 11.
A Few bugs and questions:
- Camera crashes (screen gets black) when opened from Whatsapp.
- Fullscreen on Youtube turns screen black (only the video, not the ads)
- Missing Energy-Profiles. Only one there. Not possible to change it
- Quiet high energy consumption in sleep mode. (Already restartet the phone)
- How will it continue after CM died?

Looking formward to continue testing and report issues.
Is there any official Bug-Report?

Edit:
I've had some problems after installing it the first time with a message: "encryption unsuccessfull". Found out that it had to do with the data folder. I changed the file format to ext4, than it worked just fine.
 
Last edited:

derf elot

Senior Member
May 7, 2011
817
1,706
0
Hi guys,

uploaded a new build. It's now Lineage OS, so goodbye Cid :( I have some time the next few days to hopefully get a TWRP with working decryption built and also to have a look at some more issues with the ROM.

You can download the build here: https://www.androidfilehost.com/?fid=457095661767126276

Big thanks again to sonyxperiadev and especially David Viteri for his work on the SonyLOS reps.

does it support F2FS?
No sorry, not yet.

Great work so far! I'm testing the current Version from Dec 11.
A Few bugs and questions:
- Camera crashes (screen gets black) when opened from Whatsapp.
- Fullscreen on Youtube turns screen black (only the video, not the ads)
- Missing Energy-Profiles. Only one there. Not possible to change it
- Quiet high energy consumption in sleep mode. (Already restartet the phone)
- How will it continue after CM died?

Looking formward to continue testing and report issues.
Is there any official Bug-Report?
- See if the latest build still has this problem, but I might have an idea as to what could cause that camera crash on Whatsapp, or other apps for that matter.
- As for Youtube black screen, try disabling HW overlay setting in developer options.
- Not sure which profiles you refer to, but I'm pretty sure, this is something lacking from the CM/Lineage side.
- The battery drain is something I want to look at now as well
- See above :)

There is no official bug-reporting. You can just post what you find here for now. Once new blobs are released (and things like the camera get a bit more stable), I will probably open up a thread for this.

Cheers
 

karamancho

Senior Member
May 14, 2014
476
134
73
...
No sorry, not yet.
...
I tried it on my own and experienced something strange (though its TWRP related I'm gonna write it here since I was using your TWRP build)

when I tried to convert the partitions to F2FS in TWRP before flashing the rom I got the usual log message, something like partition formatted using f2fs but then when I tried to flash the rom the log said the partitions were missing.

namely the partitions were converted to F2FS but got unmounted and I wasn't able to re-mount them again, even after a reboot.

I'm back on stock FW but I taught I'd share my experience, maybe you can look at it when you have some free time
 

derf elot

Senior Member
May 7, 2011
817
1,706
0
Hi,

yeah, that's not unexpected behavior. With the fstab I is currently use to build TWRP, it tries to mount system, data and cache as ext4 partitions only.

When I have a build that supports f2fs I will post it here :)

I tried it on my own and experienced something strange (though its TWRP related I'm gonna write it here since I was using your TWRP build)

when I tried to convert the partitions to F2FS in TWRP before flashing the rom I got the usual log message, something like partition formatted using f2fs but then when I tried to flash the rom the log said the partitions were missing.

namely the partitions were converted to F2FS but got unmounted and I wasn't able to re-mount them again, even after a reboot.

I'm back on stock FW but I taught I'd share my experience, maybe you can look at it when you have some free time
 

De_Joe_991

New member
Dec 29, 2016
3
1
0
Hi guys,

uploaded a new build. It's now Lineage OS, so goodbye Cid :( I have some time the next few days to hopefully get a TWRP with working decryption built and also to have a look at some more issues with the ROM.

- See if the latest build still has this problem, but I might have an idea as to what could cause that camera crash on Whatsapp, or other apps for that matter.
- As for Youtube black screen, try disabling HW overlay setting in developer options.
- Not sure which profiles you refer to, but I'm pretty sure, this is something lacking from the CM/Lineage side.
- The battery drain is something I want to look at now as well
- See above :)

Cheers
I installed it. THANK YOU!
old issues:
- camera still gets black if startet over Whatsapp, but when HW overlay is disabled it works fine! THANKS!
- HW overlay solves the problem on youtube as well. GREAT!
- Powerprofile - settings under battery are now removed, so this issue can be ignored now.

new issues :) :
- After power off or reboot HW overlay setting is reset again.
- Camera is very slow in focusing and fails some times. But all in all this is okay. I use the open camera app, the built in one just shows black when startet directly. Startet over other apps it works. The focus speed is the same in all camera-apps.

I will update this as soon as i find some more issues. I use the z1c it as my primary phone so i hope to find issues if there are some.
If there is anything special you want me to test, just say ist ;)
Again great work and thans a lot!

By the way: happy new year!
 
Last edited:

derf elot

Senior Member
May 7, 2011
817
1,706
0
Hi again,

finally managed to build a TWRP that supports decryption and which isn't too big to fit into our recovery partition. I built it from within the Lineage 14.1 sources.

If you want to use encryption and you have previously used a recovery that doesn't support decryption, you have to format (as in, 'format data') at least once, otherwise you wont be able to encrypt your phone. Most likely this is because your data partition is too big and there is no room for the crypto footer anymore. Make sure you back-up everything you need off your phone before you format!

I have only tested this with the new Lineage 14.1 builds. No guarantee that this will work with previous CM's or other ROMs.

Here's the download link: https://www.androidfilehost.com/?fid=529152257862692136

Cheers

Edit: No F2FS support on this one yet.

I installed it. THANK YOU!
old issues:
- camera still gets black if startet over Whatsapp, but when HW overlay is disabled it works fine! THANKS!
- HW overlay solves the problem on youtube as well. GREAT!
- Powerprofile - settings under battery are now removed, so this issue can be ignored now.

new issues :) :
- After power off or reboot HW overlay setting is reset again.
- Camera is very slow in focusing and fails some times. But all in all this is okay. I use the open camera app, the built in one just shows black when startet directly. Startet over other apps it works. The focus speed is the same in all camera-apps.

I will update this as soon as i find some more issues. I use the z1c it as my primary phone so i hope to find issues if there are some.
If there is anything special you want me to test, just say ist ;)
Again great work and thans a lot!

By the way: happy new year!
Yes, that setting always resets itself on reboot. You can search through XDA a bit, I think there are some init.d scripts available you can use to set it at boot automatically. Keep in mind that there _might_ be some downsides in terms of battery life, since the CPU has to work a bit harder.

Also, it's strange that you get a black screen with the built-in camera app. It working fine here. It's dark, and the front cam is upside down, but it works. Things should improve with new Sony blobs.

Happy new year to you too :)
 
Last edited:

karamancho

Senior Member
May 14, 2014
476
134
73
I will update this as soon as i find some more issues. I use the z1c it as my primary phone so i hope to find issues if there are some.
If there is anything special you want me to test, just say ist ;)
I remember the in-call volume (at max) being a bit lower than on stock fw, can you give your taughts on that
 

Micha_Btz

Senior Member
Jul 27, 2012
294
92
58
Hi guys,

uploaded a new build. It's now Lineage OS, so goodbye Cid :( I have some time the next few days to hopefully get a TWRP with working decryption built and also to have a look at some more issues with the ROM.

You can download the build here: https://www.androidfilehost.com/?fid=457095661767126276

Big thanks again to sonyxperiadev and especially David Viteri for his work on the SonyLOS reps.
today i tried this build. i did a dirty flash about cm-12.1 and the rom is not able to decrypt my data partition. aicp has the same problem since you used both the sony source.
i there the partition layout differrent from older cm roms? I just wanted to test how far 14.1 is so i don't want a full wipe.
Can i do a backup from the internal sd card with twrp?

Thanks

PS: maybe a extra thread for Lineage OS would be a good idea, this thread was desinged for overview i think
 

Frannny

Member
Jan 4, 2017
26
2
0
Dear Derf,

I ran into the sudden battery death issue a while ago.
When replacing the battery with a brand new one did not help even after a factory reset, I installed your 7.1.1 lineage.

Works nice, great job!!!

Still occasionally the screen freezes and can only be unfrozen by a reboot.

Battery sudden death is still there too.

Would be awesome if you find a solution.!!

YouTube and camera work as well as sim(sometimes it takes a little for the sim to be recognized) . I had it show up after the second reboot.

Camera has sometimes issues properly focusing.

Apart from that really great job to rejuvenate a phone.

The battery death is the biggest issue to me.

I run green power app too but it doesn't help a lot.

Thanks Fran
 
Last edited:

grmat

New member
Jan 26, 2017
2
0
0
Hi there,

Check the manifest on the SonyCM github.
Hi guys,

uploaded a new build. It's now Lineage OS
Thanks for your work.
Are you working towards getting an official LineageOS build for amami?

I also started looking into the topic and tried building from source by myself. I ended up with a booting system, however, many things are not working (e.g. wifi and cellular).
I basically used the SonyLOS manifest in the 14.1 branch[1] and added your 14.1 amami repo[2] to it. Could you share what else you had to do?

Thanks in advance

[1]: github/SonyLOS/local_manifests/blob/cm-14.1/roomservice.xml
[2]: github/derfelot/android_device_sony_amami/tree/cm-14.1
(not allowed to post links for the first 10 posts)
 

derf elot

Senior Member
May 7, 2011
817
1,706
0
Hello,

sorry for the lack of recent builds, but life, family and work have gotten between me and spending more serious time on this.

I have uploaded the latest build I could find on my machine. You can download it here: https://www.androidfilehost.com/?fid=817550096634743122

I should have had a later one, but that must have gotten lost in my rage :) I got too annoyed about the battery life and some other things right now though. Charging the phone every other day or so even though wifi is off and phone is on airplane mode is too much :)

The little time I have had, I spent on making a new CM12.1 build containing the latest security fixes. That's quite a hassle as well, since neither Google nor LOS seem to be updating their LP sources anymore. But now I have 10+ days without charging again (wifi off & airplane mode).

I might try another 14.1 build again when the new blobs have settled in for a bit.

Hi there,





Thanks for your work.
Are you working towards getting an official LineageOS build for amami?

I also started looking into the topic and tried building from source by myself. I ended up with a booting system, however, many things are not working (e.g. wifi and cellular).
I basically used the SonyLOS manifest in the 14.1 branch[1] and added your 14.1 amami repo[2] to it. Could you share what else you had to do?

Thanks in advance

[1]: github/SonyLOS/local_manifests/blob/cm-14.1/roomservice.xml
[2]: github/derfelot/android_device_sony_amami/tree/cm-14.1
(not allowed to post links for the first 10 posts)
Hi,

no, I am not working on official LOS support. From my understanding, a few others might be though.

Yes, unfortunately the manifest on SonyLOS has changed quite a few times, without keeping the history. Here's the manifest which I used to successfully build it last time (see build above). Keep in mind that I just changed my amami repo name to "device_sony_amami_los14.1" since I am currently making updates for cm12.1. :

Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
  <!-- This xml is project for make sony targets work with AOSP hardware -->
  
  <!-- Remove some CM stuff -->
  <remove-project name="LineageOS/android_hardware_qcom_audio" />
  <remove-project name="LineageOS/android_hardware_qcom_display" />
  <remove-project name="LineageOS/android_hardware_qcom_fm" />
  <remove-project name="LineageOS/android_hardware_qcom_media" />
  <remove-project name="LineageOS/android_packages_apps_FMRadio" />

  <project name="sonyxperiadev/packages-apps-FMRadio" path="packages/apps/FMRadio" remote="github" revision="master" />

  <!-- common -->
  <project name="SonyLOS/android_device_sony_common-aosp" path="device/sony/common-aosp" remote="github" revision="cm-14.1" />

  <!-- rhine -->
  <project name="SuperLamic/android_device_sony_rhine-common" path="device/sony/rhine-common" remote="github" revision="cm-14.1" />
  <project name="derfelot/android_device_sony_amami" path="device/sony/amami" remote="github" revision="cm-14.1" />

  <!-- shinano -->
  <project name="SonyLOS/android_device_sony_shinano-common" path="device/sony/shinano-common" remote="github" revision="cm-14.1" />
  <project name="derfelot/android_device_sony_aries" path="device/sony/aries" remote="github" revision="cm-14.1" />

  <!-- sony sepolicy -->
  <project name="sonyxperiadev/device-sony-sepolicy" path="device/sony/sepolicy" remote="github" revision="n-mr0" />
  
  <!-- kernel 3.10 -->
  <project name="sonyxperiadev/kernel" path="kernel/sony/msm" remote="github" revision="aosp/LA.BR.1.3.3_rb2.14" />

  <!-- qcom hardware -->
  <project name="SonyLOS/android_hardware_qcom_audio" path="hardware/qcom/audio/default" remote="github" revision="cm-14.1" />
  <project name="SonyLOS/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="cm-14.1" />
  <project name="SonyLOS/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="cm-14.1" />
  <project name="sonyxperiadev/vendor-qcom-opensource-fm" path="hardware/qcom/fm" remote="github" revision="master" />

  <!-- sony hardware -->
  <project name="SonyLOS/android_hardware_sony_camera" path="hardware/sony/camera" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_hardware_sony_macaddrsetup" path="hardware/sony/macaddrsetup" remote="github" revision="cm-14.1" />
  <project name="sonyxperiadev/device-sony-common-init" path="hardware/sony/init" remote="github" revision="master" />
  <project name="sonyxperiadev/vendor-qcom-opensource-dataservices" path="hardware/sony/dataservices" remote="github" revision="master" />
  
  <!-- vendor -->
  <project name="SonyAosp/vendor_nxp" path="vendor/nxp" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_qcom" path="vendor/qcom" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_sony" path="vendor/sony" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_qcom_firmware" path="vendor/qcom/firmware" remote="github" revision="android-7.0" />

</manifest>
You can of course remove the shinano stuff if you don't want to build for Z3/Z3C. I am using @SuperLamic 's repo for rhine since he has a fix in it for mobile data when you don't have LTE. It's better, but still not working stable for me. I have LTE, so for me it doesn't matter, but it also didn't help much with battery life as hoped.

Personally, I switched back to only using the xperiadev sepolicy, by changing the device/common-aosp/CommonConfig.mk from
Code:
# SELinux
include device/qcom/sepolicy/sepolicy.mk
-include device/sony/sepolicy/sepolicy.mk
to
Code:
# SELinux
include device/sony/sepolicy/sepolicy.mk
Btw, I have also successfully built TWRP from within the LOS14.1 sources. Just check out the cm-14.1-twrp branch of amami on my git. It should also support decryption. To build TWRP, you can use this manifest:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
  <!-- This xml is project for make sony targets work with AOSP hardware -->
  <!-- CM stuff -->

  <remove-project name="LineageOS/android_bootable_recovery" />
  <remove-project name="LineageOS/android_hardware_qcom_audio" />
  <remove-project name="LineageOS/android_hardware_qcom_display" />
  <remove-project name="LineageOS/android_hardware_qcom_fm" />
  <remove-project name="LineageOS/android_hardware_qcom_media" />
  <remove-project name="LineageOS/android_packages_apps_FMRadio" />

  <project name="derfelot/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-7.1" />
  <project name="sonyxperiadev/packages-apps-FMRadio" path="packages/apps/FMRadio" remote="github" revision="master" />

  <!-- common -->
  <project name="SonyLOS/android_device_sony_common-aosp" path="device/sony/common-aosp" remote="github" revision="cm-14.1" />

  <!-- rhine -->
  <project name="SuperLamic/android_device_sony_rhine-common" path="device/sony/rhine-common" remote="github" revision="cm-14.1" />
  <project name="derfelot/android_device_sony_amami" path="device/sony/amami" remote="github" revision="cm-14.1-twrp" />

  <!-- shinano -->
  <project name="SonyLOS/android_device_sony_shinano-common" path="device/sony/shinano-common" remote="github" revision="cm-14.1" />
  <project name="derfelot/android_device_sony_aries" path="device/sony/aries" remote="github" revision="cm-14.1-twrp" />

  <!-- sony sepolicy -->
  <project name="sonyxperiadev/device-sony-sepolicy" path="device/sony/sepolicy" remote="github" revision="n-mr0" />
  
  <!-- kernel 3.10 -->
  <project name="sonyxperiadev/kernel" path="kernel/sony/msm" remote="github" revision="aosp/LA.BR.1.3.3_rb2.14" />

  <!-- qcom hardware -->
  <project name="SonyLOS/android_hardware_qcom_audio" path="hardware/qcom/audio/default" remote="github" revision="cm-14.1" />
  <project name="SonyLOS/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="cm-14.1" />
  <project name="sonyxperiadev/vendor-qcom-opensource-fm" path="hardware/qcom/fm" remote="github" revision="master" />
  <project name="SonyLOS/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="cm-14.1" />

  <!-- sony hardware -->
  <project name="SonyLOS/android_hardware_sony_camera" path="hardware/sony/camera" remote="github" revision="cm-14.1" />
  <project name="sonyxperiadev/thermanager" path="hardware/sony/thermanager" remote="github" revision="master" />
  <project name="sonyxperiadev/timekeep" path="hardware/sony/timekeep" remote="github" revision="master" />
  <project name="sonyxperiadev/macaddrsetup" path="hardware/sony/macaddrsetup" remote="github" revision="master" />
  <project name="sonyxperiadev/device-sony-common-init" path="hardware/sony/init" remote="github" revision="master" />
  <project name="sonyxperiadev/vendor-qcom-opensource-dataservices" path="hardware/sony/dataservices" remote="github" revision="master" />
  
  <!-- vendor -->
  <project name="SonyAosp/vendor_nxp" path="vendor/nxp" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_qcom" path="vendor/qcom" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_sony" path="vendor/sony" remote="github" revision="android-7.0" />
  <project name="SonyAosp/vendor_qcom_firmware" path="vendor/qcom/firmware" remote="github" revision="android-7.0" />

  <project name="omnirom/android_external_busybox" path="external/busybox" remote="github" revision="android-7.1" />

</manifest>
I think TWRP has been patched to work out of the box without busybox now. You could try to remove the busybox at the end and directly grab the sources from omnirom instead of my git.

Then the following should build a TWRP:

Code:
source build/envsetup.sh
lunch lineage_amami-eng
make clean && make -j5 recoveryimage
Good luck! And please share your results :)
 

levone1

Senior Member
Dec 28, 2014
3,741
1,451
243
Hello,

sorry for the lack of recent builds, but life, family and work have gotten between me and spending more serious time on this.

I have uploaded the latest build I could find on my machine. You can download it here: https://www.androidfilehost.com/?fid=817550096634743122
Funny - I've been out of the loop for a while, so not aware of what's going on with N builds, so I wanted to update OP, and went poking around last night to see what is out there these days, and found your build and flashed it. Seemed pretty solid, but got a couple of hiccups with system r/w access, and battery reporting. I'll check out new build.

Besides that, it seems like AICP is the only other thing going, right?

BTW - I did hear from team Vanir on G+ that they plan on a N build for us soon...
 

grmat

New member
Jan 26, 2017
2
0
0
Good luck! And please share your results :)
Thank you very much. I also don't have much time right now, but I managed to run a build. It built and runs nicely, however there is some severe battery drain compared to what I was used to on CM12.1.
I could upload a build tomorrow, if wanted.

Besides that, it seems like AICP is the only other thing going, right?.
Did you try aicp yet? Might look into what they did later.

I hope the camera will work properly, but I understand this won't be possible without Sony's collaboration.
Sadly, the latest update of blobs didn't include something useful for us
 

hahnjo

Senior Member
Mar 27, 2012
124
252
0
www.hahnjo.de
Thank you very much. I also don't have much time right now, but I managed to run a build. It built and runs nicely, however there is some severe battery drain compared to what I was used to on CM12.1.
I was successful here, too. I think I have also found the kernel bug in dwc3 so that the wake lock is correctly released after unplugging (will submit a Pull Request today). Together with the fix in https://github.com/SuperLamic/android_device_sony_rhine-common, my phone enters deep sleep. Will give it a few days before I report on battery usage though :eek:

Edit: Looks like David Viteri also found it: https://github.com/sonyxperiadev/kernel/pull/1130
 
Last edited:

derf elot

Senior Member
May 7, 2011
817
1,706
0
Unfortunately, even with deep sleep working, I always got fairly bad battery life. For me, just leaving phone on airplane mode with mobile, WiFi, BT, ncf all off, battery is drained after 2-3 days. And I couldn't figure out what was causing this.