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.
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Prague power profile.
Do I need it?
Well, better having than don't.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in there, if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a PRA-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay from the Downloads session.
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-PRA.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Prague Series devices (all variants), Device Specific App for the Huawei P8lite/P8 Lite
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-06-26
Last Updated 2018-06-26
Definitely will be useful. Thanks a lot, Dil3mm4!
Hi Dil3mm4,
Thanks for your work, but I'm not sure what this app does exactly, will it help me for example with substratum themes? Thanks
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Graveen said:
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Click to expand...
Click to collapse
Our device is arm64 A only (PRA-LX1 is my device)
If the APK is included in the rom u want to flash just run the command below, if not, after flashing just install the overlay according to the instructions. Have a nice day!
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
mannas said:
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
Click to expand...
Click to collapse
Nope
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
Hey Dilemma! I have an issue with all the Treble Roms. After listening to music for a while, the playback stops and I have to restart it, or when I plug a headphone in and then out, sound usually doesnt come out of the speaker. Will this overlay fix the issues I have with treble Roms? Thanks in advance
Please help with a little overlay
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Click to expand...
Click to collapse
Hello Dil3mm4.
Sorry to send you PM, i see after sending that's not ok. I really want to solve Overlay issue for my Huawei Fig-LX1.
I try to join Telegram group indicated by you but could not find it. Maybe is not existing anymore. So - my last chance is you to respond here.
I just want you to make an overlay for my phone to work better with Phusson Treble 8.1. Just tell me what files do you need and i will do it.
Maybe you answer me.
Thanks!
Hi, by fixing BLE, you mean bluetooth low energy, like huawei band, fossil Q ?
thanks
Thanks! U did great!
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Traceur017 said:
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Click to expand...
Click to collapse
install terminal emulator , put the .APK (be sure to rename the last build taking the -P ) in the mencioned directory but first run the following command:
su
mount -o remount,rw /vendor
after this you can run the command for the apk.
It worked for me. or at least.. didnt gave an error... so.. lolol
I think I've installed it correctly but How can I see changes? Nothing added!
Hello, I have a PAR-AL00 device. Can you make an overlay for me.and Telegram group @GSI_HI6250, I can't find it.Thank you verymuch.
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
I can't find it where is it?
artus777 said:
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
Click to expand...
Click to collapse
Is this overlay necessary under Lineage 18.1 (PRAGUE device and EMUI 8.0.0.390)?
@Dil3mm4 Thread closed! Please advise the moderators team (best via the report function) to re-open the thread when ready to provide a download link for this former DevDB thread.
Regards
Oswald Boelcke
Senior Moderator
Hello xda ppl!
may be it will be useful for you.
many time was spent trying to do something good with this cpu,
to make it not so hot but fast and efficient.
so, here cooling is priority.
1. global configs
memory, cpu, gpu, thermal, doze ...
for android 6-7-8
files "thermal-engine.conf", "init.qcom.post_boot.sh"
paths detecting via existing thermal config
existing files backup ("~" suffix)
installation output, at the end there should be listing of 2 new and 2 backuped files
to revert just rename backuped files (root/twrp file manager)
2. profiles switch from status bar
its simplification of this one https://forum.xda-developers.com/android/apps-games/app-spectrum-kernel-manager-users-t3601542
for android 6-7-8 (but only if your OS has support of initialization from "/system/etc/init" (its standard))
files "/system/app/Spectrum/Spectrum.apk", "/system/etc/init/init.spectrum.rc", "/system/etc/init/init.spectrum.sh"
installation output, at the end there should be listing of 3 new files
to revert just install "SimpleSpectrum-uninstall.zip"
global configs + performance profile should be good for games.
and cool. like COOL1 should be
XDA:DevDB Information
cpu_tuning-difrED, Tool/Utility for the Coolpad Cool1
Contributors
difr
Version Information
Status: Beta
Created 2018-08-29
Last Updated 2018-08-29
1. configs script didnt work and didnt make error in case of absent thermal config in system (i didnt expect such case). so, i've made small update.
2. spectrum app no need root so often. also updated.
3. i also recommend to disable standard power control, just rename "/system[/vendor]/lib64/hw/power.qcom.so" to "power.qcom.so~". attached zip is for this purpose.
4. i see some donwloads and no one review it. it's bad. bad community, sorry
I will try now on los 15.1 beta
Edit : Im Already flash on los 15.1 and installed but can't open spectrum app, in playstore say installed but cant open ? And in launcher not see icon spectrum, i replace with 1.5 version work nice
Fauzi Hamzah said:
I will try now on los 15.1 beta
Edit : Im Already flash on los 15.1 and installed but can't open spectrum app, in playstore say installed but cant open ? And in launcher not see icon spectrum, i replace with 1.5 version work nice
Click to expand...
Click to collapse
its hidden in launcher. its available in status bar as tile
difr said:
its hidden in launcher. its available in status bar as tile
Click to expand...
Click to collapse
Ok i will try replace again with your app
Edit : it work but not see gaming profile
Bro since leeco los have smanager maybe you can add mod for this https://4pda.ru/forum/index.php?s=&showtopic=911910&view=findpost&p=75788964 , i think it will be conflict
Edit again ?, not will conflict just delete profile in smanager if use this
@Fauzi Hamzah
3 modes.
difr said:
@Fauzi Hamzah
3 modes.
Click to expand...
Click to collapse
Ok thanks bro for now just test battery mode, because not have heavy game , lazy to download ?, waiting black desert mobile global need long time
Btw thermal config in oreo just in vendor/etc ?, not see in /etc
Fauzi Hamzah said:
Ok thanks bro for now just test battery mode, because not have heavy game , lazy to download ?, waiting black desert mobile global need long time
Btw thermal config in oreo just in vendor/etc ?, not see in /etc
Click to expand...
Click to collapse
right. means oreo also is without thermal config. didnt know it
seems like all le2 ports are without thermal config
did you see patch output?
it should show error, unable to find thermal config
means patch doesnt do his work
need to rewrite it again for oreo
please, confirm that you dont see /vendor/etc/thermal-engine.conf
difr said:
right. means oreo also is without thermal config. didnt know it
seems like all le2 ports are without thermal config
did you see patch output?
it should show error, unable to find thermal config
means patch doesnt do his work
need to rewrite it again for oreo
please, confirm that you dont see /vendor/etc/thermal-engine.conf
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=1LRcwuqfzXldGofnPdxiH5_DaZxwIDuiY&usp=sharing , you mean logcat ? and i cant upload on attach xda ?
Edit : Oh i see already edit v6 on /vendor/etx
Btw is possible to add fast charge like another phone ?
difr said:
Hello xda ppl!
may be it will be useful for you.
many time was spent trying to do something good with this cpu,
to make it not so hot but fast and efficient.
so, here cooling is priority.
1. global configs
memory, cpu, gpu, thermal, doze ...
for android 6-7-8
files "thermal-engine.conf", "init.qcom.post_boot.sh"
paths detecting via existing thermal config
existing files backup ("~" suffix)
installation output, at the end there should be listing of 2 new and 2 backuped files
to revert just rename backuped files (root/twrp file manager)
2. profiles switch from status bar
its simplification of this one https://forum.xda-developers.com/android/apps-games/app-spectrum-kernel-manager-users-t3601542
for android 6-7-8 (but only if your OS has support of initialization from "/system/etc/init" (its standard))
files "/system/app/Spectrum/Spectrum.apk", "/system/etc/init/init.spectrum.rc", "/system/etc/init/init.spectrum.sh"
installation output, at the end there should be listing of 3 new files
to revert just install "SimpleSpectrum-uninstall.zip"
global configs + performance profile should be good for games.
and cool. like COOL1 should be
XDA:DevDB Information
cpu_tuning-difrED, Tool/Utility for the Coolpad Cool1
Contributors
difr
Version Information
Status: Beta
Created 2018-08-29
Last Updated 2018-08-29
Click to expand...
Click to collapse
seems to work in lineage 15.1! thank you very much, it's very convenient and useful! (on v6 version)
cant understand. does it work in oreo?
do you see /vendor/etc/thermal-config.conf (with my sign inside).
@Fauzi Hamzah, no i dont mean logcat. i mean installation output in twrp. there must be detailed listing of processed files or error message
i use it in jui7. didnt test it in other roms
difr said:
cant understand. does it work in oreo?
do you see /vendor/etc/thermal-config.conf (with my sign inside).
@Fauzi Hamzah, no i dont mean logcat. i mean installation output in twrp. there must be detailed listing of processed files or error message
i use it in jui7. didnt test it in other roms
Click to expand...
Click to collapse
Ok i will reflash again, but in vendor/etc already with you mod thermal v6 but not see init.qcom
Fauzi Hamzah said:
Ok i will reflash again, but in vendor/etc already with you mod thermal v6 but not see init.qcom
Click to expand...
Click to collapse
it must be in /vendor/bin in oreo
difr said:
it must be in /vendor/bin in oreo
Click to expand...
Click to collapse
Yeah you're right and already mod v6 :good:
This first time i use oreo so dont know at all
I think it work like a charm
Can you add fast charging like this https://forum.xda-developers.com/ne...d-xthermal-mod-fast-charging-cpu-gpu-t3477639
Fauzi Hamzah said:
Can you add fast charging like this https://forum.xda-developers.com/ne...d-xthermal-mod-fast-charging-cpu-gpu-t3477639
Click to expand...
Click to collapse
no, its enough hot without fast charging
wtf,
more than 50 downloads
noone reviewed.
difr said:
wtf,
more than 50 downloads
noone reviewed.
Click to expand...
Click to collapse
maybe you can create for universal not just this phone: D
I test pubg not heating like before (nougat without config) and now use this config with gpu turbo boost v2, I can get HDR 60fps in 960p resolution use gfx tool with some fps drop but still playable :good:
C107-9
Can all this tweak work for cool pad c106-9
---------- Post added at 05:42 AM ---------- Previous post was at 05:39 AM ----------
Can I install 7.0 ROM on my Cool pad cool changer 1c
difr said:
Hello xda ppl!
may be it will be useful for you.
many time was spent trying to do something good with this cpu,
to make it not so hot but fast and efficient.
so, here cooling is priority.
1. global configs
memory, cpu, gpu, thermal, doze ...
for android 6-7-8
files "thermal-engine.conf", "init.qcom.post_boot.sh"
paths detecting via existing thermal config
existing files backup ("~" suffix)
installation output, at the end there should be listing of 2 new and 2 backuped files
to revert just rename backuped files (root/twrp file manager)
2. profiles switch from status bar
its simplification of this one https://forum.xda-developers.com/android/apps-games/app-spectrum-kernel-manager-users-t3601542
for android 6-7-8 (but only if your OS has support of initialization from "/system/etc/init" (its standard))
files "/system/app/Spectrum/Spectrum.apk", "/system/etc/init/init.spectrum.rc", "/system/etc/init/init.spectrum.sh"
installation output, at the end there should be listing of 3 new files
to revert just install "SimpleSpectrum-uninstall.zip"
global configs + performance profile should be good for games.
and cool. like COOL1 should be
XDA:DevDB Information
cpu_tuning-difrED, Tool/Utility for the Coolpad Cool1
Contributors
difr
Version Information
Status: Beta
Created 2018-08-29
Last Updated 2018-08-29
Click to expand...
Click to collapse
Thanks man, this works great. Why do u want us to disable standard battery options?? Is that bound to create problems or conflict?
Thanks again
Hey!
I try to port nethunter kernel to redmi 7.
But every restart i got this message: "There is an internal problem with your device ..."
build.date, build.date.utc, build.fingerprint lines are the same at /vendor/build.prop and /system/build.prop files.
When I not change anything in the source code, and build and install then no message.
Only System V IPC & Generic IEEE 802.11 Networking Stack (mac80211) & Ralink WLAN USB Driver Enabled.
Everything works fine no kernel panic or etc. just the message is confusing.
Can I somehow find out the cause of the problem?
I'm not alone
I'm on the same problem but I know only show that error when activate System V IPC option, I'm also try to do with nethunter and that exactly drivers, but I'm doing in a Moto E5 Play.
EDIT:
I found that android disable this feature: "System V IPC" Because it cause a security vulnerability, they using "Android Shared Memory"(ASHMEM) instead, and there is a repo that emulates the System V using ASHMEM
So, the warning is because android dislikes that system, nothing to worry if you can take the risk, and the message doesn't bother you, I'll try the "android-shmem" from pelya.
Good luck.
reno_axel said:
I'm not alone
I'm on the same problem but I know only show that error when activate System V IPC option, I'm also try to do with nethunter and that exactly drivers, but I'm doing in a Moto E5 Play.
EDIT:
I found that android disable this feature: "System V IPC" Because it cause a security vulnerability, they using "Android Shared Memory"(ASHMEM) instead, and there is a repo that emulates the System V using ASHMEM
So, the warning is because android dislikes that system, nothing to worry if you can take the risk, and the message doesn't bother you, I'll try the "android-shmem" from pelya.
Good luck.
Click to expand...
Click to collapse
Zer0nite said:
Hey!
I try to port nethunter kernel to redmi 7.
But every restart i got this message: "There is an internal problem with your device ..."
build.date, build.date.utc, build.fingerprint lines are the same at /vendor/build.prop and /system/build.prop files.
When I not change anything in the source code, and build and install then no message.
Only System V IPC & Generic IEEE 802.11 Networking Stack (mac80211) & Ralink WLAN USB Driver Enabled.
Everything works fine no kernel panic or etc. just the message is confusing.
Can I somehow find out the cause of the problem?
Click to expand...
Click to collapse
It means that kernel is not compatible with you ROM bro.
Zer0nite said:
Hey!
I try to port nethunter kernel to redmi 7.
But every restart i got this message: "There is an internal problem with your device ..."
build.date, build.date.utc, build.fingerprint lines are the same at /vendor/build.prop and /system/build.prop files.
When I not change anything in the source code, and build and install then no message.
Only System V IPC & Generic IEEE 802.11 Networking Stack (mac80211) & Ralink WLAN USB Driver Enabled.
Everything works fine no kernel panic or etc. just the message is confusing.
Can I somehow find out the cause of the problem?
Click to expand...
Click to collapse
Every KERNEL have / has compatible Android version. And every kernel has / have a compatible ROM. Don't ignore that bro. Just restore your stock kernel.
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