[ROM][HIAEUHL/HIAEUL] Unofficial LineageOS 14.1 (2020/05/30)

[ROM][HIAEUHL/HIAEUL] Unofficial LineageOS 14.1 (2020/05/30) - HTC One A9

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website: http://lineageos.org
Downloads And Changelog
## 2020/05/30 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2020/04/05)
# This build have the same content but different codename dates between US and International version, just ignore it.
## Earlier Builds ##
## 2019/07/20 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2019/07/05)
## 2019/05/29 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2019/05/05)
## 2019/04/12 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2019/04/05)
# Clean up screenshot if nothing selected
## 2019/02/28 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2019/02/05)
## 2018/12/21 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2018/12/05)
## 2018/11/24 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2018/11/05)
## 2018/09/25 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2018/09/05)
## 2018/08/20 ##
HIAEUHL → DOWNLOAD HERE
HIAEUL → DOWNLOAD HERE
Code:
# Update Android security patch (2018/08/05)
## 2018/08/16 HIAEUHL ## → DOWNLOAD HERE
Code:
# Initial build for HIAEUHL
(Include the same features as 2018/08/10)
## 2018/08/10 HIAEUL ## → DOWNLOAD HERE
Code:
# Enable call recording for all regions
(Warning! Please follow your local laws to use the feature)
# Replace emoji with Android 9.0 (Pie) style
## 2018/08/08 HIAEUL ## → DOWNLOAD HERE
Code:
# Initial build for HIAEUL
# Update Android security patch (2018/07/05)
# Add speaker to list of output devices available for VoIP
Recommended Recovery (optional)
TWRP → DOWNLOAD HERE
Google Apps (optional)
OpenGApps → DOWNLOAD HERE (Choose ARM64, Android 7.1, and I recommend nano)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Addon For SU (optional)
Extras → DOWNLOAD HERE (Choose arm64, 14.1)
Addon For Dual-Speaker (optional) (Thank to Dante63 and his tutorial)
Extras (updated on 2018/12/04) → DOWNLOAD HERE (Warning! Please use at your own risk.)
Uninstall tool (back to default) → DOWNLOAD HERE
Information: Stereo effect with earpiece. READ MORE
Installation (TWRP for example)
Warning! Need a clean installation if you come from an official build:
- (Optional) Backup system and data partition
- Wipe data (a.k.a. factory reset)
- (Optional) Format data if you want to decrypt data partition
- Flash the ROM you download → DOWNLOAD HERE
- (Optional) Flash the patch for data decryption → DOWNLOAD HERE
- (Optional) Flash the addon for su → DOWNLOAD HERE (Choose arm64, 14.1)
- (Optional) Flash GApps → DOWNLOAD HERE (Choose ARM64, Android 7.1, and I recommend nano)
- (Optional) Any additional zip you want to flash
- Wipe cache and dalvik
- Reboot to system
Update from an earlier unofficial build:
- No need to wipe and format data unless you want
- Flash the ROM you download → DOWNLOAD HERE
- (Optional) Flash the patch for data decryption → DOWNLOAD HERE
- (Optional) Flash the addon for su → DOWNLOAD HERE (Choose arm64, 14.1)
- (Optional) Flash GApps → DOWNLOAD HERE (Choose ARM64, Android 7.1, and I recommend nano)
- (Optional) Any additional zip you want to flash
- Wipe cache and dalvik
- Reboot to system
About The Builds
Device tree:
https://github.com/LineageOS/android_device_htc_hiae-common
https://github.com/LineageOS/android_device_htc_hiaeuhl
https://github.com/LineageOS/android_device_htc_hiaeul
Kernel sources: https://github.com/LineageOS/android_kernel_htc_msm8952
Vendor blobs: https://github.com/TheMuppets/proprietary_vendor_htc
Contributors
intervigil, Dragonkind
ROM OS Version: Android 7.1.2 (Nougat)
Based On: LineageOS 14.1

Detailed Changelog
Why do I put this here? Because I'm lazy to upload to Github.
## 2018/08/10 ##
# Enable call recording for all regions (Warning! Please follow your local laws to use the feature)
/packages/Dialer/res/
Code:
Delete all folders called as "values-mcc(number)".
/packages/Dialer/res/values/config.xml
Code:
<bool name="call_recording_enabled">[COLOR="green"]true[/COLOR]</bool>
<integer name="call_recording_audio_source">[COLOR="green"]4[/COLOR]</integer>
/device/htc/hiae-common/configs/audio_policy_configuration.xml
Code:
<route type="mix" sink="primary input"
sources="Built-In Mic,Built-In Back Mic,Wired Headset Mic,BT SCO Headset Mic[COLOR="Green"],Telephony Rx[/COLOR]"/>
# Replace emoji with Android 9.0 (Pie) style
/external/noto-fonts/other/NotoColorEmoji.ttf
Code:
Download from "https://github.com/googlei18n/noto-emoji/blob/master/fonts/NotoColorEmoji.ttf" and replace it manually.
## 2018/08/08 ##
# Add speaker to list of output devices available for VoIP (reference)
/device/htc/hiae-common/configs/audio_policy_configuration.xml
Code:
<route type="mix" sink="Speaker"
sources="primary output,deep_buffer[COLOR="green"],voip_rx[/COLOR],direct_pcm,compressed_offload"/>
<route type="mix" sink="Wired Headset"
sources="primary output,deep_buffer[COLOR="green"],voip_rx[/COLOR],direct_pcm,compressed_offload"/>
<route type="mix" sink="Wired Headphones"
sources="primary output,deep_buffer[COLOR="green"],voip_rx[/COLOR],direct_pcm,compressed_offload"/>
<route type="mix" sink="Line Out"
sources="primary output,deep_buffer[COLOR="green"],voip_rx[/COLOR],direct_pcm,compressed_offload"/>

The Method I Use To Build This ROM (hiaeul for example)
My laptop specifics
- Intel Core-i5 5200U processor (x86_64)
- 8GB RAM (4GB+4GB)
- 256GB SSD
- Windows 10 (64-bit)
Environment
- Download and install Oracle VM VirtualBox
- Download your favorite Linux image file (ex: Ubuntu 18.04 LTS)
- Place the image file where you want
- Run Oracle VM VirtualBox and set up for a new machine
- Virtual storage needs to be 150GB at least
- Any preference you want
- Start up virtual machine
Prepare The Needing Tools
- Read this but remember to change the branch name "lineage-15.1" to "cm-14.1"
- Also change the device name "hiae" to "hiaeul"
- Add this into ".profile":
Code:
# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
PATH="$HOME/platform-tools:$PATH"
fi
- Add this into ".bashrc":
Code:
export USE_CCACHE=1
prebuilts/misc/linux-x86/ccache/ccache -M 50G
export CCACHE_COMPRESS=1
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export LC_ALL=C
- If the performance of your computer isn't enough, also add this into ".bashrc":
Code:
export USE_NINJA=false
- Modify swap size with terminator:
Code:
sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1M count=8192
sudo mkswap /swapfile
sudo swapon /swapfile
sudo swapon --show
- Do this step with another terminator window:
Code:
sudo su
echo 99999 > /proc/sys/kernel/pid_max
echo "kernel.pid_max=99999" >> /etc/sysctl.conf
- Add this into "/.repo/local_manifests/roomservice.xml":
Code:
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />
After Completion
- You can find the zip file under "/out/targets/products/hiaeul"

Thank you

Latest update working great. Thank you very much for keeping our devices updated

Great Gratitude
Great job to continue development on the 7.1 HTC One A9 branch. I especially appreciate current security patches being implemented. I came from official 14.1 branch (May 2018) and did not regret to invest my time on setting up the device from scratch once again!

Hi, nice work, i have a question, can i flash it with S-ON?, my bootloader is unlocked and my device is hiaeul, thanks in advance

Hi, just wondering if this is going to go up on the official builds page such that OTA update support starts post that.
Any chance that may happen?

Hi,
Has somebody been able to resolve the calling issue in Lineage OS 15.1?

Great ROM everything seems to be working fine up until now, just some battery issues not getting enough standby time, when can we expect the next update?

Girumarugt said:
Hi, nice work, i have a question, can i flash it with S-ON?, my bootloader is unlocked and my device is hiaeul, thanks in advance
Click to expand...
Click to collapse
Not sure coz my device is S-OFF. But I remember the answer is probably yes, preparing an RUU before you trying would be better.
AceNik said:
Hi, just wondering if this is going to go up on the official builds page such that OTA update support starts post that.
Any chance that may happen?
Click to expand...
Click to collapse
No, I've not sent this to intervigil (our hero) yet. Actually I am doing my compulsory duty, I can only use computer on weekends. I may update this ROM monthly syncing with Android security patch as I can. Thus, I may not have enough time to talk about these with intervigil currently. If there's anyone willing to send #2 of this thread to him, he/she will be our hero too.
Saad. Mk said:
Hi,
Has somebody been able to resolve the calling issue in Lineage OS 15.1?
Click to expand...
Click to collapse
Probably no, maybe yes. Nobody has confirmed what the issue is actually caused by.
Saad. Mk said:
Great ROM everything seems to be working fine up until now, just some battery issues not getting enough standby time, when can we expect the next update?
Click to expand...
Click to collapse
Monthly update I think. However I don't understand how to tweak kernel, the battery time may stay the same as the last 14.1 nightly ROM (180510), sorry.

Dragonkind said:
Not sure coz my device is S-OFF. But I've remembered the answer is probably yes, preparing an RUU before you trying would be better.
No, I've not sent this to intervigil (our hero) yet. Actually I have been in my compulsory duty, I can only use computer on weekends. I may update this ROM monthly syncing with Android security patch as I can. Thus, I may not have enough time to talk about these with intervigil currently. If there's anyone willing to send #2 of this thread to him, he/she will be our hero too.
Probably no, maybe yes. Nobody has confirmed what the issue is actually caused by.
Monthly update I think. However I don't understand how to tweak kernel, the battery time may stay the same as the last 14.1 nightly ROM (180510), sorry.
Click to expand...
Click to collapse
GREAT! I've been using the ROM as my daily for the past few weeks, I've been having random reboots and holding down the power button restarts my devce instead of showing the reeboot, power off etc tab...

Saad. Mk said:
... I've been having random reboots and holding down the power button restarts my devce instead of showing the reeboot, power off etc tab...
Click to expand...
Click to collapse
What ROM did you use when you were getting these issue?
If it comes with this unofficial 14.1 ROM, I think it might be a hardware issue or some apps causes it, coz I've never had these bugs since we got the nightly 14.1 till the last nightly build (180510).

Dragonkind said:
What ROM did you use when you were getting these issue?
If it comes with this unofficial 14.1 ROM, I think it might be a hardware issue or some apps causes it, coz I've never had these bugs since we got the nightly 14.1 till the last nightly build (180510).
Click to expand...
Click to collapse
I was using the latest 14.1 unofficial build, however I managed to fix the problem, it was substratum causing most of the issues when it overlayed the amdroid system. Otherwise the ROM's great, just really hoping for the dialbug issue on 15.1 to be fixed soon. I contacted the dev and according to him since he can't reproduce the issue on his device, theres no ETA on when the issue will be fixed or if it actually can be fixed

Saad. Mk said:
I was using the latest 14.1 unofficial build, however I managed to fix the problem, it was substratum causing most of the issues when it overlayed the amdroid system. Otherwise the ROM's great, just really hoping for the dialbug issue on 15.1 to be fixed soon. I contacted the dev and according to him since he can't reproduce the issue on his device, theres no ETA on when the issue will be fixed or if it actually can be fixed
Click to expand...
Click to collapse
Well, have you got them before, or had you done a clean installation when you flashed this ROM?
I can understand what you report, but I never get them, also have no idea about why they happen on your device...

Trying to install this since I didn't manage to get the offical 14.1 to work, but Im getting the same issue here and that is that after flashing tand pressing reboot the phone wont get past this with HTC-screen with that red "this build is for development jadda jadda". It just stops there. What can I do? Can still install my old cyanogen 13 rom and get it to run, but not 14.1 :\
Edit: Im on S-on btw if that matters. Don't actually know exactly what that means, just did it because I had to when I installed viper4android before.
Edit2: Or wait, might have been some permissive thing. Is there a way to see if have this S on or off? Sorry for the confusion

I can't understand this, but I went down from 71% in the night to 40% in the morning on standby even tho I had airplane mode turned on, it shows cellular consumption as the most.

rrkas said:
Trying to install this since I didn't manage to get the offical 14.1 to work, but Im getting the same issue here and that is that after flashing tand pressing reboot the phone wont get past this with HTC-screen with that red "this build is for development jadda jadda". It just stops there. What can I do? Can still install my old cyanogen 13 rom and get it to run, but not 14.1 :\
Edit: Im on S-on btw if that matters. Don't actually know exactly what that means, just did it because I had to when I installed viper4android before.
Edit2: Or wait, might have been some permissive thing. Is there a way to see if have this S on or off? Sorry for the confusion
Click to expand...
Click to collapse
It may be related to your firmware version that is under 2.18.617.30 (hiaeul) or the equivalent Nougat versions for hiaeuhl, you can check it first in Download Mode.
For S-ON or S-OFF status, you can check on the title of HBoot (just a white option screen).
Saad. Mk said:
I can't understand this, but I went down from 71% in the night to 40% in the morning on standby even tho I had airplane mode turned on, it shows cellular consumption as the most.
Click to expand...
Click to collapse
I've remembered somebodies get this issue for a while and never got solved, though for me I never experienced it. Try to NOT enable airplane mode, maybe it's similar to another bug, battery draining when expanded desktop is enabled coz the device wouldn't go deep-sleep.
There's good news is, we probably skip LOS 15.1 and get LOS 16.0 directly, I've noticed some LOS 16.0 gerrits for hiae uploaded.

Immense battery drains, 7 hours left me down form 100% to 83% with ZERO usage.....

Saad. Mk said:
Immense battery drains, 7 hours left me down form 100% to 83% with ZERO usage.....
Click to expand...
Click to collapse
Similar here, probably it's that the battery decays. Not sure but A9 is nearly 3-yo now.

Related

[EOL][ROM][SDCLANG-6][microg-ready][OMS Service Mode]NLOS-15.1 - 20190208

NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty isn't void: we are on an oneplus device.
*
* We are 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.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 15.1 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 15.1 on your device, or coming from another ROM:
Backup your current ROM and make sure you have backups of your data you want to keep.
Download the ROM below in the downloads section.
Download current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
Wipe system, data and caches.
Flash NLOS.
Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Optional: flash Magisk (if you need root)
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
Aytex, who made all of the banners on this post.
team-exynos5420 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
The microG Team
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
@Arnova8G2 for his GoggleCamera port.
@S4turno for this great thread on GoggleCamera Mods.
@knpk13 for debugging this OP.
Substratum Dev Team
@danieldmm for opening my eyes for the obvious...
@mcdachpappe for helping me with additional notification slider options.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04

Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564

Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.

How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped

stuff.

UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!

set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.

With the version from 18th February the setup wizard is working, if you are going for a fresh installation.

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).

nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?

Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.

Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.

OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.

nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you

For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.

UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.

Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.

[ROM][official] AICP 13.1 - o8.1 - amami

Reserved
Device-specific changelog for test builds:
(for complete ROM changelog, see AICP gerrit or ROM inbuilt changelog)
20180908_1022
- Fix connection to some mobile data networks
20180825_1523
- Upstream update
- Performance profiles
20180723_0816
- Fix mem sleep
- Other minor improvements
20180605_1939
- sdcardfs: fix space leak
20180516_0928
- sepolicy update
20180514_0941
- Minor fixes from upstream
20180507_2103
- Video recording fully fixed
20180506_0926
- Added exFAT support
20180428_0921
- Green stripe in video recording fixed
- Preferred network type should be working, connecting to network might be slow
20180411_1920
- Enforcing sepolicy
20180407_1320
- Fix issues with some displays
20180326_1629
- ANT+ added back
- Preferred network type fixed
20180321_1035
- Fix AudioFX crashes
20180319_0808
- Fix repeated NFC crashes
- Fix video recording (remaining issue: green stripe on edge on recordings)
20180302_1718
- Fix wrong hardware key settings showing
- Fix front camera crash
- Fix screenrecord and other possible media issues
20180228_1748
- Fix some background services
- Add Snap Camera, which has working back camera
Warning: switching to front camera will make it crash and you'll have to clear its data to use it again!
20180228_1042
- Timekeep working again
- Mobile internet fixed (now it takes a little longer to detect the SIM card though, so be patient after booting up your device)
- GPS fixed (probably)

Great to hear that there are people working on 8.1.
I just fixed wifi on lineage 15.1.
Some hours ago I tested your build quickly. These things were working at first glance.
wifi
rotation
LED
backlight (even with sensor)
flashlight
Keep up your work :good:

Good news, I finally managed to get mobile internet working, will try to provide a build with more fixes later

SpiritCroc said:
Good news, I finally managed to get mobile internet working, will try to provide a build with more fixes later
Click to expand...
Click to collapse
Really good news! Thank You!

New update (20180228_1042) is out!
Changelog:
- Timekeep working again
- Mobile internet fixed (now it takes a little longer to detect the SIM card though, so be patient after booting up your device)
- GPS fixed (probably)
Remaining issues:
- Inbuilt camera app not working
- Video recording broken
- Sepolicy
- Potentially everything that hasn't been tested yet, please report issues that aren't listed!
Enjoy!

Firmware liked!

Opinion
I also found some bugs. Sometimes when you lock the screen, it may not turn on the power button. And if you support it, the screen turns on. And also slows down in some areas of the animation.
My verdict: the Firmware is very good, but there are shortcomings. Please do not give up and continue to make new builds for us, because if you give up, no one will care about our phone. Thanks! :good:

I uploaded another build (20180228_1748) with some fixes and added a reserved post for changelog.
Latest build fixes some background services and adds Snap camera, which has working back but broken front camera. Switching to front camera will make it crash and you'll have to clear its data to use it again!

lovely

@SpiritCroc : thanks for your efforts on this! Have been quite amazed with my old trusty z1c on your AICP 12.1 builds and managing 10+ days idling on one charge with a new battery. I hope AICP 13. will help returning my z1c to being my daily driver.
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Code:
$ adb shell
amami:/ $ whoami
shell
amami:/ $ su -
amami:/ # whoami
root

cntmagistus said:
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Click to expand...
Click to collapse
Currently not planned
cntmagistus said:
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Click to expand...
Click to collapse
Here you can get lineage su for oreo (I have't tested it):
https://androidfilehost.com/?w=files&flid=243911
I wouldn't recommend using 14.1 su addon on oreo

cntmagistus said:
@SpiritCroc : thanks for your efforts on this! Have been quite amazed with my old trusty z1c on your AICP 12.1 builds and managing 10+ days idling on one charge with a new battery. I hope AICP 13. will help returning my z1c to being my daily driver.
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Code:
$ adb shell
amami:/ $ whoami
shell
amami:/ $ su -
amami:/ # whoami
root
Click to expand...
Click to collapse
Root access in ADB is also possible without flashing the addon. Just enable root access --> ADB only in developer options.
Then the following results:
Code:
$ adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root
$ adb shell
amami:/ #
amami:/ # whoami
root
Don't know if you know that

Update (20180302_1718):
- Fix wrong hardware key settings showing
- Fix front camera crash
- Fix screenrecord and other possible media issues

115ek said:
Root access in ADB is also possible without flashing the addon. Just enable root access --> ADB only in developer options....
Don't know if you know that
Click to expand...
Click to collapse
Oops, I should have figured that. Nevermind, thanks, you're right indeed!
@SpiritCroc Thanks for the info!

How was the battery drain in AICP 12.1? I'm coming from @munjeni's Lineage 14.1. And there the battery last some days. (Without doing much...)
Now the battery gets empty very fast, at least for me (on two different Z1C's...).
I'm looking for a good app to log the drainage and wakelocks. Are there any good (free) suggestions?

Battery drain with AICP 12.1 was very low/good. Got 10+ days (estimated), idle in flight mode. Never actually used it much as development stopped in favor of 13.1 so not a real usage number. With AICP-o8.1_amami_20180302_1718.zip I get ~48 hours according to battery estimations.

Tested this ROM and works fine. If you want Sony Based Camera in this rom, just download the port. It's for Nougat, but works with Oreo. (Video recording not working, but the developer is going to fix this issue). Also, you can flash Sony Apps Enabler, and you can install Sony Xperia Apps.
Camera: https://forum.xda-developers.com/cr...port-stock-camera-nougat-roms-t3628791/page49
Sony Apps Enabler: https://forum.xda-developers.com/an...-sony-apps-enabler-install-sony-apps-t3590477
Edit: Can't access to the Recovery. Orange LED appear , and after 5 second the phone is restarting.

I also tested the rom a little bit and so far so very good.
Bugs I found:
- video recording shows an error message
- sepolicy: when I set it to strict, I got the message that Magisk closed. After restart I have not got the message again. Maybe because of the question for superUser access.
@roland080: I can enter recovery via hardware button and via advanced start options(enabled in developer settings).

I am on aicp 12.1 . The ROM is great. Can I switch to this ROM with my kernel and twrp that is running on 12.1 and just flash the zip and gapps?

[9] LineageOS 16.0 for z3c

TWRP 3.3.1 for our z3c out of an Android 9.0 environment!
Changes:
Code:
3.3.1-0.4-z3c
* Fixed fastboot boot
* Added bootlogo
* Dropped TWRP App
Code:
3.3.1-0.3-z3c
* Fixed encryption when security patch level doesn't match the recovery's
- [url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/411862532c247aea2c7b48d52aa596b40305e9ea[/url]
Code:
3.3.1-0.2-z3c
* Added a script to handle the CPU
-> increased the battery life significant ([url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/63f864068ad2f17ae2f1202b4edc311d74e2803d[/url])
Code:
3.3.1-0.1-z3c
* Fixed time
* Further Clean up's
Code:
3.3.1-0-z3c
* Switched from Android 6.0 to Android 9.0 environment
* Completely reworked tree
* Working decryption
The latest build is attached to this post.
Old builds are available here: https://sourceforge.net/projects/ephedraceae/files/z3c/twrp/
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-9.0
How to install this build:
Rename the downloaded twrp image to twrp.img
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

Reserved

Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
EDIT 2 : everything is working

SUPER KOKA said:
Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
Click to expand...
Click to collapse
I use twrp-3.2.3 from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192.
I don't know yet about RR. I wanna see first whether we can get Bluetooth and gps working as soon as possible.

https://sourceforge.net/projects/ep...age-16.0-20190109-UNOFFICIAL-z3c.zip/download
Another build was uploaded with the latest lineageos updates including the January android security bulletin. On the device side Bluetooth was fixed

Installed without any problems
You did a great job!
Installed without any problems. It seems all functions work fine!

update
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update

SUPER KOKA said:
EDIT 2 : everything is working
Click to expand...
Click to collapse
Great to hear!
CDLion said:
You did a great job!
Installed without any problems. It seems all functions work fine!
Click to expand...
Click to collapse
Thanks!
muhibbuddin irsyad said:
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update
Click to expand...
Click to collapse
To be honestly I can't follow you. Do you mean that you don't know how to update the build? For this case you have to download manually and flash it in TWRP. There are no wipes needed.

Hi, thanks for this and how is the battery performance?

Any plans for making an LineageOS for microG rom?

Thanks for the ROM, I am using it right now, everything is working good except the camera. Can take photos, but video is not working. When I'm switching to video, the app is freezing and stuck. I tried to use the stock camera with magisk, it can't take photos or video neither. Tried manual camera too, it can take photos but no video.

etram said:
WOW ... !!!
Great Job.
What about the notification LED?
Click to expand...
Click to collapse
Just tested shortly, it seems to be broken, I will add to broken things list. Thanks to notify (?)

I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
frht5382 said:
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error
Click to expand...
Click to collapse
Are you sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192

NeoArian said:
Are you both sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192
Click to expand...
Click to collapse
Solved.I dowloaded false file which 632 mb.Now I re download true file and it work thank you

frht5382 said:
Yes I am sure.I install 2019 01 05 build it work but I try 20190109 fail everytime error code 255
edit
I've just realized I clik download button and if I download latest version green color button I download 631 mb but down of button lineage-16.0-20190109-UNOFFICIAL-z3c.zip 448 mb which one should I download ?
why different size ?
Click to expand...
Click to collapse
The 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c

NeoArian said:
Tue 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c
Click to expand...
Click to collapse
I installed thank you .How to enable root access? Or magisk work ?

frht5382 said:
I installed thank you .How to enable root access? Or magisk work ?
Click to expand...
Click to collapse
Magisk works.

[ROM][OFFICIAL][kirin][10] LineageOS 17.1

oh btw you might want to use this TWRP for flashing my builds.

LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
I didn't expect you here mr Luk. I'm gonna test it when I will be at home. I'm glad that Kirin got such a developer

Problem Resolved.
Problem Resolved.

AlexDaBoii said:
Hello! So I tried to install a custom rom called Lineage OS, version 17.1 unofficial for my SOny Xperia 10 through TWRP custom recovery. I then tried installing the GApps and then rebooted the system. Then it came up with a prompt saying that the OS was corrupted and then to factory reset it. I did just that, and then LineageOS booted up just fine. However no Google Apps could be seen. I then tried to boot in to TWRP custom recovery, however it came up with the LineageOS recovery instead. I then tried to flash TWRP and managed to get it up and running, but when I rebnooted the phone, it just brought me in a boot loop.
I tried for hours to fix it and the I finally managed to flash TWRP again, however all of my save files were gone. I then tried to flash the Stock ROM for the Xperia 10 to the "system" folder and then my device powered off. I tried to power it on again and then it came up with a prompt saying "Your device is corrupt. It can't be trusted and will not boot. Powering off in 5 sec.". I got really freaked out at this point and did not know what to do. I know that I am an idiot for doing this, but if there is any fix at all for this that anybody can tell me, then I would be very thankful.
Click to expand...
Click to collapse
If you join irc I may be able to help you:
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev

Flawless on I3123 so far. Really appreciate the work on this device.

Has somebody tried this on I3113?
Are all components working fine?

xXqepXx said:
Has somebody tried this on I3113?
Are all components working fine?
Click to expand...
Click to collapse
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.

LuK1337 said:
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.
Click to expand...
Click to collapse
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!

thesandroid said:
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!
Click to expand...
Click to collapse
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).

What gapps do you recommend? I have an i3113 and after i flashed opengapps, i always get this weird "Android setup isn't responding" "System UI Keeps crashing" thing. What can i do?

LuK1337 said:
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).
Click to expand...
Click to collapse
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.

thesandroid said:
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.
Click to expand...
Click to collapse
Yeah that doesn't sound fun. Not going to bother.
On a sidenote, next build will fix Netflix Widevine L1.

Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.

zzz00072 said:
Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.
Click to expand...
Click to collapse
You build it exactly the same you'd be building an official device.

Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
LuK1337 said:
You build it exactly the same you'd be building an official device.
Click to expand...
Click to collapse

After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
zzz00072 said:
Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse

zzz00072 said:
After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
Click to expand...
Click to collapse
hint: themuppets.

Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
LuK1337 said:
hint: themuppets.
Click to expand...
Click to collapse

zzz00072 said:
Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
Click to expand...
Click to collapse
Yikes, you're doing so much stupid stuff...
Msg me on irc if you want it done anytime soon.

[ROM] [11.0] [OFFICIAL] AICP 16.1 [instantnoodle]

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
Pixel Experience Team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
On Clean Flash: mandatory for first install !!!At the beginning, if you are on Stock OOS 11 ROM with locked bootloader, please follow the instructions for unlocking bootloader here: https://wiki.lineageos.org/devices/instantnoodle/install
1. Download the ROM and GApps to your PC with proper adb & fastboot setup.
Also download to your PC instantnoodle-recovery.img from HERE
2. Boot to bootloader and run in cmd (windows) / terminal (linux)
fastboot flash recovery instantnoodle-recovery.img
4. Boot to recovery. Tap on Factory Reset (this will erase everything on your device) then return to main menu
3. Connect your device to your PC and tap on Apply Update -> Apply from ADB and
4. Flash the ROM zip file using
adb sideload aicp_instantnoodle_r-16.1-WEEKLY-{date}.zip
5. Once its finished, reboot to recovery to flash the GApps (optional, needed for e.g. Google Playstore to work). This is mandatory becoz will switch automatically current slot and will flash GAPPS.
Once it boots to recovery, tap on Apply Update -> Apply from ADB then run
adb sideload GAPPS.zip
6. Reboot and set up your device.
7. Reboot back into recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The main workflow for flashing via recovery:
reboot to recovery -> adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip -> reboot to system
Click to expand...
Click to collapse
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 21.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
Go to Aicp Extras -> Update Centre then install new Weekly Build.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: We are building Neutrino Kernel adopted to our sources with permission by Kernel Dev
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
Common device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Join us on our Discord Channel
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:[/U[
ROM OS Version: 11.1
Kernel: Linux 4.19.176
ROM {Firmware|Vendor} OnePlus8Oxygen_15.E.35_OTA_0350.
Status: {STABLE}
Release Date: 04-03-2021
You want to see a "normal" night at the "DEV office", click here!!

AICP recovery: link HERE
---------------------------------------------------------------------------------------------------------------
New build guys
10.04.2021 UPDATE
Download aicp_instantnoodle_r-16.1-WEEKLY-20210410.zip from HERE
Changelog: link HERE
No GAPPS in the ROM.zip.
** İf you are comming from older version - no need to flash clean.
-- if you are rooted: Just go to Updater in AicpExtras choose the downloaded zip from your storage and install the update.
-- if you aren't rooted:
**** Download the zip. Connect your phone to your PC. and run adb root in terminal (or cmd windows for Win). Then run adb shell setenforce 0 and install downloaded zip as local upgrade from Updater in AicpExtras. You'll be on enforcing selinux mode after reboot
-- You can flash in recovery via adb sideload. İf you choose this way, don't forget to reboot to recovery and flash your GAPPS.zip via adb sideload again.
-- if you want to clean flash:
**** reboot to recovery. Format data then follow the procedure given below:
flash rom.zip via adb sideload -> reboot recovery -> flash gapps.zip via adb sideload -> reboot to system
What's new:
1. April '21 ASB merged
2. Added ALipay fingerprint payment support
3. Screenbrightness fixes for all 3 devices
4. Many fixes including SafetyNet (fixed again)
Enjoy !!!
---------------------------------------------------------------------------------------------------------------
04.04.2021 Build !!!
Download aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip from HERE.
Changelog: link HERE.
-- There is no GAPPS in the ROM.zip.Download GAPPS from:
MindTheGapps or OpenGapps Android 11 Nano
How to install:
1. Go to recovery. Format data if you want to flash clean.
2. Apply Update from ADB
3. then adb sideload aicp_instantnoodle_r-16.1-WEEKLY-20210404.zip
4. Reboot to recovery
5. Flash Gapps via adb sideload GAPPS.zip
** İmportant: Android Auto fails to connect with OpenGapps. All good with MindTheGapps
** There is no DevicePersonalization app in these - if you want, I can provide a modified GAPPS package
6. If you want to switch in between GAPPS packages, just flash other GAPPS package on the new flash. Clean flash isn't trivial, but recommended....
*** Next flashes can go through Updater or adb sideload.
** If you flash via Updater, backup tool will handle your gapps - no need to reflash them again.
** GAPPS need to be flashed on every update if you flash via adb sideload. Flash them as it is described above.
What's new?
** Stock vibration patterns are back
** App Lock from AOSP-A
** Neutrino Kernel updated to 4.19.183
** and many more....
All feedbacks are appreciated, as always.
Cheerz
---------------------------------------------------------------------------------------------------------------
For those who want to ROOT their devices:
Download Magisk 21.4 zip: link HERE
** boot to recovery
** flash via adb sideload magisk.zip:
** reboot.
** Note that you HAVE to do this on every update.
** SafetyNet is fixed on March 5 build !!!
Enjoy !!

Which Camera we can use:
1. Using this Camera: GCam_7.3.018_Urnyx05-v2.1_Wichaya_V3.1.1_snapcam.apk
2. Also I have thix xml file under GCam/Configs7 : nrG Wichaya 7.3.018_v3.1.1.xml

finally! thanks

Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?

mattie_49 said:
Very nice. Quick question. Are Verizon a11 blobs merged ? No custom rom currently gets data for us Verizon op8 users?
Click to expand...
Click to collapse
No unfortunately. Doubt it'll work on Verizon.

semdoc said:
No unfortunately. Doubt it'll work on Verizon.
Click to expand...
Click to collapse
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?

mattie_49 said:
Thanks for quick response. I'm gonna try later anyway. He he. Why is it so hard for us to get data/signal on custom roms. Qti telephony ? Or the 5g modem that gets mm wave?
Click to expand...
Click to collapse
most likely qti telephony....

Rebuilt and re-uploaded initial build. The issue was broken adb sideload . Now fixed and all should be fine.
Download aicp_instantnoodle_r-16.1-WEEKLY-20210305.zip from HERE
Cheers.

Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Will check it out Thanx for feedback

passion8059 said:
Thanks for the rom, working great, but has same issue as all lineage based roms...video calls have audio distorted (too loud) and bad feedback from mic. Any fixes in the pipeline? Thanks again!
Click to expand...
Click to collapse
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.

semdoc said:
Can you please test this build:
Download aicp_instantnoodle_r-16.1-WEEKLY-20210307.zip from HERE
** Attempt to fix audio ssues.
If you are rooted: Just download the build to your device. Choose from AicpExtras -> Updater and flash after choosing from right upper corner.
If you aren't rooted:
1. go to recovery and flash via adb sideload and reboot.
All feeedbacks are appreciated.
Click to expand...
Click to collapse
Will update and report back accordingly. Thanks

passion8059 said:
Will update and report back accordingly. Thanks
Click to expand...
Click to collapse
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.

passion8059 said:
Have tried video call today, mic seems to be fixed but on max volume (I have 2 young boys who won't be quiet ;-)) it still distorts so have to knock it down a bit and struggle to hear what is being said.
Click to expand...
Click to collapse
LUK merged fixes for all 3 op8 devices today...
So you'll get test builds later today...

hello what interests me can we record the conversation natively?

doc411 said:
hello what interests me can we record the conversation natively?
Click to expand...
Click to collapse
Yes, we have that option in our Dialer.

semdoc said:
Yes, we have that option in our Dialer.
Click to expand...
Click to collapse
thank you very much for your quick rest

New build guys.
You can download aicp_instantnoodle_r-16.1-WEEKLY-20210309.zip from HERE.
-- Please test audio, calls - including whatsapp & telegram calls in all aspects..
-- OOS Style Clear all notificaitons button added
-- Kernel Update by Neutrino kernel dev.
Changelog: link HERE
Cheerz guys

Thanks for the update. Ringing at max is distorted still and there is a severe memory lag where you watch YouTube videos it'll play but then buffer then play again. I'm on a good broadband connection (500mb) and WiFi 6 coverage. Have cleared caches and used ex kernel manager to clear memory buffers but still the same.

Database Info

welcome