Related
#include
/*
* 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.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by Open Desire Project and TeamCodefire. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
Mustaavalkosta
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON.
Reboot and enjoy.
Update instructions:
Download Nightlies
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: saga_cm11_defconfig
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I and Mustaavalkosta don't really need your money right now but if you insist on donating to us we suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
TWRP 2.8.0.0 SAGA or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_odp.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Open Desire Project, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2014-10-29
Last Updated 2017-01-04
Reserved
Bugs:
headset mic
S2w switch in device settings
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Thank you all, GODS of ROMS!!!!!!!!
So i've been using your 20141024 release and i'm sticking with it. For next release, should i make it dirty or clean install?
Awesome work :highfive:
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Thanks people!
One question...
There will be Stable versions in this thread? i mean over time of course.
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Download files are just up.
kylon said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by Open Desire Project and TeamCodefire. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
Mustaavalkosta
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
[* This should be a temp step]Download this fix.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
[* This should be a temp step]Flash mic fix.
Remember to flash boot.img via fastboot if you have S-ON.
Reboot and enjoy.
Update instructions:
Download Nightlies / [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
[* This should be a temp step]Flash mic fix.
Remember to reflash boot.img via fastboot if you have S-ON.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: saga_cm11_defconfig
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I and Mustaavalkosta don't really need your money right now but if you insist on donating to us we suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
TWRP 2.8.0.0 SAGA or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_odp.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Open Desire Project, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2014-10-29
Last Updated 2014-10-29
Click to expand...
Click to collapse
<3 :3
No sound in incoming - people don't hear me.
_hugh said:
Thanks people!
One question...
There will be Stable versions in this thread? i mean over time of course.
Click to expand...
Click to collapse
probably not.
Lapyyyyyy said:
No sound in incoming - people don't hear me.
Click to expand...
Click to collapse
flash mic fix.
kylon said:
probably not.
flash mic fix.
Click to expand...
Click to collapse
Thank you Kylon.
Three questions please:
-do we need to make a clean installation starting from this new nightly build for the first time?
-can we just dirty install for next nightly after this first one?
-will the headset mic be fixed?
Thankssssssssss
Clean install the dirty.
No guarantee
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Last kernel (from build 28.10.2014) don't work with another ROMs - bootloop/restarts... Last kernel for me is ok. I think had been something new, like problem with sim card, if u remember year ago).
Restart phone... All is ok - without any issues.
Men, thank for hard work and your time!
docertabum said:
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
tomorrow i ll make a test kernel.
connect your phone via usb and use monitor (android sdk) to see the log. or you can use adb
Kylon, how different are these nightly from your last build on the other thread? I mean, do we need to update every day? So many changes every day?
Grazie
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
kylon said:
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
Click to expand...
Click to collapse
On the first page, intallation instructions there is:
"
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
[* This should be a temp step]Download this fix."
What fix are you referring to? I found just the mic fix flinny zip attached
grazie
---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------
Lapyyyyyy said:
Last kernel (from build 28.10.2014) don't work with another ROMs - bootloop/restarts... Last kernel for me is ok. I think had been something new, like problem with sim card, if u remember year ago).
Restart phone... All is ok - without any issues.
Men, thank for hard work and your time!
Click to expand...
Click to collapse
Hi is this new rom so different from the previous one ? everything working fine so far?
thanks
kylon said:
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
Click to expand...
Click to collapse
Thanks for your effort. Besides Wifi Ap and calling mic needs fix, other than that it is working fine. I do not have headset though. Very smooth, fast and stable so far. Again thank you very much for your effort.
Same problem
docertabum said:
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
+1
dead screen after reboot
Ammiraglio said:
On the first page, intallation instructions there is:
is this new rom so different from the previous one ? everything working fine so far?
Click to expand...
Click to collapse
Hi! Everything works, with change file audio (fix is in this thread, at 1t post) works all good. Different - don't know
Hello,
Recently I downloaded the LineageOS 14.1 source code. I made some changes using IntelliJ but I find it a little cumbersome to test the source I wrote due to the following reasons:
1. I must always build the rom (building time around 20-25 minutes).
2. I have to reboot into recovery to flash the new rom
Is there any easier way to partially build the modified source and flash the changes to the device without rebooting?
UNOFFICIAL LineageOS fork with built-in microG gapps implementation.LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
While the core operating system is still released as part of the Android Open Source Project, the majority of core apps are not. It gets worse: More and more libraries and APIs are only available on phones that run various Google apps pre-installed, effectively locking third-party apps to the Google ecosystem. Several popular open-source applications already require some of Google’s proprietary libraries to be installed. Increasing demand in the free software community in addition to severe problems in Google’s proprietary software discovered by the Android modding community, have led to the development of a free software clone of Google’s proprietary core libraries and applications - the microG Project was born.
This image uses the restricted microG patch meaning only system packages embedded in the build can use FAKE_SIGNATURE permission.
I have also replaced the default chromium system webview with the bromite system webview (20190519 build) which includes extra ad-blocking and privacy patches on top of chromium.
Code:
DISCLAIMER: THERE IS NO WARRANTY OF ANY KIND APPLICABLE TO THE CONTENT BELOW
What's working:
Boots
Wifi
NFC
Bluetooth
Camera
Video Playback
Audio
Sensors
GPS
SafetyNet Check passes both Basic Integrity and CTS profile match!
Known Bugs:
Phone is not detected by adb while booted in recovery mode (TWRP). I don't know if that's a bug in TWRP or on my laptop's USB drivers. If the phone has an OS installed (checked on various ROM's) (ie booted in system mode) it is detected, but not when in it is booted in recovery mode and running the latest TWRP. Place the image in an sdcard, put it in the phone and install it from there as a workaround. (Adb sideload can also work.)
Battery consumption appears to have improved on later builds, probably because of this change.
Instructions:
Download and install the latest twrp - dl-link (Steps on how to do it not covered here.)
Reboot to recovery
Wipe Data+Cache+Dalvik+System
Install ZIP file.
Reboot
Downloads:
Latest Build: lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
20190319 Build: lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Notes:
Many thanks to Stricted for pointing me out to the patch needed to fix a phone reboot whenever the phone connected to Wi-Fi
This is an amateur hobby project. I recommend against using this image as a daily driver, and I am quite likely to be unable to help you with any problems you experience (because I don't know enough about building a ROM).
Source Code:
Complete instructions on how to build this image on your own here !
Team Exynos7580 sources
LineageOS4microG CI/CD docker image code
FAQ:
Q: What is microG?
A: The projects webpage will do a better job than me.
TLDR version: A free software implementation of some proprietary Google Play services API's.
XDA:DevDB Information
LineageOS4microG, ROM for the Samsung Galaxy S5 Neo
Contributors
Iolaum, Stricted
Source Code: https://github.com/Iolaum/s5neoltexx-lineageos-microg
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-11-18
Last Updated 2018-11-19
It seems interesting the ROM who has installed the details please as it runs the ROM
Rovar22 said:
It seems interesting the ROM who has installed the details please as it runs the ROM
Click to expand...
Click to collapse
Hello, I am not sure what you ask. Can you please elaborate?
Iolaum said:
Hello, I am not sure what you ask. Can you please elaborate?
Click to expand...
Click to collapse
Hey there, I'm guessing that he wants a log of someone who has already installed the system, to find out whether he wants to install it or not.
I'm going to flash it today and maybe post a log from a clean install, if it is helpful to anyone.
Btw thank you lolalum for the build and the instructions!
It's awesome that there's still someone left, who's trying to save us from google
Thank you for your answers, the installation is very good, what I need is the installation of "play store". Thanks for the Rom.
Sure, no problem.
Ok, now I understand: I guess you didn't know that you can't install the Playstore with microG.
The reason is, that it has been replaced by the "Fakestore" (you can find it in Settings>Apps*show system processes) It is just a fake or a placeholder to make apps "think" there is an official Playstore, when there really isn't one. So even if you tried to install it, (through Xda Labs for example) it would only be seen as an update of the Fakestore, and wouldn't work.
You can still get every app in the Playstore though, with "Aurora Store" or "Yalp Store". They both allow you to log in to your Google account and to buy apps and items. If that isn't needed "apkmirror.com" works as well.
Thank you
Rovar22 said:
Thank you
Click to expand...
Click to collapse
Glad I could help, but there is a "thank you button" for this
I've been using this rom for the past 2 days, and it worked ok, but I had issues with some calls with root and vibration settings and pretty much every time I tried to reboot to recovery the phone didn't respond at all until I removed the battery. (going to switch over to AospExtended rom now, because it supports microg as well.)
New build
New Build:
lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Added custom microG apks built with PRs that allow to pass SafetyNet check.
Added Gsam Battery monitor and Matlog libre as system apps. They require permissions that need to be given by adb or root, it's easier to use their functionality if they are built in.
New Build:
lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg apk from Nanodroid. (If Nandodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuilt so soon to include the lastest 5 Feb 2019 security update that patches a critical security vulnerability in Framework that could allow a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.
New build
New Build:
lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level march 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
I installed this ROM on top of the previous one with no problems. Process is:
Reboot into recovery
Wipe Cache, Dalvik/ART Cache and System
Install new system image (zip file) and reboot.
New build features
New Build
lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
Changelog:
Moved to new Team Exynos7580 sources.
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level May 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
Replaced android's chromium system webview with the bromite system webview. Bromite is Chromium plus ad blocking and privacy enhancements.
Installation Instructions:
Because this build is built from a slightly different source than the previous ones and the default system webview was changed, I suggest a clean install wiping data, cache, dalvik and system.
Known Issues
- Nanolx and Bromite repositories are not added in Fdroid repositories by default as intended. They need to be added manually after installation. After you do so, ignoring updates for the Play store package is recommended if you don't plan to use it. The fakestore package included by default is only intended to be there for apps that want it to be there in order to function. Nanolx's playstore app allows in-app purchaces and other functionality which may or may not work properly - I 've never tested it not intend to do so.
Source code if you want to build it yourselves.
{
"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"
}
Preamble
After TWRP first appeared for the S10 range of devices, it quickly became clear that there were some major issues with the initial builds.
Many users were understandably frustrated at losing the ability to boot their device after shutting it down, and at being unable to update Magisk after installing TWRP.
A number of users took to contacting me privately for support. I answered their questions and even shared fixed images in a few cases, but the number of support requests was rising daily and I could not keep pace with the demand.
Given that the poster of the original images (Geiti94) was evidently unable to offer fixed TWRP images in a timely fashion, I ultimately took the liberty of doing so myself in a posting to the original TWRP thread as a service to the community.
Whilst this served to relieve the immediate pressure, the ongoing need to fix bugs and make further enhancements to the software made a fork of the original project inevitable, so I have taken the step of promoting it to its own DevDB project and thread here on XDA.
Credit goes to Geiti94 for conducting the time-consuming initial legwork and releasing the original builds. His is the foundation on which this work now builds. This fork in no way implies any disrespect to him, but does strongly acknowledge the need of the S10 user base to be supplied with proper, working images and timely updates.
System-as-root with A-only partitioning scheme
All new devices launched with Android 9 are required to be factory-configured as system-as-root devices. The ramdisk image formerly used in boot.img is now merged with system.img.
For Samsung devices such as the S10 series, this means that boot.img can no longer be used to root the device. Instead, Magisk will be installed to the recovery partition and the user will be required to always boot to that partition, regardless of whether TWRP or Android is desired. The hardware keys are used at boot time to select either Magisk-rooted Android or TWRP.
This configuration dictates that TWRP and Android share a common recovery kernel. However, because TWRP cannot be booted with a stock kernel, a custom kernel must be compiled from Samsung's source code. Unfortunately, this kernel is sensitive to changes in Samsung's firmware releases from one month to the next, meaning that problems can arise if a given kernel is used with firmware newer than the version the kernel was intended for.
This unfortunate situation necessitates semi-regular maintenance releases of TWRP to keep the kernel in step with the latest version of the S10 series firmware. This requirement is further complicated by the fact that any given release of Samsung's modified kernel source code typically trails the associated firmware release by anything from a few days to a few weeks.
TWRP without Magisk
If your device is currently still unrooted and running stock firmware, you are strongly advised not to proceed with installing TWRP. First root your device with Magisk, using John Wu's excellent Samsung system-as-root-instructions for patching the firmware's AP file. Only when you have completed that procedure should you return here and continue from the Image Preparation section.
If you insist on proceeding with installing TWRP to a stock device without Magisk, you will need — at a minimum — to flash a vbmeta.img with verity disabled or you will render your device unable to boot. You can construct such an image using the following command:
Code:
$ avbtool make_vbmeta_image --out vbmeta.img
Alternatively, if you don't have a copy of avbtool at hand, the following piece of shell code will do the trick:
Code:
h=$(printf '4156423%08d1%0240d617662746f6f6c20312e312e3%0230d')
d=''
for ((i=0; i<${#h}; i+=2)); do
d="$d\x${h:$i:2}"
done
printf "$d" > vbmeta.img
Next, flash this to the vbmeta partition, using either Heimdall or Odin.
Code:
# heimdall flash --VBMETA vbmeta.img
You may then proceed with installing TWRP according to the instructions below.
Image preparation
In contrast to the original Geit94 release, these and subsequent TWRP images will not be supplied pre-rooted with Magisk. Whilst it would be trivial to offer them in this format, this kind of binary distribution of Magisk is against the terms of use laid out by Magisk's developer, John Wu.
To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Provide your freshly downloaded TWRP image file as the input.
Installation
You are now ready to flash the resulting magisk_patched.img image file to your device's recovery partition.
One quick and easy way to do this on an already rooted device is from a root shell:
Code:
# dd if=/storage/emulated/0/Download/magisk_patched.img of=/dev/block/sda15 bs=$(stat -c%s /storage/emulated/0/Download/magisk_patched.img)
1+0 records in
1+0 records out
61734912 bytes transferred in 0.426 secs (144917633 bytes/sec)
If TWRP is already installed and you are merely updating it, you may, of course, use TWRP itself to flash the new version.
If the device is not yet rooted (or even if it is), you may use Odin in Windows, but you will need to tar the image first. For example:
Code:
$ mv twrp-beyond[012]lte.img recovery.img
$ tar cf twrp-beyond[012]lte.img.tar recovery.img
And if rebooting to Windows is too disruptive, there's always Heimdall:
Code:
# heimdall flash --RECOVERY twrp-beyond[012]lte.img
Download
The latest unofficial local builds currently available are:
G970F (S10e): twrp-beyond0lte-3.3.1-3.1_ianmacd.img
G973F (S10): twrp-beyond1lte-3.3.1-3.1_ianmacd.img
G975F (S10+): twrp-beyond2lte-3.3.1-3.1_ianmacd.img
G977B (S10 5G): twrp-beyondx-3.3.1-3.1_ianmacd.img
The latest official builds are available from the official TWRP site. Note that there is no official build for beyondx (G977B), because officially supported status has not been sought.
Unless you have a very particular requirement, you are advised to use the unofficial builds for reasons discussed under Frequently Asked Questions below.
These builds are based on the latest version of TWRP, 3.3.1-0, and include a 4.14.85 kernel compiled from Samsung's latest available source code. The kernel runs in SELinux enforcing mode and has intentionally been kept as close to stock as possible in order to provide maximum compatibility with both Android and TWRP.
The builds have been well-tested and are known to work as intended on supported firmware versions. See posting #2 of this thread for details of which TWRP builds work with which versions of Samsung's firmware.
If you later find yourself running on updated firmware that is incompatible with this kernel, you have the option of flashing and rebooting to TWRP on demand. When you are finished in TWRP, you can replace your recovery image with Magisk-rooted stock recovery and reboot back to Android.
If installing TWRP on your device for the first time or reinstalling it following a firmware upgrade, do not forget to disable file-based encryption (FBE) immediately after flashing TWRP or you won't be able to read files on /data in TWRP. To achieve this (and to protect yourself against various anti-root protection mechanisms that Samsung have booby-trapped the device with), flash the multidisabler as soon as you have installed TWRP.
Device firmware updates
When it comes time to update your device's firmware, please follow John Wu's excellent instructions for patching the firmware's AP file.
Next, use Odin to flash the patched AP file, together with the stock BL, CP and HOME_CSC files. Never leave these slots empty, or your /data partition may be shrunk during the flash).
When finished, reboot back to download mode and immediately reflash your Magisk-patched TWRP image.
Alternatively, you may replace recovery.img in the patched AP file with your rooted TWRP image, thereby completing the upgrade in a single flash:
Code:
$ tar f magisk_patched_twrp.tar --delete recovery.img && tar rf magisk_patched_twrp.tar recovery.img
Lastly, boot to TWRP and reflash the multidisabler. Do not skip this last step, as flashing new firmware will have re-enabled critical security features that you must now re-disable.
Frequently Asked Questions
Q. Is there a difference between the builds offered here and those on the official TWRP site?
A. Both the official and unofficial builds are compiled from the android-9.0 branch of TWRP, using the source code of the latest official versioned release of TWRP. Any post-release changes present in the HEAD of the android-9.0 branch are usually omitted.
The latest unofficial builds may contain changes not yet integrated into the official builds, due to the bureaucratic overhead of the official release engineering process. They may also contain patches unable to be integrated into the official versions, due to policy or technical restrictions.
Additionally, the official versioning can get out of step with the unofficial versioning. This can happen, for example, if two unofficial revisions are released in quick succession, before the first sees its official release. In such a case, the second revision can find itself released with the version number intended for the first revision.
Due to the additional complexity and overhead associated with maintaining the official builds, I now recommend using only the unofficial builds.
Q. I don't want to boot Android using the custom kernel from my TWRP image. The latest TWRP kernel is often intended for older firmware. Even if there are no visible issues using this older kernel, I'm probably missing out on improvements and fixes made in the latest kernel. Is there really no other way to run TWRP on these devices?
A. There actually is another way. You can opt to flash and boot TWRP on demand, leaving a Magisk-rooted stock recovery on your device the rest of the time.
For example, you can adapt the following simple script to toggle your recovery between stock and TWRP.
Copy the below (not as the superuser) into a file, for example /storage/emulated/0/switch-recovery:
Code:
#!/bin/sh
twrp_img=/storage/9C33-6BBD/twrp-beyond2lte-3.3.1-2_ianmacd-magisk.img
stock_img=/external_sd/recovery-ase5-magisk.img
if [ -f /sbin/magisk ]; then
# We're in system: Switch to TWRP.
#
infile=$twrp_img
su='su -c'
else
# We're in TWRP: Switch to system.
#
infile=$stock_img
fi
$su dd if=$infile of=/dev/block/sda15 && reboot recovery
Then run it in Android by opening a terminal session and typing:
Code:
$ sh /storage/emulated/0/switch-recovery
It will flash your TWRP image and reboot the device to recovery. If the TWRP image isn't rooted, you'll still need to press the usual key combo to force pass-through to TWRP.
Do your work in TWRP and then run the script again from the TWRP terminal. This time, it will reflash your stock recovery image and boot you again to recovery. There's no need to press the keys this time, because you are booting to Magisk-rooted Android.
Obviously, you must change the paths in the script to match where your own images are stored.
Q. Somewhere in upgrading my firmware, rooting and installing TWRP, my /data file-system mysteriously shrank to a fraction of its former size and appears to have been wiped. What happened? Is TWRP responsible for this?
A. No. This appears to be a side-effect of using Odin to flash only an AP file to these devices, i.e. with the BL, CP and CSC slots left empty. We don't know why this causes /data to be shrunk, but we have narrowed it down to this.
To repair it, you need to boot to TWRP, select Advanced Wipe, tick Data, select Repair or Change File System followed by Resize File System. Your /data will return to its former size, but you will probably find you have lost some data. Restore a /data back-up afterwards.
Q. When I mount /system and execute commands in the TWRP terminal or over adb, I get a lot of noise about problems with the dynamic linker.
A. This problem is fixed as of version 3.3.1-1_ianmacd.
It is caused by /etc/system becoming a symlink to itself, causing infinite recursion when followed.
The screen on your text is just a warning, not an error. Your commands are being executed.
Nevertheless, noise annoys, so you can silence the warning by pasting the following commands into the terminal (with thanks to John Wu):
Code:
# mount --move /system /system_root && mount -o bind /system_root/system /system
Q. When I flash my favourite zip using this TWRP, I can't boot my device. The zip's author says these TWRP builds are to blame. Why don't you fix them?
A. Because there's nothing wrong with them. It's the installer code of your favourite zip that is broken. These builds of TWRP are merely exposing that fact. Don't shoot the messenger.
A lot of poorly written legacy installer code lazily assumes the presence of certain binaries, in particular BusyBox. However, the inclusion of BusyBox in TWRP is a compile-time option at the discretion of the builder.
Not only that, but the inclusion of BusyBox in builds of TWRP that target Android 9.0 and later is officially deprecated. Maintainers of affected devices are instead advised to use Toybox, and these builds for the S10 series comply with that advice. Furthermore, it's actually not even possible to build an official image for these devices with BusyBox included. Compilation fails on the official build server.
In short, the assumption of BusyBox on the device is unsafe and your favourite zip's author should fix his installer code. Supply him with an installation log and politely ask him to rewrite his code to be independent of this TWRP implementation detail.
Links
TWRP source code for Android 9.0
Unofficial device tree for the G970F
Unofficial device tree for the G973F
Unofficial device tree for the G975F
Unofficial device tree for the G977B
Combined kernel source code for the G97[035]F
Kernel source code for the G977B
Telegram group
XDA:DevDB Information
TWRP for Galaxy S10 Exynos series, Tool/Utility for the Samsung Galaxy S10+
Contributors
ianmacd, Geiti94
Version Information
Status: Stable
Current Stable Version: 3.3.1-3.1_ianmacd
Stable Release Date: 2019-06-12
Created 2019-04-26
Last Updated 2019-06-21
Removed
This may not apply to your build but..
I have TWRP 3.4.0-1 installed and I am trying to install a backup but every time TWRP says successful, it the log is shows and error (failed to mount '/product). What am I doing wrong?\
My S10e shows a clean install of crdriod after this. I need to install my backup so I can screenshot the recovery key for signal.
{
"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.