Related
Introduction
Hello everyone! You might/might not know that OxygenOS (and ROMs based on it) have an in-built/native call recording feature. However, it is not enabled for everyone as it is region-locked and it might/might not be illegal to record calls where you are, with/without notifying the other party that the call is being recorded.
This thread has been created with the intent of enabling this call recording feature on OxygenOS (and ROMs based on it). There are several ways to achieve this, which have been listed below. You can use any method, as per your preference, and it should work. Let's get straight to it then!
Ways to Enable
Non-Root Method(s)
ADB command via a computer
Root Method(s) (in order of recommendation)
Magisk module
Flashable zip
Tasker profile
App which runs on boot
Detailed Information and Usage
Non-Root Method(s)
Spoiler: ADB command via a computer
Requirements: A working ADB interface on a computer, USB debugging enabled on the device
Usage: Run the following command to enable native call recording:
Code:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Reboot Survival: No
Root Method(s) (in order of recommendation)
Spoiler: Magisk module
Requirements: Magisk
Usage: Download and copy the EnableOOSNativeCallRecording-Magisk v9.1.zip to your device. Once done, install it in Magisk Manager as a module.
Reboot Survival: Yes
Spoiler: Flashable zip
Requirements: TWRP
Usage: Download and copy the EnableOOSNativeCallRecording-Flashable v8.0.zip to your device. Once done, reboot to recovery (TWRP) and just flash the zip.
Reboot Survival: Yes
Note: This method should work for rootless users too, but it needs TWRP and hence an unlocked bootloader.
Spoiler: Tasker profile
Requirements: A rooted device, Tasker
Usage: Download and copy the EnableOOSNativeCallRecordingv2.prf.xml to your device. Once done, import it in Tasker as a profile.
Reboot Survival: Yes
Spoiler: App which runs on boot
Requirements: A rooted device
Usage: Download and install the EnableOOSNativeCallRecording v2.0.apk and run it. At the first launch, grant root access to the app.
Reboot Survival: Yes
Downloads
Google Drive Folder (Primary)
AndroidFileHost Folder (Mirror)
Compatibility
Device(s)
All OnePlus Devices
ROM(s)
OxygenOS
Important Read-Me Points
[Magisk module only] The module installation has been designed to use the existing TeleService.apk from your device and modify it. Hence, if you update your ROM, there is a chance that the original apk that was modified is updated with the ROM update, which might lead to bootloops/other issues after installing the update, with this module installed. To avoid this from happening, always update your ROM by following these steps: Uninstall the existing module -> Reboot -> Download and apply the system update -> Reboot -> Download and install the latest module -> Reboot your phone again once the installation is complete.
[App method only] After your device fully boots up, a notification message will appear in the status bar/pull down notification panel to let you know that call recording has been enabled (which will go after 10 seconds if you don't swipe it away).
[App method only] There is also a "Read Me" link in the notification message if you want to read a short information regarding the app.
[All methods] Please make sure that you wait for at least 30 seconds after boot before checking if the call recording menu option is visible for you under the stock dialer's settings.
[All methods] All your recordings will be stored either at /storage/emulated/0/Record/PhoneRecord OR /storage/emulated/0/Android/data/com.oneplus.communication.data/files/Record in the aac format.
[All methods] The mod works only works when using the stock OxygenOS dialer, and it will not enable call recording in any other app, like Google Dialer, etc.
[All methods] If something that is supposed to run on boot is not executing on boot, you need to turn off advanced optimisation: Settings -> Battery -> Battery optimisation -> Three dot menu (⋮) -> Advanced optimisation -> Turn off.
[All methods] The mod enables native call recording option, but may not turn on auto-recording of the calls. If you wish to do that, after using one of the methods listed above, open the Stock Dialer App -> Three dot menu (⋮) -> Settings -> Auto-record calls -> Turn on.
[All methods] If you have hidden root from the stock dialer app via Magisk Hide, the call recording option might disappear after sometime. Make sure that the stock dialer is not checked in the Magisk Hide selection list.
Disclaimers
I am not the developer of the Enable OOS Native Call Recording app. I merely stumbled upon it in OnePlus 3T's Themes, Apps and Mods forum and I take no credit for it. Please direct all your thanks and/or donations towards @padlad, the original developer of the app. Link to the original thread is here.
I am not the developer of the flashable zip. The zip was posted later in this thread and I take no credit for it. Please direct all your thanks and/or donations towards @Zackptg5, the original developer of the flashable zip.
I am not the developer of the Tasker profile. The profile was posted later in this thread and I take no credit for it. Please direct all your thanks and/or donations towards @strongst, the original creator of the Tasker profile (original idea by @Fif_).
You are doing this at your own risk. 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 are unsure of how to go about something.
It might be illegal in your country to record calls with/without notifying the other party that the call is being recorded. Either ways, you are responsible for using this mod.
Thanks To
@padlad, for creating the Enable Call Recording app and the Tasker profile
@Zackptg5, for creating the flashable zip
@strongst, for creating the Tasker profile and for being super helpful to everyone
@My Name is ShaoXIa, for doing excellent research work and making great recommendations for improving the stability and effectiveness of the Magisk module
@Taknok, for improving race condition handling at boot
@topjohnwu, for Magisk and all the work he's ever done for the community
@osm0sis, for the AnyKernel3 template and all the work he's ever done for the community
@joaomgcd, for Tasker
@Tomek Kondrat, for the mention in this XDA article
All of you guys for viewing this thread
Changelog
Spoiler: Enable OOS Native Call Recording Apk
v1.0 - Initial release
v2.0 - Enable run-on-boot
Spoiler: EnableOOSNativeCallRecording-Magisk Zip
v1.0 - Initial release for Magisk v13.1, v13.2, v13.3
v2.0 - Update for Magisk v14.0
v3.0 - Update for Magisk v15.0
v3.1 - Reduced the script execution delay from 2 minutes post boot to 10 seconds post boot
v3.2 - Slightly increased the script execution delay from 10 seconds post boot to 30 seconds post boot
v4.0 - Update for Magisk v16.0
v5.0 - Update for Magisk v17.0
v5.1 - Made the script execute the command 5 times at an interval of 30 seconds after boot
v5.2 - Made the script execute the command every minute infinitely post the initial run
v5.3 - Adjusted the script to make the infinite loop run asynchronously
v5.4 - Reverted changes made in v5.2 and v5.3 as most of the users preferred and had no issues with v5.1
v6.0 - Fixed call recording automatically getting disabled after a while
v6.1 - Reverted the last change which caused SIM settings force closes
v7.0 - Permanently fixed call recording automatically getting disabled after a while and fixed the SIM settings force close issue that was caused by the release of v6.0
v8.0 - Update for Magisk v19.0
v9.0 - Updated template and added manufacturer check
v9.1 - Base template update and manufacturer check bug fix
v9.2 - Improve race condition handling at boot and fixed installation failures with Magisk Canary
Spoiler: EnableOOSNativeCallRecording-Flashable Zip
v1.0 - Initial release
v2.0 - Updated to remove the separate init file and run the command from existing the init.rc file
v3.0 - Updated to include device codenames in addition to the official device names
v4.0 - Synced with the latest AnyKernel template and new BusyBox
v5.0 - Synced with the latest AnyKernel template and changed backup/restore method
v6.0 - Completely re-wrote flashable zip; now works for rootless users too who have an unlocked bootloader and TWRP installed
v7.0 - Added a slight delay in command execution to support Treble OOS; shifted the script to /system/etc/init
v8.0 - Permanently fixed call recording automatically getting disabled after a while
Spoiler: EnableOOSNativeCallRecording Prf Xml
v1.0 - Initial release
v2.0 - Updated parameters for stability and effectiveness
OP Update Information
Created: July 10, 2017
Last Updated: January 17, 2021
Tried it on my OOS 4.5.5 stock. Works flawlessly!
Simple word: COOL!
Sent from my OnePlus5 using XDA Labs
Works great for me. I've been played by these customer service representativeslately. No more. I'm recording all their bs so I can play it right back to them when they try to act like "Who said that?". Thank you! ?
Sent from my OnePlus 5 using XDA Labs
Thanks
You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.
djsubterrain said:
You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.
Click to expand...
Click to collapse
It's probably true in UK that you need to warn if the phone call is recorded. In some other countries it might be completely illegal to record phone calls. But at least in Finland you may record every phone call if you are a participant in that conversation without warnings or notifications.
Working on FreedomOS - thanks!
Awesome! Can we perhaps enable this using adb shell commands when not rooted somehow?
Thanks, I had to disable battery optimization for the app option 1 in order to be runned at boot.
Sent from my OnePlus 5 using XDA Labs
Flint2 said:
Thanks, I had to disable battery optimization for the app option 1 in order to be runned at boot.
Click to expand...
Click to collapse
Instead of doing that, go to Settings -> Battery -> Battery optimisation -> Three dot menu (⋮) -> Advanced optimisation -> Turn off. That should help. Try it after adding the app back to the battery optimized list.
djsubterrain said:
You know you're supposed to tell the other party that the call is being recorded? That's why every support line you ever call will warn you that "Calls may be recorded". It's a legal requirement.
Click to expand...
Click to collapse
In New York only one party had to be aware.
What is the battery consumption like?
Increases or not?
Marucins said:
What is the battery consumption like?
Increases or not?
Click to expand...
Click to collapse
I don't think it should impact the battery consumption at all. The app doesn't run in the background, and the only thing it does (on boot/when run manually) is change a toggle in secure settings. Everything else is baked into OOS. Also, I personally haven't observed any increase in battery consumption at all after using the app than the standard consumption.
Why did the command disappear after restart?
"settings put global op_voice_recording_supported_by_mcc 1"
Where to add it to be permanent? -> build.prop ??
//edit
I created a script that runs 3C Toolbox on system startup.
not working on my oos 4.5.5
Tried installing the app. It didnt ask for any root approval or didnt boot up. It didnt wok for me at all. Any suggestions ??
rgds
Lal
shadowstep said:
Disclaimer: I am not the developer of this app. I merely stumbled upon it in OnePlus 3T's Themes, Apps and Mods forum, and decided to give it a shot on my OnePlus 5. It worked like a charm, so I decided to post here for everyone's benefit. I take no credit for this work. Please direct all your thanks and/or donations towards @padlad, the original developer of this app. Link to the original thread is here.
Hi all!
Want to utilize OOS's native call recording feature without any hassles? Look no further! The app works with OOS 4.5.x flawlessly, with the OnePlus 5. There are two variants of the app, one that runs on boot (which will automatically enable the native call recording feature at every boot) and the second one that doesn't run on boot, and hence the feature will be disabled after every reboot and you will have to manually enable it (by clicking on the app icon) after the reboot.
For those curious, all that this app does is execute a root command line which enables the native call recording feature present in OOS's stock dialer. The command line is -
Code:
su
settings put global op_voice_recording_supported_by_mcc 1
Please note that this app requires root, so it will request for the root permission at it's first run. After your device fully boots up, a notification message will appear in the status bar/pull down notification panel to let you know that call recording has been enabled (which will go after 10 seconds if you don't swipe it away). There is also a "Read Me" link in the notification message if you want to read a short information regarding the app.
All your recordings will be stored at /storage/emulated/0/Record/PhoneRecord in the aac format.
Download Links:
Click here to download variant 1 (Auto-enabled at boot, call recording will be turned on automatically at every boot)
Click here to download variant 2 (Not enabled at boot, call recording will not be turned on automatically at every boot)
Have fun!
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1" seems to work for non-root too, however, might not survive restart. Lets see if I can fix that.
Marucins said:
Why did the command disappear after restart?
"settings put global op_voice_recording_supported_by_mcc 1"
Where to add it to be permanent? -> build.prop ??
//edit
I created a script that runs 3C Toolbox on system startup.
Click to expand...
Click to collapse
If you run the command manually via a terminal, it would work for the current session but as soon as you restart the phone, it would get reset to it's default value for OOS, i.e. 0. It's a hidden, secure setting and different from the stuff build.prop contains. If you want to use build.prop to enable call recording on boot, find the value below in build.prop & change it:
Code:
persist.sys.oem.region=OverSeas
[I]TO[/I]
persist.sys.oem.region=CN
This will change your phone's OEM region to China, where call recording is enabled by default by OnePlus and therefore call recording will be enabled for you too. Also, it will survive a reboot, since it's a build.prop change.
maneklal said:
Tried installing the app. It didnt ask for any root approval or didnt boot up. It didnt wok for me at all. Any suggestions ??
rgds
Lal
Click to expand...
Click to collapse
Which variant did you try? The one that auto-starts at every boot or the normal one? Also, what root system are you using - Magisk or SuperSU? All the people I know who've tried this have reported success, so I'm sure something is up at your end only.
asc366 said:
"adb shell settings put global op_voice_recording_supported_by_mcc 1" seems to work for non-root too, however, might not survive restart. Lets see if I can fix that.
Click to expand...
Click to collapse
Yeah? Interesting. My guess is that if you run the command via ADB, it doesn't need root and will work on unrooted OOS, but won't survive a reboot. However, if you run the command via a terminal emulator on the phone itself (the commands that I've mentioned in the first post), then you will need root or else the setting won't be changed. I hope this answers your question!
shadowstep said:
Yep, read my first response above. You don't need root to enable call recording, it can be done via the adb command, but it won't survive a reboot. This is where the app helps!
Click to expand...
Click to collapse
So let me get this straight; I can do the adb shell command while unrooted and running this with a terminal emulator, I need "su" (thus, root) ?
asc366 said:
So let me get this straight; I can do the adb shell command while unrooted and running this with a terminal emulator, I need "su" (thus, root) ?
Click to expand...
Click to collapse
Yes, I edited my reply in my last post for clarity. Apologies for the confusion. Don't have root? Run the command via an adb shell from a computer/laptop. Have root? Run the command via a terminal emulator on the phone itself.
Description
TDH-JR is a Magisk Module for extremely debloating ROMs based on the G920P stock nougat Android. The debloating is quite complete, so as little of your ROM actually runs after flash installing this module.
Screenshots
Coming . . .
Features
The entire debloat operation is systemless (i.e., no modifications occur to your base ROM, Magisk systemless overlays are used to prevent bloat from installing and running.
Extreme Debloat (Just enough ROM to Use, add your own apps)
The resulting debated system passes SafetyNet as long as your kernel also passes (suggest using @tdhite's SkyHigh Kernel).
Downloads
TDH-JR v1.1.20180512. (debloating based on Firrmware version G920PSPT4DRC2):
Android File Host Download
MD5: fcc0410e48d254be48c311a804ba271b
Updated for Magisk 16.40.
Updated for DRC2 stock firmware.
TDH-JR v1.0-20180101 (debloating based on Firrmware version G920PVPS4DQK1):
Android File Host Download
MD5: 5ffc47cae4dcd67bb38cb5afae17a8bb
How to Install -- FOLLOWING IN ORDER IS REQUIRED!
READ THE DISCLAIMER BEFORE INSTALLING!.
Assure you are on the appropriately similar base (stock) firmware.
Download the module from any of the download links above and place it in your /sdcard directory.
Strongly suggest downloading the latest @tdhite SkyHigh Kernel flash (installer) and place the zip in your /sdcard directory
Reboot to recovery (TWRP)
Make a backup of your existing ROM (TWRP nandroid is best)
Wipe Data, Dalvik, Cache (standard factory reset)
Strongly suggest installing (flashing) the latest @tdhite SkyHigh Kernel. That will install the kernel, root the phone with Magisk and install the kernel's support module. Note: if you do not install the SkyHigh kernel, you will have to manually install Magisk before installing the TDH-JR debloating module.
Dirty flashing coming from pure stock cannot debloat your ROM -- the bloat software is already installed and setup.
Dirty flashing over a system in which you previously installed this module cleanly (per instructions above) should work fine.
Flash (i.e., Install in TWRP) the flashable module zip file.
Reboot (to System)
Enjoy!
After cleanly installing (post a factory reset wipe) this module, the initial boot will take many minutes and may reboot once during the initial setup sequence. Many operations are taking place (e.g., Dalvik regeneration, activation, etc.).
Special Thanks and Credits
[MENTION]topjohnwu[/MENTION]@xda (For the venerable Magisk root)
XDA:DevDB Information
TDH-JR Debloating Magisk Module, Tool/Utility for the Sprint Samsung Galaxy S6
Contributors
tdhite
Source Code: https://github.com/TeamSPR/magisk-module-tdhjr
Version Information
Status: Stable
Current Stable Version: v1.1.20180512.
Stable Release Date: 2018-05-12
Created 2018-01-01
Last Updated 2018-05-13
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any software from download links provided anywhere within this thread, or convey the same to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THE PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THE PROGRAM. THE PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Disclaimer of Title Warranty
THERE IS NO WARRANTY OF TITLE FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING ANY CONVEYOR OF THE PROGRAM MAKES NO WARRANTY OF ANY KIND THAT HE OR SHE HAS ANY TITLE OR THE RIGHT TO TRANSFER ANY TITLE TO THE PROGRAM TO YOU. YOU ACCEPT THAT, IN FACT, YOU RECEIVE NO TITLE TO ANY OF THE PROGRAM.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Reserved
Thanks for this! Looking forward to testing between football games. (A guy has to have priorities.)
works great
works great love the update thanks so much no problems so far lags a little during initial setup but no lag after all set up
Nice, thanks! Am I going crazy, or are the links to the module missing?
nostrings said:
Nice, thanks! Am I going crazy, or are the links to the module missing?
Click to expand...
Click to collapse
This? https://www.androidfilehost.com/?fid=673791459329070582
I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)
Ryan-sv said:
I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)
Click to expand...
Click to collapse
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.
tdhite said:
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.
Click to expand...
Click to collapse
Oh, i also have your kernel, but ok, i'll make a backup before try this
Working great, thanks @tdhite. Kernel seems to be offering support for Synapse, is that correct?
koop1955 said:
? . . Kernel seems to be offering support for Synapse, is that correct?
Click to expand...
Click to collapse
Yup. Just install Synapse and tune to your heart's content.
Sent from my iPad using Tapatalk
koop1955 said:
This? https://www.androidfilehost.com/?fid=673791459329070582
Click to expand...
Click to collapse
Yes. The XDA Labs app wasn't showing the link (see screenshot)
I installed this and i don't have the auto rotate or portrait icon when i pull down the top of phone! It is in auto rotate and i want it in portrait mode! Any help would be much appreciative??
I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.
_Epic said:
I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.
Click to expand...
Click to collapse
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.
nostrings said:
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.
Click to expand...
Click to collapse
I haven't gotten that far into it yet. I may check it out later.
Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.
nostrings said:
Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.
Click to expand...
Click to collapse
Actually there's a rumor from two Samsung support reps that s6 may actually get oreo! Not a reliable source, but worth holding out hope!
@tdhite Thanks for this module! I just switched over from the tdhjr Rom without a hitch. Feels clean and proper. Definitely a brilliant alternative to the tdhjr rom.
I do have one question, and anyone else who might know is welcome to chime in, which package that was debloated is responsible for how Google assistant works? I thought it was just the Google app, so i installed that (and the Google Assistant app)... But i cant use smart unlock (ya know, unlock with your voice) Does it need to be installed as a system app? Or was there another google related app/package that I'm forgetting about?
Nye-uhls said:
Actually there's a rumor from two Samsung support reps that s6 may actually get nougat! Not a reliable source, but worth holding out hope!
Click to expand...
Click to collapse
That would be super, but judging by past devices and the software they got, I'd say with 99% certainty that this is it. I'd love to be proved wrong, though ?
{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is not just another ROM - it is a mobile ecosystem (ROM + online services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds are all signed with a custom private key for best trust. This also means you have to factory reset when coming from another ROM!
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
You can LOCK YOUR BOOTLOADER - if you like
Build variants (UNOFFICIAL, CUSTOM)
UNOFFICIAL builds:
full OTA support
no other differences to pure /e/. It is just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)
CUSTOM builds:
2 variants: rooted (magisk) or unrooted
removed: the app "Apps" (see FAQ why)
added: F-Droid, F-Droid priv ext, F-Droid additional repos (disabled by default), AuroraStore, Lawnchair-latest (taken from their TG group), PhoneSky (google play store - patched for microG), Magisk app when choosen the rooted variant
patched with this safetynet patch (this will not bypass safetynet though)
fully patched for AVB / dm-verity support - means you can lock your bootloader! (all builds since 3rd of Sep 2021) - yes even the rooted variant can run on locked bootloader!
SHRP included (accepted by a locked bootloader) - means when you want to use a different recovery you have to flash / re-flash it after flashing / upgrading the ROM. Including this is needed to not brick devices running on locked bootloader.
.. read all the details about locking your bootloader in this post
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
none known (yet)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build (while I am testing with SHRP only)
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything!
Planning to lock your bootloader? Read this first
Installation
Planning to lock your bootloader?
Read on here
Detailed guide:
follow MSe1969's guide here
Quick guide (assuming you have TWRP/SHRP already):
Full clean install as described here (FAQ #2). DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (planning to lock your bootloader? Read this first)
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
MSe1969, wth.. you did an AWESOME job
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot (let me know if that's the case ofc) ..
Sources
/e/ : https://gitlab.e.foundation/e
my build manifest
MSe1969's stuff
Frequently Asked Questions (FAQ)
Q #0: For CUSTOM builds only: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If your issue is not solved with selinux permissive click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there a FAQ specific for /e/?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
App alternatives (to replace google variants): click
Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
See OP
Q #8: Will my banking app (or other root detecting app) work with this ROM?
The answer is .. well .. simple. it depends.
First of all the following technique works regardless of what ROM you are using or what device. It worked with my LG G4, OnePlus 6T and now OP7tpro so its a generic "maybe-solution"
Read on here:
I am using a german banking app which works even when root gets detected. It will prompt and say thats bad but I am still able to use it. The same was the case for the TAN generator app of the same bank but it fully stopped working one day after a (forced) app upgrade.
So I started to play around and found a solution which works for me since several years but there is no guarantee it will work for you or for how long it will work. The process and steps must be followed briefly and nothing more, nothing less must be done.
The following references a banking app but it applies to any app which rejects starting when root or a custom ROM has been detected:
you need root, i.e. Magisk. This ROM has a custom build which includes Magisk already.
uninstall the currently not working banking app(s)
install & setup a work-profile manager like Insular, Shelter, (if you do not care about google trackers: Island), or [fill-in-another] ,.....
configure Magisk that it hides itself (i.e. re-package Magisk with a random name) & reboot just to be sure. and yes that works on signed and locked ROMs, too
newer Magisk versions will clone themself into the island profile during the repackage process so open island then switch to the island tab and remove the magisk app there (so not from the "mainland"!)
install the banking app(s) - BUT DO NOT start it!
clone that app into your work-profile (i.e. open Insular/Shelter/Island/.. find the app, clone it there), repeat that step for any app needed
configure Magisk hide for this app(s) and ensure you select all options (some apps can be expanded in magisk hide, select all options then)
remove any icons of your app(s) from your launcher but DO NOT UNINSTALL them!! (never)
in your work-profile manager (Insular/Shelter/Island/...) find your app and create a quick start launcher (repeat that for any app needed)
now start your banking app quick link (again it HAS to be the one created by your work-profile manager). usually you can identify that you are using the right one bc it has a mini icon of your work-profile manager on top of the regular app icon
enjoy. if it does still detect root or a custom ROM you either have not followed the above steps briefly or you are out of luck.
Background:
You cannot uninstall the app(s) from android (ever) because otherwise Magisk hide will not work. so you always need to keep that app(s) but never starting it.
It can make sense to try another work-profile manager if the above way fails for you as the app devs using different techniques
Q #9: Will DRM protected content work? | Will this ROM satisfy Safetynet?
Likely not. Yes this ROM is signed, selinux is enforcing and you can lock your bootloader but these days this is not enough anymore. While there are some workarounds available these might stop at any time. So do not expect that this will work or work for a long time.
LOCK your bootloaderYes you read correctly: you can lock your bootloader again! Why is that so amazing? The most important thing: security. When your bootloader is locked no one can install or modify without you notice it. Let's say you loose your phone and your bootloader is unlocked. The person can boot into fastboot and flash a custom recovery of his choice and have full access to your data (if not having a pin set) but also can tamper e.g. your system partitions like installing malware. Yea for that the attacker needs physical access to your phone but there is malware around and this is REAL which uses bugs to install themselves even on your system partition. For this the attacker does NOT need physical access to your phone.
On a locked bootloader the device won't boot anymore as a modification like that will be detected.
Anyways.. yea one can say both attack variants are not THAT critical or affecting you as you are paying attention on what you do but .. there is a always a risk of undetectable malware like the good old drive-by downloads etc. so .. its all up to you if you want to have that extra barrier or not..
But before we begin
a HUUUUGE thanks to @WhitbyGreg !!!
All this here would not be possible without his great guide here ! Ofc I need to adapt it and integrate all this within my automation process but it would have been a LOT harder without his thread(s).
So if you love it having a locked bootloader now - give HIM some thanks clicks, donations, hugs.. as well
Checklist: is locking the bootloader something for me?If you answer anyone - even just 1 - of the following with YES - then KEEP AWAY FROM LOCKING your bootloader!
I want to remove (not just disable) system apps (often called bloatware)
I want to add / convert apps into system apps (e.g. Titanium Backup offers such an option)
For rooted variant: I want to update Magisk to the latest version
For rooted variant: I want to change init scripts, XMLs or anything else within system/, product/ etc partitions
For rooted variant: I want to use an ad-blocker which modifies the "hosts" file (system partition)
I want to install another recovery then the one coming with the ROM (SHRP)
I want to flash GApps (LOL! this is /e/ !! even on unlocked bootloader this won't work!)
I want to flash anything else in recovery which modifies: boot, recovery, system or any other partition then userdata
Do you have answered at least 1 of the above with YES ? Then do NOT lock your bootloader. It WILL brick your device if you try.
if you can live with the above - GO GO GO
Lock your bootloader - processDownloads
ROM without root: https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom_pkmd.bin
ROM with root: https://leech.binbash.rocks:8008/e-os/a10_rooted/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom-rooted_pkmd.bin
backup all your data. I am serious EVERYTHING. we need to FORMAT the userdata partition during the lock process and there is no way around. so use TB or Swiftbackup, Migrate or any other. Always a good idea to also having a TWRP/SHRP backup just for the case..
boot your current recovery
flash the ROM of your choice (with or without root)
reboot to the bootloader / fastboot
if you flashed the ROM with root: fastboot flash avb_custom_key hotdog_eos-q_custom-rooted_pkmd.bin
if you flashed the ROM without root: fastboot flash avb_custom_key hotdog_eos-q_custom_pkmd.bin
type: fastboot oem lock
approve locking the bootloader on the phone's screen
< take a deeeeeeep breath >
recovery (SHRP) will load automatically
choose wipe -> format(!) data (there is no way around)
boot android -> you will notice a new bootloader message warning you that you have a custom ROM installed - but it will load
congrats! you now running on a locked bootloader + /e/ OS!
for the rooted variant: start the Magisk app (requires internet), accept the install request and open the magisk app afterwards and let it reboot when asked
enjoooooy
Locked - now what?OEM unlock option
The above does not mention one additional step: disabling OEM unlock in developer options. For a reason. I mean you CAN uncheck that option now that all is running fine but you don't get any more security tbh.
The reason is if you keep it checked an attacker is able to unlock your device but it WILL format the encryption keys when done. that means no way to access your data anyways. If you want to avoid even that then feel free to uncheck OEM unlock in developer settings as well but then a brick will require low level recovery tools to bring your device back to life.
Magisk (rooted variant)
I recommend to disable automatic update checking within magisk settings - remember: when flashing a newer version of magisk it WILL brick your device. you have to wait for me updating it within the ROM.
Anything you do within Magisk can EASILY BRICK your device, installing a magisk module which tampers your system partition: BRICK. So really really check if a module touches anything mentioned in the above checklist topic. Using the magisk variant has HIGH potential of bricking your device.
You can use all standard root functions, magisk hide and even re-pack the magisk app though.
Bricked
Always keep an eye on the above "Checklist" topic! If you change/do something mentioned there you will brick your device with a snap of a finger.
Android does not boot anymore because you flashed a newer version of Magisk or changed something within the protected partitions:
boot recovery (power off, press power on and vol down the same time and keep it pressed until you see the shrp logo)
flash the current ROM version or a later release and reboot
recovery does not load bc you flashed another recovery:
wait for the next OTA and it get fixed automatically
or unlock the bootloader again (this will need to FORMAT the userdata partition)
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
L4WL13T said:
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
Click to expand...
Click to collapse
hard to say. there are some which might not work and/or apps you should avoid (as they contain trackers etc). There is a good list of alternatives in FAQ 4 above
steadfasterX said:
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything
Click to expand...
Click to collapse
Do TWRP backups even work on this device? Last I heard, it was broken.
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
ap81z said:
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
Click to expand...
Click to collapse
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
steadfasterX said:
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
Click to expand...
Click to collapse
ok, I'll be waiting!!!
forgot to mention it here (another reason why users should join my automation channel):
Gestures are supported since the latest version.
breaking news:
I was working on using this device as my DD again but I have very strict requirements:
/e/ OS must work (reason: privacy focus, google-free) [ DONE ]
encryption must work (reason: security, e.g. loosing or selling the phone) [ DONE ]
selinux must run in enforcing [ DONE ]
/e/ OS must be signed with own private key (reason: allowing secure OTA and local/recovery upgrades) [ DONE ]
SHRP must work (reason: a password on startup can be set - allowing to have rich recovery feature set but secured - when the bootloader is locked!) [ DONE ]
and here the fun began:
/e/ OS must run on locked bootloader [ DONE ]
SHRP must run on locked bootloader [ DONE ]
OTA must work on locked bootloader [ WIP ]
so overall I am pretty much where I want to be and can provide a privacy focused, secure, google-free and locked bootloader experience soon...
stay tuned
Ever wanted to lock your bootloader - not on STOCK but on a custom ROM?Most ppl don't know (or don't care) that almost all Oneplus devices offer such an option - if the ROM dev is willing to take the journey implementing it.
This is now possible when running my /e/ OS CUSTOM builds (read more in the OP about the diff between CUSTOM and UNOFFICIAL) and not just that my new CUSTOM builds coming either pre-rooted or not - whatever you wish more.
I have to say that this was something on my to-do list since I bought this device more then 1 year ago. After a lot of work in the past months I am finally where I am and can use it as my DD again. Something which makes me reeeeeeally happy lol
Dunno but maybe someone enjoys having a locked bootloader like I do
Read all the details and how it works: here
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Also I doesn't find any option to change 60hz/90hz ?
Thetimelost said:
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Click to expand...
Click to collapse
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Thetimelost said:
Also I doesn't find any option to change 60hz/90hz ?
Click to expand...
Click to collapse
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
steadfasterX said:
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
Click to expand...
Click to collapse
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Thetimelost said:
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Click to expand...
Click to collapse
Hm interesting mine is running at 90 hz all the time it seems. Weird bc /e/ is based on LOS so maybe its an option in a11 first?
When will we get Android 11?
andr052h said:
When will we get Android 11?
Click to expand...
Click to collapse
Why do you want to have it?
steadfasterX said:
Why do you want to have it?
Click to expand...
Click to collapse
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
andr052h said:
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
Click to expand...
Click to collapse
Well first of all I thought no one uses my ROM anyways so there was no need for me upgrading to a11. This ROM is rock stable and does what i need as a daily driver and gets monthly security patches. Many ppl just want to have a newer android version just bc there is one and not bc for a specific reason. That's why I'm asking.
I personaly prefer a good working ROM over having always the newest android version just because there is one
Other then that i may upgrade to a11 but not anytime soon. Main reason is that I am using this as my daily driver so it would be hard alsi dev on it..
HELLo everyone...
After several weeks, months and before Android 12 released, i decided to share this ROM to this A51 community. Hopefully you guys enjoy it and don't offend me if the ROM is bad, so....let's get it ON.
Things to do before flashing:
1. Make sure you're on binary 5 (this ROM tested and using binary 5 vendor, so to avoid any broken or whatever error flash your device with latest firmware).
2. Backup your IMEI (highly recommended).
Flashing:
1. Clean flash is recommended. Flash kernel, flash J4F vendor and system.img, flash multy disabler (if necessary) then full wipe and also you can perform "typing YES" format. Reboot to recovery again, then flash as usual you guys always do (Magisk etc.).
ROM Features from S20 and Note 20 line up:
1. Samsung Dex (not full features coz need fix at kernel level).
2. Flagship live blur
3. Flagship edge lighting style
4. AirCommand (S pen)
5. LiveDrawing
6. Multy screen resolutions (HD+ - FHD+ - WQHD+)
7. 1000++ system fonts
8. Flagship sound quality and effects
9. Camera features unlocked (pro video etc.)
10. All original A51 features
11. Common tweaks here and there and so many possibility to unlock another S20 features
Bugs:
Minor glitch in pro mode video, and not really remember and deep testing everything, but hopefully still acceptable (hopefully ) but yeah..nothing's perfect, if you found one let's discuss together in A51 telegram group: https://t.me/samsunga51
Hall of Fame:
@MrWaehere for his awesome CRB kitchen
@VDavid003 and his rom TreeUI for my inspiration and countless help
@Yillié and his OFox recovery and also countless help and advise and ideas
@BlassGO and his Dynamic Installer, patches, advise and countless contributions (thanks for making AirCommand even greater lol)
@manudinath and his projects.
@Winb33 for fonts mod
@topjohnwu for Magisk
@ianmacd for multy disabler and TWRP
Stock Kernel Source
PM me if i forgot to mention someone.
Advise and Tips:
- It's normal during first boot if lags occurs, give the ROM some times to settle, finish your setup, update your apps and you good to go..
- It's better to avoid update in Galaxy store related to system app, such as MDE Service Framework, Samsung Core Services etc. It might causing conflict due to mixed up firmware. But anyway it's up to you.
- Please do not complain regarding app missing (getting debloated) and related to debloat. Because it's very hard to acomodate every person's taste. Bloatware is very Objective and absurd for each person and I know it's supposed to be using Aroma installer or any script but i don't have time that much to do that.
Download link:
**when you click this link and downloading, that's mean you're agree to all the consequences and i'm not responsible to anything - do with your own risk**
LINK
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Yillié said:
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Click to expand...
Click to collapse
nah, you have doing so great/ thank you s much for everything.
Testing .
perro
Ole its already, nice
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
Ia possible wirh This vendor run fingerprint perfectly in havoc
Badger50 said:
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
Click to expand...
Click to collapse
If run for You send details my friend
Someone knows how to pass CTSprofile in magisk with this rom?
gobblefunk said:
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
Click to expand...
Click to collapse
system and vendor.
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
mhm...thanks for everything
jagpanzer said:
system and vendor.
Click to expand...
Click to collapse
Kernel 11 support this ROM?
Magisk 23.1
Download Magisk 706a4922 alpha apk
Download File Magisk 706a4922 alpha apk
apkadmin.com
Changelog magisk 23.1
DOWNLOAD VERSion ALPHA:
Magisk v23.1 (706a4922-alpha)
Changelog:
• Switch to zygisk to execute the deny list,
• Magiskhide has been completely removed
• Denylist Added
• Restart to take effect after changing the switch state of zygisk
• Major changes, some problems may occur, temporarily not pushed to the update channel
Others changes in APK:
[General] supports pure 64-bit devices
-[General] Support Android 12 emulator
-[Zygisk] code injection framework
-[General] Remove MagiskHide
-[General] Support simulator loading module
-[MagiskBoot] supports zImage format
-[MagiskBoot] Add zopfli encoder
-[MagiskInit] supports boot configuration
-[App] Repair installation function will now check whether the script under /data/adb/magisk/ is not updated
-[MagiskInit] supports some Meizu devices
-[MagiskSU] If supported by the kernel, use isolated devpts
-[MagiskSU] Fix pts configuration code, no additional sepolicy rules are now required
-[MagiskBoot] supports v4 boot image header format
-[MagiskInit] Support some OnePlus and Opal devices Oplus.fstab
-[App] The update module needs to be restarted, mark deletion is not allowed
-[App] Delete online warehouse
-[App] Add mount information to the saved log file
-[App] Adapt to Android 12 API level
-[App] Display running waiting pop-up window when hiding/resuming the application
-[Stub] Open source obfuscation function
-[Script] View and display the sepolicy rule folder of the module
-【App】Hide the screen overlay when you need to pop up the window. Android 12+
-[App] Delete the floating bottom bar and change it to a general bottom operation bar
-[General] Support compilation cache
-[General] Added rejection list function
-[App] Delete DoH
-[App] Delete SafetyNet
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Bluetooth connect error
hacker812c said:
Kernel 11 support this ROM?
Click to expand...
Click to collapse
during testing i only test with BF2. you can try
Arya1999 said:
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Click to expand...
Click to collapse
sorry, no time.
Inomjon6940🇺🇿 said:
Bluetooth connect error
Click to expand...
Click to collapse
last time i try with old BT 4.0 earphone was fine and also BT call. will test again, on last build i've made changes and could be broke something
/* Disclaimer */
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 kernel
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. Hard. A lot.
/* Features */
Fully rebased kernel without unnecessary OnePlus code
Latest CAF msm-5.4 kernel fully merged
Latest Linux v5.4 subversion merged
Latest Google’s security fix merged
Modules support disabled for lighter kernel
Latest Wi-Fi drivers from Qualcomm with customized config
Built with Clang 15
Power optimizations
More to come soon
/* Notice */
This kernel is not based on the stock OxygenOS kernel source provided by OnePlus.
Only the necessary parts from the OnePlus kernel have been added, such as device specific drivers.
This effectively kills all kernel modifications/optimizations from OnePlus.
OxygenOS 11 is not supported.
Non-OxygenOS custom ROMs are supported.
Custom ROMs that uses OxygenOS 12 kernel and vendor, including LineageOS 19.1, are supported.
As of right now, the tri-state-key does not work. Any post complaining about this will be ignored.
Due to recent f2fs changes in kernel, you may need a format post flashing the kernel.
This kernel touches vendor_boot, boot and dtbo partitions, meaning you'd need to restore said partitions whenever you're switching to another kernel or stock.
Please make a back-up of these partitions.
Installing the stock ROM with a full OTA restores said partitions as well.
/* Thanks to */
ZVNexus
tangalbert919
Vishalcj17
kristofpetho
kdrag0n
arter97
Divyanshu-Modi
kerneltoast (SultanXDA)
/* Instructions */
Backup the above mentioned partitions.
Reboot to recovery.
Flash the zip. ( can adb sideload on recovery)
Enjoy
/* Downloads and links */
Latest Release
Nightlies Channel
Kernel source
Telegram Chat
reserved
reserved2
reserved3
Hi, can i do adb sideload zip?
Very nice. I'm gonna test this out later.
Cheers!!!
PKkeys said:
Hi, can i do adb sideload zip?
Click to expand...
Click to collapse
Successfully flashed with kernel flasher app on OP9 upon lineage 19. Got a warning message about internal problem on start up but seems ok. Didn't need to format.
sbute said:
Successfully flashed with kernel flasher app on OP9 upon lineage 19. Got a warning message about internal problem on start up but seems ok. Didn't need to format.
Click to expand...
Click to collapse
you can ignore that warning, its due to modules being disabled.
Rasenkai99 said:
you can ignore that warning, its due to modules being disabled.
Click to expand...
Click to collapse
Ok, should I stay away from this kernel ?
sbute said:
Ok, should I stay away from this kernel ?
Click to expand...
Click to collapse
up to you?
that warning occurs when userspace reads /proc/config.gz and throws out an error message after boot completes. In a nutshell its just eye candy and nothing is really broken.
Fastest kernel I've ever used
Hi @Rasenkai99,
Download links must be able to be used without registering at an external site. The easiest way to test if a download link will meet this specification is to right-click the link and open in Incognito mode (Chrome), or Private window (Firefox) or InPrivate window (Edge). If you can get to the place to download the file(s) without logging in to the site from there, then it's acceptable as long as it also meets all our other rules.
Please change Downloads Channel to a link that will work for anyone without registering elsewhere within 24 hours of now. I will be monitoring the thread and looking for the change.
Reference the details of using Telegram for download links in the stickied post at the top of each section "[General] [INFO] Device Forum Rules (Please Read before Posting)", specifically Post #5 "WhatsApp/Telegram Groups and Channels - Going Forward"
Thank you,
@roirraW "edor" ehT
Stephen said:
WhatsApp/Telegram Groups and Channels - Going Forward
Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA.
What does that mean?
We will allow links to messages on Telegram and/or other platforms anywhere, as long as they provide content for a discussion, question, or is pertinent news. This is exactly like the guidelines for YouTube links.
What about download links?
Download links from hosts, platforms or other sources are allowed as long as they do not require registration. Some Telegram links require registration for downloads, so they will not be allowed. Please check them before posting.
What is NOT changing?
Only one link to a Telegram support group is allowed in the first post of a development thread on the condition that main support is still provided on XDA. This means you can mention Telegram group: https://t.me/abc in the first post as long as you're providing thorough support in your XDA thread.
What is NOT allowed?
Posts like For support, join my Telegram group: https://t.me/abc. This means you're not willing to provide support to users on XDA.
Drop-and-run posts/threads are still not allowed under the self-promotion rule. So posts/threads like "Come to my channel for xyz" or "Watch my video and like my channel" are still not allowed. Such links will be removed and the member will be contacted regarding XDA Forum Rule #5 for self-promotion (under bullet point #6):
We thank all members for their cooperation in this matter, and wish you a pleasant stay on XDA.
Regards,
Your XDA Moderating Team
Click to expand...
Click to collapse
roirraW edor ehT said:
Hi @Rasenkai99,
Download links must be able to be used without registering at an external site. The easiest way to test if a download link will meet this specification is to right-click the link and open in Incognito mode (Chrome), or Private window (Firefox) or InPrivate window (Edge). If you can get to the place to download the file(s) without logging in to the site from there, then it's acceptable as long as it also meets all our other rules.
Please change Downloads Channel to a link that will work for anyone without registering elsewhere within 24 hours of now. I will be monitoring the thread and looking for the change.
Reference the details of using Telegram for download links in the stickied post at the top of each section "[General] [INFO] Device Forum Rules (Please Read before Posting)", specifically Post #5 "WhatsApp/Telegram Groups and Channels - Going Forward"
Thank you,
@roirraW "edor" ehT
Click to expand...
Click to collapse
i have added a latest release linking to gdrive download and a nightlies which directs to the previous downloads link. i hope that is acceptable.
Rasenkai99 said:
i have added a latest release linking to gdrive download and a nightlies which directs to the previous downloads link. i hope that is acceptable.
Click to expand...
Click to collapse
The Google Drive link is definitely acceptable for the main download link. Thanks for your fast action.
I will confer with my teammates and let you know about the nightlies link as soon as I can. The TG link for only the nightlies is fine, thanks again.
Thanks!
@roirraW "edor" ehT
Work with 9pro ?
paingod1987 said:
Work with 9pro ?
Click to expand...
Click to collapse
Well it is in the 9pro forums.....
Happy to see some more kernels for A12
I guess I didn't get it right. Apologize my inconvenience, but does this kernel work on stock and custom oos12 roms?
DroidShift79 said:
I guess I didn't get it right. Apologize my inconvenience, but does this kernel work on stock and custom oos12 roms?
Click to expand...
Click to collapse
only custom oos12 roms. Stock rom is not supported.