[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018] - Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &

[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018] - Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &

{
"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"
}
LineageOS 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* 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
* 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.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25

Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse

Reserved

Dowloanding ^^
As soon as I can, I'll report back =)

Thank You #Henkate for keeping Nova alive!

Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!

Works fine here, thanks a lot for the hard work !!!

Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.

For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/

To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.

#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk

Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.

#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.

I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.

sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:

icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.

I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful

Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !

Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?

imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).

Related

[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [BETA]

{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803
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.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E5823 and the E5803
Code:
*
* Your warranty may be voided !
*
* 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.
*
Special Thanks
The authors of my books
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for maintaining the Z5P and reminding me that smashing your device can provide a solution
@zacharias.maladroit for maintaining Z5 (sumire)
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
The Sonyxperiadev team for releasing their sources to the public
SonyCM team
And of course the entire CyanogenMod team!
Issues
Laggy back camera
Video Recording on stock camera app (Use alternative)
What has been Fixed
Stability issues
SELINUX
Lag after booting up device
Camera Colors
Bluetooth
Fingerprint sensor
Full brightness
Torch
Double Tap 2 Wake
External SD recognition
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Download the Z5C AndroPlusKernel v31 by @AndroPlus from his official website (Scroll down and select Z5 compact, then chose Z5C_AndroPlusKernel_v31.zip and download it)
Extract the Z5C_AndroPlusKernel_v31.zip
Download our TWRP 3.0.0.0 build for the Z5 Compact (Special thanks to @moonbutt74 for getting the configs right)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 Compact from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 Compact if you haven't downloaded them on your device
Power Off your Z5 Compact and wait about 10-15 seconds to make sure it's off
To enter fastboot hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification light has turned blue you have entered fastboot mode
On your PC flash the boot.img that has been extracted from the Z5C_AndroPlusKernel_v31.zip using fastboot
Now flash the twrp-3.0.0.0 image by using fastboot
Once both of those images have been flashed you can exit fastboot
After exiting fastboot wait for the notification light to turn cyan (it says cyan if you can't read it) at the Sony logo
Once it has turned cyan (it says yellow if you can't read it), you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above, reboot your device and try the step above again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP make a full backup in case you want to revert back to stock (Note: Backing up on external sd still doesn't work yet)
After the backup has completed, go back to the main menu and select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS (But not your photos, music or everything else located in internal storage)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take some time)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable and enter the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How return back to stock via TWRP backup
In CM13, enable and enter the developer options
Enable Advanced Reboot
Hold your power button for about 3 seconds
Select Reboot
Select Recovery and press ok, you will then enter TWRP
If TWRP will ask you to enable read and write, simply swipe to continue
In TWRP select restore and then select your backup, finally swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Lastest recommended CyanogenMod release for the Sony Xperia Z5 Compact E5823/E5803 : ROM | MD5
All my releases can be found here : Android File Host
Gapps (Select ARM64 > 6.0) : Open Gapps
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
2016/8/28 - Complete re-write from scratch
- Fixed Bluetooth
- Fixed Fingerprint sensors
- Fixed Camera colors
- Fixed Camera breaks
- Fixed Stability Issues
- Fixed laggy boot
- Fixed torch properly now
- Enabled SELINUX
- Merged with Sony upstream repos
- Synced to the latest CM sources
- Old repos are now deprecated and are planned to be removed in the nearby future
2016/04/17
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/12
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Source Code
All Source Code can be obtained from here : Sony Kitakami Developer Organization
We gladly accept any developers that are willing to contribute to this project! Please PM me if you are interested in joining this project!
Build from Source
How to build CyanogenMod 13 for the Sony Xperia Z5/Z5C/Z5P from source
Screen Shots
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803, ROM for the Sony Xperia Z5 Compact
Contributors
CTXz, zacharias.maladroit, oshmoun
Source Code: https://github.com/Sony-Kitakami
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-03-19
Last Updated 2016-08-28

Q&A
Q&A
Q: Does this work on the Z5/Z5 Premium
A: No, this ROM is for the Z5 Compact only. Please visit the appropriate forum for your device as the appropriate CM version for your device is located there
Q: Does this work on E58XX
A: This ROM was build for the E5823 and E5803, flash it on a different Z5C model at your own risk! If it works, please report it to me so I can update the thread
Q: How long until <insert issue here> gets fixed
A: ETA's (Short for Estimated Time of Arrival) aren't tolerated well on XDA. Please remember that this is only a hobby
Q: CM becomes really laggy after a few minutes (Should not happen anymore, however if it does then follow the answer)
A: Please check the "How to disable the Thermal Manager" guide in the thread

Z5 Development thread

Really looking forward to using this, I just got the Z5 Compact back today after repair.
Thank you!

Very excited to see CM coming for the Z5C.

@CTXz i bought rust, what to do now? :c

H3XabyT3LV said:
@CTXz i bought rust, what to do now? :c
Click to expand...
Click to collapse
Please PM me rather than posting on my threads, this isn't really Z5C related, is it?

@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!

Joeisgood99 said:
@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!
Click to expand...
Click to collapse
Hey, glad to see you reply. I'd really like to say thanks for your recovery since it supports the fstab that I use.
Cheers!

Hell yeah! Finally development for z5c. Btw, doesn't e5803 and e5823 run same software?

my last phone was a oneplus one. I couldn't get used to its size so I switched to the z5c. I kinda started regretting my decision but this makes me really happy.

Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?

oshmoun said:
Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?
Click to expand...
Click to collapse
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess

CTXz said:
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess
Click to expand...
Click to collapse
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)

oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)
Click to expand...
Click to collapse
Wups, out of thanks... Reached the limit
Anyways, like I said feel free to join our organization, you can work on PAC-ROM there if you want.
Cheers

oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Click to expand...
Click to collapse
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx

someone755 said:
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx
Click to expand...
Click to collapse
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...

CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
he was just kidding. we both have a weird sense of humor :angel:
oh and to get back on topic, you might be interested in the following repos, as they contain the commits required to reboot to recovery, like on other xperia devices
https://github.com/SonyCM
it also might be worth it to rebase your work on top of them, as they're maintained by a CM member
I'll see if i can get the stuff i have on my personal github sorted in a good way so they can be easily merged into your repos

CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
Lol don't worry I'm just taking the piss since this part of the forums is unknown territory for me.
You didn't think oshmoun would tag a complete retard? (don't answer that lol)

Much appreciate for all your hard work for the development of z5 series?

[ROM+KERNEL][CAN-L11][UNOFFICIAL] LineageOS 13.0 [11.08.2017]

{
"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"
}

[COLOR=167c80]LineageOS 13.0 for Huawei Nova CAN-L11[/COLOR]
DISCLAIMER:
Code:
* 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
* 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.
NOTES - MUST READ
1. All credits goes to @Grarak for making the sources. I've only built LOS using his sources. Also I've been able to build by using Google Cloud platform since my PC is crap... It took me 1h 30m to build with Google Cloud platform, while with my PC was still building after 7h of building and then got an error regarding my PC (was too slow or out of memory).
2. Don't use encryption. I don't know why, but Grarak mentioned this on his twitter at the last build for CAN-L01.
Click to expand...
Click to collapse
[COLOR=167c80]Requirements[/COLOR]
- Huawei Nova CAN-L11
- EMUI 4.1 (Android 6.0). I've flashed it successfully from EMUI 5 ( Android 7.0) too and I didn't encounter any problems.
- Unlocked bootloader ( here's a guide about how to unlock it)
- TWRP by @Grarak. I've been on his TWRP while flashing LOS. I don't know if it works with other TWRP.
Click to expand...
Click to collapse
[COLOR=167c80]Installation[/COLOR]
Make sure you meet the requirements listed above.
1. Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 6.0 and pico).
2. Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
3. Wipe system, data, cache and dalvik-cache.
4. Flash the ROM from the directory where you've placed it.
5. Flash GAPPS (OPTIONALLY).
6. Reboot.
Click to expand...
Click to collapse
[COLOR=167c80]Download[/COLOR]
ANDROIDFILEHOST | MEDIAFIRE
[COLOR=167c80]Sources[/COLOR]
Device https://github.com/skinzor/android_device_huawei_can/tree/cm13.0 (it's the same device tree made by Grarak, just that I've corrected the partition sizes for CAN-L11).
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/cm13.0
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953/tree/cm13.0
Click to expand...
Click to collapse
[COLOR=167c80]Credits[/COLOR]
@Grarak for the sources
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM+KERNEL][CAN-L11][UNOFFICIAL] LineageOS 13.0 [11.08.2017], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953/tree/cm13.0
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Unlocked bootloader, TWRP, EMUI 4.1 (Android 6.0)
Version Information
Status: Stable
Stable Release Date: 2017-08-11
Created 2017-05-26
Last Updated 2017-08-11

Changelog & bugs
Bugs
- FM-Radio
- signal icon becomes empty / gray when you are using 3G, but the network is working
- camera recording / video playback issues (sometimes, when you play the recorded video it gets stuck / frozen)
If you've found a bug, please report it along with a logcat.
Changelog
11.08.2017
ROM:
- 1 July 2017 security patch
- switched to Snap Camera (quality seems to be much better as I've said in one of my previous posts)
- added microG support (signature spoofing)
- fixed NFC
- fixed Dual SIM - thanks to @Yohannj who for this
- ROOT is now included (LOS`s root)
- added more blobs: OMX, IMS, CNE / DPM
- disabled LiveDisplay by default
- got rid of CM Updater since we don't have official LOS
- bluetooth name was set to "HUAWEI Nova" as default
- increased ZRAM to 1gb and applied other changes/settings as EMUI 5 (in my opinion, multitasking seems to be better)
- added ext4 support for /data
- added f2fs support for /cache
KERNEL:
- re-enabled cleancache and zcache
- applied a patch to allow 200 swappiness (for zram)
Click to expand...
Click to collapse
02.06.2017
ROM:
- sdcard problem was fixed (in first release, the sdcard wasnt recognized in other apps other than Documents app and neither MTP)
- added glove mode (Settings > Display > High Touch Sensitivity)
KERNEL:
- CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
- FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
- CPU Boost toggle; disabled by default
- KCAL: Advanced color control (RGB, Saturation, Value, Contrast, Hue)
- Vibration intensity control
- SafetyNet pass
- I/O schedulers: added SIO, SIOPLUS, FIOPS, ZEN, BFQ, tripndroid
- governors: added blu_active
- DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
- QuickWakeup driver: Allow kernel driver to do periodic jobs without resuming the full system. It can increase the battery life.
- Zen-tune: Tunes the kernel for responsiveness at the cost of throughput and power usage.
- enabled Power Efficient Workqueues: it should increase the battery life. There is also a toggle.
- enabled advanced TCP congestions: Westwood, HSTCP, HYBLA, HTCP, Vegas, Veno, Scalable, LP, Yeah, Illinois
- misc fixes
Click to expand...
Click to collapse
26.05.2017
- initial build
Click to expand...
Click to collapse

Reserved

It goes fine on my AL10, and the SD card issue I had was solved with:
Code:
sm storage-force-adaptable yes
I posted that in the other lineage thread.
My question would now be how is this different than the other build?
---------- Post added at 06:06 AM ---------- Previous post was at 05:59 AM ----------
Only other thing I will mention, I use gravity box for minor status bar tweaks (the percent seems to not natively stay in the circle) and pie control with no nav bar (more screen for me). If you touch lockscreen stuff in gravity box you will make your lockscreen insecure. It will be a simple swipe in order to get to your phone. I know gravity box should not be used with lineage, but I mention it as I encountered it.

wangdaning said:
It goes fine on my AL10, and the SD card issue I had was solved with:
Code:
sm storage-force-adaptable yes
I posted that in the other lineage thread.
Click to expand...
Click to collapse
Thanks for this tip. I understand that this command enables adoptable storage, but I don't want to use adoptable storage as it may slow down the phone. Also, by using this command, the sdcard gets formatted too?
My question would now be how is this different than the other build?
Click to expand...
Click to collapse
The CAN-L01 build couldn't be flashed on CAN-L11 because the partition sizes defined in BoardConfig.mk were L01 ones which were bigger than L11 ones and upon flashing L01 build I was getting an error saying that it's too big.
I've corrected the partition sizes for L11 and built it. That's the only change.

It seems that the sdcard can be accessed through /mnt/media_rw/9016-4EF8, assuming you're rooted.
I'm still trying to figure out what's wrong.

I see, when I ran the command posted above my SD card was visible in other file explorers.

wangdaning said:
I see, when I ran the command posted above my SD card was visible in other file explorers.
Click to expand...
Click to collapse
Ive just fixed the sdcard issue. It seems that the problem was in fstab.qcom.
Ill make some other changes and then ill make a new build.

Good man, just wonder if your build will run on my device.

hi
tnx for your work.can we (owner of nova plus)use this rom?

wangdaning said:
Good man, just wonder if your build will run on my device.
Click to expand...
Click to collapse
It should work as long as it flash successfully. It's the same ROM as L01 one just that it has the partition sizes modified for L11, so it should work. If it gets stuck in recovery while flashing, then it means that the L11 partition sizes "doesn't fit" your model.
at.great said:
hi
tnx for your work.can we (owner of nova plus)use this rom?
Click to expand...
Click to collapse
I don't know, you can try to flash and report whether it works or not. As always, take a backup before.

coool!!!NOVA user's appreciation

Hello
Does anybody have the camera working?

I will give it a shot next weekend, kind of need my phone to work during the week. I wonder if we start a partition table thread if that would be helpful. It was my understanding that most of the partitions are the same except userdata, which is based on variant.

Wahbax said:
Hello
Does anybody have the camera working?
Click to expand...
Click to collapse
Yes, the camera is working. The bugs are mentioned in post #2.
wangdaning said:
I will give it a shot next weekend, kind of need my phone to work during the week. I wonder if we start a partition table thread if that would be helpful. It was my understanding that most of the partitions are the same except userdata, which is based on variant.
Click to expand...
Click to collapse
Well, i guees that would be helpful assuming people will post their partition table. Here I've wrote how to check the partition sizes.

#Henkate said:
Yes, the camera is working. The bugs are mentioned in post #2.
Click to expand...
Click to collapse
Thanks for the quick response. I followed the guide step by step and I always get this message in camera app "Camera Error Can't connect to camera".
Also no third party camera app is working, I tried restarting, re flashing Gapps and re flashing the rom. still the same error.
attached is a screen shot.

Wahbax said:
Thanks for the quick response. I followed the guide step by step and I always get this message in camera app "Camera Error Can't connect to camera".
Also no third party camera app is working, I tried restarting, re flashing Gapps and re flashing the rom. still the same error.
attached is a screen shot.
Click to expand...
Click to collapse
That's weird. It's working fine for me and there's no issues.
Can you try to wipe Internal storage too? But make a backup of internal memory before doing that.
I haven't flashed GAPPS as I'm not using them, but it shouldn't affect the camera in any way.
I've just tried Open Camera and works fine too.

#Henkate said:
That's weird. It's working fine for me and there's no issues.
Can you try to wipe Internal storage too? But make a backup of internal memory before doing that.
I haven't flashed GAPPS as I'm not using them, but it shouldn't affect the camera in any way.
I've just tried Open Camera and works fine too.
Click to expand...
Click to collapse
I wiped internal storage, didn't flash gapps
Unfortunatly, Camera still not working

Wahbax said:
I wiped internal storage, didn't flash gapps
Unfortunatly, Camera still not working
Click to expand...
Click to collapse
Which Nova do you own?

#Henkate said:
Which Nova do you own?
Click to expand...
Click to collapse
CAN-L11

[ROM][SNAPSHOT][9] AOSP Pie for Xperia SP

{
"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.
*/
Downloads Links
AOSP 9 Pie (Unlocked Bootloader) :
Xperia SP (Huashan) - 9 : https://mega.nz/#F!6hsHyKKT!ERgr5s0BMMtO2Cb9j8wLnA
Google Applications (optional) :
MindTheGapps : https://androidfilehost.com/?w=files&flid=170282 (Use packages for ARM, Android 9.0)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.x : http://forum.xda-developers.com/xperia-sp/orig-development/-t3309938
Configure the default Low-RAM features (optional) :
Low-RAM Property Patcher : http://forum.xda-developers.com/-/-t3737373
Informations and references :
Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8960t
About AOSP : Repositories available on https://android.googlesource.com/
Flashing and updating
AOSP clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the AOSP ROM zip from recovery
- (Optional) Flash a GApps package to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
AOSP update / upgrade :
- (Information) Do not wipe anything unless you want to
- Flash the latest AOSP ROM zip from recovery
- (Optional) Flash a GApps package if you want to, otherwise preserved.
- (Optional) Every additional zip you want to flash
- Reboot
About the builds
Development project : https://github.com/AdrianDC/aosp_development_sony8960_p
Device tree : https://github.com/AdrianDC/android_device_sony_huashan
Kernel sources : https://github.com/AdrianDC/android_kernel_sony_msm8960t
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony
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
Q : Is root access included into AOSP ?
A : No but you can now root with my Boot Bridge and a superuser tool.
Q : Is the ROM suited for daily usage ?
A : Yes. Check the list below to decide for yourself.
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.
Q : When USB is connected to a computer, I can't access the storage ?
A : The phone is in charge-only mode by default (since Android Nougat),
> due to a stronger security logic regarding unauthorised data access.
> Swipe down the notifications and change the USB mode.
AOSP available for Xperia Huashan also thanks to :
- Google AOSP
- The LineageOS Team
- CodeAurora Forums
- The CyanogenMod Team
XDA:DevDB Information
AOSP Oreo 9, ROM for the Sony Xperia SP
Contributors
AdrianDC
Source Code: https://android.googlesource.com/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Snapshot
Created 2019-08-17
Last Updated 2020-08-15

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- Touchscreen : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- DRM : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Not tested yet
- SEPolicies : Permissive, enforcing is a work in progress
ALSO WORKING ON SONY HUASHAN
Music Lights Effects implementation fully working
Presentation of the features : https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399
YouTube Presentation : https://www.youtube.com/watch?v=GHk__DhyL60
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open AOSP Recovery,
- 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
Changes log
17/08 : Initial public release on Android 9.0.0_r46 August
2018: Initial AOSP 9 ports, internal bringup
>>> Kept private for development purposes
Recent branches commits
Devices + common projects: https://github.com/AdrianDC/aosp_development_sony8960_p/branches/all
Original AOSP 9 sources with following relevant additions
Huashan device tree, kernel and vendor
Bionic: Support for SHIMs (Camera)
Build: Backup tool full support (GApps)
NFC: Proper support & removed log spam
Toybox: Support for init_sony boot selection
AV: Camera support for Pie
AV: Initial camcorder partial support
Camera2: Fixes for wrongly rotated photos and improvements
UI: Various efficiency improvements and fixes
Telephony: Support for older RIL layers
Audio: 8960 adapted HAL and FM support
FM: Fully implemented with AOSP FM Radio
Music: Minor fix to permissions
Settings: Minor visual rendering improvements
Healthd: Support for Huashan offline charger
Core: Disabled flash_recovery service from AOSP
Sepolicies: Minimal changes and fully enforced ROM
Current local manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- [url]https://android.googlesource.com/platform/manifest[/url] -->
<manifest>
<!-- See [url]https://github.com/AdrianDC/aosp_development_sony8960_p[/url] -->
</manifest>

I woke up in the morning and decided for a short walk around the internet - and to my surprise I found new builds of both AOSP and Lineage suitable for my favourite backup phone Thank you so much @AdrianDC - I know it is harder to withstand people than hardware

Thank you for LTS for our Xperia SP. :good:
Is it possible for miracast to work in LOS 16 as it does in LOS 15.1?

ze7zez said:
Thank you for LTS for our Xperia SP. :good:
Is it possible for miracast to work in LOS 16 as it does in LOS 15.1?
Click to expand...
Click to collapse
Sadly Google has removed support for Miracast in AOSP P.
An attempt to revive the abandoned code for LineageOS 16.0 is ongoing and on review.

Experience, first stable build
Hello, i want to share my critic experience with you and this rom.
(C5303, Clean flash, Data and cache FS changed to F2FS, without gapps, magisk)
1. Music - i had good experience, led controls work good, but after day of using phone and some restarts, it shows only 2 from my 600 songs.
So i installed Sony music app, no difference. Cleared data, cache for both apps, but still no difference.
2. AOSP Browser - After some succesful launches, FC every launch time, other browsers OK
3. After day usage, system started drain battery as fck...
4. At same time as battery and music, system going slowly
5. And biggest issue - phone cannot turn off - it restarts. So i have 2 go 2 recovery and turn off here.
I have been without gapps, because i wanted pure system, so i installed yalp store (some 404 client errors, but logged succesfully) and with magisk 19.3 bootbridge (Modules: V4A 2.7.1.0, Audio compatibility and modification patches, Pixelarity, SF-Font, Busybox, all modules works flawlessly)
I must give big + and thanks for developers, because 6 y.o. phone still breaths for today with the new system, but stable work must have itself finality. Check this things on your phones and please fix it for stable, pure AOSP experience.
And add please full dark mode.
Edit:
I have tried new Lineage 16 and same issues with different music players, browser and newly - gallery doesnt show anything and camera not working.

jurko217 said:
(---cut---)
And add please full dark mode, it changes battery life for some hours (---cut---
Click to expand...
Click to collapse
For amoled display only. Huashan doesn't have it.

sorry, another thread

Hi,
First of all, I want to thank again AdrianDC for bringing Android Pie on our lovely SP (that I'm keeping as a backup phone and can't let it go), man, you just rock
But I'm really surprised not to read anything here about the setup problems I've encountered, because for me, it was Hell on Earth !!!
It has NOTHING to do with the ROM or the work of AdrianDC, but it seems to be purely Google's fault
So, I thought I will share how I got through it, perhaps helping some of you not getting nearly insane, like me yesterday...
First one was "Stuck on "Checking for updates..", so I found first here : https://www.reddit.com/r/GalaxyS9/comments/aqa384/t_mobile_s9_stuck_on_checking_for_updates_after/ this reply : "I had to completely disconnect from wifi, took the sim out so it would skip that process. Its finally working fine now." method confirmed in this XDA thread here : https://forum.xda-developers.com/nokia-7/help/stuck-screen-checking-updates-hard-reset-t3767866/page2 in the post #15 : "Try without SIM card inserted. It should work."
Alternatively, in this thread : https://forum.xda-developers.com/2015-moto-g/help/reset-stuck-checking-updates-t3571496 the method explained in post #4 worked well also :
"On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system"
And then came the second bug : "Phone stuck on Preparing for Setup after factory reset of Android Pie"
I read a lot of threads about it :
https://forum.xda-developers.com/mi-a2/help/phone-stuck-preparing-setup-t3870469
https://forums.oneplus.com/threads/android-preparing-for-setup-prompt-always-appearing.1083942/
https://forums.oneplus.com/threads/stuck-with-android-setup-issue-on-oneplus-6t.953686/
https://forums.lenovo.com/t5/motorola-one-motorola-one-power/Preparing-for-Setup-you-can-finish-your-motorola-one-power-soon/m-p/4391471#M4710
https://www.reddit.com/r/tmobile/comments/9uj9vw/cannot_get_android_setup_app_updates_are_ready/e94uow3
https://uk.community.huawei.com/mate-20-series-20/app-updates-is-not-moving-preparing-for-setup-2591
https://uk.community.huawei.com/mate-20-series-20/android-setup-keeps-telling-me-that-app-updates-are-ready-and-that-i-should-connect-to-wifi-5687
And so on, but nothing in all this posts helped so I ended disabling the notification AND the Android Setup app !!!
Some of those reports are more than a year old and I've rooted and flashed custom ROMs on 5 differents devices / brands over the years, but I never encountered such a mess !
Google, what's wrong with you ?!?
So I hope this will help a bit, I wish you all a nice Sunday...

For completion's sake, I forgot to add that I've made a clean install and did follow exactly these steps to do it :
- having made the TA backup years ago and finding LineageOS Oreo a bit too lagy to my taste, I took the occasion to try (for the first time) to restore the TA partition (with success), this locking back again the bootloader and then, restored with Flashtool the original ROM that was shipped with the SP;
- so I find myself back with the original DRM keys and the original Jelly Bean :crying:, played a little bit with it (a real trip down Memory Lane) and confirmed forever to myself that I really don't miss anything of Sony's crap (Bravia Engine, Track-ID, whatever...), but to each his own;
- I used fastboot and Sony's code to unlock the bootloader again, then boot twrp.img, flashed the FOTA.zip and erase EVERYTHING, but the SD card !
- I just flashed the 20190817 build and the OpenGapps Micro, one after the other from the SD Card and let the BootBridge.zip with Magisk inside for a later time...
- I rebooted and then, all Hell broke loose
- Hours (and a lot of swearing) later, I flashed BootBridge.zip with Magisk and could finaly enjoy how mean and lean is Android 9 on this 2013 device again, bravo !!!
So, I honestly don't think that any of those steps described above could have been the cause of the 2 bugs (and the numerous threads I've read seem to confirm it), but I would be glady corrected if I'm wrong...
Really, nobody here had to go through this whole hassle, seriously ? You've all got a smooth ride with a clean install ?
I would really like to know if it's me or if, in this case, Google is having two left hands, and just with thumbs :silly:

fsw_informatrix said:
For completion's sake, I forgot to add that I've made a clean install and did follow exactly these steps to do it :
- having made the TA backup years ago and finding LineageOS Oreo a bit too lagy to my taste, I took the occasion to try (for the first time) to restore the TA partition (with success), this locking back again the bootloader and then, restored with Flashtool the original ROM that was shipped with the SP;
- so I find myself back with the original DRM keys and the original Jelly Bean :crying:, played a little bit with it (a real trip down Memory Lane) and confirmed forever to myself that I really don't miss anything of Sony's crap (Bravia Engine, Track-ID, whatever...), but to each his own;
- I used fastboot and Sony's code to unlock the bootloader again, then boot twrp.img, flashed the FOTA.zip and erase EVERYTHING, but the SD card !
- I just flashed the 20190817 build and the OpenGapps Micro, one after the other from the SD Card and let the BootBridge.zip with Magisk inside for a later time...
- I rebooted and then, all Hell broke loose
- Hours (and a lot of swearing) later, I flashed BootBridge.zip with Magisk and could finaly enjoy how mean and lean is Android 9 on this 2013 device again, bravo !!!
So, I honestly don't think that any of those steps described above could have been the cause of the 2 bugs (and the numerous threads I've read seem to confirm it), but I would be glady corrected if I'm wrong...
Really, nobody here had to go through this whole hassle, seriously ? You've all got a smooth ride with a clean install ?
I would really like to know if it's me or if, in this case, Google is having to left hands, and just with thumbs :silly:
Click to expand...
Click to collapse
Sometimes opengapps can cause errors given how itself is like a rolling Nightly packages generated on demand when you hit download. I recommend trying MindTheGapps as it went smoothly for me using that one.
Not a setup issue, but an issue nonetheless: During my attempt to flash this ROM, I had free space errors with Opengapps. Even on pico package!
Ninja Edit: I found out on the LOS pie thread that Pico is the only one that fits. I still however stand by the authenticity of my story

TechnoSparks said:
Sometimes opengapps can cause errors given how itself is like a rolling Nightly packages generated on demand when you hit download. I recommend trying MindTheGapps as it went smoothly for me using that one.
Not a setup issue, but an issue nonetheless: During my attempt to flash this ROM, I had free space errors with Opengapps. Even on pico package!
Ninja Edit: I found out on the LOS pie thread that Pico is the only one that fits. I still however stand by the authenticity of my story
Click to expand...
Click to collapse
Thank you again didn't thought about that one, I will give MindTheGapps a try, next time...

OMG, my second try was so quick & easy with MindThe Gapps, thanks again @TechnoSparks
I did a Nandroid backup and couldn't resist to give it another try, so from TWRP in the FOTA :
1) I manually erased all partitions, but recovery, SD Card and USB-OTG, just to be sure.
2) I queued and installed from the first post (and in this order) aosp-9-20190817-huashan-adriandc.zip, android_lowram_enabler.zip and MindTheGapps-9.0.0-arm-20190615_031401.zip, without any errors.
That was the right call to flash the android_lowram_enabler.zip in between, because I've noticed a message from the MindTheGapps installer :
"Low ressource device detected, removing large extras", which is lovely and exactly what I needed, no Google bloatware...
3) I rebooted and didn't met any of the bugs I had with OpenGapps, not even an initial setup :laugh: just had to pick manually language and Wi-Fi (location and date/hour too, as there is no SIM inside).
4) I got back to TWRP and flashed BootBridge-SonyELF.zip with Magisk19.3 inside, rebooted and updated Magisk Manager (Note: strangely, I had to reflash BootBridge-SonyELF.zip a second time, after the Magisk Manager update, to get it working back).
Now, it's all set up and I can finally test it further
Hope this helps somebody and keep up the good work, M. AdrianDC...

fsw_informatrix said:
That was the right call to flash the android_lowram_enabler.zip in between, because I've noticed a message from the MindTheGapps installer
Click to expand...
Click to collapse
Thank you for your report.
For information, I'll remind something for everyone : My Sony Huashan & Blue releases are all using the Go low RAM configs.
Flashing android_lowram_enabler is not required, it's a no-op, however android_lowram_disabler will bring back disabled features per user choice.
The android_lowram_enabler tool serves a purpose only to come back from a disabler and for any other devices not using Go low RAM configs.

AdrianDC said:
My Sony Huashan & Blue releases are all using the Go low RAM configs.
Flashing android_lowram_enabler is not required, it's a no-op, however android_lowram_disabler will bring back disabled features per user choice.
Click to expand...
Click to collapse
I see and I could report this is the case in the system...
But I swear I don't understand why the status bar still is transparent on the homescreen and in various programs.
Btw did you investigate using the ro.config.small_battery flag? I'm not sure if huashan would fit the bill (even though, assuming you still have the original battery it may as well do) but perhaps tsubasa could qualify.

sir can i do dirty flash if i want to downgrade to aosp oreo or nougat? i got a bit unresponsive on pie
i want to keep my app data if it possible

Not really expecting an answer at this point but here goes...
I am using a really early build of this rom (4/2019), but it works really well.
I've also installed the latest version of Magisk using Bootbridge. My problem is that I can't seem to make it pass the safetynet check, says false on both CTS Profile and Basic Integrity.
I've tried a lot of things, but nothing seems to work. Is it just because of the build, and something that has been repaired in later builds?

LaRazón said:
Not really expecting an answer at this point but here goes...
I am using a really early build of this rom (4/2019), but it works really well.
I've also installed the latest version of Magisk using Bootbridge. My problem is that I can't seem to make it pass the safetynet check, says false on both CTS Profile and Basic Integrity.
I've tried a lot of things, but nothing seems to work. Is it just because of the build, and something that has been repaired in later builds?
Click to expand...
Click to collapse
No version of this room pases CTS profile without a magisk module helping it to fool Safetynet. Basic Integrity failing is a weird error that does happen from time to time. Usually just reflashing everything fixes it. Keep in mind, that there have been some changes in safetynet that could be breaking it for you.

HI AdrianDC, thank you for all you work, i think its amazing, i Tryed this rom from yesterday, and everything is going perfect, navigation on this emviroment is smooth, i instaled the lastest GAPPS, no issue found, even i installed FB , Instagram and another social apps, works fine to me.
But i may find some kind of bug or something, some apps that i use has a media pleyer inside to play micro- video tutorial, but i cant see them, looks like buffering only, even videos played from chrome , like news videos i cant see them, only seems buffering, maybe its only me, or i did something wrong, can you or anyone help me?, please
regards!

[ROM][10][ARM64][A320] crDroid v6.21 for Galaxy A3 2017 [10.08.2021]

IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
Video Review: if you want to see gaming performance and how this ROM are, you can watch this review video of the ROM in the J7 2016 (the ROM is the same for other Exynos7870 variants):
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3
Also a huge thanks to Peter Schiek for his €50 donation

Changelog:
android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
OTA configuration for crDroidOTA (make your device official) - android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
github.com
===== 17-04-2021 =====
- crDroid 6.17
- Fixed Live Display
- Added Night Light
- April Security Patch
- Deleted ConfigStore hal
===== 11-02-2021 =====
- crDroid 6.15 build
- Repartition script updated. Now you can get more userdata space.
- XDA release build
===== 24-01-2021 =====
- Fixed offline charging
- Added vibration intensity control
- Latest crDroid sources (v6.14 with January security patch)
- Initial a3y17lte private build for testing

GonicTEAM said:
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Click to expand...
Click to collapse
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.

Very nice to see a new ROM for the A3.
Did anyone test if bluetooth calls are working correctly and if recorded videos with apps other than Footej, are saved correctly?

SuperDeformed86 said:
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.
Click to expand...
Click to collapse
I use Astrako's device trees for crDroid, not LineageOS ones. I will see what was change, thanks!

What is the differenc beetween crdroid 6.15 and crdroid 6.9?

hi,
nice job. The ROM doesn't detect my SIM CARD. How to fix that point? Thanks for any help.

Can i use Twrp to flash this Rom and the cr droid partitionierer

Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...

Crim Soukyuu said:
Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...
Click to expand...
Click to collapse
It does say in the first page that BT calling is still broken in this ROM.
crDroid is awesome on this phone but the lack of BT calling sucks and I don't think there is developer motivation to fix.

nonsub said:
It does say in the first page that BT calling is still broken in this ROM.
crDroid is awesome on this phone but the lack of BT calling sucks and I don't think there is developer motivation to fix.
Click to expand...
Click to collapse
That's good to know, but I didn't ask about BT...

Hello, on my A3 2017 (a3y17lte), when install crdroid, it says:
Code:
updater process ended with error7
error installing zip file '/external-sdcard/crDroidAndroid-10.0-20210211-a3y17lte-v6.15.zip'
this is with last twrp, because with your orangeFox, i can't intall it, because it is for j7y17lte

yeye.phone said:
Hello, on my A3 2017 (a3y17lte), when install crdroid, it says:
Code:
updater process ended with error7
error installing zip file '/external-sdcard/crDroidAndroid-10.0-20210211-a3y17lte-v6.15.zip'
this is with last twrp, because with your orangeFox, i can't intall it, because it is for j7y17lte
Click to expand...
Click to collapse
It should work with this orangefox.
[OFFICIAL][TWRP][A320FL/F/Y] OrangeFox Recovery Project [R11.0]
DISCLAIMER 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...
forum.xda-developers.com

LuChaos said:
It should work with this orangefox.
[OFFICIAL][TWRP][A320FL/F/Y] OrangeFox Recovery Project [R11.0]
DISCLAIMER 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...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok i will try with this Version.I think it's better suited.

isaacragui said:
hi,
nice job. The ROM doesn't detect my SIM CARD. How to fix that point? Thanks for any help.
Click to expand...
Click to collapse
same here...any solutions? Tried different SIM cards and flashed ROM 2-3 times

Cheers @GonicTEAM,
Thanks for the crDroid release, hope to see more updates to this rom.
Tested the rom on a SM-A320F/DS, can confirm what other users have mentioned above, and some others:
SIM slots dont work, tested both slots. Ive added a logcat to the post. SDcard (SIM2 slot) works fine, no issue there.
Settings > Display > LiveDisplay: Cant edit the settings for bluelight filter.
Settings > Display > Lock screen display > Ambient display: To edit Ambient display settings this way does not work, either nothing happens or it jumps back to Display settings. To edit Ambient display settings, have to go through -> Settings > crDroid Settings > User Interface (tab) > Ambient display. Not a huge issue, just fyi.
Camera works fine with the native app, I use OpenCamera though and with the build.prop edit mentioned in 2nd post it works without issue.
Bluetooth/NFC seem to work, though I havent tested in depth due to sim issue.
Wifi works fine aswell, only annoyance is after reboot sometimes aireplane mode is activated and wifi off, even though it was on before reboot. But thats a small issue, not priority.
Phone encryption working aswell, no issue there as far as i can see.
Battery, havent tested per usual usage, though it does drain faster at first look.
Best regards and lookin forward to future releases,
yass

yass said:
Cheers @GonicTEAM,
Thanks for the crDroid release, hope to see more updates to this rom.
...
Click to expand...
Click to collapse
Thanks for the feedback. I don't have this device, but i compile the ROM anyway using the Astrako's device trees. I will try to fix this things if i can.

SuperDeformed86 said:
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.
Click to expand...
Click to collapse
GonicTEAM said:
I use Astrako's device trees for crDroid, not LineageOS ones. I will see what was change, thanks!
Click to expand...
Click to collapse
Please dont use this device tree from martin .This Device Tree have the Problem that adobtabel storage dont work
This is very bad for this device because it have only 16gb internal storage

Crim Soukyuu said:
Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...
Click to expand...
Click to collapse
my english is not so good
Yes it works but it was disabeld but you can enabeled it with a few commands
1.enabeled devolper options (tap 5 times on build number)
2.enabeled usb-debuging in devolper options
3.install minimal adb and fasboot on your pc
4.start minimal adb and fastboot
5.type adb devices and type yes on the prompt on your phone
6.type adb shell
7.type sm set-force-adoptable true
8.go to setting/storage/sdcard/format as internal storage

[ROM][13][UNOFFICIAL][BETA] Pixel Experience 13 Plus

{
"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"
}
Pixel Experience 13 Plus for Galaxy A70
Code:
/*
* 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.
*/
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13What is working:
- WiFi
- DualSIM, including calls on both sims
- Bluetooth
- NFC
- Camera
- Sound
- GPS
- Fingerprint scanner/Face unlock
- Sensors
- SD cards
- Double tap to wake
- Data encryption
- SELinux enforcing
- SafetyNet
- Sound in calls (since that requires clarifying now..)
- Most other basic stuff
Spoiler: Known issues
Known issues:
- VoLTE/VoWiFi, of course
Installation guide:
Spoiler: Using PE recovery
1. Recommended Samsung firmware version is A705FNXXU5DVK6, but it will work on slightly older versions too.Make sure that the bootloader is unlocked.--
2. Boot the phone into download mode. Flash Pixel Experience recovery through AP button in Odin.Download here. Note: TWRP will not work! It does not support new A13 roms with the latest changes.
Use PE recovery for the best experience, otherwise don't complain if your phone bootloops.
--
3. Boot into recovery (Vol+ and Power while USB is plugged into PC) Note: Samsung's OneUI wipes the custom recovery partition and possibly vbmeta while booting so try not to reboot into Android.
--
4. Format data and system in the recovery--
5. Flash the rom in "Apply update" menu. There are 2 ways to install:
On the phone: Copy the zip to a FAT32-formatted microSD card and install it in recovery.
With a PC: Use Minimal ADB on Windows. Open "cmd-here" and type
Code:
adb sideload <rom-file>
where <rom-file> is the filename (drag-and-drop the zip file into cmd window).
--
6. (Optional) If you want superuser access, flash Magisk in the same way that you flashed the rom.We now have a working ramdisk so newest Magisk works fine ^^
--
7. Reboot and enjoy
Downloads:(Update recovery and clean flash if coming from 2023.01.04!)
ROM: 2023.06.18Recovery: 2023.06.18*Please report any bugs that you find before we go official!
Changelog:
Spoiler: Click to open
See here for full changelogs: https://github.com/rtd1250/a70q_OTA/releases
Like my work? Consider donating
Buy rtd1250 a Coffee. ko-fi.com/rtd1250
Become a supporter of rtd1250 today! ❤️ Ko-fi lets you support the creators you love with no fees on donations.
ko-fi.com
Credits:
* @rttxda @ataberkozen @haky 86
* Grarak for the original 17.1 trees
* Simon1511 for his work on Lineage for similar Samsung qcom phones
* All PE devs
Source code:
https://github.com/PixelExperience
https://github.com/rtd1250/android_device_samsung_a70q
https://github.com/rtd1250/android_kernel_samsung_sm6150
https://github.com/rtd1250/proprietary_vendor_samsung_a70q
Other info:
OS version: Android 13
Linux version: 4.14.190
Recommended firmware: A705FNXXU5DVK6
Build date: 18/06/2023

So far so good on the a70(sm-a705mn), I just made the installation without problems, thank you very much for continuing to create roms for the a70q, now only remains to test the pixel experience rom.

Working well on (SM-705GM). No issues except screen gets brighter while unlocking device. Easy and Quick installation. Excellent installation guide. Thanks for this rom.

Came from the crDroid A12 GSI. This is such a lovely ROM. Really impressed, working fine and fingerprint is better than the official Samsung ROM. Great stuff. The hardware on this phone is still great and Samsung ditching it at Android 11 seems like such a waste.

New update is out, fixing a battery drain issue and homescreen stutters.
Unfortunately, it requires a recovery update and a clean flash due to filesystem-related changes, so please back up your data (for example make a google backup) before updating!
Upgrade process is basically: reflash new recovery, wipe data, flash the .zip, like in install guide.
This shouldn't be an issue in the future builds, sorry for the inconvenience.

rttxda said:
New update is out, fixing a battery drain issue and homescreen stutters.
Unfortunately, it requires a recovery update and a clean flash due to filesystem-related changes, so please back up your data (for example make a google backup) before updating!
Upgrade process is basically: reflash new recovery, wipe data, flash the .zip, like in install guide.
This shouldn't be an issue in the future builds, sorry for the inconvenience.
Click to expand...
Click to collapse
Thanks!, I actually installed yesterday and yeah, I feeled the battery drain, so thanks for updating it!

apexRathalos said:
Thanks!, I actually installed yesterday and yeah, I feeled the battery drain, so thanks for updating it!
Click to expand...
Click to collapse
I'm actually impressed with how good the battery is compared to crDroid GSI. No issues on homescreen either (using Nova). Installed only a few days ago!

I can't turn on this settings

Natram1zh said:
I can't turn on this settings
Click to expand...
Click to collapse
yeah that only works on lineage currently, I'll troubleshoot that later.
steford said:
I'm actually impressed with how good the battery is compared to crDroid GSI. No issues on homescreen either (using Nova). Installed only a few days ago!
Click to expand...
Click to collapse
GSIs are pretty terrible from my experience, so I feel like actually porting the rom is worth the effort.

It's crazy how this rom is so smooth. Well done

The ROM is awesome.. very good work
The bugs are:
1- screen of FOD not working
2- vibration on answering and ending calls not working .. I am not sure if it was working on other ROM versions ..
Thumbs up..

Munir.jacob90 said:
The ROM is awesome.. very good work
The bugs are:
1- screen of FOD not working
2- vibration on answering and ending calls not working .. I am not sure if it was working on other ROM versions ..
Thumbs up..
Click to expand...
Click to collapse
1. Answered 2 posts above
2. Didn't know about that (can't test currently..), but there were some vibrator-related changes indeed

rttxda said:
1. Answered 2 posts above
2. Didn't know about that (can't test currently..), but there were some vibrator-related changes indeed
1. Yes I know I just mentioned it
2. Hope it can be fixed..
Click to expand...
Click to collapse

Loving the ROM, works great.
Sorry to be nitpicky but could you fix the aliasing on the rounded corners. Think it's in a file called dimens.xml. Just needs a proper rounded corner value set I think. It'll also make the Google Assistant swipe animation follow the rounded corners.
I can't remember off the top of my head on how I fixed it for the A50 but I believe I removed the separate top and bottom values and replaced them with just rounded_corner_radius.

RandomAJL said:
Loving the ROM, works great.
Sorry to be nitpicky but could you fix the aliasing on the rounded corners. Think it's in a file called dimens.xml. Just needs a proper rounded corner value set I think. It'll also make the Google Assistant swipe animation follow the rounded corners.
I can't remember off the top of my head on how I fixed it for the A50 but I believe I removed the separate top and bottom values and replaced them with just rounded_corner_radius.
View attachment 5806719
Click to expand...
Click to collapse
I did notice that at some point but completely forgot about it. Thanks for reminding me

Android Auto isn't working.

markadrian031 said:
Android Auto isn't working.
Click to expand...
Click to collapse
Oh, unfortunate. Android Auto support on custom roms has always been kind of hit-and-miss anyways, on many devices across many different roms. It's not that high of a priority for rom devs. Either way I can't test that since my stereo doesn't have AA

markadrian031 said:
Android Auto isn't working.
Click to expand...
Click to collapse
Worked fine for me. My car is a wired android auto version. Is yours wireless by any chance? I can't test that.

Random Bootloops Randomly When Restarting The Device So Much ??
Can you please tell me a fix or something for this ,, it's always happening with me since I bought the phone and started to install custom roms on it !!

XxLightAngelXx said:
Random Bootloops Randomly When Restarting The Device So Much ??
Can you please tell me a fix or something for this ,, it's always happening with me since I bought the phone and started to install custom roms on it !!
Click to expand...
Click to collapse
Sounds like either an issue with your phone or the way you install stuff. What's the model? (SM-A705XX)

Database Develop

welcome