Devices supported:
R7f ONLY
Latest Build: 10-10-18
Changes:
* Latest Security patch
* Latest LineageOS sources
* Attempt to fix recent issues with partition(s)
* Wireguard Kernel integration
1. In order to use Wireguard VPN. Download the App
2. Root (addonsu) is required
Info
I'm not the author of the previous unofficial rom from august last year
The biggest change compared to last years version
This release is a pure R7f source! directly from Lineage&TheMuppets gitrepo
If I remember correctly the older ROM used device sources from the R7g (or R7s)
Security Patch Level March 2018. CVE-2017-14911 patched etc etc
What's working :
Boots (very convenient)
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Camera (Video And Photo)
Audio (Record and Playback)
Sensors
Flash
LED
GPS
What's not working :
You tell me, Haven't found issues yet.
(From ColorOS) Installation:
1. Boot phone in fastboot mode: Press and hold both Power + Volume Up buttons.
2. Unlock boot loader with command: fastboot oem unlock
3. Flash recovery with command: fastboot flash recovery name.recovery.img
4. Reboot phone into recovery mode using command "fastboot reboot-bootloader" and press and hold Volume Down button.
5. Do full wipe. So put ROM and Gapps on a SD card or use ADB to transfer them to the (now wiped) internal Data partition.
6. Install ROM and GApps.
7. Reboot phone and wait (first boot will take quite a bit of time).
Download :
*Please read notes down below before continuing
[ROM] *unrar archive! comes with md5 checksum and flashable zip
[Gapps] -> ARM -> 7.1 ->....
Don't use the Aroma variant. TWRP doesn't like it
[TWRP] * Important update/install the latest TWRP (3.2.1-0) due to partition layout changes
DEVICE SPECIFIC CHANGES :
Compared to unofficial LineageOS (14.1-20170803) build for R7f by another person back on OPPO Community forum (Before they pulled the int pages...)
The following 'Device Specific' changes are included in this build (Huge thanks to mikeNG)
Enabled screen burn-in protection support
Cleaned up bluetooth configration file(s)
Added Camera blobs from Project Spectrum (Beautification, Face detection)
Added TWRP decrypt support
Updated msm8939 source(s)
NOTES:
*This is bat country! (You are on your own when something goes bad, bricked device etc etc not my fault)
*Precausion: Charge battery atleast 80%
*Adviceable: Make Nandroid backup before flashing
*Precausion: Due to device specific source-file changes compared to previous 14.1 build, flashing this release without a full wipe might have undesired consequences (thermonuclear war? who knows)
Wise to perform full wipe before flashing.
*Precausion: Due to a weird device specific bug (Eventho I can't replicate it atm with my current build)
Don't (re)boot into Recovery nor flash the R7 with the USB cable still attached. Could result in a bootloop which is rather hard to get out off
When successfully powered off eventually, leave it off for at least 20+ min. Take a walk or something! Should boot normally after cooldown-time.
Hi
may i ask what camera app I should use? Is it possible to install and use the original r7 oppo camera app?
Thanks in advance
xaauser said:
Hi
may i ask what camera app I should use? Is it possible to install and use the original r7 oppo camera app?
Thanks in advance
Click to expand...
Click to collapse
Stock provided camera app seems to work perfectly
Not sure if the r7 ColorOS camera app would work
JJRT said:
Stock provided camera app seems to work perfectly
Not sure if the r7 ColorOS camera app would work
Click to expand...
Click to collapse
oh alright! thanks!
Just another query - is it normal that CPU-Z app and AIDA64 app reports the soc to be working at 200MHz to 1.1GHz instead of 1.5GHz? (and also cpu0-3 are always reported to be "stopped" or "sleeping")
Is this a bug?
xaauser said:
oh alright! thanks!
Just another query - is it normal that CPU-Z app and AIDA64 app reports the soc to be working at 200MHz to 1.1GHz instead of 1.5GHz? (and also cpu0-3 are always reported to be "stopped" or "sleeping")
Is this a bug?
Click to expand...
Click to collapse
The R7f has a Octa-core (4x1.5 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53)
Cpu-clock speed is on demand, spares battery lifetime.
The 4x 1.0Ghz cores (or to be more precise 1113mhz) are always active, ranging between 200mhz ~1113mhz.
When idle and/or low utilization the first 4x1.5ghz are turned off by the kernel.
Programs like CPU-z etc etc only read current cpu state of the active cores.
Not a bug, it's working like intended
JJRT said:
The R7f has a Octa-core (4x1.5 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53)
Cpu-clock speed is on demand, spares battery lifetime.
The 4x 1.0Ghz cores (or to be more precise 1113mhz) are always active, ranging between 200mhz ~113mhz.
When idle and/or low utilization the first 4x1.5ghz are turned off by the kernel.
Programs like CPU-z etc etc only read current cpu state of the active cores.
Not a bug, it's working like intended
Click to expand...
Click to collapse
oh nice! thanks btw for giving this old device a new lease of life!
hi btw will u be willing to update the rom to lineageos 15 (or have treble support) ?
Bootloop issues
Hello, so ive just installed this rom wif the latest open gapps via twrp 3.2.1.0
But the phone is now unable to start. When powering on, the lineageos logo will appear for a few seconds before the phone restarts. However, im still able to access the recovery by holding power and vol down. What can I do now?
ph03nae said:
Hello, so ive just installed this rom wif the latest open gapps via twrp 3.2.1.0
But the phone is now unable to start. When powering on, the lineageos logo will appear for a few seconds before the phone restarts. However, im still able to access the recovery by holding power and vol down. What can I do now?
Click to expand...
Click to collapse
I don't know if this would help. I have a r7plusf, and had the same problem. I solved it by booting into recovery and wiping system, dalvik and cache and immediately flashing the rom and gapps again.
kishd said:
I don't know if this would help. I have a r7plusf, and had the same problem. I solved it by booting into recovery and wiping system, dalvik and cache and immediately flashing the rom and gapps again.
Click to expand...
Click to collapse
Thanks my problem is solved (although it took multiple tries...)
And I've tested the camera and realised it is pretty noisy even in acceptably lit conditions, unlike in the stock ROM. Any reason for this? Is this also happening for r7plusf?
Hello JJRT so do u still plan to maintain the ROM?
will VOOC supported on this rom
@TIrR Yes but slow, Will try to release builds with major device specific changes
Currently trying to build a 15.1 rom stable enough for daily use (Don't get hopes up just yet)
@xinghao2003
Yes has native support for VOOC
@ph03nae
Change the camera settings within camera app. Default settings aren't fully utilizing the camera's capabilities
Set quality @ 100% and set resolution to max. Et cetera
Having a BIG problem
The rom using 4 small core instead of using all core and isn't possible to force the big core run
xinghao2003 said:
The rom using 4 small core instead of using all core and isn't possible to force the big core run
Click to expand...
Click to collapse
see page 1 it's already explained.
Not a problem or issue just cpu-on-demand
So what can I do with it? Can I using apps to force it run or other ways?
Wow, I didn't expect a new build to appear for this phone again. Thanks for your effort!
I'll take it for a spin later on today.
*UPDATE*
Since my phone was encrypted and TWRP is not able to decrypt the data partition I successfully sideloaded the zip on top of the previous 14.1 build. While the first boot took a long long time, I assume due to the cache I cleared, all is working with no loss of apps nor data.
I have not noticed any camera quality loss as has been reported earlier on in this thread.
Forage81 said:
Wow, I didn't expect a new build to appear for this phone again. Thanks for your effort!
I'll take it for a spin later on today.
*UPDATE*
Since my phone was encrypted and TWRP is not able to decrypt the data partition I successfully sideloaded the zip on top of the previous 14.1 build. While the first boot took a long long time, I assume due to the cache I cleared, all is working with no loss of apps nor data.
I have not noticed any camera quality loss as has been reported earlier on in this thread.
Click to expand...
Click to collapse
No the camera quality is perfect, only thing is user has to set the settings accordingly.
The default settings aren't perfect (quality @ normal)
But I'm here to suprise you again! Look at the main page R7 Plus General.
Just released a 15.1 build, still experimental but so far it seems to be working great (after weeks of failed builds and frustration)
xaauser said:
hi btw will u be willing to update the rom to lineageos 15 (or have treble support) ?
Click to expand...
Click to collapse
Done.
Check main thread page (R7 Plus General)
I have used this cusrom. overall very nice, no bugs. suitable for daily use.
Vooc charge, double tap to sleep and to wake, and camera very good
I hope you can fix a small bug in los 15.1 soon. i fell in love first try it.
Related
[ROM][UNOFFICIAL][6.0.1][E6853/E6803] CyanogenMod 13 for the Sony Xperia Z5 Premium [ALPHA]
{
"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 E6853 and E6803
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 E6853 and the E6803
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
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@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
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
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
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
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
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
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
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
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
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions (for the Xperia Z5 !)
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
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
(You already DID a Backup of your files so nothing to worry about)
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 several minutes)
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 the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then 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
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
E68XX_TWRP3_SD_recovery.img
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
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 or requests 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!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803, ROM for the Sony Xperia Z5 Premium
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
one
two
three
Previous ("legacy") threads,
by moonbutt74:
CM13 Z5P E6853 Beta -- Updated NegaSpork
[Rootable Kernel/ TWRP 3 - E6833/E6853/E6883 Marshsmellow ] [32.1.A.1.163] AU]
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
dominicstg2 said:
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
Click to expand...
Click to collapse
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
zacharias.maladroit said:
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
Click to expand...
Click to collapse
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
dominicstg2 said:
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
Click to expand...
Click to collapse
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
zacharias.maladroit said:
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
Click to expand...
Click to collapse
dominicstg2 said:
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
Click to expand...
Click to collapse
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Oh has other people had this problem?
zacharias.maladroit said:
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Click to expand...
Click to collapse
dominicstg2 said:
Oh has other people had this problem?
Click to expand...
Click to collapse
yeah, not sure if on Z5 compact,
but certainly on Z5 Premium and Z5
waitting for 6883 ^_^
Thanks Dev.
I join the testing!
Changelog
12.07.2016 == stable/testing/UNOFFICIAL update build
upstream ROM changes 6.0.1_r56 (Android security Patchlevel: 2016-07-01 / 2016-07-05)
ADB enabled by default for better error diagnosis, ADB over WiFi disabled
fingerprint scanner might work
NFC should work again
single SIM ONLY
.
other changes: YOU tell me
.
previous custom kernel (if used) should still work + NFC too, if you encounter issues with NFC please let me know
Click to expand...
Click to collapse
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
zacharias.maladroit said:
Changelog
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
Click to expand...
Click to collapse
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Don't ask for ETAs on XDA. It is rude.
Sent from my SGP311 using XDA Labs
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Work in progress,
please take a look at the CM13 thread for the Z5, will ya ?
there are several factors that influence access and working for
microSD, sim cards (both), fingerprint scanner and others
Hi. Just curious, is it possible if I use this on E6883 (Z5 Premium Dual) and flash Dual Enabler thereafter?
Code:
[B][COLOR="Red"]Your warranty is now void.[/COLOR][/B]
I am not responsible for bricked devices, dead SD cards. Please
do some research if you have any concerns about features included in this method
before apply it!
I also do not provide any warranty! The result of a failure could include voiding of warranty and hardware damage.
Be careful! Many of these commands have a high probability of resulting in a brick if mistyped.
What you’ll need
Backup your personal data. It is good idea backup your system with twrp too
Divice Lg V20 H990
Unlocked bootloader and rooted Device ([url]https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296[/URL])
ADB (in Linux , windows)
twrp 3.2.1 recovery
New method(07-05-2018)
Here you have an only one zip rom. Flash via twrp, reboot and wait. Please be patient, you have to wait +-18mins.
Works
NFC
gps
call
sms
wifi
Bluetooth
Hotspot
Camera focus and good resolution
STEPs
Download: https://drive.google.com/drive/folders/1zZHGjigoPZq2VNjWAn-Lg4azlTst4UzW
flash
reboot
wait
Old Method
ISSUES
Bluetooth
Hotspot
Camera poor resolution
Other that you find
STEPs
Download Official Lianogeos 14 ROM and save in SDCARD (lineage-14.1-20180405-nighttly-h910-signed.zip)
Download neocore.zip kernel and save in SDCARD ([url]https://forum.xda-developers.com/v20/development/kernel-t3726416[/URL])
Save firmware wifi files (fw_bcm*) from your device (/system/etc/firmware) in your computer
Save configuration file (bcmdhd.cal) from your device (/system/etc/wifi) in your computer
Modify zip of rom to H990:
Open(not uncompress) with some zip program
go to META-INF/com/google
open and edit update-script: replace 910 by 990
save and close
Reboot into Twrp recovery, wipe system, data, cache
flash lineageos
Reboot into Twr
if twrp ask abot password, click cancel, go wipe and format data
flash neocore.zip
Reboot into Twrp
Push wireless firmware into your device (connect your device to pc):
virify your device is ready
Code:
adb devices
into via adb
Code:
adb shell
mount sytem partition
Code:
mount /dev/block/sda14 /mnt
push
Code:
exit
adb push fw_bcmdhd.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_mfg.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_apsta.bin /mnt/system/etc/firmware
adb push bcmdhd.cal /mnt/system/etc/wifi
Reboot into SYSTEM
Enjoy!
Does this work on a H990DS
faeterov said:
Does this work on a H990DS
Click to expand...
Click to collapse
I dont have h990ds but i tried installing SuperV20 custom rom (h990ds Stock-rom based) and that works in h990, MAYBE my solution works in h990ds
You should package the zip folder and is there a result for us to use old nightly ?
I have tried with 20180419 version and this worked fine
Hi,
Possible to package the whole zip ?
@x86cpu
The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps
XolYnrac said:
The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps
Click to expand...
Click to collapse
I'm trying build it
joaovictorsouza said:
I'm trying build it
Click to expand...
Click to collapse
Let me know to test
H990ds ???
Is there any H990ds developpement guys ???
So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.
Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416
thirdzcee said:
Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416
Click to expand...
Click to collapse
The lineage patches should work fine. the kernel I use for TWRP is stock based (which needs either Lineage's patches or manually adjusting twrp's config to stop the overflow), until recently it was 99% stock.
I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.
thirdzcee said:
So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.
Click to expand...
Click to collapse
Hi, to me it isnot a disvantage, i consider that like a advantage because meaning we can manipulate the second screen. The task is that in the GUI layer add some area in the upper place, that would give us podinility to put anything in that area more than simple shortcut.
I am speculating because i dont know android architecture.
The other task is identify how neocore handle the modem and introduce that in lineageos kernel.
Yesterday i compiled lineageos based on a installation like this thread. When i installed that i only had problem with modem, wifi worked fine
iDefalt said:
I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.
Click to expand...
Click to collapse
I coul give you a screenshot runnig lineageos on my h990.
@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG
jl10101 said:
@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG
Click to expand...
Click to collapse
I will try that but I have tried with that https://forum.xda-developers.com/lg-v30/themes/cstark27-google-camera-mod-wide-angle-t3747263 the resolution is good but the focus isnt work
I'll test in H990DS. I'm building again LineageOS with the H910 binaries.
Here my own compilation of lineageos for h990 with neocore kernel.
In the screenshot we can see the complity screen but I cant see the upper left corner in the cellphone because in this part are the camera and sensors
!!! This rom has been superseded by the omnirom 9 weeklies !!!
Intro/Disclaimer:
This is an unofficial/homemade build of OmniROM 9.0 for Sony Xperia X Compact (a.k.a. 'Kugo' or 'F5321'). As OmniROM 9.0 builds are not yet officially released and the software binaries from Sony that are needed for Android Pie just recently left beta stage, bugs are to be expected. If you are unfamiliar with rom flashing, using adb and fastboot or recovering the phone after a (soft) brick, I advise against flashing this rom. If you do decide to flash this rom you acknowledge no one is responsible for any damage done to your device but you.
Rom information:
OS name: OmniROM
OS version: Android 9.0 Pie
Kernel: Linux 4.9
Security patch level: June 5, 2019
Currently known issues:
Sporadic crash/reboot when stressing GPU.
USB tethering uses data connection (3/4G) even when the phone is connected to wifi. Pay attention to your data plan when you use USB tethering. bug tracker
Connection to wifi encrypted with wpa enterprise reportedly not possible (may have improved with recent change in wifi libraries; feedback welcome).
Exfat implementation lacks (full) repairing capability.
(If you find issues missing, please let me know and I'll update the list.)
Brief installation instructions:
Backup any important files to another device.
Before first time flashing this rom, first update to / flash the latest stock rom (34.4.A.2.118), or you risk having no in-call audio.
Boot to TWRP and install the rom zip-file (and optionally opengapps).
(clean flash recommended; 'Format Data' required if device is currently encrypted, otherwise first boot will hang).
Because this is an Android Pie rom which uses a 4.9 kernel, you also need to flash a new version of Sony's software binaries to the oem partition:
Download the software binaries zip-file and unzip the image that is inside of it.
Boot to fastboot mode (power off phone; then while holding <volume up> button, connect usb cable to pc and phone. the led should turn blue.),
and flash the image to the oem partition:
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
Downloads:
omni-9-20190608-kugo-HOMEMADE.zip (download directory)
software binaries (v9)
Changelog:
08-06-2019
- Security patch level updated to June 5, 2019
- Upgraded exfat to relan's v1.3.0
23-05-2019
- Fixed: Intermediate bluetooth connection
- Fixed: Night light
- Fixed: Long-press camera button
10-05-2019
- Security patch level updated to May 5, 2019
- Switched wifi libraries to qcwcn from bcmdhd
- Fixed: QC3 charging (hardware limitation = 2A)
- Fixed: 5GHz wifi tethering
- Performance improvements for ARMv8
24-03-2019
- Fixes for software binaries v7 (probably this build is backwards incompatible with software binaries v1 to v6)
05-03-2019
- Security patch level updated to March 5, 2019
17-02-2019
- Fixed cpu usage for improved stability.
07-02-2019
- Security patch level updated to February 5, 2019
- Fixed: SELinux now enforcing (If you're experiencing (in-call audio) issues, you need to reflash stock to update the dsp partition)
- Fixed: USB-tethering
22-01-2019
- SW binaries v5 are out, and this build is backwards incompatible with previous SW versions, so only flash v5 to the oem partition or boot is going to hang on the sony logo.
- Fixed: slow sim card detection (fixed with SW binaries v5)
- Fixed: (temp workaround) random boot crash
08-01-2019
- Security patch level updated to January 5, 2019
15-12-2018
- Fixed: native camera app video recording
- Fixed: recognizing proprietary fast chargers
06-12-2018
- Security patch level updated to December 5, 2018
- Fixed: wifi-tethering
- Added feature: wireguard kernel module
- Added feature: OmniGears -> Buttons -> Music control (my own tentative hackish convolution)
08-11-2018
- Security patch level updated to November 5, 2018
Special thanks to @oshmoun for giving pointers when I encountered issues during the build process.
And of course all credits go to the whole OmniROM team for their awesome work.
OmniROM source code: https://github.com/omnirom
OmniROM gerrit review: https://gerrit.omnirom.org
Kernel source code: https://github.com/sonyxperiadev/kernel
Wireguard source code: https://git.zx2c4.com/WireGuard
Wow, I was looking to buy either a cheap x compact or a cheap xz1 compact but since @harryharryharry is here... Well I might go for this one.
I am still using ur patches from the ubuntu forum since you saved my second notebook (x205ta) from being thrown in the trash at day one.
Hah thanks, looks like we have the same preference in devices then But please don't let your purchase depend on my activity here, because I'm not a developer and pretty new to rom building. The kudos should go to the OmniROM team and people like Oshmoun for helping to maintain the device.
First impressions
Hello! I know that most of you would like to see how this rom looks like.
Consequently, here are my first impressions:
Rom is very smooth and it seems stable.
Wi-Fi and Mobile data (2G, 3G, LTE) are working.
Looks good. Personally, I prefer nougat look.
I like Omni Themes, which are personable.
Battery life is acceptable. Ram consumption ~1.1 GB
So far I found few bugs, that I hope will be fixed:
Camera Recording in stock app doesn't work.
Wi-Fi Thetering doesn't work. (Won't turn on)
Making calls is impossible - you can't here anyone (Phone app bug? Speakers are working.)
Bluetooth works for ~10 seconds and then disconnects (Same as Lineage OS 14.1 unofficial.)
Sometimes few reboots until final boot (2-4 times Selinux related?)
Selinux is set to 'permissive'
And some screenshots that you guys are waiting for.
https://drive.google.com/file/d/1PCI4fryE7g73faL43uvRwVYs7PS2OFlp/view?usp=sharing
https://drive.google.com/file/d/1YQ-7sRt9xqzC0T7dF2z4VHyRiCWgfKdP/view?usp=sharing
https://drive.google.com/file/d/1Uwmu4keaVV1m6GvX76zc5rcutncS1hjr/view?usp=sharing
https://drive.google.com/file/d/1dgJ3vsWmzgFKns-kGoFHfb0XX61D7Q95/view?usp=sharing
https://drive.google.com/file/d/14a4sC7P5nWp3QIQDJN1dV0CsBZPqwwy0/view?usp=sharing
https://drive.google.com/file/d/1GfwCgbAIR5pHAszR8ts_LdxriOdiQdiY/view?usp=sharing
https://drive.google.com/file/d/1UAMTqqb8gG2NTOKdlHWZyrKIEnGeH667/view?usp=sharing
https://drive.google.com/file/d/1qr6V2aPfNHQzpPQfWWOITu59RJvC0-xd/view?usp=sharing
https://drive.google.com/file/d/1Pt1yS9Ahp6J2yetJhx4VDSylkSpjm2mC/view?usp=sharing
https://drive.google.com/file/d/1agW2vVnperEySo-kuo1dCl1vz3fVcrT0/view?usp=sharing
https://drive.google.com/file/d/1Jh8XMPoT89LRtdovxOcjzwy-YEO7Kkwy/view?usp=sharing
https://drive.google.com/file/d/1IiOLHe6XfYuPXoinnfLz1DASNxH6gfdO/view?usp=sharing
https://drive.google.com/file/d/1CPJHx_X_a-5G_b8u91r2n2i0_IDkUht1/view?usp=sharing
https://drive.google.com/file/d/1TIjFeUS1uNHkQtB36YRrpsiD_hsgrJgC/view?usp=sharing
I'm not experiencing bluetooth issues myself with my heart rate monitor. But I saw Oshmoun also has reported an intermediate bluetooth connection issue, so I've added it to the list with known issues. Thanks for the feedback.
I'm having no problem making phone calls. Are you sure it's not related to the 'enabled but not functioning' bluetooth connection ? (I saw in the screenshots you're using a JBL headphone), I can imagine android tries to pass audio through to the (not functioning) bluetooth headphone, resulting in a muted call experience.
If other people can confirm this issue I'll add it to the list, but for now if you could do some digging into the issue, that'd be of help also.
The rebooting issue is definitely not an selinux issue, as it is set to permissive (which basically means: selinux is turned off). I'm having good hopes it (and some other known issues) will be resolved with the next version of Sony's software binaries (v3).
Connecting to other phones via Bluetooth works great.
I have a problem with transmitting audio to speakers (tested 3 different speakers - same issue - ~ 10 sec and bluetooth reboots - connection lost).
And I did phone call while I wasnt connected to bluetooth speaker, as you can see in taskbar.
https://drive.google.com/file/d/1CPJHx_X_a-5G_b8u91r2n2i0_IDkUht1/view?usp=sharing
Overall, this rom is awesome. Great job!
Strange, I tested with an old pair of bluetooth in-earbuds (earin), and I can't reproduce the issue. While I've always had issue with the sound quality (which is why I don't use them) I was able to listen to music for more than 30min (with the occasional interference, but that's likely because it's a crappy prototype). Anyhow, I think this will be addressed once this issue is solved, as it sounds very similar.
I dug into the call issue some more (which is hard because I'm not experiencing it). While calling I ran a logcat and there were some interesting errors about a mic_mute function not being implemented (also mentioned in this issue), but I don't know if that is causing your issue. I think it would be most straightforward if you make a 'adb logcat' of the bug yourself and create an issue on https://github.com/sonyxperiadev/bug_tracker/issues with the logcat attached.
I'm really interested in other people's feedback about this, is @Ketrab8 the only one having this problem while making phone calls or are other people also not hearing the other side while making phone calls?
Hi, I'm using OmniRom 8.1 since Sptember, I appreciate more your work and I want upgrade to Pie finally but why the software binaries and develop branches are from loire?
Loire is just the platform name for Xperia X and Xperia X Compact.
harryharryharry said:
Loire is just the platform name for Xperia X and Xperia X Compact.
Click to expand...
Click to collapse
upload successful but I waited 15 minutes at boot animation but still didn't open
Can you describe how you tried to install the rom ?
harryharryharry said:
Can you describe how you tried to install the rom ?
Click to expand...
Click to collapse
1-wipe cache+cache +userdata+system
2-flashzip( pi9 ommi rom)
3-fastboot flash oem SW........lorie.beta
Hmm, that ought to suffice. Only thing I can think of is that your device was encrypted and this encryption was not removed during installation. The device only very seldom boots correctly when encryption is enabled (which I've already reported on github).
If you're really set on trying the rom, you might want to retry those steps after choosing 'Format Data' in TWRP (it states in TWRP that this option will remove encryption, so one could assume wiping system+data does not)
harryharryharry said:
Hmm, that ought to suffice. Only thing I can think of is that your device was encrypted and this encryption was not removed during installation. The device only very seldom boots correctly when encryption is enabled (which I've already reported on github).
If you're really set on trying the rom, you might want to retry those steps after choosing 'Format Data' in TWRP (it states in TWRP that this option will remove encryption, so one could assume wiping system+data does not)
Click to expand...
Click to collapse
I don't know the password. Is it possible for me to load this rum? and write to me?
I'm sorry for my bad english
What password are you talking about? It's not asking for a password. If you type 'yes' it'll format your device. Be aware that all data will be destroyed, so - if you haven't already - make backups of files that are important to you.
harryharryharry said:
What password are you talking about? It's not asking for a password. If you type 'yes' it'll format your device. Be aware that all data will be destroyed, so - if you haven't already - make backups of files that are important to you.
Click to expand...
Click to collapse
backup ok.
If I do the installation after doing this, will the installation be successful?
Only way to know is to try it out.
harryharryharry said:
Only way to know is to try it out.
Click to expand...
Click to collapse
I laughed.
I want to try it now I'll make a return to you
I head
:good: Good job! I'll update the first post to reflect that the encryption issue makes it look like the rom won't boot. Thanks for the feedback.
harryharryharry said:
:good: Good job! I'll update the first post to reflect that the encryption issue makes it look like the rom won't boot. Thanks for the feedback.
Click to expand...
Click to collapse
I think I helped a little.:good:
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16
The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.
Thanks!!!
Tested and no issues found
Great Rom:good:
Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.
lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?
lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.
Works great so far. Thank you
PS: could unbrick my phone
Update in the OP. new beta release.
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.
Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
crDroid Android is a free firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
crDroid is based on the LineageOS & Android Open Source Project with extra contributions from many people within the Android community.
All the source code for crDroid is available in the crDroid GitHub repo
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware (tested over 61.2.A.0.410)
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-BQ52 (Global version)
Current build has no Gapps built-in so it's up to you either to stay Gapps-less or flash Gapps version you want (I would recommend NikGapps personally)
Make sure you have gone through the installation guide once before proceed!
Installation:
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
Bash:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
Bash:
fastboot --set-active=a
fastboot flash dtbo_a <dtbo>.img
fastboot flash vendor_boot_a <vendor_boot>.img
fastboot flash boot_a <boot>.img
Now reboot into recovery to verify the installation:
Bash:
fastboot reboot recovery
Installing ROM from recovery
Download the crDroid installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the crDroid package
On the device, select "Apply Update", then "Apply from ADB" to begin sideload
On the PC, sideload the package using:
Bash:
adb sideload filename.zip
Return to the main menu
(Optionally) If you want to install any add-ons (Gapps, Magisk..), click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from ADB", then "adb sideload filename.zip" those packages in sequence.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://sourceforge.net/projects/xperia5iii/files/crdroid13/
Device Trees & Kernel Source:
https://github.com/faust93/android_device_sony_sm8350-common
https://github.com/faust93/android_device_sony_pdx214
https://github.com/xperiaossdev/kernel_sony_sagami
Build Information
Device: Xperia 5 III (pdx214)
Build Type: Unofficial
ROM OS Version: 13
Kernel Version: 5.4.219-Krispy-v1.2
Kudos:
@Sakuu
@clfbbn
Changelog
2023-04-27:
- crDroid v9.4
- kernel side tuning and optimisations
2023-04-15:
- crDroid sources repo sync
- performance optimizations
- HW assistant button gestures fix: single, long, double click works and can be re-assigned
Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?
Gray47Maxx said:
Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?
Click to expand...
Click to collapse
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..
faust93 said:
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..
Click to expand...
Click to collapse
Neat! Based on stock, I guess?
Gray47Maxx said:
Neat! Based on stock, I guess?
Click to expand...
Click to collapse
Well, it's not GSI if that's what you meant. Closed source proprietary blobs are taken from stock ROM, otherwise just fully-fledged build from crDroid sources.
faust93 said:
Well, it's not GSI if that's what you meant.
Click to expand...
Click to collapse
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting
Gray47Maxx said:
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting
Click to expand...
Click to collapse
Aah, I see. It's my first SONY device so I'm not aware about all the nuances yet No, it's not SODP based build.
thanks very nice rom
Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.
Just installed this. Feels like I've been waiting ages for a custom ROM, and now here it is!
So far it seems too good to be true, not a single issue yet.
Sakuu said:
Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.
Click to expand...
Click to collapse
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60
bhow11 said:
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60
Click to expand...
Click to collapse
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though
Sakuu said:
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though
Click to expand...
Click to collapse
Just a prop edit?
bhow11 said:
Just a prop edit?
Click to expand...
Click to collapse
Not even that, i think you can turn it on from the settings, but qs tile is more convenient
All good thus far
Will google wallet work with this ROM?
dima_vy said:
Will google wallet work with this ROM?
Click to expand...
Click to collapse
For me it works. Magisk Delta does the trick.
After using it for a few days, it is very stable and smooth, the battery performance is also great, thank you for your efforts
Cannot get Photo Pro and other sony app running after install sony framework in Magisk delta. Any one else has the same issue?