yashsingh1/xdaforums huggingface dataset:
[Xperia Z4/Z3+ Original Android Development] joebusch67:
Is there any possibility to get the stock camera working in this nice Rom?:)
[Xperia Z4/Z3+ Original Android Development] kgalv419:
Thank you will see what i can work with for that issue.
[Xperia Z4/Z3+ Original Android Development] yawo76:
EXPERIENCING STATUS 7 ERROR ON SINGLE SIM VERSION DESPITE REMOVING ASSERT LINE

Hi all,

I have tried several times to install this rom on my Z3+ Single sim version but experiencing the usual error 7 updater problem. Followed the link to the tutorial dealing with this issue by removing the assert line and rezipping it. But I keep getting no META-INF detected.

In short what exactly needs to be done to solve the error 7 issue for the single sim version.

Thanks in advance for your help.
[Xperia Z4/Z3+ Original Android Development] nailyk:
Post your /tmp/recovery.log after attempt to flash.

Error 7 can be lot of things.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Try with newer TWRP build here https://xdaforums.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050
[Xperia Z4/Z3+ Original Android Development] yawo76:
Recovery log attached

Hi,

Find attached the Recovery log.

thanks
[Xperia Z4/Z3+ Original Android Development] yawo76:
Have already tried it. Same problem, error 7 updater issue.

Thanks for the suggestion though.
[Xperia Z4/Z3+ Original Android Development] nailyk:
Relevant parts:

Not backing up files from incompatible version: 14.1
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
[B]You have an installed system that isn't signed with this build's key, aborting...
[/B]run_program: child exited with status 124
[B]script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
[/B]Can't install this package on top of incompatible data. Please try another package or run a factory reset

I don't know what your precedent rom is but I highly recommend you full backup (twrp don't backup your internal storage), full wipe, then flash again. Also disable zip signature check.
[Xperia Z4/Z3+ Original Android Development] yawo76:
Ok, thanks will do the above and report back though I have encountered the error 7 problem even with full wipe.
[Xperia Z4/Z3+ Original Android Development] nailyk:
If you encounter error 7 again read the /tmp/recovery.log (last ~15 lines) to check what exact error it is.

Here the most important one is the signature error. Don't know why you get this but maybe rom dev will have more ideas on this.
[Xperia Z4/Z3+ Original Android Development] Master-Master:
error 7 too
[Xperia Z4/Z3+ Original Android Development] yawo76:
Full wipe this time did the trick. Installed with no errors. Also think TWRP 3.1.0 is better option compared to 3.0.2 version.

Thanks :):o

---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------

Refer to my previous post, shd work for you too. All the best.
[Xperia Z4/Z3+ Original Android Development] Master-Master:
how to find twrp 3.1.0?plz give a link to us.thanks
[Xperia Z4/Z3+ Original Android Development] yawo76:
Find below the link. Cheers!!!

https://xdaforums.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050
[Xperia Z4/Z3+ Original Android Development] Olivier:
A new build (lineage-14.1-20170415-UNOFFICIAL-ivy.zip) is up!

Changelog:

- Merged 32.3.A.2.33 kernel and blobs

- Merged latest CAF upstream in the kernel (LA.BF64.1.2.3_rb1.11)

- Switched back to the Gello browser

- Updated the bcmdhd (WiFi) driver to version 1.71.21

- Android 7.1.2
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
ASK

i have a few questions about lineage os?

1. Lineage os vs default rom, if compare the camera which one better

2. if using lineage os more cooler than using default rom?

3. last thing is, im ex xiaomi users. when i want to change from default rom to lineage os, i should unlock bootloader then install twrp then install the rom? this step is right?

thanks dude if someone reply my questions and i really apreciate that
[Xperia Z4/Z3+ Original Android Development] AtlasRedux:
1. Since you lose your DRM keys, the default is better. You can't use Sony's special features. You can however back them up, search for information on how to do so. When they're lost, they're lost for good and you can never get them back. Not even by reinstalling stock rom.

2. What is "cooler" is up to you. If you mean heat-issues, there's nothing you can do. The chip is terrible that way. It's the same. You can trade performance for cooling, but that's it.

3. Yes. That's the steps.
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
thanks sir, may you give an opinion for me.

i use z3+ for daily use like : line, whatsapp, instagram, camera, watching video should i install lineage os or default rom? thanks before

2. thanks but can i reduce heat-issues, i ever read about xiaomi mi4i (using snapdragon 615 28nm basically same with 810, they have crayon mod thermal config to reduce 2-5 degrees celcius) or underclock the cpu's using tasker or etc

thanks sir
[Xperia Z4/Z3+ Original Android Development] AtlasRedux:
You can lower the CPU clock speed I guess, but I don't really see the point. The heat isn't really a problem, it doesn't damage anything.

In my opinion, the camera quality is unnoticably worse. Only thing I can really BARELY see, is a difference in noise reduction. That's all. I honestly didn't even notice a difference before I was told to look for it. I think it looks just fine and there's always options to use different camera-apps with software filters (though probably not AS good as Sony's own)

If you back up your DRM keys correctly, you can always return to stock if you don't like it.

When it comes to SPEED, LineageOS is MUUUUUUUUUUCH faster than Sony's stock ROM.

Also, updating it is stupidly easy after you've first installed it. I flash nightlies all the time. Absolutely wonderful ROM.
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
thanks you sirrrrrr
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
Hi

Sound quality problem been fixed?
[Xperia Z4/Z3+ Original Android Development] prosnz:
The kind of changelog I really enjoy. Thanks!
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
may you tell us the setting?
[Xperia Z4/Z3+ Original Android Development] prosnz:
CPU : Big - 768

Little - 864

Gpu : 450
[Xperia Z4/Z3+ Original Android Development] Master-Master:
its not working for me,i flashed it but in my twrp wrote version 3.0.2!why?

---------- Post added at 12:56 PM ---------- Previous post was at 12:54 PM ----------

its not working for me,i flashed it but in my twrp wrote version 3.0.2!why?
[Xperia Z4/Z3+ Original Android Development] yawo76:
To get TWRP 3.1.0 to work, you need to turn off the phone, wait for a few seconds and press power and volume down at the same time, wait till it boots into 3.1.0
[Xperia Z4/Z3+ Original Android Development] Master-Master:
its very good and smooth but battery is not very good at all
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
how about the camera, if compare using stock

---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------

how about the camera, if compare using stock. example if stock nougat 8 from 10 lineage 9 from 10 and bla bla
[Xperia Z4/Z3+ Original Android Development] Master-Master:
camera?looooooooooooooool camera

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

ok thanks i will give it a try
[Xperia Z4/Z3+ Original Android Development] achmthidyt:
why lol cuz i dont understand?
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
A fix was just committed for bluetooth audio calls! whoohoo! waiting for new build.
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
Sound quality problem been fixed?
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
I confirmed, yess its fixed nomore low-sound latest build
[Xperia Z4/Z3+ Original Android Development] Olivier:
Already included in the latest build - works for me now (forgot to announce it here).
[Xperia Z4/Z3+ Original Android Development] HaveAboy:
Muffled sound

Hi guys!

I created an account just for this little problem, i have the latest build, but from the beginning i've experienced this muffled sound on my earphones, I solved this by using a soundfix zip from another site, it just boosted the volume but worked perfectly. On this latest build 20170417 the sound is good, very loud and clear on the phone speakers but on the earphones and other headphones that i have sounds too much reverberated like if i'm listening through a window. Si i flashed the zip and the sound Is just too loud from the speakers that i feared they would break so i went backt to LOS stock . I don't know if there it Is a fix for this i've been searching on this site and Google but i cant find a solution. I hope you guys can help me, and sorry for the long post.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Error try to flashing 17/04/17 build , anyone??
[Xperia Z4/Z3+ Original Android Development] nailyk:
Post /tmp/recovery.log it will contain the real error.
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
Check your recovery version

You should flash this recovery

https://dl.olivierk.at/ivy/twrp/
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
I wanted flash again. But I encountered error7

Why?
[Xperia Z4/Z3+ Original Android Development] Olivier:
1) Can you run the following command and post the output?

strings /dev/block/bootdevice/by-name/tz | grep QC_IMAGE_VERSION_STRING

2) What FTF (version) did you flash the last time?

3) Can you boot to recovery by holding the 'volume down' button (and power, obviously) pressed?
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
1) i cant now

2) 2.33

3) im going to the recovery with volume down button
[Xperia Z4/Z3+ Original Android Development] Olivier:
That's the most important part - can't really help you without knowing your TZ version.
[Xperia Z4/Z3+ Original Android Development] yawo76:
Hi Olivier,

I'm facing the same TZ error problem. Attached is my recovery log.

Thanks
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
[MENTION=1110614]olivierk[/MENTION] trying to build rom but some error happened can you please share me how to do right after succesfully synced cm 14.1 but failed when i start to breakfast ivy, brunch ivy?? Did i missed adding some repo/stuff??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
breakfast lineage_ivy-userdebug

But you will need to add a repo to get vendor blobs by hand to local_manifests otherwise it will fail to build.

https://github.com/TheMuppets/proprietary_vendor_sony

Note: It is a big repo ~1.5 GB
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Someone told me to do that, but i didn' do that, ive synced repo for 3times yess its arround 45Gb, reinstalled ubuntu for 3 times too just curious why i always gimme error, and discmman55 do you have hangouts/telegram so easier to reach and ask you about this stuff??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
you gotta post at least last few pages of build log for anyone to be able to help you. what is error ? There are hundred million things that can go wrong, we don't know which one to help you...
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Im trying to do so, i started read lineage wiki on how&needed things, and post here https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763/post71926048 but just get confused what things to do after synced cm14.1 repo, i know something needs to added repo,patces but don't know which source,and how to added some missing repo
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
The problem is build 170417

Im flash 170416 build, without problem & error
[Xperia Z4/Z3+ Original Android Development] nosiobadx:
Olivier, is it too much to ask, zacharias.maladroit is searching for a current developer for Z3+ and I believe you're the only developer currently working for this crappy phone, we will appreciate if you can develop something together.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
still error here
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Post the output of "repo manifest" command (without quotes). Run it in device tree. It looks like you have Sony ivy repo twice. It should be only in device/sony/ivy but it is present duplicated in android_device_sony_ivy. Look for duplicate in local_manifests. When you do breakfast it creates a roomservice.xml in local_manifests with device repo and dependencies in the right paths. I think the only repo you need to add by hand is the muppets. It's path should be vendor/device/sony. You can guess path from repo name that's why nobody writes it. Example android_device_sony_ivy goes in device/sony/ivy. It's a kind of convention for developers to name repos similar to the path in the tree where they should go (path attribute in project tag in manifest xml file)
[Xperia Z4/Z3+ Original Android Development] nailyk:
like [MENTION=4522003]DiscMan55[/MENTION] said you have a duplicate repo. Read the wiki about local_manifest. The cyanogenmod wiki version on archive.org is good too.
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
I can't enable encryption on a ROM I built from this sources. There's a selinux problem. I got a logcat from eng build:

06-02 17:02:10.869 489 489 W vold : type=1400 audit(0.0:2712): avc: denied { read } for name="u:object_r:tee_prop:s0" dev="tmpfs" ino=12000 scontext=u:r:vold:s0 tcontext=u:object_r:tee_prop:s0 tclass=file permissive=0
06-02 17:02:10.979 364 489 E libc : Access denied finding property "sys.keymaster.loaded"

I checked in adb shell. qseecomd is loaded and sys.keymaster.loaded = true, so it seems the only problem is proper selinux label or grant.

and it loops like that for infinity, had to reformat /data in TWRP to stop it.
[Xperia Z4/Z3+ Original Android Development] nailyk:
We have almost the same problem on shinano. Disable hardware encrypt for now solve it. (BoardConfig flag)
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Ah you're right, as part of my BoardConfig.mk changes for TWRP, I enabled and got TARGET_HW_DISK_ENCRYPTION working. I built from my sources so that flag was applied by LineageOS as well.

I fixed it there, I will try to fix it here.
[Xperia Z4/Z3+ Original Android Development] nailyk:
Please keep me informed :)

Right now am stuck at qcom err = -22 (into blob logs) which also seems related to that prop. The only 'relevant' post I found about this is the [MENTION=912474]Dees_Troy[/MENTION] one on google + about bacon encryption (really good post btw).
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
[MENTION=4522003]DiscMan55[/MENTION] i've restarted anything from scratch, and wihout add any external sources at all (just type brunch ivy) its running and loaded but it has too many Warning here, is that okay or???

its still running till i post here
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
It's working now. The warnings are normal. If you didn't add TheMuppets repo, it will reach a point and fail complaining about certain files not having a target.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
So its a must thing to add, themuppets sources??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Yes, phone won't work without vendor firmware blobs which are in themuppets repo. alternative is to pull them yourself, but that's difficult and annoying (the full list is in device/sony/ivy/proprietary-files.txt)

So just adding themuppets will put all that is needed.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Last time ive tried it gimme the 1s error, doubled sync, will that happened again, at the 1st one when i clone the sources : some folder added inside the working directory ( ~/android/lineage/ <here> ) is it the correct directory??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
You are not supposed to clone themuppets repo yourself, you're supposed to create an xml file in local_manifests and add the repo there with correct path vendor/sony and then do repo sync.

In fact, this tree is easier than normal because it is added in LineageOS official group on github so it works directly with brunch and has proper lineage.dependencies file in each project so breakfast can go and make the manifest for you (it makes roomservice.xml file automatically). For other devices you have to find out what the needed repos are and write a manifest by hand.

Read the local_manifest cookbook on xda university http://xda-university.com/as-a-developer/local_manifests-cookbook

ie: something like this (actually I use olivier97 fork of themuppets now because he added updated blobs from latest april sony security update for z3+):

<manifest>
<project name="olivier97/proprietary_vendor_sony" path="vendor/sony"/>
</manifest>

If you don't understand how repo works and how manifests work you have no hope of making this work or troubleshooting any problems. Sorry if I was not clear enough.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Thats pretty clear mate this what i looking for after 4-times try this what i believe as a missing pieces, damn its harder than i thought, i've no computer background at all, atleast i'm trying right now

---------- Post added at 05:59 PM ---------- Previous post was at 05:49 PM ----------

This thing i don't understand how, where do you create this xml i mean the string ?
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
This one
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
In .repo you create a folder called local_manifests

inside local_manifests you make a file with any name .xml

See this guide that explains repo: http://xda-university.com/as-a-developer/repo-tips-tricks
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
How yo get this its for device tree repo right

So to add the kernell lsource to local manifest i must type the string like tis one :

<manifest>

<project name="olivier97/android_kernel_sony_msm8994"

Path="kernel/sony"/>

<manifest>

???this part that make me confuse
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
If the string on manifeat xml based on the gith sources should that your missing /wrong since i saw on the gith of this cm sources was look like this

....proprietary_vendor_sony_ivy" you mised " _ivy "
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
[MENTION=6979267]nailyk[/MENTION]

I found that the selinux label for properties are defined in property_contexts files in the tree. For Sony Z3+, I found that it is actually in device/sony/kitakami-common/sepolicy/property_contexts (which is from the LineageOS/android_device_sony_kitakami-common)

It contains:

sys.keymaster.loaded u:object_r:tee_prop:s0
sys.listeners.registered u:object_r:tee_prop:s0
persist.sys.timeadjust u:object_r:timekeep_prop:s0
persist.service.bdroid.bdaddr u:object_r:bluetooth_prop:s0
persist.tareset.notfirstboot u:object_r:ta_prop:s0

The selinux error was saying that vold was running in context: u:r:vold:s0

So I used audit2allow and it generated the following rule:

allow vold tee_prop:file read;

So I should make a .te file and put it where they are included (what a pain to fork kitakami-common :( )

Maybe there is an official gerrit patch, I'll look there. I need to figure out if this will make a security hole or not. I guess 'tee' stands for Trusted Execution Environment (The word used by Qualcomm for their trustzone implementation).

[MENTION=5813857]SH1M4BD3[/MENTION]

"_ivy" is not present in the repo I mentioned because there is an "ivy" folder inside it, so when repo sync clones the github repo to the path vendor/sony, vendor/sony/ivy will exist inside it!
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
[MENTION=4522003]DiscMan55[/MENTION] so i need to create local_manifest.xml now im in ~android/lineage, the question is where i put this local_manifest.xml inside .repo or .repo/local_manifest/ ??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
The folder to put local manifest files is in .repo/local_manifests/

The file name can be local_manifest.xml or any other name like vendor_blobs.xml
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
Is there anything else to add like this cm devic-tree/kernell sorces are needed to add them to??
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Just try to build... you will get error if something is missing.
[Xperia Z4/Z3+ Original Android Development] sinivalas23:
Speaking of Sony security updates, any idea if the latest builds are vulnerable to the recent Project Zero Broadcom exploit? Looks like the current Broadcom firmwares are dated 2016-11-11.
[Xperia Z4/Z3+ Original Android Development] SH1M4BD3:
am adding local_manifest as you told me above, re-sync again start to brunch ivy , there still warning appeared here
[Xperia Z4/Z3+ Original Android Development] prosnz:
[MENTION=5813857]SH1M4BD3[/MENTION]

Is all this stuff related to the thread...?
[Xperia Z4/Z3+ Original Android Development] Olivier:
To those getting the "TZ error" while flashing the ROM: This is supposed to happen. If you want to be on the safe side, update to the latest FTF available, then flash this ROM again (remember to make backups).

Why?

Only recent versions of the bootloader have the recovery mode enabled (hence, no recovery ramdisk inside the actual boot ramdisk is required). If your bootloader is too old, you shoudn't flash this ROM, since you'd probably end up without a recovery. Sure, you can go and remove the assert, but do so at your own risk.

If you are sure your bootloader is new enough, meaning you can boot to recovery by holding the volume down button pressed while powering the phone on, please run the following command (and mention the last flashed FTF/stock ROM):

strings /dev/block/bootdevice/by-name/tz | grep QC_IMAGE_VERSION_STRING
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
[MENTION=4329876]Olivier[/MENTION]

QC_IMAGE_VERSION_STRING=TZ.BF.3.0.R1-80677

Flashed FTF: E6533_32.3.A.2.33_1294-9721_R3D.ftf
[Xperia Z4/Z3+ Original Android Development] nailyk:
Funny enough, we got the exact same problems. Thanks for the selinux tricks I will try asap. Are vold policies change the only need to get hw encryption?

Yes our device doesn't support FBE. AFAICT it is because tzapps which doesn't support it.

I think you are on the right way to get ril again. On shinano we had the same problem. After reboot with encryption ril was broken so stop/start almost every service to adjust init files. It seems that the critical one are rild, netmgrd, and ims* for our ril. Also we got some 'unrestartable' services. If they start with minimal framework, restarting this service with normal framework had no effect (netmgrd iirc): Patch1 patch2.

Another trick: build and replace adb binary for an unsecured one (rgrep "ro.adb.secure\|ro.secure" into vendor/cm & build, replace values with 0) and you will have adb before the framework restart. Maybe you can lsof /data to gather some information. (logcat at this time was really useful for me as it help me to get what services where started as they shouldn't).

To prevent you for some hard search here are the 4 ways to start a service:

late_start: Only after decrypt,

main: Restarted at framework change,

core: Started with minimal fmwk, not restarted after decrypt,

disabled: Started with a trigger. (If a service is disabled, class is useless).

Class need to be the line right after the service. If not, the default value is used: main.
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
Hi guys

Headphone sound quality problem been fixed now?

In last build
[Xperia Z4/Z3+ Original Android Development] Olivier:
Can you boot to recovery (volume down + power)?
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Yes. Works fine.
[Xperia Z4/Z3+ Original Android Development] UriahNazarian:
Please answer me
[Xperia Z4/Z3+ Original Android Development] prosnz:
It's fine here.