• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Project Treble for Xperia XZ [F8331/2] [Pie 9.0] [no repartitioning]

Search This thread

Stronger1101

Senior Member
Sep 28, 2012
367
59
Bogota
OnePlus 7T
Hi guys

I cant use the hands-free bluetooth for attend or realize calls.

I make a clear installation then of flash firmware stock 192, flash all the odm existing, and I tried with and without pico gapps

Actually I'm use the 25-05-19 compilation but this problem is pressent in this rom and omni rom.

Is importan keep clear which my device bluetooth work perfectly in stock rom and other devices, my hands-free are a QY8 Bluetooth 4.1 and have Apx support.

Anybody have any idea?
 

Attachments

  • PicsArt_05-25-09.44.58.png
    PicsArt_05-25-09.44.58.png
    155.2 KB · Views: 171

LoaderFabi

Senior Member
There are a few bugs, and lately - with encryption enabled, but maybe also without - some unexplained reboots.
I would recommend you use OmniROM for stability since I cannot test all my builds extensively myself.

Doesn't seem like a too big issue to me tho...

I give the person i maintain the XZ for a temporal replacement and try both a bit.
 

oguzbatu

Senior Member
Oct 29, 2015
299
84
İstanbul
Hi guys

I cant use the hands-free bluetooth for attend or realize calls.

I make a clear installation then of flash firmware stock 192, flash all the odm existing, and I tried with and without pico gapps

Actually I'm use the 25-05-19 compilation but this problem is pressent in this rom and omni rom.

Is importan keep clear which my device bluetooth work perfectly in stock rom and other devices, my hands-free are a QY8 Bluetooth 4.1 and have Apx support.

Anybody have any idea?
Why do you flash odm images? Just install the zip via TWRP and chose a gsi of your choice or just move on with the AOSP provided with the zip. If there is still a problem then start a logcat and reproduce your error and send it to the dev.
 

local__hero

Senior Member
Oct 13, 2018
116
263
I cant use the hands-free bluetooth for attend or realize calls.
I make a clear installation then of flash firmware stock 192, flash all the odm existing, and I tried with and without pico gapps
Actually I'm use the 25-05-19 compilation but this problem is pressent in this rom and omni rom.
Is importan keep clear which my device bluetooth work perfectly in stock rom and other devices, my hands-free are a QY8 Bluetooth 4.1 and have Apx support.
I'm a bit puzzled as to why this keeps happening to you. I have confirmed time and time again that bluetooth calling works perfectly, also with an aptX device.
Please post the output of this as root:
Code:
ls -laZ /dsp/
And give us a complete logcat and dmesg from boot until and including when you make the call with a bluetooth headset connected.
Please do that on a clean flash(no apps, no GApps, no nothing, only Magisk to get root dmesg).
 

drater2

Senior Member
Nov 22, 2018
64
6
Sony Xperia XZ Premium
the provided standard image boots just fine. Resurrection Remix seems to be stuck in boot sequence. I just flashed the modified twrp, flashed the rom through twrp and the RR image. What did I do wrong:crying:
 

Stronger1101

Senior Member
Sep 28, 2012
367
59
Bogota
OnePlus 7T
I'm a bit puzzled as to why this keeps happening to you. I have confirmed time and time again that bluetooth calling works perfectly, also with an aptX device.
Please post the output of this as root:

And give us a complete logcat and dmesg from boot until and including when you make the call with a bluetooth headset connected.
Please do that on a clean flash(no apps, no GApps, no nothing, only Magisk to get root dmesg).

Hi

Sorry for the delay

You let me share the images and the logcat here or I send you them to pm?
 
Last edited:

local__hero

Senior Member
Oct 13, 2018
116
263
I don't understand what which you want tell with "redact imei"
You referred to edit the log for erase imei? I search in the log but I did not find it.
Write down your IMEI, then search the log for it before uploading. If you find the IMEI text, delete it from the log, then upload the edited log.

You don't have to delete your IMEI from the log of course, but if you accidentally share your IMEI, people can do all sorts of bad stuff with it.
 
  • Like
Reactions: Stronger1101

Stronger1101

Senior Member
Sep 28, 2012
367
59
Bogota
OnePlus 7T
Write down your IMEI, then search the log for it before uploading. If you find the IMEI text, delete it from the log, then upload the edited log.

You don't have to delete your IMEI from the log of course, but if you accidentally share your IMEI, people can do all sorts of bad stuff with it.

Thank for the explanation.

I already shared the log of my device running AOSP compilation of 25-05-2019, I hope it is useful and can help me know what is causing the problem with my bluetooth.

I initialize the capture of logcat as soon it was possible to run the coman in of pc wile my device boot, did a call of 10 second aproximatelly and the audio reproduced in internal speaker although which my hands-free is it connected, after of finish the call, I disconnect and connect my hands_free and did other call, this time the audio don't reproduce in any place

The audio of voice notes or other fonts as player apps and youtube they reproduce normally, this only ocurred in the calls

The link of log
https://del.dog/lsuarez
 
Last edited:

Stronger1101

Senior Member
Sep 28, 2012
367
59
Bogota
OnePlus 7T
Write down your IMEI, then search the log for it before uploading. If you find the IMEI text, delete it from the log, then upload the edited log.

You don't have to delete your IMEI from the log of course, but if you accidentally share your IMEI, people can do all sorts of bad stuff with it.

Other fail which I'm experiencing sometimes

When my device entering in lock mode, when I try unlock, it restarts without reason

Here is the log just before of restaring.
https://del.dog/lsuarez_autoreboot.pl
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Project Treble for Xperia XZ

    Hey everyone,
    before the year ends, I have something quite neat for you. With this project, you can run (almost) any Generic System Image(GSI) on your Xperia XZ. This means you can test LineageOS, Havoc, Pixel Experience...

    No repartitioning necessary! This method is re-using the oem partition.

    What is Project Treble?
    Understanding Project Treble and Android updates
    Talkin’ Treble: How Android engineers are winning the war on fragmentation
    What are GSIs?
    Android Source: Generic System Image (GSI)

    Downloads:

    How to install:
    • Back up your stuff
    • Wipe data and caches
    • Install the zip via TWRP (or unzip and install just the /boot and /vendor images via fastboot)
    • Install any GSI via "fastboot flash system your-gsi-image.img"
    • Fix /dsp labels: See DSP file relabeling for SODP
    • To use Magisk: Flash twrp-kagura-oem-to-vendor.img as recovery. Reboot into recovery and install Magisk like you usually would. If you want to go back to another ROM, you need to re-flash your old TWRP recovery as well.

    Bugs: See post #2

    DO NOT POST HERE FOR FLASHING HELP OR YOU WILL BE REPORTED. Read everything before posting.​

    If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread

    List of GSIs: phhusson's treble Generic System Image
    Important: You need an A-Only, ARM64 GSI!
    GSIs based on phhusson's work offer the best compatibility.

    Magisk: For Magisk to work, you need to tweak your TWRP installation, since it doesn't know that we have shuffled /vendor to the oem partition. You need to change /oem to /vendor in TWRP's fstab file.
    See above for a tweaked TWRP.

    If you want to go back to any other AOSP-based ROM that is not a GSI, simply re-flash the regular oem image and install like you usually would.

    For developers:
    This method is repurposing the oem partition to hold /vendor and odm(blobs). There's 400mb of space on that partition and we are only using ~260mb for blobs, while vendor is only about 20-30mb.
    Re-partitioning can be quite dangerous if you do not know what you are doing. This method should be safe for everyone.

    I'll put up the sources shortly. They're based on the regular AOSP builds but need a few tweaks for compatibility.
    Update: Sources are up now.

    You need to tweak the following:
    • Kernel dtsi to disable "odm" and load /vendor from "bootdevice/by-name/oem"
    • PlatformConfig on tone
    • device-sony-common:
      adreno-symlinks branch
      symlink from /vendor/odm/lib to /vendor/lib instead of from /odm/lib: Extra symlinks for build.prop and radio (aosp already symlinks /odm to /vendor/odm, but it omits build.prop and our radio folder)
      Misc fixes
      PRODUCT_FULL_TREBLE_OVERRIDE needs to be "true"
    • device-sony-tone: treble fixes:
      Mount oem as /vendor in fstab
      "TARGET_COPY_OUT_VENDOR := vendor" needs to be set
      Set VNDK versions, and override properties that get set because the build system is made to believe our XZ shipped with Oreo
    • device/sony/odm with odm files
      Unpack the oem blobs under device/sony/odm/odm and follow the README in device/sony/odm/README.
    • We need to put the odm files("blobs") somewhere. They get symlinked from /vendor/odm to /odm; both locations need to be accessible.
    • sepolicy: Use the broad-updates branch (it's kinda hack-ish now because /odm/pm-service is using /dev/binder, which messes with sepolicy). Sepolicy is on permissive for these builds because of that issue.

    Tested:
    • AOSP Extended (calling works, bluetooth may crash)
    • Havoc (no calling, bluetooth may crash)
    • Camera should work everywhere

    Bugs are the same as the regular AOSP builds, plus some more if the GSI is not built well or doesn't have tweaks for Sony devices.

    Happy holidays, I hope you have fun with this!

    XDA:DevDB Information
    Project Treble for Xperia XZ F8331/2, ROM for the Sony Xperia XZ

    Contributors
    local__hero
    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: .184 or later stock firmware
    Based On: AOSP

    Version Information
    Status: Nightly

    Created 2018-12-30
    Last Updated 2018-12-30
    3
    Flash rom without before flash odm? According I know is necessary flash always the binaries.
    I'm wrong?
    Treble overwrites oem with vendor you don't need flash oem while installing Treble.
    2
    Reserved

    Reporting bugs

    Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.

    DO NOT REPORT ISSUES WITH GSIs! Ask the GSI maintainer to fix them!

    I will repeat the rules again here:

    Rules:
    • New bugs must include version where error popped up and which oem version you are using
    • Only reproducible errors
    • Should include adb logcat (linked in a pastebin service like https://del.dog)
    • Must include clear description what is wrong
    • If it is a visual/SystemUI bug, only report it here
    • If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
    • Always try to fix the bug yourself first! Then submit a pull request to Sony
    • Must search if error has already been reported (bug tracker, this document, dev buglist)
    • If you've reported the issue somewhere else already and just want to track it here as well, add a link
    • Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
    2
    Hi,
    can you explain how to install and make functional magisk ?
    thanks