Database Develop

[Q] Porting ROM to Xperia Z

Hi,
I'm trying to port AOSPA to the Xperia Z ... for my own usage, but I'd also share it to the community.
I've never done this before and after days of trying and editing files I'm getting a bit tired at the moment.
It would be great if someone could help me to get into it. All Porting Guides are different and most of them are using already precompiled files.
At the moment I get the error
Code:
Traceback (most recent call last):
File "../../base/android/jni_generator/jni_generator.py", line 1065, in <module>
sys.exit(main(sys.argv))
File "../../base/android/jni_generator/jni_generator.py", line 1061, in main
options.optimize_generation)
File "../../base/android/jni_generator/jni_generator.py", line 996, in GenerateJNIHeader
jni_from_javap = JNIFromJavaP.CreateFromClass(input_file, namespace)
File "../../base/android/jni_generator/jni_generator.py", line 507, in CreateFromClass
stderr=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 709, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1326, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [/home/pa/git/aospa/out/target/product/c6603/obj/GYP/shared_intermediates/ui/gl/jni/Surface_jni.h] Fehler 1
make: *** Warte auf noch nicht beendete Prozesse...
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Is this helpful? I can provide some more information if needed.
Some of the steps I did so far:
repo init -u git://github.com/AOSPA/manifest.git -b kitkat
repo sync -j48
Followed this Guide to add Sony BLOBS and edited '.repo/local_manifests/sonyxperiadev.xml' to the following (Deleted some 'remove-project' lines because they have been not present)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="sony" fetch="git://github.com/sonyxperiadev/" />
<remove-project name="platform/hardware/invensense" />
<remove-project name="platform/hardware/akm" />
<project path="device/sony/lagan" name="device-sony-lagan" groups="device" remote="sony" revision="master" />
<project path="device/sony/c6603" name="device-sony-c6603" groups="device" remote="sony" revision="master" />
<project path="device/sony/sgp321" name="device-sony-sgp321" groups="device" remote="sony" revision="master" />
<project path="vendor/sony/dash" name="DASH.git" groups="device" revision="master" remote="sony" />
</manifest>
I also commented the following lines from 'device/sony/c6603/full_c6603.mk'
Code:
#TARGET_PREBUILT_KERNEL ?= kernel
#PRODUCT_COPY_FILES += $(LOCAL_PATH)/$(TARGET_PREBUILT_KERNEL):kernel
Compiling did not work with this lines. So i tried it without kernel. My idea would be to add other kernel sources like cm11 kernel. For my understanding this would mean, that I have to add 'device/sony/c6603/kernel' folder and insert the files from 'github.com/CyanogenMod/android_kernel_sony_apq8064/tree/cm-11.0'. After that I would edit the commented lines to
Code:
TARGET_KERNEL_SOURCE ?= kernel
PRODUCT_COPY_FILES += $(LOCAL_PATH)/$(TARGET_KERNEL_SOURCE):kernel
And uncomment them. Is this correct?
After that I copied 'vendor/pa/products/pa_mako.mk' to 'vendor/pa/products/pa_yuga.mk' and edited it to the following:
Code:
# Copyright (C) 2013 ParanoidAndroid Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Check for target product
ifeq (pa_yuga,$(TARGET_PRODUCT))
# Define PA bootanimation size
PARANOID_BOOTANIMATION_NAME := XHDPI
# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_xhdpi
# Build paprefs from sources
PREFS_FROM_SOURCE ?= true
# Include ParanoidAndroid common configuration
include vendor/pa/main.mk
# Inherit AOSP device configuration
$(call inherit-product, device/sony/c6603/full_c6603.mk)
# Override AOSP build properties
PRODUCT_NAME := pa_yuga
PRODUCT_BRAND := Sony
PRODUCT_MODEL := C6603
PRODUCT_MANUFACTURER := Sony
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=yuga BUILD_FINGERPRINT="Sony/C6603_1270-6697/C6603:42.2/10.3.A.0.423/WP5_rg:user/release-keys" PRIVATE_BUILD_DESC="C6603-user 4.2.2 10.3.A.0.423 WP5_rg test-keys"
endif
Now I added
Code:
add_lunch_combo pa_yuga-userdebug
to 'vendor/pa/vendorsetup.sh'
using make -j8 gives me:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4
TARGET_PRODUCT=pa_yuga
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
[COLOR="Red"]TARGET_ARCH_VARIANT=armv7-a-neon[/COLOR]
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-13-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KRT16S
OUT_DIR=/home/pa/git/aospa/out
============================================
I think the red line should be a bit different?

[MOD] Volume Boost for i9506 ver. 4.3

This Mod is designed to increase the limit output volume of your Galaxy S4 i9506.
How to install:
1- Download the file of this post.
2- Download Root Browser in your S4 (need Root)
3- Open with Root Browser : System / etc / snd_soc_msm , place the file that you have downloaded here (and replace the existing file)
4- Set parameters to rw-r-r (permissions)
5- Finally, restart your device and... ready!
thanks to the user Cortisan to prepare our mod version. :good:
Tell me if it doesn´t work for you.

I ended up with Android OS upgrade "opening programs" and nothing happens... nandroid restore now.

[email protected] said:
I ended up with Android OS upgrade "opening programs" and nothing happens... nandroid restore now.
Click to expand...
Click to collapse
it should work for you. what version of Android have you got?
do you allow the permissions correctly?

pablogalanmusic said:
This Mod is designed to increase the limit output volume of your Galaxy S4 i9506.
How to install:
1- Download the file of this post.
2- Download Root Browser in your S4 (need Root)
3- Open with Root Browser : System / etc / snd_soc_msm , place the file that you have downloaded here (and replace the existing file)
4- Set parameters to rw-r-r (permissions)
5- Finally, restart your device and... ready!
thanks to the user Cortisan to prepare our mod version. :good:
Tell me if it doesn´t work for you.
Click to expand...
Click to collapse
don't work, I have needed to reinstall the rom and applications

Does it work for someone and does this work with the CM12 ROM's?

Doesn`t work on CM12 and had to restore backup. Useless thread. Using still Viper4Android.

Thanks, I'm going to try that then

kornelius1982 said:
Doesn`t work on CM12 and had to restore backup. Useless thread. Using still Viper4Android.
Click to expand...
Click to collapse
OMG, you were not joking, Viper4Android f**king rocks, I didn't know my phone was capable of such high quality audio even at an higher output (headphones), thank you so much for the suggestion

Can we do something to use it on lollipop?

You can use this diff on CM (/system/etc/mixer_paths.xml). The example below lowers from 84db(?) to 72.
Code:
--- mixer_paths-84.xml
+++ mixer_paths.xml
@@ -544,7 +544,7 @@
<path name="speaker">
<path name="spk" />
- <ctl name="RX7 Digital Volume" value="84" />
+ <ctl name="RX7 Digital Volume" value="72" />
<ctl name="SPK DRV Volume" value="7" />
<ctl name="COMP0 Switch" value="1" />
</path>
Optionally, a companion init.d script to patch the latest version after rom update.
Code:
#!/system/bin/sh
# Patching mixer_paths.xml (changing volume)
if [ ! -e /system/etc/.mixer_paths.xml_is_patched ]; then
mount -o remount,rw /system
cd /system/etc
patch mixer_paths.xml < /data/local/bin/mixer_paths.patch
if [ $? == 0 ]; then
touch .mixer_paths.xml_is_patched
else
touch .mixer_paths.xml_is_patched
touch .mixer_paths.xml_patching_error
fi
mount -o remount,ro /system
fi

[ROM][SNAPSHOT][6.0.1] CyanogenMod 13.0 for Xperia TX

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for CyanogenMod is available in the CyanogenMod GitHub repo.
And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Official CyanogenMod 13 Release post : http://www.cyanogenmod.org/blog/cm-13-0-release-1
Hayabusa CyanogenMod Wiki : https://wiki.cyanogenmod.org/w/Hayabusa_Info​
CyanogenMod 13.0 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3415827
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3418818
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3416938​
Downloads Links
CyanogenMod 13.0 (Unlocked Bootloader) :
Xperia TX (Hayabusa) : https://mega.nz/#F!L8cRRKiI!SzWmsKUyEdJgaMjB8ksxYw
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 6.0, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xperia-t-v/t-development/recovery-twrp-3-0-0-touch-recovery-t3319588
Useful alternatives to CM Updater (with Deltas) : CM Downloader on Play Store
About CyanogenMod : ChangeLog available on http://www.cmxlog.com/13/hayabusa/​
Unification of the user partitions into UserData
Read more about the UserData unification : https://wiki.cyanogenmod.org/w/Hayabusa_Info
Migrate to the one big partition for CM-13.0 :
- (Optional) Backup all your data, applications, internal storage, ...
- (Optional) If wished, do a full Nandroid backup from Recovery
- Flash the latest ROM zip of your device to start the unification
- Read and follow the instructions from the zip if anything goes wrong
- (Optional) Restore your Nandroid backup if you want to
- Flash the same ROM zip for CyanogenMod 13.0
Reverse the migration for older ROMs :
- (Optional) Backup all your data, applications, internal storage, ...
- Reboot to recovery and do a Factory reset (data will be lost)
- Flash restore_sdcard-YYYYMMDD-blue.zip
- Read and follow the instructions from the zip if anything goes wrong
- Flash the ROM you want now and restore your data​
Flashing and updating
CyanogenMod clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the CyanogenMod 13.0 ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod update / upgrade :
- (Information) Don't wipe anything unless you want to
- (BETA / UNOFFICIAL) Nothing to wipe when switching
- Flash the latest CyanogenMod 13.0 ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot​
About the builds
Device tree : https://github.com/CyanogenMod/android_device_sony_hayabusa/commits/cm-13.0
Common tree : https://github.com/CyanogenMod/android_device_sony_blue-common/commits/cm-13.0
Kernel sources : https://github.com/CyanogenMod/android_kernel_sony_msm8x60/commits/cm-13.0
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony/commits/cm-13.0​
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example​
Q&A - FAQ
CM-13.0 Hayabusa Regular Questions and Answers : Q&A Thread
About CM-13.0 : https://en.wikipedia.org/wiki/CyanogenMod
The CyanogenMod team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!​
CyanogenMod available for Hayabusa also thanks to :
- The CyanogenMod Team
- CodeZero and SdtBarbarossa for originally importing Huashan CM13 sources & confirming the revival was possible
- Everyone involved in working and testing​
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Sony Xperia T
Contributors
Adrian DC
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Snapshot
Current Stable Version: 20161220-SNAPSHOT
Current Beta Version: UNOFFICIAL
Created 2016-07-15
Last Updated 2017-03-20

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Dual Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently based on Huashan kernel
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok (with SONY design)
- Encryption : Status unknown
- SEPolicies : Fully enforced
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open CyanogenRecovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds

Reserved
Current status of the ROM Builds
Nightlies : Only once everything is considered working and stable.
Beta : When needed. Newest changes to test, full builds or kernels / packages to flash.
Current local manifest of the ROM build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/CyanogenMod/android -->
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" />
<project name="AdrianDC/android_device_sony_blue-common" path="device/sony/blue-common" remote="github" />
<project name="AdrianDC/android_device_sony_hayabusa" path="device/sony/hayabusa" remote="github" />
<project name="AdrianDC/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" />
<project name="AdrianDC/proprietary_vendor_sony" path="vendor/sony" remote="github" />
</manifest>

Many thanks for porting new CM to this old phone!

Beta? Let's test

A very important change will hit your devices upon next release.
Please do read here : http://forum.xda-developers.com/xpe...od-13-0-xperia-t-t3415827/page11#post67850287

test

Alright migration helpers finished, ready for public release !
Please read the details added to the main post about the process.
No help will be given if you do not want to read everything
I spent time writing & displaying on error during the flash processes.
Should you read everything correctly and follow all the instructions
given to you by all the securities embedded in my zips, and still have issues,
then maybe shall I and other consider helping you.
I'm not saying that to be mean but because this is meant to be performed totally autonomously,
and the details I gave on the first post and all instructions & warnings from the zip
have to be enough for the less experienced users who takes time to read,
since I will then be adding this all on the CM Wiki pages.
To upgrade, you'll need the zips for the unification mentioned in the OP,
the latest CM13 release for your device, and optionally, the latest TWRP release from today.

Thanks for updates! The zip file for user data unification works great. But there seems some UI issue for cm-13.0-20160722-UNOFFICIAL-hayabusa.zip. Tapping on the bottom part of the screen doesn't response properly, but triggers notification drop down menu.

cornpoppy said:
Thanks for updates! The zip file for user data unification works great. But there seems some UI issue for cm-13.0-20160722-UNOFFICIAL-hayabusa.zip. Tapping on the bottom part of the screen doesn't response properly, but triggers notification drop down menu.
Click to expand...
Click to collapse
CM failed commit, fixed last night.
I made a new release overnight.

About the sleep of death : So far, nothing relevant found or a certain way to reproduce it,
totally random & I must be the one who has it the less on the whole planet, which makes it even harder...
About the touchscreen issues in call : I think Xperia TX Hayabusa is not affected by that bug,
because its Clearpad touchscreen already has the support for the new system handling incall suspends,
however I might be wrong and it could not work properly, although it's very unlikely.
Please report on that just to confirm it's alright for Hayabusa too (In-call + proximity, touchscreen must be ignored).

@Adrian DC
Hey, so first of all, thanks for reviving this old phone. Was actually planning on testing, made backup, formatted data/caches/sdcard (ext4) inside TWRP, and tried flashing the unification zip file, I got the error
Code:
Device does not have a SDCard partition anymore
Unification unnecessary
Any ideas? Thanks
Edit:
I previously expanded my data partition according to this guide, don't know if that's relevant or not.

Go in TWRP and share the output of "adb shell /sbin/sgdisk —print /dev/block/mmcblk0".

Adrian DC said:
Go in TWRP and share the output of "adb shell /sbin/sgdisk —print /dev/block/mmcblk0".
Click to expand...
Click to collapse
Here you go, it would seem like the sdcard isn't labeled:
Code:
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 7423 1.5 MiB FFFF Boot
3 7424 10495 1.5 MiB FFFF Boot2
4 12288 53247 20.0 MiB FFFF Kernel
5 53248 55295 1024.0 KiB FFFF TZ
6 57344 63487 3.0 MiB FFFF modemst1
7 65536 71679 3.0 MiB FFFF modemst2
8 73728 79871 3.0 MiB FFFF fsg
9 79872 90111 5.0 MiB 8300 ramdump
10 90112 106495 8.0 MiB 8300 apps_log
11 106496 139263 16.0 MiB 8300 FOTAKernel
12 139264 2654207 1.2 GiB 8300 System
13 2654208 3166207 250.0 MiB 8300 Cache
14 3166208 9166015 2.9 GiB 0700 Userdata
15 9166016 30535646 10.2 GiB 0700
Update:
@Adrian DC, so I see your script checks for the partition name at one point, so that was the root of the error, probably something that wouldn't happen to many people; I most likely forgot to give that partition it's name, fixed using `parted` and it worked, rebooting now.

So flash worked, but Android only sees about 3gb of internal storage (the exact same amount that was allocated to the UserData partition originally), even though I can see it has the proper size:
Code:
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 7423 1.5 MiB FFFF Boot
3 7424 10495 1.5 MiB FFFF Boot2
4 12288 53247 20.0 MiB FFFF Kernel
5 53248 55295 1024.0 KiB FFFF TZ
6 57344 63487 3.0 MiB FFFF modemst1
7 65536 71679 3.0 MiB FFFF modemst2
8 73728 79871 3.0 MiB FFFF fsg
9 79872 90111 5.0 MiB 8300 ramdump
10 90112 106495 8.0 MiB 8300 apps_log
11 106496 139263 16.0 MiB 8300 FOTAKernel
12 139264 2654207 1.2 GiB 8300 System
13 2654208 3166207 250.0 MiB 8300 Cache
14 3166208 30535646 13.0 GiB 8300 Userdata
I can't see "internal storage" in TWRP, only "Legacy SDCard", and "Legacy SDCard" can't even be mounted.

Antiga Prime said:
So flash worked, but Android only sees about 3gb of internal storage (the exact same amount that was allocated to the UserData partition originally), even though I can see it has the proper size:
I can't see "internal storage" in TWRP, only "Legacy SDCard", and "Legacy SDCard" can't even be mounted.
Click to expand...
Click to collapse
Flash fix-userdata zip, format that new partition ...

dzadzev said:
Flash fix-userdata zip, format that new partition ...
Click to expand...
Click to collapse
Thanks, I was pretty sure I had done that through "parted" but, I guess I didn't. Did that through TWRP and all good!

Adrian DC said:
CM failed commit, fixed last night.
I made a new release overnight.
Click to expand...
Click to collapse
It works now. Many thanks!

Antiga Prime said:
@Adrian DC, so I see your script checks for the partition name at one point, so that was the root of the error, probably something that wouldn't happen to many people; I most likely forgot to give that partition it's name, fixed using `parted` and it worked, rebooting now.
Click to expand...
Click to collapse
Exactly, good job on understanding it all by yourself !
As you can see, my scripts will refuse to work if there is anything wrong on the device.
Also notice the fact that even if you had change the partitions sizes, everything will work.
To everyone : If you restore a backup, or fail to follow the instructions saying you have to Factory Reset,
and when required flash fix-userdata-YYYYMMDD-blue.zip, you won't see the full partition size.
Very important about all TX Users ! I need to know if one of you ever had a Sleep of Death !

New release 20160725 : Latest blue changes, latest CM changes.
Need confirmation Hayabusa never was concerned by sleep of deaths.

Magisk Module - Call Recording for EMUI 9 (PIE)

This module will enable call recording on EMUI 9.
Install the module with Magisk Manager, reboot and enjoy!
On devices with Call+ option enabled, there will be no "Record" icon in the Dialer screen, so you will have to enable Automatic Recording from Dialer - Settings.
Download link - > https://mega.nz/#!1s9FTQLI!BkXmo2jl9YhVkXqe0j-XgoqGPQFdmpBvJFwRrFy1BmI
Version 9.1 - This version will also disable Call+ (RCS) feature, so you can manually start call registration from Dialer (Registration Icon)
Link - > https://mega.nz/#!xpcTUAxB!sxUuj1NBmwWHnWycQJ9tO3dU43VZuyXouAIav5WqAFE
Version 9.2 - OAT folder removed as it doesn't seems to be required
Link - > https://mega.nz/#!oplFmKrY!ObM6MH34L5pPutRbyVNWPCqULXVOj4yMiq3ZDfxEI9g

Mirror link: https://www.dropbox.com/s/f4vctbexarno8zu/EMUI9_Call_Recording.zip

Pretoriano80 said:
This module will enable call recording on EMUI 9.
Install the module with Magisk Manager, reboot and enjoy!
On devices with Call+ option enabled, there will be no "Record" icon in the Dialer screen, so you will have to enable Automatic Recording from Dialer - Settings.
Download link - > https://mega.nz/#!1s9FTQLI!BkXmo2jl9YhVkXqe0j-XgoqGPQFdmpBvJFwRrFy1BmI
Version 9.1 - This version will also disable Call+ (RCS) feature, so you can manually start call registration from Dialer (Registration Icon)
Link - > https://mega.nz/#!xpcTUAxB!sxUuj1NBmwWHnWycQJ9tO3dU43VZuyXouAIav5WqAFE
Version 9.2 - OAT folder removed as it doesn't seems to be required
Link - > https://mega.nz/#!oplFmKrY!ObM6MH34L5pPutRbyVNWPCqULXVOj4yMiq3ZDfxEI9g
Click to expand...
Click to collapse
I made a copy from cust/hwcall recorder to system/app/call recorder, and it works, but have noticed that the recordings can't be accessed from the dialer, as before. Is there a fix?

Hello, is it possible that calls can be recorded at will?.
I'm not interested in recording absolutely everything, besides, you can edit a list of numbers but what about the numbers you do not have between the contacts?
Thank you and greetings.
Enviado desde mi BLA-L29 mediante Tapatalk

rey_lagarto said:
Hello, is it possible that calls can be recorded at will?.
I'm not interested in recording absolutely everything, besides, you can edit a list of numbers but what about the numbers you do not have between the contacts?
Thank you and greetings.
Enviado desde mi BLA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Just start the recording manually, from the dialer.

Need root
Or i can do it without root

The installation don't work (version 9.2, EMUI 9.0.1, STF-L09)
MAGISK LOG IS:
- Copying zip to temp directory
- Installing EMUI_Call_Recording_v9.2.zip
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: module.prop
inflating: config.sh
- Mounting /system, /vendor
/system/bin/mke2fs: invalid option -- t
*******************************
Call Recording For EMUI 9
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/adb/magisk_merge.img with size 64M
BusyBox v1.29.3-osm0sis (2018-11-17 02:42:59 AST) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
Create /data/adb/magisk_merge.img with size 64M
Cannot mount image!
! /data/adb/magisk_merge.img mount failed...
! Installation failed

gabryrizz02 said:
The installation don't work (version 9.2, EMUI 9.0.1, STF-L09)
MAGISK LOG IS:
- Copying zip to temp directory
- Installing EMUI_Call_Recording_v9.2.zip
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: module.prop
inflating: config.sh
- Mounting /system, /vendor
/system/bin/mke2fs: invalid option -- t
*******************************
Call Recording For EMUI 9
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/adb/magisk_merge.img with size 64M
BusyBox v1.29.3-osm0sis (2018-11-17 02:42:59 AST) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
Create /data/adb/magisk_merge.img with size 64M
Cannot mount image!
! /data/adb/magisk_merge.img mount failed...
! Installation failed
Click to expand...
Click to collapse
Dude, no need for magisk install. Just copy the file in the zip archive to /system/app and make proper permissions.

Can you tell how I have to do?

gabryrizz02 said:
Can you tell how I have to do?
Click to expand...
Click to collapse
First and obvious, you have to be rooted. Next:
- Go to cust/app and copy the folder HWCallRecorder
- Go to system/app and paste the folder
- Set permissions to the folder to 755 in total commander
- Set permissions to the file inside to 644 in total commander
- Reboot
- Enjoy

obviously I have the root, otherwise how did I use Magisk? However I extracted the folder from the zip of version 9.2 because in my version c432 there was not in the cust folder. I copied in system app I restarted and it's all fine.

gabryrizz02 said:
obviously I have the root, otherwise how did I use Magisk? However I extracted the folder from the zip of version 9.2 because in my version c432 there was not in the cust folder. I copied in system app I restarted and it's all fine.
Click to expand...
Click to collapse
Great to hear that it worked out.

does this work on other pie phones or only on hauwei?

xumixu said:
does this work on other pie phones or only on hauwei?
Click to expand...
Click to collapse
As far as I know, only Huawei. It's already implemented into the system, only needs a bit of a nudge.
As for other pie phones, word is that due to some privacy regulations, google is required to stop supporting call recording.

@Pretoriano80 Hi Mate
I'm on EMUI 9 with Mate 9 and I would like to know if your Magisk module is installable on Magisk v19 (Magisk often switch his template and/or configuration with .sh files)?
Thanks!

Tecalote said:
@Pretoriano80 Hi Mate
I'm on EMUI 9 with Mate 9 and I would like to know if your Magisk module is installable on Magisk v19 (Magisk often switch his template and/or configuration with .sh files)?
Thanks!
Click to expand...
Click to collapse
Hi! It's a simple module, nothing fancy, so it should install just fine with Magisk v19 too.

Pretoriano80 said:
Hi! It's a simple module, nothing fancy, so it should install just fine with Magisk v19 too.
Click to expand...
Click to collapse
You are right, thanks :good:
I made a version based on your idea and with credit for you in the readme.md file for Mate 9 /Emui 9.
https://www.androidfilehost.com/?fid=1395089523397943267
Only difference: I used the new Magisk Installer Template for Magisk v19 and additional I use the HwSoundRecorder (deodexed from Chinese Firmware) too in /system/app. Both is possible, manual recording from dialer and auto recording from dialer settings. (RCS I leave disabled)
Thanks Mate :highfive:
If you like you can try to add Soundrecorder to your module for Mate 10 Pro and test.

How to flash your file with fastboot adb command please?

cadkey said:
How to flash your file with fastboot adb command please?
Click to expand...
Click to collapse
Read the first page (OP) - it's a Magisk module and must be flashed directly from Magisk Manager (Modules section + Button)

https://www.xda-developers.com/huawei-honor-emui-9-call-recording/
Found this post by XDA and I'm so pleased that call recording works flawlessly without root.

[EvolutionX (3.5) Erfan GSIs] [Android 10 ]

New v3.5 port from Oneplus 6 https://forum.xda-developers.com/showpost.php?p=81186001&postcount=6
port from Redmi 4A https://forum.xda-developers.com/showpost.php?p=81186219&postcount=7
From Base Firmware : EvolutionX_3.3_violet-10.0-20191112-1125-OFFICIAL.zip
Raw Image Size: 2.86 GiB
Thank to TeamGSI
======================
Download:
GSI : https://drive.google.com/drive/folders/1-7N6Z9NUb-9ut8Zz8M51FAwUC11AKTaa
File Name : EvolutionX-Aonly-10-20191119-GSI.img-1621.z7 (extracted before flashing)
TWRP : https://mega.nz/#!sHoXlaDK!ZIfuRrtl7IGsruGMIWDrbvudKgxcYdiEd-6iQS2YFNg
File Name : TWRP-20191001-3.3.1.0-clover.img
Vendor & boot : Pie ( Treble ) https://mega.nz/#!xaolTKoS!pdfjw02cw3dImfB4vlyXwINALQUewQ5lJBBjSUDKxcM
File Name : vendor_197.zip
Latest Official Clover Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
File Name : fw_clover_miui_MIPAD4_9.8.29_6647b25a58_8.1.zip
Erfan tools : https://mega.nz/#!xXpViC4Y!UsRgGMYNtiaLvfdXSuzamfaxsM_FOs-9xrZrPu5QCP8
File Name : allzygotefix2.zip
Phh Magisk : Magisk-v20.2-b29f0ca4-phh.zip
https://mega.nz/#!tKxngSaD!jdDHi4-QFMX2bNgQVPi50ZrpovbNRuD61aAeIt02lCI
GMS : https://mega.nz/#!cOhmgIoY!cTYxxYpc36tMl0QnndRcaPUDQ6BpO7tG0yiPQ2i7QXo
=================
Step
-wipe--Format Data
-wipe--Advanced wipe---Dalvik , Cache , Data , System , Vendor
-Option wipe--Advanced wipe---tick Data menu----Repair or change file System-----Change File System and select F2FS
-flash Firmware
-flash Vendor
-flash GSI as System Image
-flash allzygotefix2.zip (for A-only GSI when work with Android 10)
-Reboot to System
Don't worry about " Android System error message , its only one warning --we will fix at the end.
click "OK"
-Setting menu --Display---Smallest width = set to 540 dp or more than that , Icon shape = up to you
-Setting menu --Evolution settings---enable Users and Logout ( Multi user )
Don't forgotten to setup SD Card ===(Support exFAT) for me use as removable.
-Setting menu -- About phone ===changes device name from POCO F1 to anything you like or Mipad4
==============
-Flash Magisk (phh Magisk) https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
-Reboot--update it if need
-Magisk manager --install belows modules from here ---> https://github.com/ElderDrivers/EdXposed
1. Magisk-riru-core-v19.5.zip ( save)
2. Magisk-EdXposed-YAHFA-v0.4.6.0_beta.....xxxx.zip
-Reboot
-install Edxposed Manager.apk
open it set active status
-Reboot by granted Magisk super user permission
-Add & activated eXposed modle--com.cofface..ivader
=======================================
-install updated GMS ( Google Services)
-Reboot
-Setup and login your google account
Now your Play Protect is certified. and all green Safetynet check success.
======================================
-Check your FingerPrint.
-Check your BlueTooth
-Check your Mobile Data ( VoTLE )
-Check your Auto rotate
-Your Camera
All working
=========================
Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
=========================
Viper4Android FX from magisk'repo
v.2.7.1.0
-install with Magisk manager
-reboot and open program-- follow suggestion from screen
==========================
Supported Youtube Vanced.
++++++++++++++++++++++++++++++++++++++++++++++++++
GCAM
https://www.celsoazevedo.com/files/android/google-camera/dev-parrot043/#apk1213
+++++++++++++++++++++++++++++++++++++++++++++++++

New & Update from ExpressLuke GSI ( compiled from source)
=============================
ROM Name: Evolution X 3.3 ( EvolutionX_3.3_ARM64A-10.0-20191202-0048-UNOFFICIAL.img)
ROM Version: 10
ROM Security Patch: 5 November 2019
Architecture: ARM64
Partition Layout: A
GSI Patch Base: phh v204
Built in GApps?: Yes
Changelog: https://pastebin.com/raw/0SwBzV6e
MEGA: Download
( https://mega.nz/#!QJkF3KxY!-trp3Q9NJDqtKoTddxeg3yn-bu6JU_6XuokZs-ri7B4)
SourceForge: Download
(https://sourceforge.net/projects/ex...191202-0048-UNOFFICIAL.img.xz/download)Google
Drive: Download (https://drive.google.com/a/turbox.uk/uc?id=1U0Nhpow2IMXUTV_ZQIfC9JAEocPc3Qik&export=download)
####Please use magisk-phh
Note !!!!!!
1. you must flash "Permissiver_v5.zip" cause GSI image not included. ( if not will Boot Fastboot Mode )
2. No need to install new update GMS apk.
3. Default Camera not working. use GCAM instead
4. Chrome crash.
-----> Please test wifi speed. mine very low 30 Mbit/Sec
-----> Evolution setting--->Power menu --->ERROR

EVOLUTIONX 3.4 (Recommended)
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=16_3QYEeq8DnLI92xQvY6u4hSNpZ4-sYj)
File name: EvolutionX-Aonly-10-20191210-ErfanGSI.img.gz
Information:
Android Version: 10
Brand: Xiaomi
Model: MI 8
Codename: dipper
Build Type: aosp_dipper-user
Build Number: QQ1A.191205.011
Incremental: eng.DarkAn.20191207.000600
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.5.0.OEAMIFA:user/release-keys
Description: dipper-user 8.1.0 OPM1.171019.011 V9.5.5.0.OEAMIFA release-keys
Raw Image Size: 2.60 GiB

Many thanks for your contributions to our device!
it works great , everything works except the auto rotate, is always in vertical

UPDATE EvolutionX v3.5
Information:
Android Version: 10
Brand: OnePlus
Model: ONEPLUS A6003
Codename: OnePlus6
Build Type: aosp_enchilada-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.bliss.20191212.000302
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Description: OnePlus6-user 8.1.0 OPM1.171019.011 273 release-keys
Raw Image Size: 2.81 GiB
====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=13OJZ6ABa5zLMdCGAGaW3nuNczGV8VAuE)
<<<<<<<< Not boot with my vendor for mipad >>>>>>>>>>>>>

Update EvolutionX 3.5
Information:
Android Version: 10
Brand: Xiaomi
Model: Redmi 4A
Codename: rolex
Build Type: aosp_rolex-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.ubuntu.20191212.104649
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/rolex/rolex:7.1.2/N2G47H/V9.2.6.0.NCCMIEK:user/release-keys
Description: rolex-user 7.1.2 N2G47H V9.2.6.0.NCCMIEK release-keys
Raw Image Size: 2.35 GiB
=====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=1jxyN2uiNo8rk2o4az6r8BR3nfqxqHfF6)
Bug: Evolution setting---power menu (crash) but can use advanced boot with power button.

I tried several times and always get the same problem : the autorotate not works,
I installed other Roms and in every rom I have the same probem with the autorotate
I also tried the roms from https://forum.xda-developers.com/mi-pad-4 and is the same, Im afraid my autorotate die...
I tried the sensors app in google play and says all my sensors not works...
Any idea to try to solve giroscopie?
I tried various roms and I think this one works very well :
https://forum.xda-developers.com/mi-pad-4/development/rom-lineageos-17-0-t3989187

Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
Click to expand...
Click to collapse
Everything works fine except the error every bootup is not fixed. I cannot find "ro.vendor.build.fingerprint" in build prop. I managed to set this "ro.treble.enabled=false". However, the error persists.
Also, how do I prevent the screen from turning off when I close the flip cover?