[ROM] Unofficial LineageOS 15.1 [OPM7.181205.001] for ZTE Blade S6 (P839F30) - ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De

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

Related

[ROM] [Unofficial LineageOS 14.1] [7.1.2] [Build 2018-10-10] [Oppo R7f]

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.

Lineageos 14 in V20 H990

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

[ROM][UNOFFICIAL][11][GO] Lineage OS 18.1

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Whats works:
Booting
Audio
Graphics
RIL (calls, sms, mobile data)
Wi-Fi, Wi-Fi Direct
Bluetooth
GPS, GLONASS
FM Radio
Sensors
Camera
Face Unlock
Video recording
Screen cast
Offline charging
SELinux (enforcing)
SafetyNet (with hidden Magisk or without root)
Tell me, if something does not work.
FAQ
Q: Does this ROM supports double tap to wake? A: No. And will not in future.
Q: Cannot add widgets to home screen. Widgets is not supported? A: Widgets is not supported in builtin launcher. Download any third-party home app (like Nova Launcher) and enjoy!
Q: Why split screen mode is not available? How to enable? A: Due to Android Go limitations, all forms of multiwindowing is not available on this edition of Android.
Q: When my app "foo" asks permission to access to notifications or to run on top of other apps, I see "This feature is disabled"... A: This is limitations of Android Go to save memory.
Q: Cannot use my sdcard as primary storage! A: This feature is unstable and excluded from ROM.
Q: Flashed this ROM but phone don't booting! A1: Boot to recovery and wipe /data, then reboot. A2: If your /data is formatted to f2fs, format it to ext4 and boot your phone.
Q: What is "Gapps for Android Go"? A: This is Gapps set, extracted as-is from Nokia 1 Plus Android 11 Go firmware and packaged for Lenovo A6000. Nothing removed, just fixed some permissions and added Google Camera Go.
Installation
Flash latest recovery (if needed), based on TWRP >= 3.2
Reboot to recovery
Wipe /cache and /data. If your /data is formatted in f2fs, format it in ext4, otherwise OS will not boot.
Flash the rom
Flash Gapps (Gapps for Android Go or OpenGapps ARM/Android 11/pico or nano)
Flash Magisk (also if needed)
Reboot to ROM
Spoiler: Latest changes
Build 05.09:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
NOTE: Strongly not recommended "dirty" updating. If you want to do this anyway, flash migration script before flashing the ROM!
Migration script: https://drive.google.com/file/d/15hB63RkyRpCljho9jyFTHoYWvCl4cDWe/view?usp=drivesdk
Download ROM: https://drive.google.com/file/d/1vUHuS18vDowwCSIWl8Dl4xxRHR4EHir0/view?usp=drivesdk
Gapps: Gapps for Android Go(updated!) or OpenGapps (ARM, pico or nano)
Credits to:
twain55
Moto-M8916 guys
Teo Flo
dev_harsh1998
SkepticOne
Nitrogradient
IvanHephaestus
Our Telegram discussion group: Lenovo A6000/Plus Community Discussions
Contributors
acroreiser
dev_harsh1998
Source code
Device tree: https://github.com/acroreiser/android_device_lenovo_a6000
Kernel tree: https://github.com/acroreiser/android_kernel_lenovo_a6000
Vendor tree: https://github.com/acroreiser/android_vendor_lenovo_a6000
ROM OS Version: Android 11 Go
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Hex Firmware Patch, TWRP >= 3.2
Based On: LineageOS
Version Information
Status: Stable
Created 2021-05-12
Last Updated 2021-09-13
Finally android 11 for a6000 thank you
Wow, I thought the previous version (17.1) is the last one for this device.
I am really happy I was wrong!
Thank you so much for your work acroreiser and dev_harsh1998. Also thanks to everyone who is credited!
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
[email protected] said:
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
Click to expand...
Click to collapse
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Teo Flo said:
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Click to expand...
Click to collapse
Thanks for the info, I will try that for sure...
Hey devs,
Thanks for this brand new ROM! I use this phone as a daily driver and wanted your advice on this version or the 17.1 version. Which one is likely to be maintained in the future? I understand that 17.1 is stable but will it still get more updates or security patches or should I go ahead with this 18.1 version, please?
Thank you for your help and also for keeping this phone alive in 2021.
Cheers,
S
santoshwins said:
Which one is likely to be maintained in the future?
Click to expand...
Click to collapse
Currently Lineage OS 18.1 is maintained.
Both 17.1 and 18.1 is based on my Go device tree (forked from @dev_harsh1998 lineage-16.0 tree) but lineage-17.1 branch is not maintained since february 2021.
I don't know is @twain55 can maintain 17.1 builds for a long time (better ask him).
Lineage OS 18.1 is pretty stable for daily usage by user reports and my experience with a6010 (I don't have a6000 and primarily maintaining a6010 with merging stable changes to a6000 tree).
Can a dirty flash be done from 17.1 ?
Zack316 said:
Can a dirty flash be done from 17.1 ?
Click to expand...
Click to collapse
Of course no.
New build is up!
Changes:
June security patch level
Updates from Lineage OS team
Memory and performance optimizations for 1/8 devices
Forward-ported qcom memory optimizations (frameworks/base)
Updated Binder driver (kernel)
Implemented automatic background apps memory reclaim (kernel)
Restored Qualcomm VP8 and HEVC codecs
Updated Bluetooth HAL from Nokia 1.3
Updated some media blobs
Some kernel tweaks from other low ram devices (Redmi Go, Nokia 1.3)
Workaround for broken video recording in recent versions of Google Camera Go
Recent apps screen is limited to 5 apps to save memory
Killed multiuser support - Go devices should not have this. Also this feature is pointless in our ancient phones...
Download: https://drive.google.com/file/d/1IqRTbY9CYH9Je3bmqaavjQHnn-763bx5/view?usp=drivesdk
Wow, thank you so much for the android 11 version. It is minimalistic and smooth. Loved the rom. Also thank you devs for keeping this device alive.
Needs Undervolting.
Even the standby drain is around 600ma.
Also I've bought a new battery for this, even that cannot survive more than an hour of SOT.
Please optimised the kernel or just undervolt it a bit.
Also only one of the back speaker is working,
Hi , Dear
Thank you for your your creativity
For Lenovo A6000 1G Ram & 8Gb Rom
Which version is the best 17.1 or 18.1 ??
Can i flash Twrp 3.2 on kitkat or must to be on Lolipop ??
Cheers ^_^
so this rom i cannot use my sd card right? that's super bad for me!
-ARiCK- said:
so this rom i cannot use my sd card right? that's super bad for me!
Click to expand...
Click to collapse
There is no problem with the firmware for using the SD card
I keep getting the "This build is signed with public key" error notification every time at startup.
New build us up!
Quick changelog:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
Read notes in OP before installing!
Installed the latest build. Thank you. Great work . Everything is working very good. Battery life is extremely good. Got 7-8 hours full HD youtube playback on 4g. Go version is working very smoothly ( previously was using android 5.0 stock )
...
I also have another device 10or.E which has similar SoC SD430. Can you tell me step by step instructions. Kernel source is available. ( I read about building but did not clearly understand various terms like vendor etc... Tried to create initial .mk files for the board but errors at luch command itself )

[ROM][Huawei][11][UNOFFICIAL] CAOS - Android 11 for Huawei device

C A O S [UNOFFICIAL]
Your warranty is now void!
We're 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 us for messing up your device, we will laugh at you​
CAOS (Custom AOSP OS) is a project which based on phhuson's Treble GSI AOSP 11. CAOS is a modified AOSP by eretemin which I modified to be compatible with Huawei hi6250 phones. I also provided several patches
Changelog :
CAOS 316 March 2022 version
March 2022 SPL
CAOS 315+ Febrary 2022 version
Febrary 2022 SPL
CAOS 315 January 2022 version
January 2022 SPL
Fix all storage/permission in social apps like instagram, messenger.
implemented Huawei IMS patches
added Seedvault app and option in Treble app for activating it
full fixes access for media files from some apps like WhatsApp or Telegram
backported changes from v400h device_phh_treble: All devices support unprocessed audio source
patch for gsicharger removed, should fix offline charger animation for some devices (need test)
volume dialog UI now follows rounded corners
added CAOS logo image
CAOS 314 December 2021 version
Initial build
Decembre 2021 SPL
Integrate NFC, Miracast/cast , Live Display patches
Add media patch (Fix "Error loading media" in social apps like instagram, messenger..)
Pre-requisite :
You must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! ).
Installation :
Download this file caos-v316-220321-arm64-iceows-huawei.7z:
go to TWRP
flash this file Huawei-Decrypt-Emui_8.zip to change mount data partition (disable FBE : FileBaseEncryption)
format data
reboot to TWRP again
do a full wipe (system, data, cache, dalvik/art cache) !
reboot to bootloader
extract the img from caos-v316-220321-arm64-iceows-huawei.7z
run: fastboot flash system <drag system.img here>
reboot to TWRP
resize system
(optional) flash patches :
1 - Google Apps lite : [RECOVERY]LiteGapps_arm64_11.0_v2.6_official.zip
2 - Enable AGPS : 7-AGPS-FIX-AltairVendor-v3.6-signed.zip
3 - If you are on EMUI 8.0.0.408 or sup : 8-Huawei-PRA-FixPreav-A-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most
reboot to System
(optional) install GCamGo (GoogleCamera_2.12.413042791.apk)
Enjoy !!!
Not Working :
Nothing
ROM OS Version: Android 11
ROM Kernel: Linux 4.4.x (stock 4.4.26 or Siberia_4.4.302-1.1.zip)
ROM Firmware Required: EMUI 8.0.0.360 ---> 8.0.0.402
Based On: Caos (eremitein)
Credits:
eremitein
And all the others who tested my patches and helped me improve this ROM
CAOS11 Project
GSI Treble patches. Included Phh, Andy Yan and my personal Treble works. You can using patches/solutions from here and from linked manifests (all or few my own) in none-commercial usage only and yo...
github.com
Support Group
reserved
Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?
Hykosit said:
Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?
Click to expand...
Click to collapse
CAOS , LiR, DotOS, crDRom etc. are AOSP GSI ROMs based on 'phhusson' sources, so the difference in performance, battery life, etc. is minimal. And all have some common bugs- VoLTE, native call recording, offline charging etc. If you like to take pictures, you will be disappointed with the camera...(btw, Footej camera 2-premium is a good enough replacement for gcam).
The main differences between these ROMs are in the customization options.
In my experience CAOS is faster, crDRom is customization monster, LiR is a perfect balance between battery efficiency, performance and the customization. As for DotOS, the previous version 5.1.3 was better.
hi Alf.
Indeed it is a good comparison of the different ROMs. For charging go to PHH trebble option and enable fastcharging to 4000ma. For the Volte it is in progress..., and for the camera I provide GCAM in addition
AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma.
Click to expand...
Click to collapse
-Alf- said:
offline charging
Click to expand...
Click to collapse
AltairFR said:
I provide GCAM
Click to expand...
Click to collapse
try Footej 2-premium and you'll see what I'm talking about...
Thanks you two ! That's good stuff to know
AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma
Click to expand...
Click to collapse
But won't this one harm the battery ?
-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?
moriel5 said:
Disclaimer: I am a simple user, and am not affiliated with Semaphore or ZipoApps.
Recently, Footej Camera (or officially, Footej Camera 2) was bought by ZipoApps.
After seeing things like the buyouts of software like QuickPic or certain (legacy) parts of Nano Defender and the resulting consequences, naturally I was concerned with this, especially when ZipoApps's line of business is buying existing apps and monetizing them.
After some sleuthing, I managed to get the personal cellular number of ZipoApps's CEO, Alik Hochner (I am not going to divulge any more information about how and what was needed for this, to preserve his and other involved people's privacy), and I just spoke with him a few minutes ago.
While I am not completely reassured, due to not having experience with ZipoApps's history, he did strike me as someone who does want to be able to monetize apps while protecting user's privacy to the best of his abilities, though understandably limited by the tools the current market offers without being independent of the mass market.
Make of that what you will, I will continue to keep an eye on the matter, to see whether this turns out to be a turning point for such buyouts for the better or not.
Click to expand...
Click to collapse
from :
[Android 5.0+] Footej Camera 2 2021.5.6
Get it on Google Play A brand new, fascinating, user-friendly and robust camera app is here, ready to capture, orchestrate and give a new life to your best moments… *** If you have any problem or if you can't find manual controls, before give...
forum.xda-developers.com
Hykosit said:
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Yes, look here
-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
For my part I have no problem with offline charging. Can you describe the problem?
AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
I suppose it was a question for me.
I was wondering if changing initial charging values could be harmful to the longevity of the battery as those are (i think) calibrated for specific values
AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
On A/B GSI doesn't work at all (Kirin-devices).
-Alf- said:
On A/B GSI doesn't work at all (Kirin-devices).
Click to expand...
Click to collapse
Ok
Hykosit said:
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Here is install this apk, it is modified:
- cleaned resources,
- disable wakelock,
- disable loging and analitics,
- enable premium version
AltairFR​GOOD work !!!
AltairFR​Hi Master. Please make ROM with all patches for a variety...
Nusantara_v3.2-11-arm64_avN-29082021-OFFICIAL-0849.img.xz
NusantaraROM - GSI
NusantaraProject ROM GSI (Generic system image ROM) For all devices with supported project treble.
www.pling.com
I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.
I don't have a solution but LiR build doesn't seem to have that problem. I could reboot many times on a hi3650 P9
huuhaa_tm said:
I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.
Click to expand...
Click to collapse
I have tried several roms on my honor 8 but It gets stuck with the logo ( Waiting for solutions

Development [ROM][Unofficial][pdx214][13] crDroidAndroid 13.0 - 2023-04-27

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?

Categories

Resources